[kwin] [Bug 451158] With display scaling, incorrect cursor scaling on non-XWayland-using GTK and Electron apps due to their lack of support for the cursor-shape-v1 protocl
https://bugs.kde.org/show_bug.cgi?id=451158 sac changed: What|Removed |Added CC||mila...@eclipso.de --- Comment #10 from sac --- (In reply to Nate Graham from comment #9) > Given that we have no good options available to fix this in KDE code, and > that there's a clear path forward for the developers of the GTK and Electron > toolkits, I think unfortunately we have to call this an upstream issue. I'll > mention it on https://community.kde.org/Plasma/Wayland_Showstoppers. This seems to be https://gitlab.gnome.org/GNOME/gtk/-/issues/5567 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459161] Inconsistent cursor size on Wayland
https://bugs.kde.org/show_bug.cgi?id=459161 sac changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 470057] Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 sac changed: What|Removed |Added Component|Clipboard |general Target Milestone|1.0 |--- CC||aleix...@kde.org Product|plasmashell |plasma-wayland-protocols Version|master |1.10.0 Flags|Wayland+, X11- | --- Comment #1 from sac --- Wayland & clipboard should be synced, as this was implemented here: https://phabricator.kde.org/D1973 https://blog.martin-graesslin.com/blog/2016/07/synchronizing-the-x11-and-wayland-clipboard/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462093] Add support for clipboard sharing (copy-paste) under Wayland + KVM/QEMU + Spice
https://bugs.kde.org/show_bug.cgi?id=462093 sac changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=470057 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470057] Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 sac changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=462093 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470057] New: Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 Bug ID: 470057 Summary: Shared Clipboard of Wayland applications is not working for VMs Classification: Plasma Product: plasmashell Version: master Platform: Other URL: https://gitlab.freedesktop.org/spice/linux/vd_agent/-/ issues/26 OS: All Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: mila...@eclipso.de Target Milestone: 1.0 Flags: Wayland+, X11- STEPS TO REPRODUCE 1. install vanilla Kubuntu 23.04 in a virtualbox VM 2. install virtualbox guest additions & enable shared clipboard between host & VM 3. configure Kubuntu to start in Wayland and reboot OBSERVED RESULT it's possible to copy & paste values in xWayland applications (e.g. FF in X mode) from host to VM and vice versa. Copy & pasting in native wayland applications fails. EXPECTED RESULT should be possible to use copy & paste for Wayland VMs. See also the upstream bug for Wayland to provide an API for VM (virtualbox & VMWare). However, plain Ubuntu (gnome Wayland) is able to sync the wayland & x clipboard so that it's possible to use the shared clipboard in VMs. For compatibility, it would be awesome if Kubuntu could sync to the x clipboard completely, too. -- You are receiving this mail because: You are watching all bug changes.
[kweather] [Bug 457300] FR: Graphs UI improvements
https://bugs.kde.org/show_bug.cgi?id=457300 sac changed: What|Removed |Added CC||mila...@eclipso.de --- Comment #2 from sac --- Would be awesome to be able to edit graphs, similar as portfolio-performance.info (open source linux version available). They use nested pie charts, heat maps and every graph is editable and can be filtered (diagram style, hide or add values, adjust data range [1 year back, 2 years in the future], mouse over description for every data point...). Something like this would be awesome for categories: https://jscharting.com/examples/chart-types/donut/nested-pie/ Or this via Apache ECharts (open source Javascript charts library): https://echarts.apache.org/examples/en/editor.html?c=sunburst-book -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463996] SHA256 fingerprint of device certificate: null
https://bugs.kde.org/show_bug.cgi?id=463996 sac changed: What|Removed |Added Version|unspecified |22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463996] SHA256 fingerprint of device certificate: null
https://bugs.kde.org/show_bug.cgi?id=463996 --- Comment #2 from sac --- Created attachment 155508 --> https://bugs.kde.org/attachment.cgi?id=155508=edit SHA256 null bug Encryption info in the android app shows null for both device certificate and remote device certificate. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463996] SHA256 fingerprint of device certificate: null
https://bugs.kde.org/show_bug.cgi?id=463996 sac changed: What|Removed |Added CC||sachins...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from sac --- The issue is still present in version 1.21.1 SOFTWARE/OS VERSIONS Linux: Pop!_OS 22.04 LTS x86_64 Android: 12 KDE App version 1.21.1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 sac changed: What|Removed |Added CC||mila...@eclipso.de --- Comment #48 from sac --- Not fixed for me in a wayland session: - Kubuntu 21.10 backports - Plasma 5.24.1 - Frameworks 5.91 - Qt 5.15.2 - tested in a virtualbox v6.1.32 VM Workaround: disable the kscreen2 service (System Settings > Startup and Shutdown > Background Services), logout, login (re-enabling kscreen2 service directly resizes the VM window to 800x600, X session is not affected for me). In which Plasma version should this be / or was this fixed for wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 sac changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427542] [Wayland] Context menu closes when a notification disappears
https://bugs.kde.org/show_bug.cgi?id=427542 sac changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 --- Comment #17 from sac --- You probably have to select table mode in the settings > monitor. Works great on my convertible ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437123] [Wayland] virtual keyboard is not triggered for Xwayland applications
https://bugs.kde.org/show_bug.cgi?id=437123 --- Comment #5 from sac --- Thx, done ( https://gitlab.freedesktop.org/xorg/xserver/-/issues/1179 ) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437123] [Wayland] virtual keyboard is not triggered for Xwayland applications
https://bugs.kde.org/show_bug.cgi?id=437123 --- Comment #2 from sac --- Unfortunately, FF touch input on wayland seems to be generally broken on Kubuntu 20.10 currently. So also with MOZ_ENABLE_WAYLAND=1 keyboard wasn't triggered and other touch input was lagging or not working at all. However, Opera is not triggering the keyboard, too. Is it working for you for any simple Xwayland application? Or do I have to test with Neon? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437123] New: [Wayland] virtual keyboard is not triggered for GTK applications
https://bugs.kde.org/show_bug.cgi?id=437123 Bug ID: 437123 Summary: [Wayland] virtual keyboard is not triggered for GTK applications Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mila...@eclipso.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY With a tablet it's not possible to use the virtual keyboard with GTK based applications like Firefox. STEPS TO REPRODUCE 1. Open Firefox on a tablet or touch device 2. Try to enter a website address 3. OBSERVED RESULT Virtual keyboard is not showing. EXPECTED RESULT Virtual keyboard is shown as for any other KDE application. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Desktop icons cannot be interacted with via touch
https://bugs.kde.org/show_bug.cgi?id=366462 --- Comment #27 from sac --- BTW: Works great for me: - Lenovo Yoga 900S - neon-unstable-20201112-1102.iso Tested: - touchable icon on standard desktop - context menu for a long touch on desktop - touchable icon & context menu in Dolphin (nice box animation) - all tested also with desktop scale 1,5 Absolutely awesome, amazing work ;) @Patrick probably worth a try with Fedora, but might be sth. weird with your Lenovo (although they're usally really good with Linux) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400959] Locked sidebar changes size
https://bugs.kde.org/show_bug.cgi?id=400959 sac changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #6 from sac --- Pretty cool, fixed. Many thanks for the explanation & reminder ;) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400959] Locked sidebar changes size
https://bugs.kde.org/show_bug.cgi?id=400959 --- Comment #3 from sac --- >Since the preview pane is now on the right of Dolphin I didn't find any option to display a preview inside a pane (left or right). Dolphin just shows preview instead of the file symbol. In that case yes, if the preview option inside a pane was removed completely, this issue would be irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416027] Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 sac changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from sac --- Thanks for the tip. I tried it and activated "allow resizing maximized windows from window edges". Then I was only able to resize windows at the corner. However, I reverted it back to defaults with resizing maximized windows deactivated and now I can correctly close. Seems this was just a glitch on my side. Many thanks ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416027] New: Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 Bug ID: 416027 Summary: Window close button is not positioned correctly in the corner Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: mila...@eclipso.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. open a window that has a close button 2. maximize the window 3. move the mouse cursor (blindly) in the very upper right corner (blindly move the mouse diagonally) 4. click OBSERVED RESULT the window is not closed EXPECTED RESULT window should close, as it does with the plastik theme, where the close button is correctly in the outmost corner. Should have some importance, because I think most people move the mouse blindly to the corner, and then expect the window to close after click, without aming for the close button. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415683] New: KSettings > Screen Rotation doesn't rotate touchscreen & generates xinput error
https://bugs.kde.org/show_bug.cgi?id=415683 Bug ID: 415683 Summary: KSettings > Screen Rotation doesn't rotate touchscreen & generates xinput error Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwintouchscreen Assignee: kwin-bugs-n...@kde.org Reporter: mila...@eclipso.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY On laptops screen rotation is only rotating the scree, but not the touchscreen, so touch input remains unrotated. STEPS TO REPRODUCE 1. goto Settings > Display > Rotate the screen by 180° on laptops that have devices with duplicate names (e.g. Lenovo Yoga 900s) OBSERVED RESULT Screen and touchpad are rotated, but touchscreen coordinates are not rotated. EXPECTED RESULT Coordinate Transformation Matrix must be applied for touchscreen as well. ADDITIONAL INFORMATION This happens because Settings is executing the following command: xrandr -o inverted xinput set-prop "ELAN21EF:00 04F3:2283" --type=float "Coordinate Transformation Matrix" -1 0 1 0 -1 1 0 0 1 xinput set-prop "Synaptics TM2714-003" --type=float "Coordinate Transformation Matrix" -1 0 1 0 -1 1 0 0 1 This leads to the following error: "Warning: There are multiple devices matching 'ELAN21EF:00 04F3:2283'. To ensure the correct one is selected, please use the device ID, or prefix the device name with 'pointer:' or 'keyboard:' as appropriate. unable to find device ELAN21EF:00 04F3:2283" So instead, settings should call the following (notice the pointer arg): xrandr -o inverted xinput set-prop "pointer:ELAN21EF:00 04F3:2283" --type=float "Coordinate Transformation Matrix" -1 0 1 0 -1 1 0 0 1 xinput set-prop "pointer:Synaptics TM2714-003" --type=float "Coordinate Transformation Matrix" -1 0 1 0 -1 1 0 0 1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files to directory on NTFS/FAT file system owned by another user [KIO::FileCopyJob::slotResult]
https://bugs.kde.org/show_bug.cgi?id=368287 sac changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #44 from sac --- Seems it was just a HW failure on my side (faulty DVD drive which caused irritations). While this lead to BSODs in Windows in some situations, I guess a few applications crashes in Kubuntu are OK in those situations, although I can no longer reproduce it because I destroyed the faulty drive. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files to directory on NTFS/FAT file system owned by another user [KIO::FileCopyJob::slotResult]
https://bugs.kde.org/show_bug.cgi?id=368287 sac changed: What|Removed |Added Status|RESOLVED|REOPENED CC||mila...@eclipso.de Resolution|FIXED |--- --- Comment #43 from sac --- Seems this bug was reintroduced in Kubuntu 19.04 ( https://bugs.kde.org/show_bug.cgi?id=395553 ). Moving any files to an NTFS network folder produces a "access denied" messsage > retry > "file no longer existing". If a huge number of files & folders is moved several k applications crash :/ Since this seems to be happen regularly, it might be a good idea to add this use case to the general tests. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 186376] Should be able to show original location for items placed in the trash
https://bugs.kde.org/show_bug.cgi?id=186376 sac changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400959] Locked sidebar changes size
https://bugs.kde.org/show_bug.cgi?id=400959 sac changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 sac changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #12 from sac --- Great news (spent the whole day restoring backups and was currently looking for more). I also had no other missing files, apart from the symlink. However, notifications of failed copies / moves are worrying, even more so if the original is no longer available. Nevertheless, fantastic to have you here to dig into this, many thanks ;) (we have hundreds of SLES servers in our company, where our linux admins need to proof via checksums that the eventual migration was successful. So I guess Linux/rsync/robocopy/KDE can copy files reliably in general, however guess these trash issues are more relevant & important to the end user that uses linux privately on his desktop) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #9 from sac --- Created attachment 116330 --> https://bugs.kde.org/attachment.cgi?id=116330=edit Link not copied & no message of faulty copy With the attached folder, the (broken) link "cache-ss-desktop" is not copied. In addition, here we get not even a system notification that the move was faulty. Same procedure: 1. extract temp1.tar.gz to Desktop & remove it to trash 2. Open Trash within Dolphin 3. Drag & Drop the deleted folder to the Desktop BTW: maybe related, but these kind of errors seem to be common: https://bugs.kde.org/show_bug.cgi?id=162211 https://www.reddit.com/r/linux/comments/1nvho0/warning_theres_a_horrible_bug_in_kde_that_doesnt/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #8 from sac --- Of course, but it was also not shown in Dolphin (data loss). Were you able to reproduce with a clean live? Let me know if you need additional infos ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #6 from sac --- BTW: I was able to reproduce with the live image of http://cdimage.ubuntu.com/kubuntu/releases/18.10/release/kubuntu-18.10-desktop-amd64.iso I only moved .kde to trash & drag & dropped it to desktop. There was no error notification there, but the folder was also not moved. It was deleted from trash, but didn't show up on Desktop at all. Sth. is totally wrong here :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #5 from sac --- Sure, output below. But the access denied error your referring to is most probably due to the deleted folder in trash. Because the source is deleted, the source folder is no longer accessible in Dolphin. /home/ss/.kde: insgesamt 4 lrwxrwxrwx 1 ss ss 20 Nov 14 12:50 cache-ss-desktop -> /var/tmp/kdecache-ss drwxrwxr-x 4 ss ss 4096 Nov 12 18:32 share /home/ss/.kde/share: insgesamt 8 drwxrwxr-x 3 ss ss 4096 Nov 14 01:25 apps drwxrwxr-x 2 ss ss 4096 Nov 12 21:21 config /home/ss/.kde/share/apps: insgesamt 4 drwxrwxr-x 2 ss ss 4096 Nov 14 02:26 color-schemes /home/ss/.kde/share/apps/color-schemes: insgesamt 4 -rw-r--r-- 1 ss ss 2745 Nov 14 02:26 Breeze.colors /home/ss/.kde/share/config: insgesamt 8 -rw--- 1 ss ss 29 Nov 12 20:02 kdebugrc -rw--- 1 ss ss 3289 Nov 12 21:21 kdeglobals -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #3 from sac --- Created attachment 116304 --> https://bugs.kde.org/attachment.cgi?id=116304=edit Unsuccessful folder move, system tray notification The system tray notification at the end says: move task failed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 --- Comment #2 from sac --- >So where is the data loss then if the folder exists at the destination. Usually, I would expect my OS to tell me what was not moved/copied exactly. Nevertheless: looking at the .kde folder on my desktop, I see that the symbolic links & cache was not moved. You should be able to reproduce it with the exact folder: 1. backup ~/.kde 2. delete ~/.kde (move to trash) 3. Open Trash within Dolphin 4. Drag & Drop the deleted folder to the Desktop (folder view) > Select Move (my desktop is located at the standard location ~/Schreibtisch, localalized german, guess in english this is ~/Desktop) Reproduced it again and will attach a screencapture. What I think is critical is not the unsuccessful move, but that the source is deleted, even if the move is unsuccessful and there is the system notification (that is not showing what file / folder specifically was not moved successful). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400990] New: Data loss due to an unsuccessful folder move task
https://bugs.kde.org/show_bug.cgi?id=400990 Bug ID: 400990 Summary: Data loss due to an unsuccessful folder move task Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mila...@eclipso.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Data loss due to an unsuccessful folder move task. STEPS TO REPRODUCE 1. Delete a folder (e.g. ~/.kde) 2. Open Trash within Dolphin 3. Drag & Drop the deleted folder to the Folder Desktop > Select Move OBSERVED RESULT Data loss. There's a message that the copy was not successful, but the old folder is no longer visible in trash (however .kde was exisiting in ~/Desktop). EXPECTED RESULT No data loss. If a folder move is not successful, the old folder shouldn't be deleted & there should be no folder at the target location. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400969] New: Delete Date & Original path is not shown within trash folder
https://bugs.kde.org/show_bug.cgi?id=400969 Bug ID: 400969 Summary: Delete Date & Original path is not shown within trash folder Product: dolphin Version: 18.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mila...@eclipso.de CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Currently there's no way to sort for the recent deleted files in the trash folder. Also verifying the file properties doesn't show the delete date or original path. STEPS TO REPRODUCE 1. Open trash folder 2. Try to identify the file that was deleted most recently OBSERVED RESULT Delete Date & Original path is not shown within trash folder EXPECTED RESULT Delete Date & Original path should show within trash folder and one should be able to sort according to trash date. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400959] New: Locked sidebar changes size
https://bugs.kde.org/show_bug.cgi?id=400959 Bug ID: 400959 Summary: Locked sidebar changes size Product: dolphin Version: 18.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mila...@eclipso.de CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 116257 --> https://bugs.kde.org/attachment.cgi?id=116257=edit Original locked height SUMMARY The size of the locked sidebar panes is not fix (even if locked). Compare attached screens (especially places & preview pane height). STEPS TO REPRODUCE 1. Use the complete sidebar hight (e.g. show places, folders & preview pane) 2. Resize the preview pane hight as small as possible 3. Lock sidebar 4. Preview some videos (mouse over video thumbs) OBSERVED RESULT Sidebar pane heights change. EXPECTED RESULT Sidebar is locked & keeps the size of the panes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400959] Locked sidebar changes size
https://bugs.kde.org/show_bug.cgi?id=400959 --- Comment #1 from sac --- Created attachment 116258 --> https://bugs.kde.org/attachment.cgi?id=116258=edit Height changed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379432] Folder label length in folder view decreases with icon size
https://bugs.kde.org/show_bug.cgi?id=379432 --- Comment #14 from sac --- Created attachment 116251 --> https://bugs.kde.org/attachment.cgi?id=116251=edit Horizontal Space between icons Does anyone no why there is still a space between the icons or how I can get rid of this, too? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400949] New: Dolphin doesn't find linux hidden files & doesn't search if Baloo is deactivated
https://bugs.kde.org/show_bug.cgi?id=400949 Bug ID: 400949 Summary: Dolphin doesn't find linux hidden files & doesn't search if Baloo is deactivated Product: dolphin Version: 18.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mila...@eclipso.de CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Dolphin cannot find hidden files, because Baloo is not indexing them. According to the second bug, this is by design (although I disagree here, also in windows - where are even more inexperienced users - hidden files show in search results if they are shown in Explorer). Solution could be to make Baloo only index hidden files & folders, when those are actually shown in Dolphin. Independent from that, Dolphin should also search when Baloo is deactivated and maybe show a notification "search can be slow, because the indexing service is disabled". Dolphin doesn't show windows hidden files (https://bugs.kde.org/show_bug.cgi?id=184462) Baloo unable to find files in hidden folders (https://bugs.kde.org/show_bug.cgi?id=391252) STEPS TO REPRODUCE 1. Open Dolphin 2. Press CTRL+F 3. Search for "plasma-org.kde.plasma.desktop-appletsrc" OBSERVED RESULT No results. EXPECTED RESULT File is found. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358418] Alignment of widgets to grid can prevent optimal sizes and alignments for some widgets.
https://bugs.kde.org/show_bug.cgi?id=358418 sac changed: What|Removed |Added CC||mila...@eclipso.de --- Comment #15 from sac --- The workaround from the reddit thread is no longer working: >Edit >/usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml, >find function updateGridSize (at line ~100) and change >LayoutManager.cellSize.width and height to 1. Any other workaround or idea how to disable Grid? BTW: in 2012 there was an option in Kubuntu (Right click on a empty area of the Desktop > Default Desktop Settings > View. Change "Layout" to "Grid Desktop"), but it's no longer available in QML. The spacing was reduced already and is tracked here: https://bugs.kde.org/show_bug.cgi?id=379432 , including a workaround from me to further reduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379432] Folder label length in folder view decreases with icon size
https://bugs.kde.org/show_bug.cgi?id=379432 --- Comment #13 from sac --- Kind of a workaround (mentioned in Kubuntuforum): 1. Edit "/usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderView.qml" 2. Replace "var iconWidth = iconSize + (2 * units.largeSpacing) + (2 * units.smallSpacing);" with "var iconWidth = iconSize + (4 * units.largeSpacing) + (2 * units.smallSpacing); //Multiplier changed to 4" 3. Replace "var iconHeight = iconSize + (theme.mSize(theme.defaultFont).height * plasmoid.configuration.textLines) + (4 * units.smallSpacing);" with "var iconHeight = iconSize + (theme.mSize(theme.defaultFont).height * plasmoid.configuration.textLines) + (2 * units.smallSpacing); //Multiplier changed to 2" I'm not sure if the "Grid Way" is the right solution. Personally, I'd love to have an option to position the Icons freely myself, without any Grid constraints. Disadvantage: wouldn't be that accurate, Advantage: I can gain space and position them exactly where I want, so that the icon doesn't "jump" to the near grid line. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #15 from sac --- >Why are you reopening this ticket? How would a global shortcut help an >application that expects mouse events >This will not be fixed in KWin, according to its developers. I think you're not getting the idea here. Forget about mouse events (no mouse events in this bug report). The suggestion of the developers was to adjust global shortcuts. Currently Global Shortcuts shows the following tooltip: "Click on the button, then enter the shortcut like you would in the program. Example for CTRL+A: hold the CTRL key and press A." Instead the tooltip should say: "Click on the button, then enter the shortcut like you would in the program on your keyboard or mouse. Example for CTRL+A: hold the CTRL key and press A. Example for righ mouse button: press the right mouse button. " In addition, the option to assign a shortcut to several actions would be great. (yes, I know, just changing a tooltip is only 5% of the work, but maybe this explains it better. BTW: there are keyboards with a button for a mouse context menu. So even a mouse context menu can be triggered, if there's an action for this KEYBOARD BUTTON. Again: no mouse events here, but I'm able to customize my mouse and am even able to call batch sripts or programs [that might trigger mouse events, ugh forget that]) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 sac changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Summary|Configure Mouse buttons |Configure Mouse buttons |(e.g. setting an arbitrary |(Global Shortcuts should |button to be a "double |accept accept mouse clicks |click.")|to trigger ||actions/keypresses/scripts) Resolution|WONTFIX |--- --- Comment #13 from sac --- >As I said in my first reply: global shortcut triggering is pretty much the >only possibility I can think of. Got you now & renamed the bug. That solution would be perfect. @Christoph Feck GS wouldn't have to genereate mouse clicks in that case. It would just have to learn to accept those as input / trigger. In addition, the option to assign a shortcut to several actions would be great. (Maybe libinput can later cover at least the mousewheel as doubleclick case, that would help in 90% of the cases). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #11 from sac --- OK, we need a proper solution. Apart from security, evdevremapkeys & xbindkeys don't work for productive use (GTK apps like Thunderbird remap input events, one has to click several times to trigger an action after another window had focus; totally messed up). Libinput pointed back to DE & Toolkit ( https://gitlab.freedesktop.org/libinput/libinput/issues/44 ). This affects basically every user and we expect from them to reprogram Kernels if they want to remap sth. properly :( Does noone have good connections to QT, which I guess is our last option here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #9 from sac --- Understood, there's no maintainer for libinput configs ( http://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-lot-of-config.html ) and button remapping is still a big showstopper for default wayland on KDE. However, seems that there's already a deamon available https://github.com/philipl/evdevremapkeys Any plans to utilize sth. like this to offer some customization options in the settings? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #7 from sac --- So, to what should I reassign this? Or should I open a new bug to change the KGlobalAccel API, or systems settings can already make use of the API for mice as well? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 --- Comment #5 from sac <mila...@eclipso.de> --- Seen that the regular, manual rotation is possible now in the settings ;) The solution on the plasma list from Martin relys on Wayland, will there also be an option for automatic screen rotation for xorg? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 sac <mila...@eclipso.de> changed: What|Removed |Added CC||mila...@eclipso.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394529] New: Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 Bug ID: 394529 Summary: Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.") Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: mila...@eclipso.de CC: unassigned-b...@kde.org Target Milestone: --- Hi, would be great to have an option to customize the mouse buttons. There was once btnx or easystroke tools to some customization and there's alot of documentation regarding the usage of the mouse wheel button as doubleclick ( https://help.ubuntu.com/community/MouseCustomizations ). However, even with the shortcut setting it all comes to generate scripts and using additional programs & services in the background all the time, like xbindkeys (that won't work in wayland). It would be great to have some options here. Settings>Shortcuts offers some limited customizability. My Logitech Master MX thumb button is recognized as CTRL+ALT+TAB and I can assign it to "close window", however, I cannot use the same the same shortcut then to close a tab in FF (because it's already assigned to "close window"). An option to assign an action / click / keypress to a mouse button would be great, maybe even specific for some applications. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 392572] New: Data security Risk / all mails visible
https://bugs.kde.org/show_bug.cgi?id=392572 Bug ID: 392572 Summary: Data security Risk / all mails visible Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: mila...@eclipso.de CC: she...@kde.org Target Milestone: --- Hi, I don't want that my mail is visible to everyone. Not sure if someone can create a script, parse some bug reports and pass all the assigned mail adresses in clear text. However I did receive spam with mail adresses that were not known elsewhere. At least there should be an option to disable public visibility of the own mail adress. This is a data security nightmare. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379432] Folder label length in folder view is very short and further decreases with icon size
https://bugs.kde.org/show_bug.cgi?id=379432 --- Comment #8 from sac <j1563...@trbvm.com> --- Comparism Win Kubuntu & Optimized Approximately 8 characters from a filename are displayed, which makes folderview almost unusable. - Alot of space is wasted above, below and next to a desktop symbol item. - Table grid layout is unlogic (symbol item has more height instead of more width) - Renaming a long filename is a mess (no bigger text box is shown that displays the whole filename, while navigating with the mouse within the rename text box a selection is made on the desktop) Comparism & detailed misaligned pixels displayed in the screenshot. Overall FV should be verified in terms of visibility, usability & screen space efficiency. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379432] Folder label length in folder view is very short and further decreases with icon size
https://bugs.kde.org/show_bug.cgi?id=379432 --- Comment #7 from sac <j1563...@trbvm.com> --- Created attachment 61 --> https://bugs.kde.org/attachment.cgi?id=61=edit Kubuntu optimized, Kubuntu & Windows Compareison -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #16 from sac <j1563...@trbvm.com> --- Created attachment 108547 --> https://bugs.kde.org/attachment.cgi?id=108547=edit Side by side comparism 1,5 & 2,0 Exactly, the left sidebar is fine, just the right content area is messed up. BTW: just checked, files are named correctly (as mentioned, they have to be opened in the original size, not zoomed). Attached here is a side-by-side comparism. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #12 from sac <j1563...@trbvm.com> --- You're right, tested with "openSUSE_Krypton.x86_64-5.11.90-Build1.44.iso" (QT 5.10, before I just tested with Neon Live and guess that not all was loaded after logging out and back in). >(which btw, is fixed for next Applications release) Yes, fixed in Krypton ;) >Everything should work fine with 2.0 True, all stuff is fine with 2.0. Just the login screen & desktop effects has not changed with QT5.10 and is still not aliased ( https://bugs.kde.org/attachment.cgi?id=107578 ) with "about system settings -> libraries" = "build against 5.10.0". Env attached. With 1.5 broken: https://bugs.kde.org/attachment.cgi?id=108509 With 2.0 it's OK: https://bugs.kde.org/attachment.cgi?id=108510 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #11 from sac <j1563...@trbvm.com> --- Created attachment 108511 --> https://bugs.kde.org/attachment.cgi?id=108511=edit env -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #10 from sac <j1563...@trbvm.com> --- Created attachment 108510 --> https://bugs.kde.org/attachment.cgi?id=108510=edit 1.5 NOK Desktop effects -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #9 from sac <j1563...@trbvm.com> --- Created attachment 108509 --> https://bugs.kde.org/attachment.cgi?id=108509=edit 2.0 OK Desktop effects -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #6 from sac <j1563...@trbvm.com> --- Created attachment 108488 --> https://bugs.kde.org/attachment.cgi?id=108488=edit Scale 1,5 NOK Plasma 5.11.90 Even worse in Plasma 5.11.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 sac <j1563...@trbvm.com> changed: What|Removed |Added Attachment #107578|Original OK |Scale 1,5 Login NOK description|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #5 from sac <j1563...@trbvm.com> --- Created attachment 108413 --> https://bugs.kde.org/attachment.cgi?id=108413=edit Scale 1,0 OK -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 sac <j1563...@trbvm.com> changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|UNCONFIRMED --- Comment #4 from sac <j1563...@trbvm.com> --- Sry, but this is not fixed. Exactly the same result with Qt 5.10 Beta (tested with KDE Neon devn unstable "deb http://archive.neon.kde.org/testing xenial main"). Same on Qt 5.9.2 (tested with Suse Krypton). Apart from the ugly fonts in Okular and system settings, all log screen images are not aliased, too (after clicking kde menu->logout images for shutdown, logout, restart are totally ugly). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 sac <j1563...@trbvm.com> changed: What|Removed |Added Version|5.37.0 |5.10.5 Blocks||254563 Component|general |common Product|frameworks-kdbusaddons |KScreen Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=254563 [Bug 254563] KDE does not change screen orientation to portrait or flip screen around in Tablet mode -- You are receiving this mail because: You are watching all bug changes.
[krandr] [Bug 254563] KDE does not change screen orientation to portrait or flip screen around in Tablet mode
https://bugs.kde.org/show_bug.cgi?id=254563 sac <j1563...@trbvm.com> changed: What|Removed |Added Depends on||384066 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=384066 [Bug 384066] Auto-rotate screen not working for Accelerometer sensors -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #2 from sac <j1563...@trbvm.com> --- Created attachment 107578 --> https://bugs.kde.org/attachment.cgi?id=107578=edit Original OK Open this image with 100% (original size) and compare the "e" in "Hint: to find out or configure" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 --- Comment #1 from sac <j1563...@trbvm.com> --- Created attachment 107577 --> https://bugs.kde.org/attachment.cgi?id=107577=edit Scale 1,5 NOK Open this image with 100% (original size) and compare the "e" in "Hint: to find out or configure" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdbusaddons] [Bug 384066] New: Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066
Bug ID: 384066
Summary: Auto-rotate screen not working for Accelerometer
sensors
Product: frameworks-kdbusaddons
Version: 5.37.0
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: j1563...@trbvm.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
When the tablet / convertible is rotated Fedora 26 & Ubuntu 17.04 & 17.10 are
automatically rotating the screen as well, which is not working in KDE :/
- Rotation is possible with iio-sensor-proxy (IIO sensors to D-Bus proxy,
https://github.com/hadess/iio-sensor-proxy) that comes pre-shipped with Kubuntu
& Neon.
- executing "monitor-sensor" generates proper d-bus messages ("Accelerometer
orientation changed: left-up"), Yoga 900s tablet Kernel 4.11.12
"With gnome this is picked up by gnome-settings-daemon if I'm correct. How do I
inform lightdm to use this information to auto-rotate the screen? Although it's
definitely possible to run my own script to pull all the time for changes, I
prefer to have it in an event loop that checks d-bus anyway, so I'm not
suddenly creating some kind of battery drain."
https://ubuntuforums.org/showthread.php?t=2343374
https://superuser.com/questions/1147784/how-to-auto-rotate-the-screen-using-yoga-900s-accelerometer
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 sac <j1563...@trbvm.com> changed: What|Removed |Added Summary|Monitor Scaling breaks font |Monitor Scaling / HiDPI |Anti-Aliasing |support breaks font ||Anti-Aliasing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] New: Monitor Scaling breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 Bug ID: 384031 Summary: Monitor Scaling breaks font Anti-Aliasing Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: j1563...@trbvm.com CC: plasma-b...@kde.org Target Milestone: 1.0 If System Settings > Monitor > Scaling is greater than 1 (tested with 1.5 & 2), Anti-Aliasing of fonts breaks in important applications. E.g. System Settings > Desktop Effects > Effects is broken: no anti-aliasing in the right content window. Same happens to Okular which can no longer use anti-aliasing for PDFs. This is just related to the Scaling factor. Just setting fonts DPI forced to 144 alone, is working with anti-aliasing. Only the scaling mechanism breaks some stuff here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380272] Filenames crippled in folderview
https://bugs.kde.org/show_bug.cgi?id=380272 sac <j1563...@trbvm.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from sac <j1563...@trbvm.com> --- Version specified. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380272] Filenames crippled in folderview
https://bugs.kde.org/show_bug.cgi?id=380272 --- Comment #3 from sac <j1563...@trbvm.com> --- BTW: measurements were taken with smybol size small medium (right click on desktop -> Icons -> Icon size -> small medium). But if you look at the screenshot, those issues appear with every size. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380272] Filenames crippled in folderview
https://bugs.kde.org/show_bug.cgi?id=380272 --- Comment #2 from sac <j1563...@trbvm.com> --- Sry, tested on Kubuntu 17.04, Plamsa 5.9.4, Frameworks 5.31.0 Windows 7 But it's the same with KDE Neon & Plasma 5.9.95. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380272] New: Filenames crippled in folderview
https://bugs.kde.org/show_bug.cgi?id=380272 Bug ID: 380272 Summary: Filenames crippled in folderview Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: j1563...@trbvm.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105741 --> https://bugs.kde.org/attachment.cgi?id=105741=edit Comparism Win Kubuntu & Optimized Approximately 8 characters from a filename are displayed, which makes folderview almost unusable. - Alot of space is wasted above, below and next to a desktop symbol item. - Table grid layout is unlogic (symbol item has more height instead of more width) - Renaming a long filename is a mess (no bigger text box is shown that displays the whole filename, while navigating with the mouse within the rename text box a selection is made on the desktop) Comparism & detailed misaligned pixels displayed in the screenshot. Overall FV should be verified in terms of visibility, usability & screen space efficiency. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462 --- Comment #8 from sac <j1563...@trbvm.com> --- >The code you've quotes is from Task Manager and not related to Folder View. Sry, was the only component where "MouseEventListener" was referenced. Still wonder why all other components are working well with single touches (like the menu button in the upper left corner). Is it not possible to use a similar "mechanism" for folderview? At least as workaround until Qt Quick event handling code has been reworked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462
--- Comment #6 from sac <j1563...@trbvm.com> ---
>The problem is that MouseEventListener in frameworks doesn't have touch event
>support.
Many thanks for the verification & debugging. Is this a bug in QT?
In general QT should support this:
"By default, QGuiApplication translates the first touch point in a QTouchEvent
into a QMouseEvent. This makes it possible to enable touch events on existing
widgets that do not normally handle QTouchEvent. "
http://doc.qt.io/qt-5/qtouchevent.html
"The MouseArea type allows mouse and touch events to be handled in a QML
application."
http://doc.qt.io/qt-5/qtquick-usecase-userinput.html
Is this just related to the following (I guess onContainsMouseChanged will
never fire in case of touch)?
https://cgit.kde.org/kde-workspace.git/tree/plasma/desktop/applets/tasks/package/contents/ui/Task.qml?id=e9023a81186145ac4b33268a08759ab00df61466
onClicked: {
if (isGroupParent) {
groupDialog.target = task;
groupDialog.visible = true;
} else {
tasks.activateItem(model.Id, true);
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 366462] Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462 sac <j1563...@trbvm.com> changed: What|Removed |Added Version|5.7.3 |master --- Comment #4 from sac <j1563...@trbvm.com> --- Still trying to determine the affected component. By coincidence I got some message after a false update indicating that the plugin is "/usr/lib64/qt5/plugins/kf5/kio/desktop.so". However I didn't find the source, "https://cgit.kde.org/plasma-desktop.git/tree/containments/folder/plugin/foldermodel.cpp?id=c8f43a8fa712171cb62c53000a3343a8eb08f1a9; seems to be sth. else :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462 --- Comment #2 from sac <j1563...@trbvm.com> --- Hm, I fix it myself. Is anyone mainting the code or can point to the widget source code? If I submit the patch would there be anyone here to include this in KDE? (think I'm somehow lost here or not at the right place) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366463] New: Regression: Installer crash cause grub-efi-amd64-signed could not be installed
https://bugs.kde.org/show_bug.cgi?id=366463 Bug ID: 366463 Summary: Regression: Installer crash cause grub-efi-amd64-signed could not be installed Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: j1563...@trbvm.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Built image from yesterday is not installing on my Dell Venue 11 Pro, because grub-efi-amd64-signed could not be installed. Either there is an error messsage and the installer crashes after clicking OK, or the installation completes without error message, but no boot loader is installed / configured and the systems is just showing the Grub2 shell after reboot. Dells UEFI implementation tend to be buggy and currently only Fedora is able to create a boot entry. For all other distros I have to select the file grubx64.uefi directly in UEFI in order to boot. But every other distro can at least complete the installation, even Neon did this with the previous installation images. But the current one is mostly crashing. neon-useredition-20160804-1018-amd64.iso Reproducible: Sometimes Steps to Reproduce: 1. Boot the live image 2. Try to complete the installation 3. Actual Results: Installer crashes after confirmation of the appearing error message "grub-efi-amd64-signed could not be installed" Expected Results: No crash Was working with the previous installation images, but those are no longer available. Only the current broken one neon-useredition-20160804-1018-amd64.iso can be downloaded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] New: Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462 Bug ID: 366462 Summary: Regression: All desktop items cannot be clicked / touched / launched Product: plasmashell Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: j1563...@trbvm.com If the desktop "folder view" is used (or in the widget of the usual desktop) there is no chance on a touchscreen to launch the items. Reproducible: Always Steps to Reproduce: 1. Boot Live CD 2. Activate desktop folder view 3. try to touch & open "Home" from desktop Actual Results: No chance to launch or open any desktop items on a tablet / convertible / touchscreen. Expected Results: That all items can be touched & open as in pre 5.7. Kernel & drivers are working correctly. If the symbol is hovered via touchpad, so that the selection box is shown, it can be tapped via touchscreen and the folder / item opens correctly. Seems that sth. expects a hover event before click, which of course isn't happening with touchscreens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357453] Plasma5 Crash on folder view desktop while selecting properties of an icon
https://bugs.kde.org/show_bug.cgi?id=357453 sac <j1563...@trbvm.com> changed: What|Removed |Added Platform|Ubuntu Packages |Compiled Sources Depends on||355570 --- Comment #2 from sac <j1563...@trbvm.com> --- "I fixed this by doing the following in Dolphin: Configure Dolphin > Services > Uncheck 'File to activity linking plugin'." --> workaround working for me, too; Amazing that a crash for the complete Shell that affects >90% of the userbase can be open for months (because of a new feature that is probably only used/known by 1%). Reason why we're not flooded with tickets is that the automatic bug reporting cannot be used for this one (I was just able to create the dump by luck after many trys). I suggest to deactivate Dolphin " 'File to activity linking plugin'" by default as a first solution measure. Fixing this feature (whatever it does) can be done in a seperate INC. If someone's currently collecting donations for a QA, ping me and I'll support ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355570] plasmashell crashes every time I right click on a folder and move the mouse up and down on the context menu.
https://bugs.kde.org/show_bug.cgi?id=355570 sac <j1563...@trbvm.com> changed: What|Removed |Added CC||j1563...@trbvm.com --- Comment #3 from sac <j1563...@trbvm.com> --- (In reply to John Choate from comment #2) > I fixed this by doing the following in Dolphin: > Configure Dolphin > Services > Uncheck 'File to activity linking plugin'. > Plasmashell and dolphin have not crashed when hovering mouse in the context > menu since I did that. Great thanks. I already created 357453, including a detailed dumb of the crash until I found this bug and workaround by coincidence. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355570] plasmashell crashes every time I right click on a folder and move the mouse up and down on the context menu.
https://bugs.kde.org/show_bug.cgi?id=355570 sac <j1563...@trbvm.com> changed: What|Removed |Added Blocks||357453 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358100] New: Plasma 5 is not working in VirtualBox with 3d acceleration
https://bugs.kde.org/show_bug.cgi?id=358100 Bug ID: 358100 Summary: Plasma 5 is not working in VirtualBox with 3d acceleration Product: plasmashell Version: master Platform: Compiled Sources URL: https://www.virtualbox.org/ticket/14102 OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: j1563...@trbvm.com CC: bhus...@gmail.com, plasma-b...@kde.org Since Plasma 5 every KDE distribution cannot be used in VirtualBox with 3d acceleration enabled. Reproducible: Always Steps to Reproduce: If 3D acceleration is enabled, KDEs login screen appears normally, one can login. After logging in, the Desktop appears, everything seems to be normal. BUT: 1.) Right clicking somewhere at the desktop doesn't bring up the context menu 2.) Clicking the "KDE" Menu: the KDE Menu appears, but the Control Bar disappears completely 3.) When starting an application in KDE Menu (which can still be opened with Alt+F1), the application seems to start, but no application window appears 4.) Trying to get out of KDE and switch to a console TTY (STRG+ALT+F1) just switches to a smaller screen but in this KDEs background image remains. ==> So the Desktop is completely unusable, it isn't even possible to get a terminal window, so one even can't examine "glxinfo" or some logs... Actual Results: 3d accelerated GUI elements are hidden (basically the complete shell). Expected Results: 3d acceleration usable. Seems to be mainly related to the VirtualBox graphic driver, however the guys over there are currently struggling. It would be great if someone has an idea about a major change in graphics between Plasma 4 and 5 to give them an idea how to fix this in VirtualBox. All major companies, plattforms and server farms in datacenters seem to be mainly using VMWare, which is working with Plasma 5. However, currently no KDE Linux distribution can be used with the open source VirtualBox, so I doubt we can spread open source for virtual enterprise platforms, if the basics don't work. Would be fantastic if someone can verify this from KDE side. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357453] Plasma5 Crash on folder view desktop while selecting properties of an icon
https://bugs.kde.org/show_bug.cgi?id=357453 --- Comment #1 from sac <j1563...@trbvm.com> --- Initially occured with Kubuntu 16.04 Daily Snapshot, but also confirmed with a standard, stable Live Fedora 23 KDE (tested as VM in VirtualBox): - simply start VM with the live CD - right click on the desktop icon and select properties, as soon as the desktop has loaded Should be easy to reproduce, otherwise draw some selection rectengles on the desktop and repeat the right click -> properties (for me plasmashell crashed everytime) and I think this is relevant for all KDE Linux distributions. Please confirm and reproduce. Don't think it's HW related, but just in case, I have a Intel i5-5675C that seems to suffer from elision lock crashes if there's no exception list for glibc: https://bugzilla.kernel.org/show_bug.cgi?id=103351 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357453] New: Plasma5 Crash on folder view desktop while selecting properties of an icon
https://bugs.kde.org/show_bug.cgi?id=357453 Bug ID: 357453 Summary: Plasma5 Crash on folder view desktop while selecting properties of an icon Product: plasmashell Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: j1563...@trbvm.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.3.0-2-generic x86_64 Distribution: Ubuntu Xenial Xerus (development branch) -- Information about the crash: - What I was doing when the application crashed: right click icon / file and select properties - Unusual behavior I noticed: plasmashell crash and restart - Custom settings of the application: None, Live CD, only changed destkop to "folder view" -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa96da6b8c0 (LWP 3344))] Thread 9 (Thread 0x7fa958e15700 (LWP 3350)): #0 0x7fa9681be83d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa96c254c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa96c2568d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa95af5e4a9 in QXcbEventReader::run (this=0x11c4080) at qxcbconnection.cpp:1229 #4 0x7fa9688b487e in QThreadPrivate::start (arg=0x11c4080) at thread/qthread_unix.cpp:331 #5 0x7fa9679a066a in start_thread (arg=0x7fa958e15700) at pthread_create.c:333 #6 0x7fa9681c9e4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fa952418700 (LWP 3371)): #0 0x7fa964fa8a24 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa964f64301 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa964f6441c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa968aec2eb in QEventDispatcherGlib::processEvents (this=0x7fa94c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa968a932fa in QEventLoop::exec (this=this@entry=0x7fa952417ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa9688af8d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa96b120c85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa9688b487e in QThreadPrivate::start (arg=0x128bf60) at thread/qthread_unix.cpp:331 #8 0x7fa9679a066a in start_thread (arg=0x7fa952418700) at pthread_create.c:333 #9 0x7fa9681c9e4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fa9447ce700 (LWP 3388)): #0 0x7fa964f642b0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa964f6441c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa968aec2eb in QEventDispatcherGlib::processEvents (this=0x7fa93c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #3 0x7fa968a932fa in QEventLoop::exec (this=this@entry=0x7fa9447cdce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #4 0x7fa9688af8d4 in QThread::exec (this=) at thread/qthread.cpp:503 #5 0x7fa96b120c85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fa9688b487e in QThreadPrivate::start (arg=0x1475210) at thread/qthread_unix.cpp:331 #7 0x7fa9679a066a in start_thread (arg=0x7fa9447ce700) at pthread_create.c:333 #8 0x7fa9681c9e4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fa942ab6700 (LWP 3391)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa96d4aebd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fa96d4aec19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fa9679a066a in start_thread (arg=0x7fa942ab6700) at pthread_create.c:333 #4 0x7fa9681c9e4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fa9419d7700 (LWP 3393)): #0 0x7fa968aea2c7 in QTimerInfoList::timerWait (this=0x7fa8b4002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:380 #1 0x7fa968aeb6ce in timerSourcePrepareHelper (timeout=0x7fa9419d6b24, src=) at kernel/qeventdispatcher_glib.cpp:127 #2 timerSourcePrepare (source=, timeout=0x7fa9419d6b24) at kernel/qeventdispatcher_glib.cpp:160 #3 0x7fa964f6389d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa964f6423b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa964f6441c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fa968aec2eb in QEventDispatcherGlib::processEvents (this=0x7fa8b40008c0, flags=...) at
