[Discover] [Bug 467027] New: Discover crashes on startup while feching updates
https://bugs.kde.org/show_bug.cgi?id=467027
Bug ID: 467027
Summary: Discover crashes on startup while feching updates
Classification: Applications
Product: Discover
Version: 5.27.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: discover
Assignee: plasma-b...@kde.org
Reporter: dime...@gmail.com
CC: aleix...@kde.org
Target Milestone: ---
Application: plasma-discover (5.27.2)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.2-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.2 [KCrashBackend]
-- Information about the crash:
I constatnly get a crash when starting while fetching updates, I have tried
online and offline
The crash can be reproduced every time.
-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 std::__atomic_base::load(std::memory_order)
const (__m=std::memory_order_relaxed, this=0x28) at
/usr/include/c++/12.2.1/atomic:578
#7 std::atomic::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=0x28) at
/usr/include/c++/12.2.1/atomic:579
#8
QAtomicOps::loadRelaxed(std::atomic
const&) (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9 QBasicAtomicPointer::loadRelaxed() const
(this=0x28) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 QObjectPrivate::maybeSignalConnected(unsigned int) const
(this=0x7faa24130140, signalIndex=3) at kernel/qobject.cpp:500
#11 0x7faac80be75f in doActivate(QObject*, int, void**)
(sender=0x55d309654330, signal_index=3, argv=0x7fe19050) at
kernel/qobject.cpp:3825
#12 0x7faaca1ce9d7 in
ResultsStream::resourcesFound(QVector const&)
(this=this@entry=0x55d309654330, _t1=...) at
/usr/src/debug/discover/build/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:159
#13 0x7faa751890ca in
PKResultsStream::sendResources(QVector const&, bool)
(this=0x55d309654330, res=..., waitForResolved=) at
/usr/src/debug/discover/discover-5.27.2/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp:542
#14 0x7faa7518d5be in operator() (__closure=0x55d30c32dda0) at
/usr/src/debug/discover/discover-5.27.2/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp:635
#15 std::__invoke_impl&> (__f=...) at
/usr/include/c++/12.2.1/bits/invoke.h:61
#16 std::__invoke_r&> (__fn=...) at
/usr/include/c++/12.2.1/bits/invoke.h:111
#17 std::_Function_handler >::_M_invoke(const
std::_Any_data &) (__functor=) at
/usr/include/c++/12.2.1/bits/std_function.h:290
#18 0x7faac80b1bb0 in QObject::event(QEvent*) (this=0x55d30880c000,
e=0x7faa2400fe40) at kernel/qobject.cpp:1347
#19 0x7faac9b78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55d30880c000, e=0x7faa2400fe40) at
kernel/qapplication.cpp:3640
#20 0x7faac808df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55d30880c000, event=0x7faa2400fe40) at
kernel/qcoreapplication.cpp:1064
#21 0x7faac808dfb3 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#22 0x7faac808ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55d3081c3e10) at
kernel/qcoreapplication.cpp:1821
#23 0x7faac80d4e88 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55d3082cad70) at kernel/qeventdispatcher_glib.cpp:277
#24 0x7faac6d1682b in g_main_dispatch (context=0x7faabc005010) at
../glib/glib/gmain.c:3454
#25 g_main_context_dispatch (context=0x7faabc005010) at
../glib/glib/gmain.c:4172
#26 0x7faac6d6dcc9 in g_main_context_iterate.constprop.0
(context=0x7faabc005010, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4248
#27 0x7faac6d150e2 in g_main_context_iteration (context=0x7faabc005010,
may_block=1) at ../glib/glib/gmain.c:4313
#28 0x7faac80d8c6c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55d3082cbc10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7faac80866ec in
QEventLoop::exec(QFlags) (this=0x7fe19600,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#30 0x7faac8091219 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#31 0x7faac8539fe2 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#32 0x7faac9b76f2a in QApplication::exec() () at
kernel/qapplication.cpp:2832
#33 0x55d30651f947 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/discover/discover-5.27.2/discover/main.cpp:224
[Inferior 1 (process 11871) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[telepathy] [Bug 423845] New: IM log viewer Contacts and history empty
https://bugs.kde.org/show_bug.cgi?id=423845
Bug ID: 423845
Summary: IM log viewer Contacts and history empty
Product: telepathy
Version: 20.04
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: log-viewer
Assignee: kde-telepathy-b...@kde.org
Reporter: dime...@gmail.com
Target Milestone: Future
SUMMARY
The contact list and history is empty in my setup
STEPS TO REPRODUCE
Just start the application
OBSERVED RESULT
empty boxes
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.19.2
(available in About System)
KDE Plasma Version:
KDE Frameworks Version: 5.71
Qt Version: 5.15
ADDITIONAL INFORMATION
When starting from terminal I have the following:
kf5.kxmlgui: KXMLGUI file found at deprecated location
("/usr/share/ktp-log-viewer/log-viewer.rc") -- please use
${KXMLGUI_INSTALL_DIR} to install this file instead.
Shortcut for action "jump-prev-conversation" "&Previous Conversation" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "jump-next-conversation" "&Next Conversation" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
ktp-models: Built with kpeople support, using kpeople model
tp-qt 0.9.8 WARN: Error parsing config file for connection manager "haze" -
introspecting
tp-qt 0.9.8 WARN: Error parsing config file for connection manager "haze" -
introspecting
ktp-logger: loaded factory : TpLoggerPluginFactory(0x559187fff520)
ktp-logger: loaded logger plugin : TpLoggerPlugin(0x559187fff9c0)
Created Utils instance
ktp-logviewer: Skipping initial Kopete logs import, already done.
account= true
objectPath=
"/org/freedesktop/Telepathy/Account/gabble/jabber/ktp_2djabber_2dim_14"
account= 0x55918804e160
account= true
objectPath= "/org/freedesktop/Telepathy/Account/gabble/jabber/google_2dim_8"
account= 0x55918804e2f0
account= true
objectPath=
"/org/freedesktop/Telepathy/Account/haze/skypeweb/ktp_2dhaze_2dskypeweb_2dim_16"
account= 0x55918804e480
account= true
objectPath= "/org/freedesktop/Telepathy/Account/salut/local_xmpp/account1"
account= 0x55918804e610
ktp-logger: Plugin TpLoggerPlugin(0x559187fff9c0) returned 5 entities
ktp-logger: Plugin TpLoggerPlugin(0x559187fff9c0) returned 0 entities
ktp-logger: Plugin TpLoggerPlugin(0x559187fff9c0) returned 16 entities
ktp-logger: Plugin TpLoggerPlugin(0x559187fff9c0) returned 1 entities
--
You are receiving this mail because:
You are watching all bug changes.
[kpeople] [Bug 423845] IM log viewer Contacts and history empty
https://bugs.kde.org/show_bug.cgi?id=423845
Dimitar Petrovski changed:
What|Removed |Added
CC||aleix...@gmail.com
Version|20.04 |unspecified
Component|log-viewer |general
Product|telepathy |kpeople
Target Milestone|Future |---
--- Comment #1 from Dimitar Petrovski ---
The actual problem comes from KPeopleVCard plugin which does not emit the
initialFetchComplete signal. The plugin is added as a dependency for KDE
Connect on Arch, so with KDE Connect installed the ktp-log-viewer is empty.
the following patch fixes the problem:
diff --git a/src/kpeoplevcard.cpp b/src/kpeoplevcard.cpp
index bfaf71e..20531f6 100644
--- a/src/kpeoplevcard.cpp
+++ b/src/kpeoplevcard.cpp
@@ -153,6 +153,8 @@ KPeopleVCard::KPeopleVCard()
processDirectory(QFileInfo(*vcardsLocation));
+emitInitialFetchComplete(true);
+
connect(m_fs, &KDirWatch::dirty, this, [this](const QString& path) {
const QFileInfo fi(path);
if (fi.isFile())
I will try to make a fork and commit the patch.
It is my opinion that some timeout mechanism should be added in KPeople so that
the other plugins still get displayed even if one plugin fails.
--
You are receiving this mail because:
You are watching all bug changes.
[kpeople] [Bug 423845] IM log viewer Contacts and history empty
https://bugs.kde.org/show_bug.cgi?id=423845 Dimitar Petrovski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kpeoplevcard/commit/778d034 ||45f41c536f2ca9116ee6acb5f4f ||01b868 --- Comment #3 from Dimitar Petrovski --- Git commit 778d03445f41c536f2ca9116ee6acb5f4f01b868 by Dimitar Petrovski. Committed on 06/07/2020 at 16:36. Pushed by apol into branch 'master'. Emit the Initial Fetch Complete signal The plugin does not emit the initialFetchComplete signal which seems needed by AllContactsMonitor and PersonsModel does not get initialized since it waitd for the signal from all plugins M +2-0src/kpeoplevcard.cpp https://invent.kde.org/pim/kpeoplevcard/commit/778d03445f41c536f2ca9116ee6acb5f4f01b868 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #16 from Dimitar Petrovski --- I have tested the issue now, and I can not reproduce it, I guess it was fixed during the years -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415144] New: Plasma crashes when trying to chat with instant messaging contact
https://bugs.kde.org/show_bug.cgi?id=415144 Bug ID: 415144 Summary: Plasma crashes when trying to chat with instant messaging contact Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dime...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.2-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Instant messaging, says available (connecting) and contact list is empty (this is another problem since they can contact me), in the search bar I search for a contact, and select one to start chatting, plasma crashes The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f126cc0bc80 (LWP 5845))] Thread 12 (Thread 0x7f121f5fa700 (LWP 10631)): #0 0x7f12705bec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f12710ce610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f12710ce702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1272d57e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1272d580ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f12710c8530 in () at /usr/lib/libQt5Core.so.5 #6 0x7f12705b84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1270d522d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f1238952700 (LWP 8056)): #0 0x7f12705bec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f12710ce610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f12710ce702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1272d57e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1272d580ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f12710c8530 in () at /usr/lib/libQt5Core.so.5 #6 0x7f12705b84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1270d522d3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f123a94e700 (LWP 6121)): #0 0x7f12705bec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f12710ce610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f12710ce702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1272d57e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1272d580ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f12710c8530 in () at /usr/lib/libQt5Core.so.5 #6 0x7f12705b84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1270d522d3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f123bbe7700 (LWP 6061)): #0 0x7f1270d479ef in poll () at /usr/lib/libc.so.6 #1 0x7f126f62a120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f126f62a1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f12712eeb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f127129583c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f12710c7305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f125040c13b in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f12710c8530 in () at /usr/lib/libQt5Core.so.5 #8 0x7f12705b84cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f1270d522d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1252700700 (LWP 5983)): #0 0x7f126f5da479 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f126f629898 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f126f62a046 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f126f62a1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f12712eeb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f127129583c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f12710c7305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f1272ccc70b in () at /usr/lib/libQt5Quick.so.5 #8 0x7f12710c8530 in () at /usr/lib/libQt5Core.so.5 #9 0x7f12705b84cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f1270d522d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f12537fe700 (LWP 5972)): #0 0x7f12705bec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f12710ce610 in QWaitCondition::wait(QMutex*, Q
[krdc] [Bug 365318] New: KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 Bug ID: 365318 Summary: KRDC is unreadable under breeze dark theme Product: krdc Version: unspecified Platform: Ubuntu Packages URL: https://snag.gy/gC2HUB.jpg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: dime...@gmail.com When using breeze dark theme most of the things in KRDC are unreadable, white text on white background Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #2 from Dimitar Petrovski --- I have already added the screenshot in the url of the bug. I have also resolved the problem by selecting breeze-dark as GTK2 and GTK3 theme. It did not thought of it before since I thought that the KRDC was KDE app not Gtk -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #4 from Dimitar Petrovski --- Created attachment 100016 --> https://bugs.kde.org/attachment.cgi?id=100016&action=edit krdc breeze dark problem -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #5 from Dimitar Petrovski --- here is the url: https://snag.gy/gC2HUB.jpg and I have added it as an attachment. I will test other apps for the issue and provide comments here -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #7 from Dimitar Petrovski --- I can reproduce the problem also on: Okular, KTorrent, k3b and KSnapshot file save dialog. I will attach some screenshots for them also Kate, KCalc, Gwenview, digiKam, Amarok, KMail, etc. do not have this problem. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #9 from Dimitar Petrovski --- Created attachment 100018 --> https://bugs.kde.org/attachment.cgi?id=100018&action=edit ktorrent breeze dark problem -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #8 from Dimitar Petrovski --- Created attachment 100017 --> https://bugs.kde.org/attachment.cgi?id=100017&action=edit k3b breeze dark problem -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #10 from Dimitar Petrovski --- Created attachment 100019 --> https://bugs.kde.org/attachment.cgi?id=100019&action=edit okular breeze dark problem -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #11 from Dimitar Petrovski --- One more thing that maybe helps: When I select GTK2 theme Breeze-Dark the problem is fixed The selection of GTK3 does not solve the problem -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 --- Comment #14 from Dimitar Petrovski --- Sorry for the slow response. As I have stated above, if I set the theme from Look & Feel to breeze dark, the problem is present, but it is fixed if I set also breeze dark to gtk2 setting. However I have retested the whole set breeze dark/ breeze light and login logout and the problem is present if I do not also set the gtk2 theme. >From the KDE point I do not know how to set Qt to follow Gtk theme, but if you can point me in the right direction I can test that. I have forgot to mention that I have qt development environment and qt creator, so maybe that messes things up -- You are receiving this mail because: You are watching all bug changes.
