[kopete] [Bug 369410] New: On startup kopete gives me a popup saying "the process for the file: protocol has been terminated unexpectedly"
https://bugs.kde.org/show_bug.cgi?id=369410 Bug ID: 369410 Summary: On startup kopete gives me a popup saying "the process for the file: protocol has been terminated unexpectedly" Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Whenever I start kopete (the version is 1.8.3, does not appear in the list here) I get a popup compaining about a kio_file process dying. After that kopete works normally. Running Plasma 5 here, Frameworks 5.7.5 from openSUSE build service repositories. A screenshot of the popup is attached. Reproducible: Always Steps to Reproduce: 1. start kopete Actual Results: see attached screenshot Expected Results: I'd expect kopete to start without errors. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 369410] On startup kopete gives me a popup saying "the process for the file: protocol has been terminated unexpectedly"
https://bugs.kde.org/show_bug.cgi?id=369410 --- Comment #1 from Mathias Homann --- Created attachment 101312 --> https://bugs.kde.org/attachment.cgi?id=101312&action=edit Screenshot of the popup in question -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 369410] On startup kopete gives me a popup saying "the process for the file: protocol has been terminated unexpectedly"
https://bugs.kde.org/show_bug.cgi?id=369410 Mathias Homann changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mathias Homann --- turned out to be a local misconfiguration involving mixing two different branding styles for kde4 and plasma5. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368769] New: kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=368769 Bug ID: 368769 Summary: kontact crashes on exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Quitting kontact with ctrl-q or via the menu A lot of times kontact crashes when I quit the app. I can't think of anything else special that I'm doing in such a case, other than quitting the app... The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f96d2d60800 (LWP 4991))] Thread 16 (Thread 0x7f95d17fa700 (LWP 5068)): #0 0x7f96c70b3d10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f96c7071759 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071dcf in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95e0006d00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d17f9dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1576390) at thread/qthread_unix.cpp:344 #8 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f95d27fc700 (LWP 5066)): #0 0x7f96cfa2abfd in poll () at /lib64/libc.so.6 #1 0x7f96c7071e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95cc004c20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d27fbdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1679d50) at thread/qthread_unix.cpp:344 #7 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f95d2ffd700 (LWP 5065)): #0 0x7f96c70b3cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f96c70714b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x14548a0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d2ffcdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1425330) at thread/qthread_unix.cpp:344 #8 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f95d37fe700 (LWP 5064)): #0 0x7f96cfa26ccd in read () at /lib64/libc.so.6 #1 0x7f96c70b2b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95d8004820, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d37fddd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #8 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1425890) at thread/qthread_unix.cpp:344 #9 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f95d3fff700 (LWP 5063)): #0 0x7f96cfa2abfd in poll () at /lib64/libc.so.6 #1 0x7f96c7071e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071f7c in g_main_con
[dolphin] [Bug 365904] "The process for the file protocol died unexpectedly." in all dolphin related places
https://bugs.kde.org/show_bug.cgi?id=365904 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365904] "The process for the file protocol died unexpectedly." in all dolphin related places
https://bugs.kde.org/show_bug.cgi?id=365904 --- Comment #3 from Mathias Homann --- I can confirm this on openSUSE Leap 42.1 using KF5.7.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365904] "The process for the file protocol died unexpectedly." in all dolphin related places
https://bugs.kde.org/show_bug.cgi?id=365904 --- Comment #4 from Mathias Homann --- (In reply to Mathias Homann from comment #3) > I can confirm this on openSUSE Leap 42.1 using KF5.7.5 mathias@kirika:~> rpm -qi dolphin Name: dolphin Version : 15.12.3 Release : 21.1 Architecture: x86_64 Install Date: Mi 14 Sep 2016 17:55:08 CEST Group : Productivity/File utilities Size: 1415402 License : GPL-2.0+ Signature : RSA/SHA256, Fr 01 Apr 2016 00:12:09 CEST, Key ID b88b2fd43dbdc284 Source RPM : dolphin-15.12.3-21.1.src.rpm Build Date : Fr 01 Apr 2016 00:11:18 CEST Build Host : lamb07 Relocations : (not relocatable) Packager: http://bugs.opensuse.org Vendor : openSUSE URL : http://www.kde.org/ Summary : KDE File Manager Description : This package contains the default file manager of KDE Workspaces. Distribution: openSUSE Leap 42.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368934] New: kde control center crashed on exit
https://bugs.kde.org/show_bug.cgi?id=368934 Bug ID: 368934 Summary: kde control center crashed on exit Product: systemsettings Version: 5.7.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mathias.hom...@opensuse.org Application: systemsettings5 (5.7.5) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: closing kde control center after trying to get akonadi to work -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7806e90780 (LWP 4441))] Thread 3 (Thread 0x7f77dc5b3700 (LWP 4476)): #0 0x7f7802c37ccd in read () at /lib64/libc.so.6 #1 0x7f77fa660073 in () at /usr/lib64/tls/libnvidia-tls.so.367.44 #2 0x7f77fce98b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f77fce57999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f77fce57df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f77fce5819a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #6 0x7f77dd378426 in () at /usr/lib64/libgio-2.0.so.0 #7 0x7f77fce7cf65 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f77fed780a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7802c4402d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f77ea719700 (LWP )): #0 0x7f7802c3bbfd in poll () at /lib64/libc.so.6 #1 0x7f77fce57e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f77fce57f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7803540f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f78034f08cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f780333706a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f7803e444b5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f780333b899 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f77fed780a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7802c4402d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f7806e90780 (LWP 4441)): [KCrash Handler] #6 0x7f77db4eb0a0 in () at /usr/lib64/libtelepathy-qt5.so.0 #7 0x7f77db4ef6da in () at /usr/lib64/libtelepathy-qt5.so.0 #8 0x7f77db4cf7b5 in () at /usr/lib64/libtelepathy-qt5.so.0 #9 0x7f77db4cfe7d in Tp::Connection::~Connection() () at /usr/lib64/libtelepathy-qt5.so.0 #10 0x7f77db4cfed9 in Tp::Connection::~Connection() () at /usr/lib64/libtelepathy-qt5.so.0 #11 0x7f77db3fd09d in () at /usr/lib64/libtelepathy-qt5.so.0 #12 0x7f77db3fd21d in Tp::Account::~Account() () at /usr/lib64/libtelepathy-qt5.so.0 #13 0x7f77db3fd279 in Tp::Account::~Account() () at /usr/lib64/libtelepathy-qt5.so.0 #14 0x7f77db41c10f in () at /usr/lib64/libtelepathy-qt5.so.0 #15 0x7f7803397619 in QHashData::free_helper(void (*)(QHashData::Node*)) () at /usr/lib64/libQt5Core.so.5 #16 0x7f77db4164f4 in () at /usr/lib64/libtelepathy-qt5.so.0 #17 0x7f77db41653d in Tp::AccountManager::~AccountManager() () at /usr/lib64/libtelepathy-qt5.so.0 #18 0x7f77db416599 in Tp::AccountManager::~AccountManager() () at /usr/lib64/libtelepathy-qt5.so.0 #19 0x7f77dbba9100 in () at /usr/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so #20 0x7f77dbba91f9 in () at /usr/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so #21 0x7f77ddea3ebe in () at /usr/lib64/qt5/plugins/kcm_kaccounts.so #22 0x7f77ddea3f59 in () at /usr/lib64/qt5/plugins/kcm_kaccounts.so #23 0x7f7802b96b39 in __run_exit_handlers () at /lib64/libc.so.6 #24 0x7f7802b96b85 in () at /lib64/libc.so.6 #25 0x7f7802b80b2c in __libc_start_main () at /lib64/libc.so.6 #26 0x0040cd89 in _start () at ../sysdeps/x86_64/start.S:122 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 --- Comment #12 from Mathias Homann --- it didn't happen for quite some time, but what still happens is that mail is being sent but still keeps sitting in my local outbox after it has been sent. the only way to be sure is to look in the sent mail folder for the account. -- You are receiving this mail because: You are watching all bug changes.
