[kdepim] [Bug 444985] Wrong ports in akonadi_pop3_resource.pot

[Laurent Montel]

https://bugs.kde.org/show_bug.cgi?id=444985

Laurent Montel  changed:

   What|Removed |Added

   Version Fixed In||5.19.0
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/pim/
   ||kdepim-runtime/commit/328ba
   ||ed4b99a2ca257783a01a0939fe7
   ||79541e1c

--- Comment #1 from Laurent Montel  ---
Git commit 328baed4b99a2ca257783a01a0939fe779541e1c by Laurent Montel.
Committed on 05/11/2021 at 05:47.
Pushed by mlaurent into branch 'master'.

Fix 444985: Wrong ports in akonadi_pop3_resource.pot
FIXED-IN: 5.19.0

M  +4-4resources/pop3/popsettings.ui

https://invent.kde.org/pim/kdepim-runtime/commit/328baed4b99a2ca257783a01a0939fe779541e1c

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kxmlgui] [Bug 444995] [Wayland] Non-Kirigami KDE apps stuck unmaximized or maximized

[Samuel Reddy]

https://bugs.kde.org/show_bug.cgi?id=444995

Samuel Reddy  changed:

   What|Removed |Added

   Keywords||usability, wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kxmlgui] [Bug 444995] New: [Wayland] Non-Kirigami KDE apps stuck unmaximized or maximized

[Samuel Reddy]

https://bugs.kde.org/show_bug.cgi?id=444995

Bug ID: 444995
   Summary: [Wayland] Non-Kirigami KDE apps stuck unmaximized or
maximized
   Product: frameworks-kxmlgui
   Version: 5.87.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: samuelsumukhre...@gmail.com
  Target Milestone: ---

Created attachment 143226
  --> https://bugs.kde.org/attachment.cgi?id=143226=edit
Video of the bug

SUMMARY
If a KDE app starts up maximized, then you unmaximize the window, then you try
to maximize the window, it won't let you maximize it( or if you unmaximize,
maximize, then try to unmaximize) This does not apply to kirigami apps like
discover.

STEPS TO REPRODUCE
1. Open an KDE app(like gwenview) that starts maximized(not kirigami apps
though)
2. Unmaximize the KDE app
3. Try to maximize the KDE app
4. The KDE app will not maximize
5. If you can maximize the app, try unmaximizing it
6. Does not unmaximize

OBSERVED RESULT
The KDE app refuses to maximize or unmaximize

EXPECTED RESULT
They maximize and unmaximize normally 

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: Wayland
Processors: 8 × AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx
Memory: 5.7 GiB of RAM
Graphics Processor: AMD Radeon™ Vega 8 Graphics

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 444973] General appearance -> skin doesn't change to "classic" if it is selected

[D. Debnath]

https://bugs.kde.org/show_bug.cgi?id=444973

D. Debnath  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 444973] General appearance -> skin doesn't change to "classic" if it is selected

[D. Debnath]

https://bugs.kde.org/show_bug.cgi?id=444973

D. Debnath  changed:

   What|Removed |Added

 CC||d_debn...@outlook.com

--- Comment #1 from D. Debnath  ---
The Dusk and Classic themes of the past have been replaced by the new one. So
meaning of "Classic" has changed.

Currently, the way it is set up is:

Classic theme: Monospace font in comments section
Dusk theme: Sans Serif font in comments section

Everything else is same between the two themes. The old theme is no longer an
available option.

We've to work with the constraint of just changing the CSS without touching
anything else, so this is just a technical limitation we have to work with.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 442980] Plasma wayland session does not re-detect external monitor

[Tim]

https://bugs.kde.org/show_bug.cgi?id=442980

--- Comment #20 from Tim  ---
(In reply to Méven Car from comment #18)
> Git commit 6d518e8ffe527d1e62d2c1d9949a30fc52429c35 by Méven Car, on behalf
> of Méven Car.
> Committed on 20/10/2021 at 15:33.
> Pushed by meven into branch 'master'.
> 
> DRM Backend: Add some log trace for DrmConnector
> 
> M  +2-0src/plugins/platforms/drm/drm_gpu.cpp
> M  +25   -1src/plugins/platforms/drm/drm_object_connector.cpp
> M  +4-0src/plugins/platforms/drm/drm_object_connector.h
> 
> https://invent.kde.org/plasma/kwin/commit/
> 6d518e8ffe527d1e62d2c1d9949a30fc52429c35

Have these changes landed?

I've just re-enabled the Arch kde-unstable repo and there weren't any updates,
perhaps they're already in the main Arch repo.

Anyway, output from grep kwin_wayland_drm
~/.local/share/sddm/wayland-session.log for my current setup is below.

I've also discovered if I plug a USB-A hub into the same USB-C dongle while
it's being used for video, it kills the video output similarly to unplugging
and replugging the dongle. A full reboot is required to recover video after
this has happened. I've included the additional output of grep kwin_wayland_drm
~/.local/share/sddm/wayland-session.log following plugging the hub in.

It's  worth noting that this hub is usually powered, but I don't have the power
adaptor with me right now, so this may not occur when powered.

Happy to do any further testing.

 New session, plugging in USB-C dongle / monitor for first time
grep kwin_wayland_drm ~/.local/share/sddm/wayland-session.log
kwin_wayland_drm: drmModeAddFB2WithModifiers is supported on GPU
"/dev/dri/card0"
kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card0"
kwin_wayland_drm: Number of planes on GPU "/dev/dri/card0" : 32
kwin_wayland_drm: Crtc 98 has properties "MODE_ID"=363, "ACTIVE"=1,
"VRR_ENABLED"=0, "GAMMA_LUT"=362
kwin_wayland_drm: Crtc 167 has properties "MODE_ID"=0, "ACTIVE"=0,
"VRR_ENABLED"=0, "GAMMA_LUT"=0
kwin_wayland_drm: Crtc 236 has properties "MODE_ID"=0, "ACTIVE"=0,
"VRR_ENABLED"=0, "GAMMA_LUT"=0
kwin_wayland_drm: Crtc 305 has properties "MODE_ID"=0, "ACTIVE"=0,
"VRR_ENABLED"=0, "GAMMA_LUT"=0
kwin_wayland_drm: EGL buffer configs count: 100
kwin_wayland_drm: Connector 308 has properties "CRTC_ID"=98, "non-desktop"=0,
"DPMS"=0, "EDID"=310, "overscan"not found, "vrr_capable"=0, "underscan" not
found, "underscan vborder" not found, "underscan hborder" not found, "Broadcast
RGB"="Automatic"
kwin_wayland_drm: New output on GPU "/dev/dri/card0": "eDP-1-unknown"
kwin_wayland_drm: Reading output configuration for 
KWin::DrmOutput(0x55c21e83ebf0, name="eDP-1", geometry=QRect(0,0 1920x1080),
scale=1)
kwin_wayland_drm: Received change event for monitored drm device
"/dev/dri/card0"
kwin_wayland_drm: Connector 347 has properties "CRTC_ID"=0, "non-desktop"=0,
"DPMS"=3, "EDID"=362, "overscan" not found, "vrr_capable"=0, "underscan" not
found, "underscan vborder" not found, "underscan hborder" not found, "Broadcast
RGB"="Automatic"
kwin_wayland_drm: New output on GPU "/dev/dri/card0": "DELL S2721QS/5ML3M43"
kwin_wayland_drm: Reading output configuration for 
KWin::DrmOutput(0x55c21e83ebf0, name="eDP-1", geometry=QRect(0,0 1920x1080),
scale=1)
kwin_wayland_drm: Reading output configuration for 
KWin::DrmOutput(0x55c21f19f530, name="DP-3", geometry=QRect(0,0 3840x2160),
scale=1)

--- External display not working after USB-A hub plugged into 
kwin_wayland_drm: Received change event for monitored drm device
"/dev/dri/card0"
kwin_wayland_drm: Reading output configuration for 
KWin::DrmOutput(0x55c21e83ebf0, name="eDP-1", geometry=QRect(0,648 1920x1080),
scale=1)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 426260] NVIDIA Optimus: Plasma boots a black desktop on multi-screen setup; wallpaper returns after changing display setup

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=426260

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #15 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 351529] Multimonitor setup scrambled sometimes

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=351529

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 444140] Kwin_wayland segmentation fault and restarts the whole session

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=444140

--- Comment #8 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 443683] Assert and crash when overwriting a workspace

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=443683

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 443717] [workspace] Saving a new workspace doesn't appear in "Workspaces list", but in 'Windows layout" list.

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=443717

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 444994] Calculator giving me wrong answers (PEMDAS)

[Rui Guilherme]

https://bugs.kde.org/show_bug.cgi?id=444994

Rui Guilherme  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 444994] New: Calculator giving me wrong answers (PEMDAS)

[Rui Guilherme]

https://bugs.kde.org/show_bug.cgi?id=444994

Bug ID: 444994
   Summary: Calculator giving me wrong answers (PEMDAS)
   Product: krunner
   Version: 5.23.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: calculator
  Assignee: alexander.loh...@gmx.de
  Reporter: guilhermecunha@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
Krunner is not able to handle PEMDAS correctly. 

STEPS TO REPRODUCE
1. Open Krunner
2. type **6/158(154+5)-10 **

OBSERVED RESULT
-9,999761165512300

EXPECTED RESULT
-3.96202531646

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  5.23.2
KDE Plasma Version:  5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

I'm going to use a simple expression:
2/1(2+1)
(2/1)*(2+1)
2*(2+1)
2*3
Answers: 6 (Correct)

but Krunner try it:
2/1(2+1)
2/(1*3)
2/3
Answers: 0,6667 (Wrong)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 419085] kwin_x11 misbehavior and crash with existing workspaces

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=419085

--- Comment #2 from ryu.ketsu...@outlook.com ---
Doesn't occour anymore, thankfully.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 444084] ksreen should not output information as warning

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=444084

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #5 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/libkscreen/-/merge_requests/38

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly

[Damian C]

https://bugs.kde.org/show_bug.cgi?id=442089

--- Comment #9 from Damian C  ---
Experiencing the same issue.

Running korganizer within kontact.

The frequency of the issue has increased after getting the latest version of
the app: korganizer-21.08.3-1

When it does happen I get hundreds of pop ups and the system stops responding.
I can only close the app by switching to a tty (Ctrl + Alt + F2) and killing
it.
The massive amount of pop ups causes the k11 process to use 100% of CPU.
Perhaps I'm seeing more messages than most as my google calendar has got
subscriptions from a few other calendars from other people.

The very last time it happened today I was not interacting with korzganizer at
all, rather browsing the internet.
Also, the very last time it happened I had no choice but to issue sudo reboot
from the tty as the system would not come back from the freeze/stuck.

Since it happened twice today I have removed the calendar for now.

Operating System: Manjaro Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.16-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15,5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly

[Damian C]

https://bugs.kde.org/show_bug.cgi?id=442089

Damian C  changed:

   What|Removed |Added

Version|5.18.1  |GIT (master)
 CC||dcalv...@gmail.com
   Platform|Other   |Manjaro

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 444966] Request for Keyword Import in Database Capability

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=444966

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Request for Keyword Import  |Request for Keyword Import
   |Capability  |in Database Capability

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 444966] Request for Keyword Import Capability

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=444966

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|unspecified |7.4.0
 CC||caulier.gil...@gmail.com
   Severity|normal  |wishlist

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444803] Krita crashes (Segmentation Fault)

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=444803

--- Comment #5 from drewm...@protonmail.com ---
On another note, by running gdb I got more information about the bug:

[drew@DrewPC ~]$ gdb krita
GNU gdb (GDB) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krita...
(No debugging symbols found in krita)
(gdb) r
Starting program: /usr/bin/krita 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffee93c640 (LWP 2845)]
[New Thread 0x7fffe1d54640 (LWP 2846)]
[New Thread 0x7fffe1553640 (LWP 2847)]
[Thread 0x7fffe1553640 (LWP 2847) exited]
[Thread 0x7fffee93c640 (LWP 2845) exited]
[Thread 0x7fffe1d54640 (LWP 2846) exited]
[New Thread 0x7fffe1d54640 (LWP 2848)]
[New Thread 0x7fffee93c640 (LWP 2850)]
[New Thread 0x7fffe1553640 (LWP 2851)]
[Thread 0x7fffe1553640 (LWP 2851) exited]
[Thread 0x7fffe1d54640 (LWP 2848) exited]
[Thread 0x7fffee93c640 (LWP 2850) exited]
[New Thread 0x7fffee93c640 (LWP 2852)]
[New Thread 0x7fffe1d54640 (LWP 2853)]
[New Thread 0x7fffe1553640 (LWP 2854)]
[Thread 0x7fffe1553640 (LWP 2854) exited]
[Thread 0x7fffee93c640 (LWP 2852) exited]
[Thread 0x7fffe1d54640 (LWP 2853) exited]
[New Thread 0x7fffe1d54640 (LWP 2855)]
[New Thread 0x7fffee93c640 (LWP 2856)]
[New Thread 0x7fffe1553640 (LWP 2857)]
[New Thread 0x7fffdafd1640 (LWP 2858)]
Set style "breeze"
[New Thread 0x7fffda34b640 (LWP 2859)]
[Thread 0x7fffda34b640 (LWP 2859) exited]
Icon theme "elementary" not found.
Invalid profile :  "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors"
Invalid profile :  "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors"
Loading plugin "/usr/lib/kritaplugins/kritaseexprgenerator.so" failed,  "Cannot
load library /usr/lib/kritaplugins/kritaseexprgenerator.so: (libKSeExprUI.so.4:
cannot open shared object file: No such file or directory)"
[New Thread 0x7fffda34b640 (LWP 2860)]
[New Thread 0x7fffce5e3640 (LWP 2861)]
[New Thread 0x7fffcdde2640 (LWP 2862)]
[New Thread 0x7fffcd5e1640 (LWP 2863)]
[New Thread 0x7fffccde0640 (LWP 2864)]
[New Thread 0x7fffbbfff640 (LWP 2865)]
[New Thread 0x7fffbb7fe640 (LWP 2866)]
[New Thread 0x7fffbaffd640 (LWP 2867)]
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
QPngHandler: Failed to parse ICC profile
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
QPngHandler: Failed to parse ICC profile
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
QPngHandler: Failed to parse ICC profile
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
QPngHandler: Failed to parse ICC profile
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
QPngHandler: Failed to parse ICC profile
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
QPngHandler: Failed to parse ICC profile
[New Thread 0x7fffba7fc640 (LWP 2869)]
QObject::startTimer: Timers cannot have negative intervals
[New Thread 0x7fffb9ffb640 (LWP 2873)]
[New Thread 0x7fffb97fa640 (LWP 2874)]
[Thread 0x7fffb9ffb640 (LWP 2873) exited]
/usr/lib/krita-python-libs/krita added to PYTHONPATH
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
[New Thread 0x7fffb9ffb640 (LWP 2876)]
[New Thread 0x7fffa2742640 (LWP 2877)]
qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point
libpng error: bad adaptive filter value
QImage::scaled: Image is a null image
QImage::scaled: Image is a null image

Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x71ac2053 in QuaZip::isOpen() const () from
/usr/lib/libquazip1-qt5.so.1.0.0
(gdb) bt full
#0  0x71ac2053 in QuaZip::isOpen() const () from
/usr/lib/libquazip1-qt5.so.1.0.0
No symbol table info available.
#1  0x71acee6d in QuaZipFile::close() () from
/usr/lib/libquazip1-qt5.so.1.0.0
No symbol table info available.
#2  0x71acf0c9 in QuaZipFile::~QuaZipFile() () from
/usr/lib/libquazip1-qt5.so.1.0.0
No symbol table info available.
#3  0x71acf0da in QuaZipFile::~QuaZipFile() () from
/usr/lib/libquazip1-qt5.so.1.0.0
No symbol table info available.
#4  0x7340f5b5 in ?? () from /usr/lib/libkritastore.so.20
No symbol table info available.
#5  0x7340f659 in ?? () from /usr/lib/libkritastore.so.20
No symbol table info available.
#6  0x77007344 in 

[krita] [Bug 444803] Krita crashes (Segmentation Fault)

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=444803

drewm...@protonmail.com changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Status|RESOLVED|REOPENED

--- Comment #4 from drewm...@protonmail.com ---
(In reply to Halla Rempt from comment #3)
> You should remove the distro version of krita before running an appimage.

How would I do that exactly?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 444993] Incorrect name for BreezeDark ColorScheme in kdeglobals

[Seth]

https://bugs.kde.org/show_bug.cgi?id=444993

--- Comment #1 from Seth  ---
I've also noticed errors in reporting in other fields like [General] with the
same steps to reproduce. It seems the BreezeDark ColorScheme is correctly
reported in this field, but the name of the theme is still Breeze Light when it
should be Breeze Dark.

Example:
```
[General]
ColorScheme=BreezeDark
Name=Breeze Light
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 444993] New: Incorrect name for BreezeDark ColorScheme in kdeglobals

[Seth]

https://bugs.kde.org/show_bug.cgi?id=444993

Bug ID: 444993
   Summary: Incorrect name for BreezeDark ColorScheme in
kdeglobals
   Product: Breeze
   Version: 5.23.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Color scheme
  Assignee: plasma-b...@kde.org
  Reporter: getc...@tuta.io
  Target Milestone: ---

SUMMARY

When using the BreezeDark colorscheme, `~/.config/kdegloabls` reports KDE's
colorscheme to be BreezeLight

STEPS TO REPRODUCE
1. Go to Settings >Appearance > Global Theme
2. Select Breeze Dark
3. Read `~/.config/kdeglobals`

OBSERVED RESULT
```
[KDE]
ColorScheme=BreezeLight
LookAndFeelPackage=org.kde.breezedark.desktop
contrast=4
```

EXPECTED RESULT
```
[KDE]
ColorScheme=BreezeDark
LookAndFeelPackage=org.kde.breezedark.desktop
contrast=4
```

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (5.14.16.arch1-1)
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
This has caused errors in programs such as neofetch as seen here:
https://github.com/dylanaraps/neofetch/issues/1941

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444992] New: Edit Layer Style options crash

[vanyossi]

https://bugs.kde.org/show_bug.cgi?id=444992

Bug ID: 444992
   Summary: Edit Layer Style options crash
   Product: krita
   Version: 5.0.0-beta2
  Platform: Compiled Sources
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: layer styles
  Assignee: krita-bugs-n...@kde.org
  Reporter: ghe...@gmail.com
  Target Milestone: ---

Some layer style options seem to generate a crash upon trying to open the layer
style dialog to edit them. For the layer styles I only used krita default
resources. From my testing this is at least triggered by "gradient overlay"
style. but other may fall into this category. 

STEPS TO REPRODUCE
1.  Create image and add a gradient overlay
2. Save image and close it
3. Reopen image and reopen layer style dialog.

OBSERVED RESULT
Crash

I attach backtrace.
Process 59704 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
frame #0: 0x0001023ef8f4
libkritaui.17.dylib`psd_layer_effects_shadow_base::setGradient(this=0x0002a6050900,
value=KoAbstractGradientSP @ 0x00016fdf5fd0) at psd.h:427:38
   424
   425  void setGradient(KoAbstractGradientSP value)
   426  {
-> 427  m_gradientLink.type = value->resourceType().first;
   428  m_gradientLink.md5 = value->md5Sum();
   429  m_gradientLink.filename = value->filename();
   430  m_gradientLink.name = value->name();
Target 0: (krita) stopped.
(lldb) bt all
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
  * frame #0: 0x0001023ef8f4
libkritaui.17.dylib`psd_layer_effects_shadow_base::setGradient(this=0x0002a6050900,
value=KoAbstractGradientSP @ 0x00016fdf5fd0) at psd.h:427:38
frame #1: 0x0001023e1810
libkritaui.17.dylib`GradientOverlay::fetchGradientOverlay(this=0x00029c49b1a0,
config=0x0002a6050900) const at kis_dlg_layer_style.cpp:1136:13
frame #2: 0x0001023dd9b4
libkritaui.17.dylib`KisDlgLayerStyle::style(this=0x00016fdf87a0) const at
kis_dlg_layer_style.cpp:470:24
frame #3: 0x0001024d7788
libkritaui.17.dylib`updateLayerStyles(layer=,
dlg=0x00016fdf87a0) at kis_layer_manager.cc:906:59
frame #4: 0x0001024dc9ac
libkritaui.17.dylib`decltype(__f=(0x607cd668),
__args=0x607cd670, __args=0x607cd678)(KisSharedPtr,
KisDlgLayerStyle*)>(fp)(std::__1::forward&>(fp0),
std::__1::forward(fp0))) std::__1::__invoke, KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*&>(void (*&)(KisSharedPtr, KisDlgLayerStyle*),
KisSharedPtr&, KisDlgLayerStyle*&) at type_traits:3694:1
frame #5: 0x0001024dc944
libkritaui.17.dylib`std::__1::__bind_return,
KisDlgLayerStyle*), std::__1::tuple, KisDlgLayerStyle*>,
std::__1::tuple<>, __is_valid_bind_return,
KisDlgLayerStyle*), std::__1::tuple, KisDlgLayerStyle*>,
std::__1::tuple<> >::value>::type std::__1::__apply_functor @
0x00016fdf626f, __args=size=0)(KisSharedPtr, KisDlgLayerStyle*),
std::__1::tuple, KisDlgLayerStyle*>, 0ul, 1ul,
std::__1::tuple<> >(void (*&)(KisSharedPtr, KisDlgLayerStyle*),
std::__1::tuple, KisDlgLayerStyle*>&,
std::__1::__tuple_indices<0ul, 1ul>, std::__1::tuple<>&&) at functional:2857:12
frame #6: 0x0001024dc8e4
libkritaui.17.dylib`std::__1::__bind_return,
KisDlgLayerStyle*), std::__1::tuple, KisDlgLayerStyle*>,
std::__1::tuple<>, __is_valid_bind_return,
KisDlgLayerStyle*), std::__1::tuple, KisDlgLayerStyle*>,
std::__1::tuple<> >::value>::type std::__1::__bind, KisDlgLayerStyle*),
KisSharedPtr&, KisDlgLayerStyle*>::operator()<>() at
functional:2890:20
frame #7: 0x0001024dc8a0
libkritaui.17.dylib`decltype(__f=0x607cd668)(KisSharedPtr,
KisDlgLayerStyle*), KisSharedPtr&, KisDlgLayerStyle*>&>(fp)())
std::__1::__invoke,
KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*>&>(std::__1::__bind,
KisDlgLayerStyle*), KisSharedPtr&, KisDlgLayerStyle*>&) at
type_traits:3694:1
frame #8: 0x0001024dc854 libkritaui.17.dylib`void
std::__1::__invoke_void_return_wrapper::__call, KisDlgLayerStyle*),
KisSharedPtr&, KisDlgLayerStyle*>&>(std::__1::__bind, KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*>&) at __functional_base:348:9
frame #9: 0x0001024dc82c
libkritaui.17.dylib`std::__1::__function::__alloc_func, KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*>, std::__1::allocator, KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*> >, void ()>::operator(this=0x607cd668)() at
functional:1558:16
frame #10: 0x0001024db120
libkritaui.17.dylib`std::__1::__function::__func, KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*>, std::__1::allocator, KisDlgLayerStyle*), KisSharedPtr&,
KisDlgLayerStyle*> >, void ()>::operator(this=0x607cd660)() at
functional:1732:12
frame #11: 0x0001067d5f7c

[gwenview] [Bug 444935] Thumbnail bar should try to maintain its scroll position while resizing it

[Nagy Tibor]

https://bugs.kde.org/show_bug.cgi?id=444935

--- Comment #1 from Nagy Tibor  ---
Created attachment 143225
  --> https://bugs.kde.org/attachment.cgi?id=143225=edit
Mockup

A quick mockup how I would expect this to work. Notice the scaling reference
point at the centerline of the thumbnail bar's current viewport.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 444574] kwin does not honor system setting for monitor refresh rate

[jpandrusky]

https://bugs.kde.org/show_bug.cgi?id=444574

jpandrusky  changed:

   What|Removed |Added

Product|kwin|KScreen
  Component|wayland-generic |common
   Assignee|kwin-bugs-n...@kde.org  |kscreen-bugs-n...@kde.org

--- Comment #2 from jpandrusky  ---
Changing to Kscreen. I've been doing some more digging and have found some
strange behaviour using kscreen-doctor.

When I log in and run 'kscreen-doctor -o', I get the following:

Output: 1 GBT AORUS FV43U/21100B000422 enabled connected primary Unknown Modes:
0:3840x2160@144! 1:3840x2160@60 2:3840x2160@120 3:3840x2160@60 4:2560x1440@144
5:2560x1440@120 6:2560x1440@60 7:1920x1200@144 8:1920x1080@144 9:1920x1080@120
10:1920x1080@120 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60
14:1600x1200@144 15:1680x1050@60 16:1280x1024@60 17:1440x900@60 18:1280x800@144
19:1280x720@120 20:1280x720@120 21:1280x720@100 22:1280x720@60 23:1280x720@60
24:1280x720@50 25:1024x768@75 26:1024x768@60 27:800x600@75 28:800x600@60
29:720x576@50 30:720x576@50 31:720x480@60 32:720x480@60 33:720x480@60
34:720x480@60 35:640x480@75 36:640x480@60 37:640x480@60 38:3840x2160@60*
Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic
RgbRange: unknown primary

Which says that I should be running at 3840x2160@144, but I'm actually only
running at 38402x2160@60.

If I set the refresh to 120Hz and revert to 144Hz, it fixes itself and I'll
actually be at 3840x2160@144, but the output of 'kscreen-doctor -o' is:

Output: 1 GBT AORUS FV43U/21100B000422 enabled connected primary Unknown Modes:
0:3840x2160@60 1:3840x2160@120 2:3840x2160@60 3:3840x2160@60 4:2560x1440@144
5:2560x1440@120 6:2560x1440@60 7:1920x1200@144 8:1920x1080@144 9:1920x1080@120
10:1920x1080@120 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60
14:1600x1200@144 15:1680x1050@60 16:1280x1024@60 17:1440x900@60 18:1280x800@144
19:1280x720@120 20:1280x720@120 21:1280x720@100 22:1280x720@60 23:1280x720@60
24:1280x720@50 25:1024x768@75 26:1024x768@60 27:800x600@75 28:800x600@60
29:720x576@50 30:720x576@50 31:720x480@60 32:720x480@60 33:720x480@60
34:720x480@60 35:640x480@75 36:640x480@60 37:640x480@60 38:3840x2160@144*!
Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic
RgbRange: unknown primary

The mode for 3840x2160@144 has changed to 3840x2160@60.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 444917] Make "updates available" notifications more informative

[Felipe Kinoshita]

https://bugs.kde.org/show_bug.cgi?id=444917

Felipe Kinoshita  changed:

   What|Removed |Added

 CC||kinof...@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 444991] New: Can not connect to Zorin Connect

[Edward Brennan]

https://bugs.kde.org/show_bug.cgi?id=444991

Bug ID: 444991
   Summary: Can not connect to Zorin Connect
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: iOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ios-application
  Assignee: lucas.w...@tuta.io
  Reporter: edward.bren...@yahoo.com
  Target Milestone: ---

SUMMARY
Device is not discoverable when using Zorin Connect

STEPS TO REPRODUCE
1. Tried refresh 
2. Tried swipe down refresh
3. Tried enter IP on both the phone and on the desktop 

OBSERVED RESULT
Device was not discovered

EXPECTED RESULT
Device to be discovered

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 
Zorin 16
iOS 15.0.2
ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 444800] Discover crashes with error ASSERT: "m_responsePending != pending"

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=444800

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/discover/-/merge_requests/198

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444516] Crash while painting

[David REVOY]

https://bugs.kde.org/show_bug.cgi?id=444516

--- Comment #11 from David REVOY  ---
@tiar: All the crashes backtrace here are really happening in middle of stroke
of brush with the freehand brush tool. (while penciling or inking). 

I do selection rarely when repositioning things with the transform tool (but
this is happening more at storyboard time); in this case I manage all by
keyboard (a key for the lasso or rectangular tool, Ctrl+T for the transform,
Enter to bake the result, deselect and B to repaint). But I never had a crash
within this type of sequence. 

I also rarely undo while penciling or inking. I use a slot of the Ten Brush
plugin binded to an eraser preset; and I pencil or ink with a preset and toggle
switch with this shortcut to an eraser when I need to clean.  I rarely stop
when a line is bad; I just trace the good one next to it, and switch to eraser
later in the process to do a mass cleaning of "wrong lines". It saves time. 
I'm on 15 pages episode with 84 panels doing similar workflow over and over :-)
I'm inking page 9 right now. 

Fortunately, autosave is doing a good job and I rarely loose more than 3
minutes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444990] Shortcut conflicts when filename contains number

[Aetf]

https://bugs.kde.org/show_bug.cgi?id=444990

Aetf <7437...@gmail.com> changed:

   What|Removed |Added

 CC||7437...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444990] Shortcut conflicts when filename contains number

[Aetf]

https://bugs.kde.org/show_bug.cgi?id=444990

Aetf <7437...@gmail.com> changed:

   What|Removed |Added

 Attachment #143223|0   |1
is obsolete||

--- Comment #1 from Aetf <7437...@gmail.com> ---
Created attachment 143224
  --> https://bugs.kde.org/attachment.cgi?id=143224=edit
The tab bar while pressing the alt key

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444990] New: Shortcut conflicts when filename contains number

[Aetf]

https://bugs.kde.org/show_bug.cgi?id=444990

Bug ID: 444990
   Summary: Shortcut conflicts when filename contains number
   Product: okular
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: 7437...@gmail.com
  Target Milestone: ---

Created attachment 143223
  --> https://bugs.kde.org/attachment.cgi?id=143223=edit
The tab bar while pressing the alt key

SUMMARY
In Okular by default, you can use Alt+1, Alt+2, etc. to activate annotation
tools. However, when you have multiple files open, and there are numbers in the
filenames, Alt+1, etc. may be assigned as the tabview keyboard accelerator to
switch tabs.

In the attached screenshot, it can be seen that the last document
"Statement-2021-10.pdf" has "1" underlined, suggesting it is used as the
accelerator key.

STEPS TO REPRODUCE
1. Open several documents in Okular
2. Make sure one of them gets assigned an accelerator key by pressing alt and
see which char is underlined in the tab bar
3. Press Alt+1

OBSERVED RESULT
If the current tab is not the one with filename containing "1", Okular will
switch to that tab.
If already on that tab, an "ambiguous shortcut detected" warning shows up and
nothing happens.

EXPECTED RESULT
Alt+1, Alt+2, etc. always activates the corresponding annotation tool,
regardless of filenames of currently opened documents.

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.16-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444950] Crash loading incorrect file (backup file) as pattern resource.

[amyspark]

https://bugs.kde.org/show_bug.cgi?id=444950

amyspark  changed:

   What|Removed |Added

 CC||a...@amyspark.me

--- Comment #3 from amyspark  ---
I cannot reproduce either of the two crashes with de586e5385 under MSVC.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444516] Crash while painting

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444516

--- Comment #10 from Tiar  ---
Hmm, maybe it was a Global Selection Mask, then? (It doesn't need to show on
the Layer stack, it's hidden by default, but it is there if you have anything
selected). Maybe you were editing a selection and undoing?... How do you
usually change selections?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444516] Crash while painting

[David REVOY]

https://bugs.kde.org/show_bug.cgi?id=444516

--- Comment #9 from David REVOY  ---
A new crash while painting (no mask, no undo, just drawing on regular
paint-layer). I'm copying here only the irregular thread output, it will be
shorter and probably better:

===

[New Thread 0x7fff06ffe700 (LWP 95085)]
[New Thread 0x7fff2ae79700 (LWP 95086)]
[New Thread 0x7fff2a678700 (LWP 95087)]
--Type  for more, q to quit, c to continue without paging--

Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault.
0x75d958f8 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
from /tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Widgets.so.5
(gdb) thread apply all bt

Thread 1599 (Thread 0x7fff2a678700 (LWP 95087)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x9bc2d04) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x9bc2cb0,
cond=0x9bc2cd8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x9bc2cd8, mutex=0x9bc2cb0) at
pthread_cond_wait.c:638
#3  0x750e0ddb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Core.so.5
#4  0x750e1129 in QWaitCondition::wait(QMutex*, unsigned long) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Core.so.5
#5  0x750db374 in QReadWriteLock::tryLockForRead(int) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Core.so.5
#6  0x750db426 in QReadWriteLock::lockForRead() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Core.so.5
#7  0x76e1ab76 in
KisPaintLayer::copyOriginalToProjection(KisSharedPtr,
KisSharedPtr, QRect const&) const () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17 
#8  0x76da03b4 in KisLayer::applyMasks(KisSharedPtr,
KisSharedPtr, QRect const&, KisSharedPtr,
KisSharedPtr) const () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17 
#9  0x76da10d7 in KisLayer::updateProjection(QRect const&,
KisSharedPtr) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#10 0x76da4fc8 in ?? () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#11 0x76d49b67 in KisAsyncMerger::startMerge(KisBaseRectsWalker&, bool)
() from /tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#12 0x76c0a71d in ?? () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#13 0x750dd877 in ?? () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Core.so.5
#14 0x750d942e in ?? () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libQt5Core.so.5
#15 0x7fffef5b1609 in start_thread (arg=) at
pthread_create.c:477
#16 0x74d41293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1598 (Thread 0x7fff2ae79700 (LWP 95086)):
#0  0x76c2290e in
KisMementoManager::resetRevisionHistory(QList >)
() from /tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#1  0x76c24cec in
KisMementoManager::purgeHistory(KisSharedPtr) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#2  0x76e3cd96 in KisTransactionData::~KisTransactionData() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#3  0x76e3d019 in KisTransactionData::~KisTransactionData() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#4  0x7235a360 in KUndo2QStack::clear() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritacommand.so.17
#5  0x7235a53b in KUndo2QStack::~KUndo2QStack() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritacommand.so.17
#6  0x77b12557 in ?? () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaui.so.17
#7  0x72360e61 in KisSurrogateUndoStore::~KisSurrogateUndoStore() ()
from /tmp/.mount_krita-hdj247/usr/bin/../lib/libkritacommand.so.17
#8  0x72360e79 in KisSurrogateUndoStore::~KisSurrogateUndoStore() ()
from /tmp/.mount_krita-hdj247/usr/bin/../lib/libkritacommand.so.17
#9  0x76e5cf91 in KisSurrogateUndoAdapter::~KisSurrogateUndoAdapter()
() from /tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#10 0x76c86e5c in ?? () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#11 0x76c84a4d in KisSavedMacroCommand::~KisSavedMacroCommand() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#12 0x76c84a79 in KisSavedMacroCommand::~KisSavedMacroCommand() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#13 0x7235a1e6 in KUndo2QStack::checkUndoLimit() () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritacommand.so.17
#14 0x7235d0a7 in KUndo2QStack::push(KUndo2Command*) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritacommand.so.17
#15 0x76e5d9b3 in
KisPostExecutionUndoAdapter::addCommand(QSharedPointer) () from
/tmp/.mount_krita-hdj247/usr/bin/../lib/libkritaimage.so.17
#16 0x76c43dc6 in

[kdeconnect] [Bug 444989] New: Crashes when refreshing

[Edward Brennan]

https://bugs.kde.org/show_bug.cgi?id=444989

Bug ID: 444989
   Summary: Crashes when refreshing
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: iOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ios-application
  Assignee: lucas.w...@tuta.io
  Reporter: edward.bren...@yahoo.com
  Target Milestone: ---

SUMMARY
Crashes after multiple refreshes.

STEPS TO REPRODUCE
1. Swip down to refresh
2. Repeat multiple times
3. 

OBSERVED RESULT
App crashes

EXPECTED RESULT
Not to crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 
iOS 15.0.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 444988] [Feature request]: Like bomi Subtitle viewer [or Potplayer Subtitle Browser]

[zlrkeeq]

https://bugs.kde.org/show_bug.cgi?id=444988

--- Comment #1 from zlrkeeq  ---
Created attachment 143222
  --> https://bugs.kde.org/attachment.cgi?id=143222=edit
potplayer

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 444988] New: [Feature request]: Like bomi Subtitle viewer [or Potplayer Subtitle Browser]

[zlrkeeq]

https://bugs.kde.org/show_bug.cgi?id=444988

Bug ID: 444988
   Summary: [Feature request]: Like bomi Subtitle viewer [or
Potplayer Subtitle Browser]
   Product: Haruna
   Version: unspecified
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: lacod...@yahoo.fr
  Target Milestone: ---

Created attachment 143221
  --> https://bugs.kde.org/attachment.cgi?id=143221=edit
bomi

Hi. For this very cool feature found in bomi : 'Subtitle viewer' [ "Subtitle
Browser" in Potplayer].
-You can at any moment read what just passed [sometimes the film goes too fast,
or one wasn't paying attention]
-You can doble-click any line and the movie goes to that time
-You can compare subs to choose the best, or to compare dif languages...

-bomi can show 2, 3 [or more!] subs at the same time.
https://1fichier.com/?m3qnlbm75yew9hjzsh9s Since bomi is also based in mpv,
maybe you could look at its code... https://github.com/xylosper/bomi/
;

-Potplayer [on the video it can display 2 srt files, but on the Subtitle
Browser only 1]. If the subs are coloured [srt here] it shows the colors. [also
there are edit and sync functions there]
https://1fichier.com/?zftg86prenqixyy2w9i6
Thx

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444980] Resources > Workspaces: Workspace manager GUI doesn't warn about overwrite on initial load.

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444980

Tiar  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com
   Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444981] krita crashes when I try to open an animation

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444981

Tiar  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||tamtamy.tym...@gmail.com
   Severity|normal  |crash

--- Comment #1 from Tiar  ---
Please attach a file that you can create using Help -> Show Krita log for bug
reports.

Also please first update your Krita to 4.4.8 and then try to open those files;
if they don't crash any more, please write here and we'll close the bug report
because it will no longer be needed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444977] Resource > Workspaces: Can't rename workspaces.

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444977

Tiar  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com
   Severity|minor   |wishlist

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444950] Crash loading incorrect file (backup file) as pattern resource.

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444950

--- Comment #2 from Tiar  ---
Created attachment 143220
  --> https://bugs.kde.org/attachment.cgi?id=143220=edit
Potential patch for tasksets

@Wolthera, how did you make `sketch.png~` to be visible for you when you search
for patterns? I can't see it when the ending is wrong. I think I have the Qt
dialogs, I tried to enable native dialogs but even after restart it still shows
the same dialog.

The pattern crash probably happens because:
- it needs md5 sum. But it isn't calculated yet
- to calculate md5 sum, it tries to save the pattern to memory (why? it's not
embedded in anything, it's a file)
- saving pattern to memory doesn't work, because it uses: QImage.save(buffer,
"PNG~") function. So it doesn't save any bytes
- md5 doesn't work on empty buffers (no bytes saved)
Since we're going to talk about md5 situation with Dmitry, so I'll mention
that.

For tasksets, the backtrace is different (note that it doesn't go into
`md5Sum()` function but already crashes on load()). However I have the same
problem, reproducing your issue :/
However I read the code and I think the problem might be that it simply doesn't
create a loader (I can't be sure because the backtrace is cut, I think - was it
segmentation fault because of empty loader?  I hope so, at least). In that
case, I provided a patch file, which might or might not work, because I
couldn't test it. It would be awesome if you could please test it, if it's
possible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Skanlite] [Bug 444987] silent crash while searching for scanners

[elypter]

https://bugs.kde.org/show_bug.cgi?id=444987

elypter  changed:

   What|Removed |Added

 CC||elyp...@yahoo.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[Skanlite] [Bug 444987] New: silent crash while searching for scanners

[elypter]

https://bugs.kde.org/show_bug.cgi?id=444987

Bug ID: 444987
   Summary: silent crash while searching for scanners
   Product: Skanlite
   Version: 21.08.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: elyp...@yahoo.de
  Target Milestone: ---

SUMMARY

it just closes while searching for scanners.
when running in terminal i get this error message "Speicherzugriffsfehler
(Speicherabzug geschrieben)"
xsane and simple-scan work

STEPS TO REPRODUCE
1. start skanlite


OBSERVED RESULT

crash

EXPECTED RESULT

find a scanner

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.16-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7.1 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

detected scanners by xsane:
printerscanner: lexmark mc3426ad, not supported by sane and using a proprietary
java driver
webcam: hp true vision hd

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444975] Resources > Workspaces: Can't overwrite different workspace of the same name.

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444975

Tiar  changed:

   What|Removed |Added

   Keywords||release_blocker
 CC||tamtamy.tym...@gmail.com

--- Comment #1 from Tiar  ---
Did you use the Window -> Workspaces menu or the toolbar button for importing?
Or does it happen in both?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444950] Crash loading incorrect file (backup file) as pattern resource.

[Tiar]

https://bugs.kde.org/show_bug.cgi?id=444950

Tiar  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com
   Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED
   Keywords||regression, release_blocker

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 444986] New: Kdenlive crashes when interracting with most compositions (adding/editing them)

[Anthony Naddeo]

https://bugs.kde.org/show_bug.cgi?id=444986

Bug ID: 444986
   Summary: Kdenlive crashes when interracting with most
compositions (adding/editing them)
   Product: kdenlive
   Version: 21.08.2
  Platform: Slackware Packages
OS: Microsoft Windows
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: anthony.nad...@gmail.com
  Target Milestone: ---

Created attachment 143219
  --> https://bugs.kde.org/attachment.cgi?id=143219=edit
The project file. Happy to transfer the original files somehow. Let me know.

SUMMARY
There is a very high chance that interacting with compositions or attempting to
place compositions/mix clips will cause kdenlive to crash. I managed to get a
Slide effect in once time but it crashes when I try to edit that effect.

STEPS TO REPRODUCE
1. Add a Wipe Composition

Interact with an existing transition or Mixed Clip and it crashes as well.
Doing anything relating to transitions is likely to cause a crash.

Demo of the crash: https://youtu.be/IF0uqzhuzEM

OBSERVED RESULT
Crash

EXPECTED RESULT
No crash

SOFTWARE/OS VERSIONS
Kdenlive: 21.08.2
MLT: 7.1.0
Qt: 5.15.2 (built against 5.15.2 x86_64-little_endian-llp64)
Frameworks: 5.86.0
System: Windows 10 Version 2009
Kernel: winnt 10.0.19043
CPU: x86_64
Windowing System: windows
Movit (GPU): disabled


ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444890] Okular window visible on all virtual desktops ignores setting "Open new files in tabs"

[Dominik Kummer]

https://bugs.kde.org/show_bug.cgi?id=444890

--- Comment #11 from Dominik Kummer  ---
why not? maintain your priorities as you wish. I dont expect to be the first
one.

I just file a bug report, try to connect the dots from a user point of view,
try to scratch the surface of the source code, maybe I can contribute something
helpful, or probably I will debug it on my own someday.

but randomly redirecting bug reporters is no real help for anyone.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 437269] Crash when removing all bookmarks

[Jonathan Verner]

https://bugs.kde.org/show_bug.cgi?id=437269

Jonathan Verner  changed:

   What|Removed |Added

Version|5.6.2   |20.12.2
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
  Component|general |general
Product|kdevelop|kate

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444890] Okular window visible on all virtual desktops ignores setting "Open new files in tabs"

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=444890

--- Comment #10 from Albert Astals Cid  ---
Ah, ridiculing the developer, that's how you expect me to chose to prioritize
your bug among the other 400 issues I can work on?

For the future, not a good idea.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444971] Okular crashed when opening a markdown file

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=444971

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/okular/-/merge_requests/501

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 444956] Wipe duration not adjusted

[Paul Worrall]

https://bugs.kde.org/show_bug.cgi?id=444956

Paul Worrall  changed:

   What|Removed |Added

 CC||p.r.worr...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Paul Worrall  ---
I can reproduce this.  Same version of Kdenlive installed from the KDE neon
user edition repos

Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: X11
Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: AMD CEDAR

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 412707] KDevelop leaves hundreds of megabytes of temp files if it crashes

[Tim E. Real]

https://bugs.kde.org/show_bug.cgi?id=412707

--- Comment #9 from Tim E. Real  ---
Ah yes. Good idea I suppose, since we do still have to manually clear the temp
files out
 after a non-lockup crash to the desktop.
The trouble for me was when KDevelop occasionally crashed by locking up the
computer,
 then I had all those temp files left over upon reboot. (I work on huge
projects, maybe I need more RAM).
But this 'leftover temp files upon reboot' problem seems to have gone away for
me. 
Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konqueror] [Bug 237189] konqueror: Doesn't retain "View Mode - SVN Client" when saving "View Profile"

[Martin Fritz]

https://bugs.kde.org/show_bug.cgi?id=237189

Martin Fritz  changed:

   What|Removed |Added

 CC||fritz.marti...@web.de

--- Comment #2 from Martin Fritz  ---
IF I am not mistaken Profiles are a thing of the past anyways, so that bug is
probably of no importance anymore. Can someone confirm that?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444890] Okular window visible on all virtual desktops ignores setting "Open new files in tabs"

[Dominik Kummer]

https://bugs.kde.org/show_bug.cgi?id=444890

Dominik Kummer  changed:

   What|Removed |Added

Summary|Program Feature "Open new   |Okular window visible on
   |files in tabs" not working  |all virtual desktops
   ||ignores setting "Open new
   ||files in tabs"

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444890] Program Feature "Open new files in tabs" not working

[Dominik Kummer]

https://bugs.kde.org/show_bug.cgi?id=444890

--- Comment #9 from Dominik Kummer  ---
i use special window rule blabla. yeah.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444890] Program Feature "Open new files in tabs" not working

[Dominik Kummer]

https://bugs.kde.org/show_bug.cgi?id=444890

--- Comment #8 from Dominik Kummer  ---
so please don't redirect me into other projects without reading the report.

I supect the issue around attachExistingInstance() in shell/okular_main.cpp. It
does not understand what to do
if okular is visible on multiple virtual plasma desktops at the same time. At
least that's what the
symptom looks like. Maybe it is intentional. But it does not feel like so.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 231495] Keybindings for switching between three screens are not fully working in a triplehead setup.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=231495

g...@section9.follonica.org changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdepim] [Bug 444985] New: Wrong ports in akonadi_pop3_resource.pot

[Freek de Kruijf]

https://bugs.kde.org/show_bug.cgi?id=444985

Bug ID: 444985
   Summary: Wrong ports in akonadi_pop3_resource.pot
   Product: kdepim
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: freekdekru...@kde.nl
  Target Milestone: ---

SUMMARY
Wrong ports in akonadi_pop3_resource.pot

STEPS TO REPRODUCE
1. search the above mentioned file
2. You see some text mentioning:
Considering the naming of the file, this is about POP, but the mentioned ports,
143 and 993, belong to IMAP. So I assume 143 should be 110 for POP3 and 993
should be 995 for POP3S.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 317928] Desktops signals in workspace are not triggered...

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=317928

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||kde@grau.net
 Status|REPORTED|NEEDSINFO

--- Comment #5 from kde@grau.net ---
This bug report is quite old. Can you still reproduce this issue with KDE 5.23?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 322975] desktop render will twisted when the opengl application is closed.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=322975

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||kde@grau.net

--- Comment #54 from kde@grau.net ---
This bug report is quite old and has been reported to be fixed in 5.4. Can you
still reproduce this issue with KDE 5.23?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 444890] Program Feature "Open new files in tabs" not working

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=444890

--- Comment #7 from Albert Astals Cid  ---
Honestly I don't even know how to use Window Rules, so I have not tried because
i don't understand what you wrote in that comment other that "I used special
Window Rules and it broke"

-- 
You are receiving this mail because:
You are watching all bug changes.

[ark] [Bug 444965] Ark only extracts the main folder, making it empty

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=444965

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/utilities/ark/-/merge_requests/69

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 434877] High CPU usage

[Riccardo Robecchi]

https://bugs.kde.org/show_bug.cgi?id=434877

--- Comment #12 from Riccardo Robecchi  ---
Arjen, I think I have understood why there is excessive CPU usage and I have a
proposal on how to fix it. The problem is that System Monitor (and KSysGuard as
well, though to a less extent) simply poll the information too often. The
difference between Plasma System Monitor, which uses a lot of resources, and
GNOME System Monitor, which is quite efficient, is that the latter does not
update the data as often, thus using much fewer resources and being much
lighter on the system. It is my conviction that by reducing the amount of times
the data is updated, a satisfactory balance can be achieved.
Currently System Monitor updates multiple times a second, which is overkill for
any practical purposes: nobody needs to see the CPU graph going up and down
with such precision, one or two times a second would be more than enough. As
far as I understand this, this would involve basically any other application
and widget that relies on this features because this is all managed in the KDE
Frameworks? Do you reckon reducing the update rate would be feasible?
Let me know. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=402827

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REOPENED|NEEDSINFO
 CC||kde@grau.net

--- Comment #27 from kde@grau.net ---
This bug report is quite old and Rainer Finke reported the issue resolved. Can
anyone still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 444984] New: Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only

[Kalzi]

https://bugs.kde.org/show_bug.cgi?id=444984

Bug ID: 444984
   Summary: Latte dock autohides on an empty desktop even though
"autohide" isn't enabled, "dodge active" enabled only
   Product: lattedock
   Version: 0.10.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: kalzwa...@yahoo.com
  Target Milestone: ---

SUMMARY
Every couple of days, Latte dock starts just autohiding on an empty desktop
even though only "dodge active" is enabled, not "autohide"

STEPS TO REPRODUCE
1. Edit the dock
2. Set it to "dodge active" (not sure about others as I don't use them)
3. It will auto hide on an empty desktop every couple of days until I kill it
through ksysgaurd.

OBSERVED RESULT
It auto-hides on an empty desktop, and I'd have to kill the app then restart it

EXPECTED RESULT
It should only auto-hide when there is an active window, as chosen in the
settings.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.10-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
Latte dock is 0.10.3 that I had to download from the AUR website, not from
Manjaro's pamac, because it is not available there even if I searched in the
AUR from there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 444983] New: Cannot stop 'fetching updates'

[David]

https://bugs.kde.org/show_bug.cgi?id=444983

Bug ID: 444983
   Summary: Cannot stop 'fetching updates'
   Product: Discover
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: david.cortes.riv...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
If I launch discover from the system tray and it starts to fetch updates, there
is no button at the top-right to stop that fetching of updates and the 'Esc'
key does not stop them either.

STEPS TO REPRODUCE
1. Launch discovert by clicking the system tray icon.
2. While it is fetching updates, press 'Esc'.

OBSERVED RESULT
Should abort what it was doing (fetching updates).

EXPECTED RESULT
Continues what it was doing.

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: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD VEGA10

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 418899] Everything is unusable after monitor turn on

[Nick Stefanov]

https://bugs.kde.org/show_bug.cgi?id=418899

Nick Stefanov  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Nick Stefanov  ---
It fixed itself.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows

[Andreas Kilgus]

https://bugs.kde.org/show_bug.cgi?id=366651

Andreas Kilgus  changed:

   What|Removed |Added

 CC||k...@fuenfsieben.de

--- Comment #15 from Andreas Kilgus  ---
I see this happening, too. Most of the time the first application remarkably
lacking content updates is Firefox. But I have seen this effect for example in
akregator and konqueror, too, to name at least these two.
Not knowing if this is just correlation or real causation, just for the record:
It is my impression that this regularly starts to happen as soon as main memory
is heavily under pressure (and a mentionable amount of swap space is in use).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 416340] kwin_x11 crashes when switching a screen with another computer using Edimax device

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=416340

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||kde@grau.net
 Status|REPORTED|NEEDSINFO

--- Comment #1 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[k3b] [Bug 444982] New: Mouse pointer in resizing mode causes a glitch in K3b

[Patrick Silva]

https://bugs.kde.org/show_bug.cgi?id=444982

Bug ID: 444982
   Summary: Mouse pointer in resizing mode causes a glitch in K3b
   Product: k3b
   Version: 21.08.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: bugsefor...@gmx.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Created attachment 143218
  --> https://bugs.kde.org/attachment.cgi?id=143218=edit
screen recording

SUMMARY
Please watch the attached screen recording and observe what happens when the
mouse pointer changes to resizing mode. Can reproduce on X11 and Wayland
sessions.

EXPECTED RESULT
observed glitch should not occur

Operating System: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[ark] [Bug 444965] Ark only extracts the main folder, making it empty

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=444965

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Albert Astals Cid  ---
I can reproduce that

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 418899] Everything is unusable after monitor turn on

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=418899

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||kde@grau.net

--- Comment #1 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please check
if you have any coredumps following the instructions in
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
and attach a backtrace

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)

[Andreas Kilgus]

https://bugs.kde.org/show_bug.cgi?id=433664

Andreas Kilgus  changed:

   What|Removed |Added

 CC||k...@fuenfsieben.de

--- Comment #10 from Andreas Kilgus  ---
Have you tried to switch "Keep window thumbnails" to "always" (s.
https://bugs.kde.org/show_bug.cgi?id=425856)? For several users including me
this option removes the laggy desktop experience caused by compositing enabled.
This is more of a workaround than a solution but might lead the way to get rid
of the bug if this solves the problem for different hardware/software setups …

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 426412] Kwin laggy after pausing and un-pausing compositing

[Andreas Kilgus]

https://bugs.kde.org/show_bug.cgi?id=426412

--- Comment #9 from Andreas Kilgus  ---
Have you tried to switch "Keep window thumbnails" to "always" (s.
https://bugs.kde.org/show_bug.cgi?id=425856)? For several users including me
this option removes the laggy desktop experience caused by compositing enabled.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 425856] Kwin FPS inconsistent after kwin is suspended

[Andreas Kilgus]

https://bugs.kde.org/show_bug.cgi?id=425856

Andreas Kilgus  changed:

   What|Removed |Added

 CC||k...@fuenfsieben.de
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Andreas Kilgus  ---
For a long time I had been wondering why my desktop behaved laggy with
compositing enabled (disabling compositing though gave me a smooth desktop
experience). It was not always the case after a restart of the machine but
every time after suspending or a game having disabled the compositor
temporarily. I changed drivers, OpenGL versions, … to no avail. But indeed -
changing the compositor setting to keep window thumbnails "always" (neither
"never" nor "only visible") removes the lag immediately.

Operating System: openSUSE Leap 15.2
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.15-lp153.2.g3416a5a-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.6 GiB of RAM
Graphics Processor: AMD BONAIRE

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 444896] FR: Search using wildcards does not work

[Adrian Fluturel]

https://bugs.kde.org/show_bug.cgi?id=444896

--- Comment #4 from Adrian Fluturel  ---
> Will flag as confirmed. Maybe someone else will come in with an "It's
> intentional"

Thank you. I talked for a bit on #kde-devel and people seem to think it's a
wanted feature and it is wanted, and some thought baloo supported that already.
I don't know much about dolphin or about kde in general, I'm just trying to get
started and fix something, and this started like a pretty simple problem in
theory but I am now getting in a rabbit hole of sorts that I don't know how to
navigate

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 444969] Digikam often freezes when dropping a tag over another to merge them

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=444969

--- Comment #5 from Maik Qualmann  ---
>From which camera are the images that lead to the crash? I found a thread at
Exiv2 that "BurstSheed" is a typo and must be called "BurstSpeed". However,
this is not relevant for the crash.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 444896] FR: Search using wildcards does not work

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=444896

tagwer...@innerjoin.org changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to Adrian Fluturel from comment #2)
> So what is a viable solution here? ...
I don't know what the "More Search Tools" options can give here, it sounds as
if you are looking for something like mlocate.

> ... Add this in kio-filenamesearch?
Don't know enough about the dolphin/filenamesearch/etc internals, I have to
pass on that question.

Will flag as confirmed. Maybe someone else will come in with an "It's
intentional"

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 435441] valgrind fails to interpose malloc on musl 1.2.2 due to weak symbol name and no libc soname

[Michael Forney]

https://bugs.kde.org/show_bug.cgi?id=435441

--- Comment #4 from Michael Forney  ---
Created attachment 143217
  --> https://bugs.kde.org/attachment.cgi?id=143217=edit
Patch to handle weak symbols as global

Here's a patch that fixes the issue for me by setting *is_global_out=True for
STB_WEAK symbols in addition to STB_GLOBAL.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`

[Brian Kaye]

https://bugs.kde.org/show_bug.cgi?id=400079

--- Comment #7 from Brian Kaye  ---
Harald

The image for what it looks on your system shows up as a blank darg image.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399499] KWin crashes in makeInterleavedArrays

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=399499

kde@grau.net changed:

   What|Removed |Added

 CC||rodrigo.ch...@gmail.com

--- Comment #68 from kde@grau.net ---
*** Bug 430160 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 430160] Kwin Crash after return from Suspend

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=430160

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||kde@grau.net

--- Comment #2 from kde@grau.net ---


*** This bug has been marked as a duplicate of bug 399499 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 444969] Digikam often freezes when dropping a tag over another to merge them

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=444969

--- Comment #4 from Maik Qualmann  ---
I cannot reproduce any problems with the current GIT version.
Exiv2 has many exceptions in your log that may lead to a crash.

Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot get metadata tag
title with Exiv2:  (Error # 7 :  "Invalid tag name or ifdId `BurstSheed', ifdId
115"

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 429532] kwin_x11 crashes after waking up from sleep (GPU is NVidia)

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=429532

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||kde@grau.net
 Status|REPORTED|NEEDSINFO

--- Comment #2 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 444216] When the left sidebar is hidden behind the hamburger bar, it closes when moving the mouse in it's direction.

[Claudio Cambra]

https://bugs.kde.org/show_bug.cgi?id=444216

Claudio Cambra  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Claudio Cambra  ---
Can confirm this happens in several other Kirigami applications too (Kirigami
Gallery, Neochat)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 444867] [FEATURE REQUEST] Add a new dialog to quickly add events

[Claudio Cambra]

https://bugs.kde.org/show_bug.cgi?id=444867

Claudio Cambra  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Claudio Cambra  ---
Hi juan,

Since this is not a bug, I am closing. However, your request is noted (and
appreciated!). In the future, if you'd like to submit a feature request, please
do so in our Matrix channel (#kalendar:kde.org) or on our Invent repository.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 444194] Time-picker widget should be usable, regardless of screen-size

[Claudio Cambra]

https://bugs.kde.org/show_bug.cgi?id=444194

Claudio Cambra  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Claudio Cambra  ---
Status report: I tweaked the sizing of the time picker. Now it remains as
compact as possible which in most cases makes it for within the window bounds
of the incidence editor just fine. As I mentioned, you can also now scroll in
the picker to change the time.

Additionally, the time combo boxes now use the same time format as elsewhere in
the application. The time picker itself does not yet do this.

Considering that the "bug" aspect of this report has been fixed, I am closing.
Thank you for reporting this bug!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 429837] KWin crash through QtGLCore/NVidia OpenGL

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=429837

kde@grau.net changed:

   What|Removed |Added

 CC||kde@grau.net
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 427822] Crash back to login screen after moving the cursor over an open app in the panel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=427822

kde@grau.net changed:

   What|Removed |Added

 CC||kde@grau.net
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #9 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 427496] KWin crashes when disconnecting the second monitor

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=427496

kde@grau.net changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||kde@grau.net

--- Comment #1 from kde@grau.net ---
This bug report is quite old. Can you still reproduce this issue with KDE 5.23?
If so, can you please submit a new backtrace with debugging information for
this version?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`

[Brian Kaye]

https://bugs.kde.org/show_bug.cgi?id=400079

Brian Kaye  changed:

   What|Removed |Added

 CC||b...@unb.ca

--- Comment #6 from Brian Kaye  ---
At one time  or other I have needed most of the info from dmidecode.  Wrote a
script to produce the following
--
 System Information Type s

bios-vendor LENOVO
bios-versionN1EET91W (1.64 )
bios-release-date   05/12/2021
bios-revision   1.64
firmware-revision   1.18
system-manufacturer LENOVO
system-product-name 20ENCTO1WW
system-version  ThinkPad P50
system-serial-numberPC0DTF1L
system-uuid 423e074c-20a8-11b2-a85c-b8c832f25d1c
system-family   ThinkPad P50
baseboard-manufacturer  LENOVO
baseboard-product-name  20ENCTO1WW
baseboard-version   SDK0J40697 WIN
baseboard-serial-number L1HF661007G
baseboard-asset-tag Not Available
chassis-manufacturerLENOVO
chassis-typeNotebook
chassis-version None
chassis-serial-number   PC0DTF1L
chassis-asset-tag   No Asset Information
processor-familyCore i7
processor-manufacturer  Intel(R) Corporation
processor-version   Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
processor-frequency 2700 MHz

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 427282] sddm freeze at logging

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=427282

kde@grau.net changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||kde@grau.net
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 444981] New: krita crashes when I try to open an animation

[Okaila]

https://bugs.kde.org/show_bug.cgi?id=444981

Bug ID: 444981
   Summary: krita crashes when I try to open an animation
   Product: krita
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: julia.schaeffermo...@gmail.com
  Target Milestone: ---

SUMMARY
I can create an animation, but when I close krita and I try to open the
animation again, the software crashes. However, it isn't the case with all my
animations. I can open some, but no others. The file's size doesn't matter. How
can I do ? (I have the 4.2.8 krita's version)

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 427212] kwin_x11 (5.19.5) crashes after inactive time

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=427212

kde@grau.net changed:

   What|Removed |Added

 CC||kde@grau.net
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 426245] Android emulator crashed on start

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=426245

kde@grau.net changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||kde@grau.net

--- Comment #4 from kde@grau.net ---
This bug report is quite old and unfortunately lacks proper debug information.
Can you still reproduce this issue with KDE 5.23? If so, can you please install
debugging packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 444896] FR: Search using wildcards does not work

[Adrian Fluturel]

https://bugs.kde.org/show_bug.cgi?id=444896

--- Comment #2 from Adrian Fluturel  ---
(In reply to tagwerk19 from comment #1)
> (In reply to Adrian Fluturel from comment #0)
> > The latter is the case here, baloo does not return the file requested with
> > "*_033.t*" as a search term.
> Sorry, this likely doesn't help you but you may need a different search tool
> for wildcard searches...
> 
> Baloo is tuned to provide fast results. It builds an index of things you
> _might_ search for and does lookups in that index as you type your search.
> That cannot really work for arbitrary wildcard searches.

So what is a viable solution here? Add this in kio-filenamesearch?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 426113] When closing emacs with C-z from fullscreen kwin crashes

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=426113

kde@grau.net changed:

   What|Removed |Added

 CC||kde@grau.net
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from kde@grau.net ---
This bug report is quite old and lacks proper debug information. Can you still
reproduce this issue with KDE 5.23? If so, can you please install debugging
packages following the info provided in 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports,
try to reproduce the bug and submit a backtrace with debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 426078] transparent controlpanel and menus after standy

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=426078

kde@grau.net changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from kde@grau.net ---
Waiting for information

-- 
You are receiving this mail because:
You are watching all bug changes.