October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1000482] openSUSE Leap 42.2 Beta 1 install fails by hanging at driver iwlwifi
by bugzilla_noreply＠novell.com 02 Oct '16

02 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000482 http://bugzilla.suse.com/show_bug.cgi?id=1000482#c15 --- Comment #15 from pie Lud <pierrelud(a)yahoo.com> --- (In reply to pie Lud from comment #10) > Let me clarify: > > I have Leap 42.1 installed and all logs/output was from Leap 42.1. > > I tried to newly install Leap 42.2 Beta 1, Leap 42.2 Beta 2 and lastest > TumbleWeed and ALL these installs do NOT finish and hangs at the same place > during install loading drivers iwlwifi - the exact screen output during > install is > > iwlwifi* > _ > > > Again, outputs are therefore from Leap 42.1 because 42.2 Beta 1, 42.2 Beta 2 > and TW never installed. The TW install was just a test, I do NOT want to > install it. Thanks, now the situation gets clearer. Then let's try the following: - Install only the kernel-default package from OBS Kernel:openSUSE-42.1 repo http://download.opensuse.org/repositories/Kernel:/openSUSE-42.1/standard/x8… Then boot with this 4.4.x kernel while keeping the rest of 42.1 system as is. Does it boot and does the WiFi work properly? You can still boot 42.1 kernel by selecting via GRUB menu, of course. - If WiFi doesn't work, try to install the latest TW kernel-default from http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/ and also the latest kernel-firmware package from http://download.opensuse.org/repositories/Kernel:/HEAD/standard/noarch/ (The kernel-firmware package should be backward-compatible, so it should keep working even with 42.1 kernel.) If this combination doesn't work, it's the starting point to debug. OTOH, if TW kernel + latest firmware works, try 42.2 kernel with this latest firmware. **************************************************************************** I now tried 1. 42.2 the kernel + firmware and 2. TW the kernel + firmware you wanted me to try and in both cases KDE does not want to login just hangs = nothing happens, no keyboard input does anything. This does not look good. What now? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002439] New: ARTWORK: openSUSE dark theme lock screen - hard to read date/time
by bugzilla_noreply＠novell.com 02 Oct '16

02 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1002439 Bug ID: 1002439 Summary: ARTWORK: openSUSE dark theme lock screen - hard to read date/time Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: qantas94heavy(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 695361 --> http://bugzilla.opensuse.org/attachment.cgi?id=695361&action=edit Light text hard to read on Plasma lock screen On the lock screen, if the desktop theme is set to "openSUSEdark" in Plasma 5, then the date and time become hard to read due to a lack of contrast (light on light). This is unlike the SDDM login screen where the dark text contrasts with the light bubble around the date and time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002422] New: GraphicsMagick: 8BIM/8BIMW unsigned underflow leads to heap overflow
by bugzilla_noreply＠novell.com 02 Oct '16

02 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1002422 Bug ID: 1002422 Summary: GraphicsMagick: 8BIM/8BIMW unsigned underflow leads to heap overflow Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reference: http://seclists.org/oss-sec/2016/q4/0 =========================== Today we received a report from Marco Grassi about a heap overflow in the 8BIM reader. 8BIM is a metadata chunk often attached to JPEG files. After investigation it was found that there was a small unsigned overflow leading to a huge size value, which then resulted in a heap overflow (causing a crash). We believe that this issue exists in all GraphicsMagick releases to date (including 1.3.25). The fix to this may be found in GraphicsMagick Mercurial at "https://sourceforge.net/p/graphicsmagick/code/ci/5c7b6d6094a25e99c57f8b1834…";. Bob -- Bob Friesenhahn bfriesen () simple dallas tx us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ =========================== Due to https://software.opensuse.org/package/GraphicsMagick version 1.3.25 is being in use in openSUSE Tumbleweed. Version 1.3.21 is being in use in 42.1... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1002421] New: ImageMagick: mogrify global buffer overflow
by bugzilla_noreply＠novell.com 02 Oct '16

02 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1002421 Bug ID: 1002421 Summary: ImageMagick: mogrify global buffer overflow Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reference: http://seclists.org/oss-sec/2016/q3/688 openSUSE: https://software.opensuse.org/package/ImageMagick ============================== Hi, imagemagick identify suffers of a global buffer overflow issue, which I reported and has been patched, you can find a reproducer in the github bug tracker issue link issue: https://github.com/ImageMagick/ImageMagick/issues/280 patch: https://github.com/ImageMagick/ImageMagick/commit/a7bb158b7bedd1449a34432fe… Thanks, Marco Grassi (@marcograss) of Tencent's Keen Lab ➜ utilities git:(master) ✗ ./magick mogrify ../../ImageMagick_bugs/mogrify_gbof~~ ==26125==ERROR: AddressSanitizer: global-buffer-overflow on address 0x0000037a74fc at pc 0x00000077c9ba bp 0x7ffdffbaac70 sp 0x7ffdffbaac68 READ of size 4 at 0x0000037a74fc thread T0 #0 0x77c9b9 (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x77c9b9) #1 0x78024f (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x78024f) #2 0x18bed91 (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x18bed91) #3 0x18c2594 (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x18c2594) #4 0x2ff1c7f (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x2ff1c7f) #5 0x2f8cead (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x2f8cead) #6 0x4f5da9 (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x4f5da9) #7 0x7f3717a6b82f (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #8 0x422428 (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x422428) 0x0000037a74fc is located 4 bytes to the left of global variable 'format_bytes' defined in 'MagickCore/profile.c:1945:5' (0x37a7500) of size 52 0x0000037a74fc is located 34 bytes to the right of global variable '' defined in 'MagickCore/profile.c:1306:38' (0x37a74c0) of size 26 '' is ascii string 'ResetImageProfileIterator' SUMMARY: AddressSanitizer: global-buffer-overflow (/home/bob/VulnResearch/misc/ImageMagick/utilities/magick+0x77c9b9) Shadow bytes around the buggy address: 0x0000806ece40: f9 f9 f9 f9 00 00 f9 f9 f9 f9 f9 f9 02 f9 f9 f9 0x0000806ece50: f9 f9 f9 f9 00 00 00 03 f9 f9 f9 f9 05 f9 f9 f9 0x0000806ece60: f9 f9 f9 f9 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 0x0000806ece70: 00 04 f9 f9 f9 f9 f9 f9 00 00 00 00 00 00 06 f9 0x0000806ece80: f9 f9 f9 f9 00 00 03 f9 f9 f9 f9 f9 00 00 00 00 =>0x0000806ece90: 00 06 f9 f9 f9 f9 f9 f9 00 00 00 02 f9 f9 f9[f9] 0x0000806ecea0: 00 00 00 00 00 00 04 f9 f9 f9 f9 f9 05 f9 f9 f9 0x0000806eceb0: f9 f9 f9 f9 05 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 0x0000806ecec0: 00 00 00 00 f9 f9 f9 f9 05 f9 f9 f9 f9 f9 f9 f9 0x0000806eced0: 04 f9 f9 f9 f9 f9 f9 f9 05 f9 f9 f9 f9 f9 f9 f9 0x0000806ecee0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb ==26125==ABORTING ============================== -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1002422] GraphicsMagick: 8BIM/8BIMW unsigned underflow leads to heap overflow
by bugzilla_noreply＠novell.com 02 Oct '16

02 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=1002422 http://bugzilla.novell.com/show_bug.cgi?id=1002422#c1 --- Comment #1 from Mikhail Kasimov <mikhail.kasimov(a)gmail.com> --- (In reply to Mikhail Kasimov from comment #0) > Reference: http://seclists.org/oss-sec/2016/q4/0 > > =========================== > Today we received a report from Marco Grassi about a heap overflow in the > 8BIM reader. 8BIM is a metadata chunk often attached to JPEG files. > > > After investigation it was found that there was a small unsigned overflow > leading to a huge size value, which then resulted in a heap overflow > (causing a crash). > > > We believe that this issue exists in all GraphicsMagick releases to date > (including 1.3.25). > > > The fix to this may be found in GraphicsMagick Mercurial at > "https://sourceforge.net/p/graphicsmagick/code/ci/ > 5c7b6d6094a25e99c57f8b18343914ebfd8213ef/";. > > > Bob > -- > Bob Friesenhahn > bfriesen () simple dallas tx us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > =========================== > > Due to https://software.opensuse.org/package/GraphicsMagick version 1.3.25 > is being in use in openSUSE Tumbleweed. Version 1.3.21 is being in use in > 42.1... http://seclists.org/oss-sec/2016/q4/2 : Use CVE-2016-7800. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002422] GraphicsMagick: 8BIM/8BIMW unsigned underflow leads to heap overflow
by bugzilla_noreply＠novell.com 02 Oct '16

02 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=1002422 Mikhail Kasimov <mikhail.kasimov(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Alias| |CVE-2016-7800 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002432] New: New "Activate Application Menu Widget" keyboard shortcut forgotten after reboot
by bugzilla_noreply＠novell.com 01 Oct '16

01 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1002432 Bug ID: 1002432 Summary: New "Activate Application Menu Widget" keyboard shortcut forgotten after reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: alzaagman(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build Identifier: After assigning a different keyboard shortcut to "Activate Application Menu Widget", such as Meta + R, it is forgotten after a reboot. Additionally, multiple "Activate Application Menu Widget" entries without keyboard shortcut assigned appear like so: http://i.imgur.com/L8Z2s8P.png Reproducible: Always Steps to Reproduce: 1. Assign custom keyboard shortcut to "Activate Application Menu Widget" 2. Reboot Actual Results: Custom keyboard shortcut is forgotten. Expected Results: Custom keyboard shortcut is remembered. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002351] CVE-2016-8339: Redis CONFIG SET client-output-buffer-limit Code Execution Vulnerability
by bugzilla_noreply＠novell.com 01 Oct '16

01 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=1002351 Mikhail Kasimov <mikhail.kasimov(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Alias| |CVE-2016-8339 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 980008] openSUSE Wiki is inaccessible
by bugzilla_noreply＠novell.com 01 Oct '16

01 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=980008 http://bugzilla.opensuse.org/show_bug.cgi?id=980008#c3 Mikhail Kasimov <mikhail.kasimov(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Mikhail Kasimov <mikhail.kasimov(a)gmail.com> --- Already fixed. Closed by report-starter. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002419] New: network:telephony/asterisk: Bug
by bugzilla_noreply＠novell.com 01 Oct '16

01 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1002419 Bug ID: 1002419 Summary: network:telephony/asterisk: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: nix(a)opensuse.org Reporter: diego.ercolani(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: jengelh(a)inai.de Found By: --- Blocker: --- There is a problem running asterisk 14 under Model name: AMD Turion(tm) II Neo N40L Dual-Core Processor Probably there is an incompatibility istanced during compile time that prevent asterisk to run correctly I have a kernel trap during startup. I resolved branching network:telephony/asterisk and compiling locally on a AMD CPU. Sorry, my system is in production so I cannot give you where the trap occurs. -- You are receiving this mail because: You are on the CC list for the bug.

1 3