[konsole] [Bug 356966] crash in QXcbWindow::setParent() due to NULL xcbScreen()
https://bugs.kde.org/show_bug.cgi?id=356966 Jon Burgess changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Jon Burgess --- Yes, 3 years is a long time ago. I think QT finally fixed all the NULL screen pointer issues I was seeing with X11. The only bad thing is that there seem to be similar problems handling screens disappearing in Wayland which has made me stick with X11 for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384654] found kded module "touchpad" by prepending 'kded_' to the library path, please fix your metadata
https://bugs.kde.org/show_bug.cgi?id=384654 Jon Burgess changed: What|Removed |Added CC||jburgess...@googlemail.com --- Comment #2 from Jon Burgess --- it looks like this was fixed here: https://cgit.kde.org/plasma-desktop.git/commit/?id=b10fe56678cf20688c90f15ca76c6917d830c7b5 -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 397633] kf5.kded: found kded module "colord" by prepending 'kded_' to the library path
https://bugs.kde.org/show_bug.cgi?id=397633 --- Comment #2 from Jon Burgess --- (In reply to Christoph Feck from comment #1) > So does changing the desktop file in this way fix the issue? Yes. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 397633] New: kf5.kded: found kded module "colord" by prepending 'kded_' to the library path
https://bugs.kde.org/show_bug.cgi?id=397633 Bug ID: 397633 Summary: kf5.kded: found kded module "colord" by prepending 'kded_' to the library path Product: colord-kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Daemon Module (KDED) Assignee: dantt...@gmail.com Reporter: jburgess...@googlemail.com Target Milestone: --- When I login and look at the system log messages I see the message above $ journalctl --since today | grep colord Aug 19 14:47:51 localhost.localdomain kdeinit5[837034]: kf5.kded: found kded module "colord" by prepending 'kded_' to the library path, please fix your metadata. I'm guessing that it wants this change in the desktop file: diff --git a/colord-kded/colord.desktop b/colord-kded/colord.desktop index c1086be..c07d82f 100644 --- a/colord-kded/colord.desktop +++ b/colord-kded/colord.desktop @@ -2,7 +2,7 @@ Type=Service X-KDE-ServiceTypes=KDEDModule -X-KDE-Library=colord +X-KDE-Library=kded_colord X-KDE-DBus-ModuleName=colord X-KDE-Kded-autoload=true X-KDE-Kded-phase=1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 Jon Burgess <jburgess...@googlemail.com> changed: What|Removed |Added CC||jburgess...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrastage] [Bug 356971] New: default print-to-pdf filename doesn't work for unsaved documents
https://bugs.kde.org/show_bug.cgi?id=356971 Bug ID: 356971 Summary: default print-to-pdf filename doesn't work for unsaved documents Product: calligrastage Version: 2.9.10 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: usability Assignee: t.zachm...@zagge.de Reporter: jburgess...@googlemail.com Printing to PDF using the default filename for an unsaved document fails saying the file is not writable. Reproducible: Always Steps to Reproduce: 1. Open stage 2. Pick a template 3. File -> Print -> "Print to PDF" -> Print Actual Results: Default filename looks like: Stage unsaved document (20/12/2015).pdf "File /home/jburgess/Stage unsaved document (20/12/2015).pdf is not writable. Please choose a different file name." Expected Results: default filename should work The problem is likely due to the "/" characters in the date which Linux interprets as being a subdirectory. Switching to an ISO8601 data like 2015-12-15 should resolve it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 --- Comment #5 from Jon Burgess <jburgess...@googlemail.com> --- (In reply to Stefan Becker from comment #4) > Just updated to latest Fedora 23 "updates" repo contents. Problem is still > there. You are right, the problem re-appeared as soon as I turned one of my monitors off/on. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 346969] Valgrind warning on the FStabBackend
https://bugs.kde.org/show_bug.cgi?id=346969 Jon Burgess <jburgess...@googlemail.com> changed: What|Removed |Added CC||jburgess...@googlemail.com --- Comment #1 from Jon Burgess <jburgess...@googlemail.com> --- This appears to be a glibc bug: https://sourceware.org/bugzilla/show_bug.cgi?id=18887 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356718] network connection editor crashes when editing VPN Openconnect connection.
https://bugs.kde.org/show_bug.cgi?id=356718 Jon Burgess <jburgess...@googlemail.com> changed: What|Removed |Added CC||jburgess...@googlemail.com --- Comment #1 from Jon Burgess <jburgess...@googlemail.com> --- Likely a duplicate of bug 356583. Opening a file dialogue in almost any KDE application on F23 seems to cause this crash. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356966] New: crash in setParent() dues to NULL xcbScreen()
https://bugs.kde.org/show_bug.cgi?id=356966 Bug ID: 356966 Summary: crash in setParent() dues to NULL xcbScreen() Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jburgess...@googlemail.com Application: kdeinit5 (15.12.0) Qt Version: 5.6.0 Operating System: Linux 4.4.0-0.rc5.git3.1.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: File->Save Output As This is reproduced using the Fedora rawhide packages: qt5-qtbase-5.6.0-0.16.fc24.x86_64 konsole5-15.12.0-1.fc24.x86_64 This looks like a side effect of the changes made for QTBUG-42985. Similar crashes have been seen when these were backported on top of QT 5.5 (bug 356583) but I wanted to verify they are also present in QT 5.6 beta. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94ac72e8c0 (LWP 2413))] Thread 7 (Thread 0x7f948ede7700 (LWP 2414)): #0 0x7f94a9dc290d in poll () from /lib64/libc.so.6 #1 0x7f94a82333dc in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f94a82334ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f94aac05acb in QEventDispatcherGlib::processEvents (this=0x7f94880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f94aabae50a in QEventLoop::exec (this=this@entry=0x7f948ede6cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f94aa9da744 in QThread::exec (this=this@entry=0x7f94ac859040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #6 0x7f94ac7e7225 in QDBusConnectionManager::run (this=0x7f94ac859040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:152 #7 0x7f94aa9df6b8 in QThreadPrivate::start (arg=0x7f94ac859040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #8 0x7f94a94086da in start_thread () from /lib64/libpthread.so.0 #9 0x7f94a9dce48d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f9487fff700 (LWP 2415)): #0 0x7f94a9dc290d in poll () from /lib64/libc.so.6 #1 0x7f94a8f99272 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f94a8f9aee7 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f948dc53f09 in QXcbEventReader::run (this=0x5595103aced0) at qxcbconnection.cpp:1288 #4 0x7f94aa9df6b8 in QThreadPrivate::start (arg=0x5595103aced0) at thread/qthread_unix.cpp:340 #5 0x7f94a94086da in start_thread () from /lib64/libpthread.so.0 #6 0x7f94a9dce48d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f947db45700 (LWP 2416)): #0 0x7f94a940e340 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9485e72fc3 in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x7f9485e72e27 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x7f94a94086da in start_thread () from /lib64/libpthread.so.0 #4 0x7f94a9dce48d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f947d344700 (LWP 2417)): #0 0x7f94a940e340 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9485e72fc3 in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x7f9485e72e27 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x7f94a94086da in start_thread () from /lib64/libpthread.so.0 #4 0x7f94a9dce48d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f947cb43700 (LWP 2418)): #0 0x7f94a940e340 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9485e72fc3 in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x7f9485e72e27 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x7f94a94086da in start_thread () from /lib64/libpthread.so.0 #4 0x7f94a9dce48d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f947c342700 (LWP 2419)): #0 0x7f94a940e340 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9485e72fc3 in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x7f9485e72e27 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x7f94a94086da in start_thread () from /lib64/libpthread.so.0 #4 0x7f94a9dce48d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f94ac72e8c0 (LWP 2413)): [KCrash Handler] #5 0x7f948dc6b408 in QXcbWindow::setParent (this=0x5595108d37c0, parent=0x0) at qxcbwindow.cpp:1426 #6 0x7f94aaf063d3 in QWindow::setParent (this=0x559510a4dad0, parent=parent@entry=0x559510906ff0) at
[konsole] [Bug 356966] crash in QXcbWindow::setParent() due to NULL xcbScreen()
https://bugs.kde.org/show_bug.cgi?id=356966 Jon Burgess <jburgess...@googlemail.com> changed: What|Removed |Added Component|general |general Platform|unspecified |Fedora RPMs Product|kde |konsole Summary|crash in setParent() dues |crash in |to NULL xcbScreen() |QXcbWindow::setParent() due ||to NULL xcbScreen() -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356966] crash in QXcbWindow::setParent() due to NULL xcbScreen()
https://bugs.kde.org/show_bug.cgi?id=356966 --- Comment #1 from Jon Burgess <jburgess...@googlemail.com> --- Reported to the QT bug tracker: https://bugreports.qt.io/browse/QTBUG-50081 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 --- Comment #3 from Jon Burgess <jburgess...@googlemail.com> --- I had the same issue yesterday but it seems to have gone away today after applying the latest Fedora package updates and rebooting. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 Jon Burgess <jburgess...@googlemail.com> changed: What|Removed |Added CC||jburgess...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
