[frameworks-ki18n] [Bug 482657] Underlined characters in titles rendered incorrectly as ampersands in KDE6
https://bugs.kde.org/show_bug.cgi?id=482657 --- Comment #5 from Adrian Insaurralde --- maybe this would fix this? https://invent.kde.org/plasma/breeze/-/merge_requests/491 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 482657] Underlined characters in titles rendered incorrectly as ampersands in KDE6
https://bugs.kde.org/show_bug.cgi?id=482657 Adrian Insaurralde changed: What|Removed |Added CC||adrianinsa...@freecad.org --- Comment #4 from Adrian Insaurralde --- I'm still seeing this issue in FreeCAD, with qt 6.7.2 which should already include the qt fix. Maybe this fix needs to be applied in breeze too? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 493400] New: Akonadi Server crash
https://bugs.kde.org/show_bug.cgi?id=493400 Bug ID: 493400 Summary: Akonadi Server crash Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: de...@easynet.dev CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.10.9-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: After working on Nextcloud folder in Dolphin, the laptop stops responding and then the whole DE restarted The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x558b8903e064 in ?? () #5 0x7ff1afb0bf40 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff1afade365 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff1afae1899 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff1afb3bb57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff1ae30c7df in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7ff1ae30ea17 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7ff1ae30f180 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7ff1afb3b1ed in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff1afadcd02 in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7ff1afae5722 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x558b8903b7d4 in ?? () #16 0x7ff1af23edba in __libc_start_call_main (main=main@entry=0x558b8903b4d0, argc=argc@entry=1, argv=argv@entry=0x7ffde49d0318) at ../sysdeps/nptl/libc_start_call_main.h:58 #17 0x7ff1af23ee75 in __libc_start_main_impl (main=0x558b8903b4d0, argc=1, argv=0x7ffde49d0318, init=, fini=, rtld_fini=, stack_end=0x7ffde49d0308) at ../csu/libc-start.c:360 #18 0x558b8903da91 in ?? () [Inferior 1 (process 3064) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 448248] Cannot change Qbittorrent Tray icon anymore
https://bugs.kde.org/show_bug.cgi?id=448248 --- Comment #15 from Adrian Insaurralde --- the issue for me seems to be that breeze does not provide tray icons for qbittorrent, I guess at some point in time I enabled the "use icons from system theme" option in qbittorrent, after disabling that and restarting qbittorrent the correct monochrome icon is shown. I'm running archlinux with: qbittorrent 4.6.6 plasma 6.1.5 frameworks 6.5.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 448248] Cannot change Qbittorrent Tray icon anymore
https://bugs.kde.org/show_bug.cgi?id=448248 Adrian Insaurralde changed: What|Removed |Added Ever confirmed|1 |0 CC||adrianinsa...@freecad.org Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- --- Comment #13 from Adrian Insaurralde --- this is still a problem for me -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 492535] New: Dolphin crashed when i tried to access samba server
https://bugs.kde.org/show_bug.cgi?id=492535 Bug ID: 492535 Summary: Dolphin crashed when i tried to access samba server Classification: Applications Product: dolphin Version: 23.08.1 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: de...@easynet.dev CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.08.1) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.10.3-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: After I added the User/pass to access the my samba NAS, Dophing crashed unexpected. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #5 0x7f990cca347f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 0x7f990cc54532 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7f990cc3d4ed in __GI_abort () at ./stdlib/abort.c:79 #8 0x7f990f125419 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #9 0x7f990f1cf8bb in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #10 0x7f990d518cbe in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f990e91fce9 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #12 0x7f990e925b2b in ?? () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #13 0x7f990d518cbe in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f990f17715e in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x7f990f171e2a in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #16 0x7f990f174779 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #17 0x7f990d518cbe in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f990d50bf40 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f990e163092 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f990d4de398 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f990d4e1899 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f990d53bb57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f990b10c7df in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f990b10ea17 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f990b10f180 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f990d53b1ed in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f990d4dcd02 in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f990d4e5722 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x55da01d6e17e in ?? () #30 0x7f990cc3edba in __libc_start_call_main (main=main@entry=0x55da01d6ced0, argc=argc@entry=2, argv=argv@entry=0x7ffc1a061818) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f990cc3ee75 in __libc_start_main_impl (main=0x55da01d6ced0, argc=2, argv=0x7ffc1a061818, init=, fini=, rtld_fini=, stack_end=0x7ffc1a061808) at ../csu/libc-start.c:360 #32 0x55da01d6e6b1 in ?? () [Inferior 1 (process 987744) detached] The reporter indicates this bug may be a duplicate of or related to bug 488787, bug 489968, bug 487587, bug 487834, bug 488428, bug 487327, bug 487391, bug 486859, bug 486830, bug 486697, bug 486728, bug 485914, bug 485757, bug 485365, bug 484324, bug 484160, bug 489270, bug 490249, bug 491896, bug 492371, bug 492527. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477016] Brightness flicker with adaptive sync
https://bugs.kde.org/show_bug.cgi?id=477016 --- Comment #14 from Adrian --- Sorry meant to say flicker not flash* -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477016] Brightness flicker with adaptive sync
https://bugs.kde.org/show_bug.cgi?id=477016 Adrian changed: What|Removed |Added CC||trac...@causticrays.com --- Comment #13 from Adrian --- I've also been having constant issues with VRR on automatic mode enabling on programs like firefox, mpv, virtual machine manager and so on. While they are on full screen it causes the refresh rate constantly jump between 45 hz and 165 hz causing my display to flash pretty badly. I think the severity on this bug should probably be increased as this flashing I think could seriously cause someone epilepsy. SOFTWARE/OS VERSIONS Distro: Arch Linux Kernel Version: 6.10.6-arch1-1 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 GPU: RX7900 XT Mesa: Mesa 24.1.6-arch1.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 490306] patch 4f3a8968 not working as intended
https://bugs.kde.org/show_bug.cgi?id=490306 --- Comment #7 from Adrian Insaurralde --- tried now and it doesn't fix the issue :( -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 490306] patch 4f3a8968 not working as intended
https://bugs.kde.org/show_bug.cgi?id=490306 --- Comment #6 from Adrian Insaurralde --- so there was a new android app release, has the patch been included? anyone has confirmed if it works? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 490714] The program is not restored from a saved session after another update.
https://bugs.kde.org/show_bug.cgi?id=490714 --- Comment #2 from Adrian Carver --- (In reply to Albert Astals Cid from comment #1) Albert, if you don't understand something, you can always ask clarifying questions to the authors of the two “brilliant” ideas: the one who decided that the idea of redirecting a KDE user to the project's internal bug tracker with mandatory registration there was a very good idea. The second person who can explain to you what's going on is the one who, after the first one, decided not to create a sane registration form with a short introductory FAQ on how to use this bug tracker, sincerely hoping in his heart that an ordinary user wouldn't register here. I wouldn't, if I hadn't once again started to be annoyed by the non-obvious behavior of the system and its separate component - ocular. I clicked on the “Report a bug...” menu and wrote it down as best I could. Where to redistribute it - to bugs, non-critical bugs, wishes...in general, this is the job of “moderator”, I assume yours. To me, this kind of behavior is critical in use. Well, no one has explicitly familiarized me with what the statuses in your tracker mean. At the same time, you can start a couple of tasks to finalize the registration form on the basis of the above: the situation shows that it will be useful. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 490714] New: The program is not restored from a saved session after another update.
https://bugs.kde.org/show_bug.cgi?id=490714 Bug ID: 490714 Summary: The program is not restored from a saved session after another update. Classification: Applications Product: okular Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: adrian.car...@yandex.ru Target Milestone: --- Recovering previously discovered books is an old issue that we come back to again and again. Currently (I can't think why it's done this way), you can only restore previously opened books or documents one by one in the File - Recent Files section. Considering that I usually have 15 or more of them open, opening all of them individually turns into an incredibly boring quest of several minutes (especially if they are in different places). I've been using session recovery mechanism - and ocular most often opens books again...but there is a nuance - session saving also likes to fail very much and as a result I have to look for the documents I need again in different places. I've been using session recovery mechanism - and ocular most often opens books again...but there is a nuance - session saving also likes to fail very much and as a result I have to look for the documents I need again in different places. Is it not possible to make after many years some semblance of session work and still realize a primitive mechanism of history storage with its restoration after a new start? Because crutches, frankly speaking, are tiresome. SOFTWARE/OS VERSIONS Linux: 6.10.0-arch1-2 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 490306] patch 4f3a8968 not working as intended
https://bugs.kde.org/show_bug.cgi?id=490306 Adrian Insaurralde changed: What|Removed |Added CC||adrianinsa...@freecad.org --- Comment #1 from Adrian Insaurralde --- I've seen a different patch proposed at manjaro forum: https://forum.manjaro.org/t/is-kdeconnect-file-browse-broken-again/165481/5 can this be included into kdeconnect? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Dominik Adrian Grzywak changed: What|Removed |Added CC|starte...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481214] Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481214 --- Comment #2 from Adrian --- *** Bug 481212 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481212] Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481212 Adrian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Adrian --- *** This bug has been marked as a duplicate of bug 481214 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481212] Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481212 --- Comment #1 from Adrian --- Duplicate/thread to remove -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481214] Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481214 --- Comment #1 from Adrian --- Created attachment 165747 --> https://bugs.kde.org/attachment.cgi?id=165747&action=edit widget translate (from up to bottom): screen brightness, keyboard brightness, power-profle mode (on widget: power saver is set), battery infos... Adding better screenshot -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481214] Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481214 Adrian changed: What|Removed |Added Platform|Other |Kubuntu -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481214] New: Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481214 Bug ID: 481214 Summary: Power/battery widget in tray doesn't show power profile/brightness properly Classification: Plasma Product: Powerdevil Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: byadii22+kde...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 165746 --> https://bugs.kde.org/attachment.cgi?id=165746&action=edit widget translate (from up to bottom): screen brightness, keyboard brightness, power-profle mode (on widget: power saver is set), battery infos... STEPS TO REPRODUCE 1. n/a OBSERVED RESULT Battery status widget show properly battery info (like status of charging, time remaining, percentage, etc...), but after click on settings bar, its don't 'update' its status properly. I mean the settings is changed (example: power profile from power-saver to balanced or screen brightness from 30% to 80%, etc...) but circle on bar is still on the same place. When i changed brightness by keyboard, it works fine (pop-up window shows percentage fine) and when i change power-profile by powerproflesctl, its shows and makes changes ok. Problem is only with widget, with showing current status of settings. The same result is when i create new user account and when i clean my own ~/.cache directory. Currently running Wayland, but on X11 is the same issue. EXPECTED RESULT Properly showing info (of power-settings, brightness, etc) after click on battery widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 / 6.5.0-17-generic (64-bit) (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Wayland Runs on Lenovo T14s (gen1), i5-10210U -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481212] New: Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481212 Bug ID: 481212 Summary: Power/battery widget in tray doesn't show power profile/brightness properly Classification: Plasma Product: Powerdevil Version: 5.27.8 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: byadii22+kde...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 165744 --> https://bugs.kde.org/attachment.cgi?id=165744&action=edit widget translate (from up to bottom): screen brightness, keyboard brightness, power-profle mode (on widget: power saver is set), battery infos... STEPS TO REPRODUCE 1. n/a OBSERVED RESULT Battery status widget show properly battery info (like status of charging, time remaining, percentage, etc...), but after click on settings bar, its don't 'update' its status properly. I mean the settings is changed (example: power profile from power-saver to balanced or screen brightness from 30% to 80%, etc...) but circle on bar is still on the same place. When i changed brightness by keyboard, it works fine (pop-up window shows percentage fine) and when i change power-profile by powerproflesctl, its shows and makes changes ok. Problem is only with widget, with showing current status of settings. The same result is when i create new user account and when i clean my own ~/.cache directory. Currently running Wayland, but on X11 is the same issue. EXPECTED RESULT Properly showing info (of power-settings, brightness, etc) after click on battery widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 / 6.5.0-17-generic (64-bit) (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Wayland Runs on Lenovo Thinkpad T14S (gen1) with Intel i5-10210U -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480211] Feature Request for Dolphin - Add the ability to unmount removable storage devices
https://bugs.kde.org/show_bug.cgi?id=480211 --- Comment #7 from Adrian --- I didn't mention this properly, the way I envision this working is like this: The arrow icon's (see image) behavior should remain as is, as in safely removing the removable storage device. When you right click over the removable storage device, in the context menu, "Safely remove" should still remain as the first option but under it should also exist the option to "Unmount". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480211] Feature Request for Dolphin - Add the ability to unmount removable storage devices
https://bugs.kde.org/show_bug.cgi?id=480211 --- Comment #6 from Adrian --- Created attachment 165290 --> https://bugs.kde.org/attachment.cgi?id=165290&action=edit Arrow "eject" icon -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480211] Feature Request for Dolphin - Add the ability to unmount removable storage devices
https://bugs.kde.org/show_bug.cgi?id=480211 --- Comment #5 from Adrian --- (In reply to Jin Liu from comment #4) > Also note that for spinning disks, "safely remove" also spins them down. So > if you change "safely remove" to only do `umount`, that would be a behavior > change for spinning disks, and might be undesirable. As I've said in my original message I think safely remove should remain the main option for removable storage devices for good reason as you've mentioned but, when you right click on the removable storage device, there should still exist the option to just unmount. Just being able to unmount from the UI is extremely useful to me and others. (In reply to fanzhuyifan from comment #1) > Imo having both "safely remove" and "unmount" options may be a bit confusing > for the general user... I think users will always click by default on the "arrow" next to the removable storage device icon on dolphin (see image) if they wish to safely remove the removable storage device (eject). The eject icon also exists on other platforms like MacOS and even other DEs so it's appearance is not totally unfamiliar. If not the behavior of both options I think is very obvious, one making the device inaccessible until you unplug and plug back in the device (disconnecting it) and one just unmounting it but again people will always just click the "arrow" (or just unplug the removable storage device without clicking anything). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480211] New: Feature Request for Dolphin - Add the ability to unmount removable storage devices
https://bugs.kde.org/show_bug.cgi?id=480211 Bug ID: 480211 Summary: Feature Request for Dolphin - Add the ability to unmount removable storage devices Classification: Applications Product: dolphin Version: 23.08.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: trac...@causticrays.com CC: kfm-de...@kde.org Target Milestone: --- Right now when you insert a removable storage device, after mounting it in Dolphin, the only thing you can do afterwards is "Safely Remove" which will unmount and completely disconnect the removable storage device making it unusable unless you unplug and plug in back the removable storage device. Having "Safely Remove" is completely fine but would be nice if we also had the ability to right click on the removable storage device and have a "Unmount" option that just unmounts the partition but doesn't disconnect the device entirely. This would be very useful for anyone wanting to quickly just unmount, reformat the removable device for example or write a ISO to it and then mount it again, without having to constantly unplug and plug it back (which is what you have to currently do with only having "Safely Remove"). In short, my suggestion is to add a "Unmount" option when you right click on a removable storage device beside the "Safely Remove" option to be able to just unmount the removable storage device but not disconnect it completely.q SOFTWARE/OS VERSIONS Kernel Version: 6.7.0-arch3-1 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 455784] Support for Pressure Stall Information from /proc in ksysguardd
https://bugs.kde.org/show_bug.cgi?id=455784 Adrian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Adrian --- ksysguardd seems like it may be deprecated in favor of ksystemstats -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476190] New: incorrect window minimize animation
https://bugs.kde.org/show_bug.cgi?id=476190 Bug ID: 476190 Summary: incorrect window minimize animation Classification: Plasma Product: kwin Version: 5.27.8 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: f564...@gmail.com Target Milestone: --- Created attachment 162614 --> https://bugs.kde.org/attachment.cgi?id=162614&action=edit video with bug SUMMARY *** Window animation minimizes to minimize button instead of taskbar when you clicking minimize button on window title bar. If I minimize and maximize it from taskbar button, everything will be fine. *** STEPS TO REPRODUCE 1. Open any window (e.g. konsole) 2. Press minimize button on a window title bar 3. OBSERVED RESULT Window minimizes to window title bar minimize button EXPECTED RESULT Window should minimize to taskbar icon. SOFTWARE/OS VERSIONS Distro: Debian GNU/Linux trixie (testing) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338724] Symlink from one collection to another causes high CPU usage, freeze and DB lockup errors
https://bugs.kde.org/show_bug.cgi?id=338724 --- Comment #5 from Adrian Dziubek --- Sorry, I have not been using digiKam or any other album software for some time. I lost control over my pictures mostly. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 473828] New: Crashed when flipping between two images using arrow keys.
https://bugs.kde.org/show_bug.cgi?id=473828 Bug ID: 473828 Summary: Crashed when flipping between two images using arrow keys. Classification: Applications Product: gwenview Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: adrianbo...@gmail.com Target Milestone: --- Application: gwenview (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-27-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I was using the left/right arrow keys to browse through a directory of PNG images. Sometimes I'd run across two adjacent images that were similar and I'd then blink back and forth between them by alternating left/right arrow. While (relatively) rapidly blinking between two fo these images, Gwenview crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f8fa5e3c406 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f8fa5e2287c in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f8fa5e235a4 in __libc_message (fmt=fmt@entry=0x7f8fa5fb86c6 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 #10 0x7f8fa5f2ec1b in __GI___fortify_fail (msg=msg@entry=0x7f8fa5fb86ae "stack smashing detected") at ./debug/fortify_fail.c:24 #11 0x7f8fa5f2ebf6 in __stack_chk_fail () at ./debug/stack_chk_fail.c:24 #12 0x7f8fa6b78060 in cmsBuildParametricToneCurve () from /lib/x86_64-linux-gnu/liblcms2.so.2 #13 0x7f8fa6b95935 in cmsCreate_sRGBProfileTHR () from /lib/x86_64-linux-gnu/liblcms2.so.2 #14 0x7f8fa8be031f in Gwenview::Cms::Profile::getSRgbProfile() () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #15 0x7f8fa8c11b19 in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #16 0x7f8fa78b6921 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f8fa78b717a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f8fa78b6673 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f8fa78b717a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f8fa78b6673 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f8fa787a5d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f8fa79223f8 in QGraphicsEffectSource::draw(QPainter*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f8fa78b7573 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f8fa78b7ba2 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f8fa78dc277 in QGraphicsView::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f8fa75aec28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f8fa765b792 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f8fa68baba3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f8fa756bf82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f8fa68bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f8fa75a6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f8fa75a7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f8fa75a8a66 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7f8fa75a73cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7f8fa75a8a66 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7f8fa75a73cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7f8fa
[plasma-nm] [Bug 406160] [RFE] Move VPN connections to different list
https://bugs.kde.org/show_bug.cgi?id=406160 Adrian Glaubitz changed: What|Removed |Added CC||glaub...@physik.fu-berlin.d ||e --- Comment #3 from Adrian Glaubitz --- (In reply to Kevin Adler from comment #2) > One of my biggest pet peeves is the list of wifi connections reloading right > as I'm about to click the button to connect to my VPN (and stuff reloading > while you're trying to use it in general). I agree. I regularly run into this problem myself when trying to initiate a VPN connection. The list entries jump around the moment I try to click the "Connect" button resulting in an accidental connection attempt to a different network resulting in my current WiFi connection being disconnected. > Moving the VPN connections to a separate tab would be helpful to prevent > this problem, though alternatively stop refreshing wifi networks when the > tray is opened and adding a manual refresh button would also work. Alternatively, it would also help to add a checkbox to hide unknown WiFi connections which would reduce the risk of an accidental connection attempt to a nearby network. In most cases, a user has only one known network nearby which they can connect to, so being able to hide the unknown networks would eliminate the possibility of accidentally trying to connect to such a network which would disconnect the current connection. On the other hand, making it a simple checkbox would allow to unhide unknown networks easily at any time to be able to connect to a new WiFi network when necessary. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471808] New: Time Adjust based on filename sporadically incorrect
https://bugs.kde.org/show_bug.cgi?id=471808 Bug ID: 471808 Summary: Time Adjust based on filename sporadically incorrect Classification: Applications Product: digikam Version: 8.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-TimeAdjust Assignee: digikam-bugs-n...@kde.org Reporter: adrian.br...@gmail.com Target Milestone: --- SUMMARY When modifying date/time metadata based on filename with the format described below, some of the files are correctly translated while other are incorrectly translated or deemed impossible to interpret. STEPS TO REPRODUCE 1. Run Digikam AppImage 2. Open Adjust Time & Date dialog 3. Select relevant files and tick File name timestamp OBSERVED RESULT Correctly adjusted: 2022-12-14_270__71a25cea-c940-4cba-ad7f-719a748d97e8.jpeg => 2022:12:14 00:00:00 2022-12-13_270__d8d2d326-0831-42c6-807a-f7ca326552fd.jpeg => 2022-12-13 00:00:00 Incorrectly adjusted: 2023-01-06_0__958ef4b3-d919-4a34-83dc-e8b4f5400053.jpeg => 2006:01:23 00:53:00 2022-11-02_270__3fcf88c8-a6d6-4e66-ae2f-0a0541a42226.jpeg => 2002:11:22 22:26:00 2022-11-10_270__71529f11-8064-43ec-b450-a0337a29a6c0.jpeg => 2010:11:22 03:37:00 2022-12-14_270__43e786ff-6d84-45b2-86a8-ccbf19041178.jpeg => 1178:04:19 00:00:00 Not able to be interpreted for adjustment: 2023-01-25_270__797e0df3-58d9-4382-9349-1ef1d3729c59.jpeg => nil 2023-01-24_0__791e8006-3631-42d5-9454-b7b069ebb78a.jpeg => nil EXPECTED RESULT 2023-01-06_0__958ef4b3-d919-4a34-83dc-e8b4f5400053.jpeg => 2023:01:06 00:00:00 2022-11-02_270__3fcf88c8-a6d6-4e66-ae2f-0a0541a42226.jpeg => 2022:11:02 00:00:00 2022-11-10_270__71529f11-8064-43ec-b450-a0337a29a6c0.jpeg => 2022:11:10 00:00:00 2022-12-14_270__43e786ff-6d84-45b2-86a8-ccbf19041178.jpeg => 2022:12:13 00:00:00 2023-01-25_270__797e0df3-58d9-4382-9349-1ef1d3729c59.jpeg => 2023-01-25 00:00:00 2023-01-24_0__791e8006-3631-42d5-9454-b7b069ebb78a.jpeg => 2023-01-24 00:00:00 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 using AppImage of digikam 8.0.0 KDE Plasma Version: KDE Frameworks Version: 5.104.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION The format is most likely -MM-DD_ROTATION__UID.jpeg -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441907] Yakuake always opens on the left screen in case of display scaling
https://bugs.kde.org/show_bug.cgi?id=441907 Adrian Kalla changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #6 from Adrian Kalla --- (In reply to Ravi from comment #5) > Works for me on yakuake revision 45be2665850e44180f692dc0a23d4539d91657ed > and konsole revision 77c6f26c8b9fefa7e3b9ad648ae61117d057a8d4 Cannot confirm that: with Yakuake 23.04.2 and Konsole 23.04.2 (both newer than that revisions) nothing changed for me. Yakuake still behaves exactly as in my comment from a year ago. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 468754] Touptek camera driver resets after every exposure
https://bugs.kde.org/show_bug.cgi?id=468754 Adrian Knagg-Baugh changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Adrian Knagg-Baugh --- Marked as RESOLVED - NOT A BUG as the bug was in the toupbase INDI driver, and has now been fixed in git. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 461407] Crash on opening optical trains dialog
https://bugs.kde.org/show_bug.cgi?id=461407 Adrian Knagg-Baugh changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Adrian Knagg-Baugh --- This appears to be fixed now as of 3.6.4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 468754] Touptek camera driver resets after every exposure
https://bugs.kde.org/show_bug.cgi?id=468754 Adrian Knagg-Baugh changed: What|Removed |Added CC||aje.ba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 468754] New: Touptek camera driver resets after every exposure
https://bugs.kde.org/show_bug.cgi?id=468754 Bug ID: 468754 Summary: Touptek camera driver resets after every exposure Classification: Applications Product: kstars Version: 3.6.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY Touptek camera driver (possibly others, but the Touptek is the only one I can check) gets reset after every exposure. This is making it impossible to capture a sequence of bias frames as after every frame during the reset the fan and cooler switch off and the temperature rises before they switch back on again. I don't want to incur any risk from unnecessary thermal cycling from taking hundreds of bias frames, and in any case it would drag out the process excessively if I were to wait for the temperature to stabilise again after each one. If I use the INDI control panel and trigger an exposure manually, the camera does not reset, so I suspect the issue is within ekos. STEPS TO REPRODUCE 1. Set a job of multiple exposures using the Toupcam driver. 2. Start the job. 3. OBSERVED RESULT The camera fan and cooler stop and restart before each exposure. EXPECTED RESULT The camera should remain in a state of constant cooling throughout, with no resets occurring. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466205] Discover crashes in KNSCore::Engine::addProvider() while checking for updates
https://bugs.kde.org/show_bug.cgi?id=466205 --- Comment #1 from Pedro Adrian Rojas --- It's still crashing, at about the same point in the update, the new version of the plasma-discover application is "5.27.2", I keep my Arch Linux update, but I can't update the plasma add-ons, it indicates that there are 13 updates pending -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465311] Elisa does not locate certain songs
https://bugs.kde.org/show_bug.cgi?id=465311 Adrian Barbuio changed: What|Removed |Added CC||lz4_8...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465311] Elisa does not locate certain songs
https://bugs.kde.org/show_bug.cgi?id=465311 Adrian Barbuio changed: What|Removed |Added Version|unspecified |22.12.2 Component|general |general Assignee|baloo-bugs-n...@kde.org |matthieu_gall...@yahoo.fr Product|frameworks-baloo|Elisa -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465311] New: Elisa does not locate certain songs
https://bugs.kde.org/show_bug.cgi?id=465311 Bug ID: 465311 Summary: Elisa does not locate certain songs Classification: Frameworks and Libraries Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: lz4_8...@protonmail.com Target Milestone: --- Created attachment 155954 --> https://bugs.kde.org/attachment.cgi?id=155954&action=edit a screenshot of the settings and missing songs SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install elisa (official repository or flatpak) 2. save music (on a separate hard drive) 3. link to music folder OBSERVED RESULT Some songs are found but not others. The details are there in the song for the player to pick up, but they are not there in the player EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 460066] Discover crashed when closing just after an update
https://bugs.kde.org/show_bug.cgi?id=460066 --- Comment #9 from Adrian R --- (In reply to Nate Graham from comment #8) > That probably means you don't have debug symbols installed. That stack trace isn't enough? Seems like an uphill fight just to do the right thing and report a bug. :/ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 460066] Discover crashed when closing just after an update
https://bugs.kde.org/show_bug.cgi?id=460066 --- Comment #7 from Adrian --- (In reply to Nate Graham from comment #6) > Adrian, your backtrace looks different so I think it's a different crash. If > you can truly reproduce it 100%, please do file a new bug report for it. > Thanks! I've tired to use the "Report Bug" button on the "Discover -- The KDE Crash Handler" window, but it keeps telling me "This report does not contain enough information for the developers, so the automated bug reporting process is not enabled for this crash". I select 'Yes'/'Every time'/'What I was doing when the application "Discover" crashed' options of "What do you know about the crash?". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 460066] Discover crashed when closing just after an update
https://bugs.kde.org/show_bug.cgi?id=460066 Adrian changed: What|Removed |Added CC||k...@romanelli.info --- Comment #5 from Adrian --- (In reply to Rodrigo Pedra Brum from comment #4) > Nate, > > I tried twice this week and I can't replicate it anymore. I will close the > bug for now, and if I can replicate it I will reopen it again. > > Thanks! For what its worth, I can recreate it every time. It only happens when it completes an actual update. Its been happening for a couple of months now. Here's the KDE Crash Handler output from the latest crash ... Executable: plasma-discover PID: 5434 Signal: Segmentation fault (11) Time: 11/7/22 7:02:42 PM PST Application: plasma-discover (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-52-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.5 [KCrashBackend] Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f0936e43275 in QQuickWindow::mouseGrabberItem() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f0936e45aef in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f0936e2d195 in QQuickItemPrivate::derefWindow() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f0936e2dd58 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f0936e2e03c in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f0936faf859 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f09352a2a6e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f09352ad924 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0936faf859 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f09352a2a6e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f09352ad924 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0936fb0789 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f09352a2a6e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f09352ad924 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f08f827b609 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #19 0x7f0935cac463 in QV4::MemoryManager::sweep(bool, void (*)(char const*)) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f0935cac5a9 in QV4::MemoryManager::~MemoryManager() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f0935d290e4 in QV4::ExecutionEngine::~ExecutionEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f0935d137e2 in QJSEngine::~QJSEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f0935ef1a3d in QQmlApplicationEngine::~QQmlApplicationEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x556ec8d19411 in ?? () #25 0x556ec8d1943d in ?? () #26 0x7f09352a51c3 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f0936423713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f0935277e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f093527af27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f093527ed0c in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x556ec8d17838 in ?? () #32 0x7f0934b95d90 in __libc_start_call_main (main=main@entry=0x556ec8d16f40, argc=argc@entry=3, argv=argv@entry=0x7ffe6faa6ef8) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7f0934b95e40 in __libc_start_main_impl (main=0x556ec8d16f40, argc=3, argv=0x7ffe6faa6ef8, init=, fini=, rtld_fini=, stack_end=0x7ffe6faa6ee8) at ../csu/libc-start.c:392 #34 0x556ec8d18275 in ?? () [Inferior 1 (process 5434) detached] -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 461407] New: Crash on opening optical trains dialog
https://bugs.kde.org/show_bug.cgi?id=461407 Bug ID: 461407 Summary: Crash on opening optical trains dialog Classification: Applications Product: kstars Version: 3.6.1 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY Raspberry Pi 4 running 64-bit Debian 11, indi compiled using the astro-soft-stable script. With a clean install, when clicking on the + icon to set up an optical train for the first time, kstars segfaults STEPS TO REPRODUCE 1. Install kstar-3.6.1 on a clean raspberry pi 64bit Debian Bullseye installation, via the astro-soft-stable script. 2. Set up the following EKOS profile: eqmod mount, Touptek CCD, ZWO CCD, ASI filterwheel, MyFocuserPro2 focuser. (I don't know if it's specific to part of that configuration, this is just what I did.) 3. Start EKOS and connect to equipment profile. 4. Switch to imaging tab. Press the pencil button next to the optical trains dropdown. 5. At this point there are no optical trains shown in the optical trains dialog. Click the + button to add one. OBSERVED RESULT 6. Segfault. EXPECTED RESULT Open UI to configure an optical train. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: - KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Running on xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 458772] Discover crash report
https://bugs.kde.org/show_bug.cgi?id=458772 Adrian Coanda changed: What|Removed |Added Ever confirmed|0 |1 CC||extremeadi...@gmail.com Status|RESOLVED|REOPENED Resolution|DOWNSTREAM |--- Keywords|drkonqi |reproducible --- Comment #2 from Adrian Coanda --- (In reply to Nicolas Fella from comment #1) > It appears that you are using Kali Linux, which is not appropriate for > general use, and you will find a million and a half other little weirdnesses > like this, because running everything as root is explicitly unsupported and > never recommended. I would encourage you to re-install your system with a > more appropriate general-purpose Linux distro, such as one of the ones you > can see at https://kde.org/distributions. > > > Thanks for understanding! y am aware that y am using kali wich is similar debian based distro but the report was generated in user mode and not the root account y am using this distro because it allows me do read write Mobile devices Firmwares Parameters to train optimise kernels, is a tool is required sudo like reading firmware parameters and settings and honestly programs should work same regardless of the user that is accesing some functions pf the program and nowadays operating system can support multi user and multi interface discover srashed when you enable automatic Firmware update and for that operation it needs root to acces the firmware spec so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382604] Plasma must be restarted to for cursor size changes to take effect for the desktop and empty areas of the panel
https://bugs.kde.org/show_bug.cgi?id=382604 Adrian changed: What|Removed |Added CC||kukub...@go2.pl --- Comment #29 from Adrian --- For some time (2 weeks maybe, I'm not sure) I face similar issue. Sometimes displayed cursor is not the one I set in system settings. It happens in a few places: - when I put mouse cursor on screen edge that has action defined, - when I right click in Firefox, - when I middle click in Firefox, those are just from the top of my head. It is not related to cursor theme change. I tried to change theme and it is stable until next start of plasma. After restart problem returns. It happens for both KDE-installed themes and 3rd parties. Workaround from https://wiki.archlinux.org/index.php/KDE#Plasma_cursor_sometimes_shown_incorrectly helps. If you consider this a separate bug just let me know and I'll create a new report. I use fully updated Arch Linux which means plasma 5.25.5. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 459168] New: Cannot Add Video or Audio to project bin depending on startup
https://bugs.kde.org/show_bug.cgi?id=459168 Bug ID: 459168 Summary: Cannot Add Video or Audio to project bin depending on startup Product: kdenlive Version: 22.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: lz4_8...@protonmail.com Target Milestone: --- Created attachment 152080 --> https://bugs.kde.org/attachment.cgi?id=152080&action=edit Terminal Output of Kdenlive upon running from terminal SUMMARY *** I installed Kdenlive yesterday on an up to date Manjaro installation. On Kdenlive startup from the icon, any and all additions to the project bin result in a 'could not open' message appearing below the project bin. Curiously, if I run kdenlive from the terminal, I see a long collection of error messages and missing plugins (attached) but i can upload video. I cannot, however, upload audio. I am met with an empty 'transcode clip' dialogue box and the audio clip is absent *** STEPS TO REPRODUCE 1. Open kdenlive 2. drag video/audio (mp3,flac, webm and mp4 file formats tested) 3. For audio (having run kdenlive from the terminal), press the transcode button. OBSERVED RESULT no audio or video is deposited into the project bin EXPECTED RESULT video/audio files are deposited into the project bin SOFTWARE/OS VERSIONS Kdenlive: 22.08.0 Package Type: Unknown/Default MLT: 7.8.0 Qt: 5.15.5 (built against 5.15.5 x86_64-little_endian-lp64) Frameworks: 5.97.0 System: Manjaro Linux Kernel: linux 5.15.65-1-MANJARO CPU: x86_64 Windowing System: xcb Movit (GPU): disabled Track Compositing: frei0r.cairoblend ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458272] New: Dolphin says file assoc with link does not exist but it does
https://bugs.kde.org/show_bug.cgi?id=458272 Bug ID: 458272 Summary: Dolphin says file assoc with link does not exist but it does Product: dolphin Version: 22.04.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: k...@romanelli.info CC: kfm-de...@kde.org Target Milestone: --- Created attachment 151564 --> https://bugs.kde.org/attachment.cgi?id=151564&action=edit Screenshot showing the error and the versioning info of KDE SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Create a link for a file. In my case the link was on the desktop. 2. Right-click on the link to open the Properties view 3. On the 'General' tab, the "Points to:" section, click on the ">-" button to the right of the file name that the link represents. 4. The Properties view expands displaying an error message stating the file 'does not exist' 5. Use Dolphin to confirm that the file does actually exist. OBSERVED RESULT Dolphin reports the files does not exist but it does indeed exist. The link works normally and opens the file. EXPECTED RESULT Dolphin should show not notify the user that the file does not exist. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I wasn't sure how to classify this bug, when selecting the "Component" and "Severity" options. You should review those choices. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 456560] KDE Crashes when changing the theme in system settings
https://bugs.kde.org/show_bug.cgi?id=456560 --- Comment #3 from Adrian Constantin --- Created attachment 151156 --> https://bugs.kde.org/attachment.cgi?id=151156&action=edit New crash information added by DrKonqi plasma-discover (5.25.4) using Qt 5.15.5 To me this Discover has crashed when I installed WhatsApp client for Linux flatpack, at the end of the installation. I do have a custom theme selected (Harmony-Global, that I very much like). The newly installed WhatsApp application appears to work properly, so maybe the installation completed successfully before Discover crashed. -- Backtrace (Reduced): #4 0x7fda1fb1c3ab in QTextStream::operator<<(char) () from /lib64/libQt5Core.so.5 [...] #8 0x7fda219b639e in Transaction::statusChanged(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so #9 0x7fda219bca8c in Transaction::setStatus(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so #10 0x7fda1fab5760 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7fda20cda41e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 456560] KDE Crashes when changing the theme in system settings
https://bugs.kde.org/show_bug.cgi?id=456560 Adrian Constantin changed: What|Removed |Added CC||adrian.vasile.constantin@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Dominik Adrian Grzywak changed: What|Removed |Added CC||starte...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 --- Comment #93 from Adrian R --- (In reply to Adrian R from comment #91) > Wanted to add my thoughts, as my hunch is that KDE is getting confused > between the primary and secondary monitors at login. > > TL;DR: Two monitor setup. Left monitor plugged into first port which is > DisplayPort, right monitor plugged into HDMI port. RX 580 card considers > DisplayPort-connected monitor as the 'primary' by default. I've override > 'primary' monitor in KDE via the KDE settings. When logging in the mouse > pointer is on the left/HDMI/new-primary monitor, the vertical typing cursor > is on the left/HDML/new-primary monitor, but the character dots to show > typing is occurring displays on the > right/DisplayPort/overriddden-not-primary-now monitor as typing is done. > Wallpaper/settings lost on right/DisplayPort/overridden-not-primary-now > monitor. On my previous comment, in the TLDR section, I reversed which monitor is plugged into which port. The left monitor is HDMI, and the right is DisplayPort. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 --- Comment #92 from Adrian R --- On my previous comment, in the TLDR section, I reversed which monitor is plugged into which port. The left monitor is HDMI, and the right is DisplayPort. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Adrian R changed: What|Removed |Added CC||k...@romanelli.info --- Comment #91 from Adrian R --- Wanted to add my thoughts, as my hunch is that KDE is getting confused between the primary and secondary monitors at login. TL;DR: Two monitor setup. Left monitor plugged into first port which is DisplayPort, right monitor plugged into HDMI port. RX 580 card considers DisplayPort-connected monitor as the 'primary' by default. I've override 'primary' monitor in KDE via the KDE settings. When logging in the mouse pointer is on the left/HDMI/new-primary monitor, the vertical typing cursor is on the left/HDML/new-primary monitor, but the character dots to show typing is occurring displays on the right/DisplayPort/overriddden-not-primary-now monitor as typing is done. Wallpaper/settings lost on right/DisplayPort/overridden-not-primary-now monitor. Full description ... I have an AMD RX 580 video card, with the left monitor plugged into the HDMI port, and the right monitor plugged into the DisplayPort port. Both monitors are the same make/model, identify as "Sceptre Tech Inc E246W-1080p 16843009". I've noticed that the problem triggers often for me when I'm logging in. Specifically, on my dual monitor setup, the vertical typing cursor is on the HDMI/left monitor, but when I start typing the circle/dots that represent characters being typed is display on the DisplayPort/right monitor, even though the vertical typing cursor continues to show on the first monitor. On boot up my PC initially wants to treat the DisplayPort/right monitor as the primary, but I've overrode KDE (via right click on 'configure desktop' settings) to have the HDMI/left monitor set as my primary, and have the KDE taskbar display on it. I can *almost* recreate this bug at will. It does happen about 50-75% of the time. The other times when things work correctly, when I login I type and character typing dots appear on the left/HDMI monitor, which is the overridden 'primary' monitor. One time, and one time only, I lost the wallpaper on the HDMI/left monitor as well as the DisplayPort/right monitor. All other times it was just the DisplayPort/right monitor that loses the wallpaper settings. Maybe there's some race condition with KDE in telling itself which is the primary monitor, when the (from hardware point-of-view) default monitor isn't the primary? Because of this confusion settings files are not read/written correctly? Feel free to contact me if you need more info or any testing done. --- Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-41-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441907] Yakuake always opens on the left screen in case of display scaling
https://bugs.kde.org/show_bug.cgi?id=441907 Adrian Kalla changed: What|Removed |Added Summary|Yakuake always opens on the |Yakuake always opens on the |left screen |left screen in case of ||display scaling -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441907] Yakuake always opens on the left screen
https://bugs.kde.org/show_bug.cgi?id=441907 Adrian Kalla changed: What|Removed |Added CC||adrian.ka...@gmail.com --- Comment #2 from Adrian Kalla --- I can reproduce exactly the same issue - also with scaling set to 150%. With scaling set to 100% it works as expected. I have 3 displays. The behavior on the first and the second is exactly as of the reporters. When I try to open the terminal on the third, it opens on the middle of the second screen. Tried upgrading to 22.04.2, but no change in behavior. SOFTWARE/OS VERSIONS Yakuake: 22.04.2 Linux: 5.13.0 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Graphics Platform: X11 Graphics Driver: Nvidia 510.73.05 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 455784] New: Support for Pressure Stall Information from /proc in ksysguardd
https://bugs.kde.org/show_bug.cgi?id=455784 Bug ID: 455784 Summary: Support for Pressure Stall Information from /proc in ksysguardd Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ksysguardd Assignee: ksysguard-b...@kde.org Reporter: rubberduc...@icloud.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY With the new Pressure Stall Information (https://lwn.net/Articles/753840/) added as of kernel 5.X or so, there are now /proc/pressure/[memory, cpu, io] files available that provide information on how much "pressure" different resources (CPU, memory, IO) are under. This is similar to how the MacOS activity monitor app displays memory data to users by default and may be desirable for linux users to be able to have this information available in their ksysguard. To paraphrase the lined article, the data provided in this proc file essentially shows two lines. "Some", which indicates "the time in which at least one task is stalled on the resource." and "full", which "indicates time in which *nobody* is using the [resource] productively due to pressure". There are some nuances for the different resources but thats the TL;DR. Each of these datapoints is provided as rolling averages over a few time periods (10 sec, 60 sec, 300 sec) as well as a total count). I took a look at the source code for the "memory/physical/used" sensor, which seems fundamentally similar in that it, unlike most other sensors, also seems to get its data from a file in /proc, rather than from lm-sensors or another physical sensor. heres the section of the source that led me to this conclusion: https://invent.kde.org/plasma/ksysguard/-/blob/master/ksysguardd/Linux/Memory.c#L118 I would like to submit a patch that makes this data available as sensors in ksysguardd (and thus allow them to appear in the ksysguard and Plasma System Monitor apps). My current plan is to mirror the existing implementation from the file linked above and tweak it to parse the information from the various /proc/pressure files instead of /proc/meminfo. Would a patch like this be something that would be useful to the ksysguardd project? Am i misunderstanding anything about how to go about making this change or how users of ksysguard/Plasma System Monitor could take advantage of this? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 455330] Speakers and Applet no longer detects custom config (sink / input) from Pipewire or Wireplumber
https://bugs.kde.org/show_bug.cgi?id=455330 Adrian Maulani changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #2 from Adrian Maulani --- (In reply to Nate Graham from comment #1) > Does the problem go away if you right-click on the Audio Volume icon, select > "Configure Audio Volume…" and check the checkbark saying "Show Virtual > Devices"? If so, I'll mark this as a duplicate of Bug 455283 and we'll > continue the conversation there. yes, silly me for not knowing. thanks *** This bug has been marked as a duplicate of bug 455283 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 455283] plasma-pa 5.25.0 applet hides virtual devices by default
https://bugs.kde.org/show_bug.cgi?id=455283 Adrian Maulani changed: What|Removed |Added CC||takiya2888...@gmail.com --- Comment #2 from Adrian Maulani --- *** Bug 455330 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 455330] New: Speakers and Applet no longer detects custom config (sink / input) from Pipewire or Wireplumber
https://bugs.kde.org/show_bug.cgi?id=455330 Bug ID: 455330 Summary: Speakers and Applet no longer detects custom config (sink / input) from Pipewire or Wireplumber Product: plasma-pa Version: 5.25.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: takiya2888...@gmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 149745 --> https://bugs.kde.org/attachment.cgi?id=149745&action=edit Sorry for my bad edit. But here you can see clearly, on applet it won't show Wireplumber's config, but system itself is able to read and use it. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Upgrade to 5.25.0 and Pipewire 0.3.52 2. Go to Plasma Audio Applet, no audio selected OBSERVED RESULT No Custom Config detected in plasma audio applet EXPECTED RESULT should've appear there, because it appeared on previous version. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.17.0-14.1-liquorix-amd64 / 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION First of all i wasn't sure if this was Pipewire or Wireplumber's problem, but it seems the config are working just fine, also apps are able to listen to the inputs. The only problem is there's no more custom audio devices shown on the plasma applet, but it is shown correctly on System preferences -> Audio. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 454227] kstars fails to start from current ppa packages, possible clash with upgraded libstellarsolver
https://bugs.kde.org/show_bug.cgi?id=454227 Adrian Knagg-Baugh changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Adrian Knagg-Baugh --- Packages now updated, are consistent with each other and work fine. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 454278] Wish: capture process efficiency improvements
https://bugs.kde.org/show_bug.cgi?id=454278 Adrian Knagg-Baugh changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Adrian Knagg-Baugh --- Thanks Jasem, I hadn't spotted that but it seems to be what I was looking for. I've closed this as NOTABUG. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 454278] New: Wish: capture process efficiency improvements
https://bugs.kde.org/show_bug.cgi?id=454278 Bug ID: 454278 Summary: Wish: capture process efficiency improvements Product: kstars Version: 3.5.8 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- When running a capture sequence events appear to happen in the following order: 1. Camera completes image capture. 2. Camera downloads image to computer. 3. Image is converted into fits format, WCS data added etc. 4. Preview of image displays in fitsviewer. 5. Dithering starts. 6. Dithering completes and settle time occurs. 7. Guiding resumes. 8. ekos commands next exposure to start. The clock time between 1 and 7 can be rather significant: on a Raspberry Pi 4 with a Canon EOS 600D (connects via USB2) it takes around 25s. The process doesn't seem to be optimised properly because there shouldn't be any need for the image-related activity and the dithering-related activity to be serial activities, they should be carried out in parallel. It would save a significant amount of idle time (and therefore allow more time imaging) if the process began dithering as soon as possible after image completion, especially on slower hardware and / or with USB2-connected cameras. The sequence of events would then be: 1. Camera completes image capture. 2. Camera starts downloads image to computer. 3. Dithering starts. 4. Dithering completes and settle time occurs. 5. Guiding resumes. 6. ekos commands next exposure to start. (at some point) Download completes. (following) Image is processed into fits format. (following) Preview of image displays in fitsviewer. I suppose if considering a sequence of very short exposures like bias you might want to ensure the next capture didn't start before the previous image had been completely dealt with, but even so the sequence could be: 1. Camera completes image capture. 2. Camera starts downloads image to computer. 3a. Dithering starts. 4a. Dithering completes and settle time occurs. 5a. Guiding resumes. 3b. Download completes. 4b. Image is processed into fits format. 5b. Preview of image displays in fitsviewer. 6. (requires 5a and 5b to be complete) ekos commands next exposure to start. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 454227] New: kstars fails to start from current ppa packages, possible clash with upgraded libstellarsolver
https://bugs.kde.org/show_bug.cgi?id=454227 Bug ID: 454227 Summary: kstars fails to start from current ppa packages, possible clash with upgraded libstellarsolver Product: kstars Version: 3.5.8 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY *** Kstars fails to start and shows symbol error following ppa pakage updates to libstellarsolver, indi-bin, libindi-data *** STEPS TO REPRODUCE 1. Run kstars from command line OBSERVED RESULT adrian@arcturus:~$ kstars kstars: symbol lookup error: kstars: undefined symbol: _ZN7SSolver10Parameters14convertFromMapE4QMapI7QString8QVariantE EXPECTED RESULT kstars should start up correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Software package versions are as follows: root@arcturus:/home/adrian# apt policy libstellarsolver libstellarsolver: Installed: 2.3+202205220547~ubuntu22.04.1 Candidate: 2.3+202205220547~ubuntu22.04.1 Version table: *** 2.3+202205220547~ubuntu22.04.1 500 500 https://ppa.launchpadcontent.net/mutlaqja/ppa/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status root@arcturus:/home/adrian# apt policy kstars-bleeding kstars-bleeding: Installed: 6:3.5.8+202203242252~ubuntu22.04.1 Candidate: 6:3.5.8+202203242252~ubuntu22.04.1 Version table: *** 6:3.5.8+202203242252~ubuntu22.04.1 500 500 https://ppa.launchpadcontent.net/mutlaqja/ppa/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status root@arcturus:/home/adrian# apt policy indi-bin indi-bin: Installed: 1.9.6+202205211403~ubuntu22.04.1 Candidate: 1.9.6+202205211403~ubuntu22.04.1 Version table: *** 1.9.6+202205211403~ubuntu22.04.1 500 500 https://ppa.launchpadcontent.net/mutlaqja/ppa/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1.9.4+dfsg-1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages root@arcturus:/home/adrian# apt policy libindi-data libindi-data: Installed: 1.9.6+202205211403~ubuntu22.04.1 Candidate: 1.9.6+202205211403~ubuntu22.04.1 Version table: *** 1.9.6+202205211403~ubuntu22.04.1 500 500 https://ppa.launchpadcontent.net/mutlaqja/ppa/ubuntu jammy/main amd64 Packages 500 https://ppa.launchpadcontent.net/mutlaqja/ppa/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 1.9.4+dfsg-1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe i386 Packages Should there be a package upgrade to kstars to match the upgrade to libstellarsolver? Nothing is showing up in apt update... -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452795] Wish: ability to manually override autofocus algorithm
https://bugs.kde.org/show_bug.cgi?id=452795 --- Comment #2 from Adrian Knagg-Baugh --- Autofocus usually works for me, but sometimes it just hunts forever, mostly if I start a little off the true position and the initial step goes far enough away from critical focus that the hfr detector seems to fail and reports a wrong hfr of 1.0; as it moves in toward the correct position the curve begins to form but the best fit is thrown off by the first one or two erroneous results. Also sometimes it feels like it can get thrown off for no reason - maybe thin cloud or wind shake, I don't know. If it does this overnight then tough luck I guess, but it would be nice to have a manual override so that if I happen to still be awake (say at the start of a job) I could intervene more easily if autofocus fails. Just an option for those times when the human knows better than the computer. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452795] New: Wish: ability to manually override autofocus algorithm
https://bugs.kde.org/show_bug.cgi?id=452795 Bug ID: 452795 Summary: Wish: ability to manually override autofocus algorithm Product: kstars Version: 3.5.8 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY *** The ekos autofocus routine sometimes struggles: it may include points far enough from critical focus that the HFR calculation goes wrong and throws off the best fit curve,. Also atmospheric conditions like wisps of cloud can sometimes interfere with the success of the routine. Often in cases where the algorithm struggles it's perfectly obvious after the first pass to a human operator where the true minimum of the focal curve is, or you know that it was perfectly well focused for the last sub but it's just doing a time-based focus check and getting confused. It would be fantastic if the ekos autofocus tab had a simple means of selecting the critical focus step, either by clicking on the curve or by entering the step number in a text entry box, and a button to override the algorithm, in effect to say "I'm giving you the true focal position, go to that position immediately and mark the autofocus job as complete". On marking focus as complete in this way a scheduled job would then move on to its next step. *** -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452794] New: Saving a schedule does not save the associated fits file
https://bugs.kde.org/show_bug.cgi?id=452794 Bug ID: 452794 Summary: Saving a schedule does not save the associated fits file Product: kstars Version: 3.5.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY *** The scheduling tool allows for using a fits file to get an accurate goto reference. When loading a schedule job that had a fits file specified in the config, the fits file location is not restored. *** STEPS TO REPRODUCE 1. Create new schedule item choosing object, sequence file etc. 2. Specify a fits file using the file selector. 3. Save schedule job. 4. Clear the schedule. 5. Load the saved schedule job. 6. Schedule is listed but no longer has the reference fits file listed. OBSERVED RESULT After reloading, the reference fits file is not shown in the job details. EXPECTED RESULT The reference fits file to be used for the job should be shown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.10 KDE Plasma Version: 5.86 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452793] New: Wish: the ability to edit schedules / sequences while one is running
https://bugs.kde.org/show_bug.cgi?id=452793 Bug ID: 452793 Summary: Wish: the ability to edit schedules / sequences while one is running Product: kstars Version: 3.5.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- When a sequence or a schedule is running, kstars locks out big chunks of the UI until the sequence or schedule stops. This limits usability. The overall wishlist item is somewhat broad so I've tried to break it down into discrete tasks: 1. While a schedule is running, be able to add jobs to the schedule list. If have a few items in a running schedule but decide halfway through the night that I'd like to add another target to image when the scheduler can fit it in, I can't do it without stopping the scheduler, adding the job and restarting the scheduler. This incurs all the overhead of a restart - slew, refocus, plate solve, restart guiding - for no good reason. It would be great if I could drop a new job into the running scheduler. 2. Very similar: be able to edit jobs in a running scheduler. If I decide I don't want job #2 to require focus because job #1 is already focused and theair temperature is dead stable, it would be nice to just be able to turn it off rather than stopping the scheduler, changing the job, restarting and going through all the overhead. 3. Similar, but for sequences. If I'm running a sequence of 36 x 5 minute subs, it might happen that I decide I want to extend it to 48 subs. It would be nice to be able to update the running sequence to extend it rather than having to stop it, add another set of 12 subs and restart the sequence. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 --- Comment #11 from Adrian W. --- Created attachment 147561 --> https://bugs.kde.org/attachment.cgi?id=147561&action=edit Doesn't open as markdown document -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 --- Comment #10 from Adrian W. --- Created attachment 147560 --> https://bugs.kde.org/attachment.cgi?id=147560&action=edit Opens as markdown document -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 Adrian W. changed: What|Removed |Added CC||generic@nonimportant.email Status|RESOLVED|REOPENED Resolution|FIXED |--- Version|21.08.3 |21.12.3 Platform|Other |Manjaro --- Comment #9 from Adrian W. --- I have a lot of markdown documents opening with the Txt backend. Figured it out eventually, it seems to me like it's a bug. Attached 2 files, one opens with the Txt backend and the other with the Markdown backend. - Both are 'mime-type: text/plain' - Both show in Dolphin as 'Type: Markdown document' (*.md) But Dolphin properties show different recognized content: 'markdown.md' shows correctly 'Content: plain text document' 'notmarkdown.md' shows incorrectly 'Content: MATLAB file' The difference that triggers the content to be misdiagnosed is how the first line starts. Remove the first line from 'markdown.md' and the content changes to MATLAB document, consequently opening the file in Okular with the Txt backend. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 449999] fetching includes breaks on strange characters
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #1 from Adrian Sevcenco --- actually, removing the project to clean up the parsing with KDEV_CLANG_DISPLAY_ARGS=1 i get this for the application that i actually work on: Invocation: clang -ferror-limit=100 -fspell-checking -Wunused-parameter -Wunreachable-code -Wall -std=c++11 -nostdinc -nostdinc++ -xc++ -isystem/home/physics-tools/ROOT/v6-26-00-patches/include -isystem/usr/include/c++/11 -isystem/usr/include/c++/11/x86_64-redhat-linux -isystem/usr/include/c++/11/backward -isystem/usr/local/include -isystem/usr/include -isystem /usr/lib64/llvm12/lib/clang/12.0.1/include -imacros /home/adrian/tmp/kdevelop.AjWwlc /home.hdd/adrian/work/AO2Dproto/ao2d_process.C that -std=c++11 is just wrong, so why is there, and how can it be customized? Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 449999] New: fetching includes breaks on strange characters
https://bugs.kde.org/show_bug.cgi?id=44
Bug ID: 44
Summary: fetching includes breaks on strange characters
Product: kdevelop
Version: 5.6.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: CPP (old)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: adrian@gmail.com
Target Milestone: ---
While trying to solve the problem of having a parsing report of "No type named
'string_view' in namespace 'std' "
and setting in the project configuration -> Laguage support -> C/C++ parser c++
profile to c++17 and Compiler for path = GCC
i started the kdevelop in the terminal and i seen this:
```
python code checker error: "The `pycodestyle` (previously `pep8`) module is not
installed."
kdevelop.plugins.definesandincludes: error while fetching includes for the
compiler: "gcc" "Using built-in
specs.\nCOLLECT_GCC=/usr/bin/gcc\nOFFLOAD_TARGET_NAMES=nvptx-none\nOFFLOAD_TARGET_DEFAULT=1\nTarget:
x86_64-redhat-linux\nConfigured with: ../configure --enable-bootstrap
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array
--with-isl=/builddir/build/BUILD/gcc-11.2.1-20211203/obj-x86_64-redhat-linux/isl-install
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --enable-cet --with-tune=generic
--with-arch_32=i686 --build=x86_64-redhat-linux
--with-build-config=bootstrap-lto --enable-link-serialization=1\nThread model:
posix\nSupported LTO compression algorithms: zlib zstd\ngcc version 11.2.1
20211203 (Red Hat 11.2.1-7) (GCC) \nCOLLECT_GCC_OPTIONS='-std=c99' '-E' '-v'
'-mtune=generic' '-march=x86-64'\n cc1obj -E -quiet -v - -mtune=generic
-march=x86-64 -std=c99 -dumpbase -\ngcc: fatal error: cannot execute
\xE2\x80\x98""cc1obj\xE2\x80\x99: execvp: No such file or
directory\ncompilation terminated.\n"
kdevelop.plugins.definesandincludes: error while fetching defines for the
compiler: "gcc" ("-xobjective-c", "-std=c99", "-dM", "-E", "-") "gcc: fatal
error: cannot execute \xE2\x80\x98""cc1obj\xE2\x80\x99: execvp: No such file or
directory\ncompilation terminated.\n"
kdevelop.plugins.clang: Unhandled type: ExtVector float
__attribute__((ext_vector_type(4)))
kdevelop.plugins.clang: Unhandled type: ExtVector float
__attribute__((ext_vector_type(4)))
```
beside the fact that pycode is installed, the gcc error is repeated many times.
even more puzzling is that
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto
why in the world is that whole list there?
EXPECTED RESULT
no breakage
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 35
(available in About System)
I do not have a About system in this kdevelop but it seem that i have:
KDE Frameworks Version 5.90.0
Qt Version 5.15.2 (built against 5.15.2)
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 447784] New: Add support for copying unsupported/unknown partitions
https://bugs.kde.org/show_bug.cgi?id=447784 Bug ID: 447784 Summary: Add support for copying unsupported/unknown partitions Product: partitionmanager Version: 21.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: starte...@gmail.com Target Milestone: --- Created attachment 145013 --> https://bugs.kde.org/attachment.cgi?id=145013&action=edit Screenshot of the context menu SUMMARY Currently Partition Manager doesn't support copying for unknown partitions. Gparted supports it. STEPS TO REPRODUCE 1. Have an unsupported/unknown partition (for example, created with gdisk); 2. Right-click on it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 3.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 447762] No support for moving unsupported/unknown partitions with non-integer sizes
https://bugs.kde.org/show_bug.cgi?id=447762 --- Comment #2 from Dominik Adrian Grzywak --- (In reply to Andrius Štikonas from comment #1) > I guess we could try to exclude unknown partitions from partition alignment. > > In other cases (when file system is known) it is resized because that's what > you enabled in your settings (partition alignment is a setting there but on > by default). When I uncheck the partition alignment for unknown partition, it still tries to shrink it. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 447762] New: No support for moving unsupported/unknown partitions with non-integer sizes
https://bugs.kde.org/show_bug.cgi?id=447762 Bug ID: 447762 Summary: No support for moving unsupported/unknown partitions with non-integer sizes Product: partitionmanager Version: 21.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: starte...@gmail.com Target Milestone: --- SUMMARY When I choose to move an "unknown" partition with non-integer size (like 16.10 MiB (32968 sectors) or 21.37 MiB (43769 sectors)), Partition Manager decides to resize the partition to the integer size, and when I continue the operation – it fails. Moving an unsupported partition with integer size doesn't fail, and succeeds. I also noticed that the integer size enforce applies to the supported partitions as well. STEPS TO REPRODUCE 1. Have an unsupported/unknown partition (for example, created with gdisk); 2. Try to move it; 3. PM should decide to resize it – continue the operation and see what happens. OBSERVED RESULT - Integer partition size enforce affects the unsupported partitions as well. - PM resizes the partition before moving it. - Because PM can't resize the partition - it fails. EXPECTED RESULT PM should just move the partition, and not try to resize it if it cannot be resized (even better - should let the user decide on it, when the partition is supported). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Screenshots: https://imgur.com/a/4pz7VTR -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444896] FR: Search using wildcards does not work
https://bugs.kde.org/show_bug.cgi?id=444896 --- Comment #4 from Adrian Fluturel --- > Will flag as confirmed. Maybe someone else will come in with an "It's > intentional" Thank you. I talked for a bit on #kde-devel and people seem to think it's a wanted feature and it is wanted, and some thought baloo supported that already. I don't know much about dolphin or about kde in general, I'm just trying to get started and fix something, and this started like a pretty simple problem in theory but I am now getting in a rabbit hole of sorts that I don't know how to navigate -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444896] FR: Search using wildcards does not work
https://bugs.kde.org/show_bug.cgi?id=444896 --- Comment #2 from Adrian Fluturel --- (In reply to tagwerk19 from comment #1) > (In reply to Adrian Fluturel from comment #0) > > The latter is the case here, baloo does not return the file requested with > > "*_033.t*" as a search term. > Sorry, this likely doesn't help you but you may need a different search tool > for wildcard searches... > > Baloo is tuned to provide fast results. It builds an index of things you > _might_ search for and does lookups in that index as you type your search. > That cannot really work for arbitrary wildcard searches. So what is a viable solution here? Add this in kio-filenamesearch? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444896] New: FR: Search using wildcards does not work
https://bugs.kde.org/show_bug.cgi?id=444896 Bug ID: 444896 Summary: FR: Search using wildcards does not work Product: dolphin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: fluturel.adr...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When baloo is enabled, it ignores wildcards and searches anyway, but just in the areas that it indexes, as it should. But I should also be able to use wildcards to search for anything, which right now does not happen. When baloo is disabled, dolphin uses regular expressions, which do not accept wildcard expressions like "*.jpg" STEPS TO REPRODUCE 1. Enable baloo 2. Search for something that only a wildcard would return, for example, if there is a file called "file_033.txt", searching with "*_033.t*" and successfully finding the file means wildcards are not ignored, while if it doesn't find it, it means they are ignored 3. Disable baloo and try again OBSERVED RESULT The latter is the case here, baloo does not return the file requested with "*_033.t*" as a search term. When baloo is disabled, nothing is found and in the console the message "QString::contains: invalid QRegularExpression object" is outputted. EXPECTED RESULT It should find the file using wildcards. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kernel 5.14.15-zen1-1-zen (available in About System) KDE Plasma Version: Plasma not installed KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Dolphin version 21.11.70 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444429] New: Kwin crash when opening magnet to Zoom Meet
https://bugs.kde.org/show_bug.cgi?id=29 Bug ID: 29 Summary: Kwin crash when opening magnet to Zoom Meet Product: kwin Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: takiya2888...@gmail.com Target Milestone: --- Application: kwin_x11 (5.23.1) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-38-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.1 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: i pasted the url on chrome of the meeting link. crashes when it redirects The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 1815] [New LWP 1816] [New LWP 1817] [New LWP 1818] [New LWP 1830] [New LWP 1891] [New LWP 1943] [New LWP 1944] [New LWP 1945] [New LWP 1946] [New LWP 1972] [New LWP 7079] [New LWP 8245] [New LWP 8349] [New LWP 18186] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fa10048caff in __GI___poll (fds=0x7ffd6dd141b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fa0fa74f080 (LWP 1811))] Thread 16 (Thread 0x7fa0b3fff700 (LWP 18186)): #0 0x7fa10048cbf6 in __ppoll (fds=fds@entry=0x7fa0a8001af8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fa1012c54e9 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa0a8001af8) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa0a8001af8) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7fa0a8001af8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7fa1012c6b93 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7fa10126d87b in QEventLoop::exec(QFlags) (this=this@entry=0x7fa0b3ffebc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7fa101087292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7fa0ff132549 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fa10108842c in QThreadPrivate::start(void*) (arg=0x558edb360fe0) at thread/qthread_unix.cpp:329 #10 0x7fa0feaf4609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fa100499293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fa0852c1700 (LWP 8349)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x558edb0444d0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558edb044480, cond=0x558edb0444a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558edb0444a8, mutex=0x558edb044480) at pthread_cond_wait.c:647 #3 0x7fa10108e59b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x558edb044480) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x558edb0437b8, mutex=mutex@entry=0x558edb0437b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fa0ff4acbe4 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x558edb0437a8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x558edb043710) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7fa0ff4ad059 in QSGRenderThread::run() (this=0x558edb043710) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7fa10108842c in QThreadPrivate::start(void*) (arg=0x558edb043710) at thread/qthread_unix.cpp:329 #9 0x7fa0feaf4609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fa100499293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fa0874c3700 (LWP 8245)): #0 0x7fa10048cbf6 in __ppoll (fds=fds@entry=0x7fa08d78, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fa1012c54e9 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa08d78) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa08d78) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7fa08d78, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #13 from Adrian Damian --- Thank you, Christoph! Unfortunately, the successful build of Okular (okular-21.08.2-758-macos-64-clang.dmg) fails to start on my Mac; the icon appears in the dock, but then nothing happens (there's no output on the terminal). I've noticed this happens for Kate too when running: ~/CraftRoot/build/kde/applications/kate/image-RelWithDebInfo-21.08.1/Applications/KDE/kate.app/Contents/MacOS/kate (hangs) but not when running: ~/CraftRoot/build/kde/applications/kate/archive/Applications/KDE/kate.app/Contents/MacOS/kate (starts OK, likely generated by "craft --package") Since "craft --package" seems to be fixing the RPATH of binaries, I suspect the Okular packaging script isn't fixing all of them (this is just a guess, though). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #9 from Adrian Damian --- I currently can't test Okular, since I can't get it to build: * I've tried building it twice, but it fails during `craft package` with "don't know how to handle otool -L output", and I'm not sure how to fix this. * Running ./build/kde/applications/okular/archive/Applications/KDE/okular.app/Contents/MacOS/okular fails too (no window shows), likely because `package` didn't finish (this works for Kate after `package` finishes successfully). * The Jenkins builds seem to be failing as well, but with a different(?) error: https://binary-factory.kde.org/view/MacOS/job/Okular_Release_macos/ If there's a way to run stuff from /build/kde/applications/okular/... on MacOS without `package` doing its thing, please let me know (I've struggled with finding a LD_LIBRARY_PATH equivalent on MacOS in the past, and that's what `package` seems to be doing). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 Adrian Damian changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Adrian Damian --- OK, I think I managed to narrow down the issue to these two commits. Reverting them makes the scroll stutter / stop (while still two-finger scrolling on the trackpad) go away. https://invent.kde.org/frameworks/ktexteditor/-/commit/8f8be67ccf5b151d4c6cc570229fe4fbe28e76b3 "Add basic touchscreen support" https://invent.kde.org/frameworks/ktexteditor/-/commit/aa757c80e6ce8efee288c58154998d4e8e0f0dde "Use Okular's QScroller settings" I used the latest versions of libraries: kde/applications/kate : 21.08.1 kde/frameworks/tier3/ktexteditor: 5.86.0 I don't really know how to fix this, other than reverting the two commits (but that would remove touchscreen support). Is reverting OK? For now I'll keep using my own build. --- For anyone that's affected by this, here's how to make your own build: * Install Craft: https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Mac#Installation_using_Craft (commands below assume the default ~/CraftRoot path was used). * AFAICT, this "installs" the two packages (kate uses ktexteditor) in a way that allows the sources to be edited (at ~/CraftRoot/build/$full_package_name/work/$package-$version). craft -i --no-cache kate ktexteditor * Remove the lines added in the two commits above from these files: ~/CraftRoot/build/kde/frameworks/tier3/ktexteditor/work/ktexteditor-5.86.0/src/view/kateviewinternal.cpp ~/CraftRoot/build/kde/frameworks/tier3/ktexteditor/work/ktexteditor-5.86.0/src/view/kateviewinternal.h The versions may vary, you can go to the directory that contains src/ by doing "cs ktexteditor". * Compile the changes and create an installer: craft --compile --install --qmerge ktexteditor kate && craft --package kate The path to a .dmg should be output at the end; should be something like: ~/CraftRoot/tmp/kate-21.08.1-macos-64-clang.dmg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443142] kwin crash arc
https://bugs.kde.org/show_bug.cgi?id=443142 Adrian changed: What|Removed |Added CC||zetabite.horz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443142] kwin crash arc
https://bugs.kde.org/show_bug.cgi?id=443142 --- Comment #1 from Adrian --- Addendum, i reported as general, i have no idea if there is a specific component this bug applies to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443142] New: kwin crash arc
https://bugs.kde.org/show_bug.cgi?id=443142 Bug ID: 443142 Summary: kwin crash arc Product: kwin Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: zetabite.horz...@gmail.com Target Milestone: --- SUMMARY When launching Stellaris (a Paradox Interactive game), kwin crashes, when using arc dark (from arc-gtk-theme) as window decorator, kwin crashes, tries to recover, but fails. I am not sure on how far it has to do with other settings i chose, so i report with the ones i had at the point of the crash. STEPS TO REPRODUCE 1. Set renderer to OpenGL 3 2. Set theme to arc dark 3. Set window decoration to arc dark 4. Launch Stellaris (fullscreen) 5. Observe kwin dying OBSERVED RESULT kwin crashes EXPECTED RESULT Play game normally, with arc dark as window decorator SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.8-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #6 from Adrian Damian --- Created attachment 141992 --> https://bugs.kde.org/attachment.cgi?id=141992&action=edit repro #3 log Based on some log combing, I reached this hypothesis: The scroll stutter happens because "NSEvent: type=ScrollWheel" events either stop being emmited or stop being processed, and a second-long gesture is started and keeps being updated as I keep moving my fingers on the trackpad a second time. I can't tell if the gesture starts because ScrollWheel NSEvents stop happening, OR if the gesture being started prevents the ScrollWheel events in the first place. Next things I plan to do to narrow this further (any suggestions are *highly* appreciated, since I'm really out of my depth here): * disable gestures (if possible), and see if the stutter still happens * search for Qt bugs having to do with gestures and scrolling / mouse events --- I obtained the log by starting Kate at the end of a file that's ~2k lines long, and scrolling up a few times (details on the log below). Timeline (seconds since app start, matching the log output): * ~6 start scrolling * ~6.8 scroll starts happening on screen * 6.29 .. 8.58 (repeating every ~.01s, interleaved in various ways) QGestureManager:Recognizer: ignored the event: Sending NSEvent: type=ScrollWheel Qt::ScrollUpdate Sending NSEvent: type=Gesture touchesMovedWithEvent Qt::ScrollMomentum * 8.58 these stop appearing as frequently Qt::ScrollUpdate Sending NSEvent: type=ScrollWheel Qt::ScrollMomentum type=Gesture, touchesMovedWithEvent and "ignored the event" keep appearing * ~8.6 scroll stutters visibly (it's likely at this point I've lifted my fingers off the trackpad and and put them down again to start scrolling a second time) * ~10.1 scroll stutters visibly (same as above) * 10.41 "QGestureManager:Recognizer: maybe gesture" touchesEndedWithEvent QGestureManager:Recognizer: not gesture: touchesBeganWithEvent QGestureManager:Recognizer: maybe gesture: QGestureManager::filterEventThroughContexts: started gesture was delivered and accepted by KateViewInternal(0x7f85d9be3660) * 10.46 (repeated until 13.07) "QGestureManager:Recognizer: gesture triggered" QGestureManager::deliverEvents: sending to KateViewInternal(0x7f85d9be3660) gestures: touchesMovedWithEvent QGestureManager:Recognizer: gesture triggered: QGestureManager::filterEventThroughContexts: triggered: QSet(Custom gesture(state=GestureUpdated,hotSpot=...,type=Qt::GestureType(258))) QGestureManager::deliverEvents: (every other 5-10 of the above) QGestureManager: we were asked to consume the event: (very few; ~8 during 10, 2 during 11, 1 during 12) Qt::ScrollUpdate * ~11.1 scroll stops entirely * 13:07 (first time after 10.41) Sending NSEvent: type=ScrollWheel Qt::ScrollEnd touchesEndedWithEvent --- "repro #3 timeline full" has a more complete timeline. "repro #3 log" has the full log, obtained with: QT_LOGGING_RULES="*=true" \ /Applications/kate\ 2.app/Contents/MacOS/kate ~/tomatoes.md 2>&1 \ | ts -s '%.S' \ | grep -Ev \ -e qt.widgets.painting \ -e qt.qpa.backingstore \ -e kf.texteditor \ -e kf.sonnet. \ | tee ~/Desktop/repro-3.log The Kate used was kate-21.08.1-1354-macos-64-clang.dmg (KDE Frameworks 5.86.0, Qt 5.15.2 (built against 5.15.2)). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #5 from Adrian Damian --- Created attachment 141991 --> https://bugs.kde.org/attachment.cgi?id=141991&action=edit repro #3 timeline full -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #3 from Adrian Damian --- I am able to reproduce this as well. Please let me know if you need additional data (I don't know about Qt / KDE to debug this further). IMHO, the importance should be higher; at least for me, this makes using Kate almost impossible. Thank you! --- VERSIONS macOS 10.15.7 Kate 21.08.1 (from kate-21.08.1-1348-macos-64-clang.dmg) KDE Frameworks 5.86.0 Qt 5.15.2 (built against 5.15.2) The only enabled plugins were Search & Replace and Text Filter. --- Attached "repro #2 log" and "repro #2 screen recording"; the log was generated by scrolling up and down a few times in a Kate window started with: QT_LOGGING_RULES="*=true" /Applications/kate\ 2.app/Contents/MacOS/kate CHANGES.rst 2>&1 | ts -s '%.S' > kate.log --- A version from ~March 2021 did not have this issue; unfortunately I replaced the installation and don't know the exact version. Trying to get that back, I managed to get a 21.04.3 version to build successfully with Craft; this version still has the scrolling issue: Kate 21.04.3 KDE Frameworks 5.83.0 Qt 5.15.2 (built against 5.15.2) I couldn't get a successful build with versions earlier than this. --- This Reddit thread seems to describe the same issue: https://www.reddit.com/r/kde/comments/p8byi9/kate_scrolling_problem_on_mac/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #2 from Adrian Damian --- Created attachment 141762 --> https://bugs.kde.org/attachment.cgi?id=141762&action=edit repro #2 screen recording Kate on the left, Thonny on the right (for comparison). In each of them, I scroll down 3 times and then up 3 times. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 Adrian Damian changed: What|Removed |Added CC||damian.adria...@gmail.com --- Comment #1 from Adrian Damian --- Created attachment 141761 --> https://bugs.kde.org/attachment.cgi?id=141761&action=edit repro #2 log Generated with: QT_LOGGING_RULES="*=true" /Applications/kate\ 2.app/Contents/MacOS/kate CHANGES.rst 2>&1 | ts -s '%.S' > kate.log and then scrolling for about 10 seconds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440838] qt.core.qabstractitemmodel.checkindex:error in logs
https://bugs.kde.org/show_bug.cgi?id=440838
--- Comment #1 from Adrian Sevcenco ---
oh, and doing an strace on it give me this:
sendmsg(23, {msg_name={sa_family=AF_UNIX,
sun_path="/run/systemd/journal/socket"}, msg_namelen=30,
msg_iov=[{iov_base="MESSAGE=qt.core.qabstractitemmod"..., iov_len=118},
{iov_base="\n", iov_len=1}, {iov_base="PRIORITY=4", iov_len=10},
{iov_base="\n", iov_len=1}, {iov_base="CODE_FUNC=unknown", iov_len=17},
{iov_base="\n", iov_len=1}, {iov_base="CODE_LINE=0", iov_len=11},
{iov_base="\n", iov_len=1}, {iov_base="CODE_FILE=unknown", iov_len=17},
{iov_base="\n", iov_len=1}, {iov_base="QT_CATEGORY=qt.core.qabstractite"...,
iov_len=49}, {iov_base="\n", iov_len=1}, {iov_base="SYSLOG_IDENTIFIER=",
iov_len=18}, {iov_base="plasmashell", iov_len=11}, {iov_base="\n", iov_len=1}],
msg_iovlen=15, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 258
i also tried to look over with gdb (all debug symbols installed) but i do not
know what to look for ..
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 440838] New: qt.core.qabstractitemmodel.checkindex:error in logs
https://bugs.kde.org/show_bug.cgi?id=440838 Bug ID: 440838 Summary: qt.core.qabstractitemmodel.checkindex:error in logs Product: plasmashell Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: adrian_...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I noticed that the journal is flooded with: qt.core.qabstractitemmodel.checkindex: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid (expected valid) STEPS TO REPRODUCE i have no idea how i reached this point .. in fact i do not know what to remove and where is the origin of the problem. OBSERVED RESULT flooded system journal EXPECTED RESULT not a flooded journal SOFTWARE/OS VERSIONS Fedora 34 up to date: kf5 5.83.0, qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] New: No output on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 Bug ID: 438912 Summary: No output on Wayland Product: kmag Version: 21.04.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sar...@users.sourceforge.net Reporter: starte...@gmail.com Target Milestone: --- Created attachment 139515 --> https://bugs.kde.org/attachment.cgi?id=139515&action=edit (Screenshot) KMag on Wayland has no output but a window frame SUMMARY Since no one reported this long-standing bug here yet, i will. KMag has no output while running on Wayland – in the place where the output should be, it just shows a window frame (see attachment). I also tried another modes, but they also don't work. STEPS TO REPRODUCE 1. Be running on KDE Wayland session (probably not just on KDE Plasma, but didn't test the others) 2. Run Kmag 3. Here's the bug, you can also test another modes, but they also don't work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (Unstable branch) (available in About System) KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 433027] crash while opening .ott file with preview enabled
https://bugs.kde.org/show_bug.cgi?id=433027 --- Comment #8 from Adrian Friedli --- It's the same backtrace. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 433027] crash while opening .ott file with preview enabled
https://bugs.kde.org/show_bug.cgi?id=433027 Adrian Friedli changed: What|Removed |Added Platform|Debian stable |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 433027] crash while opening .ott file with preview enabled
https://bugs.kde.org/show_bug.cgi?id=433027 Adrian Friedli changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 433027] crash while opening .ott file with preview enabled
https://bugs.kde.org/show_bug.cgi?id=433027 --- Comment #6 from Adrian Friedli --- I played around a bit and could finally reproduce the crash. I attached a file that reproducibly causes a crash. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 433027] crash while opening .ott file with preview enabled
https://bugs.kde.org/show_bug.cgi?id=433027 --- Comment #5 from Adrian Friedli --- Created attachment 136126 --> https://bugs.kde.org/attachment.cgi?id=136126&action=edit template file producing the crash -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 433458] New: Date variable in reply* template does not get localized
https://bugs.kde.org/show_bug.cgi?id=433458 Bug ID: 433458 Summary: Date variable in reply* template does not get localized Product: kmail2 Version: 5.15.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: bugs.kde@mailgurgler.com Target Milestone: --- The variable %ODATE used in a custom template of an identity does not get localized as set in KDE System Settings -> Regional Settings -> Formats. In my testing this variable always expands to English names. STEPS TO REPRODUCE 1. Go to: System Settings -> Regional Settings -> Formats ...and change the Region to a non-English locale. Log out and back in to KDE. 2. Select any message in your messagelist of KMail2 and press Reply. OBSERVED RESULT The date is localized using English names. It does not respect the settings made under "Formats", at least %DATE, %ODATE, %TIME and %OTIME. EXPECTED RESULT I would expect KMail2 respects the settings under System Settings -> Regional Settings -> Formats in custom templates. SOFTWARE/OS VERSIONS Operating System: Devuan GNU/Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-3-amd64 OS Type: 64-bit ADDITIONAL INFORMATION I did not check whether all variables are concerned. I checked with global standard templates and the per identity ones, both are affected. All Reply-Templates are affected. This Bug is related to #185446. -- You are receiving this mail because: You are watching all bug changes.
