[plasmashell] [Bug 472524] New: Crash when moving a task on the taskbar
https://bugs.kde.org/show_bug.cgi?id=472524 Bug ID: 472524 Summary: Crash when moving a task on the taskbar Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: tcosproje...@gmail.com Target Milestone: 1.0 Application: plasmashell Build from commit cc80403daa9613c10666a3c48088ff470149d712 (HEAD -> Plasma/5.27, origin/Plasma/5.27) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.3-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed STEPS TO REPRODUCE I'm not sure this is reliably reproducible. 1. Quickly add, remove, launch, and move around tasks on the task tray -- Backtrace PID: 14236 (plasmashell) UID: 1000 (will) GID: 1000 (will) Signal: 11 (SEGV) Timestamp: Sat 2023-07-22 23:13:30 PDT (1h 16min ago) Command Line: /home/will/kde/usr/bin/plasmashell --replace Executable: /home/will/kde/usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-konsolesu-8eb80c66a91e45b3ab10c9c311272e99.scope Unit: user@1000.service User Unit: app-konsolesu-8eb80c66a91e45b3ab10c9c311272e99.scope Slice: user-1000.slice Owner UID: 1000 (will) Boot ID: 4e5c51538732497f942e95c7877ec471 Machine ID: 35bbab8c5a0449aeba77a054f0d6bc69 Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.plasmashell.1000.4e5c51538732497f942e95c7877ec471.14236.169009281000.zst (present) Size on Disk: 21.6M Message: Process 14236 (plasmashell) of user 1000 dumped core. Core was generated by `/home/will/kde/usr/bin/plasmashell --replace'. 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 0x7f58d9614a00 (LWP 14236))] #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f58dac92b43 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f58dac41266 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f58de3916b7 in KCrash::defaultCrashHandler(int) (sig=11) at /home/will/kde/src/kcrash/src/kcrash.cpp:611 #4 0x7f58dac41330 in () at /lib64/libc.so.6 #5 0x7f58cc31552a in QScopedPointer >::operator->() const (this=0x10) at /usr/include/qt5/QtCore/qscopedpointer.h:118 #6 0x7f58cc31503c in TaskManager::ActivityInfo::currentActivity() const (this=0x0) at /home/will/kde/src/plasma-workspace/libtaskmanager/activityinfo.cpp:84 #7 0x7f58cc339bca in TaskManager::TasksModel::move(int, int, QModelIndex const&) (this=0x2d7f7b0, row=4, newPos=3, parent=...) at /home/will/kde/src/plasma-workspace/libtaskmanager/tasksmodel.cpp:1657 #8 0x7f58cc30d4c6 in TaskManager::TasksModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x2d7f7b0, _c=QMetaObject::InvokeMetaMethod, _id=51, _a=0x7ffded51b420) at /home/will/kde/build/plasma-workspace/libtaskmanager/taskmanager_autogen/EWIEGA46WW/moc_tasksmodel.cpp:467 #9 0x7f58cc30ea3b in TaskManager::TasksModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x2d7f7b0, _c=QMetaObject::InvokeMetaMethod, _id=51, _a=0x7ffded51b420) at /home/will/kde/build/plasma-workspace/libtaskmanager/taskmanager_autogen/EWIEGA46WW/moc_tasksmodel.cpp:763 #10 0x7f58dd4e1353 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=this@entry=0x7ffded51b6b0, type=type@entry=QMetaObject::InvokeMetaMethod, index=, index@entry=147, argv=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.10+kde26/src/qml/qml/qqmlobjectorgadget.cpp:51 #11 0x7f58dd3bda99 in CallMethod (callType=, callArgs=0x78, engine=, argTypes=, argCount=, returnType=, index=, object=...) at /usr/include/qt5/QtCore/qvarlengtharray.h:189 #12 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=..., data=, engine=engine@entry=0x14b2f80, callArgs=callArgs@entry=0x7f58cc3be6c8, callType=callType@entry=QMetaObject::InvokeMetaMethod) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.10+kde26/src/qml/jsruntime/qv4qobjectwrapper.cpp:1553 #13 0x7f58dd3bf73b in CallOverloaded (callType=, propertyCache=, callArgs=, engine=, data=, object=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.10+kde26/src/qml/jsruntime/qv4qobjectwrapper.cpp:1629 #14 QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*,
[kwin] [Bug 472509] Kwin_wayland can randomly crash if you are alt-tabbing from Apex Legends while PROTON_LOG=1 is set
https://bugs.kde.org/show_bug.cgi?id=472509 --- Comment #4 from Antti Savolainen --- Also of note that I'm on Nvidia -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 Fahim Shahriar changed: What|Removed |Added CC||fahimshahriar...@gmail.com --- Comment #6 from Fahim Shahriar --- Same problem here! When I set "Sunset and sunrise at manual location", it works perfectly. The problem is only with "Sunset and sunrise at current location". Here're the screenshots: https://ibb.co/6Pv1HMK https://ibb.co/17JPrbX -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472523] KPhotoAlbum crashes when right clicking in the empty space below category tags in Annotations window
https://bugs.kde.org/show_bug.cgi?id=472523 Victor Lobo changed: What|Removed |Added CC||victor.ip.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472523] New: KPhotoAlbum crashes when right clicking in the empty space below category tags in Annotations window
https://bugs.kde.org/show_bug.cgi?id=472523 Bug ID: 472523 Summary: KPhotoAlbum crashes when right clicking in the empty space below category tags in Annotations window Classification: Applications Product: kphotoalbum Version: GIT master Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Annotation Dialog Assignee: kpab...@willden.org Reporter: victor.ip.l...@gmail.com Target Milestone: --- Created attachment 160462 --> https://bugs.kde.org/attachment.cgi?id=160462=edit Screenshot of where to right click to induce crash SUMMARY KPhotoAlbum crashes when right clicking in the empty space below category (people, places, events etc.) tag names in Annotations window (see empty space in screenshot attached) STEPS TO REPRODUCE 1. Open KPhotoAlbum 2. Click on Show Thumbnails 3. Open the Annotations window (Ctrl + 1 on any image/video) 4. Annotations window opens 5. Right Click in empty space below tags displayed for people (or places or events etc.) 6. KPhotoAlbum crashes Screenshot of where to right click to induce crash is attached. OBSERVED RESULT Crash EXPECTED RESULT No crash; ignore right click and remain on Annotations screen. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 20230714; Kernel Version: 6.4.2-1-default (64-bit) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 KPhotoAlbum Version 5.11.0 (as installed from Opensuse Tumbleweed repository) Also occurs in latest git version v5.11.0-14-g7821c840 ADDITIONAL INFORMATION 1. Crash is reproducible every time the steps are followed. 2. Crash occurs in Annotations window and Search window 3. Crash occurs even in the demo database and is regardless of picture or video selected. GDB Backtrace for current thread: #0 QAction::setEnabled (this=0x0, b=false) at kernel/qaction.cpp:1016 #1 0x005e5cd6 in AnnotationDialog::ListSelect::showContextMenu(QPoint const&) () #2 0x005eb1c4 in QtPrivate::FunctorCall, QtPrivate::List, void, void (AnnotationDialog::ListSelect::*)(QPoint const&)>::call(void (AnnotationDialog::ListSelect::*)(QPoint const&), AnnotationDialog::ListSelect*, void**) () #3 0x005eafff in void QtPrivate::FunctionPointer::call, void>(void (AnnotationDialog::ListSelect::*)(QPoint const&), AnnotationDialog::ListSelect*, void**) () #4 0x005eaced in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () #5 0x7fffec7257a2 in QtPrivate::QSlotObjectBase::call (a=0x7fffab50, r=0x1ed4010, this=0x1ee54a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x1ed6120, signal_index=6, argv=0x7fffab50) at kernel/qobject.cpp:3925 #7 0x7fffec71e40f in QMetaObject::activate (sender=sender@entry=0x1ed6120, m=m@entry=0x7fffed8bc2c0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffab50) at kernel/qobject.cpp:3985 #8 0x7fffed3cc2a5 in QWidget::customContextMenuRequested (this=this@entry=0x1ed6120, _t1=...) at .moc/moc_qwidget.cpp:653 #9 0x7fffed3e7a79 in QWidget::event (this=this@entry=0x1ed6120, event=event@entry=0x7fffaf90) at kernel/qwidget.cpp:8852 #10 0x7fffed491f7e in QFrame::event (this=0x1ed6120, e=0x7fffaf90) at widgets/qframe.cpp:550 #11 0x7fffec6ed27b in QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x1ed6ea0, event=event@entry=0x7fffaf90) at kernel/qcoreapplication.cpp:1190 #12 0x7fffed3a518e in QApplicationPrivate::notify_helper (this=this@entry=0x837080, receiver=receiver@entry=0x1ed6ea0, e=e@entry=0x7fffaf90) at kernel/qapplication.cpp:3634 #13 0x7fffed3adaaa in QApplication::notify (this=, receiver=, e=0x7fffaf90) at kernel/qapplication.cpp:3246 #14 0x7fffec6ed4f8 in QCoreApplication::notifyInternal2 (receiver=0x1ed6ea0, event=0x7fffaf90) at kernel/qcoreapplication.cpp:1064 #15 0x7fffec6ed542 in QCoreApplication::forwardEvent (receiver=, event=, originatingEvent=) at kernel/qcoreapplication.cpp:1079 #16 0x7fffed3fff59 in QWidgetWindow::handleMouseEvent (this=this@entry=0x20d3e00, event=event@entry=0x7fffb280) at kernel/qwidgetwindow.cpp:692 #17 0x7fffed402d1f in QWidgetWindow::event (this=0x20d3e00, event=0x7fffb280) at kernel/qwidgetwindow.cpp:300 #18 0x7fffed3a519e in QApplicationPrivate::notify_helper (this=, receiver=0x20d3e00, e=0x7fffb280) at kernel/qapplication.cpp:3640 #19 0x7fffec6ed4f8 in QCoreApplication::notifyInternal2 (receiver=0x20d3e00, event=0x7fffb280) at kernel/qcoreapplication.cpp:1064 #20 0x7fffec6ed6ce in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1474 #21 0x7fffecb7d12b in QGuiApplicationPrivate::processMouseEvent (e=0x1ec80f0) at
[plasma-systemmonitor] [Bug 472522] New: Plasma System monitor falsely shows 100% CPU usage on one core
https://bugs.kde.org/show_bug.cgi?id=472522 Bug ID: 472522 Summary: Plasma System monitor falsely shows 100% CPU usage on one core Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ivb...@proton.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Plasma System Monitor, and its widgets show 100% CPU usage on one core STEPS TO REPRODUCE Steps to reproduce are unknown; however, if you kill the kwin process (and wait for the shell to restart itself) the issue goes away until the next reboot. OBSERVED RESULT n/a EXPECTED RESULT n/a SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Kernel v6.4.4-arch1-1 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Here are some images of what I am seeing: [Widget](https://imgur.com/a/jXjHk2M) [System Monitor](https://imgur.com/a/YnjslJ1) [htop](https://imgur.com/a/qJuxV7X) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469160] kscreen-doctor segmentation faults in KIconLoader::~KIconLoader() when exiting
https://bugs.kde.org/show_bug.cgi?id=469160 --- Comment #11 from Misha Labjuk --- (In reply to Nate Graham from comment #10) > Thanks for the patches, Misha! Can you submit them at > https://invent.kde.org/frameworks/kwayland/-/merge_requests so they get seen > by > developers? Done. https://invent.kde.org/frameworks/kwayland/-/merge_requests/100 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472521] New: Plasmashell crashes when I turn off / on my primary monitor
https://bugs.kde.org/show_bug.cgi?id=472521 Bug ID: 472521 Summary: Plasmashell crashes when I turn off / on my primary monitor Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-multiscreen Assignee: plasma-b...@kde.org Reporter: mihne...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 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. Log in a Plasma Wayland Session with two Monitors (Primary Monitor: Display Port, Secondary Monitor: HDMI) 2. Power off the Primary Monitor for at least a few seconds 3. Power on the Primary Monitor OBSERVED RESULT Plasmashell crashes and restarts. After plasma restarts everything works ok. EXPECTED RESULT Plasmashell will not crash and everything will work as expected SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 [Wayland Session] KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Kernel: 6.4.4-200.fc38.x86_64 No backtrace available only from gnome-logs the following: 08:51:32 systemd-coredum: Process 3872 (plasmashell) of user 1000 dumped core. Module libprisonquickplugin.so from rpm kf5-prison-5.108.0-1.fc38.x86_64 Module libKF5NotifyConfig.so.5 from rpm kf5-knotifyconfig-5.108.0-1.fc38.x86_64 Module plasma_engine_notifications.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module KF5IdleTimeWaylandPlugin.so from rpm kf5-kidletime-5.108.0-1.fc38.x86_64 Module kio_file.so from rpm kf5-kio-5.108.0-1.fc38.x86_64 Module libQuickChartsControls.so from rpm kf5-kquickcharts-5.108.0-1.fc38.x86_64 Module libgmp.so.10 from rpm gmp-6.2.1-4.fc38.x86_64 Module libhogweed.so.6 from rpm nettle-3.8-3.fc38.x86_64 Module libnettle.so.8 from rpm nettle-3.8-3.fc38.x86_64 Module libtasn1.so.6 from rpm libtasn1-4.19.0-2.fc38.x86_64 Module libunistring.so.5 from rpm libunistring-1.1-3.fc38.x86_64 Module libp11-kit.so.0 from rpm p11-kit-0.24.1-6.fc38.x86_64 Module libgnutls.so.30 from rpm gnutls-3.8.0-2.fc38.x86_64 Module libqca-qt5.so.2 from rpm qca-2.3.6-1.fc38.x86_64 Module libKF5Wallet.so.5 from rpm kf5-kwallet-5.108.0-1.fc38.x86_64 Module libnm.so.0 from rpm NetworkManager-1.42.8-1.fc38.x86_64 Module libKF5NetworkManagerQt.so.6 from rpm kf5-networkmanager-qt-5.108.0-1.fc38.x86_64 Module libKF5ModemManagerQt.so.6 from rpm kf5-modemmanager-qt-5.108.0-1.fc38.x86_64 Module libplasmanm_editor.so from rpm plasma-nm-5.27.6-1.fc38.x86_64 Module libplasmanm_internal.so from rpm plasma-nm-5.27.6-1.fc38.x86_64 Module libplasmanm_qmlplugins.so from rpm plasma-nm-5.27.6-1.fc38.x86_64 Module libnightcolorcontrolplugin.so from rpm kdeplasma-addons-5.27.6-1.fc38.x86_64 Module libkeyboardlayoutplugin.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module libqtlabsplatformplugin.so from rpm qt5-qtquickcontrols2-5.15.10-1.fc38.x86_64 Module plasma_engine_keystate.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module liboath.so.0 from rpm oath-toolkit-2.6.7-5.fc38.x86_64 Module libQt5Concurrent.so.5 from rpm qt5-qtbase-5.15.10-1.fc38.x86_64 Module libplasmapassplugin.so from rpm plasma-pass-1.2.0-6.fc38.x86_64 Module libQuickCharts.so from rpm kf5-kquickcharts-5.108.0-1.fc38.x86_64 Module libnotificationmanagerplugin.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module plasma_engine_devicenotifications.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module plasma_engine_soliddevice.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module plasma_engine_hotplug.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module libKF5SonnetCore.so.5 from rpm kf5-sonnet-5.108.0-1.fc38.x86_64 Module libKF5SonnetUi.so.5 from rpm kf5-sonnet-5.108.0-1.fc38.x86_64 Module libZXing.so.1 from rpm zxing-cpp-1.2.0-9.fc38.x86_64 Module libdmtx.so.0 from rpm libdmtx-0.7.5-11.fc38.x86_64 Module libqrencode.so.4 from rpm qrencode-4.1.1-4.fc38.x86_64 Module libKF5TextWidgets.so.5 from rpm kf5-ktextwidgets-5.108.0-1.fc38.x86_64 Module libKF5Prison.so.5 from rpm kf5-prison-5.108.0-1.fc38.x86_64 Module plasma_engine_clipboard.so from rpm plasma-workspace-5.27.6-1.fc38.x86_64 Module libmpg123.so.0 from rpm mpg123-1.31.3-1.fc38.x86_64 Module libopus.so.0 from rpm opus-1.3.1-12.fc38.x86_64 Module libvorbisenc.so.2 from rpm libvorbis-1.3.7-7.fc38.x86_64 Module libFLAC.so.12 from rpm flac-1.4.3-1.fc38.x86_64 Module libgsm.so.1 from rpm gsm-1.0.22-2.fc38.x86_64 Module libsndfile.so.1 from rpm libsndfile-1.1.0-6.fc38.x86_64 Module libpulsecommon-16.1.so from rpm pulseaudio-16.1-4.fc38.x86_64 Module libpulse.so.0 from rpm pulseaudio-16.1-4.fc38.x86_64 Module libpulse-mainloop-glib.so.0 from rpm
[kphotoalbum] [Bug 472520] Date for Videos should be sourced from Video metadata instead of filesystem file modify date
https://bugs.kde.org/show_bug.cgi?id=472520 Victor Lobo changed: What|Removed |Added CC||victor.ip.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472520] New: Date for Videos should be sourced from Video metadata instead of filesystem file modify date
https://bugs.kde.org/show_bug.cgi?id=472520 Bug ID: 472520 Summary: Date for Videos should be sourced from Video metadata instead of filesystem file modify date Classification: Applications Product: kphotoalbum Version: GIT master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Backend Assignee: kpab...@willden.org Reporter: victor.ip.l...@gmail.com Target Milestone: --- SUMMARY On initial setup, KPhotoAlbum processed my photos and videos. For each video that it found KPhotoAlbum assigned it the filesystem File Modify date. My expectation is that KPhotoAlbum would assign a date from the video metadata (CreateDate, DateTimeOriginal etc.) since most of my videos have that populated and those dates are correct (as compared to file modify date). This behavior can also be observed in the KPhotoAlbum demo. The demo contains a video "movie.avi" with DateTimeOriginal value "2006:10:29 14:33:55" reported by ExifTool. digiKam also displays "2006:10:29 14:33:55". If I do one of the below then KPhotoAlbum assigns the file system file modify date (current date) to the video instead of "2006:10:29 14:33:55": 1. Select the movie file in the demo and then do (Maintenance --> Read Exif Info from Files... --> Check ONLY "Update Image Date" --> OK) OR 2. Copy the movie file from the demo to a new KPhotoAlbum database OBSERVED RESULT After processing video files KPhotoAlbum assigns the file system file modify to the videos EXPECTED RESULT After processing video files KPhotoAlbum assigns the appropriate date time from video metadata (CreateDate, DateTimeOriginal etc.) SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 20230714; Kernel Version: 6.4.2-1-default (64-bit) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION 1. Opening this as a bug as per discussion on the KPhotoAlbum mailing list: https://mail.kde.org/pipermail/kphotoalbum/2023-July/007002.html 2. Note that the video date may be captured in different metadata tags in different files (for example QuickTime:CreateDate, XMP-exif:DateTimeOriginal etc.) 3. Workaround suggested by Johannes Zarl-Zierl: Adjust your file modification dates exiftool -FileModifyDate\
