- openSUSE Support

Both XFCE and Upower unable to execute the "Hybrid-Sleep"
by Marco Calistri 11 Jun '21

11 Jun '21

Hello, From some quite time I'm trying to enable the hybrid-sleep feature whenever battery level hit the critical threshold. Despite the fact that by running the command from the console it works perfectly, it doesn't using Upower or Xfce-power-manager. In the better cases I just obtain the Hibernate of the system. Is there anybody having a solution for this? I would like to both suspend and saving on disk my windows and tasks opened if the battery drops to critical charge. Thanks for your attention. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20210606 Kernel:5.12.9-1-default Desktop: XFCE (4.16.0)

1 0

cups HP printer not working - Busy - "Waiting for the printer to become available."
by michael.kasimir＠gmx.de 10 Jun '21

10 Jun '21

Hi all, Busy - "Waiting for the printer to become available." I cannot get HP printer 2100 Series to run. For beginning analysis I tried the obvious: $ lsusb Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0424:5534 Standard Microsystems Corp. Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04f2:b3ca Chicony Electronics Co., Ltd Bus 001 Device 005: ID 03f0:581d Hewlett-Packard lt4112 Gobi 4G Module Network Device Bus 001 Device 009: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0424:2134 Standard Microsystems Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ $ sudo cat /etc/cups/printers.conf | egrep -i 'model|device' [sudo] password for root: MakeModel HP LaserJet 2100 - CUPS+Gutenprint v5.2.14 DeviceURI usb://HP/LaserJet%202100%20Series MakeModel HP LaserJet P3005 - CUPS+Gutenprint v5.2.14 DeviceURI hp:/usb/HP_LaserJet_P3005?serial=CNF1T65817 MakeModel HP LaserJet 2100 - CUPS+Gutenprint v5.2.14 DeviceURI usb://HP/LaserJet%202100%20Series $ $ lpstat -t -v -r -H scheduler is running system default destination: HP-LaserJet-2100-Series device for HP-LaserJet-2100-Series: usb://HP/LaserJet%202100%20Series device for HP-LaserJet-P3005: hp:/usb/HP_LaserJet_P3005?serial=CNF1T65817 device for hplaserjet2100series: usb://HP/LaserJet%202100%20Series HP-LaserJet-2100-Series accepting requests since Thu 10 Jun 2021 12:50:25 CEST HP-LaserJet-P3005 accepting requests since Thu 10 Dec 2020 16:12:28 CET hplaserjet2100series accepting requests since Fri 04 Jun 2021 17:30:42 CEST printer HP-LaserJet-2100-Series now printing HP-LaserJet-2100-Series-155. enabled since Thu 10 Jun 2021 12:50:25 CEST Waiting for the printer to become available. printer HP-LaserJet-P3005 disabled since Thu 10 Dec 2020 16:12:28 CET - Unplugged or turned off printer hplaserjet2100series disabled since Fri 04 Jun 2021 17:30:42 CEST - Unplugged or turned off HP-LaserJet-2100-Series-155 mick 29696 Thu 10 Jun 2021 12:50:25 CEST device for HP-LaserJet-2100-Series: usb://HP/LaserJet%202100%20Series device for HP-LaserJet-P3005: hp:/usb/HP_LaserJet_P3005?serial=CNF1T65817 device for hplaserjet2100series: usb://HP/LaserJet%202100%20Series scheduler is running /run/cups/cups.sock $ $ lpq HP-LaserJet-2100-Series is ready and printing Rank Owner Job File(s) Total Size active mick 155 Anschreiben_A.docx 29696 bytes $ What I found interesting is: scheduler is running I didn't start a scheduler and had no idea to kill the scheduler. I see here, the document ''Anschreiben_A.docx'' is in queue. Hope someone can help... Kind regards Michael Be Free, Be Linux

4 4

Re: zypper patch about to uninstall half (all?) of leap 15.3 installation?
by Bob Williams 09 Jun '21

09 Jun '21

On Tue, 8 Jun 2021 17:39:46 +0200 Marcus Meissner wrote: > HI, > > Update ... this is still work in progress, I hope I will get through > most of the issues this week. > > Ciao, Marcus Will you announce the completion of the work, so that we know when we can use zypper patch again? Bob -- Bob Williams System: Linux 5.3.18-lp152.50-default Desktop: KDE Frameworks: 5.71.0, Qt: 5.12.7 and Plasma: 5.18.5 https://useplaintext.email/

3 4

Re: laptop microphone stopped working - solution found
by Matthew 09 Jun '21

09 Jun '21

2 1

YaST2 Partitioner in Leap 15.3: Create New Partition Table is Missing
by Ali 09 Jun '21

09 Jun '21

Hi, In YaST2 Partitioner of Leap 15.2, by selecting modify for a disk an option appears to "Create New Partition Table". This is very useful especially in AutoYaST. However in Leap 15.3, there is no longer such an option. When a disk is selected, clicking the edit button no longer presents an option to create a new partition table; it just allows to create a filesystem on the whole disk. Is this change intentional? Thanks, Ali

1 1

Re: zypper patch about to uninstall half (all?) of leap 15.3 installation?
by -pj 09 Jun '21

09 Jun '21

On 6/8/21 11:14 AM, cagsm wrote: > On Tue, Jun 8, 2021 at 5:39 PM Marcus Meissner <meissner(a)suse.de> wrote: >> Update ... this is still work in progress, I hope I will get through most of the issues >> this week. > thanks for keeping us informed here. Today some auto update of the > zypp/libzypp stack came along. >> libzypp-17.26.0-9.1.x86_64.rpm installed ok >> zypper-1.14.45-10.1.x86_64.rpm installed ok > > Right now the zypper patch has some different conflicts, but fewer: > === > zypper patch > Loading repository data... > Reading installed packages... > Patch 'SUSE-2021-1847-1' is optional. Use 'zypper in > patch:SUSE-2021-1847' to install it, or '--with-optional' to include > all optional patches. > Resolving package dependencies... > 12 Problems: > Problem: the to be installed patch:SUSE-2020-3304-1.noarch conflicts > with 'libi2c0.x86_64 < 4.0-4.3.2' provided by the installed > libi2c0-4.0-bp153.2.13.x86_64 > Problem: the to be installed patch:SUSE-2020-3792-1.noarch conflicts > with 'gzip.x86_64 < 1.10-4.3.1' provided by the installed > gzip-1.10-3.11.1.x86_64 > Problem: the to be installed patch:SUSE-2021-76-1.noarch conflicts > with 'SUSEConnect.x86_64 < 0.3.29-3.34.1' provided by the installed > SUSEConnect-0.3.29-3.6.1.x86_64 > Problem: the to be installed patch:SUSE-2021-510-1.noarch conflicts > with 'ucode-intel.x86_64 < 20210216-3.64.1' provided by the installed > ucode-intel-20210216-2.19.1.x86_64 > Problem: the to be installed patch:SUSE-2021-931-1.noarch conflicts > with 'libnghttp2-14-32bit.x86_64 < 1.40.0-3.11.1' provided by the > installed libnghttp2-14-32bit-1.40.0-3.5.1.x86_64 > Problem: the to be installed patch:SUSE-2021-1235-1.noarch conflicts > with 'numactl.x86_64 < 2.0.14-4.3.1' provided by the installed > numactl-2.0.14-1.1.x86_64 > Problem: the to be installed patch:SUSE-2021-1499-1.noarch conflicts > with 'webkit2gtk-4_0-injected-bundles.x86_64 < 2.32.0-3.74.1' provided > by the installed webkit2gtk-4_0-injected-bundles-2.32.0-3.15.1.x86_64 > Problem: the installed libx265-169-3.0-lp150.1.6.x86_64 requires > 'libnuma.so.1()(64bit)', but this requirement cannot be provided > Problem: the to be installed patch:SUSE-2020-3129-1.noarch conflicts > with 'sysconfig-netconfig.x86_64 < 0.85.6-3.6.1' provided by the > installed sysconfig-netconfig-0.85.6-3.3.1.x86_64 > Problem: the to be installed patch:SUSE-2021-1200-1.noarch conflicts > with 'libreoffice-writer-extensions.x86_64 < 7.1.2.2-13.15.1' provided > by the installed libreoffice-writer-extensions-7.1.2.2-2.3.x86_64 > Problem: the to be installed patch:SUSE-2021-1569-1.noarch conflicts > with 'libreoffice-writer.x86_64 < 7.1.3.2-13.18.3' provided by the > installed libreoffice-writer-7.1.2.2-2.3.x86_64 > Problem: the installed zypper-search-packages-plugin-0.7-5.35.noarch > requires 'rubygem(ruby:2.5.0:suse-connect) >= 0.3.9', but this > requirement cannot be provided > > Problem: the to be installed patch:SUSE-2020-3304-1.noarch conflicts > with 'libi2c0.x86_64 < 4.0-4.3.2' provided by the installed > libi2c0-4.0-bp153.2.13.x86_64 > Solution 1: Following actions will be done: > deinstallation of libi2c0-4.0-bp153.2.13.x86_64 > deinstallation of i2c-tools-4.0-bp153.2.13.x86_64 > Solution 2: do not install patch:SUSE-2020-3304-1.noarch > > Choose from above solutions by number or skip, retry or cancel > [1/2/s/r/c/d/?] (c): > === > > should we still wait with zypper patch and zypper in general? > ty. Eventually will a "being/entity" who navigates a machine. Sometimes updating - it's funny with "zypper patch" and then ask about "zypper in general". See you around bigtimers. :|

2 1

xsane--setup
by Douglas McGarrett 09 Jun '21

09 Jun '21

Hope someone out there is familiar with xsane, a scanner driver that works on Linux and on OpenSUSE. I want to use this because it allows print pixel density, save in various sizes and modes, etc. Installed it using Yast zypper. (I had it working once on Tumbleweed--don't remember what hoops I had to go thru, but it was simpler than now.) Running Leap 15.3 (Carlos take note!) Xsane website shows that it is completely compatible with Epson WP4530 all-mode-printer-scanner-fax. (I have had xsane running on Linux since PCLOS, 9 or more years ago, with the same scanner hardware.) Changed address in /etc/sane.d/epson2.conf to reflect the fixed IP address of the /printer-scanner. Computer says Points to usr/share/applications/xsane.desktop --I don't remember the "desktop" addition to the filename Also, under permissions, says file is a link and does not have permissions. Thanx for any assistance--doug

3 5

zypper patch about to uninstall half (all?) of leap 15.3 installation?
by cagsm 07 Jun '21

07 Jun '21

Is this why the wait until this weekend (is over?) to not use zypper patch according to 15.3 releasenotes? === sudo zypper lp Loading repository data... Reading installed packages... Repository | Name | Category | Severity | Interactive | Status | Since | Summary -------------------------------------------------------------+----------------+-------------+-----------+-------------+--------+-------+---------------------------- Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2021-1526 | recommended | important | --- | needed | - | Recommended update for bash === sudo zypper patch Loading repository data... Reading installed packages... Resolving package dependencies... Problem: patch:SUSE-2021-1526-1.noarch conflicts with readline-doc < 7.0-19.3.1 provided by readline-doc-7.0-17.83.noarch Solution 1: Following actions will be done: deinstallation of readline-doc-7.0-17.83.noarch deinstallation of readline-devel-7.0-17.83.x86_64 deinstallation of libreadline7-7.0-17.83.x86_64 deinstallation of bash-lang-4.4-17.83.noarch deinstallation of bash-doc-4.4-17.83.noarch deinstallation of kernel-default-optional-5.3.18-56.2.x86_64 deinstallation of kernel-default-extra-5.3.18-56.2.x86_64 deinstallation of kernel-default-5.3.18-56.2.x86_64 deinstallation of bash-4.4-17.83.x86_64 .............. tons more ty

3 3

Preventing loading of nvidia kernel module(s)
by J Leslie Turriff 04 Jun '21

04 Jun '21

I'm trying to set up my nvidia graphics card for dedication to a virtual machine, as described in "VGA PCI Passthrough guide on openSUSE Leap 42.2" https://forums.opensuse.org/showthread.php/522015-VGA-PCI-Passthrough-guide… and though I've followed all of the steps, when I get to step 6 (Reboot and check that your GPU was isolated) I see | ● lspci -k|grep -i nvidia | 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2060] (rev a1) | Kernel driver in use: nvidia | Kernel modules: nouveau, nvidia_drm, nvidia | @14:46:53,root@pinto rc=0 instead of "Kernel driver in use: vfio-pci". When I use lsmod to scan for "nvidia" or "nouveau" I get | ● modprobe -c|grep -e nvidia -e nouveau|grep -v alias | blacklist nvidiafb | blacklist nouveau | install nvidia PATH=$PATH:/bin:/usr/bin; if /sbin/modprobe --ignore-install nvidia; then if ... fi; fi | options nvidia NVreg_DynamicPowerManagement=0x01 | options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=482 NVreg_DeviceFileMode=0660 | @14:51:12,root@pinto rc=0 Looking at the zypper database, I see that I must have installed the nvidia proprietary driver some time in the past. | ● zypper se -i nvidia | Loading repository data... | Reading installed packages... | | S | Name | Summary | Type | --+---------------------------+-----------------------------------------------------------------------+-------- | i | nvidia-computeG05 | NVIDIA driver for computing with GPGPU | package | i | nvidia-gfxG05-kmp-default | NVIDIA graphics driver kernel module for GeForce 600 series and newer | package | i | nvidia-glG05 | NVIDIA OpenGL libraries for OpenGL acceleration | package | i | x11-video-nvidiaG05 | NVIDIA graphics driver for GeForce 600 series and newer | package | @14:54:32,root@pinto rc=0 Will removing these packages be sufficient to isolate the graphics card, or will further steps be necessary? Leslie -- openSUSE Leap 15.2 x86_64

2 1

Leap 15.3 and new update repositories
by Till Dörges 03 Jun '21

03 Jun '21

Hello all, I just set up a 15.3 test machine from scratch. Yesterday installing updates via 'zypper dup' gave me a new repo key to accept and new repos (see below). That raised two questions: o How can I verify the newly introduced key? In terms of crypto usability it doesn't seem like an ideal approach to introduce new trust anchors (i.e. new repo keys) w/o clearly documenting how to verify that it is actually legitimate. o Do I need the new update repos (repo-backports-update, repo-sle-update)? And if so, what's the difference to the previous update repos? Before the update there were only repo-update and repo-update-non-oss. leap153:~ # zypper up Retrieving repository 'Update repository of openSUSE Backports' metadata -----------------------------------------[\] New repository or package signing key received: Repository: Update repository of openSUSE Backports Key Name: openSUSE:Backports OBS Project <openSUSE:Backports@build.opensuse.org> Key Fingerprint: 637B32FF 3D83F07A 7AE1C40A 9C214D40 65176565 Key Created: Wed Oct 2 15:17:53 2019 Key Expires: Fri Dec 10 14:17:53 2021 Rpm Name: gpg-pubkey-65176565-5d94a381 user@leap153:~> zypper lr # | Alias | Name | Enabled | GPG Check | Refresh ---+-----------------------------+---------------------------------------------------------------------------------------------+-----------+-----------------+--------------- [...] 3 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | Nein | ---- | ---- 4 | repo-backports-update | Update repository of openSUSE Backports | Nein | ---- | ---- 5 | repo-debug | Debug Repository | Nein | ---- | ---- 6 | repo-debug-non-oss | Debug Repository (Non-OSS) | Nein | ---- | ---- 7 | repo-debug-update | Update Repository (Debug) | Nein | ---- | ---- 8 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | Nein | ---- | ---- 9 | repo-non-oss | Non-OSS Repository | Ja | (r ) Ja | Ja 10 | repo-oss | Haupt-Repository | Ja | (r ) Ja | Ja 11 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Nein | ---- | ---- 12 | repo-source | Source Repository | Nein | ---- | ---- 13 | repo-source-non-oss | Source Repository (Non-OSS) | Nein | ---- | ---- 14 | repo-update | Hauptaktualisierungs-Repository | Ja | (r ) Ja | Ja 15 | repo-update-non-oss | Aktualisierungs-Repository (Nicht-Open-Source-Software) | Ja | (r ) Ja | Ja Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 Besuchen Sie uns gerne auf der digitalen Plattform it-sa 365: https://www.itsa365.de/de-de/companies/p/presense-technologies-gmbh

2 2