May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1051848] New: server:mail/cyrus-imapd: proxy segfault after upgrade to 2.4.19-149.1
by bugzilla_noreply＠novell.com 26 Feb '20

26 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1051848 Bug ID: 1051848 Summary: server:mail/cyrus-imapd: proxy segfault after upgrade to 2.4.19-149.1 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: wullinger(a)rz.uni-kiel.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- We use cyrus imapd 2.4 in a proxy configuration for multiple mailbox storage servers. Since upgrading to 2.4.19-149.1, the frontend proxies (and only those) experience frequent segfaults of pop3d, proxyd, timsieved, and lmptproxyd: Aug 2 06:16:31 frontend3 kernel: [488770.024881] pop3d[XXXX]: segfault at 7f42ef735738 ip 00007f42ef546ca3 sp 00007ffdd7a45970 error 4 in ld-2.11.3.so[7f42ef539000+1f000] The problems disappears after downgrading back to cyrus-imapd-2.4.19-146.1. After such a crash, the BDB environment is often reported as needing recovery (we only use skiplist DBs, but BDB gets initialized nonetheless) As far as we can tell, there's no interruption of service associated with these crashes. For example, for lmtpproxyd, the problem seems to appear after the final QUIT, when the process is about to exit, anyway: write(13, "QUIT\r\n", 6) = 6 rt_sigprocmask(SIG_BLOCK, [INT QUIT ALRM TERM CHLD], [], 8) = 0 pselect6(14, [13], NULL, NULL, {229, 0}, {[], 8}) = 1 (in [13], left {228, 999487532}) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(13, "221 2.0.0 bye\r\n", 4096) = 15 rt_sigprocmask(SIG_BLOCK, [INT QUIT ALRM TERM CHLD], [], 8) = 0 pselect6(14, [13], NULL, NULL, {0, 0}, {[], 8}) = 1 (in [13], left {0, 0}) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(13, "", 4096) = 0 shutdown(13, 0 /* receive */) = 0 close(13) = 0 munmap(0x7f87be793000, 38608896) = 0 close(8) = 0 munmap(0x7f87c693f000, 40960) = 0 munmap(0x7f87c6873000, 98304) = 0 munmap(0x7f87c1aca000, 28131328) = 0 munmap(0x7f87c688b000, 671744) = 0 --- SIGSEGV (Segmentation fault) @ 0 (0) --- A slight hunch seems to suggest that there's a memory corruption issue that gets triggered during the final close of the BDB environment. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1071153] New: offlineimap needs python2-six
by bugzilla_noreply＠novell.com 25 Feb '20

25 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1071153 Bug ID: 1071153 Summary: offlineimap needs python2-six Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ralf.Friedl(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- File /usr/lib/python2.7/site-packages/offlineimap/accounts.py:23 from package offlineimap-7.1.4-1.2.noarch contains "import six", but python2-six is not listed in the package requirements. As a consequence, just installing offlineimap if python2-six is not already installed leads to this error: > Traceback (most recent call last): > File "/usr/bin/offlineimap", line 20, in <module> > from offlineimap import OfflineImap > File "/usr/lib/python2.7/site-packages/offlineimap/__init__.py", line 20, in <module> > from offlineimap.init import OfflineImap > File "/usr/lib/python2.7/site-packages/offlineimap/init.py", line 34, in <module> > from offlineimap import threadutil, accounts, folder, mbnames > File "/usr/lib/python2.7/site-packages/offlineimap/accounts.py", line 23, in <module> > import six > ImportError: No module named six -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1086614] New: Duplicate / ambiguous desktop session selection entriesin sddm
by bugzilla_noreply＠novell.com 24 Feb '20

24 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1086614 Bug ID: 1086614 Summary: Duplicate / ambiguous desktop session selection entriesin sddm 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: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation in an installation of openSUSE Leap 15.0 installing many desktop managers, window managers, etc. I see the following entries in sddm: * Enlightenment * GNOME on Xorg * GNOME * IceWM Session * IceWM * LXDE * LXQt Desktop * MATE * Openbox * Plasma * TWM * Xfce Session * Enlightenment (Wayland) * GNOME (Wayland) * Plasma (Wayland) ## Problem I see the following issues: * What is "GNOME" when there is already "GNOME on Xorg", "GNOME (Wayland)"? * Can "GNOME on Xorg" and "GNOME (Wayland)" use a common naming scheme? E.g. "GNOME" (implicit Xorg) and "GNOME (Wayland)" or "GNOME (Xorg)", "GNOME (Wayland)"? * "IceWM Session" and "IceWM" duplicate? * Why the suffix "Desktop" in "LXQt Desktop" and "Session" on "Xfce" and and of the IceWM entry when others do not have that? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1117323] New: when leap 15.1 as a kvm guest it could enable ibrs even host disable this mitigation with nospectre_v2
by bugzilla_noreply＠novell.com 24 Feb '20

24 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1117323 Bug ID: 1117323 Summary: when leap 15.1 as a kvm guest it could enable ibrs even host disable this mitigation with nospectre_v2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jnwang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I use a 4.4.162-78-default as a kvm host.(with nospectre_v2) lscpu can't dispaly 'ibrs' flag. and boot a kvm guest setup leap 15.1; The qemu cmdline is: /usr/bin/qemu-system-x86_64 -vga cirrus -only-migratable -chardev ringbuf,id=serial0,logfile=serial0,logappend=on -serial chardev:serial0 -soundhw ac97 -global isa-fdc.driveA= -m 1024 -cpu qemu64 -netdev user,id=qanet0 -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -boot order=c,menu=on,splash-time=5000 -device usb-ehci -device usb-tablet -smp 1 -enable-kvm -no-shutdown -vnc :91,share=force-shared -device virtio-serial -chardev socket,path=virtio_console,server,nowait,id=virtio_console,logfile=virtio_console.log,logappend=on -device virtconsole,chardev=virtio_console,name=org.openqa.console.virtio_console -chardev socket,path=qmp_socket,server,nowait,id=qmp_socket,logfile=qmp_socket.log,logappend=on -qmp chardev:qmp_socket -S -device virtio-scsi-pci,id=scsi0 -blockdev driver=file,node-name=hd0-overlay0-file,filename=/var/lib/openqa/pool/1/raid/hd0-overlay0,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0-overlay0,file=hd0-overlay0-file,cache.no-flush=on -device virtio-blk,id=hd0-device,drive=hd0-overlay0,bootindex=0,serial=hd0 -blockdev driver=file,node-name=hd1-file,filename=/var/lib/openqa/pool/1/raid/hd1,cache.no-flush=on -blockdev driver=qcow2,node-name=hd1,file=hd1-file,cache.no-flush=on -device virtio-blk,id=hd1-device,drive=hd1,serial=hd1 -blockdev driver=file,node-name=cd0-overlay0-file,filename=/var/lib/openqa/pool/1/raid/cd0-overlay0,cache.no-flush=on -blockdev driver=qcow2,node-name=cd0-overlay0,file=cd0-overlay0-file,cache.no-flush=on -device scsi-cd,id=cd0-device,drive=cd0-overlay0,serial=cd0 Guest could boot up, and lscpu can't display ibrs in guest. and then, I added spectre_v2=ibrs on command line. reboot guest. when guest start up with spectre_v2=ibrs, the dmesg tell me spectre_v2 enable mitigation is IBRS. but it's lscpu tell me no 'ibrs' flag. This inconsistent is a regression. I believe IBRS have been enable in Guest, even host disabled it. So there is two kep point, 1). QEMU pass-through the flag 'spec-ctrl' to guest, when host disable this feature. 2). For QEMU viewpoint, 'ibrs ibpb stibp' all in one feature 'spec-ctrl', but in linux kernel, 'nospectre_v2' only disable 'ibrs', 'ibpb' and 'stibp' still available at output of lscpu. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 917728] New: Obsolete/deprecated config option still enabled
by bugzilla_noreply＠novell.com 23 Feb '20

23 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=917728 Bug ID: 917728 Summary: Obsolete/deprecated config option still enabled Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: zaitor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Kernel people. Just installed the spiffy new 3.19 kernel from Kernel:stable, and when going through journald logs to see if there was something new and exciting I came over these warnings that I've seen for ages, but never cared for since it seem to do no harm. linux-ial4:~ # uname -r 3.19.0-1.g8a7d5f9-desktop linux-ial4:~ # journalctl -b | grep CONFIG_ACPI_PROCFS_POWER feb. 13 00:27:50 linux-ial4 kernel: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared feb. 13 00:27:50 linux-ial4 kernel: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared feb. 13 00:27:50 linux-ial4 kernel: ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared linux-ial4:~ # ---- But today I took the time to google it, and found this bug from Arch https://bugs.archlinux.org/task/25845 Snip from bug ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared This was scheduled for removal in 2.6.39, but is still there. I suggest trying to disable it for 3.1, if for nothing else than to discover what problems this might cause so the appropriate bug reports can be filed. >From Documentation/feature-removal-schedule.txt: What: CONFIG_ACPI_PROCFS_POWER When: 2.6.39 Why: sysfs I/F for ACPI power devices, including AC and Battery, has been working in upstream kernel since 2.6.24, Sep 2007. In 2.6.37, we make the sysfs I/F always built in and this option disabled by default. Remove this option and the ACPI power procfs interface in 2.6.39. Who: Zhang Rui <rui.zhang(a)intel.com> ---- Short story this was disabled on Arch back in 2011 Could we do this for openSUSE too? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1105742] New: lpoptions are ignored by KDE apps
by bugzilla_noreply＠novell.com 20 Feb '20

20 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1105742 Bug ID: 1105742 Summary: lpoptions are ignored by KDE apps Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: morten(a)soeltoft.dk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- KDE apps are ignnoring default printer setting from ~/.cups/lpoptions. Gnome apps like gedit and Gimp are working ok. Worked fine at plasma 5.12.x -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1088249] New: Korganizer deletes caldav events only locally.
by bugzilla_noreply＠novell.com 19 Feb '20

19 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1088249 Bug ID: 1088249 Summary: Korganizer deletes caldav events only locally. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dev(a)cyclinggeorgian.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Events created on the server side (web), or in other clients (mobile) are synced to the Korganizer. Events created in Korganizer synced to the server too, and they show up on all clients connected to caldav server as expected. But when i delete event in Korganizer event is removed only locally. Delete action is not transmitted to the server. (running latest Tumbleweed updates) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1127766] New: installation aborted if snapper fails
by bugzilla_noreply＠novell.com 19 Feb '20

19 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1127766 Bug ID: 1127766 Summary: installation aborted if snapper fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ohering(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- per bug#1048338, subvolume handing is (or was) suboptimal. Today I tried to upgrade an existing subvolume to 15.1. I set the default to this subvolume and booted with 'upgrade=1'. Since I do not use snapshots, there is no /.snapshots. Something does not like that fact: [Ruby] yast2/fs_snapshot.rb:317 Executing: "/usr/lib/snapper/installation-helper --step 5 --root-prefix=/mnt --snapshot-type pre --description before\ update --userdata "important=yes" --cleanup number" [bash] ShellCommand.cc(shellcommand):78 reading failed [bash] ShellCommand.cc(shellcommand):78 terminate called after throwing an instance of 'snapper::IOErrorException' [bash] ShellCommand.cc(shellcommand):78 what(): open failed path:/mnt//.snapshots errno:2 (No such file or directory) [Ruby] yast2/fs_snapshot.rb:323 Snapshot could not be created: /usr/lib/snapper/installation-helper --step 5 --root-prefix=/mnt --snapshot-type pre --description before\ update --userdata "important=yes" --cleanup number returned: {"exit"=>134, "stderr"=>"reading failed\nterminate called after throwing an instance of 'snapper::IOErrorException'\n what(): open failed path:/mnt//.snapshots errno:2 (No such file or directory)\n", "stdout"=>""} [Ruby] yast/builtins.rb:586 tostring builtin called on wrong type Class [Ruby] yast/wfm.rb:253 Client /mounts/mp_0001/usr/share/YaST2/clients/inst_update_partition.rb failed with 'Filesystem snapshot could not be created.' (Yast2::SnapshotCreationFailed). It seems the expectation is btrfs == snapshots. Did all of our fresh btrfs installs have a /.snapshots? If yes, the assumption might be valid, except for bug#1048338. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1133660] New: Balance operation renders BTRFS unmountable
by bugzilla_noreply＠novell.com 17 Feb '20

17 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1133660 Bug ID: 1133660 Summary: Balance operation renders BTRFS unmountable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Yesterday my root filesystem became 100% full, after deleting multiple gigabytes of files "df" still reported 100% disk usage. I ran in this situation already a year ago and remembered that a btrfs balance operation will help. Like last year also btrfs balance was unable to start because no free space. So I followed the general advice and added a temporary device to my btrfs filesystem to make balance work. After adding another device, btrfs had free space and balance started. I expected the balance operation to finish soon such that I could remove the temporary device again. But after a few minutes I noticed that all IO on my workstaion blocked and btrfs hint an assertion. Please see attached photo crash_while_balance.jpg. At this point I was unable to cancel balance because the kernel oops returned to userspace with a lock held. So I rebooted the machine. But after the reboot btrfs hit a BUG() statement while mounting subvolumes. Please see photo crash_after_reboot.jpg. Side note: The temporary device was still present and btrfs found it. Next step was booting from an OpenSUSE LEAP 15.0 netinstall into recovery mode. To my surprise the recovery system mounted btrfs without any problem and I was able to read all files from all subvolumes. I double checked, the most recent LEAP 15.0 kernel still hit the BUG() as shown on crash_after_reboot.jpg. Again in the recovery system I canceled the balance operation, removed the temprary device, took a backup of all files and rebooted to my regular system. At this point it was again able to mount all btrfs subvolumes but after a few minutes it hit again the assertion as shown on crash_while_balance.jpg. There seems to be a problem with the recent kernel and btrfs balance. Is my filesystem now corrupted and I need to reinstal or is this "just" a runtime problem of btrfs? -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1100506] New: some searches routinely timeout or otherwise fail to return a result page
by bugzilla_noreply＠novell.com 16 Feb '20

16 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1100506 Bug ID: 1100506 Summary: some searches routinely timeout or otherwise fail to return a result page Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- The following is a typical result: "Secure Connection Failed The document contains no data. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem." Example failing searches: https://bugzilla.opensuse.org/query.cgi?chfieldfrom=3y&chfieldto=Now&column… https://bugzilla.opensuse.org/query.cgi?no_redirect=1&query_format=advanced… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1132953] New: Can not eject media, the button is overwritten
by bugzilla_noreply＠novell.com 14 Feb '20

14 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132953 Bug ID: 1132953 Summary: Can not eject media, the button is overwritten Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 803305 --> http://bugzilla.opensuse.org/attachment.cgi?id=803305&action=edit Photo of problem See attached photo -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1132255] New: Xfce panel doesn’t hide
by bugzilla_noreply＠novell.com 14 Feb '20

14 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132255 Bug ID: 1132255 Summary: Xfce panel doesn’t hide Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: ivo.grimaldi(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- xfce panel setting as intelligently or hide always, doesn't hide and a full screen window goes down the panel. 1. Right click on panel and select properties 2. set up intelligently or hide always 3. save and close 4. open full screen a program 5. see window goes down the panel, and panel doesn't hide a possible solution open a terminal sudo killall xfce4-panel xfce4-panel & or xfce4-panel -r -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1135127] New: Error with xfce4-display-settings
by bugzilla_noreply＠novell.com 14 Feb '20

14 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135127 Bug ID: 1135127 Summary: Error with xfce4-display-settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Macintosh OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: andres(a)otondo.cl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I just installed OpenSuse Tumbleweed, and when I try to open the xfce4-display-settings it show this error No protocol specified (xfce4-display-settings:5262): xfce4-display-settings-CRITICAL **: 21:50:37.044: xfce_randr_mode_width: assertion 'mode != NULL' failed (xfce4-display-settings:5262): xfce4-display-settings-CRITICAL **: 21:50:37.044: xfce_randr_mode_height: assertion 'mode != NULL' failed Segmentation fault (core dumped). My hardware is a Macbook Pro mid 2012 with an LG external screen connected trough VGA. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1084015] New: Include fixes from en_US "translation" to sources
by bugzilla_noreply＠novell.com 13 Feb '20

13 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1084015 Bug ID: 1084015 Summary: Include fixes from en_US "translation" to sources 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: sbrabec(a)suse.com QA Contact: jsrain(a)suse.com CC: locilka(a)suse.com, padraig.dillon(a)microfocus.com Found By: --- Blocker: --- Created attachment 762751 --> http://bugzilla.opensuse.org/attachment.cgi?id=762751&action=edit problems in en_US In past, strings were fixed in RC phase by introduction of and en_US translation. It was expected, that it will be incorporated back to the code after release. Years passed, and it did not happen. Some of these hotfixes are 16 years old. Now we have a bunch of strange en_US "translations" that needs to be reviewed and included. It consist of: 1. English typo and stylistic fixes. These should be included, and existing translations to other languages updated to keep them. Example: https://github.com/yast/yast-autoinstallation/blob/f93f318b744c21557201c278… en_US changed "Frametitle" to "Frame Title". All existing translations are probably OK. To keep existing translations, it requires coordinated merge of these changes and translation updates. 2. Formatting fixes. The good: English is OK. The bad: All translators translated the source string, not the fixed en_US string. With a bit of luck, it is possible to mass fix translations. Example: https://github.com/yast/yast-add-on/blob/0c44e966702b0aefc2439eb0da384260a4… en_US removed the trailing "\n" All translations have incorrect formatting. 3. Formatting fixes that change meaning of the string. The good: English is OK. The bad: All translators translated the source string with the incorrect meaning, not the fixed en_US string. Example: https://github.com/yast/yast-apparmor/blob/afd62f82724f750d7af850f60f6d52a2… en_US made a question from the sentence. All translators translated the source string, not the fixed en_US string. Impact on the translation meaning is unknown. 4. Hot fixes of apparent nonsense. All translators translated the source string, not the fixed en_US string. With a bit of luck, it is possible to mass fix translations. Example: https://github.com/yast/yast-apparmor/blob/afd62f82724f750d7af850f60f6d52a2… en_US removed the nonsense "? " at the beginning. Translators were not aware that "? " is a mistake, and used it in the translations. And finally, en_GB mixes all the above plus: 5. Changes for British English. As nobody actively maintains en_GB, it causes very strange result: I an few strings, AppArmor is called AppArmour, in all other "untranslated" strings, AppArmor is the name. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1117074] New: aws-cli missing autocompletion after install
by bugzilla_noreply＠novell.com 10 Feb '20

10 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117074 Bug ID: 1117074 Summary: aws-cli missing autocompletion after install Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- aws-cli package contains scripts for autocompletion, but install these scripts is missing. I need to set them manually. It looks like bug, git has autocompletion right after package install. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 966255] New: System does not boot
by bugzilla_noreply＠novell.com 09 Feb '20

09 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Bug ID: 966255 Summary: System does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: rjschwei(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- kernel 4.4.0.3 Has encrypted user partition. Hangs at Ignoring BGRT: Invalid version 0 (expected 1) This appears to happen right before the point where I would expect to enter my passphrase. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1107525] New: Raise default file descriptor limits to meet Valve Proton requirements
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1107525 Bug ID: 1107525 Summary: Raise default file descriptor limits to meet Valve Proton requirements Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Valve released beta version of Proton / Steam play. Next Leap 15.1 should meet minimal requirements. One of them is file descriptor limits: https://github.com/zfigura/wine/blob/esync/README.esync "If you get something like "eventfd: Too many open files" and then things start crashing, you've probably run out of file descriptors. esync creates one eventfd descriptor for each synchronization object, and some games may use a large number of these. Linux by default limits a process to 4096 file descriptors, which probably was reasonable back in the nineties but isn't really anymore. (Fortunately Debian and derivatives [Ubuntu, Mint] already have a reasonable limit.)" -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1110722] New: pocl uses compile-time CPU detection
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1110722 Bug ID: 1110722 Summary: pocl uses compile-time CPU detection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: osukup(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com Blocks: 1100677 Found By: Development Blocker: --- Steps to Reproduce: osc co Factory/pocl && cd $_ osc build --no-service --vm-type=kvm --build-opt=--vm-custom-opt="-cpu qemu64" +compare result to one without build-opt using /usr/lib/build/pkg-diff.sh $rpm1 $rpm2 Was previously solved with https://build.opensuse.org/request/show/626138 /usr/lib64/libpocl.so.2.2.0 differs in assembler output --- /tmp/tmp.3iZr1DZRz5/tmp.MomrQD5u2D 2018-09-26 04:41:09.682694138 +0000 +++ /tmp/tmp.3iZr1DZRz5/tmp.3XC0iGKeQV 2018-09-26 04:41:09.750694493 +0000 @@ -93827,10 +93827,10 @@ lea offset(%rsp),%rdi lea offset(%rsp),%rsi callq <_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_assignERKS4_@plt> - mov %r12,%rax - sub offset(%rsp),%rax - cmp $something,%rax - jbe <_ZL14kernel_libraryP13_cl_device_id + ofs> + mov offset(%rsp),%rax + or $something,%rax + cmp %r12,%rax + je <_ZL14kernel_libraryP13_cl_device_id + ofs> lea offset(%rip),%rsi # <supported_image_formats + ofs> In the build-root I can see: /home/abuild/rpmbuild/BUILD/pocl-1.2/build/CMakeCache.txt 2033-10-28 17:46:42.015636815 +0000 @@ -411,7 +411,7 @@ LINK_COMMAND:FILEPATH=/usr/bin/ld //The Host CPU to use with llc -LLC_HOST_CPU:STRING=haswell +LLC_HOST_CPU:STRING=pentium2 //LLVM assembler LLVM_AS:FILEPATH=/usr/bin/llvm-as @@ -837,7 +837,7 @@ Hwloc_hwloc_PREFIX:INTERNAL= Hwloc_hwloc_VERSION:INTERNAL= //Autodetected CPU -LLC_HOST_CPU_AUTO:INTERNAL=haswell +LLC_HOST_CPU_AUTO:INTERNAL=pentium2 might be an upstream pocl bug, where the result of CPU detection accidentally gets used during build -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1068707] New: bcache broken on s390x
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1068707 Bug ID: 1068707 Summary: bcache broken on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- trying to repeat on s390x what worked on aarch64 ... OBS_WORKER_DISK=/dev/mapper/3600a098051764b2d515d436d66416b4f wipefs -f -a $OBS_WORKER_DISK modprobe zram num_devices=1 modprobe bcache echo 8G > /sys/block/zram0/disksize wipefs -f -a /dev/zram0 make-bcache --wipe-bcache --block 4k --bucket 2M -B $OBS_WORKER_DISK -C /dev/zram0 # up to here it seemed to work, but: echo /dev/zram0 > /sys/fs/bcache/register -bash: echo: write error: Invalid argument in dmesg: [1256250.924470] zram: Added device: zram0 [1256258.363017] zram0: detected capacity change from 0 to 8589934592 [1256269.146000] bcache: register_bcache() error opening /dev/dm-2: Not a bcache superblock [1256275.462897] bcache: register_bcache() error opening /dev/zram0: Not a bcache superblock so the written superblock is not recognized ... endianess issue ? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1105173] New: cmis-client - Fails to build with Boost 1.68.0
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1105173 Bug ID: 1105173 Summary: cmis-client - Fails to build with Boost 1.68.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: cbosdonnat(a)suse.com Blocks: 1105081 Found By: --- Blocker: --- New Boost library has been released and unfortunately this package fails to build with it. The new boost library is soon submitted to devel:libraries:c_c++/boost and will be submitted to openSUSE:Factory shortly. https://build.opensuse.org/package/show/home:adamm:boost_test/cmis-client [ 163s] xml-utils.cxx:34:10: fatal error: boost/uuid/sha1.hpp: No such file or directory [ 163s] #include <boost/uuid/sha1.hpp> [ 163s] ^~~~~~~~~~~~~~~~~~~~~ [ 163s] compilation terminated. This is caused by removal of compatibility SHA1 header from Uuid boost library. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1120637] New: No controls for REMOTE_IPADDR= field in YaST2 VLAN settings
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1120637 Bug ID: 1120637 Summary: No controls for REMOTE_IPADDR= field in YaST2 VLAN settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hello! 've a test VLAN0, created via YaST2 standard wizard interface. Result config: ===== k_mikhail@linux-mk500:~> cat /etc/sysconfig/network/ifcfg-vlan0 BOOTPROTO='static' BROADCAST='' ETHERDEVICE='eth0' ETHTOOL_OPTIONS='' IPADDR='192.168.70.222/24' MTU='' NAME='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' VLAN_ID='0' ====== The question is about REMOTE_IPADDR='' field: it is present in final config, but cannot be defined in YaST2 GUI. Steps-to-reproduce: 1. Open YaST2 via X11 or terminal. 2. Add a VLAN interface via YaST2. 3. Check 'cat /etc/sysconfig/network/ifcfg-vlan0' output after 2. is finished. Possible solution: 1. Have specific filed in YaST2 GUI for that to have possibility to add such address. 2. Keep REMOTE_IPADDR='' as is in case of leaving this field empty in YaST2 settings. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1135761] New: network:libisds fails to build due to curl forcing libopenssl to write to a dead socket
by bugzilla_noreply＠novell.com 06 Feb '20

06 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1135761 Bug ID: 1135761 Summary: network:libisds fails to build due to curl forcing libopenssl to write to a dead socket Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: tchvatal(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: pmonrealgonzalez(a)suse.com, vcizek(a)suse.com Found By: --- Blocker: --- network:libisds does not build as the build dies while running make check: > FAIL: certificate_user_password_authentication > ============================================== > > Disabling server identity verification. That was your decision. > Connection accepted > TLS handshake failed: Certificate is required. > Disabling server identity verification. That was your decision. > Connection accepted > Client sent certificate: subject `C=CZ,CN=The Server', issuer `C=CZ,CN=The Authority', serial 0x55eb09ea03dc5d51, RSA key 2048 bits, signed using RSA-SHA256, activated `2015-09-05 15:27:39 UTC', expires `2065-08-23 15:27:43 UTC', pin-sha256="93S4S1wHWCn7JAHy0aOEGwkdFMhK2/A4QepU5TkZlz0=" > Client's certificate is valid. > Client is not authorized: Client's distinguished name `CN=The Server,C=CZ' does not match required name `CN=The Client,C=CZ'. > TLS handshake failed: Error in the certificate. It only silently dies. This happens only inside KVM (i.e. on OBS). Running the test under gdb reveals that the process receives SIGPIPE: > Program received signal SIGPIPE, Broken pipe. > #0 0x00007ffff7b9b734 in __GI___libc_write (fd=4, buf=buf@entry=0x5555555e3f73, nbytes=nbytes@entry=24) at ../sysdeps/unix/sysv/linux/write.c:26 > #1 0x00007ffff77c1895 in sock_write (b=0x5555555d6d90, in=0x5555555e3f73 "\027\003\003", inl=24) at crypto/bio/bss_sock.c:114 > #2 0x00007ffff77bcbba in bwrite_conv (bio=<optimized out>, data=<optimized out>, datal=<optimized out>, written=0x7fffffffcc10) at crypto/bio/bio_meth.c:77 > #3 0x00007ffff77bbc13 in bio_write_intern (written=0x7fffffffcc10, dlen=24, data=0x5555555e3f73, b=0x5555555d6d90) at crypto/bio/bio_lib.c:343 > #4 bio_write_intern (b=0x5555555d6d90, data=0x5555555e3f73, dlen=24, written=0x7fffffffcc10) at crypto/bio/bio_lib.c:320 > #5 0x00007ffff77bc0b3 in BIO_write (b=<optimized out>, data=<optimized out>, dlen=<optimized out>) at crypto/bio/bio_lib.c:363 > #6 0x00007ffff704aff7 in ssl3_write_pending (s=s@entry=0x5555555da9c0, type=type@entry=21, buf=buf@entry=0x5555555d9140 "\001", len=len@entry=2, written=written@entry=0x7fffffffdd80) at ssl/record/rec_layer_s3.c:1146 > #7 0x00007ffff704bf41 in do_ssl3_write (s=s@entry=0x5555555da9c0, type=type@entry=21, buf=0x5555555d9140 "\001", pipelens=pipelens@entry=0x7fffffffdd78, numpipes=numpipes@entry=1, create_empty_fragment=create_empty_fragment@entry=0, written=0x7fffffffdd80) at ssl/record/rec_layer_s3.c:1107 > #8 0x00007ffff70559a9 in ssl3_dispatch_alert (s=0x5555555da9c0) at ssl/s3_msg.c:78 > #9 0x00007ffff7053ab5 in ssl3_shutdown (s=0x5555555da9c0) at ssl/s3_lib.c:4418 > #10 0x00007ffff705ebdf in SSL_shutdown (s=0x5555555da9c0) at ssl/ssl_lib.c:2074 > #11 0x00007ffff7a857e5 in ossl_close (connssl=<optimized out>) at vtls/openssl.c:1256 > #12 0x00007ffff7a85851 in Curl_ossl_close (conn=0x5555555d02e0, sockindex=<optimized out>) at vtls/openssl.c:1273 > #13 0x00007ffff7a3ea8e in conn_shutdown (conn=0x5555555d02e0) at url.c:684 > #14 Curl_disconnect (data=0x5555555b63d0, dead_connection=true, conn=0x5555555d02e0) at url.c:822 > #15 Curl_disconnect (data=data@entry=0x5555555b63d0, conn=conn@entry=0x5555555d02e0, dead_connection=dead_connection@entry=true) at url.c:778 > #16 0x00007ffff7a533ff in multi_done (data=data@entry=0x5555555b63d0, status=status@entry=CURLE_RECV_ERROR, premature=<optimized out>, premature@entry=true) at multi.c:627 > #17 0x00007ffff7a5496c in multi_runsingle (multi=multi@entry=0x5555555ae920, now=..., data=data@entry=0x5555555b63d0) at multi.c:1917 > #18 0x00007ffff7a55059 in curl_multi_perform (multi=multi@entry=0x5555555ae920, running_handles=running_handles@entry=0x7fffffffe184) at multi.c:2138 > #19 0x00007ffff7a4bcea in easy_transfer (multi=0x5555555ae920) at easy.c:625 > #20 easy_perform (events=false, data=0x5555555b63d0) at easy.c:719 > #21 curl_easy_perform (data=0x5555555b63d0) at easy.c:738 > #22 0x00007ffff7fbbb87 in http (context=context@entry=0x5555555ab7e0, url=url@entry=0x5555555af270 "https://127.0.0.1:34893/certds/DS/dz", use_get=use_get@entry=false, request=0x5555555b7af0, request_length=179, response=response@entry=0x7fffffffe390, response_length=0x7fffffffe398, mime_type=0x7fffffffe380, http_code=0x7fffffffe388, response_otp_headers=0x0, charset=0x0) at soap.c:912 > #23 0x00007ffff7fbc767 in http (use_get=false, charset=0x0, response_otp_headers=<optimized out>, http_code=0x7fffffffe388, mime_type=0x7fffffffe380, response_length=0x7fffffffe398, response=0x7fffffffe390, request_length=<optimized out>, request=<optimized out>, url=0x5555555af270 "https://127.0.0.1:34893/certds/DS/dz", context=0x5555555ab7e0) at soap.c:578 > #24 _isds_soap (context=context@entry=0x5555555ab7e0, file=file@entry=0x7ffff7fbefc2 "DS/dz", request=request@entry=0x5555555afa80, response_document=response_document@entry=0x0, response_node_list=response_node_list@entry=0x0, raw_response=raw_response@entry=0x0, raw_response_length=0x0) at soap.c:1226 > #25 0x00007ffff7fa5956 in isds_login (context=0x5555555ab7e0, url=0x5555555ac0f0 "https://127.0.0.1:34893/", username=0x555555560088 "douglas", password=0x555555560090 "42", pki_credentials=0x7fffffffe520, otp=<optimized out>) at isds.c:1459 > #26 0x00005555555580d2 in test_login (error=IE_SECURITY, context=0x5555555ab7e0, url=<optimized out>, username=<optimized out>, password=<optimized out>, pki_credentials=<optimized out>, otp=0x0) at certificate_user_password_authentication.c:37 > #27 0x0000555555557aa7 in main () at certificate_user_password_authentication.c:127 I.e. openssl tried to write to a dead socket (from lsof): > certifica 8963 abuild 4u sock 0,9 0t0 31810 protocol: TCP To me, it seems that curl should not invoke openssl when the socket is dead already. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1124078] New: [doc]
by bugzilla_noreply＠novell.com 04 Feb '20

04 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1124078 Bug ID: 1124078 Summary: [doc] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: matwey.kornilov(a)gmail.com QA Contact: fs(a)suse.com Found By: --- Blocker: --- 6.3.3 Combining the linuxrc <code class="filename">info</code> file with the AutoYaST control file https://doc.opensuse.org/projects/autoyast/#invoking_autoinst.linuxrc Hello, I've found that correct setup should be "autoyast: file:///download/info" instead of "autoyast: file:///info" for Leap 15.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1132102] New: VirtualBox 6.0.4 guest addition ISO download failed
by bugzilla_noreply＠novell.com 02 Feb '20

02 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132102 Bug ID: 1132102 Summary: VirtualBox 6.0.4 guest addition ISO download failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: i(a)guoyunhe.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to reporduce: 1. Start a VM. 2. Menu "Devices > Install Guest Additions". 3. In modal, click download button. Result: Download encounter a network error. But download https://download.virtualbox.org/virtualbox/6.0.4/VBoxGuestAdditions_6.0.4.i… in web browser will succeed. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1106831] New: kernel crash when unloading bugdet_ci module
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1106831 Bug ID: 1106831 Summary: kernel crash when unloading bugdet_ci module Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 781630 --> http://bugzilla.opensuse.org/attachment.cgi?id=781630&action=edit journal excerpt After updating from openSUSE Leap 42.3 to 15.0 the system always crashes when unloading the budget_ci dvb module - see attachement. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1052140] New: NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab with option "noauto"
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1052140 Bug ID: 1052140 Summary: NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab with option "noauto" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab, which have set option "noauto". In my environment this is a good thing, but it is not the expected behaviour. Perhaps we could have a new fstab option like "x-nm.mount" for nfs shares to explicitly control this behaviour? The reason for experimenting with fstab options for nfs shares is the really strange "cooperation" of systemd and NetworkManager. Having the "auto" option set and nfs.service is active, systemd tries to mount the shares on boot, before network is available. This gives lots of errors in the log, although NetworkManager succeeds in mounting the share, when running the dispatcher script. With "auto" in fstab and a deactivated nfs.service neither systemd nor NetworkManager are trying to mount nfs shares. With "noauto" in fstab and an activated nfs.service systemd ignores the shares, but NetworkManager's nfs dispatcher is mounting them nevertheless. I tried x-systemd.automount, too. This worked generally, but after a hibernate/resume cycle all nfs shares were inaccessible. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1077870] New: librsvg-2-2-2.42.0-1.1.i586 contains SSE2 instructions
by bugzilla_noreply＠novell.com 30 Jan '20

30 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1077870 Bug ID: 1077870 Summary: librsvg-2-2-2.42.0-1.1.i586 contains SSE2 instructions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: jan.kiszka(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since that revision, the library will crash on old i686 machines (Athlon XP) with illegal opcode because it tries to use SSE2. Regression over 2.40.20-1.1. Currently running 2.40.18-1.3 again because that's the only one I found in some archive. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1069396] New: sddm cannot be updated
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1069396 Bug ID: 1069396 Summary: sddm cannot be updated Classification: openSUSE Product: openSUSE Backports Version: SLE-12-SP3 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: kukuk(a)suse.com QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- If you try to update to the latest sddm version: Problem: nothing provides sddm-theme-openSUSE needed by sddm-branding-openSUSE-0.14.0-2.1.x86_64 Solution 1: deinstallation of sddm-branding-SLE-0.13.0-5.1.x86_64 Solution 2: do not install sddm-0.14.0-2.1.x86_64 Solution 3: break sddm-branding-openSUSE-0.14.0-2.1.x86_64 by ignoring some of its dependencies Reproduceable on SLES12 SP2 and SLES12 SP3. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1094785] New: Firefox - Bug when windows is normal (Resize bug).
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094785 Bug ID: 1094785 Summary: Firefox - Bug when windows is normal (Resize bug). Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 771478 --> http://bugzilla.opensuse.org/attachment.cgi?id=771478&action=edit Video showing bug. Hello, after a fresh install of openSUSE Leap 15.0, i proceed to customize Firefox browser and found this bug: When i unchecked the Title bar option and i try to resize, is impossible to resize the windows and too the windows shrink, attached a video for easy perception of the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1100108] New: scroll bar not adaptable
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1100108 Bug ID: 1100108 Summary: scroll bar not adaptable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Keywords: Usability Severity: Normal 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: --- In two applications I have a problem with a scroll bar. One is in kmail on my laptop and the other in lokalize on both my desktop and laptop. First I will describe what is wrong on my desktop in lokalize. In the project view there is a table with headings like Name, Graphics, Total etc. The last one is "Last Translator" At the bottom of that window is a scroll bar. This scroll bar shows a very large scroll bar (see Screenshot_1). When moving the blue part of the scroll bar completely to the right, the bar with the headings shows the endpoint the heading "Last Translator". With the mouse one should be able to move that endpoint to the left to shorten the size of the column. This column is very large and I am unable to make the size of the column smaller. This is the problem. I have the same problem in kmail in the sub window with the accounts. Clicking with right on the heading gives me the option to enable extra columns Unread, Total, and Size. On my laptop if I enable Total, the column size of Total becomes very large. See Screenshot_2 with Total and Size enabled and the scroll bar at the bottom of that sub window moved completely to the right. I should be able to shorten the column size of Total. I am unable to resize the column width. I have the same problem with lokalize on my laptop (see Screenshot_3). -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1087277] New: Upgrade from Leap 42.3 to 15.0 Beta gives segmentation fault when trying to start KDE session
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1087277 Bug ID: 1087277 Summary: Upgrade from Leap 42.3 to 15.0 Beta gives segmentation fault when trying to start KDE session Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 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 765230 --> http://bugzilla.opensuse.org/attachment.cgi?id=765230&action=edit ksmserver.kcrash.txt First I describe the test setup, second the results. I have two spare ext4 partitions on my multi boot system with Leap 42.3, Tumbleweed and a newly installed Leap 15.0 Beta. I copied the home and system partition of 42.3 to the two spare partitions, each with a new label. The spare partitions are newly formatted with ext4 and both got a new unique label. I copied, using "rsync -a .." the root and home partition of the existing 42.3 to these new partitions. On the new system partition I changed in /etc/fstab the labels for / and /home to the new assigned labels. All partitions are mounted by label in /etc/fstab. I booted the latest image of Leap 15.0 Beta from a USB disk and performed an upgrade on the new partition with the copied 42.3 system. The old 42.3 system is still intact. The 42.3 system also has repository Education, KDE:Extra and Packman, so I had to resolve some conflicts and delete unavailable packages. But all in all I ended with an upgraded 42.3 to 15.0 Beta. However the bootloader showed some problems. Error message about /boot/grub2/device.map, which contained twice hd0. After the reboot only the old 42.3 system was bootable, the other three were not, although mentioned in the GRUB menu. I inspected /boot/grub2/ device.map and removed double entries, not only hd0, but also hd3, I used yast->bootloader to generate a new grub. I was able to boot all 4 systems. The upgraded 42.3 to 15.0 system showed a login screen and I entered the password. However after that, two application showed a segmentation fault, kdmserver and akonadictl. I was unable to use drkonqi to make a traceback, but some information about a traceback could be saved (see attachement). Apparently some information on the home partition causes this. The solution I found was to delete /home/<user>/.cache, after which I was able to login. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1082023] New: git send-email fails to authenticate with SMTP server
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1082023 Bug ID: 1082023 Summary: git send-email fails to authenticate with SMTP server Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With current Tumbleweed git send-email fails to authenticate with the SMTP server. This used to work. since I rarly use git send-email I cant say when it started. The username/password combination works with mutt. Send this email? ([y]es|[n]o|[q]uit|[a]ll): y Net::SMTP>>> Net::SMTP(3.10) Net::SMTP>>> Net::Cmd(3.10) Net::SMTP>>> Exporter(5.72) Net::SMTP>>> IO::Socket::IP(0.38) Net::SMTP>>> IO::Socket(1.38) Net::SMTP>>> IO::Handle(1.36) Net::SMTP=GLOB(0x55b5df986d00)<<< 220 smtp.strato.de ESMTP RZmta (P7 -) Net::SMTP=GLOB(0x55b5df986d00)>>> EHLO sender Net::SMTP=GLOB(0x55b5df986d00)<<< 250-smtp.strato.de greets 2001:a62:816:91ff:a572:884d:f51d:1a86 Net::SMTP=GLOB(0x55b5df986d00)<<< 250-ENHANCEDSTATUSCODES Net::SMTP=GLOB(0x55b5df986d00)<<< 250-PIPELINING Net::SMTP=GLOB(0x55b5df986d00)<<< 250-8BITMIME Net::SMTP=GLOB(0x55b5df986d00)<<< 250-DELIVERBY Net::SMTP=GLOB(0x55b5df986d00)<<< 250-SIZE 104857600 Net::SMTP=GLOB(0x55b5df986d00)<<< 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN Net::SMTP=GLOB(0x55b5df986d00)<<< 250-STARTTLS Net::SMTP=GLOB(0x55b5df986d00)<<< 250-BURL imap Net::SMTP=GLOB(0x55b5df986d00)<<< 250-CHUNKING Net::SMTP=GLOB(0x55b5df986d00)<<< 250 HELP Net::SMTP=GLOB(0x55b5df986d00)>>> STARTTLS Net::SMTP=GLOB(0x55b5df986d00)<<< 220 Ready to start TLS Net::SMTP::_SSL=GLOB(0x55b5df986d00)>>> EHLO sender Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-smtp.strato.de greets 2001:a62:816:91ff:a572:884d:f51d:1a86 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-ENHANCEDSTATUSCODES Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-PIPELINING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-8BITMIME Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-DELIVERBY Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-SIZE 104857600 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-BURL imap Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-CHUNKING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250 HELP Net::SMTP::_SSL=GLOB(0x55b5df986d00)>>> EHLO sender Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-smtp.strato.de greets 2001:a62:816:91ff:a572:884d:f51d:1a86 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-ENHANCEDSTATUSCODES Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-PIPELINING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-8BITMIME Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-DELIVERBY Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-SIZE 104857600 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-BURL imap Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-CHUNKING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250 HELP Net::SMTP::_SSL=GLOB(0x55b5df986d00)>>> AUTH DIGEST-MD5 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1136307] New: laptop now longer powers fully down on shutdown or even does a reboot
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1136307 Bug ID: 1136307 Summary: laptop now longer powers fully down on shutdown or even does a reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: alexvkaam(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hi HP Notebook - 17-ca0710nd https://support.hp.com/us-en/drivers/selfservice/hp-17-ca0000-laptop-pc/203… under Leap 15.0 the laptop worked mostly fine except for a slow power drain issue (bug 1109374) Updated the laptop to 15.1 and as from that moment the shutdown (KDE) no longer shuts the laptop fully down, the Plymouth shutdown appears and if I press ESC it goes through just fine, screen is powered down so as far as I can tell it shutsdown normal on the linux side and does not hang. BUT the laptop fan keeps running and the caps-lock light blinks (on/off per second). Only way to stop it now is to hold down power for 5sec Tried a reboot and it gives the exact same effect as the powerdown ?! Waited for an hour, just kept in that state. booted up and retried a few times, same effect. shutdown now, same effect booted up a windows on usb, it had no issues with the shutdown checked HP for bios updates and installed the latest one F24 (was on F11) redid all the above steps, same effect. System is fully up to date with 15.1 now sure what info you need Regards, Alex -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1130395] New: Valgrind fails to build on armv6 and armv7
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1130395 Bug ID: 1130395 Summary: Valgrind fails to build on armv6 and armv7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build logs: * armv6: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/valg… * armv7: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/valg… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1130536] New: missing crtab option - breaks boot time entry
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1130536 Bug ID: 1130536 Summary: missing crtab option - breaks boot time entry 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: mmeeks(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- For various reasons my /etc/cryptab contained: cr_home-storage /data/home-storage none none cr_ata-Samsung_SSD_860_EVO_M.2_1TB_S415NB0M118918N-part3 /dev/disk/by-id/ata-Samsung_SSD_860_EVO_M.2_1TB_S415NB0M118918N-part3 none none And fstab: fstab:/dev/mapper/cr_home-storage /crypt-home xfs loop,nofail 0 0 /dev/mapper/cr_ata-Samsung_SSD_860_EVO_M.2_1TB_S415NB0M118918N-part3 /newhome xfs nofail 0 2 The first lookback file there /data/home-storage is/was no longer there - I removed it. At boot-time I would get prompted for the password to unlock the /newhome partition - but before that completed - I would be thrown into X - which would fail to auto-log-me-in and crash (since home was not available via a symlink to /newhome ;-) That made for quite some unpleasantness. Would love the prompter to be more robust there, and to cope with a 2nd partition that needs unlocking in the presence of a first that is not there. Thanks ! =) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1094668] New: Firefox start failure ppc64le in TW
by bugzilla_noreply＠novell.com 27 Jan '20

27 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094668 Bug ID: 1094668 Summary: Firefox start failure ppc64le in TW Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC URL: https://openqa.opensuse.org/tests/682425/modules/firef ox/steps/4 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Firefox start failure ppc64le in TW the journalctl is reporting; === May 25 06:15:07 susetest kernel: firefox[15803]: unhandled signal 11 at 0000000000000000 nip 00000001260adfb8 lr 00000001260aef8c code 1 May 25 06:15:07 susetest systemd[1]: Started Process Core Dump (PID 15810/UID 0). May 25 06:15:07 susetest kernel: firefox[15809]: unhandled signal 11 at 0000000000000008 nip 00000001260ade18 lr 00000001260aef8c code 1 May 25 06:15:07 susetest systemd[1]: Started Process Core Dump (PID 15812/UID 0). May 25 06:15:07 susetest systemd-coredump[15813]: Process 15809 (firefox) of user 1000 dumped core. May 25 06:15:07 susetest systemd-coredump[15811]: Process 15803 (firefox) of user 1000 dumped core. May 25 06:21:15 susetest systemd[1]: Started Getty on tty5. === [Build 20180524] openQA test fails in firefox ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-system_performance@ppc64le fails in [firefox](https://openqa.opensuse.org/tests/682425/modules/firefox/steps/4) ## Reproducible Fails since (at least) Build [20180524](https://openqa.opensuse.org/tests/682425) (current job) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&flavor=DVD&te… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1094138] New: VUL-0: CVE-2018-11243: upx: PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service
by bugzilla_noreply＠novell.com 24 Jan '20

24 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094138 Bug ID: 1094138 Summary: VUL-0: CVE-2018-11243: upx: PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/206156/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: meissner(a)suse.com Reporter: vpereira(a)microfocus.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-11243 PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service (double free), limit the ability of a malware scanner to operate on the entire original data, or possibly have unspecified other impact via a crafted file. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-11243 http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-11243.html https://github.com/upx/upx/blob/devel/NEWS https://github.com/upx/upx/issues/206 https://github.com/upx/upx/issues/207 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1135723] New: Installation: Fstab Options window extended below screen bottom on 1280x800 screenS
by bugzilla_noreply＠novell.com 23 Jan '20

23 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135723 Bug ID: 1135723 Summary: Installation: Fstab Options window extended below screen bottom on 1280x800 screenS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 805561 --> http://bugzilla.opensuse.org/attachment.cgi?id=805561&action=edit screenshot of Fstab Options window during NET 15.1 installation Original Summary: Installation: Fstab Options window extended below screen bottom on 1280x800 screenS This was on a Sony Vaio VGN CR290 laptop, not my own. Screens were mirrored. Same window opened on first boot centered top to bottom of smaller screen, with expected resolutions: > xrandr Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 8192 x 8192 LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.00*+ 59.99 59.97 59.81 59.91 1280x720 60.00 59.99 59.86 59.74 1024x768 60.04 60.00... VGA-1 connected 1920x1200+1280+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1680x1050 59.95 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1280x800 59.81... SVIDEO-1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1133741] New: System freeze and kernel panic after starting supertux2 1~2 minutes (radeon)
by bugzilla_noreply＠novell.com 23 Jan '20

23 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1133741 Bug ID: 1133741 Summary: System freeze and kernel panic after starting supertux2 1~2 minutes (radeon) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: dawei.pang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Run supertux2 on gnome with wayland, the whole system freeze after 1~2 minutes. Try to connect the machine with serial console, enable kernel crash dump and set boot parameter 'ignore_loglevel crashkernel=256M console=ttyS0,115200 debug drm.debug=1 sysrq_always_enabled panic=10 pause_on_oops=5 loglevel=8', just got panic information as following and refer to attachment for crash dump. #inxi -GxxSM System: Host: linux-7fu1 Kernel: 4.12.14-lp151.24-default x86_64 bits: 64 gcc: 7.4.0 Console: tty 1 dm: gdm Distro: openSUSE Leap 15.1 Machine: Device: desktop System: Dell product: Precision Tower 5810 serial: HTS9SM2 Mobo: Dell model: 0HHV7N v: A00 serial: /HTS9SM2/CNFCW007BB00B0/ UEFI: Dell v: A29 date: 12/13/2018 Chassis: type: 7 serial: HTS9SM2 Graphics: Card: Advanced Micro Devices [AMD/ATI] Cape Verde GL [FirePro W4100] bus-ID: 03:00.0 chip-ID: 1002:682c Display Server: X.org 1.20.3 drivers: ati (unloaded: modesetting,fbdev,vesa,radeon) tty size: 180x32 Advanced Data: N/A for root # loginctl show-session c1 -p Type Type=wayland ===Panic information=== [ 1499.102545] [drm:si_irq_set [radeon]] si_irq_set: sw int dma [ 1520.821321] NMI watchdog: Watchdog detected hard LOCKUP on cpu 5 [ 1520.821322] Modules linked in: fuse af_packet msr xfs nls_iso8859_1 nls_cp437 vfat libcrc32c fat snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi intel_rapl sb_edac x86_pkg_temp_th ermal intel_powerclamp coretemp kvm_intel kvm dell_smbios irqbypass crc32_pclmul mxm_wmi dell_wmi_descriptor wmi_bmof ghash_clmulni_intel iTCO_wdt pcbc mei_wdt iTCO_vendor_support dcdbas snd_hda_intel dell_smm_h wmon snd_hda_codec snd_hda_core aesni_intel snd_hwdep aes_x86_64 snd_pcm crypto_simd glue_helper cryptd i2c_i801 pcspkr lpc_ich snd_timer e1000e snd mei_me ptp soundcore mei pps_core wmi button amdgpu chash gpu_ sched btrfs xor zstd_decompress zstd_compress xxhash sr_mod cdrom raid6_pq hid_generic usbhid radeon i2c_algo_bit drm_kms_helper syscopyarea ehci_pci xhci_pci sysfillrect sysimgblt [ 1520.821337] fb_sys_fops xhci_hcd ehci_hcd ttm crc32c_intel ahci usbcore libahci drm drm_panel_orientation_quirks sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 1520.821341] CPU: 5 PID: 72 Comm: kworker/5:1 Tainted: G L 4.12.14-lp151.24-default #1 openSUSE Leap 15.1 [ 1520.821341] Hardware name: Dell Inc. Precision Tower 5810/0HHV7N, BIOS A29 12/13/2018 [ 1520.821342] Workqueue: events_power_efficient radeon_fence_check_lockup [radeon] [ 1520.821342] task: ffff88041ed541c0 task.stack: ffffc90001b8c000 [ 1520.821343] RIP: 0010:native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821343] RSP: 0018:ffffc90001b8fdf0 EFLAGS: 00000002 [ 1520.821344] RAX: 0000000000000000 RBX: 0000000000000292 RCX: ffff88042fd64c40 [ 1520.821344] RDX: 0000000000180101 RSI: 0000000000000101 RDI: ffff880419475520 [ 1520.821344] RBP: 0000000000000000 R08: 0000000000180000 R09: 0000000000000000 [ 1520.821345] R10: 0000000000000000 R11: 0000000000001329 R12: ffff880419474f10 [ 1520.821345] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 1520.821345] FS: 0000000000000000(0000) GS:ffff88042fd40000(0000) knlGS:0000000000000000 [ 1520.821346] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1520.821346] CR2: 00007f699b51d000 CR3: 000000000200a001 CR4: 00000000001606e0 [ 1520.821347] Call Trace: [ 1520.821347] _raw_spin_lock_irqsave+0x32/0x40 [ 1520.821347] __wake_up_common_lock+0x53/0x90 [ 1520.821348] radeon_fence_check_lockup+0x12d/0x170 [radeon] [ 1520.821348] process_one_work+0x1da/0x400 [ 1520.821348] worker_thread+0x2b/0x3f0 [ 1520.821349] ? process_one_work+0x400/0x400 [ 1520.821349] kthread+0x113/0x130 [ 1520.821349] ? kthread_create_worker_on_cpu+0x50/0x50 [ 1520.821350] ret_from_fork+0x35/0x40 [ 1520.821350] Code: f3 90 8b 37 81 fe 00 01 00 00 74 f4 e9 60 ff ff ff 44 89 c0 c1 e8 10 66 87 47 02 89 c2 c1 e2 10 85 d2 75 61 45 31 c9 eb 02 f3 90 <8b> 17 66 85 d2 75 f7 be 01 00 00 00 eb 0c 89 d0 f0 0f b1 37 39 [ 1520.821360] Kernel panic - not syncing: Hard LOCKUP [ 1520.821361] CPU: 5 PID: 72 Comm: kworker/5:1 Tainted: G L 4.12.14-lp151.24-default #1 openSUSE Leap 15.1 [ 1520.821361] Hardware name: Dell Inc. Precision Tower 5810/0HHV7N, BIOS A29 12/13/2018 [ 1520.821361] Workqueue: events_power_efficient radeon_fence_check_lockup [radeon] [ 1520.821362] Call Trace: [ 1520.821362] <NMI> [ 1520.821362] dump_stack+0x5c/0x86 [ 1520.821363] panic+0xd5/0x233 [ 1520.821363] nmi_panic+0x35/0x40 [ 1520.821363] watchdog_overflow_callback+0xef/0x110 [ 1520.821364] __perf_event_overflow+0x52/0xe0 [ 1520.821364] intel_pmu_handle_irq+0x24c/0x4c0 [ 1520.821364] ? perf_event_nmi_handler+0x2d/0x50 [ 1520.821364] perf_event_nmi_handler+0x2d/0x50 [ 1520.821365] nmi_handle+0x63/0x110 [ 1520.821365] default_do_nmi+0x4e/0x100 [ 1520.821365] do_nmi+0xe5/0x140 [ 1520.821366] end_repeat_nmi+0x16/0x61 [ 1520.821366] RIP: 0010:native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821366] RSP: 0018:ffffc90001b8fdf0 EFLAGS: 00000002 [ 1520.821367] RAX: 0000000000000000 RBX: 0000000000000292 RCX: ffff88042fd64c40 [ 1520.821367] RDX: 0000000000180101 RSI: 0000000000000101 RDI: ffff880419475520 [ 1520.821368] RBP: 0000000000000000 R08: 0000000000180000 R09: 0000000000000000 [ 1520.821368] R10: 0000000000000000 R11: 0000000000001329 R12: ffff880419474f10 [ 1520.821368] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 1520.821369] ? native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821369] ? native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821369] </NMI> [ 1520.821369] _raw_spin_lock_irqsave+0x32/0x40 [ 1520.821370] __wake_up_common_lock+0x53/0x90 [ 1520.821370] radeon_fence_check_lockup+0x12d/0x170 [radeon] [ 1520.821370] process_one_work+0x1da/0x400 [ 1520.821371] worker_thread+0x2b/0x3f0 [ 1520.821371] ? process_one_work+0x400/0x400 [ 1520.821371] kthread+0x113/0x130 [ 1520.821372] ? kthread_create_worker_on_cpu+0x50/0x50 [ 1520.821372] ret_from_fork+0x35/0x40 ===GDB crash=== crash> bt PID: 72 TASK: ffff88041ed541c0 CPU: 5 COMMAND: "kworker/5:1" #0 [fffffe00000e5a68] machine_kexec at ffffffff8105f08f #1 [fffffe00000e5ab8] __crash_kexec at ffffffff8111e25e #2 [fffffe00000e5b70] panic at ffffffff811bb7d0 #3 [fffffe00000e5bf0] nmi_panic at ffffffff8108a895 #4 [fffffe00000e5bf8] watchdog_overflow_callback at ffffffff8114de5f #5 [fffffe00000e5c08] __perf_event_overflow at ffffffff811a90e2 #6 [fffffe00000e5c38] intel_pmu_handle_irq at ffffffff8100c03c #7 [fffffe00000e5e40] perf_event_nmi_handler at ffffffff8100560d #8 [fffffe00000e5e58] nmi_handle at ffffffff81030213 #9 [fffffe00000e5eb0] default_do_nmi at ffffffff8103068e #10 [fffffe00000e5ed0] do_nmi at ffffffff81030825 #11 [fffffe00000e5ef0] end_repeat_nmi at ffffffff81801ccd [exception RIP: native_queued_spin_lock_slowpath+233] RIP: ffffffff810d4b59 RSP: ffffc90001b8fdf0 RFLAGS: 00000002 RAX: 0000000000000000 RBX: 0000000000000292 RCX: ffff88042fd64c40 RDX: 0000000000180101 RSI: 0000000000000101 RDI: ffff880419475520 RBP: 0000000000000000 R8: 0000000000180000 R9: 0000000000000000 R10: 0000000000000000 R11: 0000000000001329 R12: ffff880419474f10 R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 --- <NMI exception stack> --- #12 [ffffc90001b8fdf0] native_queued_spin_lock_slowpath at ffffffff810d4b59 #13 [ffffc90001b8fdf0] _raw_spin_lock_irqsave at ffffffff817da862 #14 [ffffc90001b8fe00] __wake_up_common_lock at ffffffff810ca293 #15 [ffffc90001b8fe60] radeon_fence_check_lockup at ffffffffa03860ed [radeon] #16 [ffffc90001b8fe98] process_one_work at ffffffff810a39ba #17 [ffffc90001b8fed8] worker_thread at ffffffff810a3c0b #18 [ffffc90001b8ff10] kthread at ffffffff810aa3d3 #19 [ffffc90001b8ff50] ret_from_fork at ffffffff81800235 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1117230] New: Leap 15 Privoxy is not able to resolve addresses with plasma and/or falkon, even email
by bugzilla_noreply＠novell.com 21 Jan '20

21 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117230 Bug ID: 1117230 Summary: Leap 15 Privoxy is not able to resolve addresses with plasma and/or falkon, even email Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried already the workaround of Bug 1041606 however with no effect. Privoxy itself starts up. ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2018-11-25 11:04:41 CET; 33min ago Process: 2694 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, sta> Process: 2693 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exi> Process: 2692 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc> Main PID: 2695 (privoxy) Tasks: 1 (limit: 4915) CGroup: /system.slice/privoxy.service └─2695 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config nov 25 11:04:40 roadrunner.suse systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 25 11:04:41 roadrunner.suse systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities. The system runs on wlan1 but when trying to do the following setup for systemewide kde plasma: 127.0.0.1:8118 (which is the default setting for localhost and privoxy) no proxy for localhost or when setting e.g. falcon to manually use http 127.0.0.1:8118 The command sudo tcpdump -n -i lo port 8118 [sudo] password di root: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes Does not capture traffic. The browser however loads, the page is loaded correctly. When trying to open the status page the answer is: Privoxy is not being used So obviously the settings are not honored. sudo netstat -tulpn [sudo] password di root: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 2695/privoxy tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1502/cupsd tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1871/postgres tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2116/master tcp6 0 0 ::1:631 :::* LISTEN 1502/cupsd tcp6 0 0 ::1:5432 :::* LISTEN 1871/postgres tcp6 0 0 ::1:25 :::* LISTEN 2116/master udp 0 0 0.0.0.0:68 0.0.0.0:* 2545/dhclient udp 0 0 127.0.0.1:323 0.0.0.0:* 1518/chronyd udp6 0 0 ::1:323 :::* 1518/chronyd As you see it starts and does listen. But is not used? Funnily enough, yesterday I had as a side effect the impossibility to resolve IMAP mail when setting the Plasma System settings to privoxy? This resolved after setting no proxy in the plasma system settings. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1114811] New: cifs_mount failed w/return code = -101
by bugzilla_noreply＠novell.com 19 Jan '20

19 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1114811 Bug ID: 1114811 Summary: cifs_mount failed w/return code = -101 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: chris(a)computersalat.de QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- After upgrade from 42.3 to 15.0 my smb shares are not mounted anymore on boot. I am using the following entry in fstab: //samba.int.my.domain/daten /srv/samba/daten cifs credentials=/root/credsmb,uid=admin,file_mode=0644,gid=100 0 0 Im log sehe ich nur das: 2018-11-06T09:21:00.605281+01:00 lap kernel: [ 14.338205] CIFS VFS: Error connecting to socket. Aborting operation. 2018-11-06T09:21:00.605290+01:00 lap kernel: [ 14.338207] CIFS VFS: cifs_mount failed w/return code = -101 ... 2018-11-06T09:21:00.649764+01:00 lap systemd[1]: srv-samba-daten.mount: Mount process exited, code=exited status=32 2018-11-06T09:21:00.650281+01:00 lap systemd[1]: Failed to mount /srv/samba/daten. if I do a 'mount -a' on console after login all shares get successfully mounted. looks like a 'timing problem of systemd' ??? So what is the magic that changed form Leap 42.3 to Leap 15.0 ? -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1116020] New: Please convert SysV init scripts by mailgraph into native systemd services
by bugzilla_noreply＠novell.com 19 Jan '20

19 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1116020 Bug ID: 1116020 Summary: Please convert SysV init scripts by mailgraph 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.

1 14

[Bug 1117123] New: opencl not supported AMDGPU
by bugzilla_noreply＠novell.com 18 Jan '20

18 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117123 Bug ID: 1117123 Summary: opencl not supported AMDGPU Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: antonvdh(a)gmail.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- openCL, is not available through open-source driver (amdgpu) or proprietary (amdgpu-pro) contacted AMD disappointing answer. Need openCL for Blender 2.79b or 2.8 gpu rendering linux-uvp0:/home/anton/Downloads/amdgpu-pro-18.40-673869-sle-15 # ../amdgpu-pro-install Unsupported RedHat derivative OS Dear Anton, Your service request : SR #{ticketno:[8200842059]} has been reviewed and updated. Response and Service Request History: Thank you for the response. After discussing this internally, I see that driver support is available only for SLES/SLED 15 and might not support for OpenSuse 15. I request you to check with OpenSUSE community forum for assistance on this. Thank you for contacting AMD. In order to update this service request, please respond, leaving the service request reference intact. Best regards, Santosh AMD Global Customer Care -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1128320] New: YaST Partitioner: Don't suggest /run/... mount point for USB media
by bugzilla_noreply＠novell.com 17 Jan '20

17 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1128320 Bug ID: 1128320 Summary: YaST Partitioner: Don't suggest /run/... mount point for USB media Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: shundhammer(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When you start the YaST partitioner with USB media (USB stick, USB disk, SD card) attached and mounted by your desktop (KDE, GNOME, Xfce) and edit any partition on that USB device, by default it suggests to mount that device (since it's already mounted) with the current temporary mount point below /run/media. If you continue the workflow, you have to be very careful to unselect that "mount" radio button, otherwise you will end up with that device permanently added to /etc/fstab with that /run/media mount point. That mini-workflow should NOT preselect the "mount" radio button by default for any of those temporary mount points. It should at least explicitly exclude /run/media (or probably better yet /run completely) from that check. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1126512] New: kernel-default-4.20.10-2.1.g4c06520 obsoletes drm-kmp-default for an unrelated distribution
by bugzilla_noreply＠novell.com 17 Jan '20

17 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1126512 Bug ID: 1126512 Summary: kernel-default-4.20.10-2.1.g4c06520 obsoletes drm-kmp-default for an unrelated distribution Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to use a new kernel on Leap 42.3 results in a sort-of unusable system. Installing kernel-default-4.20.10-2.1.g4c06520 (and newer) results in removing drm-kmp-default, while - due to multiversion.kernels - the distribution's kernel is still installed, and should remain usable. However, all modules needed to run this distro on some almost recent hardware (Intel Kaby Lake) wrt/ graphics are contained in this particular drm-kmp-default package. There has been an indepth discussion on the mailing list starting at <https://lists.opensuse.org/opensuse-kernel/2019-02/msg00018.html> FWIW, I now build my own kernel in OBS with just this obsoletes line being deleted for kernel-default and everything works for me; however, I'd rate this a complete waste of resources... Please get rid of the line which actually is distribution related, not part of this Kernel:stable repo! -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1121032] New: VUL-1: CVE-2015-9275: arc: directory traversal
by bugzilla_noreply＠novell.com 16 Jan '20

16 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1121032 Bug ID: 1121032 Summary: VUL-1: CVE-2015-9275: arc: directory traversal Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://smash.suse.de/issue/222273/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: meissner(a)suse.com Reporter: kbabioch(a)suse.com QA Contact: security-team(a)suse.de CC: crrodriguez(a)opensuse.org, darin(a)darins.net, kukuk(a)suse.com, mpluskal(a)suse.com, mseben(a)gmail.com, pth(a)suse.com, werner(a)suse.com Found By: Security Response Team Blocker: --- ARC 5.21q allows directory traversal via a full pathname in an archive file. Debian patches: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774527#10 References: https://bugzilla.redhat.com/show_bug.cgi?id=1179142 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-9275 https://bugs.debian.org/774527 http://www.cvedetails.com/cve/CVE-2015-9275/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1094323] New: packages do not build reproducibly from pip install
by bugzilla_noreply＠novell.com 16 Jan '20

16 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094323 Bug ID: 1094323 Summary: packages do not build reproducibly from pip install Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ja+suse(a)matejcik.cz, toddrme2178(a)gmail.com Blocks: 1062303 Found By: Development Blocker: --- When working on reproducible builds for openSUSE I found that some packages use pip install which creates .pyc files that contain a random tmp path in them that is different for every build affects at least: python-cluster python-jupyter_bqplot python-jupyter_imatlab_kernel python-PsyLab python-sphinxcontrib-github-alt here is an example diff: /usr/lib/python3.6/site-packages/cluster/method/__pycache__/kmeans.cpython-36.pyc @@ -110,7 +110,7 @@ 000006d0 00 5a 0e 63 6f 6e 74 72 6f 6c 5f 6c 65 6e 67 74 |.Z.control_lengt| 000006e0 68 da 04 69 74 65 6d a9 00 72 13 00 00 00 fa 3a |h..item..r.....:| 000006f0 2f 74 6d 70 2f 70 69 70 2d 69 6e 73 74 61 6c 6c |/tmp/pip-install| -00000700 2d 32 75 38 6a 6f 79 74 76 2f 63 6c 75 73 74 65 |-2u8joytv/cluste| +00000700 2d 6e 69 6c 34 6b 39 77 73 2f 63 6c 75 73 74 65 |-nil4k9ws/cluste| 00000710 72 2f 63 6c 75 73 74 65 72 2f 6d 65 74 68 6f 64 |r/cluster/method| 00000720 2f 6b 6d 65 61 6e 73 2e 70 79 da 08 5f 5f 69 6e |/kmeans.py..__in| 00000730 69 74 5f 5f 2e 00 00 00 73 20 00 00 00 00 01 06 |it__....s ......| IMHO, those .pyc files should not contain any tmp path because it does not exist in the target system anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1132659] New: NetworkManager-applet: no context menu when using systray instead of indicator
by bugzilla_noreply＠novell.com 15 Jan '20

15 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132659 Bug ID: 1132659 Summary: NetworkManager-applet: no context menu when using systray instead of indicator Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: maurizio.galli(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: seife(a)novell.slipkontur.de, tiwai(a)suse.com Found By: --- Blocker: --- starting nm-applet --indicator in Xfce only works if xfce4-statusnotifier-plugin (which supports indicators) is in the panel. OTOH if only the older systray is being used, nm-applet does not properly fall back: icon is visible but context menu does not work making it unusable. xfce4-statusnotifier-plugin is part of the newer default Xfce installation in openSUSE however some users still rely on the older systray only. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1127618] New: midori always crashes
by bugzilla_noreply＠novell.com 15 Jan '20

15 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1127618 Bug ID: 1127618 Summary: midori always crashes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: batpul(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- always when started it core dumps immediately. here is valgrind output $ valgrind midori ==30079== Memcheck, a memory error detector ==30079== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==30079== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==30079== Command: midori ==30079== ==30079== Warning: set address range perms: large range [0x59e45000, 0x99e47000) (noaccess) ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BE4EA: JSC::LocalAllocator::allocate(JSC::GCDeferralContext*, JSC::AllocationFailureMode)::{lambda()#1}::operator()() const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0AEB45: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdd48 is on thread 1's stack ==30079== 528 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BE4EA: JSC::LocalAllocator::allocate(JSC::GCDeferralContext*, JSC::AllocationFailureMode)::{lambda()#1}::operator()() const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0AEB45: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdd58 is on thread 1's stack ==30079== 512 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0AE728: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdce8 is on thread 1's stack ==30079== 560 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0AE728: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdcf8 is on thread 1's stack ==30079== 544 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BE4EA: JSC::LocalAllocator::allocate(JSC::GCDeferralContext*, JSC::AllocationFailureMode)::{lambda()#1}::operator()() const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC09DD86: JSC::JSFunction::create(JSC::VM&, JSC::JSGlobalObject*, int, WTF::String const&, JSC::NativeFunction, JSC::Intrinsic, JSC::NativeFunction, JSC::DOMJIT::Signature const*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC02EA11: JSC::FunctionPrototype::addFunctionProperties(JSC::ExecState*, JSC::JSGlobalObject*, JSC::JSFunction**, JSC::JSFunction**, JSC::JSFunction**) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A6047: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdcd8 is on thread 1's stack ==30079== 400 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BE4EA: JSC::LocalAllocator::allocate(JSC::GCDeferralContext*, JSC::AllocationFailureMode)::{lambda()#1}::operator()() const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC09DD86: JSC::JSFunction::create(JSC::VM&, JSC::JSGlobalObject*, int, WTF::String const&, JSC::NativeFunction, JSC::Intrinsic, JSC::NativeFunction, JSC::DOMJIT::Signature const*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC02EA11: JSC::FunctionPrototype::addFunctionProperties(JSC::ExecState*, JSC::JSGlobalObject*, JSC::JSFunction**, JSC::JSFunction**, JSC::JSFunction**) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A6047: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdce8 is on thread 1's stack ==30079== 384 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB9A1226: JSC::UnlinkedFunctionExecutable::link(JSC::VM&, JSC::SourceCode const&, std::optional<int>, JSC::Intrinsic) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7B498B: JSC::functionPrototypeApplyCodeGenerator(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC02EA3B: JSC::FunctionPrototype::addFunctionProperties(JSC::ExecState*, JSC::JSGlobalObject*, JSC::JSFunction**, JSC::JSFunction**, JSC::JSFunction**) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A6047: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdca8 is on thread 1's stack ==30079== 352 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB9A1226: JSC::UnlinkedFunctionExecutable::link(JSC::VM&, JSC::SourceCode const&, std::optional<int>, JSC::Intrinsic) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7B498B: JSC::functionPrototypeApplyCodeGenerator(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC02EA3B: JSC::FunctionPrototype::addFunctionProperties(JSC::ExecState*, JSC::JSGlobalObject*, JSC::JSFunction**, JSC::JSFunction**, JSC::JSFunction**) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A6047: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdcb8 is on thread 1's stack ==30079== 336 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1484B8: JSC::ObjectPrototype::create(JSC::VM&, JSC::JSGlobalObject*, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A63EF: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdc68 is on thread 1's stack ==30079== 592 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1484B8: JSC::ObjectPrototype::create(JSC::VM&, JSC::JSGlobalObject*, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A63EF: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffdc78 is on thread 1's stack ==30079== 576 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBFDCEA4: JSC::ArrayPrototype::finishCreation(JSC::VM&, JSC::JSGlobalObject*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBFDD376: JSC::ArrayPrototype::create(JSC::VM&, JSC::JSGlobalObject*, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A6B33: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== Address 0x1ffeffdb28 is on thread 1's stack ==30079== 576 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBFDCEA4: JSC::ArrayPrototype::finishCreation(JSC::VM&, JSC::JSGlobalObject*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBFDD376: JSC::ArrayPrototype::create(JSC::VM&, JSC::JSGlobalObject*, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A6B33: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== Address 0x1ffeffdb38 is on thread 1's stack ==30079== 560 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1B26D0: JSC::StringPrototype::create(JSC::VM&, JSC::JSGlobalObject*, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A77A1: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffddc8 is on thread 1's stack ==30079== 240 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1B26D0: JSC::StringPrototype::create(JSC::VM&, JSC::JSGlobalObject*, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0A77A1: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffddd8 is on thread 1's stack ==30079== 224 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1C184E: JSC::StructureRareData::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1A54E6: JSC::Structure::allocateRareData(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1B4CD7: JSC::Structure::ensurePropertyReplacementWatchpointSet(JSC::VM&, int) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB98FD6E: JSC::PropertyCondition::isWatchableWhenValid(JSC::Structure*, JSC::PropertyCondition::WatchabilityEffort) const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC08E7E9: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0ADDEA: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== Address 0x1ffeffdd18 is on thread 1's stack ==30079== 176 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1C184E: JSC::StructureRareData::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1A54E6: JSC::Structure::allocateRareData(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC1B4CD7: JSC::Structure::ensurePropertyReplacementWatchpointSet(JSC::VM&, int) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB98FD6E: JSC::PropertyCondition::isWatchableWhenValid(JSC::Structure*, JSC::PropertyCondition::WatchabilityEffort) const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC08E7E9: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0ADDEA: JSC::JSGlobalObject::init(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B014D: JSC::JSGlobalObject::finishCreation(JSC::VM&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC0B03CD: JSC::JSGlobalObject::create(JSC::VM&, JSC::Structure*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BDC1F: JSGlobalContextCreateInGroup (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9C8: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== Address 0x1ffeffdd28 is on thread 1's stack ==30079== 160 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BE4EA: JSC::LocalAllocator::allocate(JSC::GCDeferralContext*, JSC::AllocationFailureMode)::{lambda()#1}::operator()() const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC18E6E9: JSC::ScriptExecutable::newCodeBlockFor(JSC::CodeSpecializationKind, JSC::JSFunction*, JSC::JSScope*, JSC::JSObject*&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC19419D: JSC::ScriptExecutable::prepareForExecutionImpl(JSC::VM&, JSC::JSFunction*, JSC::JSScope*, JSC::CodeSpecializationKind, JSC::CodeBlock*&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBE060D4: JSC::Interpreter::executeProgram(JSC::SourceCode const&, JSC::ExecState*, JSC::JSObject*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC00B090: JSC::evaluate(JSC::ExecState*, JSC::SourceCode const&, JSC::JSValue, WTF::NakedPtr<JSC::Exception>&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC00B227: JSC::profiledEvaluate(JSC::ExecState*, JSC::ProfilingReason, JSC::SourceCode const&, JSC::JSValue, WTF::NakedPtr<JSC::Exception>&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7B9FA7: JSEvaluateScript (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9F4: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffe4c8 is on thread 1's stack ==30079== 544 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE9427E: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7BE4EA: JSC::LocalAllocator::allocate(JSC::GCDeferralContext*, JSC::AllocationFailureMode)::{lambda()#1}::operator()() const (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC18E6E9: JSC::ScriptExecutable::newCodeBlockFor(JSC::CodeSpecializationKind, JSC::JSFunction*, JSC::JSScope*, JSC::JSObject*&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC19419D: JSC::ScriptExecutable::prepareForExecutionImpl(JSC::VM&, JSC::JSFunction*, JSC::JSScope*, JSC::CodeSpecializationKind, JSC::CodeBlock*&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBE060D4: JSC::Interpreter::executeProgram(JSC::SourceCode const&, JSC::ExecState*, JSC::JSObject*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC00B090: JSC::evaluate(JSC::ExecState*, JSC::SourceCode const&, JSC::JSValue, WTF::NakedPtr<JSC::Exception>&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC00B227: JSC::profiledEvaluate(JSC::ExecState*, JSC::ProfilingReason, JSC::SourceCode const&, JSC::JSValue, WTF::NakedPtr<JSC::Exception>&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7B9FA7: JSEvaluateScript (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9F4: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4E98EE2: midori_normal_app_new (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x10B314: main (in /usr/bin/midori) ==30079== Address 0x1ffeffe4d8 is on thread 1's stack ==30079== 528 bytes below stack pointer ==30079== ==30079== Invalid write of size 8 ==30079== at 0xBE94274: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D0FF: JSC::CompleteSubspace::tryAllocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBD4D388: JSC::CompleteSubspace::allocateSlow(JSC::VM&, unsigned long, JSC::GCDeferralContext*, JSC::AllocationFailureMode) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBFF5730: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBE9B11F: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBE940D8: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xBE061E0: JSC::Interpreter::executeProgram(JSC::SourceCode const&, JSC::ExecState*, JSC::JSObject*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC00B090: JSC::evaluate(JSC::ExecState*, JSC::SourceCode const&, JSC::JSValue, WTF::NakedPtr<JSC::Exception>&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xC00B227: JSC::profiledEvaluate(JSC::ExecState*, JSC::ProfilingReason, JSC::SourceCode const&, JSC::JSValue, WTF::NakedPtr<JSC::Exception>&) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0xB7B9FA7: JSEvaluateScript (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.11.6) ==30079== by 0x4EAF9F4: sokoke_js_script_eval (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== by 0x4ECF07E: midori_speed_dial_construct (in /usr/lib64/libmidori-core.so.0.0.0) ==30079== Address 0x1ffeffe528 is on thread 1's stack ==30079== 144 bytes below stack pointer ==30079== (midori4:30079): Gtk-WARNING **: Theme parsing error: gtk3.css:2:31: The style property GtkButton:default-border is deprecated and shouldn't be used anymore. It will be removed in a future version (midori4:30079): Gtk-WARNING **: Theme parsing error: gtk3.css:3:39: The style property GtkButton:default-outside-border is deprecated and shouldn't be used anymore. It will be removed in a future version (midori4:30079): Gtk-WARNING **: Theme parsing error: gtk3.css:4:29: The style property GtkButton:inner-border is deprecated and shouldn't be used anymore. It will be removed in a future version (midori4:30079): Gtk-WARNING **: Theme parsing error: gtk3.css:5:33: The style property GtkWidget:focus-line-width is deprecated and shouldn't be used anymore. It will be removed in a future version (midori4:30079): Gtk-WARNING **: Theme parsing error: gtk3.css:6:30: The style property GtkWidget:focus-padding is deprecated and shouldn't be used anymore. It will be removed in a future version (midori4:30079): Gtk-WARNING **: Theme parsing error: gtk3.css:26:20: The :insensitive pseudo-class is deprecated. Use :disabled instead. ==30079== Conditional jump or move depends on uninitialised value(s) ==30079== at 0x158EA12F: ??? (in /usr/lib64/libpixman-1.so.0.34.0) ==30079== by 0x158CDE6B: ??? (in /usr/lib64/libpixman-1.so.0.34.0) ==30079== by 0x15888D30: pixman_image_composite32 (in /usr/lib64/libpixman-1.so.0.34.0) ==30079== by 0xAC1062A: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC56DD1: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC487EE: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC492BE: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC4A0FA: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC03CCF: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC15986: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC4DE29: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== by 0xAC0BF55: ??? (in /usr/lib64/libcairo.so.2.11510.0) ==30079== ==30079== Conditional jump or move depends on uninitialised value(s) ==30079== at 0x2415730E: ??? (in /usr/lib64/librsvg-2.so.2.42.3) ==30079== by 0x241663A0: rsvg_handle_get_pixbuf_sub (in /usr/lib64/librsvg-2.so.2.42.3) ==30079== by 0x23F1CE68: ??? (in /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so) ==30079== by 0xAF1F602: gdk_pixbuf_loader_close (in /usr/lib64/libgdk_pixbuf-2.0.so.0.3600.10) ==30079== by 0xAF1BF6A: ??? (in /usr/lib64/libgdk_pixbuf-2.0.so.0.3600.10) ==30079== by 0xAF1CF3C: gdk_pixbuf_new_from_stream_at_scale (in /usr/lib64/libgdk_pixbuf-2.0.so.0.3600.10) ==30079== by 0x5883170: ??? (in /usr/lib64/libgtk-3.so.0.2200.30) ==30079== by 0x5886477: gtk_icon_info_load_icon (in /usr/lib64/libgtk-3.so.0.2200.30) ==30079== by 0x58866C3: gtk_icon_theme_load_icon_for_scale (in /usr/lib64/libgtk-3.so.0.2200.30) ==30079== by 0x5A1B85A: ??? (in /usr/lib64/libgtk-3.so.0.2200.30) ==30079== by 0x5A1CDE0: ??? (in /usr/lib64/libgtk-3.so.0.2200.30) ==30079== by 0x5A254AF: gtk_window_set_icon_name (in /usr/lib64/libgtk-3.so.0.2200.30) ==30079== -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1098985] New: mate-screensaver not following display changes
by bugzilla_noreply＠novell.com 15 Jan '20

15 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1098985 Bug ID: 1098985 Summary: mate-screensaver not following display changes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jan.kiszka(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since version 1.20.0, the MATE screensaver is not following changes of the display, e.g. when docking/undocking a notebook and switching from an external to the internal display. The lock window will stick with the screen it got activated on, leaving the machine unlocked on the other screen (which is critical when suspending a notebook on one screen and resuming it on another...). Regression from 1.18.1 from Leap 42.3 (which I'm now using again to mitigate the issue). -- You are receiving this mail because: You are on the CC list for the bug.

1 6