August 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1096241] New: [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL
by bugzilla_noreply＠novell.com 19 Apr '21

19 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1096241 Bug ID: 1096241 Summary: [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: slindomansilla(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 772682 --> http://bugzilla.opensuse.org/attachment.cgi?id=772682&action=edit shutdown-log-timed-out.txt Similar issue was found a long time ago on ArchLinux and Redhat: - https://bugs.archlinux.org/task/52249 - https://bugzilla.redhat.com/show_bug.cgi?id=1152185 My questions here are: - Why do we need this process running on liveCD? - If we don't need it, can we remove it from the liveCD? - If not, how can we avoid that users get that problem? System hung when shutting down (notice 2154.900545 -> 2244.901945): [ 2154.897657] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 2154.900537] systemd-journald[6847]: Received SIGTERM from PID 1 (systemd-shutdow). [ 2154.900545] systemd-journald[6847]: systemd-journald stopped as pid 6847 [ 2244.901945] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 2244.907601] systemd-shutdown[1]: Sending SIGKILL to PID 731 (lvmetad). System not hung when shutting down (notice 2012.262209 -> 2012.314146): [ 2012.259513] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 2012.262200] systemd-journald[6792]: Received SIGTERM from PID 1 (systemd-shutdow). [ 2012.262209] systemd-journald[6792]: systemd-journald stopped as pid 6792 [ 2012.314146] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 2012.317239] systemd-shutdown[1]: Unmounting file systems. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 927268] New: clang link fails with undefined reference to `__stack_chk_guard'
by bugzilla_noreply＠novell.com 18 Apr '21

18 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=927268 Bug ID: 927268 Summary: clang link fails with undefined reference to `__stack_chk_guard' Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: PowerPC-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dap(a)open.by QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 631137 --> http://bugzilla.opensuse.org/attachment.cgi?id=631137&action=edit Full build log. Upstream report: https://llvm.org/bugs/show_bug.cgi?id=22248 My build log error: [ 35s] CMakeFiles/huffar.dir/compress.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] CMakeFiles/huffar.dir/extract.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] clang-3.5: error: linker command failed with exit code 1 (use -v to see invocation) [ 35s] CMakeFiles/huffar.dir/build.make:163: recipe for target 'huffar' failed [ 35s] make[2]: *** [huffar] Error 1 Check attachment for full log. #opensuse-ppc(a)irc.freenode.net: k0da: dark_ss, it seems you've hit an LLVM bug. It adds extra symbol. k0da: dark_ss, you can open an opensuse bug though for that issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1095700] New: setterm reports "cannot (un)set powersave mode: Inappropriate ioctl for device"
by bugzilla_noreply＠novell.com 16 Apr '21

16 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1095700 Bug ID: 1095700 Summary: setterm reports "cannot (un)set powersave mode: Inappropriate ioctl for device" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to re-establish screen blanking and power saving for virtual consoles on machines without X, I am trying to use "setterm -powersave on". This works on some machines, but not on others. I have added the following drop-in: /etc/systemd/system/getty\@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=-/usr/bin/setterm -powersave on >/dev/%I ExecStartPost=/usr/bin/setterm -blank 2 -powerdown 5 >/dev/%I I have split the setterm into two, because the 'powersave on' keeps fasiling and reporting "cannot (un)set powersave mode: Inappropriate ioctl for device". If I run it when logged into a console, it does not complain, but it also doesn't work. On older openSUSE, e.g. 12.3, it works, but I'm wondering if it might be a graphics driver issue? Maybe also refer to bug#1094452 which prompted me to look for a solution. -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1059012] New: Since upgrade to GNOME 3.26, gnome-shell crashes and reloads upon unlocking screen
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1059012 Bug ID: 1059012 Summary: Since upgrade to GNOME 3.26, gnome-shell crashes and reloads upon unlocking screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time when unlocking a locked screen, gnome-shell crashes and spits the following journal log entries: SSep 17 16:50:16 gnome-shell[8734]: Allocating size to ShellEmbeddedWindow 0x5628e771a970 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: Allocating size to ShellEmbeddedWindow 0x5628e771ac30 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 17 16:50:20 kernel: gnome-shell[8734]: segfault at 600287 ip 00007f2eb28d07f6 sp 00007ffd1db9dd50 error 4 in libgobject-2.0.so.0.5400.0[7f2eb289a000+53000] Sep 17 16:50:20 systemd[1]: Started Process Core Dump (PID 9154/UID 0). Sep 17 16:50:20 systemd-coredump[9155]: Resource limits disable core dumping for process 8734 (gnome-shell). Sep 17 16:50:20 systemd-coredump[9155]: Process 8734 (gnome-shell) of user 1000 dumped core. Sep 17 16:50:20 polkitd[868]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.276, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus Sep 17 16:50:20 gnome-session-binary[1661]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 17 16:50:20 gnome-session[1661]: gnome-session-binary[1661]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1009637] New: games/ufoai: Game crashes with "Error: Received signal 11."
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1009637 Bug ID: 1009637 Summary: games/ufoai: Game crashes with "Error: Received signal 11." Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dimstar(a)opensuse.org Reporter: bberberov+suse(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- UFO:AI consistently crashes now. This started occurring a couple of months ago, but I don't know which is the last working version. Steps to reproduce: - Start UFO:AI - Select "Single-Player" - Select "Skirmish" - Choose a map and "Start Game", I tested with the africa_small and a few others. The game loads, and the screen announcing the map and "Victory Conditions" shows up. You can move the map in the background and it renders fine with no errors or crashes with multiple graphics configurations. One the Start button is pressed it crashes after a couple of seconds. This is output from the console========== Starting the game... bberberov has joined team 1 Used inventory slots: 0 libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile Not enough spawn points for team 1 (actorsize: 1) Not enough spawn points for team 1 (actorsize: 1) Not enough spawn points for team 1 (actorsize: 1) Not enough spawn points for team 1 (actorsize: 1) Used inventory slots client bberberov spawn: 0 (player 0) It's team 1's turn! bberberov has taken control over team 1. Error: Received signal 11. ============================================= Don't know how to debug this, but I'd like to help, and finish my game in progress. :-) -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1050953] New: systemsetting5 -> Account Details does not give the option suggested in the title
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1050953 Bug ID: 1050953 Summary: systemsetting5 -> Account Details does not give the option suggested in the title Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 734130 --> http://bugzilla.opensuse.org/attachment.cgi?id=734130&action=edit screenshot of application Starting systemsetting5 and choosing Account Details -> User Manager shows the title: Add, remove or edit system users. However the only option it shows is New User. Editing a current user is impossible/not shown. See attached picture. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1074139] New: Using YaST to configure hardware sound looses information
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1074139 Bug ID: 1074139 Summary: Using YaST to configure hardware sound looses information Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Using YaST->hardware->Sound I configure one of the two sound devices: RV770 HDMI Audio [Radeon HD 4850/4870] First I delete the configuration, then I Edit the configuration and use the default Fast automatic configuration. I use Other and Volume to set/check the volume settings, which is quite a busy window with sliders. OK to exit. Start the Sound module in YaST again. Select the above device. In Other select Volume, which does not show the busy window anymore. Only at the top Master volume and a Test button. I assume this is a bug, not showing the sliders to set values. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1068469] New: package spamassassin contains obsolete file README.SuSE
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1068469 Bug ID: 1068469 Summary: package spamassassin contains obsolete file README.SuSE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, Following a conversation in <https://lists.opensuse.org/opensuse-factory/2017-11/msg00346.html> about «Bulk renaming of "README.SuSE"», it was suggested to search for README.SuSE files in the distribution, find if the contents are valid or obsolete, and then suggest action to the package maintainer in a corresponding bugzilla. The package spamassassin-3.4.1-54.2.x86_64.rpmcontains an obsolete README.SuSE, as it applies to a Sys V init system, so in my opinion it should be simply removed. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1004453] New: [mga] no Xorg with Matrox gfxcard when valid vga= mode included on kernel cmdline to produce desirable vttys
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 Bug ID: 1004453 Summary: [mga] no Xorg with Matrox gfxcard when valid vga= mode included on kernel cmdline to produce desirable vttys Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com CC: eich(a)suse.com Found By: --- Blocker: --- Created attachment 697145 --> http://bugzilla.opensuse.org/attachment.cgi?id=697145&action=edit Xorg.0.log from i586 TW host a-865 Mailing list thread starter: https://lists.opensuse.org/opensuse/2016-08/msg00322.html (same with kernels 4.7.x as with kernel 4.6.4) : # Xorg.0.log excerpts X.Org X Server 1.18.4 [ 57.691] Current Operating System: Linux a-865 4.7.4-1-default #1 SMP Thu Sep 15 09:03:59 UTC 2016 (6a5bbb1) i686 [ 57.691] Kernel command line: root=LABEL=os133SS25 ipv6.disable=1 net.ifnames=0 noresume splash=0 vga=791 video=1024x768@60 3 [ 58.342] (EE) open /dev/dri/card0: No such file or directory [ 58.382] (EE) MGA(0): Unable to map Framebuffer F0000000 2000000. Invalid argument (22) [ 58.382] (EE) MGA(0): Unable to detect video RAM. [ 58.382] (EE) Screen(s) found, but none have a usable configuration. [ 58.383] (EE) [ 58.383] (EE) no screens found(EE)... I didn't update this installation for many months, which explains large gap between installed kernels. Xorg and vttys work as expected with kernel-pae 4.2.3 and vga=791 on cmdline, but vga= needs to be omitted with the newer kernels for Xorg to start. Omitting vga= from cmdline results in far too few columns and rows on the vttys. I looked on bugs.freedesktop.org but found nothing like this. I tried a fresh zypper up, but kernel-default 4.7.6 with vga=788 proved no better, as did kernel-vanilla. Also didn't help adding to xorg.conf device section either VideoRam 16384 and/or Option "OldDmaInit" "On". # zypper se -si | egrep 'x11-serv|mga|kernel' il | kernel-default | package | 4.7.4-1.1 | i586 | (System Packages) il | kernel-default | package | 4.6.4-2.2 | i586 | (System Packages) il | kernel-default | package | 4.7.6-1.1 | i586 | OSS i | kernel-firmware | package | 20160913-1.1 | noarch | OSS il | kernel-pae | package | 4.2.3-1.4 | i686 | (System Packages) i | kernel-vanilla | package | 4.7.6-1.1 | i686 | OSS i | nfs-kernel-server | package | 1.3.4-2.2 | i586 | OSS i | xf86-video-mga | package | 1.6.4-2.2 | i586 | OSS i | xorg-x11-server | package | 7.6_1.18.4-1.2 | i586 | OSS # lspci | grep VGA 01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Millennium G550 (rev 01) -- You are receiving this mail because: You are on the CC list for the bug.

2 55

[Bug 911401] New: Wrong yast language when multiple languages specified in LANGUAGE env variable
by bugzilla_noreply＠novell.com 29 Mar '21

29 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=911401 Bug ID: 911401 Summary: Wrong yast language when multiple languages specified in LANGUAGE env variable Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: PVince81(a)yahoo.fr QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Steps to reproduce: 1. Make sure that neither LANG nor any LC_* variables are set 2. Run: export LANGUAGE="en_US:de:fr" (or set this language order in KDE's language settings) 3. Run: kdesu yast2 Expected result: Since English is the first language, Yast2 should be in English. Actual result: Yast2 is in German! More info: If you do: - export LANGUAGE="en_US" - kdesu yast2 Yast2 will be in English. It seems zypper is also affected partially. When LANGUAGE="en_US:de:fr" then zypper is in English, but the confirmation prompt is in German: Overall download size: 682.1 MiB. Already cached: 0 B After the operation, additional 753.3 MiB will be used. Fortfahren? [j/n/? zeigt alle Optionen] (j): Could be a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=843573 but that one didn't have any details. -- You are receiving this mail because: You are on the CC list for the bug.

2 2