[plasmashell] [Bug 465706] New: crash for click cross for notification
https://bugs.kde.org/show_bug.cgi?id=465706 Bug ID: 465706 Summary: crash for click cross for notification Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mbartasevis...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.26.5) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 5.15.91-4-lts x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: As soon as the notification appears, I close and the desktop disappears The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fa8ceedaf95 in QtQml::qmlExecuteDeferred(QObject*) () at /usr/lib/libQt5Qml.so.5 #5 0x7fa8cf29a68e in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () at /usr/lib/libQt5Quick.so.5 #6 0x7fa8cf28f4c4 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () at /usr/lib/libQt5Quick.so.5 #7 0x7fa8cdaa5b56 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #8 0x7fa8ce6e5b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x7fa8cda81f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x7fa8cdacc4b3 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #11 0x7fa8cdaccaaa in () at /usr/lib/libQt5Core.so.5 #12 0x7fa8cbbaa82b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #13 0x7fa8cbc01cc9 in () at /usr/lib/libglib-2.0.so.0 #14 0x7fa8cbba90e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #15 0x7fa8cdaccc6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7fa8cda7a6ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7fa8cda85219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #18 0x5588266261ef in () #19 0x7fa8cd3f8790 in () at /usr/lib/libc.so.6 #20 0x7fa8cd3f884a in __libc_start_main () at /usr/lib/libc.so.6 #21 0x5588266265a5 in () [Inferior 1 (process 1158256) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466711] New: crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 Bug ID: 466711 Summary: crash when creating 2 concurrent folders/files Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: mbartasevis...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY PLAYBACK STEPS 1. Create > folder 2 times 2. Name different folders to create them 3. Click OK, and the crash of the desktop does not contain the possibility of collecting logs more. OBSERVED RESULT Crash desktop EXPECTED RESULT Ability to create 2 different folders at the same time SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-1-lts (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 15.1 ГиБ of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: ASUSTeK COMPUTER INC. Product Name: X556UAM System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 --- Comment #2 from Maksim --- I don't know how to show it, the desktop crashes in such a way that it is not noticeable for the debugger :| The error report appears, but after 10 seconds it disappears without having time to collect the logs This is all I can provide when using dgb some errors poll.o:43 process memory check did not reveal any errors (P.S After this command, now closing the console will turn off and the desktop, this did not happen before and I could freely close the console) At first I thought it was Dbus, but as shown, everything is fine with it ➜ ~ kstart plasmashell Omitting both --window and --windowclass arguments is not recommended kf.plasma.quick: Applet preload policy set to 1 Checking screens: available: (QScreen(0x556aeb942830, name="eDP1"), QScreen(0x556aeb9a4470, name="DP1")) redundant: QHash() fake: QSet() all: (QScreen(0x556aeb942830, name="eDP1"), QScreen(0x556aeb9a4470, name="DP1")) org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl) file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13: QML Label: Binding loop detected for property "height" Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:556:5: QML Label: Binding loop detected for property "height" Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml" Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml" file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:18:1: QML MouseArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout Both point size and pixel size set. Using pixel size. file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:69:9: QML GridLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" Loading Calendar plugin HolidaysEventsPlugin(0x556af5461690) file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout 13 Both point size and pixel size set. Using pixel size. file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Hea
[plasmashell] [Bug 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711
--- Comment #3 from Maksim ---
Perhaps I found the reason why this is happening to me, the lack of some
modules
Could not find the Plasmoid for Plasma::FrameSvgItem(0x56148f969aa0)
QQmlContext(0x5614993ad4c0)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
kde.systemtray: DBusMenu disabled for this application
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5:
QML Label: Binding loop detected for property "verticalAlignment"
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML
Heading: Binding loop detected for property "verticalAlignment"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
kde.systemtray: DBusMenu disabled for this application
CompileCommand: exclude
com/intellij/openapi/vfs/impl/FilePartNodeRoot.trieDescend bool exclude = true
kde.systemtray: DBusMenu disabled for this application
Gtk-Message: 11:55:19.410: Failed to load module "xapp-gtk3-module"
Gtk-Message: 11:55:19.410: Failed to load module "canberra-gtk-module"
2023-03-06 11:56:06,431 [ 55181] WARN -
#c.i.f.ProductivityFeaturesRegistryImpl - Feature with id
'codeassists.context.actions' is overridden by: id =
[codeassists.context.actions], displayName = [Context actions], groupId =
[codeassists], usageCount = [0]
2023-03-06 11:56:06,433 [ 55183] WARN -
#c.i.f.ProductivityFeaturesRegistryImpl - Feature with id
'codeassists.generate.code' is overridden by: id = [codeassists.generate.code],
displayName = [Generate code], groupId = [codeassists], usageCount = [0]
2023-03-06 11:56:06,438 [ 55188] WARN -
#c.i.f.ProductivityFeaturesRegistryImpl - Feature with id
'codeassists.quickdefinition' is overridden by: id =
[codeassists.quickdefinition], displayName = [Quick Definition lookup], groupId
= [codeassists], usageCount = [0]
org.kde.plasma.notifications: Trying to replace notification with id 4894 which
doesn't exist, creating a new one. This is an application bug!
Could not find the Plasmoid for Plasma::FrameSvgItem(0x561490647d10)
QQmlContext(0x5614993ad4c0)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x561490647d10)
QQmlContext(0x5614993ad4c0)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
2023-03-06 11:56:18,439 [ 67189] WARN - #c.i.d.PerformanceWatcherImpl - UI
was frozen for 8890ms, details saved to
/home/kotik9821/.var/app/com.jetbrains.CLion/cache/JetBrains
[plasmashell] [Bug 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 --- Comment #5 from Maksim --- (In reply to Nate Graham from comment #4) > Do you have some JetBrains app running that's constantly querying the > clipboard or something? To be honest, I don’t know myself, as if I’m looking into a blind zone), if I knew, maybe I would have said something. And no, I don't use JetBrains. Recently uninstalled, used to Visual Studio Code -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 --- Comment #7 from Maksim --- Yes -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469520] New: Error starting kdenlive in GPU mode
https://bugs.kde.org/show_bug.cgi?id=469520
Bug ID: 469520
Summary: Error starting kdenlive in GPU mode
Classification: Applications
Product: kdenlive
Version: 23.04.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: mbartasevis...@gmail.com
Target Milestone: ---
Application: kdenlive (23.04.0)
Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.1.27-1-lts x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.4 [KCrashBackend]
-- Information about the crash:
Every time I launch the app, it crashes and prompts me to disable GPU mode. I
know it's okay to not use this mode, but I want it fixed because I need this
mode.
The crash can be reproduced every time.
-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fe093adfdab in
std::__atomic_base::compare_exchange_strong(QMutexData*&,
QMutexData*, std::memory_order, std::memory_order)
(__m2=std::memory_order_acquire, __m1=std::memory_order_acquire, __p2=0x1,
__p1=: , this=0x58) at
/usr/include/c++/12.2.1/atomic:623
#7 std::atomic::compare_exchange_strong(QMutexData*&,
QMutexData*, std::memory_order, std::memory_order) (__p2=0x1,
__m1=std::memory_order_acquire, __m2=std::memory_order_acquire, __p1=: , this=0x58) at /usr/include/c++/12.2.1/atomic:625
#8
QAtomicOps::testAndSetAcquire(std::atomic&,
QMutexData*, QMutexData*, QMutexData**) (currentValue=,
newValue=0x1, expectedValue=0x0, _q_value=, _q_value=,
expectedValue=, newValue=,
currentValue=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:308
#9 QBasicAtomicPointer::testAndSetAcquire(QMutexData*,
QMutexData*, QMutexData*&) (currentValue=: ,
newValue=0x1, expectedValue=0x0, this=0x58) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:273
#10 QBasicMutex::fastTryLock(QMutexData*&) (current=:
, this=0x58) at thread/qmutex.h:128
#11 QMutex::lock() (this=this@entry=0x58) at thread/qmutex.cpp:232
#12 0x7fe093ae1e22 in QMutexLocker::QMutexLocker(QBasicMutex*) (m=0x58,
this=) at thread/qmutex.h:257
#13 QThread::exit(int) (this=, returnCode=0) at
thread/qthread.cpp:580
#14 0x7fe093ae1eac in QThread::quit() (this=) at
thread/qthread.cpp:601
#15 0x55a9f10d4ffb in onThreadJoin(mlt_properties, GLWidget*,
mlt_event_data) (owner=, self=, data=...) at
/usr/src/debug/kdenlive/kdenlive-23.04.0/src/monitor/glwidget.cpp:911
#16 0x7fe09690882a in mlt_events_fire () at /usr/lib/libmlt-7.so.7
#17 0x7fe096908f6a in mlt_consumer_stop () at /usr/lib/libmlt-7.so.7
#18 0x55a9f10d67c2 in GLWidget::stop() (this=0x55a9f4a91190) at
/usr/include/c++/12.2.1/bits/shared_ptr_base.h:1665
#19 0x55a9f10da481 in GLWidget::setProducer(std::shared_ptr
const&, bool, int) (this=0x55a9f4a91190,
producer=std::shared_ptr (use count 1, weak count 0) = {...},
isActive=, position=0) at
/usr/src/debug/kdenlive/kdenlive-23.04.0/src/monitor/glwidget.cpp:1007
#20 0x55a9f13624f1 in ProjectManager::updateTimeline(int, bool, QString
const&, QString const&, QDateTime const&, bool) [clone .constprop.0]
(this=this@entry=0x55a9f2512590, pos=pos@entry=0, chunks=..., dirty=...,
documentDate=..., enablePreview=enablePreview@entry=false, createNewTab=true)
at /usr/src/debug/kdenlive/kdenlive-23.04.0/src/project/projectmanager.cpp:1279
#21 0x55a9f1149812 in ProjectManager::newFile(QString, bool)
(this=this@entry=0x55a9f2512590, profileName=...,
showProjectSettings=) at
/usr/src/debug/kdenlive/kdenlive-23.04.0/src/project/projectmanager.cpp:252
#22 0x55a9f114a5e3 in ProjectManager::newFile(bool)
(this=this@entry=0x55a9f2512590,
showProjectSettings=showProjectSettings@entry=false) at
/usr/src/debug/kdenlive/kdenlive-23.04.0/src/project/projectmanager.cpp:157
#23 0x55a9f114bcea in ProjectManager::slotLoadOnOpen()
(this=0x55a9f2512590) at
/usr/src/debug/kdenlive/kdenlive-23.04.0/src/project/projectmanager.cpp:114
#24 0x7fe093cb1c80 in QObject::event(QEvent*) (this=0x55a9f2512590,
e=0x55a9f57e4bf0) at kernel/qobject.cpp:1347
#25 0x7fe094f78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55a9f2512590, e=0x55a9f57e4bf0) at
kernel/qapplication.cpp:3640
#26 0x7fe093c8e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55a9f2512590, event=0x55a9f57e4bf0) at
kernel/qcoreapplication.cpp:1064
#27 0x7fe093c8e093 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#28 0x7fe093c8eb33 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55a9f1dbec50) at
kernel/qcoreapplication.cpp:1821
#29 0x7fe093cd4f58 in postEventSourceDispatch(GSource*, GSourceFun
[Bluedevil] [Bug 489699] New: Wise bluetooth hangling with dualboot
https://bugs.kde.org/show_bug.cgi?id=489699 Bug ID: 489699 Summary: Wise bluetooth hangling with dualboot Classification: Plasma Product: Bluedevil Version: 6.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: maksim.mur...@gmail.com Target Milestone: --- If you have dualboot in my case Manjaro/Kubuntu you have BT pairing issue because device uses the same MAC and if you pare you headphones with Ubuntu in Manjaro you will get an error. Solutions can be - Different macs (change macs not really convenient) - Reuse pair mode. Right now my headphones in pair mode but I still cannot connect I have to remove device use search select and reconnect, will be really nice if those steps will be done automatically so if no possible to connect and device in pair mode reconnect with new keys. - another thing nice to have autoreconnect heaphones from another device (smartphone). If I'm trying to connect to currently connected headphones I just got LE connect. And can disconnect in old Plasma version 5.x.x it also disconnect from phone so only one step to automate this to connect to PC. It will be really convenient you just press one button and system reconnect heaphones to itself (in new 6.x.x seems like disconnect not lead to disconnect from phone probably it was bug.. but quite useful if you add next step) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484779] Add ability to select/deselect all
https://bugs.kde.org/show_bug.cgi?id=484779 --- Comment #3 from Maksim --- Created attachment 168965 --> https://bugs.kde.org/attachment.cgi?id=168965&action=edit SlideShow section Exact section we are talking about -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484779] Add ability to select/deselect all
https://bugs.kde.org/show_bug.cgi?id=484779 Maksim changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|FIXED |--- --- Comment #4 from Maksim --- (In reply to Nate Graham from comment #1) > It's not possible to rotate wallpapers in this view. Which action are you > hoping to apply to all of them if you could select multiple items? We are > talking about the Plasma wallpaper chooser grid, right? We talking about slideshow -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 484779] New: Impossible do select/deselect all
https://bugs.kde.org/show_bug.cgi?id=484779 Bug ID: 484779 Summary: Impossible do select/deselect all Classification: Plasma Product: Plasma Workspace Wallpapers Version: 5.27.80 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: maksim.mur...@gmail.com Target Milestone: --- In wallpapers selector impossible do select all, if for example I want only couple wallpapers in rotation by default it selects all, and quite opposite. Also is not possible order by selected, an by groups (check box exists but not indication which images with which) Also will be really great if possible grouping wallpapers by mouse, not only by folders -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484781] New: Sound crash with HDMI output
https://bugs.kde.org/show_bug.cgi?id=484781 Bug ID: 484781 Summary: Sound crash with HDMI output Classification: Applications Product: dolphin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: maksim.mur...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Sound completely crashed in and show no outputs. If I connect HDMI output device and disable it in "Display settings" this lead to empty sound outputs! I still can use HDMI on reconnect, but no standard output soundcard anymore in list. Reason why I'm trying to do so, I want connect HDMI headphones, but HDMI itself incapable transfer sound without video, do it created 'virtual monitor' which unfortunate counts with system (no way setup it like 1 pixel size), or split it from board for not used spaces by windows. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484782] New: Dolphin save point only on exit
https://bugs.kde.org/show_bug.cgi?id=484782 Bug ID: 484782 Summary: Dolphin save point only on exit Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: maksim.mur...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin does save layout on, program correct exit, but in reality you need it most on sudden crashes, or kills. For now it pickup save from previous successful shutdown. Which is can be not exactly what user want. Make more sense save layout exactly after it active, as many IDEs does for keep work save. Save on change no on exist. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441517] New: Multiple instances of the same android device
https://bugs.kde.org/show_bug.cgi?id=441517 Bug ID: 441517 Summary: Multiple instances of the same android device Product: dolphin Version: 21.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: hyxab...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 141025 --> https://bugs.kde.org/attachment.cgi?id=141025&action=edit Multiple instances of the same android device SUMMARY Multiple instances of the same android device STEPS TO REPRODUCE 1. install KDE Connect 2. Connect to Android device multiple times (i suppose) OBSERVED RESULT Multiple instances of the same android device EXPECTED RESULT A single instance of the same android device SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest Manjaro, KDE 5.22.4 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 475960] New: Kde connect crash each time
https://bugs.kde.org/show_bug.cgi?id=475960 Bug ID: 475960 Summary: Kde connect crash each time Classification: Applications Product: kdeconnect Version: 23.08.1 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: maksim.mur...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-9-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Kubuntu 23.10 constant crash the app. Just from sleep mode of laptop. Probably related to some exceptions which occures in socket The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f2de644ae04 in Device::reloadPlugins() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #5 0x7f2de644bf54 in Device::addLink(DeviceLink*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #6 0x7f2de6446e03 in Daemon::onNewDeviceLink(DeviceLink*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #7 0x7f2de4d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2de64268d3 in LinkProvider::onConnectionReceived(DeviceLink*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #9 0x7f2de64316a4 in LanLinkProvider::addLink(QSslSocket*, DeviceInfo const&) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #10 0x7f2de64322a6 in LanLinkProvider::encrypted() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #11 0x7f2de4d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2de4586733 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f2de458ceea in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #14 0x7f2de458d6c3 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7f2de4d0602d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f2de453c577 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7f2de454f229 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #18 0x7f2de596bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f2de4ccc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f2de4d28955 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f2de3713b2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f2de376f46f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f2de3711d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f2de4d27dc6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f2de4ccb15b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f2de4cd3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x56516d316058 in ?? () #28 0x7f2de42280d0 in __libc_start_call_main (main=main@entry=0x56516d315bd0, argc=argc@entry=1, argv=argv@entry=0x7ffc557c02b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #29 0x7f2de4228189 in __libc_start_main_impl (main=0x56516d315bd0, argc=1, argv=0x7ffc557c02b8, init=, fini=, rtld_fini=, stack_end=0x7ffc557c02a8) at ../csu/libc-start.c:360 #30 0x56516d316275 in ?? () [Inferior 1 (process 59635) detached] The reporter indicates this bug may be a duplicate of or related to bug 475054. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476462] New: Plasma colors unexpectedly when I click on the cross in the notification
https://bugs.kde.org/show_bug.cgi?id=476462 Bug ID: 476462 Summary: Plasma colors unexpectedly when I click on the cross in the notification Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mbartasevis...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) Qt Version: 5.15.11 Frameworks Version: 5.110.0 Operating System: Linux 6.5.7-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: When my RAM is full, I often use the swap file, but sometimes unexpectedly when I click on the cross, the plasma crashes and zoom and VScodium crashes, but after some updates, now some applications do not crash along with the plasma crash The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x148ebbc3fc0d in QtQml::qmlExecuteDeferred(QObject*) () at /usr/lib/libQt5Qml.so.5 #5 0x148ebc150c8e in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () at /usr/lib/libQt5Quick.so.5 #6 0x148ebc145743 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () at /usr/lib/libQt5Quick.so.5 #7 0x148eba6c3b4e in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #8 0x148ebb3788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x148eba69c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x148eba6ea7cb in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #11 0x148eba6eadba in () at /usr/lib/libQt5Core.so.5 #12 0x148eb9231f19 in () at /usr/lib/libglib-2.0.so.0 #13 0x148eb92902b7 in () at /usr/lib/libglib-2.0.so.0 #14 0x148eb9230112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #15 0x148eba6eaf7c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x148eba69ae74 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x148eba69c313 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #18 0x5648ac98516c in () #19 0x148eb9e45cd0 in () at /usr/lib/libc.so.6 #20 0x148eb9e45d8a in __libc_start_main () at /usr/lib/libc.so.6 #21 0x5648ac985515 in () [Inferior 1 (process 1418148) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437797] New: Spectacle crashed after closing it
https://bugs.kde.org/show_bug.cgi?id=437797 Bug ID: 437797 Summary: Spectacle crashed after closing it Product: Spectacle Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rogoz...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.6-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I just press 'X' close button and it crashed. It happened every time. The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7f61937e3205 in kImageAnnotator::FontPicker::~FontPicker() () from /lib64/libkImageAnnotator.so.0 #5 0x7f61937a8105 in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings() () from /lib64/libkImageAnnotator.so.0 #6 0x7f61937a84a2 in kImageAnnotator::AnnotationWidget::~AnnotationWidget() () from /lib64/libkImageAnnotator.so.0 #7 0x7f619379e61b in kImageAnnotator::CoreView::~CoreView() () from /lib64/libkImageAnnotator.so.0 #8 0x7f61937a0c7d in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib64/libkImageAnnotator.so.0 #9 0x7f61937a0e6d in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib64/libkImageAnnotator.so.0 #10 0x7f6191e62eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #11 0x7f6192907f66 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #12 0x55e264692461 in KSWidget::~KSWidget() () #13 0x7f6191e62eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #14 0x7f6192907f66 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #15 0x55e264697715 in SpectacleCore::~SpectacleCore() () #16 0x55e26468f99f in main () [Inferior 1 (process 18196) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461806] New: Pipe in dir name prevent copy-paste
https://bugs.kde.org/show_bug.cgi?id=461806 Bug ID: 461806 Summary: Pipe in dir name prevent copy-paste Classification: Applications Product: dolphin Version: 22.08.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: maksim.mur...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** Dolphin unable copy-paste dir and content in it with pipe in name for example 'auth0|5a9acd0698661d293380ff' dir like this lead to fail. But I can rename it and replace pipe for - and when it works! *** STEPS TO REPRODUCE 1. create dir with name 'auth0|5a9acd0698661d293380ff' 2. open second tab with dest folder 3. dran`n`drop or copy-paste to second panel OBSERVED RESULT Failed to copy EXPECTED RESULT Just copy pasted SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 384995] No autorefresh sound devices on hardware change.
https://bugs.kde.org/show_bug.cgi?id=384995 Maksim changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #5 from Maksim --- (In reply to Christoph Feck from comment #1) > Which list? Could you please be more detailed where you click to get this > list? It could be in systemsettings5, in the Plasma widget, or even in an > application that is not developed by KDE developers. Yes. Just list in 'Advanced' -> Device Profiles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375331] Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 Maksim changed: What|Removed |Added CC||l...@maxikon.eu --- Comment #4 from Maksim --- Almost similar situation - actually problem occurs both ways, but not always. Example: @home no external display attached, booted up, works. Suspend to RAM, next day @work plug to dock with 2 external displays, open lid and whole system freezes, only option is to do a hard shutdown. After booting up laptop + 2 displays works like a charm, no changes needed. Suspend to RAM. @home resume from RAM, mouse pointer is visible on far left, not moving. Blindly log in then xrandr --auto works. Lenovo T460s (but similar problem happened with HP Elitebook 8470p + dock + 1 external display). Plasma 5.8.5 Fedora 24 (4.9.9-100.fc24.x86_64) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 384995] New: No autorefresh sound devices on hardware change.
https://bugs.kde.org/show_bug.cgi?id=384995 Bug ID: 384995 Summary: No autorefresh sound devices on hardware change. Product: frameworks-kconfig Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: maksim.mur...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- I have HDMI headphone between my monitor and laptop. Then I switch on Headphones device no appears in the list. I have to boot KDE with headphones station power on in that case everything almost perfect. No issue with Ubuntu Unity like this, so its only KDE problem. As minor problem after sleep mode I cant have sound in my HDMI output until I switch back to internal sound card and back to HDMI. And no switch back to internal sound card then HDMI output is disabled. So system completely ignore events like this. I have to handle everything manually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462694] kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 Maksim Melnikau changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #11 from Maksim Melnikau --- I don't have issues anymore (mesa update probably helped) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442599] New: okular crashes on pdf reload
https://bugs.kde.org/show_bug.cgi?id=442599 Bug ID: 442599 Summary: okular crashes on pdf reload Product: okular Version: 21.08.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: maxpose...@gmail.com Target Milestone: --- Application: okular (21.08.0) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.5-gentoo-x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: 1. open pdf file (beamer presentation which I'm preparing now) 2. start presention mode 3. continues editing beamer tex, and recompiling pdf from time to time 4. everything works 5. suddenly (on reload) okular crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Okular (okular), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f7501057140 (LWP 57723))] [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7f7504e47536 in __GI_abort () at abort.c:79 #8 0x7f7504e9e658 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f7504fab5bd "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 #9 0x7f7504f2bc22 in __GI___fortify_fail (msg=msg@entry=0x7f7504fab5a5 "stack smashing detected") at fortify_fail.c:26 #10 0x7f7504f2bc00 in __stack_chk_fail () at stack_chk_fail.c:24 #11 0x7f75044bcce8 in __pthread_cond_wait (cond=0x7ffd67c26260, mutex=0x557ab0ddcea8) at pthread_cond_wait.c:620 #12 0x7f750473bed1 in _xcb_conn_wait (c=c@entry=0x557ab0ddce90, cond=cond@entry=0x7ffd67c26260, vector=vector@entry=0x0, count=count@entry=0x0) at /usr/src/debug/x11-libs/libxcb-1.14/libxcb-1.14/src/xcb_conn.c:448 #13 0x7f750473dd6f in wait_for_reply (c=c@entry=0x557ab0ddce90, request=81761, e=e@entry=0x0) at /usr/src/debug/x11-libs/libxcb-1.14/libxcb-1.14/src/xcb_in.c:516 #14 0x7f750473de81 in xcb_wait_for_reply (c=0x557ab0ddce90, request=81761, e=e@entry=0x0) at /usr/src/debug/x11-libs/libxcb-1.14/libxcb-1.14/src/xcb_in.c:532 #15 0x7f75047446e5 in xcb_get_property_reply (c=, cookie=..., e=e@entry=0x0) at xproto.c:3713 #16 0x7f7506a50f32 in xcb_icccm_get_wm_hints_reply (c=, cookie=..., hints=hints@entry=0x7ffd67c26330, e=e@entry=0x0) at /usr/src/debug/x11-libs/xcb-util-wm-0.4.1-r3/xcb-util-wm-0.4.1/icccm/icccm.c:778 #17 0x7f7500aee859 in QXcbWindow::setWindowState (this=0x557ab1aefeb0, state=...) at /usr/src/debug/dev-qt/qtgui-5.15.2-r1/qtbase-everywhere-src-5.15.2/src/plugins/platforms/xcb/qxcbwindow.cpp:1154 #18 0x7f75058b5a2c in QWindow::setWindowStates (this=0x557ab1e5fac0, state=..., state@entry=...) at /usr/src/debug/dev-qt/qtgui-5.15.2-r1/qtbase-everywhere-src-5.15.2/src/gui/kernel/qwindow.cpp:1367 #19 0x7f7505e920e0 in QWidget::setWindowState (this=this@entry=0x557ab1cbcca0, newstate=...) at /usr/src/debug/dev-qt/qtwidgets-5.15.2/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:2931 #20 0x7f74f99dfe94 in PresentationWidget::setScreen (this=this@entry=0x557ab1cbcca0, newScreen=) at /var/tmp/portage/kde-apps/okular-21.08.0/work/okular-21.08.0/part/presentationwidget.cpp:1602 #21 0x7f74f99dfff0 in PresentationWidget::slotDelayedEvents (this=0x557ab1cbcca0) at /var/tmp/portage/kde-apps/okular-21.08.0/work/okular-21.08.0/part/presentationwidget.cpp:1514 #22 0x7f7505476efa in QObject::event (this=0x557ab1cbcca0, e=0x557ab1e6eda0) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:1314 #23 0x7f7505e5614f in QApplicationPrivate::notify_helper (this=, receiver=0x557ab1cbcca0, e=0x557ab1e6eda0) at /usr/src/debug/dev-qt/qtwidgets-5.15.2/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3632 #24 0x7f750544fd98 in QCoreApplication::notifyInternal2 (receiver=0x557ab1cbcca0, event=0x557ab1e6eda0) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1063 #25 0x7f7505452a1a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x557ab0dc3570) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1817 #26 0x7f750549b133 in postEventSourceDispatch (s=0x557ab0e302e0) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:277 #27 0x7f7503b1542b in g_main_dispatch (context=0x7f74fc005000) at ../glib-2.68.3/glib/gmain.c:3337 #28 g_main_context_dispatch (context=0x7f74fc005000) at ../glib-2.68.3/glib/gmain.c:4055 #29 0x7f7503b156d8 in g_main_context_iterate (cont
[kdenlive] [Bug 474362] Segmentation fault on opening a project
https://bugs.kde.org/show_bug.cgi?id=474362 Maksim K. changed: What|Removed |Added CC||maksim.e.koz...@gmail.com --- Comment #3 from Maksim K. --- Have the same problem with new projects - kdenlive crashes (sometime hangs) on startup after some number of open-edit-save-close "cycles" of editing. OS: FreeBSD 13.2-RELEASE-p3 kdenlive-23.08.1 (installed from ports) mlt7-7.18.0 There was not such problem with kdenlive-22.12.0 & mlt7-7.10.0 which I uses previously -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474362] Segmentation fault on opening a project
https://bugs.kde.org/show_bug.cgi?id=474362 --- Comment #4 from Maksim K. --- After some investigation I think I found workaround for my case (FreeBSD). I launched kdenlive in gdb and saw that kdenlive creates a lot of threads (more then 16000 at the crash/hang time): Thread 16138 received signal SIGSEGV, Segmentation fault. Address not mapped to object. [Switching to LWP 462857 of process 40657] 0x000814ac6d9d in ?? () from /usr/local/lib/mlt-7/libmltavformat.so (gdb) bt #0 0x000814ac6d9d in () at /usr/local/lib/mlt-7/libmltavformat.so #1 0x000800eebf35 in mlt_frame_get_audio () at /usr/local/lib/libmlt-7.so.7 #2 0x000814ad0514 in () at /usr/local/lib/mlt-7/libmltavformat.so #3 0x000800eebf35 in mlt_frame_get_audio () at /usr/local/lib/libmlt-7.so.7 #4 0x0008145d8d9e in () at /usr/local/lib/mlt-7/libmltcore.so #5 0x000800eebf35 in mlt_frame_get_audio () at /usr/local/lib/libmlt-7.so.7 #6 0x000800ee883d in () at /usr/local/lib/libmlt-7.so.7 #7 0x0008044dea78 in () at /lib/libthr.so.3 #8 0x in () (gdb) info threads Id Target Id Frame 1LWP 115972 of process 406570x00080574c29c in ?? () from /usr/local/lib/libfreetype.so.6 2LWP 446587 of process 406570x00080416029a in _poll () from /lib/libc.so.7 3LWP 446588 of process 40657 "pool-spawner" 0x0008044dbd2c in ?? () from /lib/libthr.so.3 4LWP 446589 of process 40657 "gmain"0x00080416029a in _poll () from /lib/libc.so.7 5LWP 446590 of process 40657 "gdbus"0x00080416029a in _poll () from /lib/libc.so.7 6LWP 446591 of process 406570x00080416029a in _poll () from /lib/libc.so.7 7LWP 446592 of process 406570x0008041601da in _kevent () from /lib/libc.so.7 9LWP 446623 of process 406570x00080416029a in _poll () from /lib/libc.so.7 10 LWP 446624 of process 406570x00080416029a in _poll () from /lib/libc.so.7 11 LWP 446625 of process 406570x00080416029a in _poll () from /lib/libc.so.7 12 LWP 446626 of process 406570x00080416029a in _poll () from /lib/libc.so.7 13 LWP 446627 of process 406570x00080416029a in _poll () from /lib/libc.so.7 14 LWP 446628 of process 406570x00080416029a in _poll () from /lib/libc.so.7 15 LWP 446629 of process 406570x00080416029a in _poll () from /lib/libc.so.7 16 LWP 446630 of process 406570x00080416029a in _poll () from /lib/libc.so.7 17 LWP 446631 of process 406570x00080416029a in _poll () from /lib/libc.so.7 27 LWP 446642 of process 406570x0008041602ba in _ppoll () from /lib/libc.so.7 28 LWP 446643 of process 406570x0008041602ba in _ppoll () from /lib/libc.so.7 40 LWP 446657 of process 40657 "dconf worker" 0x00080416029a in _poll () from /lib/libc.so.7 57 LWP 446693 of process 40657 "av:h264:df0" 0x0008044dbd2c in ?? () from /lib/libthr.so.3 58 LWP 446694 of process 40657 "av:h264:df1" 0x0008044dbd2c in ?? () from /lib/libthr.so.3 59 LWP 446695 of process 40657 "av:h264:df2" 0x0008044dbd2c in ?? () from /lib/libthr.so.3 60 LWP 446696 of process 40657 "av:h264:df3" 0x0008044dbd2c in ?? () from /lib/libthr.so.3 ... 16134 LWP 462821 of process 40657 "av:h264:df15" 0x0008044dbd2c in ?? () from /lib/libthr.so.3 16135 LWP 462822 of process 406570x0008044dbd2c in ?? () from /lib/libthr.so.3 16136 LWP 462855 of process 40657 "PulseHotplug" 0x0008041602ba in _ppoll () from /lib/libc.so.7 16137 LWP 462856 of process 406570x0008044dbd2c in ?? () from /lib/libthr.so.3 * 16138 LWP 462857 of process 406570x000814ac6d9d in ?? () from /usr/local/lib/mlt-7/libmltavformat.so At the same time, I have in my system: kern.maxthread: 100 kern.threads.max_threads_hits: 7135 kern.threads.max_threads_per_proc: 2048 max_threads_hits is just a count, as I understand, which show how many times we reached threads limit. So I increased max_threads_per_proc value iterately (with reboot) and found that max_threads_hits decreases on every iteratition (after launch kdenlive) and become 0 when max_threads_per_proc reached 16384 and kdelive launch my project corretly without crash. So, now I set max_threads_per_proc=32768 and it seems that this resolves my problem But I beleave that "low" number of threads in system settings is not root cause of the problem. This is because, my previous project was large: ~1700 clips vs carrent has ~1200, but I had no problem with previous version of Kdenlive (22.12.0). Also, it is a question
[kwin] [Bug 462694] kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 --- Comment #10 from Maksim Melnikau --- (In reply to Maksim Melnikau from comment #3) > (In reply to Vlad Zahorodnii from comment #2) > > What version of Mesa do you have on your computer? > =media-libs/mesa-22.2.3 After updating to mesa-22.3.0 system become more stable --- I don't have such issues few days already (previously few timers per day). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463665] New: Everything on the screen is frozen.
https://bugs.kde.org/show_bug.cgi?id=463665 Bug ID: 463665 Summary: Everything on the screen is frozen. Classification: Plasma Product: kwin Version: 5.26.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: timoha9...@mail.ru Target Milestone: --- SUMMARY Everything on the screen is frozen. STEPS TO REPRODUCE This happened while working in the Firefox browser (nothing special, a plain text Wikipedia webpage was opened). OBSERVED RESULT The image froze: all widgets did not respond to actions with them, window switching did not work, windows did not minimize, did not move, the contents of the windows also did not respond to actions, etc. Only the mouse cursor moved. EXPECTED RESULT - SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 5.10.154-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Pentium® Silver N5000 CPU @ 1.10GHz Memory: 7.6 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics 605 ADDITIONAL INFORMATION Sorry for such a big text. I couldn't describe it briefly. For several years I have been seeing this problem on different operating systems with KDE (Kubuntu, Manjaro KDE, KDE Neon) and on different computers with different hardware: after using the computer for a long time without rebooting (for several weeks), the PC starts to slow down a lot: all desktop effect animations turn into a "slideshow", the reaction to user actions becomes very long. At the same time, the "Xorg" process consumes 10-20% of the CPU, even if all user applications are closed. Restarting the "plasmashell" process only slightly improved the situation, but not for long. The last time it ended up being that while working in the Firefox browser (nothing special, a Wikipedia text web page was opened), the image froze: all widgets did not respond to actions with them, window switching did not work, windows did not minimize, did not move , the contents of the windows also did not respond to actions, etc. Only the mouse cursor moved. The system did not react to the call of the "konsole" terminal (ctrl+alt+t), more precisely, the new window did not appear on the screen. Logging in to tty2, in another session as a different user (the graphical interface did not automatically start, I started it with the "Startx" command), I looked at the list of processes, CPU and memory load, in order to exclude a memory leak in the "plasmashell", as it happened before. But there were no problems with this. In the process list, I saw several dozen "konsole" processes running in the problematic session. I killed them, went back to tty1 with the problematic session, called "konsole" (ctrl+alt+t) again a few dozen times, returned to the session in tty2 and saw in the list of processes these new "konsole" processes (running as user in problematic session) - it means that the "broken" session worked, only the image froze. In tty2, I tried to kill the "plasmashell" process of the broken session, so that I can start it again later. Went back to the broken tty1 session - didn't help. Further, in tty2, just in case, I killed unnecessary applications, such as Skype - it did not help. I further thought that if "konsole" opens but is not displayed on the screen, then the problem might be with the "kwin_x11" window manager. I killed the process "kwin_x11" of session tty1 via session in tty2. When I switched back to the tty1 session, I found that everything worked. Then I called "konsole" again, ran "plasmashel" and everything worked perfectly, as if I rebooted the computer. Before killing "kwin_x11", I checked the CPU and memory consumption of this process: there was no excessive memory and CPU consumption by the "kwin_x11" process - about 20 MB. I think the appearance of these problems lies in the "kwin_x11" process. And one more thing (maybe important): at the time of the crash, RAM consumption was close to the maximum - ~6.5GB out of 7.6GB and swap ~6GB out of 8GB. This is not a memory leak. Just a large number of running applications and data (mostly many tabs in browsers). And I have such a high memory consumption all the time. (In my computer, you cannot increase the amount of RAM). Maybe using swap somehow affects the problem? Although after restarting "kwin_x11" I did not close applications and did not release RAM and swap and everything worked perfectly. I haven't even restarted my computer since. Specifically, this problem with a complete freeze of the desktop could not be reproduced. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447678] "plasmashell" is froze and began 100% 1 core cpu usage and unlimited memory consumption when opening the "Notifications" applet
https://bugs.kde.org/show_bug.cgi?id=447678 Maksim Timofeev changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Maksim Timofeev --- (In reply to Nate Graham from comment #3) > Thank you for reporting this issue in KDE software. As it has been a while > since it was reported, can we please ask you to see if you can reproduce the > issue with a recent software version? Like Plasma 5.25, or ideally 5.26? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Hello dear Nate Graham. I tried to reproduce the problem in KDE Plasma versions 5.23.4, 5.23.5, 5.24.4, 5.26.3, but the problem never showed up. Perhaps this problem is related to something else, it just manifested itself at the time of interaction with the Notifications applet. This has happened before while working in different applications (more often when working in the Firefox browser). Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462484] New: Incorrect display of notifications
https://bugs.kde.org/show_bug.cgi?id=462484 Bug ID: 462484 Summary: Incorrect display of notifications Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: timoha9...@mail.ru CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY Incorrect display of notifications. STEPS TO REPRODUCE 1. Open the Notifications applet (25.11.2022); 2. Click the "Show more" button (screenshot 1). The "Show less" button is superimposed on the notification title from below (screenshot 2); 3. Click the "Show less" button; 4. Click the "Show more" button again - does not work (screenshot 3); (25.11.2022 - after screenshots i uploaded some more files via Firefox browser). Next day (26.11.2022): 5. Open the Notifications applet. Violated sorting of notifications by date (screenshot 4); 6. Click the "Show more" button. This time there was an overlay of notifications about yesterday's downloads. Notifications about loading the first and third files were superimposed, and the second file was above them (screenshot 5); 7. Click the "Show less" button. 8. The "Show more" button is superimposed on the notification title from below (screenshot 6); 8. Click the "Show more" button again - does not work (screenshot 6). OBSERVED RESULT Described above, see screenshots. EXPECTED RESULT Correct display of notifications. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 5.10.154-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Pentium® Silver N5000 CPU @ 1.10GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 605 ADDITIONAL INFORMATION Firefox notifications always stay at the top of the list, regardless of the last notification date. Links to screenshots: https://cloud.mail.ru/public/1R8t/Ebcrmq2cH https://cloud.mail.ru/public/d9uH/sy6Ck1Gk8 https://cloud.mail.ru/public/hHiF/nSBjJ7dnh https://cloud.mail.ru/public/zrQ7/cZPNAts3q https://cloud.mail.ru/public/KN5p/48Hb9VSv5 https://cloud.mail.ru/public/jUJZ/YgGFQhqAi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462694] New: kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 Bug ID: 462694 Summary: kwin_x11 freeze forever after alt+tab Classification: Plasma Product: kwin Version: 5.26.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: maxpose...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. usual system usage 2. multiple regular alt-tab 3. 99.99% everything works correctly but sometimes ... OBSERVED RESULT everything frozen forever, music plays, but interface completely frozen kill -s KILL (SIGQUIT) from terminal helps, after this everything woks fine for some time EXPECTED RESULT normal work Operating System: Gentoo Linux 2.9 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.5 Kernel Version: 6.0.10-gentoo-dist (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION coredumpctl info 36778 PID: 36778 (kwin_x11) UID: 1001 (max_posedon) GID: 1001 (max_posedon) Signal: 3 (QUIT) Timestamp: Tue 2022-12-06 11:27:26 EET (9min ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1001.slice/user@1001.service/session.slice/plasma-kwin_x11.service Unit: user@1001.service User Unit: plasma-kwin_x11.service Slice: user-1001.slice Owner UID: 1001 (max_posedon) Boot ID: 543bfd3665884ef9a659e8c1328f8176 Machine ID: be1598bd68baa268cb48e33d000f Hostname: LT1-LL-008 Storage: /var/lib/systemd/coredump/core.kwin_x11.1001.543bfd3665884ef9a659e8c1328f8176.36778.167031884600.zst (present) Size on Disk: 5.3M Message: Process 36778 (kwin_x11) of user 1001 dumped core. Module libplasmacomponentsplugin.so without build-id. Module libqtquickcontrolsplugin.so without build-id. Module libqtquicktemplates2plugin.so without build-id. Module libwindowplugin.so without build-id. Module libqmlplugin.so without build-id. Module libplasmaextracomponentsplugin.so without build-id. Module libOpenGL.so.0 without build-id. Module libKF5QuickAddons.so.5 without build-id. Module libKF5PlasmaQuick.so.5 without build-id. Module libcorebindingsplugin.so without build-id. Module libqquicklayoutsplugin.so without build-id. Module libQt5QmlWorkerScript.so.5 without build-id. Module libqtquick2plugin.so without build-id. Module libqsvg.so without build-id. Module libjpeg.so.62 without build-id. Module libqjpeg.so without build-id. Module libqico.so without build-id. Module libqgif.so without build-id. Module kimg_xcf.so without build-id. Module kimg_tga.so without build-id. Module kimg_rgb.so without build-id. Module kimg_ras.so without build-id. Module kimg_psd.so without build-id. Module kimg_pic.so without build-id. Module kimg_pcx.so without build-id. Module kimg_ora.so without build-id. Module kimg_kra.so without build-id. Module kimg_hdr.so without build-id. Module kimg_ani.so without build-id. Module libKF5ThreadWeaver.so.5 without build-id. Module libKF5Runner.so.5 without build-id. Module krunnerintegration.so without build-id. Module MouseButtonToKeyPlugin.so without build-id. Module colordintegration.so without build-id. Module libKWinNightColorPlugin.so without build-id. Module libxcb-res.so.0 without build-id. Module KF5WindowSystemX11Plugin.so without build-id. Module breezedecoration.so without build-id. Module libKF5Style.so.5 without build-id. Module libbreezecommon5.so.5 without build-id. Module libKF5Kirigami2.so.5 without build-id. Module breeze.so without build-id. Module libpciaccess.so.0 without build-id. Module libxml2.so.2 without build-id. Module libtinfo.so.6 without build-id. Module libdrm_intel.so.1 without build-id. Module libdrm_nouveau.so.2 without build-id. Module libLLVM-15.so without build-id. Module libxcb-present.so.0 without build-id. Module libxcb-dri3.so.0 without build-id
[kwin] [Bug 462694] kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 --- Comment #1 from Maksim Melnikau --- Created attachment 154353 --> https://bugs.kde.org/attachment.cgi?id=154353&action=edit kwin_x11 thread apply all bt with symbols core is too big (compressed 6Mb) may be at least backtrace with symbols will be useful it is generated after SIGQUIT on frozen process -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462694] kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 --- Comment #3 from Maksim Melnikau --- (In reply to Vlad Zahorodnii from comment #2) > What version of Mesa do you have on your computer? =media-libs/mesa-22.2.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462694] kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 --- Comment #5 from Maksim Melnikau --- (In reply to Vlad Zahorodnii from comment #4) > _Might_ be related to bug 461316. I saw weird freezing when it occurred. FYI, I took test from attachment (compile, run) --- not reproduced. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462694] kwin_x11 freeze forever after alt+tab
https://bugs.kde.org/show_bug.cgi?id=462694 Maksim Melnikau changed: What|Removed |Added Attachment #154353|0 |1 is obsolete|| --- Comment #6 from Maksim Melnikau --- Created attachment 154424 --> https://bugs.kde.org/attachment.cgi?id=154424&action=edit thread apply all bt full on frozen kwin_x11 very verbose backtrace on frozen kwin_x11 (it happens once per ~3-4 hours) -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] New: Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494
Bug ID: 378494
Summary: Debugee terminates on any signal
Product: Heaptrack
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: m...@milianw.de
Reporter: maxim.go...@gmail.com
Target Milestone: ---
Created attachment 104899
--> https://bugs.kde.org/attachment.cgi?id=104899&action=edit
A reproducer which handles SIGTERM
When running under heaptrack, a debuggee is terminated upon receiving any
signal even when it handles that signal. As a result, no memory cleanup on
shutdown happens and heaptrack reports false positives for memory leaks.
OS: Centos 7.2
Heaptrack version: c513793b
Reproduction steps:
# Build
~/work/heaptrack-eval $ g++ -std=c++11 -pthread test.cpp
# Interrupt by Ctrl-C
~/work/heaptrack-eval $ ./a.out
Started, press Ctrl-C to abort
^CInterrupted
Done.
# Interrrupt by "kill -TERM `pidof a.out`"
~/work/heaptrack-eval $ ./a.out
Started, press Ctrl-C to abort
Interrupted
Done.
# Run under heaptrack and interrupt by "kill -TERM `pidof a.out`"
~/work/heaptrack-eval $ heaptrack ./a.out
heaptrack output will be written to
"/home/centos/work/heaptrack-eval/heaptrack.a.out.20509.gz"
starting application, this might take some time...
Started, press Ctrl-C to abort
heaptrack stats:
allocations:2
leaked allocations: 2
temporary allocations: 0
/usr/local/bin/heaptrack: line 195: 20525 Terminated
LD_PRELOAD=$LIBHEAPTRACK_PRELOAD${LD_PRELOAD:+:$LD_PRELOAD}
DUMP_HEAPTRACK_OUTPUT="$pipe" "$client" "$@"
Heaptrack finished! Now run the following to investigate the data:
heaptrack_print "/home/centos/work/heaptrack-eval/heaptrack.a.out.20509.gz" |
less
# Check for leaks - `p` is not freed
centos@maxim-dev7 ~/work/heaptrack-eval $ heaptrack_print -l 1
"/home/centos/work/heaptrack-eval/heaptrack.a.out.20509.gz"
reading file "/home/centos/work/heaptrack-eval/heaptrack.a.out.20509.gz" -
please wait, this might take some time...
Debuggee command was: ./a.out
Failed to read time stamp: c
finished reading file, now analyzing data:
MOST CALLS TO ALLOCATION FUNCTIONS
1 calls to allocation functions with 1000.00B peak consumption from
main
in /home/centos/work/heaptrack-eval/a.out
1 calls with 1000.00B peak consumption from:
1 calls to allocation functions with 608B peak consumption from
_dl_allocate_tls
in /lib64/ld-linux-x86-64.so.2
1 calls with 608B peak consumption from:
__pthread_create_2_1
in /lib64/libpthread.so.0
main
in /home/centos/work/heaptrack-eval/a.out
PEAK MEMORY CONSUMERS
WARNING - the data below is not an accurate calcuation of the total peak
consumption and can easily be wrong.
For an accurate overview, disable backtrace merging.
1000.00B peak memory consumed over 1 calls from
main
in /home/centos/work/heaptrack-eval/a.out
1000.00B consumed over 1 calls from:
608B peak memory consumed over 1 calls from
_dl_allocate_tls
in /lib64/ld-linux-x86-64.so.2
608B consumed over 1 calls from:
__pthread_create_2_1
in /lib64/libpthread.so.0
main
in /home/centos/work/heaptrack-eval/a.out
MEMORY LEAKS
1000.00B leaked over 1 calls from
main
in /home/centos/work/heaptrack-eval/a.out
1000.00B leaked over 1 calls from:
608B leaked over 1 calls from
_dl_allocate_tls
in /lib64/ld-linux-x86-64.so.2
608B leaked over 1 calls from:
__pthread_create_2_1
in /lib64/libpthread.so.0
main
in /home/centos/work/heaptrack-eval/a.out
MOST TEMPORARY ALLOCATIONS
total runtime: 2.73s.
bytes allocated in total (ignoring deallocations): 1.61KB (590B/s)
calls to allocation functions: 2 (0/s)
temporary memory allocations: 0 (0/s)
peak heap memory consumption: 1.61KB
peak RSS (including heaptrack overhead): 4.35MB
total memory leaked: 1.61KB
# Same scenario with "kill -HUP `pidof a.out`"
~/work/heaptrack-eval $ heaptrack ./a.out
heaptrack output will be written to
"/home/centos/work/heaptrack-eval/heaptrack.a.out.21914.gz"
starting application, this might take some time...
Started, press Ctrl-C to abort
heaptrack stats:
allocations:2
leaked allocations: 2
temporary allocations: 0
/usr/local/bin/heaptrack: line 195: 21935 Hangup
LD_PRELOAD=$LIBHEAPTRACK_PRELOAD${LD_PRELOAD:+:$LD_PRELOAD}
DUMP_HEAPTRACK_OUTPUT="$pipe" "$client" "$@"
Heaptrack finished! Now run the following to investigate the data:
heaptrack_print "/home/centos/work/heaptrack-eval/heaptrack.a.out.21914.gz" |
less
--
You are receiving this mail because:
You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #4 from Maksim Golov --- I was not aware of timer thread, must have missed it in my reading of heaptrack code. Likely it has the signals enabled and gets to handle the signal instead of the signal thread. Not sure how this can be addressed, maybe disable signals for the timer thread completely? -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #5 from Maksim Golov --- What the code in the reproduce does is to ensure that all signals are handled by a single dedicated thread only, and all other threads have them disabled. This ensures that the signals are handled in well-defined manner. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #8 from Maksim Golov --- Confirm that it works for my case. One thing to note, the proposed patch introduces a dependency on pthreads, which is probably quite safe in practice, and I'd expect CMake can probe for pthreads being available. I wouldn't be able to say if there are potential heaptrack users affected by this, though. An alternative would be to somehow allow the application to expose a hook which heaptrack will call when starting the timer thread - not sure if this is worth the trouble. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378765] New: Invoke glibc cleanup when present (__libc_freeres)
https://bugs.kde.org/show_bug.cgi?id=378765 Bug ID: 378765 Summary: Invoke glibc cleanup when present (__libc_freeres) Product: Heaptrack Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@milianw.de Reporter: maxim.go...@gmail.com Target Milestone: --- Created attachment 105019 --> https://bugs.kde.org/attachment.cgi?id=105019&action=edit Reproducer for strftime leak Several functions like strftime allocate memory on the first use which is not cleaned up on shutdown by default. heaptrack reports such allocations as memory leaks. glibc provides a cleanup method which can be used to release this memory before exit, see, for example, valgrind documentation. Attached is a reproducer. $ g++ leak-strftime.cpp $ ./a.out $ heaptrack ./a.out heaptrack output will be written to "/home/centos/work/heaptrack-eval/heaptrack.a.out.16784.gz" starting application, this might take some time... heaptrack stats: allocations:4 leaked allocations: 3 temporary allocations: 0 Heaptrack finished! Now run the following to investigate the data: heaptrack_print "/home/centos/work/heaptrack-eval/heaptrack.a.out.16784.gz" | less $ heaptrack ./a.out noleak heaptrack output will be written to "/home/centos/work/heaptrack-eval/heaptrack.a.out.16809.gz" starting application, this might take some time... heaptrack stats: allocations:4 leaked allocations: 0 temporary allocations: 1 Heaptrack finished! Now run the following to investigate the data: heaptrack_print "/home/centos/work/heaptrack-eval/heaptrack.a.out.16809.gz" | less -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498916] New: system settings crached
https://bugs.kde.org/show_bug.cgi?id=498916
Bug ID: 498916
Summary: system settings crached
Classification: Applications
Product: systemsettings
Version: 6.2.5
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: maxpose...@gmail.com
Target Milestone: ---
Application: systemsettings (6.2.5)
(Compiled from sources)
ApplicationNotResponding [ANR]: false
Qt Version: 6.8.1
Frameworks Version: 6.10.0
Operating System: Linux 6.12.10-gentoo-dist x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 6.2.5 [CoredumpBackend]
-- Information about the crash:
I just used system settings to check display configuration
Switching between 120hz and 60hz
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during
file-backed mapping note processing
warning: Can't open file /memfd:xshmfence (deleted) during file-backed mapping
note processing
warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:xorg (deleted) during file-backed mapping note
processing
[New LWP 79911]
[New LWP 79913]
[New LWP 79912]
[New LWP 79947]
[New LWP 79917]
[New LWP 79919]
[New LWP 79930]
[New LWP 79920]
[New LWP 79936]
[New LWP 79937]
[New LWP 79918]
[New LWP 79938]
[New LWP 79921]
[New LWP 79939]
[New LWP 79948]
[New LWP 79940]
[New LWP 79923]
[New LWP 79942]
[New LWP 79955]
[New LWP 79960]
[New LWP 79946]
[New LWP 79941]
[New LWP 79922]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/systemsettings kcm_kscreen'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f10ade9c14c in ?? () from /usr/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f10ab42e480 (LWP 79911))]
python sentry-sdk not installed :(
Cannot QML trace cores :(
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:516: DeprecationWarning:
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in
a future version. Use timezone-aware objects to represent datetimes in UTC:
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
boot_time =
datetime.utcfromtimestamp(psutil.boot_time()).strftime('%Y-%m-%dT%H:%M:%S')
Unexpectedly stumbled over an objfile (/usr/lib64/libjpeg.so.62.4.0) without
build_id. Not creating payload.
[Current thread is 1 (Thread 0x7f10ab42e480 (LWP 79911))]
Thread 23 (Thread 0x7f10921fc6c0 (LWP 79922)):
#0 0x7f10ade96cae in ??? () at /usr/lib64/libc.so.6
#1 0x7f10ade995d9 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2 0x7f10a2156d2d in cnd_wait (cond=, mtx=)
at ../mesa-24.3.3/src/c11/impl/threads_posix.c:135
#3 0x7f10a2124e4b in util_queue_thread_func
(input=input@entry=0x563813458c50) at ../mesa-24.3.3/src/util/u_queue.c:275
#4 0x7f10a2156c5b in impl_thrd_routine (p=) at
../mesa-24.3.3/src/c11/impl/threads_posix.c:67
#5 0x7f10ade9a3f9 in ??? () at /usr/lib64/libc.so.6
#6 0x7f10adf19c9c in ??? () at /usr/lib64/libc.so.6
Thread 22 (Thread 0x7f105bfff6c0 (LWP 79941)):
#0 0x7f10ade96cae in ??? () at /usr/lib64/libc.so.6
#1 0x7f10ade99923 in pthread_cond_timedwait () at /usr/lib64/libc.so.6
#2 0x7f10ae55e103 in QWaitConditionPrivate::wait_relative (this=, deadline=...) at
/usr/src/debug/dev-qt/qtbase-6.8.1/qtbase-everywhere-src-6.8.1/src/corelib/thread/qwaitcondition_unix.cpp:95
#3 QWaitConditionPrivate::wait (this=0x563814682f80, deadline=...) at
/usr/src/debug/dev-qt/qtbase-6.8.1/qtbase-everywhere-src-6.8.1/src/corelib/thread/qwaitcondition_unix.cpp:103
#4 QWaitCondition::wait (this=this@entry=0x56381468b120,
mutex=mutex@entry=0x563814669088, deadline=...) at
/usr/src/debug/dev-qt/qtbase-6.8.1/qtbase-everywhere-src-6.8.1/src/corelib/thread/qwaitcondition_unix.cpp:183
#5 0x7f10ae63433e in QThreadPoolThread::run (this=0x56381468b110) at
/usr/src/debug/dev-qt/qtbase-6.8.1/qtbase-everywhere-src-6.8.1/src/corelib/thread/qthreadpool.cpp:118
#6 0x7f10ae619f85 in operator() (__closure=) at
/usr/src/debug/dev-qt/qtbase-6.8.1/qtbase-everywhere-src-6.8.1/src/corelib/thread/qthread_unix.cpp:354
#7 (anonymous
namespace)::terminate_on_exception >
(t=) at
/usr/src/debug/dev-qt/qtbase-6.8.1/qtbase-everywhere-src-6.8.1/src/corelib/thread/qthread_unix.cpp:290
#8 QThreadPrivate::start (arg=0x56381468b110) at
/usr/
[kio] [Bug 366108] New: MTP recursively allow request.
https://bugs.kde.org/show_bug.cgi?id=366108 Bug ID: 366108 Summary: MTP recursively allow request. Product: kio Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: mtp Assignee: philschm...@gmx.net Reporter: maksim.mur...@gmail.com After connect the phone I have endless 'reconnect' which started from 'deny / allow' request on the phone after seems like it goes reconnect again and ask this again and so on. :~$ mtpfs --version Listing raw device(s) No raw devices found. mf@mf-laptop:~$ mtpfs --version Listing raw device(s) Device 0 (VID=1004 and PID=633e) is a LG Electronics Inc. LG G Flex 2. Found 1 device(s): LG Electronics Inc.: LG G Flex 2 (1004:633e) @ bus 2, dev 22 Attempting to connect device ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device Android device detected, assigning default bug flags Error 1: Get Storage information failed. Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles. Error 2: Error 02fe: PTP: Protocol error, data expected Listing File Information on Device with name: MF_G4 LIBMTP_Get_Storage() failed:-1 kio-mtp is already the newest version (0.75+git20140304-2). Reproducible: Always Steps to Reproduce: 1. connect the phone 2. press allow on popup question 3. goes to 2 stage again -- You are receiving this mail because: You are watching all bug changes.
