[Elisa] [Bug 473696] New: Lots of warnings/errors in terminal
https://bugs.kde.org/show_bug.cgi?id=473696
Bug ID: 473696
Summary: Lots of warnings/errors in terminal
Classification: Applications
Product: Elisa
Version: 23.04.3
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: radb...@gmail.com
Target Milestone: ---
I use MX-Linux (Debian-Buster-based, Xfce) on an Intel NUC12 with Qt version
5.15.2.
Since the version of Elisa offered at MX-Linux is very old, I now have the
newer version 23.04.3 using snap.
But:
Starting elisa in the terminal brings a whole lot of warnings/errors that I
can't interpret:
$ elisa
Qt: Session management error: Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based authentication
failed
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QApplication(0x7ffeacf0c9f0), parent's thread is
QThread(0x560caf4b6690), current thread is QThread(0x560caf4c3ee0)
QObject::installEventFilter(): Cannot filter events for objects in a different
thread.
kf.kirigami: Failed to find a Kirigami platform plugin
file:///snap/elisa/36/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/Page.qml:328:
Error: Cannot assign QObject* to PageRow_QMLTYPE_30*
file:///snap/elisa/36/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/Page.qml:328:
Error: Cannot assign QObject* to PageRow_QMLTYPE_30*
file:///snap/elisa/36/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
file:///snap/elisa/36/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
org.kde.elisa.indexers.manager: Local file system indexer is inactive
org.kde.elisa.indexers.manager: Baloo indexer is unavailable
org.kde.elisa.indexers.manager: Baloo indexer is inactive
qrc:/qml/MediaPlayListView.qml:118:13: QML Connections: Implicitly defined
onFoo properties in Connections are deprecated. Use this syntax instead:
function onFoo() { ... }
qrc:/qml/MediaPlayListView.qml:118:13: QML Connections: Implicitly defined
onFoo properties in Connections are deprecated. Use this syntax instead:
function onFoo() { ... }
org.kde.elisa.baloo: Baloo service is not detected and seems not be running.
Disabling Elisa support for using Baloo indexer.
org.kde.elisa.indexers.manager: Local file system indexer is active
org.kde.elisa.indexers.manager: MusicListenersManager::startAndroidIndexing
org.kde.elisa.indexers.manager: trigger init of local file indexer
qrc:/qml/FooterBar.qml:31:13: QML Binding: Not restoring previous value because
restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
qrc:/qml/FooterBar.qml:39:13: QML Binding: Not restoring previous value because
restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
qrc:/qml/FooterBar.qml:31:13: QML Binding: Not restoring previous value because
restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
qrc:/qml/FooterBar.qml:39:13: QML Binding: Not restoring previous value because
restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
qrc:/qml/FooterBar.qml:31:13: QML Binding: Not restoring previous value because
restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
qrc:/qml/FooterBar.qml:39:13: QML Binding: Not restoring previous value because
restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is
[Elisa] [Bug 473545] New: Some bugs and inadequacies (Linux version)
https://bugs.kde.org/show_bug.cgi?id=473545 Bug ID: 473545 Summary: Some bugs and inadequacies (Linux version) Classification: Applications Product: Elisa Version: 20.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: radb...@gmail.com Target Milestone: --- Preliminary: I've been trying for a while to recreate all the programs/functions of my previous "main computer" a Mac Mini, in Linux. As far as managing and playing music is concerned, so far "Elisa" is the best approximation to iTunes/Apple Music i could find. Therefore many thanks to the developers! However, I have found some bugs/inadequacies: 1. in my music folder there are subfolders that I do NOT want to play with Elisa (audio books). In this respect, it should also be possible not only to add new paths, but also to remove / exclude paths. 2. if I "re-read" the music collection, then NOTHING is visible at first, neither albums nor artists etc.. Only after quitting and restarting Elisa, the newly read in music collection is available again. 3. if I click on "Genre" on the left, all matching artists are displayed in the main window. This is not factually correct: Artists cannot be clearly assigned to a genre, but albums can. So the albums matching the genre (with cover) should be displayed in the main window. I use "Elisa" under MX-Linux 21.3 on an Intel NUC12 (64 bit). Best regards Clemens -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 444339] New: seemingly random crash when entering/leaving fullscreen
https://bugs.kde.org/show_bug.cgi?id=444339 Bug ID: 444339 Summary: seemingly random crash when entering/leaving fullscreen Product: gwenview Version: 21.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: linuxhi...@gmail.com Target Milestone: --- Application: gwenview (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.13-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: I entered exited fullscreen mode - Unusual behavior I noticed: gwenview has no visible title bar until I moved it around, later it crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7ff01b42d9df in KIO::UDSEntry::UDSEntry(KIO::UDSEntry const&) () from /lib64/libKF5KIOCore.so.5 #5 0x7ff01b875bcf in Gwenview::ThumbnailProvider::slotResult(KJob*) () from /lib64/libgwenviewlib.so.5 #6 0x7ff019e313a9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7ff01a18ecf0 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #8 0x7ff01a1935cb in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #9 0x7ff01b5c95c8 in KIO::PreviewJobPrivate::startPreview() () from /lib64/libKF5KIOWidgets.so.5 #10 0x7ff019e27f09 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7ff01aaa4443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7ff019dfd798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7ff019e00d06 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7ff019e4f0d7 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7ff0180644cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7ff0180b84f8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7ff018061c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7ff019e4eb78 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7ff019dfc1a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7ff019e046e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #21 0x5581f6b52933 in main () [Inferior 1 (process 4475) detached] The reporter indicates this bug may be a duplicate of or related to bug 444091. Possible duplicates by query: bug 444091, bug 444002, bug 443954, bug 443935, bug 443784. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439968] New: dolphin takes a long time to start after having logged out and in again
https://bugs.kde.org/show_bug.cgi?id=439968 Bug ID: 439968 Summary: dolphin takes a long time to start after having logged out and in again Product: dolphin Version: 21.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: linuxhi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140138 --> https://bugs.kde.org/attachment.cgi?id=140138=edit strace output of slow startup + abort (Strg+C) SUMMARY When logging out & in again (same user) some applications like dolphin take very long to start. Strace shows they are waiting on some condition - please see the attached log file. STEPS TO REPRODUCE 1. log in -> dolphin starts quite fast 2. log out & in again (same user is sufficient) 3. start dolphin -> take 10-15s. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439609] New: crash creating folder on MTP device
https://bugs.kde.org/show_bug.cgi?id=439609 Bug ID: 439609 Summary: crash creating folder on MTP device Product: dolphin Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: linuxhi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.12.13-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: When I created a new folder (using the right-click context menu New->Folder) on my Huawei P20 phone, Dolphin immediatly crashed. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7fa384ad2189 in QLineEdit::text() const () from /lib64/libQt5Widgets.so.5 #5 0x7fa385bc1c48 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () from /lib64/libKF5KIOFileWidgets.so.5 #6 0x7fa383e65386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7fa384f891c0 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #8 0x7fa384f8de8b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #9 0x7fa383e65386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7fa385725f6a in KIO::SlaveInterface::error(int, QString const&) () from /lib64/libKF5KIOCore.so.5 #11 0x7fa385725637 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #12 0x7fa38571e05d in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #13 0x7fa3857277a2 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #14 0x7fa383e65386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fa383e5dd1e in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fa38498eec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7fa383e35bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7fa383e388c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #19 0x7fa383e82c27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7fa381ddea9f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7fa381e30a98 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7fa381ddbe73 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7fa383e826f3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7fa383e3457b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7fa383e3c1b4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x7fa385f75d5e in kdemain () from /lib64/libkdeinit5_dolphin.so #27 0x7fa385d7b1e2 in ?? () from /lib64/libc.so.6 #28 0x55ec1d7f00ae in _start () [Inferior 1 (process 5056) detached] Possible duplicates by query: bug 439605, bug 439542, bug 439303, bug 439043, bug 438933. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437818] Crash when loggin in after having logged out previously
https://bugs.kde.org/show_bug.cgi?id=437818 Clemens Eisserer changed: What|Removed |Added CC||linuxhi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437818] Crash when loggin in after having logged out previously
https://bugs.kde.org/show_bug.cgi?id=437818 --- Comment #5 from Clemens Eisserer --- Created attachment 139731 --> https://bugs.kde.org/attachment.cgi?id=139731=edit New crash information added by DrKonqi plasmashell (5.20.5) using Qt 5.15.2 - What I was doing when the application crashed: logged out and in again, which sometimes works - sometimes results in various crashes. -- Backtrace (Reduced): #6 0x7f5d87523db6 in _dbus_abort.cold () from /lib64/libdbus-1.so.3 #7 0x7f5d87549310 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3 #8 0x7f5d89044059 in QDBusConnectionPrivate::getNameOwnerNoCache(QString const&) () from /lib64/libQt5DBus.so.5 #9 0x7f5d89046051 in QDBusConnectionPrivate::addSignalHook(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5 #10 0x7f5d890476c5 in QtPrivate::QSlotObject, bool>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libQt5DBus.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437818] Crash when loggin in after having logged out previously
https://bugs.kde.org/show_bug.cgi?id=437818 --- Comment #4 from Clemens Eisserer --- what I find interesting - most of the time, those bugs are catched by the system-wide bug reporting utility (ABRT), only on rare occuasions the kde bug reporter is able to catch a crash. This seems to be a sad thing, because the bugs filed at redHat usually are not noticed by anybody and every 6 months I get about 20 emails regarding bugs that will be auto-closed because their reported release is approacing EOL. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437818] Crash when loggin in after having logged out previously
https://bugs.kde.org/show_bug.cgi?id=437818 --- Comment #3 from Clemens Eisserer --- When logging out & in again, I see all kinds of weird behaviour, sometimes crashes on login, sometimes wifi does not work anymore - and sometimes everything works as expected. I'll give the usb live system a try, F34 changed quite a bit and to be honest I am a bit reluctant to see my production desktop broken again (wayland) or without audio (pipewire) ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437818] New: Crash when loggin in after having logged out previously
https://bugs.kde.org/show_bug.cgi?id=437818 Bug ID: 437818 Summary: Crash when loggin in after having logged out previously Product: plasmashell Version: 5.20.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: linuxhi...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.12.7-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: When KDE started after login I got this crash, which seems to happen randomly when the login was performed after a previous logout (not a clean boot). The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f0345ce29e5 in raise () from /lib64/libc.so.6 #5 0x7f0345ccb8a4 in abort () from /lib64/libc.so.6 #6 0x7f03450cfdb6 in _dbus_abort.cold () from /lib64/libdbus-1.so.3 #7 0x7f03450f5310 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3 #8 0x7f0346bf0059 in QDBusConnectionPrivate::getNameOwnerNoCache(QString const&) () from /lib64/libQt5DBus.so.5 #9 0x7f0346bf2051 in QDBusConnectionPrivate::addSignalHook(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5 #10 0x7f0346bf36c5 in QtPrivate::QSlotObject, bool>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libQt5DBus.so.5 #11 0x7f0346303d1e in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f03462dbbad in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f03462de8c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7f0346328c27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7f03447f1a9f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7f0344843a98 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7f03447eee73 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7f03463286f3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7f03462da57b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f034613fb67 in QThread::exec() () from /lib64/libQt5Core.so.5 #21 0x7f0346be010b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #22 0x7f0346140df0 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #23 0x7f034513d3f9 in start_thread () from /lib64/libpthread.so.0 #24 0x7f0345da64c3 in clone () from /lib64/libc.so.6 Thread 2 (LWP 3456 "QXcbEventQueue"): #1 0x7f034817d842 in _xcb_conn_wait.part.0 () from /lib64/libxcb.so.1 #2 0x7f034817f1cc in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f0334525448 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f0346140df0 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f034513d3f9 in start_thread () from /lib64/libpthread.so.0 #6 0x7f0345da64c3 in clone () from /lib64/libc.so.6 Thread 1 (LWP 3392 "plasmashell"): #1 0x7f0346142d51 in QSemaphore::acquire(int) () from /lib64/libQt5Core.so.5 #2 0x7f034630b2bd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #3 0x7f0346c30d07 in QDBusConnectionPrivate::signalNeedsConnecting(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5 #4 0x7f0346be889c in QDBusConnectionPrivate::connectRelay(QString const&, QString const&, QString const&, QDBusAbstractInterface*, QMetaMethod const&) () from /lib64/libQt5DBus.so.5 #5 0x7f0346302b4a in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5 #6 0x7f0346302ebd in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5 #7 0x7f034833c3c8 in std::_Function_handler::_M_invoke(std::_Any_data const&) () from /lib64/libKF5Activities.so.5 #8 0x7f034833ae77 in KActivities::ActivitiesCache::self() () from /lib64/libKF5Activities.so.5 #9 0x7f034833022b in KActivities::Consumer::Consumer(QObject*) () from /lib64/libKF5Activities.so.5 #10 0x7f0348330b2d in KActivities::Controller::Controller(QObject*) () from /lib64/libKF5Activities.so.5 #11 0x56367c7beb35 in main () [Inferior
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #13 from Clemens Eisserer --- Created attachment 137303 --> https://bugs.kde.org/attachment.cgi?id=137303=edit New crash information added by DrKonqi dolphin (20.12.2) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f7fb34e3e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f7fb34e42d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f7fb0ff6c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f7fb0ff6107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f7fb344bd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #12 from Clemens Eisserer --- Created attachment 137302 --> https://bugs.kde.org/attachment.cgi?id=137302=edit New crash information added by DrKonqi korgac (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f01f1061e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f01f10622d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f01eda8cc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f01eda8c107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f01f0fc9d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #11 from Clemens Eisserer --- Created attachment 137301 --> https://bugs.kde.org/attachment.cgi?id=137301=edit New crash information added by DrKonqi akonadi_followupreminder_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f499e4a8e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f499e4a92d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f499e6c6c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f499e6c6107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f499e410d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #10 from Clemens Eisserer --- Created attachment 137300 --> https://bugs.kde.org/attachment.cgi?id=137300=edit New crash information added by DrKonqi kdeconnectd (20.12.2) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #4 0x7f201c161a2e in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /lib64/libQt5Core.so.5 #5 0x7f201c764695 in QWindowSystemInterface::handleScreenOrientationChange(QScreen*, Qt::ScreenOrientation) () from /lib64/libQt5Gui.so.5 #6 0x7f20180fdd46 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f20180fe2d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #8 0x7f2017eaec04 in ffi_call_unix64 () from /lib64/libffi.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #9 from Clemens Eisserer --- Created attachment 137299 --> https://bugs.kde.org/attachment.cgi?id=137299=edit New crash information added by DrKonqi akonadi_ical_resource (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #4 0x7fc940c05a2e in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /lib64/libQt5Core.so.5 #5 0x7fc940212695 in QWindowSystemInterface::handleScreenOrientationChange(QScreen*, Qt::ScreenOrientation) () from /lib64/libQt5Gui.so.5 #6 0x7fc93bf49d46 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #7 0x7fc93bf4a2d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #8 0x7fc93ba33c04 in ffi_call_unix64 () from /lib64/libffi.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #8 from Clemens Eisserer --- Created attachment 137298 --> https://bugs.kde.org/attachment.cgi?id=137298=edit New crash information added by DrKonqi akonadi_mailfilter_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7fd610ab2e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7fd610ab32d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7fd60c8cdc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7fd60c8cd107 in ffi_call () from /lib64/libffi.so.6 #9 0x7fd610a18d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #7 from Clemens Eisserer --- Created attachment 137297 --> https://bugs.kde.org/attachment.cgi?id=137297=edit New crash information added by DrKonqi akonadi_newmailnotifier_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f596ac8ee65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f596ac8f2d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f596a6a9c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f596a6a9107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f596abf6d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #6 from Clemens Eisserer --- Created attachment 137296 --> https://bugs.kde.org/attachment.cgi?id=137296=edit New crash information added by DrKonqi akonadi_akonotes_resource (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f2615bf6e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f2615bf72d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f2615fb8c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f2615fb8107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f2615b5ed10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #5 from Clemens Eisserer --- Created attachment 137295 --> https://bugs.kde.org/attachment.cgi?id=137295=edit New crash information added by DrKonqi akonadi_archivemail_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #4 0x7f312912ea3a in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /lib64/libQt5Core.so.5 #5 0x7f31283e0695 in QWindowSystemInterface::handleScreenOrientationChange(QScreen*, Qt::ScreenOrientation) () from /lib64/libQt5Gui.so.5 #6 0x7f311d5ced46 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f311d5cf2d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #8 0x7f311b414c04 in ffi_call_unix64 () from /lib64/libffi.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #4 from Clemens Eisserer --- Created attachment 137294 --> https://bugs.kde.org/attachment.cgi?id=137294=edit New crash information added by DrKonqi akonadi_unifiedmailbox_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f679f7cce65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f679f7cd2d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f679d0f0c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f679d0f0107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f679f734d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #3 from Clemens Eisserer --- Created attachment 137293 --> https://bugs.kde.org/attachment.cgi?id=137293=edit New crash information added by DrKonqi akonadi_sendlater_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f74f7d78e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f74f7d792d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f74f5414c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f74f5414107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f74f7ce0d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 --- Comment #2 from Clemens Eisserer --- Created attachment 137292 --> https://bugs.kde.org/attachment.cgi?id=137292=edit New crash information added by DrKonqi akonadi_maildispatcher_agent (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: - Unusual behavior I noticed: crash after enabling second monitor in system settings -- Backtrace (Reduced): #5 0x7f77d94dbe65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f77d94dc2d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f77d98cac04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f77d98ca107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f77d9443d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 Clemens Eisserer changed: What|Removed |Added CC||linuxhi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435295] New: crash after enabling second monitor
https://bugs.kde.org/show_bug.cgi?id=435295 Bug ID: 435295 Summary: crash after enabling second monitor Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: linuxhi...@gmail.com Target Milestone: --- Application: akonadi_indexing_agent (5.16.2 (20.12.2)) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.11-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.3 Distribution: Fedora 34 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: crash after enabling second monitor I enabled the laptop monitor which was previously disabled in my laptop+external monitor setup The reporter is unsure if this crash is reproducible. -- Backtrace: Application: akonadi_indexing_agent (akonadi_indexing_agent), signal: Segmentation fault [KCrash Handler] #4 0x55beb8c2db00 in ?? () #5 0x7f28b36a5e65 in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /lib64/libQt5WaylandClient.so.5 #6 0x7f28b36a62d7 in QtWaylandClient::QWaylandScreen::output_done() () from /lib64/libQt5WaylandClient.so.5 #7 0x7f28b32dbc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f28b32db107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f28b360dd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #10 0x7f28b360e42b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #11 0x7f28b360e61c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #12 0x7f28b36986e3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #13 0x7f28b7d844fd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x7f28b7d86b3a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #15 0x7f28b7d872d4 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f28b8908e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f28b7d53f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f28b7da117f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f28b63c146f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f28b64153a8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #21 0x7f28b63beba3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f28b7da06f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f28b7d529b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f28b7d5a544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55beb806edf5 in int Akonadi::AgentBase::init(int, char**) () #26 0x7f28b76f1b75 in __libc_start_main () from /lib64/libc.so.6 #27 0x55beb80668ce in _start () [Inferior 1 (process 1444) detached] Possible duplicates by query: bug 377347, bug 377346, bug 376678, bug 321447, bug 293627. Reported using DrKonqi This report was filed against 'kde' because the product 'akonadi_indexing_agent' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 429289] New: crash when closing dragon player while playing video
https://bugs.kde.org/show_bug.cgi?id=429289 Bug ID: 429289 Summary: crash when closing dragon player while playing video Product: dragonplayer Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: linuxhi...@gmail.com CC: myr...@kde.org Target Milestone: --- Application: dragon (20.08.1) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.18-300.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I closed dragon while a video was playing -> crash. i wonder ... is a kde-specific video player really nescessary? why not simply ship VLC or another mature player and use the saved work to enhance the actual kde desktop interface (instead of trying to provide kde versions of every single available software package)? -- Backtrace: Application: Dragon Player (dragon), signal: Aborted [KCrash Handler] #4 0x7f83a333a9d5 in raise () from /lib64/libc.so.6 #5 0x7f83a33238a4 in abort () from /lib64/libc.so.6 #6 0x7f83a1df2e04 in flush () from /usr/lib64/pulseaudio/libpulsecommon-13.99.so #7 0x7f83a1df305f in pa_fdsem_after_poll () from /usr/lib64/pulseaudio/libpulsecommon-13.99.so #8 0x7f83a1e0fd8d in semread_cb () from /usr/lib64/pulseaudio/libpulsecommon-13.99.so #9 0x7f83a2d6978e in dispatch_func () from /lib64/libpulse-mainloop-glib.so.0 #10 0x7f83a2367fd7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #11 0x7f83a23b8d88 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #12 0x7f83a236541f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #13 0x7f83a3a9aa2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #14 0x7f83a3a4e64b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #15 0x7f83a3a56010 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #16 0x555a30b1003d in main () [Inferior 1 (process 38400) detached] Possible duplicates by query: bug 429233, bug 428296, bug 427618, bug 426577, bug 425507. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428043] New: crash when I typed "exit" in the terminal panel
https://bugs.kde.org/show_bug.cgi?id=428043 Bug ID: 428043 Summary: crash when I typed "exit" in the terminal panel Product: dolphin Version: 20.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: linuxhi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.04.1) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.15-201.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: crash when I typed "exit" in the terminal panel, despite it worked all the times before. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdb146fd940 (LWP 5759))] Thread 16 (Thread 0x7fdac3652700 (LWP 5774)): #0 0x7ffc467f5a6d in clock_gettime () #1 0x7fdb1b0756e5 in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6 #2 0x7fdb19226415 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7fdb19224d5d in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7fdb192251a9 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7fdb192268be in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7fdb17174fc2 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #7 0x7fdb171759db in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #8 0x7fdb17175be3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #9 0x7fdb19226b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #10 0x7fdb191d991b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7fdb19045427 in QThread::exec() () from /lib64/libQt5Core.so.5 #12 0x7fdb19046690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #13 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #14 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7fdaf0a79700 (LWP 5773)): #0 0x7fdb17b22e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdafee3686b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fdafee3633b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7fdaf127a700 (LWP 5772)): #0 0x7fdb17b22e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdafee3686b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fdafee3633b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fdaf1a7b700 (LWP 5771)): #0 0x7fdb17b22e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdafee3686b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fdafee3633b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fdaf227c700 (LWP 5770)): #0 0x7fdb17b22e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdafee3686b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fdafee3633b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fdaf2a7d700 (LWP 5769)): #0 0x7fdb17b22e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdafee3686b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fdafee3633b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fdaf327e700 (LWP 5768)): #0 0x7fdb17b22e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdafee3686b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fdafee3633b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fdb17b1c432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb1b0ae913 in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fdafc97e700 (LWP 5767)): #0
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #190 from Clemens Eisserer --- even worse - with F31 + latest updates I get not only horizontal lines but blinking / missing text. it makes konsole almost unuseable. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407053] New: scrollbar almost invisible
https://bugs.kde.org/show_bug.cgi?id=407053 Bug ID: 407053 Summary: scrollbar almost invisible Product: konsole Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: linuxhi...@gmail.com Target Milestone: --- Created attachment 119714 --> https://bugs.kde.org/attachment.cgi?id=119714=edit screenshot SUMMARY After fedora shipped latest KDE updates, the scrollbar in konsole is almost invisble. It might look nice, but from a usability point of view it is pure horror (imagine working on a laptop with sub-optimal lightning). please see screenshot for more details. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #71 from Clemens Eisserer --- > There is no need to state it multiple times. > If the issue gets fixed, the bug gets closed. I guess the reason why there are so many "me too"s is that there is nothing done about it and the bug was filed exactly two years ago. This is rather basic functionality broken in a (these days) rather common environment. I could now go on and complain about bugs in core-functionality, while developer time is spent on KDE-branded applications just for the sake of having a QT-clone available, but I guess it would do no good. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 402049] New: Neither docs nore help nore Templates nore man pages can be found
https://bugs.kde.org/show_bug.cgi?id=402049 Bug ID: 402049 Summary: Neither docs nore help nore Templates nore man pages can be found Product: telepathy Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: documentation Assignee: kde-telepathy-b...@kde.org Reporter: y...@vienna.at Target Milestone: Future SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #56 from Clemens Eisserer --- > Once Qt 5.12 comes out, we can re-open this if the lines are still present. > It's quite likely that this will be as well. Could we let this report open, until we know for sure instead of closing it without a single confirmation that it has been really fixed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #49 from Clemens Eisserer --- i am already couting days to the 2 year anniversary bug-report ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394465] Logout-Screen distorted on hidpi screens
https://bugs.kde.org/show_bug.cgi?id=394465 --- Comment #1 from Clemens Eisserer <linuxhi...@gmail.com> --- follow up: for the screenshot I had graycsale anitaliasing enabled for text, so it doesn't look asugly as it would with subpixel/rgb antialiasing enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394465] New: Logout-Screen distorted on hidpi screens
https://bugs.kde.org/show_bug.cgi?id=394465 Bug ID: 394465 Summary: Logout-Screen distorted on hidpi screens Product: plasmashell Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: linuxhi...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112763 --> https://bugs.kde.org/attachment.cgi?id=112763=edit screenshot On HiDPI screens the logout screen has distorted fonts & graphics. It seems like bitmap scaling is applied instead of rendering the content with a higher dpi setting. This causes especially text to appear distorted, as subpixel smoothing causes further colorful artifacts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #11 from Clemens Eisserer <linuxhi...@gmail.com> --- I can confirm this issue disappears as soon as I set "splash screen" to none. So instead of some display detection code being buggy, it seems something as ordinary as the splash screen is causing this issue. @Fabio: do you also experience this only on multi-display setups? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 393676] New: Somtimes all days are selected in calendar plasma plugin
https://bugs.kde.org/show_bug.cgi?id=393676 Bug ID: 393676 Summary: Somtimes all days are selected in calendar plasma plugin Product: kdeplasma-addons Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: linuxhi...@gmail.com Target Milestone: --- Sometimes multiple or even all days are selected after the calendar pops up: https://youtu.be/1wKmG1lD_m0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] When compositing is disabled, switching to another virtual desktop with Kicker open prevents it from showing again
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #21 from Clemens Eisserer <linuxhi...@gmail.com> --- There are use-cases where disabling the compositor makes actually sense - like running inside VirtualBox on a 4k monitor setup. Now imagine the outrage if Windows-7 would not open the start-menu after a few times in case the user decides to disable Aero. Too bad even core components are that buggy :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #8 from Clemens Eisserer <linuxhi...@gmail.com> --- KDE startup on my dual-screen AMD system: https://youtu.be/F4uIm3LVIwg KDE startup on my old intel notebook: https://youtu.be/JvJPieBXNpo Both systems have exactly the same software configuration, as I use one SSD (Crucial MX500) for both systems and swap it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #7 from Clemens Eisserer <linuxhi...@gmail.com> --- I could try to get stacktraces during boot - any idea which processes I should monitor? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #6 from Clemens Eisserer <linuxhi...@gmail.com> --- already posted above -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #4 from Clemens Eisserer <linuxhi...@gmail.com> --- I am using lightdm, so the file you asked for is not present. However, this is the content of /var/log/lightdm.log: [+0.00s] DEBUG: Starting Light Display Manager 1.25.1, UID=0 PID=1094 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-backup-logs.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-minimum-vt.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-session-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-user-authority-in-system-dir.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: [LightDM] contains unknown option autologin-user [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Monitoring logind for seats [+0.01s] DEBUG: New seat added from logind: seat0 [+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.01s] DEBUG: Seat seat0: Starting [+0.01s] DEBUG: Seat seat0: Creating user session [+0.01s] DEBUG: Loading users from org.freedesktop.Accounts [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.07s] DEBUG: Seat seat0: Creating display server of type x [+0.07s] DEBUG: Deactivating Plymouth [+0.09s] DEBUG: Using VT 1 [+0.09s] DEBUG: Seat seat0: Starting local X display on VT 1 [+0.09s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.09s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.14s] DEBUG: XServer 0: Launching X Server [+0.14s] DEBUG: Launching process 1102: /usr/bin/X -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0 -listen tcp vt1 -novtswitch -background none [+0.14s] DEBUG: XServer 0: Waiting for ready signal from X server :0 [+0.14s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.14s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+1.38s] DEBUG: Got signal 10 from process 1102 [+1.38s] DEBUG: XServer 0: Got signal from X server :0 [+1.38s] DEBUG: XServer 0: Connecting to XServer :0 [+1.39s] DEBUG: Quitting Plymouth; retaining splash [+1.41s] DEBUG: Seat seat0: Display server ready, starting session authentication [+1.41s] DEBUG: Session pid=1117: Started with service 'lightdm-autologin', username 'ce' [+1.44s] DEBUG: Session pid=1117: Authentication complete with return value 0: Success [+1.44s] DEBUG: Seat seat0: Session authenticated, running command [+1.44s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0 [+1.44s] DEBUG: Session pid=1117: Running command /etc/X11/xinit/Xsession /usr/bin/startkde [+1.44s] DEBUG: Creating shared data directory /var/lib/lightdm-data/ce [+1.44s] DEBUG: Session pid=1117: Logging to .xsession-errors [+1.50s] DEBUG: Activating VT 1 [+1.50s] DEBUG: Activating login1 session 1 [+1.50s] DEBUG: Seat seat0 changes active session to 1 [+1.50s] DEBUG: Session 1 is already active -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #2 from Clemens Eisserer <linuxhi...@gmail.com> --- This seems somehow linked to my hardware configuration - I am using the same SSD on both my desktop PC as well as my notebook (this way I don't have to take care syncing two systems, while I still get the benefits of a more powerful desktop PC). Desktop System: AMD Kaveri 7650k, AMD GCN apu (radeonsi + amdgpu), 4k monitor on HDMI, FHD monitor connected via DVI Laptop: Elitebook 2540po, Core i5 540M, Intel HD Graphics (GEN 5) When booting the system on the Elitebook, kde starts pretty fast - on the deksop system I can watch the start animation spin for ~30s. Maybe this has something to do with probing monitors? I'll try gathering some additional information. My xsession-errors seems clean after booting the desktop system: startkde: Starting up... 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/disable_kmix.upd' for new updates 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/fonts_akregator.upd' for new updates 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/fonts_global.upd' for new updates 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/fonts_global_toolbar.upd' for new updates 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/fonts_kate.upd' for new updates 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/gtkbreeze5.5.upd' for new updates 2018-03-31T22:13:57 gtkbreeze5.5.upd: Found new update 'GTKBreeze5.5' 2018-03-31T22:13:57 gtkbreeze5.5.upd:3:'Script=gtkbreeze5.5': Script 'gtkbreeze5.5' not found 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/krdb_libpathwipe.upd' for new updates 2018-03-31T22:13:57 krdb_libpathwipe.upd: Found new update 'LibraryPathWipeOut' 2018-03-31T22:13:57 krdb_libpathwipe.upd:3:'Script=krdb_clearlibrarypath': Script 'krdb_clearlibrarypath' not found 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/krunnerplugins.upd' for new updates 2018-03-31T22:13:57 krunnerplugins.upd: Found new update '5.9KRunnerPlugins' 2018-03-31T22:13:57 krunnerplugins.upd:3:'Script=krunnerplugins': Script 'krunnerplugins' not found 2018-03-31T22:13:57 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates vmware-user: could not open /proc/fs/vmblock/dev (uint32 1,) Cannot save the changes made to the configuration Successfully migrated abrt-applet:AutoreportingEnabled to org.gnome.desktop.privacy:report-technical-problems OpenGL vendor string: X.Org OpenGL renderer string: AMD KAVERI (DRM 3.23.0 / 4.15.13-300.fc27.x86_64, LLVM 5.0.1) OpenGL version string: 4.5 (Core Profile) Mesa 17.3.6 OpenGL shading language version string: 4.50 Driver: Unknown GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 17.3.6 Linux kernel version: 4.15.13 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] New: After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 Bug ID: 392556 Summary: After updating Fedora-27 to plasma-5.12, login takes >30s Product: plasmashell Version: 5.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: linuxhi...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 After updating my Fedora-27 system to kde-5.12.2/5.12.3 - the time from login to desktop took a noticeable hit. While 5.11 was already quite slow compared to Gnome or XFCE, with 5.12 there is definitivly something wrong (especially keeping in mnid the changes in 5.12 to actually *improve* startup time). What are the preferred was to gather additional information? Is there any way to find out for what event plasma is waiting during startup? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 391302] SigSEV in QXcbConnection::processXcbEvents()
https://bugs.kde.org/show_bug.cgi?id=391302 --- Comment #5 from Clemens Eisserer <linuxhi...@gmail.com> --- seems ot be fixed, I haven't seen those issues after upgrading to 5.12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392076] Kwin issues illegal OpenGL calls when ALT+TABing through window list
https://bugs.kde.org/show_bug.cgi?id=392076 --- Comment #2 from Clemens Eisserer <linuxhi...@gmail.com> --- this happens with the "Breeze" switcher theme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392076] New: Kwin issues illegal OpenGL calls when ALT+TABing through window list
https://bugs.kde.org/show_bug.cgi?id=392076 Bug ID: 392076 Summary: Kwin issues illegal OpenGL calls when ALT+TABing through window list Product: kwin Version: 5.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: linuxhi...@gmail.com Target Milestone: --- Created attachment 111518 --> https://bugs.kde.org/attachment.cgi?id=111518=edit screenshot of error message When running Kwin with MESA_DEBUG=1, I get the the following output when ALT+TABing through the window list: Mesa: User error: GL_INVALID_OPERATION in GlTexSubImage2D(invalid texture level 0) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Rectangular Region Selection doesn't work w/ scaling on multiple monitors
https://bugs.kde.org/show_bug.cgi?id=385885 Clemens Eisserer <linuxhi...@gmail.com> changed: What|Removed |Added CC||linuxhi...@gmail.com --- Comment #2 from Clemens Eisserer <linuxhi...@gmail.com> --- I can reproduce this issue with Spectacle 17.12.1, same setting as the original reporter: 4k main display + FullHD and some scaling factor applied (1.4 in my case) However, contrary to the duplicate suggestion (Bug 381528), the cursor correctly apperas and I can perform a sepection - it is just the selection area doesn't correctly show both monitors. Please see the following video: https://youtu.be/BMzENE6t1kE So I think this bug is valid for its own and reproduceable. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Rectangular Region Selection doesn't work w/ scaling on multiple monitors
https://bugs.kde.org/show_bug.cgi?id=385885 Clemens Eisserer <linuxhi...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #18 from Clemens Eisserer <linuxhi...@gmail.com> --- I finally found the root cause of this issue: I am using kwin/kde with no compositor. When I enable the compositor, the application menu behaves as expected - when I start plasma with the compositor disabled it is broken once I switch to another virtual desktop while the menu was open. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 391302] SigSEV in QXcbConnection::processXcbEvents()
https://bugs.kde.org/show_bug.cgi?id=391302 --- Comment #2 from Clemens Eisserer <linuxhi...@gmail.com> --- Indeed, sorry - this is the bug I was talking about: https://bugzilla.redhat.com/show_bug.cgi?id=1537282 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391303] New: Crash while pasting files from clipboard
https://bugs.kde.org/show_bug.cgi?id=391303 Bug ID: 391303 Summary: Crash while pasting files from clipboard Product: dolphin Version: 17.12.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: linuxhi...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- When pasting files from the clipboard, dolphin suddenly crashed. Please see the automatically generated error report at fedoras bugzilla instance for more crash details: https://bugzilla.redhat.com/show_bug.cgi?id=1551038 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 391302] New: SigSEV in QXcbConnection::processXcbEvents()
https://bugs.kde.org/show_bug.cgi?id=391302 Bug ID: 391302 Summary: SigSEV in QXcbConnection::processXcbEvents() Product: kactivitymanagerd Version: 5.11.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: linuxhi...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I see kactivitymanagerd crash with a segmentation fault in QXcbConnection::processXcbEvents() from time to time when logging out, and Fedora's Bugzilla shows I am not the only one experiencing this issue (CC list with 63 users): https://bugzilla.redhat.com/show_bug.cgi?id=1551038 Please see the fedora bug report for strack-traces and crash information. I am using Fedora 27 with kactivitymanagerd-5.11.5-1.fc27.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 Clemens Eisserer <linuxhi...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #14 from Clemens Eisserer <linuxhi...@gmail.com> --- another finding: doesn't make a difference whether I have the application menu in the taskbar or on the desktop, broken behaviour is the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #13 from Clemens Eisserer <linuxhi...@gmail.com> --- video of the issue: https://www.youtube.com/watch?v=xznM6m2IUAU=youtu.be updated to updates-testing: qt5-qtbase-5.9.4-1.fc27.x86_64 kf5-plasma-5.43.0-3.fc27.x86_64 plasma-workspace-5.11.5-3.fc27.x86_64 ... issue is still existant. Is there anything I can do to diagnose this issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #11 from Clemens Eisserer <linuxhi...@gmail.com> --- > how exactly are you switching virtual desktops By clicking on the virtual desktop chooser kf5-plasma is a little bit older on my machine: qt5-qtbase-5.9.4-1.fc27.x86_64 kf5-plasma-5.42.0-1.fc27.x86_64 plasma-workspace-5.11.5-3.fc27.x86_64 I'll enable updates-testing and report back -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #9 from Clemens Eisserer <linuxhi...@gmail.com> --- > For what it's worth, that trigger recipe is not reproducible > for me on my fedora 27 box. Funny, I've just verified it has nothing to do with my multi-monitor setup. Just took my SSD and bootet it in my laptop (single-screen), same behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #7 from Clemens Eisserer <linuxhi...@gmail.com> --- Found out what is causing this: When I switch the virtual desktop while the application / launcher is shown, it is left in broken state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #6 from Clemens Eisserer <linuxhi...@gmail.com> --- another thing I noted: when I remove such a mis-behaving application menu (hover mouse above, wait for popup and click red "x" icon), the plugin is removed. When I now choose "revert", it is restored, it still doesn't work. In case I remove it completle and add a new one, it works again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #5 from Clemens Eisserer <linuxhi...@gmail.com> --- I experience the issue almost every time. Funny enough, for fallback reasons I've added the smaller application menu - and after some time it now exhibits the same issue. So I have two icons, application starter and application menu, both not displaying :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #3 from Clemens Eisserer <linuxhi...@gmail.com> --- not knowingly, can it be triggered by accident? I initially thought maybe the menu is shown on the wrong screen (in a hidden area because of the lower resolution of my 2nd screen) - but this is also not the case. It simply doesn't appear :/ -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 390894] New: KRunner SIGSEV while typing
https://bugs.kde.org/show_bug.cgi?id=390894
Bug ID: 390894
Summary: KRunner SIGSEV while typing
Product: krunner
Version: 5.11.5
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@privat.broulik.de
Reporter: linuxhi...@gmail.com
Target Milestone: ---
https://bugzilla.redhat.com/show_bug.cgi?id=1547909
Thread 1 (Thread 0x7f34f700 (LWP 24472)):
#0 __GI_raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {0, 5568977996435677184, 139865475803720,
139867602828227, 1, 139867518599894, 206158430240, 139865609984400,
139865609984192, 5568977996435677184, 1256, 0, 0, 0, 0, 0}}
pid =
tid =
#1 0x7f3576c841df in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kf5-kcrash-5.42.0-1.fc27.x86_64/src/kcrash.cpp:432
argv = {0x0 }
i =
platformName = {d = 0x0}
about =
sigtxt = "\000\000\000\000\000\000\000\000\000"
pidtxt = '\000'
startupId = {d = 0x0}
crashRecursionCounter = 2
#2
No locals.
#3 tcache_get (tc_idx=) at malloc.c:2943
e = 0x
#4 __GI___libc_malloc (bytes=24) at malloc.c:3044
ar_ptr =
victim =
hook =
#5 0x7f35728d554c in QListData::detach (this=0x7f34e110, alloc=1) at
tools/qlist.cpp:120
x = 0x7f3572ad52e0
t =
#6 0x7f35729ba745 in QList::detach_helper
(alloc=, this=0x7f34e110) at
../../include/QtCore/../../src/corelib/tools/qlist.h:786
x =
#7 QList::reserve (alloc=, this=0x7f34e110)
at ../../include/QtCore/../../src/corelib/tools/qlist.h:572
No locals.
#8 QHash >::keys
(this=this@entry=0x7f34f800a728) at
../../include/QtCore/../../src/corelib/tools/qhash.h:655
res = { = {}, {p =
{static shared_null = {ref = {atomic = {_q_value = { =
{static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}},
alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f3572ad52e0
}, d = 0x7f3572ad52e0 }}
i =
#9 0x7f35729ba092 in QFSFileEnginePrivate::unmapAll
(this=this@entry=0x7f34f800a6b0) at io/qfsfileengine.cpp:467
keys = { = {}, {p
= {static shared_null = {ref = {atomic = {_q_value = {
= {static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}},
alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f3572ad52e0
}, d = 0x7f3572ad52e0 }}
#10 0x7f35729ba140 in QFSFileEngine::~QFSFileEngine (this=0x7f34f8005030,
__in_chrg=) at io/qfsfileengine.cpp:180
d = 0x7f34f800a6b0
#11 0x7f35729ba189 in QFSFileEngine::~QFSFileEngine (this=0x7f34f8005030,
__in_chrg=) at io/qfsfileengine.cpp:181
No locals.
#12 0x7f3572975a80 in QFileDevicePrivate::~QFileDevicePrivate
(this=0x7f34f80070d0, __in_chrg=) at io/qfiledevice.cpp:65
No locals.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 390858] Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 --- Comment #1 from Clemens Eisserer <linuxhi...@gmail.com> --- It were these kinds of bugs that made me leave KDE back in the 4x days, now after 6 years using XFCE it is sad to see quality hasn't improved that much. I've already filed a dozen of crash reports via Fedora automatic bug reporter, since I started using it a month a go. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] New: Application starter sometimes doesn't appear anymore
https://bugs.kde.org/show_bug.cgi?id=390858 Bug ID: 390858 Summary: Application starter sometimes doesn't appear anymore Product: plasmashell Version: 5.11.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: linuxhi...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 >From time to time, the application launcher does no longer open when I left-click on it - until I logout & login again: https://youtu.be/Uc0VJjPZmyY I have a dual-monitor setup, running Fedora 27 on an AMD kaveri based system (7650k). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Clemens Eisserer <linuxhi...@gmail.com> changed: What|Removed |Added CC||linuxhi...@gmail.com --- Comment #32 from Clemens Eisserer <linuxhi...@gmail.com> --- +1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 348521] Dolphin is a little bit slow to startup
https://bugs.kde.org/show_bug.cgi?id=348521 Clemens Eisserer <linuxhi...@gmail.com> changed: What|Removed |Added CC||linuxhi...@gmail.com --- Comment #24 from Clemens Eisserer <linuxhi...@gmail.com> --- I experience the same - Dolphin needs 1-2s to load on my 4Ghz Quad Core equipped with an SSD - and this is not caused by I/O, as subsequent starts are also slow. Other file managers open almost instantly, I hope Dolphin can be brought to the same speed. Unbelievable Dolphin was once promoted as light-weight alternative to konqueror, -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 379187] PHP class generation from code fails
https://bugs.kde.org/show_bug.cgi?id=379187 --- Comment #2 from Clemens John <clemens.j...@floh.de> --- Hi Ralph, thanks for your reply. You are right the file https://bugs.kde.org/attachment.cgi?id=105183 was not generated using Umbrello. It was created manually by me. Maybe there is a misunderstanding so I'll try to clarify what I'm trying to do to make shure we are talking about the same topic. I'm trying to reverse engineer php files containing php classes manually created by me to automatically have them available as UML classes in Umbrello. In most cases there will be imports (use statements) of classes which are not directly available to Umbrello but reverse engineering should work nevertheless. During my research I found the Pear PHP_UML package [1] which generates an *.xmi file I can open using Umbrello using the following command: phpuml ./packages/timetracker/base/src/Models/Hour.php -o ./test.xmi This works quite well as a workaround and I think this is what the "Code Importing Wizard" should do out of the box if PHP is selected as language. [1] https://pear.php.net/manual/en/package.php.php-uml.php Best whises Clemens -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 379187] New: PHP class generation from code fails
https://bugs.kde.org/show_bug.cgi?id=379187 Bug ID: 379187 Summary: PHP class generation from code fails Product: umbrello Version: 2.21.3 (KDE Applications 16.12.3) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: clemens.j...@floh.de Target Milestone: --- Created attachment 105183 --> https://bugs.kde.org/attachment.cgi?id=105183=edit Example of PHP file from which generating an UML class fails. Hi, I am using the latest Umbrello version 2.22.0 on Archlinux. I'm trying to generate an UML class from PHP code (PHP5 compatible) but it fails with various errors in the log complaining about the code syntax. The only thing I will get is a "file"-entity in the components view but there should be a "class"-entity in the logical view I think. Generating UML classes from java source works as expected. I'll attach you an example of the failing file so you can try yourself. Best whishes Clemens -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 379003] Wallpaper "Picture of the Day" from National Geographics only changing after reboot or not at all.
https://bugs.kde.org/show_bug.cgi?id=379003 Clemens <em...@clemens-karner.eu> changed: What|Removed |Added CC||em...@clemens-karner.eu --- Comment #3 from Clemens <em...@clemens-karner.eu> --- In my case, it does not work at all. Even after I reboot, the picture is not available. Plasma Version 5.9.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'
https://bugs.kde.org/show_bug.cgi?id=368350 Clemens <em...@clemens-karner.eu> changed: What|Removed |Added CC||em...@clemens-karner.eu --- Comment #4 from Clemens <em...@clemens-karner.eu> --- Same issue on Kubuntu 17.04 using Kmail 5.2.3 This is bug is a deal breaker for me. It's the only reason I use Thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 Clemens <em...@clemens-karner.eu> changed: What|Removed |Added CC||em...@clemens-karner.eu --- Comment #8 from Clemens <em...@clemens-karner.eu> --- I get the same error on Kubuntu 16.10. Each time I press logout or shutdown, ksmserver crashes. Please confirm this bug. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 374530] Crash when adding message to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=374530 --- Comment #12 from Clemens John <clemens.j...@floh.de> --- I just want to leave some feedback, that the bug is fixed for me in Version 2.21.1. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 374530] Crash when adding message to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=374530 --- Comment #2 from Clemens John <clemens.j...@floh.de> --- I recompiled umbrello including debug symbols and gdb shows the following: +++ umbrello: "Create widget : new_class" [ 2 ] umbrello: Modified file= "Untitled" umbrello: Object_Factory::createUMLObject( "" ): parentPkg is not set, assuming Model_Type "Logical" umbrello: "Create UML object : new_class_1" [ 3 ] umbrello: Modified file= "Untitled" umbrello: scene= "sequence diagram" / object= "new_class_1" umbrello: Modified file= "Untitled" umbrello: "Create widget : new_class_1" [ 3 ] umbrello: Modified file= "Untitled" umbrello: virtual void ToolBarStateMessages::setCurrentElement() Object detected umbrello: virtual void ToolBarStateMessages::setCurrentElement() Object detected Thread 1 "umbrello" received signal SIGSEGV, Segmentation fault. __cxxabiv1::__dynamic_cast (src_ptr=0x0, src_type=0xb304a0 , dst_type=0xb30630 , src2dst=0) at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/dyncast.cc:50 50 /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/dyncast.cc: Datei oder Verzeichnis nicht gefunden. (gdb) +++ I hope this helps. If you need any further information please let me know! -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 374530] New: Crash when adding message to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=374530 Bug ID: 374530 Summary: Crash when adding message to sequence diagram Product: umbrello Version: 2.21.0 (KDE Applications 16.12.0) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: clemens.j...@floh.de Target Milestone: --- Umbrello crashes (segmentation fault) when adding a message to a sequence diagram. Using Archlinux. Steps to reproduce: * Open Umbrello * Add new logical view of type "Sequence diagram" * Add two objects * Add a message between both objects (doesnt matter if sync. or async.) * Crash occurs when clicking on the second lifeline -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]
https://bugs.kde.org/show_bug.cgi?id=370516 --- Comment #25 from Clemens John <clemens-j...@gmx.de> --- Hi, I updated to Plasma 5.3 on Archlinux today and can confirm that the bug is fixed. Thank you :) Best whishes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]
https://bugs.kde.org/show_bug.cgi?id=370516 Clemens John <clemens-j...@gmx.de> changed: What|Removed |Added CC| |clemens-j...@gmx.de --- Comment #1 from Clemens John <clemens-j...@gmx.de> --- Hi, I updated this morning to Plasma 5.8.1 on Archlinux too and I see the same behaviour. I deleted all plasma and activities related config files from ~./config and then the desktop starts without failures. But when adding the activity pager to the desktop or to the system panel plasma immidiately crashes. If you need any log please send me a note. Best whishes -- You are receiving this mail because: You are watching all bug changes.
