[Bluedevil] [Bug 373083] New: Bluetooth is marked as disabled, but I can connect from command line
https://bugs.kde.org/show_bug.cgi?id=373083 Bug ID: 373083 Summary: Bluetooth is marked as disabled, but I can connect from command line Product: Bluedevil Version: 5.8.4 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: gigal...@gmail.com Target Milestone: --- Created attachment 102524 --> https://bugs.kde.org/attachment.cgi?id=102524&action=edit User interface showing the mouse connected but the bluetooth disabled Bluetooth is marked as disabled, and clicking on "enable bluetooth" doesn't do anything, but I can connect the mouse from the command line. Once it is connected the systray icon changes to show a device is connected but still reports the bluetooth as off. Rfkill output: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: yes 3: hci0: Bluetooth Soft blocked: no Hard blocked: no On Debian, package installed: bluedevil4:5.8.4-1 amd64 KDE Bluetooth stack -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469748] New: Graphical glitches when viewing the attached PDF
https://bugs.kde.org/show_bug.cgi?id=469748 Bug ID: 469748 Summary: Graphical glitches when viewing the attached PDF Classification: Applications Product: okular Version: 23.04.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: lorgar...@gmail.com Target Milestone: --- Created attachment 158941 --> https://bugs.kde.org/attachment.cgi?id=158941&action=edit Problematic PDF SUMMARY While viewing this PDF the rendering is intermittent: sometimes changing page renders it (except a bar on the bottom), sometimes nothing happens. Selecting areas on a page shows the real content (only in the selected region), when the previous page is still visible after a page switch. Chromium of Firefox have no problems with this file. STEPS TO REPRODUCE 1. Open the PDF attached. 2. Switch pages. OBSERVED RESULT Previous page stays on the screen. EXPECTED RESULT Next pages appears on the screen. SOFTWARE/OS VERSIONS Linux: 6.3.1 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents/changes on quit
https://bugs.kde.org/show_bug.cgi?id=353654 Lorenzo changed: What|Removed |Added CC||lorenzofsut...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents/changes on quit
https://bugs.kde.org/show_bug.cgi?id=353654 Lorenzo changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #24 from Lorenzo --- I am using Kate 23.08.4 on Manjaro and this doesn't seem to work for me. These are the settings for 'Sessions': https://gcdnb.pbrd.co/images/FtUBw5mWYTrD.png?o=1 I tried starting kate with kate -s and I get an untitled file. I add some text and quit (as expected no warning to save the file). But when I re-start kate the contents of the untitled file is lost. I'd expect the file and session to be saved and then restored based on the above options? I did notice that when quitting for a second there is an orange line on the left highlighting changes ( I have this feature on) but then re-starting the changes are lost. I think either the setting options are misleading or something is not working because the user gets no warning to save the file and this can lead to data loss -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436268] New: Caps lock not work correctly on virtual machine vmware MSI P75
https://bugs.kde.org/show_bug.cgi?id=436268 Bug ID: 436268 Summary: Caps lock not work correctly on virtual machine vmware MSI P75 Product: neon Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: lorenzo.ven...@vivaldi.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY When press caps lock to lock the capital letter and press again to disable caps lock doesn't disable and the icon continue to blink for several seconds STEPS TO REPRODUCE 1. Install the last kde neon on windows 10 with vmware workstation player 13 2. Press on caps lock 3. Press on caps lock again OBSERVED RESULT Caps lock doesn't disable and icon on desktop continues to blink, led of MSI have not a correct behaviour EXPECTED RESULT Caps Lock goes disabled, caps lock led on keyboard switch-off SOFTWARE/OS VERSIONS Windows: Hosted by windows 10 machine Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437137] New: Impossible to acquire rectangular region
https://bugs.kde.org/show_bug.cgi?id=437137 Bug ID: 437137 Summary: Impossible to acquire rectangular region Product: Spectacle Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: loren...@inbox.lv CC: k...@david-redondo.de Target Milestone: --- Created attachment 138445 --> https://bugs.kde.org/attachment.cgi?id=138445&action=edit Impossible to acquire rectangular region SUMMARY Impossible to acquire rectangular region STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.21.5-x86_64 (available in About System) KDE Plasma Version: 5.21.5-x86_64 KDE Frameworks Version: plasma-framework-5.82.0-x86_64 Qt Version: qt5-5.15.2-x86_64 ADDITIONAL INFORMATION Operating System: Slackware 14.2 (current) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.10.37 OS Type: 64-bit Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] New: Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 Bug ID: 463357 Summary: Task Manager uses theme icons, so multiple window application icons are not shown Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: lorenzofsut...@gmail.com Target Milestone: 1.0 SUMMARY *** It seems Task Manager uses the theme's icons for windows. In various cases, in particular when grouping is not selected, using actual windows' icons is more beneficial and makes the task manager more useful. *** STEPS TO REPRODUCE 1. Currently the icons used by the task manager come from the selected theme 2. For applications with multiple windows this means that even if those windows have different icons which may also indicate the window's functionality these are displayed with the 'parent' application icon (taken from the theme See the screenshots for a couple of good examples: - QjackCtl [1] is an application which can create multiple windows each of which has different functionalities and therefore icons. The task manager in this case shows all the same windows. - In the second screenshot Rosegarden [2] opens different kinds of editing windows: notice each has a slightly different icon to indicate the kind of editor. This is not reflected by the task manager which is using the applications 'stock' theme icon. It would be good to have the functionality (and option) to use the actual window icon displayed in the task manager. This might be related to https://bugs.kde.org/show_bug.cgi?id=384357 but is more general and focuses on the Virtualbox icon, not on the underlying functionality. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #1 from Lorenzo --- Created attachment 154762 --> https://bugs.kde.org/attachment.cgi?id=154762&action=edit multiple windows application icons not shown in task manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #2 from Lorenzo --- Created attachment 154763 --> https://bugs.kde.org/attachment.cgi?id=154763&action=edit multiple windows application icons not shown in task manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #3 from Lorenzo --- Add: another case is applications with the same name. For instance "Element" is a well-know Matrix client but also a (maybe less well known) music sequencer / patchbay. In the screenshot below you can see that Element (the sequencer) is incorrectly given the other Element icon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #4 from Lorenzo --- Created attachment 154764 --> https://bugs.kde.org/attachment.cgi?id=154764&action=edit Applications with same name but different (and different icon) are assigned same icon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #6 from Lorenzo --- Hi Fushan Wen, Thanks for checking into this! Actually the fact that all icons are the same (and taken from the theme, in this case Breeze) is exactly the bug... Icons should all be different as foreseen by the app developer because windows are underlining different functionality / behaviour By contrast the 'Present Window' plugin (triggered e.g. by screen edges) correctly show the App's "native" icons. See screenshot below. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Task Manager uses theme icons, so multiple window application icons are not shown
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #7 from Lorenzo --- Created attachment 154795 --> https://bugs.kde.org/attachment.cgi?id=154795&action=edit Example of present windows correctly showing app's native icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463357] Consider allowing windows' custom icons to be shown instead of the themed app icon for Tasks of non-icons only Task Manager
https://bugs.kde.org/show_bug.cgi?id=463357 --- Comment #9 from Lorenzo --- Thanks for your insight Nate. Please also do not forget multi-window applications which use different icons for different (functional) environments like the examples provided (I'm sure there's more in the Linux application ecosystem). As there's probably a degree of personal preference in these cases, IMHO the ideal would be to allow users to chose with some sane defaults. I will say that using theme icons as a default works in most cases, the cited examples being exceptions. Lorenzo -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Lorenzo changed: What|Removed |Added CC||lorenzofsut...@gmail.com --- Comment #22 from Lorenzo --- Hi I am experiencing a similar issue with KDE Plasma 5.26.4 on Manjaro with an Android MTP phone while wanting to use Android File Transfer [1][2] to mount the device and e.g. do rsync or similar (AFT will mount to a 'normal' directory thus allowing terminal operations etc.). Whenever I plug the phone in and select file transfer (i.e. MTP) on the phone, KDE / Dolphin grab it and it results 'busy' to any other application trying to use it. Also there's no 'unmount' / release option. The only work-around I've found is, as reported by other users, to kill kiod5 and then after that run aft-mtp-mount I think it would be great to have either an interface to 'release' a device or maybe have an option in the Removable devices systems setting for this. [1] https://whoozle.github.io/android-file-transfer-linux/ [2] https://wiki.archlinux.org/title/Media_Transfer_Protocol#Android_File_Transfer -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Lorenzo changed: What|Removed |Added CC||llore...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Lorenzo changed: What|Removed |Added CC||lorgar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 --- Comment #18 from Lorenzo --- I can also confirm it is no longer working and I am getting the A04 NO AUTHENTICATE error in KMail on Fedora 40 with a personal Outlook account. I'd really prefer staying on KDE rather than switching over to Thunderbird -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Lorenzo changed: What|Removed |Added Version|5.19.3 |6.1.2 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 373083] Bluetooth is marked as disabled, but I can connect from command line
https://bugs.kde.org/show_bug.cgi?id=373083 --- Comment #1 from Lorenzo --- Some extra context. The integrated bt was disabled by bios. After enabling it and removing the usb bt it started working as supposed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501393] Window focus is lost after activity switch when using multiple activities and screens (Plasma 6.3.2, Frameworks 6.1.1, Qt 6.8.2)
https://bugs.kde.org/show_bug.cgi?id=501393 Lorenzo changed: What|Removed |Added CC||lorenzofsut...@gmail.com --- Comment #9 from Lorenzo --- I'm also hit by this: Plasma 6.3.4 KDE Framework 6.13.0 Manjaro with X11 The same virtual desktop workaround doesn't work form me as I'm having two virtual desktops per activity, which is kind of the point of having activities for me, i.e. having an additional 'dimension' on top of virtual desktops (I imagine virtual desktops like being the X of switching and activities the Y...) A really annoying workaround for me is after switching also doing e.g. META + D two times (show / hide desktop) or a couple of ALT+ TAB to re-focus the correct window. This is particularly painful when working with browsers or file managers as you accidentally click on a hyperlink in the 'old' window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501393] Window focus is lost after activity switch when using multiple activities and screens (Plasma 6.3.2, Frameworks 6.1.1, Qt 6.8.2)
https://bugs.kde.org/show_bug.cgi?id=501393 --- Comment #10 from Lorenzo --- I've actually tested this with Wayland session and this is even more annoying IMHO. When keyboard cycling through an activity with different virtual desktops on each activity the virtual desktop switching 'animation' is triggered and still the focus is on the 'old' window. So it seems that this is not an X11 bug only (which seemed to be hinted from some comments). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501393] Window focus is lost after activity switch when using multiple activities and screens (Plasma 6.3.2, Frameworks 6.1.1, Qt 6.8.2)
https://bugs.kde.org/show_bug.cgi?id=501393
--- Comment #11 from Lorenzo ---
(In reply to Lorenzo from comment #10)
> I've actually tested this with Wayland session and this is even more
> annoying IMHO.
>
> When keyboard cycling through an activity with different virtual desktops on
> each activity the virtual desktop switching 'animation' is triggered and
> still the focus is on the 'old' window.
>
> So it seems that this is not an X11 bug only (which seemed to be hinted from
> some comments).
So this creates two major annoyances and rather unusable UX:
- the virtual desktop switching 'animation' ('fade desktop' in my case) is
triggered
- if I click on what I think is the window in focus on the activity / desktop
because focus is on the old one everything 'jumps' back to that
activity/desktop/window
--
You are receiving this mail because:
You are watching all bug changes.
[kalendar] [Bug 450693] Cannot edit the Google Groupware source
https://bugs.kde.org/show_bug.cgi?id=450693 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it --- Comment #3 from Lorenzo Bettini --- Same for me, and the same problem is present in Korganizer: Version 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 450693] Cannot edit the Google Groupware source
https://bugs.kde.org/show_bug.cgi?id=450693 --- Comment #4 from Lorenzo Bettini --- (In reply to Lorenzo Bettini from comment #3) > Same for me, and the same problem is present in Korganizer: Version 5.21.1 > (22.08.1) I also found the culprit: you must enable the KDE wallet subsystem in KDE settings (it's also best to log out and log in or simply restart the computer). That is required for configuring Google calendars. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 353366] Amarok does not write statistics/metadata to mp3 files
https://bugs.kde.org/show_bug.cgi?id=353366 Lorenzo Bettini changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Lorenzo Bettini --- Yes, I'm still seeing this problem -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489658] New: Release 5.2.3: Incorrect file names for the Windows x64 packages
https://bugs.kde.org/show_bug.cgi?id=489658 Bug ID: 489658 Summary: Release 5.2.3: Incorrect file names for the Windows x64 packages Classification: Applications Product: krita Version: 5.2.3-beta1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: lorenzo.ga...@gmail.com Target Milestone: --- The release announcement for 5.2.3 https://krita.org/en/posts/2024/krita-5-2-3-released/ contains links to nonexistent files (resulting in 404 errors): "64 bits Windows Installer" https://download.kde.org/stable/krita/5.2.3/krita-5.2.3-setup.exe "Portable 64 bits Windows" https://download.kde.org/stable/krita/5.2.3/krita-5.2.3.zip "Debug symbols" https://download.kde.org/stable/krita/5.2.3/krita-5.2.3-dbg.zip The correct filenames (from the directory listing at https://download.kde.org/stable/krita/5.2.3/) are respectively https://download.kde.org/stable/krita/5.2.3/krita-x64-5.2.3-setup.exe https://download.kde.org/stable/krita/5.2.3/krita-x64-5.2.3.zip https://download.kde.org/stable/krita/5.2.3/krita-x64-5.2.3-dbg.zip The main download page https://krita.org/en/download/ has a correct link to the Windows setup package but an incorrect one for the Windows portable package. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489658] Release 5.2.3: Incorrect file names for the Windows x64 packages
https://bugs.kde.org/show_bug.cgi?id=489658 Lorenzo Gatti changed: What|Removed |Added CC||lorenzo.ga...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489658] Release 5.2.3: Incorrect file names for the Windows x64 packages
https://bugs.kde.org/show_bug.cgi?id=489658 Lorenzo Gatti changed: What|Removed |Added URL||https://krita.org/en/posts/ ||2024/krita-5-2-3-released/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 --- Comment #5 from Lorenzo Bettini --- (In reply to wgalen from comment #4) > I am also encountering this after upgrading to 6.0.1 with Arch. For now, I > changed the fixed width font in system settings to a nerd-font patched > FiraCode, and that seems to work fine. I suspect that luisbocanegra found > the cause, and it appears to be intended behavior. > > Can we perhaps get a new setting to control this behavior, or choose a > default fallback font? I'd prefer to not have to use patched fonts to get > the nerd font symbols if there's a way to make that work without breaking > the use case described in QTBUG-110502. Indeed, if I install `ttf-hack-nerd` and then set the "Fixed width" font in System Settings to "Hack Nerd Font 10pt" (the default is "Hack 10pt"), then Konsole shows the nerd font IF you DON'T set any specific font in the profile (it will take the default). The same holds for Kate: DON'T set any font, and it will take the default. As soon as you set a font, either you make sure you select a Nerd font, or it won't work (you experience this bug). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451622] Cursor remains disabled after alt+tabbing a window that disables it
https://bugs.kde.org/show_bug.cgi?id=451622 Lorenzo Rutayisire changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Lorenzo Rutayisire --- (In reply to Vlad Zahorodnii from comment #2) > Are you running X11 or Wayland? On Wayland, it seems to work fine. > > Please reset the bug report status back to REPORTED after providing the > requested information. Oh I'm sorry, this report was from a long time ago and I don't have Manjaro installed anymore. I think it was xorg though (i.e. X11). Setting the status back to REPORTED. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483550] New: Kate uses a too light grey for printing text files
https://bugs.kde.org/show_bug.cgi?id=483550 Bug ID: 483550 Summary: Kate uses a too light grey for printing text files Classification: Applications Product: kate Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: lorebett2...@yahoo.it Target Milestone: --- SUMMARY Since the switch to KDE Plasma 6, Kate uses a too light grey for printing text files: the result is almost unreadable on printed paper STEPS TO REPRODUCE 1. open a text file with Kate 2. print it OBSERVED RESULT The text is printed on a very light grey EXPECTED RESULT The text should be printed as black as it was before SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.2.2 ADDITIONAL INFORMATION The problem can be seen also in print preview -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it --- Comment #28 from Lorenzo Bettini --- I confirm; but this has been marked as resolved? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #30 from Lorenzo Bettini --- (In reply to Zesko from comment #29) > (In reply to Lorenzo Bettini from comment #28) > > I confirm; but this has been marked as resolved? > > How to reproduce your issue? > > I have no problem copying any text from any text editor for example "micro" > in Konsole (Wayland) <> Kate (Wayland) on the same host except VM. > This requires a dependency “wl-clipboard” for that. Sorry, I wasn't clear: I cannot copy and paste from host to VM and vice-versa, when the VM is KDE Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483550] Kate uses a too light grey for printing text files
https://bugs.kde.org/show_bug.cgi?id=483550 --- Comment #2 from Lorenzo Bettini --- (In reply to Christoph Cullmann from comment #1) > Printing i a mess and uses and modifies even parts of the current view > colors, that will need fixing. Yes, I forgot to mention that it also modifies the current view colors. I seem to understand there's a property in katerc for specifying the Printing color scheme, but I find no way of setting that from Kate, and manually setting in katerc doesn't seem to do anything. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 480570] New: Storage size not working with BTRFS with plasma 6 rc1
https://bugs.kde.org/show_bug.cgi?id=480570
Bug ID: 480570
Summary: Storage size not working with BTRFS with plasma 6 rc1
Classification: Frameworks and Libraries
Product: frameworks-kio
Version: unspecified
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: kio-bugs-n...@kde.org
Reporter: lore.rizzo...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
STEPS TO REPRODUCE
1. Install arch on a BTRFS partition (I'm using cachyo which is based on archs)
2. Follow arch wiki steps to install kde-unstable
https://wiki.archlinux.org/title/Official_repositories#kde-unstable
OBSERVED RESULT
- Total and used size is not available in dolphin
- The disk total size plasmoid shows double the actual disk size in the plasma
desktop plasmoid
- The disk used space is 0 in the plasma desktop plasmoid
30/01/24 16:47 dolphin kf.kio.widgets: Could not find mount point for
QUrl("file:///")
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.
[konsole] [Bug 453448] Link recognition ignores port
https://bugs.kde.org/show_bug.cgi?id=453448 Lorenzo Micci changed: What|Removed |Added CC||lorenzom...@gmail.com --- Comment #1 from Lorenzo Micci --- (In reply to suienzan from comment #0) > SUMMARY > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > > > STEPS TO REPRODUCE > 1. `echo http://localhost:8080` > 2. holding `ctrl` and click on the output `http://localhost:8080` or select > it and right click then choose `open link`. > > OBSERVED RESULT > Open link `http://localhost` > > EXPECTED RESULT > Open link `http://localhost:8080` > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Arch linux > (available in About System) > KDE Plasma Version: 5.24.5 > KDE Frameworks Version: 5.93.0 > Qt Version: 5.15.3 > > ADDITIONAL INFORMATION Hi, is attributable to this bug https://bugs.kde.org/show_bug.cgi?id=452978 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455774] New: (Wayland) Opening links with an application which has a window already open doesn't work well like in X11
https://bugs.kde.org/show_bug.cgi?id=455774 Bug ID: 455774 Summary: (Wayland) Opening links with an application which has a window already open doesn't work well like in X11 Product: plasmashell Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: lorenzus.i...@gmail.com Target Milestone: 1.0 Flags: Wayland+, X11-, Brainstorm-, Translation_missing-, Usability+, VisualDesign- Opening links with an application which has a window already open doesn't work well like in X11: - If the opened window is on the same virtual desktop, it won't change focus (1) - If the opened window is on another virtual desktop, the highlighted task manager icon won't appear (2) or it will be broken (clicking on it won't change focus to that window) (3) STEPS TO REPRODUCE (1) 1. Open an application (like a browser) 2. Open another application on the same virtual desktop 3. Open a link in the second app with the first app OBSERVED RESULT (1) Focus doesn't change to the first application when the link is opened EXPECTED RESULT (1) Focus changes to the first application when the link is opened STEPS TO REPRODUCE (2) 1. Open an application (like a browser) 2. Open another application on a different virtual desktop 3. Open a link in the second app with the first app OBSERVED RESULT (2) The highlighted icon of the first app doesn't appear EXPECTED RESULT (2) An highlighted icon of the first app should appear in the task manager. Clicking on this icon should change focus to the first app (where the link is opened) STEPS TO REPRODUCE (3) 1. Open an application (like a browser) 2. Open another application on a different virtual desktop (like Konsole) 3. Open a link in the second app with the first app using the "Search << >> with" function OBSERVED RESULT (3) An highlighted icon of the first app appears in the task manager, but clicking on it doesn't change focus to the first app EXPECTED RESULT (3) An highlighted icon of the first app should appear in the task manager. Clicking on this icon should change focus to the first app (where the link is opened) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.5-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387097] Need ability to read client.maximizeMode since it's currently not a property
https://bugs.kde.org/show_bug.cgi?id=387097 Lorenzo Ianotto changed: What|Removed |Added Version|5.11.3 |5.24.1 CC||lorenzus.i...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387097] Need ability to read client.maximizeMode since it's currently not a property
https://bugs.kde.org/show_bug.cgi?id=387097 Lorenzo Ianotto changed: What|Removed |Added Version|5.24.1 |5.25.1 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455793] New: Add option to choose color mode directly on the print dialog "Options <<"
https://bugs.kde.org/show_bug.cgi?id=455793
Bug ID: 455793
Summary: Add option to choose color mode directly on the print
dialog "Options <<"
Product: print-manager
Version: 22.04.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: dantt...@gmail.com
Reporter: lorenzus.i...@gmail.com
Target Milestone: ---
Add option to choose color mode ("Color" or "Black and White") directly on the
print dialog "Options <<", without the need to modify the printer proprieties
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 451622] New: Cursor remains disabled after alt+tabbing a window that disables it
https://bugs.kde.org/show_bug.cgi?id=451622 Bug ID: 451622 Summary: Cursor remains disabled after alt+tabbing a window that disables it Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: loryrut...@gmail.com Target Milestone: --- SUMMARY *** I'm running an application that disables the cursor on startup through the GLFW call: ``` glfwSetInputMode(g_window, GLFW_CURSOR, GLFW_CURSOR_DISABLED); ``` If I switch window using alt+tab the cursor remains disabled, the only choice I have to enable it back is to kill the application that disabled it. *** STEPS TO REPRODUCE 1. Run any application that disables the cursor 2. Alt+tab to another window 3. The cursor is still disabled! OBSERVED RESULT The cursor remains disabled after switching window through alt+tab. EXPECTED RESULT The cursor should appear back... SOFTWARE/OS VERSIONS Manjaro Linux 21.2.4 KDE ADDITIONAL INFORMATION I don't know if it can be of any interest, but I'm using multiple monitors (3 monitors right now). I'm not sure if this is a bug or an expected behavior, however this is really unhandy when debugging GLFW applications (games) using an IDE. In this situation I used to alt+tab frequently to switch from the window to the code, put breakpoints, interact with IDE's UI and having the cursor disabled doesn't permit me to do nearly anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451622] Cursor remains disabled after alt+tabbing a window that disables it
https://bugs.kde.org/show_bug.cgi?id=451622 --- Comment #1 from Lorenzo Rutayisire --- I've made a minimalistic C++ application that grabs the cursor (through GLFW) and then goes to sleep(100) after some iterations. If I alt+tab the application the cursor does not get ungrabbed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it --- Comment #5 from Lorenzo Bettini --- by the way, when you're on a VM, you might want to install the SSH server and run `sudo pkcon refresh && sudo pkcon update` via SSH. Thanks for the workaround, it works for me as well! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 --- Comment #6 from Lorenzo Bettini --- Some additional information: the update actually breaks something. For example, `discover` had been uninstalled. Moreover, some desktop effects, like blur, are not available anymore. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 428058] Dolphin does not synchronise with GoogleDrive
https://bugs.kde.org/show_bug.cgi?id=428058 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it --- Comment #4 from Lorenzo Bettini --- When I experience this problem on EndeavourOS (Arch) I see this core dump in journalctl: ``` systemd-coredump[27929]: [🡕] Process 27927 (kioslave5) of user 1000 dumped core. Module linux-vdso.so.1 with build-id f4c0c67a495415ccf56ef21d6eaadfebc34186ec Module libffi.so.8 with build-id f90d8b734f6de9b25faedb8cbfab7054dafc0a42 Module libgmodule-2.0.so.0 with build-id 5da4523e8d6b5c244a0193e27093d1e61f6ac9e4 Module libsqlite3.so.0 with build-id 5f711261aabe285f02a673ded77a37b413afbfa2 Module libxml2.so.2 with build-id b710b880b0d4e9c93554fa632129db44c20632cd Module libgobject-2.0.so.0 with build-id e67b3a29cecdd98c3d8bd6eb7524a812331b20a2 Module libgio-2.0.so.0 with build-id bce5a3881708e1e885fa1c9c32e2769a6447c411 Module libaccounts-glib.so.0 with build-id 39159b874fc693de010c8ddec4ce367b91fab590 Module libKF5Wallet.so.5 with build-id aeaed59d3b3b82bf83380c60772ce74c79d0c0e3 Module libsignon-qt5.so.1 with build-id 6f4ec4d20513e77c5a8d2be8db4c2d0c4adabf75 Module libaccounts-qt5.so.1 with build-id cb30e02c93768b98f22a8022d7674629f917dc5b Module libKPimGAPICore.so.5 with build-id 5906e932df7604299f6ec49f3910d187cdc5c0a0 Module libkaccounts.so.2 with build-id e6c549debf1b03904c6f794f8a04524a28c3c9fb Module libKPimGAPIDrive.so.5 with build-id e663f6e409596a42604e44926a158ef249f160fe Module gdrive.so with build-id 39e93f29431596dde6c7a6f37c83b28a2f0d5a43 Module libbrotlicommon.so.1 with build-id a4ba3f4b4571c8272343b621da812a6e24a202a7 Module libbrotlidec.so.1 with build-id 45defc036e918e0140a72f1fbce6e7692d38241d Module libbz2.so.1.0 with build-id 919597c477c9b2cb9cdbb7745ed6494ac0e6da60 Module libgraphite2.so.3 with build-id 47761dc11e553f519cde97ed9ee985be12ccdae2 Module libfreetype.so.6 with build-id 26c5f833068ff72660d1975cbc2074c3eb47fad8 Module libGLX.so.0 with build-id 2a08836c6e6126ce9ff4496b6aacaf29ae9b4e7b Module libGLdispatch.so.0 with build-id 501765b3a78d668860fa54229b18107473aeda4c Module libXdmcp.so.6 with build-id 8ca0792d23c8b8b4c0864297512349292bea5955 Module libXau.so.6 with build-id 1c67764663e07bec24d8951e5fd93f4d165979ff Module libgpg-error.so.0 with build-id 3801187d42c4955bd93c605451430cdf1b164e63 Module libmd4c.so.0 with build-id 2151dba72cdc9960097e6e960a58a2f03c8bb96e Module libharfbuzz.so.0 with build-id 1d9dee49dd99162c3f83eb3259c3c88c6b4cd7fe Module libpng16.so.16 with build-id 2dc0bce07f199bf983c07a05fb95a6f4af83a9b3 Module libGL.so.1 with build-id 912ac4f37a9fa2d5abcf7a9088c9983cfe46f12a Module libQt5Widgets.so.5 with build-id 81df494250e82a872761420306c3f308d05b935b Module libxcb-keysyms.so.1 with build-id 333e5eb4075795f947c924a2085f17e2e2ae7147 Module libxcb.so.1 with build-id 0d1ef11740a5daad2ee331e812a51aa6574af222 Module libresolv.so.2 with build-id c915c72668282861a813f7ea3c0780f37b681dc0 Module libkeyutils.so.1 with build-id ac405ddd17be10ce538da3211415ee50c8f8df79 Module libkrb5support.so.0 with build-id adf65240a4d2aba772d7a0772b4d015469934113 Module libcom_err.so.2 with build-id be99503e12b86d78d6ede2f0d1ffb66408a37576 Module libk5crypto.so.3 with build-id eb8220b8f36675aac769450be4cb6bb7f97ec38a Module libkrb5.so.3 with build-id 72d26767c5cb1097db75a5f5bff88860233c902b Module libpcre.so.1 with build-id 845483dd0acba86de9f0313102bebbaf3ce52767 Module libicudata.so.70 with build-id e1dcc2a88cfaafed882d09c90c668af0eed4efed Module libgcrypt.so.20 with build-id db45f5d5e0f7af1e77324fea1885f974619ad268 Module libcap.so.2 with build-id f56c6cd6ad4d35053340d7ff2f8f954498796739 Module liblz4.so.1 with build-id e63600ab23b2f6997f42fac2fa56e1f02ce159a1 Module liblzma.so.5 with build-id 8b615460aa230708c5183f16bede67aa0437d95e Module libdbus-1.so.3 with build-id 74f2ab9c60512f3a93c932c3f627564d42e0b11e Module librt.so.1 with build-id 75484da2d6f1515189eefa076e0a40328834cd16 Module libblkid.so.1 with build-id 057b6bc8eebd42d1f5cafe4f4ac72646aae1f2c5 Module libQt5Gui.so.5 with build-id 5b8c60ab05ea0f4e00a7562f3bdc2cbcbe4a9208 Module libQt5X11Extras.so.5 with build-id e41614d2e35852f913bf00633d635cfbf5a90dce Module libX11.so.6 with build-id 5ba5798d193c0065014b8c6252a0678671c8d478 Module libKF5WindowSystem.so.5 with build-id 10d0f0de888eb46a1fddcb91ef4ea4dcb3f117f2 Module libcrypto.so.1.1 with build-id 4c926b672d97886b123e03a008387aecf0786de4 Module libssl.so.1.1 with build-id 1024424ab33a3767da03f4fdb1fc1b02479f160f Module libgssapi_krb5.so.2 with build-id e6e098ad51ce7bdd3dbe902d7b0f69a90f8a9e08 Module libKF5DBusAddons.so.5 with build-id 2d3ca02cc76d878e00280b05ec8728c677dbd6b1 Module ld-linux-x86-64.so.2 with build-id 040cc3dd10461562f177df39e3be2f3704258c3c Module libgcc_s.so.1 with build-id 7f8508bb914546ada778809b64b99d234337d835 Module libm.so.6 with build-id
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408279] Battery and brightness widget doesn't show correct time remaining estimate
https://bugs.kde.org/show_bug.cgi?id=408279 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it --- Comment #24 from Lorenzo Bettini --- (In reply to Frank Kruger from comment #22) > Given openSUSE Tumbleweed with Plasma 5.19.5, I am also observing a battery > widget with frozen remaining time (upower shows the correct time). I could > solve the issue, however, by unticking "restore previous session" on login. > Seems to be weird, but maybe it helps to pin down the culprit. Still a problem with Plasma 5.20.4 (Manjaro) and your workaround seems to solve it... but this way we lose one of the cool things of Plasma :( -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 430381] New: HTML version of email has first line smaller than rest of body
https://bugs.kde.org/show_bug.cgi?id=430381 Bug ID: 430381 Summary: HTML version of email has first line smaller than rest of body Product: kmail2 Version: 5.15.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: alejandro_a...@yahoo.es Target Milestone: --- SUMMARY The HTML version of emails kmail is producing emails with the first line smaller than the rest of the body without being instructed to do so STEPS TO REPRODUCE 1. Write an email with two lines saying "this is a test" without any further formatting 2. Send email to yourself 3. Email received has first line smaller OBSERVED RESULT The produced html code: This is another test This is a test-- Notice the EXPECTED RESULT This is another test This is a test-- SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Testing KDE Plasma Version: 20.08.2 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408279] Battery and brightness widget doesn't show correct time remaining estimate
https://bugs.kde.org/show_bug.cgi?id=408279 --- Comment #26 from Lorenzo Bettini --- (In reply to Fushan Wen from comment #25) > Cannot reproduce. Can someone still be able to reproduce? It's been a long time, and I cannot reproduce it anymore either -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489835] New: Can't set shortcut for opening Kickoff
https://bugs.kde.org/show_bug.cgi?id=489835 Bug ID: 489835 Summary: Can't set shortcut for opening Kickoff Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: lorenzus.i...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 171429 --> https://bugs.kde.org/attachment.cgi?id=171429&action=edit Kickoff not saving shortcuts SUMMARY Kickoff doesn't apply any keyboard shortcut STEPS TO REPRODUCE 1. Open Kickoff settings 2. Go to keyboard shortcuts section 3. Type a new shortcut 4. Apply changes OBSERVED RESULT Sometimes the shortcut gets deleted immediately after clicking "Apply", some other times it stays but it doesn't work and disappears after closing and reopening the settings. EXPECTED RESULT The shortcut should be saved and it should work. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489835] Can't set shortcut for opening Kickoff
https://bugs.kde.org/show_bug.cgi?id=489835 Lorenzo Ianotto changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Lorenzo Ianotto --- The bug randomly went away and now Kickoff works correctly -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420423] New: HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423
Bug ID: 420423
Summary: HTML font size is affected by view zoom in composer
Product: kmail2
Version: 5.9.3
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: alejandro_a...@yahoo.es
Target Milestone: ---
First of all, i am not sure if this has already been fixed in more modern
versions of kmail (using Debian Stable here).
STEPS TO REPRODUCE
1. Compose an email in HTML mode with, let's say Noto Sans at 11 points of size
2. Make text bigger or smaller for viewing (Ctrl+Mouse scroll wheel, or
Ctrl+{,+})
3. Send message
4. Received message will have a font size proportional to the zoom you used
composing the message
It's also notable that when kmail receives emails composed like this (a CC for
yourself) the size of the text will appear normal so you won't notice but other
people with different emails clients will
In my mind, zoom of the text should be independent of the font size sent in the
HTML. But that's my two cents
OBSERVED RESULT
Example of the HTML code generated by the composer
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Stable 10.3
KDE Plasma Version: 5.14.5.1
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3+dfsg1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Touchpad-KCM] [Bug 395348] [Libinput backend] enable/disable touchpad setting is gray out and unavailable since plasma 5.13
https://bugs.kde.org/show_bug.cgi?id=395348 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391969] New: System tray icons and text corruption.
https://bugs.kde.org/show_bug.cgi?id=391969 Bug ID: 391969 Summary: System tray icons and text corruption. Product: plasmashell Version: 5.12.3 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: lnz...@gmail.com Target Milestone: 1.0 Created attachment 111465 --> https://bugs.kde.org/attachment.cgi?id=111465&action=edit tray corruption. System tray icons and text get corrupted and become unreadable, clicking doesn't work as intended (I click on an icon and it does not open the corresponding applet). Happens every time I click on a network connection in the tray applet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390824] baloo_file crashes randomly
https://bugs.kde.org/show_bug.cgi?id=390824 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it --- Comment #1 from Lorenzo Bettini --- I'm experiencing the same problem (crashes after some time): Application: baloo_file (5.44.0) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-19-generic x86_64 Distribution: Ubuntu Bionic Beaver (development branch) After the crash, the only way to use baloo again is to disable it and enable it again, so that the index is recreated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388701] New: Extremely slow scrolling applications and tearing.
https://bugs.kde.org/show_bug.cgi?id=388701 Bug ID: 388701 Summary: Extremely slow scrolling applications and tearing. Product: plasmashell Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: lnz...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 109744 --> https://bugs.kde.org/attachment.cgi?id=109744&action=edit Can see the tearing in kickoff. When I scroll applications with the mouse wheel (e.g. during a search) the scroll is extremely slow and I can see the top of the letters tear. I understand it could have something to do with libinput. Any other info just ask. arch kernel4.14.12-1-ARCH (64-bit) KDE Plasma 5.11.5 KDE Frameworks 5.41.0 Qt 5.10.0 libinput 1.9.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #28 from Lorenzo Murarotto --- Found a workaround (for arch linux): 1. Install xf86-input-evdev 2. Create file /etc/X11/xorg.conf.d/10-evdev.conf (Delete existing if needed). 3. Put https://pastebin.com/Y5cePdTj in said file. 4. Reboot. Tell me if it worked :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389933] New: Dolphin crashes when trying to drag any element
https://bugs.kde.org/show_bug.cgi?id=389933 Bug ID: 389933 Summary: Dolphin crashes when trying to drag any element Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lorenzo.ra...@yandex.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.2) Qt Version: 5.9.3 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: I'm trying to use Wayland as much as possible so it's about two weeks i use it as my daily driver; since the latest update (Plasma 5.12 - 5/2/2018), Dolphin started force-closing everytime i try to drag and drop any element. To be precise, it crashes in the exact moment i move the cursor: i can easily double click or long click a folder, for instance, with no issues, till the second i move the cursor (both with physical button click and double touch). The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd7b36df8c0 (LWP 15152))] Thread 3 (Thread 0x7fd79153b700 (LWP 15154)): #0 0x7fd7b300427d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd7a63026f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd7a62bee74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd7a62bf330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd7a62bf49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd7ad23d6cb in QEventDispatcherGlib::processEvents (this=0x7fd78c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fd7ad1e5e2a in QEventLoop::exec (this=this@entry=0x7fd79153ad00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fd7ad00e8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7fd7ad013709 in QThreadPrivate::start (arg=0x2155ba0) at thread/qthread_unix.cpp:368 #9 0x7fd7a83926ba in start_thread (arg=0x7fd79153b700) at pthread_create.c:333 #10 0x7fd7b301441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fd79c43e700 (LWP 15153)): #0 0x7fd7b300874d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd7a62bf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd7a62bf49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd7ad23d6cb in QEventDispatcherGlib::processEvents (this=0x7fd7940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fd7ad1e5e2a in QEventLoop::exec (this=this@entry=0x7fd79c43dcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fd7ad00e8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7fd7ad6bc315 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fd7ad013709 in QThreadPrivate::start (arg=0x7fd7ad930d40) at thread/qthread_unix.cpp:368 #8 0x7fd7a83926ba in start_thread (arg=0x7fd79c43e700) at pthread_create.c:333 #9 0x7fd7b301441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fd7b36df8c0 (LWP 15152)): [KCrash Handler] #6 QDrag::mimeData (this=0x1100) at kernel/qdrag.cpp:154 #7 0x7fd7ada745ab in QDragManager::QDragManager (this=0x23e7a30) at kernel/qdnd.cpp:81 #8 0x7fd7ada7464e in QDragManager::self () at kernel/qdnd.cpp:93 #9 0x7fd7ada730fc in QDrag::exec (this=0x2411200, supportedActions=..., defaultDropAction=) at kernel/qdrag.cpp:284 #10 0x7fd7b2c5e997 in KItemListController::startDragging() () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #11 0x7fd7b2c5eb12 in KItemListController::mouseMoveEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #12 0x7fd7b2c5bbe4 in KItemListController::processEvent(QEvent*, QTransform const&) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #13 0x7fd7b2c6dba2 in KItemListView::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #14 0x7fd7ae1d1b9c in QApplicationPrivate::notify_helper (this=, receiver=0x21beae0, e=0x7ffcc0339e90) at kernel/qapplication.cpp:3722 #15 0x7fd7ae1d95a7 in QApplication::notify (this=0x7ffcc033ad10, receiver=0x21beae0, e=0x7ffcc0339e90) at kernel/qapplication.cpp:3481 #16 0x7fd7ad1e7df8 in QCoreApplication::notifyInternal2 (receiver=0x21beae0, event=0x7ffcc0339e90) at kernel/qcoreapplication.cpp:1018 #17 0x7fd7ae1d1ede in QCoreApplication::sendSpontaneousEvent (event=event@entry=0x7ffcc0339e90, rec
[kmail2] [Bug 394505] Many "unnamed" identities are created without intervention
https://bugs.kde.org/show_bug.cgi?id=394505 Alejandro Lorenzo changed: What|Removed |Added CC||alejandro_a...@yahoo.es -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394505] Many "unnamed" identities are created without intervention
https://bugs.kde.org/show_bug.cgi?id=394505 --- Comment #2 from Alejandro Lorenzo --- I am also seeing this behaviour, will try to remove from emailidentities -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391969] System tray icons and text corruption.
https://bugs.kde.org/show_bug.cgi?id=391969 --- Comment #3 from Lorenzo Murarotto --- Can confirm this doesn't happen in plasmashell 5.12.5 with same setup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385964] Unusable system tray
https://bugs.kde.org/show_bug.cgi?id=385964 Lorenzo Murarotto changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Lorenzo Murarotto --- Can confirm it's solved for me with KDE Plasma 5.12.5. KDE Frameworks version: 5.46.0 Qt version: 5.11.0 Kernel version: 4.14.48-2-MANJARO Nvidia driver version: 340.106 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 498412] New: kdialog crash without open itself
https://bugs.kde.org/show_bug.cgi?id=498412 Bug ID: 498412 Summary: kdialog crash without open itself Classification: Applications Product: kdialog Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: zern...@gmail.com Target Milestone: --- Created attachment 177217 --> https://bugs.kde.org/attachment.cgi?id=177217&action=edit a pdf collection of screen shots and data SUMMARY Kdialog crashes after some minutes in silent mode, wasting memory STEPS TO REPRODUCE 1. Open VSCodium 2. Choose Open file or folder OBSERVED RESULT Nothing happens on GUI, but in process monitor I can see kdialog wasting memory up to 20GB and I get a system tray notification of kdialog crash after 4 minutes EXPECTED RESULT Use the dialog to choose a folder or a file SOFTWARE/OS VERSIONS Operating System: Ubuntu Studio 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-50-lowlatency (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5900XT 16-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060/PCIe/SSE2 ADDITIONAL INFORMATION https://errors.ubuntu.com/user/49e9916a884c07910437faac38503e8edd6878fce2da29190322f05585051b806489f937462a890ee3472525d1a265699895237b8e814ae214c0fb55b776 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499005] New: After starting Plasma, clicking on System Tray Widget doesn't open it
https://bugs.kde.org/show_bug.cgi?id=499005 Bug ID: 499005 Summary: After starting Plasma, clicking on System Tray Widget doesn't open it Classification: Plasma Product: plasmashell Version: 6.2.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Tray widget Assignee: plasma-b...@kde.org Reporter: lorenzus.i...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 177591 --> https://bugs.kde.org/attachment.cgi?id=177591&action=edit A reproduction of the bug SUMMARY After starting Plasma, clicking on System Tray Widget doesn't open it. The bugs goes away once the widget is clicked or new icons appear. STEPS TO REPRODUCE 1. Start Plasma (logging in or with 'plasmashell --replace'); 2. Click on one icon in the system tray. OBSERVED RESULT The system tray does not open and the arrow on the right twitches. EXPECTED RESULT The system tray opens. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G Memory: 7.2 GiB of RAM Graphics Processor: AMD Radeon R7 Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop X510QA_F510QA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499265] New: Sytem monitor fail to save and reload sensors
https://bugs.kde.org/show_bug.cgi?id=499265 Bug ID: 499265 Summary: Sytem monitor fail to save and reload sensors Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor widgets Assignee: plasma-b...@kde.org Reporter: zern...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 177783 --> https://bugs.kde.org/attachment.cgi?id=177783&action=edit Screen shot of System monitor with error on sensors SUMMARY System monitor show empty sensors box on cpu, memory, disk, network STEPS TO REPRODUCE 1. open System monitor I get the error 2. close System monitor 3. delete /home/user/.cache/plasma-systemmonitor/ 4. open System monitor works fine 5. close System monitor 6. open System monitor I get the error again, this lead me to and endless loop OBSERVED RESULT With the System monitor I get the error again and again, this lead me to and endless loop EXPECTED RESULT The System monitor working fine SOFTWARE/OS VERSIONS Operating System: Ubuntu Studio 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 Kernel Version: 6.11.0-1007-lowlatency (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5900XT 16-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 503648] New: unmet dependencies: linux-modules-nvidia-560-6.11.0-1012-lowlatency:
https://bugs.kde.org/show_bug.cgi?id=503648 Bug ID: 503648 Summary: unmet dependencies: linux-modules-nvidia-560-6.11.0-1012-lowlatency: Classification: I don't know Product: kde Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: zern...@gmail.com Target Milestone: --- Risoluzione della dipendenza non riuscita: The following packages have unmet dependencies: linux-modules-nvidia-560-6.11.0-1012-lowlatency: Dipende: linux-signatures-nvidia-6.11.0-1012-lowlatency (= 6.11.0-1012.13) but 6.11.0-1012.13+1 is to be installed I've received this messages from KDE discover update ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-modules-nvidia-560-6.11.0-1012-lowlatency 6.11.0-1012.13 ProcVersionSignature: Ubuntu 6.11.0-1013.14-lowlatency 6.11.11 Uname: Linux 6.11.0-1013-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.30.0-0ubuntu4.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 2 08:26:05 2025 InstallationDate: Installed on 2024-08-29 (246 days ago) InstallationMedia: Ubuntu-Studio 24.04 LTS "Noble Numbat" - Release amd64 (20240424.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1013-lowlatency root=UUID=d8411dec-5cbe-4664-b607-4f3b9f9d22b4 ro quiet splash preempt=full threadirqs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-1013-lowlatency N/A linux-backports-modules-6.11.0-1013-lowlatency N/A linux-firmware 20240913.gita34e7a5f-0ubuntu2.6 RfKill: SourcePackage: linux-restricted-modules-lowlatency UpgradeStatus: Upgraded to oracular on 2025-01-11 (111 days ago) dmi.bios.date: 03/22/2024 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5013 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5013:bd03/22/2024:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 472635] Feature request: Add shortcut for "Enlarge Font" and "Shrink Font"
https://bugs.kde.org/show_bug.cgi?id=472635 Lorenzo Bettini changed: What|Removed |Added CC||lorebett2...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422938] When tiling a window to half the screen, present others as targets for tiling to the other side
https://bugs.kde.org/show_bug.cgi?id=422938 Lorenzo Rizzotti changed: What|Removed |Added CC||lore.rizzo...@gmail.com --- Comment #11 from Lorenzo Rizzotti --- (In reply to Natalie Clarius from comment #9) > This now exists as an extension: KWin Script "Snap Assist" by emvaized: > https://store.kde.org/p/1875687. This unfortunately no longer works -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466998] New: Illegal instruction on ARMv7
https://bugs.kde.org/show_bug.cgi?id=466998 Bug ID: 466998 Summary: Illegal instruction on ARMv7 Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: david.dilore...@verizonconnect.com Target Milestone: --- SUMMARY Valgrind does not recognize an instruction when executing code from an external shared library, and thus generates a SIGILL. Memcheck did not report any bad jumps, so it might indeed be an issue with valgrind not recognizing the instruction. There is also an unhandled arm-linux syscall, which I am not sure if it's related. STEPS TO REPRODUCE The instruction not recognized by valgrind is contained within an external library, which unfortunately I cannot legally share. I realize it's usually pointless to submit a bug report without enabling you to reproduce the issue, but in this case maybe knowing the unrecognized instruction opcode might be enough? (I am no expert). See below for the full valgrind log, including the unrecognized opcode. OBSERVED RESULT Here is the valgrind log: ==9735== Memcheck, a memory error detector ==9735== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==9735== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info ==9735== Command: ./dr_app_simulator frame0.yuv 800 554 ==9735== ==9735== Conditional jump or move depends on uninitialised value(s) ==9735==at 0x4F4DA7C: ??? (in /opt/lib/libSNPE.so) ==9735== ==9735== Use of uninitialised value of size 4 ==9735==at 0x4F4DA7E: ??? (in /opt/lib/libSNPE.so) ==9735== --9735-- WARNING: unhandled arm-linux syscall: 345 --9735-- You may be able to write your own handler. --9735-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --9735-- Nevertheless we consider this a bug. Please report --9735-- it at http://valgrind.org/support/bug_reports.html. --9735-- WARNING: unhandled arm-linux syscall: 345 --9735-- You may be able to write your own handler. --9735-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --9735-- Nevertheless we consider this a bug. Please report --9735-- it at http://valgrind.org/support/bug_reports.html. disInstr(thumb): unhandled instruction: 0xEF0C 0x0CF6 ==9735== valgrind: Unrecognised instruction at address 0x4e927d3. ==9735==at 0x4E927D2: ??? (in /opt/lib/libSNPE.so) ==9735== Your program just tried to execute an instruction that Valgrind ==9735== did not recognise. There are two possible reasons for this. ==9735== 1. Your program has a bug and erroneously jumped to a non-code ==9735==location. If you are running Memcheck and you just saw a ==9735==warning about a bad jump, it's probably your program's fault. ==9735== 2. The instruction is legitimate but Valgrind doesn't handle it, ==9735==i.e. it's Valgrind's fault. If you think this is the case or ==9735==you are not sure, please let us know and we'll try to fix it. ==9735== Either way, Valgrind will now raise a SIGILL signal which will ==9735== probably kill your program. ==9735== ==9735== Process terminating with default action of signal 4 (SIGILL) ==9735== Illegal opcode at address 0x4E927D3 ==9735==at 0x4E927D2: ??? (in /opt/lib/libSNPE.so) ==9735== ==9735== HEAP SUMMARY: ==9735== in use at exit: 0 bytes in 0 blocks ==9735== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==9735== ==9735== All heap blocks were freed -- no leaks are possible ==9735== ==9735== Use --track-origins=yes to see where uninitialised values come from ==9735== For lists of detected and suppressed errors, rerun with: -s ==9735== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Illegal instruction EXPECTED RESULT Valgrind should recognize the opcode. Note that when executed directly (without valgrind), the program runs normally, so I don't think there is an actual illegal instruction in the library itself. SOFTWARE/OS VERSIONS I am working on a ARM embedded device, here is the output of uname -a Linux phoenix 3.18.115 #3 SMP PREEMPT Sat Jan 14 13:19:03 KST 2023 armv7l GNU/Linux Note that the hardware supports 64bit, but the installed OS is 32bit. ADDITIONAL INFORMATION I also tried running valgrind with the --smc-check=all option, as suggested here https://valgrind-users.narkive.com/r2fTd4tQ/how-can-ignore-lib-containing-unrecognized-instruction-illegal-opcode However, the output remains the same. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466998] Illegal instruction on ARMv7
https://bugs.kde.org/show_bug.cgi?id=466998 --- Comment #1 from David Di Lorenzo --- Created attachment 157085 --> https://bugs.kde.org/attachment.cgi?id=157085&action=edit Full valgrind log with the -v option I am attaching the valgrind log with the -v option, as suggested in the bug submission guidelines -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 431477] New: Cannot browse Application addons and Plasma Addons, loads indefinitely
https://bugs.kde.org/show_bug.cgi?id=431477 Bug ID: 431477 Summary: Cannot browse Application addons and Plasma Addons, loads indefinitely Product: Discover Version: 5.20.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: lorenzolo...@hotmail.it CC: aleix...@kde.org Target Milestone: --- Created attachment 134760 --> https://bugs.kde.org/attachment.cgi?id=134760&action=edit Discover stays on this screen forever, and it only happens with the Addons. SUMMARY Whenever I open Discover and click "Plasma Addons" or "Application addons", it loads indefinitely. Search doesn't work either. STEPS TO REPRODUCE 1. Open Discover 2. Click on "Application addons" or "Plasma addons" OBSERVED RESULT Searching indicator with spinner, category doesn't load. Navigating sub-categories leads to the same result. Browsing normal applications works. EXPECTED RESULT The spinner eventually goes away and a list of addons is presented. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.9.9-arch1-1 OS Type: 64-bit Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 ADDITIONAL INFORMATION Browsing Plasma widgets from the "Add object" Desktop context menu works just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430697] Plasma shell segfaults on startup: impossible to get a working desktop
https://bugs.kde.org/show_bug.cgi?id=430697 Lorenzo De Marco changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430697] New: Plasma shell segfaults on startup: impossible to get a working desktop
https://bugs.kde.org/show_bug.cgi?id=430697 Bug ID: 430697 Summary: Plasma shell segfaults on startup: impossible to get a working desktop Product: plasmashell Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: lorenzolo...@hotmail.it Target Milestone: 1.0 SUMMARY Briefly after logging in to my Plasma session today, the shell terminated abruptly. It then restarted and crashed again two times. Eventually, Plasma gave up and Dr. Konqi showed up, allowing me to file a bug. I'm reporting this manually because the tool wasn't able to gather as much information as needed by himself. STEPS TO REPRODUCE 1. Log in to Plasma (I use SDDM) 2. The desktop crashes in a matter of seconds 3. It keeps restarting and crashing a couple times. OBSERVED RESULT Plasma Shell crashes and restarts until you're left with nothing but a black screen (luckily I have Yakuake always open) EXPECTED RESULT Plasma Shell starts as usual. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.9.14-arch1-1 OS Type: 64-bit Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 7.7 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 ADDITIONAL INFORMATION Application: plasmashell (5.20.4) -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f37c99c0002 in () at /usr/lib/qt/qml/org/kde/plasma/calendar/libcalendarplugin.so #5 0x7f37e4586582 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #6 0x7f37e51f5752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #7 0x7f37e4559a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #8 0x7f37e455c573 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #9 0x7f37e45b30a4 in () at /usr/lib/libQt5Core.so.5 #10 0x7f37e297ba84 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #11 0x7f37e29cf9b1 in () at /usr/lib/libglib-2.0.so.0 #12 0x7f37e297a2b1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #13 0x7f37e45b26e1 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #14 0x7f37e45583fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #15 0x7f37e4560894 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #16 0x56366f138069 in () #17 0x7f37e3f24152 in __libc_start_main () at /usr/lib/libc.so.6 #18 0x56366f1382ae in () [Inferior 1 (process 752) detached] Here is the console output I get when issuing 'kstart5 plasmashell' manually, after it crashed a couple times and I'm left with the black screen. My comments start with ~~ on the same line Omitting both --window and --windowclass arguments is not recommended kf.plasma.quick: Applet preload policy set to 1 Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:445:13: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:431:13: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:411:17: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:398:17: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:385:17: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:372:17: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:160:13: QML TextArea: Binding loop detected for property "implicitWidth" trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:445:13: QML ToolButton: Binding loop detected for property "icon.height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/
[plasmashell] [Bug 430697] Plasma shell segfaults on startup: impossible to get a working desktop
https://bugs.kde.org/show_bug.cgi?id=430697 --- Comment #1 from Lorenzo De Marco --- relevant lines in dmesg: 34.091597] plasmashell[1457]: segfault at 7fb105c8f656 ip 7fb475511002 sp 7ffe646eb790 error 4 in libcalendarplugin.so[7fb47550b000+c000] [ 34.091604] Code: 48 0c 48 8d 0c ca 48 89 0c 24 48 39 cb 74 44 66 0f 1f 84 00 00 00 00 00 4c 8b 33 be 2a 00 00 00 48 89 ef 48 83 c3 08 49 8b 06 <4c> 8b 68 60 ff 15 3c da 00 00 4c 89 e2 48 89 ee 4c 89 f7 48 89 84 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430697] Plasma shell segfaults on startup: impossible to get a working desktop
https://bugs.kde.org/show_bug.cgi?id=430697 --- Comment #2 from Lorenzo De Marco --- tried again, different dmesg output: [ 778.443761] plasmashell[2534]: segfault at 0 ip sp 7ffed3027368 error 14 [ 778.443764] Code: Unable to access opcode bytes at RIP 0xffd6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430697] Plasma shell segfaults on startup: impossible to get a working desktop
https://bugs.kde.org/show_bug.cgi?id=430697 --- Comment #3 from Lorenzo De Marco --- Yesterday I added a clock widget to one of my panels, and configured it as follows: [Containments][3][Applets][117] immutability=1 plugin=org.kde.plasma.digitalclock [Containments][3][Applets][117][Configuration] PreloadWeight=42 [Containments][3][Applets][117][Configuration][Appearance] lastSelectedTimezone=America/New_York selectedTimeZones=America/New_York,Local showDate=false showLocalTimezone=true use24hFormat=0 wheelChangesTimezone=true [Containments][3][Applets][117][Configuration][ConfigDialog] DialogHeight=540 DialogWidth=720 Removing these lines from ~/.config/plasma-org.kde.plasma.desktop-appletsrc fixed this! Yay! It must be a problem with the clock widget then. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406673] New: Security: Sudo Restriction Bypass
https://bugs.kde.org/show_bug.cgi?id=406673 Bug ID: 406673 Summary: Security: Sudo Restriction Bypass Product: kate Version: Git Platform: Debian testing OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: hl1...@protonmail.com Target Milestone: --- SUMMARY When kate is ran, it checks if SUDO_USER is empty, and if it is not, kate exits with a message stating due to security concerns running as sudo is disabled. However, one can continue to run kate as sudo very easily. STEPS TO REPRODUCE 1. sudo bash -c "unset SUDO_USER && kate" OBSERVED RESULT It runs under sudo EXPECTED RESULT It would exit without running under sudo ADDITIONAL INFORMATION I am marking it as critical initially because I am unsure of the security implications of running under sudo in this way and whether the security concerns are mitigated via this special procedure or if the security concerns are still present. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 505172] New: Exporting Problem if the audio is discontinued
https://bugs.kde.org/show_bug.cgi?id=505172 Bug ID: 505172 Summary: Exporting Problem if the audio is discontinued Classification: Applications Product: kdenlive Version First 25.04.1 Reported In: Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Rendering & Export Assignee: j...@kdenlive.org Reporter: demarcolorenz...@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 Please remove this comment after reading and before submitting - thanks! *** SUMMARY Dear Devs, I've discovered an unseen bug. If you import 2 clips and you haven't a countinuos audio/video track (i.e. you have a 2 video/audio files splitted and nothing between those) you cannot export the video as is in the timeline, but you will export it until the first split. I've resolved adding a mute audio track between the split, but I think that you could solve it as default. Thanks in advance for listening, Best Regards Lorenzo DM STEPS TO REPRODUCE 1. add 2 clip to the timeline with 1 minute of nothing from the end of the 1st and the begin of the 2nd 2. try to export 3. you will have only the first video exported OBSERVED RESULT Only one video exported on 2 added to the timeline EXPECTED RESULT the 2 video exported with a pause in between SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371215] Plasma Crashes when trying to end application with kquiapp5
https://bugs.kde.org/show_bug.cgi?id=371215 Alejandro Lorenzo changed: What|Removed |Added CC||alejandro_a...@yahoo.es --- Comment #9 from Alejandro Lorenzo --- (In reply to David Edmundson from comment #8) > Fixed with d6853cc1dc4e63a779e126c7f23acc2f1ce180f1 which is in Plasma 5.8.3 Could it be possible you were refering to 5.8.2 ? I looked into the plasma git repository and i cannot find the slightest mention to 5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #61 from Alejandro Lorenzo --- I think each software should be responsible for its own bugs. If the bug is in Owncloud, just fix Owncloud and do not make miserable other projects because of your faults. Workarounds and such usually open the door to bugs ( Code paths that do not execute often or can only be tested to some versions of software), create harder to maintain software and generally, eat kittens, so personally I think it would be a bad idea -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 360969] Buttons for account creation don't work
https://bugs.kde.org/show_bug.cgi?id=360969 Lorenzo Chianura changed: What|Removed |Added CC||zul...@gmail.com --- Comment #1 from Lorenzo Chianura --- This bug seems not related to the kaccount-integration and kaccount-providers packages, but related to some wrong managed dependencies. To reproduce this bug in up-to-date archlinux machine (plasma 5.7.4, kde-applications 16.04), just install kaccount-providers and kaccount-integration packages (pacman will obviously handle dependecies): you'll end up with the "Online account" option in System Settings, but clicking on "Create" entry ends with nothing happened. As I said, in my case (archlinux) seems to be To "fix" it, just install telepathy-kde group, which involve: telepathy-kde-accounts-kcm telepathy-kde-approver telepathy-kde-auth-handler telepathy-kde-call-ui telepathy-kde-common-internals telepathy-kde-contact-list telepathy-kde-contact-runner telepathy-kde-desktop-applets telepathy-kde-filetransfer-handler telepathy-kde-integration-module telepathy-kde-send-file telepathy-kde-text-ui after that you'll be able to add online accounts. On which linux platform did you test this bug? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 Alejandro Lorenzo changed: What|Removed |Added CC||alejandro_a...@yahoo.es --- Comment #58 from Alejandro Lorenzo --- I am also experiencing this bug with Kmail and i think i have found the problem. Some CardDav clients, when creating an .ics file in a remote resource (E.g. owncloud in its caldav resource) creates a VCALENDAR file that does not contain the tag "VERSION:2.0" which declares the file conforming to VCALENDAR files version 2.0 I have manually accessed the caldav storage and added the VERSION:2.0 line to an owncloud created file and it immediately syncs into korganizer According to the RFC that defines iCal, VERSION is mandatory and owncloud is not including it, so korganizer is actually doing the right thing (i think) which is to ignore the file The relevant bug in owncloud is: https://github.com/owncloud/core/issues/23715 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 341067] Events from caldav resource do not appear in Korganizer
https://bugs.kde.org/show_bug.cgi?id=341067 Alejandro Lorenzo changed: What|Removed |Added CC||alejandro_a...@yahoo.es -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=357085 --- Comment #20 from Lorenzo Desole --- Any news on this? Does anybody know if QT 5.6 solves it? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358628] Konsol crashes when opening new tab
https://bugs.kde.org/show_bug.cgi?id=358628 Lorenzo Paulatto changed: What|Removed |Added CC||justfors...@email.it --- Comment #2 from Lorenzo Paulatto --- I don't know, I have since upgraded my distribution, now I am on Konsole Version 16.04.1 Using: KDE Frameworks 5.22.0 Qt 5.6.0 (built against 5.6.0) The xcb windowing system and I've never met the problem again... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 363781] New: System Settings crash while change buttons order in Window Decorations
https://bugs.kde.org/show_bug.cgi?id=363781 Bug ID: 363781 Summary: System Settings crash while change buttons order in Window Decorations Product: systemsettings Version: 5.6.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zul...@gmail.com Application: systemsettings5 (5.6.4) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.5.4-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160530) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was changing the titlebar buttons order in System Settings -> Application Style -> Window Decorations -> Buttons The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb90a0278c0 (LWP 6193))] Thread 7 (Thread 0x7fb8f68f6700 (LWP 6194)): #0 0x7fb905d179cd in poll () from /lib64/libc.so.6 #1 0x7fb902b183f2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb902b1a147 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb8f8e56969 in QXcbEventReader::run (this=0x166e230) at qxcbconnection.cpp:1325 #4 0x7fb90640cb29 in QThreadPrivate::start (arg=0x166e230) at thread/qthread_unix.cpp:340 #5 0x7fb90229f454 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb905d203fd in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fb8ee525700 (LWP 6195)): #0 0x7ffc82ab3979 in ?? () #1 0x7ffc82ab3c75 in clock_gettime () #2 0x7fb905d2d086 in clock_gettime () from /lib64/libc.so.6 #3 0x7fb9064b3df6 in qt_clock_gettime (ts=0x7fb8ee524a80, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fb906620919 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fb8e8002ed0) at kernel/qtimerinfo_unix.cpp:84 #7 0x7fb906620e45 in QTimerInfoList::timerWait (this=0x7fb8e8002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0x7fb9066221be in timerSourcePrepareHelper (timeout=0x7fb8ee524b34, src=) at kernel/qeventdispatcher_glib.cpp:126 #9 timerSourcePrepare (source=, timeout=0x7fb8ee524b34) at kernel/qeventdispatcher_glib.cpp:159 #10 0x7fb901d7fa1d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #11 0x7fb901d80323 in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7fb901d804fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7fb906622c5b in QEventDispatcherGlib::processEvents (this=0x7fb8e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #14 0x7fb9065ce79a in QEventLoop::exec (this=this@entry=0x7fb8ee524ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7fb906407f2c in QThread::exec (this=) at thread/qthread.cpp:503 #16 0x7fb906f1d7b5 in ?? () from /usr/lib64/libQt5DBus.so.5 #17 0x7fb90640cb29 in QThreadPrivate::start (arg=0x7fb90718cd00) at thread/qthread_unix.cpp:340 #18 0x7fb90229f454 in start_thread () from /lib64/libpthread.so.0 #19 0x7fb905d203fd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fb8dcf1f700 (LWP 6196)): #0 0x7fb9022a506f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb8e425d5c3 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7fb8e425d447 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7fb90229f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb905d203fd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fb8dc71e700 (LWP 6197)): #0 0x7fb9022a506f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb8e425d5c3 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7fb8e425d447 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7fb90229f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb905d203fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb8d892f700 (LWP 6199)): #0 0x7ffc82ab3979 in ?? () #1 0x7ffc82ab3c75 in clock_gettime () #2 0x7fb905d2d086 in clock_gettime () from /lib64/libc.so.6 #3 0x7fb9064b3df6 in qt_clock_gettime (ts=0x7fb8d892ea90, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fb906620919 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fb8d4002cd0) at kernel/qtimerinfo_unix.cpp:84 #7 0x7fb906620e45 in QTimerInfoList::timerWait (this=0x7fb8d4002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0x7fb9066221be in timerSourcePrepareHelper (timeout=0x7fb8d892eb44, src=) at kernel/qeventdispatcher_glib.
[kwin] [Bug 363781] System Settings crash while change buttons order in Window Decorations
https://bugs.kde.org/show_bug.cgi?id=363781 --- Comment #2 from Lorenzo Chianura --- I've experienced this bug ONLY in an upgraded opensuse leap -> tumbleweed. I've just installed opensuse tumbleweed on another virtual machine (no upgrade from leap, just a clean install) and I cannot reproduce the bug anymore. Anyway, I still have both virtual machines so, if do not think that this bug it's only a side-effect of the opensuse distro-upgrade process, I can investigate deeply and give more infos. To answer your question: to reproduce this bug (in the upgraded opensuse) simply change 5-10 times titlebar's button layout and SystemManager will crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357085] plugout VGA output then plugin plasmashell segfault
https://bugs.kde.org/show_bug.cgi?id=357085 Lorenzo Desole changed: What|Removed |Added CC||lorenzodes...@gmail.com --- Comment #4 from Lorenzo Desole --- Created attachment 96843 --> https://bugs.kde.org/attachment.cgi?id=96843&action=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357085] plugout VGA output then plugin plasmashell segfault
https://bugs.kde.org/show_bug.cgi?id=357085 --- Comment #5 from Lorenzo Desole --- I can confirm comment #3. Crash report attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=357085 --- Comment #10 from Lorenzo Desole --- (In reply to Martin Klapetek from comment #9) > > it would be very important to get a fix that hardens against this ASAP… > > If you're not running Qt 5.5.x, please upgrade ASAP. It will help. It's crashing here with QT 5.5.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=357085 --- Comment #12 from Lorenzo Desole --- (In reply to Martin Klapetek from comment #11) > Ok, good to know. Here's a crash report with QT 5.5 (debug symbols included) Thread 8 (Thread 0x7f36acea2700 (LWP 1703)): #0 0x7f36bc975c1d in poll () at /lib64/libc.so.6 #1 0x7f36c18bc422 in () at /usr/lib64/libxcb.so.1 #2 0x7f36c18be00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f36aeff33c9 in QXcbEventReader::run() (this=0x126b400) at qxcbconnection.cpp:1229 #4 0x7f36bd06d32f in QThreadPrivate::start(void*) (arg=0x126b400) at thread/qthread_unix.cpp:331 #5 0x7f36bc17f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f36bc97e04d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f36a61fd700 (LWP 1795)): #0 0x7f36b9098cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f36b9056387 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f36b9056d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f36b9056f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f36bd29fd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f36a8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f36bd246d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7f36a61fcdf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f36bd06861a in QThread::exec() (this=this@entry=0x1344410) at thread/qthread.cpp:503 #7 0x7f36c037adf8 in QQmlThreadPrivate::run() (this=0x1344410) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7f36bd06d32f in QThreadPrivate::start(void*) (arg=0x1344410) at thread/qthread_unix.cpp:331 #9 0x7f36bc17f0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f36bc97e04d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f36992e2700 (LWP 1816)): #0 0x7f36b9098d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f36b9056d73 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f36b9056f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f36bd29fd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f36940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f36bd246d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7f36992e1df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f36bd06861a in QThread::exec() (this=this@entry=0x1660400) at thread/qthread.cpp:503 #6 0x7f36c037adf8 in QQmlThreadPrivate::run() (this=0x1660400) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7f36bd06d32f in QThreadPrivate::start(void*) (arg=0x1660400) at thread/qthread_unix.cpp:331 #8 0x7f36bc17f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f36bc97e04d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f3693a14700 (LWP 1817)): #0 0x7f36b9054210 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f36b905644b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f36b9056d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f36b9056f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f36bd29fd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f368c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f36bd246d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7f3693a13df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f36bd06861a in QThread::exec() (this=this@entry=0x176e9d0) at thread/qthread.cpp:503 #7 0x7f36c037adf8 in QQmlThreadPrivate::run() (this=0x176e9d0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7f36bd06d32f in QThreadPrivate::start(void*) (arg=0x176e9d0) at thread/qthread_unix.cpp:331 #9 0x7f36bc17f0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f36bc97e04d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f3692096700 (LWP 1820)): #0 0x7f36bc18305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f36c2b4186b in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7f36c2e28ea0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f36c2b41899 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f36bc17f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f36bc97e04d in clone () at /lib64/libc.so.6 ---Type to continue, or q to quit--- Thread 3 (Thread 0x7f360a9d3700 (LWP 1830)): #0 0x7f36bc975c1d in poll () at /lib64/libc.so.6 #1 0x7f36b9056e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f36b9056f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f36bd29fd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f36040008c0, flags=...) at kernel/qeventdispatcher_
[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=357085 --- Comment #18 from Lorenzo Desole --- I am assuming this won't be fixed prior to QT 5.6. -- You are receiving this mail because: You are watching all bug changes.
