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

[Bug 1124641] New: Using yast2 bootloader on Raspberry Pi 2 with Leap 15.0 gives error about EFI
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1124641 Bug ID: 1124641 Summary: Using yast2 bootloader on Raspberry Pi 2 with Leap 15.0 gives error about EFI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 796269 --> http://bugzilla.opensuse.org/attachment.cgi?id=796269&action=edit output of save_y2logs I installed yast2-bootloader on a Raspberry Pi 2 with Leap 15.0 and used it. Got an error message about something like EFI not available or present and to report a bug with output of save-y2logs attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1116014] New: Please convert SysV init scripts by fwnn into native systemd services
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.suse.com/show_bug.cgi?id=1116014 Bug ID: 1116014 Summary: Please convert SysV init scripts by fwnn into native systemd services 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1121301] New: Mails can not read in roundcubemail from server:Kolab:Extra
by bugzilla_noreply＠novell.com 09 Apr '21

09 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1121301 Bug ID: 1121301 Summary: Mails can not read in roundcubemail from server:Kolab:Extra Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In roundcubemail from server:Kolab there come serveral errors. 1.) Every time When call the Link, without login, it rise up following warnings in /var/log/roundcubemail/errors: [09-Jan-2019 17:20:01 UTC] PHP Warning: Declaration of rcube_kolab_contacts::validate(&$save_data) should be compatible with rcube_addressbook::validate(&$save_data, $autofix = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:20:01 UTC] PHP Warning: Declaration of rcube_kolab_contacts::delete_all() should be compatible with rcube_addressbook::delete_all($with_groups = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:20:01 UTC] PHP Warning: Declaration of rcube_kolab_contacts::list_groups($search = NULL) should be compatible with rcube_addressbook::list_groups($search = NULL, $mode = 0) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:20:01 UTC] PHP Warning: Declaration of rcube_kolab_contacts::rename_group($gid, $newname) should be compatible with rcube_addressbook::rename_group($group_id, $newname, &$newid) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 2.) After login this is in /var/log/roundcubemail/errors: [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::validate(&$save_data) should be compatible with rcube_addressbook::validate(&$save_data, $autofix = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::delete_all() should be compatible with rcube_addressbook::delete_all($with_groups = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::list_groups($search = NULL) should be compatible with rcube_addressbook::list_groups($search = NULL, $mode = 0) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::rename_group($gid, $newname) should be compatible with rcube_addressbook::rename_group($group_id, $newname, &$newid) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::validate(&$save_data) should be compatible with rcube_addressbook::validate(&$save_data, $autofix = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::delete_all() should be compatible with rcube_addressbook::delete_all($with_groups = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::list_groups($search = NULL) should be compatible with rcube_addressbook::list_groups($search = NULL, $mode = 0) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:20 UTC] PHP Warning: Declaration of rcube_kolab_contacts::rename_group($gid, $newname) should be compatible with rcube_addressbook::rename_group($group_id, $newname, &$newid) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::validate(&$save_data) should be compatible with rcube_addressbook::validate(&$save_data, $autofix = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::delete_all() should be compatible with rcube_addressbook::delete_all($with_groups = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::list_groups($search = NULL) should be compatible with rcube_addressbook::list_groups($search = NULL, $mode = 0) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::rename_group($gid, $newname) should be compatible with rcube_addressbook::rename_group($group_id, $newname, &$newid) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::validate(&$save_data) should be compatible with rcube_addressbook::validate(&$save_data, $autofix = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::delete_all() should be compatible with rcube_addressbook::delete_all($with_groups = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::list_groups($search = NULL) should be compatible with rcube_addressbook::list_groups($search = NULL, $mode = 0) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:25:22 UTC] PHP Warning: Declaration of rcube_kolab_contacts::rename_group($gid, $newname) should be compatible with rcube_addressbook::rename_group($group_id, $newname, &$newid) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 3.) When click on Subject to read mail, noting happens. Only the message is loading without end. And in /var/log/roundcubemail/errors is: [09-Jan-2019 17:27:21 UTC] PHP Warning: Declaration of rcube_kolab_contacts::validate(&$save_data) should be compatible with rcube_addressbook::validate(&$save_data, $autofix = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:27:21 UTC] PHP Warning: Declaration of rcube_kolab_contacts::delete_all() should be compatible with rcube_addressbook::delete_all($with_groups = false) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:27:21 UTC] PHP Warning: Declaration of rcube_kolab_contacts::list_groups($search = NULL) should be compatible with rcube_addressbook::list_groups($search = NULL, $mode = 0) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:27:21 UTC] PHP Warning: Declaration of rcube_kolab_contacts::rename_group($gid, $newname) should be compatible with rcube_addressbook::rename_group($group_id, $newname, &$newid) in /srv/www/roundcubemail/plugins/kolab_addressbook/lib/rcube_kolab_contacts.php on line 29 [09-Jan-2019 17:27:21 UTC] PHP Fatal error: Class vobject_location_property contains 3 abstract methods and must therefore be declared abstract or implement the remaining methods (Sabre\VObject\Property::getValueType, Sabre\VObject\Property::setRawMimeDirValue, Sabre\VObject\Property::getRawMimeDirValue) in /srv/www/roundcubemail/plugins/libcalendaring/libvcalendar.php on line 1364 So. Mail can never read. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1123566] New: kolab-freebusyd doesn't generate files
by bugzilla_noreply＠novell.com 09 Apr '21

09 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1123566 Bug ID: 1123566 Summary: kolab-freebusyd doesn't generate files Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kolab-freebusyd from package kolab-utils does not generate his files. It generates errors: $ # kolab-freebusyd -c /etc/kolab/kolab.conf -g foo(a)foobar.com (18:51:03) fbcoordinator.cpp(139): Starting generation for user: "foo(a)foobar.com" (18:51:03) kolabjob.cpp(47): =========================================================== (18:51:03) kolabjob.cpp(48): starting kolab job: "foo(a)foobar.com" on "localhost" : 993 (18:51:03) authenticationjob.cpp(34): logging in as "foo(a)foobar.com" using "cyrusAdminUsername" (18:51:04) authenticationjob.cpp(68): authentication successful (18:51:04) createkolabfolderjob.cpp(65): "Create failed, server replied: A000010 NO Mailbox already exists " Trying to fix the metadata (18:51:04) setupkolabfoldersjob.cpp(122): Created folder "" "Freebusy" (18:51:04) fbcoordinator.cpp(162): Error: "" (18:51:04) fbcoordinator.cpp(117): All done. Total time elapsed [s]: 0.147 (18:51:04) kolabjob.cpp(41): lost connenction So, no availability is seen by generation of a new appointment in roundcube or Korganizer. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1124862] New: gnutls and TLS 1.3
by bugzilla_noreply＠novell.com 09 Apr '21

09 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1124862 Bug ID: 1124862 Summary: gnutls and TLS 1.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- All versions of gnutls, but Tumbleweed, have to old versions of gnutls. All versions, but Tumbleweed, does not support TLS 1.3 Think it is for SLE also. First stable support was with 3.6.4. Current version is 3.6.6. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1116625] New: Systemd automount units fail after suspend/resume
by bugzilla_noreply＠novell.com 08 Apr '21

08 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1116625 Bug ID: 1116625 Summary: Systemd automount units fail after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Systemd's automount units often fail after a suspend/resume cycle. I believe it occurs for units that are not mounted at the time the system is suspended, but I'm not sure. I've only tried this with nfs mounts, so it may only apply to nfs autmounts. Here's a log from such a failed unit: Nov 19 16:22:39 homelap5.WalkerStreet.info systemd[1]: DWMedia-DWMedia7.automount: Got invalid poll event 16 on pipe (fd=71) Nov 19 16:22:39 homelap5.WalkerStreet.info systemd[1]: DWMedia-DWMedia7.automount: Unit entered failed state. Restarting the automount unit after the system resumes gets things working again, so I've put the following script into /etc/NetworkManager/dispatcher.d as a quick and dirty workaround: #!/usr/bin/perl # # FixAutomount - Query systemctl for failed automount units and restart them. # This is needed, as suspend/resume seems to make them fail. # It can be invoked from a NetworkManager dispatcher script. # if ($ARGV[1] eq "up") { open (FAILED, "systemctl list-units *.automount --failed |"); while (<FAILED>) { if (/\s+(\S+).automount\s+loaded\s/) { system ("systemctl restart $1.automount"); }; }; }; -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1134688] New: Bug with German Umlauts on desktop
by bugzilla_noreply＠novell.com 06 Apr '21

06 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 Bug ID: 1134688 Summary: Bug with German Umlauts on desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: office(a)hantsch.co.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I use openSUSE Leap 15.0 with KDE/Plasma5. The same problem exists also on openSuSE 42.x My system wide locale settings are: de_DE@euro (German, no UTF8). All files/folders (their names) are correctly encoded in iso-8859-1. Since Plasma5 I experience the following mis-behavior, while this smoothly worked on KDE4 (openSuSE 13.x): I am able to open Dolphin. Inside Dolphin I can navigate without any problem into folders having German Umlauts in their names. I also can click a file with German Umlauts in its name. I also can copy/paste and/or drag/drop such files/folders from Dolphin directly onto the desktop. Everything is fine here. I am also able to right-click such file/folder on the desktop to rename it (this also works as it should). When trying to click such file/folder on the desktop (to open it), I get an error: (translated German->English by me): "This command cannot be executed. The file or folder <.....> does not exist" Surprisingly the correct filename is showing up in <....>! As an example, a testing filename is: /home/rainer/Desktop/miniLÖT-Deckel.pdf (notice the "Ö" inside the file name. When renaming the file (right-click -> rename) to i.e. miniLOeT-Deckel.pdf, I am able to open the file afterwards. This happens with any kind of file/folder (also symlinks, etc..., even over NFS mounts). converting the entire system (and also all servers) is no option. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1114761] New: spamassassin spamd writing errors int logfile and not scanning some email
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1114761 Bug ID: 1114761 Summary: spamassassin spamd writing errors int logfile and not scanning some email Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pszaban(a)wne.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: Lots of messages like the following are being written into LEAP 15.0 /var/log/messages file by URIDBL.pm (spamassassin-3.4.1-lp150.5.3.x86_64) plugin: 2018-11-02T00:01:11.353456-04:00 XXXX spamd[2641]: Use of uninitialized value $4 in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.26.1/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1044. Reproducible: Sometimes Steps to Reproduce: 1.install Leap15.0, postfix and spamassassin 2.configure postfix to use spamassassin 3.start spamd and postfix 4.wait for email to come in via SMTP on port 25 5.examine /var/log/messages to see the error Unfortunately, I have a lot of config changes in postfix's main.cf and master.cf. I don't think it matters, g spamassassin and postfix seems to do the same thing. FYI: I send mail from postfix to spamd with the following lines in postfix's master.cf: smtp inet n - n - - smtpd -o content_filter=spamfilter:dummy . . . spamfilter unix - n n - - pipe flags=Rq user=defang argv=/usr/local/bin/spamfilter.scr -f ${sender} -- ${recipient} where /usr/local/bin/spamfilter.scr contains: #! /bin/bash /usr/bin/spamc --max-size=1500000 | /usr/sbin/sendmail -i "$@" exit $? ...and I start spamd with: /usr/sbin/spamd -d -i 127.0.0.1 -i ::1 -p 783 -x -m 40 -u spamd -r /var/run/spamd.pid --siteconfigpath=/usr/local/etc/mail/spamassassin/ Actual Results: /var/log/messages contains things like: 2018-11-02T00:01:11.353456-04:00 XXXX spamd[2641]: Use of uninitialized value $4 in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.26.1/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1044. Expected Results: should not have produced the error message, and should have scanned the message for URI's and looked them up in the DNS blocklists. I google'd the problem and installed the following patch to /usr/lib/perl5/vendor_perl/5.26.1/Mail/SpamAssassin/Plugin/URIDNSBL.pm. The patch *appears* to have solved the problem for me: --- spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm 2015/04/28 20:36:05 1676616 +++ spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm 2015/08/04 23:16:38 1694126 @@ -942,9 +942,8 @@ next unless (defined($str) && defined($dom)); dbg("uridnsbl: got($j) NS for $dom: $str"); - if ($str =~ /IN\s+NS\s+(\S+)/) { - my $nsmatch = lc $1; - $nsmatch =~ s/\.$//; + if ($rr->type eq 'NS') { + my $nsmatch = lc $rr->nsdname; # available since at least Net::DNS 0.14 my $nsrhblstr = $nsmatch; my $fullnsrhblstr = $nsmatch; @@ -1025,9 +1024,9 @@ } dbg("uridnsbl: complete_a_lookup got(%d) A for %s: %s", $j,$hname,$str); - local $1; - if ($str =~ /IN\s+A\s+(\S+)/) { - $self->lookup_dnsbl_for_ip($pms, $ent->{obj}, $1); + if ($rr->type eq 'A') { + my $ip_address = $rr->rdatastr; + $self->lookup_dnsbl_for_ip($pms, $ent->{obj}, $ip_address); } } } I'm reluctant to make many changes to the system to perform testing for fear of losing email. I mostly wanted to make you aware of the issue, and a potential solution to save someone else from having to go through what I recently went through to fix this. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1135043] New: spamassassin: sa-update triggers perl deprecation
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1135043 Bug ID: 1135043 Summary: spamassassin: sa-update triggers perl deprecation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hpj(a)urpla.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, after upgrading to 15.0, I noticed, that every (cron controlled) run of sa-update triggers: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^(.{ <-- HERE ,200}).*$/ at /usr/lib/perl5/vendor_perl/5.26.1/Mail/SpamAssassin/PerMsgStatus.pm line 921. Update available for channel updates.spamassassin.org: 1859108 -> 1859132 Command is: sa-update --nogpg --verbose --channelfile /etc/mail/spamassassin/update-channels.txt -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1133591] New: Spamassassin is noisy
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1133591 Bug ID: 1133591 Summary: Spamassassin is noisy Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: joerg(a)bec.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When running spamassassin as mail filter, the following annoying warning is written to the terminal: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^(.{ <-- HERE ,200}).*$/ at /usr/lib/perl5/vendor_perl/5.26.1/Mail/SpamAssassin/PerMsgStatus.pm line 921. It would be nice to get the trivial patch the escape it. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1107765] New: SpamAssassin Net::DNS : Patching required
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1107765 Bug ID: 1107765 Summary: SpamAssassin Net::DNS : Patching required Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: b631093f-779b-4d67-9ffe-5f6d5b1d3f8a(a)protonmail.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SpamAssassin 3.4.1 has an important bug (https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7223) that needs to be patched if the release of the Net::DNS Perl package installed on your system is 1.01 or larger. Leap15 is affected: SpamAssassin Server version 3.4.1 > perl -MNet::DNS -le 'print $Net::DNS::VERSION' 1.14 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[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 1118678] New: devel:languages:perl/spamassassin: Bug in Spec: Source:1 is not in bz2 Format
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1118678 Bug ID: 1118678 Summary: devel:languages:perl/spamassassin: Bug in Spec: Source:1 is not in bz2 Format Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request Assignee: varkoly(a)suse.com Reporter: mgoppold(a)web.de QA Contact: adrian(a)suse.com CC: coolo(a)suse.com Found By: --- Blocker: --- Source1: .../Mail-SpamAssassin-rules-%{version}.r%{rules_revision}.tgz and later in %install: ... pushd %{buildroot}/usr/share/spamassassin && tar -xjf %{S:1} && popd ... Fix it with: tar -xzf %{S:1} -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[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

[Bug 1028018] New: Updating postfix gives chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory
by bugzilla_noreply＠novell.com 29 Mar '21

29 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1028018 Bug ID: 1028018 Summary: Updating postfix gives chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just `zypper dup`-ed a Tumbleweed installation and got the following: Installing: postfix-3.1.4-3.1.x86_64 ........[done] Additional rpm output: Executing upgrade-configuration. chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory Updating /etc/sysconfig/postfix ... Updating /etc/sysconfig/mail ... Looking into /usr/lib/postfix indeed this file does not exist after the upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1112500] New: logwatch is out of sync with logrotate
by bugzilla_noreply＠novell.com 26 Mar '21

26 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1112500 Bug ID: 1112500 Summary: logwatch is out of sync with logrotate Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: adaugherity(a)tamu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In previous versions of openSUSE (up through Leap 42.2/SLE12SP2), both logwatch and logrotate were run via scripts in the /etc/cron.daily directory; logwatch was always run first because its symlink is named "0logwatch". This changed in 42.3/SP3 (and continues in 15) when logrotate was changed to use a systemd timer instead of cron.daily. Now it is possible for logrotate to run before logwatch, and if a log file is rotated, logwatch reports on just the few log entries in the new log file (which may be entirely skipped, depending on the range and archive settings used with logwatch), rather than a whole 24 hours' worth. Example: Apache access log; assume it's large enough to be rotated. Rotation happens at midnight (logrotate.timer) and the file is renamed to e.g. access_log-20181018.xz. When cron.daily runs (at DAILY_TIME from /etc/sysconfig/cron, let's say 04:00, or at boot and 24 hours thereafter if DAILY_TIME is not set), logwatch reports on /var/log/apache2/access_log, which only contains entries after midnight. With the default range of "yesterday", nothing will be reported*. *It would be via logwatch's archive processing (enabled by default), except that the shipped version of logwatch does not handle xz archives, only gz & bz2. Fix: replace the /etc/cron.daily/0logwatch symlink with a systemd timer? There are systemd service/timer definitions in the logwatch git[1], although they may need some tweaking to conform to SUSE and/or upstream systemd standards, and to make it run before logrotate does. Additionally, the git master has also added xz archive support, and a few other fixes/improvements. I don't know when an actual release will be cut, though -- there's an unanswered post in their forum asking that very thing. [1] https://sourceforge.net/p/logwatch/git/ci/master/tree/ systemd stuff is under the scheduler subdirectory -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1125689] New: nghttp2 mistake in spec file
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1125689 Bug ID: 1125689 Summary: nghttp2 mistake in spec file 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: holgerbruenjes(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in spec file from nghttp2-1.36.0-1.2.src.rpm and before the devel package require not the libnghttp2-asio correct require was libnghttp2 see pkgconfig file Libs: -L${libdir} -lnghttp2 %package -n %{soname}-devel Summary: Development files for nghttp2 Group: Development/Languages/C and C++ - Requires: %{soname_asio}%{sover_asio} = %{version} + Requires: %{soname}%{sover} = %{version} Provides: %{name}-devel -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1134616] New: nghttp2: fails to build with boost 1.70.0
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1134616 Bug ID: 1134616 Summary: nghttp2: fails to build with boost 1.70.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: tchvatal(a)suse.com Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com Blocks: 1134606 Found By: --- Blocker: --- This is a bug indicating that a package for whom you are maintainer in openSUSE:Factory no longer builds with the proposed Boost 1.70.0 and as such will require patching. You can see your package failing to build at, https://build.opensuse.org/package/show/home:adamm:boost_test/nghttp2 asio_server_connection.h:85:17: error: 'class boost::asio::ssl::stream<boost::asio::basic_stream_socket<boost::asio::ip::tcp> >' has no member named 'get_io_service' [ 121s] socket_.get_io_service(), socket_.lowest_layer().remote_endpoint(ec), [ 121s] ~~~~~~~~^~~~~~~~~~~~~~ https://stackoverflow.com/questions/39445636/alternative-to-deprecated-get-… Please patch the problem and submit the fixes as Boost 1.70.0 will be shortly submitted to Factory. If you are not maintainer, please let me know. Some packages do not have maintainers but only project maintainers, in which case I'm assigning the bug to the person doing most of recent changes and CC'ing the other maintainers. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1045287] New: systemd: mounts using "nofail" option are not correctly ordered during shutdown
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1045287 Bug ID: 1045287 Summary: systemd: mounts using "nofail" option are not correctly ordered during shutdown 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a mount entry in fstab uses the "nofail" option, systemd doesn't order the corresponding mount unit with a "Before=local-fs.target" so if the mount unit takes time to be activated, it won't delay the whole boot process. However by doing this, we also remove ordering constraint for the shutdown process. This can lead to the mount unit being stopped while some applications are still using the corresponding mount point. This problem was discussed in bug 1036962 but this bug was more about NFS or remote fs. In this case the fix already exists since v218 and remote fs automatically gain a Before=remote-fs.target after they're mounted. A similar fix has been submitted upstream for local fs which can be found here: https://github.com/systemd/systemd/pull/6102 and is waiting for approval. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 934256] New: Passwords maintained by Filezilla are easily recovered in some cases
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=934256 Bug ID: 934256 Summary: Passwords maintained by Filezilla are easily recovered in some cases Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Greg.Freemyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm testing with LaZagne: http://www.kitploit.com/2015/02/the-lazagne-project-recover-most-common.html Or in OBS @ home:gregfreemyer:Tools-for-forensic-boot-cd LaZagne Running LaZagne under my normal user account recovered one filezilla stored passwd. The amount of time taken was near instantaneous so I believe the password was simply decoded, not cracked in the sense of "John the ripper". The password was associated with a SFTP account, so it is a password I consider needing to be kept securely. I don't know if Filezilla simply handles passwords poorly or if it can be compiled differently to store passwords securely. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1135224] New: yast2-adsi crashes with "TypeError: Expected a string or unicode object" during auth
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1135224 Bug ID: 1135224 Summary: yast2-adsi crashes with "TypeError: Expected a string or unicode object" during auth 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: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- 2019-05-14 15:34:05 <3> linux-h7xz(14712) [Python] clients/adsi.py(<module>):57 Traceback (most recent call last): File "/usr/share/YaST2/clients/../include/adsi/wizards.py", line 11, in <lambda> 'adsi' : [(lambda lp, creds: ADSI(lp, creds).Show()), lp, creds], File "/usr/share/YaST2/clients/../include/adsi/dialogs.py", line 522, in Show self.conn = ConnectionSettings(self.creds, self.lp).Show() File "/usr/share/YaST2/clients/../include/adsi/dialogs.py", line 423, in Show ycred.Show(cred_valid) File "/usr/lib/python3.7/site-packages/adcommon-1.0-py3.7.egg/adcommon/creds.py", line 150, in Show got_creds = self.get_creds() File "/usr/lib/python3.7/site-packages/adcommon-1.0-py3.7.egg/adcommon/creds.py", line 182, in get_creds self.__delete_keyring() File "/usr/lib/python3.7/site-packages/adcommon-1.0-py3.7.egg/adcommon/creds.py", line 244, in __delete_keyring delete_password('adcommon', keyring_user) File "/usr/lib/python3.7/site-packages/keyring/core.py", line 69, in delete_password _keyring_backend.delete_password(service_name, username) File "/usr/lib/python3.7/site-packages/keyring/backends/SecretService.py", line 92, in delete_password for item in items: File "/usr/lib/python3.7/site-packages/secretstorage/collection.py", line 86, in search_items signature='a{ss}') File "/usr/lib/python3.7/site-packages/secretstorage/util.py", line 31, in function_out return function_in(*args, **kwargs) File "/usr/lib/python3.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3.7/site-packages/dbus/connection.py", line 641, in call_blocking message.append(signature=signature, *args) TypeError: Expected a string or unicode object This happens when 'save creds' is unchecked, but no creds have been previously saved to the keychain. I None type is being passed into keyring.delete_password(). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1135130] New: yast2-adsi authentication fails with "Failed to initialize ldap connection"
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1135130 Bug ID: 1135130 Summary: yast2-adsi authentication fails with "Failed to initialize ldap connection" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- adcommon/yldap.py(__ldap_connect):104 Failed to initialize ldap connection adsi/dialogs.py(cred_valid):421 Failed to initialize ldap connection The failure is actually in yast2-adcommon-python, in the kinit code. # kinit Administrator(a)FROGGY.SUSE.DE kinit: Credential cache directory /run/user/0/krb5cc does not exist while getting default ccache I can work around this by creating the /run/user/0 directory. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1133568] New: yast2-adcommon-python ldap doesn't correctly parse ldap urls for ldap.initialize()
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1133568 Bug ID: 1133568 Summary: yast2-adcommon-python ldap doesn't correctly parse ldap urls for ldap.initialize() 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: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Ldap urls with anything other than the scheme, host, and port crash with an LdapError and no message details. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1084864] New: YaST module names are too similar to some desktop environment configuration modules
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1084864 Bug ID: 1084864 Summary: YaST module names are too similar to some desktop environment configuration modules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: noahadvs(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 763361 --> http://bugzilla.suse.com/attachment.cgi?id=763361&action=edit How it should look when fixed YaST, GNOME, KDE Plasma and Enlightenment all have configuration modules named "Fonts" and a YaST module with the same exact name shows up when searching for "fonts" in all 3 DEs. This is not currently too much of a problem for users because the YaST Fonts module uses an icon representing X11 instead of an icon representing fonts, but there's no way to tell the difference without the icon. This will also be a problem for me because I am working on a KDE Breeze theme for YaST and intend to change the icon of the YaST Fonts module to a proper fonts icon. Fixing this problem will require changes to the code of yast-control-center and changes to the .desktop files shown for all YaST modules. 1. Every Name field needs to be prefixed with "YaST " or something similar to show association with YaST. However, this will cause every module name shown in the YaST Control Center to also have that prefix, which doesn't look good. 2. GenericName can be the field that YaST Control Center uses for module names instead. For example, the Name field could be "YaST Fonts" and the GenericName field could be "Fonts". 3. The GenericName field is currently used as if it was the Comment field, so YaST Control Center needs to display the Comment field instead of the GenericName field for module descriptions. All descriptions in the .desktop files need to be moved to the Comment field. -- You are receiving this mail because: You are on the CC list for the bug.

2 41

[Bug 918028] New: no Grub Legacy shell history
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=918028 Bug ID: 918028 Summary: no Grub Legacy shell history Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- To reproduce: 1-login root on tty[1-6] on en_US installation 2-grub 3-find /boot/grub/stage1 4-keystroke <UP> Actual behavior: 1-^[[A appears at prompt Expected behavior: 1-find /boot/grub/stage1 appears at prompt Comments: 1-Shell cmdline history works as expected in 13.1, as in all previous openSUSE releases. 2-I recognized this problem many months ago, maybe as much as a year ago, but only just surmised it was almost certainly 13.2 and up Grub Legacy post-0.97-194.1.2 itself rather than having anything to do with kernel, framebuffer configuration, video mode, or files contained in target /boot/grub/. "Downgrading" to 13.1's 0.97-194.1.2 fixes 13.2 and Tumbleweed. 3-Nearly all my Grub stanzas include "splash=verbose vga=791 video=1024x768@60 3 " on cmdline. 4-All my openSUSE installations are on multiboot hardware (no VMs), with keyboards on PS/2 ports. 5-Plymouth is not installed in any of my openSUSE installations. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1012388] New: cmake should not set -Wl,--no-undefined for modules
by bugzilla_noreply＠novell.com 12 Mar '21

12 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1012388 Bug ID: 1012388 Summary: cmake should not set -Wl,--no-undefined for modules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the file /etc/rpm/macros.cmake -Wl,--no-undefined should not be set for CMAKE_MODULE_LINKER_FLAGS. As modules are loaded into other binaries they are allowed to have undefined functions. Normally the application loading them has the required library loaded. Please remove the flag for modules in openSUSE Leap, Tumbleweed and Factory. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1097006] New: dwz debuginfo splitting is one-thread and very very slow on packages which have too many libs
by bugzilla_noreply＠novell.com 10 Mar '21

10 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1097006 Bug ID: 1097006 Summary: dwz debuginfo splitting is one-thread and very very slow on packages which have too many libs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: pth(a)suse.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mliska(a)suse.cz Found By: --- Blocker: --- Obs generates dwz compression for all items at once to reduce space: [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_0x0100.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/adt_null.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_ed25519.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_gssapi.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_pam.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_socket.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/disks.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/client_ed25519.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/dialog_examples.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_test_plugin.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_blackhole.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/file_key_management.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/example_key_management.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_connect.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_archive.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_example.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_federated.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_mroonga.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_oqgraph.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_federatedx.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_rocksdb.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_sphinx.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_spider.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/handlersocket.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/libdaemon_example.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/locales.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_test_sql_discovery.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/metadata_lock_info.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/qa_auth_client.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/query_cache_info.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/mypluglib.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/qa_auth_interface.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/qa_auth_server.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/query_response_time.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/semisync_slave.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/sql_errlog.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/semisync_master.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/server_audit.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/sbin/mysqld [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/simple_password_check.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/wsrep_info.so [ 497s] /usr/lib/rpm/sepdebugcrcfix: Updated 80 CRC32s, 0 CRC32s did match. As you can see whole build took 209s while dwz split another 288s utilizing just one core. The -multifile mode tries to reduce the size even more, but question is if there are enough gains to justify the slowdown. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1135809] New: Udev package does not contain persistent-ifnames script any more
by bugzilla_noreply＠novell.com 08 Mar '21

08 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1135809 Bug ID: 1135809 Summary: Udev package does not contain persistent-ifnames script any more Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: sknorr(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- The script mentioned in https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/index.html… is not available from the package `udev` anymore. IT is now packaged as `udev-persistent-interfaces`. To be able to use it at all, you need to run the following after installation: > ln -s foobar/75-rule-generator-script.rule /etc/udev/rules.d/ -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1084827] New: email links in forum "Reply to thread" notices open Corrupted Content Error page instead of forum page
by bugzilla_noreply＠novell.com 08 Mar '21

08 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1084827 Bug ID: 1084827 Summary: email links in forum "Reply to thread" notices open Corrupted Content Error page instead of forum page Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: lars.vogdt(a)suse.com CC: per(a)computer.org, suse-beta(a)cboltz.de Found By: --- Blocker: --- Problem: email links in forum "Reply to thread" notices open Corrupted Content Error page instead of forum page email list thread that produced no useful response: https://lists.opensuse.org/heroes/2018-02/msg00008.html error message:[quote] Corrupted Content Error The site at https://forums.opensuse.org/showthread.php/530041-Leap-42-3-nouveau-pointer… has experienced a network protocol violation that cannot be repaired. The page you are trying to view cannot be shown because an error in the data transmission was detected. Please contact the website owners to inform them of this problem.[/quote] These forums(a)microfocus.com email links always work if pasted into the urlbar and the trailing "?goto=newpost" is removed before proceeding. This highly annoying web accessibility impediment started happening routinely around the first of this year. IIRC, around that time, around 6 months after I updated from 42.1 to 42.3, there were some significant Nuremberg infrastructure changes. To cause these links to load the error page instead of the intended destination requires no particular action or inaction I've been able to pin down. It routinely happens while I have various B.O.O. bug pages loaded, among them saved searches, one or more of which have remained loaded across browser restarts, and may or may not have been used in recent hours or minutes. There may or may not be any open wiki or forum pages on restart, but there will nearly always have been at least one of them open in logged in state within the past 24 hours. I rarely have the browser closed except briefly for daily backup or when I log out for zypper system updating. I always start browser by loading previous session, which always has well over a hundred tabs. Since browser restarts usually cause logging out from login.microfocus.com, I typically switch to one of the open B.O.O. tabs to force re-logging in by clicking on a saved search link shortly after a browser reopen. Often I remember to check that I remain logged in before trying to open an emailed forum link, after which the link is less likely to produce the error page. Unless I've relatively recently been active on a forum or wiki page, the most likely result of the attempt is the corruption error, unless I have one or more open and recently touched forum or wiki page with a visible "log out" link. The browser I virtually always use for BOO, forum and Wiki Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.2 has NoScript extension set to always allow opensuse.org pages. -- You are receiving this mail because: You are on the CC list for the bug.

2 26

[Bug 1130294] New: Problem reading past end of CD-ROMs?
by bugzilla_noreply＠novell.com 04 Mar '21

04 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1130294 Bug ID: 1130294 Summary: Problem reading past end of CD-ROMs? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Sine a few months I'm having the new problem that my BlueRay drive goes crazy once dracut or GUB2 updates the bootloader: The BlueRay drive (with a boot CD in it) spins up, makes noises as if continually relacibrating, and everything seems to hang, and pressing the ejct button does not work for a long time (>30s). Eventually when the tray opens, dracut continues, and the the update finshes. My suspect is that the kernel (or dracut or some related code) tried to access the medium past it end, and the drive does not like that. For a recent occurrence the kernel messages look like this: Mär 18 21:30:12 host.site [RPM][4520]: erase dracut-044.1-lp150.14.18.1.x86_64: success Mär 18 21:30:12 host.site [RPM][4520]: Transaction ID 5c8fffd2 finished: 0 Mär 18 21:30:12 host.site [RPM][4567]: Transaction ID 5c8fffd4 started Mär 18 21:30:12 host.site [RPM][4567]: erase java-1_8_0-openjdk-devel-1.8.0.191-lp150.2.9.2.x86_64: success Mär 18 21:30:14 host.site [RPM][4567]: install java-1_8_0-openjdk-devel-1.8.0.201-lp150.2.12.1.x86_64: success Mär 18 21:30:14 host.site [RPM][4567]: erase java-1_8_0-openjdk-devel-1.8.0.191-lp150.2.9.2.x86_64: success Mär 18 21:30:14 host.site [RPM][4567]: install java-1_8_0-openjdk-devel-1.8.0.201-lp150.2.12.1.x86_64: success Mär 18 21:30:14 host.site [RPM][4567]: Transaction ID 5c8fffd4 finished: 0 Mär 18 21:31:26 host.site kernel: sr 2:0:0:0: [sr0] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mär 18 21:31:26 host.site kernel: sr 2:0:0:0: [sr0] tag#30 Sense Key : Medium Error [current] Mär 18 21:31:26 host.site kernel: sr 2:0:0:0: [sr0] tag#30 Add. Sense: No seek complete Mär 18 21:31:26 host.site kernel: sr 2:0:0:0: [sr0] tag#30 CDB: Read(10) 28 00 00 00 1a 10 00 00 02 00 Mär 18 21:31:26 host.site kernel: print_req_error: I/O error, dev sr0, sector 26688 Mär 18 21:31:26 host.site kernel: attempt to access beyond end of device Mär 18 21:31:26 host.site kernel: sr0: rw=0, want=26692, limit=26688 Mär 18 21:31:26 host.site kernel: Buffer I/O error on dev sr0, logical block 6672, async page read Mär 18 21:31:26 host.site kernel: attempt to access beyond end of device Mär 18 21:31:26 host.site kernel: sr0: rw=0, want=26696, limit=26688 Mär 18 21:31:26 host.site kernel: Buffer I/O error on dev sr0, logical block 6673, async page read Mär 18 21:31:34 host.site kernel: sr 2:0:0:0: [sr0] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mär 18 21:31:34 host.site kernel: sr 2:0:0:0: [sr0] tag#2 Sense Key : Medium Error [current] Mär 18 21:31:34 host.site kernel: sr 2:0:0:0: [sr0] tag#2 Add. Sense: No seek complete Mär 18 21:31:34 host.site kernel: sr 2:0:0:0: [sr0] tag#2 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00 Mär 18 21:31:34 host.site kernel: print_req_error: I/O error, dev sr0, sector 0 Mär 18 21:31:41 host.site kernel: sr 2:0:0:0: [sr0] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mär 18 21:31:41 host.site kernel: sr 2:0:0:0: [sr0] tag#5 Sense Key : Medium Error [current] Mär 18 21:31:41 host.site kernel: sr 2:0:0:0: [sr0] tag#5 Add. Sense: No seek complete Mär 18 21:31:41 host.site kernel: sr 2:0:0:0: [sr0] tag#5 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00 Mär 18 21:31:41 host.site kernel: print_req_error: I/O error, dev sr0, sector 0 Mär 18 21:31:41 host.site kernel: Buffer I/O error on dev sr0, logical block 0, async page read Mär 18 21:31:48 host.site kernel: sr 2:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mär 18 21:31:48 host.site kernel: sr 2:0:0:0: [sr0] tag#8 Sense Key : Medium Error [current] Mär 18 21:31:48 host.site kernel: sr 2:0:0:0: [sr0] tag#8 Add. Sense: No seek complete Mär 18 21:31:48 host.site kernel: sr 2:0:0:0: [sr0] tag#8 CDB: Read(10) 28 00 00 00 00 01 00 00 01 00 Mär 18 21:31:48 host.site kernel: print_req_error: I/O error, dev sr0, sector 4 Mär 18 21:31:48 host.site kernel: Buffer I/O error on dev sr0, logical block 1, async page read Information of the boot cd in the drive is: # isoinfo -d -i /dev/sr0 Setting input-charset to 'UTF-8' from locale. CD-ROM is in ISO 9660 format System id: Volume id: ISOIMAGE Volume set id: Publisher id: Data preparer id: XORRISO-1.4.6 2016.09.16.133001, LIBISOBURN-1.4.6, LIBISOFS-1.4.6, LIBBURN-1.4.6 Application id: Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 6660 El Torito VD version 1 found, boot catalog is in sector 1610 NO Joliet present SUSP signatures version 1 found Rock Ridge signatures version 1 found Rock Ridge id 'RRIP_1991A' Eltorito validation header: Hid 1 Arch 0 (x86) ID '' Cksum AA 55 OK Key 55 AA Eltorito defaultboot header: Bootid 88 (bootable) Boot media 0 (No Emulation Boot) Load segment 0 Sys type 0 Nsect 4 Bootoff 9CE 2510 A similar effect happens when I plug in an old Sandisk Cruzer U3 stick that features CD-ROM emulation: Mär 24 19:28:11 i7g4x4a.site kernel: scsi_io_completion: 85 callbacks suppressed Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current] Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 be 81 00 00 01 00 Mär 24 19:28:11 i7g4x4a.site kernel: print_req_error: 85 callbacks suppressed Mär 24 19:28:11 i7g4x4a.site kernel: print_req_error: I/O error, dev sr1, sector 195076 Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current] Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf fa 00 00 02 00 Mär 24 19:28:11 i7g4x4a.site kernel: print_req_error: I/O error, dev sr1, sector 196584 Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current] Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf fa 00 00 01 00 Mär 24 19:28:11 i7g4x4a.site kernel: print_req_error: I/O error, dev sr1, sector 196584 Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current] Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information Mär 24 19:28:11 i7g4x4a.site kernel: sr 6:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf fb 00 00 01 00 Mär 24 19:28:11 i7g4x4a.site kernel: print_req_error: I/O error, dev sr1, sector 196588 ISO-Information for this device is: # isoinfo -d -i /dev/sr1 Setting input-charset to 'UTF-8' from locale. CD-ROM is in ISO 9660 format System id: Volume id: U3 System Volume set id: 20090910_1508 Publisher id: MagicISO v5.2 COPYRIGHT (C) 2001-2006 MagicISO, Inc. Data preparer id: MagicISO v5.2 COPYRIGHT (C) 2001-2006 MagicISO, Inc. Application id: Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 0 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 3518 Joliet with UCS level 3 found. No SUSP/Rock Ridge present -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1133294] New: LTO: xorg-x11-server build fails
by bugzilla_noreply＠novell.com 03 Mar '21

03 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1133294 Bug ID: 1133294 Summary: LTO: xorg-x11-server build fails 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails due to: [ 786s] events.c:605:49: error: array subscript -1 is below array bounds of 'struct _Window *[16]' [-Werror=array-bounds] https://bugs.freedesktop.org/show_bug.cgi?id=110256 -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1090209] New: Package libgccjit
by bugzilla_noreply＠novell.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1090209 Bug ID: 1090209 Summary: Package libgccjit Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: adam(a)mizerski.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- GCC provides libgccjit. I'd be grateful if it was packaged. https://gcc.gnu.org/onlinedocs/jit/internals/index.html#packaging-notes -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1127857] New: libreoffice fails to build against devel:gcc
by bugzilla_noreply＠novell.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1127857 Bug ID: 1127857 Summary: libreoffice fails to build against devel:gcc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gcc8 slated for submission to Factory (SR#679161) fails to build libreoffice. Local build of Factory status results in [10399s] [build CUT] sw_uwriter [10399s] /bin/sh: line 1: 6191 Segmentation fault ( LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program":$W/UnpackedTarball/cppunit/src/cppunit/.libs MALLOC_CHECK_=2 MALLOC_PERTURB_=153 $W/LinkTarget/Executable/cppunittester $W/LinkTarget/CppunitTest/libtest_sw_uwriter.so --headless "-env:BRAND_BASE_DIR=file://$S/instdir" "-env:BRAND_SHARE_SUBDIR=share" "-env:BRAND_SHARE_RESOURCE_SUBDIR=program/resource" "-env:UserInstallation=file://$W/CppunitTest/sw_uwriter.test.user" "-env:CONFIGURATION_LAYERS=xcsxcu:file://$I/share/registry xcsxcu:file://$W/unittest/registry" "-env:UNO_TYPES=file://$I/program/types.rdb file://$I/program/types/offapi.rdb file://$I/program/types/oovbaapi.rdb" "-env:UNO_SERVICES=file://$W/Rdb/ure/services.rdb file://$W/ComponentTarget/comphelper/util/comphelp.component file://$W/ComponentTarget/configmgr/source/configmgr.component file://$W/ComponentTarget/framework/util/fwk.component file://$W/ComponentTarget/i18npool/util/i18npool.component file://$W/ComponentTarget/package/util/package2.component file://$W/ComponentTarget/package/source/xstor/xstor.component file://$W/ComponentTarget/sfx2/util/sfx.component file://$W/ComponentTarget/ucb/source/core/ucb1.component file://$W/ComponentTarget/ucb/source/ucp/file/ucpfile1.component file://$W/ComponentTarget/unotools/util/utl.component file://$W/ComponentTarget/unoxml/source/service/unoxml.component file://$W/ComponentTarget/uui/util/uui.component" -env:URE_INTERNAL_LIB_DIR=file://$I/program -env:LO_LIB_DIR=file://$I/program -env:LO_JAVA_DIR=file://$I/program/classes --protector $W/LinkTarget/Library/unoexceptionprotector.so unoexceptionprotector --protector $W/LinkTarget/Library/unobootstrapprotector.so unobootstrapprotector --protector $W/LinkTarget/Library/libvclbootstrapprotector.so vclbootstrapprotector "-env:CPPUNITTESTTARGET=$W/CppunitTest/sw_uwriter.test" ) > $W/CppunitTest/sw_uwriter.test.log 2>&1 [10399s] ToxMiscTest::testTdf73162 finished in: 0ms [10399s] ToxTextGeneratorTest::EmptyStringIsReturnedForPageNumberPlaceholderOfZeroItems finished in: 0ms [10399s] ToxTextGeneratorTest::OneAtSignIsReturnedForPageNumberPlaceholderOfOneItem finished in: 0ms [10399s] ToxTextGeneratorTest::TwoAtSignsAreReturnedForPageNumberPlaceholderOfOneItem finished in: 0ms [10399s] ToxTextGeneratorTest::TwoAtSignsAreReturnedForPageNumberPlaceholderOfOneItem finished in: 0ms [10399s] ToxTextGeneratorTest::EmptyStringIsReturnedAsNumStringIfNoTextMarkIsSet finished in: 0ms [10399s] ToxTextGeneratorTest::EmptyStringIsReturnedAsNumStringIfToxSourcesIsEmpty finished in: 0ms [10399s] which: no gdb in (/usr/local/bin:/usr/bin:/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/lib64/jvm/java/bin) [10399s] You need gdb in your path to show backtraces [10400s] [10400s] Error: a unit test failed, please do one of: [10400s] [10400s] make CppunitTest_sw_uwriter CPPUNITTRACE="gdb --args" [10400s] # for interactive debugging on Linux [10400s] make CppunitTest_sw_uwriter VALGRIND=memcheck [10400s] # for memory checking [10400s] make CppunitTest_sw_uwriter DEBUGCPPUNIT=TRUE [10400s] # for exception catching [10400s] [10400s] You can limit the execution to just one particular test by: [10400s] [10400s] make CPPUNIT_TEST_NAME="testXYZ" ...above mentioned params... [10400s] [10400s] make[1]: *** [/home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/solenv/gbuild/CppunitTest.mk:121: /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/workdir/CppunitTest/sw_uwriter.test] Error 1 [10400s] make[1]: *** Waiting for unfinished jobs.... [10425s] In member function '_ZN10ScDPSource17FillMemberResultsEv.part.548', [10425s] inlined from 'FillMemberResults' at /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx:1018:6, [10425s] inlined from 'getResults' at /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx:1063:22: [10425s] /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx:1036:84: warning: argument 1 value '18446744073709551615' exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=] [10425s] pColResults.reset(new uno::Sequence<sheet::MemberResult>[nColLevelCount]); [10425s] ^ [10425s] /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx: In member function 'getResults': [10425s] /usr/include/c++/8/new:122:7: note: in a call to allocation function 'operator new []' declared here [10425s] void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc) [10425s] ^ [10425s] In member function '_ZN10ScDPSource17FillMemberResultsEv.part.548', [10425s] inlined from 'FillMemberResults' at /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx:1018:6, [10425s] inlined from 'getResults' at /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx:1063:22: [10425s] /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx:1050:85: warning: argument 1 value '18446744073709551615' exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=] [10425s] pRowResults.reset( new uno::Sequence<sheet::MemberResult>[nRowLevelCount] ); [10425s] ^ [10425s] /home/abuild/rpmbuild/BUILD/libreoffice-6.2.0.3/sc/source/core/data/dptabsrc.cxx: In member function 'getResults': [10425s] /usr/include/c++/8/new:122:7: note: in a call to allocation function 'operator new []' declared here [10425s] void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc) [10425s] ^ [10425s] make: *** [Makefile:286: build] Error 2 [10425s] error: Bad exit status from /var/tmp/rpm-tmp.veZtng (%check) [10425s] [10425s] [10425s] RPM build errors: [10425s] Macro expanded in comment on line 23: %define tarball_url https://download.documentfoundation.org/libreoffice/src/6.1.0 [10425s] [10425s] Bad exit status from /var/tmp/rpm-tmp.veZtng (%check) [10425s] [10425s] murzim failed "build libreoffice.spec" at Mon Mar 4 16:22:26 UTC 2019. [10425s] I'm not sure whether the interleaved compiler warnings/notes have anything to say or whether just the segmentation fault is the issue (I think that's it). gdb is not in BuildRequires so we don't get a meaningful backtrace. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1111735] New: Out of date package: openSUSE:Factory/mypaint
by bugzilla_noreply＠novell.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1111735 Bug ID: 1111735 Summary: Out of date package: openSUSE:Factory/mypaint 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: sean(a)suspend.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory/mypaint is out of date (1.1.0). Current upstream release is: https://github.com/mypaint/mypaint/releases/download/v1.2.1/mypaint-1.2.1.t…. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1074478] New: scim-bridge-*-32bit not installable
by bugzilla_noreply＠novell.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1074478 Bug ID: 1074478 Summary: scim-bridge-*-32bit not installable 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- can't install scim-bridge-qt4-32bit-0.4.17-1.3.x86_64: nothing provides scim-bridge-32bit = 0.4.17 needed by scim-bridge-qt4-32bit-0.4.17-1.3.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1090572] New: VUL-0: CVE-2018-1110: CVE-2018-1110: Knot Resolver <= 2.2.0 Improper Input Validation
by bugzilla_noreply＠novell.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1090572 Bug ID: 1090572 Summary: VUL-0: CVE-2018-1110: CVE-2018-1110: Knot Resolver <= 2.2.0 Improper Input Validation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/204731/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: i(a)marguerite.su Reporter: kbabioch(a)suse.com QA Contact: security-team(a)suse.de CC: detlef(a)die-mafia.de, mrueckert(a)suse.com, pascal.bleser(a)opensuse.org Found By: Security Response Team Blocker: --- CVE-2018-1110 Hello, Knot Resolver software version <= 2.2.0 suffers from Improper Input Validation bugs which allow remote attacker to crash the resolver by sending specially crafted packets. Fixes ===== Knot Resolver 2.3.0 fixes all known security bugs and is available from https://www.knot-resolver.cz/download/ Backports ========= To fix the bugs we had to do major changes to some data structures so backport it most likely not feasible. We are discontinuing support for *all* versions older than 2.3.0 and discourage attempts to backport fixes because these will most likely introduce additional bugs. CVE request data ================ Fixed version: Knot Resolver 2.3.0 Vulnerability type: CWE-20: Improper Input Validation Affected component: resolver Impact of exploitation: Program crashes. Description of vulnerability: Improper input validation bugs in DNS resolver component of Knot Resolver (up to and including version 2.2.0) allow remote attacker who can create malformed packets to cause denial of service. Attack Vector (AV): Network Attack Complexity (AC): Low Privileges Required (PR): None User Interaction (UI): None Scope (S): Unchanged Confidentiality (C): None Integrity (I): Low Availability (A): High Technical Details: CWE-20 CWE-476 CWE-626 Acknowledgment: CZ.NIC would like to thank Toshifumi Sakaguchi and Vicky Shrestha for their responsible reporting of security vulnerabilities. -- Petr Špaček @ CZ.NIC References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1110 http://seclists.org/oss-sec/2018/q2/63 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1029979] New: util-linux has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029979 Bug ID: 1029979 Summary: util-linux has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- util-linux is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1029978] New: tcsh has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029978 Bug ID: 1029978 Summary: tcsh has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- tcsh is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1029974] New: rpm has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029974 Bug ID: 1029974 Summary: rpm has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpm is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3