[plasma-pa] [Bug 486413] Headphones default and switch to "Line Out" mode
https://bugs.kde.org/show_bug.cgi?id=486413 --- Comment #3 from Wilbur Jaywright --- Correction: But, not if I scroll over the volume icon at least once before in the session to change the volume that way. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486413] Headphones default and switch to "Line Out" mode
https://bugs.kde.org/show_bug.cgi?id=486413 --- Comment #2 from Wilbur Jaywright --- correction: It switches back to Line Out EVERY time I change the volume with the keyboard buttons. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486413] Headphones default and switch to "Line Out" mode
https://bugs.kde.org/show_bug.cgi?id=486413 --- Comment #1 from Wilbur Jaywright --- Correction: If the headphones were plugged in, and I unplug them, then plug them back, they act like they are in Headphone mode until I change the volume. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486413] New: Headphones default and switch to "Line Out" mode
https://bugs.kde.org/show_bug.cgi?id=486413 Bug ID: 486413 Summary: Headphones default and switch to "Line Out" mode Classification: Plasma Product: plasma-pa Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zargulthewiz...@outlook.com CC: isma...@gmail.com, m...@ratijas.tk Target Milestone: --- SUMMARY Whenever I plug headphones into the front jack on my desktop (I have speakers connected to the true line out in the back), as of Plasma 6 they now always default to Line Out, but now they've been bug glitching back to Line Out after I switch them to Headphones mode, or even acting like Headphones mode for a bit when they said they were set to Line Out, and then "realizing" and doing Line Out mode. STEPS TO REPRODUCE 1. Have speakers connected to the line out jack. 2. Plug earbuds into the headphone jack. 3. Check the applet. They will show in Line Out mode, though they may act like Headphone mode for a bit. 4. Switch them to Headphones mode. 5. After about a minute, they may glitch and switch back to Line Out, and have to be changed again (only happens once). EXPECTED RESULT The headphone jack defaults to Headphones mode, and stays where it is set when nothing was unplugged. SOFTWARE/OS VERSIONS Windows: X macOS: X Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Using Realtek audio hardware. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 480818] kcm-wacomtablet does not work with the Wacom One Pen Dispaly 2023 models
https://bugs.kde.org/show_bug.cgi?id=480818 Wilbur Jaywright changed: What|Removed |Added CC||zargulthewiz...@outlook.com --- Comment #1 from Wilbur Jaywright --- Installing xorg-x11-drv-wacom and libwacom-utils (did not test individually) fixed my issue Thankfully. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459494] Cannot add Brother printer over network: Configuration completes, but no printer is added
https://bugs.kde.org/show_bug.cgi?id=459494 --- Comment #2 from Wilbur Jaywright --- I have since abandoned Neon for Fedora, and Plasma 6 is not released for that yet. However, network scanning was recently failing, until I checked and saw that the printer was telling me I might need to reconfigure my firewall. I allowed the ports through the firewall that Brother recommended upon searching online for them, and now scanning works. I didn’t try adding the printer over the network on this distro recently, but it worked when I tried it just now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478911] KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close
https://bugs.kde.org/show_bug.cgi?id=478911 --- Comment #5 from Wilbur Jaywright --- Yeah, it was. Not sure why a second reboot fixed it, but if it happens again, I’ll let you know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478911] KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close
https://bugs.kde.org/show_bug.cgi?id=478911 --- Comment #3 from Wilbur Jaywright --- This seems to have been fixed by a simple reboot? I had already done the normal reboot after updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478911] KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close
https://bugs.kde.org/show_bug.cgi?id=478911 --- Comment #2 from Wilbur Jaywright --- Created attachment 164383 --> https://bugs.kde.org/attachment.cgi?id=164383=edit Developer info from the crash handler (Wayland) Dude, I tried using Wayland, and the same thing happened, but startplasma-wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478911] KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close
https://bugs.kde.org/show_bug.cgi?id=478911 --- Comment #1 from Wilbur Jaywright --- Created attachment 164381 --> https://bugs.kde.org/attachment.cgi?id=164381=edit Developer info from the crash handler -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478911] New: KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close
https://bugs.kde.org/show_bug.cgi?id=478911 Bug ID: 478911 Summary: KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: zargulthewiz...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 164380 --> https://bugs.kde.org/attachment.cgi?id=164380=edit What I see on login SUMMARY So, I log in, and KDE Crash Handler reports that startplasma-x11 died due to a segmentation fault. The desktop works normally, until I close the crash handler window, at which point Plasma crashes within a few seconds, throwing me back out to SDDM. STEPS TO REPRODUCE 1. Log in. 2. Close the appearing crash handler window. OBSERVED RESULT Plasma is ded. EXPECTED RESULT Plasma is not ded (and the crash handler never shows up in the first place). SOFTWARE/OS VERSIONS Windows: X macOS: X Linux/KDE Plasma: Fedora 39 x64 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Using NVidia proprietary drivers. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 475266] When trying to activate broken desktop files an assert in libdbus is hit
https://bugs.kde.org/show_bug.cgi?id=475266 --- Comment #17 from Wilbur Jaywright --- Clicking Firefox in Kickoff search results does the same thing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475295] New: Clicking Firefox on the desktop panel to launch it resets the panel
https://bugs.kde.org/show_bug.cgi?id=475295 Bug ID: 475295 Summary: Clicking Firefox on the desktop panel to launch it resets the panel Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: zargulthewiz...@outlook.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY So, Firefox is pinned to the main panel by default, right? Or, you can add it as a widget. Right now, if I click it, the desktop goes back and the panel closes and reopens (and Firefox isn't launched). Launching from Kickoff doesn't do this. STEPS TO REPRODUCE 1. Click Firefox on the main panel. 2. Boom. OBSERVED RESULT The desktop goes black, and the panel closes and re-opens. No error messages. EXPECTED RESULT Firefox opens. SOFTWARE/OS VERSIONS Windows: No macOS: No Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I am using X11 with two monitors. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 389766] Weather widget does not show the temperature beside or over the icon in the Plasma panel when I use wetter.com provider
https://bugs.kde.org/show_bug.cgi?id=389766 Wilbur Jaywright changed: What|Removed |Added CC||zargulthewiz...@outlook.com --- Comment #10 from Wilbur Jaywright --- Same problem, NixOS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #22 from Wilbur Jaywright --- Ah, too many cooks spoiling the broth, eh? All right, I’ll ask in said forum. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #20 from Wilbur Jaywright --- Notably, the problem did not occur on first boot this time, only after logging back out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #19 from Wilbur Jaywright --- Created attachment 159524 --> https://bugs.kde.org/attachment.cgi?id=159524=edit Output from command drm_info at login with only one monitor with problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #18 from Wilbur Jaywright --- Pretty sure both monitors were connected. Will check again. Should I wait until the problem does occur to do it, though? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469417] Ark cannot extract password-protected RAR archives
https://bugs.kde.org/show_bug.cgi?id=469417 Wilbur Jaywright changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #16 from Wilbur Jaywright --- Was having kind of similar issue in Wayland desktop. Now with no tablet connected and all background apps closed, I finally got a clean session running. Note that the background apps should NOT cause such performance lag. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #15 from Wilbur Jaywright --- Note, I am still having this problem with only one monitor, but it has been strictly of the kind where clicking on another user account icon clears it up. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 461844] Menu editor crashes SOME OF THE TIME when I save
https://bugs.kde.org/show_bug.cgi?id=461844 --- Comment #5 from Wilbur Jaywright --- Created attachment 159226 --> https://bugs.kde.org/attachment.cgi?id=159226=edit New crash information added by DrKonqi kmenuedit (5.27.5) using Qt 5.15.9 I had deleted some desktop entrys, but they may have been removed after I opened Kmenuedit via their wine uninstallers and before I clicked save. Does the save button affect all actions, or just edits within an entry? -- Backtrace (Reduced): #4 0x7fb7693b5954 in KService::desktopEntryName() const () from /lib64/libKF5Service.so.5 #5 0x5641c0424e2e in GlobalAccel::changeMenuEntryShortcut(QExplicitlySharedDataPointer const&, QKeySequence const&) () #6 0x5641c04303be in MenuFolderInfo::save(MenuFile*) () #7 0x5641c0435047 in TreeView::save() () #8 0x7fb767ce87d8 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 461844] Menu editor crashes SOME OF THE TIME when I save
https://bugs.kde.org/show_bug.cgi?id=461844 Wilbur Jaywright changed: What|Removed |Added CC||zargulthewiz...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469417] Ark cannot extract password-protected RAR archives
https://bugs.kde.org/show_bug.cgi?id=469417 --- Comment #7 from Wilbur Jaywright --- So, extraction seems to work in Ark with unrar installed, but notably progress hangs at 50% until extraction completes. Also, I feel that if unrar is a dependency it should be marked as such somehow, rather than giving the erroneous "wrong password or not enough space" error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #13 from Wilbur Jaywright --- Created attachment 159011 --> https://bugs.kde.org/attachment.cgi?id=159011=edit Output from command drm_info while on login screen Notably, I had to use sudo to run this without the GUI logged in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #12 from Wilbur Jaywright --- Notably, when logging in via SSH, and not the GUI, I needed super user privileges to “retrieve information from /dev/dri/card0” and “card1”. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #11 from Wilbur Jaywright --- If my CPU does have an integrated GPU, I can't connect it to a display. I don't think I changed any kernel boot options. I do use OpenRGB. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #9 from Wilbur Jaywright --- Created attachment 159004 --> https://bugs.kde.org/attachment.cgi?id=159004=edit Output from command drm_info Here is the log. I will note that in one instance, even without multi-monitors, SDDM was sluggish for a few seconds, but it cleared up quickly. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469590] SDDM is slow and jittery most of the time, sometimes recording doubled keystrokes
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #6 from Wilbur Jaywright --- Tried it, that definitely is connected to the problem. Not only was it not sluggish booting with the other monitor disconnected, but it became sluggish as soon as the other monitor was reconnected while still on the login screen. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469590] SDDM is slow and jittery most of the time, sometimes recording doubled keystrokes
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #4 from Wilbur Jaywright --- Uh, hol up, I'm sorry: sddm-x11 is NOT installed. My way of checking for it was to try and install it and see if I got the "is already installed" message. I did, but it was for sddm-wayland-plasma, which I guess is because dnf knows they do the same job. Since I am using X11 because I use NVidia, should I remove sddm-wayland-plasma and install sddm-x11? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469590] SDDM is slow and jittery most of the time, sometimes recording doubled keystrokes
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #2 from Wilbur Jaywright --- Yes, I do have multiple screens, two to be exact. I did not manually install either of the mentioned sddm packages (unless they were a dependency), but I checked and they are both installed. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 469499] Created ISO files are unusable / not real ISO files.
https://bugs.kde.org/show_bug.cgi?id=469499 --- Comment #1 from Wilbur Jaywright --- As it turns out, it is the "Clone copy" option that triggers this problem. The image saved from this format was never intended to be an ISO file, but it lets you save it as one, causing confusion. Using the option "Normal copy" creates a real ISO 9660 file. I suggest implementing using the extension specifying system of the file picker when saving this image, as right now it lets the user save the image with any extension. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 456800] Plasma Mobile: Wallpaper reverts to default occasionally
https://bugs.kde.org/show_bug.cgi?id=456800 --- Comment #2 from Wilbur Jaywright --- I have not encountered the problem in some time on my desktop. I'll have to get back to you about Plasma Mobile. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469590] New: SDDM is slow and jittery most of the time, sometimes recording doubled keystrokes
https://bugs.kde.org/show_bug.cgi?id=469590 Bug ID: 469590 Summary: SDDM is slow and jittery most of the time, sometimes recording doubled keystrokes Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: zargulthewiz...@outlook.com Target Milestone: --- SUMMARY When trying to log in, repeatedly SDDM has occasionally been very sluggish (1-2 FPS), and has even occasionally started recording one keystroke as multiple, making typing a password very difficult. This has happened on all kinds of instances where SDDM would launch, including on first boot. On at least two occasions, clicking the password field restored normal functionality. I should note that I do have a dual monitor setup. STEPS TO REPRODUCE 1. Have a dual monitor setup on the same NVidia card (akmod-nvidia installed). 2. Boot without automatic login, or log out of a signed in account. 3. Move the mouse around. It may not happen every time, so you may have to try multiple times. OBSERVED RESULT The mouse and all UI elements except maybe the blinking cursor rare at 1-2 FPS, and trying to type the password may result in doubled keystrokes. EXPECTED RESULT No low FPS or sluggishness, and the keyboard functions normally. SOFTWARE/OS VERSIONS Windows: X macOS: X Linux/KDE Plasma: Fedora 38 spin Plasma (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I am using an NVidia RTX 2060 SUPER with X-11. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 469499] New: Created ISO files are unusable / not real ISO files.
https://bugs.kde.org/show_bug.cgi?id=469499 Bug ID: 469499 Summary: Created ISO files are unusable / not real ISO files. Classification: Applications Product: k3b Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Copying Assignee: k...@kde.org Reporter: zargulthewiz...@outlook.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY I have created some ISO images with K3B of some old CD-ROMs, but after many attempts to mount them in various ways with no success (not even to a VirtualBox), I finally ran the file command on one, and it says: " lhs/off overflow 4294967295 0 zoombinis.iso: data " On the Hannah Montanah Linux ISO, on the other hand, it says: " hannah_montana_linux_x86_basic_edition.iso: ISO 9660 CD-ROM filesystem data 'Hannah_Montana_Linux' (bootable " It seems that the files produced by K3B are not in fact ISO 9660 files. What is going on? STEPS TO REPRODUCE 1. Insert a real CD. 2. Use the K3B copy feature, set to "Clone copy" and "Only create ISO." 3. Attempt to mount the ISO using ohto the system using the mount command, GNOME Disks, or the Dolphin menu option, or onto a VirtualBox. OBSERVED RESULT All programs will be unable to use the ISO, giving one error or another. The file command will not identify it as an ISO. EXPECTED RESULT The produced file is a true ISO 9660 file, with it's semi-universal compatibility. SOFTWARE/OS VERSIONS Windows: X macOS: X Linux/KDE Plasma: Fedora 38 spin Plasma (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469417] Ark cannot extract password-protected RAR archives
https://bugs.kde.org/show_bug.cgi?id=469417 --- Comment #5 from Wilbur Jaywright --- Ooh, it sounds like unrar is a hidden dependency to Ark. I don’t think I ever tried Ark after I installed unrar. Will try. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469417] Ark cannot extract password-protected RAR archives
https://bugs.kde.org/show_bug.cgi?id=469417 --- Comment #4 from Wilbur Jaywright --- Unrar does work perfectly. I have been using it as a substitute. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 206884] Ark : can't open password protected 7zip and RAR archives
https://bugs.kde.org/show_bug.cgi?id=206884 Wilbur Jaywright changed: What|Removed |Added Blocks||469417 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=469417 [Bug 469417] Ark cannot extract password-protected RAR archives -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 189825] Opening a password protected 7-zip archive hangs Ark
https://bugs.kde.org/show_bug.cgi?id=189825 Wilbur Jaywright changed: What|Removed |Added Blocks||469417 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=469417 [Bug 469417] Ark cannot extract password-protected RAR archives -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 35371] Ark cannot extract password-protected archives
https://bugs.kde.org/show_bug.cgi?id=35371 Wilbur Jaywright changed: What|Removed |Added Blocks||469417 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=469417 [Bug 469417] Ark cannot extract password-protected RAR archives -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469417] New: Ark cannot extract password-protected RAR archives
https://bugs.kde.org/show_bug.cgi?id=469417 Bug ID: 469417 Summary: Ark cannot extract password-protected RAR archives Classification: Applications Product: ark Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: zargulthewiz...@outlook.com CC: aa...@kde.org, alessandro.u...@gmail.com, aphi...@hotmail.com, ashl1fut...@gmail.com, aspotas...@gmail.com, atalantt...@googlemail.com, chea...@gmail.com, cm...@live.com, dj...@ya.ru, dmitry.ashka...@gmail.com, doktor5...@arcor.de, fi...@finex.org, g11072...@trbvm.com, giecr...@stegny.2a.pl, jasmin...@gmx.de, jeremy9...@gmail.com, joel.schae...@laposte.net, kaiuwebroul...@hotmail.com, karl.sebastian.lieb...@web.de, kde-2011...@dotancohen.com, k...@chees.info, k...@kitterman.com, koro...@mail.com, kouzinopou...@gmail.com, leszek.les...@web.de, luka...@poczta.fm, magis...@gmail.com, markusha...@gmx.de, matt.drza...@gmail.com, mat...@openews.it, mozi...@jorgk.com, n.lederba...@tsn.at, oneorj...@gmail.com, pie...@e-delman.com, rak...@freebsd.org, romain@laposte.net, rthoms...@gmail.com, the.tux.l...@gmail.com, thstyl2...@yahoo.com, vamp...@ignaz.org, walt...@gmx.de, willianholtzjvi...@gmail.com, xapi...@gmx.net, yan...@gmail.com, zergling@libero.it Depends on: 35371, 189825, 206884 Target Milestone: --- +++ This bug was initially created as a clone of Bug #35371 +++ SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Have a password-protected RAR archive. 2. Attempt extraction with Ark. 3. Enter password when prompted. OBSERVED RESULT Ark fails, suggesting that the password was wrong or you do not have enough space. EXPECTED RESULT The archive is extracted normally once the password is entered. SOFTWARE/OS VERSIONS Windows: X macOS: X Linux/KDE Plasma: Fedora 37-38 spin KDE Plasma (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION (*** This bug was imported into bugs.kde.org ***) Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=35371 [Bug 35371] Ark cannot extract password-protected archives https://bugs.kde.org/show_bug.cgi?id=189825 [Bug 189825] Opening a password protected 7-zip archive hangs Ark https://bugs.kde.org/show_bug.cgi?id=206884 [Bug 206884] Ark : can't open password protected 7zip and RAR archives -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459494] New: Cannot add Brother printer over network: Configuration completes, but no printer is added
https://bugs.kde.org/show_bug.cgi?id=459494 Bug ID: 459494 Summary: Cannot add Brother printer over network: Configuration completes, but no printer is added Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: zargulthewiz...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I am trying to add a Brother MFC-L2750DW over the network, which had previously worked, but since a recent update, jobs were failing, and after reinstalling Neon from an up-to-date ISO, I now cannot add the printer at all. I have tried manually adding it with lpadmin, upon which it got added with a raw printer driver, but attempting to change the driver to the correct one from systemsettings resulted in an error: "Invalid argument." STEPS TO REPRODUCE 1. Have a Brother MFC-L2750DW on the same network as the KDE Neon system (not connected via USB). 2. Attempt to add the printer via System Settings -> Printers. OBSERVED RESULT The printer will be discovered, and the correct driver selected, but upon clicking "Finish," no printer is added. EXPECTED RESULT The printer is added and is usable. SOFTWARE/OS VERSIONS Windows: No macOS: No Linux/KDE Plasma: KDE Neon 5.25 user edition (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION The official Brother driver packages resulted in a printer being added, but when i tried to print, it's status changed to: Idle - "Unable to locate printer." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457427] Cannot change panel back from Floating to Maximized
https://bugs.kde.org/show_bug.cgi?id=457427 Wilbur Jaywright changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Wilbur Jaywright --- Oops! I misunderstood the button functions. All good now :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457427] New: Cannot change panel back from Floating to Maximized
https://bugs.kde.org/show_bug.cgi?id=457427 Bug ID: 457427 Summary: Cannot change panel back from Floating to Maximized Product: kwin Version: 5.25.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: zargulthewiz...@outlook.com Target Milestone: --- SUMMARY The button to change the system panel back to maximized does nothing, so a change to a floating panel is irreversible. STEPS TO REPRODUCE 1. Go into edit mode on the panel 2. Click "More options" 3. Click "Floating panel" 4. The panel is now floating. Click "Maximize panel" OBSERVED RESULT The panel remains floating, and the "Floating panel" option remains highlighted. EXPECTED RESULT The panel would change from floating to maximized. SOFTWARE/OS VERSIONS Windows: N macOS: N Linux/KDE Plasma: Y (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I am aware that my Plasma is out of date. I will attempt updating... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456800] New: Plasma Mobile: Wallpaper reverts to default occasionally
https://bugs.kde.org/show_bug.cgi?id=456800 Bug ID: 456800 Summary: Plasma Mobile: Wallpaper reverts to default occasionally Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: zargulthewiz...@outlook.com Target Milestone: --- SUMMARY When using KDE Neon+Plasma on my desktop, and Manjaro with Plasma Mobile on my PinePhone, the desktop background has repeatedly reset to the default wallpaper upon unlock/login. I initially thought this had to do with the wallpaper being stored on an external hard drive that wasn’t always mounted on my PC, but I’ve since moved it to my home folder, and the problem persisted. Once it occurred on my pinephone, I realized this was probably specific to Plasma. Thankfully, it seems to be happening far less often on my desktop now, but I have no idea why. STEPS TO REPRODUCE 1. Set a custom wallpaper on Plasma Mobile (a photo, for example) 2. Continue normal use of locking and unlocking regularly, shutting down and rebooting occasionally. 3. If that doesn’t trigger it, try a couple forced shutdowns. OBSERVED RESULT Eventually, the wallpaper would reset to the default (currently “Safe Landing”). I think this may have something to do with a graphical reset or plasma restarting, because one time I unexpectedly witnessed the KDE booting screen while unlocking the phone when it was already on, and the wallpaper reset. EXPECTED RESULT The wallpaper stays the same unless I change it or delete the file in cache somewhere. SOFTWARE/OS VERSIONS Windows: N macOS: N Linux/KDE Plasma: Y (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION As stated above, it seems to no longer be occurring on my desktop. The phone software is up-to-date. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456181] Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=456181 --- Comment #7 from Wilbur Jaywright --- I still consider this a bug, as touch mode is disabled in KDE settings, but it doesn't stop the jumbo UI, which basically means I have to plug and unplug my graphics tablet every time I want to use it. Am I mistaken somehow? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456181] Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=456181 --- Comment #6 from Wilbur Jaywright --- Can confirm, this is related to the graphics tablet. I unplugged its HDMI cable from the DVI<-->HDMI adapter plugged into my PC, then logged out, and since then the UI has been normal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456181] Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=456181 --- Comment #5 from Wilbur Jaywright --- Created attachment 150326 --> https://bugs.kde.org/attachment.cgi?id=150326=edit screenshot showing carryover to Blender The problem carries over to flatpak-installed Blender's UI. This is now problematic. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456181] Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=456181 --- Comment #3 from Wilbur Jaywright --- I should note that I am duplicating my main monitor onto the graphics tablet, with the main monitor being the primary screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456181] Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=456181 --- Comment #2 from Wilbur Jaywright --- I am using X11 as it is the default, and Wayland fails on my GPU. I’m not using any of the other features mentioned. Both my displays are 1920x1080 natively. I have sometimes run an application via wine that changed the display resolution to 640x480, but the problem was occurring before that application was even set up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456181] New: Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=456181 Bug ID: 456181 Summary: Various UI elements going jumbo arbitrarily, suspected to have to do with graphics tablet Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: zargulthewiz...@outlook.com Target Milestone: --- Created attachment 150303 --> https://bugs.kde.org/attachment.cgi?id=150303=edit screenshot showing the problem SUMMARY Occasionally, especially after logging out and then logging in, parts of the Plasma UI are jumbo sized. This can include window title bars, system tray icons, Kickstart, and the login manager outside of Plasma. I initially thought this had to do with my Wacom tablet, but it has happened even with the tablet turned off since system startup. I do slightly suspect KDE is still detecting the included adapter, even though the tablet is off., but it would be very inconvenient to have to disconnect that each time. STEPS TO REPRODUCE 1. Have a Wacom One 13 connected to the PC, along with a standard HDMI monitor. The tablet can be off, but should be plugged in to power via the adapter. 2. Boot. 3. Log out, and log back in. OBSERVED RESULT Some UI elements are jumbo sized. EXPECTED RESULT UI elements to remain at normal sizes, at least until I turn the tablet on. SOFTWARE/OS VERSIONS Windows: No macOS: No Linux/KDE Plasma: Yes, Neon. (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I am using Nvidia 515 proprietary drivers on a GeForce 2060 SUPER. -- You are receiving this mail because: You are watching all bug changes.
