[kwin] [Bug 479293] New: Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293
Bug ID: 479293
Summary: Multi-monitor Wayland surface does not extend to the
left (Plasma 6)
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: stefan.hoffmeis...@econos.de
Target Milestone: ---
SUMMARY
In a Wayland multi-monitor setup where the non-primary screen is to the _left_
of the primary screen ("extend to the left"), the content is overlapped into
the primary screen.
In ASCII art, for
* left non-primary == 2.5K resolution
* primary == 4K resolution
this looks like
```
+-++
| ||
|-+|
| |
| |
+--|
```
Extending to the right works as expected. This also holds true for a triple
monitor setup, where one screen extends to the left and one screen extends to
the right of the primary screen.
"Display Configuration" shows the intended (correct) layout.
This may be an artefact of running KDE Plasma 6 b2+ (git master) under VMware
Workstation / vmwgfx with `export KWIN_DRM_NO_AMS=0`
STEPS TO REPRODUCE
1. create a multi-monitor setup
2. "physically" place at least one screen to the left of the primary screen
3. use "Display Configuration" to assert that physical left screen is logically
placed to extend the primary screen to the left (i.e. vertically aligned at the
top, offset to the left by resolution of secondary screen)
OBSERVED RESULT
Left screen overlaps primary screen as in ASCII art diagram above.
EXPECTED RESULT
Left screen extends desktop to the left.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 477539] Snapping a window to maximize on screen 1 when another application on second is maximized creates artifacts on the screen next to it
https://bugs.kde.org/show_bug.cgi?id=477539 --- Comment #6 from Iason Malkotsis --- Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 0:1920x1080@60! 1:1920x1080@240* 2:1920x1080@144 3:1920x1080@120 4:1920x1080@120 5:1920x1080@96 6:1920x1080@72 7:1920x1080@60 8:1920x1080@60 9:1920x1080@60 10:1920x1080@50 11:1920x1080@50 12:1920x1080@48 13:1680x1050@60 14:1600x900@60 15:1280x1024@75 16:1280x1024@60 17:1440x900@60 18:1280x800@60 19:1152x864@75 20:1280x720@60 21:1280x720@60 22:1280x720@50 23:1024x768@75 24:1024x768@60 25:800x600@75 26:800x600@60 27:720x576@50 28:720x480@60 29:720x480@60 30:720x480@60 31:720x480@60 32:640x480@75 33:640x480@60 34:640x480@60 35:640x480@60 36:720x400@70 37:1280x1024@60 38:1024x768@60 39:1280x800@60 40:1920x1080@60 41:1600x900@60 42:1368x768@60 43:1280x720@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Output: 2 DP-2 enabled connected priority 3 DisplayPort Modes: 0:1920x1080@60*! 1:1680x1050@60 2:1400x1050@60 3:1600x900@60 4:1280x1024@75 5:1280x1024@60 6:1440x900@60 7:1280x800@60 8:1152x864@75 9:1280x720@60 10:1024x768@75 11:1024x768@60 12:832x624@75 13:800x600@75 14:800x600@60 15:800x600@56 16:640x480@75 17:640x480@60 18:720x400@70 19:1280x1024@60 20:1024x768@60 21:1280x800@60 22:1920x1080@60 23:1600x900@60 24:1368x768@60 25:1280x720@60 Geometry: 1920,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477539] Snapping a window to maximize on screen 1 when another application on second is maximized creates artifacts on the screen next to it
https://bugs.kde.org/show_bug.cgi?id=477539 Iason Malkotsis changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Iason Malkotsis --- Retested using the latest KDE plasma 6.0 beta 2 and it seems that this is no longer an issue -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 479292] ModemManager-QT Compiling from master source is failing
https://bugs.kde.org/show_bug.cgi?id=479292 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #1 from Stefan Hoffmeister --- Created attachment 164616 --> https://bugs.kde.org/attachment.cgi?id=164616&action=edit drm_info in broken state (left-extend not working) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #2 from Stefan Hoffmeister --- Created attachment 164617 --> https://bugs.kde.org/attachment.cgi?id=164617&action=edit drm_info in working state (right-extend working well) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479275] Duplicate tags created with "\" as separator since upgrade to 8.3
https://bugs.kde.org/show_bug.cgi?id=479275 --- Comment #4 from Jens --- OK, this is understandable, but I actually loved the possibility to organize my face tags in a hierarchy directly upon creation. No way to do this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #3 from Stefan Hoffmeister --- Attached drm_info dumps where VMware Workstation adds the monitor "to the left" and "to the right", respectively, where KDE Desktop Configuration matches the extend intent exactly * left-extend == 2.5k screen physically (and mapped through host) to the left * right-extend == 3k laptop screen physically (and mapped through the host) to the right Center screen is always the 4k screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #4 from Stefan Hoffmeister --- FWIW, and possibly a separate challenge: Take the working "extend to the right" setup from above and move the secondary screen to _extend to the bottom_. This does not render correctly, either (fair enough - see above). Do note that the mouse cursor now moves "in an unnatural fashion" - it feels as if some unsuitable mouse acceleration profile is being applied. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 478882] Nightly Kast APK fails to locate symbols __clear_cache (can't start)
https://bugs.kde.org/show_bug.cgi?id=478882 b...@mogwai.be changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from b...@mogwai.be --- Forgot to close this after it got fixed. Feel free to open new bug reports in case you hit other bugs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #5 from Stefan Hoffmeister --- No difference in behaviour with KWIN_DRM_NO_AMS _not_ set - right now (on my kernel) this implies no atomic mode-setting. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Dan changed: What|Removed |Added Status|RESOLVED|VERIFIED Resolution|FIXED |REMIND --- Comment #5 from Dan --- (In reply to Waqar Ahmed from comment #1) > Hi, would it be possible for you to try the latest Kate? You seem to be on > Arch, so the latest version should be available Hi, I have tried it with the latest version available in Arch: * kate 23.08.4 * KDE Frameworks 5.113.0 * Qt 5.15.11 *Still too slow*: * sort ~ 2sec * kate >> minute -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479294] New: Error exporting to Google Photos
https://bugs.kde.org/show_bug.cgi?id=479294 Bug ID: 479294 Summary: Error exporting to Google Photos Classification: Applications Product: digikam Version: 8.2.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Album Assignee: digikam-bugs-n...@kde.org Reporter: antonrosenf...@yahoo.co.uk Target Milestone: --- SUMMARY Exporting files to google photos generates an error window with the following message Error transferring https://photoslibrary.googleapis.com/v1/albums?pageSize=50 - server replied: As I understand, this has happened before and it is a problem with Google, but they have to be contacted. Perhaps somebody has done this already, but if not, I am flagging this up. *** 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. Export 2. Select Google photos 3. OBSERVED RESULT Generates error message Error transferring https://photoslibrary.googleapis.com/v1/albums?pageSize=50 - server replied: EXPECTED RESULT Photos are uploaded to Google Photos SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478936] Unable to bind / use the calculator key in plasma 6
https://bugs.kde.org/show_bug.cgi?id=478936 --- Comment #3 from Steven Eastland --- As I mentioned in the bug I filed that was marked as a duplicate of this one, my calculator key works in an X11 session, but not in a Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479295] New: feature request for digiKam's geo tagging
https://bugs.kde.org/show_bug.cgi?id=479295 Bug ID: 479295 Summary: feature request for digiKam's geo tagging Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rainer.ba...@freenet.de Target Milestone: --- I am searching for an easier way to correlate GPS- Tracks to photos Is there a possibility to select one picture (out of my collection where I want to edit the GPS- coordinates) and pick a position from the GPS track (where I know the particular picture was taken) to calculate the time difference for all pictures in the collection? Would be nice to have a table or list of all GPS- positions and if I click on one position this position should be marked in the Map-View. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Kåre Särs changed: What|Removed |Added Resolution|REMIND |FIXED Status|VERIFIED|RESOLVED Version Fixed In||24.02.0 CC||kare.s...@iki.fi --- Comment #6 from Kåre Särs --- Hi, This has been improved in master and will be released with 24.02.0 in February. If you need the improvement _now_, you have to compile your self or use some bleeding development edge distribution that packages beta versions of KDE software. Instructions for building it your self: https://kate-editor.org/build-it/ Br, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #6 from Stefan Hoffmeister --- The matching Fedora Rawhide (40) GNOME setup, which runs in legacy mode (no atomic mode-setting) exposes the exact same behavior as KDE Plasma 6 b2+ (git master) on Wayland. To that extent, there may be a commonality to the multi-monitor Wayland driving of GNOME and KDE Plasma 6 on Fedora Rawhide (40). Additional data point: I also tried KDE Plasma 5.27.10 in an X11 session on Arch Linux, with the same virtual graphics "hardware" setup and with legacy mode setting. In that X11 environment, the screens both left-extend and right-extend correctly for rendering (this was also working previously on F39, do not have this infra at the moment). Note that that the KDE X11 setup has challenges in cursor to (virtual) screen mapping though - but those can be fixed by running a script that uses kscreen-doctor to "re-layout" the screens in a different sequence (cf https://github.com/vmware/open-vm-tools/issues/484#issuecomment-1703922094. So, in theory, given the above, one could argue that Wayland KDE Plasma 6 has regressed relative to X11 KDE Plasma 5.27.10. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 478808] Incorrect feedback for Mastermind level 8
https://bugs.kde.org/show_bug.cgi?id=478808 --- Comment #4 from lc...@april.org --- (In reply to Jazeix Johnny from comment #3) > You're right, then let's implement it the correct way :) I do not really want to look at the existing code (you certainly know how long it usually takes to enter a code you have not written). Anyway, if a feedback at level 1-4 is stored in a std::vector (where Key_peg is an enum, with three values, for black, white and nothing) of size the number of pegs in the code (3 at level 1, 4 at level 2, etc.), then the same could be done for the harder levels. A mere function could take such a feedback and return a std::pair: how many black pegs and how many white pegs. It would simply iterate over the vector and, at each iteration, increment the proper counter or none (for the nothing Key_peg). If a feedback at level 1-4 is *not* stored in a std::vector, well, maybe doing so would be "the correct way". :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #10 from Dennis --- I use wayland (In reply to fanzhuyifan from comment #9) > (In reply to Dennis from comment #7) > > confirmed on: > > > > Operating System: KDE neon Unstable Edition > > KDE Plasma Version: 5.91.90 > > KDE Frameworks Version: 5.248.0 > > Qt Version: 6.6.1 > > Kernel Version: 6.2.0-39-generic (64-bit) > > Graphics Platform: Wayland > > Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz > > Memory: 15,3 GiB of RAM > > Graphics Processor: Mesa Intel® UHD Graphics 620 > > Manufacturer: Dell Inc. > > Product Name: XPS 13 9380 > > Is your sddm using wayland or x11? Wayland as far as I can see. I login with Wayland selected at least. I'm not sure if the system boots up with x11/wayland before logging in. I looked at the sddm config files, but no x11 is set. Let me know how I can check this further if you need to know more. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 478808] Incorrect feedback for Mastermind level 8
https://bugs.kde.org/show_bug.cgi?id=478808 --- Comment #5 from Jazeix Johnny --- (In reply to lcerf from comment #4) > (In reply to Jazeix Johnny from comment #3) > > You're right, then let's implement it the correct way :) > > I do not really want to look at the existing code (you certainly know how > long it usually takes to enter a code you have not written). Anyway, if a > feedback at level 1-4 is stored in a std::vector (where Key_peg is > an enum, with three values, for black, white and nothing) of size the number > of pegs in the code (3 at level 1, 4 at level 2, etc.), then the same could > be done for the harder levels. A mere function could take such a feedback > and return a std::pair: how many black pegs and > how many white pegs. It would simply iterate over the vector and, at each > iteration, increment the proper counter or none (for the nothing Key_peg). > If a feedback at level 1-4 is *not* stored in a std::vector, well, > maybe doing so would be "the correct way". :-) No worry, we'll take a look :). We plan to fix it for the next version we should do in February. The function to fix is probably https://invent.kde.org/education/gcompris/-/blob/master/src/activities/superbrain/superbrain.js#L143 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479294] Error exporting to Google Photos
https://bugs.kde.org/show_bug.cgi?id=479294 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED OS|Other |Microsoft Windows CC||metzping...@gmail.com Component|Thumbs-Album|Plugin-WebService-Google Resolution|--- |DUPLICATE Platform|Other |Microsoft Windows --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 472494 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 Maik Qualmann changed: What|Removed |Added CC||antonrosenf...@yahoo.co.uk --- Comment #11 from Maik Qualmann --- *** Bug 479294 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 --- Comment #7 from Dan --- (In reply to Kåre Särs from comment #6) > Hi, > > This has been improved in master and will be released with 24.02.0 in > February. > > If you need the improvement _now_, you have to compile your self or use some > bleeding development edge distribution that packages beta versions of KDE > software. > > Instructions for building it your self: > https://kate-editor.org/build-it/ > > Br, > Kåre Hi, no need to hurry. Thank you for the info. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479295] feature request for digiKam's geo tagging
https://bugs.kde.org/show_bug.cgi?id=479295 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Assignee|unassigned-b...@kde.org |digikam-bugs-n...@kde.org Product|kde |digikam Component|general |Plugin-Generic-GeolocationE ||dit -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479295] feature request for digiKam's geo tagging
https://bugs.kde.org/show_bug.cgi?id=479295 Maik Qualmann changed: What|Removed |Added Version|unspecified |8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 479248] Help has invalid URL
https://bugs.kde.org/show_bug.cgi?id=479248 Thomas Baumgart changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/-/commit/c29012 ||e25bd265711e71c40245125439f ||d4eebde Resolution|--- |FIXED Version Fixed In||5.2 Status|CONFIRMED |RESOLVED --- Comment #1 from Thomas Baumgart --- Git commit c29012e25bd265711e71c40245125439fd4eebde by Thomas Baumgart. Committed on 02/01/2024 at 10:32. Pushed by tbaumgart into branch 'master'. Fix link to documentation FIXED-IN: 5.2 M +1-1kmymoney/wizards/newuserwizard/knewuserwizard.cpp https://invent.kde.org/office/kmymoney/-/commit/c29012e25bd265711e71c40245125439fd4eebde -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479296] New: Some images are not displayed in the slideshow for desktop background.
https://bugs.kde.org/show_bug.cgi?id=479296 Bug ID: 479296 Summary: Some images are not displayed in the slideshow for desktop background. Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: tnem...@free.fr CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY Hi. It's been bugging me for some time now and I thought someone would report it quickly but that has not been the case ^_^; I have a folder, ~/Images/Backgrounds/slideshow, that's filled with images from previous KDE/Plasma versions default backgrounds and some. They are ALL symlinks to real images but strangely, only some of them show up in the desktop background configuration window. STEPS TO REPRODUCE 1. Collect old KDE/Plasma "Next" backgrounds from Debian in separate directories (since all of them are named "Next") and some from Kali linux 2. Create a directory for desktop background slideshow 3. Create symlinks to original "Next" images (with meaningful names) in the slideshow directory 4. Use that directory in the desktop background configuration window OBSERVED RESULT All 3 background images from kali linux are displayed, only 3 from KDE/Plasma are shown. EXPECTED RESULT All files/thumbnails should be displayed and available as selection for background slideshow. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz Memory: 31.2 Gio of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics 650 Manufacturer: Intel Corporation Product Name: NUC7i7BNH System Version: J31153-308 ADDITIONAL INFORMATION My directories hierarchy (note: "diaporama" is french for "slideshow") : ```bash $ tree -d . ├── Breeze │ ├── Next-v5.0.0 │ │ └── contents │ │ └── images │ ├── Next-v5.1.0 │ │ └── contents │ │ └── images │ ├── Next-v5.10.0 │ │ └── contents │ │ └── images │ ├── Next-v5.11.0 │ │ └── contents │ │ └── images │ ├── Next-v5.12.0 │ │ └── contents │ │ └── images │ ├── Next-v5.13.0 │ │ └── contents │ │ └── images │ ├── Next-v5.14.0 │ │ └── contents │ │ └── images │ ├── Next-v5.15.0 │ │ └── contents │ │ └── images │ ├── Next-v5.2.0 │ │ └── contents │ │ └── images │ ├── Next-v5.22 │ │ └── contents │ │ └── images │ ├── Next-v5.24 │ ├── Next-v5.26 │ ├── Next-v5.3.0 │ │ └── contents │ │ └── images │ ├── Next-v5.4.0 │ │ └── contents │ │ └── images │ ├── Next-v5.5.0 │ │ └── contents │ │ └── images │ ├── Next-v5.6.0 │ │ └── contents │ │ └── images │ ├── Next-v5.7.0 │ │ └── contents │ │ └── images │ ├── Next-v5.8.0 │ │ └── contents │ │ └── images │ └── Next-v5.9.0 │ └── contents │ └── images ├── diaporama └── Kali ``` Slideshow directory contents : ```bash $ ls -l total 8,0K lrwxrwxrwx 1 thomas thomas 21 3 mars 2019 kali-3840x2160.png -> ../Kali/3840x2160.png lrwxrwxrwx 1 thomas thomas 28 9 juin 2023 kali-cubism-16x9.jpg -> ../Kali/kali-cubism-16x9.jpg lrwxrwxrwx 1 thomas thomas 51 1 juin 2022 kali-layers-16x9.png -> /home/thomas/Images/Fonds/Kali/kali-layers-16x9.png lrwxrwxrwx 1 thomas thomas 52 3 mars 2019 Next-v5.10.0-3840x2160.png -> ../Breeze/Next-v5.10.0/contents/images/3840x2160.png lrwxrwxrwx 1 thomas thomas 52 3 mars 2019 Next-v5.12.0-3840x2160.png -> ../Breeze/Next-v5.12.0/contents/images/3840x2160.png lrwxrwxrwx 1 thomas thomas 52 3 mars 2019 Next-v5.13.0-3840x2160.png -> ../Breeze/Next-v5.13.0/contents/images/3840x2160.png lrwxrwxrwx 1 thomas thomas 51 3 mars 2019 Next-v5.2.0-2560x1440.png -> ../Breeze/Next-v5.2.0/contents/images/2560x1440.png lrwxrwxrwx 1 thomas thomas 73 29 déc. 2021 Next-v5.22-3840x2160.png -> /home/thomas/Images/Fonds/Breeze/Next-v5.22/contents/images/3840x2160.png lrwxrwxrwx 1 thomas thomas 57 12 janv. 2022 Next-v5.24-3840x2160.jpg -> /home/thomas/Images/Fonds/Breeze/Next-v5.24/3840x2160.jpg lrwxrwxrwx 1 thomas thomas 62 29 oct. 2022 Next-v5.26-3840x2160-dark.png -> /home/thomas/Images/Fonds/Breeze/Next-v5.26/3840x2160-dark.png lrwxrwxrwx 1 thomas thomas 57 29 oct. 2022 Next-v5.26-3840x2160.png -> /home/thomas/Images/Fonds/Breeze/Next-v5.26/3840x2160.png lrwxrwxrwx 1 thomas thomas 51 3 mars 2019 Next-v5.3.0-2560x1440.png -> ../Breeze/Next-v5.3.0/contents/images/2560x1440.png lrwxrwxrwx 1 thomas thomas 51 3 mars 2019 Next-v5.4.0-2560x1440.png -> ../Breeze/Next-v5.4.0/contents/images/2560x1440.png lrwxrwxrwx 1 tho
[gcompris] [Bug 478808] Incorrect feedback for Mastermind level 8
https://bugs.kde.org/show_bug.cgi?id=478808 --- Comment #6 from lc...@april.org --- (In reply to Jazeix Johnny from comment #5) > The function to fix is probably > https://invent.kde.org/education/gcompris/-/blob/master/src/activities/ > superbrain/superbrain.js#L143 JavaScript... now, I really do not want to look at the code. Lol. Thank you in advance for your fix and for the next version. :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479295] feature request for digiKam's geo tagging
https://bugs.kde.org/show_bug.cgi?id=479295 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479295] feature request for digiKam's geo tagging
https://bugs.kde.org/show_bug.cgi?id=479295 --- Comment #1 from Maik Qualmann --- digiKam can assign the coordinates to the images using a GPS file. https://docs.digikam.org/en/geolocation_editor/geoeditor_coordinates.html#the-correlator Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #7 from Stefan Hoffmeister --- Created attachment 164618 --> https://bugs.kde.org/attachment.cgi?id=164618&action=edit X11 5.27 left-extend working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479295] feature request for digiKam's geo tagging
https://bugs.kde.org/show_bug.cgi?id=479295 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.3.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #8 from Stefan Hoffmeister --- Created attachment 164619 --> https://bugs.kde.org/attachment.cgi?id=164619&action=edit drm_info with legacy mode setting in broken state (left-extend not working) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 --- Comment #8 from Waqar Ahmed --- Most of the slowdown is because of accessibility. You can try to turn it off in your system. As per the docs https://doc.qt.io/qt-6/qaccessible.html: > In the Unix/X11 AT-SPI implementation, applications become accessible when > two conditions are met: >org.a11y.Status.IsEnabled DBus property is true >org.a11y.Status.ScreenReaderEnabled DBus property is true > An alternative to setting the DBus AT-SPI properties is to set the > QT_LINUX_ACCESSIBILITY_ALWAYS_ON environment variable. In master, we allow disabling it in settings and have tried to make accessibility faster in general. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 479292] ModemManager-QT Compiling from master source is failing
https://bugs.kde.org/show_bug.cgi?id=479292 --- Comment #1 from rac...@achellal.com --- related to change/commit: https://github.com/KDE/modemmanager-qt/commit/32e468ba67b1e361f1700022c649de081516853c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479275] Duplicate tags created with "\" as separator since upgrade to 8.3
https://bugs.kde.org/show_bug.cgi?id=479275 --- Comment #5 from Maik Qualmann --- You can continue to do this. Only the images with face metadata saved with a slash require the names to be re-entered. The fact that the people's names still appear in a hierarchy is ensured by standard tags. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479293 --- Comment #9 from Stefan Hoffmeister --- Created attachment 164620 --> https://bugs.kde.org/attachment.cgi?id=164620&action=edit Left 6.0 Wayland (broken) <-> Right X11 5.27 (working) Attached a screenshot which shows the material difference(s) between the working X11 setup on Plasma 5.27 and the equivalent non-working Wayland setup on Plasma 6 b2+. Fundamentally, * on X11 (right side), there is one backing framebuffer with size 6400x2160 covering both active planes (with offsetting via the SRC_X property) * on Wayland (left side), there are two distinct framebuffers, one for each plane, each of the "right size", and each at SRC_X == 0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479297] New: Add center lines to composition guides
https://bugs.kde.org/show_bug.cgi?id=479297 Bug ID: 479297 Summary: Add center lines to composition guides Classification: Applications Product: digikam Version: 8.2.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Plugin-Editor-Crop Assignee: digikam-bugs-n...@kde.org Reporter: lucana...@hotmail.fr Target Milestone: --- SUMMARY In the "Aspect Ratio Crop" tool of the editor, there are several "compositional guides" (golden mean, thirds, etc.) However, there is no compositional guide with "center lines". These are lines which divide the picture in 4 equal rectangles. It is very useful for cropping symmetrical pictures (to check if the symmetry line is really in the middle of the picture or not). You can see them in Gimp or Darktable. It would be nice to add "Center lines" in Digikam (or whatever other compositional guides which include center lines : Darktable have "Grid", "Metering" and "Perspective" which include center lines). Thanks you -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 479108] Zoom dropdown list in toolbar not working
https://bugs.kde.org/show_bug.cgi?id=479108 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/897 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479148] Startup stuck at Loading tools
https://bugs.kde.org/show_bug.cgi?id=479148 Peter changed: What|Removed |Added CC||benedekppe...@gmail.com --- Comment #21 from Peter --- (In reply to caulier.gilles from comment #20) > Voilà. > > The new 8.3.0 pre-release Windows Installer based on Mesa, Qt 6.6.1, and > last KF6 frameworks are online at usual place: > > https://files.kde.org/digikam/ > > Please install as well and report if the problem still reproducible (or any > others). > > Best regards > > Gilles Caulier I tested digiKam-8.3.0-20240102T090012-Win64.exe version on old computer, and I can reproduce this fault. Graphics: Intel(R) G41 Express Chipset (Microsoft Corporation - WDDM 1.1) The digiKam 8.3 does not start (in the same place the digiKam 8.2 start within 20 seconds). The program did not start, I stopped loading after 3 minutes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479148] Startup stuck at Loading tools
https://bugs.kde.org/show_bug.cgi?id=479148 --- Comment #22 from Peter --- Created attachment 164621 --> https://bugs.kde.org/attachment.cgi?id=164621&action=edit digiKam 8.3 not start on old computer -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 479110] Text-to-speech is not working
https://bugs.kde.org/show_bug.cgi?id=479110 Sune Vuorela changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@pusling.com --- Comment #1 from Sune Vuorela --- Thank you for your report. Unfortunately, I cannot reproduce. I just - like in my kf5 setup - drew a square and clicked 'Speak text' from context menu, and in both cases I got the same 'machine voice' speaking the exact same words. (Note; I have only tested with speech dispatcher, and just a single pdf document) I think this might be a setup issue in your end; either by yourself or by your distribution. Do you have the package speech-dispatcher installed ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 471018] Terrible browsing performance with mounted remote FS on links with high latency
https://bugs.kde.org/show_bug.cgi?id=471018 Pedro V changed: What|Removed |Added Component|general |general Status|REPORTED|CONFIRMED Assignee|dolphin-bugs-n...@kde.org |kio-bugs-n...@kde.org Product|dolphin |frameworks-kio Keywords|usability |efficiency, reproducible CC||kdelibs-b...@kde.org, ||voidpointertonull+bugskdeor ||g...@gmail.com Ever confirmed|0 |1 Version|22.12.3 |5.110.0 --- Comment #1 from Pedro V --- I'm not sure if the issue I have is exactly the same, but given that the symptom is familiar, figured I'd do some digging. I tend to use Krusader with sftp which is a better target to reproduce such troubles anyway given that it doesn't even require mounting. Found `sftp://testhost/usr/share/man/man1/` to be a good test target on an Ubuntu host with high latency. Running `strace -p $(pidof sftp-server)` on the target host shows the slow iteration with readlink and newfstatat alternating. What's interesting though is that it starts with a large batch of newfstatat, and apparently the slow iteration is only done over symbolic links. This seems to be confirmed by being able to check out directories consisting of many regular files rather quick. I think my issue lies in SFTPWorker::listDir -> SFTPWorker::createUDSEntry -> sftp_stat being called for each symlink back to back with synchronous I/O. Likely a more generic solution is desired though than dealing with this specifically, or additional framework features would be needed which would need to be implemented for each KIO slave individually. These approaches could help: - Asynchronous I/O support to allow KIO slaves to queue up all I/O work in one pass so there's only one latency hit per operation group - Progressive directory listing especially as the file list is already available early, and filling in the details later would be more desirable than waiting for everything even though the extra info may not be needed at all Likely no easy feat due to the need to work on slaves individually, but apparently sftp was getting some related goods already with Harald Sitter introducing some light coroutine usage and mentioning "sftp_aio is currently being worked on upstream" which is definitely an encouraging direction. Setting CONFIRMED as it's really a reproducible problem, and moving to frameworks-kio as this isn't really Dolphin specific, at least I don't think that's doing anything interesting to make the problem worse than what I can observe with Krusader. This isn't really a bug though as it's more of a design shortcoming, so recommending dropping importance to wishlist. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479252] Windows are teleported beyond viewport
https://bugs.kde.org/show_bug.cgi?id=479252 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Can you confirm if you have any kwin scripts enabled Also can you confirm if librewolf is a wayland application. The easiest test is to run xprop and hover over librewolf if the cursor changes to a + it's running via xwayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452240] wayland: "No titlebar and frame" rule doesn't force SSDs
https://bugs.kde.org/show_bug.cgi?id=452240 David Edmundson changed: What|Removed |Added Severity|normal |wishlist Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- This isn't as doable on wayland as it was under X11. The GTK clients will behave differently. We can force a deco, but it'd have a massive margin and then the window contents. Your best bet is to complain to upstream for not supporting the proper standards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479144] Refresh rate becomes unstable in Wayland using freesync at 4k 120hz only after using fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=479144 David Edmundson changed: What|Removed |Added CC||streng.alexan...@outlook.co ||m --- Comment #2 from David Edmundson --- *** Bug 479222 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479222] Variable Refresh rate (Freesync) doesn't work properly on fullscreen apps in wayland
https://bugs.kde.org/show_bug.cgi?id=479222 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 479144 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ksvg] [Bug 479159] Aurorae engine references "fill" element in svg if it have both "fill" and "style" element
https://bugs.kde.org/show_bug.cgi?id=479159 David Edmundson changed: What|Removed |Added Product|kwin|frameworks-ksvg Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Component|aurorae |General Version|5.27.8 |unspecified CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479077] Moving a window with the keyboard arrows causes unwanted actions inside the window
https://bugs.kde.org/show_bug.cgi?id=479077 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479036] "Invert (natural scrolling)" should be default Touchpad swipe scroll setting
https://bugs.kde.org/show_bug.cgi?id=479036 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479148] Startup stuck at Loading tools
https://bugs.kde.org/show_bug.cgi?id=479148 --- Comment #23 from Maik Qualmann --- Peter, can you download this file for testing, unzip it and copy it to the C:\Program Files\digiKam folder? https://download.qt.io/development_releases/prebuilt/llvmpipe/windows/opengl32sw-64-mesa_11_2_2-signed_sha256.7z Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479024] Double-click titlebar actions (such as maximize) not working.
https://bugs.kde.org/show_bug.cgi?id=479024 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- I cannot immediately reproduce this. Can you share your ~/.config/kwinrc file please. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478998] kwin_wayland crashes after activating search result in overview effect
https://bugs.kde.org/show_bug.cgi?id=478998 David Edmundson changed: What|Removed |Added Component|effects-overview|calculator Product|kwin|krunner CC||alexander.loh...@gmx.de, ||k...@davidedmundson.co.uk, ||natalie_clar...@yahoo.de Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479148] Startup stuck at Loading tools
https://bugs.kde.org/show_bug.cgi?id=479148 --- Comment #24 from Peter --- (In reply to Maik Qualmann from comment #23) > Peter, can you download this file for testing, unzip it and copy it to the > C:\Program Files\digiKam folder? > > https://download.qt.io/development_releases/prebuilt/llvmpipe/windows/ > opengl32sw-64-mesa_11_2_2-signed_sha256.7z > > Maik Yes! digiKam has now started (and fast)! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478333] Random stutters while gaming on Wayland session.
https://bugs.kde.org/show_bug.cgi?id=478333 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- Performance is something that we are constantly improving. There isn't anything unique or useful information in this ticket that makes this actionable as an open ticket. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479148] Startup stuck at Loading tools
https://bugs.kde.org/show_bug.cgi?id=479148 --- Comment #25 from Peter --- Created attachment 164622 --> https://bugs.kde.org/attachment.cgi?id=164622&action=edit Log with opengl32sw -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479298] New: Pinning apps or reodering icons doesn't persist between boots
https://bugs.kde.org/show_bug.cgi?id=479298 Bug ID: 479298 Summary: Pinning apps or reodering icons doesn't persist between boots Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: m...@fireburn.co.uk CC: qydwhotm...@gmail.com Target Milestone: 1.0 When I add applications from Kicker via "Pin to Task Manager", or reorder the icons on the Task Manager, after a reboot thing go back to the default -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 479262] Directory exists but didn't pass the security checks, can't use it
https://bugs.kde.org/show_bug.cgi?id=479262 Pedro V changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||voidpointertonull+bugskdeor ||g...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Pedro V --- Those paths don't exactly look healthy, there's a need for quite a bit more context here: - What's the full path of the file you attempted to trash? - What's the mount point that file resides on? - Is your $HOME on a different mount point? If I interpret the problem well, then those extra zero bytes will lead to the path being just "/" which of course really shouldn't be used for trash purposes, but where are the garbage bytes coming from? Is KMountPoint::currentMountPoints getting an unexpected null byte somewhere and is Qt turning that into 2 bytes of zero due to using the horrible UTF-16 mess? Alternatively it could come from Solid::Device::listFromQuery, but that's in case of scanning for trash directories, and without more info I'll assume that the error was encountered when attempting to use the trash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes
https://bugs.kde.org/show_bug.cgi?id=395023 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479148] Startup stuck at Loading tools
https://bugs.kde.org/show_bug.cgi?id=479148 --- Comment #26 from Maik Qualmann --- @Gilles, compiling Mesa is not necessary for the bundle, or there is an option to create the software variant. We only need the software renderer if system OpenGL is not available. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 477902] Breeze themed cursor changes to a generic one when hovering over Qt5 apps, and also some other apps.
https://bugs.kde.org/show_bug.cgi?id=477902 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479059] Floating moves to the wrong position when in contact with a window
https://bugs.kde.org/show_bug.cgi?id=479059 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478087] Poor ranking of search results
https://bugs.kde.org/show_bug.cgi?id=478087 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478442] When window opens in maximized state, de-maximizing it doesn't return it to its pre-maximized geometry
https://bugs.kde.org/show_bug.cgi?id=478442 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477199] KWin doesn't redraw the screen after a fullscreened app closes in some cases
https://bugs.kde.org/show_bug.cgi?id=477199 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477431] Slightly jumpy scrolling when scrolling through sidebar by slowly dragging the scroll handle
https://bugs.kde.org/show_bug.cgi?id=477431 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478080] Rounded top window corners in XWayland-using apps sometimes display a sharp unmasked pixel in the corner
https://bugs.kde.org/show_bug.cgi?id=478080 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478680] Automatic VRR and Tearing stop working once a WINE window is displayed.
https://bugs.kde.org/show_bug.cgi?id=478680 Connor Jenzsch changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Connor Jenzsch --- (In reply to Connor Jenzsch from comment #2) > (In reply to Zamundaaa from comment #1) > > Please check if there's any weird X11 windows from Wine on your system. You > > can do that in the kwin debug console, which you can open with krunner. > > Nope, nothing. > > The issue also persists after all WINE processes have closed. > > I should probably mention that this wasn't the case on the same system with > Plasma 5. On Plasma 5 both automatic VRR and Tearing have worked flawlessly > both with WINE and native software. Status updated to REPORTED. Forgot to do it earlier, sorry! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477986] Visual glitch when resizing Plasma popups
https://bugs.kde.org/show_bug.cgi?id=477986 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 479262] Directory exists but didn't pass the security checks, can't use it
https://bugs.kde.org/show_bug.cgi?id=479262 Henning changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Henning --- Using an OSTree filesystem, so all files are mounted in /var/home. The system uses BTRFS nvme0n1p3 259:30 929,9G 0 part └─luks-abcd-xyz1-2345 253:00 929,9G 0 crypt /var/home /var /sysroot/ostree/deploy/fedora/var /usr /etc / /sysroot I didnt delete any file actively I think, but if then it was somewhere in /var/home -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479253] Ctrl+F focuses on search field but no input works
https://bugs.kde.org/show_bug.cgi?id=479253 Henning changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #2 from Henning --- hm okay, so my distro seems to be pretty outdated for a testing ground. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479256] crash when taking rectangular screenshot
https://bugs.kde.org/show_bug.cgi?id=479256 Henning changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Henning --- I dont know. I just took a rectangle screenshot launched from the small first window and the rectangle selection crashed. the screen had the rectange selection and all as it should, and it didnt go away until I manually killed spectacle. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479274] Assign rectangle Area or overview to "Print"
https://bugs.kde.org/show_bug.cgi?id=479274 Henning changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Henning --- No with overview I mean one of the too many spectacle "main windows" where you can decide to take a screenshot. I guess this would be better as in the future it may also allow to record. The rectangle selection is just one type of screenshot, so it would be like flameshot but not make much other functionality (screenshot window, all, etc) available. So with "overview" I simply mean launching whats currently done with the desktop entry, this small first window. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479274] Assign rectangle Area or overview to "Print"
https://bugs.kde.org/show_bug.cgi?id=479274 --- Comment #3 from Henning --- I did not change any settings, so for me "Print" is simply not doing anything. So this would be a FR to change to the overview but as there is nothing currently it is a bug ;D -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478958] Touchscreen: Long pressing on the desktop doesn't enter the edit mode
https://bugs.kde.org/show_bug.cgi?id=478958 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3738 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479299] New: modemmanager as optional dependency
https://bugs.kde.org/show_bug.cgi?id=479299 Bug ID: 479299 Summary: modemmanager as optional dependency Classification: Plasma Product: plasma-nm Version: 5.27.10 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pr...@ww.ee Target Milestone: --- SUMMARY I wish that `modemmanager` became optional dependency instead of being currently hard dependency. My Desktop computer has absolutely 0 reason to have mobile network connection packages installed in any shape or form. Sadly KDE insists that I have all of them installed, as basically bloatware 🤦🏻 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.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #5 from n...@nils-griebner.de --- (In reply to nils from comment #4) > (In reply to Jack from comment #3) > > I suspect that either you will need to explicitly convert your database > > from version 3 to version 4, or else we need to figure out how to get > > KMyMoney to invoke sqlcipher with the compatability setting. I don't use > > sqlcipher, so I'm only guessing, but is there a config file where you can > > specify to always use compatability mode? > > I took that from https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283 I got mymoney running again by: 1. Let mymoney create a new encrypted sqlite db 2. Follow step 3 (custom export migration) from https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452240] wayland: "No titlebar and frame" rule doesn't force SSDs
https://bugs.kde.org/show_bug.cgi?id=452240
--- Comment #2 from `{third: "Beedell", first: "Roke"}`{.JSON5}
---
Created attachment 164623
--> https://bugs.kde.org/attachment.cgi?id=164623&action=edit
Response to #c1.
(In reply to David Edmundson from comment #1)
> This isn't as doable on wayland as it was under X11. The GTK clients will
> behave differently. We can force a deco, but it'd have a massive margin and
> then the window contents.
>
> Your best bet is to complain to upstream for not supporting the proper
> standards.
Like this?
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 470563] konsole bell sound blows up memory usage of pipewire-pulse
https://bugs.kde.org/show_bug.cgi?id=470563 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 479300] New: Latte Dock crashes when using the systray
https://bugs.kde.org/show_bug.cgi?id=479300 Bug ID: 479300 Summary: Latte Dock crashes when using the systray Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: ro...@protonmail.com Target Milestone: --- Created attachment 164624 --> https://bugs.kde.org/attachment.cgi?id=164624&action=edit crash backtrace SUMMARY Backtrace available as attachment. STEPS TO REPRODUCE 1. Set latte dock to auto hide when a window covers it 2. Open an application that covers the entire screen so that latte dock hides 3. Toggle items in the systray very quickly (within a couple of seconds) multiple times OBSERVED RESULT Latte dock crashes EXPECTED RESULT Latte dock should not crash SOFTWARE/OS VERSIONS Windows: NA macOS: NA Linux/KDE Plasma: Arch Linux 6.6.8-arch1-1 (available in About System) KDE Plasma Version: KDE Plasma 5.27.10 (Wayland) KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Issue seen only on my AMD system. Doesn't seem to be an issue on my Intel system. -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 432767] Add inspecting of web pages when using QWebEngine
https://bugs.kde.org/show_bug.cgi?id=432767 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/offi ||ce/alkimia/-/commit/13edb81 ||8da5f964fc85bb913bd734a985f ||27ff29 Status|REPORTED|RESOLVED Version Fixed In||8.1.73 --- Comment #1 from Ralf Habacker --- Git commit 13edb818da5f964fc85bb913bd734a985f27ff29 by Ralf Habacker. Committed on 02/01/2024 at 15:29. Pushed by habacker into branch 'master'. Add inspecting of web pages when using QWebEngine QWebEngine depends on setting an environment variable for the development tool, which is currently hard coded in the implementation file for the class AlkWebPage. FIXED-IN: 8.1.73 M +5-0src/alkonlinequoteswidget.cpp M +62 -4src/alkwebpage.cpp M +2-2src/alkwebpage.h https://invent.kde.org/office/alkimia/-/commit/13edb818da5f964fc85bb913bd734a985f27ff29 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479191] vgdb is blocked after several tries
https://bugs.kde.org/show_bug.cgi?id=479191 --- Comment #3 from Fred M --- Created attachment 164625 --> https://bugs.kde.org/attachment.cgi?id=164625&action=edit valgrind -d -d -d logs Hello, [What is the reason for this in your case ?] For no reason, I could retry without it if needed. [chipset] Arm [linux] kernel 4.9 glibc 2.24 I re-run, (Please find the log in attachment ) valgrind -v -v -v -d -d -d --tool=massif --time-unit=ms --vgdb=yes --trace-children=yes --threshold=0.01 --vgdb-error=0 my_progs > /tmp /valgrind_log.txt 2>&1 // vgdb ok : vgdb -d detailed_snapshot /tmp/test 15:27:55.768100 searching pid in directory /tmp/ format /tmp/vgdb-pipe-from-vgdb-to- 15:27:55.768392 check_trial 0 15:27:55.768578 vgdb: using /tmp/vgdb-pipe-from-vgdb-to-5313-by-root-on-??? /tmp/vgdb-pipe-to-vgdb-from-5313-by-root-on-??? /tmp/vgdb-pipe-shared-mem-vgdb-5313-by-root-on-??? 15:27:55.768756 opening /tmp/vgdb-pipe-from-vgdb-to-5313-by-root-on-??? write to pid 15:27:55.768809 opened /tmp/vgdb-pipe-from-vgdb-to-5313-by-root-on-??? write to pid fd 4 15:27:55.768872 opening /tmp/vgdb-pipe-to-vgdb-from-5313-by-root-on-??? read cmd result from pid 15:27:55.769010 opened /tmp/vgdb-pipe-to-vgdb-from-5313-by-root-on-??? read cmd result from pid fd 5 sending command detailed_snapshot /tmp/test to pid 5313 --5313-- XT_massif_print detailed --5313-- iteration 1 --5313-- XT_print_massif ms_ec n_ec 1 --5313-- XT_massif_print producing depth 0 groups --5313-- depth 0 n_groups 1 n_insig 0 --5313-- XT_massif_print outputting 1 depth 0 groups --5313-- depth 1 n_groups 0 n_insig 0 15:27:55.770032 OK packet rcvd 15:27:55.770083 nr received signals: sigint 0 sigterm 0 sighup 0 sigpipe 0 15:27:55.770118 joining with invoke_gdbserver_in_valgrind_thread /root # /root # ls -ltr /tmp/ [...] prw---1 root root 0 Jan 2 15:27 vgdb-pipe-to-vgdb-from-5313-by-root-on-??? -rw---1 root root36 Jan 2 15:27 vgdb-pipe-shared-mem-vgdb-5313-by-root-on-??? prw---1 root root 0 Jan 2 15:27 vgdb-pipe-from-vgdb-to-5313-by-root-on-??? -rw-r--r--1 root root 760 Jan 2 15:27 test -rw-r--r--1 root root 1967966 Jan 2 15:28 valgrind_log.txt // vgdb ko : /root # vgdb -d detailed_snapshot /tmp/test 15:28:14.104760 searching pid in directory /tmp/ format /tmp/vgdb-pipe-from-vgdb-to- 15:28:14.105576 check_trial 0 15:28:14.105888 vgdb: using /tmp/vgdb-pipe-from-vgdb-to-5313-by-root-on-??? /tmp/vgdb-pipe-to-vgdb-from-5313-by-root-on-??? /tmp/vgdb-pipe-shared-mem-vgdb-5313-by-root-on-??? 15:28:14.106192 opening /tmp/vgdb-pipe-from-vgdb-to-5313-by-root-on-??? write to pid 15:28:14.106279 opened /tmp/vgdb-pipe-from-vgdb-to-5313-by-root-on-??? write to pid fd 4 15:28:14.106459 opening /tmp/vgdb-pipe-to-vgdb-from-5313-by-root-on-??? read cmd result from pid 15:28:14.206649 attach to 'main' pid 5313 15:28:14.206929 attach main pid PTRACE_ATTACH pid 5313 15:28:14.206979 waitstopped attach main pid before waitpid signal_expected 19 15:28:14.212162 after waitpid pid 5313 p 5313 status 0x137f WIFSTOPPED 19 15:28:14.212292 examining thread entries from tid 1 to tid 499 15:28:14.212362 found tid 1 status VgTs_WaitSys lwpid 5313 15:28:14.212396 found tid 2 status VgTs_WaitSys lwpid 5425 15:28:14.212418 attach_thread PTRACE_ATTACH pid 5425 15:28:14.212453 waitstopped attach_thread before waitpid signal_expected 19 15:28:14.212574 after waitpid pid 5425 p 5425 status 0x137f WIFSTOPPED 19 15:28:14.212616 found tid 3 status VgTs_WaitSys lwpid 5499 15:28:14.212638 attach_thread PTRACE_ATTACH pid 5499 15:28:14.212665 waitstopped attach_thread before waitpid signal_expected 19 15:28:14.212742 after waitpid pid 5499 p 5499 status 0x137f WIFSTOPPED 19 15:28:14.212781 found tid 4 status VgTs_WaitSys lwpid 5431 15:28:14.212803 attach_thread PTRACE_ATTACH pid 5431 15:28:14.212828 waitstopped attach_thread before waitpid signal_expected 19 15:28:14.226020 after waitpid pid 5431 p 5431 status 0x137f WIFSTOPPED 19 15:28:14.226214 found tid 5 status VgTs_WaitSys lwpid 5438 15:28:14.226241 attach_thread PTRACE_ATTACH pid 5438 15:28:14.226282 waitstopped attach_thread before waitpid signal_expected 19 15:28:14.230184 after waitpid pid 5438 p 5438 status 0x137f WIFSTOPPED 19 15:28:14.234720 getregs regs_bsz 72 15:28:14.234895 PTRACE_GETREGSET defined, not used (yet?) by vgdb 15:28:14.234993 getregs PTRACE_GETREGS 15:28:14.235089 detected a working PTRACE_GETREGS 15:28:14.235182 setregs regs_bsz 72 15:28:14.235275 setregs PTRACE_SETREGS 15:28:14.235378 PTRACE_CONT to invoke 15:28:14.236057 waitstopped waitpid status after PTRACE_CONT to invoke before waitpid signal_expected 19 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479301] New: Cannot open wallpaper config
https://bugs.kde.org/show_bug.cgi?id=479301 Bug ID: 479301 Summary: Cannot open wallpaper config Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nicolas.fe...@gmx.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 STEPS TO REPRODUCE 1. Right-click on desktop 2. Configure Desktop and Wallpaper OBSERVED RESULT Wallpaper config is empty EXPECTED RESULT Wallpaper config SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 6.7 file:///home/nico/kde/usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationContainmentAppearance.qml:117:17: Type NewStuff.Button unavailable qrc:/qt/qml/org/kde/newstuff/Button.qml:102:5: Type NewStuff.Dialog unavailable qrc:/qt/qml/org/kde/newstuff/Dialog.qml:101:5: Type NewStuff.DialogContent unavailable qrc:/qt/qml/org/kde/newstuff/DialogContent.qml:62:28: Type NewStuff.Page unavailable qrc:/qt/qml/org/kde/newstuff/Page.qml:532:9: Type EntryGridDelegates.ThumbDelegate unavailable qrc:/qt/qml/org/kde/newstuff/private/entrygriddelegates/ThumbDelegate.qml:34:9: Cannot assign object to list property "actions" This is presumably a Qt 6.7 regression since it doesn't happen with 6.6.1. Needs investigation though -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479302] New: Several things crash in QWaylandWindow::createDecoration
https://bugs.kde.org/show_bug.cgi?id=479302 Bug ID: 479302 Summary: Several things crash in QWaylandWindow::createDecoration Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nicolas.fe...@gmx.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 See linked bugreports Potentially related to https://bugreports.qt.io/browse/QTBUG-105703 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 479210] KRunner random crash
https://bugs.kde.org/show_bug.cgi?id=479210 Nicolas Fella changed: What|Removed |Added Blocks||479302 CC||nicolas.fe...@gmx.de Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479302 [Bug 479302] Several things crash in QWaylandWindow::createDecoration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479302] Several things crash in QWaylandWindow::createDecoration
https://bugs.kde.org/show_bug.cgi?id=479302 Nicolas Fella changed: What|Removed |Added Depends on||479210 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479210 [Bug 479210] KRunner random crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479302] Several things crash in QWaylandWindow::createDecoration
https://bugs.kde.org/show_bug.cgi?id=479302 Nicolas Fella changed: What|Removed |Added Depends on||479057 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479057 [Bug 479057] plasmashell crash when clearing history in the clipboard applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479057] plasmashell crash when clearing history in the clipboard applet
https://bugs.kde.org/show_bug.cgi?id=479057 Nicolas Fella changed: What|Removed |Added Blocks||479302 CC||nicolas.fe...@gmx.de Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479302 [Bug 479302] Several things crash in QWaylandWindow::createDecoration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479302] Several things crash in QWaylandWindow::createDecoration
https://bugs.kde.org/show_bug.cgi?id=479302 Nicolas Fella changed: What|Removed |Added Depends on||478086 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=478086 [Bug 478086] plasmashell crashed sometimes in QtWaylandClient::QWaylandWindow::createDecoration when hovering over task manager icons -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 478086] plasmashell crashed sometimes in QtWaylandClient::QWaylandWindow::createDecoration when hovering over task manager icons
https://bugs.kde.org/show_bug.cgi?id=478086 Nicolas Fella changed: What|Removed |Added Blocks||479302 CC||nicolas.fe...@gmx.de Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479302 [Bug 479302] Several things crash in QWaylandWindow::createDecoration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476952] Plasma crashed in QtWaylandClient::QWaylandWindow::createDecoration() after trying to unmount an device via Disks & Devices applet
https://bugs.kde.org/show_bug.cgi?id=476952 Nicolas Fella changed: What|Removed |Added Blocks||479302 CC||nicolas.fe...@gmx.de Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479302 [Bug 479302] Several things crash in QWaylandWindow::createDecoration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479302] Several things crash in QWaylandWindow::createDecoration
https://bugs.kde.org/show_bug.cgi?id=479302 Nicolas Fella changed: What|Removed |Added Depends on||476952 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=476952 [Bug 476952] Plasma crashed in QtWaylandClient::QWaylandWindow::createDecoration() after trying to unmount an device via Disks & Devices applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472748] plasmashell crashed when task tooltip is dismissed before thumbnails are available
https://bugs.kde.org/show_bug.cgi?id=472748 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Blocks||479302 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=479302 [Bug 479302] Several things crash in QWaylandWindow::createDecoration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479302] Several things crash in QWaylandWindow::createDecoration
https://bugs.kde.org/show_bug.cgi?id=479302 Nicolas Fella changed: What|Removed |Added Depends on||472748 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=472748 [Bug 472748] plasmashell crashed when task tooltip is dismissed before thumbnails are available -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478958] Touchscreen: Long pressing on the desktop doesn't enter the edit mode
https://bugs.kde.org/show_bug.cgi?id=478958 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||6.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||b8bf8448cca0560ca4c4230e251 ||713d50c0af4a3 --- Comment #2 from Fushan Wen --- Git commit b8bf8448cca0560ca4c4230e251713d50c0af4a3 by Fushan Wen. Committed on 02/01/2024 at 15:36. Pushed by fusionfuture into branch 'master'. containments/desktop: set GridView as eventManagerToFilter The GridView contains mouse events and can be forwarded to AppletsLayout. FIXED-IN: 6.0 M +1-1containments/desktop/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/b8bf8448cca0560ca4c4230e251713d50c0af4a3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477220] "More" button in the desktop toolbox does not open the context menu
https://bugs.kde.org/show_bug.cgi?id=477220 --- Comment #4 from Fushan Wen --- Git commit 72ebd9a2857d052ef4cf36752ba58f8d06af1eea by Fushan Wen. Committed on 02/01/2024 at 15:52. Pushed by fusionfuture into branch 'master'. appiumtests/desktoptest: test long press to enter edit mode on desktop M +53 -4appiumtests/desktoptest.py A +---appiumtests/resources/bug478958_new_file_menu_item_icon.png https://invent.kde.org/plasma/plasma-desktop/-/commit/72ebd9a2857d052ef4cf36752ba58f8d06af1eea -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478087] Poor ranking of search results
https://bugs.kde.org/show_bug.cgi?id=478087 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3739 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 479303] New: Energy information graph shows 2 lines
https://bugs.kde.org/show_bug.cgi?id=479303 Bug ID: 479303 Summary: Energy information graph shows 2 lines Classification: Applications Product: kinfocenter Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ro...@protonmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 164626 --> https://bugs.kde.org/attachment.cgi?id=164626&action=edit kinfocenter energy module screenshot SUMMARY The energy information module shows 2 lines in the battery percentage as well as the energy consumption timeline graphs. One of the lines is the actual history while the other is just a straight horizontal line that starts from the very first data point for some reason. STEPS TO REPRODUCE NA. OBSERVED RESULT 2 Lines are visible in the graph EXPECTED RESULT Only 1 line should be visible in the graph joining the actual data points SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux 6.6.8-arch1-1 (available in About System) KDE Plasma Version: 5.27.10 (Wayland) KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Screenshot available in attachments -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 479303] Energy information graph shows 2 lines
https://bugs.kde.org/show_bug.cgi?id=479303 --- Comment #1 from Rohit --- Created attachment 164627 --> https://bugs.kde.org/attachment.cgi?id=164627&action=edit kinfocenter energy consumption graph -- You are receiving this mail because: You are watching all bug changes.
