[plasmashell] [Bug 373749] Left/right arrow keys switch to one direction in RTL
https://bugs.kde.org/show_bug.cgi?id=373749 --- Comment #4 from Hamid --- Thank you. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373804] New: Crash when searching google for html5 tests
https://bugs.kde.org/show_bug.cgi?id=373804 Bug ID: 373804 Summary: Crash when searching google for html5 tests Product: konqueror Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: thesir...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.7.10-hardened x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: This system has seen KDE 5, but has never seen Konqueror before. Opened Konqueror. Searched google for html5 tests. Crash, no search results noticably shown -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe1e7dc37c0 (LWP 13464))] Thread 19 (Thread 0x7fe1d3722700 (LWP 13465)): #0 0x7fe1e77d8acd in poll () from /lib64/libc.so.6 #1 0x7fe1decd09d6 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7fe1decd2a6d in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fe1d56637a3 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe1e2f50978 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe1df35c5a0 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe1e77e24cd in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7fe1d2201700 (LWP 13466)): #0 0x7fe1e77ef6c0 in clock_gettime () from /lib64/libc.so.6 #1 0x7fe1e2fd9920 in do_gettime(long long*, long long*) () from /usr/lib64/libQt5Core.so.5 #2 0x7fe1e2fd9a12 in qt_gettime() () from /usr/lib64/libQt5Core.so.5 #3 0x7fe1e30ecc68 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x7fe1e30ed1d8 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe1e30ee361 in timerSourcePrepareHelper(GTimerSource*, int*) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe1e30ee471 in timerSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe1dd4a950a in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x7fe1dd4a9c6d in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #9 0x7fe1dd4a9e5d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7fe1e30eecac in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7fe1e30aad32 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #12 0x7fe1e2f4c4aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #13 0x7fe1e7f2b55a in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #14 0x7fe1e2f50978 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #15 0x7fe1df35c5a0 in start_thread () from /lib64/libpthread.so.0 #16 0x7fe1e77e24cd in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7fe1b5ae6700 (LWP 13523)): #0 0x7fe1e77d496d in write () from /lib64/libc.so.6 #1 0x7fe1e7769c67 in _IO_file_write () from /lib64/libc.so.6 #2 0x7fe1e77691f6 in new_do_write () from /lib64/libc.so.6 #3 0x7fe1e776a2c6 in _IO_file_xsputn () from /lib64/libc.so.6 #4 0x7fe1e773d289 in buffered_vfprintf () from /lib64/libc.so.6 #5 0x7fe1e773a495 in vfprintf () from /lib64/libc.so.6 #6 0x7fe1e77f0d5c in __fprintf_chk () from /lib64/libc.so.6 #7 0x7fe1bcb55c6e in _warn_helper () from /usr/lib64/libevent-2.0.so.5 #8 0x7fe1bcb55eaf in event_warn () from /usr/lib64/libevent-2.0.so.5 #9 0x7fe1bcb5a41f in epoll_dispatch () from /usr/lib64/libevent-2.0.so.5 #10 0x7fe1bcb4728e in event_base_loop () from /usr/lib64/libevent-2.0.so.5 #11 0x7fe1be3ceee6 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7fe1be3f6ffa in base::RunLoop::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7fe1be3e6893 in base::MessageLoop::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #14 0x7fe1be409c11 in base::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #15 0x7fe1be4069f1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #16 0x7fe1df35c5a0 in start_thread () from /lib64/libpthread.so.0 #17 0x7fe1e77e24cd in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7fe1b52e5700 (LWP 13524)): #0 0x7fe1df3623ef in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7fe1be40092b in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fe1be4009d5 in base::WaitableEvent::Wait() () from /usr/lib64/libQt5WebEngine
[kalzium] [Bug 372671] solver doesn't build with ocaml 4.04
https://bugs.kde.org/show_bug.cgi?id=372671 --- Comment #2 from Viktor Yu. Kovalskiy --- (In reply to Viktor Yu. Kovalskiy from comment #1) > (In reply to Antonio Rojas from comment #0) > > I can confirm this issue. > kalzium from git fails to build with ocaml-4.04 with the same error. > > I can build kalzium from git with ocaml-4.03. > > Maybe changelog from ocaml-4.04 helps: > > http://caml.inria.fr/pub/distrib/ocaml-4.04/notes/Changes Kalzium-16.12.0 fails to build with the same error. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373803] New: Konqueror crash at startup when startup page is set to blank page
https://bugs.kde.org/show_bug.cgi?id=373803 Bug ID: 373803 Summary: Konqueror crash at startup when startup page is set to blank page Product: konqueror Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: hkz85825...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: If the startup page in Konqueror is set to blank page, it will crash at startup. I'm using the newly upgraded 16.12. The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc5571ed840 (LWP 2096))] Thread 19 (Thread 0x7fc4f97fa700 (LWP 2116)): #0 0x7fc54c52310f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc52a95fbb0 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fc52a947cb0 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fc52a94804b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fc52a9438da in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fc52bb314ee in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fc52bb33984 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fc52bb339d5 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fc52bb33ab9 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #9 0x7fc52ada5604 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #10 0x7fc52ad8f595 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #11 0x7fc52adbe41a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #12 0x7fc52adba78c in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #13 0x7fc54c51d454 in start_thread () from /usr/lib/libpthread.so.0 #14 0x7fc556b307df in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7fc4f9ffb700 (LWP 2115)): #0 0x7fc54c52310f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc52adbd639 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fc52adbdc39 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fc52adbddf0 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fc52adba78c in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fc54c51d454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fc556b307df in clone () from /usr/lib/libc.so.6 Thread 17 (Thread 0x7fc4fa7fc700 (LWP 2114)): #0 0x7fc54323e82e in ?? () from /usr/lib/pulseaudio/libpulsecommon-9.0.so #1 0x7fc54323f0aa in ?? () from /usr/lib/pulseaudio/libpulsecommon-9.0.so #2 0x7fc5436a6b9c in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0 #3 0x7fc5436a6f9c in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #4 0x7fc5436a7040 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #5 0x7fc5436b5069 in ?? () from /usr/lib/libpulse.so.0 #6 0x7fc54324eed8 in ?? () from /usr/lib/pulseaudio/libpulsecommon-9.0.so #7 0x7fc54c51d454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fc556b307df in clone () from /usr/lib/libc.so.6 Thread 16 (Thread 0x7fc4faffd700 (LWP 2113)): #0 0x7fc54c5234b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc52adb1ac2 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fc52adb2375 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fc52ad93401 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fc52ada5604 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fc52ad8f595 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fc52adbe41a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fc52adba78c in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fc54c51d454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fc556b307df in clone () from /usr/lib/libc.so.6 Thread 15 (Thread 0x7fc4fb7fe700 (LWP 2112)): #0 0x7fc54c52310f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc52a43e88d in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fc52adbdcce in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fc52adbddf0 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fc52adba78c in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fc54c51d454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fc556b307df in clone () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7fc4fbfff700 (LWP 2111)): #0 0x7fc54c52310f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc52adb22e5 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x00
[marble] [Bug 373802] New: flatpak-kde-applications fails to compile: missing /app/files/share/applications/org.kde.marble.maps.desktop
https://bugs.kde.org/show_bug.cgi?id=373802 Bug ID: 373802 Summary: flatpak-kde-applications fails to compile: missing /app/files/share/applications/org.kde.marble.maps.desk top Product: marble Version: 2.1 (KDE Applications 16.12) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: brentonhorn...@gmail.com Target Milestone: --- I have tried to build the flatpak-kde-applications repo (https://github.com/KDE/flatpak-kde-applications) with make but it failed giving the error: Fetching git repo git://anongit.kde.org/marble.git Starting build of org.kde.marble.maps Cache hit for marble, skipping build Cache miss, checking out last cache hit Cleaning up Rewriting contents of org.kde.marble.maps.desktop Error: Can't load desktop file /home/fusion809/GitHub/others/flatpak-kde-applications/app/files/share/applications/org.kde.marble.maps.desktop: Error opening file /home/fusion809/GitHub/others/flatpak-kde-applications/app/files/share/applications/org.kde.marble.maps.desktop: No such file or directory Makefile:6: recipe for target 'org.kde.marble.app' failed make: *** [org.kde.marble.app] Error 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373738] Panel is unable to receive focus after opening Youtube video on Firefox
https://bugs.kde.org/show_bug.cgi?id=373738 --- Comment #5 from frag...@gmail.com --- The only messages I can see in the log are the following (when the tooltip is stuck): Initializing "kcm_input" : "kcminit_mouse" QXcbConnection: XCB error: 3 (BadWindow), sequence: 8389, resource id: 79691782, major code: 18 (ChangeProperty), minor code: 0 Initializing "kcm_input" : "kcminit_mouse" QXcbConnection: XCB error: 3 (BadWindow), sequence: 19207, resource id: 79691782, major code: 18 (ChangeProperty), minor code: 0 Initializing "kcm_input" : "kcminit_mouse" QXcbConnection: XCB error: 3 (BadWindow), sequence: 42301, resource id: 79691782, major code: 18 (ChangeProperty), minor code: 0 *** Does it make sense? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 --- Comment #3 from Andreas Hartmann --- Created attachment 102849 --> https://bugs.kde.org/attachment.cgi?id=102849&action=edit Hardware description and kwin options -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373801] New: why won't it work
https://bugs.kde.org/show_bug.cgi?id=373801 Bug ID: 373801 Summary: why won't it work Product: krita Version: 3.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bekkaplayminecr...@gmail.com Target Milestone: --- when I tried using my tablet the mouse wouldn't move!!! if you have the time plz write back.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 --- Comment #2 from Andreas Hartmann --- Created attachment 102848 --> https://bugs.kde.org/attachment.cgi?id=102848&action=edit example 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 --- Comment #1 from Andreas Hartmann --- Created attachment 102847 --> https://bugs.kde.org/attachment.cgi?id=102847&action=edit example 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] New: Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 Bug ID: 373800 Summary: Frequent kwin crashes Product: kwin Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andihartm...@freenet.de Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.38-1-desktop x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I did nothing particular. But I can see it most of the time at the beginning of a session. Afterwards it is working mostly for longer time. But comes up again. There are two more crashes from yesterday. Maybe, it is related to starting new programms? I could see it while starting the process list (CTRL-ESC) or Firefox, e.g.. But this is just an assumption. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f84dec5b940 (LWP 3481))] Thread 6 (Thread 0x7f84b2ffe700 (LWP 3749)): #0 0x7f84dba841f9 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #1 0x7f84dba84527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f84dba33fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f84db86ef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f84d64089b8 in () at /usr/lib64/libQt5Qml.so.5 #5 0x7f84db8739e9 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #7 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f84a1bca700 (LWP 3614)): #0 0x7f84de6990af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f84da9f793b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f84da9f7969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f84a2dd3700 (LWP 3609)): #0 0x7f84de6990af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f84b2186533 in () at /usr/lib64/dri/r600_dri.so #2 0x7f84b2185d57 in () at /usr/lib64/dri/r600_dri.so #3 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f84b3fff700 (LWP 3592)): #0 0x7f84de3c6b03 in select () at /lib64/libc.so.6 #1 0x7f84dba82849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f84dba840c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f84dba84527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f84dba33fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f84db86ef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f84d64089b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f84db8739e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f84c31fb700 (LWP 3516)): #0 0x7f84de3c6b03 in select () at /lib64/libc.so.6 #1 0x7f84dba82849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f84dba840c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f84dba84527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f84dba33fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f84db86ef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f84d55db1d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f84db8739e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f84dec5b940 (LWP 3481)): [KCrash Handler] #6 0x7f84d63f4dd0 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #7 0x7f84d63f624a in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #8 0x7f84d63ff2f6 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f84d638d93b in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5 #10 0x7f84d638d9f7 in QQmlComponentPrivate::completeCreate() () at /usr/lib64/libQt5
[Touchpad-KCM] [Bug 373794] System setting crashes when trying to access Touchpad settings on Wayland
https://bugs.kde.org/show_bug.cgi?id=373794 Christoph Feck changed: What|Removed |Added Component|general |kcm Version|5.8.4 |unspecified Assignee|plasma-b...@kde.org |rajeeshknamb...@gmail.com Product|systemsettings |Touchpad-KCM -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373645] keyboard input not accepted
https://bugs.kde.org/show_bug.cgi?id=373645 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Christoph Feck --- Already reported as bug 373717. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373717] no keyboard input when trying to edit message
https://bugs.kde.org/show_bug.cgi?id=373717 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Please ask for help in a user forum of your distribution. If you cannot use your keyboard in GTK applications, it is certainly no KMail issue. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373781] Konqueror 5.0.97 crashes with qtwebengine
https://bugs.kde.org/show_bug.cgi?id=373781 Christoph Feck changed: What|Removed |Added Severity|critical|crash --- Comment #2 from Christoph Feck --- Could you use the 'bt' command in gdb to get an actual backtrace after the crash and add it here? For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 296093] Complete input not being displayed when using really big numbers
https://bugs.kde.org/show_bug.cgi?id=296093 Christoph Feck changed: What|Removed |Added CC||drankinatty@suddenlinkmail. ||com --- Comment #2 from Christoph Feck --- *** Bug 373719 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 373719] kcalc only displays 40-bits of 64-bit number in binary and lacks binary display in all but Numeral mode
https://bugs.kde.org/show_bug.cgi?id=373719 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- Please report one issue per ticket. The second issue you reported is bug 248264. *** This bug has been marked as a duplicate of bug 296093 *** -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 373799] New: Compilation error with cyrus-sasl 2.1.26
https://bugs.kde.org/show_bug.cgi?id=373799 Bug ID: 373799 Summary: Compilation error with cyrus-sasl 2.1.26 Product: kmailtransport Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dschep...@gmail.com Target Milestone: --- Compiling kmailtransport 16.12.0 gives several compilation errors: [ 37%] Building CXX object kioslave/src/smtp/CMakeFiles/kio_smtp.dir/command.cpp.o In file included from /home/daniel/src/kmailtransport/kmailtransport-16.12.0/kioslave/src/smtp/command.h:36:0, from /home/daniel/src/kmailtransport/kmailtransport-16.12.0/kioslave/src/smtp/command.cpp:32: /usr/include/sasl/sasl.h:228:35: error: typedef 'sasl_malloc_t' is initialized (use decltype instead) typedef void *sasl_malloc_t(size_t); ^ /usr/include/sasl/sasl.h:228:29: error: 'size_t' was not declared in this scope typedef void *sasl_malloc_t(size_t); ^~ /usr/include/sasl/sasl.h:229:29: error: typedef 'sasl_calloc_t' is initialized (use decltype instead) typedef void *sasl_calloc_t(size_t, size_t); ^~ /usr/include/sasl/sasl.h:229:29: error: 'size_t' was not declared in this scope /usr/include/sasl/sasl.h:229:37: error: 'size_t' was not declared in this scope typedef void *sasl_calloc_t(size_t, size_t); ^~ /usr/include/sasl/sasl.h:230:38: error: 'size_t' has not been declared typedef void *sasl_realloc_t(void *, size_t); ^~ /usr/include/sasl/sasl.h:233:33: error: variable or field 'sasl_set_alloc' declared void LIBSASL_API void sasl_set_alloc(sasl_malloc_t *, ^ /usr/include/sasl/sasl.h:233:33: error: 'sasl_malloc_t' was not declared in this scope /usr/include/sasl/sasl.h:233:48: error: expected primary-expression before ',' token LIBSASL_API void sasl_set_alloc(sasl_malloc_t *, ^ /usr/include/sasl/sasl.h:234:5: error: 'sasl_calloc_t' was not declared in this scope sasl_calloc_t *, ^ /usr/include/sasl/sasl.h:234:20: error: expected primary-expression before ',' token sasl_calloc_t *, ^ /usr/include/sasl/sasl.h:235:20: error: expected primary-expression before '*' token sasl_realloc_t *, ^ /usr/include/sasl/sasl.h:235:21: error: expected primary-expression before ',' token sasl_realloc_t *, ^ /usr/include/sasl/sasl.h:236:17: error: expected primary-expression before '*' token sasl_free_t *); ^ /usr/include/sasl/sasl.h:236:18: error: expected primary-expression before ')' token sasl_free_t *); ^ make[2]: *** [kioslave/src/smtp/CMakeFiles/kio_smtp.dir/build.make:159: kioslave/src/smtp/CMakeFiles/kio_smtp.dir/command.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:357: kioslave/src/smtp/CMakeFiles/kio_smtp.dir/all] Error 2 make: *** [Makefile:139: all] Error 2 The cyrus-sasl version is 2.1.26 (without any patches). It would appear the sasl.h header from that version is missing a #include . I found I can work around the issue and get kmailtransport to compile by adding #include to kioslave/src/smtp/command.h. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373798] New: Super (Windows) Key does not open the menu after suspend.
https://bugs.kde.org/show_bug.cgi?id=373798 Bug ID: 373798 Summary: Super (Windows) Key does not open the menu after suspend. Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: d.misdani...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Super key only works as Meta after suspend. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373797] Launching fullscreen applications freezes taskbar
https://bugs.kde.org/show_bug.cgi?id=373797 --- Comment #1 from sunshinehunte...@gmail.com --- I want to add that this problem didn't occur yet with League of Legends started with Wine, and that it doesn't always happen on first try (sometimes 2nd to 4th time). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373797] New: Launching fullscreen applications freezes taskbar
https://bugs.kde.org/show_bug.cgi?id=373797 Bug ID: 373797 Summary: Launching fullscreen applications freezes taskbar Product: plasmashell Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sunshinehunte...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Hello! Whenever I open fullscreen applications like games, the taskbar will freeze when switching windows and display the state it had on the first time it freezed. Steps to reproduce: 1. Open a fullscreen application. (In my case these were games from Steam, like Rocket League or DOTA 2) 2. Switch windows by pressing ALT-TAB Actual Results: 1. The taskbar freezes (no animations, elements are static like in an image) 2. The taskbar displays a state of itself, when it freezed the first time (example: Before executing a fullscreen application, the bar looks like this: [ ... [ Vivaldi - New Tab ] [ Steam ] ... 12:00 ] After starting it and switching to [Steam], it still looks like before with no visual changes. Elements are still movable, and the preview by hovering is appearing. Now after closing the application, the bar looks like this: [ ... [ Steam ] [ google.com ] [ #general - Discord ] ... 12:10 ] After opening another fullscreen application (at 12:10) and switching windows, it will return to the first state: [ ... [ Vivaldi - New Tab ] [ Steam ] ... 12:00 ] ) Expected results: The taskbar should still display the current state (open windows, time, animations, tray icons) when a fullscreen application is opened and windows are switched. Build date & Platform: I'm running Arch Linux with kernel version 4.8.13-1-ARCH with KDE 5.8.4-1. CPU is Intel Xeon E3-1230v5 and graphics card is a NVIDIA GTX 760 with the proprietary drivers (package version 375.26-1). I experience that problem since installing KDE about 2-3 weeks ago on a fresh install. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 373796] Partition Manager uses different config when not launched from terminal emulator
https://bugs.kde.org/show_bug.cgi?id=373796 Andrius Štikonas changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- I am not sure if different theme is related to that... sudo does not pass environmental variables, so if you use sudo that is the most common reason for different theme. But maybe you need to set your root user theme to breeze too... KDE Partition Manager 3.0 will help with sudo a bit, it will pass required environmental variables to kdesu in case it uses sudo as a backend. Most likely this is distro issue. I don't reproduce this behaviour on gentoo. It always uses /root/.config/partitionmanagerrc Maybe try to talk to Arch people, also wait and see how 3.0 will change things (should be released tomorrow). If those two options don't work, please reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 373796] New: Partition Manager uses different config when not launched from terminal emulator
https://bugs.kde.org/show_bug.cgi?id=373796 Bug ID: 373796 Summary: Partition Manager uses different config when not launched from terminal emulator Product: partitionmanager Version: 2.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ras...@gmail.com Target Milestone: --- I don't know if this is a bug in Partition Manager itself, but it is the only app that does this AFAIK. When started from a terminal, it uses ~/.config/partitionmanagerrc. When started from a .desktop file (app menu, krunner, etc.), it uses /root/.config/partitionmanagerrc. It also doesn't use my KDE theme when started this way, which I'd assume is related. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373088] Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 --- Comment #8 from Francis Herne --- Tangentially, I looked through the colours in Breeze-dark, and can't find any one that matches the inactive tab colour. It's not clear where this is colour derived from, or how to modify it. (also, I messed up my previous comment slightly; part of one entry is duplicated. It's 2am here, time to sleep...) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373088] Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 --- Comment #7 from Janek Bevendorff --- I agree that Breeze is the nicest theme of all those. But the inverted colors are clearly confusing and counter-intuitive. I'm not quite sure where the error lies, though. This weird tab coloring also appears with other dark color schemes, such as various Krita color schemes. So it could either be that they are all just based on each other and inherit the same bug or that it is really an issue with the Breeze widget style. The fact that changing the widget style leads to correct tab coloring lets strongly assume it is. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 373677] Command line '--title' option is no longer actioned
https://bugs.kde.org/show_bug.cgi?id=373677 sssiii...@protonmail.com changed: What|Removed |Added CC||sssiii...@protonmail.com --- Comment #1 from sssiii...@protonmail.com --- Same problem here. Additionally, when running kdialog in a system with dual monitors, QCommandLineParser complains about missing "geometry" parameter. More details: https://www.reddit.com/r/kde/comments/5ix96k/kdialog_broken/ -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373088] Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 --- Comment #6 from Francis Herne --- Created attachment 102846 --> https://bugs.kde.org/attachment.cgi?id=102846&action=edit Comparison of tabs in different widget styles -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373088] Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 --- Comment #5 from Francis Herne --- I think your statement is incorrect - no other widget style installed on my system displays tabs with reversed colours, using Breeze-dark or other dark schemes. In the attachment, all using Breeze-dark, top to bottom: - QtCurve (default settings): active tab is lighter, taller and has red close icon. - Oxygen: active tab is lighter, taller all using Breeze-dark, top to bottom: - QtCurve (default settings): active tab is lighter, taller and has red close icon. - Win9x (bleh): active tab has same colour, taller, has red close icon. - Fusion: active tab is lighter and taller. All close buttons identical (red). - Breeze: active tab is much darker, same height. All close buttons identical (grey). To be honest, I find Breeze's tabs clearer than the other variants with this colour scheme - ignoring distinct close-icon colours which make a huge difference - but the inverse-colour behaviour is clearly influenced by Breeze QtStyle and is reversed from all other styles. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373795] New: plasmashell crashed and restarted when quitting firefox
https://bugs.kde.org/show_bug.cgi?id=373795 Bug ID: 373795 Summary: plasmashell crashed and restarted when quitting firefox Product: plasmashell Version: 5.8.4 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: arthur.ma...@internode.on.net CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.8.0-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: After a video playback program, mpv was terminated due to lock-up, chromium froze. When I quit firefox, chromium unfroze but plasmashell terminated and restarted. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5dcb183e80 (LWP 4310))] Thread 9 (Thread 0x7f5d22c15700 (LWP 4615)): #0 0x7f5dd83b156d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5dd3d429f6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f5d14002e70, timeout=, context=0x7f5d14000990) at ././glib/gmain.c:4228 #2 0x7f5dd3d429f6 in g_main_context_iterate (context=context@entry=0x7f5d14000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7f5dd3d42b0c in g_main_context_iteration (context=0x7f5d14000990, may_block=1) at ././glib/gmain.c:3990 #4 0x7f5dd8cc4f5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5dd8c6e8da in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5dd8a9c0f3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5dd8aa0da8 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5dd7bb4464 in start_thread (arg=0x7f5d22c15700) at pthread_create.c:333 #9 0x7f5dd83ba9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7f5d23416700 (LWP 4614)): #0 0x7f5dd83b156d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5dd3d429f6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f5d1c0013c0, timeout=, context=0x7f5d1c000990) at ././glib/gmain.c:4228 #2 0x7f5dd3d429f6 in g_main_context_iterate (context=context@entry=0x7f5d1c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7f5dd3d42b0c in g_main_context_iteration (context=0x7f5d1c000990, may_block=1) at ././glib/gmain.c:3990 #4 0x7f5dd8cc4f5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5dd8c6e8da in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5dd8a9c0f3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5d23866a35 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #8 0x7f5dd8aa0da8 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5dd7bb4464 in start_thread (arg=0x7f5d23416700) at pthread_create.c:333 #10 0x7f5dd83ba9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7f5d2c301700 (LWP 4570)): #0 0x7f5dd7bba18f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5db87ea2bb in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f5db87ea117 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f5dd7bb4464 in start_thread (arg=0x7f5d2c301700) at pthread_create.c:333 #4 0x7f5dd83ba9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f5dba35d700 (LWP 4569)): #0 0x7f5dd7bba18f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5ddd5212c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f5ddd521309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f5dd7bb4464 in start_thread (arg=0x7f5dba35d700) at pthread_create.c:333 #4 0x7f5dd83ba9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f5dbbfff700 (LWP 4562)): #0 0x7f5dd3d88004 in g_mutex_unlock (mutex=0x7f5db990) at ././glib/gthread-posix.c:1348 #1 0x7f5dd3d41ed0 in g_main_context_prepare (context=context@entry=0x7f5db990, priority=priority@entry=0x7f5dbbffeca0) at ././glib/gmain.c:3499 #2 0x7f5dd3d4291b in g_main_context_iterate (context=context@entry=0x7f5db990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909 #3 0x7f5dd3d42b0c in
[systemsettings] [Bug 372153] Autostart wrong command string
https://bugs.kde.org/show_bug.cgi?id=372153 --- Comment #6 from k...@web.de --- Upon further inspection i think that my comment about arguments.takeFirst() is wrong, but the problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372153] Autostart wrong command string
https://bugs.kde.org/show_bug.cgi?id=372153 --- Comment #5 from k...@web.de --- This is not solved. When changing the command string by editing the settings, additional arguments are ignored. For example, adding this argument to start thunderbird with the addressbook open thunderbird -addressbook does start thunderbird, but does not open the addressbook. This might be related to the takeFirst() method, if it works as i'm thinking it does, it ignores any arguments but the first one. auto program = arguments.takeFirst(); -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372153] Autostart wrong command string
https://bugs.kde.org/show_bug.cgi?id=372153 k...@web.de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373778] icons shown are too small
https://bugs.kde.org/show_bug.cgi?id=373778 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Eike Hein --- Patch under review at https://phabricator.kde.org/D3719 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372153] Autostart wrong command string
https://bugs.kde.org/show_bug.cgi?id=372153 --- Comment #4 from k...@web.de --- You might want to look at https://bugs.kde.org/show_bug.cgi?id=357027 after this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357027] Unable to add autostart entries (via "Add program..." button)
https://bugs.kde.org/show_bug.cgi?id=357027 k...@web.de changed: What|Removed |Added CC||k...@web.de --- Comment #1 from k...@web.de --- This bug is still alive. When trying to add libreoffice writer, the properties dialog pops up, and clicking on OK gives the following error: "Could not save properties. You do not have sufficient access to write to /home/me/.config/autostart//libreoffice-writer.desktop" The folder /home/me/.config/autostart/ already exists, but the bug happens anyway. This seems to happen only when the .desktop file has an Exec line with an additional commandline flag, such as libreoffice --writer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373749] Left/right arrow keys switch to one direction in RTL
https://bugs.kde.org/show_bug.cgi?id=373749 Eike Hein changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #3 from Eike Hein --- Bug's in the TabBar component in the Plasma framework in KF5. Patch under review: https://phabricator.kde.org/D3718 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372153] Autostart wrong command string
https://bugs.kde.org/show_bug.cgi?id=372153 --- Comment #3 from k...@web.de --- The fix is working. However, the command is still shown as "firefox %u", which is not the command that is executed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373794] New: System setting crashes when trying to access Touchpad settings on Wayland
https://bugs.kde.org/show_bug.cgi?id=373794 Bug ID: 373794 Summary: System setting crashes when trying to access Touchpad settings on Wayland Product: systemsettings Version: 5.8.4 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: a...@haxalot.com Target Milestone: --- Application: systemsettings5 (5.8.4) Qt Version: 5.6.2 Frameworks Version: 5.28.0 Operating System: Linux 4.8.0-sabayon x86_64 Distribution: "Sabayon Linux amd64 16.12" -- Information about the crash: - What I was doing when the application crashed: Testing the wayland desktop, setting input layouts and configuring mouse. Any attempt to switch to the touchpad options instantly crashes. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #6 0x7f37bfbb62b6 in TouchpadConfig::TouchpadConfig(QWidget*, QList const&) () from /usr/lib64/qt5/plugins/kded_touchpad.so #7 0x7f37bfbb366b in QObject* KPluginFactory::createInstance(QWidget*, QObject*, QList const&) () from /usr/lib64/qt5/plugins/kded_touchpad.so #8 0x7f3803c9d95f in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /usr/lib64/libKF5CoreAddons.so.5 #9 0x7f38065287de in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () from /usr/lib64/libKF5KCMUtils.so.5 #10 0x7f380652fd4c in KCModuleProxyPrivate::loadModule() () from /usr/lib64/libKF5KCMUtils.so.5 #11 0x7f3806530905 in KCModuleProxy::realModule() const () from /usr/lib64/libKF5KCMUtils.so.5 #12 0x7f3806530e03 in KCModuleProxy::showEvent(QShowEvent*) () from /usr/lib64/libKF5KCMUtils.so.5 #13 0x7f3804ec75a8 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7f3804e8414c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f3804e88552 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f3803a1c098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7f3804ec440b in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f3804ec4310 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f3804ec43e2 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f3804ec7065 in QWidget::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #21 0x7f3804ec4378 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7f3804ec43e2 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #23 0x7f3804ec7065 in QWidget::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7f3804ea9a9d in QStackedLayout::setCurrentIndex(int) () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f3804ea9cd4 in QStackedLayout::setCurrentWidget(QWidget*) () from /usr/lib64/libQt5Widgets.so.5 #26 0x7f3805005a41 in QStackedWidget::setCurrentWidget(QWidget*) () from /usr/lib64/libQt5Widgets.so.5 #27 0x7f380547045e in KPageViewPrivate::_k_pageSelected(QItemSelection const&, QItemSelection const&) () from /usr/lib64/libKF5WidgetsAddons.so.5 #28 0x7f3803a41bba in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #29 0x7f38039dae77 in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib64/libQt5Core.so.5 #30 0x7f38039df3e3 in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib64/libQt5Core.so.5 #31 0x7f38039e1b39 in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /usr/lib64/libQt5Core.so.5 #32 0x7f38050deccd in QListView::setSelection(QRect const&, QFlags) () from /usr/lib64/libQt5Widgets.so.5 #33 0x7f38050c282b in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #34 0x7f3804ec7d09 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #35 0x7f3804fa7fbe in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #36 0x7f38050c6bcb in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #37 0x7f3803a1be3e in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #38 0x7f3804e84125 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #39 0x7f3804e88d87 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #40 0x7f3803a1c098 in QCoreApplication::notifyInternal2(QObject
[plasmashell] [Bug 373738] Panel is unable to receive focus after opening Youtube video on Firefox
https://bugs.kde.org/show_bug.cgi?id=373738 --- Comment #4 from frag...@gmail.com --- (In reply to Eike Hein from comment #3) > My guess is the plasmashell process takes 100% CPU and becomes unresponsive. Hi Eike. I was just testing this: 1) I move the mouse over the systray over all icons very fast (showing all the tooltips) 2) after a few seconds, plasmashell consumes 30% of the CPU, and the tooltip gets stuck 3) then plasmashell CPU consumption goes back to normal (but the tooltip keeps stuck) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364859] maximized windows appear behind the panels on the left edge after resolution change or screen lock
https://bugs.kde.org/show_bug.cgi?id=364859 Alan Ezust changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373793] New: Workspace behavior crash every time
https://bugs.kde.org/show_bug.cgi?id=373793 Bug ID: 373793 Summary: Workspace behavior crash every time Product: systemsettings Version: 5.8.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wagneralvar...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.14-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Just browsing in the workspcae behavior section - Unusual behavior I noticed: I did not notice anything unusual - Custom settings of the application: My most significant change was in the composer I changed from opengl 2.0 to opengl 3 The crash can be reproduced every time. -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f37a10d06c0 (LWP 8112))] Thread 7 (Thread 0x7f376ef7a700 (LWP 8356)): #0 0x7f37a5b42814 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f37a5afd10a in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f37ada7073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f37ada2173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f37ad87e5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f374ee342c7 in KCupsConnection::run() () at /lib64/libkcupslib.so #7 0x7f37ad8829da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f376e0cd700 (LWP 8163)): #0 0x7f37acc6a00d in poll () at /lib64/libc.so.6 #1 0x7f37a5afd156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f37ada7073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f37ada2173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f37ad87e5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f37ac4424e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f37ad8829da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f377fd46700 (LWP 8125)): #0 0x7f37acc65bdd in read () at /lib64/libc.so.6 #1 0x7f37a5b41450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afcc60 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f37a5afd0f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f37a5afd4e2 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #5 0x7f37964d7946 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #6 0x7f37a5b24b03 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f3780547700 (LWP 8124)): #0 0x7f37acc6a00d in poll () at /lib64/libc.so.6 #1 0x7f37a5afd156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f37a5afd2b1 in glib_worker_main () at /lib64/libglib-2.0.so.0 #4 0x7f37a5b24b03 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f378d9fb700 (LWP 8114)): #0 0x7f37ad87ad93 in QMutex::unlock() () at /lib64/libQt5Core.so.5 #1 0x7f37ada70611 in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7f37a5afcba9 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f37a5afd0f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f37ada7073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f37ada2173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f37ad87e5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f37ae16d739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f37ad8829da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f37a9d466ca in start_thread () at /lib
[plasmashell] [Bug 373749] Left/right arrow keys switch to one direction in RTL
https://bugs.kde.org/show_bug.cgi?id=373749 --- Comment #2 from Eike Hein --- Can reproduce with ar_AR locale in Kickoff. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364859] maximized windows appear behind the panels on the left edge after resolution change or screen lock
https://bugs.kde.org/show_bug.cgi?id=364859 --- Comment #10 from Alan Ezust --- After a recent upgrade, I am no longer able to reproduce this like I was able to before. This might be fixed. I will mark it as such if I don't see it again in the next week. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373749] Left/right arrow keys switch to one direction in RTL
https://bugs.kde.org/show_bug.cgi?id=373749 Eike Hein changed: What|Removed |Added CC||h...@kde.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Eike Hein --- Based on "pages" I reassigned this from Kicker to Kickoff. Can you confirm you meant Kickoff? Which locale are you using? I can't reproduce this currently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in
https://bugs.kde.org/show_bug.cgi?id=346181 Przemek Tomczyk changed: What|Removed |Added CC||tomczyk.prze...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364859] maximized windows appear behind the panels on the left edge after resolution change or screen lock
https://bugs.kde.org/show_bug.cgi?id=364859 Przemek Tomczyk changed: What|Removed |Added CC||tomczyk.prze...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372586] Plasma panel covers windows when a second monitor is added
https://bugs.kde.org/show_bug.cgi?id=372586 Przemek Tomczyk changed: What|Removed |Added CC||tomczyk.prze...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373761] Task Manager crashes leading to no plasma at all
https://bugs.kde.org/show_bug.cgi?id=373761 Eike Hein changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Eike Hein --- Could you ask in #kubuntu for the debug symbol package names? A reliably reproducable crash is great but we really need the backtrace to progress. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 233991] color remap xterm ANSI sequences not supported
https://bugs.kde.org/show_bug.cgi?id=233991 Brad Hubbard changed: What|Removed |Added CC||bhubb...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373738] Panel is unable to receive focus after opening Youtube video on Firefox
https://bugs.kde.org/show_bug.cgi?id=373738 Eike Hein changed: What|Removed |Added Assignee|h...@kde.org|k...@davidedmundson.co.uk Summary|Task bar is unable to |Panel is unable to receive |receive focus after opening |focus after opening Youtube |Youtube video on Firefox|video on Firefox CC||bhus...@gmail.com Component|Task Manager|general -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 344181] konsole 256 color support differs from xterm/rxvt
https://bugs.kde.org/show_bug.cgi?id=344181 Brad Hubbard changed: What|Removed |Added CC||bhubb...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373738] Panel is unable to receive focus after opening Youtube video on Firefox
https://bugs.kde.org/show_bug.cgi?id=373738 Eike Hein changed: What|Removed |Added CC||h...@kde.org --- Comment #3 from Eike Hein --- My guess is the plasmashell process takes 100% CPU and becomes unresponsive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373749] Left/right arrow keys switch to one direction in RTL
https://bugs.kde.org/show_bug.cgi?id=373749 Eike Hein changed: What|Removed |Added Component|Application Menu (Kicker) |Application Launcher ||(Kickoff) Assignee|h...@kde.org|k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 151540] usability: video view is missing some play/stop/pause buttons
https://bugs.kde.org/show_bug.cgi?id=151540 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/dd6239a58fe31d526e37c8 ||f89f625b787303f0de Version Fixed In||5.4.0 Resolution|INVALID |FIXED --- Comment #7 from Maik Qualmann --- Git commit dd6239a58fe31d526e37c8f89f625b787303f0de by Maik Qualmann. Committed on 17/12/2016 at 22:07. Pushed by mqualmann into branch 'master'. polish mediaplayer and add pause/play button to the toolbar FIXED-IN: 5.4.0 M +2-1NEWS M +49 -42 app/views/mediaplayerview.cpp M +4-6app/views/mediaplayerview.h https://commits.kde.org/digikam/dd6239a58fe31d526e37c8f89f625b787303f0de -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373395] Crash on exit after playing track silently
https://bugs.kde.org/show_bug.cgi?id=373395 --- Comment #2 from robert marshall --- It seems to only happen when I get the audio playback in that broken state. I've done a rescan and am trying to get it to happen again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373792] New: kmail fecha sozinho e informa erro
https://bugs.kde.org/show_bug.cgi?id=373792 Bug ID: 373792 Summary: kmail fecha sozinho e informa erro Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: celo.flor...@gmail.com Target Milestone: --- Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.2 Frameworks Version: 5.27.0 Operating System: Linux 4.8.12-200.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: aguardando kmail mostrar mensagem. chamei o kmail, ele iniciou normal, mostrou lista de emails na tela, cliquei em um item da lista, segundos depois fechou sozinho informando erro. tem sido sempre assim faz 2 meses depois da instalar o kde neste pc. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f46ad99f940 (LWP 6603))] Thread 34 (Thread 0x7f4609265700 (LWP 6675)): #0 0x7f46d21d756d in poll () at /lib64/libc.so.6 #1 0x7f46c1f20a06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f46c1f20b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f46d2fdd75b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f46d2f8c81a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f46d2deb353 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f46d2def9ba in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f46c339e5ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f46d21e30ed in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f4609a66700 (LWP 6671)): #0 0x7f46c33a3bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f46ca224959 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f46ca225020 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f46ca2251f0 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f46ca221c2d in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f46c339e5ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f46d21e30ed in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f460b7fe700 (LWP 6663)): #0 0x7f46c33a3bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f46b6ddd1a4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f46b6ddd1e9 in () at /lib64/libQt5Script.so.5 #3 0x7f46c339e5ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f46d21e30ed in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f460bfff700 (LWP 6660)): #0 0x7f46d21d756d in poll () at /lib64/libc.so.6 #1 0x7f46c1f20a06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f46c1f20b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f46d2fdd75b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f46d2f8c81a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f46d2deb353 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f46d2def9ba in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f46c339e5ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f46d21e30ed in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f46167b0700 (LWP 6652)): #0 0x7f46c1f64a24 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f46c1f1f9ae in g_main_context_acquire () at /lib64/libglib-2.0.so.0 #2 0x7f46c1f208b5 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f46c1f20b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f46d2fdd75b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f46d2f8c81a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f46d2deb353 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f46d2def9ba in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f46c339e5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f46d21e30ed in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f46171c3700 (LWP 6644)): #0 0x7f46d21d7571 in poll () at /lib64/libc.so.6 #1 0x7f46c1f20a06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f46c1f20b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f46d2fdd75b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f46d2f8c81a
[marble] [Bug 360871] JSON file filter doesn't work
https://bugs.kde.org/show_bug.cgi?id=360871 Friedrich W. H. Kossebau changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||kosse...@kde.org Resolution|--- |FIXED Version Fixed In||2.0 (Applications 16.08) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373791] New: Crash on exit
https://bugs.kde.org/show_bug.cgi?id=373791 Bug ID: 373791 Summary: Crash on exit Product: kdenlive Version: 16.08.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kacerna...@quick.cz Target Milestone: --- Created attachment 102845 --> https://bugs.kde.org/attachment.cgi?id=102845&action=edit backtrace report Crashed on closing the kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361516] Panel on top/left cause a black window in cube animation
https://bugs.kde.org/show_bug.cgi?id=361516 --- Comment #7 from Łukasz --- Mint 18, Plasma updated to version 5.8.4 and bug still exists. But most noticed bugs from Plasma 5.6.4 disappeared :-) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 365834] Android version claims to open APK files
https://bugs.kde.org/show_bug.cgi?id=365834 Friedrich W. H. Kossebau changed: What|Removed |Added Component|general |android -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 365834] Android version claims to open APK files
https://bugs.kde.org/show_bug.cgi?id=365834 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. This should have been fixed in more recent versions of the Marble Maps apk. Please try the latest from https://play.google.com/store/apps/details?id=org.kde.marble.maps or from http://files.kde.org/marble/downloads/android/ If still noticed, please reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373790] New: Crash on opening a diff from Git History dialog
https://bugs.kde.org/show_bug.cgi?id=373790 Bug ID: 373790 Summary: Crash on opening a diff from Git History dialog Product: kdevelop Version: 5.0.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: kosse...@kde.org Target Milestone: --- Application: kdevelop (5.0.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.14-1.gab53e9a-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: 1. opened a git-based project 2. RMB on a file (or opened document) 3. Select Git -> History... 4. Select a revision in the dialog 5. RMB on line 6. Select Diff to previous revision The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f09b1ad6dc0 (LWP 641))] Thread 14 (Thread 0x7f0920f8a700 (LWP 19773)): #0 0x7f09a127510f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f09a2827834 in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7f09a2b10ec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f09a2827879 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f09a126f454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f09a9f0039f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f0923fff700 (LWP 892)): #0 0x7f09a9ef768d in poll () at /lib64/libc.so.6 #1 0x7f099ec37876 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f099ec3798c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f09aad3179b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f094c004980, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f09aacdb1ea in QEventLoop::exec(QFlags) (this=this@entry=0x7f0923ffecc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f09aab098b3 in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f09aab0e558 in QThreadPrivate::start(void*) (arg=0x7f09b061fba8 ) at thread/qthread_unix.cpp:344 #7 0x7f09a126f454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f09a9f0039f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f0943fff700 (LWP 856)): #0 0x7f09a127510f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f09aab0f40b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0xfa2d20) at thread/qwaitcondition_unix.cpp:143 #2 0x7f09aab0f40b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x105b620, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f09a721de60 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f09a7222018 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f09a721cfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f09a7222072 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f09a721cfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f09a7222072 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f09a721cfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f09a721fea9 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f09aab0e558 in QThreadPrivate::start(void*) (arg=0x7f0928016e90) at thread/qthread_unix.cpp:344 #12 0x7f09a126f454 in start_thread () at /lib64/libpthread.so.0 #13 0x7f09a9f0039f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f0940c37700 (LWP 855)): #0 0x7f09a127510f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f09aab0f40b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0xfa2d20) at thread/qwaitcondition_unix.cpp:143 #2 0x7f09aab0f40b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x105b620, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f09a721de60 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f09a7222018 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f09a721cfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f09a7222072 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f09a
[choqok] [Bug 372056] Choqok does not remember window position
https://bugs.kde.org/show_bug.cgi?id=372056 --- Comment #3 from André Fettouhi --- I just updated today to 16.12 and the issue with choqok seems to be gone now. It respects the position now it seems. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 372056] Choqok does not remember window position
https://bugs.kde.org/show_bug.cgi?id=372056 --- Comment #2 from Wulf --- If you choose to enforce the window settings choqok respects the horizontal value, but not the vertical - weird change of ~/.config/choqokrc did not help -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #18 from Michael K. --- Unsetting the above env variables (QT_...) restores old (kdelibs4-based) behavior/rendering. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 372056] Choqok does not remember window position
https://bugs.kde.org/show_bug.cgi?id=372056 Wulf changed: What|Removed |Added CC||wulf.richa...@gmx.de --- Comment #1 from Wulf --- I have this problem now too. After Update to Framework 5.29 and KDE 16.12 with Choqok 1.6 Choqok ignores special application/window settings. My special application windows settings: - Apply initially - Position: 1250,70 - Size: 375,950 Monitor resolution: 1680x1050 It's only choqok, I tested also kcalc and okular, they have no problems to respect the special windows settings I did not have this problem before the update > But when you minimize to tray and then reopen it, then it has moved again. In > my case it shifts down a few centimeter everytime from the original position > I've set. I can't confirm this. I tested with a brand new user: Same issue -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 349114] Marble silently fails to import valid kml. Does not signal error
https://bugs.kde.org/show_bug.cgi?id=349114 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Friedrich W. H. Kossebau --- Still fails with latest Marble from master, v2.1.20 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373359] KMail hangs when scrolling HTML messages
https://bugs.kde.org/show_bug.cgi?id=373359 --- Comment #4 from Larry --- Created attachment 102844 --> https://bugs.kde.org/attachment.cgi?id=102844&action=edit Output from launching kontact and reading 2 E-Mail messages. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373359] KMail hangs when scrolling HTML messages
https://bugs.kde.org/show_bug.cgi?id=373359 --- Comment #3 from Larry --- Tried again sicne filing this report with the same results. I launched kontact from konsole and am attaching the output. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373789] konqueror crashes while displaying a local svg image
https://bugs.kde.org/show_bug.cgi?id=373789 --- Comment #1 from Toralf Förster --- Created attachment 102843 --> https://bugs.kde.org/attachment.cgi?id=102843&action=edit graph.svg -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373789] New: konqueror crashes while displaying a local svg image
https://bugs.kde.org/show_bug.cgi?id=373789 Bug ID: 373789 Summary: konqueror crashes while displaying a local svg image Product: konqueror Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: toralf.foers...@gmx.de Target Milestone: --- Application: konqueror (5.0.97) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-hardened x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: I run this command : h=mr-fox ; svg=/tmp/graph.svg; rsync --archive $h:/var/log/sa ~/tmp/sa/$h && sadf -g -T ~/tmp/sa/$h/sa/sa`date +%d` -O skipempty,oneday -- -u -q -n ALL > $svg && konqueror $svg The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x361a83347c0 (LWP 28150))] Thread 18 (Thread 0x36194acc700 (LWP 28151)): #0 0x0361a7d2f93d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x03619eb1faaa in poll (__timeout=-1, __nfds=1, __fds=0x36194acbcd0) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x30c443a080, cond=cond@entry=0x30c443a0c0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_conn.c:479 #3 0x03619eb2212f in xcb_wait_for_event (c=0x30c443a080) at /var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_in.c:693 #4 0x036196b019e9 in QXcbEventReader::run (this=0x30c750) at qxcbconnection.cpp:1343 #5 0x0361a2fd4d42 in QThreadPrivate::start (arg=0x30c750) at thread/qthread_unix.cpp:368 #6 0x03619f1b560c in start_thread (arg=0x36194acc700) at pthread_create.c:334 #7 0x0361a7d3989d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x3618ef4d700 (LWP 28152)): #0 0x03619d28feec in g_mutex_lock (mutex=mutex@entry=0x36188000990) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gthread-posix.c:1335 #1 0x03619d23adcb in g_main_context_prepare (context=context@entry=0x36188000990, priority=priority@entry=0x3618ef4cc30) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3444 #2 0x03619d23b806 in g_main_context_iterate (context=context@entry=0x36188000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3820 #3 0x03619d23ba51 in g_main_context_iteration (context=0x36188000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901 #4 0x0361a320fd04 in QEventDispatcherGlib::processEvents (this=0x361880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x0361a31b497a in QEventLoop::exec (this=this@entry=0x3618ef4cda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x0361a2fcf6bd in QThread::exec (this=this@entry=0x361a84e6440 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x0361a846c645 in QDBusConnectionManager::run (this=0x361a84e6440 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x0361a2fd4d42 in QThreadPrivate::start (arg=0x361a84e6440 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x03619f1b560c in start_thread (arg=0x3618ef4d700) at pthread_create.c:334 #10 0x0361a7d3989d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x3617b0b2700 (LWP 28155)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x0361a7d48652 in ___fprintf_chk (fp=0x361a7fea8e0 <_IO_stdfile_2_lock>, flag=1, format=0x36181e82431 "[%s] %s\n") at fprintf_chk.c:30 #2 0x3c20 in ?? () #3 0x0031 in ?? () #4 0x in ?? () Thread 15 (Thread 0x3617a808700 (LWP 28156)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x0361840bb3e1 in base::WaitableEvent::TimedWait (this=this@entry=0x3616c0018c0, max_time=...) at /var/portage/dev-qt/qtwebengine-5.7.1/work/qtwebengine-opensource-src-5.7.1/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:216 #2 0x0361840bb4c9 in base::WaitableEvent::Wait (this=this@entry=0x3616c0018c0) at /var/portage/dev-qt/qtwebengine-5.7.1/work/qtwebengine-opensource-src-5.7.1/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:156 #3 0x03618409a092 in base::MessagePumpDefault::Run (this=0x3616c0018b0, delegate=0x30c48ecf20) at /var/portage/dev-qt/qtwebengine-5.7.1/work/qtwebengine-opensource-src-5.7.1/src/3rdpa
[marble] [Bug 275819] world clock plasmoid crash
https://bugs.kde.org/show_bug.cgi?id=275819 Friedrich W. H. Kossebau changed: What|Removed |Added Component|data|plasmoid CC||kosse...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #7 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still, especially timezones). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 373788] New: Calligra Plan Crash Without Pattern
https://bugs.kde.org/show_bug.cgi?id=373788 Bug ID: 373788 Summary: Calligra Plan Crash Without Pattern Product: calligraplan Version: 2.9.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dand...@get2net.dk Reporter: hamidrjaf...@gmail.com Target Milestone: --- Application: calligraplan (2.9.11) KDE Platform Version: 4.14.22 Qt Version: 4.8.7 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: Hello, Clicking on a Plan file opens the document but more than often it crashes. This is related to another bug I reported the same day only using the web (Bug 373769). The crash can be reproduced sometimes. -- Backtrace: Application: Plan (calligraplan), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fec053affc0 (LWP 7187))] Thread 2 (Thread 0x7febe3951700 (LWP 7190)): #0 0x7febffc8f090 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7febffc8f8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7febffc8faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fec034ac22e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7fec0347a12f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7fec0347a495 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fec03369549 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fec0345a1c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fec0336be3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fec001796ca in start_thread (arg=0x7febe3951700) at pthread_create.c:333 #10 0x7fec04dbd0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fec053affc0 (LWP 7187)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #7 0x7fec04cec3ea in __GI_abort () at abort.c:89 #8 0x7fec04d2e0d0 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fec04e43368 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fec04d3775a in malloc_printerr (ar_ptr=, ptr=, str=0x7fec04e3fefb "free(): invalid pointer", action=3) at malloc.c:5046 #10 _int_free (av=, p=, have_lock=) at malloc.c:3902 #11 0x7fec04d3b18c in __GI___libc_free (mem=) at malloc.c:2982 #12 0x7fec0348d99a in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7fec0348da09 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 0x7fec0347f370 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x7fec034ac09e in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x7febffc8f7d7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7febffc8fa40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7febffc8faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fec034ac20e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #20 0x7fec03f3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #21 0x7fec0347a12f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7fec0347a495 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #23 0x7fec03480459 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #24 0x7fec0507d9c5 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_calligraplan.so #25 0x7fec04cd53f1 in __libc_start_main (main=0x5584a8edf770, argc=2, argv=0x7fff07472c28, init=, fini=, rtld_fini=, stack_end=0x7fff07472c18) at ../csu/libc-start.c:291 #26 0x5584a8edf7aa in _start () Possible duplicates by query: bug 348699, bug 347139, bug 347134, bug 347050, bug 346742. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 373787] drkonqi doesn't remember KDEs bugzilla credentials
https://bugs.kde.org/show_bug.cgi?id=373787 Toralf Förster changed: What|Removed |Added Summary|kdebugdialog doesn't|drkonqi doesn't remember |remember KDEs bugzilla |KDEs bugzilla credentials |credentials | -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 373787] kdebugdialog doesn't remember KDEs bugzilla credentials
https://bugs.kde.org/show_bug.cgi?id=373787 Toralf Förster changed: What|Removed |Added Product|kdebugdialog|drkonqi Version|unspecified |5.8.4 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 373787] kdebugdialog doesn't remember KDEs bugzilla credentials
https://bugs.kde.org/show_bug.cgi?id=373787 Toralf Förster changed: What|Removed |Added Platform|Other |Homebrew (Mac OS X) -- You are receiving this mail because: You are watching all bug changes.
[kdebugdialog] [Bug 373787] New: kdebugdialog doesn't remember KDEs bugzilla credentials
https://bugs.kde.org/show_bug.cgi?id=373787 Bug ID: 373787 Summary: kdebugdialog doesn't remember KDEs bugzilla credentials Product: kdebugdialog Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: toralf.foers...@gmx.de Target Milestone: --- I click every time "stoe in kwallet" but have to type in username and password for every new bug report qt 5.7.1 KDE 5.29 + 5.8.4 + 16.12.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 Michael K. changed: What|Removed |Added CC||kolober...@gmail.com --- Comment #17 from Michael K. --- Same problem here. - 5K monitor - QT_SCREEN_SCALE_FACTORS=2 - QT_AUTO_SCREEN_SCALE_FACTOR=0 - xdpyinfo | grep resolution resolution:215x215 dots per inch I have just upgraded to the new release of KF5/plasma which includes KF5-based okular. Documents look as if they were rendered at lower resolution and then upscaled. The irony is that the kdelibs4-based okular rendered documents properly -- at native resolution -- as it was not aware of scaling. (the UI elements were half-sized though, which was a bit annoying) This seems to affect every backend. (I've tried PDF, ePub and Mobi) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 202630] marble wallpaper plugin not repainting after changing view
https://bugs.kde.org/show_bug.cgi?id=202630 Friedrich W. H. Kossebau changed: What|Removed |Added Component|plasmoid|wallpaper Resolution|--- |UNMAINTAINED CC||kosse...@kde.org Status|CONFIRMED |RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 202353] Earth as desktop background causes noticeable, constant CPU load
https://bugs.kde.org/show_bug.cgi?id=202353 Friedrich W. H. Kossebau changed: What|Removed |Added Component|plasmoid|wallpaper -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 202353] Earth as desktop background causes noticeable, constant CPU load
https://bugs.kde.org/show_bug.cgi?id=202353 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||kosse...@kde.org Resolution|--- |UNMAINTAINED --- Comment #9 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved and the patch been used? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 269754] desktop background
https://bugs.kde.org/show_bug.cgi?id=269754 Friedrich W. H. Kossebau changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||kosse...@kde.org Resolution|--- |UNMAINTAINED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 346160] Plasma se detuvo tras añadir el fondo de pantalla Globo la primera vez
https://bugs.kde.org/show_bug.cgi?id=346160 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 329137] Crash!
https://bugs.kde.org/show_bug.cgi?id=329137 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 275430] Crash Selecting Globe Wallpaper
https://bugs.kde.org/show_bug.cgi?id=275430 Friedrich W. H. Kossebau changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||kosse...@kde.org Resolution|--- |UNMAINTAINED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 245155] plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=245155 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #3 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 287233] Plasma Earth Dynamic Wallpaper crashes
https://bugs.kde.org/show_bug.cgi?id=287233 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373709] Clock shows wrong time for Turkey
https://bugs.kde.org/show_bug.cgi?id=373709 bil changed: What|Removed |Added CC||bel...@list.ru --- Comment #1 from bil --- KDE Plasma 5.8.4 KDE Frameworks 5.28.0 Qt 5.6.1 Confirm wrong time. It's like https://bugs.kde.org/show_bug.cgi?id=370149 and fixes in QT https://bugreports.qt.io/browse/QTBUG-53071 for 5.6.2, 5.7.1 versions. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 248843] plasma freeze (100% cpu) when starting desktop settings (only with marble as wallpaper)
https://bugs.kde.org/show_bug.cgi?id=248843 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365256] Krunner dictionary is buggy
https://bugs.kde.org/show_bug.cgi?id=365256 Hamid changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Hamid --- Upgraded to 16.10 and it seems it takes time to fetch info from the net hence illusion of no response if late. Anyway it is not possible for me to reproduce the bug with the new environment and has not been bugged by others, so I will close it. But where is the close fix? -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 274109] Plasma crashes when selecting Globe wallpaper. [null Marble::GeoSceneDocument::map, Marble::MarbleMapPrivate::paintGround, Marble::MarbleMap::paint]
https://bugs.kde.org/show_bug.cgi?id=274109 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #8 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 327344] Plasma crashed when trying to choose globe wallpaper
https://bugs.kde.org/show_bug.cgi?id=327344 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #4 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldmap wallpaper has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new wallpaper and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 201486] worldtime doesn't work in plasmoid
https://bugs.kde.org/show_bug.cgi?id=201486 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||kosse...@kde.org Resolution|--- |UNMAINTAINED --- Comment #6 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still, especially timezones). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 289095] Adding Widget to desktop
https://bugs.kde.org/show_bug.cgi?id=289095 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still, especially timezones). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373785] kwin crash in apper
https://bugs.kde.org/show_bug.cgi?id=373785 --- Comment #1 from Larry --- I don't know if it's relevant but I did enable DRI3 in response to https://bugzilla.redhat.com/show_bug.cgi?id=1399396. Before enabling DRI3, loading apper and selecting a category (any category) would cause the bug above fairly consistently. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 257366] Add Widgets -> World Clock shortly after login crushes KDE
https://bugs.kde.org/show_bug.cgi?id=257366 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still, especially timezones). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 195015] worldclock plasmoid shows yellow dot outside of the map
https://bugs.kde.org/show_bug.cgi?id=195015 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #6 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still, especially timezones). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 373779] QFileDialog integration causes crashes on program exit
https://bugs.kde.org/show_bug.cgi?id=373779 --- Comment #2 from David Korth --- I'm using Qt 5.7.1. I don't remember if this problem happened with 5.7.0. (On Windows, I'm using Qt 5.5.1, and it doesn't crash when using native dialogs.) I'll go through the 5.7.1 changelog again and see if there's anything relevant. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 268427] Plasma-desktop Crash when configuring widget
https://bugs.kde.org/show_bug.cgi?id=268427 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||kosse...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still, especially timezones). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373786] New: Secondary display's panel is misplaced after disconnecting it - assignig panels and widgets to display devices?
https://bugs.kde.org/show_bug.cgi?id=373786 Bug ID: 373786 Summary: Secondary display's panel is misplaced after disconnecting it - assignig panels and widgets to display devices? Product: plasmashell Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use a laptop with an external monitor. When I disconnect the external monitor, the panel that I placed there jumps back onto my primary display - covering the panel that's already there. To access my primary display's panel, I have to move the secondary display's panel away - I usually put it on top of the screen. They both have task managers (showing only their current screen's task). I would like to have the panel for the secondary monitor remain hidden and show itself up only when I connect the secondary monitor - and to hide itself again when I disconnect it, instead of cramming itself on my other monitor. Right now when I connect the secondary monitor again I have to manually move the secondary panel there. --- A slightly dodgy feature requestish part (Sorry if this is not a good place for such ideas. Please let me know where shold I got to discuss such matters if so): Would it be possible to make sure that some panels and widgets are assigned to a particular physical display, and will only be presented when that particular device is connected? For example I might not want the stuff I put on a secondary monitor to show up on a projector if I connect it. Accessing, reviewing and modifying panels and widgets assigned to particular display devices could be helpful - for example if I configured a panel for a particular monitor, but I'd want to copy it to another monitor (but I don't have access to the previous device that was assigned to that panel). Maybe a matrix of panels and widgets with a checklist of currently and previously connected display devices and/or categories (monitors, TVs, projectors etc) would be good? The user could easily assign what should be displayed where. -- You are receiving this mail because: You are watching all bug changes.
