[dolphin] [Bug 466978] dolphin crash report

[Timothy]

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

Timothy  changed:

   What|Removed |Added

 CC||accounts.kdebugs@tec.tecosa
   ||ur.net

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

[dolphin] [Bug 466978] dolphin crash report

[Timothy]

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

--- Comment #2 from Timothy  ---
Created attachment 157476
  --> https://bugs.kde.org/attachment.cgi?id=157476&action=edit
New crash information added by DrKonqi

dolphin (22.12.3) using Qt 5.15.8

I've been noticing this for a few months now, but intermittently, seemingly at
random, dolphin will segfault. I have not been able to reliably reproduce this
issue, but thought I might as well finally get around to reporting it.

-- Backtrace (Reduced):
#5  0x7f4d63cb0388 in UpdateItemStatesThread::run (this=0x55fd4ecd8f80) at
/usr/src/debug/dolphin-22.12.3/src/views/versioncontrol/updateitemstatesthread.cpp:41
#6  0x7f4d618f5e3d in QThreadPrivate::start (arg=0x55fd4ecd8f80) at
thread/qthread_unix.cpp:330
#7  0x7f4d61293615 in start_thread (arg=) at
pthread_create.c:444
#8  0x7f4d61319c60 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
#1  0x7f4d5f91bdbe in g_main_context_poll (priority=,
n_fds=1, fds=0x7f4d280029e0, timeout=, context=0x7f4d28000c30)
at ../glib/gmain.c:4553

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

[dolphin] [Bug 466978] dolphin crash report

[Timothy]

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

Timothy  changed:

   What|Removed |Added

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

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

[Breeze] [Bug 468683] New: Icon request: text/julia

[Timothy]

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

Bug ID: 468683
   Summary: Icon request: text/julia
Classification: Plasma
   Product: Breeze
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: accounts.kdeb...@tec.tecosaur.net
CC: kain...@gmail.com, m...@nueljl.in
  Target Milestone: ---

Hello,

It would be great if the text/julia MIME type (added in this Freedesktop
commit: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/fea642e9)
could have an icon added :)

Relevant graphical material: https://github.com/JuliaLang/julia-logo-graphics

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

[plasmashell] [Bug 475507] Add option to only minimize current desktop's windows

[Timothy]

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

--- Comment #2 from Timothy  ---
I was glad to hear this makes sense and looks like a straightforward change. Do
you think there's much chance of somebody picking this up? For people with
setups like mine, I think it would be a pretty good QoL improvement and I'm
afraid I haven't the background/time to give this a shot myself.

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

[dolphin] [Bug 444290] New: It would be nice to customise git status icons and the emphasis text colour

[Timothy]

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

Bug ID: 444290
   Summary: It would be nice to customise git status icons and the
emphasis text colour
   Product: dolphin
   Version: 21.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: plugins: git
  Assignee: sebast...@sebastian-doerner.de
  Reporter: tecosau...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Hello! I've just discovered the dolphin-plugins' git plugin, and it's rather
nice getting an indication of which files are tracked, have unstaged changes,
etc. 

However, I find myself wanting to get rid of the file name colouring** and
change the unstaged changes icon*. It doesn't seem like there's currently a way
to set these in dolphin's config — I think it would be rather nice if it would
be possible. This is definitely a wishlist item, but it would be cool to be
able to tweak this :)

Thanks for all the great work so far,
Timothy.


* I imagine this may vary based on the user icon theme, but for me this shows
up as a purple exclamation mark, which seems a bit over-dramatic just for
unstaged changes.

** The colour of the green used for the text is clearly different to the shade
of green used for the "all up to date" check icon, which clashes with my visual
sensibilities.

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

[akregator] [Bug 427406] New: Detaching tab causes crash

[Timothy]

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

Bug ID: 427406
   Summary: Detaching tab causes crash
   Product: akregator
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: timothy.m.butterwo...@gmail.com
  Target Milestone: ---

Application: akregator (5.9.3)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 5.4.0-0.bpo.4-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

-- Information about the crash:
- What I was doing when the application crashed: I was detaching a tab at which
point the application crashed.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7000a63c80 (LWP 3675))]

Thread 27 (Thread 0x7f6f1b96d700 (LWP 13362)):
#0  0x7f700f0a53f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f70119c4847 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f70119c710a in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f70119c71f2 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f70119cb781 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f70119ccc61 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f70119d5971 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f700f09efa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f701666b4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 26 (Thread 0x7f6efa963700 (LWP 7613)):
#0  0x7f701660a20a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f70165a6540 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7f70165a4454 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x7f70165a3d8b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x7f70165f9f2c in strerror_r () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x7f70165f9e4f in strerror () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x7f700caefc21 in event_warn () from
/lib/x86_64-linux-gnu/libevent-2.1.so.6
#7  0x7f700caf1588 in ?? () from /lib/x86_64-linux-gnu/libevent-2.1.so.6
#8  0x7f700cae7329 in event_base_loop () from
/lib/x86_64-linux-gnu/libevent-2.1.so.6
#9  0x7f7011999529 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f70119b8afb in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#11 0x7f70119d9eeb in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#12 0x7f70119d5971 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#13 0x7f700f09efa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#14 0x7f701666b4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 25 (Thread 0x7f6ef760a700 (LWP 4912)):
#0  0x7f700f0a53f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f70119c4847 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f70119c710a in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f70119c71f2 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f70119cb781 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f70119ccc61 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f70119d5971 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f700f09efa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f701666b4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 24 (Thread 0x7f6f1b16c700 (LWP 4884)):
#0  0x7f700f0a500c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f70119c4779 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f70119c7118 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f70119c71af in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f70119cb798 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f70119cca7f in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f70119d5971 in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f700f09efa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f701666b4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 23 (Thread 0x7f6f1700 (LWP 3706)):
#0  0x7f701667871b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f701667a4e4 in __fprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7f700caefa5a in event_logv_ () from
/lib/x86_64-linux-gnu/libevent-2.1.so.6
#3  0x7f700caefc34 in event_wa

[khelpcenter] [Bug 474718] linuxfx does not look like windows 11

[Timothy]

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

--- Comment #1 from Timothy  ---
kde-doc-engl...@kde.org is a distribution list for documentation not end
user support.

KDE Plasma is not a Windows clone! KDE does not provide Windows logos as
that would be copy right infringement. Similarities between KDE Plasma
Desktop and Windows 11 are not intentional as KDE has had the same look and
feel UI since Plasma 4 (2007).

If you are looking for an Open Source Windows clone then you should try
ReactOS https://reactos.org/

Happy Hacking

Tim

On Wed, Sep 20, 2023 at 12:40 AM George  wrote:

> https://bugs.kde.org/show_bug.cgi?id=474718
>
> Bug ID: 474718
>Summary: linuxfx does not look like windows 11
> Classification: Applications
>Product: khelpcenter
>Version: unspecified
>   Platform: Other
> OS: Linux
> Status: REPORTED
>   Severity: critical
>   Priority: NOR
>  Component: general
>   Assignee: kde-doc-engl...@kde.org
>   Reporter: heavymetaldude1...@yahoo.com
>   Target Milestone: ---
>
> i downloaded linuxfx 11.4.1 Redsand and purchased a license key but when i
> try
> to customize it to look like windows 11 the icons still look like linux.
> Not
> even the windows logo anywere. Pls help me with this problem thank u. have
> a
> nice night.
>
>   George
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

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

[kwin] [Bug 475495] New: Request: keyboard shortcut for moving window across tiles

[Timothy]

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

Bug ID: 475495
   Summary: Request: keyboard shortcut for moving window across
tiles
Classification: Plasma
   Product: kwin
   Version: 5.27.8
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Custom Tiling
  Assignee: kwin-bugs-n...@kde.org
  Reporter: accounts.kdeb...@tec.tecosaur.net
CC: notm...@gmail.com
  Target Milestone: ---

At the moment Kwin has keybindings for quick-tiling a window the the
left/right/top/bottom, it would be rather nice if similar keybindings existed
for moving a tilled window into the tile to the left/right/above/below.

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

[plasmashell] [Bug 475507] New: Add option to only minimize current desktop's windows

[Timothy]

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

Bug ID: 475507
   Summary: Add option to only minimize current desktop's windows
Classification: Plasma
   Product: plasmashell
   Version: 5.27.8
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Show Desktop/Minimize All
  Assignee: plasma-b...@kde.org
  Reporter: accounts.kdeb...@tec.tecosaur.net
  Target Milestone: 1.0

Sometimes a particular virtual desktop becomes a tad cluttered, and I'd like to
minimise the windows currently open *on that desktop*. Currently, the "minimise
all windows" applet acts across all desktops. A simple configuration checkbox
to change the targetted desktops to be "all" or "current" would be a
much-appreciated piece of functionality for me (and perhaps others?).

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

[Breeze] [Bug 425836] New: Request icon for Org documents

[Timothy]

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

Bug ID: 425836
   Summary: Request icon for Org documents
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: tecosau...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

Created attachment 131203
  --> https://bugs.kde.org/attachment.cgi?id=131203&action=edit
Org files

I would like to request that there be an icon for Org files.

Other than visual nicety I'd find this particularly helpful as .org files can
be exported to a wide range of formats, and result in a large number of files
being produced. Not having a distinct icon makes it hard to identify the
'source' .org file in many cases (see attachment).

File type: Org-mode (.org)
Icon Name: text-org
Description: A plain text markup format that's been around for 17 years.
Designed in Emacs but there are extensions for many other editors.
Webpage: https://orgmode.org/
Original Icon: https://orgmode.org/img/org-mode-unicorn.png

On a system with Org registered as a file type, one finds the following (which
may be useful)

$ gio info -a standard::icon ~/.org/todo.org
  standard::icon: text-org, text-x-generic, text-org-symbolic,
text-x-generic-symbolic

$ xdg-mime query filetype ~/.org/todo.org
text/org

Example implementation:
https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/blob/master/Papirus/64x64/mimetypes/text-org.svg

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

[Breeze] [Bug 425836] Request icon for Org documents

[Timothy]

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

--- Comment #9 from Timothy  ---
Thanks for your effort Jens - it's fantastic to see something actually come of
this. Two minor criticisms if you don't mind:
 - The mane line looks overly jagged to me
 - The horn seems to thin and spindly

Thanks again for your work :)

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

[KScreen] [Bug 490744] New: When using the color-management feature on external monitors, it seems that this causes the idle power draw to increase substantially, making the entire system run hotter o

[Timothy]

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

Bug ID: 490744
   Summary: When using the color-management feature on external
monitors, it seems that this causes the idle power
draw to increase substantially, making the entire
system run hotter overall. This does not happen when
using  the built-in laptop screen only.
Classification: Plasma
   Product: KScreen
   Version: 6.1.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: timot...@tutanota.com
  Target Milestone: ---

Created attachment 171947
  --> https://bugs.kde.org/attachment.cgi?id=171947&action=edit
Display settings with with idle power draw. Left without ICC, right with ICC
profile

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When using the color-management feature on external monitors, it seems that
this causes the idle power draw to increase substantially, making the entire
system run hotter overall. This does not happen when using  the built-in laptop
screen only. 

STEPS TO REPRODUCE
1.  Connect external Monitor
2.  Select ICC profile in Display settings

OBSERVED RESULT
Idle power draw triples

EXPECTED RESULT
Power draw stays the same


SOFTWARE/OS VERSIONS
Linux: 6.9.9-1
KDE Plasma Version: 6.1.2  
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
The Laptop is a Tuxedo InfinityBook Pro 14 gen 8 with Nvidia 3050 GPU. The bug
occurs when running in dedicated GPU mode and with integrated graphics.

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

[KScreen] [Bug 490744] tripled idle power draw when using ICC profile on external monitor

[Timothy]

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

Timothy  changed:

   What|Removed |Added

Summary|When using the  |tripled idle power draw
   |color-management feature on |when using ICC profile on
   |external monitors, it seems |external monitor
   |that this causes the idle   |
   |power draw to increase  |
   |substantially, making the   |
   |entire system run hotter|
   |overall. This does not  |
   |happen when using  the  |
   |built-in laptop screen  |
   |only.   |

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

[kdeconnect] [Bug 491609] New: Android album art not seen on desktop

[Timothy]

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

Bug ID: 491609
   Summary: Android album art not seen on desktop
Classification: Applications
   Product: kdeconnect
   Version: 24.05.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: accounts.kdeb...@tec.tecosaur.net
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY

On one KDE computer I've connected my android phone to over a VPN, the album
art of media playing on the android device is not transferred over.

STEPS TO REPRODUCE
1. Connect phone and desktop over a VPN
2. Play media on phone
3. Observe lack of art on desktop

OBSERVED RESULT

```
~$ dbus-send --print-reply
--dest=org.mpris.MediaPlayer2.kdeconnect.mpris_e53ec9e64972478189e9b4502aa6ba4c
/org/mpris/MediaPlayer2 org.freedesktop.DBus.Properties.Get
string:'org.mpris.MediaPlayer2.Player' string:'Metadata'

method return time=1723450577.022262 sender=:1.1936 -> destination=:1.1942
serial=132 reply_serial=2
   variant   array [
 dict entry(
string "mpris:length"
variantint64 18400
 )
 dict entry(
string "mpris:trackid"
variantobject path "/org/mpris/MediaPlayer2"
 )
 dict entry(
string "xesam:album"
variantstring "Iechyd Da"
 )
 dict entry(
string "xesam:artist"
variantarray [
  string "Bill Ryder-Jones"
   ]
 )
 dict entry(
string "xesam:title"
variantstring "I Hold Something In My Hand"
 )
  ]
```

EXPECTED RESULT

I expected mpris:artUrl to be supplied.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 24.05.2
Qt Version: 6.7.2

ADDITIONAL INFORMATION

To get more information, I restarted kdeconnectd with info logs enabled:

```
~$ QT_LOGGING_RULES="*.info=true; *.debug=true; qt.*.debug=false" kdeconnectd
--replace &!

2024-08-12T16:19:26 kdeconnect.core: Daemon starting
2024-08-12T16:19:26 kf.coreaddons: Checking for plugins in
QList("/usr/bin/kdeconnect", "/usr/lib64/qt6/plugins/kdeconnect")
2024-08-12T16:19:26 kdeconnect.core: Broadcasting identity packet
2024-08-12T16:19:26 kdeconnect.core: Sending announce
2024-08-12T16:19:26 kdeconnect.core: Opening socket for address
QHostAddress("172.28.137.194")
2024-08-12T16:19:26 kdeconnect.core: Opening socket for address6
QHostAddress("fe80::e08f:1673:23b8:7ef%enp67s0")
2024-08-12T16:19:26 kdeconnect.core: Opening socket for address
QHostAddress("172.17.0.1")
2024-08-12T16:19:26 kdeconnect.core: Opening socket for address
QHostAddress("100.64.0.3")
2024-08-12T16:19:26 kdeconnect.core: Opening socket for address6
QHostAddress("fe80::d502:7775:e694:1e74%tailscale0")
2024-08-12T16:19:26 kdeconnect.core: Opened 5 sockets to listen for MDNS query
responses
2024-08-12T16:19:26 kdeconnect.core: Sending MDNS query for service
"_kdeconnect._udp.local"
2024-08-12T16:19:26 kdeconnect.core: Sending mDNS query via socket 32
2024-08-12T16:19:26 kdeconnect.core: Sending mDNS query via socket 33
2024-08-12T16:19:26 kdeconnect.core: Sending mDNS query via socket 34
2024-08-12T16:19:26 kdeconnect.core: Sending mDNS query via socket 35
2024-08-12T16:19:26 kdeconnect.core: Sending mDNS query via socket 36
2024-08-12T16:19:26 kdeconnect.core: LanLinkProvider started
2024-08-12T16:19:26 kdeconnect.core: Daemon started
2024-08-12T16:19:26 kdeconnect.core: Discovered myself, ignoring
2024-08-12T16:19:29 kdeconnect.core: TCP connection done (i'm the existing
device)
2024-08-12T16:19:29 kdeconnect.core: Starting server ssl (I'm the client TCP
socket)
2024-08-12T16:19:30 kdeconnect.core: Socket successfully established an SSL
connection
2024-08-12T16:19:30 kdeconnect.core: Device discovered
"cf4d1fdb_11fb_437a_939f_268549cb9a55" via link with priority 20
2024-08-12T16:19:30 kdeconnect.core: It is a known device "Pixel 8"
2024-08-12T16:19:30 kdeconnect.core: Not loading plugin
"kdeconnect_remotesystemvolume" because device doesn't support it
2024-08-12T16:19:30 kdeconnect.core: Not loading plugin
"kdeconnect_virtualmonitor" because device doesn't support it
2024-08-12T16:19:30 kdeconnect.core: Not loading plugin "kdeconnect_lockdevice"
because device doesn't support it
2024-08-12T16:19:30 kdeconnect.core: Not loading plugin "kdeconnect_bigscreen"
because this device of type "desktop" is not supported. Supports: "tv"
2024-08-12T16:19:30 kdeconnect.core: Not loading plugin
"kdeconnect_remotecommands" because device doesn't support it
2024-08-12T16:19:30 default: new capabilities for  "Pixel 8"
2024-08-12T16:19:30 kdeconnect.core: "Pixel 8" - reload plugins
2024-08-12T16:1

[kdeconnect] [Bug 491609] Android album art not seen on desktop

[Timothy]

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

--- Comment #2 from Timothy  ---
(In reply to cwo from comment #1)
> Thank you for the feature request!
> 
> Support for sending album art from phone to pc was added a week ago, see
> this merge request:
> https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/541

Ah oops, thanks for clarifying the situation. I saw that MR and based on the "1
year ago" at the top assumed it must have made its way into the last release by
now. Now I see that's just the creation date not the merge date...

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

[frameworks-kio] [Bug 419434] Folders without sub-folders are not expandable in the TreeView the "Filesystem Browser"

[Timothy]

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

Timothy  changed:

   What|Removed |Added

 CC||timothy.gouskov@protonmail.
   ||com

--- Comment #1 from Timothy  ---
I have the same problem. I found a workaround on one of my computers though. I
installed Kate via Flatpak, and it's running version 19.12.3. The KDE
frameworks is 5.67.0. The Qt is 5.14.1 (built against 5.14.1).

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

[digikam] [Bug 393577] New: Implement Camera colour profiles from X-Rite colorchecker passport Software - similar to Lightroom/PS

[Timothy]

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

Bug ID: 393577
   Summary: Implement Camera colour profiles from X-Rite
colorchecker passport Software - similar to
Lightroom/PS
   Product: digikam
   Version: unspecified
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ImageEditor-WishForNewTools
  Assignee: digikam-bugs-n...@kde.org
  Reporter: tskinne...@hotmail.com
  Target Milestone: ---

Created attachment 112287
  --> https://bugs.kde.org/attachment.cgi?id=112287&action=edit
Profile for 5D and lens no ND

I use X-Rite colorchecker passport with Lightroom to calibrate my cameras and
lenses so that I can control the colours far more accurately than the built in
profiles from both Canon and Adobe. It also removes the colour cast from ND
filters amazingly, because it uses a standard colour board to work out how the
colours should be. Currently, I have not found any software besides Adobe, that
can use these profiles created by the colorchecker software. It is the only
real reason that I must stick with Lightroom for now. It would be a very good
addition to your software. 

I am happy to aid in the implementation. I have 3 Canon cameras - 40D, 7D & 5D
MKIII  - my family have 600D and I have profiled all of them and the lenses/ND
filters I use. I can provide you with the profile files to inspect their
properties and figure out how they could possibly be implemented. ;-) 

I'm sure there are other users of your software that will have the colorchecker
passport that could help as well. :-)

Thank you or your consideration.

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

[kdenlive] [Bug 388122] New: Feature Request - Video Splitter Clip Maker

[Timothy]

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

Bug ID: 388122
   Summary: Feature Request - Video Splitter Clip Maker
   Product: kdenlive
   Version: 17.12.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: timothy.m.butterwo...@gmail.com
  Target Milestone: ---

Please produce an easy to use front end designed to simply split videos into
clips similiar to Easy Video Splitter http://www.doeasier.org/splitter/.

I always have issues splitting videos in kdenlive and all the extra
functionality creates a lot of confusion for folks not needing full linear
editing capabilities.

A simple to use wizard would also work as well.

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

[krita] [Bug 389900] New: Feature Request - Direct Draw Surface DDS, openGL Normal Mapping, NIF 3D Model Import

[Timothy]

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

Bug ID: 389900
   Summary: Feature Request - Direct Draw Surface DDS, openGL
Normal Mapping, NIF 3D Model Import
   Product: krita
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: timothy.m.butterwo...@gmail.com
  Target Milestone: ---

Krita is great.

I would like to use it for texturing 3D models for modding video games. In
order to do this it would need Direct Draw Surface DDS file format
import/export. The ability to generate openGL Normal Maps (Bump Mapping) and
amazingly if it can be done the ability to load NIF NetImerse File Format and
OSG Open Scene Graph 3D models so textures can be painted directly on the 3D
model. I don't even know if the last part their is even possible as I just make
small modifications to textures not using GIMP. GIMP has Open Source Plugins
for DDS and Normal Mapping, OSG is open source, NIF specification was leaked in
Python a few years ago and open source project like NifSkope current exist for
modifying the 3D models but their is nothing that can load the 3D model and
allow painting the textures directly on top of it.

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

[ktorrent] [Bug 384476] New: Ktorrent Crashes on shutdown

[Timothy]

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

Bug ID: 384476
   Summary: Ktorrent Crashes on shutdown
   Product: ktorrent
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: timothy.m.butterwo...@gmail.com
  Target Milestone: ---

Application: ktorrent (5.1.0)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.10.0-33-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed:

I exited the application using the system tray icon. It seems to happen each
and every time since KDE Neon updaged to the latest Ktorrent 17.08

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f43ef2d38c0 (LWP 24494))]

Thread 6 (Thread 0x7f43c796a700 (LWP 15742)):
#0  0x7f43f0942d86 in pa_pstream_ref () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7f43f0943781 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7f43f094401a in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0x7f43f5d950b7 in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f43f5d954bc in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f43f5d95560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f43f5da37a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f43f0954078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0x7f43f8b4a6ba in start_thread (arg=0x7f43c796a700) at
pthread_create.c:333
#9  0x7f43fca053dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f43c1feb700 (LWP 24657)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f43fd6188eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1b94650) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x1bb6ba8,
mutex=mutex@entry=0x1bb6ba0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f44012c2d13 in net::ReverseResolverThread::run (this=0x1bb6b90) at
/workspace/build/src/net/reverseresolver.cpp:124
#4  0x7f43fd617989 in QThreadPrivate::start (arg=0x1bb6b90) at
thread/qthread_unix.cpp:368
#5  0x7f43f8b4a6ba in start_thread (arg=0x7f43c1feb700) at
pthread_create.c:333
#6  0x7f43fca053dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f43e5427700 (LWP 24499)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f43fc9f5242 in read () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f43f71246f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f43f70e0e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f43f70e1330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f43f70e149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f43fd84094b in QEventDispatcherGlib::processEvents
(this=0x7f43dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f43fd7e97ca in QEventLoop::exec (this=this@entry=0x7f43e5426d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7f43fd612cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#9  0x7f43fd617989 in QThreadPrivate::start (arg=0xbd72b0) at
thread/qthread_unix.cpp:368
#10 0x7f43f8b4a6ba in start_thread (arg=0x7f43e5427700) at
pthread_create.c:333
#11 0x7f43fca053dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f43e6e39700 (LWP 24497)):
#0  0x7f43fc9f970d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f43f70e138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f43f70e149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f43fd84094b in QEventDispatcherGlib::processEvents
(this=0x7f43e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f43fd7e97ca in QEventLoop::exec (this=this@entry=0x7f43e6e38cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f43fd612cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f43fe66bb75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f43fd617989 in QThreadPrivate::start (arg=0x7f43fe6e1da0) at
thread/qthread_unix.cpp:368
#8  0x7f43f8b4a6ba in start_thread (arg=0x7f43e6e39700) at
pthread_create.c:333
#9  0x

[ark] [Bug 381966] New: Bethesda Software Archive

[Timothy]

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

Bug ID: 381966
   Summary: Bethesda Software Archive
   Product: ark
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: timothy.m.butterwo...@gmail.com
CC: rthoms...@gmail.com
  Target Milestone: ---

Please incorporate the ability to browse, extract and pack files into Bethesda
Software Archive BSA container format. This would be really useful with openMW
modding using openCS.

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

[ark] [Bug 381966] Bethesda Software Archive

[Timothy]

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

--- Comment #1 from Timothy  ---
Here is a like to the BSA File Format.

http://web.archive.org/web/20070429221314/http://www34.brinkster.com:80/ghostwheel/TES3_BSA_File_Format.htm

Full C++ source code is located here:
http://www34.brinkster.com/ghostwheel/bsapack.zip.

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

[kwin] [Bug 494382] KDE 6.2 with lag when moving windows with ICC profiles

[Timothy]

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

Timothy  changed:

   What|Removed |Added

 CC||hahnt9...@gmail.com
   Platform|Fedora RPMs |Arch Linux

--- Comment #21 from Timothy  ---
I am seeing this on EndeavourOS. Since upgrading  'plasma-desktop 6.2.0-1' I
have been experiencing major lag/latency when dragging windows as well as icons
(directories or individual files in dolphin/on the desktop). As others have
reported it seems to resolve itself when I disable the night light. I have a
single 3440x1440 monitor to my laptop (with screen disabled) and no ICC
profile(s) configured.

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

[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login

[Timothy B]

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

--- Comment #94 from Timothy B  ---
I just updated Plasma to 5.24.1 on both my Manjaro PCs, and I can confirm this
bug as soon as I log in. Luckily, the older workaround described in comment #49
works like a charm with this version of Plasma. I haven't tried the newer
workaround described in comment #87, but I think the older one is less likely
to fail at least for me.

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

[kwin] [Bug 444243] Notifications disappear below current window on click

[Timothy B]

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

--- Comment #12 from Timothy B  ---
This is still happening as of Plasma 5.24.1, and it's really annoying. Any
update on this?

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

[systemsettings] [Bug 403580] KCM shows invalid locales and allows them to be chosen, which can break various parts of the system

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kwin] [Bug 466010] New: Task Bar Window Preview Position Breaks on Windows with Player Controls

[Timothy Arnold]

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

Bug ID: 466010
   Summary: Task Bar Window Preview Position Breaks on Windows
with Player Controls
Classification: Plasma
   Product: kwin
   Version: 5.27.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tima...@proton.me
  Target Milestone: ---

Created attachment 156443
  --> https://bugs.kde.org/attachment.cgi?id=156443&action=edit
Window Preview image is drawn over the task bar

SUMMARY

STEPS TO REPRODUCE
1.  Open Firefox and go to a webpage that has content playing that allows for
controls
2.  Click off of the window onto any other window
3.  Use your mouse hover over the Firefox task bar icon (must be the first icon
the mouse hovers for preview) to see the window preview.

OBSERVED RESULT

The position of the window preview gets redrawn directly over the top of the
task bar icon. (See attachment for an image) Additionally, the next icon you
hover over has a window preview that is far above the task bar. 

EXPECTED RESULT

The window preview should be drawn directly on the top border of the task bar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 37 
(available in About System)
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 590 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS GAMING 7 WIFI

ADDITIONAL INFORMATION

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

[kwin] [Bug 466010] Task Bar Window Preview Position Breaks on Windows with Player Controls

[Timothy Arnold]

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

--- Comment #1 from Timothy Arnold  ---
Created attachment 156444
  --> https://bugs.kde.org/attachment.cgi?id=156444&action=edit
Subsequent Window Preview is Elevated

This is an image of the subsequent window preview

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

[yakuake] [Bug 468760] New: Frozen Terminal at Start Up

[Timothy Arnold]

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

Bug ID: 468760
   Summary: Frozen Terminal at Start Up
Classification: Applications
   Product: yakuake
   Version: 22.12.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: tima...@proton.me
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

System: Fedora 38 KDE

STEPS TO REPRODUCE
1. Reboot computer
2. Login
3. Use the F12 shortcut key to open the terminal
4. Begin Typing 

OBSERVED RESULT
No input is seen in the Yakuake terminal. This is shortly after the Fedora 37
-> 38 upgrade.

In order for Yakuake to be responsive again, you must close Yakuake and reopen.

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.

[frameworks-plasma] [Bug 438644] Broken corners on pop-ups, dialogs, applets, and tooltips

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #50 from Timothy B  ---
It's still happening for me randomly but it's very inconsistent to reproduce.
Every night I would turn off my monitor and leave the computer running, and the
next day I would see broken corners on all Plasma tooltips, popouts, and OSDs
after turning on the monitor as if the fixes never existed. It would go away
after I run `rm -rf ~/.cache/plasma*` in the terminal and then restart
plasmashell and/or KWin, but then again the broken corners come back after a
few days.

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Graphics Platform: X11
Graphics Processor: AMD Radeon RX 570 Series
Graphics Driver: AMDGPU (Mesa 23.0.3)

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

[yakuake] [Bug 468760] Yakuake terminal not receiving keyboard input at startup

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

Summary|Frozen Terminal at Start Up |Yakuake terminal not
   ||receiving keyboard input at
   ||startup

--- Comment #1 from Timothy Arnold  ---
It appears that this issue has to do with an interaction with IBus being
started prior to a particular process for plasmashell or some other desktop
environment setup program.

In order to resolve this, I had to add a 3 second delay to the IBus script.
(Aside: The reason I'm using IBus instead of fcitx is that Ibus has better
support for certain asian languages which I switch between.)

Below is startup script I have now for starting the IBus daemon. It is run
using the `Autostart` settings in System settings.
```
#!/bin/sh
sleep 3
ibus-daemon -drxR
```

I'm still not clear on which program the ibus-daemon is waiting on in order to
properly start but this appears to be what was causing the Yakuake not
receiving input (initially I thought it was frozen but it appears to have just
been the keyboard input that wasn't working).

If anyone has any idea on how I can determine what the background process the
ibus-daemon needs to wait on, please let me know.

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

[yakuake] [Bug 468760] Yakuake terminal not receiving keyboard input at startup

[Timothy Arnold]

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

--- Comment #2 from Timothy Arnold  ---
I just noticed that I didn't fill out the form completely when I submitted
this:

EXPECTED RESULT
Yakuake should receive input from the keyboard on startup

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.13-300.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 590 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS GAMING 7 WIFI

ADDITIONAL INFORMATION

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

[kdevelop] [Bug 460025] New: When trying to generate makefile, I'm getting errors about not being able to link against KDev::Tests

[Timothy Hutchins]

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

Bug ID: 460025
   Summary: When trying to generate makefile, I'm getting errors
about not being able to link against KDev::Tests
Classification: Applications
   Product: kdevelop
   Version: git master
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Language Support: CSS
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: tgh6...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Clone the repository (commit: d9162558095a5ee8a6f82591c292e5e599bd7f6c)
2. Make a build directory (mkdir build && cd build)
3. Run cmake ..

OBSERVED RESULT
I get a bunch of errors about a bunch of targets trying to link against target
KDev::Tests but it could not be found.

EXPECTED RESULT
It generates the makefile.

SOFTWARE/OS VERSIONS
Windows: None
macOS: None
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
According to this mail archive I will show below, by default, the KDev::Tests
target is only built when BUILD_TESTING is enabled using CMake with KDevelop.
With that information, the only way to get the target is to build kdevelop from
source with that enabled.

https://www.mail-archive.com/search?l=kde-bugs-dist@kde.org&q=subject:%22%5C%5Bkdevplatform%5C%5D+%5C%5BBug+409951%5C%5D+Missing+component+KDev%5C%3A%5C%3ATests+required+for+Umbrello%22&o=newest&f=1

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

[kdevelop] [Bug 460025] When trying to generate makefile, I'm getting errors about not being able to link against KDev::Tests

[Timothy Hutchins]

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

--- Comment #2 from Timothy Hutchins  ---
(In reply to Igor Kushnir from comment #1)
> Which project are you trying to build?
> d9162558095a5ee8a6f82591c292e5e599bd7f6c does not refer to a commit in
> KDevelop repository.

I am trying to build the kdev-css language support addon.

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

[kdevelop] [Bug 460025] When trying to generate makefile, I'm getting errors about not being able to link against KDev::Tests

[Timothy Hutchins]

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

--- Comment #3 from Timothy Hutchins  ---
(In reply to Timothy Hutchins from comment #2)
> (In reply to Igor Kushnir from comment #1)
> > Which project are you trying to build?
> > d9162558095a5ee8a6f82591c292e5e599bd7f6c does not refer to a commit in
> > KDevelop repository.
> 
> I am trying to build the kdev-css language support addon.

This is the relevant repository: https://invent.kde.org/kdevelop/kdev-css

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

[kdevelop] [Bug 460025] When trying to generate makefile, I'm getting errors about not being able to link against KDev::Tests

[Timothy Hutchins]

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

--- Comment #5 from Timothy Hutchins  ---
(In reply to Igor Kushnir from comment #4)
> 1. Doesn't Ubuntu provide a package with KDev::Tests?
> 2. Have you tried turning off BUILD_TESTING CMake variable in kdev-css?

1 > kdevelop provides it, but it has to be compiled from source manually with
BUILD_TESTING set to on, in the release builds that get pushed to the
repositories that option is set to off.
2 > I did try, and looked in the CMakeLists.txt file and I don't think that the
project implements that option.

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

[kdevelop] [Bug 460025] When trying to generate makefile, I'm getting errors about not being able to link against KDev::Tests

[Timothy Hutchins]

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

--- Comment #7 from Timothy Hutchins  ---
(In reply to Igor Kushnir from comment #6)
> According to kdev-css git history, it always unconditionally depended on
> KDev::Tests. So either something has changed elsewhere recently, or there is
> some issue on your system.
> > 1 > kdevelop provides it, but it has to be compiled from source manually 
> > with BUILD_TESTING set to on, in the release builds that get pushed to the 
> > repositories that option is set to off.
> I thought that Ubuntu could provide a separate (split) package with
If it is, then it must not be well documented, I tried looking and ended up
empty handed.
> KDev::Tests, but maybe it doesn't.
> > 2 > I did try, and looked in the CMakeLists.txt file and I don't think that 
> > the project implements that option.
> https://api.kde.org/ecm/module/ECMMarkAsTest.html?highlight=build_testing
> Did you reconfigure CMake after disabling BUILD_TESTING?
Yes, many times, all yealding the same result. If kdev-css depends on it, then
I believe I would have to compile KDevelop manual.
Would you possibly know what target I would have to build to build KDev::Tests
so that I won't have to build the entire thing?

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

[kdevelop] [Bug 460025] When trying to generate makefile, I'm getting errors about not being able to link against KDev::Tests

[Timothy Hutchins]

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

--- Comment #9 from Timothy Hutchins  ---
(In reply to Igor Kushnir from comment #8)
> I think you are right that something is wrong in kdev-css. See e.g.
> https://invent.kde.org/kdevelop/kdev-php/-/blob/master/parser/CMakeLists.txt
> 
> Try to enclose the test code in kdev-css/CMakeLists.txt in the `if
> (BUILD_TESTING)` block. If it works well, please create a merge request.

The issue has been resolved and a relevant merge request has been created at
https://invent.kde.org/kdevelop/kdev-css/-/merge_requests/2

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

[kwin] [Bug 433436] Cursor offset issue

[Timothy B]

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

--- Comment #16 from Timothy B  ---
(In reply to Vlad Zahorodnii from comment #14)
> In that case, given all the observations above, it seems like a driver
> issue. Please report this issue to driver (amdgpu) developers.
It looks like an issue for this exact bug has already been submitted in the
AMDGPU repository last year:
https://gitlab.freedesktop.org/drm/amd/-/issues/1968. It also mentioned bug
#447797, so this ticket is a possible duplicate.

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

[kwin] [Bug 433436] Cursor offset issue

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=447797

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

[kwin] [Bug 447797] Mouse cursor glitching upon switching states in the Wayland session

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=433436

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

[kwin] [Bug 433436] Cursor offset issue

[Timothy B]

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

--- Comment #18 from Timothy B  ---
(In reply to Jacopo Martellini from comment #17)
> (In reply to Timothy B from comment #16)
> > (In reply to Vlad Zahorodnii from comment #14)
> > > In that case, given all the observations above, it seems like a driver
> > > issue. Please report this issue to driver (amdgpu) developers.
> > It looks like an issue for this exact bug has already been submitted in the
> > AMDGPU repository last year:
> > https://gitlab.freedesktop.org/drm/amd/-/issues/1968. It also mentioned bug
> > #447797, so this ticket is a possible duplicate.
> 
> If the same thing happens both on intel and amd, couldn't it be kwin doing
> something strange?

I don't really think KWin is at fault here, since I was able to reproduce this
exact behavior with other DEs and compositors. I'm betting it has to do with
the DRM/DRI

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

[kwin] [Bug 433436] Cursor offset issue

[Timothy B]

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

--- Comment #20 from Timothy B  ---
(In reply to Jacopo Martellini from comment #19)
> Fascinating!
> May I ask you how?
All I did was moving the cursor over window borders and other UI elements where
it's expected to change states on different Manjaro editions (KDE, Gnome,
XFCE), and I took slow motion videos for each DE. I posted all my findings on
the old Manjaro forum, but unfortunately the entire site has been taken down in
the past month or so.

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

[kwin] [Bug 454658] Blur effect is badly compatible with window opacity (Meta+Scroll)

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kwin] [Bug 454658] Blur effect is badly compatible with window opacity (Meta+Scroll)

[Timothy B]

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

--- Comment #1 from Timothy B  ---
I notice this every time a Plasma tooltip, notification, or OSD fades in and
out, especially against dark backgrounds. I can also reproduce this with both
windows and Plasma panels exactly as on the video attached to the description.
But unlike the reporter, I use AMD instead of Nvidia for the GPU.

Operating System: Manjaro Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.8-1-MANJARO (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon RX 570 Series
Graphics Driver: Mesa 22.3.4

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

[plasma-pa] [Bug 457023] Applet leaks audio sinks with Pipewire and WEBRTC

[Timothy Hutchins]

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

Timothy Hutchins  changed:

   What|Removed |Added

 CC||tgh6...@gmail.com

--- Comment #7 from Timothy Hutchins  ---
Created attachment 155855
  --> https://bugs.kde.org/attachment.cgi?id=155855&action=edit
leak havoc

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

[plasma-pa] [Bug 457023] Applet leaks audio sinks with Pipewire and WEBRTC

[Timothy Hutchins]

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

--- Comment #8 from Timothy Hutchins  ---
Comment on attachment 155855
  --> https://bugs.kde.org/attachment.cgi?id=155855
leak havoc

Can confirm this happens to me

kernal: 6.1.8-arch1-1
KDE Plasma: 5.26.5
libpipewire: 0.3.65

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

[systemsettings] [Bug 488760] systemsetting crashes after opening sound twice

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

--- Comment #5 from Timothy Arnold  ---
I can reproduce this in a KDE Neon VM as well so it doesn't seem specific to
Fedora 40

KDE neon 6.0
Software:
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
QT Version: 6.7.0
Kernel Version: 6.5.0-41-generic (64-bit)
Graphics Platform: Wayland

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

[systemsettings] [Bug 434954] Support firewalld zones

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

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

[KPipeWire] [Bug 476187] OpenH264 codec support

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

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

[kwin] [Bug 455585] WindowHeap-based effects' animations aren't smooth when using a high refresh rate screen

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0
 Status|NEEDSINFO   |REPORTED

--- Comment #38 from Timothy B  ---
I finally updated to Plasma 6.1, but the choppiness in the Overview and Present
Windows effect are still there. I also noticed the same exact behavior in the
new Edit Mode interface.

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

[kwin] [Bug 455585] WindowHeap-based effects' animations aren't smooth when using a high refresh rate screen

[Timothy B]

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

--- Comment #43 from Timothy B  ---
(In reply to Nate Graham from comment #40)
> FWIW I can still reproduce this issue a bit with my hardware (HD620 iGPU +
> 4K screen @ 225% scale).

What is the refresh rate of your display? Most of us here including myself are
using displays that run at least 75 Hz.

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

[kwin] [Bug 488843] Triple buffering causing stuttering

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kwin] [Bug 455585] WindowHeap-based effects' animations aren't smooth when using a high refresh rate screen

[Timothy B]

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

--- Comment #31 from Timothy B  ---
Created attachment 163736
  --> https://bugs.kde.org/attachment.cgi?id=163736&action=edit
Overview effect with choppiness slowed down from 100Hz to 60Hz

I finally had the chance to provide video evidence of this bug. Here I slowed
the original footage from 100 FPS to 60 FPS using Avidemux and reencoded it to
make the file size fit below the 4MB limit. If you look through the video frame
by frame, you'll notice that there are missed frames in the transition going in
and out of the Overview effect. Every 2-3 frames appear to be a duplicate of
the previous one, which indicates that the effect ran about 60 FPS instead of
the expected 100.

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

[kwin] [Bug 455585] WindowHeap-based effects' animations aren't smooth when using a high refresh rate screen

[Timothy B]

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

--- Comment #32 from Timothy B  ---
Created attachment 163737
  --> https://bugs.kde.org/attachment.cgi?id=163737&action=edit
Expected behavior after dragging window to edge, slowed down from 100Hz to 60Hz

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

[kwin] [Bug 477802] XWayland windows do not appear in Wayland session

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0

--- Comment #3 from Timothy B  ---
I have an Arch Linux VM with Plasma 6 Beta 1 installed, and I could not
reproduce this when I ran glxgears from the terminal, so it appears that this
is a Neon-specific issue.

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

[kwin] [Bug 477802] XWayland windows do not appear in Wayland session in KDE Neon Unstable

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

Summary|XWayland windows do not |XWayland windows do not
   |appear in Wayland session   |appear in Wayland session
   ||in KDE Neon Unstable

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

[yakuake] [Bug 486018] Yakuake randomly crashes when clicking on buttons

[Timothy B]

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

--- Comment #2 from Timothy B  ---
Yakuake crashed at me again doing the same steps to reproduce above, this time
with Yakuake 24.05.0 and Frameworks 6.2:

#5  std::__atomic_base::fetch_add (this=0x8a040076, __i=1,
__m=std::memory_order_acq_rel, this=, __i=,
__m=) at /usr/include/c++/14.1.1/bits/atomic_base.h:629
#6  QAtomicOps::ref (_q_value=, _q_value=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qatomic_cxx11.h:259
#7  QBasicAtomicInteger::ref (this=0x8a040076, this=) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qbasicatomic.h:47
#8  QtSharedPointer::ExternalRefCountData::getAndRef
(obj=obj@entry=0x63b79f792730) at
/usr/src/debug/qt6-base/qtbase/src/corelib/tools/qsharedpointer.cpp:1456
#9  0x7f36b7f7f511 in QWeakPointer::QWeakPointer
(this=, ptr=0x63b79f792730) at
/usr/src/debug/qt6-base/qtbase/src/corelib/tools/qsharedpointer_impl.h:733
#10 QWeakPointer::assign (this=0x63b7a0e37630,
ptr=0x63b79f792730) at
/usr/src/debug/qt6-base/qtbase/src/corelib/tools/qsharedpointer_impl.h:728
#11 0x7f36b7fd229f in QPointer::operator= (this=0x63b7a0e37630,
p=0x63b79f792730, this=, p=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qpointer.h:71
#12 QWindowPrivate::connectToScreen (this=, screen=) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qwindow.cpp:490
#13 QWindowPrivate::setTopLevelScreen (this=0x63b7a0e374e0,
newScreen=0x63b79f792730, recreate=) at
/usr/src/debug/qt6-base/qtbase/src/gui/kernel/qwindow.cpp:515
#14 0x7f36b8936a87 in QWidgetPrivate::create
(this=this@entry=0x63b79fbd1c00) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qwidget.cpp:1318
#15 0x7f36b8935816 in QWidget::create (this=0x63b79faf5540,
window=, initializeWindow=,
destroyOldWindow=) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qwidget.cpp:1209
#16 0x7f36b8ad4208 in QMenuPrivate::popup(QPoint const&, QAction*,
std::function) (this=0x63b79fbd1c00, p=...,
atAction=0x0, positionFunction=...) at
/usr/src/debug/qt6-base/qtbase/src/widgets/widgets/qmenu.cpp:2369
#17 0x7f36b8ae713d in QMenu::popup (this=, p=...,
atAction=0x0) at
/usr/src/debug/qt6-base/qtbase/src/widgets/widgets/qmenu.cpp:2313
#18 QPushButtonPrivate::popupPressed (this=) at
/usr/src/debug/qt6-base/qtbase/src/widgets/widgets/qpushbutton.cpp:586
#19 0x7f36b79a17e7 in QtPrivate::QSlotObjectBase::call
(this=0x63b79fbb8060, r=0x63b79fbb81a0, a=0x7ffe0237a078, this=,
r=, a=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469
#20 doActivate (sender=, signal_index=,
argv=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4086
#21 0x7f36b8a0e4d2 in QAbstractButton::pressed (this=0x63b79fbb81a0) at
/usr/src/debug/qt6-base/build/src/widgets/Widgets_autogen/include/moc_qabstractbutton.cpp:311
#22 QAbstractButtonPrivate::emitPressed (this=0x63b79fbadf00) at
/usr/src/debug/qt6-base/qtbase/src/widgets/widgets/qabstractbutton.cpp:395
#23 0x7f36b8a1b138 in QAbstractButton::mousePressEvent
(this=0x63b79fbb81a0, e=0x7ffe0237a6e0) at
/usr/src/debug/qt6-base/qtbase/src/widgets/widgets/qabstractbutton.cpp:948
#24 0x7f36b894bcc6 in QWidget::event (this=0x63b79fbb81a0,
event=0x7ffe0237a6e0) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qwidget.cpp:9018
#25 0x7f36b88fc55c in QApplicationPrivate::notify_helper
(this=this@entry=0x63b79f778be0, receiver=receiver@entry=0x63b79fbb81a0,
e=e@entry=0x7ffe0237a6e0) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287
#26 0x7f36b8901a01 in QApplication::notify (this=,
receiver=, e=0x7ffe0237a6e0) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:2765
#27 0x7f36b7944e38 in QCoreApplication::notifyInternal2
(receiver=0x63b79fbb81a0, event=0x7ffe0237a6e0) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1142
#28 0x7f36b7944e8d in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1597
#29 0x7f36b88f3e6d in QApplicationPrivate::sendMouseEvent
(receiver=0x63b79fbb81a0, event=0x7ffe0237a6e0, alienWidget=,
nativeWidget=0x7ffe0237b1b0, buttonDown=, lastMouseReceiver=...,
spontaneous=true, onlyDispatchEnterLeave=false) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:2347
#30 0x7f36b8962072 in QWidgetWindow::handleMouseEvent (this=0x63b79feaf7f0,
event=event@entry=0x7ffe0237ab30) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qwidgetwindow.cpp:649
#31 0x7f36b89636b0 in QWidgetWindow::event (this=0x63b79feaf7f0,
event=0x7ffe0237ab30) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qwidgetwindow.cpp:263
#32 0x7f36b88fc55c in QApplicationPrivate::notify_helper (this=, receiver=0x63b79feaf7f0, e=0x7ffe0237ab30) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287
#33 0x7f36b7944e38 in QCoreApplication::notifyInternal2
(receiver=0x63b79feaf7f0, e

[yakuake] [Bug 486018] Yakuake randomly crashes when opening app menu

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

Summary|Yakuake randomly crashes|Yakuake randomly crashes
   |when clicking on buttons|when opening app menu

--- Comment #3 from Timothy B  ---
It seems that the crash only occurs when I click on the Open Menu button or
right click its system tray icon; I could not make Yakuake crash when I clicked
on the Quit or Always on Top buttons. I've updated the title to reflect this
observation.

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

[NeoChat] [Bug 485137] Turning off Link Previews not Functional if Matrix Server doesn't support link previews

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Timothy Arnold  ---
(In reply to James Graham from comment #1)
> So this setting should have nothing to do with the server and is local. It
> works for me on master, if I flick it off they all go away and come back if
> switched on.
> 
> That being said it would still be a good idea to ping the endpoint sometime
> early on and just not show them if they aren't supported.

It appears to be working for me on master now -- perhaps
https://invent.kde.org/network/neochat/-/commit/1a96899336f2f1a916207796b482ca4112909ebf
fixed it? 

We can close this. If you'd like me to open a separate bug for hitting that
endpoint, I can, though.

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

[NeoChat] [Bug 485137] Turning off Link Previews not Functional if Matrix Server doesn't support link previews

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

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

[kteatime] [Bug 481917] KTeaTime symbolic tray icon fails to change colors e.g. when using a dark theme

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kteatime] [Bug 481917] KTeaTime symbolic tray icon fails to change colors e.g. when using a dark theme

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC|yule2...@live.com   |

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

[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[konsole] [Bug 481683] Unicode characters doesn't render on konsole.

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com
 Resolution|NOT A BUG   |DUPLICATE

--- Comment #4 from Timothy B  ---
I'm pretty sure this is a duplicate of bug 478549. It seems that setting a
different font that contains the missing characters is more of a workaround
than a solution.

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

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

[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||rsi.de...@gmail.com

--- Comment #11 from Timothy B  ---
*** Bug 481683 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme

[Timothy B]

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

--- Comment #6 from Timothy B  ---
I'm pretty sure this is a duplicate of bug 482645. It seems that this has been
addressed in Plasma 6.0.4 (which will be released very soon as of this comment)
with Frameworks 6.1 per bug 482645 comment 26.

I was able to reproduce this with KDE Gear apps (specifically Akregator and
Yakuake) on Plasma 6.0.3 with Frameworks 6.1 (and also Frameworks 6.0). Only
setting the Plasma theme to Breeze Dark (or any other theme with a dark panel
background) was enough to trigger this behavior.

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

[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme

[Timothy B]

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

--- Comment #27 from Timothy B  ---
Can confirm that upgrading Plasma 6.0.4 fixed the icons on my EndeavourOS
system. Before that, symbolic icons of KDE Gear apps, specifically Yakuake and
Akregator, would remain dark no matter what Plasma theme I choose, even those
that follow the color scheme like the default Breeze theme.

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

[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #8 from Timothy B  ---
I just updated Plasma to 6.0.4 and can confirm that all symbolic icons in the
system tray are using the same color as expected, so I think it's now safe to
close this issue.

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

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

[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme

[Timothy B]

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

--- Comment #28 from Timothy B  ---
*** Bug 484473 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 484473] Symbolic icons in Add Widgets sidebar have wrong color when using Twilight theme

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

Summary|Symbolic icons have wrong   |Symbolic icons in Add
   |color when using Twilight   |Widgets sidebar have wrong
   |theme   |color when using Twilight
   ||theme
   Keywords||qt6

--- Comment #10 from Timothy B  ---
Good point. I now realize what this bug ticket originally addressed and noticed
that follow-up comments gradually changed the topic to similar behavior in the
system tray, which I initially thought was the topic of this report. Therefore,
I have changed the title to clarify that this bug specifically affects the Add
Widgets sidebar.

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

[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme

[Timothy B]

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

--- Comment #29 from Timothy B  ---
Please disregard my previous comment. The linked bug report actually referred
to similar behavior in the Add Widgets sidebar, but follow-up comments have
managed to change the subject to the same behavior in system tray icons.

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

[yakuake] [Bug 486018] New: Yakuake randomly crashes when clicking on buttons

[Timothy B]

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

Bug ID: 486018
   Summary: Yakuake randomly crashes when clicking on buttons
Classification: Applications
   Product: yakuake
   Version: 24.02.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: yule2...@live.com
  Target Milestone: ---

SUMMARY
Since upgrading to Plasma 6 and KDE Gear 24.02, Yakuake would randomly crash
when I click on the Open Menu button.

STEPS TO REPRODUCE
1. Leave Yakuake running for a couple days
2. Open Yakuake if hidden
3. Click on the menu icon

OBSERVED RESULT
Yakuake suddenly crashes, with all its tabs being killed.

EXPECTED RESULT
A menu would appear.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
Yakuake Version: 24.02.2
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I was also able to reproduce this with Qt 6.6 as well as Frameworks 6.0. I
haven't tried reproducing this on the X11 session.

BACKTRACE
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0)
at pthread_kill.c:44
#1  0x7b41d76ab393 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2  0x7b41d765a6c8 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x7b41d9abc45f in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kcrash/kcrash-6.1.0/src/kcrash.cpp:593
#4  0x7b41d765a770 in  () at /usr/lib/libc.so.6
#5  0x7b41d83c2353 in QScreen::devicePixelRatio (this=0x5f5f0c532e10)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qscreen.cpp:288
#6  0x7b41d83cb3a0 in QWindowPrivate::updateDevicePixelRatio
(this=0x5f5f0d35c710)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qwindow.cpp:1404
#7  0x7b41d7d97609 in QtPrivate::QSlotObjectBase::call
(a=0x7ffcf8d6e570, r=0x5f5f0d2ffb20, this=0x5f5f0d3c5000, this=, r=, a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobjectdefs_impl.h:469
#8  doActivate (sender=0x5f5f0d2ffb20, signal_index=3,
argv=0x7ffcf8d6e570)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:4078
#9  0x7b41d83cb7d3 in QWindow::screenChanged (_t1=0x5f5f0c532e10,
this=0x5f5f0d2ffb20)
at
/usr/src/debug/qt6-base/build/src/gui/Gui_autogen/include/moc_qwindow.cpp:817
#10 QWindowPrivate::emitScreenChangedRecursion (newScreen=0x5f5f0c532e10,
this=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qwindow.cpp:496
#11 QWindowPrivate::setTopLevelScreen (this=,
newScreen=0x5f5f0c532e10, recreate=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qwindow.cpp:520
#12 0x7b41d8d32ae7 in QWidgetPrivate::create
(this=this@entry=0x5f5f0c585ed0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:1318
#13 0x7b41d8d31912 in QWidget::create
(this=0x5f5f0c980d90, window=, initializeWindow=, destroyOldWindow=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:1209
#14 0x7b41d8ebb448 in QMenuPrivate::popup(QPoint const&, QAction*,
std::function)
(this=0x5f5f0c585ed0, p=..., atAction=0x0, positionFunction=...)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qmenu.cpp:2359
#15 0x7b41d8eceb6b in QMenu::popup (atAction=, p=, this=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qmenu.cpp:2306
#16 QPushButtonPrivate::popupPressed (this=0x7ffcf8d6e7d0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qpushbutton.cpp:586
#17 0x7b41d7d97609 in QtPrivate::QSlotObjectBase::call
(a=0x7ffcf8d6e8b8, r=0x5f5f0c939e80, this=0x5f5f0c939d40, this=, r=, a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobjectdefs_impl.h:469
#18 doActivate (sender=0x5f5f0c939e80, signal_index=7,
argv=0x7ffcf8d6e8b8)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:4078
#19 0x7b41d8dff332 in QAbstractButton::pressed (this=0x5f5f0c939e80)
at
/usr/src/debug/qt6-base/build/src/widgets/Widgets_autogen/include/moc_qabstractbutton.cpp:311
#20 QAbstractButtonPrivate::emitPressed (this=0x5f5f0c939180)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qabstractbutton.cpp:395
#21 0x7b41d8e0b8ab in QAbstractButton::mousePressEvent
(this=0x5f5f0c939e80, e=0x7ffcf8d6eeb0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qabstractbutton.cpp:948
#22 0x7b41d8d47292 in QWidget::event (this=0x5f5f0c939e80,
event=0x7ffcf8d6eeb0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:9018
#23 0x7b41d8cfb

[NeoChat] [Bug 486126] New: Double Text when there is text with a Link and No Link Previews Is On

[Timothy Arnold]

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

Bug ID: 486126
   Summary: Double Text when there is text with a Link and No Link
Previews Is On
Classification: Applications
   Product: NeoChat
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: tima...@proton.me
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 168904
  --> https://bugs.kde.org/attachment.cgi?id=168904&action=edit
Displays Double comment

SUMMARY

When Link Previews are off, you see double text for comments/posts that have a
URL in them. Separately, it was stated that individual room link preview
settings are broken. 

STEPS TO REPRODUCE
1.  Turn off Link Previews
2.  Go into a chat and type a message with a URL in it
3.  See double comment

OBSERVED RESULT

The comment and text will become double posted within the same message.

EXPECTED RESULT

You should not see a doubling of the comment in the same message

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.2
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 590 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS GAMING 7 WIFI

NeoChat:
Built from Git master
KDe Frameworks 6.2.0
Wayland
QT 6.6.2
LibQuotient 0.8.2

ADDITIONAL INFORMATION

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

[NeoChat] [Bug 486126] Double Text when there is text with a Link and No Link Previews Is On

[Timothy Arnold]

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

--- Comment #1 from Timothy Arnold  ---
When bisecting, this appeared to be related to
https://invent.kde.org/network/neochat/-/commit/de40701cf65e1b8bb28499bfcf20ed00c6bf4fc1

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

[yakuake] [Bug 486018] Yakuake randomly crashes when clicking on buttons

[Timothy B]

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

--- Comment #1 from Timothy B  ---
Yakuake crashed again with the above steps to reproduce. This time the
backtrace looks a bit different, with the top of the backtrace stack still
pointing to QScreen:

#5  0x7cfd3a7bee48 in QScreen::geometry (this=0x59862d3e2e10) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qscreen.cpp:330
#6  0x7cfd3b2b2c00 in QWidgetPrivate::screenGeometry
(hasPosition=, globalPosition=, widget=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget_p.h:489
#7  QWidgetPrivate::screenGeometry (widget=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget_p.h:470
#8  QMenuPrivate::popupGeometry (this=, screen=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qmenu.cpp:297
#9  0x7cfd3b2b7c68 in QMenuPrivate::updateActionRects (this=0x59862d48c650)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qmenu.cpp:328
#10 QMenu::sizeHint (this=0x59862d830090) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qmenu.cpp:2265
#11 0x7cfd3b2ce5ca in QPushButtonPrivate::adjustedMenuPosition
(this=0x59862d834e00) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qpushbutton.cpp:604
#12 0x7cfd3b2cea00 in QPushButtonPrivate::popupPressed
(this=0x59862d834e00) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qpushbutton.cpp:577
#13 0x7cfd3a197609 in QtPrivate::QSlotObjectBase::call (a=0x7ffdf4b9f938,
r=0x59862d7e9080, this=0x59862d7e8f40, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobjectdefs_impl.h:469
#14 doActivate (sender=0x59862d7e9080, signal_index=7,
argv=0x7ffdf4b9f938) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:4078
#15 0x7cfd3b1ff332 in QAbstractButton::pressed (this=0x59862d7e9080) at
/usr/src/debug/qt6-base/build/src/widgets/Widgets_autogen/include/moc_qabstractbutton.cpp:311
#16 QAbstractButtonPrivate::emitPressed (this=0x59862d834e00) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qabstractbutton.cpp:395
#17 0x7cfd3b20b8ab in QAbstractButton::mousePressEvent
(this=0x59862d7e9080, e=0x7ffdf4b9ff30) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/widgets/qabstractbutton.cpp:948
#18 0x7cfd3b147292 in QWidget::event (this=0x59862d7e9080,
event=0x7ffdf4b9ff30) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:9018
#19 0x7cfd3b0fbfcb in QApplicationPrivate::notify_helper
(this=this@entry=0x59862d3a6be0, receiver=receiver@entry=0x59862d7e9080,
e=e@entry=0x7ffdf4b9ff30) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287
#20 0x7cfd3b100ac5 in QApplication::notify (this=,
receiver=, e=0x7ffdf4b9ff30) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:2765
#21 0x7cfd3a13dae8 in QCoreApplication::notifyInternal2
(receiver=0x59862d7e9080, event=0x7ffdf4b9ff30) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134
#22 0x7cfd3a13db3d in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1589
#23 0x7cfd3b0f4597 in QApplicationPrivate::sendMouseEvent
(receiver=0x59862d7e9080, event=0x7ffdf4b9ff30, alienWidget=0x59862d7e9080,
nativeWidget=0x7ffdf4ba0970, buttonDown=, lastMouseReceiver=...,
spontaneous=true, onlyDispatchEnterLeave=false) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:2347
#24 0x7cfd3b15be37 in QWidgetWindow::handleMouseEvent (this=0x59862d8c9cb0,
event=event@entry=0x7ffdf4ba02a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidgetwindow.cpp:649
#25 0x7cfd3b15d1c0 in QWidgetWindow::event (this=0x59862d8c9cb0,
event=0x7ffdf4ba02a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidgetwindow.cpp:263
#26 0x7cfd3b0fbfcb in QApplicationPrivate::notify_helper (this=, receiver=0x59862d8c9cb0, e=0x7ffdf4ba02a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287
#27 0x7cfd3a13dae8 in QCoreApplication::notifyInternal2
(receiver=0x59862d8c9cb0, event=0x7ffdf4ba02a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134
#28 0x7cfd3a13db3d in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1589
#29 0x7cfd3a7720e5 in QGuiApplicationPrivate::processMouseEvent
(e=0x7cfd20003640) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qguiapplication.cpp:2327
#30

[plasmashell] [Bug 486409] Plasma allows users to select Adwaita as an icon theme, which breaks things due to missing icons

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

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

[kwin] [Bug 455585] WindowHeap-based effects' animations aren't smooth when using a high refresh rate screen

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

Version|5.25.5  |6.0.2
   Keywords||qt6

--- Comment #33 from Timothy B  ---
After upgrading to Plasma 6, it now occurs consistently with the Overview
effect on Wayland, even after performing the window drag workaround outside the
effect. What's interesting this time is when I drag any window in Overview, it
moves with the cursor at the expected full 100 FPS until I release my mouse
button. I've also upgraded my GPU from a Radeon 570 to a Radeon 6750 XT since
the previous comment while keeping the same 100 Hz monitor, so I'm still using
the same AMDGPU graphics driver.

I haven't tested it on X11 but getting this fixed for Wayland at the very least
would be great, since it's the path forward for windowing systems these days.

UPDATED SYSTEM INFO:
Plasma version: 6.0.2 (waiting for 6.0.3 to be released in my distro)
Frameworks version: 6.0
Qt version: 6.6.2

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

[kwin] [Bug 464196] Drag and drop in GTK apps: 'drag-motion' is triggered when GTK window regains focus

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

--- Comment #6 from Timothy B  ---
This started happening to me since I upgraded to Plasma 6 and KDE Gear 24.02,
and the workarounds mentioned in the initial comment work perfectly on my end.
But then again, the issue returns the next time I relaunch Akegrator or when it
autostarts at login.

Also, given the number of duplicates we have linked to this report so far, I
think it's safe to say that this bug should be marked as confirmed.

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

[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[NeoChat] [Bug 485137] New: Turning off Link Previews not Functional if Matrix Server doesn't support link previews

[Timothy Arnold]

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

Bug ID: 485137
   Summary: Turning off Link Previews not Functional if Matrix
Server doesn't support link previews
Classification: Applications
   Product: NeoChat
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: tima...@proton.me
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 168221
  --> https://bugs.kde.org/attachment.cgi?id=168221&action=edit
Shows setting is turned off but loading preview still shows

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY

I'm currently using a matrix server implementation that doesn't have URL
Previews implemented (endpoint `/_matrix/media/v3/preview_url`). So in order to
get rid of the endless spinning cog on preview url attempts, I tried turning
them off in settings. This didn't change the behaviour and I still see the
spinning cog.

(Aside: The server returns an `M_UNRECOGNIZED` errcode if the endpoint isn't
supported. It might be worth hitting the endpoint and see if it returns that
error code to determine if the url preview should be loaded)

STEPS TO REPRODUCE
1. Connect to a server without the preview_url endpoint implemented or turned
off 
2. Attempt to turn off link previews in messages
3. Confirm that the "loading preview" image is still displayed

OBSERVED RESULT

"Loading Preview" is displayed even if the link previews are turned off in the
client

EXPECTED RESULT

"Loading Preview" shouldn't be displayed

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.4-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 590 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS GAMING 7 WIFI

ADDITIONAL INFORMATION
NeoChat Build Information:
KDE Frameworks 6.1.0 
Wayland Windowing System
Qt 6.6.2
libQuotient 0.8.1.2

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

[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators::paint()

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

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

[frameworks-kirigami] [Bug 484888] Kirigami.Icon is blurry when used as a CompactRepresentation in a plasmoid

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

--- Comment #5 from Timothy B  ---
Can confirm this happening on all floating panels on EndeavourOS, which I
switched from Manjaro very recently. What's also strange is when I switched
between icon themes, some of the icons in both floating and non-floating panels
wouldn't update until I hovered over each one.

I've never seen this happen on Manjaro with Plasma 6.0.2 nor on Plasma 5.27 in
any distro. I first noticed this when I tested the Plasma 6 betas and release
candidates on an Arch Linux VM, but I initially thought of it as some kind of
issue related to display drivers and Qt 6.

Operating System: EndeavourOS
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Graphics Platform: Wayland

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

[Elisa] [Bug 480573] Elisa always switches back to outputting to the audio output used when Elisa is initially launched when changing tracks.

[Timothy Arnold]

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

Timothy Arnold  changed:

   What|Removed |Added

 CC||tima...@proton.me

--- Comment #1 from Timothy Arnold  ---
Created attachment 165477
  --> https://bugs.kde.org/attachment.cgi?id=165477&action=edit
F39 QT6.6.0 Build of Elisa Switches Audio Output back to previous output

I'm able to replicate this bug on a QT6 master build of Elisa (24.04.70) on
Fedora 39 using the procedure above

Using KDE Frameworks 6.0.0
Built against QT 6.6.0

It not only switches output during the switching of tracks but also when
seeking on the current track. Attached screenshots shows audio playing on the
previously selected output but not on the currently selected output

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

[Elisa] [Bug 480743] New: Elisa: Pressing Play on Final Song on the Playlist panel doesn't start the song from the beginning if the Song has completed

[Timothy Arnold]

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

Bug ID: 480743
   Summary: Elisa: Pressing Play on Final Song on the Playlist
panel doesn't start the song from the beginning if the
Song has completed
Classification: Applications
   Product: Elisa
   Version: 24.01.95
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: tima...@proton.me
  Target Milestone: ---

SUMMARY

Attempting to play a the final song on a playlist that has already completed by
pressing the "Play" button on the playlist panel doesn't restart the song.


STEPS TO REPRODUCE
1.  Open Elisa
2.  Load a Playlist
3.  Play the Last Song on the Playlist to completion
4.  Attempt to play the song again by pressing the play button next to the song
on the playlist panel

OBSERVED RESULT
The song doesn't play from the beginning but remains at the end of the song

EXPECTED RESULT
The song would play from the beginning

*APPLICATION BUILD INFORMATION*
Elisa Version: 24.04.70
Qt Version: 6.6.0 (built against 6.6.0)
KDE Frameworks Version 6.0.0

Built using kdesrc-build and using the master branch


SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
Kernel Version: 6.6.13-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 590 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS GAMING 7 WIFI

ADDITIONAL INFORMATION

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

[Elisa] [Bug 480743] Elisa: Pressing Play on Final Song on the Playlist panel doesn't start the song from the beginning if the Song has completed

[Timothy Arnold]

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

--- Comment #1 from Timothy Arnold  ---
Created attachment 165479
  --> https://bugs.kde.org/attachment.cgi?id=165479&action=edit
Elisa Video showing pressing the play button resulting in no playback of the
completed song

My original video was too large it appears. adding a shorter on

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

[kwin] [Bug 481933] Menus somtimes appear as normal windows when activated from anything other than the current active window

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[plasmashell] [Bug 447744] Notifications applet when started in Latte renames Plasma Desktop global shortcuts _k_friendly_name

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kwin] [Bug 451778] Blur/Kornerbug enabled even when a window is set to opaque

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[kwin] [Bug 447797] Mouse cursor glitching upon switching states in the Wayland session

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[plasmashell] [Bug 432810] exiting keepassxc after it has put a password in the clipboard hangs plasma for 5 secs

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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

[plasmashell] [Bug 432810] exiting keepassxc after it has put a password in the clipboard hangs plasma for 5 secs

[Timothy B]

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

--- Comment #11 from Timothy B  ---
(In reply to Mo Kirchner from comment #8)
> There is a weird workaround though: 
> 
> 1. open keepassxc
> 2. copy password to clipboard [&& paste or do other stuff]
> 3. select another item from the clipboard history
> 3. exit keepassxc without hanging

Can confirm that workaround worked well on my end, but I find it very tedious
to do those steps after every time I copy a password. I also discovered some
interesting observations regarding this behavior:

- The KeePassXC process actually exits properly while Plasma (or in my case,
Latte Dock) hangs. I did this by running `pgrep keepassxc` in the terminal
immediately after quitting the app through normal means (Ctrl+Q, File > Quit,
exit from tray icon menu, etc.)
- Killing KeePassXC with `pkill keepassxc` or `killall keepassxc` also triggers
this bug. But running `pkill -KILL keepassxc` while the app is running won't
cause Plasma/Latte to hang, regardless whether or not a password from KeepassXC
was copied beforehand.

Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.18.6-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series

Note that while writing this comment, Manjaro has not yet upgraded Plasma to
5.25 unless you are in sync with the unstable branch, so I will report back
once I have that upgraded, or someone who's already using that Plasma version
can try to reproduce this bug again instead.

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

[kcalc] [Bug 454835] Entering operators repeatedly without a number in between results in history/result mismatch

[Timothy Pederick]

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

Timothy Pederick  changed:

   What|Removed |Added

 CC||peder...@gmail.com

--- Comment #1 from Timothy Pederick  ---
Most likely related, entering a square root as an intermediate step produces
incorrect history.

Steps to reproduce:
1. Ensure History is open
2. Enter "2 × 2 Shift √ =" using the on-screen buttons (physical keys also work
for 2, ×, and =, but I don't know if there are shortcuts for the square root)

Observed result:
History adds these two lines, the first after the square root and the second
after the equals. Both lines are mathematically incorrect, and they do not
accurately reflect user entry.
> 1.41421356237 = 2.82842712475
> 2 ×  √ 2 = 1.41421356237

Expected result:
History should show correct figures, either one for the whole process such as:
> 2 ×  √ 2 = 2.82842712475

...or two separate ones like so:
> 2 × 1.41421356237 = 2.82842712475
> √ 2 = 1.41421356237

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

[kwin] [Bug 443434] Window resizing broken when using wobbly windows + resize effects

[Timothy B]

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

Timothy B  changed:

   What|Removed |Added

 CC||yule2...@live.com

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