https://bugs.kde.org/show_bug.cgi?id=481308
--- Comment #74 from Michael Hamilton ---
(In reply to navid.zamani+kde from comment #72)
> I have the same problem, and since this is 7 months now and nobody of the...
I haven't seen this issue on any of our desktops for months (latest
https://bugs.kde.org/show_bug.cgi?id=494065
--- Comment #4 from Michael Hamilton ---
I was altering jpegs from a Samsung phone, I just tried images from a different
camera (very old Olympus E-M5) with the same result.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=494065
--- Comment #3 from Michael Hamilton ---
Here is a coredump from when I did a crop, crop/resize/...
These other operations often work, but sometimes dump core. There were no
message in the journal in this instance, just the report of a core dump
https://bugs.kde.org/show_bug.cgi?id=494065
--- Comment #2 from Michael Hamilton ---
If I perform an operation, such as resize, before using annotate, then I can
successfully exit the annotate and save the result.
But sometimes a resize or crop will also cause a coredump - not sure if it'
https://bugs.kde.org/show_bug.cgi?id=494065
--- Comment #1 from Michael Hamilton ---
This appears in the systemd journal prior to but in the same second as each
coredump:
org.kde.kdegraphics.gwenview.lib: Gwenview cannot apply color profile on
QImage::Format_ARGB32_Premultiplied images
--
You
https://bugs.kde.org/show_bug.cgi?id=494065
Bug ID: 494065
Summary: Coredump on exiting gwenview annotate-tool
Classification: Applications
Product: gwenview
Version: 24.08.1
Platform: openSUSE
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=482887
--- Comment #36 from Michael Hamilton ---
(In reply to Harald Sitter from comment #34)
> Looks useful enough. It's a different trace though. Best file a new bug
> report. Thanks.
https://bugs.kde.org/show_bug.cgi?id=492560
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=492560
Bug ID: 492560
Summary: Crash in kastatsfavoritesmodel.cpp at login
Classification: Plasma
Product: plasmashell
Version: 6.1.4
Platform: openSUSE
OS: Linux
Status: REP
https://bugs.kde.org/show_bug.cgi?id=482887
--- Comment #35 from Michael Hamilton ---
(In reply to Justin Zobel from comment #33)
> Interesting as it should download all required debug symbols, might be worth
> bringing up with Fedora if they are missing symbols in their debuginfod
> se
https://bugs.kde.org/show_bug.cgi?id=482887
--- Comment #32 from Michael Hamilton ---
(In reply to Justin Zobel from comment #31)
> Michael thanks for the added report, it is however missing debug symbols,
> please see
> https://community.kde.org/Guidelines_and_HOWTOs/
https://bugs.kde.org/show_bug.cgi?id=482887
--- Comment #30 from Michael Hamilton ---
I'm on 6.1.4 using Nvidia and I'm still seeing something similar as recently as
yesterday.
Operating System: openSUSE Tumbleweed 20240829
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
https://bugs.kde.org/show_bug.cgi?id=490624
--- Comment #3 from Michael Hamilton ---
Created attachment 172094
--> https://bugs.kde.org/attachment.cgi?id=172094&action=edit
coredumpctl gdb 2742 | tee ~/plasmashell-coredump-2742.log
This coredump occured when I logged in, I got the
https://bugs.kde.org/show_bug.cgi?id=490624
--- Comment #2 from Michael Hamilton ---
Not sure if I picked the right coredump, but I started with "coredumpctl gdb
34855" which seems to be a number and about the right time. The bt output is
as follows:
--
(gdb) bt
#0 0x7f287
https://bugs.kde.org/show_bug.cgi?id=490624
Bug ID: 490624
Summary: plasmashell core dump on login
Classification: Plasma
Product: plasmashell
Version: 6.1.2
Platform: openSUSE
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=486599
--- Comment #8 from Michael Hamilton ---
Adding this note on the best solution I've found so far, which is to use the
QT_USE_PHYSICAL_DPI environment variable:
echo 'export QT_USE_PHYSICAL_DPI=1' >>
/home/testuser/.config/plasma-w
https://bugs.kde.org/show_bug.cgi?id=486599
--- Comment #6 from Michael Hamilton ---
(In reply to Zamundaaa from comment #5)
> Sorry, but if you want to have content be shown at specific (physical or
> otherwise) sizes, you need to request that feature from apps, otherwise you
> will n
https://bugs.kde.org/show_bug.cgi?id=486599
--- Comment #4 from Michael Hamilton ---
(In reply to Nate Graham from comment #3)
> > The scaling leads to different on screen size in different applications
> That's the problem, yes: the DPI setting in Qt is global, not per-screen.
&g
https://bugs.kde.org/show_bug.cgi?id=486599
--- Comment #2 from Michael Hamilton ---
(In reply to Michael Hamilton from comment #0)
> ...
> When dealing with the above use cases, it could be argued that the user
> could determine their physical DPI and convert back to achieve a scale b
https://bugs.kde.org/show_bug.cgi?id=486599
--- Comment #1 from Michael Hamilton ---
Some relevant discussions:
https://discuss.kde.org/t/return-dpi-resolution-adjustments-in-font-settings-support/11860/12
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486599
Bug ID: 486599
Summary: Request for a use-native-DPI setting
Classification: Plasma
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=484606
--- Comment #9 from Michael Hamilton ---
I'm not sure if I'm seeing the same issue. I do see high CPU usage after I've
locked the session, but I only for my old/existing user login, if I try a newer
user login, then the problem does n
https://bugs.kde.org/show_bug.cgi?id=484606
Michael Hamilton changed:
What|Removed |Added
CC||mich...@actrix.gen.nz
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=436240
--- Comment #16 from Michael Hamilton ---
(In reply to Nate Graham from comment #15)
> Are you 100% positive it's the exact same issue? Including triggering steps
> as well as GPU hardware? Os so, updated reproduction steps would be
>
https://bugs.kde.org/show_bug.cgi?id=481308
Michael Hamilton changed:
What|Removed |Added
CC||mich...@actrix.gen.nz
--- Comment #62 from
https://bugs.kde.org/show_bug.cgi?id=474634
--- Comment #1 from Michael Hamilton ---
Created attachment 161682
--> https://bugs.kde.org/attachment.cgi?id=161682&action=edit
Image with bad exif that caused the issue
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474634
Bug ID: 474634
Summary: Qwenview crashes when scanning a folder
Classification: Applications
Product: gwenview
Version: 23.08.0
Platform: openSUSE
OS: Linux
Status: RE
https://bugs.kde.org/show_bug.cgi?id=414785
--- Comment #35 from Michael Hamilton ---
(In reply to Magne Djupvik from comment #34)
> I still have stutters when notifications pop up, very easily reproducible
> with e.g. Spotify changing track while playing certain games. I have a dual
&g
https://bugs.kde.org/show_bug.cgi?id=466463
--- Comment #19 from Michael Hamilton ---
(In reply to Nate Graham from comment #16)
> *** Bug 466506 has been marked as a duplicate of this bug. ***
In answer to the question from Bug 466506:
> Can you try again with Plasma 5.27.2? We remove
https://bugs.kde.org/show_bug.cgi?id=466463
--- Comment #18 from Michael Hamilton ---
(In reply to Michal Hlavac from comment #4)
> Thanks Luca, would be really great to have it in 5.27.2, anyway maybe a kind
> of workaround for GTK3+ & java applications is to run:
>
> GDK
https://bugs.kde.org/show_bug.cgi?id=466506
--- Comment #2 from Michael Hamilton ---
(In reply to Nate Graham from comment #1)
> Can you try again with Plasma 5.27.2? We removed some unnecessary font size
> handling stuff in that bugfix release.
Will do when 5.27.2 makes in to Tumb
https://bugs.kde.org/show_bug.cgi?id=466506
Bug ID: 466506
Summary: With two different DPI monitors, to achieve the same
font sizes as 5.26.*, I have to disable the GNOME/GTK
Settings Synchronisations Service.
Classification: Plasm
https://bugs.kde.org/show_bug.cgi?id=452627
Michael Hamilton changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=442380
--- Comment #112 from Michael Hamilton ---
(In reply to Kishore Gopalakrishnan from comment #111)
> (In reply to Michael Hamilton from comment #110)
> > Is there a journal message that confirms systemd boot is now responsible for
> >
https://bugs.kde.org/show_bug.cgi?id=442380
--- Comment #110 from Michael Hamilton ---
OpenSUSE tumbleweed is now on 5.25.2. I removed ~/.config/startkderc which did
contain [General] systemdBoot=false. I checked the value of kreadconfig5
--group General --key systemdBoot - it reports
https://bugs.kde.org/show_bug.cgi?id=442380
Michael Hamilton changed:
What|Removed |Added
CC||mich...@actrix.gen.nz
--- Comment #96 from
https://bugs.kde.org/show_bug.cgi?id=452627
--- Comment #3 from Michael Hamilton ---
(In reply to Kai Uwe Broulik from comment #2)
> Thanks for your effort! You may restart plasmashell (Type "plasmashell
> --replace" into krunner) to reload the notification system.
Thanks, th
https://bugs.kde.org/show_bug.cgi?id=452627
--- Comment #1 from Michael Hamilton ---
Created attachment 148166
--> https://bugs.kde.org/attachment.cgi?id=148166&action=edit
Test python script, creates a notification and updates it twice.
This python script tests the same error, but
https://bugs.kde.org/show_bug.cgi?id=452627
Bug ID: 452627
Summary: The notification system can become corrupted -
notifications fail to update
Product: frameworks-knotifications
Version: 5.93.0
Platform: openSUSE RPMs
https://bugs.kde.org/show_bug.cgi?id=414785
--- Comment #32 from Michael Hamilton ---
(In reply to Carlo Meijer from comment #29)
> I managed to work around the problem by means of the solution proposed here,
> number 2 (Disabling KWIN Vsync and force full composition pipeline):
&
https://bugs.kde.org/show_bug.cgi?id=447956
--- Comment #3 from Michael Hamilton ---
(In reply to Vlad Zahorodnii from comment #2)
> Can't reproduce the issue on my machine with an amd video card. KWin clears
> the decoration texture with # color after creating the texture, it
https://bugs.kde.org/show_bug.cgi?id=447956
--- Comment #1 from Michael Hamilton ---
I should note that in the screenshot I attached, the notification that
corrupted the title bar has already timed out and dismissed itself, so it is
not visible.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=447956
Bug ID: 447956
Summary: Wayland: inverted DBUS-notifications appear in app
title bar
Product: kwin
Version: 5.23.4
Platform: openSUSE RPMs
OS: Linux
St
https://bugs.kde.org/show_bug.cgi?id=436240
Michael Hamilton changed:
What|Removed |Added
CC||mich...@actrix.gen.nz
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=443696
Bug ID: 443696
Summary: notices with expire times consume a lot of cpu and
make the desktop unresponsive
Product: plasmashell
Version: 5.22.5
Platform: openSUSE RPMs
https://bugs.kde.org/show_bug.cgi?id=332512
--- Comment #102 from Michael Hamilton ---
(In reply to apache from comment #101)
> @Michael Hamilton
>
> > arguably showing an appalling lack of sensibility to real-world usability
> > in the age of 4K monitors
>
> You h
https://bugs.kde.org/show_bug.cgi?id=332512
--- Comment #100 from Michael Hamilton ---
(In reply to Guido Schmidt from comment #99)
> No Michael, this bug is not about kickoff only, it's about the plasmoids
> in general that are attached to the startmenu. For instance the folder
&g
https://bugs.kde.org/show_bug.cgi?id=332512
Michael Hamilton changed:
What|Removed |Added
CC||mich...@actrix.gen.nz
--- Comment #98 from
https://bugs.kde.org/show_bug.cgi?id=416728
Bug ID: 416728
Summary: Konsole with multiple tabs pops up an N open terminals
warning on logout or shutdown.
Product: konsole
Version: 19.12.1
Platform: openSUSE RPMs
https://bugs.kde.org/show_bug.cgi?id=395779
Bug ID: 395779
Summary: Application 'kdeinit5' crashing...
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Keywords: drkonq
49 matches
Mail list logo
