August 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1051059] BUG: scheduling while atomic: systemd-sleep/7880/0x00000002
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1051059 http://bugzilla.suse.com/show_bug.cgi?id=1051059#c23 Joey Lee <jlee(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jlee(a)suse.com |tiwai(a)suse.com --- Comment #23 from Joey Lee <jlee(a)suse.com> --- Set assign to Takashi because he done all jobs to fix this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965674] New: Desktop moves off-screen
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=965674 Bug ID: 965674 Summary: Desktop moves off-screen Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: turtlevt(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 664786 --> http://bugzilla.opensuse.org/attachment.cgi?id=664786&action=edit picture of screen with desktop incorrectly placed I updated my OpenSuse 13.2 system to Tumbleweed. Upgrade went well. On reboot I logged into my user and started to configure the desktop as it seems to change from my old 13.2 one. I added widgets to the panel and app Icons to the desktop. All went well for a while, then suddenly after a reboot and logging in my user, when the desktop started it was moved to the right and down the screen. I logged out/in and now the desktop was further right and down the screen. After a reboot the desktop had disappeared completely. Yet, application windows and the application launcher appeared in the correct places. It was most frustrating. Thinking there was perhaps something wrong during the upgrade, I downloaded a Tumbleweed iso image and did a new install. Again all was well but after reconfiguring my desktop, the same thing happened. I have had to reinstall my old system from a backup. Fortunately V13.2 seemed to pay no attention to the new plasma setup and everything was file. Cost me a lot of tile and frustration - especially as I really liked the new Plasma 5. So, today, with a bit of spare time on hand, I downloaded the latest Tumbleweed image and installed it on an old 32-bit Dell laptop. Again, no installation problems and for a while it seemed the problem had gone, but then I changed the desktop wallpaper and after logging out/in, back comes the disappearing desktop problem. I do not know how to reset the system's positioning of the desktop nor do I know what I can give you as diagnostics. Please advise and I shall provide. All I have is a pretty poor picture, taken with my phone, of the screen showing the desktop way down in the right hand bottom corner. If it helps.... -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1051059] BUG: scheduling while atomic: systemd-sleep/7880/0x00000002
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1051059 http://bugzilla.suse.com/show_bug.cgi?id=1051059#c22 --- Comment #22 from Joey Lee <jlee(a)suse.com> --- Sorry for my delay! (In reply to Takashi Iwai from comment #19) > Created attachment 734772 [details] > Revised patch Thanks for Takashi's help! I have reviewed this patch. It's good to me. (In reply to Takashi Iwai from comment #16) [...snip] > > I'm not sure whether it's safe to assume that. Basically you're calling > some sleepable functions like mutex or kmalloc with GFP_KERNEL inside the > local irq-disabled context. This may not work. > Is that because using sleepable functions in irq-disabled context that it may causes the irq disable too long then causes hard lock? > I guess the problem is only in the crypto shash allocation and > initialization. If so, a better option would be to move it before the > actual swsusp_arch_suspend() call. > > Maybe we can define swsusp_arch_suspend_prepare() and call it in > kernel/power/hibernate.c:create_image() before disabling irq. And call the > counter-part swsusp_arch_suspend_post() at the end. > Make weak-link dummy functions for these, so that the arch-specific code can > be bound as opt-in. Thanks for your idea that it makes sense. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1048074] Can not Boot Tumbleweed media from Macbook Pro.
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1048074 http://bugzilla.suse.com/show_bug.cgi?id=1048074#c7 --- Comment #7 from Kazufumi Watanabe <kiyomi.kakitsubata(a)gmail.com> --- Dear Steffen Winterfeldt I think sorry to delay my reply. Perhaps,ZALMAN ZM-VE350 can not emulate openSUSE's disk. (Other distoribution's iso image happened!) This problem is not caused by iso image. I think sorry to you. Please close this ticket as resolved. Thank you for your help. Cheers -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1020030] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=1020030 http://bugzilla.novell.com/show_bug.cgi?id=1020030#c21 --- Comment #21 from Randy Wright <rwright(a)hpe.com> --- Reproducing pretty reliably on my SUT with the previously mentioned KOTD. Most recently if produced a full call trace: [ 21.155564] Call Trace: [ 21.158047] [<ffffffff81019b19>] dump_trace+0x59/0x310 [ 21.163310] [<ffffffff81019eba>] show_stack_log_lvl+0xea/0x170 [ 21.169270] [<ffffffff8101ac41>] show_stack+0x21/0x40 [ 21.174448] [<ffffffff81320810>] dump_stack+0x5c/0x7c [ 21.179628] [<ffffffff8107e061>] warn_slowpath_common+0x81/0xb0 [ 21.185708] [<ffffffffa034526d>] btrfs_qgroup_free_refroot+0x14d/0x180 [btrfs] [ 21.193104] [<ffffffffa02d6797>] commit_fs_roots.isra.21+0x147/0x180 [btrfs] [ 21.200315] [<ffffffffa02d8f86>] btrfs_commit_transaction.part.27+0x3f6/0xa90 [btrfs] [ 21.208290] [<ffffffff812369ee>] sync_filesystem+0x6e/0xa0 [ 21.213905] [<ffffffff812086e2>] generic_shutdown_super+0x22/0xf0 [ 21.220126] [<ffffffff812087be>] kill_anon_super+0xe/0x20 [ 21.225667] [<ffffffffa02a7983>] btrfs_kill_super+0x13/0x100 [btrfs] [ 21.232152] [<ffffffff81208089>] deactivate_locked_super+0x39/0x70 [ 21.238466] [<ffffffff812234ab>] cleanup_mnt+0x3b/0x80 [ 21.243730] [<ffffffff8109a112>] task_work_run+0x72/0x90 [ 21.249168] [<ffffffff81078ad9>] exit_to_usermode_loop+0x91/0xc2 [ 21.255305] [<ffffffff81003ae5>] syscall_return_slowpath+0x85/0xa0 [ 21.261618] [<ffffffff81609348>] int_ret_from_sys_call+0x25/0x8f [ 21.271028] DWARF2 unwinder stuck at int_ret_from_sys_call+0x25/0x8f There is a supportconfig bundle from this SUT attached to a different confidential bug 1043261. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1020030] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=1020030 http://bugzilla.novell.com/show_bug.cgi?id=1020030#c20 --- Comment #20 from Randy Wright <rwright(a)hpe.com> --- Actually I recreated the warning again running the 4.4.79-2.g7fe2b65-default KOTD on a subsequent crashdump test -- again it occurred as the crash capture completed and the system is about to reboot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1020030] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=1020030 http://bugzilla.novell.com/show_bug.cgi?id=1020030#c19 Randy Wright <rwright(a)hpe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rwright(a)hpe.com --- Comment #19 from Randy Wright <rwright(a)hpe.com> --- I just observed something quite similar running the SLES12SP3 kotd 4.4.79-2.g7fe2b65-default. I was testing crashdump, and as makedumpfile was completing successfully, I observed this on the serial console: [ 51.673736] ------------[ cut here ]------------ [ 51.673784] WARNING: CPU: 0 PID: 325 at ../fs/btrfs/qgroup.c:2466 btrfs_qgroup_free_refroot+0x14d/0x180 [btrfs]() [ 51.673812] Modules linked in: btrfs xor hid_generic usbhid uas ... [ 51.673813] Supported: Yes [ 51.673818] CPU: 0 PID: 325 Comm: umount Not tainted 4.4.79-2.g7fe2b65-default #1 [ 51.673819] Hardware name: HPE ProLiant.... [ 51.673824] 0000000000000000 ffffffff81320810 0000000000000000 ffffffffa03839e9 [ 51.673827] ffffffff8107e061 ffff8800624fc908 0000000000050000 ffff88027788ad80 [ 51.673829] ffff8800624fc880 ffff88027788a000 ffffffffa036b26d 0000000000000103 [ 51.673830] Call Trace: [ 51.673853] [<ffffffff81019b19>] dump_trace+0x59/0x310 [ 51.673862] [<ffffffff81019eba>] show_stack_log_lvl+0xea/0x170 [ 51.673868] [<ffffffff8101ac41>] show_stack+0x21/0x40 [ 51.673875] [<ffffffff81320810>] dump_stack+0x5c/0x7c [ 51.673884] [<ffffffff8107e061>] warn_slowpath_common+0x81/0xb0 umount: /kdump/mnt0: not mounted umount[ 51.673923] [<ffffffffa036b26d>] btrfs_qgroup_free_refroot+0x14d/0x180 [btrfs] If you want more detail from my sighting, I will need to create a confidental bugzilla, as this was seen on an as-yet-unreleased HPE system. I can relate that I have run many previous crashdump tests on this system and never previously seen a warning from btrfs_qgroup_free_refroot, so I can offer no clues for reproduction. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1029364] open-iscsi/iscsiadm not working as expected on openSUSE
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1029364 http://bugzilla.suse.com/show_bug.cgi?id=1029364#c15 Lee Duncan <lduncan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #15 from Lee Duncan <lduncan(a)suse.com> --- (In reply to C. Holm from comment #14) > Thanks for the fix! Please just go ahead and close this, we will update the > affected servers as soon as we can, and we can live with the problem and our > workaround for now. Don't waste time on outdated releases. (; Thank you. Closing as resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1051697] New: VUL-0: CVE-2017-12061: mantis,mantisbt: XSS in /admin/install.php script
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1051697 Bug ID: 1051697 Summary: VUL-0: CVE-2017-12061: mantis,mantisbt: XSS in /admin/install.php script Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: astieger(a)suse.com Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2017-12061: XSS in /admin/install.php script A cross-site scripting (XSS) vulnerability in the MantisBT Installation script allows remote attackers to inject arbitrary code through crafted parameters. This is only possible if the admin/ folder was not deleted after installation, as recommended in the MantisBT Admin Guide [1]. Affected versions: 1.3.11 and older, 2.5.1 and older Fixed in versions: 1.3.12, 2.5.2, 2.6.0 (not yet released*) Patch: - 1.3: https://github.com/mantisbt/mantisbt/commit/17f9b94f031ba93ae2a727bca0e6845… - 2.x: https://github.com/mantisbt/mantisbt/commit/c73ae3d3d4dd4681489a9e697e8ade7… Credits: - Reported by aLLy from ONSEC (https://twitter.com/IamSecurity) - Fixed by Damien Regad (MantisBT Developer) References: - MantisBT issue tracker https://mantisbt.org/bugs/view.php?id=23146 [1] http://mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.insta… * Releases 1.3.12, 2.5.2 and 2.6.0 are scheduled for release in the coming week. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1051698] New: VUL-0: CVE-2017-12062: mantis,mantisbt: XSS in manage_user_page.php
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1051698 Bug ID: 1051698 Summary: VUL-0: CVE-2017-12062: mantis,mantisbt: XSS in manage_user_page.php Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: astieger(a)suse.com Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2017-12062: XSS in manage_user_page.php A cross-site scripting (XSS) vulnerability in the MantisBT Manage User page allows remote attackers to inject arbitrary code (if CSP settings permit it) through a crafted 'filter' parameter. Affected versions: 2.1.0 through 2.5.1 Fixed in versions: 2.5.2, 2.6.0 (not yet released*) Patch: https://github.com/mantisbt/mantisbt/commit/9b5b71dadbeeeec27efea59f562ac5b… Credits: - Reported by Trí Chim Trích (https://twitter.com/trichimtrich) - Fixed by Roland Becker (MantisBT Developer) References: - MantisBT issue tracker http://www.mantisbt.org/bugs/view.php?id=23166 * Releases 1.3.12, 2.5.2 and 2.6.0 are scheduled for release in the coming week. -- You are receiving this mail because: You are on the CC list for the bug.

1 1