[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #7 from Laosom --- (In reply to Nate Graham from comment #3) > All right, thanks. Not sure how to proceed here. Please see also https://bugs.kde.org/show_bug.cgi?id=471639 and https://www.youtube.com/watch?v=Ro2C9oM-j_s&t=773s at 10:30 Only manual setting works fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471639] Transition to night color starts way too early
https://bugs.kde.org/show_bug.cgi?id=471639 Laosom changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||dellfirmw...@gmail.com --- Comment #1 from Laosom --- I also experience this weird behaviour with the "sunset and sunrise at current location" setting on EndeavourOS (Plasma 5.27.6) and Debian Bookworm (Plasma 5.27.5) as well. It starts about 2 hours before and stops about 2 hours later. If I choose "sunrise and sunset at manual location" with my location coordinates , it starts and stops in the right time. I doublechecked my locale and timezone settings, it's correct. In Plasma 5.24.7 LTS Night Color works well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465620] Plasmashell crashes when adding and deleting a new default panel
https://bugs.kde.org/show_bug.cgi?id=465620 --- Comment #4 from Laosom --- (In reply to Nate Graham from comment #1) > Ah, this was fixed in 5.27. Hello Nate, Are you sure ? I cannot reproduce this crash in Kubuntu 22.04 LTS (even with Kubuntu backports installed, Plasma 5.24.7 ) neither in Opensuse Leap 15.3 (Plasma 5.24.4). So I presume it's distro related. I am also trying to contact the package builder for Debian 11. as it's not officially supported by Debian. https://www.preining.info/blog/2022/11/kde-plasma-for-debian-update-2022-11/?unapproved=150746&moderation-hash=02b5ca9fb1616545054d7385ce34ebcf#comment-150746 (In reply to Nate Graham from comment #3) > Those are both older versions of Plasma, so I don't see how they're related > to my assertion that it's fixed in 5.27, which is newer. :) If 5.27 LTS is released, 5.24 LTS is no longer supported ? I prefer LTS releases with stable user experience , but I guess there are several unfixed bugs in 5.24 LTS right ? How can I prove this is an unfixed bug ? I would like to use Plasma 5.24 with Debian 11 until Debian12 is released later this year. (hopefully with 5.27) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465620] Plasmashell crashes when adding and deleting a new default panel
https://bugs.kde.org/show_bug.cgi?id=465620 --- Comment #2 from Laosom --- (In reply to Nate Graham from comment #1) > Ah, this was fixed in 5.27. Hello Nate, Are you sure ? I cannot reproduce this crash in Kubuntu 22.04 LTS (even with Kubuntu backports installed, Plasma 5.24.7 ) neither in Opensuse Leap 15.3 (Plasma 5.24.4). So I presume it's distro related. I am also trying to contact the package builder for Debian 11. as it's not officially supported by Debian. https://www.preining.info/blog/2022/11/kde-plasma-for-debian-update-2022-11/?unapproved=150746&moderation-hash=02b5ca9fb1616545054d7385ce34ebcf#comment-150746 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465620] New: Plasmashell crashes when adding and deleting a new default panel
https://bugs.kde.org/show_bug.cgi?id=465620 Bug ID: 465620 Summary: Plasmashell crashes when adding and deleting a new default panel Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dellfirmw...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 156171 --> https://bugs.kde.org/attachment.cgi?id=156171&action=edit bug SUMMARY Plasmashell crashes when adding and deleting a new default panel *** 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 new default panel 2. New panel is created on top of screen with systray entries missing on new panel 3. Delete the new panel in edit 4. New panel is deleted and you click close on not undo window 5. Plasmashell crashes OBSERVED RESULT Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f863798836f in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f8637d7267a in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f8637d69305 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f86364f6f2f in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f863718915f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f86364cafca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f86365218e3 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f8636522164 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f86342a8e6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f86342a9118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f86342a91cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f863652251f in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f86364c998b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f86364d1c00 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x56373bc50751 in ?? () #19 0x7f8635e9ed0a in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #20 0x56373bc5087a in ?? () [Inferior 1 (process 30121) detached] EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 11 KDE Plasma Version: Plasma 5.24.7 & 5.25.5 KDE Frameworks Version: 5.100 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #36 from Laosom --- Please rewrite it in QML and restore the dropped effects. There are too many regressions in Plasma since 5.21. The best Linux desktop still, but please listen to the fans. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443555] Discover takes up to ~5 minutes to fetch updates on Arch Linux due to flatpak backend
https://bugs.kde.org/show_bug.cgi?id=443555 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #5 from Laosom --- I can also reproduce the problem in Neon , no snaps or flatpaks installed. The issue first appeared to me in Neon 5.23.1 , when tried to update to 5.23.2 As a workaround I removed snap and flatpak backends, working fine. I wonder why these sources simply cannot be disabled by untick , is it so much programing work ? Reinstalled backends, same issue. Disabled only flathub.org , fetching updates is working properly and not stucked. It's surely flatpak related. https://www.reddit.com/r/kde/comments/qdtdm3/anyone_else_having_problems_with_discover_since/ -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #22 from Laosom --- I see. I will set up a Neon VM too with the similar FS layout. Have you tested it yet ? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #20 from Laosom --- Created attachment 130120 --> https://bugs.kde.org/attachment.cgi?id=130120&action=edit kpart -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #19 from Laosom --- Created attachment 130119 --> https://bugs.kde.org/attachment.cgi?id=130119&action=edit journal -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #18 from Laosom --- journatctl shows no sign of udisks2 2020. 07. 14. 18:12 partitionmanager"Add operation: Shrink partition ‘/dev/sda6’ from 78,76 GiB to 58,90 GiB" 2020. 07. 14. 18:12 partitionmanager"Applying operations..." 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40090, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40094, resource id: 96469182, major code: 18 (ChangeProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40101, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40102, resource id: 96469182, major code: 18 (ChangeProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40103, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40104, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40105, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40106, resource id: 96469182, major code: 7 (ReparentWindow), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40107, resource id: 96469182, major code: 6 (ChangeSaveSet), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40108, resource id: 96469182, major code: 2 (ChangeWindowAttributes), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40109, resource id: 96469182, major code: 10 (UnmapWindow), minor code: 0 2020. 07. 14. 18:12 systemd Stopped File System Check on /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb. 2020. 07. 14. 18:12 systemd Starting File System Check on /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb... 2020. 07. 14. 18:12 systemd Started File System Check Daemon to report status. 2020. 07. 14. 18:12 systemd-fsckvirtualmachines: clean, 34/3866624 files, 9188632/15440384 blocks 2020. 07. 14. 18:12 systemd Started File System Check on /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb. 2020. 07. 14. 18:12 systemd Mounting /virtual_machines... 2020. 07. 14. 18:12 kernel EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) 2020. 07. 14. 18:12 systemd Mounted /virtual_machines. 2020. 07. 14. 18:12 ksystemstatscould not find subsystem "pscount" 2020. 07. 14. 18:12 plasmashell Model size of -2147483647 is less than 0 2020. 07. 14. 18:13 xdg-desktop-portal-kde xdp-kde-background: GetAppState called: no parameters -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #13 from Laosom --- Created attachment 129771 --> https://bugs.kde.org/attachment.cgi?id=129771&action=edit 20200629_2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #12 from Laosom --- Created attachment 129770 --> https://bugs.kde.org/attachment.cgi?id=129770&action=edit 20200629_1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #11 from Laosom --- As I wrote the filesystem is mounted back again after it was extended and that's the reason for the error. Of course I can run fsck if I unmount it manually before running it. I did and it works this way. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #8 from Laosom --- Created attachment 129702 --> https://bugs.kde.org/attachment.cgi?id=129702&action=edit PM error automounter -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #9 from Laosom --- I checked and find it was not running. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #6 from Laosom --- I tried on ArcoB Plasma (5.19.2) and Manjaro KDE (5.18.5) latest. It was OK. No issues, which was surprising , but delightful. The resized ext4 filesystem was not in fstab. Retested in Neon. The resized filesystem(s) were in fstab. Unmounted and commented out. Same issue again. One filesystem is used for timeshift backups the other one is for virtual machines. I wonder what Neon (ubuntu ?) is doing. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #5 from Laosom --- I tried again. Dolphin was not open. I unmounted in PM. Same behaviour. I am running KDE Neon 5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #3 from Laosom --- Hi Andrius, No matter how I unmount the FS. I did it within Partition Manager and in Dolphin too. I did not try fsck manually afterwards, as the filesystem was mounted after resize by Partition Manager. I assume it is successful if the FS is not mounted. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] New: fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 Bug ID: 423397 Summary: fsck fails after shrinking ext4 fs Product: partitionmanager Version: 4.1.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: dellfirmw...@gmail.com Target Milestone: --- SUMMARY When the user tries to resize a mounted ext4 filesystem , there is no warning to unmount it first, the sliders does not move to shrink similar to gparted. The user then unmounts the ext4 filesystem and do the shrink and apply. STEPS TO REPRODUCE 1. Unmount ext4 filesystem 2. Shrink ext4 filesystem 3. FS shrinked and mounted, fsck fails with error displayed OBSERVED RESULT Filesystem resized, but cannot be checked with fsck, error displayed EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71 Qt Version: 5.14.2 ADDITIONAL INFORMATION KDE Partition Manager: SMART Status Report Date: 2020. 06. 23. 16:17 Program version:4.1.0 Backend:pmsfdiskbackendplugin (1) KDE Frameworks version: 5.67.0 Machine:Linux dell6540 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 UTC 2020 x86_64 Shrink partition ‘/dev/sda6’ from 78,76 GiB to 48,97 GiB Job: Check file system on partition ‘/dev/sda6’ Command: e2fsck -f -y -v /dev/sda6 Check file system on partition ‘/dev/sda6’: Success Job: Resize file system on partition ‘/dev/sda6’ to 102 701 056 sectors Resizing file system from 165 167 759 to 102 701 056 sectors. Command: resize2fs /dev/sda6 102701056s Resize file system on partition ‘/dev/sda6’ to 102 701 056 sectors: Success Job: Set geometry of partition ‘/dev/sda6’: Start sector: 334 950 400, length: 102 701 056 Command: sfdisk --force /dev/sda -N 6 Set geometry of partition ‘/dev/sda6’: Start sector: 334 950 400, length: 102 701 056: Success Job: Check file system on partition ‘/dev/sda6’ Command: e2fsck -f -y -v /dev/sda6 Check file system on partition ‘/dev/sda6’: Error Checking partition ‘/dev/sda6’ after resize/move failed. Shrink partition ‘/dev/sda6’ from 78,76 GiB to 48,97 GiB: Error -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 --- Comment #23 from Laosom --- Only Numpad enter works in Neon I confirm :))) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #13 from Laosom --- Not fixed in 5.17.5 ? No RCA found ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390890] All entries disappear from the systemtray settings after modifying an entry's hidden state
https://bugs.kde.org/show_bug.cgi?id=390890 --- Comment #46 from Laosom --- Not fixed in 5.15.0 confirmed changing entries makes it stuck and unusable. Logoff / logon still needed to recover it :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403272] Desktop icons do not respond to clicks
https://bugs.kde.org/show_bug.cgi?id=403272 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #6 from Laosom --- I think the bug appeared with Frameworks 5.55. Doubleclick on desktop icons was OK till PLasma 5.14.5 / FW 5.54. See Bug 404461 too. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403776] Powerdevil suddenly crashes during normal operation
https://bugs.kde.org/show_bug.cgi?id=403776 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #5 from Laosom --- Confirmed. Powerdevil sometimes just crashes after desktop startup. Icon disappears from system tray, you need to log off and log in back. Annoying bug. Basic desktop functonality. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404461] Double-clicking a desktop icon does not work properly
https://bugs.kde.org/show_bug.cgi?id=404461 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #1 from Laosom --- Confirmed. Notice this behaviour when upgraded to 5.15.0 in KDE Neon. Annoying bugs in general desktop functions. Shame. This could be the best linux desktop with QA not skipped . Why to rush with new versions if not tested enough ? Not enough beta testers. Yeah yeah. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390890] All entries disappear from the systemtray settings after modifying an entry's hidden state
https://bugs.kde.org/show_bug.cgi?id=390890 --- Comment #22 from Laosom --- (In reply to Anthony Fieroni from comment #21) > @Laosom, most of time they are regressions in GUI part which is not easy for > auto-testing. You can try patch at https://phabricator.kde.org/D16890 after > all it's not fix all related bugs, only this. Hello Anthony Thanks for the link, but I will wait for the official fix . I hope it's really not far away now . -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390890] All entries disappear from the systemtray settings after modifying an entry's hidden state
https://bugs.kde.org/show_bug.cgi?id=390890 --- Comment #20 from Laosom --- I wrote to Nate Graham , he confirmed it too. Unbelievable noone picks this up and severity is only normal. Plasma is the best linux desktop, but bugs like this are very annoying. They should fix the bugs with more care and willingness . -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #72 from Laosom --- Problem solved for me too with kdeconnect 1.3.3 Thanks a lot guys , awesome work. Best wishes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390890] All entries disappear from the systemtray settings after modifying an entry's hidden state
https://bugs.kde.org/show_bug.cgi?id=390890 --- Comment #17 from Laosom --- Anyone checking this bug ? Any plans to fix in the 5.14.X bugfix releases ? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #59 from Laosom --- I have also upgraded my kdeconnect package to kdeconnect:amd64 (1.3.2-0xneon+18.04+bionic+build7, 1.3.2-0xneon+18.04+bionic+build8) and also the kdeconnect app to 1.10. Cleaned up /home/.../.config/kdeconnect folder, reboot Phone readded . Same error during filebrowse in Dolphin :( -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #47 from Laosom --- Simon & Erik Thanks for the updates and your efforts so far. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #42 from Laosom --- (In reply to Simon from comment #40) > (In reply to Andras from comment #38) > > > Yes, I mean none of the KDE Connect developers > > I don't want to overreact anything and redundantly spiel however if not a > > single KDE developer got KDE neon related to Kdeconnect then wow, that's > > disgraceful indeed. > I don't think I quite see the point being made here. KDE Connect has a very > small development team (depending on how you count, somewhere between 5 and > 10, probably closer to 5). I would rather use the system I am most familiar > with (dnf/yum/RedHat) and be able to focus more effort on work and hobbies. > This does not detract from the usefulness or value of Neon, just that its > goals do not align with mine. > > (In reply to Laosom from comment #37) > > Neon being the "techdemo" distro of KDE Plasma 5, and thought kdeconnect is > > integral part of it , it's strange to hear that and not a good promotion of > > Plasma . I hope someone will pick this up sooner or later. If I compare it > > with Kubuntu 18.10 with backports ppa the OS base is definitely older > > (Ubuntu 18.04 LTS) in NEON. I am going to check the other parts. > One of KDE Connect's goals is to be distribution- and desktop-environment- > independent, so I wouldn't describe it as being "integral" to Plasma 5 or > Plasma 5 being integral to KDE Connect, even though we do integrate nicely > with Plasma. Thanks Simon for the explanation. I really thought Kdeconnect is a Plasma application an part of Plasma. The name of the product was the cause I think. I respect your great work with this great app. I don't use Neon as my daily driver either, as the KDE team states it's not quite a distro . They needed a stable base (Ubuntu LTS) for the latest KDE software to be built on. The first minor versions of a new release is always full of bugs , but the last builds were OK and very fine for daily use. The current version 5.14 is expecting 3 more bugfix releases in the upcoming months and compared to Kubuntu I can use more up-to-date KDE Software. For example Debian Stretch has Plasma 5.8.9 ; Kubuntu 18.04 LTS has Plasma 5.12.6 LTS ; Kubuntu 18.10 has Plasma 5.13.5 and with backports enabled 5.14.2 , but the KDE Applications is still older (18.04) compared to NEON (18.08.2). The interesting thing is Arch / Manjaro is also on the latest of everything and this bug does not exist there. Nathan Graham stated the following in his blog regarding 5.14 : https://pointieststick.wordpress.com/2018/10/14/this-week-in-usability-productivity-part-40/ "We apologize for these bugs and we’re working to get them fixed quickly! One of the reasons why bugs like this squeak through is that we don’t have enough pre-release QA testers. You could be one of them, and next week, your name could be in this list! Just check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!" It would be really nice if one you could test Neon VM and get in contact with the Neon team what's going on ;) Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #37 from Laosom --- (In reply to Simon from comment #36) > (In reply to Laosom from comment #35) > > (In reply to Simon from comment #34) > > > I do not have problems on Fedora 28/29 Plasma 5.12.6/5.13.5. So no, I > > > cannot > > > reproduce this. None of us run Neon, as far as I am aware. I have not yet > > > had time to install a Neon VM and test there. > > > > Hello Simon, > > > > No matter the kdeconnect version, it started to fail only on Neon from the > > 5.14.X updates. No issues on Arch or Kubuntu with Plasma 5.12 / 5.13 /5.14. > Neon 5.14 seems to be the common denominator here, which unfortunately comes > with a huge number of variables, so it will not be easy to chase down unless > someone takes serious ownership of it > > > What do you mean "none of us" ? You mean kdeconnect developers :))) ? > > Thanks. > Yes, I mean none of the KDE Connect developers Neon being the "techdemo" distro of KDE Plasma 5, and thought kdeconnect is integral part of it , it's strange to hear that and not a good promotion of Plasma . I hope someone will pick this up sooner or later. If I compare it with Kubuntu 18.10 with backports ppa the OS base is definitely older (Ubuntu 18.04 LTS) in NEON. I am going to check the other parts. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #35 from Laosom --- (In reply to Simon from comment #34) > I do not have problems on Fedora 28/29 Plasma 5.12.6/5.13.5. So no, I cannot > reproduce this. None of us run Neon, as far as I am aware. I have not yet > had time to install a Neon VM and test there. Hello Simon, No matter the kdeconnect version, it started to fail only on Neon from the 5.14.X updates. No issues on Arch or Kubuntu with Plasma 5.12 / 5.13 /5.14. What do you mean "none of us" ? You mean kdeconnect developers :))) ? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #33 from Laosom --- After upgrading to kdeconnect 1.3.2 same results for me. I can also browse the phone folders by pasting /run/user/... to Dolphin, but not by opening the phone object . lali@neonusr:~$ kdeconnect-cli --list-devices - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) lali@neonusr:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted true lali@neonusr:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait true lali@neonusr:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp getDirectories /run/user/1000/104bfb976bc224ee/storage/extSdCard: SD card /run/user/1000/104bfb976bc224ee/storage/extSdCard/DCIM/Camera: Camera pictures(SD card) /run/user/1000/104bfb976bc224ee/storage/sdcard0: Internal storage /run/user/1000/104bfb976bc224ee/storage/sdcard0/DCIM/Camera: Camera pictures(Internal storage) tmpfs 307364 12 307352 1% /run/user/1000 kdeconnect@192.168.0.103:/ 1048576000 0 1048576000 0% /run/user/1000/104bfb976bc224ee I also confirm to experience this on Neon 5.14.X , info details as wrote earlier. There is no update to the KDEconnect Android app and my phone runs an older Android (4.x). It would be nice to get a feedback from the develeopers if they can reproduce it or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390890] All entries disappear from the systemtray settings after modifying an entry's hidden state
https://bugs.kde.org/show_bug.cgi?id=390890 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #16 from Laosom --- I also experience this bug on Plasma 5.12 LTS(!!!) , 5.13 and 5.14 as well apart from the distro. The only "bugless" was 5.8.6 in Debian. I need to logoff / login or restart plasma with kquitapp5 plasmashell && kstart plasmashell otherwise the system tray is stucked, entries gone , you cannot click on any of them , you get to the settings instead. Very anoying bug , please correct if possible . -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #24 from Laosom --- (In reply to Andras from comment #23) > (In reply to Laosom from comment #21) > > journalctl -ex > > Forget it if I'm wrong however I don't think placing whole bunch of common > device and journalctl information would help the thread, it creates a mess. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178
--- Comment #21 from Laosom ---
journalctl -ex
okt 29 12:52:32 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: TCP
connection done (i'm the existing device)
okt 29 12:52:32 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: Starting
server ssl (I'm the client TCP socket)
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: Socket
succesfully stablished an SSL connection
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: It is a
known device "Samsung GT-S7710"
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: add
to dolphin
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
Created device: "Samsung GT-S7710"
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: Connecting to deprecated
signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]:
kdeconnect.plugin.sendnotification: Registered notifications listener for
device "Samsung GT-S7710"
okt 29 12:52:41 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount
device: "Samsung GT-S7710"
okt 29 12:52:41 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
Created mounter
okt 29 12:52:41 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
Starting loop to wait for mount
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
Unmount QObject(0x0)
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: Converting
IPv6 QHostAddress(":::192.168.0.103") to IPv4 QHostAddress("192.168.0.103")
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
Starting process: "sshfs kdeconnect@192.168.0.103:/
/run/user/1000/104bfb976bc224ee -p 1739 -s -f -F /
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: QDBusAbstractAdaptor: Cannot
relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type
in parameter list:
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
Process started
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
"Samsung GT-S7710" "Remote filesystem mounted at
/run/user/1000/104bfb976bc224ee"
okt 29 12:52:43 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp:
stdout: "Warning: Permanently added '[192.168.0.103]:1739' (DSA) to the list of
known hosts.\r\n"
okt 29 12:52:44 neonlts org.kde.kdeconnect[1453]: kf5.kio.widgets:
KRun(0x55c2f22c0780) ERROR 143 "The process for the
kdeconnect://104bfb976bc224ee protocol died unexpectedly."
okt 29 12:53:31 neonlts dbus-daemon[1453]: [session uid=1000 pid=1453]
Activating service name='org.kde.runners.baloo' requested by ':1.24' (uid=1000
pid=1566 comm="/usr/bin/pla
okt 29 12:53:31 neonlts dbus-daemon[1453]: [session uid=1000 pid=1453]
Successfully activated service 'org.kde.runners.baloo'
okt 29 12:54:45 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount
device: "Samsung GT-S7710"
okt 29 12:59:22 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount
device: "Samsung GT-S7710"
okt 29 12:59:58 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount
device: "Samsung GT-S7710"
okt 29 13:00:00 neonlts org.kde.kdeconnect[1453]: kf5.kio.widgets:
KRun(0x55c2f2223160) ERROR 143 "The process for the
kdeconnect://104bfb976bc224ee protocol died unexpectedly."
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #20 from Laosom --- Hello Simon Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.2 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.15.0-38-generic OS Type: 64-bit Processors: 2 × Intel® Core™2 Duo CPU P8400 @ 2.26GHz Memory: 3,8 GiB of RAM $ kdeconnect-cli --list-devices - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) 1 device found $ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted true $ df -h Filesystem Size Used Avail Use% Mounted on udev1,9G 0 1,9G 0% /dev tmpfs 390M 1,5M 389M 1% /run /dev/sda612G 11G 916M 92% / tmpfs 2,0G 15M 1,9G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 2,0G 0 2,0G 0% /sys/fs/cgroup /dev/loop0 88M 88M 0 100% /snap/core/5328 /dev/loop1 88M 88M 0 100% /snap/core/5548 /dev/loop2 88M 88M 0 100% /snap/core/5662 tmpfs 390M 16K 390M 1% /run/user/1000 kdeconnect@192.168.0.103:/ 1000G 0 1000G 0% /run/user/1000/104bfb976bc224ee $ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait true $ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp getDirectories /run/user/1000/104bfb976bc224ee/storage/extSdCard: SD card /run/user/1000/104bfb976bc224ee/storage/extSdCard/DCIM/Camera: Camera pictures(SD card) /run/user/1000/104bfb976bc224ee/storage/sdcard0: Internal storage /run/user/1000/104bfb976bc224ee/storage/sdcard0/DCIM/Camera: Camera pictures(Internal storage) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #15 from Laosom --- Issue not fixed in Neon User ed. by the 5.14.2 update installed today. Kubuntu 18.10 (with backports) on the same Plasma version is fine. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #14 from Laosom --- Experienced only in KDE Neon, other distros and Kubuntu is fine. kdeconnect-cli --list-devices - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) 1 device found qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted true qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait true Error : The process for the kdeconnect://104bfb976bc224ee protocol died unexpectedly. Checked in terminal, and it seems to be mounted and can be browsed: kdeconnect@192.168.0.103:/ 10485760000 1048576000 0% /run/user/1001/104bfb976bc224ee Even with the path pasted to Dolphin. -- You are receiving this mail because: You are watching all bug changes.
