After a number of fatal crashes with opensuse 15.6 due to updates to certain programs, I wonder how to prevent these updates from appearing in Notifications at the bottom right,
(software updates). The reason is simple: updates are not tested and it is incredibly difficult to save files from disk.
Please: be very clear with the description so that a 75 year old novice
can do it. SUSE before they were sold, was much more stable
than today’s openSUSE!
I am patient 
, but what you write here is nonsense. Every update is tested. See openqa.opensuse.org
What do you mean by this?
The fact that SUSE was sold ( in my days Novell, Microfocus, Attachmate, EQT ) is absolutely not related to stability of the distros.
That said, prejudice / assumptions like this actually can be in the way re. the user’s options to solve matters.
One does not selectively update individual packages. In your case (Leap 15.6) one uses the Update repos (preconfigured) and YaST Software Management, or (preferably) Myrlyn, which has a single click Update button that does it all.
FYI: I’m 65, so not too much difference 
- You need to be very specific … what are “certain programs”?? … also, “what” is crashing??
- Turn Off auto-update if it’s Enabled - Or maybe you just click to Update without reviewing the update(s).
- “save files from disk” … what does that mean? Are you referring to performing a “backup” of your system? If yes, that’s easy … use “rsync” once a week … or some other backup software tool. That’s a user’s responsibility.
- Let us know which “sell” you’re referring to.
.
For us on our few machines:
For #1 … have never had any crash with 15.6.
For #2 … we only use “zypper up” for 15.6 updates.
For #3 … we do a weekly “rsync” to backup - it takes about 15 minutes on average, to do a backup.
For #4 … Been using SUSE since before Release 6.1 … any “sell” never mattered
Well, it’s not very useful to repeat what I already posted, right?
1 Like
Hi!
How to prevent update? Do I have an unusually odd system?
09:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 85e7
Flags: bus master, fast devsel, latency 0, IRQ 116
Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
Memory at d8000000 (64-bit, prefetchable) [size=128M]
Memory at e0000000 (64-bit, prefetchable) [size=32M]
I/O ports at f000 [size=128]
Expansion ROM at fc000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel driver in use: nouveau
Kernel modules: nouveau
0a:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c98
Flags: bus master, fast devsel, latency 0, IRQ 118
Memory at f9000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at fa000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting <?>
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel driver in use: nouveau
Kernel modules: nouveau
Model name: AMD Ryzen 9 3900X 12-Core Processor
Thread(s) per core: 2
Socket(s): 1
NUMA node(s): 1
NUMA node0 CPU(s): 0-23
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: KINGSTON SNV3S1000G
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 17725F35-B556-4197-9084-E6648769C07F
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 1949329407 1948278784 929G Linux filesystem
/dev/nvme0n1p3 1949329408 1953525134 4195727 2G Linux swap
Disk /dev/loop0: 73.92 MiB, 77508608 bytes, 151384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 505.41 MiB, 529956864 bytes, 1035072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 50.77 MiB, 53235712 bytes, 103976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 2502
Release Date: 11/11/2020
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.17
Handle 0x0043, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 9
Currently Installed Language: en|US|iso8859-1
dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Pro WS X570-ACE
Version: Rev X.0x
Serial Number: 200772084000311
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Regards
Please next time use Code-Tags:
Code-Tags
Post:
zypper lr -d
How do you expect us to guess what program generates those notifications? Start with telling us what desktop environment you are using.
You disable automatic update in whatever program you are using or disable autostart of this program if it does not have such option. If you need step by step guide, you need to tell what program you are using.
Here’s how you can turn them off in Gnome:
To disable auto update checking in GNOME Software on openSUSE, you can use the dconf-editor to navigate to /org/gnome/software/ and set allow-updates to false. Alternatively, you can run the command gsettings set org.gnome.software allow-updates false in the terminal.
Not sure what Desktop Environment you are running, but hopefully this might help you to solve your problem if you are on Gnome. You would then need to use the Terminal and sudo DUP up to get updates in the future though.
If you are using another Desktop perhaps let us know on here and someone who knows that one will be able to help?
Yes, you have an “odd” system.
The GeForce GT 710 is an old card supported by the (old) G05 proprietary drivers.
The GeForce GT 1030 is a newer card supported by the G06 proprietary drivers.
You are currently using both with the open source nouveau driver, so you are using both with minimal performance.
I don’t know if your problems are related to that “odd” graphics configuration; if so, please be specific and maybe somebody here might devise a solution.
Again, please use pre-formatted text ( </> ) to post output.
Like this snippet here
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.