February 2023 - openSUSE Support - openSUSE Mailing Lists

Thunar 4.18.3 lp154 - Regular Expression not available in Bulk Renamer dialog
by bjurg orsku 16 Feb '23

16 Feb '23

Thunar 4.18.3 (from X11:xfce repository) installed on leap 15.4 with zypper and the --no-recommends option leaves the Thunar Bulk Renamer dialog window with the Regular Expression option grayed out – i.e.: unavailable.

3 3

wickedd-dhcp4 debugging
by Bjoern Voigt 16 Feb '23

16 Feb '23

My Wicked based network (Tumbleweed 20230213) does not accept new IPv4 addresses from a DHCP server (a cable router) unless I remove the status files in /var/lib/wicked/*. The journalctl log does not show many details in the situation, that wickedd-dhcp4 still uses an outdated IPv4 address (from another LAN), but can not accept the new IPv4 address: Feb 15 11:36:58 mybox systemd[1]: Starting wicked DHCPv4 supplicant service... Feb 15 11:36:58 mybox systemd[1]: Started wicked DHCPv4 supplicant service. Feb 15 11:37:07 mybox wickedd-dhcp4[1736]: br0: Request to acquire DHCPv4 lease with UUID ...-000007000000 Feb 15 11:37:22 mybox wickedd-dhcp4[1736]: br0: defer timeout 15 reached in state REBOOT Feb 15 11:37:23 mybox wickedd-dhcp4[1736]: br0: Committed DHCPv4 lease with address 192.168.12.2 (lease time 32720, renew in 11120 sec, rebind in 27320 sec) Feb 15 11:40:44 mybox systemd[1]: Stopping wicked DHCPv4 supplicant service... Feb 15 11:40:44 mybox systemd[1]: wickedd-dhcp4.service: Deactivated successfully. Feb 15 11:40:44 mybox systemd[1]: Stopped wicked DHCPv4 supplicant service. After deleting /var/lib/wicked/* and restarting wickedd-dhcp4 it works (100.66.111.3 is accepted). Feb 15 11:40:44 mybox systemd[1]: Starting wicked DHCPv4 supplicant service... Feb 15 11:40:44 mybox systemd[1]: Started wicked DHCPv4 supplicant service. Feb 15 11:42:21 mybox wickedd-dhcp4[5621]: br0: Request to acquire DHCPv4 lease with UUID ...-000010000000 Feb 15 11:42:23 mybox wickedd-dhcp4[5621]: br0: Committed DHCPv4 lease with address 100.66.111.3 (lease time 604800, renew in 302400 sec, rebind in 529200 sec) Feb 15 11:56:47 mybox wickedd-dhcp4[5621]: br0: Request to acquire DHCPv4 lease with UUID ...-000010000000 Feb 15 11:57:02 mybox wickedd-dhcp4[5621]: br0: defer timeout 15 reached in state REBOOT Feb 15 11:57:02 mybox wickedd-dhcp4[5621]: br0: Committed DHCPv4 lease with address 100.66.111.3 (lease time 603921, renew in 301521 sec, rebind in 528321 sec) Feb 15 11:57:39 mybox wickedd-dhcp4[5621]: br0: Request to drop DHCPv4 lease with UUID ...-000010000000: starting... Feb 15 11:57:45 mybox systemd[1]: Stopping wicked DHCPv4 supplicant service... Feb 15 11:57:45 mybox systemd[1]: wickedd-dhcp4.service: Deactivated successfully. Feb 15 11:57:45 mybox systemd[1]: Stopped wicked DHCPv4 supplicant service. But how I can configure wickedd-dhcp4 so, that it logs more details? Björn

2 1

nvidia G04 driver builds fail for glibc >2.36-4
by Patrick Shanahan 15 Feb '23

15 Feb '23

current builds of nvidia graphic drivers for G04 series are not usable with glibc >2.36-4 on tumbleweed. current glibc is 2.37.1.1 I have reverted to glibc 2.36-4.4 to have graphical display nvidia-gfxG04-kmp-default-390.157_k6.1.10_9-68.41.x86_64 nvidia-computeG04-390.157-68.5.x86_64 x11-video-nvidiaG04-32bit-390.157-68.5.x86_64 x11-video-nvidiaG04-390.157-68.5.x86_64 nvidia-glG04-32bit-390.157-68.5.x86_64 nvidia-glG04-390.157-68.5.x86_64 nvidia-computeG04-32bit-390.157-68.5.x86_64 if needed, I can test. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

1 1

Bluetooth - br-connection-profile-unavailable
by Axel Braun 11 Feb '23

11 Feb '23

Hi, (I never worked with Bluetooth on the Laptop, so sorry if this question is really stupid...) I try to connect a TomTom Wireless GPS MkII to my TW Laptop and get the above error message - Anyone an idea what profile is requested? (Smartphone/Android worked immediately, and DDG did not offer helping results....) Thanks Axel

3 4

nvidia G04 display broken
by Patrick Shanahan 11 Feb '23

11 Feb '23

kernel modules no longer build nvidia G04 Graphics: Device-1: NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: N/A alternate: nouveau non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm built: 2010-16 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 bus-ID: 03:00.0 chip-ID: 10de:0dc4 class-ID: 0300 kernel 6.1.10 gcc-12-2.4.x86_64 NVIDIA-Linux-x86_64-390.151.run NVIDIA-Linux-x86_64-390.154.run NVIDIA-Linux-x86_64-390.157.run fail also nvidia-computeG04-32bit-390.157-68.5.x86_64.rpm nvidia-computeG04-390.157-68.5.x86_64.rpm nvidia-gfxG04-kmp-default-390.157_k6.1.10_9-68.40.x86_64.rpm nvidia-glG04-32bit-390.157-68.5.x86_64.rpm nvidia-glG04-390.157-68.5.x86_64.rpm x11-video-nvidiaG04-32bit-390.157-68.5.x86_64.rpm x11-video-nvidiaG04-390.157-68.5.x86_64.rpm tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

4 10

Re: '-D' option of diff 3.9 - #ifdef directives missing
by Robert Webb 10 Feb '23

10 Feb '23

On Fri, 10 Feb 2023 14:10:35 +0100, Axel Braun <docb(a)opensuse.org> wrote: > Am Freitag, 10. Februar 2023, 00:58:01 CET schrieb Robert Webb: >> Hi, >> There has been no response to my bug report at: >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61193 >> >> Can anyone else at least confirm this problem (on Tumbleweed)? >> The output from 'diff -D' (v3.9) is missing the '#ifdef' directives. >> Version 3.8 of diff works ok, so it may be fine on Leap. >> >> The following creates a file 'c', and diffs it with a couple lines >> deleted, using three different options. >> >> diff -v |grep diff >> seq 5 > c >> for OPT in '' '-D ZZZ' '-u' ;do >> printf '\n=== diff %s\n' "$OPT" >> sed 2,3d c |diff $OPT c - >> done > > Is this what you are looking for? > > docb@X1E:/tmp> diff -v |grep diff > *diff* (GNU *diff*utils) 3.9 > docb@X1E:/tmp> seq 5 > c > docb@X1E:/tmp> for OPT in '' '-D ZZZ' '-u' ;do >> printf '\n=== diff %s\n' "$OPT" >> sed 2,3d c |diff $OPT c - >> done > > === diff > 2,3d1 > < 2 > < 3 > > === diff -D ZZZ > 1 > 2 > 3 > 4 > 5 Thanks, Axel. Yes, it is the same as my results - no #ifdef directives. The correct output for the -D option, as from version 3.8, is: === diff -D ZZZ 1 #ifndef ZZZ 2 3 #endif /* ! ZZZ */ 4 5 > === diff -u > --- c 2023-02-10 14:08:17.055916079 +0100 > +++ - 2023-02-10 14:08:18.933093494 +0100 > @@ -1,5 +1,3 @@ > 1 > -2 > -3 > 4 > 5 I am going to add this pass/fail test to the bug report: #!/bin/bash diff -D AAAA /dev/null <(echo A) \ |cmp - <(printf '%s\n' '#ifdef AAAA' A '#endif /* AAAA */') -- Robert Webb

1 0

'-D' option of diff 3.9 - #ifdef directives missing
by Robert Webb 09 Feb '23

09 Feb '23

Hi, There has been no response to my bug report at: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61193 Can anyone else at least confirm this problem (on Tumbleweed)? The output from 'diff -D' (v3.9) is missing the '#ifdef' directives. Version 3.8 of diff works ok, so it may be fine on Leap. The following creates a file 'c', and diffs it with a couple lines deleted, using three different options. diff -v |grep diff seq 5 > c for OPT in '' '-D ZZZ' '-u' ;do printf '\n=== diff %s\n' "$OPT" sed 2,3d c |diff $OPT c - done -- Robert Webb

1 0

Problems with Gnome in Leap 15.4
by Patrick Headley 09 Feb '23

09 Feb '23

These issues only seem to be present on new installations of Leap 15.4. Upgrades from 15.3 don't seem to be affected. Using Gnome 41.8. The greeter doesn't show domain logins in the list. Under certain circumstances the names will appear, or at least the user name I use appears. Locking the screen doesn't allow the screen to turn off. Power settings are set to turn off the display after 15 minutes. When logging in after the screen has been locked, any open applications on monitor 2 move to monitor 1. Hope these issues can be resolved in Leap 15.4.

1 0

Testing 15.5 - MATE Desktop no longer there.
by Larry Len Rainey 09 Feb '23

09 Feb '23

1 0

Where to actually report a bug??
by Adam Majer 09 Feb '23

09 Feb '23

Hi all, So, welcome to a frustrating Wednesday morning. I came across a bug where there is an "Ajax error" going to http://download.opensuse.org/repositories/multimedia:/libs:/cisco-openh264/ with a popup, DataTables warning: table id=data - Ajax error. For more information about this error, please see http://datatables.net/tn/7 At this point I wanted to report a bug. Easy. There is even a Link at the bottom that says "Report issue". And that just goes to bugzilla. So now the hunt starts -- which category? The MirrorCache link said nothing about category. The only thing with "download" in the description, ends up with microfocus.com email..... Anyone know what category bugs for MirrorCache should be filed? And shouldn't this information be, at very least, part of the link? Thanks, Adam

4 4

2023

2022

2021

2020

2019

2018

openSUSE Support February 2023