[kontact] [Bug 372319] New: Move an email to an event
https://bugs.kde.org/show_bug.cgi?id=372319 Bug ID: 372319 Summary: Move an email to an event Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Creating an event in my calendar based on an email I just received - Custom settings of the application: Many email accounts The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd14fc0c7c0 (LWP 3145))] Thread 30 (Thread 0x7fd076791700 (LWP 12733)): #0 0x7fff6aecdb26 in clock_gettime () #1 0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fd14d20d7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd14d38eb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1453ab4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fd1453abd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fd1453abf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fd14d38ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fd14d335d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fd14d15c32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fd14c85302d in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fd08b7fe700 (LWP 11234)): #0 0x7fff6aecdb26 in clock_gettime () #1 0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fd14d20d7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd14d38eb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1453ab4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fd1453abd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fd1453abf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fd14d38ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fd14d335d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fd14d15c32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fd14c85302d in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fd08bfff700 (LWP 11229)): #0 0x7fff6aecdb26 in clock_gettime () #1 0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fd14d20d7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd14d38eb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1453ab4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fd1453abd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fd1453abf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fd14d38ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fd14d335d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fd14d15c32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fd14c85302d in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7fd091687700 (LWP 11227)): #0 0x7fff6aecdb26 in clock_gettime () #1 0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fd14d20d7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd14d38eb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1453ab4ad in g_main_context_prepare () at /usr/lib64
[kontact] [Bug 373230] New: overloaded with options
https://bugs.kde.org/show_bug.cgi?id=373230 Bug ID: 373230 Summary: overloaded with options Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Starting the program - Custom settings of the application: Many-many firlters, for about 10 email account (12 profiles + xxx alias in 8 email account) Filters doesn't work anymore, and I gave up even trying to set it up again-again-agian Spam filter never worked, I gave up trying Sorting and labelling email never worked, I gave up The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5d3b8557c0 (LWP 1887))] Thread 22 (Thread 0x7f5c857fa700 (LWP 2398)): #0 0x7f5d31036d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f5d30ff4538 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5d30ff4d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5d30ff4f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f5d38fd7d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5d38f7ed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f5d38da061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f5d38da532f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f5d318120a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f5d3849c02d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f5c867fc700 (LWP 2395)): #0 0x7ffd3455eb26 in clock_gettime () #1 0x7f5d384a8c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f5d38e567d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f5d38fd63b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f5d38fd6945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5d38fd7b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f5d30ff44ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f5d30ff4d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f5d30ff4f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f5d38fd7d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f5d38f7ed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f5d38da061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f5d38da532f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f5d318120a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f5d3849c02d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f5c86ffd700 (LWP 2394)): #0 0x7ffd3455eb26 in clock_gettime () #1 0x7f5d384a8c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f5d38e567d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f5d38fd63b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f5d38fd6945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5d38fd7b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f5d30ff44ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f5d30ff4d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f5d30ff4f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f5d38fd7d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f5d38f7ed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f5d38da061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f5d38da532f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f5d318120a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f5d3849c02d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f5c877fe700 (LWP 2390)): #0 0x7ffd3455eb26 in clock_gettime () #1 0x7f5d384a8c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f5d38e567d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f5d38fd63b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f5d38fd6945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5d38fd7b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f5d30ff44ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f5d30ff4d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f5d30ff4f7c in g_main_context_iteration () at /usr/lib64/li
[kate] [Bug 454594] New: Settings->Configure Kate Crashes
https://bugs.kde.org/show_bug.cgi?id=454594 Bug ID: 454594 Summary: Settings->Configure Kate Crashes Product: kate Version: 22.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: eric.justin.al...@gmail.com Target Milestone: --- Application: kate (22.04.1) Qt Version: 5.15.2 Frameworks Version: 5.94.0 Operating System: Linux 5.17.9-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I clicked Settings then I clicked Configure Kate and the program crashed. I also tried the shortcut ctrl+shift+, and that also crashed with seg fault. Is there a fix for this bug I read previous bug reports that wer simular, one said fixed but I didn't see how to fix the bug on that report, I updated kate and it is still crashing with the same action. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7f4004db268a in QMapData::root (this=0xf66306b8840fffe) at /usr/include/qt5/QtCore/qmap.h:208 #5 QMapData::findNode (this=0xf66306b8840fffe, akey=...) at /usr/include/qt5/QtCore/qmap.h:287 #6 0x7f4004dd8a66 in QMap::constFind (akey=..., this=0x7f3ffd6c1b70) at /usr/include/qt5/QtCore/qmap.h:852 #7 KEntryMap::constFindEntry(QByteArray const&, QByteArray const&, QFlags) const [clone .isra.0] (this=this@entry=0x7f3ffd6c1b70, key=..., flags=..., flags@entry=..., group=...) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfigdata.cpp:60 #8 0x7f4004db20ee in KEntryMap::getEntry (group=..., expand=0x7fffe6c79b17, flags=..., defaultValue=..., key=..., this=0x7f3ffd6c1b70) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfigdata.cpp:217 #9 KConfigPrivate::lookupData (this=0x7f3ffd6c1b50, group=..., key=, flags=..., expand=0x7fffe6c79b17) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfig.cpp:1061 #10 0x7f4004dbe7a1 in KConfigGroup::readEntry (this=this@entry=0x557a26f16530, key=key@entry=0x7f3ffe1d7f7b "View Style", aDefault=...) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfiggroup.cpp:674 #11 0x7f4004dbe9bb in KConfigGroup::readEntry (this=this@entry=0x557a26f16530, key=key@entry=0x7f3ffe1d7f7b "View Style", aDefault=aDefault@entry=0x7f3ffe1d7f70 "DetailTree") at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfiggroup.cpp:659 #12 0x7f3ffe171d5e in KDirOperator::readConfig (this=0x557a27f336d0, configGroup=...) at /usr/src/debug/kio-5.94.0-1.1.x86_64/src/filewidgets/kdiroperator.cpp:2436 #13 0x7f3ffc992300 in KateFileBrowser::readSessionConfig (this=0x557a27eed3a0, cg=...) at /usr/src/debug/kate-22.04.1-1.1.x86_64/addons/filebrowser/katefilebrowser.cpp:160 #14 0x7f3ffc995a98 in KateFileBrowserPluginView::createFileBrowser (this=0x557a26c7a710, visible=) at /usr/include/c++/12/bits/unique_ptr.h:191 #15 0x7f3ffc996655 in KateFileBrowserPluginView::createFileBrowser (visible=true, this=) at /usr/include/qt5/QtCore/qlist.h:117 #16 KateFileBrowserPlugin::configPage (this=0x557a26b140a0, number=, parent=0x557a27800030) at /usr/src/debug/kate-22.04.1-1.1.x86_64/addons/filebrowser/katefilebrowserplugin.cpp:56 #17 0x557a2662954f in KateConfigDialog::addPluginPage (this=0x557a27800030, plugin=0x557a26b140a0) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/kateconfigdialog.cpp:306 #18 0x557a265e6622 in KateConfigDialog::addPluginPages (this=0x557a27800030) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/kateconfigdialog.cpp:286 #19 KateConfigDialog::KateConfigDialog (parent=, this=) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/kateconfigdialog.cpp:63 #20 KateMainWindow::showPluginConfigPage (this=, configpageinterface=, id=) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/katemainwindow.cpp:905 #21 0x7f400387ce1c in doActivate (sender=0x557a26c949b0, signal_index=4, argv=0x7fffe6c7a090) at kernel/qobject.cpp:3898 #22 0x7f40038760cf in QMetaObject::activate (sender=sender@entry=0x557a26c949b0, m=m@entry=0x7f4004941d40, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffe6c7a090) at kernel/qobject.cpp:3946 #23 0x7f4004426b62 in QAction::triggered (this=this@entry=0x557a26c949b0, _t1=) at .moc/moc_qaction.cpp:376 #24 0x7f40044297ab in QAction::activate (this=0x557a26c949b0, event=) at kernel/qaction.cpp:1161 #25 0x7f400442a37d in QAction::event (e=, this=) at kernel/qaction.cpp:1086 #26 QAction::event (this=, e=) at kernel/qaction.cpp:1075 #27 0x7f400442d37e in QApplicationPrivate::notify_helper (this=, receiver=0x557a26c949b0, e=0x7fffe6c7a230) at kernel/qapplication.cpp:3632 #28 0x7f4003845988 in QCoreApplication::notifyInternal2 (receiver=0x5
[kate] [Bug 454594] Settings->Configure Kate Crashes
https://bugs.kde.org/show_bug.cgi?id=454594 --- Comment #3 from Eric --- (In reply to Waqar Ahmed from comment #2) > > *** This bug has been marked as a duplicate of bug 453234 *** Hey thanks sorry about the confusion i see the fixes now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467716] New: Application Launcher widget should have a fixed height on vertical panels (regression)
https://bugs.kde.org/show_bug.cgi?id=467716 Bug ID: 467716 Summary: Application Launcher widget should have a fixed height on vertical panels (regression) Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: openSUSE OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: m...@ericvanblokland.nl CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 With a vertical panel, the Application Launcher widget icon/button scales its height 1:1 with the panel width. Previously that height was fixed, preventing a Fisher-Price style button. Observed in openSuse Tumbleweed since a few months, still occurring with latest updates. Previous reports: https://bugs.kde.org/show_bug.cgi?id=378443 https://bugs.kde.org/show_bug.cgi?id=395594 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466566] Kickoff button too large with super thick panel
https://bugs.kde.org/show_bug.cgi?id=466566 --- Comment #8 from Eric --- Sorry for the duplicate, for some reason my search did not turn up with this one. I was probably searching for open issues. (In reply to Nate Graham from comment #2) > Sorry, this is the new design goal, as making some buttons mysteriously > remain rectangles for no clear reason confused the heck out of a lot of > people and we go no end of bug reports about it. I would really like you to reconsider this new design goal. As it confused the heck out of me why that button became so large. (In reply to Nate Graham from comment #5) > Fortunately most people don't use enormously thick panels so hopefully the > impact will be limited. But yet, if this is wrong and a lot of people have > this configuration and complain about it, we can consider making the new > sizing optional. > There are several of us out there that use vertical panels, at least 3. If we're talking user expectations, users would expect one of the following, in order of most likely behavior: 1. The same height as Task Manager (icons). This is the behavior users are used to in a variety of desktop environments. 2. Some arbitrary height that looks good. 3. The height of the icon that is used for that widget. (I know, good luck with vectors, but hey, it is user expectation) 4. I don't think there is a 4th expectation for this particular widget. Just kidding, I guess it actually makes a lot of sense for horizontal panels. However, I suspect the widget would become rather small on slim horizontal panels. For me any default behavior chosen is a not really an issue, as long as I can change it. So a toggle would be nice, a toggle and an input where I can specify the desired size (width for horizontal, height for vertical) or scale would be better. > Relatedly, this is the downside of our data-poor and off-by-default > telemetry; we don't know this kind of thing until people complain about it! Never change. The least we as users can do is give some constructive feedback. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468168] New: Erratic behavior shift+click task to start new application instance
https://bugs.kde.org/show_bug.cgi?id=468168 Bug ID: 468168 Summary: Erratic behavior shift+click task to start new application instance Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: m...@ericvanblokland.nl Target Milestone: 1.0 SUMMARY I am used to click on a task holding down the shift key in the task manager to start a new instance of an application. Since a few months (probably started when I was switched to Wayland by default) the results are unpredictable. For a while it wil just work, then suddenly after I have opened a new task this way, I can no longer switch tasks by clicking on applications in the task manager because a new instance of an application gets started as if I were holding down the shift key. After (shift) clicking around a bit, task switching may become possible again, but shift-clicking to start a new application instance stops working altogether. I have observed that some more clicking can eventually restore normal behavior. STEPS TO REPRODUCE 1. Some arbitrary combination of clicking and shift-clicking tasks in the task manager. (I just realized it might have something to do with whether or not I click on the icon of the task, but I'm not near that machine right now so I can't test. I will update this report if I find more reliable steps to reproduce) OBSERVED RESULT Task switching by clicking a task becomes impossible, a new instance keeps getting launched. - or - Launching a new application instance by holding shift doesn't work anymore. EXPECTED RESULT - Reliably switch task by clicking it. - Reliably start a new application instance by holding down shift and clicking a task. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.27.3 KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468168] Erratic behavior shift+click task to start new application instance
https://bugs.kde.org/show_bug.cgi?id=468168 --- Comment #2 from Eric --- (In reply to Nate Graham from comment #1) > Interesting; looks like there's a hidden feature for this. I had no idea. I > can confirm it's broken-ish on Wayland. Code is in tools.js, line 100. > > JFYI another method of doing this is to middle-click on a task, which is > supported and exposed in the config window as an option. Thanks for having a look so quickly. I'm aware of the middle-click option, but I've never been able to get used to that input method. With some mice I use hitting middle without scrolling is almost impossible (good luck using that for pasting) and/or it's uncomfortable because my hands are rather big. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466566] Kickoff button too large with super thick panel
https://bugs.kde.org/show_bug.cgi?id=466566 --- Comment #11 from Eric --- (In reply to Ismael Asensio from comment #10) > > 2. Add per-widget settings for 1st-party widgets to control the maximum icon > > size as needed. For some reason people only ever seem to complain about this > > issue as it applies to their launcher menu widgets, so maybe it will be > > enough to do this for Kickoff, Kicker, and Application Dashboard. Cons: lots > > of code duplication if we end up implementing it for multiple widgets; worse > > UX if you want to make this change for all the affected widgets on your > > panel; universality would still be elusive since 3rd-party widgets have to > > implement the same code. > > We might explore this solution, a "per-applet size setting", but implemented > as a sizing handle on the panel edit mode (not as a specific configuration > the applet has to provide). If only, some properties or hints would be > required for the applets to "opt-in". That would be similar to what we do > now with applet pop-ups resizing. > > It would act as a Layout.Preferred/Maximum size, and potentially also solve > the sizing problem with two full-width competing widgets on the same panel > (ex. Menubar + Taskmanager). > > Ideally it should be useful but not overwhelming, that is, defaults should > still suffice for the majority of the cases. This solution would be the Rolls Royce in my opinion. Actually, one of the first things I checked for when I was confronted with my new Kickoff button was whether I was allowed to resize it in edit mode by dragging its edge. So there is at least some intuitivity with this. Implementing this could also benefit other widgets. For me it would be a "nice to have" if I could increase the size of "Pager" as an example. (don't consider this a feature request, I'm just brainstorming) While consistency is important, it might be worth considering this as a preferred size instead of a maximum. If we look at the "System Tray" for example, it would be a "nice to have" if it could be set as a minimum size. Here's why: it has happened several times to me that my Task Manger is "pixels away" from scaling down. Then I'm in a browser tab that starts playing media and the System Tray expands its size because of that extra icon. This causes the Task Manager to scale down and up again. Since the number of System Tray items is rather constant for me, just reserving space for those one or two extra icons would be nice. (again, not a feature request, just brainstorming) In the end I think everyone would benefit, if I were to put my launcher on a horizontal panel again I would appreciate that I could make the "clickable surface" wider than my panel height. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437210] Removed and then restored Plasma panel is positioned in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=437210 Eric changed: What|Removed |Added CC||m...@ericvanblokland.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466566] Kickoff button too large with super thick panel
https://bugs.kde.org/show_bug.cgi?id=466566 --- Comment #13 from Eric --- (In reply to Nate Graham from comment #12) > Yes, that does sound like a good solution that would solve other problems as > well. Re-opening. I'm very glad to hear that. I've been thinking about how this feature could work. I don't use a lot of different widgets so I may be overlooking some use cases but I have a suggestion on how this could work, generalized: 1. There must be some sane minimum size (width for horizontal panels, height for vertical panels) so you can't make a widget disappear. 2. Widgets should probably be able to specify their own minimum size, I guess based on some scale against the other axis. 3. Widgets might want to specify a default size, again based on some scale, larger than their minimum, but some "sane" size to match user expectation/design goals. 4. Widgets might want to specify a maximum size if scaling beyond a certain ratio doesn't make sense or isn't supported. 5. Widgets should be allowed to grow beyond their minimum size (either their advertised minimum size or the user specified minimum size), see my System Tray example above. 6. Depending on how well this all works in general (how well do most widgets handle/scale with the extra surface area) widgets should be able to either opt-in or opt-out of this feature. To me it seems a minimum size is the way to go, but maybe someone else could come up with an example where a "user specified maximum" size would be preferred. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484103] New: Play to Zone end from Cursor
https://bugs.kde.org/show_bug.cgi?id=484103 Bug ID: 484103 Summary: Play to Zone end from Cursor Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: vink.e...@gmail.com Target Milestone: --- To start with, I am really happy with Kdenlive! Thank you so much! There is one tiny feature (but important to me) I really miss, and that is to play from cursor to Zone End, or play e.g. the last second before Zone End. Especially if the clip or zone gets larger it is really a bore to use Play Zone (CTRL + SPACE) if one is trying to get the timing of the Zone Out point right! In case of the Zone In point one can use Play Zone and immediately Pause it, but I found no possibility to play to Zone Out and/or set a shortcut for it. I would really appreciate the effort. Kind regards, Eric Vink. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Eric changed: What|Removed |Added CC||majzo...@umsl.edu Platform|Other |Ubuntu Packages --- Comment #60 from Eric --- +1 My mouse is a logitech bluetooth mouse. Kubuntu 22.04 KDE Plasma version 5.24.4 KDE Framework: 5.92.0 X11 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442166] New: wipe effect not applied when rendering in windows
https://bugs.kde.org/show_bug.cgi?id=442166 Bug ID: 442166 Summary: wipe effect not applied when rendering in windows Product: kdenlive Version: 21.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: e...@loquiz.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. create a project 2. add two videos overlapping 3. add wipe effect OBSERVED RESULT wipe effect shows inside KDE, but after rendering with MP4-H264 profile it does not show wipe effect. Issue appears in 21.08.0 and 21.08.1 windows versions both standalone and installed. It works correctly on 21.04 version EXPECTED RESULT wipe effect added to rendered outcome as well. SOFTWARE/OS VERSIONS Windows: 10 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.
[kdenlive] [Bug 442166] wipe effect not applied when rendering in windows
https://bugs.kde.org/show_bug.cgi?id=442166 --- Comment #2 from e...@loquiz.com --- Hi, thanks for the comment. I had updated the app from previous version. uninstalling the app and deleting the directory (just in case) and then installing version 21.08.1 again fixed the issue. So it was a problem with my setup. The issue is fully resolved for me. Thanks and sorry for making noise too early. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417994] Typing boxes stop taking input until next restart
https://bugs.kde.org/show_bug.cgi?id=417994 Eric changed: What|Removed |Added CC||emun...@mgebm.net --- Comment #6 from Eric --- I am having this same issue as well and it started with my update to Ubuntu 20.10. If I kill the ibus applet I loose the ability to send keyboard input to any QT application search box. However GTK applications seem to be fine. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427865] New: kde-init5 crash each time when pc start
https://bugs.kde.org/show_bug.cgi?id=427865 Bug ID: 427865 Summary: kde-init5 crash each time when pc start Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lessarte...@hotmail.com Target Milestone: --- Created attachment 132473 --> https://bugs.kde.org/attachment.cgi?id=132473&action=edit kde-init5 crash each time when pc start SUMMARY kde-init5 crash each time when pc start 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 434892] konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 --- Comment #4 from eric --- I would like to add that I've now installed the debug symbols for a full report. Konsole crashes immediately on opening every single time under both xorg and wayland on my Intel Kaby Lake laptop w/ intel graphics: Application: konsole (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.3 Distribution: "Fedora release 34 (Thirty Four)" -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7f5b7ffb1292 in raise () from /lib64/libc.so.6 #5 0x7f5b7ff9a8a4 in abort () from /lib64/libc.so.6 #6 0x7f5b7fe72c78 in std::__replacement_assert (__file=, __line=, __function=, __condition=) at /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2648 #7 0x7f5b7ff1548f in std::piecewise_linear_distribution::param_type::_M_initialize (this=0x7ffee1fdec90) at /usr/include/c++/11/bits/random.tcc:3055 #8 0x7f5b7ff1c5af in std::piecewise_linear_distribution::piecewise_linear_distribution > (__fw=..., __bl=..., this=0x7ffee1fdec90) at /usr/include/c++/11/bits/random.h:5867 #9 Konsole::ColorScheme::colorEntry (this=0x7ffee1fdec90, index=, randomSeed=3791514576) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/colorscheme/ColorScheme.cpp:322 #10 0x7f5b7fecea29 in Konsole::ColorScheme::getColorTable (randomSeed=209784833, table=0x7ffee1fe0150, this=0x55f018787b90) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/colorscheme/ColorScheme.cpp:339 #11 Konsole::TerminalDisplay::applyProfile (this=0x55f01871baa0, profile=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/terminalDisplay/TerminalDisplay.cpp:3118 #12 0x7f5b7fe8633b in Konsole::ViewManager::applyProfileToView (this=0x55f01849efb0, view=0x55f01871baa0, profile=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/ViewManager.cpp:832 #13 0x7f5b7fe8e84b in Konsole::ViewManager::createView (this=0x55f01849efb0, session=session@entry=0x55f018521070) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/ViewManager.cpp:675 #14 0x7f5b8074d82e in Konsole::MainWindow::createSession (this=this@entry=0x55f0184539e0, profile=..., directory=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/MainWindow.cpp:512 #15 0x7f5b80753a64 in Konsole::Application::newInstance (this=0x7ffee1fe0730) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/Application.cpp:235 #16 0x7f5b8075e918 in kdemain (argc=, argv=) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/main.cpp:235 #17 0x7f5b7ff9bb75 in __libc_start_main () from /lib64/libc.so.6 #18 0x55f017bb136e in _start () [Inferior 1 (process 204868) detached] Report to https://bugs.kde.org/ (In reply to tcanabrava from comment #1) > Created attachment 137035 [details] > attachment-11681-0.html > > we are missing important information from your backtrace, can you install > the debug symbols? > > > On Wed, Mar 24, 2021 at 4:18 PM guy wrote: > > > https://bugs.kde.org/show_bug.cgi?id=434892 > > > > Bug ID: 434892 > >Summary: konsole crash when open > >Product: konsole > >Version: 20.12.2 > > Platform: Fedora RPMs > > OS: Linux > > Status: REPORTED > > Keywords: drkonqi > > Severity: crash > > Priority: NOR > > Component: general > > Assignee: konsole-de...@kde.org > > Reporter: guy.car...@gmail.com > > Target Milestone: --- > > > > Application: konsole (20.12.2) > > > > Qt Version: 5.15.2 > > Frameworks Version: 5.80.0 > > Operating System: Linux 5.11.8-300.fc34.x86_64 x86_64 > > Windowing System: X11 > > Drkonqi Version: 5.21.3 > > Distribution: Fedora 34 (KDE Plasma Prerelease) > > > > -- Information about the crash: > > - What I was doing when the application crashed: > > > > After I've upgrade frm F33 to F34 beta consloe crash when try to start it. > > > > The crash can be reproduced every time. > > > > -- Backtrace: > > Application: Konsole (konsole), signal: Aborted > > > > [KCrash Handler] > > #4 0x7f12bba2e292 in raise () from /lib64/libc.so.6 > > #5 0x7f12bba178a4 in abort () from /lib64/libc.so.6 > > #6 0x7f12bb8efc78 in std::__replacement_assert(char const*, int, char > > const*, char const*) () from /lib64/libkonsoleprivate.so.20 > > #7 0x7f12bb99248f in > > std::piecewise_linear_distribution::param_type::_M_initialize() () > > from > > /lib64/libkonsoleprivate.so.20 > > #8 0x7f12bb9995af in Konsole::ColorScheme::colorEntry(in
[konsole] [Bug 434892] konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 --- Comment #5 from eric --- Ok I have tried deleting my ~/.config/konsolerc and now konsole opens just fine. I believe the issue was my default konsole profile had the setting to "randomly adjust colors for each session" under Edit Color Scheme. If I create a new profile in konsole settings and use "randomly adjust colors" then set it as default it causes the same crash behavior. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 427865] kde-init5 crash in ThumbnailProtocol::get() each time when pc start
https://bugs.kde.org/show_bug.cgi?id=427865 Eric changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Eric --- After reinstall, i think the bugs is when i raise the resolution 100x to 300x (hidpi) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 427865] kde-init5 crash in ThumbnailProtocol::get() each time when pc start
https://bugs.kde.org/show_bug.cgi?id=427865 Eric changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Eric --- KDE Frameworks 5.75.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Eric changed: What|Removed |Added CC||majzo...@umsl.edu --- Comment #56 from Eric --- Are there any reasonable workarounds? Say a script that reads all window positions, sizes, etc., and saves the information, and then another script that can read this info and open and arrange the windows? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #59 from Eric --- According to the plasma/wayland showstoppers page, session restore is a priority: https://community.kde.org/Plasma/Wayland_Showstoppers However, on the plasma 6 development page there is no mention of session restore: https://community.kde.org/Plasma/Plasma_6 Does anyone know if session restore is supposed to be in plasma 6? -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 Eric changed: What|Removed |Added CC||majzo...@umsl.edu --- Comment #3 from Eric --- Created attachment 160290 --> https://bugs.kde.org/attachment.cgi?id=160290&action=edit strace output for rkward crash This is the strace output for rkward when it crashes at start. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 Eric changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Eric --- (In reply to Eric from comment #3) > Created attachment 160290 [details] > strace output for rkward crash > > This is the strace output for rkward when it crashes at start. Not sure what happened to the rest of my comment, it disappeared after I added the attachment. I'm on Fedora 38. I built version 0.7.5 from the tarball, and also tried building from git. In both cases it is crashing on startup with an error about the R backend: Connection closed unexpectedly. Last error was: QLocalSocket: Remote closed The R backend will be shut down immediately. This means, you can not use any more functions that rely on it. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 --- Comment #6 from Eric --- Thank you for the instructions. My system is stock Fedora 38 with R version 4.3.1. The version of rkward shipped with F38 is 0.7.4 and it works fine. Running rkward version 0.7.5 with --debug-level 5 shows an error in the output of /tmp/rkward.rbackend: ... ... lots of stuff here that seems fine ... Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackendprotocol_shared.cpp - function ~RBackendRequest line 42 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrsupport.cpp - function environmentFor line 289 creating new shadow environment for 0x9f94d8 Assert 'Rf_isEnvironment(shadowenvbase)' failed at /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrsupport.cpp - function environmentFor line 301 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackend.cpp - function RWriteConsoleEx line 454 raw output type 1, size 51: Error: argument to 'findVar' is not an environment Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackendprotocol_shared.cpp - function handleOutput line 166 Output type 2: Error: argument to 'findVar' is not an environment Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackend.cpp - function doSimpleBackendCall line 968 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrsupport.cpp - function SEXPToStringList line 82 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackend.cpp - function doError line 906 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackendprotocol_shared.cpp - function handleOutput line 166 Output type 3: Error: argument to 'findVar' is not an environment error 'Error: argument to 'findVar' is not an environment Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackend.cpp - function tryToDoEmergencySave line 603 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackend.cpp - function RCleanUp line 536 Created emergency save file in /home/ehm/.rkward/rkward_recover0.RData Cleanup finished Main loop finished Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkbackendtransmitter.cpp - function doExit line 75 Aborting connection to frontend Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rktransmitter.cpp - function disconnected line 270 Trace: /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrbackend.cpp - function tryToDoEmergencySave line 603 Assert 'false' failed at /home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rksignalsupport.cpp - function signal_proxy line 98 -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926
--- Comment #8 from Eric ---
The file is over 20MB so I can't send it. You were right though, there were
errors in there about 0.7.5 not being the correct version it finds. So to
simplify things I uninstalled 0.7.4 from the system and ran 0.7.5 again. Both
the frontend and rbackend files are very small now, but there is still a crash
of the R backend. Here is the output.
$ cat /tmp/rkward.frontend
resource.ver not found. Data path(s):
/home/ehm/.local/share/rkward:/home/ehm/.local/share/flatpak/exports/share/rkward:/var/lib/flatpak/exports/share/rkward:/usr/local/share/rkward:/usr/share/rkward
Assert 'QFileInfo::exists(source)' failed at
/home/packages/SOURCE/rkward-0.7.5/rkward/rkward.cpp - function startR line 386
Assert 'QFile::copy(source, package)' failed at
/home/packages/SOURCE/rkward-0.7.5/rkward/rkward.cpp - function startR line 388
Assert 'QFileInfo::exists(source)' failed at
/home/packages/SOURCE/rkward-0.7.5/rkward/rkward.cpp - function startR line 386
Assert 'QFile::copy(source, package)' failed at
/home/packages/SOURCE/rkward-0.7.5/rkward/rkward.cpp - function startR line 388
R syntax highlighting definition ('R interactive session')not found!
QMetaObject::invokeMethod: No such method
KatePluginIntegrationWindow::createViewBar(KTextEditor::View*)
Command failed (other)
failed command was 0: 'R Startup'
- error message was: ''
XML-parsing 'pages//rkward_welcome.rkh' : Could not open file
pages//rkward_welcome.rkh for reading
XML-parsing 'pages//rkward_welcome.rkh' : Error parsing XML-file. Error-message
was: 'unexpected end of file' in line '1', column '1'. Expect further errors to
be reported below
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
The Wayland connection experienced a fatal error: Bad file descriptor
$ cat /tmp/rkward.rbackend
Changing locale
New locale codec is UTF-8
Assert 'Rf_isEnvironment(shadowenvbase)' failed at
/home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rkrsupport.cpp - function
environmentFor line 301
Created emergency save file in /home/ehm/.rkward/rkward_recover0.RData
Assert 'false' failed at
/home/packages/SOURCE/rkward-0.7.5/rkward/rbackend/rksignalsupport.cpp -
function signal_proxy line 98
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 --- Comment #10 from Eric --- Here is my procedure: tar xvf rkward-0.7.5.tar.gz cd rkward-0.7.5 mkdir ehm_build ehm_install cd ehm_build cmake .. -DR_EXECUTABLE=`which R` -DCMAKE_INSTALL_PREFIX=/home/packages/SOURCE/rkward-0.7.5/ehm_install/ make -j8 make install -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 --- Comment #11 from Eric --- I forgot, I start rkward by giving the full path: /home/packages/SOURCE/rkward-0.7.5/ehm_install/bin/rkward -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 --- Comment #13 from Eric --- That works, rkward starts up without error. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 --- Comment #16 from Eric --- Yes, I can confirm this works fine now. I followed the same build procedure in my comment above. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 469926] RKWard doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=469926 --- Comment #17 from Eric --- (In reply to Eric from comment #16) > Yes, I can confirm this works fine now. I followed the same build procedure > in my comment above. Except, from git master, of course. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461996] displayed aspect ratio changes when switching monitors?
https://bugs.kde.org/show_bug.cgi?id=461996 --- Comment #2 from Eric --- I get: org.kde.okular.core: Output DPI: QSizeF(338.667, 304.8) The full output is below. What is the meaning of 'request observer'? org.kde.okular.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so" org.kde.okular.core: Output DPI: QSizeF(338.667, 304.8) org.kde.okular.core: request observer=0x55937461aef0 547x637@2 org.kde.okular.core: request observer=0x55937461aef0 547x637@3 org.kde.okular.core: request observer=0x55937461aef0 547x637@4 org.kde.okular.core: sending request observer=0x55937461aef0 547x637@2 async == true isTile == false org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@3 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@4 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@2 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@5 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@1 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@6 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@0 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@7 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2519@8 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2518@9 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@10 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@11 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@12 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@13 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@14 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@3 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@4 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@2 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@5 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@1 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@6 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@0 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@7 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2519@8 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2518@9 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@10 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@11 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@12 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@13 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@14 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@3 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@4 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@2 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@5 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@1 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@6 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@0 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@7 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2519@8 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2518@9 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@10 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@11 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@12 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@13 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@14 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@3 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@4 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@2 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@5 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@1 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@6 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@0 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@7 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2519@8 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2518@9 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@10 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@11 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@12 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@13 org.kde.okular.core: request observer=0x5593745b4aa0 1978x2303@14 org.kde.okular.core: sending request observer=0x5593745b4aa0 1978x2303@3 async == true isTile == false org.kde.okular.core: request observer=0x5593745b4aa0 1957x2279@3 org.kde.okular.core: request observer=0x5593745b4aa0 1957x2279@4 org.kde.okular.core: request observer=0x5593745b4aa0 1957x2279@2 org.kde.okular.core: request observer=0x5593745b4aa0 1957x2279@5 org.kde.okular.core: request obs
[okular] [Bug 461996] displayed aspect ratio changes when switching monitors?
https://bugs.kde.org/show_bug.cgi?id=461996 --- Comment #4 from Eric --- When it does not. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461996] displayed aspect ratio changes when switching monitors?
https://bugs.kde.org/show_bug.cgi?id=461996 --- Comment #5 from Eric --- The way I set up the resolutions on both the laptop and the external monitor is through xrandr: xrandr --output eDP-1 --mode 3840x2160 --output DP-3 --mode 1920x1080 --scale 2x2 These are both 16:9 aspect ratios. However, the physical laptop screen is 16:10. Can Okular be setting the aspect ratio on the physical laptop screen? Note: All other KDE and GNOME pdf reader applications display the aspect ratio fine. It's only Okular that does not. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461996] displayed aspect ratio changes when switching monitors?
https://bugs.kde.org/show_bug.cgi?id=461996 --- Comment #7 from Eric --- This is getting tiresome. Again, the only application that doesn't display PDF aspect ratio properly is Okular. Viewing in evince works fine, even viewing pdfs in emacs works fine. The aspect ratio of my external monitor is 16:9 and I set it to 1920x1080 which is 16:9, so I am not using the incorrect aspect ratio for my monitor. I am not a developer of KDE software and I don't know how Okular tries to determine the aspect ratio so I submitted this as a bug to help the development of Okular, which I like, and to hopefully learn more about how Okular works so that I could help contribute to a solution that may affect other people. Your vapid replies make me question if you even understand how Okular works. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461996] displayed aspect ratio changes when switching monitors?
https://bugs.kde.org/show_bug.cgi?id=461996 --- Comment #9 from Eric --- Yeah, that was funny. :-) But you still haven't answered the question so I must assume that you just don't know. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 425885] New: repeatedly redrawn figure when making scatterplot with gui, leads to crash
https://bugs.kde.org/show_bug.cgi?id=425885
Bug ID: 425885
Summary: repeatedly redrawn figure when making scatterplot with
gui, leads to crash
Product: rkward
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: User Interface
Assignee: rkward-de...@kde.org
Reporter: majzo...@umsl.edu
Target Milestone: ---
Created attachment 131224
--> https://bugs.kde.org/attachment.cgi?id=131224&action=edit
data file needed to observe the behavior
SUMMARY
Selecting scatterplot from the menu and doing the following below gives hard
crash.
STEPS TO REPRODUCE
1. Open R script
2. Run the script
3. Select Plots-->Scatterplot
4. scroll down to data frame ch_wide_2
5. input FISCAL_YEAR three times into "'X' variables"
6. input FS, SP, SS into the 'Y' variables
7. select the 'use wizard' button
8. keep selecting 'next' to get to the preview.
OBSERVED RESULT
The preview window repeatedly redraws the figure and it flashes, and other
things happen.
EXPECTED RESULT
It just makes the plot preview.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.5
kernel 5.7-17-200.fc32.x86_64
KDE Frameworks 5.70.0
Qt 5.14.2 (built against 5.14.2)
The xcb windowing system
ADDITIONAL INFORMATION
I can get it to crash doing this if I keep trying to add things to the plot
like different colors for the different Y variables, etc.
The script file is: (I have been playing with other plotting packages)
library(reshape2)
library(tidyverse)
library(skimr)
library(ggplot2)
library(ggraptR)
library(shiny)
library(ggplotgui)
library(GrapheR)
ch = read.csv("/home/me/Credit_Hour_Counts_data_fixed.csv") # read csv file
#ch[is.na(ch)] <- 0
ch_wide_1 <- dcast(ch, Term ~ FISCAL_YEAR)
ch_wide_1[is.na(ch_wide_1)] <- 0
ch_wide_2 <- dcast(ch, FISCAL_YEAR ~ Term)
ch_wide_2[is.na(ch_wide_2)] <- 0
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 425885] repeatedly redrawn figure when making scatterplot with gui, leads to crash
https://bugs.kde.org/show_bug.cgi?id=425885 --- Comment #1 from Eric --- ... 9. click 'submit' so the figure is placed in the workspace. 10. Click "Run Again" ---> hard crash -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 425885] repeatedly redrawn figure when making scatterplot with gui, leads to crash
https://bugs.kde.org/show_bug.cgi?id=425885 --- Comment #5 from Eric --- Will do! Thank you for the very quick fix. -E -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 208121] incorrect space characters in pdf form
https://bugs.kde.org/show_bug.cgi?id=208121 --- Comment #29 from eric --- (In reply to Justin Zobel from comment #28) > If this bug is no longer persisting or relevant please change the status to > resolved. The problem mentioned in comment #27 has not disappeared. Currently I'm using: okular 1.11.1, kde frameworks 5.74.0 and Qt 5.15.1. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 430680] New: rkward process continues after exiting program
https://bugs.kde.org/show_bug.cgi?id=430680 Bug ID: 430680 Summary: rkward process continues after exiting program Product: rkward Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: majzo...@umsl.edu Target Milestone: --- SUMMARY Built rkward from source (git, as of today. build info below). After starting rkward and exiting the program the rkward process continues and has to be shut down by hand with "kill -HUP". STEPS TO REPRODUCE 1. start rkward 2. quit rkward from either the menu or the close button on the top right of the window OBSERVED RESULT rkward process is still running EXPECTED RESULT rkward exits and there are no processes running SOFTWARE/OS VERSIONS Operating System: Fedora 33 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.2 Kernel Version: 5.9.14-200.fc33.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: AMD CEDAR ---Session Info--- -- Frontend -- RKWard version: 0.7.2z+0.7.3+devel1 KDE Frameworks version (runtime): 5.75.0 KDE Frameworks version (compile time): 5.75.0 Qt version (runtime): 5.15.2 Qt version (compile time): 5.15.2 Using QtWebKit for HTML rendering Local config directory: /home/ehm/.config RKWard storage directory: /home/ehm/.rkward/ Backend version (as known to the frontend): 4.0.3 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend R version (compile time): 4.0.3 (2020-10-10 r79318) R runtime session info: R version 4.0.3 (2020-10-10) Platform: x86_64-redhat-linux-gnu (64-bit) Running under: Fedora 33 (Workstation Edition) Matrix products: default BLAS/LAPACK: /usr/lib64/libflexiblas.so.3.0 locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 [9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8 [11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] rkward_0.7.3 loaded via a namespace (and not attached): [1] compiler_4.0.3 tools_4.0.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461996] New: displayed aspect ratio changes when switching monitors?
https://bugs.kde.org/show_bug.cgi?id=461996 Bug ID: 461996 Summary: displayed aspect ratio changes when switching monitors? Classification: Applications Product: okular Version: 22.08.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: majzo...@umsl.edu Target Milestone: --- Created attachment 153866 --> https://bugs.kde.org/attachment.cgi?id=153866&action=edit two instances of okular showing different aspect ratios SUMMARY First, I'm on Ubuntu 22.10 and since upgrading to this version okular has never displayed the aspect ratio of a pdf correctly. It's squashed vertically. However, the displayed aspect ratio seems to change when switching from one external monitor to another. In the attached png file you can see two instances of okular. On the left is an instance I had open and then switched monitors (same resolution is set for both), and the aspect ratio is correct. The second instance of okular shown on the right is what I see whenever I open a new document, it is squashed vertically, which is easy to see in comparing the two. STEPS TO REPRODUCE 1. open file in okular, it is squashed vertically 2. disconnect external monitor and reconnect or switch monitors SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Dell Inc. Product Name: XPS 13 7390 2-in-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 492658] New: Digikam crashes after adding a new collection
https://bugs.kde.org/show_bug.cgi?id=492658 Bug ID: 492658 Summary: Digikam crashes after adding a new collection Classification: Applications Product: digikam Version: 8.4.0 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: erobi...@gmail.com Target Milestone: --- Application: digikam (8.4.0) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: FreeBSD 14.0-RELEASE-p9 amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I added a new collection (path to a local directory of pictures), and digikam crashed immediately. Restarted digikam and it crashed a second or two after opening the window, probably while reading the database. restarted several more times, got the same crash each time. I've been using digikam for over a year without this problem. I installed digikam from the Freebsd pkg collection, I did not compile it from ports. I'm running FreeBSD 14.0-RELEASE-p9, digikam-8.4.0, QT5, Plasma5, kde 23.08.5_x. The pkgs were updated within the last week. If it'd help, I can give you a list of all installed pkgs or just the ones that digikam depends on. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault (lldb) process attach --pid 1358 Process 1358 stopped * thread #1, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51ae88 libc.so.7`__sys_wait4 + 8 libc.so.7`__sys_wait4: -> 0x83f51ae88 <+8>: syscall 0x83f51ae8a <+10>: jb 0x83f5179c8 0x83f51ae90 <+16>: retq 0x83f51ae91: int3 thread #2, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51acaa libc.so.7`__sys_read + 10 libc.so.7`__sys_read: -> 0x83f51acaa <+10>: jb 0x83f5179c8 0x83f51acb0 <+16>: retq 0x83f51acb1: int3 0x83f51acb2: int3 thread #3, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51abaa libc.so.7`__sys_nanosleep + 10 libc.so.7`__sys_nanosleep: -> 0x83f51abaa <+10>: jb 0x83f5179c8 0x83f51abb0 <+16>: retq 0x83f51abb1: int3 0x83f51abb2: int3 thread #4, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51ac2a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x83f51ac2a <+10>: jb 0x83f5179c8 0x83f51ac30 <+16>: retq 0x83f51ac31: int3 0x83f51ac32: int3 thread #5, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51acaa libc.so.7`__sys_read + 10 libc.so.7`__sys_read: -> 0x83f51acaa <+10>: jb 0x83f5179c8 0x83f51acb0 <+16>: retq 0x83f51acb1: int3 0x83f51acb2: int3 thread #6, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00086683ed2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x86683ed2c <+12>: retq 0x86683ed2d <+13>: int3 0x86683ed2e <+14>: int3 0x86683ed2f <+15>: int3 thread #7, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00086683ed2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x86683ed2c <+12>: retq 0x86683ed2d <+13>: int3 0x86683ed2e <+14>: int3 0x86683ed2f <+15>: int3 thread #8, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51ab6a libc.so.7`__sys_kevent + 10 libc.so.7`__sys_kevent: -> 0x83f51ab6a <+10>: jb 0x83f5179c8 0x83f51ab70 <+16>: retq 0x83f51ab71: int3 0x83f51ab72: int3 thread #9, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00086683ed2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x86683ed2c <+12>: retq 0x86683ed2d <+13>: int3 0x86683ed2e <+14>: int3 0x86683ed2f <+15>: int3 thread #10, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00086683ed2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x86683ed2c <+12>: retq 0x86683ed2d <+13>: int3 0x86683ed2e <+14>: int3 0x86683ed2f <+15>: int3 thread #11, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00086683ed2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x86683ed2c <+12>: retq 0x86683ed2d <+13>: int3 0x86683ed2e <+14>: int3 0x86683ed2f <+15>: int3 thread #12, name = 'digikam', stop reason = signal SIGSTOP frame #0: 0x00083f51ab6a libc.so.7`__sys_kevent + 10 libc.so.7`__sys_kevent: -> 0x83f51ab6a <+10>: jb 0x83f5179c8 0x83f51ab70 <+16>: retq 0x83
[Powerdevil] [Bug 489932] New: lid close results in sleep even when connected to external monitor
https://bugs.kde.org/show_bug.cgi?id=489932 Bug ID: 489932 Summary: lid close results in sleep even when connected to external monitor Classification: Plasma Product: Powerdevil Version: 6.1.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: majzo...@umsl.edu CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Ever since upgrading to Plasma 6.1.1 my laptop will always sleep when closing the lid even when connected to an external monitor through HDMI. I have the settings in powerdevil such that lid closure should be ignored if connected to an external monitor. I tried changing the following settings in logind.conf (every possible combination) and rebooted. Nothing works. HandleLidSwitch=ignore HandleLidSwitchExternalPower=ignore HandleLidSwitchDocked=ignore LidSwitchIgnoreInhibited=yes and no STEPS TO REPRODUCE 1. connect external monitor 2. close lid OBSERVED RESULT computer sleeps EXPECTED RESULT computer stays awake SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Wayland -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 485623] Powerdevil does not respect lid-switch inhibitor created with systemd-inhibit
https://bugs.kde.org/show_bug.cgi?id=485623 Eric changed: What|Removed |Added CC||majzo...@umsl.edu --- Comment #4 from Eric --- This is still an issue in Plasma 6.1.2. Is there a fix or workaround out there? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 485623] Powerdevil does not respect lid-switch inhibitor created with systemd-inhibit
https://bugs.kde.org/show_bug.cgi?id=485623 --- Comment #5 from Eric --- Found a workaround / fix. Lot's of stuff on the web about settings in .config/powerdevilrc (or the same file .config/powermanagementprofilesrc), and logind.conf in /etc. None of this worked. It's a setting in .config/kwinoutputconfig.json, but I don't know which one. Creating a new user and closing the lid works, so I tried just copying over their kwinoutputconfig.json file, but this file gets overwritten for some reason after you edit it or on logout or something. So I copied the file over again from the new user and set it read only (chmod 444). Now I can close the lid with an external monitor and the laptop stays awake. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 489932] lid close results in sleep even when connected to external monitor
https://bugs.kde.org/show_bug.cgi?id=489932 Eric changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Eric --- Actually I found the solution a couple of days ago on another forum. Somehow on upgrading to KDE 6.1 I think a kwinoutputconfig.json setting gets corrupted. It's some setting in .config/kwinoutputconfig.json, but I don't know which one. Creating a new user and closing the lid works, so I tried just copying over the new user kwinoutputconfig.json file to my directory, but this file gets overwritten somehow after you edit it or on logout or something. So I copied the file over again from the new user and set it read only. Now everything works again. Oh, and I also have in my logind.conf file: HandleLidSwitch=ignore But I don't know that this has any effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412483] New: Add a side bar panel, which contains several widgets
https://bugs.kde.org/show_bug.cgi?id=412483 Bug ID: 412483 Summary: Add a side bar panel, which contains several widgets Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: schmidt.er...@gmx.net Target Milestone: 1.0 Created attachment 122950 --> https://bugs.kde.org/attachment.cgi?id=122950&action=edit Example of the Action Center in Win10. SUMMARY It would be nice to have something like the Action Center of Windows 10 in KDE Plasma. A full sidebar instead of a small panel gives more spaces for notifications and other sorts of lists. Further there could be some sort of tabs or bug and easy to click buttons instead of tiny tray bar icons. Also it could be divided into several sections, where one section always contains the latest notifications. This could help solving the issue of https://phabricator.kde.org/D23253. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412483] Add a side bar panel, which contains several widgets
https://bugs.kde.org/show_bug.cgi?id=412483 Eric changed: What|Removed |Added CC||schmidt.er...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 420588] New: hard crash on "code preview"
https://bugs.kde.org/show_bug.cgi?id=420588 Bug ID: 420588 Summary: hard crash on "code preview" Product: rkward Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: majzo...@umsl.edu Target Milestone: --- SUMMARY Version 0.7.1 STEPS TO REPRODUCE 1. make "correlation matrix plot" or calculate "descriptive stats" and submit 2. click "Run Again" in the output.html window 3. click on "code preview" 4. move your mouse into the code preview window and crash Note: It does not crash until you move your mouse into the code preview window. OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: plasma 5 on Fedora 31 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 420588] hard crash on "code preview"
https://bugs.kde.org/show_bug.cgi?id=420588 --- Comment #1 from Eric --- On a different linux box running Ubuntu 20.04, with everything else the same, I cannot reproduce the error. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 420588] hard crash on "code preview"
https://bugs.kde.org/show_bug.cgi?id=420588 --- Comment #3 from Eric --- Yes, it is 100% reproducible. Thank you for letting me know what to do. Here is the output from the backtrace... Thread 9 (Thread 0x7fff933ec700 (LWP 5395)): #0 0x727391bd in syscall () at /lib64/libc.so.6 #1 0x72c060c5 in QBasicMutex::lockInternal() () at /lib64/libQt5Core.so.5 #2 0x5571a0a1 in QtScriptBackendThread::run() () #3 0x72c05e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #5 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fff93ffd700 (LWP 5394)): #0 0x723f7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x77d8c74a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x77d8c76f in () at /lib64/libQt5Script.so.5 #3 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fffd93ff700 (LWP 5391)): #0 0x72733a3f in poll () at /lib64/libc.so.6 #1 0x70d2586e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x70d259a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x72e0a885 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x72db423b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x72c04cd5 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x72c05e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #8 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fffdb35c700 (LWP 5390)): #0 0x723f7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x72a1d6a0 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x770721f1 in bmalloc::AsyncTask::threadRunLoop() () at /lib64/libQt5WebKit.so.5 #3 0x7707232f in () at /lib64/libQt5WebKit.so.5 #4 0x72a233d4 in execute_native_thread_routine () at /lib64/libstdc++.so.6 #5 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fffe4f4c700 (LWP 5381)): #0 0x72733a3f in poll () at /lib64/libc.so.6 #1 0x70d2586e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x70d259a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x72e0a885 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x72db423b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x72c04cd5 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x5572f93a in RKFrontendTransmitter::run() () #7 0x72c05e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #9 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fffe574d700 (LWP 5380)): #0 0x723f7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fffe65d719b in util_queue_thread_func () at /usr/lib64/dri/i965_dri.so #2 0x7fffe65d6dab in impl_thrd_routine () at /usr/lib64/dri/i965_dri.so #3 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fffec9f1700 (LWP 5379)): #0 0x72733a3f in poll () at /lib64/libc.so.6 #1 0x70d2586e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x70d259a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x72e0a885 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x72db423b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x72c04cd5 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x735cff6a in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x72c05e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #9 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fffed737700 (LWP 5378)): #0 0x72733a3f in poll () at /lib64/libc.so.6 #1 0x7028138a in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x70282fea in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fffed931d48 in QXcbEventQueue::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x72c05e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x723f14e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7273e6a3 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fffeda7e900 (LWP 5374)): #0 0x73a54ee4 in QTabWidget::indexOf(QWidget*) c
[rkward] [Bug 420588] hard crash on "code preview"
https://bugs.kde.org/show_bug.cgi?id=420588 --- Comment #6 from Eric --- Thank you for fixing this so easily! Indeed, I changed the focus setting and it won't crash if set for click to focus. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 419404] New: Kamoso crashes on startup when webcam is plugged in
https://bugs.kde.org/show_bug.cgi?id=419404 Bug ID: 419404 Summary: Kamoso crashes on startup when webcam is plugged in Product: kamoso Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: ejsta...@joyrex.net Target Milestone: --- Application: kamoso (19.12.3) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.5.13-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Opening Kamoso with webcam plugged in. When it's unplugged, this doesn't happen. Kamoso opens fine. When the webcam gets plugged in Kamoso will then crash. I plugged the webcam into a different USB bus and received the same result. - Custom settings of the application: $ sudo lsusb -v -s 001:007 Bus 001 Device 007: ID 046d:08aa Logitech, Inc. Labtec Notebooks Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0x08aa Labtec Notebooks bcdDevice1.00 iManufacturer 0 iProduct2 Camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0150 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x0080 1x 128 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x00c0 1x 192 bytes bInterval 1 Endpoint Descriptor: bLength
[systemsettings] [Bug 393598] New: Crash while searching in system settings
https://bugs.kde.org/show_bug.cgi?id=393598 Bug ID: 393598 Summary: Crash while searching in system settings Product: systemsettings Version: 5.12.4 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: etyr...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.15.17-65.current x86_64 Distribution: "Solus" -- Information about the crash: - What I was doing when the application crashed: Was searching in system settings. Crash happened while typing in search box. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #6 0x7f7cb49a8440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7cb3dce015 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f7cb3dcdc9d in QQuickItemPrivate::filterKeyEvent(QKeyEvent*, bool) () at /usr/lib/libQt5Quick.so.5 #9 0x7f7cb3dda1e5 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () at /usr/lib/libQt5Quick.so.5 #10 0x7f7cb3dda535 in QQuickItem::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #11 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f7cb538c48e in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f7cb3de57f8 in QQuickWindowPrivate::deliverKeyEvent(QKeyEvent*) () at /usr/lib/libQt5Quick.so.5 #15 0x7f7cb3de9cbf in QQuickWindow::keyReleaseEvent(QKeyEvent*) () at /usr/lib/libQt5Quick.so.5 #16 0x7f7cb4d9d095 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5 #17 0x7f7cb3df41f5 in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #18 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f7cb538c48e in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7f7cb40739fc in QQuickWidget::keyReleaseEvent(QKeyEvent*) () at /usr/lib/libQt5QuickWidgets.so.5 #22 0x7f7cb53c3b48 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7f7cb407519b in QQuickWidget::event(QEvent*) () at /usr/lib/libQt5QuickWidgets.so.5 #24 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f7cb538da34 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x7f7cb53e11c4 in () at /usr/lib/libQt5Widgets.so.5 #28 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #29 0x7f7cb538c48e in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #31 0x7f7cb4d8dc80 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5 #32 0x7f7cb4d92ca5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #33 0x7f7cb4d6a84b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #34 0x7f7ca8fb in () at /usr/lib/libQt5XcbQpa.so.5 #35 0x7f7cb49a671a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #36 0x7f7cb49af9b4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #37 0x0040c976 in () #38 0x7f7cb5d5800a in __libc_start_main () at /usr/lib/libc.so.6 #39 0x0040c9fa in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 387831] New: weird behaviour of "what's interesting" window
https://bugs.kde.org/show_bug.cgi?id=387831 Bug ID: 387831 Summary: weird behaviour of "what's interesting" window Product: kstars Version: 2.8.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bilbohobbi...@orange.fr Target Milestone: --- The window of "what's interesting" tool opens normally, but as soon as you click on the sky map, it goes in the background of the main window, as shown in the video. After a few manipulations, I manage to put "what's interesting" in the foreground, but some buttons (those below) are unusable. I close the windows of "What's interesting", I restart the tool, and there, miracle, everything works normally ... the problem seems to come from the fact that at startup, the tool opens a second window. When we close these windows and restart the tool, it does not open additional windows and then works properly. I made a screencast of the bug available here : https://youtu.be/C-6B_T8LQlA -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 387929] New: The dates of the equinoxes and solstices given in kstars by the calculator tool are wrong
https://bugs.kde.org/show_bug.cgi?id=387929 Bug ID: 387929 Summary: The dates of the equinoxes and solstices given in kstars by the calculator tool are wrong Product: kstars Version: 2.8.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bilbohobbi...@orange.fr Target Milestone: --- Created attachment 109385 --> https://bugs.kde.org/attachment.cgi?id=109385&action=edit Results provided by IMCCE (https://promenade.imcce.fr/en/pages4/439.html) vs provided by Kstars The dates of the equinoxes and solstices given in kstars by the calculator tool are wrong. 1- It seems that there is a lag of one year. 2018 in kstars => 2017 for the IMCCE (Institute for Celestial Mechanics and Computation of Ephemerides, official service that "manages" the time in France, see presentation here : https://www.imcce.fr/institut/presentation/) 2 even with the lag of a year, there are differences of several minutes between the different results. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 387929] The dates of the equinoxes and solstices given in kstars by the calculator tool are wrong
https://bugs.kde.org/show_bug.cgi?id=387929 --- Comment #2 from Eric --- The winter solstice in 2017 is scheduled for December 21 at 16:29 UTC (or 16:27 according to the IMCCE). What I do not understand is why Kstars tells me that it is scheduled for December 21 at 22:19 UTC? I tested kstars on two different computers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392589] New: Driving color picker
https://bugs.kde.org/show_bug.cgi?id=392589 Bug ID: 392589 Summary: Driving color picker Product: krita Version: 4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: erykpoc...@outlook.com Target Milestone: --- Created attachment 111764 --> https://bugs.kde.org/attachment.cgi?id=111764&action=edit shows place where I clicked and where the actual color is My scenario is simple. I press right mouse button on canvas to show color picker but when i choose a color it randomly changes. That mini circle in color picker usually drives for 2-3 seconds before it stops at the edge. I had that problem in Krita 3.3.3 and I still have that in krita 4. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392508] pop-up pallete color picker bug
https://bugs.kde.org/show_bug.cgi?id=392508 --- Comment #4 from Eric --- Is there any way to fix that bug? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392508] pop-up pallete color picker bug
https://bugs.kde.org/show_bug.cgi?id=392508 --- Comment #6 from Eric --- Also, I had that bug in Krita 3.3.3 too. Is it still supported? Should I report that bug specially for Krita 3? I see it's a little quiet here. I don't know if it's helpful but if I remember correctly when I launch Krita for the first time (without preferences) that bug does not occur. So it isn't really a solution to delete prefs every time I launch the app. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390773] New: Can't create new record using existing beneficiaire
https://bugs.kde.org/show_bug.cgi?id=390773 Bug ID: 390773 Summary: Can't create new record using existing beneficiaire Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: eric.piff...@laposte.net Target Milestone: --- I have try with 2 differents databases but have exactly save problem : If I create a new beneficiare I can crate a new record one time If I try to use an existing beneficiaire, I got immediatly a message to let me know I have to save or cancel operation without any possibility to put an amount or any additional information. In any case it cancel and never save. Please let me know if you need more information. Regards, Eric -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390773] Can't create new record using existing beneficiaire
https://bugs.kde.org/show_bug.cgi?id=390773 --- Comment #2 from Eric --- Dear Thomas, Bug still exist. It's probably not the same ticket... I can't crate any record based on an existing beneficiaire. I can only do that with new beneficiaire. Thaks for your help. Kind regards, Eric - Mail original - De: "Thomas Baumgart" À: "eric piffaut" Envoyé: Mardi 20 Février 2018 15:24:50 Objet: [kmymoney] [Bug 390773] Can't create new record using existing beneficiaire https://bugs.kde.org/show_bug.cgi?id=390773 Thomas Baumgart changed: What |Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Baumgart --- Although you don't experience a crash, the fix is the same. *** This bug has been marked as a duplicate of bug 390264 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390773] Can't create new record using existing beneficiaire
https://bugs.kde.org/show_bug.cgi?id=390773 Eric changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Eric --- I'm using KMyMoney V5.0.0 under Ubuntu Bionic Beaver / Gnome 3.26.2 64bit KMyMoney crash each time I want to add a record using an existing beneficiaire so what we are doing everytime using this software... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390773] Can't create new record using existing beneficiaire
https://bugs.kde.org/show_bug.cgi?id=390773 --- Comment #6 from Eric --- Thanks Thomas! Sorry for the misunderstanding ;-) It works using the keyboard. Thanks again. Eric - Mail original - De: "Thomas Baumgart" À: "eric piffaut" Envoyé: Vendredi 23 Février 2018 07:34:46 Objet: [kmymoney] [Bug 390773] Can't create new record using existing beneficiaire https://bugs.kde.org/show_bug.cgi?id=390773 Thomas Baumgart changed: What |Removed |Added Status|REOPENED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Thomas Baumgart --- As I mentioned before, this has been fixed in the source code and will be available in version 5.0.1. Workaround is to use the keyboard (arrow keys and Enter) to select the existing payee instead of the mouse. This should avoid the crash. *** This bug has been marked as a duplicate of bug 390264 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 375259] New: crashes on any new action
https://bugs.kde.org/show_bug.cgi?id=375259 Bug ID: 375259 Summary: crashes on any new action Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: entering a new agenda entry - Custom settings of the application: all Akonady and Kontact folders are simlinked to a safer partition on a separate disk, many account, many profile, many-many filters The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c9738a7c0 (LWP 10683))] Thread 33 (Thread 0x7f2bc4a3a700 (LWP 22785)): #0 0x7f2c8cb29f8d in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2c94b0cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f2c94ab3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f2c948da32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2c93fd102d in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f2bd464c700 (LWP 22732)): #0 0x7f2c93fc4ccd in read () at /lib64/libc.so.6 #1 0x7f2c8cb6ab60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2c8cb2 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2c8cb29df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2c8cb29f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2c94b0cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2c94ab3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f2c948da32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2c93fd102d in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f2bd4e4d700 (LWP 22730)): #0 0x7ffd99501b26 in clock_gettime () #1 0x7f2c93fddc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f2c9498b7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f2c94b0b3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f2c94b0b945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2c94b0cb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f2c8cb294ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f2c8cb29d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f2c8cb29f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f2c94b0cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f2c94ab3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f2c948da32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f2c93fd102d in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f2bd705d700 (LWP 22728)): #0 0x7ffd99501b26 in clock_gettime () #1 0x7f2c93fddc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f2c9498b7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f2c94b0b3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f2c94b0b945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2c94b0cb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f2c8cb294ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f2c8cb29d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f2c8cb29f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f2c94b0cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f2c94ab3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f2c948da32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f2c93fd102d in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f2bd685c700 (LWP 22678)): #0 0x7ffd99501b26 in clock_gettime () #1 0x7f2c93fddc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f2c9498b7d6 in
[kontact] [Bug 375511] New: Crashes on reboot
https://bugs.kde.org/show_bug.cgi?id=375511 Bug ID: 375511 Summary: Crashes on reboot Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: zypper patch + zypper up + reboot - Custom settings of the application: all folder are simlinked to an external partition Many profile, many account, many-many filters. Most filters no longer work and spam filter never did The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62bc9077c0 (LWP 1900))] Thread 22 (Thread 0x7f62057fa700 (LWP 2420)): #0 0x7f62b9e4fccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f62ba089cc5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f62b20a64ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f62b20a6d80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62b20a6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f62ba089d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f62ba030d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f62b9e5732f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f62b28c40a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f62b954e02d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f62067fc700 (LWP 2417)): #0 0x7fff8aeafb26 in clock_gettime () #1 0x7f62b955ac7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f62b9f087d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f62ba0883b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f62ba088945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f62ba089b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f62b20a64ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f62b20a6d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f62b20a6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f62ba089d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f62ba030d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f62b9e5732f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f62b28c40a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f62b954e02d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f6206ffd700 (LWP 2415)): #0 0x7fff8aeafb26 in clock_gettime () #1 0x7f62b955ac7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f62b9f087d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f62ba0883b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f62ba088945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f62ba089b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f62b20a64ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f62b20a6d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f62b20a6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f62ba089d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f62ba030d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f62b9e5732f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f62b28c40a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f62b954e02d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f62077fe700 (LWP 2411)): #0 0x7f62b955a5ff in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7f62b9541cc2 in read () at /lib64/libc.so.6 #2 0x7f62b20e7b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f62b20a6999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62b20a6df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f62b20a6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f62ba089d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f62ba030d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x0
[kontact] [Bug 375587] New: crashes on reboot
https://bugs.kde.org/show_bug.cgi?id=375587 Bug ID: 375587 Summary: crashes on reboot Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: restart (zypper + reboot) - Custom settings of the application: All folder simlinked to a separate disk. Many account, many profile, many-many filter that most no longer works for ages, neither did the spam filter The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f93aad6d7c0 (LWP 4713))] Thread 24 (Thread 0x7f92f05e9700 (LWP 4754)): #0 0x7f93a79abbfd in poll () at /lib64/libc.so.6 #1 0x7f93a050ce64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f93a050cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f93a84efd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f93a8496d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f93a82bd32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f93a79b402d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f92f0dea700 (LWP 4752)): #0 0x7ffcad595b26 in clock_gettime () #1 0x7f93a79c0c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f93a836e7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f93a84ee3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f93a84ee945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f93a84efb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f93a050c4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f93a050cd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f93a050cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f93a84efd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f93a8496d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f93a82bd32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f93a79b402d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f92f1ffb700 (LWP 4750)): #0 0x7f93a054ecf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f93a050c387 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f93a050cd80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f93a050cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f93a84efd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f93a8496d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f93a82bd32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f93a79b402d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f92f27fc700 (LWP 4748)): #0 0x7ffcad595b26 in clock_gettime () #1 0x7f93a79c0c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f93a836e7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f93a84ee3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f93a84ee945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f93a84efb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f93a050c4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f93a050cd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f93a050cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f93a84efd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f93a8496d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f93a82bd32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f93a79b402d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f92f2ffd700 (LWP 4746)): #0 0x7ffcad595b26 in clock_gettime () #1 0x7f93a79c0c7d i
[dolphin] [Bug 375753] New: crash on file transfer
https://bugs.kde.org/show_bug.cgi?id=375753 Bug ID: 375753 Summary: crash on file transfer Product: dolphin Version: 15.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: moving some files from one partition to another. A bulk move, about 20 files, from my local SDD to a remote NAS partition The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efe12bb57c0 (LWP 9098))] Thread 3 (Thread 0x7efdeff62700 (LWP 9119)): #0 0x7efe12462bfd in poll () at /lib64/libc.so.6 #1 0x7efe0749ae64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7efe0749af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7efe0c7a4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7efe0c74bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efe0c56d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7efe0c57232f in () at /usr/lib64/libQt5Core.so.5 #7 0x7efe080200a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7efe1246b02d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7efdfbb67700 (LWP 9103)): #0 0x7efe12462bfd in poll () at /lib64/libc.so.6 #1 0x7efe0545f422 in () at /usr/lib64/libxcb.so.1 #2 0x7efe0546100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7efdfdebc3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7efe0c57232f in () at /usr/lib64/libQt5Core.so.5 #5 0x7efe080200a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7efe1246b02d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7efe12bb57c0 (LWP 9098)): [KCrash Handler] #6 0x7efe119886a4 in KNotification::flags() const () at /usr/lib64/libKF5Notifications.so.5 #7 0x7efe119a5dd7 in () at /usr/lib64/libKF5Notifications.so.5 #8 0x7efe119ab525 in () at /usr/lib64/libKF5Notifications.so.5 #9 0x7efe0c77dcc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x7efe0e023e75 in () at /usr/lib64/libphonon4qt5.so.4 #11 0x7efe0c77eac6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x7efe0d8c4e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7efe0d8c9cc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7efe0c74de95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7efe0c750057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x7efe0c7a58f3 in () at /usr/lib64/libQt5Core.so.5 #17 0x7efe0749ac84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #18 0x7efe0749aed8 in () at /usr/lib64/libglib-2.0.so.0 #19 0x7efe0749af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x7efe0c7a4d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7efe0c74bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7efe0c7538f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #23 0x7efe1278e427 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so #24 0x7efe123a7b25 in __libc_start_main () at /lib64/libc.so.6 #25 0x004007ee in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 375771] New: Crashes on settings change
https://bugs.kde.org/show_bug.cgi?id=375771 Bug ID: 375771 Summary: Crashes on settings change Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: writing a "reply all" using a different "from" than the one in the original email, so far so good, then decided to change the "sent folder" to match the new profile ... and crash. - Custom settings of the application: Many profiles, many accounts, and every foldr are simlinked to a different partition on a different disk The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7feac23e17c0 (LWP 2587))] Thread 26 (Thread 0x7fea05f8c700 (LWP 2700)): #0 0x7feabf0345ff in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7feabf01bcc2 in read () at /lib64/libc.so.6 #2 0x7feab7bc1b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7feab7b80999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7feab7b80df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7feab7b80f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7feabfb63d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7feabfb0ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7feabf93132f in () at /usr/lib64/libQt5Core.so.5 #10 0x7feab839e0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7feabf02802d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fea06be8700 (LWP 2697)): #0 0x7feabf01fbfd in poll () at /lib64/libc.so.6 #1 0x7feab7b80e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feab7b80f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feabfb63d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feabfb0ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7feabf93132f in () at /usr/lib64/libQt5Core.so.5 #7 0x7feab839e0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7feabf02802d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fea077fe700 (LWP 2629)): #0 0x7ffe48c56b26 in clock_gettime () #1 0x7feabf034c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7feabf9e27d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7feabfb623b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7feabfb62945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7feabfb63b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7feab7b804ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7feab7b80d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7feab7b80f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7feabfb63d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7feabfb0ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7feabf93132f in () at /usr/lib64/libQt5Core.so.5 #13 0x7feab839e0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7feabf02802d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fea07fff700 (LWP 2628)): #0 0x7ffe48c56b26 in clock_gettime () #1 0x7feabf034c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7feabf9e27d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7feabfb623b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7feabfb62945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7feabfb63b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7feab7b804ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7feab7b80d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7feab7b80f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7feabfb63d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7feabfb0ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7feabf93132f in () at /usr/lib64/libQt5Core.so.5 #13
[kontact] [Bug 375870] New: Crashes on reboot
https://bugs.kde.org/show_bug.cgi?id=375870 Bug ID: 375870 Summary: Crashes on reboot Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: after update, restart computer, start Kontact, it crashes - Custom settings of the application: many profiles, many email account, many many filter that no longer works, and all akonadi folder are simlinked to a different drive The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3b8ccb7c0 (LWP 2064))] Thread 22 (Thread 0x7ff309ffb700 (LWP 2598)): #0 0x7ffe5e341b26 in clock_gettime () #1 0x7ff3b591ec7d in clock_gettime () at /lib64/libc.so.6 #2 0x7ff3b62cc7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7ff3b644c3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7ff3b644c945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff3b644db5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7ff3ae46a4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7ff3ae46ad80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7ff3ae46af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7ff3b644dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7ff3b63f4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7ff3b621b32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7ff3b591202d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ff30affd700 (LWP 2594)): #0 0x7ff3b5905cd9 in read () at /lib64/libc.so.6 #1 0x7ff3ae4abb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff3ae46a999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff3ae46adf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff3ae46af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff3b644dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff3b63f4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ff3b621b32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7ff3b591202d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ff30b7fe700 (LWP 2593)): #0 0x7ff3b5909bfd in poll () at /lib64/libc.so.6 #1 0x7ff3ae46ae64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff3ae46af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff3b644dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff3b63f4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff3b621b32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff3b591202d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7ff30bfff700 (LWP 2587)): #0 0x7ffe5e341b26 in clock_gettime () #1 0x7ff3b591ec7d in clock_gettime () at /lib64/libc.so.6 #2 0x7ff3b62cc7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7ff3b644c3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7ff3b644c945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff3b644db5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7ff3ae46a4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7ff3ae46ad80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7ff3ae46af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7ff3b644dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7ff3b63f4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7ff3b621b32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7ff3b591202d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7ff318ff9700 (LWP 2585)): #0 0x7ff
[marble] [Bug 365061] Marble could not download maps
https://bugs.kde.org/show_bug.cgi?id=365061 Eric changed: What|Removed |Added CC||econrad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 386766] New: Download maps does not work
https://bugs.kde.org/show_bug.cgi?id=386766 Bug ID: 386766 Summary: Download maps does not work Product: marble Version: 1.9 (KDE 4.14) Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: econrad...@gmail.com Target Milestone: --- Created attachment 108807 --> https://bugs.kde.org/attachment.cgi?id=108807&action=edit Download dialogue (T) Install (B) 100% download, must cancel In version 1.9.1 (Windows/Qt): the download maps function is not able to load the map that has been downloaded. To recreate the problem: 1) In the File menu, select the "Download Maps..." dialog. 2) Select an available map (I chose Mercury) and select "Install" 3) Download progresses and reaches 100%, but the only option is Cancel -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 387678] New: compute in calculator tool makes kstars crash
https://bugs.kde.org/show_bug.cgi?id=387678 Bug ID: 387678 Summary: compute in calculator tool makes kstars crash Product: kstars Version: 2.8.8 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bilbohobbi...@orange.fr Target Milestone: --- Created attachment 109240 --> https://bugs.kde.org/attachment.cgi?id=109240&action=edit gdb result That's how I proceed with kstars: In the menu bar, tools> calculator, then in the calculator module, I choose solar system, conjunctions. I set the dates as of 1st January 2018 00:00 until 1st January 2019 00:00. I choose between the planets and the moon, a gap of 10 degrees max, I leave conjunction and I ask to calculate. From there, every time, the software crashes completely and I have to restart it -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398841] flats sequence not created with adu
https://bugs.kde.org/show_bug.cgi?id=398841 --- Comment #3 from Eric --- the bug is fixed for me ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392508] pop-up pallete color picker bug
https://bugs.kde.org/show_bug.cgi?id=392508 --- Comment #16 from Eric --- (In reply to kentoons from comment #15) > (In reply to Boudewijn Rempt from comment #14) > > Do you by any chance work in CMYK? > > Yes... i was working with CMYK when i exp’d the bug... > and now it works fine with RGB... i was used to using CMYK with other apps > That’s why i ended up posting this thread... > — > I still consider this as a bug tho, that’s still present > In v4.1.3. I just checked it and in RGB it also works fine for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394489] Graphical glitches on panel
https://bugs.kde.org/show_bug.cgi?id=394489 Eric changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||majzo...@umsl.edu --- Comment #6 from Eric --- Same issue is happening for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392508] pop-up pallete color picker bug
https://bugs.kde.org/show_bug.cgi?id=392508 --- Comment #8 from Eric --- Ok. No need to hurry :D Do you know when it will be fixed? I am just curious. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392508] pop-up pallete color picker bug
https://bugs.kde.org/show_bug.cgi?id=392508 --- Comment #11 from Eric --- Is there any way I can help you with it? It happens on my laptop that uses Wacom pen. I don't have that bug on my PC when I try to paint with my mouse :D -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394489] Graphical glitches on panel
https://bugs.kde.org/show_bug.cgi?id=394489 --- Comment #9 from Eric --- I'm on fedora 28. My system info is the following: kde plasma: 5.12.5 kde frameworks: 5.46.0 qt version: 5.10.1 kernel: 4.16-12-300 When it happens I usually just use xkill and click on the panel to restart it. Sometimes it works. Interestingly I have only seen this behaviour on my laptop Dell XPS 15. An identically configured desktop has not had the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394489] Graphical glitches on panel
https://bugs.kde.org/show_bug.cgi?id=394489 --- Comment #11 from Eric --- I can make this happen reproducibly. I have 4 virtual desktops that can be switched back and forth using the middle wheel on the mouse with the pointer on an open spot on the desktop. If I switch quickly (roll the wheel back and forth) so that the virtual desktops switch quickly, and then go to the panel and move the mouse cursor back and forth from left to right to make things pop up off the panel, then I can get the glitch within a minute of doing this. I don't know exactly what triggers it, but it's relatively easy to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394489] Graphical glitches on panel
https://bugs.kde.org/show_bug.cgi?id=394489 --- Comment #13 from Eric --- Dan: I may have narrowed it down. It does appear to be something with the pager. Try this and see if it happens for you. 1. open several konsole windows so that app identifier in the panel will pop up window previews when you hover over it on the panel. If you click on the app identifier while the previews are shown they should shrink to a text list of the windows. 2. Go to your pager and move the mouse around all over the virtual windows. Hover long enough over one pager virtual desktop so that a window list pops up. 3. Go back over to the konsole app identifier in the panel and hover and let the preview windows show. 4. Click on the app identifier so that the previews shrink to the text list. 5. repeat until you get the glitch. It seems to occur for me after step 3 or 4, but step 2 appears to be necessary for it to happen, at least for me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 Eric changed: What|Removed |Added CC||pub08-...@davor.org --- Comment #11 from Eric --- How about this: - If digiKam modifies either the main file or the sidecar, update the database's timestamp column to match - If another program modifies *either* of those files, digiKam should reread the image and update the database timestamp That is, ISTM that the timestamp column is trying to indicate when the conceptual "image" entity last changed -- more specifically, when its discrete, out-of-database representation changed. Supposing that's correct, whether the representation consists of one file or two is beside the point. (Then again, I don't know what other uses digiKam makes of that column, and whether any of those would conflict with this idea.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #13 from Eric --- (In reply to Maik Qualmann from comment #12) > I do not know if this is your suggestion. I believe you and I are saying the same thing: if digiKam changes either the image file or its sidecar (or both), update the last-modified-time column in the database. (I agree that changing the other file's file-system last-modified-date should be avoided if possible.) > Now we can check if there is a new modification > date and start a scan. Yes. I guess I was mostly responding to gilles's comment: > What's happen if image change and not xmp sidecar, and if we write to xmp > side > car only ? This case cannot be managed ? If digiKam compares the database timestamp against *both* files' change dates, this stops being a problem. I.e. if either file is newer than the database timestamp, reread. Thus, if somebody else modifies the original file, digiKam will notice that -- even if digiKam itself is configured to only ever modify the sidecar. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398841] New: flats sequence not created with adu
https://bugs.kde.org/show_bug.cgi?id=398841 Bug ID: 398841 Summary: flats sequence not created with adu Product: kstars Version: 2.9.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bilbohobbi...@orange.fr Target Milestone: --- Application: kstars (2.9.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: I configured a sequence of flats as before, in the calibration section, I chose ADU and adjusted its level. Once the sequence was configured, I wanted to launch it. A picture was taken, then nothing. No automatic exposure adjustment with successive images. In the sequence queue, the flat sequence is indicated "idle". I click to restart the sequence, kstars crashed and return to the desktop The crash can be reproduced every time. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f39952ca440 (LWP 12867))] Thread 6 (Thread 0x7f3955fe6700 (LWP 12878)): #0 0x7f3988806cf9 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f39887c02e0 in g_main_context_acquire () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f39887c12f5 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f39887c154c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f398f55d90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f398f5029ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f398f32122a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f398f32616d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f398e5f26db in start_thread (arg=0x7f3955fe6700) at pthread_create.c:463 #9 0x7f398d3b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f396d93f700 (LWP 12873)): #0 0x7f398d3a6bf9 in __GI___poll (fds=0x7f396400fa00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f39887c1439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f39887c154c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f398f55d90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f398f5029ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f398f32122a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f398f9dad45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f398f32616d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f398e5f26db in start_thread (arg=0x7f396d93f700) at pthread_create.c:463 #9 0x7f398d3b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f396efa2700 (LWP 12872)): #0 0x7f398d3a6bf9 in __GI___poll (fds=0x556337f9f830, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f39887c1439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f39887c17d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3971abef66 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f39887e8e05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f398e5f26db in start_thread (arg=0x7f396efa2700) at pthread_create.c:463 #6 0x7f398d3b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f396f7a3700 (LWP 12871)): #0 0x7f398d3a6bf9 in __GI___poll (fds=0x556337f8ca40, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f39887c1439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f39887c154c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f39887c1591 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f39887e8e05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f398e5f26db in start_thread (arg=0x7f396f7a3700) at pthread_create.c:463 #6 0x7f398d3b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f39798e0700 (LWP 12870)): #0 0x7f398d3a6bf9 in __GI___poll (fds=0x7f39798dfc28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f39879db747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f39879dd36a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f397c68d2a9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f398f32616d in () at /usr/lib
[kstars] [Bug 398841] flats sequence not created with adu
https://bugs.kde.org/show_bug.cgi?id=398841 --- Comment #1 from Eric --- Created attachment 115099 --> https://bugs.kde.org/attachment.cgi?id=115099&action=edit video reproducing the bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394489] Graphical glitches on panel
https://bugs.kde.org/show_bug.cgi?id=394489 --- Comment #14 from Eric --- Let me rewrite step 4 to include one more point. 4. Click on the app identifier so that the previews shrink to the text list. While the text list is up for the open konsole apps, move the cursor to other apps in the panel and back to the konsole list. Move on and off the panel so that the preview list shows up when going back to the konsole app, and again click it down to the text list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394489] Graphical glitches on panel
https://bugs.kde.org/show_bug.cgi?id=394489 --- Comment #18 from Eric --- Looks like we are not alone. It's reported on the Debian bugs site as well: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900316#5 See message #5 and related messages. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392508] pop-up pallete color picker bug
https://bugs.kde.org/show_bug.cgi?id=392508 --- Comment #13 from Eric --- When I delete Krita preferences it works fine first time I run the app. If this would be system problem it shoudn't work after deleting prefs. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376654] New: Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 Bug ID: 376654 Summary: Crashes on restart Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.38-47-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: zypper patch and zypper up then reboot - Custom settings of the application: all folder seemlinked to a safe side hard drive The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b4ca3e7c0 (LWP 3274))] Thread 22 (Thread 0x7f4a957fa700 (LWP 3812)): #0 0x7f4b4221fd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4b421dde0e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4b421ddf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4b4a1c0d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4b4a167d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f4b49f8e32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f4b4968502d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f4a967fc700 (LWP 3808)): #0 0x7fffda4ddb26 in clock_gettime () #1 0x7f4b49691c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f4b4a03f7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f4b4a1bf3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f4b4a1bf945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4b4a1c0b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f4b421dd4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f4b421ddd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f4b421ddf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f4b4a1c0d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f4b4a167d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f4b49f8e32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f4b4968502d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f4a96ffd700 (LWP 3806)): #0 0x7f4b49f86bfa in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f4b4a1c0cb5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f4b421dd4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4b421ddd80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4b421ddf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4b4a1c0d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4b4a167d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f4b49f8e32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4b4968502d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f4a977fe700 (LWP 3802)): #0 0x7f4b4967cbfd in poll () at /lib64/libc.so.6 #1 0x7f4b421dde64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4b421ddf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4b4a1c0d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4b4a167d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f4b49f8e32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f4b4968502d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f4a97fff700 (LWP 3801)): #0 0x7fffda4ddb26 in clock_gettime () #1 0x7f4b49691c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f4b4a03f7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f4b4a1bf3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f4b4a1bf945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4b4a1c0b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f4b421dd4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f4b421d
[kontact] [Bug 376654] Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 --- Comment #2 from Eric --- Hi Christophe, I'm sorry that the bug report system is unable to find a bug that appears every other day and reported with the same title from the same person That's why I HAVE to create a new one each time. I can feel your frustration, please consider mine. It's also unfortunate that KDE is not suggesting Kmail/Kontact update, even though I zypper patch AND Zypper up every other day if not every day I will do a manual specific update of the package, hopping it won't smash all my simlinks, it took me ages to find them all and simlink them one by one Thks again for your support ! Eric A long time user still novice ;) On 2017-02-22 22:39, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=376654 > > Christoph Feck changed: > >What|Removed |Added > > Resolution|--- |INVALID > Status|UNCONFIRMED |RESOLVED > > --- Comment #1 from Christoph Feck --- > Already reported, and I am not going to search it again. > > Please update your software, we already released KMail 5.3 and KMail > 5.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377321] New: KWIN crashes sometimes when opening VBOX client
https://bugs.kde.org/show_bug.cgi?id=377321 Bug ID: 377321 Summary: KWIN crashes sometimes when opening VBOX client Product: kwin Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ebelc...@eacbelcher.net Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: On starting a VirtualBox client (Windows 10) with two screens, one window will sometimes fail during startup. Disabling and restarting the second screen resolves the symptom. VirtualBox Graphical User Interface Version 5.1.14 r112924 (Qt5.6.1) NAME="openSUSE Leap" VERSION="42.2" ID=opensuse ID_LIKE="suse" VERSION_ID="42.2" PRETTY_NAME="openSUSE Leap 42.2" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.2" BUG_REPORT_URL="https://bugs.opensuse.org"; HOME_URL="https://www.opensuse.org/ The problem is a reasonably new one, 4-6 weeks and I believe due to a OpenSUSE patch. VBOX has remained at the above version since it was released. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f52d37b1940 (LWP 2670))] Thread 7 (Thread 0x7f5217ce5700 (LWP 2847)): #0 0x7f52d2f26b03 in select () at /lib64/libc.so.6 #1 0x7f52d05f9849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f52d05fb0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f52d05fb527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f52d05aafdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f52cafd79c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f52d03ea9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f52d2f2dd3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f52b1ffc700 (LWP 2773)): #0 0x7f52d31f40af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f52cf58093b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f52cf580969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f52d2f2dd3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f529871e700 (LWP 2772)): #0 0x7f52d31f40af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f52a398e533 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f52a398dd57 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f52d2f2dd3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f52b2ffd700 (LWP 2749)): #0 0x7f52d05fb1f9 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #1 0x7f52d05fb527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f52d05aafdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f52cafd79c8 in () at /usr/lib64/libQt5Qml.so.5 #5 0x7f52d03ea9e9 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0 #7 0x7f52d2f2dd3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f52b3fff700 (LWP 2702)): #0 0x7f52d2f26b03 in select () at /lib64/libc.so.6 #1 0x7f52d05f9849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f52d05fb0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f52d05fb527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f52d05aafdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f52ca1b81d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f52d03ea9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f52d2f2dd3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f52b9ee0700 (LWP 2671)): #0 0x7f52d2f2549d in poll () at /lib64/libc.so.6 #1 0x7f52d20ac3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f52d20adfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f52bab90839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x00
[kwin] [Bug 377440] New: KWIN crashes when starting saved VBOX client with two screens.
https://bugs.kde.org/show_bug.cgi?id=377440 Bug ID: 377440 Summary: KWIN crashes when starting saved VBOX client with two screens. Product: kwin Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ebelc...@eacbelcher.net Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Starting VBOX saved client from a shortcut on the desktop. VirtualBox Graphical User Interface Version 5.1.14 r112924 (Qt5.6.1) Symptom have only started occuring in the last few weeks after some OpenSUSE updates. Virtual Box version has been installed and stable since the release of this version. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f457c988940 (LWP 2474))] Thread 7 (Thread 0x7f44c0d65700 (LWP 2632)): #0 0x7f457c0fdb03 in select () at /lib64/libc.so.6 #1 0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45797d20c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45797d2527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4579781fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f45741ae9c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4552ffe700 (LWP 2585)): #0 0x7f457c3cb0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f457875793b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f4578757969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f454179e700 (LWP 2584)): #0 0x7f457c3cb0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4550ed7533 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f4550ed6d57 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4553fff700 (LWP 2554)): #0 0x7f457c0fdb03 in select () at /lib64/libc.so.6 #1 0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45797d20c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45797d2527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4579781fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f45741ae9c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4561864700 (LWP 2514)): #0 0x7f457c0fdb03 in select () at /lib64/libc.so.6 #1 0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45797d20c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45797d2527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4579781fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f457338f1d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f45630b7700 (LWP 2510)): #0 0x7f457c0fc49d in poll () at /lib64/libc.so.6 #1 0x7f457b2833e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f457b284fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f4563d67839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #6 0x000
[kontact] [Bug 373324] New: crashes at opening
https://bugs.kde.org/show_bug.cgi?id=373324 Bug ID: 373324 Summary: crashes at opening Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Restart the computer after last update (zypper patch + zypper up + reboot) - Custom settings of the application: Many email account, many profile and aliases, many-many filters The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad243a27c0 (LWP 1919))] Thread 22 (Thread 0x7fac6d7fa700 (LWP 2423)): #0 0x7fad19b83cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fad19b414b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fad19b41d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fad19b41f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fad21b24d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fad21acbd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fad218f232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fad20fe902d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fac6e7fc700 (LWP 2421)): #0 0x7fffb5de8b26 in clock_gettime () #1 0x7fad20ff5c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fad219a37d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fad21b233b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fad21b23945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fad21b24b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fad19b414ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fad19b41d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fad19b41f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fad21b24d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fad21acbd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fad218f232f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fad20fe902d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7fac6effd700 (LWP 2420)): #0 0x7fad19b83d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fad19b41759 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7fad19b41dcf in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fad19b41f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fad21b24d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fad21acbd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fad218f232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fad20fe902d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fac6f7fe700 (LWP 2414)): #0 0x7fffb5de8b26 in clock_gettime () #1 0x7fad20ff5c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fad219a37d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fad21b233b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fad21b23945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fad21b24b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fad19b414ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fad19b41d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fad19b41f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fad21b24d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fad21acbd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fad218f232f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fad20fe902d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fac6700 (LWP 2413)): #
[kontact] [Bug 373516] New: Crash on start
https://bugs.kde.org/show_bug.cgi?id=373516 Bug ID: 373516 Summary: Crash on start Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-38-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Restarted the computer after update (zypper patch + zypper up + reboot) - Custom settings of the application: Many accounts, many profile, many-many filters The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff14715d7c0 (LWP 3476))] Thread 22 (Thread 0x7ff08bfff700 (LWP 3974)): #0 0x7fff3ec94b26 in clock_gettime () #1 0x7ff143db0c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7ff14475e7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7ff1448de3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7ff1448de945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff1448dfb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7ff13c8fc4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7ff13c8fcd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7ff13c8fcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7ff1448dfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7ff144886d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7ff1446ad32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7ff143da402d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ff0997fa700 (LWP 3971)): #0 0x7ff1448dfd8d in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #1 0x7ff144886d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #3 0x7ff1446ad32f in () at /usr/lib64/libQt5Core.so.5 #4 0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff143da402d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ff099ffb700 (LWP 3970)): #0 0x7ff143db05ff in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7ff143d9bbf2 in poll () at /lib64/libc.so.6 #2 0x7ff13c8fce64 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff13c8fcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff1448dfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff144886d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ff1446ad32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff143da402d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7ff09a7fc700 (LWP 3966)): #0 0x7fff3ec94b26 in clock_gettime () #1 0x7ff143db0c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7ff14475e7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7ff1448de3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7ff1448de945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff1448dfb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7ff13c8fc4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7ff13c8fcd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7ff13c8fcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7ff1448dfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7ff144886d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7ff1446ad32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7ff143da402d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7ff09affd700 (LWP 3965)): #0 0x7fff3ec94b26 in clock_gettime () #1 0x7ff143db0c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7ff14475e7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7ff1448de3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7ff1448de945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so
[kontact] [Bug 373772] New: Crash after upload
https://bugs.kde.org/show_bug.cgi?id=373772 Bug ID: 373772 Summary: Crash after upload Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-41-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: reboot after zypper patch + zypper up - Custom settings of the application: Many profiles, many email account, many many filters The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f97756807c0 (LWP 3627))] Thread 22 (Thread 0x7f96ba7fc700 (LWP 4157)): #0 0x7ffd3c9bbb26 in clock_gettime () #1 0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f9772c817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9772e02b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f976ae1f4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f976ae1fd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f976ae1ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f9772e02d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f9772da9d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f9772bcb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f9772bd032f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f976b63d0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f97722c702d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f96bb7fe700 (LWP 4155)): #0 0x7ffd3c9bbb26 in clock_gettime () #1 0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f9772c817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9772e02b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f976ae1f4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f976ae1fd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f976ae1ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f9772e02d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f9772da9d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f9772bcb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f9772bd032f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f976b63d0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f97722c702d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f96bbfff700 (LWP 4153)): #0 0x7ffd3c9bbb26 in clock_gettime () #1 0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f9772c817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9772e02b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f976ae1f4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f976ae1fd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f976ae1ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f9772e02d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f9772da9d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f9772bcb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f9772bd032f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f976b63d0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f97722c702d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f96d4ff9700 (LWP 4149)): #0 0x7ffd3c9bbb26 in clock_gettime () #1 0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f9772c817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9772e02b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f976ae1f4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.
[kontact] [Bug 374471] New: Reboot crash everytime
https://bugs.kde.org/show_bug.cgi?id=374471 Bug ID: 374471 Summary: Reboot crash everytime Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: zypper patch + zypper up + reboot - Custom settings of the application: Simlinks to a different partition, many profiles, many many filters (most filters stoped working a while ago, and spam filter never worked) The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7d948587c0 (LWP 3548))] Thread 22 (Thread 0x7f7ce57fa700 (LWP 4050)): #0 0x7ffde4139b26 in clock_gettime () #1 0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f7d91e597d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7d91fdab5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f7d89ff74ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f7d89ff7d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f7d89ff7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f7d91fdad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f7d91f81d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f7d91da832f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f7d9149f02d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f7ce67fc700 (LWP 4043)): #0 0x7ffde4139b26 in clock_gettime () #1 0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f7d91e597d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7d91fdab5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f7d89ff74ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f7d89ff7d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f7d89ff7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f7d91fdad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f7d91f81d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f7d91da832f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f7d9149f02d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f7ce6ffd700 (LWP 4041)): #0 0x7ffde4139b26 in clock_gettime () #1 0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f7d91e597d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7d91fdab5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f7d89ff74ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f7d89ff7d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f7d89ff7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f7d91fdad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f7d91f81d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f7d91da832f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f7d9149f02d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f7ce77fe700 (LWP 4033)): #0 0x7f7d8a039d10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f7d89ff78e9 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7d89ff7df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7d89ff7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7d91fdad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x0
[kontact] [Bug 374642] New: Crashes while changing account settings
https://bugs.kde.org/show_bug.cgi?id=374642 Bug ID: 374642 Summary: Crashes while changing account settings Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was changing the trashbox settings and the expiring settings for one of my accounts - Custom settings of the application: many accounts, many identity, many-many filters The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fea0ae807c0 (LWP 2637))] Thread 26 (Thread 0x7fe94d659700 (LWP 13897)): #0 0x7fea00e4103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe9f50f386b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fe9f50f3899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fea07ac702d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fe94ce58700 (LWP 3502)): #0 0x7ffcfe7e5b26 in clock_gettime () #1 0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fea084817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fea08602b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fea0061f4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fea0061fd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fea0061ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fea08602d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fea085a9d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fea083d032f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fea07ac702d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fe94fde8700 (LWP 2705)): #0 0x7ffcfe7e5b26 in clock_gettime () #1 0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fea084817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fea08602b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fea0061f4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fea0061fd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fea0061ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fea08602d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fea085a9d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fea083d032f in () at /usr/lib64/libQt5Core.so.5 #13 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7fea07ac702d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fe9505e9700 (LWP 2678)): #0 0x7fea07abaccd in read () at /lib64/libc.so.6 #1 0x7fea00660b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fea0061f999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fea0061fdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fea0061ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fea08602d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fea085a9d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fea083d032f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fea07ac702d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fe950dea700 (LWP 2676)): #0 0x7ffcfe7e5b26 in clock_gettime () #1 0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7fea084817d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #
[kontact] [Bug 374643] New: Crashes while changing defalut settings
https://bugs.kde.org/show_bug.cgi?id=374643 Bug ID: 374643 Summary: Crashes while changing defalut settings Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Changing the "sent email" box address for one of my accounts - Custom settings of the application: Many accounts, many identity, many-many filters The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f648bcc97c0 (LWP 13967))] Thread 27 (Thread 0x7f634e836700 (LWP 14102)): #0 0x7ffec0afbb26 in clock_gettime () #1 0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f64892ca7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f648944bb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f64814684ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f6481468d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f6481468f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f648944bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f64893f2d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f648921932f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f648891002d in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f63cf7be700 (LWP 14101)): #0 0x7f6481c8a03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6475f3c86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f6475f3c899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f648891002d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f63d4dea700 (LWP 14081)): #0 0x7ffec0afbb26 in clock_gettime () #1 0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f64892ca7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f648944bb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f64814684ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f6481468d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f6481468f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f648944bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f64893f2d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f648921932f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f648891002d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f63d55eb700 (LWP 14047)): #0 0x7f6488903ccd in read () at /lib64/libc.so.6 #1 0x7f64814a9b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6481468999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6481468df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f6481468f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f648944bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f64893f2d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f648921932f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f648891002d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f63d5dec700 (LWP 14046)): #0 0x7ffec0afbb26 in clock_gettime () #1 0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f64892ca7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f648944bb5
