[kate] [Bug 444473] New: kwrite inserts a spurious space when a portuguese composite character with accent ' is typed in
https://bugs.kde.org/show_bug.cgi?id=73 Bug ID: 73 Summary: kwrite inserts a spurious space when a portuguese composite character with accent ' is typed in Product: kate Version: 21.08.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: r...@fc.ul.pt Target Milestone: --- kwrite inserts a spurious space when a portuguese composite character with accent ' is typed in STEPS TO REPRODUCE Plug a portuguese keyboard in Set the desktop language to portuguese Open kwrite type the word Amália OBSERVED RESULT Am ália EXPECTED RESULT Amália SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian testing KDE Plasma Version: 5.21.5 KDE Frameworks Version: Qt Version: 5.15.2+dfsg-12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444176] Key strokes are propagated to window contents while resizing/moving window by keyboard only
https://bugs.kde.org/show_bug.cgi?id=444176 --- Comment #3 from Vlad Zahorodnii --- see also https://invent.kde.org/plasma/kwin/-/merge_requests/90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444425] chrome exhibits artifacts on window redraw
https://bugs.kde.org/show_bug.cgi?id=25 Vlad Zahorodnii changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Vlad Zahorodnii --- Hmm, it might be a chrome issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #21 from Andrey --- p-d, are you completely sure you have the patch? Anyone else has the problem? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #22 from p d --- I have KDE 5.23.2, that is supposed to include the patch, is it not? Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-300.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #23 from p d --- With "Hide Titles" kwin script, the issue still happens some of the time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443463] radio buttons missing labels
https://bugs.kde.org/show_bug.cgi?id=443463 arne anka changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444474] New: auto-hide panel hides while ordering taskbar entries -- entry ends up on desktop
https://bugs.kde.org/show_bug.cgi?id=74 Bug ID: 74 Summary: auto-hide panel hides while ordering taskbar entries -- entry ends up on desktop Product: plasmashell Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde-b...@ginguppin.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I've set my panel to auto-hide. While ordering/moving a taskbar entry the panel suddenly hides and thus the selected entry ends up as shortcut on the desktop. If it helps: this new with 5.23, didn't happen before. STEPS TO REPRODUCE 1. set Panel to "auto-hide" and Task Manager to "order manually" 2. left click, hold and move a taskbar entry 3. panel hides and you're left with a selection hovering over the desktop that cannot be cancelled 4. release selection and the selection creates a shortcut on the desktop EXPECTED RESULT 1) panel should not hide until selection is released 2) selection should at least be cancel-able by hitting ESC SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-3-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4700MQ CPU @ 2.40GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444474] auto-hide panel hides while ordering taskbar entries -- entry ends up on desktop
https://bugs.kde.org/show_bug.cgi?id=74 arne anka changed: What|Removed |Added Platform|Other |Debian unstable -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 444475] New: can't find music
https://bugs.kde.org/show_bug.cgi?id=75 Bug ID: 75 Summary: can't find music Product: frameworks-baloo Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: aron...@gmail.com Target Milestone: --- SUMMARY Elisa can't find my music, I tried the filesystem and os search STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[kwin] [Bug 442846] Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time
https://bugs.kde.org/show_bug.cgi?id=442846 --- Comment #5 from Vlad Zahorodnii --- (In reply to p d from comment #4) > I haven't had this issue in a while. > > Sometimes I launch a separate wayland session via (Ctrl + Alt + F > and log in as different user, startplasma-wayland), then switch back. I > wonder if that has something to do with the issue. Maybe.. It will be helpful to see kwin_wayland's backtrace when session is frozen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444200] kwin_wayland segfaults when switching activities
https://bugs.kde.org/show_bug.cgi?id=444200 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Vlad Zahorodnii --- *** This bug has been marked as a duplicate of bug 441547 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441547] Crash in KWin::clamp_row() when switching activities
https://bugs.kde.org/show_bug.cgi?id=441547 Vlad Zahorodnii changed: What|Removed |Added CC||sjurberengal+...@gmail.com --- Comment #12 from Vlad Zahorodnii --- *** Bug 444200 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444476] New: Black screen, no panel, only window content and decoration
https://bugs.kde.org/show_bug.cgi?id=76 Bug ID: 76 Summary: Black screen, no panel, only window content and decoration Product: plasmashell Version: 5.23.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: julien@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On Wayland, after update from 5.23.1 to 5.23.2, instead of classical desktop session, I have black screen, no visible panel (but working), only window content and decoration. STEPS TO REPRODUCE 1. update from 5.23.1 to 5.23.2 2. launch a Wayland session OBSERVED RESULT Many invisible or black elements. EXPECTED RESULT Visible element like panel, wallpaper, etc. Operating System: Gentoo Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-gentoo-x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 31.3 Gio of RAM Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444477] New: Resize application launcher
https://bugs.kde.org/show_bug.cgi?id=77 Bug ID: 77 Summary: Resize application launcher Product: plasmashell Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: m...@iyanmv.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I don't know how to resize the application launcher to a custom size, or even to go back to the default size. I learned this the hard way. By mistake I pressed the shortcut to maximize windows while the launcher was open, and it got resized to use all the screen. I can use other shortcuts like half screen or a third of the screen (I'm using Mudeer for these extra shortcuts), but none of them are the default size. I think it would be useful to be be able to resize the launcher with the mouse. If I remember correctly, with the previous default launcher it was possible to do that by pressing some key (Alt?) while dragging the menu with the mouse. STEPS TO REPRODUCE 1. Open Kickoff 2. Press the maximize shortcut (Meta + PgUp by default) OBSERVED RESULT Application launcher is maximized and it doesn't go back to its "normal" size even after closing it EXPECTED RESULT I don't know if the menu should behave as a normal window. But if this is the intended behavior, then it should be also as easy to resize the launcher as any other window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444476] Black screen, no panel, only window content and decoration
https://bugs.kde.org/show_bug.cgi?id=76 --- Comment #1 from Julien Delquié --- Also, if I relaunch plasmashell from console, I have many many many messages like this: qt.qpa.wayland: Could not create EGL surface (EGL error 0x321c) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444477] Resize application launcher
https://bugs.kde.org/show_bug.cgi?id=77 --- Comment #1 from Iyán Méndez Veiga --- Okay, just after I wrote down the issue, I figured out the shortcut to resize windows: Meta + Right click. With this combo it is possible to resize the launcher. However, I still think that it should be easier (possible) to do without knowing this shortcut. Also, I think the launcher should not behave exactly as a window. For example, it is possible to move it around with Meta + Left click, and I find it quite weird. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444476] Black screen, no panel, only window content and decoration
https://bugs.kde.org/show_bug.cgi?id=76 --- Comment #2 from Julien Delquié --- Created attachment 142933 --> https://bugs.kde.org/attachment.cgi?id=142933&action=edit An example of the issue Desktop with no Wallpaper, no visible Panel (but exists), 2 consoles with transparency+blur, and calendar opened from clock in the right corner but nothing appear just the transparency+blur effect on it. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 444374] Exclusive UI language change is not applied.
https://bugs.kde.org/show_bug.cgi?id=444374 --- Comment #5 from t-ask --- Created attachment 142934 --> https://bugs.kde.org/attachment.cgi?id=142934&action=edit The selected language. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 444374] Exclusive UI language change is not applied.
https://bugs.kde.org/show_bug.cgi?id=444374 --- Comment #6 from t-ask --- To complete the file list. This is `` on my system. ``` # ls -al /usr/share/locale/de/LC_MESSAGES/kmymoney.mo -rw-r--r-- 1 root root 380226 Sep 10 21:50 /usr/share/locale/de/LC_MESSAGES/kmymoney.mo ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #32 from 80p3fy7...@cloud-mail.top --- (In reply to Patrick Silva from comment #26) > This bug also persists on Wayland after update to Plasma 5.23.2 on Arch > Linux. (In reply to Samuel Reddy from comment #30) > Plasma 5.23.2 on Arch Linux does not fix the problem for me. Same here on Arch Linux and Gentoo. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration
https://bugs.kde.org/show_bug.cgi?id=179678 --- Comment #104 from lega99 --- (In reply to Bo Weaver from comment #103) > (In reply to petrk from comment #102) > > That revert was stuck for a year. I don't see it going anywhere with > > dissatisfied users being called "vocal minority". > > > > I'm not speaking for myself, as I don't mind doing stuff via terminal. > > However, KDE lately was aiming more towards new users. Why would they be > > forced to learn their way around console, or to keep different file manager > > just to edit some files in restricted areas? > > I wrote about this back in 2019 and they aren't going to listen. The > developers here seem to know better than you and me and are protecting us > from ourselves. My best fix found is XFCE. It is a great DE and the > developers don't mess with root access. BTW I was a KDE user since the 90's > and finally gave up. Never finished the story, happiness there is a Krusader, so it is possible to start this file manager in root mode with sudo. Sometimes a great program Dolphin is nothing now. Discover the same hour works or doesn't work or need an eternity to load update. Every update of the plasme happens, I am interfering, I have the impression that something changes and there is no purpose. I advertised on the forum Thermal Monitor KJI works in all other Linuxima and only the update plasms from 5.21 to 5.22 it was raiding, Instal Xysguard does not help me. Developers are more and more like Windows developers, they know what we need and think of us and protect us from ourselves. -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 440824] Get WordPress website development services from experts
https://bugs.kde.org/show_bug.cgi?id=440824 Erik Jensen changed: What|Removed |Added CC||jensenerikonecl...@gmail.co ||m URL||https://www.oneclickactivat ||e.com/discover-com-activate ||/ --- Comment #2 from Erik Jensen --- Visit discover.com/activate to find the proper activation page that will let you activate your services in no time. With the discover.com/activate link, you may begin using your card services with the utmost convenience. If you are interested in joining Discover's services, please refer to us. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444476] Black screen, no panel, only window content and decoration
https://bugs.kde.org/show_bug.cgi?id=76 --- Comment #3 from Julien Delquié --- Trying to force gui-libs/egl-wayland from 1.1.7-r1 to 1.1.9 seems to make things better, I have a wallpaper, no messages about EGL error, but everything is really slow, the panel appears only if I put my mouse on the bottom edge, but panel does not work at all and makes plasmashell crash many times. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444478] New: Visit tcm.com/activate to stream unlimited content on Fire TV, Apple TV, and Roku
https://bugs.kde.org/show_bug.cgi?id=78 Bug ID: 78 Summary: Visit tcm.com/activate to stream unlimited content on Fire TV, Apple TV, and Roku Product: korganizer Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jensenerikonecl...@gmail.com Target Milestone: --- TCM programming is available to stream on popular streaming platforms such as Fire TV, Apple TV, and Roku. All you have to do is, explore our page and learn how to acquire a code to activate Turner Classic Movies on your available device. Using tcm.com/activate enjoy your favorite episodes and movies. Visit Us: https://www.oneclickactivate.com/tcm-com-activate/ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444478] Visit tcm.com/activate to stream unlimited content on Fire TV, Apple TV, and Roku
https://bugs.kde.org/show_bug.cgi?id=78 Erik Jensen changed: What|Removed |Added URL||https://www.oneclickactivat ||e.com/tcm-com-activate/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #24 from Méven Car --- (In reply to Andrey from comment #21) > p-d, are you completely sure you have the patch? > Anyone else has the problem? It is part of Plasma 5.23.2 https://kde.org/announcements/changelogs/plasma/5/5.23.1-5.23.2/ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444478] Visit tcm.com/activate to stream unlimited content on Fire TV, Apple TV, and Roku
https://bugs.kde.org/show_bug.cgi?id=78 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Laurent Montel --- SPAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #25 from Méven Car --- (In reply to p d from comment #23) > With "Hide Titles" kwin script That's this one I guess: https://store.kde.org/p/1354715/ https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > the issue still happens some of the time. Do you know if that is when you click the maximize button or drap up a window, or double click on a window title bar ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #26 from Méven Car --- (In reply to Méven Car from comment #25) > (In reply to p d from comment #23) > > With "Hide Titles" kwin script > > That's this one I guess: > https://store.kde.org/p/1354715/ > https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > > > the issue still happens some of the time. > > Do you know if that is when you click the maximize button or drap up a > window, or double click on a window title bar ? That's a different bug this one concerned specifically the "BorderlessMaximizedWindows" case. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] New: digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Bug ID: 79 Summary: digikam doesn't start, instead "cannot process schema initialization" Product: digikam Version: 7.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Database-Schema Assignee: digikam-bugs-n...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- When starting digikam, it stops and opens a window saying (in German) that upgrading the database schema hadn't been successful and that I should start it from the konsole and send the error message which is shown there. When I start it from the CLI, I get the following message (nothing more, only this one line): "digikam.coredb: Core database: cannot process schema initialization" STEPS TO REPRODUCE 1. start digikam 2. 3. OBSERVED RESULT See summary above EXPECTED RESULT digikam working SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Manjaro shows me the version number 7.3.0-5 for digikam. I am totally lost here. Digikam doesn't give any useful information except the above, and I have no clue where to look for the database (I'm sorry, but digikam worked for me most of the time during the last 20 or so years, and I don't remember what settings there are, so questions like "what database" I simply can't answer unless I am told where to look for this info). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Which kind of database type did you use : sqlite, mysql local, mysql remote serveur ? If you use Mysql, which version exactly ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 426012] drag-n-drop to konsole seems to have stopped working
https://bugs.kde.org/show_bug.cgi?id=426012 --- Comment #3 from davidblunkett --- Still broken a year+ later konsole 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 444480] New: amarokcollectionscanner hangs in /dev
https://bugs.kde.org/show_bug.cgi?id=80 Bug ID: 80 Summary: amarokcollectionscanner hangs in /dev Product: amarok Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: gran...@tempmail.de Target Milestone: kf5 my collectionscanner hangs at weird folders like /dev (which are part of lxc filesystem within the collection folder) what can i do - except micromanage all folders? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 365890] When using Shift+Home/End as shortcut using the neo layout, the Shift+U / Shift+O keys do not enter large U/O anymore.
https://bugs.kde.org/show_bug.cgi?id=365890 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=401806 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 401806] presence of german/neo2 keyboard layout causes kglobalaccel5 to consume several local shortcuts while german/qwertz layout is active
https://bugs.kde.org/show_bug.cgi?id=401806 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=365890 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 401806] presence of german/neo2 keyboard layout causes kglobalaccel5 to consume several local shortcuts while german/qwertz layout is active
https://bugs.kde.org/show_bug.cgi?id=401806 Till Schäfer changed: What|Removed |Added Version|5.52.0 |5.87.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 401806] presence of german/neo2 keyboard layout causes kglobalaccel5 to consume several local shortcuts while german/qwertz layout is active
https://bugs.kde.org/show_bug.cgi?id=401806 --- Comment #4 from Till Schäfer --- The patch fix-x11-keygrabs from Bug 365890 did not resolve my issue. alt+x still does not work in yakuake as sson I add the neo layout to the list of configured keyboard layouts. Thus, I do not say these bugs are unrelated, but at least the patch is incomplete. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442830] Places tab text is not centered
https://bugs.kde.org/show_bug.cgi?id=442830 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/368 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Before you start digiKam in the terminal, please activate the debug output with the command: export QT_LOGGING_RULES="digikam*=true" Post all messages. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443086] Add software rendering toggle for OpenGL backends
https://bugs.kde.org/show_bug.cgi?id=443086 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #1 from vindicator --- OH! This should be good (not). Much like how I refuse to install Wayland given amount and kind of bugs I've encountered, so too do I hate that xrender was removed. My most notable issue with OpenGl was when viewing videos in the browser or Kodi, at some random point in time (doesn't even have to be in that viewing session), rendering would get all borked. The audio would still play, but the video would freeze and may get some partial renders when moving my mouse or switching/moving windows. The only "fix" would be to switch rendering version (going back and forth between 2.0/3.1. Yeah, I'm definitely going to hate this and can't wait for Alder Lake to come out so I can upgrade to that (from Haswell) and this won't be an issue any longer... "hopefully". I'm quite certain I posted about this before, though don't see it in my bug post list. Maybe it didn't come with my email address change or something. Or maybe I hopped on someone else's post regarding my rendering issue. And yes, I've toyed with the X driver settings. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443460] Gwenview crashed on opening new PNG file from within Dolphin file browser
https://bugs.kde.org/show_bug.cgi?id=443460 --- Comment #1 from el...@theliddingtons.nz --- Created attachment 142935 --> https://bugs.kde.org/attachment.cgi?id=142935&action=edit New crash information added by DrKonqi gwenview (19.12.3) using Qt 5.12.8 - What I was doing when the application crashed: As per suggested duplicate report, I was attempting to open a JPG image. Crash occurs multiple times consistently again and again each time I tried to re-open same file. Image info - "Image Orientation: 90Deg. Rotated CCW" 3.4MB in size Opening image in GIMP gives error message "This image containes Exif orientation metadata - Would you like to rotate the image?" Letting GIMP rotate image as per metadata, and then Saving Image as *.jpg under GIMP, Gwenview is able to OPEN the image successfully. So it appears as if having Exif rotation data causes the error. NOTE: On re-opening saved (and rotated image), it did take Gwenview a few seconds to open file, but it did. -- Backtrace (Reduced): #6 0x7f3a74ee6fe7 in QUrl::operator== (this=this@entry=0x7ffcf4a681e0, url=...) at io/qurl.cpp:3639 #7 0x7f3a769ce19e in Gwenview::ContextManager::setCurrentDirUrl (this=this@entry=0x55ed1ffd6b10, _url=...) at ./lib/contextmanager.cpp:186 #8 0x7f3a769ce29a in Gwenview::ContextManageroperator() (__closure=, urlReady=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qurl.h:69 #12 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:432 #13 0x7f3a74fb8458 in QtPrivate::QSlotObjectBase::call (a=0x7ffcf4a68330, r=0x7f3a76add190 , this=0x55ed1ffba3b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443460] Gwenview crashed on opening new PNG file from within Dolphin file browser
https://bugs.kde.org/show_bug.cgi?id=443460 el...@theliddingtons.nz changed: What|Removed |Added CC||el...@theliddingtons.nz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443086] Add software rendering toggle for OpenGL backends
https://bugs.kde.org/show_bug.cgi?id=443086 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Note that LIBGL_ALWAYS_SOFTWARE=1 will only affect mesa, so that needs querying or explaining in the UI. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443555] Discover takes up to ~5 minutes to fetch updates on Arch Linux due to flatpak backend
https://bugs.kde.org/show_bug.cgi?id=443555 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #5 from Laosom --- I can also reproduce the problem in Neon , no snaps or flatpaks installed. The issue first appeared to me in Neon 5.23.1 , when tried to update to 5.23.2 As a workaround I removed snap and flatpak backends, working fine. I wonder why these sources simply cannot be disabled by untick , is it so much programing work ? Reinstalled backends, same issue. Disabled only flathub.org , fetching updates is working properly and not stucked. It's surely flatpak related. https://www.reddit.com/r/kde/comments/qdtdm3/anyone_else_having_problems_with_discover_since/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444389] Wayland: panel/taskbar crash after display sleep
https://bugs.kde.org/show_bug.cgi?id=444389 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from David Edmundson --- It's fine, you don't need any more symbols. >xdg_surface@51: error -1: invalid window geometry size (0x0) The Wayland connection experienced a fatal error: Protocol error Error is all here. GDB won't tell you anything new, the issue is caused long before we receive the error and assert. I have made a patch for this in 5.23.2 that I hope addresses this problem. Please reopen if not. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444251] digiKam crashes when importing photos from HD
https://bugs.kde.org/show_bug.cgi?id=444251 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.4.0 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 444471] "keep open" tooltip obstruction
https://bugs.kde.org/show_bug.cgi?id=71 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 428191 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428191] PC3 Tooltips in small/short windows get cut off, mis-rendered, or overlap their parent control because they aren't drawn as a separate window
https://bugs.kde.org/show_bug.cgi?id=428191 Patrick Silva changed: What|Removed |Added CC||afedotov...@outlook.com --- Comment #7 from Patrick Silva --- *** Bug 71 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444325] GIMP does not appear in Task Manager on Wayland
https://bugs.kde.org/show_bug.cgi?id=444325 David Edmundson changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||k...@davidedmundson.co.uk Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444477] Resize application launcher
https://bugs.kde.org/show_bug.cgi?id=77 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 411462 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 411462] Plasma dialogs (applet popups, OSDs, notifications) should not be movable, maximizable, or minimizable, or tilable
https://bugs.kde.org/show_bug.cgi?id=411462 Patrick Silva changed: What|Removed |Added CC||m...@iyanmv.com --- Comment #8 from Patrick Silva --- *** Bug 77 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444325] GIMP does not appear in Task Manager on Wayland
https://bugs.kde.org/show_bug.cgi?id=444325 --- Comment #4 from David Edmundson --- I ran plasmashell with wayland_debug and we're not getting a second window announced Plasma window management. This implies it is a kwin bug somewhere -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443330] Undoing/redoing merged strokes from Cumulative Undo tends to result in safe asserts and leftover artifacts
https://bugs.kde.org/show_bug.cgi?id=443330 sh_zam changed: What|Removed |Added Status|REPORTED|ASSIGNED CC||sh...@sdf.org Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |sh...@sdf.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444462] Kickoff is ignoring submenus
https://bugs.kde.org/show_bug.cgi?id=62 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- bug 443503 seems related. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444442] Conversion from Sony ARW to DNG loses pixels on the right side of the image
https://bugs.kde.org/show_bug.cgi?id=42 --- Comment #4 from Maik Qualmann --- This thread is quite interesting even if it's from 2015: https://www.libraw.org/node/2117 Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396016] KMYMoney GPG option is grayed out even though GPG installed
https://bugs.kde.org/show_bug.cgi?id=396016 --- Comment #24 from Ralf Habacker --- Created attachment 142936 --> https://bugs.kde.org/attachment.cgi?id=142936&action=edit Screenshot showing KDE related processes When you follow the the recipe mentioned at comment #14, do you see the processes mentioned in the screenshot ? If not which processes are missing ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444481] New: gdb_server test failures on s390x
https://bugs.kde.org/show_bug.cgi?id=81 Bug ID: 81 Summary: gdb_server test failures on s390x Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- With valgrind 3.18.1 on Fedora 34 s390x with: glibc-2.33-20.fc34.s390x gdb-10.2-3.fc34.s390x gcc-11.2.1-1.fc34.s390x binutils-2.35.2-6.fc34.s390x I am seeing the following failures: gdbserver_tests/hgtls(stdoutB) gdbserver_tests/nlsigvgdb(stderr) gdbserver_tests/nlsigvgdb(stderrB) gdbserver_tests/nlvgdbsigqueue (stderr) gdbserver_tests/nlvgdbsigqueue (stdoutB) Which I don't observe on RHEL8 s390x with: glibc-2.28-167.el8.s390x gdb-8.2-16.el8.s390x gcc-8.5.0-3.el8.s390x binutils-2.30-108.el8.s390x The f34 log files: --- hgtls.stdoutB.exp 2021-10-26 12:44:44.997207954 -0400 +++ hgtls.stdoutB.out 2021-10-26 12:49:28.717217935 -0400 @@ -9,37 +9,5 @@ Breakpoint 1, tls_ptr (p=0x) at tls.c:55 55 int here = 0; test local tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test local tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test global tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test global tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test static_extern tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test static_extern tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test so_extern tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test so_extern tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test so_local tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test so_local tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test so_global tls_ip 0x ip 0x equal 1 -Breakpoint 1, tls_ptr (p=0x) at tls.c:55 -55 int here = 0; -test so_global tls_ip 0x ip 0x equal 1 -Program exited normally. +Program terminated with signal 0, Signal 0. +The program no longer exists. --- nlsigvgdb.stderr.exp2021-10-26 12:44:44.997207954 -0400 +++ nlsigvgdb.stderr.out2021-10-26 12:50:13.507232568 -0400 @@ -3,4 +3,3 @@ (action at startup) vgdb me ... -Reset valgrind output to log (orderly_finish) gdbserver_tests/nlsigvgdb.stderr.diff (END) --- nlsigvgdb.stderrB.exp 2021-10-26 12:44:44.997207954 -0400 +++ nlsigvgdb.stderrB.out 2021-10-26 12:50:13.767232568 -0400 @@ -1,5 +1,6 @@ vgdb-error value changed from 0 to 99 gdbserver: continuing in 5000 ms ... -gdbserver: continuing after wait ... -monitor command request to kill this process +syscall failed: No such process +invoke_gdbserver_in_valgrind: check for pid existence failed Remote connection closed +"monitor" command not supported by this target. --- nlvgdbsigqueue.stderr.exp 2021-10-26 12:44:44.997207954 -0400 +++ nlvgdbsigqueue.stderr.out 2021-10-26 12:50:16.967232568 -0400 @@ -8,4 +8,64 @@ London ready to sleep and/or burn Petaouchnok ready to sleep and/or burn main ready to sleep and/or burn -Gdb request to kill this process +VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting +si_code=1; Faulting address: 0x3FFBAF7E000; sp: 0x1002e401e8 + +valgrind: the 'impossible' happened: + Killed by fatal signal + +host stacktrace: + at 0x3FFBAF7E480: ??? + by 0x800027FE7: vgPlain_poll (m_libcfile.c:765) + by 0x: ??? + +sched status: + running_tid=0 + +Thread 1: status = VgTs_WaitSys syscall 301 (lwpid 47398) + at 0x495A8E8: select (in /...libc...) + by 0x1001163: sleeper_or_burner (sleepers.c:85) + by 0x1001849: main (sleepers.c:193) +client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFEFFF890 +valgrind stack range: [0x1002D41000 0x1002E40FFF] top usage: 12384 of 1048576 + +Thread 2: status = VgTs_WaitSys syscall 301 (lwpid 47428) + at 0x495A8E8: select (in /...libc...) + by 0x1001163: sleeper_or_burner (sleepers.c:85) + by 0x4847175: start_thread (in /usr/lib64/libpthread-2.33.so) + by 0x49629D5: ??? (in /...libc...) + by 0x: ??? +client stack ra
[okular] [Bug 416651] The ability to fix tab width or prefixed by program by default
https://bugs.kde.org/show_bug.cgi?id=416651 Tom changed: What|Removed |Added CC||t-k...@hotmail.de --- Comment #1 from Tom --- Created attachment 142937 --> https://bugs.kde.org/attachment.cgi?id=142937&action=edit Varying tab sizes in okular -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416651] The ability to fix tab width or prefixed by program by default
https://bugs.kde.org/show_bug.cgi?id=416651 --- Comment #2 from Tom --- I want to second this. Okular is the only software I know in which the tab sizes vary significantly, which doesn't make a lot of sense. If there is a few tabs open, it is really hard to read which is which since, some tabs are extremely small (see screenshot). Evenly distributed space between all tabs should be the obvious choice here. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416651] The ability to fix tab width or prefixed by program by default
https://bugs.kde.org/show_bug.cgi?id=416651 Tom changed: What|Removed |Added Version|19.12.1 |21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #10 from Attila --- As far as I can see, this bug effects only "subfolders" of the "local folder". I have set up some filter. After new e-mails are sorted to the "subfolders", many of them appear twice. Click on the first one shows an empty e-mail (this is wrong) and the second shows the new e-mail correct. When I click on the first e-mail again I get the message in the status bar: Unable to fetch item from backend with dirty payload It doesn't happen on my "inbox". So I think it is affected to the "subfolders" and has something to do with filters. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 443503] KMenuedit no longer utilizes application directory structure
https://bugs.kde.org/show_bug.cgi?id=443503 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #4 from Kai Uwe Broulik --- There's no issue with the menu editor. Kickoff has "flat: true" set on the model. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442304] Firefox context menu is small and displays with scrollbar on KDE Wayland
https://bugs.kde.org/show_bug.cgi?id=442304 Lyubomir changed: What|Removed |Added URL||https://bugzilla.mozilla.or ||g/show_bug.cgi?id=1729944 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444481] gdb_server test failures on s390x
https://bugs.kde.org/show_bug.cgi?id=81 Mark Wielaard changed: What|Removed |Added Depends on||441474 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=441474 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=441474 [Bug 441474] vgdb might eat all memory while waiting for sigstop -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441474] vgdb might eat all memory while waiting for sigstop
https://bugs.kde.org/show_bug.cgi?id=441474 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Blocks||81 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=81 Resolution|--- |FIXED --- Comment #4 from Mark Wielaard --- (In reply to Mark Wielaard from comment #3) > I pushed the workaround: > > commit 970820852e542506dd7a4c722fecd73e34363fde > Author: Mark Wielaard > Date: Tue Oct 12 23:25:32 2021 +0200 > > vgdb: only queue up to 64 pending signals when waiting for SIGSTOP > > We should not queue infinite pending signals so we won't run out of > memory when the SIGSTOP never arrives. > > But keep this bug open because the root cause isn't known yet. Here is a bug with more logs about failing gdb_server tests on s390x: https://bugs.kde.org/show_bug.cgi?id=81 Lets use that one to track s390x gdb_server issues and close this one since the specific workaround for the "eat all memory" issue has been pushed. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=81 [Bug 81] gdb_server test failures on s390x -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444481] gdb_server test failures on s390x
https://bugs.kde.org/show_bug.cgi?id=81 Bug 81 depends on bug 441474, which changed state. Bug 441474 Summary: vgdb might eat all memory while waiting for sigstop https://bugs.kde.org/show_bug.cgi?id=441474 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 444482] New: Wayland: Spectacle screenshot of window under cursor works via GUI but not in background mode
https://bugs.kde.org/show_bug.cgi?id=82 Bug ID: 82 Summary: Wayland: Spectacle screenshot of window under cursor works via GUI but not in background mode Product: Spectacle Version: 21.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: chimak...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY With Spectacle 21.08.2 in Wayland, I can capture the window under cursor via the GUI but cannot do so in background mode. spectacle -bn -u -o $HOME/Pictures/"$(date +%Y%m%d-%H%M%S)".jpg does nothing (bound to Meta+Ctrl+U). spectacle -bn -r -o $HOME/Pictures/"$(date +%Y%m%d-%H%M%S)".jpg works (bound to Meta+Ctrl+R). spectacle -bn -f -o $HOME/Pictures/"$(date +%Y%m%d-%H%M%S)".jpg works (bound to Meta+Ctrl+F). spectacle -bn -d 1 -o $HOME/Pictures/"$(date +%Y%m%d-%H%M%S)".jpg works (bound to Meta+Ctrl+D). EXPECTED RESULT Using "-u" should work in background mode. Or maybe "spectacle --help" should be modified to indicate which options won't work in Wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444483] New: KWin crashes consistently on startup after updating Debian Testing
https://bugs.kde.org/show_bug.cgi?id=83 Bug ID: 83 Summary: KWin crashes consistently on startup after updating Debian Testing Product: kwin Version: 5.21.5 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jim+...@nekojimi.moe Target Milestone: --- Application: kwin_x11 (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.14.0-2-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.23.0 [KCrashBackend] -- Information about the crash: KWin can no longer start after upgrading my Debian system about a week ago; I've installed debug packages to get a good stacktrace, and from looking at that and my apt history I suspect the issue was caused by upgrading libkdecorations2-5v5:amd64 from 4:5.21.5-2 to 4:5.23.0-2. (I can also send the rest of the apt history from the last day it was working if it will help) I can still run other window managers, and I am currently using Awesome as a stop-gap to get my system working again. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7fe80a401510 in KDecoration2::DecorationSettings::font (this=this@entry=0x55623c3722e0) at /usr/include/c++/11/bits/unique_ptr.h:173 #5 0x7fe80a401737 in operator() (__closure=) at ./src/decorationsettings.cpp:19 #6 KDecoration2::DecorationSettings::DecorationSettings (this=0x55623c3722e0, bridge=0x55623c339430, parent=) at ./src/decorationsettings.cpp:34 #7 0x7fe80c4a2add in KWin::Decoration::DecorationBridge::init() () from /lib/x86_64-linux-gnu/libkwin.so.5 #8 0x7fe80c5a75a7 in KWin::Workspace::Workspace() () from /lib/x86_64-linux-gnu/libkwin.so.5 #9 0x7fe80c500990 in KWin::Application::createWorkspace() () from /lib/x86_64-linux-gnu/libkwin.so.5 #10 0x55623a2a841e in KWin::ApplicationX11::continueStartupWithScreens (this=0x7ffec16b3740) at ./main_x11.cpp:272 #11 0x7fe80b0a5977 in QtPrivate::QSlotObjectBase::call (a=0x7ffec16b2fd0, r=0x7ffec16b3740, this=0x55623c3439b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55623c278500, signal_index=3, argv=0x7ffec16b2fd0) at kernel/qobject.cpp:3886 #13 0x7fe7f8206d73 in KWin::X11StandalonePlatform::doUpdateOutputs (this=0x7ffec16b30a8) at ./plugins/platforms/x11/standalone/x11_platform.cpp:603 #14 0x7fe7f8200779 in KWin::X11StandalonePlatform::initOutputs (this=0x55623c278500) at ./plugins/platforms/x11/standalone/x11_platform.cpp:473 #15 0x7fe7f82007d1 in KWin::X11StandalonePlatform::init (this=0x55623c278500) at ./plugins/platforms/x11/standalone/x11_platform.cpp:143 #16 0x55623a2a7ddd in operator() (__closure=0x55623c1b7580) at ./main_x11.cpp:259 #17 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::ApplicationX11::performStartup():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #18 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #19 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55623c1b7570, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #20 0x7fe80b0a5977 in QtPrivate::QSlotObjectBase::call (a=0x7ffec16b32f0, r=0x55623c1b5aa0, this=0x55623c1b7570) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x55623c1b5aa0, signal_index=4, argv=0x7ffec16b32f0, argv@entry=0x0) at kernel/qobject.cpp:3886 #22 0x7fe80b09ecc0 in QMetaObject::activate (sender=, m=m@entry=0x7fe80c32e680 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #23 0x7fe80c2f73d3 in KSelectionOwner::claimedOwnership (this=) at ./obj-x86_64-linux-gnu/src/KF5WindowSystem_autogen/HBARIMPYTU/moc_kselectionowner.cpp:160 #24 0x7fe80c30a223 in KSelectionOwner::Private::claimSucceeded (this=0x55623c1a9330) at ./src/platforms/xcb/kselectionowner.cpp:187 #25 0x7fe80b09b6af in QObject::event (this=0x55623c1b5aa0, e=0x7ffec16b34c0) at kernel/qobject.cpp:1336 #26 0x7fe80bc1374f in QApplicationPrivate::notify_helper (this=, receiver=0x55623c1b5aa0, e=0x7ffec16b34c0) at kernel/qapplication.cpp:3632 #27 0x7fe80b06ee9a in QCoreApplication::notifyInternal2 (receiver=0x55623c1b5aa0, event=0x7ffec16b34c0) at kernel/qcoreapplication.cpp:1063 #28 0x7fe80b0c5e53 in QTimerInfoList::activateTimers (this=this@entry=0x7fe7fc000df8) at kernel/qtimerinfo_unix.cpp:643 #29 0x7fe80b0c359c in QEventDispatcherUNIXPrivate::activateTimers (this=this@entry=0x7fe7fc000d70) a
[kdev-python] [Bug 444484] New: Crash in stylechecker (due to stale ReferencedDUChainTopContext)
https://bugs.kde.org/show_bug.cgi?id=84 Bug ID: 84 Summary: Crash in stylechecker (due to stale ReferencedDUChainTopContext) Product: kdev-python Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: jonathan.ver...@matfyz.cz Target Milestone: --- When working on a python project, I occasionally get the following crashes coming from the stylechecker: #0 Python::StyleChecking::addSetupErrorToContext(QString const&) (this=0x5b4aede0, error="Got invalid size: stdin:5:1:") at /home/jonathan/zdroj/clones/kdev-python/pythonstylechecking.cpp:203 #1 0x7fff319b6f97 in Python::StyleChecking::processOutputStarted() (this=0x5b4aede0) at /home/jonathan/zdroj/clones/kdev-python/pythonstylechecking.cpp:139 #2 0x7fff319b91bc in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (Python::StyleChecking::*)()>::call(void (Python::StyleChecking::*)(), Python::StyleChecking*, void**) (f=(void (Python::StyleChecking::*)(Python::StyleChecking * const)) 0x7fff319b6eae , o=0x5b4aede0, arg=0x7fffce90) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152 I only included the first three frames, since the function which crashes is called in response to a signal (QProcess::readyReadStandardOutput), so the rest of the trace is not interesting. The crash is due to `m_stylechecker` being no longer valid at the point. The only way I see that can happen is due to some problem in the `kdevpythonsupport/codestyle.py` script which leads it to output more stuff then expected or take too long outputting it. That way, the `processOutputStarted` function would read the output up to the expected size (or up to what it can read in 100ms) and then set the `m_currentlyChecking` to nullptr. However, when the script outputs some more after this, `processOutputStarted` is called again, now with `m_currentlyChecking` null which eventually leads to a crash (note also, that when its called again, `m_mutex` is probably not held anymore, so there might be other races).| -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444485] New: System monitor pie charts have graphics aliasing effect
https://bugs.kde.org/show_bug.cgi?id=85 Bug ID: 85 Summary: System monitor pie charts have graphics aliasing effect Product: plasma-systemmonitor Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: yesoji5...@ateampc.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 142938 --> https://bugs.kde.org/attachment.cgi?id=142938&action=edit system monitor overview SUMMARY System monitor pie charts have graphics aliasing effect. STEPS TO REPRODUCE 1. Open system monitor 2. See overview page; 3. Add widgets to desktop and remove background OBSERVED RESULT Rough circle EXPECTED RESULT antialised drawing. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-38-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 3.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444483] KWin crashes consistently on startup after updating Debian Testing
https://bugs.kde.org/show_bug.cgi?id=83 --- Comment #1 from Vlad Zahorodnii --- (In reply to Jim+kde from comment #0) > Application: kwin_x11 (5.21.5) > ... > libkdecorations2-5v5:amd64 from 4:5.21.5-2 to 4:5.23.0-2. It looks like a packaging issue. kwin 5.21 is incompatible with kdecoration 5.23 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444486] New: Windows minimize and restore to a panel that no longer exists
https://bugs.kde.org/show_bug.cgi?id=86 Bug ID: 86 Summary: Windows minimize and restore to a panel that no longer exists Product: plasmashell Version: 5.21.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: walterm...@gmail.com Target Milestone: 1.0 Created attachment 142939 --> https://bugs.kde.org/attachment.cgi?id=142939&action=edit Reproduction steps SUMMARY Windows minimize and restore to a panel that no longer exists STEPS TO REPRODUCE 1. Create a new Kubuntu default panel on the top of the screen 2. Delete this panel right after creating it. 3. Try to minimize or restore an application OBSERVED RESULT When minimizing or restoring, the window animates to the top of the screen where the panel used to be. EXPECTED RESULT The window should animate to the correct panel, as the panel on top no longer exists. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443697] KDE does not respect "primary" screen settings when launching applications and using multiple screens
https://bugs.kde.org/show_bug.cgi?id=443697 --- Comment #6 from Cristiano Guadagnino --- I'm now using openSuse Tumbleweed version 20211024 and most bugs seem to be fixed. I also found a KWin script named "Always Open on Active Screen" by Natalie Clarius that helped. However, I find that things work correctly now even on my second PC where I did not apply that KWin script. The only problem remaining is that Dolphin keeps opening on the left screen, but I'm not convinced it's a problem in Plasma, as my second PC does not exhibit this behavior anymore. Both PCs are running openSuse Tumbleweed version 20211024. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443697] KDE does not respect "primary" screen settings when launching applications and using multiple screens
https://bugs.kde.org/show_bug.cgi?id=443697 --- Comment #7 from Cristiano Guadagnino --- (In reply to Cristiano Guadagnino from comment #6) > I'm now using openSuse Tumbleweed version 20211024 and most bugs seem to be > fixed. > I also found a KWin script named "Always Open on Active Screen" by Natalie > Clarius that helped. However, I find that things work correctly now even on > my second PC where I did not apply that KWin script. > The only problem remaining is that Dolphin keeps opening on the left screen, > but I'm not convinced it's a problem in Plasma, as my second PC does not > exhibit this behavior anymore. > Both PCs are running openSuse Tumbleweed version 20211024. I should stress that the desired behavior, in my case, is that windows open on the active screen, rather than the primary (which would be my second choice). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443697] KDE does not respect "primary" screen settings when launching applications and using multiple screens
https://bugs.kde.org/show_bug.cgi?id=443697 --- Comment #8 from Cristiano Guadagnino --- (In reply to Cristiano Guadagnino from comment #6) > I'm now using openSuse Tumbleweed version 20211024 and most bugs seem to be > fixed. > I also found a KWin script named "Always Open on Active Screen" by Natalie > Clarius that helped. However, I find that things work correctly now even on > my second PC where I did not apply that KWin script. > The only problem remaining is that Dolphin keeps opening on the left screen, > but I'm not convinced it's a problem in Plasma, as my second PC does not > exhibit this behavior anymore. > Both PCs are running openSuse Tumbleweed version 20211024. Sorry, one more thing: openSuse Tumbleweed 20211024 means Plasmashell 5.23.1. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444487] New: hginfo test detects an extra lock inside data symbol "_rtld_local"
https://bugs.kde.org/show_bug.cgi?id=87
Bug ID: 87
Summary: hginfo test detects an extra lock inside data symbol
"_rtld_local"
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: helgrind
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
Target Milestone: ---
This is with valgrind 3.18.1 and glibc 2.34:
gdbserver_tests/hginfo/stderrB.diff:
Lock ga 0x {
Address 0x is 2440 bytes inside data symbol "_rtld_local"
kind mbRec
}
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 442972] Copy/Cut became very slow and bugged
https://bugs.kde.org/show_bug.cgi?id=442972 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Keywords||regression, release_blocker -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444483] KWin crashes consistently on startup after updating Debian Testing
https://bugs.kde.org/show_bug.cgi?id=83 --- Comment #2 from jim+...@nekojimi.moe --- On closer inspection it does seem to be a packaging issue, sorry. There's a bug already filed in Debian for it here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726 Using the workaround in comment #25 (downgrading libkdecorations2-5v5) resolved the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443985] Kwin Crashing constantly
https://bugs.kde.org/show_bug.cgi?id=443985 --- Comment #4 from tim --- Indeed it is! Thanks so much!! Keep up the incredible work, y'all. On Mon, Oct 25, 2021 at 3:00 AM Vlad Zahorodnii wrote: > https://bugs.kde.org/show_bug.cgi?id=443985 > > --- Comment #3 from Vlad Zahorodnii --- > because this bug is fixed in 5.23.0? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444488] New: Use glibc.pthread.stack_cache_size tunable
https://bugs.kde.org/show_bug.cgi?id=88
Bug ID: 88
Summary: Use glibc.pthread.stack_cache_size tunable
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
Target Milestone: ---
Since glibc 2.34 the internal/private stack_cache_maxsize variable isn't
available anymore, which causes "sched WARNING: pthread stack cache cannot be
disabled!" when the simhint no_nptl_pthread_stackcache is set (e.g. in
helgrind/tests/tls_threads.vgtest)
See coregrind/pub_core_clientstate.h:
/* glibc nptl pthread systems only, when no-nptl-pthread-stackcache
was given in --sim-hints.
Used for a (kludgy) way to disable the cache of stacks as implemented in
nptl glibc.
Based on internal knowledge of the pthread glibc nptl/allocatestack.c code:
a huge value in stack_cache_actsize (bigger than the constant
stack_cache_maxsize) makes glibc believes the cache is full
and so stacks are always released when a pthread terminates.
Several ugliness in this kludge:
* hardcodes private glibc var name "stack_cache_maxsize"
* based on knowledge of the code of the functions
queue_stack and __free_stacks
* static symbol for "stack_cache_maxsize" must be in
the debug info.
It would be much cleaner to have a documented and supported
way to disable the pthread stack cache. */
extern SizeT* VG_(client__stack_cache_actsize__addr);
Instead we should use the new (in glibc 2.34) tunable:
@deftp Tunable glibc.pthread.stack_cache_size
This tunable configures the maximum size of the stack cache. Once the
stack cache exceeds this size, unused thread stacks are returned to
the kernel, to bring the cache size below this limit.
The value is measured in bytes. The default is @samp{41943040}
(fourty mibibytes).
@end deftp
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 444439] Floating-point HDR colors get clipped from painting, layer blending or color space conversion
https://bugs.kde.org/show_bug.cgi?id=39 --- Comment #3 from M --- Right, so I did some more testing. First, I could not reproduce the problem that basic blending operation I know can algorithmically handle HDR color values would clip them, such as Addition, or Multiply and Normal with values above 1.0. I found is that the Specific Color Selector could show the values clipped at 1.0, but the Foreground color selector window shows the correct channel values, and that picking an HDR color from a palette would also paint a clipped or somehow tone-mapped version of the color. That would tie back to https://bugs.kde.org/show_bug.cgi?id=437429 So unless I can reproduce what I thought was happening initially, I'm assuming I was mislead by the number readouts and those blending modes are not affected. What I can confirm however is that certain color space conversions will clip color values to 1.0, possibly between linear and non-linear profiles. This is not exclusive to Krita 5.1, I can reproduce it the same way in 4.4.8 on Windows, but curiously 4.4.8 on Linux doesn't seem to have the issue. It might be a Windows specific bug, but not a regression to Krita 5.1. To reproduce on a Windows build: 1. Create a document in 16 or 32-bit float and ACEScg-g10 2. Produce some HDR color values on the canvas and merge down all layers 3. Verify from the Foreground color picker that any color channel is way above 1.0 4. Use Image > Convert Image Color Space. Leave the bit depth, choose sRGB-srgbtrc (not linear). Rendering intent can optionally be relative colorimetric 5. Check the colors on canvas again in the Foreground color picker The colors on canvas should now be clipped at 1.0. Some 16-bit float conversions seem to be more robust, but most combinations will still result in clipping on my end. You can also try the conversion result of negative float colors from Subtract. Though none of the color pickers seem to indicate negative values. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444489] New: [Wayland] Kickoff launches dragged-and-dropped favorite when I click on any part of it
https://bugs.kde.org/show_bug.cgi?id=89 Bug ID: 89 Summary: [Wayland] Kickoff launches dragged-and-dropped favorite when I click on any part of it Product: plasmashell Version: 5.22.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. use Wayland session 2. open Kickoff 3. drag-and-drop any app in favorites list 4. click on any part of Kickoff OBSERVED RESULT Kickoff launches the favorite dragged-and-dropped in the step 3 EXPECTED RESULT observed result should not occur SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION categories/apps/buttons are not highlighted on mouseover after drag-and-drop in the step 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #33 from Patrick Silva --- On Arch Linux, package plasma-desktop 5.23.2-2 fixes the bug on X11. But there is a bug possibly related to this fix on Wayland, see bug 89. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 330503] Table headings not adjustable
https://bugs.kde.org/show_bug.cgi?id=330503 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #9 from S. Christian Collins --- This bug seems to be resolved now, as tested on the following configuration: OS: KDE Neon 5.23 User Edition Plasma Desktop 5.23.2 KDE Frameworks 5.87.0 Qt 5.15.3 Muon doesn't appear to have been updated (still at 5.8.0), so it looks like the fix came through one of the KDE libraries? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #31 from ltstarwars...@gmail.com --- Requesting this be re-opened, I'm still getting the issue on 5.23.2 10/27/21 7:40 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-background: GetAppState called: no parameters 10/27/21 7:41 AMkactivitymanagerd qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: Removing output: 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: manufacturer: "LG Electronics" 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: model: "27GN950/007NTEP02148" 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/27/21 7:41 AMbaloorunner qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/27/21 7:41 AMkernel usb 7-1.4: USB disconnect, device number 4 10/27/21 7:41 AMkernel Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 10/27/21 7:41 AMkernel Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 10/27/21 7:41 AMkernel Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: Adding output: 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: manufacturer: "LG Electronics" 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: model: "27GN950/007NTEP02148" 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: resolution: QSize(3840, 2160) 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: Adding output: 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: manufacturer: "LG Electronics" 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: model: "27GN950/007NTEP02148" 10/27/21 7:41 AMorg.freedesktop.impl.portal.desktop.kde xdp-kde-wayland-integration: resolution: QSize(3840, 2160) It then repeats the attempt to add my monitor about 20 more times. In addition, drkonqi crashes if I click on the report bug button after this. It didn't do that before. If I can get a backtrace without drkonqi crashing, I'll attach the crash file for the new version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444489] [Wayland] Kickoff launches dragged-and-dropped favorite when I click on any part of it
https://bugs.kde.org/show_bug.cgi?id=89 Patrick Silva changed: What|Removed |Added Platform|Other |Archlinux Packages Version|5.22.90 |5.23.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423426] POP3 setup wizard defaults to unencrypted connections.
https://bugs.kde.org/show_bug.cgi?id=423426 Sandro Knauß changed: What|Removed |Added CC||skna...@kde.org --- Comment #7 from Sandro Knauß --- It is a CVE assigned for this bugreport: CVE-2020-15954. https://nostarttls.secvuln.info/ sees this as fixed in 20.08. Debian follows the bugreport and the information of the CVE and maked that to be closed: https://security-tracker.debian.org/tracker/CVE-2020-15954 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444490] New: "Login" column doesn't show usernames
https://bugs.kde.org/show_bug.cgi?id=90 Bug ID: 90 Summary: "Login" column doesn't show usernames Product: plasma-systemmonitor Version: 5.23.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 142941 --> https://bugs.kde.org/attachment.cgi?id=142941&action=edit Screenshot of Plasma Systemmonitor SUMMARY If enabled, "login" column shows no usernames of owners of processess. STEPS TO REPRODUCE 1. Enable "login" column in Plasma Systemmonitor. 2. Observe the effect. OBSERVED RESULT No usernames on this column. EXPECTED RESULT "Login" column contains usernames corresponding to UIDs of processess. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-7619-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu backports PPA enabled -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444490] "Login" column doesn't show usernames
https://bugs.kde.org/show_bug.cgi?id=90 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 357981] Quick / Incremental search of package name in the list (not filtering)
https://bugs.kde.org/show_bug.cgi?id=357981 S. Christian Collins changed: What|Removed |Added Attachment #107457|0 |1 is obsolete|| CC||s_chriscoll...@hotmail.com --- Comment #2 from S. Christian Collins --- Created attachment 142942 --> https://bugs.kde.org/attachment.cgi?id=142942&action=edit GIF showing the bug Being able to start typing a package name--or even just a letter or two--to jump within the package list is what keeps me using Synaptic over Muon. Without this feature, navigating such a long package list becomes quite clumsy. Here is a GIF showing how this works in Synaptic. You can see the text as I am typing it in a little box that appears to the bottom-right of the package list. I have also "obsoleted" the attachment shared in comment #1, which is a script file that has nothing to do with this bug. My System: OS: KDE Neon 5.23 User Edition Plasma Desktop 5.23.2 KDE Frameworks 5.87.0 Qt 5.15.3 Muon version 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Wolfram Köhn changed: What|Removed |Added CC||wolfram.ko...@gmx.net --- Comment #28 from Wolfram Köhn --- I also liked the cube. Please bring it back !!! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 444491] New: drkonqi Crashes During Attempt to Backtrace plasmashell on Wayland
https://bugs.kde.org/show_bug.cgi?id=91 Bug ID: 91 Summary: drkonqi Crashes During Attempt to Backtrace plasmashell on Wayland Product: drkonqi Version: 5.23.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ltstarwars...@gmail.com Target Milestone: --- Created attachment 142943 --> https://bugs.kde.org/attachment.cgi?id=142943&action=edit drkonqi crash report SUMMARY drkonqi crashes when attempt to click on developer information tab or report bug button after wayland related plasmashell crash. See bug 438839 for crash attempting to generate backtrace of to request reopening. STEPS TO REPRODUCE 1. Experience crash per bug 438839 and related duplicates. 2. Click on either "report bug" or the "Developer Information" tab in drkonqi OBSERVED RESULT Reporter freezes for extended period before crashing. EXPECTED RESULT Able to get backtrace either via the developer information tab or the report bug button. SOFTWARE/OS VERSIONS Operating System: Ubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-21-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION System is configured to receive updates from the Kubuntu updates and backports PPAs. Crash can be reproduced every time. BACKTRACE Application: The KDE Crash Handler (drkonqi), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140569437149632) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140569437149632) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140569437149632, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7fd8e2ac3476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fd8e2aa97b7 in __GI_abort () at abort.c:79 #9 0x7fd8e2f68ba3 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #10 QMessageLogger::fatal (this=this@entry=0x7ffd9e6a3840, msg=msg@entry=0x7fd8e1aab078 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #11 0x7fd8e1a0fe45 in QtWaylandClient::QWaylandDisplay::checkError (this=) at ./src/client/qwaylanddisplay.cpp:209 #12 QtWaylandClient::QWaylandDisplay::checkError (this=) at ./src/client/qwaylanddisplay.cpp:204 #13 0x7fd8e1a2006a in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x56093b75f770) at ./src/client/qwaylanddisplay.cpp:222 #14 0x7fd8e31c8a88 in doActivate (sender=0x56093b7a3360, signal_index=4, argv=0x7ffd9e6a3940) at kernel/qobject.cpp:3898 #15 0x7fd8e31c1d67 in QMetaObject::activate (sender=sender@entry=0x56093b7a3360, m=m@entry=0x7fd8e342d800 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #16 0x7fd8e318dba7 in QAbstractEventDispatcher::awake (this=this@entry=0x56093b7a3360) at .moc/moc_qabstracteventdispatcher.cpp:149 #17 0x7fd8e31ea5db in QEventDispatcherGlib::processEvents (this=0x56093b7a3360, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #18 0x7fd8e318fa9b in QEventLoop::exec (this=this@entry=0x7ffd9e6a3a60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x7fd8e3198024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x7fd8e37e4d10 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #21 0x7fd8e3ef8629 in QApplication::exec () at kernel/qapplication.cpp:2824 #22 0x56093b005829 in main (argc=, argv=) at ./src/main.cpp:229 [Inferior 1 (process 29603) detached] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #3 from Martin Senftleben --- Thank you, Mike, that was a helpful hint. Here is the output: "digikam.widgets: Use installed icons digikam.general: Switch to widget style: "breeze" digikam.general: AlbumWatch is disabled digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name:"digikam" DB Face Name: "digikam" DB Similarity Name:"" Connect Options: "" Host Name: "localhost" Host port: Internal Server: false Internal Server Path: "" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "drmartin" Password: "XXX" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 12 digikam.coredb: Core database: makeUpdates 12 to 13 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Die Abfrage konnte nicht ausgeführt werden" "Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50537, now running 100604. Please use mariadb-upgrade to fix this error" "1558" 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ] Statement [ "\nDROP PROCEDURE IF EXISTS create_index_if_not_exists;\n" ] digikam.coredb: Core database: schema update to V 13 failed! digikam.coredb: Core database: cannot process schema initialization" I hope this answers Gilles questions as well. It seems it's using MariaDB? As mentioned above, I do not know what digikam is doing in the background, I was always content with what it does, until this bug occured. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #4 from Martin Senftleben --- If it's Mariadb, it has the version 10.6.4-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444492] New: Few Ideas
https://bugs.kde.org/show_bug.cgi?id=92 Bug ID: 92 Summary: Few Ideas Product: digikam Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: cont...@wild-turtles.com Target Milestone: --- Hello, I not go deep inside the software and i come here after a discution with a friend. I think some "features" in https://www.ephoto.fr/ can be include in digikam. - send to WordPress 5 ou Drupal 9 - audit code owasp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442699] Laptop display remains black with only a cursor after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=442699 Jan Petersen changed: What|Removed |Added CC||jpeters...@hotmail.com --- Comment #3 from Jan Petersen --- I think I've run into the same issue. On a Dell XPS13 laptop. No external monitors. After sleep, the screen does not appear to wake up. The power light is still on, and if I leave the laptop running unplugged, it will run down the battery to 0% and die. I'm on the latest anniversary release of Neon, from a few days ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #459 from Olivier BELLEUX --- I never understood what the activities were for or how they differed from a virtual desktop. The concept is wrong from the start. If you look at a dictionary for "activité": (Yes, I'm French...) - [Larousse](https://www.larousse.fr/dictionnaires/francais/activité/947) 1) A set of phenomena by which certain forms of life, a process, a functioning are manifested: Physical activity, intellectual activity. 2) Faculty, power to act; manifestation of this faculty: A man overflowing with activity. - [dictionary.lerobert](https://dictionnaire.lerobert.com/definition/activite) 1) (THINGS) The faculty or fact of acting. The activity of a drug. - A volcano in activity. ➙ action. 2) Coordinated acts and works of human origin. Physical activity. The industrial activity of a region. - PLURAL The activities of sb. ➙ occupation. 3) The quality of an active person. To show great activity. 4) Situation of a person (ESPECIALLY a military person) who is exercising his employment (as opposed to retirement, availability). An activity is not a place on which to place windows or widgets or wallpaper… That's a desktop! The concept of "activity" would be interesting if it were rather a tool allowing to save a particular state of a work session and to come back to it later, i.e. to save the windows, widgets and wallpapers at a given moment in a database and to allow, via a graphic interface (a dashboard) to consult the list of saved activities, the various existing snapshots and to choose one of them to reopen it and resume from this state of the user session. To be more synthetic: 1) turn on the computer 2) login + password = connection to the user account with the default activity 3) open the activity dashboard and choose the "photography" activity 4) work on you holidays photos... 5) open the activities dashboard and choose the activity "contribute to kde", reopen the session of 2014-11-21. 6) reply to bug 341143. 7) open the activity dashboard and choose the activity "play 0ad 8) turn off the computer and go to sleep This is just an idea that popped into my head, so I'll just give it to you as it comes. Sincerely -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 443214] KOrganizer segmentation fault when creating new caldendar event with multiple reminders
https://bugs.kde.org/show_bug.cgi?id=443214 --- Comment #4 from gjditchfi...@acm.org --- (In reply to James Beddek from comment #3) > ... however this crash seems very reproducible > just by clicking on the "Status" and "Response" selections for a blank > attendee without changing anything. Perhaps try this before adding the > reminders? Crash on my first try. Progress, of a sort! -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 444324] Show qr code form ticket
https://bugs.kde.org/show_bug.cgi?id=444324 Volker Krause changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||itinerary/commit/a9bfd52703 ||b479b27312366ccdae784d2bd18 ||89b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Volker Krause --- Git commit a9bfd52703b479b27312366ccdae784d2bd1889b by Volker Krause. Committed on 27/10/2021 at 15:56. Pushed by vkrause into branch 'master'. Add PDF417 barcode support for tickets This is needed for example for MÁV train tickets. Will need KF 5.88 to actually work though. M +14 -6src/app/TicketTokenDelegate.qml https://invent.kde.org/pim/itinerary/commit/a9bfd52703b479b27312366ccdae784d2bd1889b -- You are receiving this mail because: You are watching all bug changes.
