[plasmashell] [Bug 468438] New: file:///usr/share/plasma/plasmoids/org.kde.milou/contents/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine
https://bugs.kde.org/show_bug.cgi?id=468438 Bug ID: 468438 Summary: file:///usr/share/plasma/plasmoids/org.kde.milou/conte nts/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Milou Assignee: plasma-b...@kde.org Reporter: kevin.coo...@gmail.com CC: alexander.loh...@gmx.de Target Milestone: 1.0 Click on Desktop and Plasma Crashes. Every time. It restarts, but still... STEPS TO REPRODUCE 1. Click on desktop 2. 3. OBSERVED RESULT KCrash: Attempting to start /usr/bin/plasmashell 25 -- exe=/usr/bin/plasmashell 13 -- platform=xcb 11 -- display=:0 20 -- appname=plasmashell 17 -- apppath=/usr/bin 9 -- signal=7 9 -- pid=6582 18 -- appversion=5.27.4 19 -- programname=Plasma 31 -- bugaddress=sub...@bugs.kde.org 15 -- restarted=true KCrash: Application 'plasmashell' crashing... kf.plasma.quick: Applet preload policy set to 1 file:///usr/share/plasma/plasmoids/org.kde.milou/contents/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine file:///usr/share/plasma/plasmoids/org.kde.milou/contents/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine libpng warning: iCCP: known incorrect sRGB profile org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x557ba02a2490) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x557ba0048660) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x557ba0048750) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x557b9ffadc90) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x557b9ff718c0) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x557b9feb8be0) libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile file:///home/kevin/.local/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:87: TypeError: Cannot read property 'height' of null file:///home/kevin/.local/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:63: TypeError: Cannot read property 'height' of null qml: [weatherWidget] Timezone Data is available - using met.no API qml: https://api.met.no/weatherapi/sunrise/2.0/.json?lat=44.97997&lon=-93.26384&height=262&date=2023-04-12&offset=-05:00 qml: cacheBackend failed to initialize qml: [weatherWidget] Timezone Data is available - using met.no API qml: https://api.met.no/weatherapi/sunrise/2.0/.json?lat=44.97997&lon=-93.26384&height=262&date=2023-04-12&offset=-05:00 org.kde.plasma.taskmanager: DragHelper is deprecated in Plasma 5.27. Use Backend::generateMimeData and QtQuick.DragHandler instead. / "Plasma Desktop version: 5.27.4 (334596)" / qml: PulseAudio Latte interface was loaded... file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:586: Error: Invalid write to global property "groupDialog" qml: Tasks: Applying UNIQUE Launchers List... qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:265:5: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:952:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:965:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:265:5: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any Q
[plasmashell] [Bug 468438] file:///usr/share/plasma/plasmoids/org.kde.milou/contents/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine
https://bugs.kde.org/show_bug.cgi?id=468438 --- Comment #1 from Kevin Coonan --- I removed all my desktop widgets, but obviously some plasma components still loaded. Output from restarting plasmashell (using plasmashell -d): 17:46 ~ $ plasmashell -d kf.plasma.quick: Applet preload policy set to 1 file:///usr/share/plasma/plasmoids/org.kde.milou/contents/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine file:///usr/share/plasma/plasmoids/org.kde.milou/contents/ui/main.qml:47:17: Unable to assign double to QQuickAnchorLine libpng warning: iCCP: known incorrect sRGB profile org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x55ddabaf1c50) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x55ddab931ff0) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x55ddab9320e0) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x55ddabbf5320) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x55ddab90cb60) org.kde.plasma.kicker: Entry is not valid "applications:org.kde.Help.desktop" QSharedPointer(0x55ddab930a10) libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile file:///home/kevin/.local/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:87: TypeError: Cannot read property 'height' of null file:///home/kevin/.local/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:63: TypeError: Cannot read property 'height' of null qml: [weatherWidget] Timezone Data is available - using met.no API qml: https://api.met.no/weatherapi/sunrise/2.0/.json?lat=44.97997&lon=-93.26384&height=262&date=2023-04-12&offset=-05:00 qml: cacheBackend failed to initialize qml: [weatherWidget] Timezone Data is available - using met.no API qml: https://api.met.no/weatherapi/sunrise/2.0/.json?lat=44.97997&lon=-93.26384&height=262&date=2023-04-12&offset=-05:00 org.kde.plasma.taskmanager: DragHelper is deprecated in Plasma 5.27. Use Backend::generateMimeData and QtQuick.DragHandler instead. / "Plasma Desktop version: 5.27.4 (334596)" / qml: PulseAudio Latte interface was loaded... file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:586: Error: Invalid write to global property "groupDialog" qml: Tasks: Applying UNIQUE Launchers List... qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:265:5: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:952:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:965:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:265:5: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:952:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:965:13: QML Binding: Not restoring
[khelpcenter] [Bug 465451] New: Man page search results limited to first ten
https://bugs.kde.org/show_bug.cgi?id=465451 Bug ID: 465451 Summary: Man page search results limited to first ten Classification: Applications Product: khelpcenter Version: 5.8.22121 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: kevin.coo...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Search for something in KDE Help Center that has more than ten relevant man pages (e.g. search for "search", apropos returns 141 man page listings). OBSERVED RESULT The first ten man pages returned by apropos are shown. * There is no indication that there are more than ten man pages found. * There is no way to change how many man pages are shown. * There is no way to scroll down/view addition matching results * There is no way to further limit the search via a useful function (e.g. by section, i.e. type of man page--header filels, executables/shell commands, system calls, library calls, files, sysadmin stuff, etc. etc.) * Right clicking and selecting "Next Page" / Ctrl+PageDn / PageDn / or clicking on "Find Next" have no effect EXPECTED RESULT (1) Indicate the number of found man pages (2) Let the user configure how many man pages to show at one time (3) Provide means for the user to scroll through the various man pages (4) Have an option "Restriction man pages to section:" and then have a check box (so you can, for example, look at man pages in section 1 and 8) that lists each section by section number *and name* (because newbies don't know what '(1p)' means.) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1.6-1 x86_64 openSUSE Tumbleweed 20230118, KDE Plasma v: 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: KDE Frameworks Version 5.102.0 Qt Version: Qt Version 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 465453] New: let users define a time and units format that is useful to them
https://bugs.kde.org/show_bug.cgi?id=465453 Bug ID: 465453 Summary: let users define a time and units format that is useful to them Classification: Frameworks and Libraries Product: frameworks-kconfig Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: kevin.coo...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Do anything involving time or units of measurement 2. Put in your locale 3. Try and get the time, date, or units of measurements to reflect your needs without having to do some really screwy things (e.g set local to en-DE to try and force metric units even though they use dl, and I use ml or l!) OBSERVED RESULT 1. Choose "Set Time Format" does NOT ever let you set a time format. Rigid and illogical bindings to locale as defined in some C or C++ library EXPECTED RESULT 1. Choose "Set Time Format" --> lets you set the time AND date format. Let the user specify the default time and date based on a range of conventions (see, for example, any software besides KDE that deals with date/time). E.g. AT A MINIMUM, for local en-US, support the **CHOICE** between ISO-8601, RFC 3339, MM-DD-, DD-3letter all cap month-YY (like the US military uses), MM/DD/YY, M/D/YY, Month (spelled out), D, , and a few more. Allow **users** to **pick** whether to use SI/metric, US Imperial, UK Imperial, etc. for units of measurement. In fact, maybe even let them pick which units they use for different things. It doesn't matter what MISTAKES were made in the past, your location does NOT define what your need for units of measurements (I haven't used most US Imperial measurements at work for almost 30 years now as I work in healthcare, and I switched from writing dates like 03MAR02 on or about 2002-03-03--I think I last wrote dates like 2/7/23 and time like 5:17PM (even though I have used 24h time at work, and every other clock/device I own can show me that it is 17:17--becuse that is how I set them) in the mid 1980s, yet my KDE desktop cannot be cured of this affliction. Just FYI, the current, correct time/date **FOR ME** is: Tue 2023-02-07 17:17:23 CST Is it NOT: Tuesday, February 7, 2023 5:17 PM *or any of the other formats that 'copy to clipboard' from my digital clock widget supports. SOFTWARE/OS VERSIONS Windows: (lets user pick format) macOS: (probably uses whatever format Apple said and they all go along with it...) Linux/KDE Plasma: Been a pain in my ass ever since KDE 3.x!!! (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.
[plasmashell] [Bug 441333] New: touching anything related to Plasma
https://bugs.kde.org/show_bug.cgi?id=441333 Bug ID: 441333 Summary: touching anything related to Plasma Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kevin.coo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.8-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Desperately trying to do some web browsing w/ Firefox, as well as trying to figure out why MariaDB won't load (so was trying to find the damn log--remember when we had text logs and text configuration systems and we could easily fix crap. Now it is as bad as digging into the goddamn windows registry!) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f2402f7f980 (LWP 31841))] [KCrash Handler] #6 QString::~QString (this=, this=) at /usr/include/c++/11/bits/atomic_base.h:385 #7 QString::clear (this=0x5653e09a1c00) at /usr/include/qt5/QtCore/qstring.h:1092 #8 KProcess::clearProgram (this=) at /usr/src/debug/kcoreaddons-5.85.0-1.1.x86_64/src/lib/io/kprocess.cpp:158 #9 0x7f23d6ac3f81 in Konsole::Pty::start (this=0x5653ea229ff0, program=..., programArguments=..., environment=..., winid=0, addToUtmp=) at lib/Pty.cpp:165 #10 0x7f23d6ac46b5 in Konsole::Session::run (this=0x5653de303790) at /usr/include/qt5/QtCore/qstringlist.h:138 #11 0x7f23d6ae458b in KSession::qt_metacall (this=0x5653dbe41a50, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7ffe2c43ad10) at /usr/src/debug/qmltermwidget-0.2.0-2.8.x86_64/moc_ksession.cpp:407 #12 0x7f24070e504d in ?? () from /lib64/libQt5Qml.so.5 #13 0x7f2406fc2c7e in ?? () from /lib64/libQt5Qml.so.5 #14 0x7f2406fc5f0b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib64/libQt5Qml.so.5 #15 0x7f2406fe2b53 in ?? () from /lib64/libQt5Qml.so.5 #16 0x7f2406fe57e7 in ?? () from /lib64/libQt5Qml.so.5 #17 0x7f2406f78c6e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #18 0x7f24070ffc05 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #19 0x7f24070b165b in QQmlBoundSignalExpression::evaluate(void**) () from /lib64/libQt5Qml.so.5 #20 0x7f24070b2848 in ?? () from /lib64/libQt5Qml.so.5 #21 0x7f24070e4af5 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #22 0x7f2405aedb38 in ?? () from /lib64/libQt5Core.so.5 #23 0x7f24071155fc in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #24 0x7f24070abac5 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #25 0x7f24070ac0bd in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib64/libQt5Qml.so.5 #26 0x7f24070a59fb in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /lib64/libQt5Qml.so.5 #27 0x7f2407ab58da in KDeclarative::QmlObject::completeInitialization (initialProperties=..., this=0x5653d9ebb180) at /usr/src/debug/kdeclarative-5.85.0-1.1.x86_64/src/kdeclarative/qmlobject.cpp:307 #28 KDeclarative::QmlObject::completeInitialization (this=0x5653d9ebb180, initialProperties=...) at /usr/src/debug/kdeclarative-5.85.0-1.1.x86_64/src/kdeclarative/qmlobject.cpp:289 #29 0x7f2407d889eb in PlasmaQuick::AppletQuickItem::init (this=this@entry=0x5653d9ebb2c0) at /usr/src/debug/plasma-framework-5.85.0-1.1.x86_64/src/plasmaquick/appletquickitem.cpp:649 #30 0x7f23f837f802 in AppletInterface::init (this=0x5653d9ebb2c0) at /usr/src/debug/plasma-framework-5.85.0-1.1.x86_64/src/scriptengines/qml/plasmoid/appletinterface.cpp:141 #31 0x7f2407d85e91 in PlasmaQuick::AppletQuickItem::itemChange (this=0x5653d9ebb2c0, change=QQuickItem::ItemSceneChange, value=...) at /usr/src/debug/plasma-framework-5.85.0-1.1.x86_64/src/plasmaquick/appletquickitem.cpp:927 #32 0x7f24075c53ab in QQuickItemPrivate::refWindow(QQuickWindow*) () from /lib64/libQt5Quick.so.5 #33 0x7f24075c5369 in QQuickItemPrivate::refWindow(QQuickWindow*) () from /lib64/libQt5Quick.so.5 #34 0x7f24075c5770 in QQuickItem::setParentItem(QQuickItem*) () from /lib64/libQt5Quick.so.5 #35 0x7f2407d8dd1d in PlasmaQuick::ContainmentViewPrivate::setContainment (this=0x5653da0b7f40, cont=) at /usr/src/debug/plasma-framework-5.85.0-1.1.x86_64/src/plasmaq
[plasmashell] [Bug 441394] New: Every damn time I use that activity Plasma crashes
https://bugs.kde.org/show_bug.cgi?id=441394 Bug ID: 441394 Summary: Every damn time I use that activity Plasma crashes Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kevin.coo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.12-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Trying to get back to work on a huge database development project (I have 40 tables to load w/ ~60gb of data--and thats my data dictionary!) and when I switched back to my "admin" desktop, which has a lot of plasmoids of dubious quality, to try and fix some problem w/ flakey behavior on the part of the Qt windows decorators which made it impossible to get Konsole out of my way. I did have an active (proxyish) connection to Google Cloud SQL, and was also connected to MariaDB on my workstation. A million Firefox pages open trying to figure out if I want to try and learn pgloader or take a bigger leap w/ openrefine...but memory was about 8 out of 16gb used. I had been keeping an eye on things w/ HTOP, and I didn't see anything that looked like a memory leak. I suspect it is a flakey plasmoid, and I am getting rid of them as soon as I...ah crap...it just crashed again just LOOKING at the plasmoids. Tmux and framebuffer are looking pretty good these days - Unusual behavior I noticed: Switching activities and it seems to be to the one cluttered w/ plasmoids. - Custom settings of the application: Nothing too odd. I have just installed it, and am trying to work out the glitches (no sound?!?), so I have gone over my alternatives w/ a fine tooth comb to make sure that everythign Python3 is 3.8 (I did install 3.9 as well, as I figure if I am going to have to learn it, might as well start w/ the current version--now figuring out which verion of Qt (5.15? 6?) to use is a problem for another day. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fb28e41e980 (LWP 5450))] [KCrash Handler] #6 QString::~QString (this=, this=) at /usr/include/c++/11/bits/atomic_base.h:385 #7 QString::clear (this=0x55e907342890) at /usr/include/qt5/QtCore/qstring.h:1092 #8 KProcess::clearProgram (this=) at /usr/src/debug/kcoreaddons-5.85.0-1.1.x86_64/src/lib/io/kprocess.cpp:158 #9 0x7fb2753a4f81 in Konsole::Pty::start (this=0x55e906ecefb0, program=..., programArguments=..., environment=..., winid=0, addToUtmp=) at lib/Pty.cpp:165 #10 0x7fb2753a56b5 in Konsole::Session::run (this=0x55e907338b90) at /usr/include/qt5/QtCore/qstringlist.h:138 #11 0x7fb2753c558b in KSession::qt_metacall (this=0x55e9073217c0, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fff8bcc7340) at /usr/src/debug/qmltermwidget-0.2.0-2.8.x86_64/moc_ksession.cpp:407 #12 0x7fb29258404d in QQmlObjectOrGadget::metacall (this=this@entry=0x7fff8bcc7580, type=type@entry=QMetaObject::InvokeMetaMethod, index=, argv=argv@entry=0x7fff8bcc7340) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qml/qml/qqmlobjectorgadget.cpp:51 #13 0x7fb292461c7e in CallMethod (callType=QMetaObject::InvokeMetaMethod, callArgs=0x7fb2829b05b0, engine=0x55e9062491d0, argTypes=0x0, argCount=0, returnType=43, index=, object=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1319 #14 CallPrecise (object=..., data=..., engine=engine@entry=0x55e9062491d0, callArgs=callArgs@entry=0x7fb2829b05b0, callType=callType@entry=QMetaObject::InvokeMetaMethod) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1573 #15 0x7fb292464f0b in CallOverloaded (callType=, propertyCache=, callArgs=, engine=, data=..., object=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1645 #16 QV4::QObjectMethod::callInternal (this=, thisObject=, argv=, argc=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:2133 #17 0x7fb292481b53 in QV4::FunctionObject::call (argc=, argv=, thisObject=, this=) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4functionobject_p.h:202 #18 QV4::Moth::VME::interpret (frame=0x7fff8bcc7840, engine=0x55e9062491d0, code=0x7fb2829b0538 "") at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:754 #19 0x7fb292
[plasmashell] [Bug 441408] New: Every time I choose one specific ativity plasma crashes.
https://bugs.kde.org/show_bug.cgi?id=441408 Bug ID: 441408 Summary: Every time I choose one specific ativity plasma crashes. Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kevin.coo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.12-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Doesn't really matter, as soon as I end up on my "admin" activity (where Yast2 is, some easy links to Linux, openSUSE, KDE, etc. documentation. There were (I thought I got rid the suspect ones) several plasmoids / widgets on my desktop. I nixed most of them, but suspect there is someone still lurking there so that when I change context / break of containment etc. (good idea--better if it worked!) and end up on my 'admin' activity it crashes. - Unusual behavior I noticed: My entire desktop vanishes, I accidentally figured out that krunner survives (alt+F2) so I was still able to get some work on a critical DB job done. If I clicked on an open app, I could get suck into that activity, but I had no way to navigate beyond what was in the activity via alt+tab (i.e. right clicking on desktop didn't do anything, Windows key didn't fire up, etc.) - Custom settings of the application: This is the best I can come up with (having a way to automatically attach relevant config files might be a "nice to have" feature for the next iteration of Dr. Konqui. This is my plasma-org.kde/plasma.desktop-apletetsrc:: [ActionPlugins][0] MiddleButton;NoModifier=org.kde.paste RightButton;NoModifier=org.kde.contextmenu wheel:Vertical;NoModifier=org.kde.switchdesktop [ActionPlugins][1] RightButton;NoModifier=org.kde.contextmenu [Containments][1] ItemGeometries-3840x2160= ItemGeometriesHorizontal= activityId=1a2ea874-b033-4ce0-8b06-12558fb97ca6 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][1][Configuration] PreloadWeight=42 [Containments][1][Wallpaper][org.kde.image][General] Image=file:///usr/share/wallpapers/openSUSEdefault/contents/images/1920x1080.jpg [Containments][2] ItemGeometries-1920x1080= ItemGeometriesHorizontal= activityId=1a2ea874-b033-4ce0-8b06-12558fb97ca6 formfactor=0 immutability=1 lastScreen=1 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][2][Configuration] PreloadWeight=42 [Containments][2][Wallpaper][org.kde.image][General] Image=file:///usr/share/wallpapers/openSUSEdefault/contents/images/1920x1080.jpg [Containments][3] activityId= formfactor=2 immutability=1 lastScreen=1 location=4 plugin=org.kde.panel wallpaperplugin=org.kde.image [Containments][3][Applets][20] immutability=1 plugin=org.kde.plasma.digitalclock [Containments][3][Applets][20][Configuration] PreloadWeight=42 [Containments][3][Applets][21] immutability=1 plugin=org.kde.plasma.showdesktop [Containments][3][Applets][21][Configuration] PreloadWeight=42 [Containments][3][Applets][4] immutability=1 plugin=org.kde.plasma.kickoff [Containments][3][Applets][4][Configuration] PreloadWeight=92 [Containments][3][Applets][4][Configuration][General] favorites=preferred://browser,/usr/share/applications/org.kde.kontact.desktop,/usr/share/applications/writer.desktop,/usr/share/applications/kde4/org.kde.amarok.desktop,/usr/share/applications/org.kde.digikam.desktop,/usr/share/applications/org.kde.dolphin.desktop,/usr/share/applications/systemsettings.desktop,/usr/share/applications/org.kde.Help.desktop,/usr/share/applications/org.kde.konsole.desktop favoritesPortedToKAstats=true [Containments][3][Applets][4][Configuration][Shortcuts] global=Alt+F1 [Containments][3][Applets][4][Shortcuts] global=Alt+F1 [Containments][3][Applets][5] immutability=1 plugin=org.kde.plasma.pager [Containments][3][Applets][5][Configuration] PreloadWeight=42 [Containments][3][Applets][6] immutability=1 plugin=org.kde.plasma.icontasks [Containments][3][Applets][6][Configuration] PreloadWeight=42 [Containments][3][Applets][7] immutability=1 plugin=org.kde.plasma.marginsseparator [Containments][3][Applets][7][Configuration] PreloadWeight=42 [Containments][3][Applets][8] immutability=1 plugin=org.kde.plasma.systemtray [Containments][3][Applets][8][Configuration] PreloadWeight=47 SystrayContainmentId=9 [Containments][3][Configuration] PreloadWeight=42 [Containments][3][General] AppletOrder=4;5;6;7;8;20;21 [Containments][9] activityId= formfactor=2 immutability=1 lastScreen=1 location
[plasmashell] [Bug 474919] New: plasma crashes on start
https://bugs.kde.org/show_bug.cgi?id=474919 Bug ID: 474919 Summary: plasma crashes on start Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kevin.coo...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 5.14.21-150500.55.19-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Plasma desktop using X11 will load, including desktop widgets and wall paper. Then it restarts. It will attempt this a few times before calling it quits. The same behavior is noted if I try to restart w/ kdeinit5 plasmashell. Unfortunately, I recently updated my KDE and added a bunch of desktop widgets. I will see if it repeats w/ Wayland. I did something yeterday that gave me a stable desktop, but I cannot for the life of me remember what it was (I cannot remove desktop widgets to exclude them as the cause of a segfault). I can still launch programs via alt+F2 and they run fine, and (fortunately) my Latte task bar still works. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 QOpenGLContext::surface (this=this@entry=0x0) at kernel/qopenglcontext.cpp:1078 #5 0x7f07b5c4809f in qsg_device_pixel_ratio (ctx=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/scenegraph/qsgdefaultglyphnode_p.cpp:99 #6 QSGTextMaskMaterial::updateCache (this=0x55b34b12d8d0, glyphFormat=QFontEngine::Format_A32) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/scenegraph/qsgdefaultglyphnode_p.cpp:781 #7 0x7f07b5c455c8 in QSGDefaultGlyphNode::update (this=0x55b34b1a5c50) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/scenegraph/qsgdefaultglyphnode.cpp:107 #8 0x7f07b5cdf0a9 in QQuickTextNode::addGlyphs (this=this@entry=0x55b34b325a00, position=..., glyphs=..., color=..., style=style@entry=QQuickText::Normal, styleColor=..., parentNode=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquicktextnode.cpp:117 #9 0x7f07b5ce455c in QQuickTextNodeEngine::addToSceneGraph (this=this@entry=0x7ffe03629120, parentNode=parentNode@entry=0x55b34b325a00, style=style@entry=QQuickText::Normal, styleColor=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquicktextnodeengine.cpp:793 #10 0x7f07b5ce01ea in QQuickTextNode::addTextLayout (this=this@entry=0x55b34b325a00, position=..., textLayout=textLayout@entry=0x55b34b132e68, color=..., style=QQuickText::Normal, styleColor=..., anchorColor=..., selectionColor=..., selectedTextColor=..., selectionStart=-1, selectionEnd=-1, lineStart=0, lineCount=1) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquicktextnode.cpp:287 #11 0x7f07b5cdebef in QQuickText::updatePaintNode (this=0x55b34b471e80, oldNode=, data=) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquicktext.cpp:2500 #12 0x7f07b5cc1d38 in QQuickWindowPrivate::updateDirtyNode (this=this@entry=0x55b348947f70, item=item@entry=0x55b34b471e80) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquickwindow.cpp:3895 #13 0x7f07b5cc25c3 in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55b348947f70) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquickwindow.cpp:3640 #14 0x7f07b5cc3aed in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x55b348947f70) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquickwindow.cpp:524 #15 0x7f07b5c413a8 in QSGGuiThreadRenderLoop::renderWindow (this=0x55b34663f830, window=) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/scenegraph/qsgrenderloop.cpp:752 #16 0x7f07b5ccfca8 in QQuickWindow::event (this=0x55b3472cc780, e=0x7ffe0362bc00) at /usr/src/debug/libqt5-qtdeclarative-5.15.10+kde26-lp155.1.3.x86_64/src/quick/items/qquickwindow.cpp:1865 #17 0x7f07b4dab81c in QApplicationPrivate::notify_helper (this=this@entry=0x55b345c2e510, receiver=receiver@entry=0x55b3472cc780, e=e@entry=0x7ffe0362bc00) at kernel/qapplication.cpp:3640 #18 0x7f07b4db25df in QApplication::notify (this=, receiver=0x55b3472cc780, e=0x7ffe0362bc00) at kernel/qapplication.cpp:3164 #19 0x7f07b3fde4e3 in QCoreApplication::notifyInternal2 (receiver=0x55b3472cc780, event=0x7ffe0362bc00) at kernel/qcoreappl
[plasmashell] [Bug 474919] plasma crashes on start
https://bugs.kde.org/show_bug.cgi?id=474919 Kevin Coonan changed: What|Removed |Added CC||kevin.coo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474919] plasma crashes on start
https://bugs.kde.org/show_bug.cgi?id=474919 --- Comment #4 from Kevin Coonan --- Created attachment 163478 --> https://bugs.kde.org/attachment.cgi?id=163478&action=edit New crash information added by DrKonqi plasmashell (5.27.9) using Qt 5.15.11 Still keeps crashing, and if I can get it to stay up long enough I will try and make sure all my widgets are gone. It will start up, show my desktop (somewhat--shows the folder view for a few moments, not quite a second, and then tanks again. -- Backtrace (Reduced): #4 QOpenGLContext::surface() const (this=this@entry=0x0) at kernel/qopenglcontext.cpp:1078 #5 0x7f982ab8fcbf in qsg_device_pixel_ratio (ctx=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.3.x86_64/src/quick/scenegraph/qsgdefaultglyphnode_p.cpp:99 #6 QSGTextMaskMaterial::updateCache(QFontEngine::GlyphFormat) (this=0x55ddbaa72490, glyphFormat=QFontEngine::Format_A32) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.3.x86_64/src/quick/scenegraph/qsgdefaultglyphnode_p.cpp:781 #7 0x7f982ab8d1e8 in QSGDefaultGlyphNode::update() (this=0x55ddba8255c0) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.3.x86_64/src/quick/scenegraph/qsgdefaultglyphnode.cpp:107 #8 0x7f982ac26b89 in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) (this=this@entry=0x55ddbbdc4800, position=..., glyphs=..., color=..., style=style@entry=QQuickText::Normal, styleColor=..., parentNode=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.3.x86_64/src/quick/items/qquicktextnode.cpp:117 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476529] New: Plasma Crashes (Again) when I try and use the klippboard widget
https://bugs.kde.org/show_bug.cgi?id=476529 Bug ID: 476529 Summary: Plasma Crashes (Again) when I try and use the klippboard widget Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kevin.coo...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 5.14.21-150500.55.31-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: Whenever I have used the clipboard history to try and access something clever I previously clipped plastma crashes and the data does not transfer, i.e. I cannot then paste it even if I selected it. I can scroll the history, and I can click on the little bitty icons, but when it comes time to cough up the data is splats. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f8e4b14ad2b in raise () at /lib64/libc.so.6 #5 0x7f8e4b14c3e5 in abort () at /lib64/libc.so.6 #6 0x7f8e4b5f56bb in qt_message_fatal (context=, message=...) at global/qlogging.cpp:1919 #7 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffe52afc050, msg=msg@entry=0x7f8e4d0abe18 "Object %p destroyed while one of its QML signal handlers is in progress.\nMost likely the object was deleted synchronously (use QObject::deleteLater() instead), or the application is running a nested e"...) at global/qlogging.cpp:898 #8 0x7f8e4cf7f4b7 in QQmlData::destroyed(QObject*) (this=, object=0x5565cc9de370) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.2.x86_64/src/qml/qml/qqmlengine.cpp:1960 #9 0x7f8e4b84e5ea in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1019 #10 0x7f8e4d4e5a4d in QQuickItem::~QQuickItem() (this=0x5565cc9de370, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.2.x86_64/src/quick/items/qquickitem.cpp:2327 #11 0x7f8e43882fbd in () at /usr/lib64/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #12 0x7f8e4b847835 in QObject::event(QEvent*) (this=this@entry=0x5565cc9de370, e=e@entry=0x7f8e3000fd90) at kernel/qobject.cpp:1334 #13 0x7f8e4d4e773b in QQuickItem::event(QEvent*) (this=0x5565cc9de370, ev=0x7f8e3000fd90) at /usr/src/debug/libqt5-qtdeclarative-5.15.11+kde30-lp155.1.2.x86_64/src/quick/items/qquickitem.cpp:8337 #14 0x7f8e4c5e081c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5565ba160910, receiver=receiver@entry=0x5565cc9de370, e=e@entry=0x7f8e3000fd90) at kernel/qapplication.cpp:3640 #15 0x7f8e4c5e75df in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x5565cc9de370, e=0x7f8e3000fd90) at kernel/qapplication.cpp:3164 #16 0x7f8e4b813953 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5565cc9de370, event=0x7f8e3000fd90) at kernel/qcoreapplication.cpp:1064 #17 0x7f8e4b813b2e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=receiver@entry=0x5565cc9de370, event=event@entry=0x7f8e3000fd90) at kernel/qcoreapplication.cpp:1462 #18 0x7f8e4b816371 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5565ba13a0d0) at kernel/qcoreapplication.cpp:1821 #19 0x7f8e4b8168f8 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #20 0x7f8e4b8766d3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5565ba2a27f0) at kernel/qeventdispatcher_glib.cpp:277 #21 0x7f8e4952082b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x7f8e49520bd0 in () at /usr/lib64/libglib-2.0.so.0 #23 0x7f8e49520c5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x7f8e4b875d7c in QEventDispatcherGlib::processEvents(QFlags) (this=0x5565ba2b0250, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #25 0x7f8e4b8121ba in QEventLoop::exec(QFlags) (this=0x7ffe52afc7a0, flags=...) at kernel/qeventloop.cpp:235 #26 0x7f8e4c297295 in KJob::exec() () at /usr/lib64/libKF5CoreAddons.so.5 #27 0x7f8e4a168fab in KIO::AccessManager::createRequest(QNetworkAccessManager::Operation, QNetworkRequest const&, QIODevice*) () at /usr/lib64/libKF5KIOWidgets.so.5 #28 0x7f8e4aa98e45 in QNetworkAccessManager::get(QNetworkRequest const&) () at /usr/lib64/libQt5Network.so.5 #29 0x7f8e4d031e6b in QQmlXMLHttpRequest::requestFromUrl(QUrl const&) (this=this@entry=0x5565cde8a670, url=...) at /usr/src/debug
[kmenuedit] [Bug 461844] New: Menu editor crashes SOME OF THE TIME when I save
https://bugs.kde.org/show_bug.cgi?id=461844 Bug ID: 461844 Summary: Menu editor crashes SOME OF THE TIME when I save Classification: Applications Product: kmenuedit Version: 5.26.2 Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kevin.coo...@gmail.com Target Milestone: --- Application: kmenuedit (5.26.2) Qt Version: 5.15.7 Frameworks Version: 5.99.0 Operating System: Linux 6.0.7-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.2 [KCrashBackend] -- Information about the crash: It crashed after I did a HUGE edit. I tried it with a simple edit, no problem. Then, with a medium size change it crashed again. I think it waits until you have done enough changes to represent enough effort to really piss you off when you go to save and then lose all that work. The crash can be reproduced sometimes. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault [KCrash Handler] #4 0x7ff4a6cc6390 in KService::desktopEntryName() const () from /lib64/libKF5Service.so.5 #5 0x55d5ccfbde69 in ?? () #6 0x55d5ccfc941e in ?? () #7 0x55d5ccfce301 in ?? () #8 0x7ff4a551354c in doActivate (sender=0x55d5cd934d70, signal_index=4, argv=0x7ffe3406ebd0) at kernel/qobject.cpp:3931 #9 0x7ff4a619ebb2 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #10 0x7ff4a61a16fb in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #11 0x7ff4a6298c4a in ?? () from /lib64/libQt5Widgets.so.5 #12 0x7ff4a6298d97 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7ff4a63913aa in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7ff4a61e6c38 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7ff4a61a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7ff4a61ad922 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7ff4a54dc128 in QCoreApplication::notifyInternal2 (receiver=0x55d5cd9751e0, event=0x7ffe3406f150) at kernel/qcoreapplication.cpp:1064 #18 0x7ff4a61aba9e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #19 0x7ff4a61ffa58 in ?? () from /lib64/libQt5Widgets.so.5 #20 0x7ff4a6202fb0 in ?? () from /lib64/libQt5Widgets.so.5 #21 0x7ff4a61a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7ff4a54dc128 in QCoreApplication::notifyInternal2 (receiver=0x55d5cda5a330, event=0x7ffe3406f400) at kernel/qcoreapplication.cpp:1064 #23 0x7ff4a597b9ad in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #24 0x7ff4a594f37c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #25 0x7ff4a0d1a0fa in ?? () from /lib64/libQt5XcbQpa.so.5 #26 0x7ff4a3bc0a90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x7ff4a3bc0e48 in ?? () from /lib64/libglib-2.0.so.0 #28 0x7ff4a3bc0edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x7ff4a5533b56 in QEventDispatcherGlib::processEvents (this=0x55d5cd50fb80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7ff4a54dab9b in QEventLoop::exec (this=this@entry=0x7ffe3406f730, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #31 0x7ff4a54e2d06 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #32 0x55d5ccfb7c04 in ?? () #33 0x7ff4a4c2c5b0 in __libc_start_call_main () from /lib64/libc.so.6 #34 0x7ff4a4c2c679 in __libc_start_main_impl () from /lib64/libc.so.6 #35 0x55d5ccfb8535 in ?? () [Inferior 1 (process 15396) detached] The reporter indicates this bug may be a duplicate of or related to bug 212990, bug 426822, bug 450553. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 376490] New: KDE5 does not allow configuration of units of measure, time, or date format separate from the single value allowed by locale
https://bugs.kde.org/show_bug.cgi?id=376490 Bug ID: 376490 Summary: KDE5 does not allow configuration of units of measure, time, or date format separate from the single value allowed by locale Product: kdelibs Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: klocale Assignee: caslav.i...@gmx.net Reporter: kevin.coo...@gmail.com Target Milestone: --- Users in a given locale have different requirements for date-time format and use of units. In the United States, in spite of many (if not a majority) clinging to the Imperial units of measure, many communities (e.g. military, medicine, science, transportation, weather) routinely use ISO date-time and/or metric units of measure. Different communities have different per-measurement-type preferences (e.g. in medicine we use mm and cm quite a bit, km not so much) even within the broad scope of the metric system. This is a solved problem, with well described options. For example, while units of measurement were limited to what the OS actually used (quite reasonable), KDE4 let me configure use of ISO date-time values system wide. KDE5 apparently ignored this rather significant user requirement. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 378381] New: Help --> About KDE doesn't show information about installed KDE
https://bugs.kde.org/show_bug.cgi?id=378381 Bug ID: 378381 Summary: Help --> About KDE doesn't show information about installed KDE Product: frameworks-plasma Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: kevin.coo...@gmail.com Target Milestone: --- I might be crazy, but I seem to recall that in KDE4 selecting "About KDE" actually told you something about the installed KDE platform. E.g. version of major components. Use case: I want to install a new desktop theme designed to run with Plasma 5.9. I would try and install it, but only if I knew that I was running Plasma 5.9 or later. This should be easy, and it would make support quite a bit more straight forward. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 378381] Help --> About KDE doesn't show information about installed KDE
https://bugs.kde.org/show_bug.cgi?id=378381 --- Comment #2 from Kevin Coonan --- Not exactly. I use openSUSE w/ Zypper, so I live in the world of a million repositories. I try, very hard, to use a single repo for all my KDE apps, as past experience has shown that even the exact same version, from different repo (different build/linking???) of a component that differs from the rest can crash plasma. Being able to check and see that I am at lease using the same version of KMail, Konqeror (which I still like better than Dolphin, esp. once all the icon display, text menu display, loss of side bar, screwed up time/date format and all the other KDE4->KDE5/Qt5 regressions are fixed...ahem), KOrganizer, etc. etc. Part of this is my own making, but there are apps in various repos not in the standard build ones that I need, or versions which fix problems or add functionality I need. How hard would it be to show the Qt version, KDE framework version, Plasma version, and application version? It would avoild 95% of my bug reports which come back to me with some snooty email that tells me that I shouldn't mix and match component versions (a consitant versioning, or at least letting users know which versions of the various applications will work together would be fantastic) and to switch some component to the same repo the others came from. openSUSE doesn't do a great job with letting you know this--I think Zypper just trusts whatever the required version of some dependency is based on the documentation developers provide, but is confusing as hell to have some common application listed 5 times and having to dig into the repo, dependency, and versioning info to figure out which version of Akonadi I need. Don't get me wrong, I am not going to go back to one of the RedHat or Debian/Ubuntu flavors, and don't have time for Arch--I really like openSUSE esp. with OBS working and Tumbleweed. YaST and Zypper are awesome, but make it too easy to get into dependency issues that can be subtle and heard to track down if you cannot read the crash reports yourself. Thanks, Kevin Coonan, MD On Thu, Apr 20, 2017 at 6:35 PM Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=378381 > > Christoph Feck changed: > >What|Removed |Added > > > Status|UNCONFIRMED |RESOLVED > Resolution|--- |DUPLICATE > > --- Comment #1 from Christoph Feck --- > Please read bug 351337 comment #9. > > *** This bug has been marked as a duplicate of bug 351337 *** > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363047] New: Crash on login
https://bugs.kde.org/show_bug.cgi?id=363047 Bug ID: 363047 Summary: Crash on login Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kevin.coo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Just logged in to system. Has been doing this since installation. Have tried to consolidate KDE applications into a single repo, but there is no clear guidance on which version of KDE applications should be installed. The transition KDE4-KDE5 is NOT GOING WELL from a user perspective. Where is the documentation that would tell me which packages should be installed to create a working desktop w/ Plasma5, etc.? Why is the menu structure (when it actually shows up, rather than blank black screen) all messed up? Why is it so hard to actually run KDE?!? The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5161da7800 (LWP 2727))] Thread 9 (Thread 0x7f514a5ca700 (LWP 2730)): #0 0x7f515b2cdbbd in poll () at /lib64/libc.so.6 #1 0x7f5160221422 in () at /usr/lib64/libxcb.so.1 #2 0x7f516022300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f514cd4d3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f515b9c832f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f5156df0754 in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7f515b2d5fed in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f51433ea700 (LWP 2737)): #0 0x7f515b2cdbbd in poll () at /lib64/libc.so.6 #1 0x7f51579a8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f51579a8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f515bbfad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f515bba1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f515b9c361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f515ecd7e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f515b9c832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f5156df0754 in () at /usr/X11R6/lib64/libGL.so.1 #9 0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f515b2d5fed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f513635e700 (LWP 2738)): #0 0x7f515b2cdbbd in poll () at /lib64/libc.so.6 #1 0x7f51579a8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f51579a8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f515bbfad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f515bba1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f515b9c361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f515ecd7e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f515b9c832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f5156df0754 in () at /usr/X11R6/lib64/libGL.so.1 #9 0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f515b2d5fed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f5134bb2700 (LWP 2739)): #0 0x7f515b2cdbbd in poll () at /lib64/libc.so.6 #1 0x7f51579a8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f51579a8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f515bbfad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f515bba1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f515b9c361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f515ecd7e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f515b9c832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f5156df0754 in () at /usr/X11R6/lib64/libGL.so.1 #9 0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f515b2d5fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f512f1cf700 (LWP 2740)): #0 0x7f515aadb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f51614a686b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f51614a6899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f5156df0754 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f515b2d5fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f50a7fff700 (LWP 2757)): #0 0x000
[plasmashell] [Bug 362760] New: Crash on start, display blurry, no KDE components
https://bugs.kde.org/show_bug.cgi?id=362760 Bug ID: 362760 Summary: Crash on start, display blurry, no KDE components Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kevin.coo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Logged on as normal user. No activity bar, wallpaper, or desktop items (basically a black screen with a blurry menu to restart konqueror). I can launch applications (e.g. Konsole) via KRunner. kevin@pyrope:~> uname -a Linux pyrope 4.1.20-11-default #1 SMP PREEMPT Fri Mar 18 14:42:07 UTC 2016 (0a392b2) x86_64 x86_64 x86_64 GNU/Linux System info: kevin@pyrope:~> sudo lshw pyrope description: Desktop Computer product: All Series (All) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-2.7 dmi-2.7 vsyscall32 configuration: administrator_password=disabled boot=normal chassis=desktop family=ASUS MB frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=All uuid=804BD91E-DAD7-DD11-AE3F-AC220BBF7D30 *-core description: Motherboard product: Z87I-DELUXE vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 130714197600059 slot: To be filled by O.E.M. *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 1204 date: 11/26/2014 size: 64KiB capacity: 8128KiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory:0 UNCLAIMED physical id: 1 *-bank UNCLAIMED description: DIMM DDR3 Synchronous 1600 MHz (0.6 ns) product: DDR3 1600G vendor: Fujitsu physical id: 0 serial: 2887 slot: ChannelA-DIMM0 size: 8GiB width: 64 bits clock: 1600MHz (0.6ns) *-memory:1 description: System Memory physical id: 39 slot: System board or motherboard *-bank description: DIMM DDR3 Synchronous 1600 MHz (0.6 ns) product: DDR3 1600G vendor: Fujitsu physical id: 0 serial: 284C slot: ChannelB-DIMM0 size: 8GiB width: 64 bits clock: 1600MHz (0.6ns) *-cache:0 description: L1 cache physical id: 3e slot: CPU Internal L1 size: 256KiB capacity: 256KiB capabilities: internal write-back *-cache:1 description: L2 cache physical id: 3f slot: CPU Internal L2 size: 1MiB capacity: 1MiB capabilities: internal write-back unified *-cache:2 description: L3 cache physical id: 40 slot: CPU Internal L3 size: 8MiB capacity: 8MiB capabilities: internal write-back unified *-cpu description: CPU product: (Fill By OEM) vendor: Intel Corp. physical id: 4d bus info: cpu@0 version: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz slot: SOCKET 1150 size: 3392MHz capacity: 3900MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt cpufreq configuration: cores=4 enabledcores=4 threads=8 *-memory:2 UNCLAIMED physical id: 2 *-memory:3 UNCLAIMED physical id: 3 *-pci description: Host bridge product: 4th Gen Core Processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:0
[trojita] [Bug 359545] New: cannot access GMail: Too many commands before auth
https://bugs.kde.org/show_bug.cgi?id=359545 Bug ID: 359545 Summary: cannot access GMail: Too many commands before auth Product: trojita Version: 0.5 Platform: openSUSE RPMs URL: imap.gmail.com OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: kevin.coo...@gmail.com When attempting to connect to GMail I receive an error: "Too many commands before auth [some string of alphanumerics]"and 9(!) popups saying "The server sent the following ALERT: Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)". I am attempting to connect via "Network Connection" (which works, BTW, and I have used many other IMAP clients to connect to GMail with these same settings. I can access via web browser and have been through GMail's trouble shooting) to imap.gmail.com on 993 with "Forced encryption (TLS)". My refresh interval is increased to 15min to avoid any issues w/ too frequent connection attempts. NB: Connection settings work fine w/ my ISP provided email services. Reproducible: Always Steps to Reproduce: 1. Attempt to connect to GMail Actual Results: My log shows: 12:35:30.837 Network Session Switched to network configuration IWantAPuppy (WLAN, /org/freedesktop/NetworkManager/Settings/4) 12:35:30.837 Network Session Opening network session 12:35:30.837 Network Session Session is open (configuration[my home WiFi]), online state:online 12:35:31.967 Imap::Mailbox::ListChildMailboxesTask Listing stuff below mailbox Failed: The connection is being killed for unspecified reason 12:35:31.967 Imap::Mailbox::GetAnyConnectionTask Failed: The connection is being killed for unspecified reason Expected Results: Reading my email Using openSuSE 42.1 (same problem under KDE Plasma, LXQt and RazorQT). -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 359546] New: need to manage multiple accounts
https://bugs.kde.org/show_bug.cgi?id=359546 Bug ID: 359546 Summary: need to manage multiple accounts Product: trojita Version: 0.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: kevin.coo...@gmail.com Why only one account? Most people have many email accounts. Reproducible: Always Expected Results: Add as many IMAP accounts + their corresponding identity and SMTP settings as needed. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 359588] New: KMenu editor crashes
https://bugs.kde.org/show_bug.cgi?id=359588 Bug ID: 359588 Summary: KMenu editor crashes Product: kmenuedit Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kevin.coo...@gmail.com Application: kmenuedit (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.17-4.g9550abf-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying to restore the categories (submenus) by hand which are missing w/ KF5. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7fa622da1df7 in KSycocaEntry::entryPath() const () at /usr/lib64/libKF5Service.so.5 #7 0x7fa6244bb24c in () at /usr/lib64/libkdeinit5_kmenuedit.so #8 0x7fa6244a8526 in () at /usr/lib64/libkdeinit5_kmenuedit.so #9 0x7fa6244c1b0c in () at /usr/lib64/libkdeinit5_kmenuedit.so #10 0x7fa6201aacc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #11 0x7fa6244c1512 in () at /usr/lib64/libkdeinit5_kmenuedit.so #12 0x7fa6244c1844 in () at /usr/lib64/libkdeinit5_kmenuedit.so #13 0x7fa6201aacc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #14 0x7fa62111928b in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7fa621121d91 in () at /usr/lib64/libQt5Widgets.so.5 #16 0x7fa6201aacc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #17 0x7fa62012f8fa in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () at /usr/lib64/libQt5Core.so.5 #18 0x7fa62012face in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x7fa6210adbf4 in QAbstractItemView::mousePressEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #20 0x7fa6210f1f0a in QTreeView::mousePressEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #21 0x7fa620e9f3ba in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #22 0x7fa620f9943e in QFrame::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #23 0x7fa6210b494b in QAbstractItemView::viewportEvent(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #24 0x7fa6210f1870 in QTreeView::viewportEvent(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #25 0x7fa62017b0d3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #26 0x7fa620e5ee5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #27 0x7fa620e642cb in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #28 0x7fa62017ae95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #29 0x7fa620e63191 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib64/libQt5Widgets.so.5 #30 0x7fa620eb813b in () at /usr/lib64/libQt5Widgets.so.5 #31 0x7fa620eba353 in () at /usr/lib64/libQt5Widgets.so.5 #32 0x7fa620e5ee7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #33 0x7fa620e63cc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #34 0x7fa62017ae95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #35 0x7fa6206cc8d4 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #36 0x7fa6206ce0e5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5 #37 0x7fa6206b31c8 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #38 0x7fa611940200 in () at /usr/lib64/libQt5XcbQpa.so.5 #39 0x7fa61b597c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #40 0x7fa61b597ed8 in () at /usr/lib64/libglib-2.0.so.0 #41 0x7fa61b597f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #42 0x7fa6201d1d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #43 0x7fa620178d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #44 0x7fa6201808f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #45 0x7fa6244a4958 in kdemain () at /usr/lib64/libkdeinit5_kmenuedit.so #46 0x7fa624105b05 in __libc_start_main () at /lib64/libc.so.6 #47 0x004007ee in _start () Reported using DrKonqi
[trojita] [Bug 359545] cannot access GMail: Too many commands before auth
https://bugs.kde.org/show_bug.cgi?id=359545 --- Comment #3 from Kevin Coonan --- I suspect you are right. I am having the same problem with Trojitá. It would seem helpful, given the popularity of GMail, to provide instructions/configuration so people could actually use KMail.* I really prefer it to any other options.* However, if I cannot my email, it isn't quite as useful. It is a huge disappointment that KMail doesn't provide a simple to use wizard/fill in the blank form to connect to GMail. Ditto for Apple's mail/tasks/notes/calendar (iCloud). Instructions for connecting to it are a bit hard to find (I found the WebDAV settings in one of the Apple/iThings fanboy listserv). While I am toying with switching my main email to MyKolab, or self-hosting OX or Kolab, I, and a lot of other people, need to connect to GMail (the world's leading email service). Your users should not have to spend hours trying to set up KMail! Both my (former) iPhone and Android phone *connect out of the box*, with only a few seconds required to put in my account information. KMail (and Trojitá) are both no-shows in this regard. I gave up using C++ years ago, and am not an expert on email services like you are, so there isn't much I can do to add a wizard to do whatever it takes to connect to non-Kolab email servers. *Kevin M. Coonan, M.D.* Minneapolis, MN Skype: kevin.coonan kevin.coo...@gmail.com In the last analysis, we see only what we are ready to see, what we have been taught to see. We eliminate and ignore everything which is not a part of our prejudices. *Jean-Martin Charcot (1825-1893)* On Mon, Feb 22, 2016 at 7:25 AM, Jan Kundrát via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=359545 > > Jan Kundrát changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #2 from Jan Kundrát --- > Please reopen when you have provided the requested information -- this is > very > likely GMail's security feature which allows you to perform some manual > steps. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
