[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646 --- Comment #21 from Martin Gräßlin --- just for the record: rebooted system, now using Intel driver version 2.99.917+git20160218-1, still same problem -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359633] krita includes nonfree image lena*.png
https://bugs.kde.org/show_bug.cgi?id=359633 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #4 from Dmitry Kazakov --- Hi, Wolthera! The images in sdk/tests/data were my attempt not to store the data in every testing directory and fetch them from a centralized storage via TestUtil::fetchDataFileLazy(). According to grep lena.png was not used this way, so the commit is safe. The rest of the usages weem to be not very difficult to fix libs/ui/tests/filter_stroke_test.cpp:QImage src(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); libs/ui/tests/kis_animation_importer_test.cpp: files.append(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); libs/ui/tests/kis_animation_importer_test.cpp:QImage source2(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); libs/ui/tests/kis_prescaled_projection_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); libs/ui/tests/kis_prescaled_projection_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); libs/ui/tests/kis_prescaled_projection_test.cpp:QImage referenceImage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); libs/ui/tests/kis_prescaled_projection_test.cpp:sourceImage = QImage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); plugins/filters/tests/kis_all_filter_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); plugins/filters/tests/kis_all_filter_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); plugins/filters/tests/kis_all_filter_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); plugins/filters/tests/kis_all_filter_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); plugins/filters/tests/kis_crash_filter_test.cpp:QImage qimage(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); plugins/tools/basictools/tests/move_stroke_test.cpp:QImage src(QString(FILES_DATA_DIR) + QDir::separator() + "lena.png"); -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646 --- Comment #22 from Martin Gräßlin --- comment #21 was on DRI2/UXA just changed to DRI3/SNA and problem is completely gone \o/ Will do further tests for that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646 --- Comment #23 from Martin Gräßlin --- DRI2/SNA: problem visible -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359812] New: plasmashell crashes when you try to establish a new network connection
https://bugs.kde.org/show_bug.cgi?id=359812 Bug ID: 359812 Summary: plasmashell crashes when you try to establish a new network connection Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: registrazi...@fracassa.org CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was trying to connect a VPN previously saved in networkmanager; by clicking connect, plasmashell crashes! The same thing happens if you try to start a UMTS connection or a wired network profile. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9e897fa7c0 (LWP 2423))] Thread 9 (Thread 0x7f9e73262700 (LWP 2426)): #0 0x7f9e82d26bbd in poll () at /lib64/libc.so.6 #1 0x7f9e87c53422 in () at /usr/lib64/libxcb.so.1 #2 0x7f9e87c5500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f9e753b33c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f9e8341f32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f9e825300a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f9e82d2efed in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f9e6bfff700 (LWP 2433)): #0 0x7f9e7f406205 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9e7f40883f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9e7f408df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9e7f408f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9e83651d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9e835f8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f9e8341a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f9e86705df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f9e8341f32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f9e825300a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9e82d2efed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f9e5f491700 (LWP 2434)): #0 0x7f9e7f44ad14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9e7f40889b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9e7f408df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9e7f408f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9e83651d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9e835f8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f9e8341a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f9e86705df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f9e8341f32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f9e825300a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9e82d2efed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f9e5dcf8700 (LWP 2435)): #0 0x7f9e82d26bbd in poll () at /lib64/libc.so.6 #1 0x7f9e7f408e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9e7f408f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9e83651d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9e835f8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9e8341a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f9e86705df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f9e8341f32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f9e825300a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f9e82d2efed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9e57fff700 (LWP 2436)): #0 0x7f9e8253403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9e88ed786b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f9e88ed7899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f9e825300a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9e82d2efed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9e54a77700 (LWP 2437)): #0 0x7f9e82d26bbd in poll () at /lib64/libc.so.6 #1 0x7f9e7f408e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9e7f408f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9e83651d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9e835f8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9e8341a6
[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646 --- Comment #24 from Martin Gräßlin --- further tests: * enabling Option "TearFree" did not improve the situation * glamor was ignored, switched to SNA according to Xorg log -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359813] New: images inserted in mail with CID are not displayed
https://bugs.kde.org/show_bug.cgi?id=359813 Bug ID: 359813 Summary: images inserted in mail with CID are not displayed Product: kmail2 Version: 5.1 Platform: Archlinux Packages URL: http://snag.gy/nfCac.jpg OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: bem...@gmail.com I've got KMail connected to both Gmail and Exchange servers. When I receive mail with build-in images, they are displayed as attachments and in message's body there is only an empty frame. If launch kmail in console, I can see following errors every time I open message with such image: couldn't create slave: "Unable to create io-slave:\nklauncher said: Unknown protocol «cid».\n" If I open such message in message editor, images are displayed correctly. I'm used to face this bug also on OpenSuse, and now I'm getting it on ArchLinux. Reproducible: Always Steps to Reproduce: 1. Get e-mail with attached (build-in) image 2. Select this e-mail in message list 3. Look into message view section. Actual Results: Images are missing, there are only empty frames for them Expected Results: Images are displayed correctly -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359813] images inserted in mail with CID are not displayed
https://bugs.kde.org/show_bug.cgi?id=359813 Sergei Gureev changed: What|Removed |Added CC||bem...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Martin Droessler changed: What|Removed |Added CC||m...@martindroessler.de -- You are receiving this mail because: You are watching all bug changes.
[calligraflow] [Bug 359814] New: No text tool to be found
https://bugs.kde.org/show_bug.cgi?id=359814 Bug ID: 359814 Summary: No text tool to be found Product: calligraflow Version: 2.8.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: usability Assignee: yue@mail.com Reporter: j...@pearcey.net I cannot find any way to add text onto the flow diagram. I read somewhere that the text tool should be found either under the shape properties or else in the stencil box. Neither has the text tool. Reproducible: Always Steps to Reproduce: 1. Start Calligra flow 2. Add a shape onto the page 3. Select it and look for the text tool somewhere, anywhere in fact Actual Results: No text tool Expected Results: Expected to find a text tool None -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 359800] KWalletManager5 and some other apps using KWallet fails on dbus_connection_send_with_reply
https://bugs.kde.org/show_bug.cgi?id=359800 Mykola Krachkovsky changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Mykola Krachkovsky --- Sorry for false alarm. It looks like some glitch while transition from Qt 5.5 to Qt 5.6. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 344675] No menu items are displayed for Plugins
https://bugs.kde.org/show_bug.cgi?id=344675 --- Comment #11 from Mike --- I also really don't understand why this is unconfirmed because this bug is always present ! Meanwhile I am on Manjaro 15.12 Bellatrix and nothing changed. Even the unconfirmed status but it is confirmed by many people who are confronted with that problem. I use a distro like Arch / manjaro to be able to use a large repo of programpackages that could be easily installed by some sort of package manage because I'm not able to compile a program especially adapted to my needs because some dependencies are not fixed. We as user don't know the technical background and/or dont have the linux skills to compile programs. Or is that just because Gwenview won't be supported any more ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 359806] QML files for menu widgets are missing
https://bugs.kde.org/show_bug.cgi?id=359806 smihael changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from smihael --- The problem can be solved by following steps described at: http://jriddell.org/2016/02/23/kde-neon-comes-alive/ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 344675] No menu items are displayed for Plugins
https://bugs.kde.org/show_bug.cgi?id=344675 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #12 from Antonio Rojas --- (In reply to Peter DC from comment #10) > Fresh install of Kubuntu 15.10 for 64-bit with KDE Plasma 5.4.2 and same > issue : Gwenview has only minimal functionality, no rotate or crop for > example. How can I fix this ? (and how come the status is unconfirmed ? I > would like to start contributing to the Kubuntu community, but this thread > doesn't inspire me with confidence). This is a different unrelated issue that has been fixed long ago. Complain to your distribution for not delivering critical bug fixes to their users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359661] Digital clock is not updated consistently
https://bugs.kde.org/show_bug.cgi?id=359661 Don Jajo changed: What|Removed |Added CC||donjajo4...@gmail.com --- Comment #3 from Don Jajo --- Same issue here I use Debian Stretch and Plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 359815] New: Window is not maximized after exiting full screen mode
https://bugs.kde.org/show_bug.cgi?id=359815 Bug ID: 359815 Summary: Window is not maximized after exiting full screen mode Product: frameworks-kwidgetsaddons Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: aspotas...@gmail.com CC: kdelibs-b...@kde.org See "Steps to Reproduce". Reproducible: Always Steps to Reproduce: 1. Open an application that supports KF5::KWidgetsAddons' fullscreen mode toggle action, e.g. Kate or KDevelop. 2. Maximize the window. 3. Press Ctrl+Shift+F to enable fullscreen mode. 4. Press Ctrl+Shift+F again to disable fullscreen mode. Actual Results: After these steps the window is not maximized. Expected Results: The window should be maximized because it was maximized before going to full screen mode. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 359815] Window is not maximized after exiting full screen mode
https://bugs.kde.org/show_bug.cgi?id=359815 --- Comment #1 from Alexander Potashev --- Related: bug #343697 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 349291] Konqueror crashed when closing a tab with ark file as folder
https://bugs.kde.org/show_bug.cgi?id=349291 Anton Yablokov changed: What|Removed |Added CC||stsav...@mail.ru --- Comment #2 from Anton Yablokov --- I confirm the bug in Konqueror 4.14.2 with Ark 2.19. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 359815] Window is not maximized after exiting full screen mode
https://bugs.kde.org/show_bug.cgi?id=359815 Alexander Potashev changed: What|Removed |Added Version|unspecified |5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 271679] Digikam detects but does not recognize faces.
https://bugs.kde.org/show_bug.cgi?id=271679 Jan Schneider changed: What|Removed |Added CC||j...@horde.org --- Comment #29 from Jan Schneider --- Still doesn't work at all with 4.12.0. Face detection works, face recognition doesn't. It runs, and scans, and does its magic, but without any results, not even on almost identical images. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 359816] New: After opening notebook part of windows hide under task bar if they are maximized
https://bugs.kde.org/show_bug.cgi?id=359816 Bug ID: 359816 Summary: After opening notebook part of windows hide under task bar if they are maximized Product: Planet KDE Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ranveeraggar...@gmail.com Reporter: damian.tr...@gmail.com When I close my notebook cover and open it back while I have maximized windows (ex. Opera or Android Studio) after open small part of bottom part of window is hiding under task bar. Bug is until I reboot a notebook. Reproducible: Always Steps to Reproduce: 1.Open some windows and maximize them 2.Close notebook screencover and open it Actual Results: Bottom parts of windows are hidden under taskabar. Expected Results: I should see whole window of application -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 271679] Digikam detects but does not recognize faces.
https://bugs.kde.org/show_bug.cgi?id=271679 --- Comment #30 from caulier.gil...@gmail.com --- Try with last 4.14.0... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 359807] Gletters - Keyboard does not work immediately in Simple Letters by default choosing keyboard
https://bugs.kde.org/show_bug.cgi?id=359807 Jazeix Johnny changed: What|Removed |Added CC||jaz...@gmail.com --- Comment #2 from Jazeix Johnny --- Hi, to be sure, it is this version: http://gcompris.net/download/beta/gcompris-qt-0.60-win32.exe or the Gtk+ version ? If you don't know, does the application look like: http://gcompris.net/screenshots-en.html (Gtk+ version) or https://play.google.com/store/apps/details?id=net.gcompris (KDE/Qt version). Johnny -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349778] The escape sequences to terminate a telnet session don't work
https://bugs.kde.org/show_bug.cgi?id=349778 Joan changed: What|Removed |Added Severity|grave |normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346638] Panels which are configured as "Auto hide" are shown when change window focus
https://bugs.kde.org/show_bug.cgi?id=346638 --- Comment #6 from Viorel-Cătălin Răpițeanu --- > I can't reproduce the problem on my dev system. I'm also unable to reproduce it. I believe that this bug can be closed... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359817] New: digiKam crashed while scanning faces
https://bugs.kde.org/show_bug.cgi?id=359817 Bug ID: 359817 Summary: digiKam crashed while scanning faces Product: digikam Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: mikebi...@aol.com Application: digikam (4.12.0) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 4.2.0-27-generic i686 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: scanning (and detecting) faces from photos on an NFS share. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xacff99c0 (LWP 17936))] Thread 19 (Thread 0xacd12b40 (LWP 17953)): #0 0xb7793be8 in __kernel_vsyscall () #1 0xb42c53db in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xafcf91a3 in ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0 #3 0xb39fb1aa in start_thread (arg=0xacd12b40) at pthread_create.c:333 #4 0xb42cffde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 18 (Thread 0xab6fcb40 (LWP 17955)): #0 0xb7793be8 in __kernel_vsyscall () #1 0xb3a0025c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb42dccf6 in __pthread_cond_wait (cond=0x8d1bc28, mutex=0x8d1bc10) at forward.c:149 #3 0xb4625232 in QWaitConditionPrivate::wait (time=4294967295, this=0x8d1bc10) at thread/qwaitcondition_unix.cpp:86 #4 QWaitCondition::wait (this=0x8d1bb84, mutex=0x8d1bb80, time=4294967295) at thread/qwaitcondition_unix.cpp:158 #5 0x0822567e in Digikam::ScanController::run (this=0x8cfef38) at /build/digikam-tUtjhi/digikam-4.12.0/core/app/database/scancontroller.cpp:725 #6 0xb4624c5e in QThreadPrivate::start (arg=0x8cfef38) at thread/qthread_unix.cpp:349 #7 0xb39fb1aa in start_thread (arg=0xab6fcb40) at pthread_create.c:333 #8 0xb42cffde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 17 (Thread 0xaacffb40 (LWP 17956)): #0 0xb7793be8 in __kernel_vsyscall () #1 0xb42bf75b in read () at ../sysdeps/unix/syscall-template.S:81 #2 0xb316c005 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb31269aa in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb3126eb1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb3127054 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb477527c in QEventDispatcherGlib::processEvents (this=0xaa300468, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #7 0xb4740daf in QEventLoop::processEvents (this=0xaacfefe4, flags=...) at kernel/qeventloop.cpp:149 #8 0xb474113e in QEventLoop::exec (this=0xaacfefe4, flags=...) at kernel/qeventloop.cpp:204 #9 0xb462210b in QThread::exec (this=0x8d1f010) at thread/qthread.cpp:538 #10 0xb4720576 in QInotifyFileSystemWatcherEngine::run (this=0x8d1f010) at io/qfilesystemwatcher_inotify.cpp:265 #11 0xb4624c5e in QThreadPrivate::start (arg=0x8d1f010) at thread/qthread_unix.cpp:349 #12 0xb39fb1aa in start_thread (arg=0xaacffb40) at pthread_create.c:333 #13 0xb42cffde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 16 (Thread 0xaa2ffb40 (LWP 17963)): #0 0xb7793be8 in __kernel_vsyscall () #1 0xb3a0025c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb42dccf6 in __pthread_cond_wait (cond=0x8f59ab8, mutex=0x8f59aa0) at forward.c:149 #3 0xb4625232 in QWaitConditionPrivate::wait (time=4294967295, this=0x8f59aa0) at thread/qwaitcondition_unix.cpp:86 #4 QWaitCondition::wait (this=0x8f57840, mutex=0x8f5783c, time=4294967295) at thread/qwaitcondition_unix.cpp:158 #5 0xb700c92e in Digikam::ParkingThread::run (this=0x8f57830) at /build/digikam-tUtjhi/digikam-4.12.0/core/libs/threads/threadmanager.cpp:119 #6 0xb4624c5e in QThreadPrivate::start (arg=0x8f57830) at thread/qthread_unix.cpp:349 #7 0xb39fb1aa in start_thread (arg=0xaa2ffb40) at pthread_create.c:333 #8 0xb42cffde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 15 (Thread 0x9707fb40 (LWP 18041)): #0 0xb4774bd4 in idleTimerSourceCheck (source=0xa9903700) at kernel/qeventdispatcher_glib.cpp:229 #1 0xb31268da in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb3126eb1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3127054 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb477527c in QEventDispatcherGlib::processEvents (this=0xa9902ab0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0xb4740daf in QEventLoop::processEvents (this=0x9707efd4, flags=...) at kernel/qeventloop.cpp:149 #6 0xb474113e in QEventLoop::exec (this=0x9707efd4, flags=...) at kern
[konqueror] [Bug 359818] New: Konqueror plante en voulant ajouter services
https://bugs.kde.org/show_bug.cgi?id=359818 Bug ID: 359818 Summary: Konqueror plante en voulant ajouter services Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: pascal.thom...@hesge.ch Application: konqueror (4.14.17) KDE Platform Version: 4.14.17 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Dans Konfiguration -> Gestion de fichiers -> Service -> Télécharger de nouveau services: Le dialogue affiche "Fichiers de configuration introuvable service.knsrc". En remplissant le champs "Recherche", Konqueror plante. The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f25efcf57c0 (LWP 29443))] Thread 5 (Thread 0x7f25d0e8c700 (LWP 29444)): #0 0x7f25ef572c8d in read () at /lib64/libc.so.6 #1 0x7f25e89e6b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f25e89a5999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f25e89a5df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f25e89a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f25ec1aafde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f25ec17cd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f25ec17d045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7f25ec07a4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7f25ec07cbbf in () at /usr/lib64/libQtCore.so.4 #10 0x7f25e9de60a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f25ef57efed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f25c3fff700 (LWP 29452)): #0 0x7f25ef576bbd in poll () at /lib64/libc.so.6 #1 0x7f25e89a5e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f25e89a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f25ec1aafde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f25ec17cd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f25ec17d045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f25ec07a4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f25ec15e653 in () at /usr/lib64/libQtCore.so.4 #8 0x7f25ec07cbbf in () at /usr/lib64/libQtCore.so.4 #9 0x7f25e9de60a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f25ef57efed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f25c359c700 (LWP 29453)): #0 0x7f25e9dea03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f25d9a6feb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f25d9a6fee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f25e9de60a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f25ef57efed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f25c1e48700 (LWP 29454)): #0 0x7f25ef576bbd in poll () at /lib64/libc.so.6 #1 0x7f25e89a5e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f25e89a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f25ec1aafde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f25ec17cd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f25ec17d045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f25ec07a4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f25ec07cbbf in () at /usr/lib64/libQtCore.so.4 #8 0x7f25e9de60a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f25ef57efed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f25efcf57c0 (LWP 29443)): [KCrash Handler] #6 0x7f25d73a60a0 in () at /usr/lib64/libknewstuff3.so.4 #7 0x7f25d73add94 in () at /usr/lib64/libknewstuff3.so.4 #8 0x7f25d739ef8e in () at /usr/lib64/libknewstuff3.so.4 #9 0x7f25d73a0dc9 in () at /usr/lib64/libknewstuff3.so.4 #10 0x7f25ec1920fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #11 0x7f25ecf83452 in QLineEdit::textChanged(QString const&) () at /usr/lib64/libQtGui.so.4 #12 0x7f25ecf83829 in () at /usr/lib64/libQtGui.so.4 #13 0x7f25ec1920fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #14 0x7f25ed1d42c5 in QLineControl::textChanged(QString const&) () at /usr/lib64/libQtGui.so.4 #15 0x7f25ecf88e6d in QLineControl::finishChange(int, bool, bool) () at /usr/
[digikam] [Bug 359817] digiKam crashed while scanning faces
https://bugs.kde.org/show_bug.cgi?id=359817 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Please try with last 4.14.0... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 350075] Import of recipes takes too long
https://bugs.kde.org/show_bug.cgi?id=350075 José Manuel Santamaría Lema changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krec ||ipes/aea810e290ce605c0255ae ||a56c9652744a8244ae Resolution|--- |FIXED --- Comment #2 from José Manuel Santamaría Lema --- Git commit aea810e290ce605c0255aea56c9652744a8244ae by José Manuel Santamaría Lema. Committed on 26/02/2016 at 12:38. Pushed by joselema into branch 'master'. Use transactions when exporting recipes. This reduces a lot the time to get a large number of recipes into the database. M +18 -3src/backends/qsqlrecipedb.cpp M +4-0src/backends/qsqlrecipedb.h M +5-0src/backends/recipedb.h M +12 -0src/importers/baseimporter.cpp http://commits.kde.org/krecipes/aea810e290ce605c0255aea56c9652744a8244ae -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 313793] Consistency checker is reporting spurious errors
https://bugs.kde.org/show_bug.cgi?id=313793 Thomas Baumgart changed: What|Removed |Added CC||debrabant.phili...@free.fr --- Comment #43 from Thomas Baumgart --- *** Bug 359695 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 359695] New file, new bank account, first operation : old date is invalid
https://bugs.kde.org/show_bug.cgi?id=359695 Thomas Baumgart changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Thomas Baumgart --- The problems around the account opening date esp. with categories have been addressed in master already. So these problems are already fixed in the current development version. See #313793 at https://bugs.kde.org/show_bug.cgi?id=313793#c41 for more details. So I mark this as a duplicate to it. *** This bug has been marked as a duplicate of bug 313793 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 359819] New: Add support for more partition types
https://bugs.kde.org/show_bug.cgi?id=359819 Bug ID: 359819 Summary: Add support for more partition types Product: partitionmanager Version: 2.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: richard.l...@gmail.com Due to an installation of linux on BIOS system with GPT partitioning, I noticed that the "Bios boot" partition type is not supported by KPM. It wrongly lists the partition as ext4 partition. I created the "bios boot" partition with fdisk, which also gives a list of known partition types: # fdisk /dev/sda Welcome to fdisk (util-linux 2.27). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): l 1 EFI System C12A7328-F81F-11D2-BA4B-00A0C93EC93B 2 MBR partition scheme 024DEE41-33E7-11D3-9D69-0008C781F39F 3 Intel Fast Flash D3BFE2DE-3DAF-11DF-BA40-E3A556D89593 4 BIOS boot 21686148-6449-6E6F-744E-656564454649 5 Sony boot partitionF4019732-066E-4E12-8273-346C5641494F 6 Lenovo boot partition BFBFAFE7-A34F-448A-9A5B-6213EB736C22 7 PowerPC PReP boot 9E1A2D38-C612-4316-AA26-8B49521E5A8B 8 ONIE boot 7412F7D5-A156-4B13-81DC-867174929325 9 ONIE configD4E6E2CD-4469-46F3-B5CB-1BFF57AFC149 10 Microsoft reserved E3C9E316-0B5C-4DB8-817D-F92DF00215AE 11 Microsoft basic data EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 12 Microsoft LDM metadata 5808C8AA-7E8F-42E0-85D2-E1E90434CFB3 13 Microsoft LDM data AF9B60A0-1431-4F62-BC68-3311714A69AD 14 Windows recovery environment DE94BBA4-06D1-4D40-A16A-BFD50179D6AC 15 IBM General Parallel Fs37AFFC90-EF7D-4E96-91C3-2D7AE055B174 16 Microsoft Storage Spaces E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D 17 HP-UX data 75894C1E-3AEB-11D3-B7C1-7B03A000 18 HP-UX service E2A1E728-32E3-11D6-A682-7B03A000 19 Linux swap 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F 20 Linux filesystem 0FC63DAF-8483-4772-8E79-3D69D8477DE4 21 Linux server data 3B8F8425-20E0-4F3B-907F-1A25A76F98E8 22 Linux root (x86) 44479540-F297-41B2-9AF7-D131D5F0458A 23 Linux root (ARM) 69DAD710-2CE4-4E3C-B16C-21A1D49ABED3 24 Linux root (x86-64)4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709 25 Linux root (ARM-64)B921B045-1DF0-41C3-AF44-4C6F280D3FAE 26 Linux reserved 8DA63339-0007-60C0-C436-083AC8230908 27 Linux home 933AC7E1-2EB4-4F13-B844-0E14E2AEF915 28 Linux RAID A19D880F-05FC-4D3B-A006-743F0F84911E 29 Linux extended bootBC13C2FF-59E6-4262-A352-B275FD6F7172 30 Linux LVM E6D6D379-F507-44C2-A23C-238F2A3DF928 31 FreeBSD data 516E7CB4-6ECF-11D6-8FF8-00022D09712B 32 FreeBSD boot 83BD6B9D-7F41-11DC-BE0B-001560B84F0F 33 FreeBSD swap 516E7CB5-6ECF-11D6-8FF8-00022D09712B 34 FreeBSD UFS516E7CB6-6ECF-11D6-8FF8-00022D09712B 35 FreeBSD ZFS516E7CBA-6ECF-11D6-8FF8-00022D09712B 36 FreeBSD Vinum 516E7CB8-6ECF-11D6-8FF8-00022D09712B 37 Apple HFS/HFS+ 48465300--11AA-AA11-00306543ECAC 38 Apple UFS 55465300--11AA-AA11-00306543ECAC 39 Apple RAID 52414944--11AA-AA11-00306543ECAC 40 Apple RAID offline 52414944-5F4F-11AA-AA11-00306543ECAC 41 Apple boot 426F6F74--11AA-AA11-00306543ECAC 42 Apple label4C616265-6C00-11AA-AA11-00306543ECAC 43 Apple TV recovery 5265636F-7665-11AA-AA11-00306543ECAC 44 Apple Core storage 53746F72-6167-11AA-AA11-00306543ECAC 45 Solaris boot 6A82CB45-1DD2-11B2-99A6-080020736631 46 Solaris root 6A85CF4D-1DD2-11B2-99A6-080020736631 47 Solaris /usr & Apple ZFS 6A898CC3-1DD2-11B2-99A6-080020736631 48 Solaris swap 6A87C46F-1DD2-11B2-99A6-080020736631 49 Solaris backup 6A8B642B-1DD2-11B2-99A6-080020736631 50 Solaris /var 6A8EF2E9-1DD2-11B2-99A6-080020736631 51 Solaris /home 6A90BA39-1DD2-11B2-99A6-080020736631 52 Solaris alternate sector 6A9283A5-1DD2-11B2-99A6-080020736631 53 Solaris reserved 1 6A945A3B-1DD2-11B2-99A6-080020736631 54 Solaris reserved 2 6A9630D1-1DD2-11B2-99A6-080020736631 55 Solaris reserved 3 6A980767-1DD2-11B2-99A6-080020736631 56 Solaris reserved 4 6A96237F-1DD2-11B2-99A6-080020736631 57
[partitionmanager] [Bug 359819] Add support for more partition types
https://bugs.kde.org/show_bug.cgi?id=359819 Andrius Štikonas changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359820] New: Nvidia X server X Server Display Configuration Crashes KDE
https://bugs.kde.org/show_bug.cgi?id=359820 Bug ID: 359820 Summary: Nvidia X server X Server Display Configuration Crashes KDE Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: morbid@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Simply switching the one monitor off causes KDE to crash. There are many other issues with KDE and Nvidia X server, some are way too inconsistent to report. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7feb600a0800 (LWP 1776))] Thread 23 (Thread 0x7feb480ce700 (LWP 1777)): #0 0x7feb595c4bbd in poll () at /lib64/libc.so.6 #1 0x7feb5e4f1422 in () at /usr/lib64/libxcb.so.1 #2 0x7feb5e4f300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7feb4a8513c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7feb45502700 (LWP 1791)): #0 0x7feb595c0c8d in read () at /lib64/libc.so.6 #1 0x7feb51762f45 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #2 0x7feb55ce7b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb55ca6999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7feb55ca6df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7feb5cfa3df8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #11 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7feb35368700 (LWP 1811)): #0 0x7feb595c4bbd in poll () at /lib64/libc.so.6 #1 0x7feb55ca6e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7feb5cfa3df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7feb2fa78700 (LWP 1812)): #0 0x7feb55ce8cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7feb55ca6e4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7feb5cfa3df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7feb2e1a8700 (LWP 1816)): #0 0x7feb58dd203f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7feb5f77586b in () at /usr/lib64/libQt5Script.so.5 #2 0x7feb5f775899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7feaa730d700 (LWP 1818)): #0 0x7feb595c4bbd in poll () at /lib64/libc.so.6 #1 0x7feb55ca6e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6
[plasmashell] [Bug 359812] plasmashell crashes when you try to establish a new network connection
https://bugs.kde.org/show_bug.cgi?id=359812 Marco Martin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 342195 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 342195] plasma-nm + plasma panel crashed after disconnection from usb modem
https://bugs.kde.org/show_bug.cgi?id=342195 Marco Martin changed: What|Removed |Added CC||registrazi...@fracassa.org --- Comment #2 from Marco Martin --- *** Bug 359812 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359804] Plasma crash
https://bugs.kde.org/show_bug.cgi?id=359804 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||notm...@gmail.com Resolution|--- |BACKTRACE --- Comment #1 from Marco Martin --- needs debug symbols of plasma-framework -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358370] Crash when using NoMachine to remote login.
https://bugs.kde.org/show_bug.cgi?id=358370 Marco Martin changed: What|Removed |Added CC||henr...@yahoo.fr --- Comment #1 from Marco Martin --- *** Bug 359799 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359799] Crash when using Eclipse Neon (GTK 3)
https://bugs.kde.org/show_bug.cgi?id=359799 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 358370 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359793] Folderview context menu crash
https://bugs.kde.org/show_bug.cgi?id=359793 Marco Martin changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|h...@kde.org Component|general |Folder CC||notm...@gmail.com Summary|Dophin crash|Folderview context menu ||crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359821] New: Time chooser of wallpaper change causes crash of Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=359821 Bug ID: 359821 Summary: Time chooser of wallpaper change causes crash of Plasma desktop Product: systemsettings Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: guoyunhebr...@gmail.com When you config desktop wallpaper and set a time to change wallpaper among a list of files, you can see here is a time picker. http://i.imgur.com/DR2Unf8.png Problems: 1. If you increase seconds from 0:0:59, the time suddenly becomes 24:45:0, not 0:1:0 2. Users can type 60 in seconds. But if now you change hour and minute to 0, it will crash or freeze the settings window. 3. If you set 0:1:0, it always change it to 0:1:1 next time you open settings window. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359781] Plasma crash on clicking "Disable this popup"
https://bugs.kde.org/show_bug.cgi?id=359781 Marco Martin changed: What|Removed |Added Resolution|--- |BACKTRACE CC||notm...@gmail.com Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Marco Martin --- needs debug symbols of frameworks and plasma-workspace installed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 Marco Martin changed: What|Removed |Added CC||morbid@hotmail.com --- Comment #38 from Marco Martin --- *** Bug 359820 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359820] Nvidia X server X Server Display Configuration Crashes KDE
https://bugs.kde.org/show_bug.cgi?id=359820 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 351777 *** -- You are receiving this mail because: You are watching all bug changes.
[picmi] [Bug 359822] New: Link to manual opens an error page
https://bugs.kde.org/show_bug.cgi?id=359822 Bug ID: 359822 Summary: Link to manual opens an error page Product: picmi Version: 2.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jakob.gru...@gmail.com Reporter: tipos...@tiscali.it This one. https://docs.kde.org/index.php?branch=stable5&language=it_IT&application=picmi&path=/ Don't put the broken link inside the application please. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 359513] Network app constantly requires manual input of wireless network passwords
https://bugs.kde.org/show_bug.cgi?id=359513 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED CC||sit...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #3 from Harald Sitter --- Thanks for the information. I am marking this resolved then. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359823] New: Scrolling in message view window only updates window partially
https://bugs.kde.org/show_bug.cgi?id=359823 Bug ID: 359823 Summary: Scrolling in message view window only updates window partially Product: kmail2 Version: 5.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: stephan.diestelho...@gmail.com After a while of using kmail (5.0.2 KDE Frameworks: 5.15.0, Qt 5.4.2), it seems that the message preview below the message list stops scrolling properly. I can still scroll, but if I scroll down, only the lower ~50 pixels (~2 lines of text) get updated. When I scroll up, it is only the top 50 pixels in that window. The rest stays exactly flat. I have tried disabling Desktop Effects (Alt + Shift + F12), but that does not resolve the problem once it has occurred. I also played with the KDE compositor settings and selected all different tearing options, GL versions etc, but nothing helped. The only way to fix this seems to be to restart KMail for now. Then it continues working for a while, I have not yet identified when this happens. I usually can work for (felt) 30 mins to several hours until this turns up again. This happens for both HTML and text emails. Going to the next message will render the full view correctly. Resizing the preview pane does not have an effect, other than temporarily rendering the screen correctly. Reproducible: Always Steps to Reproduce: 1. browse emails and use the preview window and scroll 2. do this for a while 3. observe the scrolling not affecting the middle of the window Actual Results: the middle of the rendered email does not move on the screen Expected Results: the entire message scrolls up and down kubuntu package: 4:15.08.2-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 351232] Konsole crashed after exiting
https://bugs.kde.org/show_bug.cgi?id=351232 --- Comment #7 from Pawel Kraszewski --- Got it. Hanging kosole dwells in NVidia tls cleanup code on libc's exit() (I have no debug symbols for NVidia, so no useful stacktrace). It appears to happen generally after konsole has done all the cleaning. OTOH, konsole is the ONLY app doing that. It looks both cases (crash/hang) are somehow related to graphics subroutines. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355354] Swap CapsLock and Escape feature disabled spontaneously
https://bugs.kde.org/show_bug.cgi?id=355354 Stephan Diestelhorst changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com --- Comment #1 from Stephan Diestelhorst --- This might be related to #356851 and to my recent report Kubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356851] System keyboard layout ctrl capslock requires re-apply after log out
https://bugs.kde.org/show_bug.cgi?id=356851 Stephan Diestelhorst changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com --- Comment #1 from Stephan Diestelhorst --- I have a similar problem and investigated it here: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293 Also, bug 355354 might be related. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 338361] After swapping Esc and Caps Lock and assigning new action to shortcut which includes Esc, it doesn't work.
https://bugs.kde.org/show_bug.cgi?id=338361 Stephan Diestelhorst changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com --- Comment #3 from Stephan Diestelhorst --- Maybe similar to bug 356851 and bug 355354? I also have a similar bug with detaild log output here: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355354] Swap CapsLock and Escape feature disabled spontaneously
https://bugs.kde.org/show_bug.cgi?id=355354 --- Comment #2 from Stephan Diestelhorst --- I meant bug 356851. If I look at my log output, it seems that sometimes (for me it is after resume and undocking / docking) the keyboard settings get reset from symbols: pc+us+inet(evdev) geometry: pc(pc105) to symbols: pc+us+inet(evdev)+capslock(escape) geometry: pc(pc101) My config in KDE suggests the latter (pc101) and the caps as an additional escape. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 359824] New: Konqueror crash when restoring a session
https://bugs.kde.org/show_bug.cgi?id=359824 Bug ID: 359824 Summary: Konqueror crash when restoring a session Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: tom.hilin...@comcast.net Application: konqueror (4.14.17) KDE Platform Version: 4.14.17 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: System was restoring a konqueror session at startup, after login. -- Backtrace: Application: Konqueror (konqueror), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c5badc7c0 (LWP 1928))] Thread 24 (Thread 0x7f2c4309f700 (LWP 1931)): #0 0x7f2c55bd103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2c48075eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f2c48075ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f2c01b52700 (LWP 1943)): #0 0x7f2c5b359c8d in read () at /lib64/libc.so.6 #1 0x7f2c547cdb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2c5478c999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2c5478cdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2c5478cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2c57f91fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f2c57f63d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f2c57f64045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7f2c57e614df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7f2c57e63bbf in () at /usr/lib64/libQtCore.so.4 #10 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f2bfbfff700 (LWP 1971)): #0 0x7f2c55bd103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2c47de8b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f2c4809da06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f2be00f5700 (LWP 2022)): #0 0x7f2c5b359c8d in read () at /lib64/libc.so.6 #1 0x7f2c547cdb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2c5478c999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2c5478cdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2c5478d19a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2be31b1426 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7f2c547b1f65 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f2bdf4b4700 (LWP 2023)): #0 0x7f2c5b359c8d in read () at /lib64/libc.so.6 #1 0x7f2c547cdb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2c5478c999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2c5478cdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2c5478cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2c5478cfb9 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f2c547b1f65 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f2bde3a3700 (LWP 2026)): #0 0x7f2c55bd103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bde40ad79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f2bde40b819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f2bddba2700 (LWP 2027)): #0 0x7f2c55bd103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bde40ad79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f2bde40b819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f2c55bcd0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2c5b365fed in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f2bdd3a1700 (LWP 2028)): #0 0x7f2c55bd103f in pthread_cond_wa
[frameworks-frameworkintegration] [Bug 359758] Dolphin crashes on exit when you specify the --icon command line parameter
https://bugs.kde.org/show_bug.cgi?id=359758 --- Comment #4 from Wolfgang Bauer --- (In reply to Frank Reininghaus from comment #3) > https://quickgit.kde.org/?p=frameworkintegration. > git&a=commit&h=7bbc6c98222eb6db988ed78fc334ad9eef0bb6fb > > Reverting that commit fixes the crash for me. Yes, I found this out myself too meanwhile. Btw, I was wrong, sorry. The crash does not only happen with dolphin, but also other applications (not all though, I couldn't reproduce it with the ones I tried earlier). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359756] Crash that unlocks the session
https://bugs.kde.org/show_bug.cgi?id=359756 Daniël Huisman changed: What|Removed |Added Attachment #97551|text/x-log |text/txt mime type|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359825] New: Plasma crashed without any specific window action
https://bugs.kde.org/show_bug.cgi?id=359825 Bug ID: 359825 Summary: Plasma crashed without any specific window action Product: plasmashell Version: 5.5.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jsm...@allworx.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.3.4-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: Running Fedora 23 with Plasma in a VirtualBox hosted on Windows 7. Plasma crashed while I was not actively in the VirtualBox (window had been minimized, when I reopened it, I had the crash wwindow). This happensto me multiple times a day - not always when VirtualBox is minimized. I cannot link it to any specific user action - sometime just moving the mouse between windows when this occurs. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f1be03e2940 (LWP 21330))] Thread 12 (Thread 0x7f1bc0492700 (LWP 21352)): #0 0x7f1bd7db4fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1bde26e272 in poll (__timeout=-1, __nfds=1, __fds=0x7f1bc0491b80) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x55e50e4ab900, cond=cond@entry=0x55e50e4ab940, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7f1bde26fee7 in xcb_wait_for_event (c=0x55e50e4ab900) at xcb_in.c:693 #4 0x7f1bc241cda9 in QXcbEventReader::run (this=0x55e50e4b9e50) at qxcbconnection.cpp:1255 #5 0x7f1bd89bd3de in QThreadPrivate::start (arg=0x55e50e4b9e50) at thread/qthread_unix.cpp:331 #6 0x7f1bd70f860a in start_thread (arg=0x7f1bc0492700) at pthread_create.c:334 #7 0x7f1bd7dc0a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f1bbda41700 (LWP 21355)): #0 0x7f1bd7db4fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1bd32da16c in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f1bd32da27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1bd8bf4ecb in QEventDispatcherGlib::processEvents (this=0x7f1bb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f1bd8b9beca in QEventLoop::exec (this=this@entry=0x7f1bbda40c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f1bd89b8434 in QThread::exec (this=this@entry=0x55e50e5d1310) at thread/qthread.cpp:503 #6 0x7f1bdcd059b5 in QQmlThreadPrivate::run (this=0x55e50e5d1310) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7f1bd89bd3de in QThreadPrivate::start (arg=0x55e50e5d1310) at thread/qthread_unix.cpp:331 #8 0x7f1bd70f860a in start_thread (arg=0x7f1bbda41700) at pthread_create.c:334 #9 0x7f1bd7dc0a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f1bb5306700 (LWP 21362)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1bb6853a23 in cnd_wait (mtx=0x55e50e6e7850, cond=0x55e50e6e7878) at ../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0x55e50e6e7850) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 thread_function (init_data=init_data@entry=0x55e50e6e77a8) at lp_rast.c:805 #4 0x7f1bb6853887 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7f1bd70f860a in start_thread (arg=0x7f1bb5306700) at pthread_create.c:334 #6 0x7f1bd7dc0a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f1bb4b05700 (LWP 21363)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1bb6853a23 in cnd_wait (mtx=0x55e50e6e79b8, cond=0x55e50e6e79e0) at ../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0x55e50e6e79b8) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 thread_function (init_data=init_data@entry=0x55e50e6e7910) at lp_rast.c:805 #4 0x7f1bb6853887 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7f1bd70f860a in start_thread (arg=0x7f1bb4b05700) at pthread_create.c:334 #6 0x7f1bd7dc0a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f1badb2c700 (LWP 21364)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1bb6853a23 in cnd_wait (mtx=0x55e50
[digikam] [Bug 271679] Digikam detects but does not recognize faces.
https://bugs.kde.org/show_bug.cgi?id=271679 --- Comment #31 from Jan Schneider --- Is there some backport to Kubuntu? The official backports on launchpad are outdated badly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359826] New: Plasma crash when opening classic application menu
https://bugs.kde.org/show_bug.cgi?id=359826 Bug ID: 359826 Summary: Plasma crash when opening classic application menu Product: plasmashell Version: 5.5.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: b...@michaudtech.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.3.5-300.fc23.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Clicked on the menu and was hunting through the program categories - drawing of sub-menus seemed to hang for about a second (stopped with just menu borders drawn, no contents), then Plasma crashed and restarted. This happens occasionally (typically at least once per day). The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f733ef6d940 (LWP 3583))] Thread 36 (Thread 0x7f731dda4700 (LWP 3586)): #0 0x7f7336893fdd in poll () from /lib64/libc.so.6 #1 0x7f733cdcf272 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f733cdd0ee7 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f7320b8dda9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f73374b03de in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f7335bcc60a in start_thread () from /lib64/libpthread.so.0 #6 0x7f733689fa4d in clone () from /lib64/libc.so.6 Thread 35 (Thread 0x7f7316fac700 (LWP 3587)): #0 0x7f7331cf3719 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f7331caf12e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f7331caf27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f73376e7ecb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f733768eeca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f73374ab434 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f733b84e9b5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f73374b03de in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f7335bcc60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f733689fa4d in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7f730e964700 (LWP 3589)): #0 0x7f7331cf3734 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f7331caeba9 in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7f7331caf110 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f7331caf27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f73376e7ecb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f733768eeca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f73374ab434 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f733b84e9b5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #8 0x7f73374b03de in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f7335bcc60a in start_thread () from /lib64/libpthread.so.0 #10 0x7f733689fa4d in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f730cee4700 (LWP 3590)): #0 0x7f7331cf3734 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f7331cae9e9 in g_main_context_query () from /lib64/libglib-2.0.so.0 #2 0x7f7331caf0e7 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f7331caf27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f73376e7ecb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f733768eeca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f73374ab434 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f733b84e9b5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #8 0x7f73374b03de in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f7335bcc60a in start_thread () from /lib64/libpthread.so.0 #10 0x7f733689fa4d in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f73075dc700 (LWP 3593)): #0 0x7f7335bd1b10 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f733e6e2514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f733e6e2559 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f7335bcc60a in start_thread () from /lib64/libpthread.so.0 #4 0x7f733689fa4d in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f727fac4700 (LW
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #25 from kuanyui --- (In reply to Jim Duchek from comment #24) > Is anyone from KDE ever going to fix this? It's literally a one-line fix > (see my comment from September). I suppose I'm going to have to go through > the process of submitting a patch officially, I hate to go through all that > effort for a one line fix. This bug is a daily frustration though. Jim Duchek++ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359828] New: Plasma crash during normal desktop work (external monitor connected via Display Port)
https://bugs.kde.org/show_bug.cgi?id=359828 Bug ID: 359828 Summary: Plasma crash during normal desktop work (external monitor connected via Display Port) Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: raf...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Normal desktop operation. I was writing a document with Libre Office (not connected with the bug) when plasma crash occured. There was couple other windows opened like Dolphin anf FireFox, but nothing unusual. My laptop (AUSUS Ux 303 LN) is connected with external monitor via Display Port (laptop screen is closed). The system was using Intel integrated video card (Kernel driver in use: i915) The crash can be reproduced sometimes. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7bf2cba7c0 (LWP 19529))] Thread 16 (Thread 0x7f7bdc750700 (LWP 19533)): #0 0x7f7bec1e6bbd in poll () at /lib64/libc.so.6 #1 0x7f7bf1113422 in () at /usr/lib64/libxcb.so.1 #2 0x7f7bf111500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f7bde8a13c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f7bec8df32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7beb9f00a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7bec1eefed in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f7bd9b27700 (LWP 19538)): #0 0x7f7bec1e6bbd in poll () at /lib64/libc.so.6 #1 0x7f7be88c8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7be88c8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7becb11d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f7becab8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7bec8da61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f7befbc5df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f7bec8df32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f7beb9f00a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7bec1eefed in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f7bc8b45700 (LWP 19570)): #0 0x7f7bec1e6bbd in poll () at /lib64/libc.so.6 #1 0x7f7be88c8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7be88c8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7becb11d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f7becab8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7bec8da61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f7befbc5df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f7bec8df32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f7beb9f00a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7bec1eefed in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f7bc3257700 (LWP 19571)): #0 0x7f7bec1fb622 in __libc_disable_asynccancel () at /lib64/libc.so.6 #1 0x7f7bec1e2c99 in read () at /lib64/libc.so.6 #2 0x7f7be8909b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7be88c8999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7be88c8df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f7be88c8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f7becb11d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f7becab8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f7bec8da61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f7befbc5df8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f7bec8df32f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f7beb9f00a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f7bec1eefed in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f7bc1beb700 (LWP 19583)): #0 0x7f7beb9f403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7bf239786b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f7bf2397899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f7beb9f00a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f7bec1eefed in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f7b3a575700 (LWP 19610)): #0 0x7f7bec1e6bbd in poll () at /lib64/libc.so.6 #1 0x7f7be88c8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7be88c8f7c in g_main_context_iteration
[kdenlive] [Bug 359827] New: 0.9.6 4.13.3, Kubuntu packages - RAM SATURATION WHILE RENDERING HDV VIDEO
https://bugs.kde.org/show_bug.cgi?id=359827 Bug ID: 359827 Summary: 0.9.6 4.13.3, Kubuntu packages - RAM SATURATION WHILE RENDERING HDV VIDEO Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: yuri.se...@gmail.com Created attachment 97562 --> https://bugs.kde.org/attachment.cgi?id=97562&action=edit ram saturation after 10 seconds that the rendering has begun Good day, I am presently using Kdenlive 0.9.6 on UbuntuStudio 14.04. After I start the rendering with AVCHD 1080 50i camera file (Sony HDR-CX100), to HDV PAL 1080 50i, i can clearly see in system monitor that RAM get full (till100%) meanwhile SWAP file is not used at all. (system ram 8gb - swap 8 gb). Computer finally get stuck. This problem doesn't happen if I use other other codec to render video, like H.264 or MPEG-2 or MEPG-4. Note about picture in attachment: if I do not stop manually the rendering process, the memory fill until the computer get stuck. In the proposed trend(ram is in violet colour), I have stopped manually the rendering in order to be able to take a picture of the screen. Could you help me to fix this problem? Best regards. Yuri -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359793] Folderview context menu crash
https://bugs.kde.org/show_bug.cgi?id=359793 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Eike Hein --- Backtrace is incomplete, please get debug symbols for KIO and crash again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359618] folder view in panel: much too small fixed icon size, no resizing anymore
https://bugs.kde.org/show_bug.cgi?id=359618 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-desktop/28aae4bc188c8c89 ||dbb00cf060aa34472787355c Version Fixed In||5.6.0 Status|REOPENED|RESOLVED --- Comment #5 from Kai Uwe Broulik --- Git commit 28aae4bc188c8c89dbb00cf060aa34472787355c by Kai Uwe Broulik. Committed on 26/02/2016 at 15:19. Pushed by broulik into branch 'master'. [FolderView] Allow chosing list or icon view in popup While I really like the list view for the popup, there might be cases where you prefer to see larger thumbnails. This patch allows to choose between the default list view and the icon view mode with cascading popups identical to what you get on the desktop. FIXED-IN: 5.6.0 Differential Revision: https://phabricator.kde.org/D1021 M +3-0containments/desktop/package/contents/config/main.xml M +18 -2containments/desktop/package/contents/ui/ConfigIcons.qml M +63 -30 containments/desktop/package/contents/ui/FolderItemDelegate.qml M +8-8containments/desktop/package/contents/ui/FolderView.qml M +32 -24 containments/desktop/package/contents/ui/main.qml http://commits.kde.org/plasma-desktop/28aae4bc188c8c89dbb00cf060aa34472787355c -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 352367] vectors too short. last frame not plotted
https://bugs.kde.org/show_bug.cgi?id=352367 --- Comment #4 from Michael Brewer --- >From your previous comment, I got the impression that INDEX was something specific to the plot. If INDEX is in fact just another 1 sample per frame vector, then I agree that it should be the same as all the other 1 sample per frame vectors. *** Right: Imagine you want to plot a field which is 100 samples per frame vs something that is 1 samples per frame. And you want to plot one frame. Maybe because your datasource is only one frame long. What should you do? *** Currently, this question is moot since it is not possible to plot one frame of data in KST. But that is my point. If the user has only one frame of data, there should be a way for them to look at that data. In the example that you give, there is only one X-Y pair to plot. In order to plot this, the plot itself needs to extend from 0 to 1. In general, the plot should always extend from 0 to nframes. This is one more than the INDEX array that extends from 0 to nframes - 1. Since this is just a matter of setting the boundaries of the X axis of the plot, it seems straight forward to me. Perhaps I am missing something though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 342356] MIPS: determine page size at runtime
https://bugs.kde.org/show_bug.cgi?id=342356 --- Comment #5 from Petar Jovanovic --- Committed in r15813. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359734] "Track Mouse" feature shows non-transparent background rotating.
https://bugs.kde.org/show_bug.cgi?id=359734 --- Comment #10 from J Lee --- > Can you confirm it ever worked on the XRender backend in the KF5 based KWin? I never looked at these settings before, (compositor), so they would have been set at the default settings. I know that this used to work fine until about two weeks ago. After a system update (I think it was one of the Xorg updates) it broke. When no patches came, I submitted this report. My installation is about one month old. Not sure if it is relevant, but I've got Deepin installed as an alternative DE - would this have broken something? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359734] "Track Mouse" feature shows non-transparent background rotating.
https://bugs.kde.org/show_bug.cgi?id=359734 --- Comment #11 from Thomas Lübking --- Means it's likely been broken all KF5 > Not sure if it is relevant, but I've got Deepin installed as an alternative > DE - would this have broken something? Nope. -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 352367] vectors too short. last frame not plotted
https://bugs.kde.org/show_bug.cgi?id=352367 --- Comment #5 from Michael Brewer --- (In reply to Michael Brewer from comment #4) > From your previous comment, I got the impression that INDEX was something > specific to the plot. If INDEX is in fact just another 1 sample per frame > vector, then I agree that it should be the same as all the other 1 sample > per frame vectors. > > *** > Right: Imagine you want to plot a field which is 100 samples per frame vs > something that is 1 samples per frame. And you want to plot one frame. Maybe > because your datasource is only one frame long. What should you do? > *** > > Currently, this question is moot since it is not possible to plot one frame > of data in KST. > But that is my point. If the user has only one frame of data, there should > be a way for them to look at that data. In the example that you give, there > is only one X-Y pair to plot. In order to plot this, the plot itself needs > to extend from 0 to 1. In general, the plot should always extend from 0 to > nframes. This is one more than the INDEX array that extends from 0 to > nframes - 1. Since this is just a matter of setting the boundaries of the X > axis of the plot, it seems straight forward to me. Perhaps I am missing > something though. BTW, in your example if the user has two fields of data at 100 samples per frame that they want to plot using one field as X and the other as Y, then there are 100 X-Y pairs to plot. Does it make sense that KST should do nothing? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons
https://bugs.kde.org/show_bug.cgi?id=355592 Kai Uwe Broulik changed: What|Removed |Added Version|5.5.3 |unspecified Summary|Thumbnail icons in folder |IconItem does not support |view layout desktop have|non-square icons |wrong fixed 1:1 aspect | |ratio | CC||k...@privat.broulik.de Component|Folder |components Assignee|h...@kde.org|notm...@gmail.com Target Milestone|1.0 |--- Product|plasmashell |frameworks-plasma --- Comment #6 from Kai Uwe Broulik --- This is actually a bug in the Plasma IconItem that just assumes everything to be square although QIcon can also hold non-square icons such as the ones coming from the thumbnail generator. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359825] Plasma crashed without any specific window action
https://bugs.kde.org/show_bug.cgi?id=359825 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 357895 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358964] Plasma crashed while opening application menu (fullscreen launcher)
https://bugs.kde.org/show_bug.cgi?id=358964 Marco Martin changed: What|Removed |Added CC||b...@michaudtech.com --- Comment #2 from Marco Martin --- *** Bug 359826 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359826] Plasma crash when opening classic application menu
https://bugs.kde.org/show_bug.cgi?id=359826 Marco Martin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 358964 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359828] Plasma crash during normal desktop work (external monitor connected via Display Port)
https://bugs.kde.org/show_bug.cgi?id=359828 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Component|general |Application Menu (Kicker) Assignee|k...@davidedmundson.co.uk|h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 359404] Problem viewing graphic output in Windows
https://bugs.kde.org/show_bug.cgi?id=359404 Thomas Friedrichsmeier changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Thomas Friedrichsmeier --- Hi! Sorry for the long delay. This should be fixed in the 0.6.4-1 binaries, available for download, now ( http://download.kde.org/stable/rkward/0.6.4/win32/ or http://rkward.kde.org/windows ). Should you continue to see this or different issues, don't hesitate to open a new bug report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359223] [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
https://bugs.kde.org/show_bug.cgi?id=359223 Aleix Pol changed: What|Removed |Added CC||aleix...@kde.org --- Comment #7 from Aleix Pol --- Should be fixed as of: http://commits.kde.org/okular/154c98fdaab2e593091fe644cfaeed96dd9fefaf -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over TaskManager
https://bugs.kde.org/show_bug.cgi?id=357895 Marco Martin changed: What|Removed |Added CC||jsm...@allworx.com --- Comment #49 from Marco Martin --- *** Bug 359825 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359223] [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
https://bugs.kde.org/show_bug.cgi?id=359223 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 359404] Problem viewing graphic output in Windows
https://bugs.kde.org/show_bug.cgi?id=359404 --- Comment #7 from Leszek Pawlowicz --- Works perfectly. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359829] New: Power PC test suite none/tests/ppc64/test_isa_2_07.c uses uninitialzed data
https://bugs.kde.org/show_bug.cgi?id=359829 Bug ID: 359829 Summary: Power PC test suite none/tests/ppc64/test_isa_2_07.c uses uninitialzed data Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: c...@us.ibm.com The test none/tests/ppc64/test_isa_2_07.c steps beyond the data array in a number of places. The issue is the array is declared to be of size N. The for loop is: for (i=0; i
[okular] [Bug 348172] Scaling options missing in print dialog
https://bugs.kde.org/show_bug.cgi?id=348172 Felix Jaeckel changed: What|Removed |Added CC||fxjaec...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356950] [Regression][15.12.0] Empty message when viewing encrypted message in preview pane without auto-decrypt.
https://bugs.kde.org/show_bug.cgi?id=356950 Thiago Macieira changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Thiago Macieira --- Confirmed fixed in KMail 5.1.2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 359830] New: KMail stops silently working because of error "Unable to fetch item from backend"
https://bugs.kde.org/show_bug.cgi?id=359830 Bug ID: 359830 Summary: KMail stops silently working because of error "Unable to fetch item from backend" Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: tietze.he...@gmail.com CC: kdepim-b...@kde.org, vkra...@kde.org The error "Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." is shown in the status bar. It happens on synchronizing the Google trash folder. The really awkward is that KMail silently stops working (except from the status bar info) until I restart per "akonadictl restart" (without any error). It helps when I cleanup the trash but it's not a solution. My suggestion is to a) fix the bug and b) show a plasma notification on error that prevent KMail from receiving emails. Reproducible: Always KMail 5.1.2 akonadictl -v: "Akonadi 5.1.51" plasmashell -v: "plasmashell 5.5.4" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359831] New: Avoid closing animation if application is minimized
https://bugs.kde.org/show_bug.cgi?id=359831 Bug ID: 359831 Summary: Avoid closing animation if application is minimized Product: kwin Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: nierr...@gmail.com As title says: i noted that "glide" closing animation is drawed even for minimized applications (eg: open konsole, minimize it, close it). I think that minimized applications should be blacklisted from the animation. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 359246] Ark misidentifies uncompressed GNU tar file with pdf document as first member
https://bugs.kde.org/show_bug.cgi?id=359246 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Elvis Angelaccio --- (Already) fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=94089 -- You are receiving this mail because: You are watching all bug changes.
[picmi] [Bug 359822] Link to manual opens an error page
https://bugs.kde.org/show_bug.cgi?id=359822 --- Comment #1 from Jakob Gruber --- Where in the application is that link located? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359797] BorderlessMaximizedWindows=true forces server-side decorations
https://bugs.kde.org/show_bug.cgi?id=359797 Thomas Lübking changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Thomas Lübking --- You likely installed the recompiled kwin version out of PATH or similar - the patch works (tested gtk3-demo which shares CSD & relevant props) and the props support that. Correct patch (motif hint must be flagged & invoking rules is nice - neither is relevant for the behavior) diff --git a/geometry.cpp b/geometry.cpp index 1bffa9b..2a07a20 100644 --- a/geometry.cpp +++ b/geometry.cpp @@ -2256,7 +2256,7 @@ void Client::changeMaximize(bool vertical, bool horizontal, bool adjust) // triggers a maximize change. // The next setNoBorder interation will exit since there's no change but the first recursion pullutes the restore geometry changeMaximizeRecursion = true; -setNoBorder(app_noborder || max_mode == MaximizeFull); +setNoBorder(rules()->checkNoBorder(app_noborder || (m_motif.hasDecoration() && m_motif.noBorder()) || max_mode == MaximizeFull)); changeMaximizeRecursion = false; } Review-request as soon as I can focus for more than a minute next time :-( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 355011] Plasma Add-On Installer cannot update widgets after restart
https://bugs.kde.org/show_bug.cgi?id=355011 Markus S. changed: What|Removed |Added Product|kdelibs |frameworks-knewstuff Status|UNCONFIRMED |CONFIRMED CC||kamika...@web.de, ||kdelibs-b...@kde.org Component|knewstuff |general Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359831] Glide effect doesn't filter minimized windows
https://bugs.kde.org/show_bug.cgi?id=359831 Thomas Lübking changed: What|Removed |Added Component|effects-window-management |effects-various Summary|Avoid closing animation if |Glide effect doesn't filter |application is minimized|minimized windows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359832] New: Can't read visibility dropdown menus in "Entries" section of System Tray Settings window with Breeze Dark. Background is white (video example included)
https://bugs.kde.org/show_bug.cgi?id=359832 Bug ID: 359832 Summary: Can't read visibility dropdown menus in "Entries" section of System Tray Settings window with Breeze Dark. Background is white (video example included) Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: jesse.dub...@gmail.com See video in URL field for details. In Breeze dark, trying to view the dropdown menu in the "Entries" section of the system tray settings window shows the background as white. Can't ready it. Reproducible: Always Steps to Reproduce: 1. Open system tray settings 2. Go to "Entries" 3. Click the visibility of an item to open the dropdown menu list Actual Results: Background for options are white. Can't read text unless you highlight the mouse over it. Expected Results: options should have dark theme like the rest of Plasma. Tested while running Antergos Linux x64, KDE Plasma 5.5.4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359832] Can't read visibility dropdown menus in "Entries" section of System Tray Settings window with Breeze Dark. Background is white (video example included)
https://bugs.kde.org/show_bug.cgi?id=359832 Jesse changed: What|Removed |Added URL||https://youtu.be/CRZnEUspA2 ||k CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359829] Power PC test suite none/tests/ppc64/test_isa_2_07.c uses uninitialzed data
https://bugs.kde.org/show_bug.cgi?id=359829 Carl Love changed: What|Removed |Added Resolution|--- |FIXED CC||will_schm...@vnet.ibm.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Carl Love --- The code was fixed in Valgrind commit 15816. The expected output files were also updated for the new code. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359829] Power PC test suite none/tests/ppc64/test_isa_2_07.c uses uninitialzed data
https://bugs.kde.org/show_bug.cgi?id=359829 Carl Love changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359833] New: Have option in Pager Settings to enable/disable tooltip?
https://bugs.kde.org/show_bug.cgi?id=359833 Bug ID: 359833 Summary: Have option in Pager Settings to enable/disable tooltip? Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: jesse.dub...@gmail.com Just a small convenience, but there's no option to disable the toolip for Pager when the mouse hovers over one of the desktops. Would be a nice option. :) Reproducible: Always Suggested while using Antergos Linux x64, KDE Plasma 5.5.4. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359160] 15.13.0 git master - Composite in tracks not working right when three (or more?) tracks are used. (Video example included)
https://bugs.kde.org/show_bug.cgi?id=359160 --- Comment #10 from Jean-Baptiste Mardelle --- Git commit ffae410dab837906843a77743eea1db4d7228bf1 by Jean-Baptiste Mardelle. Committed on 26/02/2016 at 17:49. Pushed by mardelle into branch 'master'. Fix composite in multitrack M +7-18 src/doc/kdenlivedoc.cpp M +2-44 src/timeline/customtrackview.cpp M +1-3src/timeline/customtrackview.h M +20 -0src/timeline/timeline.cpp M +6-2src/timeline/timeline.h M +42 -1src/timeline/transitionhandler.cpp M +2-0src/timeline/transitionhandler.h http://commits.kde.org/kdenlive/ffae410dab837906843a77743eea1db4d7228bf1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 347601] git username dialog looks like a password dialog
https://bugs.kde.org/show_bug.cgi?id=347601 Milian Wolff changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Milian Wolff --- can you show a screenshot please? or tell me how to reproduce this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359834] New: After creating new activity, cannot move the that desktop tab on the edge of the screen.
https://bugs.kde.org/show_bug.cgi?id=359834 Bug ID: 359834 Summary: After creating new activity, cannot move the that desktop tab on the edge of the screen. Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: jesse.dub...@gmail.com CC: bhus...@gmail.com When I create a new activity and go into it, I cannot move the tab that's on the screen edge. It won't move at all. I can click it, and the menu options open just fine, though. I made sure to check that widgets were unlocked when I tried this. Reproducible: Always Steps to Reproduce: 1. Create a new activity 2. Go into that activity 3. Try to click+drag the tab that has the activity name and the hamburger icon Actual Results: Tab thing (sorry, I don't know its proper name) won't move. Expected Results: Should be able to move it just like all other activities. Tested while using KDE Plasma 5.5.4 on Antergos Linux x64. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359834] After creating new activity, cannot move the that desktop tab on the edge of the screen.
https://bugs.kde.org/show_bug.cgi?id=359834 Jesse changed: What|Removed |Added CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359833] Have option in Pager Settings to enable/disable tooltip?
https://bugs.kde.org/show_bug.cgi?id=359833 Jesse changed: What|Removed |Added CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359832] Can't read visibility dropdown menus in "Entries" section of System Tray Settings window with Breeze Dark. Background is white (video example included)
https://bugs.kde.org/show_bug.cgi?id=359832 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 343369 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable
https://bugs.kde.org/show_bug.cgi?id=343369 Kai Uwe Broulik changed: What|Removed |Added CC||jesse.dub...@gmail.com --- Comment #22 from Kai Uwe Broulik --- *** Bug 359832 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
