October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 922405] 1 minute delay until USB thumb drive is usable
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=922405 Alan Ott <alan(a)softiron.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(triffterer(a)web.de | |) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922405] 1 minute delay until USB thumb drive is usable
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=922405 http://bugzilla.suse.com/show_bug.cgi?id=922405#c15 Alan Ott <alan(a)softiron.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |alan(a)softiron.co.uk Resolution|NORESPONSE |--- --- Comment #15 from Alan Ott <alan(a)softiron.co.uk> --- Hi guys, I know what the problem is, as I have seen this issue and chased it down. The symptom: Plug in a specific thumb drive, and it is unusable (eg: unable to be mounted) for 60 seconds. dmesg will show that after 60 seconds the drive is reset and then becomes usable (eg: able to be mounted). Using a USB analyzer, I was able to determine that the host is sending a SCSI INQUIRY request with the VPD bit set looking for page 0x80, which is where the device strings are. The device then incorrectly returns a non-zero in a reserved field, which the host incorrectly treats as part of a length field, causing the host to re-send the SCSI INQUIRY request again with the much larger length field, causing the thumb drive to hang. Make no mistake, this is a bug on the thumb drive, but we need to work around it, like we always do. See SCSI documentation from [1]. The section numbers below come from this document. Summary of events: 1. device is connected 2. host enumerates device 3. host sends SCSI INQUIRY with EVPD bit set, requesting page 0x80 (serial numbers). See 3.6.1, Table 45, and information on EVPD in the same section. 4. The device returns the contents of page 0x80, but incorrectly puts a 0x6 in byte 2, which is supposed to be a reserved field. See 4.4.10. This is a bug in the thumb drive. 5. The host interprets bytes 2 and 3 together as a 16-bit length value, relying on the device to have zeroed byte 2 (as required), which this thumb drive incorrectly does not do. 6. With the length returned by the device being much larger than expected, the host will then re-send the INQUIRY with the new, larger, incorrect length (in this case 0x6fc instead of just 0xfc). 7. The thumb drive, for whatever reason, can't handle this request and hangs. 8. After 60 seconds, the request times out, and the device is reset. After the device is reset, the host will NOT issue the INQUIRY with VPD for page 0x80, and the device works fine (eg: is able to be mounted). After trying to find where in the kernel this SCSI INQUIRY with VPD was originating from, I eventually was able to determine that it was happening as a result of an ioctl() initiated from user space by the sg_inq process, which is part of the sg3_utils package. This is happening as a result of a udev rule[2], which is also part of sg3_utils. This udev rule[2] calls sg_inq which sends the SCSI commands directly to the device. It's worth pointing out here, that the Linux kernel's code, which can read these VPD pages, will _not_ issue these EVPD INQUIRY requests for USB devices. In drivers/usb/storage/scsiglue.c, is the code: /* Some devices don't handle VPD pages correctly */ sdev->skip_vpd_pages = 1; Indeed, this device does not handle VPD correctly. There's a reason the kernel doesn't issue these requests on USB devices, so they shouldn't be issued from user space either. 1. Is there a reason to need this sg3_utils udev file which pokes at the drive from user space when it's attached? 2. If the answer to the above is yes, can it be modified to _not_ be run for USB devices? My recommendation is to remove the udev rule at [2] completely. The kernel is very good at working around broken hardware and giving each device the interactions that it needs in order to work properly. This udev rule cuts through all those checks and workarounds and issues SCSI commands directly from user space, re-exposing the same hardware issues that the kernel is very careful to work around. I'm running on Leap 42.1 on aarch64, with sg3_utils version 1.41. The latest sg3_utils source[3] still has the issue. Again though, the larger issue here is not that sg3_utils is doing something incorrectly (even though it is); the issue is that we are sending SCSI commands from user space to devices where they are not appropriate (eg: USB devices). Thanks! Alan. [1] http://www.seagate.com/staticfiles/support/disc/manuals/scsi/100293068a.pdf [2] /usr/lib/udev/rules.d/55-scsi-sg3_id.rules [3] https://github.com/hreinecke/sg3_utils/blob/master/src/sg_inq.c#L3058 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1000440] New: no kernel messages in dmesg buffer
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000440 Bug ID: 1000440 Summary: no kernel messages in dmesg buffer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I cannot tell why installer fails to detect hardware because there are no kernel messages in the dmesg buffer nor are there any in journald buffer. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1002503] zypper dup installs unneeded package texlive-lm-fonts
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=1002503 http://bugzilla.novell.com/show_bug.cgi?id=1002503#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rdodopoulos(a)suse.com Flags| |needinfo?(rdodopoulos@suse. | |com) --- Comment #1 from Michael Andres <ma(a)suse.com> --- Every 'zypper dup' leaves a solver testcase in /var/log/updateTestcase-YYYY-MM-DD-hh-mm-ss'. Please tar the testcase of the 2nd dup (the one that replaced ctan-latinmodern-fonts ) and attach it to the bugreport. In case the testcase exceeds the 10MB limit for bugzilla uploads, you can use 'split' to divide the file into smaller pieces: > $ cd /tmp > $ tar cvjf zypper.solverTestCase.tar.bz2 /var/log/updateTestcase-YYYY-MM-DD-hh-mm-ss > $ split -b 10M --additional-suffix=-zypper.solverTestCase.tar.bz2 zypper.solverTestCase.tar.bz2 The created pieces will be named like this: > xaa-zypper.solverTestCase.tar.bz2 > xab-zypper.solverTestCase.tar.bz2 > xac-zypper.solverTestCase.tar.bz2 > ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 999738] At screen lock the plasmashell causes high load
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=999738 http://bugzilla.suse.com/show_bug.cgi?id=999738#c8 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(wbauer(a)tmo.at) --- Comment #8 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Wolfgang Bauer from comment #1) What is going on on this bug entry ... I'd like to have a solution. How to avoid this nasty polling loop? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 989341] New: [AArch64] KDE broken as QML crashes on startup
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=989341 Bug ID: 989341 Summary: [AArch64] KDE broken as QML crashes on startup Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: aarch64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Anytime I start anything using QML on AArch64, it crashes instantly in /usr/lib64/libQt5Qml.so.5. Sample backtrace from kwin_x11: #0 0x0000ffffb54f20b0 in QV4::Object::defineReadonlyProperty(QV4::String*, QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5 #1 0x0000ffffb554365c in ?? () from /usr/lib64/libQt5Qml.so.5 #2 0x0000ffffb54b9ad4 in QV4::ExecutionEngine::ExecutionEngine(QV4::EvalISelFactory*) () from /usr/lib64/libQt5Qml.so.5 #3 0x0000ffffb55ef5b0 in QV8Engine::QV8Engine(QJSEngine*) () from /usr/lib64/libQt5Qml.so.5 #4 0x0000ffffb544b600 in QJSEngine::QJSEngine(QJSEnginePrivate&, QObject*) () from /usr/lib64/libQt5Qml.so.5 #5 0x0000ffffb555ac44 in QQmlEngine::QQmlEngine(QObject*) () from /usr/lib64/libQt5Qml.so.5 #6 0x0000ffffb7cddc20 in ?? () from /usr/lib64/libkwin.so.5 #7 0x0000ffffb7cddd14 in ?? () from /usr/lib64/libkwin.so.5 #8 0x0000ffffb7be17c4 in KWin::Workspace::init() () from /usr/lib64/libkwin.so.5 #9 0x0000ffffb7be2220 in KWin::Workspace::Workspace(QString const&) () from /usr/lib64/libkwin.so.5 #10 0x0000ffffb7c27454 in KWin::Application::createWorkspace() () from /usr/lib64/libkwin.so.5 #11 0x0000ffffb7f9e8e0 in ?? () from /usr/lib64/libkdeinit5_kwin_x11.so #12 0x0000ffffb6c90f78 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #13 0x0000ffffb7aaf65c in KSelectionOwner::Private::claimSucceeded() () from /usr/lib64/libKF5WindowSystem.so.5 #14 0x0000ffffb7aafea4 in KSelectionOwner::filterEvent(void*) () from /usr/lib64/libKF5WindowSystem.so.5 #15 0x0000ffffb6c605cc in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () from /usr/lib64/libQt5Core.so.5 #16 0x0000ffffb101edb4 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib64/libQt5XcbQpa.so.5 #17 0x0000ffffb101f990 in QXcbConnection::processXcbEvents() () from /usr/lib64/libQt5XcbQpa.so.5 #18 0x0000ffffb6c91b28 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x0000ffffb7565284 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x0000ffffb756cae0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #21 0x0000ffffb6c637b4 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #22 0x0000ffffb6c66058 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #23 0x0000ffffb6cb6c94 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #24 0x0000ffffb1096dac in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #25 0x0000ffffb6c61564 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #26 0x0000ffffb6c69d10 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #27 0x0000ffffb7fa00fc in kdemain () from /usr/lib64/libkdeinit5_kwin_x11.so #28 0x0000ffffb7e1e8a4 in __libc_start_main () from /lib64/libc.so.6 #29 0x0000000000400960 in _start () The same issue affects Qt 5.6.0, 5.6.1 and 5.7.0 and I could not find the same issue anywhere else on the internet and Qt is supposedly used on many aarch64 platforms, so I assume that this might be an openSUSE-only issue. The nullptr comes from a function that returns 0 after some bit fiddling with pointers. Any idea what causes this issue? Is it maybe related to the issue with firefox, which also crashed in the JS engine? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1000988] YaST Software Management crashed on second start under KDE Session
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000988 http://bugzilla.suse.com/show_bug.cgi?id=1000988#c4 Iakov Karpov <srid(a)rkmail.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(srid(a)rkmail.ru) | --- Comment #4 from Iakov Karpov <srid(a)rkmail.ru> --- Created attachment 695684 --> http://bugzilla.suse.com/attachment.cgi?id=695684&action=edit y2log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 954143] Leap (KDE5) doesn't know what to do with an .rpm file. Chrome 64bit and Skype tested.
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=954143 http://bugzilla.suse.com/show_bug.cgi?id=954143#c28 --- Comment #28 from Adam Liebermann <opensuse_org(a)xibo.at> --- @Ludwig Nussel I as a user am able to install via command line, but I have to check the command. What for? I know what I'm doing and sometimes I need to install a package from RPM (examples are missing Wifi driver on a laptop without ethernet, skype, mendeley, chrome..). Why making the live harder than need be? It is those small things that make me as a user feel that I'm testing an unfinished product. please don't reject the patch :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947645] aarch64: Yast crashes immediately
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=947645 http://bugzilla.suse.com/show_bug.cgi?id=947645#c9 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(dmueller(a)suse.com | |) | --- Comment #9 from Dirk Mueller <dmueller(a)suse.com> --- resolving as fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 971814] emacs: fill-paragraph sets the modified flag even when no changes occur
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=971814 http://bugzilla.suse.com/show_bug.cgi?id=971814#c13 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(j_k_v(a)ro.ru) --- Comment #13 from Dr. Werner Fink <werner(a)suse.com> --- Now what's about GNU Emacs 25.1 now out there? -- You are receiving this mail because: You are on the CC list for the bug.

1 0