[ark] [Bug 482901] New: Hangs while trying to unpack 20k+ files from .7z archive
https://bugs.kde.org/show_bug.cgi?id=482901 Bug ID: 482901 Summary: Hangs while trying to unpack 20k+ files from .7z archive Classification: Applications Product: ark Version: 23.08.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: c3i8zv...@mozmail.com CC: rthoms...@gmail.com Target Milestone: --- I have an 7-zip archive with more than 20k files, sized at 8Gib in total. In Windows, the extraction with the 7-zip Gui takes approx. 2 minutes. In Linux, the extraction with ark just hangs forever (I waited 30 minutes). This bug is related to 454268 and therefore seems to affect all archive types - could be merged. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411431] Detach Tabs / Combine multiple windows in tabs
https://bugs.kde.org/show_bug.cgi?id=411431 --- Comment #5 from Julius R. --- This is lingering on for a while, but... It would really be a great update to usability. Also, even the windows explorer is capable of this nowadays. :) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to open the filetype options while ripping audio CD.
https://bugs.kde.org/show_bug.cgi?id=253768 --- Comment #13 from Julius R. --- (In reply to Albert Astals Cid from comment #12) > But you want to change it while the ripping is happening or from that dialog > before the ripping has started? Before, of course... -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to open the filetype options while ripping audio CD.
https://bugs.kde.org/show_bug.cgi?id=253768 --- Comment #11 from Julius R. --- (In reply to Albert Astals Cid from comment #10) > Is the a point in doing that? > > I mean i understand the error should not happen but what's the rationale for > opening the configuration Window while Ripping an Audio CD? We are not talking about main program setting window, but the ripping configuration setting. Example: We want to rip an Audio CD to MP3, then you can configure the bitrate of the mp3 from the dialogue window. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 477682] When opening an Audio CD in Dolphin, kio keeps accesssing it like crazy
https://bugs.kde.org/show_bug.cgi?id=477682 Julius R. changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Julius R. --- *** This bug has been marked as a duplicate of bug 400816 *** -- You are receiving this mail because: You are watching all bug changes.
[AudioCD-KIO] [Bug 400816] Audio CD never stops spinning while Dolphin shows its contents
https://bugs.kde.org/show_bug.cgi?id=400816 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #12 from Julius R. --- *** Bug 477682 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 477682] When opening an Audio CD in Dolphin, kio keeps accesssing it like crazy
https://bugs.kde.org/show_bug.cgi?id=477682 --- Comment #2 from Julius R. --- You're probably right. Sorry, I missed 400816. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 477682] New: When opening an Audio CD in Dolphin, kio keeps accesssing it like crazy
https://bugs.kde.org/show_bug.cgi?id=477682 Bug ID: 477682 Summary: When opening an Audio CD in Dolphin, kio keeps accesssing it like crazy Classification: Frameworks and Libraries Product: kio-extras Version: 23.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: AudioCD Assignee: plasma-b...@kde.org Reporter: c3i8zv...@mozmail.com CC: yurc...@ukr.net Target Milestone: --- SUMMARY When opening an Audio CD in Dolphin, we are presented with the neat system of folders for automatic ripping (which is superconfusing and bloated for a normal user, who does not expect this imho, but that's another matter). After that, kio (?) keeps accessing and reading the disk, probably due to a CDDB lookup. But: It never stops! I waited 15 minutes and the drive keeps on clacking and reading, as long as Dolphin is open. The problem presented here is: When trying to rip one audio file, it takes hours (due to the constant access on the drive). The CD is absolutely fine! When closing dolphin and using a third party tool to rip (like K3b or Asunder), it works fine and is finished within minutes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (Manjaro) Kernel 6.6.2-1 KDE Plasma Version: 5.27.9 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to open the filetype options while ripping audio CD.
https://bugs.kde.org/show_bug.cgi?id=253768 Julius R. changed: What|Removed |Added Summary|Error when trying to change |Error when trying to open |the bitrate of an audio cd |the filetype options while |being ripped to mp3.|ripping audio CD. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to change the bitrate of an audio cd being ripped to mp3.
https://bugs.kde.org/show_bug.cgi?id=253768 Julius R. changed: What|Removed |Added Component|Plugins |Copying Platform|openSUSE|Manjaro CC||mich...@jabster.pl Version|2.0.1 |23.08.3 --- Comment #9 from Julius R. --- Sorry, I meant version 23.08.3-2 of course. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to change the bitrate of an audio cd being ripped to mp3.
https://bugs.kde.org/show_bug.cgi?id=253768 Julius R. changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||c3i8zv...@mozmail.com --- Comment #8 from Julius R. --- I have the same problem - and it's not resolved. When trying to open the configuration Window while Ripping an Audio CD (no matter which filetype is the selected) it results in the following error: " Possible reasons: - An error occured during your last system upgrade, leaving an orphaned control module behind - You have old third party modules lying around Check these points carefully and try to remove the module mentioned in the error message if this fails consider contacting your distributor or packager. " And that's it. No hint to what is going on there. System Info: Arch (Manjaro) Kernel 6.6.2-1 KDE Plasma 5.27.9 QT Version 5.15.11 K3b v. 1.23.08.3-2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #28 from Julius R. --- I also still experience this bug. When mounting a drive with $ veracrypt or $ cryptsetup, the drive will be shown with the unmount icon. Unmounting an encrypted drive accidently can cause serious data corruption! This icon MUST go. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468749] "Selection mode" shortcuts are not changeable / can not be disabled
https://bugs.kde.org/show_bug.cgi?id=468749 --- Comment #2 from Julius R. --- (In reply to Felix Ernst from comment #1) > See https://bugs.kde.org/show_bug.cgi?id=466050 for details. Is it okay for > you if I mark this bug report as a duplicate? Of course, sorry, I've missed that one! > > >Further, it might be a good idea to prevent hardcoded changes for keyboard > >shortcuts in the future, possibly by introducing respective design > >guidelines? > > Don't worry, there is no interest in hardcoding shortcuts if this can be > prevented. In this case it was a quick change to fix two potentially bigger > bugs in a smaller update which we knew would cause this smaller bug. Then I am relieved. I had no idea about the bug avalanche in the background, makes all sense now. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468749] New: "Selection mode" shortcuts are not changeable / can not be disabled
https://bugs.kde.org/show_bug.cgi?id=468749 Bug ID: 468749 Summary: "Selection mode" shortcuts are not changeable / can not be disabled Classification: Applications Product: dolphin Version: 22.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Selection Mode Assignee: kfm-de...@kde.org Reporter: c3i8zv...@mozmail.com CC: felixer...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. I recently noticed, that hardcoded keyboard shortcuts (space, F2) were introduced in Dolphin, activating the so called "selection mode". CHANGE PROPOSAL As for as I understand, it is the design philosophy of KDE to be customizable in mosts aspects, especially regarding the workflow of the user. Actually, this is the selling point (imho) that distinguishes it from DEs like GNOME. I therefore would kindly propose the idea of: Adding the ability to change or disable the selection mode shortcut. Further, it might be a good idea to prevent hardcoded changes for keyboard shortcuts in the future, possibly by introducing respective design guidelines? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.2.10-1 Manjaro KDE Plasma Version: 5.27.4 Qt Version: 5.15.8 ADDITIONAL INFORMATION Thanks to all developers for their hard work! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465763] The installation folder can not be changed
https://bugs.kde.org/show_bug.cgi?id=465763 --- Comment #4 from Julius R. --- (In reply to Ben Bonacci from comment #3) > After some more testing, I stumbled upon something. If the vault location is > selected with the file dialog button (which is what I done initially), there > are no errors and the vault gets created successfully. However if a file > path is typed out manually (which is what the reporter is doing), then the > "this specified path does not exist" error appears. > When typing the file path, it has to point to an empty folder (without > *.enc) to be accepted. What is confusing to me is that the default path > provided has *.enc added to the end (ironically it doesn't actually exist > yet), which is implying to the end user that it also needs to be added to > the new path, which causes the error if they do so. > > I don't know if this is a bug per-se, but it does cause some confusion. I'd rather say broken (or not optimized) than confusing. :) a) When entering a path manually (as I did) that actually does exist, it still shows the error "path does not exists". b) Contrary to your observation, the error also occurs when not providing the *.enc file at the end of a path. Suggestion: When a user enters a path that does not exists, it should just silently create it - or at least ask the user, if he wants to create it. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465763] The installation folder can not be changed
https://bugs.kde.org/show_bug.cgi?id=465763 --- Comment #2 from Julius R. --- Created attachment 156358 --> https://bugs.kde.org/attachment.cgi?id=156358=edit Screenshot of the error Steps to reproduce: 1. Install plasma-vault and gocryptfs via pamac 2. Rebooting 3. Create a new vault, name 'test', setting password 4. Trying to change the path of either the encrypted data location or the mount point results in error 'The specified path does not exist'. It occurs immediately, when changing the first letter of the defaults. It also does not matter, wether the new path / folder exists, or not. See attached screenshot. System: Kernel: 6.1.11-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux CPU: Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: ZOTAC driver: nvidia v: 525.89.02 arch: Ampere pcie: speed: 16 GT/s lanes: 16 bus-ID: 2d:00.0 chip-ID: 10de:2484 class-ID: 0300 Display: x11 server: X.Org v: 21.1.7 compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0 screens: 1 API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2 direct-render: Yes Drives: Local Storage: total: 2.96 TiB used: 576.48 GiB (19.0%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: rev: 2B2QEXM7 temp: 25.9 C scheme: GPT ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: rev: 2B2QEXM7 temp: 44.9 C scheme: GPT ID-3: /dev/sda vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB speed: 6.0 Gb/s type: SSD serial: rev: 2B6Q scheme: GPT Partition: ID-1: / size: 227.88 GiB used: 54.11 GiB (23.7%) fs: ext4 dev: /dev/nvme1n1p2 ID-2: /boot/efi size: 299.4 MiB used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465763] New: The installation folder can not be changed
https://bugs.kde.org/show_bug.cgi?id=465763 Bug ID: 465763 Summary: The installation folder can not be changed Classification: Plasma Product: Plasma Vault Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: c3i8zv...@mozmail.com Target Milestone: --- When setting up a Vault, the installer denies changing the installation folder. When changing it from its default $user/.local/share/plasma-vault/...and so on, it throws the error "the specified path does not exist". So, for me, this renders the software useless. For security reasons and drive space restrictions, I need to store the vault files on another folder. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 449178] KCM and Applet no longer show paired devices after turning bluetooth off and on again; have to restart plasmashell or leave/return to the KCM
https://bugs.kde.org/show_bug.cgi?id=449178 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #22 from Julius R. --- (In reply to Nate Graham from comment #21) > BTW I can also confirm the fix after upgrading to bluez-5.64-1. Sorry for resurrecting this, but I am running bluez 5.66-1 here and the error still occurs to me occasionally: Sometimes, when I start KDE, the Bluetooth ist activated, but unpopulated. In the system settings, the Enable Button can be seen, but nothing happens when clicking it. I tried $ rmod btusb and then $ modprobe btusb, but to no avail. Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 450154] LPD printer discovered but address/queue fields are empty
https://bugs.kde.org/show_bug.cgi?id=450154 --- Comment #2 from Julius R. --- My guess is, that this is DNSSD related... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371130] unable to reassign standard shortcut for backspace to "up" instead of "back"
https://bugs.kde.org/show_bug.cgi?id=371130 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #17 from Julius R. --- +1 for swapping Backspace and Back. Count me in on this one. This is hellishly annyoing. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 462626] Dual Monitor setup: Primary Display does not wake up after energy save mode
https://bugs.kde.org/show_bug.cgi?id=462626 --- Comment #3 from Julius R. --- (In reply to Nate Graham from comment #1) > Are one or both displays connected to an NVIDIA GPU, by any chance? You are right, it is probably 460341. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 462626] Dual Monitor setup: Primary Display does not wake up after energy save mode
https://bugs.kde.org/show_bug.cgi?id=462626 --- Comment #2 from Julius R. --- (In reply to Nate Graham from comment #1) > Are one or both displays connected to an NVIDIA GPU, by any chance? Hi Nate, both are connected to one Nvidia RTX 3070 indeed. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 450154] LPD printer discovered but address/queue fields are empty
https://bugs.kde.org/show_bug.cgi?id=450154 Julius R. changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 450154] LPD printer discovered but address/queue fields are empty
https://bugs.kde.org/show_bug.cgi?id=450154 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #1 from Julius R. --- I can confirm this behaviour. Yet again, another function broken that once worked. ;( Manjaro, 6.0.8-1 Kernel, Plasma 5.26.3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 462626] Dual Monitor setup: Primary Display does not wake up after energy save mode
https://bugs.kde.org/show_bug.cgi?id=462626 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 462626] New: Dual Monitor setup: Primary Display does not wake up after energy save mode
https://bugs.kde.org/show_bug.cgi?id=462626 Bug ID: 462626 Summary: Dual Monitor setup: Primary Display does not wake up after energy save mode Classification: Plasma Product: KScreen Version: 5.26.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: c3i8zv...@mozmail.com Target Milestone: --- I am using 2 Displays: One is connected as primary on DP4, the other one is a secondary display in another room, connected via HDMI1. When the displays are powered off due to energy saving schedule, the primary display does not wake up again. When triggering the wake up (mouse movement, key input), the displays both get powered up again (as can be seen by the stanby LEDs), but the primary stays black. In the .local/share/kscreen config file, the line with "enabled" seems to be stuck at "false". Once I manually unplug the second display (HDMI1), the primary display shows the desktop again. Complete Bug description with steps taken to alleviate: https://forum.manjaro.org/t/monitor-does-not-turn-back-on-after-energy-saving/128030/4 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #36 from Julius R. --- I doubt that this bug is resolved, nor fixed. I am running Manjaro with a dual screen setup and just recently updated to 5.26.3. After updating to the forementioned version from 5.25, my main screen did not wake up after energy save mode. I made a fresh reinstall of the system, then it became even worse: The primary monitor would not be recognized at all at boottime! I found that the config in .local/share/kscreen was messed up. No matter if I choose the primary to display to be "primary" and "enabled" in the GUI system settings, kscreen did neither apply the setting and / pr forgot about it (probably never saved the setting in the config file). I changed the setting manually from false to true, now it works as expected. See this thread for further explanation https://forum.manjaro.org/t/monitor-does-not-turn-back-on-after-energy-saving/128030/9 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #15 from Julius R. --- Absolutely impressive! Thanks to all involved -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #11 from Julius R. --- (In reply to Thomas from comment #10) > So I guess the question/rub for me - is why did this have to change..?? Put > the code that handled this back the way it was. > Seemed to work perfectly before. So why was it "fixed". > > If I want to unmount a physical drive attached to a SATA cable screwed into > the case of the computer and mounted via FSTAB - I should need to do more > that just click an always visible Unmount icon cluttering up the view in > Dolphin. Whether in fact clicking that Icon intentionally or accidentally > will or will not cauise additional dialogue to prevent the Unmount. > > If I plug a Thumb Drive or some other USB Storage device, with no > over-riding FSTAB entry to make it a "permanent" drive - then an Unmount > Icon makes absolute sense. > > Just like it worked a few days ago. > > Thanks! I second every word of that comment! As can be seen in my bug duplicate above, this little changed caused several - even critical - disturbances. A solid drive, that is integrated in the system (like network drives in a company) should not be unmountable with a single click. Imho :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 453894] Disk can be ejected while files on it are still being read from or written to
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #11 from Julius R. --- (In reply to Nate Graham from comment #10) > No, we can't guess the future, but we can prevent ejecting a disk that still > has files on it being actively read or written to. > > Are you saying that this happened on a disk that did *not* have any files on > it being read or written at the moment you clicked the eject button? > > Are you saying you want what's being requested in Bug 453890? Yes. Sorry for the hassle. This is a duplicate of 453890. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 453894] Disk can be ejected while files on it are still being read from or written to
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #9 from Julius R. --- (In reply to Nate Graham from comment #8) > That shouldn't happen. Since the system is aware of open files, if you try > to unmount a disk that has open files on it, it's supposed to prevent that > from happening. If that didn't work and you were able to unmount a disk with > open files, that's a bug. That's the bug that we're tracking with this > Bugzilla ticket. More misunderstandings :) The system is surley aware of open files, there is no bug with that. It can not anticipate that files "might" be opened or accessed soon... The inconvenience I describe happens (apart from the critical synology bug), when files are not available at a specific time, due to accidently unmounting the drive. If, to give that example again, config files (the user profile) for e.g. Firefox are stored on an encrypted drive (or in a company on a network drive) - and that drive is not available due to a user accidently and unknowingly unmounting drives, then the browser gives an error: It simply can not find the user profile. There is neither file activity before or after, there are no open file activities. The problem described is btw exactly, what happenend to my mum: She accidently unmounted the drive and then didn't know, what to do. Due to the small little change of adding an unmount icon, I - personally - experienced a critical data loss (I had backups, of course). This was a bug of a third party software, that no one could foresee. On the other hand, I also had problems with a less experienced user, that did not understand the concept of mounting and unmounting - at all. Therefore, I stand by my suggestion: Network Drives and Encrypted Drives should never ever have a "quick-unmount-icon". Unlike usb flash drives (which are used only temporarily), network drives and (un)encrypted drives are (in most use cases) an integrated part of the users workflow. They need to be accessible at all times, from boot till shutdown. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 453894] Disk can be ejected while files on it are still being read from or written to
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #7 from Julius R. --- Thanks for the clarification. I do believe, this bug report should be closed as resolved now? Reason: As you described KDE is aware of file operations and disallows unmounting (as it should), when there are operations running (like copying). My point is a different one: That it can lead to unwanted behaviour, if a mounted drive gets unmounted accidently, if other software relies on it. For example, a browser does not start anymore, when the config files have been stored on that particular drive, which is mounted at boot. There is also no file-operation in my case of data-loss, which was a critical bug in synologys software (I circumvented this now with a little script, that kills the synology client, whenever it detects, that the drive is no longer mounted). So, summarized a) There is no way for the system to anticipate the complications described above. They just happen and are not related to file operations. b) When the majority of users is fine with the eject icon luring dangerously over every mounted drive, folder and device - then that is the way it is and it should stay. :) Thanks Nate! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to unexpected behaviour.
https://bugs.kde.org/show_bug.cgi?id=453894 Julius R. changed: What|Removed |Added Summary|Eject Symbol next to mount |Eject Symbol next to mount |drives can lead to |drives can lead to |catastrophic data failures! |unexpected behaviour. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #5 from Julius R. --- Let me rephrase that: Unmounting drives with one click, is convenient - if the user knows what he is doing. For example, by triggering the context menu. Unmounting drives with one click by accidently (!) clicking on a pictogram, can be a problem. Imho :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #4 from Julius R. --- Yes, it did. This is a freak case, but when using synology drive client on a mounted drive (synchronisation tool for a local or remote NAS) and the local source gets unmounted while the app is running, it acknowledges the emptiness as a command to delete all files at target. This is, obviously, unwanted behaviour and a critical bug within the synology software. But I stand by my point, a locally mounted drives should not be dismounted without confirmation. It must not always be critical, it could also be simply inconvenient. Imagine this use case: A user has an encrypted drive. For dual-boot purposes, this is done with veracrypt. The decrypted drive will now appear as mounted device. On this drive, the user stores config files from mozilla, work files, sensible settings from other programs etc etc. If this drive can be randomly unmounted by accidently clicking on it in the file explorer (dolphin), that can be quite an annoyance... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #2 from Julius R. --- Hi Nate, you are right, when the file process is handled by plasma, this does not pose a problem. False assumption by me, sorry. The other problems remain however: Whenever a service or third party application depends on the mounted drive "being there", an accidental unmount can lead to serious problems. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453894] New: Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 Bug ID: 453894 Summary: Eject Symbol next to mount drives can lead to catastrophic data failures! Product: dolphin Version: 22.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: c3i8zv...@mozmail.com CC: kfm-de...@kde.org Target Milestone: --- Hi everyone, I don't know who and why this has been green flagged, but the newest addition of an eject button next to mounted drives (not USB drives, hard drives! Meaning all network folders, all additional mounted volumes!) is an terrible idea! It is really mindbuffling dangerous. A normal user - like my mom - could (has) accidently click on them way, way to easily. For there is no dialogue of confirmation (!), the drive gets onhooked immediately. An ongoing copy process could lead to data corruption. Running services relying on the drive could lead to data corruption. Imagine for example having a syncing software running. Like synology drive? When the drive is unmounted without shutting it down beforehand, the syncing software might (I know it does, it is badly written) interpret the missing drive as deleted files, meaning, it deletes the files on the synced target. And so on and so on. This should definetly not be there for hard drives and if, it needs a confirmation for unmounts. Cheers and have a nice day. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #95 from Julius R. --- Isecond the bug. In my case, the login sound is completely gone on two different systems (running latest plasma). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Julius R. changed: What|Removed |Added Platform|Archlinux Packages |Manjaro Version|5.17.2 |5.24.3 --- Comment #24 from Julius R. --- I also have the same or a similar problem: After the last update (strangely enough from 5.24.2 to 5.24.3), my Desktop widget (a clock) keeps getting reset after every restart to the upper left corner of my screen. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 450230] Improve cover and flip switch
https://bugs.kde.org/show_bug.cgi?id=450230 Julius R. changed: What|Removed |Added CC||c3i8zv...@mozmail.com --- Comment #4 from Julius R. --- I absolutely second the statements above. I was excited to see the QML rewrite of the Cover Switch effect, but it does fall a bit short in comparison to the old effect. It is good, but things like blur, window size, and margins should be configurable. It seems, this effect has not been designed with different resolutions and screen aspect ratios in mind. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 433470] New: Desktop Context Menu has "Leave" Option? What the...
https://bugs.kde.org/show_bug.cgi?id=433470 Bug ID: 433470 Summary: Desktop Context Menu has "Leave" Option? What the... Product: frameworks-plasma Version: 5.79.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: priv...@sharklasers.com CC: plasma-b...@kde.org Target Milestone: --- It seems that it has been around since Plasma 4, but now, for the first time, I had the premiere of accidently finding (and clicking on) "leave" in the context menu. Thank god it did not ask for confirmation, so yeah, all my work is lost. Good stuff. Who thought, that it would be a good idea to shut down the system from the desktops context-menu? That entry is a) cluttering and b) should not ever be there in the first place (imho) and if it must be there it c) should definitely and absolutely always (!) ask for confirmation, no matter what the global setting might be. SOFTWARE/OS VERSIONS KDE manjaro latest -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 Julius R. changed: What|Removed |Added Version|5.18.5 |5.20.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 Julius R. changed: What|Removed |Added CC||priv...@sharklasers.com --- Comment #18 from Julius R. --- Same problem here. This is critical for everyday usage, it is a bit strange, that it has not been adressed as priority. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424748] New: Option to change default zoom level
https://bugs.kde.org/show_bug.cgi?id=424748 Bug ID: 424748 Summary: Option to change default zoom level Product: krita Version: git master Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: priv...@sharklasers.com Target Milestone: --- I found some remarks about this in years old threads at reddit, as today, it is still not possible to change the default zoom level for starting / opening new documents. I work with smaller graphics most of the time and it feels very unintuitive, having to reset the zoom to 100% each time - it is of course possible to use a shortcut or toolbar button, but that's one unecessary click ;) Thank you all for this grande piece of open-source software. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420905] New: Feature Request: Please support more than two audio channels (5.1 support)
https://bugs.kde.org/show_bug.cgi?id=420905 Bug ID: 420905 Summary: Feature Request: Please support more than two audio channels (5.1 support) Product: kdenlive Version: 20.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: kont...@juliusreich.de Target Milestone: --- Dear KDE developers, first of all: Thank you all for your brilliant work! I would have loved to said goodbye to Adobe forever, but unfortunately, KDEnlive does not support 5.1 audio channels (more than stereo atm). That is most unfortunate, for it denies the usage in professional surroundings. :) I really hope, this will be implemented in future versions. KDEnlive should gain far more widespread. Cheers Julius -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 382606] when changing a larger file in an archive, Ark asks for confirmation twice
https://bugs.kde.org/show_bug.cgi?id=382606 Julius R. changed: What|Removed |Added Version|17.12.3 |20.04.0 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 391749] Impossible to resize columns
https://bugs.kde.org/show_bug.cgi?id=391749 Julius R. changed: What|Removed |Added Version|17.12.3 |20.04.0 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 391749] Impossible to resize columns
https://bugs.kde.org/show_bug.cgi?id=391749 Julius R. changed: What|Removed |Added CC||kont...@juliusreich.de --- Comment #10 from Julius R. --- I completely second the notion of the bug reporter. It is more than inconvenient that columns can neither be resized, nor hidden or shown individually. Software should meet up to todays standards, especially when we take into regard, that the main reason to promote opensource to everyday users is the flexibility and customizabilty imho... which is painfully missing here. It's always the small details. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 382606] when changing a larger file in an archive, Ark asks for confirmation twice
https://bugs.kde.org/show_bug.cgi?id=382606 Julius R. changed: What|Removed |Added CC||kont...@juliusreich.de --- Comment #13 from Julius R. --- I experience the same bug. Everytime a file is modified and written back to the archive, ark asks twice for confirmation. Running Manjaro with KDE Plasma 5.18.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406569] Elide tab title on the left when displaying full paths
https://bugs.kde.org/show_bug.cgi?id=406569 --- Comment #7 from Julius R. --- Whoa, that was fast. Thank you very much! Have a nice easter time. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406569] Elide tab title on the left when displaying full paths
https://bugs.kde.org/show_bug.cgi?id=406569 --- Comment #5 from Julius R. --- Stop. Stupid me! I am too tired. We are misleading each other. I am not talking about the location pane. I am talking about the TABS! The circled path in the tabs! Think about the following: You have four tabs open. Now you want to drag and drop on file from your current view, to one of the four tabs. I mean, literally, clicking file test.xyz, dragging to a TAB (!) and releasing it right there. How is a user supposed to know, what folder that tab is? Have a look at the screenshot, it is impossible to tell. We see the root of the tabs folders, but not the folders name of the open tabs! The problem is NOT the location bar, it is the abbreviated display of names in the tabs themselves :) Cheers -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406569] Elide tab title on the left when displaying full paths
https://bugs.kde.org/show_bug.cgi?id=406569 --- Comment #4 from Julius R. --- Oh my... I am ashamed, the most important info is missing: That I am using the "show full path in titlebar" option. Sorry! Yeah, of course, switching to current folder works - I am using this right now. But still, when having the full path enabled, it should be text-align: right :) Just for logical and obvious reasons. Have a nice weekend. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406569] Feature Requests for a more intuitive user experience #01 Text alignment of tabs
https://bugs.kde.org/show_bug.cgi?id=406569 --- Comment #2 from Julius R. --- Created attachment 119491 --> https://bugs.kde.org/attachment.cgi?id=119491=edit Left aligned tab description... I am unwilling to believe, no one ever stumbled across this problem? With left aligned text in tabs, there is no way to differentiate between the folders of other open tabs. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406570] New: Feature Requests for a more intuitive user experience #02 Drag & Drop Tabs
https://bugs.kde.org/show_bug.cgi?id=406570 Bug ID: 406570 Summary: Feature Requests for a more intuitive user experience #02 Drag & Drop Tabs Product: dolphin Version: 18.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kont...@juliusreich.de CC: elvis.angelac...@kde.org Target Milestone: --- Dear Developers, as usual: First of all kudos for your efforts to the community! :) My second proposal for improved usability: It is at the moment not possible to detach or attach tabs via drag and drop. This has become a quite common feature for tab enviroments, e.g. Firefox or other file managers. This feature would highly increase the workflow. With regards -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406569] New: Feature Requests for a more intuitive user experience #01 Text alignment of tabs
https://bugs.kde.org/show_bug.cgi?id=406569 Bug ID: 406569 Summary: Feature Requests for a more intuitive user experience #01 Text alignment of tabs Product: dolphin Version: 18.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kont...@juliusreich.de CC: elvis.angelac...@kde.org Target Milestone: --- Dear Developers, first of all: kudos for your efforts to the community! :) My feature request: When using multible tabs, the text-align of the folders name is left. This is sth the (evil) windows explorer does better. With large folder structures, the left-aligned text shows the root of the tabs folder. This obscures the name of the folder, which the user is currently looking at. Example: /home/user/documents/private/finances/2019 becomes /home/user/documents/private/... instead if .../documents/private/finances/2019 The text aligment should be right, to keep the focus on the working folder in view. Imagine having these two folders open: /home/user/documents/private/finances/2019 /home/user/documents/private/finances/2018 There is no way to distinguish them, with left aligned text, which results in two tabs stating: /home/user/documents/private/... /home/user/documents/private/... With regards -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406538] Feature Requests for a more intuitive user experience
https://bugs.kde.org/show_bug.cgi?id=406538 --- Comment #2 from Julius R. --- Thank you for your kind response, I will reopen #01 and #02 as seperate posts. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406538] New: Feature Requests for a more intuitive user experience
https://bugs.kde.org/show_bug.cgi?id=406538 Bug ID: 406538 Summary: Feature Requests for a more intuitive user experience Product: dolphin Version: 18.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kont...@juliusreich.de CC: elvis.angelac...@kde.org Target Milestone: --- Dear Mr Penz, Reininghaus, Pescocsta and Angelaccio, first and foremost I would like to express my deepest gratitude for your contribution to the world, which is in this case, one of the best filemanagers for Linux. It is people like you who make it possible for someone like me, to finally get rid of proprietary systems and corporations - in my case, switching from Windows to Manjaro Linux and KDE. Thank you! But, not all is evil in the Windows world and there are some cases, in which we can learn from. I noticed a couple of possible improvements, which will certainly lead to an even better, more intuitive user experience. My feature requests are: 1) When using multible tabs, the text-align of the folders name is left. This is sth the windows explorer does better. With large folder structes, the left-aligned text shows the root of the tabs folder, it obscures the name of the folder, the user is currently looking at. The text aligment should be right. Example: /home/user/documents/private/finances/2019 becomes /home/user/documents/private/... instead if .../documents/private/finances/2019 2) It is not possible to detach or attach tabs via drag and drop. This is a quite common feature for all tab enviroments, e.g. Firefox or other file managers. This feature would highly increase the workflow. 3) This is the best feature I ever found in a filemanager: Incremental inline search. I stumbled across this in an addon called qttabs for windows explorer. What it does is primarily searching for a filename, while typing it. But not restricted to the beginning of the file. Example: kwalletmanager.ending. If the user types "wallet" or "walletmanager" it will not be found. Incremental inline search would be a feature, that would skyrocket usability. Of course, it must be restricted to folders with less than (n) number of files for performance reasons, but still, this feature became a must have for me and I severely miss it, now that I switched to KDE. 4) A simple, but undescribebly useful workflow function: Go one level up, when double clicking on white space within a folder. This also comes from qttabs for windows explorer and it increased my workflow tremendously. That is all from side :) Again, thank you very much for your hard efforts! With regards Julius R. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 405470] Logout sound is not played under certain conditions
https://bugs.kde.org/show_bug.cgi?id=405470 --- Comment #2 from Julius R. --- (In reply to Kai Uwe Broulik from comment #1) > We migrated notifications to use libcanberra which is a low-latency audio > library. As such it only supports a limited number of codeces, such as OGG > Vorbis. Thank you for the information, that solves the mystery. In that case, wouldn't it be user friendly to restrict the selection of filetypes to supported only? This was very confusing, for there is no error and the preview works fine with other codecs. -- You are receiving this mail because: You are watching all bug changes.