[Merkuro] [Bug 481251] Mail - Folders that have subfolders can't be selected
https://bugs.kde.org/show_bug.cgi?id=481251 Kwon-Young Choi changed: What|Removed |Added CC||kwon-young.c...@hotmail.fr --- Comment #1 from Kwon-Young Choi --- *** Bug 488298 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 488298] Clicking on folder in treeview folds the node instead of showing emails of the folder
https://bugs.kde.org/show_bug.cgi?id=488298 --- Comment #3 from Kwon-Young Choi --- *** This bug has been marked as a duplicate of bug 481251 *** -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 470092] Unable to view mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=470092 Kwon-Young Choi changed: What|Removed |Added CC||kwon-young.c...@hotmail.fr --- Comment #1 from Kwon-Young Choi --- *** Bug 488298 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 488298] Clicking on folder in treeview folds the node instead of showing emails of the folder
https://bugs.kde.org/show_bug.cgi?id=488298 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Kwon-Young Choi --- *** This bug has been marked as a duplicate of bug 470092 *** -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 488298] Clicking on folder in treeview folds the node instead of showing emails of the folder
https://bugs.kde.org/show_bug.cgi?id=488298 --- Comment #1 from Kwon-Young Choi --- I forgot to specify that this bug is about Merkuro Mail -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 488298] New: Clicking on folder in treeview folds the node instead of showing emails of the folder
https://bugs.kde.org/show_bug.cgi?id=488298 Bug ID: 488298 Summary: Clicking on folder in treeview folds the node instead of showing emails of the folder Classification: Applications Product: Merkuro Version: 24.05.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: kwon-young.c...@hotmail.fr CC: c...@carlschwan.eu Target Milestone: --- Created attachment 170321 --> https://bugs.kde.org/attachment.cgi?id=170321=edit recording of the folding *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Clicking on folder with subfolders in treeview folds the node instead of showing emails of the folder STEPS TO REPRODUCE 1. click on an inbox with subfolder 2. the folder folds as if we had clicked on the folding arrow OBSERVED RESULT The folder folds. EXPECTED RESULT I expect the folder to be selected and show emails of the folder on the email list view. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: Dell Inc. Product Name: Precision 5520 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436125] ISO mounting plugin mounts ISO images as non-removable devices
https://bugs.kde.org/show_bug.cgi?id=436125 --- Comment #8 from Kwon-Young Choi --- (In reply to Patrick Silva from comment #7) > I have two ISOs, can reproduce with both: > Fedora-KDE-Live-x86_64-35-1.2.iso > manjaro-sway-21.0-210428-linux510.iso > > The ISOs are mounted as non-removable devices regardless of whether the ISO > files are located on an ntfs partition or on an EXT4. > > Also regardless where the ISOs are located, I'm always able to mount and > unmount them via context menu of the files. I can also unmount the ISOs via > the context menu of the Places panel, but in this case the ISOs are not > removed from 'Devices' section. Okay, so all of this is expected behavior. Are the little mounted and unmounted icons still missing ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436125] ISO mounting plugin mounts ISO images as non-removable devices
https://bugs.kde.org/show_bug.cgi?id=436125 --- Comment #6 from Kwon-Young Choi --- And also, where are the iso files located ? There is a known bug where if the iso file is on an NTFS mounted drive, the mounted device does not show without a dolphin restart. Are you able to mount and unmount the iso file via the file contextual menu ? via the device contextual menu in dolphin [Devices] panel ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436125] ISO mounting plugin mounts ISO images as non-removable devices
https://bugs.kde.org/show_bug.cgi?id=436125 --- Comment #5 from Kwon-Young Choi --- (In reply to Patrick Silva from comment #4) > yes, I can reproduce on neon unstable. > > Operating System: KDE neon Unstable Edition > KDE Plasma Version: 5.25.80 > KDE Frameworks Version: 5.97.0 > Qt Version: 5.15.5 > Graphics Platform: Wayland Does this happen for any iso you have? If not, could you send me an example file? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457508] Disc Images mount successfully, but aren't shown under the 'Places' panel.
https://bugs.kde.org/show_bug.cgi?id=457508 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Kwon-Young Choi --- dummy comment to change status -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431704] Dolphin cannot mount some iso's
https://bugs.kde.org/show_bug.cgi?id=431704 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #14 from Kwon-Young Choi --- Also, does the iso appear if you restart dolphin ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443125] Mounted ISO does not appear in left sidebar immediately
https://bugs.kde.org/show_bug.cgi?id=443125 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #4 from Kwon-Young Choi --- Also do you mount an iso file located in an NTFS partition ? See https://bugs.kde.org/show_bug.cgi?id=443444 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431704] Dolphin cannot mount some iso's
https://bugs.kde.org/show_bug.cgi?id=431704 --- Comment #13 from Kwon-Young Choi --- (In reply to Patrick Silva from comment #11) > I have the same problem on Arch Linux. > In the attached screen recording, I can't mount two DVD-video ISO images > created with K3b. > > Mounting with udisksctl gives me this output (ISOs are still not visible in > Places panel of Dolphin after > this command): > $udisksctl loop-setup -f > Mapped file as /dev/loopX. Hello, Does this bug still happen ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443125] Mounted ISO does not appear in left sidebar immediately
https://bugs.kde.org/show_bug.cgi?id=443125 Kwon-Young Choi changed: What|Removed |Added CC||edpi...@orange.fr --- Comment #3 from Kwon-Young Choi --- *** Bug 445262 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445262] Mount Iso context menu shows no entries in the device panel
https://bugs.kde.org/show_bug.cgi?id=445262 Kwon-Young Choi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Kwon-Young Choi --- This also seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=443125 *** This bug has been marked as a duplicate of bug 443125 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443125] Mounted ISO does not appear in left sidebar immediately
https://bugs.kde.org/show_bug.cgi?id=443125 --- Comment #2 from Kwon-Young Choi --- Hello again, I do not observe this behavior now on Fedora 36. Do you still observe the bug on your system ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443444] ISOs located on external NTFS disks are only displayed in the hamburger menu after you quit and restart Dolphin.
https://bugs.kde.org/show_bug.cgi?id=443444 Kwon-Young Choi changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kwon-Young Choi --- Hello, I can also reproduce this bug. I'll try to see what I can do. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445262] Mount Iso context menu shows no entries in the device panel
https://bugs.kde.org/show_bug.cgi?id=445262 --- Comment #3 from Kwon-Young Choi --- Hello, Sorry for the very late reply. Can anybody reproduce this bug with a more recent build of dolphin ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436125] ISO mounting plugin mounts ISO images as non-removable devices
https://bugs.kde.org/show_bug.cgi?id=436125 --- Comment #3 from Kwon-Young Choi --- Hello, Sorry for the very very late reply. The fact that the iso is mounted under the section [Devices] instead of [Removal Devices] is expected. As you have noticed, maybe it would be more logical to put it under [Removal Devices]. One thing that is not normal is that when the device is shown on the left panel of Dolphin, it should either have a small unmounted icon or a mounted arrow icon. Can you still reproduce this bug ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457508] Disc Images mount successfully, but aren't shown under the 'Places' panel.
https://bugs.kde.org/show_bug.cgi?id=457508 --- Comment #1 from Kwon-Young Choi --- Hello, How do you mount the iso file ? Would it be possible to transmit the iso file so that I can test it on my system ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446916] KCMs flicker and reload when the cursor passes over their QQuickWidget
https://bugs.kde.org/show_bug.cgi?id=446916 --- Comment #9 from Kwon-Young Choi --- Ah, I'm sorry, after going back to the settings app, what I've noticed is that the list of settings category on the left-hand side of the app does not flicker, but some kcms like "display and monitor" -> "display configuration" does flicker (a lot less than the other laptop though) but not "display and monitor" -> "compositor". After switching scaling factors, the problem seems to get a little bit worse, and even the left-hand side list starts to flicker. Restarting the settings app seems to resolve the flickering of the list but not the rest. I'll try to compile the new overview effect on this -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446916] KCMs flicker and reload when the cursor passes over their QQuickWidget
https://bugs.kde.org/show_bug.cgi?id=446916 --- Comment #8 from Kwon-Young Choi --- > I think I'm seeing the same thing in the new KWin Overview effect. Can anyone > else who is able to reproduce the bug confirm that? Sorry, I can't compile kde software from source on the laptop with the bug. But I have another laptop of the same brand and series, a bit older with a 1080p screen and I can't reproduce the bug there. Here is the configuration of that laptop: Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 >From this quick comparison, the only thing that changes is the cpu generation and the graphics processor being `HD Graphics 630` vs `UHD Graphics` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446916] heavy stuttering in settings app
https://bugs.kde.org/show_bug.cgi?id=446916 --- Comment #1 from Kwon-Young Choi --- I also forgot to say that I am using a 200% scaling factor. I believe that this is the cause because I use another very similar laptop but with a 1080p screen instead of 4k and the settings app does not flicker. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446916] New: heavy stuttering in settings app
https://bugs.kde.org/show_bug.cgi?id=446916 Bug ID: 446916 Summary: heavy stuttering in settings app Product: systemsettings Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kwon-young.c...@hotmail.fr Target Milestone: --- Created attachment 144503 --> https://bugs.kde.org/attachment.cgi?id=144503=edit video showing stuttering in the system settings app 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 *** The whole app stutters with a lot of the ui constantly disappearing and reappearing when moving the mouse. STEPS TO REPRODUCE 1. open the settings app 2. move the mouse 3. OBSERVED RESULT The whole app stutters with a lot of the ui constantly disappearing and reappearing when moving the mouse. EXPECTED RESULT Nothing stutters. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics My laptop also has a nvidia gpu quadro that I use only for deep learning, so I have the nvidia drivers and cuda installed but that's all. All of the desktop is rendered through the intel gpu. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #9 from Kwon-Young Choi --- Hello, I have upgraded to: Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics And the wayland session and plasmashell is starting correctly. I think we can now close this bug. However, I have noticed a very heavy stuttering in the settings app (I'll try to open a new bug for that). The rest of the desktop seems normal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #8 from Kwon-Young Choi --- I've tried to downgrade egl-wayland as suggested in the previously linked bug report and got a working plasmashell session. I don't really understand if it is nvidia or qt that should be patched but I'll wait for more updates to come :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #7 from Kwon-Young Choi --- Maybe this will also help ``` ☧~ dnf info egl-wayland Installed Packages Name : egl-wayland Version : 1.1.9 Release : 2.fc35 Architecture : i686 Size : 66 k Source : egl-wayland-1.1.9-2.fc35.src.rpm Repository : @System >From repo: updates Summary : Wayland EGL External Platform library URL : https://github.com/NVIDIA/egl-wayland License : MIT Description : Wayland EGL External Platform library ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #6 from Kwon-Young Choi --- >From the error message, I've found this bug: https://github.com/NVIDIA/egl-wayland/issues/40 My laptop has an two card, intel and nvidia. By default, I believe everything should be using the intel card, no ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #5 from Kwon-Young Choi --- Here is the output of trying to launch plasmahsell: ``` ☧~ plasmashell --replace kf.plasma.quick: Applet preload policy set to 1 qt.svg: :303:258: Could not add child element to parent element because the types are incorrect. qt.svg: :303:463: Could not add child element to parent element because the types are incorrect. qt.svg: :303:659: Could not add child element to parent element because the types are incorrect. qt.svg: :303:913: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1049: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1251: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1453: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1631: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1739: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1980: Could not add child element to parent element because the types are incorrect. qt.svg: :303:2223: Could not add child element to parent element because the types are incorrect. trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height" qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [destroyed object]: error 7: importing the supplied dmabufs failed The Wayland connection experienced a fatal error: Protocol error ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #4 from Kwon-Young Choi --- Yes ! Doing ctrl-alt-t opens konsole. Don't know why I haven't thouht of doing that -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 Kwon-Young Choi changed: What|Removed |Added Version|5.23.2 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #2 from Kwon-Young Choi --- updated to: Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.18-300.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Still the same problem happens when login to wayland with a freshly created user -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 --- Comment #1 from Kwon-Young Choi --- tried with a freshly created user, results in the same problem with only black screen and mouse -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445735] New: wayland login results in black screen with mouse
https://bugs.kde.org/show_bug.cgi?id=445735 Bug ID: 445735 Summary: wayland login results in black screen with mouse Product: kwin Version: 5.23.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kwon-young.c...@hotmail.fr Target Milestone: --- SUMMARY Hello, I've just upgraded from plasma 22 to plasma 23 in fedora 35 and when I try to login with wayland, I just obtain a black screen with my mouse still responsive. I've also noticed some blue effect on the corners of the screen. STEPS TO REPRODUCE 1. login in sddm with wayland OBSERVED RESULT Immediately shown black screen with mouse still moving. EXPECTED RESULT normal plasma desktop is shown SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.17-301.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION My laptop is a dell precision with a 4k screen, which I normally set to 1920p in x11 because I can't specify different scaling factor for different monitors. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443125] Mounted ISO does not appear in left sidebar immediately
https://bugs.kde.org/show_bug.cgi?id=443125 Kwon-Young Choi changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Kwon-Young Choi --- Yes, I already noticed this bug. I'll try to debug it someday when I have time. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434617] It's possible to mount the same ISO image multiple times
https://bugs.kde.org/show_bug.cgi?id=434617 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||dolphin-plugins/commit/f136 ||702d2adc8643ea12f1b6e3bf979 ||25f1b33f0 Status|ASSIGNED|RESOLVED --- Comment #12 from Kwon-Young Choi --- Git commit f136702d2adc8643ea12f1b6e3bf97925f1b33f0 by Kwon-Young Choi. Committed on 28/03/2021 at 07:03. Pushed by elvisangelaccio into branch 'release/21.04'. BackingFile property should be use with StorageVolume instead of StorageAccess When mounting an iso with `udisksctl`, first a loop device is created `/dev/loop0` then a second device `/dev/loop0p1` is used to mount it on a filesystem location. Querying for StorageAccess devices sometimes only returns the `/dev/loop0p1` device without the `/dev/loop0` device and the BackingFile property does not work on `/dev/loop0p1`. Solution: query for StorageVolume instead which returns all loop devices: `/dev/loop0` and `/dev/loop1`. Warning: Because StorageVolume returns more devices, the function `getDeviceFromBackingFile` could be a little bit slower. M +1-1mountiso/mountisoaction.cpp https://invent.kde.org/sdk/dolphin-plugins/commit/f136702d2adc8643ea12f1b6e3bf97925f1b33f0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434617] It's possible to mount the same ISO image multiple times
https://bugs.kde.org/show_bug.cgi?id=434617 --- Comment #11 from Kwon-Young Choi --- (In reply to Nate Graham from comment #10) > Not fixed yet since that merge request hasn't been merged. :) Yes, my bad... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434617] It's possible to mount the same ISO image multiple times
https://bugs.kde.org/show_bug.cgi?id=434617 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Kwon-Young Choi --- So I believed I know what is wrong, I've created a merge request https://invent.kde.org/sdk/dolphin-plugins/-/merge_requests/28 which should solve this. (In reply to popov895 from comment #7) > And just a question: should the mounted ISO images be shown in the "Disk & > Devices" widget as well? It's shown in the non-removable devices which by default is not visible. You can change the view in the hamburger menu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434617] It's possible to mount the same ISO image multiple times
https://bugs.kde.org/show_bug.cgi?id=434617 Kwon-Young Choi changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #6 from Kwon-Young Choi --- Well, until now with the iso I tested with, it worked. But I can reproduce your issue, so let me debug this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434617] It's possible to mount the same ISO image multiple times
https://bugs.kde.org/show_bug.cgi?id=434617 Kwon-Young Choi changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Kwon-Young Choi --- Ok, so just to be sure, what is the output of: * `solid-hardware5 nonportableinfo /org/freedesktop/UDisks2/block_devices/loop0` * `solid-hardware5 nonportableinfo /org/freedesktop/UDisks2/block_devices/loop1` * `solid-hardware5 nonportableinfo /org/freedesktop/UDisks2/block_devices/loop2` If all the `BackingFile` properties are the same, I don't know what is happening, and I'm going to need your iso so that I can try to reproduce this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434617] It's possible to mount the same ISO image multiple times
https://bugs.kde.org/show_bug.cgi?id=434617 --- Comment #1 from Kwon-Young Choi --- Hello, It seems the detection of the mounting of the iso is not working. Could you provide the output of `udiskctl dump` when you have mounted the iso multiple times? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431704] Dolphin cannot mount some iso's
https://bugs.kde.org/show_bug.cgi?id=431704 Kwon-Young Choi changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #9 from Kwon-Young Choi --- So, I actually tried to mount an iso from a USB key formatted with a NTFS partition. What I have found is that the iso is actually correctly mounted (I was able to explore the iso by going to /run/media/username/myiso) but it did not appear in the dolphin sidebar. Therefore, I think this is a problem with Dolphin itself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431704] Dolphin cannot mount some iso's
https://bugs.kde.org/show_bug.cgi?id=431704 Kwon-Young Choi changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Kwon-Young Choi --- (In reply to soredake from comment #7) > I've identified that i cannot mount these iso's because they was stored in > ntfs partition, mounting from ext4 works fine. Okay, I have no idea why this is the case. I hope someone more experimented can comment on this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431704] Dolphin cannot mount some iso's
https://bugs.kde.org/show_bug.cgi?id=431704 Kwon-Young Choi changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Kwon-Young Choi --- (In reply to soredake from comment #0) > SUMMARY > Sample iso's: > https://www.myabandonware.com/game/the-punisher-c6u#download (first russian > iso) > > STEPS TO REPRODUCE > 1. Try to mount these iso's > 2. Fail. > > OBSERVED RESULT > Iso cannot be mounted. > > EXPECTED RESULT > Iso can be mounted. > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Kubuntu 20.10 > (available in About System) > KDE Plasma Version: 5.19.5 > KDE Frameworks Version: 5.74.0 > Qt Version: 5.14.2 > > ADDITIONAL INFORMATION So I tested the iso from the link and the only problem is that the mimetype of the iso is not recognized. The downloaded iso file uses the `.mdf` extension which seems to not be recognized as an x-cd-image file. If I rename the file with a `.iso` extension, everything works as intended. So the problem is not with the plugin itself but with the handling of the mimetype of the file. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431704] Dolphin cannot mount some iso's
https://bugs.kde.org/show_bug.cgi?id=431704 --- Comment #2 from Kwon-Young Choi --- Hello, I will try to investigate, but it would be easier if you had a smaller iso to test with. Could you test this command to mount your iso: ``` udisksctl loop-setup -f myisofile.iso ``` -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429914] ISO is mounted,but user cannot enter folder
https://bugs.kde.org/show_bug.cgi?id=429914 --- Comment #2 from Kwon-Young Choi --- Sorry for not replying earlier. > Assume root permissions and navigate to the node. Contents can indeed be > read. This seems to be problem with how permissions are set up on the iso. Could you show what `ls -alh` do when you are able to navigate as root to the mounted iso directory ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 --- Comment #16 from Kwon-Young Choi --- (In reply to Harald Sitter from comment #15) > (In reply to Kwon-Young Choi from comment #13) > > (In reply to Harald Sitter from comment #12) > > > Kind of. The data we care about is available so we could still show the > > > device, the output you posted suggests our timeout is just too short > > > (well, > > > it's 30 seconds - short is relative here ^^) > > > > Yeah, you would need a timeout longer than 120s I think. > > How do you figure 120? Looking at the code the timeouts are 60, or does it > in fact take 120 for the smartctl to return when you run it manually? yes, see https://listi.jpberlin.de/pipermail/smartmontools-support/2020-November/000538.html -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 --- Comment #13 from Kwon-Young Choi --- (In reply to Harald Sitter from comment #12) > Kind of. The data we care about is available so we could still show the > device, the output you posted suggests our timeout is just too short (well, > it's 30 seconds - short is relative here ^^) Yeah, you would need a timeout longer than 120s I think. -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #11 from Kwon-Young Choi ---
(In reply to Harald Sitter from comment #10)
> Thanks. There's something weird though...
>
> > "exit_status": 4
>
> shouldn't be filtered right now, so there must be something else going on
> additionally.
>
> It'd be great if you could get me the output of
>
> `QT_LOGGING_RULES="org.kde.plasma.disks=true" kded5 --replace`
Sorry for the delay.
Here's the output for:
```
$ `QT_LOGGING_RULES="org.kde.plasma.disks=true" kded5 --replace`
kf.kded: Couldn't register name "org.kde.kcookiejar5" with DBUS - another
process owns it already!
org.kde.plasma.disks: starting
org.kde.plasma.disks: "/org/freedesktop/UDisks2/block_devices/nvme0n1"
org.kde.plasma.disks: evaluating!
org.kde.plasma.disks: true true "org.kde.kded.smart"
KAuth::Action::AuthorizedStatus
org.kde.plasma.disks: "/org/freedesktop/UDisks2/block_devices/nvme0n1p1"
org.kde.plasma.disks:bad type Solid::StorageVolume::FileSystem
org.kde.wacomtablet.common: d->name.isEmpty? true
org.kde.wacomtablet.common: d->name.isEmpty? true
bluedevil: Created
Installing the delayed initialization callback.
kcm_touchpad: Using X11 backend
Delayed initialization.
Reloading the khotkeys configuration
Version 2 File!
true
1
Known activities: ("380a83a6-47ae-4f65-87be-08be5d57e561",
"4ca8abe1-deed-47b4-9b4b-627cfad25fd9")
Registering "org.kde.StatusNotifierItem-1224-1/StatusNotifierItem" to system
tray
Registering "org.kde.StatusNotifierHost-1059" as system tray
bluedevil: Bluetooth operational changed true
bluedevil: ObexManager operational changed true
Registering ":1.167/StatusNotifierItem" to system tray
Registering ":1.42/StatusNotifierItem" to system tray
Registering ":1.48/StatusNotifierItem" to system tray
bluedevil: ObexAgent registered
bluedevil: Agent registered
bluedevil: Requested default Agent
kf.auth: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."
org.kde.plasma.disks: looks like we got no data back for "/dev/nvme0n1" 0 true
Warning from helper: QProcess: Destroyed while process ("smartctl") is still
running.
```
So, after contacting the smartmontools team, it turns out that this is a
firmware bug of my ssd but fortunately, it is easy to modify smartctl to hide
this bug. See the mail thread here:
https://listi.jpberlin.de/pipermail/smartmontools-support/2020-November/000544.html
Since we now know that this is an upstream bug, I believe we can close this bug
report.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 422082] Using mountiso plugin unmount action on a mounted loop device does not remove the loop device
https://bugs.kde.org/show_bug.cgi?id=422082 Kwon-Young Choi changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||dolphin-plugins/commit/f4e7 ||a1b8a1fa74f7a0d47d85f702ffb ||c201423d8 --- Comment #3 from Kwon-Young Choi --- Git commit f4e7a1b8a1fa74f7a0d47d85f702ffbc201423d8 by Kwon-Young Choi. Committed on 11/11/2020 at 11:07. Pushed by elvisangelaccio into branch 'release/20.12'. Autmatically unmount mounted directory when deleting loop device When deleting a loop device, all mounts depending on this loop device should be unmounted before deletion. This patch uses Solid to get all StorageAccess devices linked to the loop device to delete and unmounts them if needed before the loop devie deletion. M +22 -7mountiso/mountisoaction.cpp https://invent.kde.org/sdk/dolphin-plugins/commit/f4e7a1b8a1fa74f7a0d47d85f702ffbc201423d8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428962] New: Fail to mount the same iso file twice
https://bugs.kde.org/show_bug.cgi?id=428962 Bug ID: 428962 Summary: Fail to mount the same iso file twice Product: dolphin Version: 20.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins: ISO mounting Assignee: kwon-young.c...@hotmail.fr Reporter: kwon-young.c...@hotmail.fr CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The MountIso plugin fails to mount the same iso file a second time after mounting and unmounting it. This leads to an unresponsive dolphin for 10 seconds. STEPS TO REPRODUCE 1. mount an iso 2. unmount an iso 3. mount an iso OBSERVED RESULT Dolphin freeze during 10 seconds. The iso file is not mounted. EXPECTED RESULT The iso file mounts immediately. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.3-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 ADDITIONAL INFORMATION Both the latest dolphin on manjaro and dolphin built from sources exhibit this behavior. Interestingly, udisksctl does not have this problem. So, I compared the dbus calls from mountiso and udisksctl and found that udisksctl does not set the read-only option on the loop-setup call: http://storaged.org/doc/udisks2-api/2.8.4/gdbus-org.freedesktop.UDisks2.Manager.html#gdbus-method-org-freedesktop-UDisks2-Manager.LoopSetup After removing the read-only option in the mountiso plugin, the mount works as expected. I'll make a merge-request to fix this immediately. -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #9 from Kwon-Young Choi ---
(In reply to Harald Sitter from comment #8)
> You'll want to take this upstream https://www.smartmontools.org/#BugReports
> this is either a bug in smartmontools or, I guess more likely, the drive
> firmware itself as it fails to respond (in time).
>
> If you could attach a file with the output of `sudo smartctl --all --json
> /dev/nvme0n1` that'd be helpful though. Depending on its contents we could
> choose to ignore the return value of smartctl I suppose.
I will try to send something upstream.
Here is the output of `sudo smartctl --all --json /dev/nvme0n1`:
{
"json_format_version": [
1,
0
],
"smartctl": {
"version": [
7,
1
],
"svn_revision": "5022",
"platform_info": "x86_64-linux-5.9.3-1-MANJARO",
"build_info": "(local build)",
"argv": [
"smartctl",
"--all",
"--json",
"/dev/nvme0n1"
],
"messages": [
{
"string": "Read Error Information Log failed: NVME_IOCTL_ADMIN_CMD:
Appel système interrompu",
"severity": "error"
}
],
"exit_status": 4
},
"device": {
"name": "/dev/nvme0n1",
"info_name": "/dev/nvme0n1",
"type": "nvme",
"protocol": "NVMe"
},
"model_name": "PC300 NVMe SK hynix 256GB",
"serial_number": "EJ77N46141180792O",
"firmware_version": "20005A00",
"nvme_pci_vendor": {
"id": 7260,
"subsystem_id": 7260
},
"nvme_ieee_oui_identifier": 11330606,
"nvme_controller_id": 0,
"nvme_number_of_namespaces": 1,
"nvme_namespaces": [
{
"id": 1,
"size": {
"blocks": 500118192,
"bytes": 256060514304
},
"capacity": {
"blocks": 500118192,
"bytes": 256060514304
},
"utilization": {
"blocks": 500118192,
"bytes": 256060514304
},
"formatted_lba_size": 512,
"eui64": {
"oui": 11330606,
"ext_id": 487747682236
}
}
],
"user_capacity": {
"blocks": 500118192,
"bytes": 256060514304
},
"logical_block_size": 512,
"local_time": {
"time_t": 1605000494,
"asctime": "Tue Nov 10 10:28:14 2020 CET"
},
"smart_status": {
"passed": true,
"nvme": {
"value": 0
}
},
"nvme_smart_health_information_log": {
"critical_warning": 0,
"temperature": 30,
"available_spare": 100,
"available_spare_threshold": 10,
"percentage_used": 2,
"data_units_read": 5188835,
"data_units_written": 21146267,
"host_reads": 66725315,
"host_writes": 282306897,
"controller_busy_time": 1018,
"power_cycles": 1826,
"power_on_hours": 158,
"unsafe_shutdowns": 112,
"media_errors": 0,
"num_err_log_entries": 218352,
"warning_temp_time": 0,
"critical_comp_time": 0,
"temperature_sensors": [
30
]
},
"temperature": {
"current": 30
},
"power_cycle_count": 1826,
"power_on_time": {
"hours": 158
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 --- Comment #7 from Kwon-Young Choi --- I have just run the dell diagnostics on my laptop and the smart, dst short and long test all passed without any problems. -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 Kwon-Young Choi changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Kwon-Young Choi --- (In reply to Justin Zobel from comment #5) > Looks like Appel système interrompu means System call interrupted. > > If it were me I'd check the NVMe diagnostics (if they exist) from your > EFI/BIOS. Ok, I'll try to do that and report back -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 Kwon-Young Choi changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Kwon-Young Choi --- (In reply to Justin Zobel from comment #3) > Does smartctl show any info on it? > > sudo smartctl --all /dev/nvme0n1 $ sudo smartctl --all /dev/nvme0n1 [sudo] Mot de passe de kwon-young : smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.3-1-MANJARO] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: PC300 NVMe SK hynix 256GB Serial Number: EJ77N46141180792O Firmware Version: 20005A00 PCI Vendor/Subsystem ID:0x1c5c IEEE OUI Identifier:0xace42e Controller ID: 0 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256,060,514,304 [256 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:ace42e 719006ffbc Local Time is: Mon Nov 9 09:04:24 2020 CET Firmware Updates (0x16):3 Slots, no Reset required Optional Admin Commands (0x0016): Format Frmw_DL Self_Test Optional NVM Commands (0x001e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages Warning Comp. Temp. Threshold: 88 Celsius Critical Comp. Temp. Threshold: 90 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 5.87W --0 0 0 05 5 1 + 2.40W --1 1 1 1 30 30 2 + 1.90W --2 2 2 2 100 100 3 - 0.1000W --3 3 3 3 10001000 4 - 0.0060W --3 3 3 3 10005000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 - 512 0 0 1 -4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:25 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:2% Data Units Read:5,174,435 [2.64 TB] Data Units Written: 20,997,211 [10.7 TB] Host Read Commands: 66,438,160 Host Write Commands:279,794,847 Controller Busy Time: 1,007 Power Cycles: 1,822 Power On Hours: 157 Unsafe Shutdowns: 112 Media and Data Integrity Errors:0 Error Information Log Entries: 218,352 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Temperature Sensor 1: 25 Celsius # stops for a long time here Read Error Information Log failed: NVME_IOCTL_ADMIN_CMD: Appel système interrompu Something seems to be wrong at the end. Do you think it is a problem with smartctl ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 --- Comment #2 from Kwon-Young Choi --- ok, I don't really know what to do to understand what is not working on my system. Does plasma-disks has log somewhere I could get ? Maybe it will tell us what is going wrong ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 428844] New: No support for nvme disks
https://bugs.kde.org/show_bug.cgi?id=428844 Bug ID: 428844 Summary: No support for nvme disks Product: plasma-disks Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kwon-young.c...@hotmail.fr CC: sit...@kde.org Target Milestone: --- SUMMARY I have a nvme ssd PC300 NVMe SK hynix 256GB but it does not appear in the smart monitoring of the info center. STEPS TO REPRODUCE 1. open info center, go to devices -> SMART Status OBSERVED RESULT No S.M.A.R.T devices found EXPECTED RESULT Smart status of my nvme disks SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.3-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 ADDITIONAL INFORMATION $ solid-hardware5 details /org/freedesktop/UDisks2/drives/PC300_NVMe_SK_hynix_256GB_EJ77N46141180792O udi = '/org/freedesktop/UDisks2/drives/PC300_NVMe_SK_hynix_256GB_EJ77N46141180792O' parent = '/org/freedesktop/UDisks2' (string) vendor = '' (string) product = 'PC300 NVMe SK hynix 256GB' (string) description = '238.5 GiB Hard Drive' (string) icon = 'drive-harddisk' (string) Block.major = 259 (0x103) (int) Block.minor = 1 (0x1) (int) Block.device = '/dev/nvme0n1p1' (string) StorageDrive.bus = 'Platform' (0x5) (enum) StorageDrive.driveType = 'HardDisk' (0x0) (enum) StorageDrive.removable = false (bool) StorageDrive.hotpluggable = false (bool) StorageDrive.inUse = true (bool) StorageDrive.size = 256060514304 (0x3b9e656000) (qulonglong) $ solid-hardware5 details /org/freedesktop/UDisks2/block_devices/nvme0n1p1 udi = '/org/freedesktop/UDisks2/block_devices/nvme0n1p1' parent = '/org/freedesktop/UDisks2/drives/PC300_NVMe_SK_hynix_256GB_EJ77N46141180792O' (string) vendor = '' (string) product = 'PC300 NVMe SK hynix 256GB' (string) description = '238.5 GiB Hard Drive' (string) icon = 'drive-harddisk-root' (string) Block.major = 259 (0x103) (int) Block.minor = 1 (0x1) (int) Block.device = '/dev/nvme0n1p1' (string) StorageAccess.accessible = true (bool) StorageAccess.filePath = '/' (string) StorageAccess.ignored = true (bool) StorageVolume.ignored = false (bool) StorageVolume.usage = 'FileSystem' (0x2) (enum) StorageVolume.fsType = 'ext4' (string) StorageVolume.label = '' (string) StorageVolume.uuid = '31563a99-fa20-4ee4-8bea-6c6e005a703f' (string) StorageVolume.size = 256059229184 (0x3b9e51c400) (qulonglong) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428392] Impossible to "eject" a mounted ISO image
https://bugs.kde.org/show_bug.cgi?id=428392 Kwon-Young Choi changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Kwon-Young Choi --- (In reply to Patrick Silva from comment #2) > clearer step 3: > 3. right-click on the ISO image under "Devices" section of Places panel, > choose "Unmount" > > OBSERVED RESULT > the icon under "Devices" indicates successful unmounting but the ISO image > is not "ejected". > If I right-click on the same ISO image and select "Unmount ISO" > (unexpectedly available in the context menu because the ISO image is already > unmounted), > the ISO image is "ejected" and disappears from "Devices" section. Ok, so this is the expected behavior. The idea is that the "Mount" and "Unmount" entry on the contextual menu of the ISO file act as if you physically inserted or ejected the CD-ROM. It would be nice to be able to remove the unmounted iso file from Dolphin's Place pane directly but it is much more difficult to implement for me since it involves modifying Dolphin's code. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428392] Impossible to "eject" a mounted ISO image
https://bugs.kde.org/show_bug.cgi?id=428392 --- Comment #1 from Kwon-Young Choi --- (In reply to Patrick Silva from comment #0) > SUMMARY > When I unmount an ISO image mounted with "Mount ISO" plugin, > it remains under "Devices" section of Places panel and there is no "Eject" > option > to remove it. Reboot is the only solution. > > STEPS TO REPRODUCE > 1. open Dolphin > 2. right-click on an ISO image, choose "Mount ISO" > 3. unmount the just mounted ISO image How do you unmount the ISO image ? Do you use the Dolphin left pane called Place or do you use the contextual menu of the ISO file ? Normally, you can remove the ISO file by using the "Unmount ISO" entry of the contextual menu of the ISO file. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425319] Mounting an ISO with multiple partitions always mounts the wrong partition
https://bugs.kde.org/show_bug.cgi?id=425319 Kwon-Young Choi changed: What|Removed |Added Status|NEEDSINFO |RESOLVED URL||https://github.com/storaged ||-project/udisks/issues/725 Resolution|WAITINGFORINFO |UPSTREAM --- Comment #5 from Kwon-Young Choi --- Thanks for your additional input. For now, I'll mark this bug as resolved and add a link to the udisks issue. If you happen to open a new issue, let me know so that I can update the url. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425319] Mounting an ISO with multiple partitions always mounts the wrong partition
https://bugs.kde.org/show_bug.cgi?id=425319 --- Comment #3 from Kwon-Young Choi --- (In reply to Oded Arbel from comment #2) > > > * Can you mount your iso file using only `udisksctl` commands? > > Yes, but only the second partition: after `loop-setup`, I have /dev/loop24, > /dev/loop24p1 and /dev/loop24p2. with `sudo mount` I can mount either > /dev/loop24 (Joliet/ISO9660 file system) or /dev/loop24p2 (HFS filesystem). > I'm not sure what /dev/loop24p1 is - maybe the isolyzer or solid-hardware > output from above has some clues. When using `udisksctl mount`, only > /dev/loop24p2 successfully mounts. So I have a feeling this is indeed not a > Dolphin problem but a udisks2 problem. Could you share the output of the following commands: ``` $ udisksctl info --block-device /dev/loop24 $ udisksctl info --block-device /dev/loop24p1 $ udisksctl info --block-device /dev/loop24p2 ``` `udisksctl` has often more detailed informations than `solid-hardware`. >From what I understand of `udisksctl`, /dev/loop24 represent the partition table of the image and each additional loop device loop24p1, loop24p2 represent an different partition. I found this issue at the udisks project page: https://github.com/storaged-project/udisks/issues/725 but I am not sure if it is the exact same problem. For now, I think it is fair to say that this is a problem coming from udisks and maybe you could add a comment on that udisks issue thread. > > * Could you provide an iso file with which I could reproduce your results? > > You can mail it to me directly at my email address if you want > > (kwon-young.c...@hotmail.fr) > > It is commercial software, so I'm not sure that is a good idea, and it is > also very large. I'll email you privately and we can discuss there. Since I'm a new contributor and you do not know me, I 100% understand that. Moreover, I might not be the best person to help you since I don't know a lot about this stuff. I guess the other solution would be to switch to from udisks to another tool like fuseiso, but that would be a enormous amount of work. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425319] Mounting an ISO with multiple partitions always mounts the wrong partition
https://bugs.kde.org/show_bug.cgi?id=425319 Kwon-Young Choi changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Kwon-Young Choi --- Hello, First of all, the mountiso is just a frontend to `udisksctl` which means that if the iso is not mounted correctly, it is probably because of `udisksctl`. On my machine, I tried to create an HFS/Joliet iso image using `mkisofs`: ``` $ mkisofs -o test.iso -R -J -hfs test ``` where the `test` directory contains a single file. But I was not able to mount this iso using `udisksctl` (but `fuseiso` and `mount` worked). So I have the following questions: * Can you mount your iso file using only `udisksctl` commands? (you can use `udisksctl loop-setup -f image.iso` to create a loop device and `udisksctl mount --block-device /dev/loop1` to mount the loop device) * Could you provide an iso file with which I could reproduce your results? You can mail it to me directly at my email address if you want (kwon-young.c...@hotmail.fr) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422082] Using mountiso plugin unmount action on a mounted loop device does not remove the loop device
https://bugs.kde.org/show_bug.cgi?id=422082 Kwon-Young Choi changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |kwon-young.c...@hotmail.fr Component|general |plugins: ISO mounting -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424410] "Unmount ISO" option from the context menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=424410 Kwon-Young Choi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Kwon-Young Choi --- Hello, This is a known bug, see: https://bugs.kde.org/show_bug.cgi?id=422082 And there is an ongoing patch at: https://invent.kde.org/sdk/dolphin-plugins/-/merge_requests/2 *** This bug has been marked as a duplicate of bug 422082 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422082] Using mountiso plugin unmount action on a mounted loop device does not remove the loop device
https://bugs.kde.org/show_bug.cgi?id=422082 Kwon-Young Choi changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Kwon-Young Choi --- *** Bug 424410 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424413] "Mount ISO" feature doesn't mount an ISO image if "Enable automatic mounting of removable media" option is unchecked in Removable Devices kcm
https://bugs.kde.org/show_bug.cgi?id=424413 --- Comment #1 from Kwon-Young Choi --- Hello, Currently, this is the expected behaviour of the Mount ISO plugin. In order to mount the ISO file to a directory, you have to manually click on the new entry created in Dolphin. However, I completely agree that the default behaviour should be to automatically mount the ISO file to a directory but it is a little bit trickier to do. I have already proposed a merge request to do this: https://invent.kde.org/sdk/dolphin-plugins/-/merge_requests/8 but it is a little bit hacky and I'm not sure the maintainers will agree to do it that way. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 156534] Support renaming volumes via udisks2
https://bugs.kde.org/show_bug.cgi?id=156534 Kwon-Young Choi changed: What|Removed |Added CC||kwon-young.c...@hotmail.fr --- Comment #11 from Kwon-Young Choi --- I have made a merge request out of the patch of Orion Poplawski at https://invent.kde.org/frameworks/solid/-/merge_requests/7 Let me know if there is anything to change. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402692] Unable to *re*mount encrypted removable volumes with Dolphin after unmounting
https://bugs.kde.org/show_bug.cgi?id=402692 Kwon-Young Choi changed: What|Removed |Added CC||kwon-young.c...@hotmail.fr Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #3 from Kwon-Young Choi --- Hello, I have tried to replicate this bug but I haven't been able to reproduce the bug behavior. I can mount and unmount the luks encrypted of an usb key multiple times with dolphin without any problem. System information: Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.7.0-3-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 15.2 Gio -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422082] New: Using mountiso plugin unmount action on a mounted loop device does not remove the loop device
https://bugs.kde.org/show_bug.cgi?id=422082 Bug ID: 422082 Summary: Using mountiso plugin unmount action on a mounted loop device does not remove the loop device Product: dolphin Version: 20.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kwon-young.c...@hotmail.fr CC: kfm-de...@kde.org Target Milestone: --- SUMMARY This concerns the mountiso dolphin-plugins but I could not find the correct components. This bug concerns the unmount behavior of the mountiso plugin. Before starting, here is a schema of the workflow used to mount an iso file as a directory using the mountiso plugin in dolphin: mountiso mount/unmount action dolphin sidebar mount/unmount action | automatic | myimage.iso -> /dev/loop0 -> /dev/loop0p1 -> /run/media/user/myimage The problem here is that you can't delete the /dev/loop0 device if /dev/loop0p1 is already mounted on /run/media/user/myimage. I already have a patch for the mountiso plugin to unmount the /dev/loop0p1 device before deleting /dev/loop0 and I'll make a merge request soon. Additional questions: * Should the mount action of the mountiso plugin automatically mount the /dev/loop0p1 device to a directory? * Should the unmount action of dolphin sidebar automatically delete the /dev/loop0 device? I have already tried to automatically mount /dev/loop0p1 device to a directory when mounting using mountiso action, but I can't make it to work. After mounting the iso file to /dev/loop0, I can get the corresponding /dev/loop0p1 device but it seems that Solid does not consider to be a StorageAccess device, which means that I can't mount it to a directory. STEPS TO REPRODUCE 1. Mount iso file using mountiso mount action 2. Click on the newly appeared device on dolphin side bar (as a results, new device is mounted on a directory) 3. Go back to iso file, unmount using mountiso unmount action OBSERVED RESULT The device on dolphin side bar does not disappear. When the user unmount the device from dolphin side bar, the device disappear automatically. EXPECTED RESULT The device disappear from dolphin sidebar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.6.12-1-MANJARO (available in About System) KDE Plasma Version: latest build from source KDE Frameworks Version: latest build from source Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417909] RFE: Text and page background - dark themed
https://bugs.kde.org/show_bug.cgi?id=417909 Kwon-Young Choi changed: What|Removed |Added CC||kwon-young.c...@hotmail.fr --- Comment #1 from Kwon-Young Choi --- Hi, Just an okular user here, but I think there is already an option to change the background and foreground color in okular. Go to "Settings" -> Configure Okular -> "Accessibility". Then, tick the "Change colors" box and select "Change Dark & Light Colors" menu item in "Color mode". This will allow you to change the "Dark color" (background) and "Light color" (foreground). However, that settings comes with the warning: "Warning: these options can badly affect drawing speed". I suppose that rendering a pdf with other colors involves additional processing which could impact your battery life so I'm not sure if this is a good solution. Best regards, Kwon-Young Choi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417821] Jump Stack
https://bugs.kde.org/show_bug.cgi?id=417821 Kwon-Young Choi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417821] Jump Stack
https://bugs.kde.org/show_bug.cgi?id=417821 --- Comment #2 from Kwon-Young Choi --- Ok, this works! So, before filing this bug, I actually went and search for something in the "Configure Keyboard Shortcuts" menu under "Settings". And I saw the "Alt+Shift+Left" and "Alt+Shift+Right" shortcut for the "Back" and "Forward" action. But I confused them with the "Previous Page" and "Next Page" and did not try them myself. Thank you for your help! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417821] New: Jump Stack
https://bugs.kde.org/show_bug.cgi?id=417821 Bug ID: 417821 Summary: Jump Stack Product: okular Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: kwon-young.c...@hotmail.fr Target Milestone: --- Created attachment 126120 --> https://bugs.kde.org/attachment.cgi?id=126120=edit PDF scientific paper containing clickable citation and a bibliography at the end of the document SUMMARY Hello, This is a feature request based on my daily usage of okular to view scientific papers. Scientific papers have a lots citation which you can actually click and okular will jump to the corresponding citation usually at the end of the document. The big frustration is when you are in the middle of reading a big paper, you click on a citation, which brings you at the end of the document. However, you can't easily backtrack to the place you were earlier in order to continue to read the paper. I actually would like to help to develop such a feature (I already know a little bit of c++ and Qt but never did anything with kde apart from a little of kirigami) Thank you for your help. STEPS TO REPRODUCE 1. Open a scientific paper with clickable citations (see attachment) 2. Click on a citation (this brings you to the end of the document) 3. (Not possible yet) Jump back where you were before clicking on the citation OBSERVED RESULT Not possible to jump back after clicking on a citation. EXPECTED RESULT Ability to jump back after clicking on a citation ADDITIONAL INFORMATION Thank you all for your awesome work! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406658] Multi-screen multi-notification pop-up
https://bugs.kde.org/show_bug.cgi?id=406658 --- Comment #1 from Kwon-Young Choi --- I also found this bug: https://bugs.kde.org/show_bug.cgi?id=392669 However, for me, the number of notifications on each screen is linked to the number of panels and not on the number of screens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406658] New: Multi-screen multi-notification pop-up
https://bugs.kde.org/show_bug.cgi?id=406658 Bug ID: 406658 Summary: Multi-screen multi-notification pop-up Product: plasmashell Version: 5.15.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kwon-young.c...@hotmail.fr CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY While having a multi-screen setup, with one default plasma default panel on each screen, io-bounded notifications like ones produced by move/copy/delete operations in dolphin will produce as many notifications as the number of panel on each screen, i.e. having three screen with three panels will produce 3 notifications on each screens, which amount in a total of 9 notifications. A workaround is to disable the check box: "Track file transfers and other jobs" in each notification configuration menu of each panel (except one in order to keep at least one notification on each screen). STEPS TO REPRODUCE 1. use multiple screens 2. have one default panel on each screens 3. delete/copy/move a file using dolphin OBSERVED RESULT multiple notifications of the same event on each screen. EXPECTED RESULT one notifications of the event on each screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: manjaro (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
