April 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1195393] New: KDE Plasma sound level starts with 74% after every reboot
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195393 Bug ID: 1195393 Summary: KDE Plasma sound level starts with 74% after every reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: 64bit OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: datenteiler(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36 Build Identifier: I want to start with a lower sound level, because 74%, the default level, is too loud. But when I change the sound level in KDE Plasma to e.g. 42% it's back on 74% after the next reboot. When I log out and log back in, the sound level stays at the value I set, but the volume level is back to 74% after reboot. I have configured my sound card in YaST but this didn't changed anything. Reproducible: Always Steps to Reproduce: 1. Set sound level to a different level then 74% in KDE Plasma (maybe other DE are also effected) 2. Restart openSUSE Leap 15.4 3. Sound level is on 74% again Actual Results: Sound level is on 74%, always. After every reboot. Expected Results: Sound level stays at the value I set. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Device-2: AMD Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] driver: snd_hda_intel Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo Device-4: RODE Microphones RODE NT-USB type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server-1: ALSA v: k5.14.21-150400.3-default running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.39 running: yes ps -e | grep pipewire 2513 ? 00:00:00 pipewire 2514 ? 00:00:00 pipewire-media- -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1198530] New: Mouse Pointer flicker and artifacts
by bugzilla_noreply＠suse.com 13 Jan '23

13 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198530 Bug ID: 1198530 Summary: Mouse Pointer flicker and artifacts Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: sjr.apd(a)shaw.ca QA Contact: qa-bugs(a)suse.de Found By: Customer Blocker: --- Using Leap 15.4 Beta: During initial boot to login screen the mouse pointer flickers and moving it over parts of interface leaves graphic artifacts behind. Once logged into X11 Gnome the same mouse pointer flicker/artifact issue persists. Also moving some windows around has square border artifacts--I assume where the translucent shadows would normally be. The work around is log back out and back in and the issue goes away. Another method is immediately setting machine to suspend, then waking it up. The lock screen login also fixes the mouse pointer. What would be the best way to resolve this for intial boot to avoid the secondary logout and login. p.s. (I added the Wayland pattern for Gnome to try via wayland instead of x11, but don't get the choice at the login screen for X11 or Wayland GNOME. It only shows GNOME and GNOME classic) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1173321] New: Move /etc/skel/* files to /usr/etc/skel ?
by bugzilla_noreply＠suse.com 13 Jan '23

13 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1173321 Bug ID: 1173321 Summary: Move /etc/skel/* files to /usr/etc/skel ? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm currently working on the config file switch /etc --> /usr/etc (find Details on https://en.opensuse.org/openSUSE:Packaging_UsrEtc) and now I'm wondering what should be done with files in /etc/skel/* Thorten Kukuk: Hard to change, as the admin should be able to change them... Me: Hm. Maybe move the distributed ones to /usr/etc/skel and adjust everything needed to priotarize the ones in /etc/skel, i.e. use any file in /etc/skel but also any file, which exists in /usr/etc/skel, but not in /etc/skel? -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1019024] New: Update zone for DNS server doesn't occurs in Yast
by bugzilla_noreply＠novell.com 12 Jan '23

12 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1019024 Bug ID: 1019024 Summary: Update zone for DNS server doesn't occurs in Yast Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I tried updating a zone in Yast2. Adding a A record for an IP alias address. When I save it the zone (pce23.net) is not updated in /var/lib/named/dyn I updated again today (10 Jan 2017) adding a new A record and after exit and reload the zone is not changed. The date of the zone file remains the original date -rw-rw-r-- 1 named named 332 Jan 8 09:18 pce23.net I saved the log with save_y2logs and attach it here (it is big > 5mb) Regards Philippe Condé -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1100765] New: gimp create from screenshot snap region is missing in french and error
by bugzilla_noreply＠novell.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1100765 Bug ID: 1100765 Summary: gimp create from screenshot snap region is missing in french and error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: conde.philippe(a)skynet.be QA Contact: ke(a)suse.com Found By: --- Blocker: --- Created attachment 776591 --> http://bugzilla.opensuse.org/attachment.cgi?id=776591&action=edit gimp in english with 3 options Hello, in gimp select create image ==> from screenshot in Enclish you have 3 options (see attachment gimp_englishok.png) - take a screenshot of a single window - take screenshot of entire screen - select a region to grab in french the third option is missing (see attachment gimp_frenchbad.png) if I select in french one of the two available options I receive an error (see attachment gimp_error.png Erreur d’exécution « Capture d’écran » : GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/Screenshot' -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1193742] New: go1.18 release tracking
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193742 Bug ID: 1193742 Summary: go1.18 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- go1.18 (expected February 2022) is a major release of Go. Minor releases of go1.18.x will be provided through February 2023. This issue tracks go1.18.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1198124] New: chromium: Opening and closing media controls triggers segmentation fault
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198124 Bug ID: 1198124 Summary: chromium: Opening and closing media controls triggers segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: victhor.foster(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 857852 --> http://bugzilla.opensuse.org/attachment.cgi?id=857852&action=edit gdb backtrace Chromium 100.0.4896.60-1.1 suffers from a bug that causes the entire browser to crash with either a segfault or a general protection fault, triggered by opening then closing the media controls. Steps to reproduce: 1. Open any site that plays back media (youtube, spotify, etc) 2. Click on the media control button on the toolbar 3. Click on the button again, to close the dialog Actual result: Chromium crashes with a segfault or a general protection fault. Expected result: Media control dialog closes. Build: Tumbleweed 20220403 x86_64 CPU: Intel Core i7-7200U GPU: Intel HD Graphics 620 No command line options or flags were used, other than any set by the distribution's /usr/bin/chromium script. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1182148] New: systemd-analyze verify is unhappy with /usr/lib/systemd/system/mcelog.service systemd unit
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1182148 Bug ID: 1182148 Summary: systemd-analyze verify is unhappy with /usr/lib/systemd/system/mcelog.service systemd unit Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: azhou(a)suse.com, dmueller(a)suse.com, fcrozat(a)suse.com, guillaume.gardet(a)arm.com, lubos.kocman(a)suse.com, meissner(a)suse.com, mlin(a)suse.com, nwr10cst-oslnx(a)yahoo.com, qzhao(a)suse.com, stasiek(a)michalski.cc, yfjiang(a)suse.com Found By: --- Blocker: --- When running systemd-analyze verify ~/.config/systemd/user/*.service I get a list of errors on unrelated systemd units: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1138135] New: gui version of yast's automatic update configuration fails to change anything
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1138135 Bug ID: 1138135 Summary: gui version of yast's automatic update configuration fails to change anything Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I enter the automatic update configuration from gui and enable it. I click on OK - it closes as if everything was fine. I enter the automatic update configuration again and I see it is disabled - so all my changes were disregarded So I switch to console yast. I enable auto update in the config - click ok and now i get prompted to trust pgp keys for certain repos. After having dont that and and reruning the console yast auto update config again I see that now the changes persisted. I now tried to lunch gui version and it also shows auto update as enabled. I tired to disable this feature in gui to check if gui yast can do it. It failed t apply changes again. COnclusion: FOr some reason gui yast auto update config fails to save that the feature is enabled or disabled. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1104571] New: 3g 4g modem connects but no traffic possible
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1104571 Bug ID: 1104571 Summary: 3g 4g modem connects but no traffic possible Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi I have a dual boot Opensuse Leap15/Ubuntu 18.04 system on HP G2 laptop with 4g modem. In ubuntu all works fine In opensuse I added the connection in KDE - all default options -my carrier was listed. The modem get's connected - receives default route, IP assignment, DNS but for some reason no data is being sent/received - not even a simple ping 8.8.8.8 works here are the params ip addr show 5: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 7a:c6:53:8c:bf:03 brd ff:ff:ff:ff:ff:ff inet 100.101.44.242/30 brd 100.101.44.243 scope global noprefixroute wwan0 valid_lft forever preferred_lft forever ip route show default via 100.101.44.241 dev wwan0 proto static metric 20700 100.101.44.240/30 dev wwan0 proto kernel scope link src 100.101.44.242 metric 700 and also the logs of netowork manager sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2045] device (cdc-wdm0): Activation: starting connection 'Play Online' (f77e62a8-66e0-4f34-b70e-f54a907a0630) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2046] audit: op="connection-activate" uuid="f77e62a8-66e0-4f34-b70e-f54a907a0630" name="Play Online" pid=3812 uid=1000 result="success" sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2047] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2048] manager: NetworkManager state is now CONNECTING sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect started... sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (4/8): Wait to get fully enabled sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (5/8): Register sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (6/8): Bearer sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (7/8): Connect sie 11 07:37:55 laprus ModemManager[1580]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2087] modem["cdc-wdm0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus kdeinit5[3768]: plasma-nm: Unhandled active connection state change: 1 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: Item "Play Online" : active connection state changed to 1 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: NetworkManager state changed to 4 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: Item "Play Online" : active connection changed to 1 sie 11 07:37:55 laprus ModemManager[1580]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (8/8): All done sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3919] modem["cdc-wdm0"]: modem state changed, 'connecting' --> 'connected' (reason: user-requested) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3936] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3939] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3942] modem-broadband[cdc-wdm0]: IPv4 static configuration: sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: address 100.101.44.242/30 sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: gateway 100.101.44.241 sie 11 07:37:55 laprus avahi-daemon[1565]: Joining mDNS multicast group on interface wwan0.IPv4 with address 100.101.44.242. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: DNS 185.89.185.2 sie 11 07:37:55 laprus avahi-daemon[1565]: New relevant interface wwan0.IPv4 for mDNS. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: DNS 89.108.202.21 sie 11 07:37:55 laprus avahi-daemon[1565]: Registering new address record for 100.101.44.242 on wwan0.IPv4. sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus avahi-daemon[1565]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::16b5:7d4d:10ab:f6ae. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3956] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus avahi-daemon[1565]: New relevant interface wwan0.IPv6 for mDNS. sie 11 07:37:55 laprus avahi-daemon[1565]: Registering new address record for fe80::16b5:7d4d:10ab:f6ae on wwan0.*. sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3970] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3971] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3972] manager: NetworkManager state is now CONNECTED_LOCAL sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.4262] manager: NetworkManager state is now CONNECTED_SITE sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.4263] policy: set 'Play Online' (wwan0) as default for IPv4 routing and DNS sie 11 07:37:55 laprus nscd[1604]: 1604 monitored file `/etc/resolv.conf` was written to sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus NetworkManager[1843]: nisdomainname: you must be root to change the domain name sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.5272] device (cdc-wdm0): Activation: successful, device activated. -- You are receiving this mail because: You are on the CC list for the bug.

2 5