[dolphin] [Bug 494129] New: Dolphin's Info Panel doesn't show the BTRFS file system
https://bugs.kde.org/show_bug.cgi?id=494129
Bug ID: 494129
Summary: Dolphin's Info Panel doesn't show the BTRFS file
system
Classification: Applications
Product: dolphin
Version: 24.08.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: panels: information
Assignee: dolphin-bugs-n...@kde.org
Reporter: joserafael...@riseup.net
CC: kfm-de...@kde.org
Target Milestone: ---
Created attachment 174431
--> https://bugs.kde.org/attachment.cgi?id=174431&action=edit
print
Dolphin's Info Panel doesn't show the BTRFS file system, but it does show other
file systems normally.
Print attached
Terminal Dolphin:
➜ teste dolphin .
QGestureManager::deliverEvent: could not find the target for gesture
QGestureManager::deliverEvent: could not find the target for gesture
kf.kio.widgets: Could not find mount point for
QUrl("file:///home/joserafael/teste")
qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.11-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4400
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 493931] New: KDE Connect Virtual Keyboard is causing restricted access to keyboard inputs and mouse clicks on plasma
https://bugs.kde.org/show_bug.cgi?id=493931 Bug ID: 493931 Summary: KDE Connect Virtual Keyboard is causing restricted access to keyboard inputs and mouse clicks on plasma Classification: Applications Product: kdeconnect Version: 24.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: joserafael...@riseup.net Target Milestone: --- *** I discovered an extremely bizarre bug in KDE Connect that is causing restricted access to keyboard input and mouse clicks on the plasma, preventing me from unlocking the session or even accessing the TTY! What happens is that when using PC-1's Virtual Keyboard on PC-2, if PC-1 locks and turns off the screen and spends a while without activating the screen again, PC-1 can't receive keyboard inputs for unlocking the screen, let alone access the TTY! So I can unlock the screen using pre-defined commands in KDE Connect on the phone, and I see that no keyboard keys or mouse clicks work *** SUMMARY STEPS TO REPRODUCE 1- connect PC-1 to PC-2 with KDE Connect 2- open a text editor on PC-2 and use KDE Connect's PC-1 Remote Keyboard to type on PC-2 3- wait for the PC-1 to lock and turn off the screen, and wait a few minutes to try to unlock it OBSERVED RESULT Plasma doesn't receive keyboard calls or mouse clicks for any operation, so you'll have to turn off the notebook directly from the socket, or by using the shutdown command pre-defined in your KDE Connect cell phone. EXPECTED RESULT I can unlock the plasma normally with my PC keyboard SOFTWARE/OS VERSIONS PC-1 Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.11-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 PC-2 Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2410M CPU @ 2.30GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 473343] Virtual Monitor plugin doesn't work
https://bugs.kde.org/show_bug.cgi?id=473343 José Rafael changed: What|Removed |Added CC||joserafael...@riseup.net --- Comment #1 from José Rafael --- I discovered this bug in Plasma 6.1.5 (fedora 40) and Plasma 6.1.90 (6.2) (fedora 41) as well, KRDC is in version 24.08.0 in the 2 versions of fedora and to top it off, because of trying to create a virtual screen, in the monitor settings several virtual screens were created next to each other and it turns out that the mouse cursor disappears when you use it towards these screens! PC-1 Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.11-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 PC-2 Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2410M CPU @ 2.30GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493699] Night Light does not identify GPS location
https://bugs.kde.org/show_bug.cgi?id=493699 --- Comment #4 from José Rafael --- (In reply to Vlad Zahorodnii from comment #3) > Você tem o geoclue2 instalado em sua máquina? Yes, I have this package installed on my system joserafael2@Ibyte-Fly2:~$ rpm -qa | grep geoc geoclue2-2.7.0-6.fc41.x86_64 joserafael2@Ibyte-Fly2:~$ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493699] Night Light does not identify GPS location
https://bugs.kde.org/show_bug.cgi?id=493699 --- Comment #2 from José Rafael --- (In reply to Nate Graham from comment #1) > Talvez o backend do geoclue esteja quebrado no seu sistema? Funciona no meu. > Você tem um proxy ou VPN ativo? Você pode executar `systemsettings > kcm_nightlight` em uma janela de terminal, reproduzir o problema e colar > qualquer texto mostrado na janela do terminal? Muito obrigado! joserafael2@Ibyte-Fly2:~$ systemsettings kcm_nightlight qml: Pushed pages do not conform to the rules. Please check the documentation. qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 So, I don't use Proxy or VPN here, I've already created a new user on this Laptop, so it's clean of settings from other past versions of fedora, but the location spends forever looking for my location anyway! Above is the command you asked for and it only showed that! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 493697] the wi-fi widget shows all the connected networks around you
https://bugs.kde.org/show_bug.cgi?id=493697 --- Comment #2 from José Rafael --- (In reply to Nate Graham from comment #1) > Não consigo reproduzir isso com o git master atual no Fedora 40. Você está > no 41; talvez uma mudança no NetworkManager abaixo de nós tenha causado isso. > > Presumo que você não esteja conectado a todas essas redes, certo? Você pode > colar a saída de `nmcli dev wifi` executada em uma janela de terminal? Yes, to be more precise, I'm on fedora Atomic Kinoite 41 and it's showing that I'm connected to all the surrounding networks that appear! I'll send you a screenshot too joserafael2@Ibyte-Fly2:~$ nmcli dev wifi IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY * 00:01:02:00:00:00 LoadingInfra 2 65 Mbit/s 100 ▂▄▆█ WPA2 00:01:02:00:00:08 Xiaomi_4656Infra 2 65 Mbit/s 47 ▂▄__ WPA2 00:01:02:00:00:01 brisa-1936481 Infra 2 65 Mbit/s 44 ▂▄__ WPA2 00:01:02:00:00:0A realme C53 Infra 2 65 Mbit/s 17 ▂___ WPA2 joserafael2@Ibyte-Fly2:~$ -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 493697] the wi-fi widget shows all the connected networks around you
https://bugs.kde.org/show_bug.cgi?id=493697 --- Comment #3 from José Rafael --- Created attachment 174116 --> https://bugs.kde.org/attachment.cgi?id=174116&action=edit print nmcli dev wifi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493699] New: Night Light does not identify GPS location
https://bugs.kde.org/show_bug.cgi?id=493699 Bug ID: 493699 Summary: Night Light does not identify GPS location Classification: Applications Product: systemsettings Version: 6.1.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: joserafael...@riseup.net CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 174115 --> https://bugs.kde.org/attachment.cgi?id=174115&action=edit print The night light's GPS location service has been changed, but it continues to search endlessly for a location and doesn't pick the right time to turn it on Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2410M CPU @ 2.30GHz Memory: 5.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 493697] New: the wi-fi widget shows all the connected networks around you
https://bugs.kde.org/show_bug.cgi?id=493697 Bug ID: 493697 Summary: the wi-fi widget shows all the connected networks around you Classification: Plasma Product: plasma-nm Version: 6.1.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: joserafael...@riseup.net Target Milestone: --- Created attachment 174109 --> https://bugs.kde.org/attachment.cgi?id=174109&action=edit print the wi-fi widget shows all the connected networks around you Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2410M CPU @ 2.30GHz Memory: 5.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 493316] New: Import of KNotes notes didn't work for me
https://bugs.kde.org/show_bug.cgi?id=493316 Bug ID: 493316 Summary: Import of KNotes notes didn't work for me Classification: Applications Product: Marknote Version: 1.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: rafael.linux.u...@gmail.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- SUMMARY I have more than 20 notes in Knotes. Now I can't access it because suddenly Plasma no longer has KNotes available to install. I have installed marknote to import the notes, but after doing the process, none of the notes I have created with Knotes appear. STEPS TO REPRODUCE 1. Open marknote 2. "Menu -> Import -> Import from Knotes" 3. Enter "My old Knotes notes" in "Name" field and leave icon and color as they are 4. Click "Import" button OBSERVED RESULT A new "Bloc of notes" calle "My old Knotes notes" appear, but if I click on it, no notes appear in right panel. EXPECTED RESULT To show my notes from Knotes SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240910 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I had a Knotes issue from one year ago, after some KNotes release. Knotes did not show any note (no notes at all) till I close Knotes (totally) and launched it again. Then all my Knotes were there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 492715] Digikam displays the metadata of JXL files incomplete and/or altered
https://bugs.kde.org/show_bug.cgi?id=492715 --- Comment #6 from Rafael Linux User --- (In reply to Maik Qualmann from comment #5) > Git commit 2276a248356ab97d738e65d70e3aff4d336c1f97 by Maik Qualmann. > Committed on 07/09/2024 at 18:32. > Pushed by mqualmann into branch 'master'. > > fix decoding image metadata from XMP.exif* tags > We get the Exiv2::xmpText type for all XMP.exif.* metadata. > Possibly an Exiv2 bug? > FIXED-IN: 8.5.0 > > M +1-1NEWS > M +33 -1core/libs/metadataengine/engine/metaengine_xmp.cpp > > https://invent.kde.org/graphics/digikam/-/commit/ > 2276a248356ab97d738e65d70e3aff4d336c1f97 Thanks for your quick fix! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 492715] Digikam displays the metadata of JXL files incomplete and/or altered
https://bugs.kde.org/show_bug.cgi?id=492715 --- Comment #4 from Rafael Linux User --- Indeed, this option was not activated and once activated, the metadata is exported correctly. This is the first time I have noticed this problem with the metadata and I had never changed this option, shouldn't this option be activated by default? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 492715] Digikam displays the metadata of JXL files incomplete and/or altered
https://bugs.kde.org/show_bug.cgi?id=492715 Rafael Linux User changed: What|Removed |Added Summary|Digikam displays the|Digikam displays the |metadata of incomplete |metadata of JXL files |and/or altered JXL files. |incomplete and/or altered CC||rafael.linux.u...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 492715] New: Digikam displays the metadata of incomplete and/or altered JXL files.
https://bugs.kde.org/show_bug.cgi?id=492715 Bug ID: 492715 Summary: Digikam displays the metadata of incomplete and/or altered JXL files. Classification: Applications Product: digikam Version: 8.4.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- Created attachment 173382 --> https://bugs.kde.org/attachment.cgi?id=173382&action=edit Comparison of metadata SUMMARY After exporting from a RAW image to TIFF, WEBP and JXL, I noticed that the metadata displayed by Digikam from the JXL image is not correct and/or incomplete. STEPS TO REPRODUCE 1. Export from RW2 file to TIFF, WEBP and JXL 2. Compare metadata included in each format OBSERVED RESULT Metadata of JXL showed by Digikam seems not the included in the JXL file EXPECTED RESULT Show same metadata stored in JXL file SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240902 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-1-default (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7600 ADDITIONAL INFORMATION RAW file https://www.transfernow.net/dl/20240906UsozTEUX Screenshot comparing metadata of JXL and TIFF showed by Digikam from same RAW file. -- You are receiving this mail because: You are watching all bug changes.
[krecorder] [Bug 492292] krecorder doesn't save format chosen by user
https://bugs.kde.org/show_bug.cgi?id=492292 --- Comment #1 from José Rafael --- Created attachment 173018 --> https://bugs.kde.org/attachment.cgi?id=173018&action=edit krecoder demo -- You are receiving this mail because: You are watching all bug changes.
[krecorder] [Bug 492292] New: krecorder doesn't save format chosen by user
https://bugs.kde.org/show_bug.cgi?id=492292 Bug ID: 492292 Summary: krecorder doesn't save format chosen by user Classification: Applications Product: krecorder Version: 24.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: espi...@gmail.com Reporter: joserafael...@riseup.net Target Milestone: --- SUMMARY I'm taking the opportunity to report this Krecorder bug (I believe it is a bug): no matter what format or codec you choose, the application only records audio in .wmv format. Even if you choose other file formats and codecs, when you close and open the app your settings are reset! STEPS TO REPRODUCE 1. Open krecorder 2. choose a codec and a suitable format 3. record your audio OBSERVED RESULT Krecorder doesn't change the chosen format and codec, always recording in .wmv. EXPECTED RESULT krecorder records in any format and codec of the user's choice! SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491144] Opening the overview effect not working correctly with external monitor and Unify Outputs option
https://bugs.kde.org/show_bug.cgi?id=491144 Rafael Lima changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Rafael Lima --- (In reply to Nate Graham from comment #1) > Cannot reproduce in current git master. When I connect an external screen > (in my case a 1080p HDMI monitor) and select "unify outputs", Overview > appears on both screens as expected. Assuming it's fixed in Plasma 6.2, but > feel free to re-open this if you find that it's not fixed for you after > upgrading to Plasma 6.2. Thanks! I tested today with the latest Dev edition of KDE neon (built on Aug 18 - Plasma 6.2) and the issue persists. The overview does open on both screens, but the windows are shown only on one of them. Here is an improved set of steps to reproduce the issue: 1. Connect an external monitor or projector 2. Choose the "Unify outputs" option to show the same image on both outputs 3. Open some application windows 4. Press Meta+W to open the overview 5. Notice that the windows will appear only on one of the outputs; they should appear on both, because outputs are unified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491629] Wayland Plasma breaking when changing monitor
https://bugs.kde.org/show_bug.cgi?id=491629 --- Comment #6 from José Rafael --- Created attachment 172633 --> https://bugs.kde.org/attachment.cgi?id=172633&action=edit coredump file Sorry, I didn't see the file attachment button here Now here it goes! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 491715] New: Plasma does not prompt for username and password when using a proxy with authentication
https://bugs.kde.org/show_bug.cgi?id=491715 Bug ID: 491715 Summary: Plasma does not prompt for username and password when using a proxy with authentication Classification: Frameworks and Libraries Product: frameworks-kwallet Version: 6.4.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: rafael.linux.u...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I am on an intranet that requires access to an HTTP proxy with authentication every time I need to access the Internet (either HTTP or FTP protocol). The proxy configuration and the user and password it requires are configured in the system proxy (openSUSE's YaST, but it could be any other Linux) and it works correctly. When I update the system or add repositories, I don't need to enter the proxy username and password because the system provides them from the configuration I made previously. Applications that have access to the Internet, such as browsers, even though the username and password are in the system proxy settings, ask for the username and password when accessing the Internet for the first time in the session. The openSUSE installer does not ask for the credentials, because they are already stored in the system proxy configuration and the Plasma proxy should also use the same ones. Discover, however, prompts for the proxy credentials when launching the proxy. This is not a problem, but it is confusing that if the Plasma proxy takes the system proxy settings, it still requires the user to provide those credentials. The real problem with this is that only “Discover” asks for credentials, in order to access the Internet. All other native Plasma applications do NOT request the credentials and fail. For example, from "System preferences, Global theme", if I try to “Get new ...” themes, cursors, color schemes, window decorations, etc, Plasma doesn't show nothing cause is not able to access the Internet and, at best, shows a window with the message “Network error 0: Proxy requires authentication”. STEPS TO REPRODUCE 1. Configure system proxy 2. Configure Plasma proxy to get same system configuration 3. Launch "System preferences, Global Theme, Cursors" and click on "Get new cursors". OBSERVED RESULT A Plasma window showing "An error happened" appears, showing "Network error 0: Proxy requires authentication”. EXPECTED RESULT To show downloadable cursors SOFTWARE/OS VERSIONS (two distint PC and openSUSE version tested) Operating System: openSUSE Leap 15.6 / openSUSE Leap Tumbleweed KDE Plasma Version: 5.27.11 / 6.1.3 KDE Frameworks Version: 5.115.0 / 6.4.0 Qt Version: 5.15.12 / 6.7.2 Kernel Version: 6.4.0-150600.23.17-default (64-bit) / 6.10.2-1-default (64-bit) Graphics Platform: X11 / Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 491711] New: Plasma ignores proxy settings on FTP accesses
https://bugs.kde.org/show_bug.cgi?id=491711 Bug ID: 491711 Summary: Plasma ignores proxy settings on FTP accesses Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.4.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: FTP Assignee: kio-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I am on an intranet that requires use of HTTP proxy with user authentication to access Internet resources. In my case, I only need to use the proxy for the HTTP(S) protocol. The rest of the services I access, are all local servers, which I access by the IP of each server, so they do not require the use of the proxy. Until this last year, I have had no problems to correctly access the servers using HTTP, SMB, FTP and FISH protocols. I made myself a PAC file whose rules required to use proxy only if the request included the HTTP protocol. However, since more than 6 months, both Dolphin and Krusader try to use the proxy ignoring the PAC file. To verify that this is a problem with the KDE libraries, I have tried other programs that allow access to FTP servers without relying on the KDE libraries, such as the following: - “Box”, a file manager from the MATE window environment accesses the FTP server without problems. - “Filezilla”, the FTP client by definition, seamlessly accesses the FTP server. - “curl”, the Linux system command, seamlessly accesses the same server. Even if I directly specify the values of these environment variables in my user's “~/.bashrc” file as follows, they are totally ignored by KIO-FTP. export FTP_PROXY= export ftp_proxy= export no_proxy="0.0.0.0/0" # Don't use proxy for IPs export NO_PROXY="0.0.0.0/0" # Don't use proxy for IPs Despite all this, Plasma (using Dolphin or Krusader) still tries to use the proxy for any access requiring the FTP protocol, displaying the message “Could not connect to machine 10.162.0.20: The proxy type is invalid for this operation.” . That is, Plasma Dolphin like Krusader, totally ignore the NO_PROXY / no_proxy and FTP_PROXY / ftp_proxy environment variables, regardless of whether they are specified in the system configuration, Plasma's network configuration or directly in “~/.bashrc”. STEPS TO REPRODUCE 1. Configure proxies (any way described in summary) 2. Try to access any valid FTP local server with Dolphin or Krusader OBSERVED RESULT Dolphin and Krusader are unable to connect to server, they always try to use proxy. EXPECTED RESULT To access FTP server w/o proxy SOFTWARE/OS VERSIONS (two distint PC and openSUSE version tested) Operating System: openSUSE Leap 15.6 / openSUSE Leap Tumbleweed KDE Plasma Version: 5.27.11 / 6.1.3 KDE Frameworks Version: 5.115.0 / 6.4.0 Qt Version: 5.15.12 / 6.7.2 Kernel Version: 6.4.0-150600.23.17-default (64-bit) / 6.10.2-1-default (64-bit) Graphics Platform: X11 / Wayland ADDITIONAL INFORMATION I have been using same configuration on my intranet for more than 10 years. This problem first started about 5 years ago also with FISH and SAMBA protocols, but I was able to avoid it using a local PAC file in "Use URL for proxy configuration" in Plasma "Proxy settings". "Caja" or "Filezilla" file manager never had this issue. Now, issue is only with FTP. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 ignores proxy configuration for FTP protocol
https://bugs.kde.org/show_bug.cgi?id=477081 Rafael Linux User changed: What|Removed |Added Summary|Plasma 6 ignores proxy |Plasma 6 ignores proxy |configuration arbitrary |configuration for FTP ||protocol --- Comment #13 from Rafael Linux User --- I -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 ignores proxy configuration arbitrary
https://bugs.kde.org/show_bug.cgi?id=477081 Rafael Linux User changed: What|Removed |Added Summary|Plasma 6 proxy |Plasma 6 ignores proxy |configuration bypass PAC|configuration arbitrary |files directives| -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 491686] New: Removal of the National Geographic Day Wallpaper
https://bugs.kde.org/show_bug.cgi?id=491686 Bug ID: 491686 Summary: Removal of the National Geographic Day Wallpaper Classification: Plasma Product: Plasma Workspace Wallpapers Version: 6.1.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: task Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joserafael...@riseup.net Target Milestone: --- I would like to request the removal of the National Geographic Day Wallpaper, as their server appears to have not updated the wallpaper since 2022, as the wallpaper is always the same ( https://www.nationalgeographic.com/photo-of-the-day/media-spotlight/taxi-halloween-costume-man ) I noticed this on Arch so I thought it was a bug, but now that I moved to Fedora it's still the same! Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491629] Wayland Plasma breaking when changing monitor
https://bugs.kde.org/show_bug.cgi?id=491629 --- Comment #4 from José Rafael --- Okay, I re-did the steps and the plasma wayland keeps crashing, and when this happens the crash manager appears with the following statement: "Collection of crash information was not completed for unknown reasons. You can try again or close the window." Here is what you asked me, I believe https://paste.centos.org/view/c4d37853 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491629] Wayland Plasma breaking when changing monitor
https://bugs.kde.org/show_bug.cgi?id=491629 --- Comment #2 from José Rafael --- Sorry, I was just deleting the bug report because I found out what was causing it! I was having black screen bugs on plasma randomly and I solved it by applying these 2 environment variables KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 KWIN_DRM_NO_AMS=1 I removed them because the new plasma 6.1.4 update arrived and I decided to test without them, and that's when the crashes stopped. now I'm monitoring that the black screen bugs have been fixed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491629] New: Wayland Plasma breaking when changing monitor
https://bugs.kde.org/show_bug.cgi?id=491629 Bug ID: 491629 Summary: Wayland Plasma breaking when changing monitor Classification: Plasma Product: kwin Version: 6.1.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: joserafael...@riseup.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Connect an external monitor 2. Go to the screen configuration widgets on the plasma tray 3. Change the internal monitor to the external one RESULT OBSERVED Plasma makes the switch, then restarts with black screen, crash failure and all applications close together EXPECTED RESULT Switches screens only SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491144] New: Opening the overview effect not working correctly with external monitor and Unify Outputs option
https://bugs.kde.org/show_bug.cgi?id=491144 Bug ID: 491144 Summary: Opening the overview effect not working correctly with external monitor and Unify Outputs option Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: rafael.palma.l...@gmail.com Target Milestone: --- SUMMARY I am using Plasma 6.1.3 on Fedora 40 (KDE spin). When I connect an second monitor or projector, select "Unify outputs" and activate the overview effect, the effect is only shown in the primary monitor; the second monitor only shows the background image. Previously (in Plasma 5.27) when I activated the Overview effect with a projector, the effect was shown in both outputs as expected (since the Unify outputs option is selected). There's no problem when I extend outputs. STEPS TO REPRODUCE 1. Connect an external monitor or projector 2. Choose the "Unify outputs" option to show the same image on both outputs 3. Press Meta+W to open the overview 4. The overview will be shown in the primary monitor, but not in the projector OBSERVED RESULT The projector is not showing the overview effect; only the background image is shown. EXPECTED RESULT The projector should show the overview effect as well. ADDITIONAL INFORMATION Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.12-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: LENOVO Product Name: 82CG System Version: IdeaPad Gaming 3 15IMH05 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490925] I cannot able to add my Google account under "Online Accounts" in the Settings app (KDE Neon).
https://bugs.kde.org/show_bug.cgi?id=490925 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490157] Default shortcuts for switching current application (forward or reverse) not working
https://bugs.kde.org/show_bug.cgi?id=490157 --- Comment #2 from Rafael Baboni Dominiquini --- (In reply to TraceyC from comment #1) > Thank you for the bug report. I just tested this and can't reproduce with > Plasma 6.1.3. > With the language set to English (US, intl, with dead keys), those shortcuts > work. They look as expected in the Task Switcher settings as well. > > Can we ask you to please check if this is still an issue with a live Plasma > 6.1.3 environment? > > If you can still reproduce the bug, please change the Status to "CONFIRMED". > Thanks. I tested on Plasma 6.1.3 inside EndeavourOS Live Enviroment and the problem remains! I'm using X11! Operating System: EndeavourOS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 33.5 GB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Is there any more info that I could share to help? Thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490157] Default shortcuts for switching current application (forward or reverse) not working
https://bugs.kde.org/show_bug.cgi?id=490157 Rafael Baboni Dominiquini changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454790] Can't drag-and-drop items to applications on second monitor when using 4K monitor as source
https://bugs.kde.org/show_bug.cgi?id=454790 --- Comment #12 from Rafael Linux User --- (In reply to David Edmundson from comment #11) > On X11 kwin is not involved in D&D. There is nothing we can do, sorry. I only want to give you thanks. I think it was effectively NOT a bug, but some kind of specific behaviour on a shared (NFS) folder. I think this bug can even be REMOVED to not cause confusion. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 486576] Cannot log into Google account with two factor authentication enabled
https://bugs.kde.org/show_bug.cgi?id=486576 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489645] Online Accounts KCM: creating new Google account fails - "This browser or app may not be secure"
https://bugs.kde.org/show_bug.cgi?id=489645 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489435] Google: Couldn’t sign you in / This browser or app may not be secure
https://bugs.kde.org/show_bug.cgi?id=489435 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482808] Adding Online Accounts doesn't work (google says the browser isn't secure).
https://bugs.kde.org/show_bug.cgi?id=482808 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480779] Can not add Google to Online Accounts anymore
https://bugs.kde.org/show_bug.cgi?id=480779 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490157] Default shortcuts for switching current application (forward or reverse) not working
https://bugs.kde.org/show_bug.cgi?id=490157 Rafael Baboni Dominiquini changed: What|Removed |Added CC||rafaeldominiqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490157] New: Default shortcuts for switching current application (forward or reverse) not working
https://bugs.kde.org/show_bug.cgi?id=490157 Bug ID: 490157 Summary: Default shortcuts for switching current application (forward or reverse) not working Classification: Applications Product: systemsettings Version: 6.1.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwintabbox Assignee: kwin-bugs-n...@kde.org Reporter: rafaeldominiqu...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 171599 --> https://bugs.kde.org/attachment.cgi?id=171599&action=edit Task Switcher with broken shortcuts SUMMARY Changing my keyboard layout broken some shortcuts! STEPS TO REPRODUCE 1. Set the keyboard layout to English (US) 2. Open two windows of the same application 3. The default shortcuts (Alt+` and Alt+~) work fine 4. Set the keyboard layout to English (US, intl, with dead keys) 5. The default shortcut doesn't work! 6. Change the forward shortcut to Alt+`and the reverse to Alt+~ 7. The input became broken! 8. Setup some other shortcut, like Alt+Q and Alt+W 9. The switcher works fine! OBSERVED RESULT Some incompatibility with shortcuts because my keyboard layout! EXPECTED RESULT The shortcuts should work with any keyboard layout! SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (X11) KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I'm testing with the live version! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 José Rafael changed: What|Removed |Added CC||joserafael...@riseup.net --- Comment #56 from José Rafael --- Regardless of whether you have control or not, this bug of turning off, blocking the screen happens when you watch videos on firefox or telegram for example, Plasma is not respecting the rule that shows on the power plasmoid that the application is preventing from turning off the screen! It also happens if the game is paused without using the mouse, the monitor turns off and locks! Arch Linux Plasma 6.1.1 KDE Frameworks: 6.3.0 Qt: 6.7.2 Kernel 6.9.7-arch1-1 Wayland Fedora Atomic Kinoite 40 Plasma 6.1.1 KDE Frameworks: 6.3.0 Qt: 6.7.1 Kernel: 6.9.6-200.fc40.x86_64 Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488163] New: Plasma crashes uppon restore
https://bugs.kde.org/show_bug.cgi?id=488163 Bug ID: 488163 Summary: Plasma crashes uppon restore Classification: Plasma Product: plasmashell Version: 5.27.11 Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rafael.martinezca...@orange.fr CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.11) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.12-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.11 [CoredumpBackend] -- Information about the crash: I've set up hibernation on my desktop, but it seems everytime i restore from hibernation state, Plasma just crashes. The applications are still usable, but the panels are frozen, and the application launcher also won't open. It also happens when simply put to sleep. I'm using: Plasma 5.27.11, X11, nvidia drivers The crash can be reproduced every time. -- Backtrace (Reduced): #10 0x7fa4ddf8d7bf in vvk::Destroy(VkDevice_T*, VkCommandPool_T*, vvk::DeviceDispatch const&) (device=, handle=, dld=) at /home/rafael/src/wallpaper-engine-kde-plugin/src/backend_scene/src/Vulkan/vulkan_wrapper.cpp:189 #11 0x7fa4ddf65f07 in vvk::Handle::Release() (this=0x7fa4a801eb70) at /home/rafael/src/wallpaper-engine-kde-plugin/src/backend_scene/src/Vulkan/include/Vulkan/../vvk/handle.hpp:61 #12 vvk::Handle::~Handle() (this=0x7fa4a801eb70, __in_chrg=) at /home/rafael/src/wallpaper-engine-kde-plugin/src/backend_scene/src/Vulkan/include/Vulkan/../vvk/handle.hpp:34 #13 vvk::CommandPool::~CommandPool() (this=0x7fa4a801eb70, __in_chrg=) at /home/rafael/src/wallpaper-engine-kde-plugin/src/backend_scene/src/Vulkan/include/Vulkan/../vvk/vulkan_wrapper.hpp:403 #14 wallpaper::vulkan::Device::~Device() (this=this@entry=0x7fa4a801e490, __in_chrg=) at /home/rafael/src/wallpaper-engine-kde-plugin/src/backend_scene/src/Vulkan/Device.cpp:171 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488163] Plasma crashes uppon restore
https://bugs.kde.org/show_bug.cgi?id=488163 --- Comment #1 from Rafael Martinez --- Created attachment 170229 --> https://bugs.kde.org/attachment.cgi?id=170229&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #12 from Rafael Linux User --- Before answering the result of the test you ask me, I have verified what is different between the "kioslaverc" files in a "Plasma pre-6" installation (to call it somehow) and "Plasma 6" (I don't know if it is a certain time or a certain version of Plasma 6 when the problem appears). In that file, there are only two lines that change: ProxyConnectTimeout=10 (line that doesn't appear in Plasma pre-6) ftpProxy=NO_PROXY About ftpProxy value, seems no difference of using NO_PROXY value or not. In Plasma pre-6, value is EMPTY and works. In Plasma 6, default value is NO_PROXY. In Plasma 6, if value is EMPTY then Dolphin shows "Can't connect to host 10.162.0.46: Invalid proxy type for this operaton" when trying reach FTP (I insist, local FTP servers in our intranet) and Dolphin shows "Canceled" when trying to access remote FTP. Regarding changing the value of "Proxy Config Script", there has been no success after changing the value, logging out and logging back in. Dolphin still behaves the same. Moreover, if I make the change in the Plasma proxy configurator, apply the changes, and open the Plasma proxy configurator again, it doesn't save the change!!! (it probably doesn't recognise the "file" URL as correct). Also, I was surprised that if I make the change in the "kioslaverc" file as I had to do because of the problem I just mentioned, and I open the Plasma proxy configurator, it still shows the correct path "/home/...". !!. It is as if that file is not the one that modifies the Plasma proxy configurator. In any case, after modifying it by hand, logging out, etc, nothing has changed, the problem is still the same. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #10 from Rafael Linux User --- (In reply to Nicolas Fella from comment #9) > Can you attach your .config/kioslaverc file? Of course. I changed to publish here user/domain and path to PAC file for privacy, but they are correct. AutoResume=true ConnectTimeout=20 MarkPartial=true ProxyConnectTimeout=10 ProxyUrlDisplayFlags=3 ReadTimeout=15 ResponseTimeout=600 [Browser Settings/SMBro] Password=0H@0GA0H@0AO0I50F>0F>0F:0F= User=1234@intranet [Proxy Settings] NoProxyFor=NO_PROXY Proxy Config Script=/home/myuser/proxy_PAC_configuracion.pac ProxyType=2 ReversedException=false ftpProxy= httpProxy=http_proxy httpsProxy=https_proxy socksProxy= - Now that I see this file content, I should add that every time I access an SMB folder in the domain, it forces me to type the user as "1234@intranet", although by default only "1234" appears in the user/password window that appears when trying to access a shared SMB folder. A couple of years ago, that wasn't the case. There was no need to enter the domain. Since some change, it forces me to try "1234@intranet" or "intranet\1234". If you need more info, please, tell it to me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #8 from Rafael Linux User --- I found some related issue at https://codereview.qt-project.org/c/qt/qtbase/+/494754 And I warned about this issue in 2021 ... no one ask about. No priority, I guess. https://bugs.kde.org/show_bug.cgi?id=445272 Even I wrote in another thread about with or without using PAC files, when trying to download plasmoids, new themes or any other “downloadable” (I suspect using FTP protocol) packages from Plasma settings menus, it simply fails, cause maybe Plasma try to access to proxy without authentication (and it’s required). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #7 from Rafael Linux User --- IMHO, I think we can rule out my system configuration, since they are two different computers, on the same network, and that configuration I've been using for years only fails when I update KDE. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #5 from Rafael Linux User --- I don't attach a "crash" file cause basically Dolphin doesn't crash, simply doesn't work like before upgrading. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #4 from Rafael Linux User --- Created attachment 169362 --> https://bugs.kde.org/attachment.cgi?id=169362&action=edit Errors showed when trying to access remote folders -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 --- Comment #3 from Rafael Linux User --- Created attachment 169361 --> https://bugs.kde.org/attachment.cgi?id=169361&action=edit PAC file directives Basically, the PAC file says "only use proxy for http protocol" (so no for FTP, FISH or SMB) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] Plasma 6 proxy configuration bypass PAC files directives
https://bugs.kde.org/show_bug.cgi?id=477081 Rafael Linux User changed: What|Removed |Added Summary|No access to remote FTP |Plasma 6 proxy |folders after upgrading |configuration bypass PAC |Plasma |files directives --- Comment #2 from Rafael Linux User --- I have again done a more extensive test on this, which is why I have changed the title of this thread. We started from a pre-Plasma 6 version of Tumbleweed where accessing folders on intranet servers with the FTP, FISH and SMB protocols (on a Windows domain) worked fine on an intranet with an HTTP proxy that requires a username and password. After upgrading to any version of Plasma 6, none of the protocols work. I noticed that Dolphin, on the first attempt to access an FTP service after upgrading, asked for the proxy username and password, when in fact it should NOT ask for that information after parsing the request if it uses the PAC file. In other words, Plasma is now ignoring the directives in the PAC file (attached). I launched Dolphin from console, and attached here error showed while trying to reach any of the servers folders using FTP, FISH or SMB. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] No access to remote FTP folders after upgrading Plasma
https://bugs.kde.org/show_bug.cgi?id=477081 Rafael Linux User changed: What|Removed |Added Summary|No access to remote FTP |No access to remote FTP |folders when upgrading |folders after upgrading |Plasma |Plasma -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477081] No access to remote FTP folders when upgrading Plasma
https://bugs.kde.org/show_bug.cgi?id=477081 Rafael Linux User changed: What|Removed |Added Summary|No access to remote FTP |No access to remote FTP |folders |folders when upgrading ||Plasma -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 --- Comment #17 from Rafael Linux User --- > still exists on plasma 6 currently Still doing nothing in Plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485290] New: Application launcher should float even when the panel is not floating
https://bugs.kde.org/show_bug.cgi?id=485290 Bug ID: 485290 Summary: Application launcher should float even when the panel is not floating Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: rafael.palma.l...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY In Plasma 6 we get a nice floating application launcher, which together with the floating panel makes Plasma look very modern. However, when a window is maximized and the panel de-floats, the application launcher stops floating. I see the reasoning here, but it would be better if the application launcher could still float, even when the panel is not floating. Since this might not be everyone's cup of tea, it would be nice to have an option in Kickoff's settings that allows to "Float even when the panel is not floating". STEPS TO REPRODUCE 1. Start Plasma and make sure no window is visible, so that the panel is floating 2. Click the application launcher in the panel 3. The app launcher will float (as expected) 4. Now open an application and maximize its window 5. Click the application launcher in the panel 6. The app launcher no longer floats (this is what will change with this proposal) OBSERVED RESULT In Step 6 the panel does not float EXPECTED RESULT In Step 6 the panel should float SYSTEM INFO Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: LENOVO Product Name: 82CG System Version: IdeaPad Gaming 3 15IMH05 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484849] Wrong mouse pointer during login
https://bugs.kde.org/show_bug.cgi?id=484849 --- Comment #2 from Rafael Lima --- (In reply to mydarkstar from comment #1) > could you please check if going to "System Settings → Colors & Themes → > Login Screen (SDDM) → Apply Plasma Settings... → Apply" fixes your issue? It did not fix the issue... I still get the same mouse pointer. Actually, right before the the login screen appears, I get a black screen with a mouse pointer (using the correct Breeze pointer). Then when the login screen appears, the mouse pointer changes to the wrong pointer. And then after I enter my password and click the ">" button, the mouse pointer switches to the Breeze theme. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 484965] New: cannot receive file from desktop to Android 14
https://bugs.kde.org/show_bug.cgi?id=484965 Bug ID: 484965 Summary: cannot receive file from desktop to Android 14 Classification: Applications Product: kdeconnect Version: 24.02.1 Platform: Android OS: Other Status: REPORTED Severity: major Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: dryestb...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- *** 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 cannot receive files from desktop to android it works fine in Android 13 until Samsung has a system update to 14, still does not work when specifying the path STEPS TO REPRODUCE 1. have a android 14 2. connect the device to pc 3. send a file from PC to android 4. if the file is not received, customize and specify the Android device destination directory (mine is at "/tree/primary:KDE" or internal storage/KDE) 5. send the file again OBSERVED RESULT does not receive the file, no noisy notification, or if it has a notification it does nothing when clicking it. EXPECTED RESULT In Android 13 it works fine, when I send a file, I can open it manually via file manager or by clicking the notification SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Android version: 14 Device: Samsung Galaxy A54 5g -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446468] Selected folder icon becomes white in selected list items
https://bugs.kde.org/show_bug.cgi?id=446468 --- Comment #33 from Rafael Lima --- O Plasma 6.0.3 I am now getting black icons instead of white. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483945] The Plasma 6 Overview/Desktop Grid combined effect does not function as well as the Overview Desktop Grid effects on Plasma 5.27, and Overview has missing options
https://bugs.kde.org/show_bug.cgi?id=483945 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- I'd say this is a duplicate of bug 475077 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 477968] Snaps not showing in Discover (plasma-discover-backend-snap is missing necessary files)
https://bugs.kde.org/show_bug.cgi?id=477968 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #4 from Rafael Lima --- I can confirm that snaps are not showing in Discover, even though plasma-discover-backend-snap and snapd are installed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484849] New: Wrong mouse pointer during login
https://bugs.kde.org/show_bug.cgi?id=484849 Bug ID: 484849 Summary: Wrong mouse pointer during login Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: rafael.palma.l...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY When I boot my laptop and get to the login screen, the mouse pointer does not use the Breeze theme. Instead it uses a small pointer that reminds Gnome's mouse theme. STEPS TO REPRODUCE 1. Boot your PC 2. Wait till it gets to the login screen 3. Notice the mouse pointer is not the Breeze style OBSERVED RESULT Wrong mouse pointer EXPECTED RESULT Breeze mouse pointer should be used SYSTEM INFO Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: LENOVO Product Name: 82CG System Version: IdeaPad Gaming 3 15IMH05 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450 --- Comment #10 from Rafael Linux User --- (In reply to Andrius Štikonas from comment #9) > (In reply to Rafael Linux User from comment #8) > > (In reply to Andrius Štikonas from comment #7) > > > > > > (or somewhere else you don't want them). Perhaps we need some kind of > > > detection logic depending on whether destination path is user or root > > > writable. > > > > I agree, cause meanwhile, I can't use the KDE partition tool to do backups > > that way and need to use Gnome based one. > > Well, you could always manually adjust destination permissions with chown... Not the way if there are tools that take it into account and let user to do all from that tool. That's how I would like KDE Partitioner to work. > > Anyway, keep in mind that gnome disks and kde partition manager backup > slightly different things. From what I just saw, gnome disks backups whole > device, e.g. /dev/sda whereas KDE Partition Manager backups /dev/sda1 No. "DISKS" let user make backup from whole disk or individual partitions (like I showed in first attached screenshot). I don't understand why KDE have not same features in 2024 :( -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450 --- Comment #8 from Rafael Linux User --- (In reply to Andrius Štikonas from comment #7) > > (or somewhere else you don't want them). Perhaps we need some kind of > detection logic depending on whether destination path is user or root > writable. I agree, cause meanwhile, I can't use the KDE partition tool to do backups that way and need to use Gnome based one. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480726] Actual user not showed in active tab
https://bugs.kde.org/show_bug.cgi?id=480726 Rafael Linux User changed: What|Removed |Added Summary|Inconsistency between the |Actual user not showed in |information displayed in|active tab |the window header and the | |active tab. | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480726] Actual user not updated in title tab
https://bugs.kde.org/show_bug.cgi?id=480726 Rafael Linux User changed: What|Removed |Added Summary|Actual user not showed in |Actual user not updated in |active tab |title tab -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480726] Inconsistency between the information displayed in the window header and the active tab.
https://bugs.kde.org/show_bug.cgi?id=480726 --- Comment #3 from Rafael Linux User --- I have tried to reproduce the exact problem I was talking about, but I have not succeeded. However, the problem that does persist is with respect to the user when changing user with "your user", which corresponds to the screenshot I show. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480726] Inconsistency between the information displayed in the window header and the active tab.
https://bugs.kde.org/show_bug.cgi?id=480726 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #2 from Rafael Linux User --- Created attachment 167790 --> https://bugs.kde.org/attachment.cgi?id=167790&action=edit After change of user using "su -", window title is not changed After changing to the "root" user with "su -", the user shown in the tab title for that console should also change, however, it still shows the user with which you connected to that server. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450 --- Comment #6 from Rafael Linux User --- Created attachment 167781 --> https://bugs.kde.org/attachment.cgi?id=167781&action=edit Asking for password when I select "Start creating" -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450 --- Comment #5 from Rafael Linux User --- Created attachment 167780 --> https://bugs.kde.org/attachment.cgi?id=167780&action=edit DISKS - Selecting source partition to backup -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450 --- Comment #4 from Rafael Linux User --- I mistook the name of the partitioning application. It is "DISKS" not "GPARTED". And I have also found that it asks for the root password ALWAYS when a partition backup operation is to be performed, regardless of the destination to be chosen for the image file. That is to say, it works as I said, but it really requires root privileges to be able to take control of the partition to be backed up, regardless of whether or not the destination requires root permissions. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #2 from Rafael Linux User --- I understand the logic. However, it is also logical that if the user selects a user/password protected disk or partition, it will ask the user for this information and only if they are incorrect, deny access. This is how other applications (such as those mentioned above) that allow partition copying do it. I think this should be an improvement to implement because in the meantime, I won't be able to use the KDE partitioner to make partition copies. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 484450] New: Access error when trying to make backup from partition (to file) to any folder of another partition.
https://bugs.kde.org/show_bug.cgi?id=484450
Bug ID: 484450
Summary: Access error when trying to make backup from partition
(to file) to any folder of another partition.
Classification: Applications
Product: partitionmanager
Version: 23.04.2
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: andr...@stikonas.eu
Reporter: rafael.linux.u...@gmail.com
Target Milestone: ---
SUMMARY
I have a partition drive ("BACKUP") that is not mounted at boot time. When I
want to access it, Dolphin asks for the superuser password and there is no
problem accessing it or creating folders or files. However, when I try to make
a copy ("Partition, Backup") of a partition from another disk to this "Backup"
partition (regardless of whether I have previously mounted the "Backup"
partition with Dolphin or not), "partitionmanager" displays a window with the
error message "The specified folder does not exist or could not be read", and I
cannot make the copy. The same procedure, with other partitioners like "Disks"
(Gdisks) can access to write to the "BACKUP" partition to write the copy file
without problems.
STEPS TO REPRODUCE
1. Select a partition from "A" disk
2. "Partition, Backup"
3. In "Save file" window, select "BACKUP" partition in "B" disk (owned by root)
OBSERVED RESULT
"partitionmanager" displays a window with the error message "The specified
folder does not exist or could not be read".
EXPECTED RESULT
Two options:
- If "BACKUP" partition not mounted, ask for root password)
- If "BACKUP" partition is mounted (from Dolphin) simply leave user select
"BACKUP" partition and a folder.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230613
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.3.7-1-default (64-bit)
Graphics Platform: X11
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #112 from Rafael Linux User --- (In reply to pallaswept from comment #111) > Sadly, not fixed in Plasma 6. Interaction with pipewire still causes a > lockup. It doesn't freeze the panel any more, but pipewire objects are still > left 'hanging' until pw crashes. See screenshots of the same behaviour as > before. Plasma 6 + Tumbleweed. Now, my autohide panel freezes COMPLETELY from time to time. Icons are not responsive at all. Simply panel is FROZEN and visible. I need to launch "kquitapp6 plasmashell || killall plasmashell" and wait about 5 minutes to get panel hided and responsive again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #11 from José Rafael --- (In reply to Giacomo Lozito from comment #10) > (Em resposta a Nate Graham no comentário nº 6 ) > > Ah, isso deveria ter sido corrigido no Plasma 6.0.2, então. Você pode > testar isso e > > reabrir se ainda estiver quebrado? > > Acabei de testar no Arch com plasma 6.0.2 e ainda ocorre para mim. > Também confirmei o mesmo comportamento relatado inicialmente: ocorre apenas > com o estilo de plasma definido como Breeze e apenas no X11, mudar para > outro estilo de plasma, como Breeze Light, evitará que o problema ocorra. > Não ocorre com Wayland. It does happen with Wayland, but I'm using the Breeze Dark theme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #9 from José Rafael --- (In reply to Nate Graham from comment #6) > Ah, isso deveria ter sido corrigido no Plasma 6.0.2, então. Você pode > testar isso e reabrir se ainda estiver quebrado? I updated Arch linux with plasma 6.0.2, and this black screen bug still happens Nate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 José Rafael changed: What|Removed |Added CC||joserafael...@riseup.net Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #8 from José Rafael --- This black screen bug just happened, as soon as the screen goes off and I move the mouse the plasma wakes up and then the screen goes black, I need to use KDE COnnect or TTY in arch linux to unblock the session -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 483026] KDEConnect virtual screen opens KRDC on remote machine, but causes plasmashell crash on host
https://bugs.kde.org/show_bug.cgi?id=483026 José Rafael changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 483026] New: KDEConnect virtual screen opens KRDC on remote machine, but causes plasmashell crash on host
https://bugs.kde.org/show_bug.cgi?id=483026 Bug ID: 483026 Summary: KDEConnect virtual screen opens KRDC on remote machine, but causes plasmashell crash on host Classification: Applications Product: kdeconnect Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: joserafael...@riseup.net CC: andrew.g.r.hol...@gmail.com Target Milestone: --- KDEConnect virtual screen opens KRDC on remote machine, but causes plasmashell crash on host *** KDEConnect virtual screen opens KRDC on remote machine, but causes plasmashell crash on host Sometimes it causes the guest's plasmashell to crash and it has also occasionally happened that the KRDC opens several times at the same time (I counted 6 windows open the last time it happened to me). *** Playback instructions 1. have KDE Connect on Computer 1 and 2 2. Pair the two computers 3. Click on Virtual Screen in the KDE Connect Tray to connect to Computer 2 Observed result I got 3 different behaviors: 1- Arch Linux (Computer 1) had PlasmaShell restart several times 2- Fedora Linux (Computer 2) had PlasmaShell restarting as well as Arch Linux, but called KRDC on Arch Linux six times one after the other. 3 - I called the Virtual Screen from Fedora and this time it was Arch Linux that crashed the plasmashell. Expected result KRDC is called normally on the Guest computer SOFTWARE/OS VERSIONS Computer 1 Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Computer 2 Linux/KDE Plasma: Fedora Kinoite Atomic 40 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 Rafael Linux User changed: What|Removed |Added CC|rafael.linux.u...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #19 from Rafael Linux User --- I really don't know by what logic you understand that it is not a "bug". I have clearly defined the scenario: A computer, with a certain configuration. Among all PDF reader software tested (from embedded in web browsers of all kinds, to professional applications like FoxitReader or Master PDF) only Okular fails to show as enabled the checkboxes in cases like this. And yet, it does show it correctly in form mode. I don't know under what criteria Okular can't be considered to have a resolution problem in these cases. I give up. The solution after everything I have said is not to consider it an error to be solved by you and, thanks to that attitude, unfortunately I can only stop using Okular since we are talking about transcendental information that is not correctly processed by Okular. Best wishes -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #15 from Rafael Linux User --- However, why does it show the character in "form mode"? Furthermore, I understand that the correct thing to do in these cases would be to apply the same solution that the PDF readers that are built into web browsers use. Shouldn't this thread be reopened so that the problem can be solved? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #13 from Rafael Linux User --- Created attachment 166556 --> https://bugs.kde.org/attachment.cgi?id=166556&action=edit Fonts -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 Rafael Linux User changed: What|Removed |Added Attachment #166428|0 |1 is obsolete|| --- Comment #10 from Rafael Linux User --- Created attachment 166472 --> https://bugs.kde.org/attachment.cgi?id=166472&action=edit Only the checkboxes -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #9 from Rafael Linux User --- Before I opened this thread, I tried to delete private information with LibreOffice Draw, but the form is lost, so it didn't work. As it is more complex than using Adobe tools, I remembered that there is "Master PDF" which is multiplatform and, although it adds a watermark, it works perfectly for this case. Now I will attach the file with just those checkboxes. I have already checked that the problem remains despite having altered the document with "Master PDF". Best regards -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #7 from Rafael Linux User --- Following your instructions, I have found that they have used "PDFCreator 2.4.1.13" to create the PDF, so I get the impression that they must be using an old version of "MSWord" or, less likely, are unaware of the "Convert to PDF" function of their word processor (they can only be using either MSOffice or OpenOffice/LibreOffice, which are "official" in the company). I took some additional time to check browsers internal PDF reader. "EDGE" (for Linux), "Chrome" and "Chromium" all them shows right marked checkboxes with symbol "✓". "Firefox" too, but shows an "✕" symbol instead. To make sure it's not my computer and not to waste anyone's time, I even checked on a computer also running openSUSE but outdated, if Okular behaves the same, and it does. On that PC "Okular" is version 21.08.3. Any other thing I can do, please, aks me. Thanks -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #5 from Rafael Linux User --- I am sorry it is not enough. The bug exists and I took the time to document it, but I can't keep looking for ways to recreate it, as I don't know with which tools to create such files. Closing the thread does not seem adequate or appropriate, but I think it should be up to you - based on the information provided - to find out which word processor generates such peculiar checkboxes. Best regards -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #3 from Rafael Linux User --- Created attachment 166428 --> https://bugs.kde.org/attachment.cgi?id=166428&action=edit Screenshots -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #2 from Rafael Linux User --- (In reply to Albert Astals Cid from comment #1) > please attach a file where you're having this problem. I can't share the document as it has private content, but I have captured the screen shot in the attached document, compared to "Foxit Reader". However, I have discovered that the problem lies in the "type" of checkbox. The ones containing an "X" are always displayed without problems by Okular. The ones containing the "✓" symbol are the ones that Okular does not display until you enter edit mode. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] New: Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 Bug ID: 482363 Summary: Checkboxes on forms do not show as checked even though they are checked Classification: Applications Product: okular Version: 24.01.80 Platform: openSUSE OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- NOTE: This issue is same than https://bugs.kde.org/show_bug.cgi?id=184489 CLOSED issue SUMMARY When the user opens a form that has checkboxes, they appear by default as unchecked even though they are checked. The user has to enter "form" mode for Okular to correctly show that these checkboxes are checked. STEPS TO REPRODUCE 1. Open a PDF form with checkboxes and enable "form mode" 2. Enable some of the checkboxes 3. Save document and close Okular 4. Open again same document (default view mode, no "form mode") OBSERVED RESULT Checked boxes are not showed like checked if you don't enter in "form mode". EXPECTED RESULT To show checked boxes as checked without entering "form mode". SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230613 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I discovered this error when verifying digitally signed PDF documents where Okular showed as unchecked checkboxes that the user claimed to have checked. Only when switching to "form mode" did the checkboxes show that the sender had indeed checked them before signing the document. This is why this is a serious bug. Other PDF viewers do display ticked boxes correctly. It is not normal for all the contents of the boxes in a form to be displayed (such as text boxes) except for the checkboxes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #14 from Rafael Lima --- (In reply to Niccolò Venerandi from comment #8) > You can press the Overview shortcut again to switch to the grid mode and > easily move applications between desktops Unfortunately this is not a nice experience. The current implementation in 5.27 is so much better. (In reply to postix from comment #13) > To further decrease any confusion about a different layout some users may > have due the linearization I'd suggest to add a row indicator to the VD > preview bar. Please see the mockup. I believe this makes it pretty obvious > and clear. :) TBH I think the indicators are not needed... they clutter the interface. It would be better to simply revert to what we had in 5.27. If a user sets a 2x2 = 4 workspaces, they won't find it weird to see a row with 4 workspaces when they open the overview. Now, if the user sees nothing at the top bar when the Overview is started, then this will be weird. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #7 from Rafael Lima --- I was about to report this issue as well... If this is intentional, I'm not sure it's a very wise choice. This will basically make it a pain for users who like to have layouts with 2 or more rows, which are very handy. It kills a lot of the functionalities of the Overview, since you can no longer move applications to other desktops. Using multiple-row layouts (f.i. 2x2, 3x3, etc) is very useful, because it gives much more flexibility for switching layouts with a single move (up, down, left, right). When I was trying out Plasma 6, I set my virtual desktops in a 2x2 layout and when I toggled the overview to move applications to other desktops, it wasn't possible to do so. It simply killed the Overview for me. FTR this works nicely on Plasma 5.27, so I don't see the point of removing something that is useful and works fine in Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 445965] Allow a one time change to charging thresholds
https://bugs.kde.org/show_bug.cgi?id=445965 Rafael <6ynjpr...@mozmail.com> changed: What|Removed |Added CC||6ynjpr...@mozmail.com --- Comment #4 from Rafael <6ynjpr...@mozmail.com> --- I was thinking of something similar. I like to work away from a power outlet, e.g. in a garden. Doesn't have to be a once off. I want to tell my laptop I'm intending to switch from working continuously on a charger to a battery, and I'd like it to prepare for it, by charging the battery to the max (as configured). There could be another option telling what to do after the laptop is plugged again, it could switch to the standard charging thresholds - (battery longevity) or max charge, so I can go again away from the outlet as soon as possible. So in summary, we'd have two or three charging profiles: - battery longevity - max charge, once off (goes back to longevity once plugged) - max charge, continuous (doesn't switch to battery longevity) -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 481637] New: Kio Gdrive doesn't load folder contents
https://bugs.kde.org/show_bug.cgi?id=481637 Bug ID: 481637 Summary: Kio Gdrive doesn't load folder contents Classification: Frameworks and Libraries Product: kio-gdrive Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: rafa...@outlook.com.br Target Milestone: --- SUMMARY kio gdrive is not able to load gdrive folder contents, keeps loading endlessly. STEPS TO REPRODUCE 1. Add Google account to KDE Accounts 2. Install KIO GDrive 3. Attempt to open gdrive folder OBSERVED RESULT dolphin stays stuck at loading contents, never loads anything EXPECTED RESULT SHould load google drive folders and files as expected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-17-generic (64-bit) ADDITIONAL INFORMATION Reinstalling does not fix the issue, restarting computer does not do anything. attempting to run kioclient5 exec gdrive:/ results in the following error: kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/gdrive" not found I've installed it through Discover, and then reinstalled it through sudo apt, neither worked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466005] Add a base tool to BQM to transcode jpg to jxl (and vice versa) [NB. transcode is different from convert]
https://bugs.kde.org/show_bug.cgi?id=466005 --- Comment #8 from Rafael Linux User --- For those of us who do believe that JXL should replace JPG because of its amazing qualities, retaining the original quality in transcoding is important. Could you consider the inclusion of the mentioned transcoding library in Digikam? After all, it is a native feature of the JXL format, as is choosing the "effort" parameter in the encoding. The native TIFF format does not implement some of the encoding methods offered by Digikam and other image processing software. Moreover, there are so many non-native options that, as I'm sure you know, TIFF is also known as "Thousands of Incompatible File Formats". And yet, it seems that implementing all the native features of JXL is more problematic than implementing the non-native (non-standard) features for TIFF. That's my opinion, of course, but why hide from the user the native options of a format like JXL that has been developed in such a way that it covers all the weak points of the other image formats? Thank you -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448234] Usage of Qt SVG renderer causes some 3rd-party app icons to be mis-rendered
https://bugs.kde.org/show_bug.cgi?id=448234 --- Comment #26 from Rafael Linux User --- Created attachment 165751 --> https://bugs.kde.org/attachment.cgi?id=165751&action=edit SVG referred view in Gwenview -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448234] Usage of Qt SVG renderer causes some 3rd-party app icons to be mis-rendered
https://bugs.kde.org/show_bug.cgi?id=448234 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #25 from Rafael Linux User --- Confirming. If fact, gwenview doesn't render that SVG file correctly. Operating System: openSUSE Tumbleweed 20240208 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336990] Chromium and Firefox does not remember their virtual desktops on session restore
https://bugs.kde.org/show_bug.cgi?id=336990 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #10 from Rafael Linux User --- Can confirm this issue. I thought it was only Firefox, but can confirm same for Chrome/Chromium. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481221] New: Question about transcoding JPEG to JPEGXL (JPG to JXL)
https://bugs.kde.org/show_bug.cgi?id=481221 Bug ID: 481221 Summary: Question about transcoding JPEG to JPEGXL (JPG to JXL) Classification: Applications Product: digikam Version: 8.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Bqm-Convert Assignee: digikam-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- SUMMARY I’m recoding my TIFF files to JXL with Digikam. I want to do the same with my JPG files, however, before doing it, I have a question, related to re-encoding. cjxl command line tool from libjxl let users to losslessly transcode JPEG images into JPEG XL. Transcoding preserves the already-lossy compression data from the original JPEG image without any quality loss caused by re-encoding, while making the file size smaller than the original, so my question is what library is using Digikam to transcode JPG to JXL? Thank you -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #106 from Rafael Linux User --- For usability, I think "Version fixed in" should be next to "Status" ... It would be clearer for anyone to identify the resolution of the problem.. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 480921] New: Gwenview eats RAM when generating thumbnails
https://bugs.kde.org/show_bug.cgi?id=480921 Bug ID: 480921 Summary: Gwenview eats RAM when generating thumbnails Classification: Applications Product: gwenview Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- SUMMARY I have 2025 JXL files in a folder. When I open it with Gwenview, it begin to show thumbnails, while literally eating all my RAM till I have no more (I have 16GB RAM). STEPS TO REPRODUCE 1. Create a directory with JXL images (HD resolution mostly) 2. Open previous folder with Gwenview OBSERVED RESULT While generating thumbnails, Gwenview eats all RAM slowly, till system need to take swap storage and then system begin unresponsive. EXPECTED RESULT To show thumbnails without issues. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240202 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 16 GiB of RAM Graphics Processor: AMD Radeon RX 7600 Product Name: B550M Phantom Gaming 4 ADDITIONAL INFORMATION This begin to happen just after transcode all 2025 JPG files to JXL. So I think is related to the way Gwenview is managing JXL thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480726] New: Inconsistency between the information displayed in the window header and the active tab.
https://bugs.kde.org/show_bug.cgi?id=480726 Bug ID: 480726 Summary: Inconsistency between the information displayed in the window header and the active tab. Classification: Applications Product: konsole Version: 23.04.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- SUMMARY The information about the server/user you are working with in the header of the window does not correspond to the information displayed in the active tab. STEPS TO REPRODUCE 1. Add a new tab in Konsole 2. Login to a remote server and observe the server name in Konsole window. 3. Exit from that server (hold the same tab) 4. Login to another remote server (with distinct machine name) OBSERVED RESULT While tab info show correct IP/user, Konsole window title continue showing previous logged user@server_name data. EXPECTED RESULT To show in Konsole window tittle the correct machine data from selected tab. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I suggest to show in both (window title and tab name) IP+server_name@loged user. In fact, in my intranet we usually do a double login: first "general_user" login and then "su -" (that's to say, "root" user). However, Konsole continue showing that user logged is "general_user", despite I'm using "root" account. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480651] Exporting to JXL lowers the colour depth to 8 bpp
https://bugs.kde.org/show_bug.cgi?id=480651 --- Comment #9 from Rafael Linux User --- (In reply to Maik Qualmann from comment #8) > The problem with the AppImage in up to date Linux distributions is already > known, see this Bug 480134 > > Maik That's perfect. I thought I should let you know, but I see it wasn't necessary because you already knew. Thanks for adding the 16bit functionality so quickly. -- You are receiving this mail because: You are watching all bug changes.
