[krita] [Bug 358350] Version 2.9.9 in OS X 10.9.5 and MS Windows 7 crash opening JPEG file from scanned image.
https://bugs.kde.org/show_bug.cgi?id=358350 --- Comment #3 from Boudewijn Rempt --- Hm, I tested with 2.9.10 on Windows 10, and there it opened fine. With 2.9.10 on OSX, Krita complained that the jpeg file was not in a normal colorspace for jpeg and loaded it as grayscale with your scanner's Gray profile -- but I didn't get a crash. The 3.0 pre-alpha loaded it fine as well. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354316] Dolphin fails to give option to overwrite files when dragging them from a browser
https://bugs.kde.org/show_bug.cgi?id=354316 jmaspons changed: What|Removed |Added CC||joanmasp...@gmail.com --- Comment #2 from jmaspons --- Same problem when copying files from remote connections (fish protocol) in dolphin. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 jed-bugs.kde@uma.litech.org changed: What|Removed |Added CC||jed-bugs.kde.org@uma.litech ||.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358353] New: kscreen ignores primary screen
https://bugs.kde.org/show_bug.cgi?id=358353 Bug ID: 358353 Summary: kscreen ignores primary screen Product: KScreen Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: dvra...@kde.org Reporter: b...@mrvanes.com Since upgrade to plasma 5.5.3 kscreen allways places my panel on external monitor, even though I configure it to be above laptop panel and make laptop panel primary. After disconnecting external monitor, panel does not return to laptop leaving me with a broken system which can only be reparied by "find .config '*plasma*' -delete" Reproducible: Always Steps to Reproduce: 1. Connect external monitor 2. Open Display Configuration and place monitor above laptop screen and mark (or keep) laptop primary 3. Watch panel go to external monitor 4. Disconnect monitor 5. Panel disappears Actual Results: Panel is lost Expected Results: Panel stays on Laptop screen, and stays there after external monitor disconnect The same happens if I configure external screen using xrandr, so I suspect it not to be the config tools fault. It seems plasma doesn't respect "primary" anymore. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 357718] KInfoCenter Crashed When Closing
https://bugs.kde.org/show_bug.cgi?id=357718 Vytautas changed: What|Removed |Added CC||v...@azuolas.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358354] New: Plasma Closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=358354 Bug ID: 358354 Summary: Plasma Closed unexpectedly Product: plasmashell Version: 5.4.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sumitre...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.5.0 Operating System: Linux 4.1.12-1-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - Custom settings of the application: After installing the nvidia drivers,the plasma gets crashed on restart. I reinstall opensuse and the sam e thing happens after nvidia driver installation from common repositories i add the nvidia graphics drivers then i give zypper inr in terminal after that i restart then the problem occurs The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f16de2cf800 (LWP 2226))] Thread 7 (Thread 0x7f16c64ce700 (LWP 2228)): #0 0x7f16d7842c1d in poll () at /lib64/libc.so.6 #1 0x7f16dc748422 in () at /usr/lib64/libxcb.so.1 #2 0x7f16dc74a00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f16c8c50c29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f16d7f3955f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f16d704c0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f16d784b04d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f16bc071700 (LWP 2236)): #0 0x7f16d70527bc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f16d704e4a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f16d704e306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f16d3369fcc in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f16d336eb11 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f16d336f018 in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f16cfa13001 in () at /usr/lib64/tls/libnvidia-tls.so.352.55 #7 0x7f16d3f74b60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f16d3f33999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7f16d3f33df8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7f16d3f33f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x7f16d816aa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7f16d8111a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #13 0x7f16d7f3484a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #14 0x7f16db2045f8 in () at /usr/lib64/libQt5Qml.so.5 #15 0x7f16d7f3955f in () at /usr/lib64/libQt5Core.so.5 #16 0x7f16d704c0a4 in start_thread () at /lib64/libpthread.so.0 #17 0x7f16d784b04d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f16b0b45700 (LWP 2237)): #0 0x7f16d816a9b0 in () at /usr/lib64/libQt5Core.so.5 #1 0x7f16d3f334ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f16d3f33d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f16d3f33f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f16d816aa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f16d8111a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f16d7f3484a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f16db2045f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f16d7f3955f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f16d704c0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f16d784b04d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f16ab048700 (LWP 2240)): #0 0x7f16d3f75d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f16d3f338e9 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f16d3f33df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f16d3f33f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f16d816aa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f16d8111a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f16d7f3484a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f16db2045f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f16d7f3955f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f16d704c0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f16d784b04d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f16a96ba700 (LWP 2241)): #0 0x7f16d705005f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f16dd9ac7eb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f16dd9ac819 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f16d704
[kinfocenter] [Bug 357718] KInfoCenter Crashed When Closing
https://bugs.kde.org/show_bug.cgi?id=357718 --- Comment #2 from Vytautas --- Sometimes crashes for me too. Plasma 5.5.3, qt 5.5.1. Not sure, maybe specific module causes crash, because it usually crashes after browsing some detailed information. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 358355] New: Please add a "Copy" context menu entry
https://bugs.kde.org/show_bug.cgi?id=358355 Bug ID: 358355 Summary: Please add a "Copy" context menu entry Product: trojita Version: 0.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: tobias.leup...@web.de When selecting some text in the message view, this can be copied to the clipboard by pressing the standard CTRL+C key combination. The context menu lacks such a "Copy" entry though, which is imo expected to be there; at least, in most programs, such an entry is visible in this situation. It's just a small thing, but I think it would improve the user's experience. Would be nice if you added it :-) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358353] kscreen ignores primary screen
https://bugs.kde.org/show_bug.cgi?id=358353 --- Comment #1 from Martin van Es --- Some more testing reveals kscreen DOES think HDMI1 is primary after connection and setting eDP1 primary using xrandr makes the panel go down again, but I do have to restart plasmashell for that to happen. Unitl the restart, the laptop panel is black. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 350732] windows, activated from krunner, doesn't get focus
https://bugs.kde.org/show_bug.cgi?id=350732 --- Comment #3 from Vytautas --- Still doesn't work. Tested: kubuntu with plasma 5.5.3 and qt 5.5.1 (new installation). opensuse live cd (plasma 5.5.2, qt 5.5.1). Do we talk about the same bug? To reproduce: 1. Press Alt-f2 and type "konsole". Choose "Applications Konsole". Press Enter to launch it. 2. new Konsole is launched, it has focus. 3. Press Alt-f2 and type "kinfocenter". Choose "Applications KInfoCenter". Press Enter to launch it. 4. new KInfoCenter is launced, it has focus. 5. Press Alt-f2 and type "konsole". Choose "Windows linux: bash -- Konsole" (existing window). Press Enter to activate (don't use mouse in this step). 6. Konsole window is moved on top, but focus is still on KInfoCenter. BTW. If activating item "Windows linux: bash -- Konsole" on krunner search list with mouse, Konsole get focus. It doesn't get focus if activated with keyboard. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 350732] windows, activated from krunner, doesn't get focus
https://bugs.kde.org/show_bug.cgi?id=350732 Vytautas changed: What|Removed |Added Version|5.3.2 |5.5.3 Platform|Debian unstable |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358356] New: digikam collapsed
https://bugs.kde.org/show_bug.cgi?id=358356 Bug ID: 358356 Summary: digikam collapsed Product: digikam Version: 4.0.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: mkkoma...@gmail.com Application: digikam (4.0.0) KDE Platform Version: 4.14.2 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.19.0-32-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed:When copying pictures from sd card, suddenly fell digikam. Launch applications only KDE IM. Google translation -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f13f00ebac0 (LWP 3169))] Thread 15 (Thread 0x7f13cc810700 (LWP 3171)): #0 0x7f13e923a12d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f13d0f70248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7f13e5722182 in start_thread (arg=0x7f13cc810700) at pthread_create.c:312 #3 0x7f13e924747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7f13c5cc3700 (LWP 3185)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f13eaf20816 in wait (time=18446744073709551615, this=0x146cd10) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x100f690, mutex=mutex@entry=0x100f688, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x005e3d9e in Digikam::ScanController::run (this=0x1069b20) at /build/buildd/digikam-4.0.0/core/digikam/database/scancontroller.cpp:725 #4 0x7f13eaf2032f in QThreadPrivate::start (arg=0x1069b20) at thread/qthread_unix.cpp:349 #5 0x7f13e5722182 in start_thread (arg=0x7f13c5cc3700) at pthread_create.c:312 #6 0x7f13e924747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 13 (Thread 0x7f13c54c2700 (LWP 3186)): #0 0x7f13e226261a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f13e22629a9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13e2220f91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13e22210ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f13eb04f7be in QEventDispatcherGlib::processEvents (this=0x7f13b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7f13eb0210af in QEventLoop::processEvents (this=this@entry=0x7f13c54c1ae0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f13eb0213a5 in QEventLoop::exec (this=this@entry=0x7f13c54c1ae0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f13eaf1dc5f in QThread::exec (this=this@entry=0x106cc40) at thread/qthread.cpp:537 #8 0x7f13eb002823 in QInotifyFileSystemWatcherEngine::run (this=0x106cc40) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x7f13eaf2032f in QThreadPrivate::start (arg=0x106cc40) at thread/qthread_unix.cpp:349 #10 0x7f13e5722182 in start_thread (arg=0x7f13c54c2700) at pthread_create.c:312 #11 0x7f13e924747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 12 (Thread 0x7f13c4cc1700 (LWP 3188)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f13eaf20816 in wait (time=18446744073709551615, this=0x1709f50) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1318870, mutex=mutex@entry=0x1318868, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f13ed7608aa in Digikam::ParkingThread::run (this=0x1318850) at /build/buildd/digikam-4.0.0/core/libs/threads/threadmanager.cpp:119 #4 0x7f13eaf2032f in QThreadPrivate::start (arg=0x1318850) at thread/qthread_unix.cpp:349 #5 0x7f13e5722182 in start_thread (arg=0x7f13c4cc1700) at pthread_create.c:312 #6 0x7f13e924747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 11 (Thread 0x7f13b7b8e700 (LWP 3189)): #0 0x7f13e57257ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f13ba60) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x7f13ba60) at pthread_mutex_unlock.c:310 #2 0x7f13e22629b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13e2220e9d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f13e22210ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f13eb04f7be in QEventDispatcherGlib::processEvents (this=0x7f13b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7f13eb0210af in QEventLoop::processEvents (this=th
[dolphin] [Bug 358357] New: Dolphin crashes when configure dolphin is clicked
https://bugs.kde.org/show_bug.cgi?id=358357 Bug ID: 358357 Summary: Dolphin crashes when configure dolphin is clicked Product: dolphin Version: 15.08.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 812682...@qq.com Application: dolphin (15.08.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: After I upgraded plasma to 5.5.3, dolphin starts to crash at least 8 out of 10 times when I click on configure dolphin. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f298ac7f800 (LWP 17249))] Thread 2 (Thread 0x7f297bad4700 (LWP 17251)): #0 0x7f299bb588dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f299267e1ec in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f2974003020, timeout=, context=0x7f2974000990) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:4135 #2 0x7f299267e1ec in g_main_context_iterate (context=context@entry=0x7f2974000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3835 #3 0x7f299267e2fc in g_main_context_iteration (context=0x7f2974000990, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #4 0x7f299695c50b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f299690350a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f299671fac4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2996724a6e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2992db46aa in start_thread (arg=0x7f297bad4700) at pthread_create.c:333 #9 0x7f299bb63eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f298ac7f800 (LWP 17249)): [KCrash Handler] #6 0x7f29967ade13 in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f29974682d5 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f299746a52b in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f299740a9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f299740fea6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f2996905d7b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2996e585f1 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f2996e5a2b5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f2996e3e228 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f298a7640b0 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #16 0x7f299267dff7 in g_main_context_dispatch (context=0x7f29800016f0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3154 #17 0x7f299267dff7 in g_main_context_dispatch (context=context@entry=0x7f29800016f0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3769 #18 0x7f299267e250 in g_main_context_iterate (context=context@entry=0x7f29800016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3840 #19 0x7f299267e2fc in g_main_context_iteration (context=0x7f29800016f0, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #20 0x7f299695c4ef in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f299690350a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f299758abb0 in QMenu::exec(QPoint const&, QAction*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f29975ccffe in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f29969348ea in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f2997507bc7 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f2997507d21 in QAbstractButton::mousePressEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f29975cddef in QToolButton::mousePressEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f
[umbrello] [Bug 358358] New: No change of association symbol colour possible
https://bugs.kde.org/show_bug.cgi?id=358358 Bug ID: 358358 Summary: No change of association symbol colour possible Product: umbrello Version: 2.18.0 (KDE Applications 15.12.0) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Changing the colour of an association do not change the colour of the related association symbol too. Reproducible: Always Steps to Reproduce: 1. start umbrello 2. add two classes and add an inheritance association between them 3. right-click on the association, select line colour, change colour and save Actual Results: The colour of the association line has been changed, but the colour of the association symbol on the end of the association not. Expected Results: The colour of the association symbol should be changed too. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 350779] krunner forgets enabled categories, when switching KDE regional settings to another language
https://bugs.kde.org/show_bug.cgi?id=350779 Vytautas changed: What|Removed |Added Version|5.3.2 |5.5.3 --- Comment #2 from Vytautas --- Still not fixed on plasma 5.5.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358342] Intermittent plasmashell crash when hovering mouse over taskbar applications
https://bugs.kde.org/show_bug.cgi?id=358342 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** 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 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over panel
https://bugs.kde.org/show_bug.cgi?id=357895 David Edmundson changed: What|Removed |Added CC||spe...@gmail.com --- Comment #24 from David Edmundson --- *** Bug 358342 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358356] digikam collapsed
https://bugs.kde.org/show_bug.cgi?id=358356 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 329697 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed
https://bugs.kde.org/show_bug.cgi?id=345563 David Edmundson changed: What|Removed |Added CC||sumitre...@gmail.com --- Comment #65 from David Edmundson --- *** Bug 358354 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)
https://bugs.kde.org/show_bug.cgi?id=329697 caulier.gil...@gmail.com changed: What|Removed |Added CC||mkkoma...@gmail.com --- Comment #153 from caulier.gil...@gmail.com --- *** Bug 358356 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358354] Plasma Closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=358354 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Error raised here means there's something broken with your openGL drivers. One common cause is NVidia's libGL installed, but the NVidia kernel module missing. See linked report. *** This bug has been marked as a duplicate of bug 345563 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358349] plasma crashes when starting minimwatch
https://bugs.kde.org/show_bug.cgi?id=358349 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- #7 0x7fe19210ddcc in brw_clear (ctx=0x18d1f88, mask=34) at ../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:247 This is crashing in your graphic driver which we can't do much about. Please upgrade/downgrade your version of mesa. See information (including a workaround) in the linked report.. *** This bug has been marked as a duplicate of bug 349519 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349519] plasmashell occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=349519 David Edmundson changed: What|Removed |Added CC||g...@netcologne.de --- Comment #108 from David Edmundson --- *** Bug 358349 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 358304] Ark does not open ISO files with UDF filesystem.
https://bugs.kde.org/show_bug.cgi?id=358304 --- Comment #9 from Elvis Angelaccio --- (In reply to cameronpoe from comment #7) > Yes, you are right!!! :) > I was testing only windows ISOs :( > Ark opens Linux ISOs :) > > Output on almost all of them windows images gives me: > application/x-iso9660-image This confirms that we cannot do much. Libarchive (which is used for ISO files) supports ISO9660 images, but not if they have an UDF filesystem. It may be possible to use directly libcdio instead of libarchive, but that would require someone to write another plugin from scratch. > but on one of them it is: application/octet-stream > ...and when I try to open this one with Ark it is totally empty. This should not happen. Can you start Ark from terminal and post here its output? -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 358359] New: HIgh cpu consumption and apt-check process infinte fork
https://bugs.kde.org/show_bug.cgi?id=358359 Bug ID: 358359 Summary: HIgh cpu consumption and apt-check process infinte fork Product: muon Version: 5.5.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: notifier Assignee: echidna...@kubuntu.org Reporter: christophe.cail...@gmail.com CC: aleix...@kde.org, sit...@kde.org When executing apt update command on Konsole I've the following behaviour : High CPU consumption Memory consumption due to fork of apt-check processes When I remove package plasma-discover-updater this issue dissapear Reproducible: Always Steps to Reproduce: 1. apt update on Konsole 2. 3. Actual Results: High memory consumption HIgh CPU consumption: actually all cores of CPU are at 100% Expected Results: no High memory or CPU consumption With plasma 5.4.3 and Framework 5.15 no problem Problem occurs when upgrading with ppa:kubuntu-ppa/backports packages -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 358360] New: Add support for multiple page layouts per document
https://bugs.kde.org/show_bug.cgi?id=358360 Bug ID: 358360 Summary: Add support for multiple page layouts per document Product: calligrawords Version: 2.9.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: martin.tlus...@gmail.com Right now a selected page layout will apply to the whole document. I would like to be able to apply page layouts to specific pages. Also I cannot find a way to edit a page layout. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358312] The shortcut "M" does not move messages
https://bugs.kde.org/show_bug.cgi?id=358312 --- Comment #6 from Rigo Wenning --- The bug appeared after upgrade to KF5. Now I have rebooted the machine (not only logged out/in again) and the default is on "ok" now. I should have taken a screenshot. But maybe this bug report serves others who run into the same issue. For me, it is solved. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358361] New: The network icon (wired ethernet) no longer shows vpn connection
https://bugs.kde.org/show_bug.cgi?id=358361 Bug ID: 358361 Summary: The network icon (wired ethernet) no longer shows vpn connection Product: Breeze Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: uri_herr...@nitrux.in Reporter: nortex...@gmail.com CC: kain...@gmail.com In Plasma 5.4.x, when connected to a vpn on my wired ethernet, it would show a little lock overlay indicating that I was connected to the vpn. It no longer does that with the update to 5.5.3. I notice the icon for wired ethernet has changed, which may be the source of the problem. Reproducible: Always Steps to Reproduce: 1. Connect to wired ethernet connection 2. Connect to vpn Actual Results: The ethernet connection icon does not indicate connection to vpn Expected Results: The icon indicates connection to vpn -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 358362] New: importing a bigger csv file takes ~20 seconds until import filter pops up.
https://bugs.kde.org/show_bug.cgi?id=358362 Bug ID: 358362 Summary: importing a bigger csv file takes ~20 seconds until import filter pops up. Product: calligrasheets Version: 2.9.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: filters Assignee: calligra-sheets-bugs-n...@kde.org Reporter: martin.tlus...@gmail.com The csv file has around 1300 lines. Importing the same file into libreoffice takes about 1 second. (I know it sucks to be compared to libreoffice all the time... ;-) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 358362] importing a bigger csv file takes ~20 seconds until import filter pops up.
https://bugs.kde.org/show_bug.cgi?id=358362 Martin Tlustos changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #113 from painless roaster --- (In reply to Rex Dieter from comment #111) > That test case is not reproducible for me, clock widget with seconds > displayed... plasmashell hasn't grown any over the course of the past few > minutes at least. Few minutes is very short time for test with clock. Faster test: - download plasmoid thermal monitor and set: - refresh speed - 0.1s - create 5 fields for temperature monitoring (physical id and 4 cores) - in this test is leak speed is 12MB / minute Is any chance for use memory leak profiler please? For example compile plasma-workspace with library jemalloc and use jeprof. Valgrind is too slow and not monitor during run. But jemalloc is ideal library for memory monitoring. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358363] New: After system restart often TaskBar resets his position in TwinView
https://bugs.kde.org/show_bug.cgi?id=358363 Bug ID: 358363 Summary: After system restart often TaskBar resets his position in TwinView Product: plasmashell Version: 5.5.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: zmo...@hotmail.com I have two displays: smaller on left (secondary; external) and larger on right (primary; laptop). TaskBar resides in right (primary) display on right side (see "taskbar__should.png"). After I upgraded Plasma from 5.4 to 5.5 very often after restart TaskBar self moves to left (secondary) screen (see "taskbar__bad.png"). Further restart doenst fix "taskbar reset", I must manually move it. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358363] After system restart often TaskBar resets his position in TwinView
https://bugs.kde.org/show_bug.cgi?id=358363 --- Comment #1 from Valdas --- Created attachment 96780 --> https://bugs.kde.org/attachment.cgi?id=96780&action=edit taskbar in "self reset" position -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358363] After system restart often TaskBar resets his position in TwinView
https://bugs.kde.org/show_bug.cgi?id=358363 --- Comment #2 from Valdas --- Created attachment 96781 --> https://bugs.kde.org/attachment.cgi?id=96781&action=edit taskbar in right position -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358363] After system restart often TaskBar resets his position in TwinView
https://bugs.kde.org/show_bug.cgi?id=358363 Valdas changed: What|Removed |Added Attachment #96781|taskbar in right position |taskbar in "self reset" description||position -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358363] After system restart often TaskBar resets his position in TwinView
https://bugs.kde.org/show_bug.cgi?id=358363 Valdas changed: What|Removed |Added Attachment #96780|image/png |image/jpg mime type|| Attachment #96780|taskbar in "self reset" |taskbar in right position description|position| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 juha.heljora...@iki.fi changed: What|Removed |Added CC||juha.heljora...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358364] New: Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 Bug ID: 358364 Summary: Crashes on startup ever since trying to answer email Product: kontact Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: b...@ucw.cz Application: kontact (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: Kontact crashed. I am not sure whether it was trying to answer or just display email. Ever since it crashes immediately on startup. Starting kmail alone crashes as well. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f508d07d940 (LWP 3726))] Thread 3 (Thread 0x7f5066317700 (LWP 3727)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f50897baa4d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f50897baaa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f50842bf284 in start_thread (arg=0x7f5066317700) at pthread_create.c:333 #4 0x7f508a56974d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f5025a14700 (LWP 3742)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f50894de191 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f50897eafe6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f50842bf284 in start_thread (arg=0x7f5025a14700) at pthread_create.c:333 #4 0x7f508a56974d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f508d07d940 (LWP 3726)): [KCrash Handler] #6 0x7f508a4b4657 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7f508a4b5a2a in __GI_abort () at abort.c:89 #8 0x7f508a4f2bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f508a5eb5f8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f508a4f800e in malloc_printerr (action=1, str=0x7f508a5eb708 "free(): invalid next size (fast)", ptr=) at malloc.c:4965 #10 0x7f508a4f87eb in _int_free (av=, p=, have_lock=0) at malloc.c:3834 #11 0x7f508b9bd89d in QTextEngine::clearLineData() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x7f508ba09b8f in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f508bbdb564 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x7f508bbdbde0 in QTextEdit::resizeEvent(QResizeEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #15 0x7f508b7a71b0 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x7f508bb6d80e in QFrame::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #17 0x7f508ad2abd6 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x7f508b7508bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x7f508b757816 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #20 0x7f508c4d271a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #21 0x7f508ad2aa6d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7f508b7a3321 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x7f508b7a44b3 in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x7f508b7a6502 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x7f508b7a4407 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x7f508b7a44cf in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #27 0x7f508b7a6502 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x7f508b7a4407 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7f508b7a44cf in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #30 0x7f508b7a6502 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x7f508b7a4407 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #32 0x7f508b7a44cf in QWidgetPrivate::show_helper() () from /usr/li
[trojita] [Bug 347625] Be able to copy text from received messages with using right mouseclick
https://bugs.kde.org/show_bug.cgi?id=347625 Jan Kundrát changed: What|Removed |Added CC||tobias.leup...@web.de --- Comment #6 from Jan Kundrát --- *** Bug 358355 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 358355] Please add a "Copy" context menu entry
https://bugs.kde.org/show_bug.cgi?id=358355 Jan Kundrát changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jan Kundrát --- *** This bug has been marked as a duplicate of bug 347625 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage
https://bugs.kde.org/show_bug.cgi?id=358261 --- Comment #5 from Daniel --- Thank you for the answers. I sent a message in the kde-hardware-devel list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #114 from painless roaster --- (In reply to Rex Dieter from comment #111) > That test case is not reproducible for me, clock widget with seconds > displayed... plasmashell hasn't grown any over the course of the past few > minutes at least. I tried leak with thermal monitor on second pc. Leak exists, but it is slower (500kB / minute) . But for leak need set 6 virtual workspaces. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358365] New: Complete refactoring of line color and line with based setting to QPen.
https://bugs.kde.org/show_bug.cgi?id=358365 Bug ID: 358365 Summary: Complete refactoring of line color and line with based setting to QPen. Product: umbrello Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de >From the umbrello-soc branch a new QPen based design to access (an set) line color and line with for a widget (class AssociationLine and Symbol). It would be nice to use this api in the whole umbrello source code. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358366] New: Complete refactoring of fill color based widget settings to a QBrush based
https://bugs.kde.org/show_bug.cgi?id=358366 Bug ID: 358366 Summary: Complete refactoring of fill color based widget settings to a QBrush based Product: umbrello Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de >From the umbrello-soc branch a new QBrush based design to access (an set) widgets fill color (class AssociationLine) has been introduced. It would be nice to use this api in the whole umbrello source code. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358358] No change of association symbol line colour and width possible
https://bugs.kde.org/show_bug.cgi?id=358358 Ralf Habacker changed: What|Removed |Added Summary|No change of association|No change of association |symbol colour possible |symbol line colour and ||width possible -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358358] No change of association symbol line colour and width possible
https://bugs.kde.org/show_bug.cgi?id=358358 --- Comment #1 from Ralf Habacker --- Symbol line width could also no be changed. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 358336] Allow for article previews to be next to the list instead of below
https://bugs.kde.org/show_bug.cgi?id=358336 avlas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from avlas --- Indeed. How could I miss this feature all this time...! I guess I just expected it to be inside akregator settings as for kmail. Sorry for the noise -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358365] Complete refactoring of line color and line with based setting to QPen.
https://bugs.kde.org/show_bug.cgi?id=358365 --- Comment #1 from Ralf Habacker --- Git commit c14b580a5f42358d9dfbd916b3afc315e12ffd51 by Ralf Habacker. Committed on 22/01/2016 at 10:32. Pushed by habacker into branch 'Applications/15.12'. Fix 'No change of association symbol line colour and width possible'. The bug is caused by two issues: 1. line color changes are not routed through the virtual method setLineColor() 2. class AssociationLine did not propagate line color changes to the related symbols. This patch includes a minor refactoring in class AssociationLine to provide the standard pen based api, which is required to set symbol pen. Related: bug 358358 FIXED-IN:2.18.2 (KDE Applications 15.12.2) M +23 -8umbrello/umlwidgets/associationline.cpp M +2-0umbrello/umlwidgets/associationline.h M +16 -0umbrello/umlwidgets/associationwidget.cpp M +2-0umbrello/umlwidgets/associationwidget.h M +1-1umbrello/umlwidgets/boxwidget.cpp M +8-8umbrello/umlwidgets/widgetbase.cpp http://commits.kde.org/umbrello/c14b580a5f42358d9dfbd916b3afc315e12ffd51 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358358] No change of association symbol line colour and width possible
https://bugs.kde.org/show_bug.cgi?id=358358 Ralf Habacker changed: What|Removed |Added Latest Commit||http://commits.kde.org/umbr ||ello/c14b580a5f42358d9dfbd9 ||16b3afc315e12ffd51 Status|UNCONFIRMED |RESOLVED Version Fixed In||2.18.2 (KDE Applications ||15.12.2) Resolution|--- |FIXED --- Comment #2 from Ralf Habacker --- Git commit c14b580a5f42358d9dfbd916b3afc315e12ffd51 by Ralf Habacker. Committed on 22/01/2016 at 10:32. Pushed by habacker into branch 'Applications/15.12'. Fix 'No change of association symbol line colour and width possible'. The bug is caused by two issues: 1. line color changes are not routed through the virtual method setLineColor() 2. class AssociationLine did not propagate line color changes to the related symbols. This patch includes a minor refactoring in class AssociationLine to provide the standard pen based api, which is required to set symbol pen. Related: bug 358365 FIXED-IN:2.18.2 (KDE Applications 15.12.2) M +23 -8umbrello/umlwidgets/associationline.cpp M +2-0umbrello/umlwidgets/associationline.h M +16 -0umbrello/umlwidgets/associationwidget.cpp M +2-0umbrello/umlwidgets/associationwidget.h M +1-1umbrello/umlwidgets/boxwidget.cpp M +8-8umbrello/umlwidgets/widgetbase.cpp http://commits.kde.org/umbrello/c14b580a5f42358d9dfbd916b3afc315e12ffd51 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 358304] Ark does not open ISO files with UDF filesystem.
https://bugs.kde.org/show_bug.cgi?id=358304 --- Comment #10 from Elvis Angelaccio --- Git commit ced29dc40b5d33b595862c0c20b01e588655cd10 by Elvis Angelaccio. Committed on 22/01/2016 at 10:33. Pushed by elvisangelaccio into branch 'master'. Warn the user when trying to open ISO images with UDF filesystem. Libarchive does not currently support ISO9660 images with UDF filesystem. We can at least warn the user about this. M +9-0part/part.cpp http://commits.kde.org/ark/ced29dc40b5d33b595862c0c20b01e588655cd10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #115 from painless roaster --- (In reply to Anthony from comment #112) > (In reply to painless roaster from comment #110) > Did you use Breeze? https://bugs.kde.org/show_bug.cgi?id=357800 > Select Oxygen LookAndFeeel, logout - login make same tests. Leak (new test with thermal monitor) exists with oxygen and breeze . -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #10 from Joost VandeVondele --- Created attachment 96782 --> https://bugs.kde.org/attachment.cgi?id=96782&action=edit self-hosting output 2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #11 from Joost VandeVondele --- Created attachment 96783 --> https://bugs.kde.org/attachment.cgi?id=96783&action=edit self hosting output 3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #12 from Joost VandeVondele --- Since the error is recurring, I have now tried to run the self-hosting. Running : /data/vjoost/test/outer/install/bin/valgrind --sim-hints=enable-outer --trace-children=yes --smc-check=all-non-file --run-libc-freeres=no --tool=memcheck -v /data/vjoost/test/inner/install/bin/valgrind --suppressions=/data/vjoost/toolchain-r16494/install/valgrind.supp --max-stackframe=2168152 --error-exitcode=42 --vgdb-prefix=./inner --core-redzone-size=1000 --tool=memcheck -v /data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.sdbg ethanol_both_rcut10.0_e1-1_v1-4_RSR.inp (I.e. self-hosting with added redzone, on the our executable corresponding to a failed run, with its arguments and parameters), I get a seemingly correct run. The output will be attached as out.innerouter.2 . Maybe it is worthwhile to look with expert eyes. However, after observing in that output a warning on stack switching, I added --max-stackframe=68009224472 (as suggested, seems a bit large;-), and that lead to a run with some other error (Memcheck: the 'impossible' happened: create_MC_Chunk: shadow area is accessible). -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 358367] New: Disable touchpad when laptop is closed.
https://bugs.kde.org/show_bug.cgi?id=358367 Bug ID: 358367 Summary: Disable touchpad when laptop is closed. Product: Touchpad-KCM Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: daemon Assignee: rajeeshknamb...@gmail.com Reporter: oliv...@churlaud.com Currently if I close my laptop and take it, the screen touches the touchpad and it does thing (open app/document, select items...). It would be better to disable it when the laptop is closed. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 350608] settings window too high
https://bugs.kde.org/show_bug.cgi?id=350608 maxir...@gmail.com changed: What|Removed |Added CC||maxir...@gmail.com --- Comment #5 from maxir...@gmail.com --- I'm having this bug too on Plasma 5.5.3 Qt 5.5.1 I can still confirm the dialog box using the TAB key but it's a bit annoying. I can't resize it to a lower height too, and trying to move the window up it kinda "hit" the top margin on the screen and won't go higher. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358368] New: Files to be opened with "%u" are opened like "%f"
https://bugs.kde.org/show_bug.cgi?id=358368 Bug ID: 358368 Summary: Files to be opened with "%u" are opened like "%f" Product: dolphin Version: 15.08.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: cyberb...@gmx.de For example: I have my own definition (see screenshot) of file type "*.old" for kwrite with command "kwrite %u". The files on "sftp://.../x.old"; are opened from a local directory "~/.cache/kioexec/.." (and are not stored remotely on ctrl-s!!!). If I use the right-click option "open with" and type "kwrite %u" it works like expected. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358368] Files to be opened with "%u" are opened like "%f"
https://bugs.kde.org/show_bug.cgi?id=358368 --- Comment #1 from H.H. --- Created attachment 96784 --> https://bugs.kde.org/attachment.cgi?id=96784&action=edit Showing my *.old file configuration -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage
https://bugs.kde.org/show_bug.cgi?id=358261 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 355415] Cannot connect to Google Hangouts
https://bugs.kde.org/show_bug.cgi?id=355415 --- Comment #12 from Thomas Van Parys --- Is there a way to get a list of where Telepathy is storing it's data? I've removed all accounts in the config panel, deleted ~/.config/libaccounts-glib and ~/.config/signond, all mentions of ktp in ~/.config and in the (old?) ~/.kde directory, and still, even after reboot, it is trying to connect to my XMPP account. So somewhere some old info is still lingering, but I don't see where. Fedora now updated to 15.12.1. Trying that now, so far without success. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352149] when SelectedTags at startup is a bundle auto-tag ; the preset list is empty
https://bugs.kde.org/show_bug.cgi?id=352149 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- Well, right now, it doesn't happen with the default tags that come with krita, but it does still happen with the bundle autotags. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351146] Shortcut for pause/next/prev when plasmoid is active
https://bugs.kde.org/show_bug.cgi?id=351146 --- Comment #1 from Kai Uwe Broulik --- Interesting idea, however, you could use Tab to navigate to the buttons, and there are also global shortcuts so you wouldn't actually need to open the applet at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 --- Comment #30 from AJslye --- (In reply to Bassio from comment #28) > This happened to me after setting up the kubuntu-ppa backports to upgrade to > plasma 5.5.3. > I am on Kubuntu Wily. > > Symptoms: > On the SDDM login, after I enter the username and password, and instead of > showing the plasma desktop, a black screen comes over, with only the cursor > visible. > After a while this black screen becomes responsive to CTRL+ALT+Backspace, > which when pressed now shows up a new SDDM login screen. The SDDM screen can > thus show up 2 or maybe 3 times. > Another symptom is that the kcm module for SDDM was hanging (only when > accessed through the system settings and not directly through the > application launcher) > I have an NVIDIA GTX 970 but I was using the open source Nouveau driver. > > Different to what others were saying here, changing the Breeze theme (to > Maui or Maldives) did not solve this problem. > > What worked for me though was when I switched my driver to the Nvidia > binary. This helped resolve the issue and now I can login, even using the > Breeze SDDM theme. I think your issue is a different one since your SDDM is not reseting back to itself on it's own. I believe your issue has more to due with your Nvidia chip, the nouveau drivers, mesa and possibly the compositor. The kcm hang issue is also another issue that been around for a while. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 356909] Virtual desktop switcher shows minimized windows when setting "Keep window thumbnails" to "Always" in KWin
https://bugs.kde.org/show_bug.cgi?id=356909 --- Comment #5 from Alexander Schlarb --- Martin Gräßlin: Could you please explain to me why KWin sets the _NET_WM_STATE_HIDDEN atom, if even you yourself refuse to make use of it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] New: Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 Bug ID: 358369 Summary: Plasma crashed after opening an HTML5 video in Chrome Product: kwin Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: superrobowiz...@gmail.com Application: kwin_x11 (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Navigating to a youtube HTML5 video: if Chrome is in fullscreen, it always happens. If Chrome is not, it only sometimes happens. - Custom settings of the application: I use the Diamond desktop them, the breeze-hacked cursors, and breeze loock & feel as well as spladch screen. I also use the following desktop effects: window blur at 50%, mouse click animation, background contrast, fade, glide, login, logout, maximize, sliding popups, translucency (10, 8, 10, 10, 10, disabled), window aperture, wobbly windows (8, 75, 10), minimize animation, dialog parent, dim screen for administrator mode, slide, desktop grid, and present windows. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fed65bac880 (LWP 5045))] Thread 4 (Thread 0x7fed44eb8700 (LWP 5073)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7fed6568e735 in select () at ../sysdeps/unix/syscall-template.S:81 #2 0x7fed63cc590f in qt_safe_select (nfds=14, fdread=fdread@entry=0x7fed38000a98, fdwrite=fdwrite@entry=0x7fed38000d28, fdexcept=fdexcept@entry=0x7fed38000fb8, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #3 0x7fed63cc740e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fed38000fb8, writefds=0x7fed38000d28, readfds=0x7fed38000a98, nfds=, this=0x7fed380008e0) at kernel/qeventdispatcher_unix.cpp:320 #4 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fed38000900, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #5 0x7fed63cc793e in QEventDispatcherUNIX::processEvents (this=0x7fed380008e0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #6 0x7fed63c7075a in QEventLoop::exec (this=this@entry=0x7fed44eb7d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7fed63a8e3d4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7fed5e56df85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fed63a932be in QThreadPrivate::start (arg=0x123dfc0) at thread/qthread_unix.cpp:337 #10 0x7fed64cc86aa in start_thread (arg=0x7fed44eb8700) at pthread_create.c:333 #11 0x7fed65697eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fed3e6f6700 (LWP 5130)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fed62c07114 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fed62c07159 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fed64cc86aa in start_thread (arg=0x7fed3e6f6700) at pthread_create.c:333 #4 0x7fed65697eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fed32dff700 (LWP 5421)): #0 0x7fed6568e743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fed63cc590f in qt_safe_select (nfds=25, fdread=fdread@entry=0x7feca80d1588, fdwrite=fdwrite@entry=0x7feca80d1818, fdexcept=fdexcept@entry=0x7feca80d1aa8, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fed63cc740e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7feca80d1aa8, writefds=0x7feca80d1818, readfds=0x7feca80d1588, nfds=, this=0x7feca8039d30) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7feca80d13f0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fed63cc793e in QEventDispatcherUNIX::processEvents (this=0x7feca8039d30, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fed63c7075a in QEventLoop::exec (this=this@entry=0x7fed32dfed20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fed63a8e3d4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fed5e56df85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fed63a932be in QThreadPrivate::start (arg=0x1948e60) at thread/qthread_unix.cpp:337 #9 0x7fed64cc86aa in start_thread (arg=0x7fed32dff700) at pthread_create.c:333 #10 0x7fed65697eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fe
[KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason
https://bugs.kde.org/show_bug.cgi?id=355928 tuxfus...@gmail.com changed: What|Removed |Added CC||tuxfus...@gmail.com --- Comment #10 from tuxfus...@gmail.com --- Same here, repeats every 12 seconds exactly Arch Linux, plasma 5 shortened output from "journalctl -b -t kdeinit5 -t kscreen_backend_launcher" : Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kdeinit5[892]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kdeinit5[892]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:30 hal8000 kdeinit5[892]: kscreen.kded: Change detected Jan 22 11:00:31 hal8000 kdeinit5[892]: kscreen.kded: Saving current config to file Jan 22 11:00:31 hal8000 kdeinit5[892]: kscreen.kded: Calculating config ID for KScreen::Config(0xd3f210) Jan 22 11:00:31 hal8000 kdeinit5[892]: kscreen.kded: Part of the Id: "382290b851cb5c7fff583389bf3bdc61" Jan 22 11:00:31 hal8000 kdeinit5[892]: kscreen.kded: Config ID: "2d0606ab1e3d55cda67323465ed3dec6" Jan 22 11:00:31 hal8000 kdeinit5[892]: kscreen.kded: Config saved on: "/home/ken/.local/share/kscreen/2d0606ab1e3d55cda67323465ed3dec6" Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kdeinit5[892]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kdeinit5[892]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launcher[921]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 639 , Name: "HDMI-0" ) ( "HDMI-0" ) Jan 22 11:00:42 hal8000 kscreen_backend_launch
[umbrello] [Bug 358091] Add value field to Enum Literal
https://bugs.kde.org/show_bug.cgi?id=358091 Ralf Habacker changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||2.18.80 (KDE Applications ||16.03.80) Resolution|--- |FIXED Latest Commit||http://commits.kde.org/umbr ||ello/af8a6492b0e7a111d379e9 ||e3828a248390bb4b05 --- Comment #1 from Ralf Habacker --- Git commit af8a6492b0e7a111d379e9e3828a248390bb4b05 by Ralf Habacker, on behalf of Tzvetelin Katchov. Committed on 22/01/2016 at 12:12. Pushed by habacker into branch 'master'. Add value field to Enum Literal The "value" field is an extension to the UML 2.5 metamodel. It manages the internal representation of enumeration value in system programming languages. Add value field to new Enum Literal properties dialog, and class UMLEnumLiteral, and widget Enum. Add new attribute "value" to "UML:EnumerationLiteral" element in xmi file format, and increase the version of XMI_FILE_VERSION. FIXED-IN:2.18.80 (KDE Applications 16.03.80) REVIEW:126612 M +1-0umbrello/CMakeLists.txt A +104 -0umbrello/dialogs/umlenumliteraldialog.cpp [License: GPL (v3+)] A +53 -0umbrello/dialogs/umlenumliteraldialog.h [License: GPL (v3+)] M +53 -17 umbrello/umlmodel/enumliteral.cpp M +15 -1umbrello/umlmodel/enumliteral.h M +2-2umbrello/umlwidgets/enumwidget.cpp M +2-2umbrello/version.h http://commits.kde.org/umbrello/af8a6492b0e7a111d379e9e3828a248390bb4b05 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358370] New: Crash when using NoMachine to remote login.
https://bugs.kde.org/show_bug.cgi?id=358370 Bug ID: 358370 Summary: Crash when using NoMachine to remote login. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sird...@bydeiu.net Application: polkit-kde-authentication-agent-1 (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.3.3-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: Using NoMachine client from Windows to acces a NoMachine server (with ssh) on KDE Plasma 5 desktop on Fedora 23, causes all sorts of crashes, starting with kdeinit5, plasmashell, kwin etc. - Unusual behavior I noticed: Desktop dissapears, plasmashell crashes, but process remains. The crash can be reproduced sometimes. -- Backtrace: Application: PolicyKit1 KDE Agent (polkit-kde-authentication-agent-1), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa170840900 (LWP 2319))] Thread 5 (Thread 0x7fa155bf6700 (LWP 2320)): #0 0x7fa16c645fdd in poll () from /lib64/libc.so.6 #1 0x7fa168fd1272 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7fa168fd2ee7 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7fa157dbfda9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7fa16d2623de in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7fa168ba660a in start_thread () from /lib64/libpthread.so.0 #6 0x7fa16c651a4d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fa14c24e700 (LWP 2323)): #0 0x7fa16c641bcd in read () from /lib64/libc.so.6 #1 0x7fa169a14390 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7fa1699d0c64 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7fa1699d1110 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7fa1699d127c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fa1699d12b9 in glib_worker_main () from /lib64/libglib-2.0.so.0 #6 0x7fa1699f7835 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #7 0x7fa168ba660a in start_thread () from /lib64/libpthread.so.0 #8 0x7fa16c651a4d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fa143fff700 (LWP 2324)): #0 0x7fa169a15737 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7fa1699d108e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fa1699d14f2 in g_main_loop_run () from /lib64/libglib-2.0.so.0 #3 0x7fa1696e7336 in gdbus_shared_thread_func () from /lib64/libgio-2.0.so.0 #4 0x7fa1699f7835 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #5 0x7fa168ba660a in start_thread () from /lib64/libpthread.so.0 #6 0x7fa16c651a4d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa14133e700 (LWP 3653)): #0 0x7fa168babb10 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa149d293b3 in radeon_drm_cs_emit_ioctl () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa149d28b07 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa168ba660a in start_thread () from /lib64/libpthread.so.0 #4 0x7fa16c651a4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa170840900 (LWP 2319)): [KCrash Handler] #5 0x7fa157dd055c in QXcbScreen::mapFromNative(QPoint const&) const () from /lib64/libQt5XcbQpa.so.5 #6 0x7fa157dd89ba in QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () from /lib64/libQt5XcbQpa.so.5 #7 0x7fa157dc1afd in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /lib64/libQt5XcbQpa.so.5 #8 0x7fa157dc2433 in QXcbConnection::processXcbEvents() () from /lib64/libQt5XcbQpa.so.5 #9 0x7fa16d473161 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7fa16e5d341c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7fa16e5d88e6 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7fa16d44373b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7fa16d445b36 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7fa16d499aa3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7fa1699d0e3a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7fa1699d11d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #17 0x7fa1699d127c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7fa16d499eaf in QEventDispatcherGlib::processEvents(QFlags) () from /lib
[okular] [Bug 358371] New: Forms in the document (see URL) are displayed with black background, instead of white.
https://bugs.kde.org/show_bug.cgi?id=358371 Bug ID: 358371 Summary: Forms in the document (see URL) are displayed with black background, instead of white. Product: okular Version: unspecified Platform: Fedora RPMs URL: https://www.google.ch/url?sa=t&rct=j&q=&esrc=s&source= web&cd=1&ved=0ahUKEwjXie6Iqb3KAhVJn3IKHb4ODQkQFgg0MAA& url=https%3A%2F%2Fwww.mieterverband.ch%2Fdam%2Fjcr%3A5 aa1368f-0532-4fd0-ad71-404076d2b260%2Fvert-untermietve rtrag.pdf&usg=AFQjCNHXM68fyqSk-3I0mooHkuuPYTlgUQ OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: wgzimmer-zu...@gmx.ch When I open the document (see URL) I cannot fill in any of the forms as they have a black background. I tested this both on Fedora 22 with XFCE 4.12 and Linux Mint 17.3 with the current XFCE version. I can open and edit the document with the Adobe program. Reproducible: Always Steps to Reproduce: 1. open URL 2. 3. Actual Results: Forms show black background. Expected Results: Background should be white. Okular Version 0.22.0 (Using KDE Development Platform 4.14.14), XFCE 4.12 on Fedora 22. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=352259, ||https://bugreports.qt.io/br ||owse/QTBUG-50368 Resolution|--- |UPSTREAM Component|general |aurorae Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lübking --- Driver bug, induced by QtQuick as used by the aurorae decoration engine. The crashes should not occur with the breeze decoration. It looks a hell lot like https://bugreports.qt.io/browse/QTBUG-50368, but that's about inactive X screens - is this on bare metal or some virtual machine, vnc etc.? Also check whether all backtraces follow the same pattern or this may be a red herring on bug #352259. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352259] segfault in QV4::ExecutionEngine::toVariant()
https://bugs.kde.org/show_bug.cgi?id=352259 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=358369 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358372] New: KDE System Settings Crashed applying changes to Trackpad configuration
https://bugs.kde.org/show_bug.cgi?id=358372 Bug ID: 358372 Summary: KDE System Settings Crashed applying changes to Trackpad configuration Product: systemsettings Version: 5.4.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: emeraldd.ch...@gmail.com Application: systemsettings5 (5.4.1) Qt Version: 5.4.2 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was attempting to adjust the sensitivity and tap delays of the track pad and system settings crashed. I experienced this crash twice, once with no immediately discernable trigginer action and the second time when hititng the apply button. Oddly enough, it would appear that the changes have actually been applied to the system. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbe967d800 (LWP 2249))] Thread 2 (Thread 0x7fbbd6716700 (LWP 2250)): #0 0x7fbbe5e148dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fbbe3b24bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fbbe3b2674f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fbbd94afa39 in QXcbEventReader::run (this=0x1271dd0) at qxcbconnection.cpp:1105 #4 0x7fbbe65072be in QThreadPrivate::start (arg=0x1271dd0) at thread/qthread_unix.cpp:337 #5 0x7fbbe32af6aa in start_thread (arg=0x7fbbd6716700) at pthread_create.c:333 #6 0x7fbbe5e1feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fbbe967d800 (LWP 2249)): [KCrash Handler] #6 QVector::count (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:202 #7 QStandardItemModel::mimeData (this=, indexes=...) at itemmodels/qstandarditemmodel.cpp:2988 #8 0x7fbbe7de8878 in QIconModeViewBase::filterStartDrag (this=0x1c1df20, supportedActions=...) at itemviews/qlistview.cpp:2697 #9 0x7fbbe7de824f in QListView::startDrag (this=this@entry=0x1c0afe0, supportedActions=...) at itemviews/qlistview.cpp:884 #10 0x7fbbe7dc9f73 in QAbstractItemView::mouseMoveEvent (this=this@entry=0x1c0afe0, event=event@entry=0x7fff798554e0) at itemviews/qabstractitemview.cpp:1770 #11 0x7fbbe7de7d87 in QListView::mouseMoveEvent (this=0x1c0afe0, e=0x7fff798554e0) at itemviews/qlistview.cpp:773 #12 0x7fbbe7bad188 in QWidget::event (this=this@entry=0x1c0afe0, event=event@entry=0x7fff798554e0) at kernel/qwidget.cpp:9023 #13 0x7fbbe7ca776e in QFrame::event (this=0x1c0afe0, e=0x7fff798554e0) at widgets/qframe.cpp:526 #14 0x7fbbe7dcaa4b in QAbstractItemView::viewportEvent (this=0x1c0afe0, event=0x7fff798554e0) at itemviews/qabstractitemview.cpp:1689 #15 0x7fbbe66e6d0c in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x1243ca0, receiver=receiver@entry=0x1c1dee0, event=event@entry=0x7fff798554e0) at kernel/qcoreapplication.cpp:1031 #16 0x7fbbe7b6ab6c in QApplicationPrivate::notify_helper (this=this@entry=0x1243ca0, receiver=receiver@entry=0x1c1dee0, e=e@entry=0x7fff798554e0) at kernel/qapplication.cpp:3716 #17 0x7fbbe7b70c7a in QApplication::notify (this=, receiver=0x1c1dee0, e=0x7fff798554e0) at kernel/qapplication.cpp:3280 #18 0x7fbbe66e6f1b in QCoreApplication::notifyInternal (this=0x7fff79855da0, receiver=receiver@entry=0x1c1dee0, event=event@entry=0x7fff798554e0) at kernel/qcoreapplication.cpp:935 #19 0x7fbbe7b6f6f2 in QCoreApplication::sendSpontaneousEvent (event=0x7fff798554e0, receiver=0x1c1dee0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x1c1dee0, event=event@entry=0x7fff798554e0, alienWidget=alienWidget@entry=0x1c1dee0, nativeWidget=0x13fd170, buttonDown=buttonDown@entry=0x7fbbe8090a10 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2751 #21 0x7fbbe7bc4440 in QWidgetWindow::handleMouseEvent (this=this@entry=0x1472950, event=event@entry=0x7fff79855900) at kernel/qwidgetwindow.cpp:543 #22 0x7fbbe7bc678b in QWidgetWindow::event (this=0x1472950, event=0x7fff79855900) at kernel/qwidgetwindow.cpp:210 #23 0x7fbbe7b6ab8c in QApplicationPrivate::notify_helper (this=this@entry=0x1243ca0, receiver=receiver@entry=0x1472950, e=e@entry=0x7fff79855900) at kernel/qapplication.cpp:3720 #24 0x7fbbe7b70230 in QApplication::notify (this=0x7fff79855da0, receiver=0x1472950, e=0x7fff79855900) at kernel/qapplication.cpp:3503 #25 0x7fbbe66e6f1b in QCoreApplication::notifyInternal (this=0x7fff79855da0, receiver=receiver@entry=0x1472950, event=event@entry
[Bluedevil] [Bug 302964] Show link to "Downloaded" folder in bluetooth:/ kio
https://bugs.kde.org/show_bug.cgi?id=302964 David Rosca changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/blue ||devil/1f0dc2e3dcd2f098089c0 ||561322e9b5ebf052551 --- Comment #3 from David Rosca --- Git commit 1f0dc2e3dcd2f098089c0561322e9b5ebf052551 by David Rosca, on behalf of Kai Uwe Broulik. Committed on 22/01/2016 at 12:33. Pushed by drosca into branch 'master'. Add link to "Downloaded Files" directory in kio bluetooth This patch adds a link to the folder configured for "Download folder" to the bluetooth:/ kio. REVIEW: 108503 M +3-0src/kio/bluetooth/CMakeLists.txt M +15 -0src/kio/bluetooth/kiobluetooth.cpp M +5-0src/kio/bluetooth/kiobluetooth.h http://commits.kde.org/bluedevil/1f0dc2e3dcd2f098089c0561322e9b5ebf052551 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 fabrice salvaire changed: What|Removed |Added CC||fabrice.salva...@orange.fr --- Comment #42 from fabrice salvaire --- >From the point of view of a lambda user (on Fedora 24) something is wrong with the actual Plasma UI layout. Peoples will consider the foreground aspects and not the background works. With French translation, the application launcher must be larger since the menu looks like : Favoris Applicat... Ordinat... Historiq... Quitter instead of Favoris Applicat/ion Ordinat/eur Historiq/ue Quitter Same for the top right desktop corner button popup, text is truncated without elision. UI designers should be aware some languages use more space than English. The network applet doesn't have enough place for the graph. And the way to resize the dialogue is not intuitive. We have to know the pin workaround. I understand the priority dilemma but the lambda user will see theses issues first. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 357699] Disk Quota widget does nothing and is missing icon etc.
https://bugs.kde.org/show_bug.cgi?id=357699 bill p. (aka google01103) changed: What|Removed |Added CC||dweeble01...@gmail.com --- Comment #1 from bill p. (aka google01103) --- when hovering the widget do you get any messages like "please install quota? if so then the quota package is not installed. Once installed I get the message "no quota restrictions found" as they have not be set. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #1 from Jan Hudec --- I am now certain it started after trying to answer email, because when I started it under valgrind it filtered the invalid write and two composers opened. I am attaching the valgrind memcheck output. There are two invalid writes, presumably one in each composer that starts. The backtraces clearly show they are MessageComposer-related. Unfortunately Debian does not seem to have debug information for the /usr/lib/libkmailprivate.so.4.14.10, which appears on the last line of the stack trace. All of the MessageComposer and everything called from it is decoded correctly though. Hope it helps. Kind regards, Jan -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358373] New: crash some minutes after resume
https://bugs.kde.org/show_bug.cgi?id=358373 Bug ID: 358373 Summary: crash some minutes after resume Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: msch...@gentoo.org Application: kdeinit5 () Qt Version: 5.5.1 Operating System: Linux 4.1.6-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I resumed my laptop from s2ram. Then I plugged in my external monitor. NO crash! I started to work. Often, my laptop goes to sleep again when I close the laptop lid (Which it should not do when there is an external monitor plugged in... but this is another story) . It did not go to sleep this time. BUT after a few minutes this crash happend AND my laptop immediately went into sleep mode. After resuming I am now writing this bugreport. -- Backtrace: Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f411e766800 (LWP 32577))] Thread 6 (Thread 0x7f41096ed700 (LWP 32580)): #0 0x7f411d06164d in poll () from /lib64/libc.so.6 #1 0x7f411c7c7ac2 in poll (__timeout=-1, __nfds=1, __fds=0x7f41096eccc0) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x7f5810, cond=cond@entry=0x7f5850, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x7f411c7c972f in xcb_wait_for_event (c=0x7f5810) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7f410b84ec89 in QXcbEventReader::run (this=0x8039e0) at qxcbconnection.cpp:1229 #5 0x7f411d3be4f2 in QThreadPrivate::start (arg=0x8039e0) at thread/qthread_unix.cpp:331 #6 0x7f411ae18444 in start_thread () from /lib64/libpthread.so.0 #7 0x7f411d06a6ad in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f40fe551700 (LWP 32613)): #0 0x7f411d06164d in poll () from /lib64/libc.so.6 #1 0x7f411a0d0f1c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f40f80013c0, timeout=-1, context=0x7f40f80009b0) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f40f80009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7f411a0d102c in g_main_context_iteration (context=0x7f40f80009b0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f411d5b903c in QEventDispatcherGlib::processEvents (this=0x7f40f80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #5 0x7f411d56a27a in QEventLoop::exec (this=this@entry=0x7f40fe550d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f411d3b9a84 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f4100ab9957 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #8 0x7f411d3be4f2 in QThreadPrivate::start (arg=0x813f20) at thread/qthread_unix.cpp:331 #9 0x7f411ae18444 in start_thread () from /lib64/libpthread.so.0 #10 0x7f411d06a6ad in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f40fdd50700 (LWP 32614)): #0 0x7f411d06164d in poll () from /lib64/libc.so.6 #1 0x7f411a0d0f1c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f40f00013c0, timeout=-1, context=0x7f40f9b0) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f40f9b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7f411a0d102c in g_main_context_iteration (context=0x7f40f9b0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f411d5b903c in QEventDispatcherGlib::processEvents (this=0x7f40f8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #5 0x7f411d56a27a in QEventLoop::exec (this=this@entry=0x7f40fdd4fdc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f411d3b9a84 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f411d3be4f2 in QThreadPrivate::start (arg=0x8303e0) at thread/qthread_unix.cpp:331 #8 0x7f411ae18444 in start_thread () from /lib64/libpthread.so.0 #9 0x7f411d06a6ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f40fd0a3700 (LWP 473)): #0 0x7f411d06164d in poll () from /lib64/libc.so.6 #1 0x7f411a0d0f1c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f40f40013c0, timeout=10048, context=0x7f40f40009b0) at /var/tmp/portage
[kontact] [Bug 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #2 from Jan Hudec --- Created attachment 96785 --> https://bugs.kde.org/attachment.cgi?id=96785&action=edit Valgrind memcheck trace I killed kontact after it started (successfully under valgrind). When I then started it, it crashed again, so I am quite sure the log corresponds to the faulty case. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 Jan Hudec changed: What|Removed |Added Component|general |mail -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 358188] compress to application/zip creates wrong file type (application/x-7z-compressed)
https://bugs.kde.org/show_bug.cgi?id=358188 --- Comment #3 from Bart De Ceulaer --- > You meant "application/zip"? Of course, that's what I meant, sorry, my mistake. And indeed, I forgot to mention that I unchecked the "automatically select filename extension" checkbox. I normally use this shortcut to create .cbz files (comic book reader), to be viewed via Okular. I will use one of the workarounds you described for the time being; no problem. Thanks for the support. Bart -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356048] kalarm always crashes when changing alarms
https://bugs.kde.org/show_bug.cgi?id=356048 David Jarvie changed: What|Removed |Added Version Fixed In||15.12.2 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||6af5386719f01cc3a71f9486807 ||c66b1b3da26d1 --- Comment #2 from David Jarvie --- Thanks for the information on how to reproduce the crash. I suspect that one of the library classes doesn't handle destruction properly, and allows the contentsChanged() signal to be emitted when it shouldn't, but KAlarm now ignores the unwanted signal. Fixed in commit 6af5386719f01cc3a71f9486807c66b1b3da26d1 (15.12 branch and master). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340447] [Plasma 5] Please add an xembed compatible system tray applet
https://bugs.kde.org/show_bug.cgi?id=340447 Moritz Augustin changed: What|Removed |Added CC||softw...@moritz-augustin.de --- Comment #12 from Moritz Augustin --- Maybe interesting for other people: plasma-workspace >= 5.5 seems to contain a workaround which provides a program "xembedsniproxy" making (a not-so-beautiful but functional) version of xembed-based tray icons available in the plasma tray. (This is at least true for the arch linux packages.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358374] New: Mouse pointer randomly disappears everywhere
https://bugs.kde.org/show_bug.cgi?id=358374 Bug ID: 358374 Summary: Mouse pointer randomly disappears everywhere Product: kwin Version: 5.5.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: gree...@greenrd.org I don't know what causes this. The invisible mouse pointer can still be moved and clicked because I can see its effects, but other than that I can't see where it is. It comes back by itself after a while. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #3 from Jan Hudec --- Created attachment 96786 --> https://bugs.kde.org/attachment.cgi?id=96786&action=edit One more valgrind trace When I started it next time, one more message editor came up. However the number of invalid writes remained two. I also noticed some invalid reads there. The standard error also showed these errors: kontact(9096) MessageList::Core::ModelPrivate::findMessageParent: Circular reference loop detected in the message tree kontact(9096) MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill: Circular In-Reply-To reference loop detected in the message tree kontact(9096) MessageList::Core::ModelPrivate::findMessageParent: Circular In-Reply-To reference loop detected in the message tree Not sure whether they are related; they appeared long after the point where it would have crashed without valgrind. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #4 from Jan Hudec --- I closed the message editors when running under valgrind. Since then, kontact starts up correctly again. This workaround isn't for mere mortals, but presumably there might be some way to remove the draft message via akonadi. I don't know how though; I restarted since it started crashing and something remembered there should be message editor open across it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356540] Krita Animation Beta - Moving First Frame Leaves Behind Blank Frame Instead of Empty
https://bugs.kde.org/show_bug.cgi?id=356540 Dmitry Kazakov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #4 from Dmitry Kazakov --- I'll mark this bug as LATER. We will probably fix it after 3.0 release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358374] Mouse pointer randomly disappears everywhere
https://bugs.kde.org/show_bug.cgi?id=358374 --- Comment #1 from Thomas Lübking --- Zoom effect related? Otherwise there's no chance than kwin hides the cursor - any client however may at any time, eg. konsole and videoplayers typically do after a short while. > It comes back by itself after a while. This does not sound like a bug (in kwin) to me then - we'd either break on the counter (in the zoom effect) or not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352149] when SelectedTags at startup is a bundle auto-tag ; the preset list is empty
https://bugs.kde.org/show_bug.cgi?id=352149 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krit ||a/42a7a211de6f271b0e8b1679d ||648ad684c6eae30 Resolution|--- |FIXED --- Comment #3 from Boudewijn Rempt --- Git commit 42a7a211de6f271b0e8b1679d648ad684c6eae30 by Boudewijn Rempt. Committed on 22/01/2016 at 13:32. Pushed by rempt into branch 'master'. This now loads the bundles at the end of loading all resources. M +0-4krita/plugins/extensions/resourcemanager/CMakeLists.txt M +13 -12 krita/plugins/extensions/resourcemanager/dlg_bundle_manager.cpp M +5-5krita/plugins/extensions/resourcemanager/dlg_bundle_manager.h M +2-2krita/plugins/extensions/resourcemanager/dlg_create_bundle.cpp M +3-3krita/plugins/extensions/resourcemanager/dlg_create_bundle.h M +5-57 krita/plugins/extensions/resourcemanager/resourcemanager.cpp M +3-20 krita/plugins/extensions/resourcemanager/resourcemanager.h M +2-0krita/ui/CMakeLists.txt M +1-0krita/ui/KisApplication.cpp C +48 -54 krita/ui/KisResourceBundle.cpp [from: krita/plugins/extensions/resourcemanager/resourcebundle.cpp - 090% similarity] C +7-5krita/ui/KisResourceBundle.h [from: krita/plugins/extensions/resourcemanager/resourcebundle.h - 094% similarity] C +11 -11 krita/ui/KisResourceBundleManifest.cpp [from: krita/plugins/extensions/resourcemanager/resourcebundle_manifest.cpp - 090% similarity] C +5-3krita/ui/KisResourceBundleManifest.h [from: krita/plugins/extensions/resourcemanager/resourcebundle_manifest.h - 094% similarity] M +21 -0krita/ui/kis_resource_server_provider.cpp M +6-3krita/ui/kis_resource_server_provider.h C +0-0krita/ui/resourcemanager/CMakeLists.txt [from: krita/plugins/extensions/resourcemanager/CMakeLists.txt - 100% similarity] A +1-0krita/ui/resourcemanager/NOTES C +0-0krita/ui/resourcemanager/dlg_bundle_manager.cpp [from: krita/plugins/extensions/resourcemanager/dlg_bundle_manager.cpp - 100% similarity] C +0-0krita/ui/resourcemanager/dlg_bundle_manager.h [from: krita/plugins/extensions/resourcemanager/dlg_bundle_manager.h - 100% similarity] C +0-0krita/ui/resourcemanager/dlg_create_bundle.cpp [from: krita/plugins/extensions/resourcemanager/dlg_create_bundle.cpp - 100% similarity] C +0-0krita/ui/resourcemanager/dlg_create_bundle.h [from: krita/plugins/extensions/resourcemanager/dlg_create_bundle.h - 100% similarity] A +9-0krita/ui/resourcemanager/kritaresourcemanager.json R +0-0krita/ui/resourcemanager/resourcebundle.cpp [from: krita/plugins/extensions/resourcemanager/resourcebundle.cpp - 100% similarity] R +0-0krita/ui/resourcemanager/resourcebundle.h [from: krita/plugins/extensions/resourcemanager/resourcebundle.h - 100% similarity] R +0-0krita/ui/resourcemanager/resourcebundle_manifest.cpp [from: krita/plugins/extensions/resourcemanager/resourcebundle_manifest.cpp - 100% similarity] R +0-0krita/ui/resourcemanager/resourcebundle_manifest.h [from: krita/plugins/extensions/resourcemanager/resourcebundle_manifest.h - 100% similarity] C +0-0krita/ui/resourcemanager/resourcemanager.cpp [from: krita/plugins/extensions/resourcemanager/resourcemanager.cpp - 100% similarity] C +0-0krita/ui/resourcemanager/resourcemanager.h [from: krita/plugins/extensions/resourcemanager/resourcemanager.h - 100% similarity] A +13 -0krita/ui/resourcemanager/resourcemanager.rc R +0-0krita/ui/resourcemanager/tests/CMakeLists.txt [from: krita/plugins/extensions/resourcemanager/tests/CMakeLists.txt - 100% similarity] C +0-0krita/ui/resourcemanager/tests/ResourceBundleTest.cpp [from: krita/plugins/extensions/resourcemanager/tests/ResourceBundleTest.cpp - 100% similarity] C +0-0krita/ui/resourcemanager/tests/ResourceBundleTest.h [from: krita/plugins/extensions/resourcemanager/tests/ResourceBundleTest.h - 100% similarity] C +---krita/ui/resourcemanager/tests/data/thumb.png [from: krita/plugins/extensions/resourcemanager/tests/data/thumb.png - 100% similarity] A +539 -0krita/ui/resourcemanager/wdgdlgbundlemanager.ui A +466 -0krita/ui/resourcemanager/wdgdlgcreatebundle.ui M +7-0krita/ui/tests/CMakeLists.txt R +4-4krita/ui/tests/ResourceBundleTest.cpp [from: krita/plugins/extensions/resourcemanager/tests/ResourceBundleTest.cpp - 096% similarity] R +0-0krita/ui/tests/ResourceBundleTest.h [from: krita/plugins/extensions/resourcemanager/tests/ResourceBundleTest.h - 100% similarity] R +---krita/ui/tests/data/thu
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #53 from jeremy9...@gmail.com --- Since this bug seems to be fixed with latest Nvidia drivers can someone take a look at this (small) bug please ? "Terminal Size" setting in profile ignored https://bugs.kde.org/show_bug.cgi?id=345403 And thanks for your work for trying to fix this bug even if (need to be confirmed by devs) it was in the Nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 --- Comment #16 from jeremy9...@gmail.com --- A reminder for this that need to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 338506] image wallpapers are blurry in scaled and scaled and cropped mode
https://bugs.kde.org/show_bug.cgi?id=338506 --- Comment #37 from jeremy9...@gmail.com --- That's disappointing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 348998] SDDM login manager configuration window can be unresponsive
https://bugs.kde.org/show_bug.cgi?id=348998 --- Comment #15 from jeremy9...@gmail.com --- Maybe it's a problem with some drivers ? Nvidia recently fixed their driver for a problem with Qt that impede KDE softs. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 --- Comment #17 from David Edmundson --- Please don't do "a reminder" emails. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 345403] "Terminal Size" setting in profile ignored
https://bugs.kde.org/show_bug.cgi?id=345403 --- Comment #25 from jeremy9...@gmail.com --- A reminder for this that need to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 --- Comment #18 from jeremy9...@gmail.com --- So please fix it ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop
https://bugs.kde.org/show_bug.cgi?id=350826 --- Comment #56 from jeremy9...@gmail.com --- ?? -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 358359] HIgh cpu consumption and apt-check process infinte fork
https://bugs.kde.org/show_bug.cgi?id=358359 stef changed: What|Removed |Added CC||s...@vogliaditerra.com --- Comment #1 from stef --- Same behaviour here: http://forum.ubuntu-it.org/viewtopic.php?f=30&t=606905 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 --- Comment #19 from David Edmundson --- Follow here: https://git.reviewboard.kde.org/r/126524/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357179] Email remains in inbox after moving it to a folder
https://bugs.kde.org/show_bug.cgi?id=357179 Daniel Hornung changed: What|Removed |Added CC||skna...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 --- Comment #20 from jeremy9...@gmail.com --- Thank you very much ! -- You are receiving this mail because: You are watching all bug changes.
