May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1128630] New: libLLVMFuzzer.a missing (in llvm)
by bugzilla_noreply＠novell.com 17 Apr '21

17 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1128630 Bug ID: 1128630 Summary: libLLVMFuzzer.a missing (in llvm) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: harald.achitz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I miss libLLVMFuzzer.a on my system, tried to use it in a program but get a linke error > clang++ -std=c++14 -g -O3 -fsanitize=fuzzer entrypoint_libfuzzer.cpp bdecode.cpp -lboost_system -o libfuzzer_plain /usr/bin/ld: cannot find /usr/lib/libLLVMFuzzer.a: No such file or directory clang-5.0.1: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [makefile:23: libfuzzer_plain] Error 1 I think I found the reason in the change log of llvm packate ---- Tue May 9 08:29:31 UTC 2017 - idonmez(a)suse.com - Package libLLVMFuzzer ---- but than : ---- Tue Oct 10 12:14:31 UTC 2017 - msrb(a)suse.com - Drop llvm5-devel-static. llvm5-devel contains shared library with the same content. ---- Thu Jan 4 10:28:07 UTC 2018 - msrb(a)suse.com - Update to llvm 5.0.1 * This release contains bug-fixes for the LLVM 5.0.0 release. * This release is API and ABI compatible with 5.0.0. - llvm-do-not-install-static-libraries.patch * Updated. ---- so maybe not all static libraries should have been removed? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[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 1135395] New: GNOME:Factory/gnome-builder: Missing typelib: Jsonrpc
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1135395 Bug ID: 1135395 Summary: GNOME:Factory/gnome-builder: Missing typelib: Jsonrpc Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: hellcp(a)mailbox.org QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- When starting builder, it complains about lack of Jsonrpc namespace, installing Jsonrpc fixes it. Would be nice to install it by default ;) -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[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 1113636] New: gnome-shell failed to start, libmozjs-60.so error
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1113636 Bug ID: 1113636 Summary: gnome-shell failed to start, libmozjs-60.so error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: HP OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: suse(a)you-ra.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 Build Identifier: After "zypper up" and reboot can't login into gnome desktop. Reproducible: Always Steps to Reproduce: 1. Boot into login 2. submit username and password 3. again on login screen after screen flickering Actual Results: gnome-shell crashes every time I am trying to log in. gdb.txt === Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x00007f261556bdb6 in ?? () from /usr/lib64/libmozjs-60.so #0 0x00007f261556bdb6 in () at /usr/lib64/libmozjs-60.so #1 0x00007f261a5ae580 in gjs_string_from_utf8 () at /usr/lib64/libgjs.so.0 #2 0x00007f261a565ff2 in gjs_value_from_g_argument () at /usr/lib64/libgjs.so.0 #3 0x00007f261a577ec4 in () at /usr/lib64/libgjs.so.0 #4 0x00007f261a5784d0 in () at /usr/lib64/libgjs.so.0 #5 0x0000131c854478cb in () #6 0x00007ffce08b2d18 in () #7 0x00007ffce08b2c50 in () #8 0x0000000000000000 in () 'gjs_dumpstack' has unknown return type; cast the call to its declared return type A debugging session is active. gdb.txt === journal === ct 28 20:50:40 linux-mh3d org.gnome.Shell.desktop[3429]: Hit MOZ_CRASH(invalid UTF-8 string: ReportInvalidCharacte r) at /home/abuild/rpmbuild/BUILD/firefox-60.1.0/js/src/vm/CharacterEncoding.cpp:339 Oct 28 20:50:40 linux-mh3d kernel: show_signal_msg: 39 callbacks suppressed Oct 28 20:50:40 linux-mh3d kernel: gnome-shell[3429]: segfault at 0 ip 00007f261556bdb6 sp 00007ffce08b2430 error 6 in libmozjs-60.so[7f26154a9000+c52000] Oct 28 20:50:40 linux-mh3d kernel: Code: ff ff c7 04 25 00 00 00 00 4d 01 00 00 e8 72 ea f3 ff ba 53 01 00 00 48 8d 35 4e ed bf 00 48 8d 3d 2f 03 c0 00 e8 57 d6 ff ff <c7> 04 25 00 00 00 00 53 01 00 00 e8 4a ea f3 ff ba 44 01 00 00 48 journal === cat /etc/SUSE-brand openSUSE VERSION = 15.0 gnome extensions disabled (empty folder) -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1106997] New: Plasma startup hangs and sometimes ksmserver error
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1106997 Bug ID: 1106997 Summary: Plasma startup hangs and sometimes ksmserver error 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: --- After entering password to startup Plasma desktop the process hangs. After entering <Ctrl>+<Alt>+<Backspace>+<Backspace>, reentering password, sometimes I see a message about ksmserver not able to start. Most of the time Plasma starts OK after entering the password for the second time. Once I went to tty1, after entering the password for the first time, and killed the ksmserver process, which showed the same effect as entering <Ctrl>+<Alt>+<Backspace>+<Backspace>. I see this same problem both on my desktop as on my laptop, although it occurred earlier on my laptop. However I did not see the ksmserver error on my laptop. Both systems are kept current on the latest version of Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1116849] New: Failed to start Load Kernel Modules
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1116849 Bug ID: 1116849 Summary: Failed to start Load Kernel Modules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since quite some time, months, when booting my Tumbleweed system, always up-to-date, I see a red message shown, telling "Failed to start Load Kernel Modules", coming from the systemd unit systemd-modules-load.service. However "systemctl status systemd-modules-load.service" later does not show any error message. Further inspection shows that the module inspects a number of files with names of modules, among others /etc/modules-load.d/* which contain module names: sg and snd-hda-intel. I don't know anymore how I did see a hint on what went wrong, but what I recall is that it could not find a file or directory. My suggestion is therefor that at the moment this unit is executed the filesystem with one of these modules is not yet available. Apparently another attempt to run the unit succeeds, which explains why such an error message does not show in the journal. Maybe the unit should depend on finishing of mounting the root filesystem or maybe /usr -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[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