July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201425] This device appears to be connected to a network but is unable to reach the internet.
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201425 https://bugzilla.suse.com/show_bug.cgi?id=1201425#c5 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Workspace (Plasma) |Network Assignee|opensuse-kde-bugs@opensuse. |screening-team-bugs(a)suse.de |org | Flags|needinfo?(cosmin.tanczel@gm | |ail.com) | --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Cosmin Tanczel from comment #4) > Well, when I first connect the message appears for about 15 seconds and then > it disappears. So it's not like it stays there forever. Ok, you didn't write that in the initial description. > But indeed, when I do a rcnetwork restart, the message does not appear > anymore Ok, so definitely an issue in NetworkManager. Reassigning. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201425] New: This device appears to be connected to a network but is unable to reach the internet.
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201425 Bug ID: 1201425 Summary: This device appears to be connected to a network but is unable to reach the internet. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Whenever I start my computer I get "This device appears to be connected to a network but is unable to reach the internet", even though the internet is working without issues. It happens on all Linux based computers I use. I also have a PiHole configured as the default DNS server, but I temporary disabled and the result is the same. nslookup looks good, ping works, curl works... (tests were performed also on conncheck.opensuse.org) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1201349] [Build 20220708] pipewire: no audio after logout/login
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201349 https://bugzilla.suse.com/show_bug.cgi?id=1201349#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Fabian Vogt from comment #2) > (In reply to Fabian Vogt from comment #1) > > So pipewire needs to check for accessibility of more device files. I'll file > > a report upstream. > > https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2534 My upstream MR got merged already \o/ https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1319 https://build.opensuse.org/request/show/988946 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201398] Plasma crash when nvidia-gl05 installed and connected to usb-c dock
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201398 https://bugzilla.suse.com/show_bug.cgi?id=1201398#c13 --- Comment #13 from Yakun Li <liyakun127(a)gmail.com> --- (In reply to Stefan Dirsch from comment #11) > Ok. You could try with installing suse-prime package and running > 'prime-select nvidia'. In case that's not configured yet anyway... Hi, thanks for the advice. The suse-prime was already installed, but I did not run the command you post. I just run the command, however the issue was not resolved, I attached the newest log. Maybe the command itself was not executed successfully, I got the following message in the terminal after running the command ``` nvidia catched Preparing first configuration bbswitch module not found. NVIDIA card will not be powered off logout to switch graphics ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201398] Plasma crash when nvidia-gl05 installed and connected to usb-c dock
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201398 https://bugzilla.suse.com/show_bug.cgi?id=1201398#c12 --- Comment #12 from Yakun Li <liyakun127(a)gmail.com> --- Created attachment 860146 --> https://bugzilla.suse.com/attachment.cgi?id=860146&action=edit nvidia prime select -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201460] New: LDAP not properly set up
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201460 Bug ID: 1201460 Summary: LDAP not properly set up Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aaronw(a)doofus.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the YaST2 user and group management when I attempt to configure LDAP for anonymous access I get the error: "A direct parent for DN 'ou=ldapconfig,dc=mydomain,dc=com' does not exist in the LDAP directory. The object with the selected DN cannot be created." replace mydomain with my actual domain name. I have reinstalled openldap and everything I can see that's related to ldap. Note that I am also unable to configure the ldap admin password. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201398] Plasma crash when nvidia-gl05 installed and connected to usb-c dock
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201398 https://bugzilla.suse.com/show_bug.cgi?id=1201398#c11 --- Comment #11 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. You could try with installing suse-prime package and running 'prime-select nvidia'. In case that's not configured yet anyway... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199193] Gajim fails to start, but issue relates to python cryptography version
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1199193 https://bugzilla.suse.com/show_bug.cgi?id=1199193#c3 --- Comment #3 from Stevan Lockhart <websl-osmat(a)vasten.co.uk> --- Thank you to everyone who worked on this. The resolution in https://bugzilla.suse.com/show_bug.cgi?id=1198851 also resolves the gajim issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201431] VUL-0: CVE-2022-29187: git,libgit2: incomplete fix for CVE-2022-24765
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201431 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |CVSSv3.1:SUSE:CVE-2022-2918 | |7:7.3:(AV:L/AC:L/PR:L/UI:R/ | |S:U/C:H/I:H/A:H) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201425] This device appears to be connected to a network but is unable to reach the internet.
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201425 https://bugzilla.suse.com/show_bug.cgi?id=1201425#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Cosmin Tanczel from comment #2) > No, for both questions: > > ping -6 conncheck.opensuse.org > ping: connect: Network is unreachable > user@host:~> sudo rcnetwork restart > [sudo] password for root: > user@host:~> ping -6 conncheck.opensuse.org > ping: connect: Network is unreachable Sorry, I meant whether the warning disappeared after rcnetwork restart. -- You are receiving this mail because: You are on the CC list for the bug.

1 0