[plasmashell] [Bug 492578] when i tried formatting my fat32 micro sdcard in kde partition manager plasmashell crashed
https://bugs.kde.org/show_bug.cgi?id=492578 --- Comment #4 from pollux/ned --- added a attachment that could be similar to this one, plasma 6.1.5, bazzite -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492578] when i tried formatting my fat32 micro sdcard in kde partition manager plasmashell crashed
https://bugs.kde.org/show_bug.cgi?id=492578 --- Comment #3 from pollux/ned --- Created attachment 174000 --> https://bugs.kde.org/attachment.cgi?id=174000&action=edit got a similar crash possibly again, fedora iso on a usb stick -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493033] plasmashell will crash in Plasma::Corona::editModeChanged() when resizing the weather widget in edit mode
https://bugs.kde.org/show_bug.cgi?id=493033 --- Comment #4 from pollux/ned --- (In reply to Nate Graham from comment #3) > Just this widget? Or does it happen when you resize any other widgets too? well i dont know because i cant replicate the issue anymore..damn it :/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493166] New: cursor doesnt go away in fullscreen games like THE FINALS
https://bugs.kde.org/show_bug.cgi?id=493166 Bug ID: 493166 Summary: cursor doesnt go away in fullscreen games like THE FINALS Classification: Plasma Product: kwin Version: 6.1.90 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: xwayland Assignee: kwin-bugs-n...@kde.org Reporter: pollu...@proton.me Target Milestone: --- SUMMARY When you play a game like THE FINALS the cursor will stay on the screen when clicking on the game when a match starts, if you click on the shortcut it wont do it STEPS TO REPRODUCE 1. Launch the finals 2. Play a random match like powershift for example 3. Click on the game not the shortcut on the panel when the game actually starts 4. Watch the cursor stay on the screen where it was last put OBSERVED RESULT EXPECTED RESULT click on the game and the cursor shouldn't stay where it was last put SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.5.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 493058] Audio becomes distorted when launching a game under proton
https://bugs.kde.org/show_bug.cgi?id=493058 pollux/ned changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 493058] New: Audio becomes distorted when launching a game under proton
https://bugs.kde.org/show_bug.cgi?id=493058 Bug ID: 493058 Summary: Audio becomes distorted when launching a game under proton Classification: Frameworks and Libraries Product: KPipeWire Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me CC: aleix...@kde.org Target Milestone: --- SUMMARY When launching a proton game the audio becomes distorted a lot, i have tried apex legends, the finals, halo, they all distort the audio when being launched STEPS TO REPRODUCE 1. Launch any game under proton 2. Audio becomes distorted 3. Close game to get no audio distorted OBSERVED RESULT Audio becomes distorted until game is closed EXPECTED RESULT not to be distorted when launching a game SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.5.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493033] when resizing the weather widget plasma shell will crash
https://bugs.kde.org/show_bug.cgi?id=493033 --- Comment #1 from pollux/ned --- Created attachment 173594 --> https://bugs.kde.org/attachment.cgi?id=173594&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493033] New: when resizing the weather widget plasma shell will crash
https://bugs.kde.org/show_bug.cgi?id=493033 Bug ID: 493033 Summary: when resizing the weather widget plasma shell will crash Classification: Plasma Product: plasmashell Version: 6.1.90 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me Target Milestone: 1.0 Application: plasmashell (6.1.90) ApplicationNotResponding [ANR]: false Qt Version: 6.8.0 Frameworks Version: 6.5.0 Operating System: Linux 6.10.9-zen1-2-zen x86_64 Windowing System: Wayland Distribution: EndeavourOS DrKonqi: 6.1.90 [CoredumpBackend] -- Information about the crash: at first what happend was adding the weather widget on the desktop would look not look correct, requiring the user to resize it which made plasmashell crash but it shows correctly now on the desktop but resizing it will crash the shell still The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x763f801a4b28 in QQuickItemPrivate::setEffectiveVisibleRecur (this=0x0, newEffectiveVisible=newEffectiveVisible@entry=false) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6589 #6 0x763f801a4c07 in QQuickItemPrivate::setEffectiveVisibleRecur (this=0x626c4077d640, newEffectiveVisible=newEffectiveVisible@entry=false) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6609 #7 0x763f801a4c07 in QQuickItemPrivate::setEffectiveVisibleRecur (this=0x626c49cb7030, newEffectiveVisible=newEffectiveVisible@entry=false) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6609 #8 0x763f801a4c07 in QQuickItemPrivate::setEffectiveVisibleRecur (this=0x626c525c4dc0, newEffectiveVisible=newEffectiveVisible@entry=false) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6609 #9 0x763f801a4c07 in QQuickItemPrivate::setEffectiveVisibleRecur (this=0x626c50bafc70, newEffectiveVisible=newEffectiveVisible@entry=false) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6609 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492578] when i tried formatting my fat32 micro sdcard in kde partition manager plasmashell crashed
https://bugs.kde.org/show_bug.cgi?id=492578 --- Comment #1 from pollux/ned --- Created attachment 173266 --> https://bugs.kde.org/attachment.cgi?id=173266&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492578] New: when i tried formatting my fat32 micro sdcard in kde partition manager plasmashell crashed
https://bugs.kde.org/show_bug.cgi?id=492578 Bug ID: 492578 Summary: when i tried formatting my fat32 micro sdcard in kde partition manager plasmashell crashed Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me Target Milestone: 1.0 Application: plasmashell (6.1.4) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.7-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.4 [CoredumpBackend] -- Information about the crash: similar to the other crash i had when plugging in my usb stick but with kde partition manager instead The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x7361e68813d1 in QQmlContextData::contextObject (this=, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:128 #6 QQmlContextData::ContextGuard::objectDestroyedImpl (impl=0x55a6829c2a78) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:455 #7 0x7361e688f2d2 in QQmlData::destroyed (this=0x55a685835a70, object=0x55a685835a50) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1415 #8 0x7361e5591ffe in QObject::~QObject (this=0x55a685835a50, this=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1078 #9 0x7361e6fd88f3 in QQuickImplicitSizeItem::~QQuickImplicitSizeItem (this=0x55a685835a50, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickimplicitsizeitem_p.h:24 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492356] plugging in a fat32 micro sd card usb stick crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=492356 --- Comment #6 from pollux/ned --- (In reply to Akseli Lahtinen from comment #5) > Can't repro either, but the Qml related symbols makes me wonder if this is > related to the notification somehow. > > Do you have desktop widgets that have USB information? Or widgets downloaded > from the widget store? nope no third party widgets or any widgets on the desktop, i cant reproduce it either anymore :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492356] plugging in a fat32 micro sd card usb stick crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=492356 --- Comment #3 from pollux/ned --- Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7b7f976a9a00 (LWP 21577))] (gdb) backtrace #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7b7f9dca5463 in __pthread_kill_internal (threadid=, signo=11) at pthread_kill.c:78 #2 0x7b7f9dc4c120 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7b7fa0268711 in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash/kcrash-6.5.0/src/kcrash.cpp:606 #4 0x7b7f9dc4c1d0 in () at /usr/lib/libc.so.6 #5 0x7b7f9ea813d1 in QQmlContextData::contextObject (this=, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:128 #6 QQmlContextData::ContextGuard::objectDestroyedImpl (impl=0x56f83f1b9cf8) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:455 #7 0x7b7f9ea8f2d2 in QQmlData::destroyed (this=0x56f843238c60, object=0x56f843238c40) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1415 #8 0x7b7f9d791ffe in QObject::~QObject (this=0x56f843238c40, this=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1078 #9 0x7b7f9f1d88f3 in QQuickImplicitSizeItem::~QQuickImplicitSizeItem (this=0x56f843238c40, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickimplicitsizeitem_p.h:24 #10 QQuickLoader::~QQuickLoader (this=0x56f843238c40, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickloader.cpp:281 #11 QQmlPrivate::QQmlElement::~QQmlElement (this=0x56f843238c40, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlprivate.h:100 #12 QQmlPrivate::QQmlElement::~QQmlElement (this=0x56f843238c40, this=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlprivate.h:100 is this what you need? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492356] plugging in a fat32 micro sd card usb stick crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=492356 --- Comment #1 from pollux/ned --- Created attachment 173081 --> https://bugs.kde.org/attachment.cgi?id=173081&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492356] New: plugging in a fat32 micro sd card usb stick crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=492356 Bug ID: 492356 Summary: plugging in a fat32 micro sd card usb stick crashes plasmashell Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me Target Milestone: 1.0 Application: plasmashell (6.1.4) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.6-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.4 [CoredumpBackend] -- Information about the crash: i had been using a fat32 micro sd card in a usb stick to put some games on it and everytime i plugged in the stick plasmashell would crash once every 2 or 3 times i did it The crash can be reproduced sometimes. -- Backtrace (Reduced): Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389281] qml errors persist in systemsettings5 making it unusable.
https://bugs.kde.org/show_bug.cgi?id=389281 --- Comment #10 from Ned --- (In reply to Ned from comment #9) > Similar or possibly same issue on Tuxedo OS. > > Display config: "Error loading QML file. > > qrc:/kcm/kcm_kscreen/main.qml:151 Type Kirigami.InlineMessage unavailable > file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/InlineMessage.qml: > 63 Type KT.InlineMessage unavailable > qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign > object of type "TP.IconPropertiesGroup" to property of type > "IconPropertiesGroup_QMLTYPE_80*" as the former is neither the same as the > latter nor a sub-class of it." > > Sound settings: "Error loading QML file. > > qrc:/kcm/kcm_pulseaudio/main.qml:366 Type Kirigami.InlineMessage unavailable > file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/InlineMessage.qml: > 63 Type KT.InlineMessage unavailable > qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign > object of type "TP.IconPropertiesGroup" to property of type > "IconPropertiesGroup_QMLTYPE_80*" as the former is neither the same as the > latter nor a sub-class of it." > > System basics: > > Operating System: TUXEDO OS 3 > KDE Plasma Version: 6.1.4 > KDE Frameworks Version: 6.5.0 > Qt Version: 6.7.2 > Kernel Version: 6.8.0-101041-tuxedo (64-bit) > Graphics Platform: Wayland Huh. It's working now. Just fixed itself. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389281] qml errors persist in systemsettings5 making it unusable.
https://bugs.kde.org/show_bug.cgi?id=389281 Ned changed: What|Removed |Added CC||nedretherbr...@gmail.com --- Comment #9 from Ned --- Similar or possibly same issue on Tuxedo OS. Display config: "Error loading QML file. qrc:/kcm/kcm_kscreen/main.qml:151 Type Kirigami.InlineMessage unavailable file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type KT.InlineMessage unavailable qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign object of type "TP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_80*" as the former is neither the same as the latter nor a sub-class of it." Sound settings: "Error loading QML file. qrc:/kcm/kcm_pulseaudio/main.qml:366 Type Kirigami.InlineMessage unavailable file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type KT.InlineMessage unavailable qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign object of type "TP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_80*" as the former is neither the same as the latter nor a sub-class of it." System basics: Operating System: TUXEDO OS 3 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-101041-tuxedo (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489381] plasmashell crashes when updating with paru
https://bugs.kde.org/show_bug.cgi?id=489381 --- Comment #1 from pollux/ned --- Created attachment 171134 --> https://bugs.kde.org/attachment.cgi?id=171134&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489381] New: plasmashell crashes when updating with paru
https://bugs.kde.org/show_bug.cgi?id=489381
Bug ID: 489381
Summary: plasmashell crashes when updating with paru
Classification: Plasma
Product: plasmashell
Version: 6.1.1
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: pollu...@proton.me
Target Milestone: 1.0
Application: plasmashell (6.1.1)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.7-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: Garuda Linux
DrKonqi: 6.1.1 [CoredumpBackend]
-- Information about the crash:
this has happened quite a bit over the past week, whenever doing a paru or
flatpak update plasmashell will crash
this probs have been reported already lol
The crash can be reproduced sometimes.
-- Backtrace (Reduced):
#5 0x7fd98cd79b0e in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x5a45bc7f5c20) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.1.1/applets/kicker/plugin/kastatsfavoritesmodel.cpp:196
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::FunctorCallable::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x5a45bc7f5c10, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9 0x7fd9bb38c00f in QObject::event (this=0x5a45bc8f7830,
e=0x5a45c46e4bf0) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1452
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 477641] Displays wake up right after locking the screens and going to sleep
https://bugs.kde.org/show_bug.cgi?id=477641 --- Comment #13 from ned --- Created attachment 170568 --> https://bugs.kde.org/attachment.cgi?id=170568&action=edit battery icon Just adding here because I struggled to find this anywhere else in a search. If you click the battery icon in the system tray, then if anything is blocking sleep, it should show up at the top of that window, like Mixxx in the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488348] New: kwin_wayland crash (core dump)
https://bugs.kde.org/show_bug.cgi?id=488348 Bug ID: 488348 Summary: kwin_wayland crash (core dump) Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: naught...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY kwin_wayland randomly crashes, sending me back to the login screen, and killing all apps STEPS TO REPRODUCE 1. No apparent trigger, occurs every few days OBSERVED RESULT Crash EXPECTED RESULT Don't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable/13/trixie (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 8 × Intel® Core™ i5-8259U CPU @ 2.30GHz Mesa Intel® Iris® Plus Graphics 655 ADDITIONAL INFORMATION crash info from DrKonqi: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 38716 (kwin_wayland) UID: 1000 (naught101) GID: 1000 (naught101) Signal: 11 (SEGV) Timestamp: Tue 2024-06-11 21:48:31 AEST (3min 50s ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_xUrHnb --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (naught101) Boot ID: f71a0c31a2214f65abdf516a3d3b73d9 Machine ID: a655ca69bed9425eaf5748c0f9465c6b Hostname: naught-dnuc Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.f71a0c31a2214f65abdf516a3d3b73d9.38716.171810651100.zst (inaccessible) Message: Process 38716 (kwin_wayland) of user 1000 dumped core. Module libblkid.so.1 from deb util-linux-2.40.1-3.amd64 Module libsystemd.so.0 from deb systemd-256~rc3-5.amd64 Module libmount.so.1 from deb util-linux-2.40.1-3.amd64 Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64 Module libudev.so.1 from deb systemd-256~rc3-5.amd64 Stack trace of thread 38716: #0 0x7f3160588ae4 _ZNK14QOpenGLContext10shareGroupEv (libQt5Gui.so.5 + 0x188ae4) #1 0x7f31608fb8d7 n/a (libQt5Gui.so.5 + 0x4fb8d7) #2 0x7f31608fbb66 n/a (libQt5Gui.so.5 + 0x4fbb66) #3 0x7f31613b2322 _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5 + 0x1b2322) #4 0x7f31613b2bec _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5 + 0x1b2bec) #5 0x7f316139a824 _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5 + 0x19a824) #6 0x7f316139acd3 _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5 + 0x19acd3) #7 0x7f31613fecb7 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5 + 0x1fecb7) #8 0x7f316146f859 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSizeS2_ (libQt5Quick.so.5 + 0x26f859) #9 0x7f31613e9581 n/a (libQt5Quick.so.5 + 0x1e9581) #10 0x7f31613eb352 n/a (libQt5Quick.so.5 + 0x1eb352) #11 0x7f316054ba95 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x14ba95) #12 0x7f315f762f82 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f82) #13 0x7f31600ce0e8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ce0e8) #14 0x7f31605409d1 _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x1409d1) #15 0x7f316051324c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x11324c) #16 0x7f31605134c0 _ZN22QWindowSystemInterface23flushWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x1134c0) #17 0x7f316052c384 _ZN15QPlatformWindow10setVisibleEb (libQt5Gui.so.5 + 0x12c384) #18 0x7f3160ef55cf n/a (libQt5Qml.so.5 + 0x2f55cf) #19 0x7f3160ef6076 n/a (libQ
[plasmashell] [Bug 487908] plasmashell crashes when opening osu!(lazer)
https://bugs.kde.org/show_bug.cgi?id=487908 --- Comment #1 from pollux/ned --- Created attachment 170059 --> https://bugs.kde.org/attachment.cgi?id=170059&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487908] New: plasmashell crashes when opening osu!(lazer)
https://bugs.kde.org/show_bug.cgi?id=487908
Bug ID: 487908
Summary: plasmashell crashes when opening osu!(lazer)
Classification: Plasma
Product: plasmashell
Version: master
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: pollu...@proton.me
Target Milestone: 1.0
Application: plasmashell (6.0.90)
Qt Version: 6.7.1
Frameworks Version: 6.2.0
Operating System: Linux 6.9.3-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.90 [CoredumpBackend]
-- Information about the crash:
trying to open osu(lazer) .appimage will crash plasmashell under plasma 6.1
beta
the appimage was installed using gear lever aswell
The crash can be reproduced every time.
-- Backtrace (Reduced):
#5 0x78e1735bdb0e in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x6055d2b2fbd0) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.90/applets/kicker/plugin/kastatsfavoritesmodel.cpp:196
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::FunctorCallable::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x6055d2b2fbc0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9 0x78e19eb8c0ff in QObject::event (this=0x6055d2bc68f0,
e=0x6055d6436b00) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1452
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[yakuake] [Bug 402634] Hotkey to open/retract yakuake doesn't work in Wayland if flag "Use Open/Retract action to focus window" is set
https://bugs.kde.org/show_bug.cgi?id=402634 ned changed: What|Removed |Added CC||naught...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487509] settings crashes sometimes when clicking around in it on 6.1 beta
https://bugs.kde.org/show_bug.cgi?id=487509 --- Comment #1 from pollux/ned --- Created attachment 169798 --> https://bugs.kde.org/attachment.cgi?id=169798&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487509] New: settings crashes sometimes when clicking around in it on 6.1 beta
https://bugs.kde.org/show_bug.cgi?id=487509 Bug ID: 487509 Summary: settings crashes sometimes when clicking around in it on 6.1 beta Classification: Applications Product: systemsettings Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me Target Milestone: --- Application: systemsettings (6.0.90) Qt Version: 6.7.1 Frameworks Version: 6.2.0 Operating System: Linux 6.9.1-zen1-2-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.90 [CoredumpBackend] -- Information about the crash: i clicked on display and monitor, settings crashed when trying to go into it as typing this i did it again with sound setting aswell, so just clicking around on the side panel can make it close on itself The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 operator() (__closure=0x5c8434492310) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1915 #8 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x5c8434492300, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555 #9 0x77fc609a17b7 in QtPrivate::QSlotObjectBase::call (this=0x5c8434492300, r=0x5c84343eb500, a=0x7ffdbb98c8c0, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #10 doActivate (sender=, signal_index=, argv=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4086 #11 0x77fc60b4a464 in QAbstractItemModel::modelReset (this=0x5c843558d8f0, _t1=...) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1112 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487102] creating a gpt partition table crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=487102 --- Comment #1 from pollux/ned --- Created attachment 169529 --> https://bugs.kde.org/attachment.cgi?id=169529&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487102] New: creating a gpt partition table crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=487102 Bug ID: 487102 Summary: creating a gpt partition table crashes plasmashell Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me Target Milestone: 1.0 Application: plasmashell (6.0.4) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.9.0-1-MANJARO x86_64 Windowing System: Wayland Distribution: Manjaro Linux DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: tried creating a gpt parition table in kde partition manager and plasma shell crashes after it finished The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #4 0x7b37953d051d in Plasma::Theme::~Theme() () at /usr/lib/libPlasma.so.6 #5 0x7b377fe0ad45 in ??? () at /usr/lib/qt6/plugins/kf6/kirigami/platform/KirigamiPlasmaStyle.so #6 0x7b3792d8660b in QObjectPrivate::deleteChildren() () at /usr/lib/libQt6Core.so.6 #7 0x7b3792d8a888 in QObject::~QObject() () at /usr/lib/libQt6Core.so.6 #8 0x7b3787458baa in ??? () at /usr/lib/qt6/qml/org/kde/ksvg/libcorebindingsplugin.so Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486980] booting the pc crashed plasmashell when opening some software
https://bugs.kde.org/show_bug.cgi?id=486980 --- Comment #1 from pollux/ned --- Created attachment 169456 --> https://bugs.kde.org/attachment.cgi?id=169456&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486980] New: booting the pc crashed plasmashell when opening some software
https://bugs.kde.org/show_bug.cgi?id=486980
Bug ID: 486980
Summary: booting the pc crashed plasmashell when opening some
software
Classification: Plasma
Product: plasmashell
Version: 6.0.4
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: pollu...@proton.me
Target Milestone: 1.0
Application: plasmashell (6.0.4)
Qt Version: 6.7.0
Frameworks Version: 6.2.0
Operating System: Linux 6.9.0-1-cachyos x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 6.0.4 [CoredumpBackend]
-- Information about the crash:
i booted my pc on kernel 6.9 and after launching some apps like discord,
firefox, spotify, discover, plasmashell decided to crash right after launching
them
The reporter is unsure if this crash is reproducible.
-- Backtrace (Reduced):
#5 0x77388bf161d6 in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x55b322255c80) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:193
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::FunctorCallable::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x55b322255c70, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9 0x7738bf98c147 in QObject::event (this=0x55b322c47b50,
e=0x55b327673af0) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1446
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 486937] discover flatpak update, crashes plasmashell after the update
https://bugs.kde.org/show_bug.cgi?id=486937
pollux/ned changed:
What|Removed |Added
Resolution|DUPLICATE |BACKTRACE
--- Comment #5 from pollux/ned ---
(In reply to pollux/ned from comment #4)
> (In reply to Harald Sitter from comment #3)
> > Almost. When using the interactive debugger you generally need to run
> > 'backtrace' in the prompt that appears so the actual trace gets printed.
> > Thankfully it already provides enough context for me to tell where the
> > problem is :)
> >
> > *** This bug has been marked as a duplicate of bug 485933 ***
>
> I see, thank you for the information & help, im gladd its been solved (人
> •͈ᴗ•͈)
(gdb) backtrace
#0 0x756c70d791d6 in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x626089fe59e0)
at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:193
#1 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (arg=, f=...)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#2
QtPrivate::FunctorCallable::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (arg=, f=...)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#3
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=, this_=0x626089fe59d0, r=,
a=, ret=)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#4 0x756c9dd8c147 in QObject::event (this=0x626089e48e60,
e=0x62608abaccb0)
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1446
#5 0x756c9fcfc44d in QApplicationPrivate::notify_helper
(this=, receiver=0x626089e48e60, e=0x62608abaccb0)
at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287
#6 0x756c9dd3fe18 in QCoreApplication::notifyInternal2
(receiver=0x626089e48e60, event=event@entry=0x62608abaccb0)
at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1142
#7 0x756c9dd401d2 in QCoreApplication::sendEvent (event=0x62608abaccb0,
receiver=)
at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1583
#8 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=
yay i did it :D
just to make sure if it could be something else :P
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 486937] discover flatpak update, crashes plasmashell after the update
https://bugs.kde.org/show_bug.cgi?id=486937 --- Comment #4 from pollux/ned --- (In reply to Harald Sitter from comment #3) > Almost. When using the interactive debugger you generally need to run > 'backtrace' in the prompt that appears so the actual trace gets printed. > Thankfully it already provides enough context for me to tell where the > problem is :) > > *** This bug has been marked as a duplicate of bug 485933 *** I see, thank you for the information & help, im gladd its been solved (人 •͈ᴗ•͈) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486937] discover flatpak update, crashes plasmashell after the update
https://bugs.kde.org/show_bug.cgi?id=486937 --- Comment #2 from pollux/ned --- (In reply to Harald Sitter from comment #1) > Please read through > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports and generate a backtrace with symbols. sorry, this is probs not the right one so ill grab the gdb debug at the bottom, i havent done a backtrace before so my bad if i get something wrong lol PID: 1353 (plasmashell) UID: 1000 (pollux) GID: 1000 (pollux) Signal: 11 (SEGV) Timestamp: Mon 2024-05-13 07:41:56 AEST (2h 30min ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (pollux) Boot ID: 0308a0d1c10b4dafbe6df16a95277349 Machine ID: 37d90398cf5a4fae9660f86147b29276 Hostname: pollux-b550maoruspro Storage: /var/lib/systemd/coredump/core.plasmashell.1000.0308a0d1c10b4dafbe6df16a95277349.1353.171555011600.zst (present) Size on Disk: 44.1M Message: Process 1353 (plasmashell) of user 1000 dumped core. Stack trace of thread 1353: #0 0x756c70d791d6 n/a (libkickerplugin.so + 0x481d6) #1 0x756c9dd8c147 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c147) #2 0x756c9fcfc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #3 0x756c9dd3fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #4 0x756c9dd401d2 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1401d2) #5 0x756c9df959ac n/a (libQt6Core.so.6 + 0x3959ac) #6 0x756c9c996a89 n/a (libglib-2.0.so.0 + 0x5ca89) #7 0x756c9c9f89b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #8 0x756c9c995f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #9 0x756c9df93389 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x393389) #10 0x756c9dd48350 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x148350) #11 0x756c9dd43c1d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x143c1d) #12 0x6260869542a7 n/a (plasmashell + 0x272a7) #13 0x756c9d639c88 n/a (libc.so.6 + 0x25c88) #14 0x756c9d639d4c __libc_start_main (libc.so.6 + 0x25d4c) #15 0x626086954a95 n/a (plasmashell + 0x27a95) Stack trace of thread 1388: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9fb79ce8 n/a (libQt6WaylandClient.so.6 + 0x64ce8) #2 0x756c9debb619 n/a (libQt6Core.so.6 + 0x2bb619) #3 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #4 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1384: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9c9f88fd n/a (libglib-2.0.so.0 + 0xbe8fd) #2 0x756c9c995f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #3 0x756c9df93389 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x393389) #4 0x756c9dd48350 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x148350) #5 0x756c9de32a20 _ZN7QThread4execEv (libQt6Core.so.6 + 0x232a20) #6 0x756c9ec42b1e n/a (libQt6DBus.so.6 + 0x2db1e) #7 0x756c9debb619 n/a (libQt6Core.so.6 + 0x2bb619) #8 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #9 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1401: #0 0x756c9d6a34e9 n/a (libc.so.6 + 0x8f4e9) #1 0x756c9d6a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) #2 0x756c944863fc n/a (radeonsi_dri.so + 0x863fc) #3 0x756c9449ec2c n/a (radeonsi_dri.so + 0x9ec2c) #4 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #5 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1389: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9fb79ce8 n/a (libQt6WaylandClient.so.6 + 0x64ce8) #2 0x756c9debb619 n/a (libQt6Core.so.6 + 0x2bb619) #3 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded)
[Discover] [Bug 486937] New: discover flatpak update, crashes plasmashell after the update
https://bugs.kde.org/show_bug.cgi?id=486937 Bug ID: 486937 Summary: discover flatpak update, crashes plasmashell after the update Classification: Applications Product: Discover Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: pollu...@proton.me CC: aleix...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. open discover, go to updates, update a flatpak package like for me it was gpu screen recorder 2. 3. OBSERVED RESULT plasmashell crashes & reopens EXPECTED RESULT discover is supposed to update flatpak without issue and plasmashell is not supposed to crash after the update SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Endeavour os/arch, kernel 6.8.9 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION ksystemlog of the plasmashell crash Process 1353 (plasmashell) of user 1000 dumped core. Stack trace of thread 1353: #0 0x756c70d791d6 n/a (libkickerplugin.so + 0x481d6) #1 0x756c9dd8c147 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c147) #2 0x756c9fcfc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #3 0x756c9dd3fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #4 0x756c9dd401d2 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1401d2) #5 0x756c9df959ac n/a (libQt6Core.so.6 + 0x3959ac) #6 0x756c9c996a89 n/a (libglib-2.0.so.0 + 0x5ca89) #7 0x756c9c9f89b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #8 0x756c9c995f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #9 0x756c9df93389 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x393389) #10 0x756c9dd48350 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x148350) #11 0x756c9dd43c1d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x143c1d) #12 0x6260869542a7 n/a (plasmashell + 0x272a7) #13 0x756c9d639c88 n/a (libc.so.6 + 0x25c88) #14 0x756c9d639d4c __libc_start_main (libc.so.6 + 0x25d4c) #15 0x626086954a95 n/a (plasmashell + 0x27a95) Stack trace of thread 1388: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9fb79ce8 n/a (libQt6WaylandClient.so.6 + 0x64ce8) #2 0x756c9debb619 n/a (libQt6Core.so.6 + 0x2bb619) #3 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #4 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1384: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9c9f88fd n/a (libglib-2.0.so.0 + 0xbe8fd) #2 0x756c9c995f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #3 0x756c9df93389 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x393389) #4 0x756c9dd48350 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x148350) #5 0x756c9de32a20 _ZN7QThread4execEv (libQt6Core.so.6 + 0x232a20) #6 0x756c9ec42b1e n/a (libQt6DBus.so.6 + 0x2db1e) #7 0x756c9debb619 n/a (libQt6Core.so.6 + 0x2bb619) #8 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #9 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1401: #0 0x756c9d6a34e9 n/a (libc.so.6 + 0x8f4e9) #1 0x756c9d6a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) #2 0x756c944863fc n/a (radeonsi_dri.so + 0x863fc) #3 0x756c9449ec2c n/a (radeonsi_dri.so + 0x9ec2c) #4 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #5 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1389: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9fb79ce8 n/a (libQt6WaylandClient.so.6 + 0x64ce8) #2 0x756c9debb619 n/a (libQt6Core.so.6 + 0x2bb619) #3 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #4 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1564: #0 0x756c9d6a34e9 n/a (libc.so.6 + 0x8f4e9) #1 0x756c9d6a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) #2 0x756c944863fc n/a (radeonsi_dri.so + 0x863fc) #3 0x756c9449ec2c n/a (radeonsi_dri.so + 0x9ec2c) #4 0x756c9d6a6ded n/a (libc.so.6 + 0x92ded) #5 0x756c9d72a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 1500: #0 0x756c9d71c39d __poll (libc.so.6 + 0x10839d) #1 0x756c9c9f88fd n/a (libglib-2.0.so.0 + 0xbe8fd) #2 0x756c9c995f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #
[dolphin] [Bug 360643] Dolphin doesn't obey time/date settings in "Formats" (Sys settings)
https://bugs.kde.org/show_bug.cgi?id=360643 --- Comment #4 from ned --- See related discussions at https://superuser.com/questions/1162283/use-iso-time-and-date-format-in-kde-5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 360643] Dolphin doesn't obey time/date settings in "Formats" (Sys settings)
https://bugs.kde.org/show_bug.cgi?id=360643 ned changed: What|Removed |Added CC||naught...@gmail.com Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from ned --- This problem is occuring again in Kubuntu 22.04-LTS. Dolphin does not respect the plasma dat format settings. For example, if I set the date format to `en_SE` (date format -MM-DD), I still see D/M/YY format in Dolphin, both when using relative and absolute dates. Dolphin version 21.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462744] New: Will Digikam run on Apple M1 or M2 chips?
https://bugs.kde.org/show_bug.cgi?id=462744 Bug ID: 462744 Summary: Will Digikam run on Apple M1 or M2 chips? Classification: I don't know Product: kde Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ianlit...@gmail.com Target Milestone: --- Is it possible to run Digikam on a macbook built on the M1 or M2 chips? I need to update my macbook; currently I have an intel based macbook, but any upgrade will be based on the M1 or M2 chip. I see that requests for this have been submitted, but it isn't clear if Digikam will run on M1 or M2 chips, either natively, or with some form of virtualization. Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 450683] Windows 10 64 bit software not found...
https://bugs.kde.org/show_bug.cgi?id=450683 Ned <19331744...@gmail.com> changed: What|Removed |Added CC||19331744...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 450683] New: Windows 10 64 bit software not found...
https://bugs.kde.org/show_bug.cgi?id=450683 Bug ID: 450683 Summary: Windows 10 64 bit software not found... Product: ktorrent Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: 19331744...@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. 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 Could you please make a windows 10 64 operating software of this software please - didnt see any for windows 10 64 bit version released out - if any is released out please contact me at 19331744...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441067] Yakuake is no longer available in the task switcher list
https://bugs.kde.org/show_bug.cgi?id=441067 --- Comment #10 from ned --- (In reply to FeepingCreature from comment #7) > I'd guess the devs considered this valuable feature as a bug? > > You can force KDE to consider yakuake as a normal window by going to Window > Rules in the system settings, then set Window Class (application) [Exact > Match] yakuake, then Add Property..., Set window type, [Force] [Normal > Window]. This restores yakuake to the taskbar and the window switcher. Thanks for the work-around FeepingCreature! Massively appreciated. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441067] Yakuake is no longer available in the task switcher list
https://bugs.kde.org/show_bug.cgi?id=441067 ned changed: What|Removed |Added CC||naught...@gmail.com --- Comment #9 from ned --- Also missing this feature after a recent change. My fingers sit on alt-tab all the time. They never hover near F12. Not being able to tab-switc back to yakuake is a massive pain. I've been trying to get used to it for 6 weeks now, and it's still tripping me up multiple times an hour. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444592] Will digiKam work on MacOS Monterey?
https://bugs.kde.org/show_bug.cgi?id=444592 --- Comment #3 from Ned --- I have just installed Digikam 7.4.0 on an intel-based MacBook running Monterey OS 12.1. Everything so far is working as expected. Thanks to all the team for the new version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444592] New: Will digiKam work on MacOS Monterey?
https://bugs.kde.org/show_bug.cgi?id=444592 Bug ID: 444592 Summary: Will digiKam work on MacOS Monterey? Product: digikam Version: 7.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: ianlit...@gmail.com Target Milestone: --- I am successfully running digiKam 7.3.0 on a MacBook Pro (Intel) and MacOS BigSur. Do you know if digiKam will run on MacOS Monterey? Thanks. Ian Litton -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414161] New: Every 3 times crash after check "Use desktop layot from theme"
https://bugs.kde.org/show_bug.cgi?id=414161 Bug ID: 414161 Summary: Every 3 times crash after check "Use desktop layot from theme" Product: systemsettings Version: 5.17.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: megomas...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.2) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.9-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I installed the global theme "Breeze-Chameleon-Light", then checked "use desktop layout from theme". After which everything, all panels disappeared, only Krunner worked. After the reboot, 370 updates came, which were before that. Panels appeared, but System settings began to fall. Especially in the items "Colors", "Plasma style", "Cursors", "Global Theme". The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79be7a2800 (LWP 2744))] Thread 17 (Thread 0x7f798700 (LWP 3966)): #0 0x7f79bf2cb5d9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f79bf27f817 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f79bf2801ab in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f79bf28039f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f79c147199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f79c141a0db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f79c1252021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f79c07133f5 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f79c12531a2 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f79bfbbaf2a in start_thread () at /lib64/libpthread.so.0 #10 0x7f79c2b374af in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f7966210700 (LWP 2775)): #0 0x7f79c2b2860c in read () at /lib64/libc.so.6 #1 0x7f79bf2c710f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f79bf27fdd7 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f79bf280222 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f79bf28039f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f79c147199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f79c141a0db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f79c1252021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f79c12531a2 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f79bfbbaf2a in start_thread () at /lib64/libpthread.so.0 #10 0x7f79c2b374af in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f798cfe1700 (LWP 2767)): #0 0x7f79c2b32059 in syscall () at /lib64/libc.so.6 #1 0x7f79c12554f1 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7f79c007ee64 in () at /usr/lib64/libQt5Network.so.5 #3 0x7f79c12531a2 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f79bfbbaf2a in start_thread () at /lib64/libpthread.so.0 #5 0x7f79c2b374af in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f798d7e2700 (LWP 2766)): #0 0x7f79bf250af1 in g_ptr_array_set_size () at /usr/lib64/libglib-2.0.so.0 #1 0x7f79bf27f6fe in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f79bf2801ab in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f79bf28039f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f79c147199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f79c141a0db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f79c1252021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f79c12531a2 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f79bfbbaf2a in start_thread () at /lib64/libpthread.so.0 #9 0x7f79c2b374af in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f798dfe3700 (LWP 2764)): #0 0x7f79c2b2860c in read () at /lib64/libc.so.6 #1 0x7f79bf2c710f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f79bf27fdd7 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f79bf280222 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f79bf28039f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f79c147199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f79c141a0db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f79c1252021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f79c12531a2 in ()
[krita] [Bug 412460] New: Keyboard shortcuts for changing the brush size do not work when using the Line Tool
https://bugs.kde.org/show_bug.cgi?id=412460 Bug ID: 412460 Summary: Keyboard shortcuts for changing the brush size do not work when using the Line Tool Product: krita Version: 4.2.6 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: catava...@gmail.com Target Milestone: --- SUMMARY While using the Line Tool, keyboard sortcuts (square brackets in my case), or otherwise using Shift+Click and dragging doesn't change the brush size. STEPS TO REPRODUCE 1. Select the Line Tool 2. Use square brackets to change brush size or Shift+Click OBSERVED RESULT Brush size does not change. EXPECTED RESULT Brush size should change. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro, Version 1903 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 397443] New: Upgrade from 16.04 to 18.04 failure
https://bugs.kde.org/show_bug.cgi?id=397443 Bug ID: 397443 Summary: Upgrade from 16.04 to 18.04 failure Product: konsole Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: e.r.wa...@btinternet.com Target Milestone: --- Created attachment 114430 --> https://bugs.kde.org/attachment.cgi?id=114430&action=edit Image of Konsole report Upgrade from 16.04 to Bionic Beaver failed both through Graphical Upgrade Manager and through the Konsole. 'Subprocess installed post instaation script returned error exit status 1' -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 131068] When an image that's open in Gwenview is edited with another program, the thumbnail updates instantly, but the image itself doesn't
https://bugs.kde.org/show_bug.cgi?id=131068 --- Comment #13 from ned --- slightly related: Even when F5 is pressed to refresh the image, the image size shown in pixels in the title bar does not refresh at all. This can be annoying, for example when you're trying to optimise the size of a graph image, and you need to know how large the current version is. It DOES refresh if you move to another image, and then move back, after a refresh. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390828] Can't pin secondary version of app to task bar
https://bugs.kde.org/show_bug.cgi?id=390828 --- Comment #1 from ned --- This is a work-around, and is maybe good enough that this should be a won'tfix.. not sure. https://www.dedoimedo.com/computers/plasma-task-manager-icons-custom-wine.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390828] New: Can't pin secondary version of app to task bar
https://bugs.kde.org/show_bug.cgi?id=390828 Bug ID: 390828 Summary: Can't pin secondary version of app to task bar Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: naught...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I have two versions of Mixxx that I want to run. The main one is from the repos, and the other is a custom dekstop entry I've added to the menus, called "Mixxx-beta", which runs the git version of mixxx within GDB. I would like to pin both to the taskbar, but I can't - when I try to pin the Mixxx-beta version, and then quit, and re-open it from the taskbar pin, it opens the plain Mixxx version. I guess this is some kind of bug caused by the taskbar pin using the window name instead of the desktop entry name to identify apps? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 335730] No easy way to reposition krunner window
https://bugs.kde.org/show_bug.cgi?id=335730 ned changed: What|Removed |Added CC|naught...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 335730] No way to reposition krunner window
https://bugs.kde.org/show_bug.cgi?id=335730 ned changed: What|Removed |Added CC||naught...@gmail.com --- Comment #13 from ned --- I think this is fixed? I can move krunner with the inner window move action (system settings -> window settings -> actions -> Window Actions, I have Alt+MMB set to "Move"). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 131068] When an image that's open in Gwenview is edited with another program, the thumbnail updates instantly, but the image itself doesn't
https://bugs.kde.org/show_bug.cgi?id=131068 --- Comment #12 from ned --- You don't have to close and open, you can just hit refresh (F5), but it's still annoying if there are lots of images. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 388982] Main image view does not automatically refresh on file changes
https://bugs.kde.org/show_bug.cgi?id=388982 --- Comment #2 from ned --- Content modification, with the same name. For example, I'm generating plots using python scripts, and they get regenerated every time I tweak the scripts, but I have to manually reload the images in Gwenview. I actually have to manually reload EVERY image that Gwenview has viewed - so if I have 5 images in a folder, and I scroll through them all, then regenerate them all, then when I scroll back through, I have to press F5 5 times. This can be annoying when there are a lot of images. I guess Gwenview should check the modified time each time it views an image, and check if its' cached version is older? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 388982] New: Main image view does not automatically refresh on file changes
https://bugs.kde.org/show_bug.cgi?id=388982 Bug ID: 388982 Summary: Main image view does not automatically refresh on file changes Product: gwenview Version: 17.04.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: naught...@gmail.com Target Milestone: --- Gwenview's main image view does not update when a file is modified. The thumbnail bar thumbnails do update. Perhaps there is a reason for this behaviour, but it would be good to at least have an option in the settings to allow auto refresh (and I think that that should be the default behaviour). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384160] File copy: Overwrite only if size is different
https://bugs.kde.org/show_bug.cgi?id=384160 --- Comment #2 from ned --- Yes, fair enough, but the first 2 reasons are not something Dolphin has any control over. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384160] New: File copy: Overwrite only if size is different
https://bugs.kde.org/show_bug.cgi?id=384160 Bug ID: 384160 Summary: File copy: Overwrite only if size is different Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: naught...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- When copying files from one place to another, the operation can sometimes be interrupted mid-file (e.g. USB cable falls out, network connection drops, disk full, manual cancel). It is sometime useful to be able to resume such an operation (I often have this problem when copying music to my phone, but also with network transfers). In such cases if I try to copy over the existing files, I get three options: overwrite, skip, or cancel. Generally, skip is fine, but if there was an operation that was killed mid-copy, then I can be left with some half-complete files. Overwrite fixes that problem, but then it wastes needless time, disk writes, and network bandwidth. It would be nice to have an "Overwrite if different (size)" option, that would skip files that are the same size, or overwrite files that are different. This would be the best of both options. It would not catch some edge cases where a file has changed, but the size is exactly the same, but I think those cases are probably extremely rare.. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 377398] New: Ubiquity fails to install onto existing encrypted partitions due to missing /etc/crypttab
https://bugs.kde.org/show_bug.cgi?id=377398 Bug ID: 377398 Summary: Ubiquity fails to install onto existing encrypted partitions due to missing /etc/crypttab Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: naught...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I had to re-install due to a corrupted root partition. All of my partitions other than /boot (/, /home/, /data/, swap) are encrypted. I first unlocked them using `udiskctl unlock -b /dev/sdXY`. I then ran ubiquity, and used manual partition selection to assign them to the appropriate luks partitions. Installation seemed to go fine, but when I entered my user details, I got an error saying "ubi-usersetup failed with error 1". When I looked in /var/log/syslog, there were no clear messages related to ubi-usersetup (other than it crashed), but there was a message `cannot stat '/etc/crypttab': no such file or directory`. At this point, pressing 'ignore' caused ubiquity to freeze on the last screen, with no messages, 'retry' took me back to the user-data entry panel, and 'cancel' aborted and failed the install. When I looked, there was no /target/etc/crypttab, so I just copied the one from /etc/crypttab (which only contained a single commented header line, no actual info). That fixed the problem, and after pressing 'retry' in ubiquity, the ubi-usersetup did not fail again, and setup continued as normal. I will now follow the instructions at http://askubuntu.com/questions/853078/reinstall-to-existing-encrypted-partitions/868726 to fix crypttab on the new system. No sure if this is a neon bug, a ubiquity bug, or a feature, but I figured I'd post it, as I suspect other people will hit this sometimes, and the work-around is useful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370163] Regression: can no longer mouse-scroll through windows in a group.
https://bugs.kde.org/show_bug.cgi?id=370163 --- Comment #5 from ned --- Damn, that was fast. Thanks Eike! Excellent :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370163] New: Regression: can no longer mouse-scroll through windows in a group.
https://bugs.kde.org/show_bug.cgi?id=370163 Bug ID: 370163 Summary: Regression: can no longer mouse-scroll through windows in a group. Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: naught...@gmail.com CC: plasma-b...@kde.org In older versions of Plasma (<5.6.x?), it was possible to mouse-scroll to cycle through all of the windows in a single group on the task bar. If you scrolled on an ungrouped window, it would scroll through all windows in the task bar. In more recent versions, it appears that the mouse scroll only scrolls through all windows on the task bar, regardless of whether the window you're hovering over in the task bar is in a group or not. This feels like a regression, as the old behaviour was really useful, for instance for looking through a bunch of images or documents at once, and comparing them... If there was a valid reason for removing this behaviour, would it at least be possible to get it back as an optional behaviour? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364689] Prevent/delay focus stealing while typing
https://bugs.kde.org/show_bug.cgi?id=364689 --- Comment #2 from ned --- Cool. Not exactly sure of the terminology, but that looks to cover most of it. I think it would still be nice to have the option for windows to be activated as well as raised after the delay - otherwise alt+tabbing gets really confusing, and mouse-use is required, which is annoying. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364689] New: Prevent/delay focus stealing while typing
https://bugs.kde.org/show_bug.cgi?id=364689 Bug ID: 364689 Summary: Prevent/delay focus stealing while typing Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: naught...@gmail.com I have focus stealing prevention turned off, generally, because I like to be notified if something requires my attention (e.g. password inputs, chat messages etc). However, when multiple things are happening at once, it can happen that you're half way through typing something, focus is stolen, and you end up typing the rest in the wrong window. This can be problematic at times: for example, accidentally pressing the wrong ok/cancel button in a new dialogue window, or accidentally sexting your grandmother... It would be great if there was an option to turn focus stealing prevention on only while typing - so, for example, if I press any key, focus stealing is prevented for the next 1000ms (configurable). It would be ideal if focus stealing was optionally delayed, instead of prevented: so one second after I stop typing, and I'm looking at the screen, thinking, and the new window pops up, and I can react intentionally, instead of accidentally. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 363256] QFSFileEngine::open: No file name specified
https://bugs.kde.org/show_bug.cgi?id=363256 --- Comment #1 from ned --- rm -rf /var/tmp/kdecache-naught101/choqok-userimages.kcache rm -rf /home/naught101/.kde/share/apps/choqok/* seem to have sorted the problem, but the messages still appear, when run from the command line. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 363256] New: QFSFileEngine::open: No file name specified
https://bugs.kde.org/show_bug.cgi?id=363256 Bug ID: 363256 Summary: QFSFileEngine::open: No file name specified Product: choqok Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: naught...@gmail.com CC: scarp...@kde.org When starting choqok, I get these messages: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified ... the last message repeats indefinitely, until I kill the program. The program never starts properly. This may have been caused by the computer crashing during the previous session, but I'm not sure which files I should be looking at... Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 321824] Multi-column layout (like TweetDeck)
https://bugs.kde.org/show_bug.cgi?id=321824 ned changed: What|Removed |Added CC||naught...@gmail.com --- Comment #2 from ned --- Agree, this would be really useful for those of us with multiple accounts. -- You are receiving this mail because: You are watching all bug changes.
