[frameworks-kded] [Bug 372904] New: kded5 maxing one CPU core after search performed in Dolphin
https://bugs.kde.org/show_bug.cgi?id=372904 Bug ID: 372904 Summary: kded5 maxing one CPU core after search performed in Dolphin Product: frameworks-kded Version: 5.28.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: kdeb...@fratti.ch CC: kdelibs-b...@kde.org Target Milestone: --- the kded5 process appears to max out one CPU core after a search is performed in Dolphin (through hitting Ctrl+F in a folder). The CPU usage of the kded5 process continues to be that high until it is killed and restarted. The problem appears to always be reproducible, and did not occur in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442232] New: On Wayland, Dolphin always sends WL_DATA_DEVICE_MANAGER_DND_ACTION_COPY even when holding Shift
https://bugs.kde.org/show_bug.cgi?id=442232 Bug ID: 442232 Summary: On Wayland, Dolphin always sends WL_DATA_DEVICE_MANAGER_DND_ACTION_COPY even when holding Shift Product: dolphin Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kdeb...@fratti.ch CC: kfm-de...@kde.org Target Milestone: --- When dragging and dropping, holding shift and dropping a file should send WL_DATA_DEVICE_MANAGER_DND_ACTION_MOVE to the application. However, Dolphin always sends WL_DATA_DEVICE_MANAGER_DND_ACTION_COPY. This breaks Shift+drop to append files to playlist on mpv. STEPS TO REPRODUCE 1. mpv --no-config --idle --pause videohere.mp4 2. Shift+drag and drop a file from Dolphin onto mpv OBSERVED RESULT mpv receives a WL_DATA_DEVICE_MANAGER_DND_ACTION_COPY event from Dolphin, which means it replaces the currently playing file. EXPECTED RESULT mpv receives a WL_DATA_DEVICE_MANAGER_DND_ACTION_MOVE event from Dolphin, which means it'll append the file to the playlist SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.13.13 (available in About System) KDE Plasma Version: Plasma 5.22.5 KDE Frameworks Version: Frameworks 5.85 Qt Version: 5.15.2 Only occurs on Wayland, it's a Wayland specific problem. Bug report on mpv's side: https://github.com/mpv-player/mpv/issues/9201 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 425938] Drag & Drop file from Ark to mpv
https://bugs.kde.org/show_bug.cgi?id=425938 --- Comment #4 from Nicolas Frattaroli --- > I can think of one: extraction takes a long time. One possible solution is to have Ark expose a temporary fuse mount of the archive. It mounts the archive, passes a filename to the application of that path (i.e. no Ark-specific code is needed) and then keeps around a fuse daemon process while there are still some file handles to it open, plus some grace period for reopening and such. That way, ark only really has to extract as the application reads. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427771] New: Flat/Adaptive pointer acceleration setting does nothing on wayland
https://bugs.kde.org/show_bug.cgi?id=427771 Bug ID: 427771 Summary: Flat/Adaptive pointer acceleration setting does nothing on wayland Product: systemsettings Version: 5.20.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- Launching a Plasma Wayland session and going into the touchpad settings, one can change the flat/adaptive radio button option for pointer acceleration with no effect. In fact, hitting apply shows the options as immediately being reverted back to its previous state. The same appears to apply for natural scrolling, which seems to be forced on for some applications on Wayland, even if the settings show it as being off. STEPS TO REPRODUCE 1. Open system settings -> touchpad 2. Click on "Flat" instead of "Adaptive" 3. Hit "Apply" OBSERVED RESULT Pointer acceleration remains, GUI immediately reverts to the option "Adaptive" being checked EXPECTED RESULT Setting is actually changed SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Works fine on X11, also using libinput. Occasionally, the "Adaptive" or "Flat" choice doesn't show up at all; in those cases, clicking on some other settings menu then going back makes it appear. Weird. This also happens on X11 sometimes, though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427771] Flat/Adaptive pointer acceleration setting does nothing on wayland
https://bugs.kde.org/show_bug.cgi?id=427771 --- Comment #2 from Nicolas Frattaroli --- Has always been broken, not a regression from 5.19. In fact, the only reason why I even tried to use Wayland was to see if it was still broken so that I could report it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427771] Flat/Adaptive pointer acceleration setting does nothing on wayland
https://bugs.kde.org/show_bug.cgi?id=427771 --- Comment #3 from Nicolas Frattaroli --- I've done some more sleuthing. Initially I thought this was related to some old unmaintained third party kcm I've had installed - "kcm-pointing-devices", but no, after removing it and restarting my computer, and logging back into Wayland, the problem still persisted. I've tried seeing if `kcmshell5 kcm_touchpad` produces any interesting output when toggling options, but to no avail. Is there some console utility to read out and alter the current touchpad settings on KWin Wayland? That way I might narrow it down as to whether it's a UI issue, otherwise I'll just try and get a KDE dev environment set up when I have the time and litter the KCM with debug printfs until I find what's causing this. Hilariously, the Flat/Adaptive toggle works for "Mouse", namely my Thinkpad's included red nipple thing. So it's either specific to the Synaptics touchpad, or specific to the Touchpad UI. I'm also not sure if natural scrolling is just an artefact of SystemSettings being weird, it works as expected in all other Qt applications. I'll disregard it for now and assume that's a completely separate issue. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365714] Akregator tray icon is very low resolution on high DPI displays
https://bugs.kde.org/show_bug.cgi?id=365714 Nicolas Frattaroli changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Nicolas Frattaroli --- Hi Justin, this has indeed resolved itself over the past 4 years. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 425938] Drag & Drop file from Ark to mpv
https://bugs.kde.org/show_bug.cgi?id=425938 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #2 from Nicolas Frattaroli --- That dbus API is bad. It requires the application to implement Ark-specific handling for drag-and-drop events by making the application tell Ark to extract the file instead of having Ark just extract the file to a temporary location and pass that temporary location to the application through the normal drag and drop mechanism with no involvement of a secondary dbus API to initiate this process. Is there literally any reason as to why it was misengineered this way? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437674] New: Spectacle crashes on exit inside kImageAnnotator
https://bugs.kde.org/show_bug.cgi?id=437674 Bug ID: 437674 Summary: Spectacle crashes on exit inside kImageAnnotator Product: Spectacle Version: 21.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: kdeb...@fratti.ch CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.6-arch1-1 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was closing Spectacle with the "x" button. I don't have debug symbols for Qt, but I did get some debug symbols for the kImageAnnotator lib, which shows it crashing in a destructor. Presumably it's trying to delete something that doesn't exist. The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7f8836306e88 in kImageAnnotator::FontPicker::~FontPicker (this=0x56528a2f3650, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/widgets/settingsPicker/FontPicker.cpp:40 #5 0x7f88363070a9 in kImageAnnotator::FontPicker::~FontPicker (this=0x56528a2f3650, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/widgets/settingsPicker/FontPicker.cpp:46 #6 0x7f88362c7265 in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings (this=0x56528a130320, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/annotator/settings/AnnotationItemSettings.cpp:49 #7 0x7f88362c73a9 in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings (this=0x56528a130320, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/annotator/settings/AnnotationItemSettings.cpp:52 #8 0x7f88362c2e5e in kImageAnnotator::AnnotationWidget::~AnnotationWidget (this=0x56528a1ea7c0, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/annotator/AnnotationWidget.cpp:40 #9 0x7f88362c2ef9 in kImageAnnotator::AnnotationWidget::~AnnotationWidget (this=0x56528a1ea7c0, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/annotator/AnnotationWidget.cpp:44 #10 0x7f88362c282b in kImageAnnotator::CoreView::~CoreView (this=0x56528a1c4af0, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/CoreView.cpp:51 #11 0x7f88362c1a77 in kImageAnnotator::KImageAnnotatorPrivate::~KImageAnnotatorPrivate (this=0x56528a1c4a60, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/KImageAnnotator.cpp:53 #12 QScopedPointerDeleter::cleanup (pointer=0x56528a1c4a60) at /usr/include/qt/QtCore/qscopedpointer.h:60 #13 QScopedPointerDeleter::cleanup (pointer=0x56528a1c4a60) at /usr/include/qt/QtCore/qscopedpointer.h:52 #14 QScopedPointer >::~QScopedPointer (this=0x56528a1eb520, __in_chrg=) at /usr/include/qt/QtCore/qscopedpointer.h:107 #15 kImageAnnotator::KImageAnnotator::~KImageAnnotator (this=0x56528a1eb4f0, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/KImageAnnotator.cpp:71 #16 0x7f88362c1aaa in kImageAnnotator::KImageAnnotator::~KImageAnnotator (this=0x56528a1eb4f0, __in_chrg=) at /usr/src/debug/kImageAnnotator-0.5.0/src/gui/KImageAnnotator.cpp:71 #17 0x7f88347ab7de in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #18 0x7f88352955ce in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #19 0x56528825a26e in ?? () #20 0x7f88347ab7de in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #21 0x7f88352955ce in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #22 0x56528825b46d in ?? () #23 0x56528825650c in ?? () #24 0x7f883410db25 in __libc_start_main () from /usr/lib/libc.so.6 #25 0x565288256e0e in ?? () [Inferior 1 (process 19938) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427771] Flat/Adaptive pointer acceleration setting does nothing on wayland
https://bugs.kde.org/show_bug.cgi?id=427771 --- Comment #4 from Nicolas Frattaroli --- Created attachment 139161 --> https://bugs.kde.org/attachment.cgi?id=139161&action=edit Video of the bug in action Here's a screen recording of the bug in action. Note that the option only appears when I looked at the Mouse tab before, which has it by default. Pointer acceleration at 0.00 does not actually disable pointer acceleration. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407836] New: Okular crashes with a segfault when opening epub file
https://bugs.kde.org/show_bug.cgi?id=407836 Bug ID: 407836 Summary: Okular crashes with a segfault when opening epub file Product: okular Version: 1.7.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: EPub backend Assignee: okular-de...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- Created attachment 120254 --> https://bugs.kde.org/attachment.cgi?id=120254&action=edit gdb bt full Okular crashes with a segmentation fault when opening an epub file STEPS TO REPRODUCE 1. Open https://0x0.st/zm07.epub 100% reproducible. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Please see the attached gdb backtrace Okular built with "debugfull" -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 378904] Ark should use charset auto-detection for filenames
https://bugs.kde.org/show_bug.cgi?id=378904 --- Comment #11 from Nicolas Frattaroli --- >and there only to files created by legacy software (does anyone know which >programs produce these zip files actually?) Windows creates ZIP files with filenames encoded in the system locale's charset. So any ZIP file created on Windows with "send to->zip compressed folder" by someone using a locale that doesn't map to utf8 is affected. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 416303] New: ksgrd_network_helper maxes out an entire CPU thread while qBittorrent is running
https://bugs.kde.org/show_bug.cgi?id=416303 Bug ID: 416303 Summary: ksgrd_network_helper maxes out an entire CPU thread while qBittorrent is running Product: ksysguard Version: 5.17.5 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- Created attachment 125154 --> https://bugs.kde.org/attachment.cgi?id=125154&action=edit flamegraph of the ksgrd_network_helper process, captured with a 99 Hz interval for 60 seconds. ksgrd_network_helper sits at full usage of one logical CPU core if qBittorrent is running in the background. If one closes qBittorrent, the CPU usage of ksgrd_network_helper drops. STEPS TO REPRODUCE 1. Launch ksysguard 2. Launch qBittorrent with some torrents 3. Look at the CPU usage of ksgrd_network_helper OBSERVED RESULT Ridiculously high CPU usage because it presumably scales badly with the number of connections an application makes. EXPECTED RESULT Developer realises that more network applications than just web browsers exists and uses appropriately scaling algorithms. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.4.8 / Plasma 5.17.5 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION I'm tunnelling through wireguard while doing this, but I'm not sure if it matters at all. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410859] plasmashell hangs for multiple seconds while nmcli is also slow to respond
https://bugs.kde.org/show_bug.cgi?id=410859 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #3 from Nicolas Frattaroli --- I can confirm this bug, the way I can reproduce it specifically is to use stubby as a local DNS resolver. 1. Install stubby and configure it 2. Set DNS resolver to 127.0.0.1 3. Switch from one wifi to the other 4. The entirety of plasmashell will now freeze as NetworkManager waits for a dns response to time out Note that restarting stubby unfreezes plasmashell and NetworkManager prematurely (i.e. before the timeout happens) The general problem here appears to be threefold, 1. plasmashell lets itself get blocked by applets, 2. plasma-nm lets itself get blocked by NetworkManager, 3. NetworkManager is not good. Ideally plasmashell would not freeze if a widget freezes, and even more ideally plasma-nm won't freeze if NetworkManager decides to pointlessly block. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388785] New: Link colour doesn't change in selected or hovered elements with breeze-dark
https://bugs.kde.org/show_bug.cgi?id=388785 Bug ID: 388785 Summary: Link colour doesn't change in selected or hovered elements with breeze-dark Product: Breeze Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: kdeb...@fratti.ch Target Milestone: --- Created attachment 109782 --> https://bugs.kde.org/attachment.cgi?id=109782&action=edit Unreadable retweet text in corebird because of static colours In the Breeze-Dark GTK theme, the link colour should change from blue to yellow when text with a link in it is selected or the element is hovered over. However, it doesn't do that, and remains blue. This is an issue in Corebird, for example, which gives an entire tweet the hovered colour when the mouse hovers over it, hiding the link colour. baedert of corebird assured me that they don't hardcode link colours, so Breeze-Dark should be the one at fault here. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 390326] New: elisa should extract cover art from file metadata
https://bugs.kde.org/show_bug.cgi?id=390326 Bug ID: 390326 Summary: elisa should extract cover art from file metadata Product: elisa Version: 0.0.81 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: kdeb...@fratti.ch Target Milestone: --- Currently, elisa appears to be reading cover.jpg files in the directory of an album, but not the covers from the following sources: - inside the metadata - in files matching regex "(artist \- )?title\.(jp(e?g|e)|png)" where artist and title are the respective values from the track metadata The latter is usually how e.g. bandcamp distributes their album cover files, along with album covers in each track's metadata. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 390326] elisa should extract cover art from file metadata
https://bugs.kde.org/show_bug.cgi?id=390326 --- Comment #1 from Nicolas Frattaroli --- On second look through my music collection, some bandcamp albums actually seem to use "(artist \- )?title - cover\.(jp(e?g|e)|png)", i.e. a "- cover" appended after the title. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 390329] New: elisa occasionally crashes when opening the settings dialogue while a track is playing
https://bugs.kde.org/show_bug.cgi?id=390329 Bug ID: 390329 Summary: elisa occasionally crashes when opening the settings dialogue while a track is playing Product: elisa Version: 0.0.81 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: kdeb...@fratti.ch Target Milestone: --- 1. Play back an album 2. Open "Configure Elisa..." from the hamburger menu 3. elisa will occasionally crash elisa-git commit 201538a6897850c043deba7f667fd45d802159a8 KDE Frameworks 5.42.0 Qt 5.10.0 (built against 5.10.0) Backtrace of questionable usefulness: Thread 1 "elisa" received signal SIGSEGV, Segmentation fault. 0x75208e77 in QV4::QObjectWrapper::markObjects(QV4::Heap::Base*, QV4::MarkStack*) () from /usr/lib/libQt5Qml.so.5 (gdb) bt #0 0x75208e77 in QV4::QObjectWrapper::markObjects(QV4::Heap::Base*, QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5 #1 0x7507cbd8 in () at /usr/lib/libQt5Qml.so.5 #2 0x751713a9 in QV4::PersistentValueStorage::mark(QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5 #3 0x7507d4b0 in QV4::MemoryManager::collectRoots(QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5 #4 0x7507d6c4 in QV4::MemoryManager::mark() () at /usr/lib/libQt5Qml.so.5 #5 0x7507e621 in () at /usr/lib/libQt5Qml.so.5 #6 0x75080516 in QV4::MemoryManager::allocData(unsigned long) () at /usr/lib/libQt5Qml.so.5 #7 0x751a353c in () at /usr/lib/libQt5Qml.so.5 #8 0x751a649e in QV4::Object::setInternalClass(QV4::InternalClass*) () at /usr/lib/libQt5Qml.so.5 #9 0x751775c6 in () at /usr/lib/libQt5Qml.so.5 #10 0x751a6bdd in QV4::Object::insertMember(QV4::String*, QV4::Property const*, QV4::PropertyAttributes) () at /usr/lib/libQt5Qml.so.5 #11 0x751ab235 in QV4::Object::__defineOwnProperty__(QV4::ExecutionEngine*, QV4::String*, QV4::Property const*, QV4::PropertyAttributes) () at /usr/lib/libQt5Qml.so.5 #12 0x7516e4d3 in QV4::ExecutionContext::createMutableBinding(QV4::String*, bool) () at /usr/lib/libQt5Qml.so.5 #13 0x75220bf3 in QV4::Runtime::method_declareVar(QV4::ExecutionEngine*, bool, int) () at /usr/lib/libQt5Qml.so.5 #14 0x7fffa54b73c9 in () #15 0x0002 in () #16 0x7fbf67bc4320 in () #17 0x5a3e4410 in () #18 0x7516e11a in QV4::ExecutionContext::newCallContext(QV4::Function*, QV4::CallData*) () at /usr/lib/libQt5Qml.so.5 #19 0x75170a0d in QV4::ExecutionContext::call(QV4::Scope&, QV4::CallData*, QV4::Function*, QV4::FunctionObject const*) () at /usr/lib/libQt5Qml.so.5 #20 0x751bea9c in QV4::Script::run() () at /usr/lib/libQt5Qml.so.5 #21 0x7526ac31 in () at /usr/lib/libQt5Qml.so.5 #22 0x752dae95 in () at /usr/lib/libQt5Qml.so.5 #23 0x752d9f6b in () at /usr/lib/libQt5Qml.so.5 #24 0x752dacd5 in () at /usr/lib/libQt5Qml.so.5 #25 0x752d9f6b in () at /usr/lib/libQt5Qml.so.5 #26 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #27 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #28 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #29 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #30 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #31 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #32 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #33 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #34 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #35 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #36 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #37 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #38 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #39 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #40 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #41 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #42 0x752dacd5 in () at /usr/lib/libQt5Qml.so.5 #43 0x752d9f6b in () at /usr/lib/libQt5Qml.so.5 #44 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #45 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #46 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #47 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #48 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #49 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #50 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #51 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #52 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #53 0x752d8919 in () at /usr/lib/libQt5Qml.so.5 #54 0x752d9200 in () at /usr/lib/libQt5Qml.so.5 #55 0x752da0e8 in () at /usr/lib/libQt5Qml.so.5 #56 0x752d863f in () at /usr/lib/libQt5Qml.so.5 #57 0x752d8919 in () at /usr/lib/libQt5Qml.
[plasmashell] [Bug 389132] New: plasmashell's notification history seems to have no upper limit
https://bugs.kde.org/show_bug.cgi?id=389132 Bug ID: 389132 Summary: plasmashell's notification history seems to have no upper limit Product: plasmashell Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kdeb...@fratti.ch CC: plasma-b...@kde.org Target Milestone: 1.0 It appears that plasmashell's notification history does not have an upper limit, which means that buggy applications may accidentally OOM the system through plasmashell by creating a lot of notifications. In my case, qBittorrent spams a notification for every IOError it encounters (happens quite often when you accidentally disconnect the external drive), which quickly leads to plasmashell's memory usage ballooning in size to several gigabytes. plasmashell could enforce a per-PID maximum number of notifications that it keeps in its history to prevent this from happening, discarding old notifications as new ones come in if the limit is reached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389132] plasmashell's notification history seems to have no upper limit
https://bugs.kde.org/show_bug.cgi?id=389132 --- Comment #3 from Nicolas Frattaroli --- >In addition, please file a bug report on QBittorrent; spamming the shell with >notifications on every error isn't good practice. I've already done this a while ago[1], turns out plasmashell isn't the only environment that has issues with notification spam (Windows doesn't seem to like it either). Thanks for the quick response. [1] https://github.com/qbittorrent/qBittorrent/issues/7586 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389132] plasmashell's notification history seems to have no upper limit
https://bugs.kde.org/show_bug.cgi?id=389132 --- Comment #8 from Nicolas Frattaroli --- I've applied the patch to plasmashell 5.11.5, and tested it. The good news is that it drastically reduced the memory usage from the notification spam. Even after minutes of waiting, plasmashell only climbed up to about 400 MiB used memory. I could even open the notifications area this time, which previously would immediately OOM the system. The bad news is that when dismissing the notifications (which I previously couldn't do, because the system was very busy), the memory usage actually increases by about 300K per dismissed notification. It doesn't seem to decrease again after waiting a while either. (The lack of a "dismiss all" button for the notification applet also means that a user has to do a solid 10 minutes of clicking to get their notifications back in order) Seems good enough for now though, the memory leak is much much smaller now. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 403797] New: Akregator should show the error message of a failed feed fetch somewhere
https://bugs.kde.org/show_bug.cgi?id=403797 Bug ID: 403797 Summary: Akregator should show the error message of a failed feed fetch somewhere Product: akregator Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- SUMMARY If Akregator cannot fetch the feeds for some reason, such as with a misconfigured system proxy, the user will not know what precisely happened; all they'll see is that Akregator failed to fetch feeds. Having e.g. the same string that "kioclient5 cat " shows somewhere in the UI could make it easier for users to remedy their problems. STEPS TO REPRODUCE 1. Use Firefox, which doesn't use the system proxy, for daily browsing 2. Set the system proxy to a SOCKS5 localhost ssh tunnel because you wanted to see some region blocked content in Chromium 3. Close the tunnel 4. Wtf why akregator no workie when firefox work?? >:( >:( >:( OBSERVED RESULT Akregator shows a little "x" icon for each failed feed, but no info beyond that. EXPECTED RESULT Akregator yells at me for not being able to connect to the proxy. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.20.3-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION What happens in such a misconfiguration with kioclient5 cat is e.g.: $ kioclient5 cat http://www.kde.org/dotkdeorg.rdf "Could not connect to host www.kde.org: Connection to proxy refused." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379465] kwin_x11 crashes after mpv is set to fullscreen
https://bugs.kde.org/show_bug.cgi?id=379465 --- Comment #2 from Nicolas Frattaroli --- Then DrKonqi should probably not give this backtrace a 3 out of 3 star rating. I'm personally not going to try and reproduce this again with debug symbols. Building Qt with debug symbols is going to take me way too long, and the crash happens so rarely that it's hard to reproduce in the first place. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379465] kwin_x11 crashes after mpv is set to fullscreen
https://bugs.kde.org/show_bug.cgi?id=379465 --- Comment #4 from Nicolas Frattaroli --- I've discovered that the qutebrowser people host an Arch Linux repository with prebuilt qt5 debug packages. I've installed qt5-base-debug from there and built kwin with build type RelWithDebInfo. I hope the crash happens again so that I can supply you with a useful backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383296] New: Powerdevil immediately discards xdg-screensaver inhibitions
https://bugs.kde.org/show_bug.cgi?id=383296 Bug ID: 383296 Summary: Powerdevil immediately discards xdg-screensaver inhibitions Product: Powerdevil Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- Steps to reproduce: 1. watch the log with `journalctl -x -f` 2. run `xdg-screensaver suspend 0xsomevalididhere` powerdevil will do the following: Aug 09 00:10:51 archbook org_kde_powerdevil[797]: powerdevil: Scheduling inhibition from ":1.12" "0x5c1" with cookie 24 and reason "xdg-screensaver" Aug 09 00:10:51 archbook org_kde_powerdevil[797]: powerdevil: Releasing inhibition with cookie 24 Aug 09 00:10:51 archbook org_kde_powerdevil[797]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it mpv's current git HEAD relies on xdg-screensaver to suspend the lock screen, so this is somewhat irritating. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 364978] ksysguard shows negative relative start time due to getting the timezone wrong
https://bugs.kde.org/show_bug.cgi?id=364978 --- Comment #4 from Nicolas Frattaroli --- I also suspend/resume often, so it may indeed be related to suspending and resuming as opposed to anything to do with timezones. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383296] Powerdevil immediately discards xdg-screensaver inhibitions
https://bugs.kde.org/show_bug.cgi?id=383296 --- Comment #2 from Nicolas Frattaroli --- This is not a duplicate of that bug, for me, the inhibition does not work at all. The screen lock or dimming proceeds regardless. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383296] Powerdevil immediately discards xdg-screensaver inhibitions
https://bugs.kde.org/show_bug.cgi?id=383296 --- Comment #3 from Nicolas Frattaroli --- Nevermind, just read all the comments on that bug report and it looks like this was reported upstream and indeed the same issue. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383380] New: Duplicate overwrite warning when exporting feeds
https://bugs.kde.org/show_bug.cgi?id=383380 Bug ID: 383380 Summary: Duplicate overwrite warning when exporting feeds Product: akregator Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- When choosing File->Export Feeds and selecting a file which already exists, not only will the KDE file dialog warn of a file being overwritten, but Akregator itself will give you a second redundant warning. One warning (the KDE file dialog one) should be enough. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383381] New: Getting the feed URL from a youtube channel no longer works
https://bugs.kde.org/show_bug.cgi?id=383381 Bug ID: 383381 Summary: Getting the feed URL from a youtube channel no longer works Product: akregator Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- When given a regular web page URL, akregator will fetch the RSS/atom feed url from it based on its headers. However, on YouTube, this no longer works, because YouTube believes that Akregator is a mobile client and redirects it to m.youtube.com, which in turn confuses Akregator and makes it unable to add the feed url. Searching the feed url in the webpage source and adding that manually works as a workaround. Example URL: https://www.youtube.com/user/bigclivedotcom/videos Akregator will try to add the feed https://m.youtube.com/user/bigclivedotcom/videos Akregator should add the feed https://www.youtube.com/feeds/videos.xml?channel_id=UCtM5z2gkrGRuWd0JQMx76qA -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #1 from Nicolas Frattaroli --- I've had the issue of Akregator corrupting the feed list too multiple times after rebooting following several days of uptime. Occasionally, it can't even restore the feed list at all, and further examination reveals that it it halfway overwrote something in the middle of its feedlist file. Akregator 5.5.3 here. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in
https://bugs.kde.org/show_bug.cgi?id=381929 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 383575] org.freedesktop.ScreenSaver.Inhibit is unusable from dbus-send
https://bugs.kde.org/show_bug.cgi?id=383575 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 386467] New: Expose auto-lip-sync value through kscreen-doctor
https://bugs.kde.org/show_bug.cgi?id=386467 Bug ID: 386467 Summary: Expose auto-lip-sync value through kscreen-doctor Product: KScreen Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: common Assignee: se...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- HDMI 1.3 has a standard optional way for display devices such as TVs to signal back the input latency through EDID called "auto-lip-sync". This is intended for A/V receivers that pass through the video to the TV but play back the audio to adjust the audio playback delay to match the delay of the TV, as TVs tend to have several frames of input latency. Apparently HDMI 2.0 introduces an additional dynamic way to signal latency which does not use EDID. By exposing this in kscreen, applications could determine the approximate input latency of the screen they're currently running on, and adjust their audio delay accordingly if the audio isn't already being adjusted by the playback setup. Other uses could include games asking the user to change their TV setting if the reported latency is very high, or accurate syncing of external ambient lighting to video playback. This has very little real-world usability right this moment, but could come in handy for multimedia people to tinker with. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Nicolas Frattaroli changed: What|Removed |Added CC|kdeb...@fratti.ch | -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 374214] New: "Disable touchpad when typing" option does nothing with xf86-input-libinput
https://bugs.kde.org/show_bug.cgi?id=374214 Bug ID: 374214 Summary: "Disable touchpad when typing" option does nothing with xf86-input-libinput Product: Touchpad-KCM Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: rajeeshknamb...@gmail.com Reporter: kdeb...@fratti.ch Target Milestone: --- With xf86-input-libinput, turning off the "Disable touchpad when typing" option in the "Enable/Disable Touchpad" tab seemingly has no effect, as demonstrated by xinput list-props not changing. It appears that libinput integration in general is quite poor, as quite a few options are greyed out. Furthermore, the version of systemsettings which I'm using (5.8.4) is not even listed as an option in the bugtracker. Is this software unmaintained? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384602] New: Quick Tile shortcuts no longer works after update
https://bugs.kde.org/show_bug.cgi?id=384602 Bug ID: 384602 Summary: Quick Tile shortcuts no longer works after update Product: frameworks-kglobalaccel Version: 5.38.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: kdeb...@fratti.ch CC: kdelibs-b...@kde.org Target Milestone: --- To reproduce: 1. Bind the kwin shortcut Quick Tile Left to Shift+Meta+Left 2. Bind the kwin shortcut Quick Tile Right to Shift+Meta+Right 3. Try them This used to work in the previous version. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384602] Quick Tile shortcuts no longer works after update
https://bugs.kde.org/show_bug.cgi?id=384602 --- Comment #1 from Nicolas Frattaroli --- Looks like this is an issue with the Meta key, I can still bind it to e.g. F7 and it works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377706] New: Plasma freezes, then crashes, after interacting with the taskbar
https://bugs.kde.org/show_bug.cgi?id=377706 Bug ID: 377706 Summary: Plasma freezes, then crashes, after interacting with the taskbar Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kdeb...@fratti.ch CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: Plasma occasionally freezes and a few seconds later crashes after interacting with the task bar in some way. I believe I misclicked a task entry, and switched desktops instead, after which the crash occured. - What I was doing when the application crashed: I tried to switch from the browser back to Quassel by clicking on it in the task bar, but may have missed the right area and clicked the desktop switcher symbol next to it, though I'm not sure about that. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7465cdc800 (LWP 765))] Thread 17 (Thread 0x7f7369457700 (LWP 29412)): #0 0x7f745f3a337d in read () at /usr/lib/libc.so.6 #1 0x7f74538fdf51 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7f7453f8e30e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f7453f8ed80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f7453f8ee40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f7453f9ce29 in () at /usr/lib/libpulse.so.0 #6 0x7f745392cfe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7f745e9532e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f745f3b154f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f736a870700 (LWP 15019)): #0 0x7f745a1d2e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f745a18cffe in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f745a18d744 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f745a18d8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f745fcce06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f745fc7789a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f745fa99a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7462bd1025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f745fa9e6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f745e9532e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f745f3b154f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f7388ac0700 (LWP 1155)): #0 0x7f745e959756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f745fa9f58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f73a57721d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f73a57769d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f73a5771263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f73a5776a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f73a5771263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f73a5774249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f745fa9e6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f745e9532e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f745f3b154f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f73892c1700 (LWP 1154)): #0 0x7f745e959756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f745fa9f58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f73a57721d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f73a57769d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f73a5771263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f73a5776a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f73a5771263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f73a5776a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f73a5771263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Th
[ark] [Bug 378904] New: Ark should use charset auto-detection for filenames
https://bugs.kde.org/show_bug.cgi?id=378904 Bug ID: 378904 Summary: Ark should use charset auto-detection for filenames Product: ark Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: kdeb...@fratti.ch CC: rthoms...@gmail.com Target Milestone: --- ZIP archives have no standardised encoding for filenames and do not supply the charset information in the archive itself. This results in a problem that occurs when opening a ZIP created by, say, a Japanese Windows user, in Ark, as the filenames will come out as a garbled mess since Ark will expect a different encoding than the one that was used. This can be worked around by using a library such as uchardet, which can guess the used encoding from the binary filename string. Allowing users to manually specify which encoding should be tried would also be a helpful addition. A file demonstrating this issue can be found here: http://maltinerecords.cs8.biz/release/164/MARU164.zip -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379465] New: kwin_x11 crashes after mpv is set to fullscreen
https://bugs.kde.org/show_bug.cgi?id=379465 Bug ID: 379465 Summary: kwin_x11 crashes after mpv is set to fullscreen Product: kwin Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- Application: kwin_x11 (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.13-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I set mpv to fullscreen by hitting F in mpv. Upon trying to exit fullscreen by hitting F again, I noticed that it's not working, and discovered that the issue is that kwin crashed. - Unusual behavior I noticed: When restarting kwin_x11 from the terminal, I noticed that the terminal it was restarted in did not get any window decorations. Other windows however are fine. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc83d2c9840 (LWP 25014))] Thread 5 (Thread 0x7fc801a4f700 (LWP 25023)): #0 0x7fc835f63756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc8392da234 in () at /usr/lib/libQt5Script.so.5 #2 0x7fc8392da279 in () at /usr/lib/libQt5Script.so.5 #3 0x7fc835f5d2e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fc83cd2154f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fc80d0df700 (LWP 25021)): #0 0x7fc83cd1776b in ppoll () at /usr/lib/libc.so.6 #1 0x7fc83a39b329 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fc83a39c99a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fc83a3498ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc83a16ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fc83a1706d8 in () at /usr/lib/libQt5Core.so.5 #6 0x7fc835f5d2e7 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fc83cd2154f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fc8218b0700 (LWP 25017)): #0 0x7fc83cd1776b in ppoll () at /usr/lib/libc.so.6 #1 0x7fc83a39b329 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fc83a39c99a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fc83a3498ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc83a16ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fc833e2e125 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fc83a1706d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7fc835f5d2e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fc83cd2154f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fc823a00700 (LWP 25016)): #0 0x7fc83cd1767d in poll () at /usr/lib/libc.so.6 #1 0x7fc83be308e0 in () at /usr/lib/libxcb.so.1 #2 0x7fc83be32679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fc824adc239 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fc83a1706d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc835f5d2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc83cd2154f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fc83d2c9840 (LWP 25014)): [KCrash Handler] #6 0x7fc83cc68a10 in raise () at /usr/lib/libc.so.6 #7 0x7fc83cc6a13a in abort () at /usr/lib/libc.so.6 #8 0x7fc83a156e21 in () at /usr/lib/libQt5Core.so.5 #9 0x7fc83a16ad04 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #10 0x7fc83a16adf9 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #11 0x7fc83a375441 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #12 0x7fc83a37ed9f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #13 0x7fc820e8cc69 in KWin::X11StandalonePlatform::~X11StandalonePlatform() () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #14 0x7fc83a375441 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #15 0x7fc83a37ed9f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #16 0x7fc83a34cf86 in QCoreApplication::~QCoreApplication() () at /usr/lib/libQt5Core.so.5 #17 0x7fc83b02ddc1 in QApplication::~QApplication() () at /usr/lib/libQt5Widgets.so.5 #18 0x7fc83cfe0834 in () at /usr/lib/libkdeinit5_kwin_x11.so #19 0x7fc83cfe23e0 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so #20 0x7fc83cc55511 in __libc_start_main () at /usr/lib/libc.so.6 #21 0x0040069a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 383575] org.freedesktop.ScreenSaver.Inhibit is unusable from dbus-send
https://bugs.kde.org/show_bug.cgi?id=383575 --- Comment #5 from Nicolas Frattaroli --- Guess mpv won't work right on KDE then, pat yourselves on the back for your grand achievement. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #8 from Nicolas Frattaroli --- Arch Linux on Plasma 5.8 here, on a ~168 DPI monitor. Regardless of the clock font, the clock is tiny. However, if the panel height is changed to a certain size, the clock's size suddenly jumps up. Here's a video demo: https://fratti.ch/tmp/plasma58_clock.mp4 (1.6M H.264 yuv444p10) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 --- Comment #4 from Nicolas Frattaroli --- This is with the side-panel preview on. The folder is full of mainly PNG images. The images are sorted by filename. I've just tried again with kdialog and compared it to a minimal file widget application I wrote based on the kio tests, and while kdialog now seems to no longer hang (although this isn't git HEAD), the test application still does. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 --- Comment #5 from Nicolas Frattaroli --- Correction: kdialog now seems to hang again, so seemingly this isn't consistently reproducible. It still only hangs if the folder has a lot of files in it, though. After a few tries, I've also gotten it to hang on my /usr/bin/ (5490 items), so it seems the filetype does not matter. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 --- Comment #6 from Nicolas Frattaroli --- Created attachment 101545 --> https://bugs.kde.org/attachment.cgi?id=101545&action=edit gdb backtrace of interrupted process while it hangs Here's the gdb backtrace of a hanging kdialog process (built as debug), however kde frameworks and Qt aren't built with debug symbols because Arch Linux doesn't provide pre-compiled debug packages, I'll try to build everything with debug symbols someday, but since this will probably take a long time I haven't done so yet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 --- Comment #7 from Nicolas Frattaroli --- Created attachment 101546 --> https://bugs.kde.org/attachment.cgi?id=101546&action=edit A different backtrace from another hanging kdialog process Sorry for the many successive comments, but here's another backtrace, this time hanging in libharfbuzz. It looks like this might be an issue with my system's fonts, which would explain why you might not be able to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 --- Comment #10 from Nicolas Frattaroli --- Actually, I already have previews turned off in the folders in which this happens. The fact that it happens inconsistently would also indicate that the problem is something else. I'll try to mess around with gdb some more when I get the time to. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 364978] New: ksysguard shows negative relative start time due to getting the timezone wrong
https://bugs.kde.org/show_bug.cgi?id=364978 Bug ID: 364978 Summary: ksysguard shows negative relative start time due to getting the timezone wrong Product: ksysguard Version: 5.6.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: kdeb...@fratti.ch On recently started processes, ksysguard claims they have been launched -1 day and some hours ago. Hovering over the entry in the relative start time column reveals that it believes it has been started one hour in the future (possibly due to timezone or DST), and then makes a bogus calculation. Reproducible: Always # hwclock 2016-07-01 16:32:37.140183+1:00 # hwclock -c hw-time system-time freq-offset-ppm tick 1467383595 1467383595.038249 1467383605 1467383605.03872748 0 ^C $ locale LANG=en_GB.UTF-8 LC_CTYPE="en_GB.UTF-8" LC_NUMERIC="en_GB.UTF-8" LC_TIME="en_GB.UTF-8" LC_COLLATE="en_GB.UTF-8" LC_MONETARY="en_GB.UTF-8" LC_MESSAGES="en_GB.UTF-8" LC_PAPER="en_GB.UTF-8" LC_NAME="en_GB.UTF-8" LC_ADDRESS="en_GB.UTF-8" LC_TELEPHONE="en_GB.UTF-8" LC_MEASUREMENT="en_GB.UTF-8" LC_IDENTIFICATION="en_GB.UTF-8" LC_ALL= $ timedatectl Local time: Fri 2016-07-01 16:34:23 CEST Universal time: Fri 2016-07-01 14:34:23 UTC RTC time: Fri 2016-07-01 14:34:23 Time zone: Europe/Zurich (CEST, +0200) Network time on: yes NTP synchronized: yes RTC in local TZ: no The output of ps -o start_time is actually the correct start time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365215] New: Animated tray icons cause plasmashell to use up a lot of CPU time
https://bugs.kde.org/show_bug.cgi?id=365215 Bug ID: 365215 Summary: Animated tray icons cause plasmashell to use up a lot of CPU time Product: plasmashell Version: 5.6.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch Should a tray icon be animated, e.g. the quassel icon when receiving a highlight, or the Skype icon while logging in, the "plasmashell" process takes up a good 15% of the total CPU time (25% being maximum for one core), with additional CPU time used by Xorg as well. (So it's probably busy sending tons of drawing commands) This is pretty bad when I receive a quassel highlight while I'm not looking, and then notice that plasmashell was busy draining my battery doing god-knows-what to re-render that small area on the screen. Reproducible: Always Steps to Reproduce: 1. Have a tray icon which is animated 2. Watch plasmashell shoot up in CPU usage xf86-video-intel 2.99.917+674+g9154dff-1 xorg-server 1.18.3 no special optimus setup compositing vsync prevention set to "automatic" $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365714] New: Akregator tray icon is very low resolution on high DPI displays
https://bugs.kde.org/show_bug.cgi?id=365714 Bug ID: 365714 Summary: Akregator tray icon is very low resolution on high DPI displays Product: akregator Version: unspecified Platform: Archlinux Packages URL: https://fratti.ch/bugdemos/akregator/akregatortray.png OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kdeb...@fratti.ch On high DPI displays, the tray icon Akregator shows appears to be an upscaled low-resolution one. Both the icon and the number drawn on top of it look very blocky. Reproducible: Always ✓ fratti@archbook ~ $ akregator --version akregator 5.2.3 ✓ fratti@archbook ~ $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 290mm x 170mm 1920x1080 60.00*+ 40.00 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1280x960 60.00 1368x768 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 346826] Konsole crash during destruction of XCB connection
https://bugs.kde.org/show_bug.cgi?id=346826 Nicolas Frattaroli changed: What|Removed |Added CC|kdeb...@fratti.ch | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 363672] Save As dialog don't use default KDE dialog
https://bugs.kde.org/show_bug.cgi?id=363672 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #4 from Nicolas Frattaroli --- Is there a compile-time option to change this? One of the bugs has been resolved, and the other one seems to be stuck in limbo, and using the Qt file dialog which doesn't have places and for me doesn't show any icons for some reason is a bit obnoxious. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369420] New: After turning off external monitor, taskbar disappears on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369420 Bug ID: 369420 Summary: After turning off external monitor, taskbar disappears on primary monitor Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: kdeb...@fratti.ch CC: plasma-b...@kde.org I connected my Laptop to the TV over HDMI, and first arranged them so that the TV was to the right of my laptop in the monitor arrangement widget. I accidentally set the TV as the primary display at this point. I then proceeded to arrange the TV to be above my laptop display in the widget, and also set it back to be a secondary monitor. At this point, all of your windows should be on the TV, while the task bar is back on the laptop. I played around with the refresh rates of the TV for a bit, but made sure not to set it as a primary display again. After being done watching my Chinese cartoons, I turned off the TV, and then disconnected the HDMI cable. This resulted in plasmashell suddenly eating my taskbar. I tried resetting the monitor configurations to the default value and made sure multiple times to set my laptop's display as being the primary. A reboot did not fix the issue, I had to manually add a new default panel to my laptop screen. Reproducible: Didn't try Steps to Reproduce: 1. Turn on TV 2. Connect HDMI cable to TV 3. Set TV to be the primary display 4.1 Move TV to the right of the primay display 4.2 Remember that you can also stack them in a vertical manner, so after moving it to the right, move it above the laptop display 5. Set laptop display to be the primary display again, after noticing your mistake 6. Drag a bunch of windows around and play with the refresh rate setting of the TV a little. 7. Turn off the TV before unplugging it, then unplug it. Actual Results: The panel disappears from the primary display, and a new one needs to be added back manually to get a panel again. Expected Results: plasma should not allow a situation where no connected monitor has any panels left, especially if one of them is the primary display. If someone can tell me whether plasma keeps a file somewhere with all the widget arrangements on different monitors, I can probably more closely identify what exactly happened, since apparently the original panel ended up on a monitor that was not connected, even though at the time of disconnecting a secondary monitor, it was on the proper display. This happened on X11. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369422] New: Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries
https://bugs.kde.org/show_bug.cgi?id=369422 Bug ID: 369422 Summary: Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries Product: KScreen Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: kdeb...@fratti.ch The refresh rate numbers in their dropdown menu of the advanced settings are being rounded to one decimal digit, which is insufficient precision to distinguish between some refresh rates. As an example, 59.98 Hz would get rounded to 60.0 Hz, when there already is a 60.0 Hz entry in the list stemming from the screen supporting 60.00 Hz also. This gets even worse with TVs which support several close refresh rates due to different standards in video frame rates, such as 24.00 Hz and 23.98 Hz (according to xrandr, but more likely to be 23.976 Hz). Increasing the precision by as much as it needs should fix this issue. Reproducible: Always Steps to Reproduce: 1. Either get a display that supports weird fractional refresh rates or use xrandr to check at which solutions your already connected display supports weird fractional refresh rates 2. Check the advanced settings, and notice how there are now duplicate-looking entries in the dropdown 3. After choosing them, note how xrandr's output will confirm that the two are distinct refresh rate, and thus confirms this is merely a visual issue. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369422] Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries
https://bugs.kde.org/show_bug.cgi?id=369422 Nicolas Frattaroli changed: What|Removed |Added URL||https://fratti.ch/bugdemos/ ||kscreen/refresh.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369420] After turning off external monitor, taskbar disappears on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369420 --- Comment #1 from Nicolas Frattaroli --- I've just tried connecting my laptop to the TV again. Everything went a bit crazy. The taskbar disappeared, even though my laptop display was set as the primary output. Plasma ended up crashing (sadly I could not get a crashdump), and I had to reboot the system after disconnecting it from the external TV to even get working compositing again, as windows did not refresh and the background was replaced with black. I've found some files of interest in my .local and .config: 1. Three files in .local/share/kscreen, which seem to list (in a duplicate manner) configured screens. Here they are, tarred and gzipped: https://fratti.ch/bugdemos/kscreen/kscreen.tar.gz 2. The following lines in .config/plasmashellrc: [PlasmaViews][Panel 1][Horizontal1920] length=3779 thickness=30 [PlasmaViews][Panel 16][Horizontal1920] thickness=36 I'm assuming my original panel, Panel 1, still exists *somewhere*, just not on any physical screens. Panel 16 seems to be the one I'm currently using and have created after I've encountered the bug, as it is indeed thicker. Any ideas on how I can get my original panel back, or identify where it even went? (Where does plasma store this info?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369420] After turning off external monitor, taskbar disappears on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369420 --- Comment #2 from Nicolas Frattaroli --- Created attachment 101317 --> https://bugs.kde.org/attachment.cgi?id=101317&action=edit org.kde.plasma.desktop-appletsrc Found where the applet parameters are saved in the elegantly named "plasma-org.kde.plasma.desktop-appletsrc" inside .config. As you can see, my original panel (referred to as [Containments][1]) has a lastScreen value of 1, whereas my new panel (referred to as [Containments][16]) has one of 0. What those numbers refer to, I do not know, but I'm fairly sure there's something fucky going on with whatever screen 1 is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369420] After turning off external monitor, taskbar disappears on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369420 --- Comment #3 from Nicolas Frattaroli --- Created attachment 101319 --> https://bugs.kde.org/attachment.cgi?id=101319&action=edit log of plasma crashing as the second monitor gets plugged in, and then being restarted but still messed up -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 Nicolas Frattaroli changed: What|Removed |Added CC|kdeb...@fratti.ch | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 357865] The QPA file dialog does not respect mime type filters
https://bugs.kde.org/show_bug.cgi?id=357865 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #1 from Nicolas Frattaroli --- If I comment out dialog.setOption(QFileDialog::DontUseNativeDialog); in spectacle for the native dialog, I see that the Save As mimetype filter is not set to "image/png", but it's not set to image/bmp like the original report appears to imply. Was the behaviour of this changed at some point without the ticket being mentioned in the commit? Also, arguably this makes this bug quite a bit less severe. The image now properly is a PNG, it's just not filtered for image/png. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 363672] Save As dialog don't use default KDE dialog
https://bugs.kde.org/show_bug.cgi?id=363672 --- Comment #6 from Nicolas Frattaroli --- Eh, you having to do the work to add a compile time option for this and me having to then maintain my own package seems not worth the effort when we could both invest that time in fixing the actual bug (which, by the way, should be marked as a blocker for this bug). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 363672] Save As dialog don't use default KDE dialog
https://bugs.kde.org/show_bug.cgi?id=363672 --- Comment #7 from Nicolas Frattaroli --- As it turns out, that other bug now has different behaviour. Instead of choosing the wrong MimeType filter, it now chooses no MimeType filter, which means that the only functionality broken with the native dialog now is that it doesn't hide everything except for image/png, which I believe to be a better behaviour anyway. At any rate, at least on my system (which is also Arch Linux), the native dialog is more functional than the Qt dialog right now. Perhaps the native dialog should be re-enabled again? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 367759] New: System occasionally unable to suspend if Dolphin left running with sshfs folder open
https://bugs.kde.org/show_bug.cgi?id=367759 Bug ID: 367759 Summary: System occasionally unable to suspend if Dolphin left running with sshfs folder open Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kdeb...@fratti.ch Occasionally, if a user attempts to suspend the system, the entire system will hang and cannot be recovered. This appears to be related to having Dolphin open viewing a SSHFS mounted folder. Journal messages indicate that the file.so component does not wish to be suspended, and its call trace shows references to fuse. Reproducible: Sometimes Steps to Reproduce: 1. Mount an SSHFS 2. Open a folder on it in dolphin and watch some videos or something 3. Suspend the system while dolphin is still open Actual Results: The system hangs on a black screen with only the mouse cursor showing and no longer accepts mouse or keyboard inputs. A while later, the sddm lock screen pops up, but does not react to any inputs. Switching VTs is impossible. The only way to get the system running again is to do a hard reset. Expected Results: The system actually suspends properly. The journal logs the following information: Aug 24 03:48:49 archbook kernel: Freezing user space processes ... Aug 24 03:48:49 archbook kernel: Freezing of tasks failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0): Aug 24 03:48:49 archbook kernel: file.so D 88021ca8bbb8 0 5791 641 0x0004 Aug 24 03:48:49 archbook kernel: 88021ca8bbb8 00ff8800a2fe1838 8180d500 8801aeade3c0 Aug 24 03:48:49 archbook kernel: 88021ca8bbc0 88021ca8c000 88021ca8bbe8 880064c89520 Aug 24 03:48:49 archbook kernel: 8800a2fe1840 fe00 88021ca8bbd0 815d9aac Aug 24 03:48:49 archbook kernel: Call Trace: Aug 24 03:48:49 archbook kernel: [] schedule+0x3c/0x90 Aug 24 03:48:49 archbook kernel: [] request_wait_answer+0x11a/0x270 [fuse] Aug 24 03:48:49 archbook kernel: [] ? wake_atomic_t_function+0x60/0x60 Aug 24 03:48:49 archbook kernel: [] __fuse_request_send+0x67/0x90 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_request_send+0x27/0x30 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_simple_request+0xcf/0x1a0 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_do_getattr+0x120/0x330 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_update_attributes+0x68/0x70 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_getattr+0x43/0x50 [fuse] Aug 24 03:48:49 archbook kernel: [] vfs_getattr_nosec+0x29/0x40 Aug 24 03:48:49 archbook kernel: [] vfs_getattr+0x26/0x30 Aug 24 03:48:49 archbook kernel: [] vfs_fstatat+0x78/0xc0 Aug 24 03:48:49 archbook kernel: [] SyS_newstat+0x33/0x60 Aug 24 03:48:49 archbook kernel: [] ? exit_to_usermode_loop+0x5e/0xc0 Aug 24 03:48:49 archbook kernel: [] ? syscall_return_slowpath+0x4e/0x60 Aug 24 03:48:49 archbook kernel: [] entry_SYSCALL_64_fastpath+0x1a/0xa4 Aug 24 03:48:49 archbook kernel: file.so D 880219263bb8 0 6439 641 0x0004 Aug 24 03:48:49 archbook kernel: 880219263bb8 00ff8800a2fe1838 880225ecc740 880221d18e40 Aug 24 03:48:49 archbook kernel: 880219263bc0 880219264000 880219263be8 880064d30580 Aug 24 03:48:49 archbook kernel: 8800a2fe1840 fe00 880219263bd0 815d9aac Aug 24 03:48:49 archbook kernel: Call Trace: Aug 24 03:48:49 archbook kernel: [] schedule+0x3c/0x90 Aug 24 03:48:49 archbook kernel: [] request_wait_answer+0x11a/0x270 [fuse] Aug 24 03:48:49 archbook kernel: [] ? wake_atomic_t_function+0x60/0x60 Aug 24 03:48:49 archbook kernel: [] __fuse_request_send+0x67/0x90 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_request_send+0x27/0x30 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_simple_request+0xcf/0x1a0 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_do_getattr+0x120/0x330 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_update_attributes+0x68/0x70 [fuse] Aug 24 03:48:49 archbook kernel: [] fuse_getattr+0x43/0x50 [fuse] Aug 24 03:48:49 archbook kernel: [] vfs_getattr_nosec+0x29/0x40 Aug 24 03:48:49 archbook kernel: [] vfs_getattr+0x26/0x30 Aug 24 03:48:49 archbook kernel: [] vfs_fstatat+0x78/0xc0 Aug 24 03:48:49 archbook kernel: [] SyS_newstat+0x33/0x60 Aug 24 03:48:49 archbook kernel: [] ? exit_to_usermode_loop+0x5e/0xc0 Aug 24 03:48:49 archbook kernel: [] ? syscall_return_slowpath+0x4e/0x60 Aug 24 03:48:49 archbook kernel: [] entry_SYSCALL_64_fastpath+0x1a/0xa4 Aug 24 03:48:49 archbook kernel: file.so D 880215733bb8 0 6447 641 0x0004 Aug 24 03:48:49 archbook kernel: 880215733bb8 00ff8800a2fe1838 88021cab9c80 880220d463c0 Aug 24 03:48:49 archbook kernel: 880215733bc0 880215734000 fff
[dolphin] [Bug 367759] System occasionally unable to suspend if Dolphin left running with sshfs folder open
https://bugs.kde.org/show_bug.cgi?id=367759 --- Comment #1 from Nicolas Frattaroli --- Note that this is on the Arch Linux stock kernel 4.7.1 on x86_64, for all I know this could be a kernel bug making fuse hang which makes file.so hang which makes Dolphin hang which makes suspend hang which makes my system hang. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 Nicolas Frattaroli changed: What|Removed |Added Product|kdialog |kfile Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403 --- Comment #2 from Nicolas Frattaroli --- Moved this to the product kfile, since kdialog simply builds on top of that. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 360526] New: Gwenview needs a long time to close when viewing a kdeconnect sftp image directly
https://bugs.kde.org/show_bug.cgi?id=360526 Bug ID: 360526 Summary: Gwenview needs a long time to close when viewing a kdeconnect sftp image directly Product: gwenview Version: Git (add output of "git log -1 --oneline" to description) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kdeb...@fratti.ch CC: myr...@kde.org When opening an image which is accessed over kdeconnect's sftp functionality by either double-clicking the file in Dolphin or opening it directly by passing it as a parameter to gwenview on the command line, gwenview will need a long time to close when the X on the window is hit. Long enough to trigger the KDE hung application dialogue. Surprisingly, if one navigates to said folder from within gwenview and opens an image, gwenview shuts down just fine. It seems that gwenview might be waiting on some redundant filesystem operation to complete when closing. Version information: gwenview: $ git log -1 --oneline c8edede SVN_SILENT made messages (after extraction) kdeconnect: kdeconnect 0.9.g-1 Reproducible: Always Steps to Reproduce: 1. Install kdeconnect on an Android phone and on your desktop. 2. Enable "Remote filesystem browser" 3. Browse the remote filesystem of your phone with dolphin 4. From within dolphin, open an image on your phone in gwenview 5. Click on the close window button. Actual Results: gwenview needs around 20 seconds to close the window Expected Results: gwenview closes instantly This seems to not happen with things mounted over sshfs. I have not tried reproducing with SFTP mounts other than kdeconnect's. Both devices are connected to wifi. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 360830] New: Implement high quality scaling filters for pages
https://bugs.kde.org/show_bug.cgi?id=360830 Bug ID: 360830 Summary: Implement high quality scaling filters for pages Product: okular Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kdeb...@fratti.ch Currently, pages are scaled with what appears to be bilinear filtering. While fast, this can often result in a blurry picture. While this isn't too much of an issue when reading a PDF document, it can be pretty annoying when reading small text in a CBZ that's zoomed in to fit the page width. Examples for scaling filters can be found in mpv's documentation: https://mpv.io/manual/stable/#video-output-drivers-bilinear I'd suggest Mitchell-Netravali, here's a PDF of the paper I found: www.cs.utexas.edu/users/fussell/courses/cs384g/lectures/mitchell/Mitchell.pdf Additionally, the current bilinear interpolation should be done using GPU accelaration if available, if this isn't already the case, for performance and power saving purposes. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364503] New: plasmashell freezes is system is I/O bound
https://bugs.kde.org/show_bug.cgi?id=364503 Bug ID: 364503 Summary: plasmashell freezes is system is I/O bound Product: plasmashell Version: 5.6.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kdeb...@fratti.ch CC: bhus...@gmail.com, plasma-b...@kde.org If the system is I/O bound, such as when removing a lot of files, or if there is a hung SSH process of a remotely mounted sshfs, plasmashell will hang. In the ksysguard process list, it shows up as being in "disk sleep". As soon as the heavy I/O operation finishes (or the hung ssh process is terminated), plasmashell becomes responsive again. Reproducible: Always Steps to Reproduce: 1. Remotely mount something through sshfs 2. Put your system to sleep for a few minutes 3. Wake the system, the ssh process should now be hanging. Shortly afterwards, plasmashell should enter disk sleep. Alternatively, 1. Grab the GCC source through SVN 2. Build GCC 3. Run a recursive rm operation on the folder, and attempt to interact with plasmashell Actual Results: plasmashell hangs until the I/O issue is resolved. For a stuck SSHFS mount, this usually means that the associated SSH task needs to be killed. plasmashell will not react to SIGKILL while it's in disk sleep mode. Expected Results: plasmashell should have a timeout on non-essential I/O operations, or perform blocking I/O in a separate thread, as to ensure that user interactivity is not lost. While this happened, a Dolphin window into the SSHFS mounted folder was opened. This might be related, so I'll add it here. The system uses a Kingston SSD connected through mSATA, and uses ext4 as both the root and the /home file system. While plasmashell is frozen, Ctrl+Escape for opening the system activity window still works, however, Alt+F2 to bring up KRunner doesn't. The volume keys also no longer work, which is a bit awkward when I click on a video and then notice that plasmashell is frozen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364503] plasmashell freezes if system is I/O bound
https://bugs.kde.org/show_bug.cgi?id=364503 Nicolas Frattaroli changed: What|Removed |Added Summary|plasmashell freezes is |plasmashell freezes if |system is I/O bound |system is I/O bound -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 350661] Kate crashes if block of text is indented multiple times at once in vi mode
https://bugs.kde.org/show_bug.cgi?id=350661 --- Comment #2 from Nicolas Frattaroli --- The behaviour changed in recent versions, apparently. Instead of crashing, it now claims multiple indents are an invalid command. 1. i activates insert mode. hit i, write some text, multiple lines. 2. Then hit escape to leave insert mode. 3. Enter visual line selection mode by hitting Shift+V 4. Use the cursor or vi movement keys (h, j, k, l) to select multiple lines 5. Hit : 6. Hit > twice 7. Hit Enter Note how it says unrecognised command now. In earlier versions, it would crash. It can be worked around by instead of doing steps 5 to 7, simply typing the number of places to indent and >, e.g. "2>" -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 363209] New: Allow browsing AppImage images
https://bugs.kde.org/show_bug.cgi?id=363209 Bug ID: 363209 Summary: Allow browsing AppImage images Product: ark Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kdemail.net Reporter: kdeb...@fratti.ch CC: rak...@freebsd.org, rthoms...@gmail.com AppImage consist of an ELF embedded in the ISO9660 header which mounts the image, and the actual zisofs compressed data. I do not think AppImage has its own mimetype, though the format should be easily identifiable considering it's essentially an ISO9660 with a special header. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363846] New: Krita crashes if a second window with a view into the first window is closed
https://bugs.kde.org/show_bug.cgi?id=363846 Bug ID: 363846 Summary: Krita crashes if a second window with a view into the first window is closed Product: krita Version: 3.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: kdeb...@fratti.ch If a second window is opened, and assigned the view of the document in the first window, and then said second window is closed, Krita will crash. Reproducible: Always Steps to Reproduce: 1. Create a new document 2. Go to Window->New Window 3. In said new window, go to Window->New View->Unnamed 4. Close the new window. Actual Results: Krita will close both windows as it crashes Expected Results: Only the second window closes This crash only happens if the window is opened after creating the document, apparently. If I create a new window first, then create a new document, then switch to the second window and assign the view there and close it, it won't crash. Here's the backtrace Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57567aa800 (LWP 2659))] Thread 5 (Thread 0x7f5734bd9700 (LWP 2661)): #0 0x7f57535b268d in poll () from /usr/lib/libc.so.6 #1 0x7f574d39cfd6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f574d39d0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f57540e974b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f57540914ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f5753eb82f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f574dae6a65 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f5753ebd1d8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f574d8bb474 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f57535bb69d in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f571e78e700 (LWP 2662)): #0 0x7f574d8c109f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5753ebe08b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f5753eb6d53 in QSemaphore::acquire(int) () from /usr/lib/libQt5Core.so.5 #3 0x7f57519540dd in ?? () from /usr/lib/libkritaimage.so.15 #4 0x7f5753ebd1d8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f574d8bb474 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f57535bb69d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f571df8d700 (LWP 2663)): #0 0x7f574d8c109f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5753ebe08b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f5753eb7046 in QSemaphore::tryAcquire(int, int) () from /usr/lib/libQt5Core.so.5 #3 0x7f575197039a in KisTileDataSwapper::run() () from /usr/lib/libkritaimage.so.15 #4 0x7f5753ebd1d8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f574d8bb474 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f57535bb69d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f571d78c700 (LWP 2665)): #0 0x7f574d8c109f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5753ebe08b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f5754fed139 in ?? () from /usr/lib/libQt5Widgets.so.5 #3 0x7f5753ebd1d8 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f574d8bb474 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f57535bb69d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f57567aa800 (LWP 2659)): [KCrash Handler] #5 0x7f5753091ee0 in KisBrush::scale() const () from /usr/lib/libkritalibbrush.so.15 #6 0x7f5729e6d4a2 in KisBrushBasedPaintOpSettings::brushOutlineImpl(KisPaintInformation const&, KisPaintOpSettings::OutlineMode, double, bool) const () from /usr/lib/libkritalibpaintop.so.15 #7 0x7f5729e6da38 in KisBrushBasedPaintOpSettings::brushOutline(KisPaintInformation const&, KisPaintOpSettings::OutlineMode) const () from /usr/lib/libkritalibpaintop.so.15 #8 0x7f57560a511a in KisToolFreehandHelper::paintOpOutline(QPointF const&, KoPointerEvent const*, KisPaintOpSettings const*, KisPaintOpSettings::OutlineMode) const () from /usr/lib/libkritaui.so.15 #9 0x7f575609fba1 in KisToolFreehand::getOutlinePath(QPointF const&, KoPointerEvent const*, KisPaintOpSettings::OutlineMode) () from /usr/lib/libkritaui.so.15 #10 0x7f57560acb1a in KisToolPaint::requestUpdateOutline(QPointF const&, KoPointerEvent const*) () from /usr/lib/libkritaui.so.15 #11 0x7f5750fb93e0 in KoToolProxy::mouseMoveEvent(QMouseEvent*, QPointF const&) () from /usr/lib/libkritaflake.so.15 #12 0x7f5755e
[krita] [Bug 363847] New: Measure tool should also show angle and distance using a tooltip at the cursor position
https://bugs.kde.org/show_bug.cgi?id=363847 Bug ID: 363847 Summary: Measure tool should also show angle and distance using a tooltip at the cursor position Product: krita Version: 3.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: kdeb...@fratti.ch Currently, the measure tool will only show distance and angle measurements in the tool options docker. Sometimes, people may not currently see this though as they start measuring, and either get confused as to where the measurement is displayed or get annoyed at having forgotten to tab to the right docker again before starting to line up their cursor just right. By adding a small hovering tooltip displaying the angle and the distance near the cursor position, this could be made more intuitive and make for a smoother workflow. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363848] New: Transform tool does not allow rotating by fractions of a degree
https://bugs.kde.org/show_bug.cgi?id=363848 Bug ID: 363848 Summary: Transform tool does not allow rotating by fractions of a degree Product: krita Version: 3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: transform Assignee: krita-bugs-n...@kde.org Reporter: kdeb...@fratti.ch When trying to rotate a large scanned-in page just right, occasionally, one notices that the measure tool will report fractions of a degree of rotation. However, the transform tool will now allow users to actually input fractional values such as 12.3, thus users have to settle for the closest integer, which for large measured reference lines can be noticeably off. Reproducible: Always Steps to Reproduce: 1. Go to the transform tool options and choose "Rotate" 2. Try to input some number with a fraction, such as "1.5". 3. Note how it will let you input the decimal point, but no number afterwards. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352645] kOrganizer 15.08.1-pre: Multiple issues with categories cause a huge mess and make using categories basically impossible
https://bugs.kde.org/show_bug.cgi?id=352645 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #7 from Nicolas Frattaroli --- I can also confirm this, assigning several ToDo items the same category apparently makes duplicates of said category as well. Arch Linux, Version 15.12.1 Help->About KOrganizer->Version mentions "Version 5.1.1", KDE Frameworks 5.18.0, Qt 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer
https://bugs.kde.org/show_bug.cgi?id=353240 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #1 from Nicolas Frattaroli --- Same issue here on a 168 DPI monitor, Arch Linux, KOrganizer 15.12.1 (version number in "About KOrganizer->Version" shows "5.1.1" and using frameworks 5.18.0) The font sizes in the month view appear to be too big in general. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer
https://bugs.kde.org/show_bug.cgi?id=353240 --- Comment #2 from Nicolas Frattaroli --- Created attachment 97091 --> https://bugs.kde.org/attachment.cgi?id=97091&action=edit Screenshot of the monthly calendar view -- You are receiving this mail because: You are watching all bug changes.
