[kwin] [Bug 482780] Incorrect color gamut with HDR enabled

2024-05-23 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=482780

Daniel  changed:

   What|Removed |Added

 CC||danielmorenol...@gmail.com

--- Comment #22 from Daniel  ---
(In reply to Zamundaaa from comment #19)
> Not yet. NVidia is now aware of this bug and the possible cause, but the
> person that's usually responsible for this stuff is currently not available,
> so it might still take a bit for someone from NVidia to take a look.
> I'll update this bug report when there's news

Any update on this? I'm affected by this issue on my RTX 4090, driver 550.54.14
and the recently released 555.42.02. No matter what I do the colors look
washout with HDR on. At this point I suspect the Nvidia drivers, after doing
tests with my steam deck on the same monitor, which did seem to work, though it
was through a gamescope session and not plasma 6.

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

[neon] [Bug 487381] There are no almost all icons.

2024-05-22 Thread Daniel Kraus
https://bugs.kde.org/show_bug.cgi?id=487381

Daniel Kraus  changed:

   What|Removed |Added

 CC||boven...@bovender.de

--- Comment #7 from Daniel Kraus  ---
+1

I do have icons in the system tray.

Interestingly, when I start Konsole, I get this message twice:

kf.config.core: Created a KConfigGroup on an inaccessible config location
":/icons/breeze/index.theme" "Icon Theme"

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

[kwalletmanager] [Bug 487094] Nextcloud Sync Client (Flatpak) asks for credentials every relaunch when KDE wallet subsystem disabled

2024-05-20 Thread Daniel Rusek
https://bugs.kde.org/show_bug.cgi?id=487094

Daniel Rusek  changed:

   What|Removed |Added

 CC||m...@asciiwolf.com

--- Comment #4 from Daniel Rusek  ---
Did you try reinstalling the Flatpak and removing its existing config files and
other data?

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

[Marknote] [Bug 487185] (Feature Request) Menubar on desktop

2024-05-18 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=487185

--- Comment #2 from Daniel  ---
Sounds great! I considered waiting, but since it was mentioned in the changelog
for the latest release I thought I might as well mention it. :)
Thanks for all your hard work on this and other good apps!

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

[Marknote] [Bug 487185] New: (Feature Request) Menubar on desktop

2024-05-18 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=487185

Bug ID: 487185
   Summary: (Feature Request) Menubar on desktop
Classification: Applications
   Product: Marknote
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@kaidan.im
  Reporter: imer...@gmail.com
CC: c...@carlschwan.eu, m...@kaidan.im
  Target Milestone: ---

First: Thanks for creating a great app - I hope I am posting this in the right
place. MarkNote is looking really nice and has already gained many nice
features. As of version 1.2 there is support for a Global Menu in Linux. This
is a feature request for being able to show that menu bar inside the window
too, as is possible in most other desktop apps. This woul bring quick and
discoverable one-click access to vital functions and would make the app be able
to match other desktop apps such as Dolphin, Gwenview, Mercuro and Okular.

Either on by default on desktop, or as an option. I would suggest the former,
on by default. Many of my customers who buy pre-configured Linux desktops
believe apps to be less functional or "simple" if they don't have a regular
menu bar, and displaying it first is an easy way to show what the software can
do and which functions and options are available. After that has been made
clear, the user can hide it. But hidden by default but easily discoverable also
works well.

I realize there might not yet be much items in those menus, but the function is
good to have as the application grows.

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

[systemsettings] [Bug 486935] New: Find Action/Command Bar partially hidden

2024-05-12 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=486935

Bug ID: 486935
   Summary: Find Action/Command Bar partially hidden
Classification: Applications
   Product: systemsettings
   Version: 6.0.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Quick Settings
  Assignee: plasma-b...@kde.org
  Reporter: dvra...@kde.org
  Target Milestone: ---

Created attachment 169406
  --> https://bugs.kde.org/attachment.cgi?id=169406=edit
Screenshot of the problem

SUMMARY
When I invoke the command bar ("Find Action") via Ctrl+Alt+I in the System
Settings window, the popup is only partially visible - it's visible above the
navigation view, but the rest is obscured by the actual KCM view on the right -
see the attached screenshot.

STEPS TO REPRODUCE
1. Open System Settings
2.  Press Ctrl+Alt+I (or whatever shortcut you have configured for "Find
Action")

OBSERVED RESULT
The command bar is partially obscured by the window content.

EXPECTED RESULT
The command bar appears on top of all the window content.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Graphics platform: Wayland

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

[Akonadi] [Bug 485132] DAV resource: invalid response from backend

2024-05-09 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485132

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Daniel Vrátil  ---
The error message is not very good, but it indicates that the DAV server has
returned an invalid response.

Is this some standard DAV server (like Nextcloud), or some custom/proprietary
one? Are you able to test with some other calendar client?

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

[korganizer] [Bug 485621] No alarams and no updates from Google - update is stuck

2024-05-09 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485621

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||dvra...@kde.org
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Daniel Vrátil  ---
Do reminders from other calendar types work?

Can you please check whether there's a process called "kalendarac" running on
your system?

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

[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved

2024-05-09 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485205

Daniel Vrátil  changed:

   What|Removed |Added

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

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

[korganizer] [Bug 485207] Error while trying to create calendar item. Error was: Invalid parent collection

2024-05-09 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485207

Daniel Vrátil  changed:

   What|Removed |Added

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

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

[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable

2024-05-09 Thread Daniel Albers
https://bugs.kde.org/show_bug.cgi?id=482142

Daniel Albers  changed:

   What|Removed |Added

 CC||dan...@lbe.rs

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

[plasmashell] [Bug 486756] fontconfig to turn antialiasing off freezes KDE plasma

2024-05-07 Thread Daniel Jay Haskin
https://bugs.kde.org/show_bug.cgi?id=486756

--- Comment #1 from Daniel Jay Haskin  ---
Indeed, having a fontconfig file there _at all_ seems to cause stability
issues. I got a lot further with anti aliasing on but had to remove it
altogether to stop the stability issues entirely.

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

[plasmashell] [Bug 486756] New: fontconfig to turn antialiasing off freezes KDE plasma

2024-05-07 Thread Daniel Jay Haskin
https://bugs.kde.org/show_bug.cgi?id=486756

Bug ID: 486756
   Summary: fontconfig to turn antialiasing off freezes KDE plasma
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: plasma-b...@kde.org
  Reporter: djhaskin...@gmail.com
  Target Milestone: 1.0

SUMMARY

fontconfig set to antialiasing freezes KDE and associated applications.
STEPS TO REPRODUCE
1. Place this in `~/.config/fontconfig/conf.d/10-no-anti-aliasing.conf`: ```


false

```
2. Reboot computer
3. Log in

OBSERVED RESULT

Opened the application "Konsole". It came up but stopped responding. I opened
the -- start menu? I guess that's "kicker" -- and typed "q", thinking to open
qutebrowser. It froze. I couldn't even pull up a tty (ctrl-alt-f3). I had to
power cycle the machine manually. The mouse worked, but the OS stopped
responding.

I changed the `false` to `true` in the fontconfig via boot to tty and _then_
logged in, and everything worked again.

ADDITIONAL INFORMATION

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: HP
Product Name: HP Spectre x360 Convertible 13-aw0xxx

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

[kde] [Bug 486744] New: /bin/sh: bad interpreter: input/output error - while executing a file on a CIFS share

2024-05-07 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=486744

Bug ID: 486744
   Summary: /bin/sh: bad interpreter: input/output error - while
executing a file on a CIFS share
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: daniel.scho...@bluewin.ch
  Target Milestone: ---

***
I'm reporting this here, because Dolphin (the filemanager) told me so.
***

SUMMARY

If executing a file on a smb share, mounted with cifs, errors occure:
/bin/sh: bad interpreter: input/output error
(original german text --> bash: ./test.sh: /bin/sh: Defekter Interpreter:
Eingabe-/Ausgabefehler)

If executing it from Dolphin gives an error message:
'Unbekannter Fehlercode 100
execvp: Eingabe-/Ausgabefehler
Bitte senden Sie einen ausführlichen Problembericht an https://bugs.kde.org.'

File 'test.sh' content:
#!/bin/sh
echo "test"

STEPS TO REPRODUCE
1. you nead at least a server (NAS) with smb shares and cifs installed on your
system.
2. add to fstab: '//192.168.1.15/Netshare  /home/username/Netshare  cifs 
noauto,users,rw,exec,credentials=/home/username/.config/.smb-cred  0 0'
(address of the server and name of the share)
3. mount it with '$ mount ~/Netshare' (the folder Netshare has to exist)
4. create a file 'test.sh' on this share
#!/bin/sh
echo "test"
5. try to execute it with '$ ./test.sh' 
6. try to execute any executable from this share

OBSERVED RESULT

The script is not executed.

The execution gives an error:
(original german text --> bash: ./test.sh: /bin/sh: Defekter Interpreter:
Eingabe-/Ausgabefehler)

Executing from Dolphin too:
'Unbekannter Fehlercode 100
execvp: Eingabe-/Ausgabefehler
Bitte senden Sie einen ausführlichen Problembericht an https://bugs.kde.org.'

EXPECTED RESULT

A simple echo: 
Test

SOFTWARE/OS VERSIONS

Operating System: Ubuntu Studio 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 6.5.0-26-lowlatency (64-bit)
Graphics Platform: X11
Processors: 16 × 13th Gen Intel® Core™ i7-13700K
Memory: 62.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2

ADDITIONAL INFORMATION

I've also tried to add 'file_mode=0777,dir_mode=0777,' to the fstab entry, with
no success.

If I'm using '$ /bin/bash ./test.sh' the script is running.
If I copy the script to a local drive, it's running.

The file on the smb share has the attributes 'rwx' set, for users and groups.
Programs on the same drive are running under Windows 10.

I've also tried to upgrade the kernel to the next one (6.5.0-27-lowlatency),
but then I had copy problems on the share and had to downgrade again to solve
it.

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

[korganizer] [Bug 486243] Crash when shift+deleting an event

2024-05-06 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=486243

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||dvra...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Daniel Vrátil  ---
Fixed by David in current git master:
https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/87

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

[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen

2024-05-04 Thread Daniel DS
https://bugs.kde.org/show_bug.cgi?id=484323

Daniel DS  changed:

   What|Removed |Added

 CC||stoyanov.dan...@gmail.com

--- Comment #30 from Daniel DS  ---
Same issue here with me with plasma 6.0.4 on Fedora 40.  Disabling KScreen2 did
the trick for me as well.

Before somebody stat commenting that F40 KDE cannot run on X - actually this is
not the truth. F40 KDE is capable of running "the hidden" X11 session option
via manually installing package plasma-workspace-x11 and sddm-x11. These 
packages are  part of the official repos.

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

[kup] [Bug 477002] Kup does not ask for confirmation consistently

2024-05-03 Thread Daniel M
https://bugs.kde.org/show_bug.cgi?id=477002

--- Comment #2 from Daniel M  ---
Thanks for chiming in Simon!

When I originally submitted the bug, I was new to Kup.  After using it for a
while now, I think I have a somewhat better understanding of what's happening
and I get the feeling Kup was written for a time when faster networks, faster
computers and broad Internet/cloud coverage was less plentiful.

As for getting a question the first time a backup runs, it feel it should be
the default and unchangeable; the backup is likely to be large and you might
want an ideal environment before doing this.

While bup natively supports a bup server/SSH endpoint, it appears Kup does not
support this configuration and was designed for attached storage.  Since
lugging around and connecting/disconnecting external storage is not ideal for
me, I configured sshfs on my machine
(x-systemd.automount,_netdev,auto_cache,delay_connect,reconnect,nofail,ServerAliveInterval=10),
which connects to another machine on my LAN, and configure Kup to use this
mount/Destination.

So, my Kup workflow tends to go like this:

1. Kup runs when I'm at the office and does not ask for confirmation (this
reflects your comment).
2. When I'm away from the office, I'm usually running off the battery/in Power
Save, so Kup asks for confirmation and I say no.
3. When I return to the office, Kup never runs unless I do it manually (this
reflects your comment).

This workflow is less than ideal; I could have days without a backup if I don't
remember/pay attention to the icon/tray.

I think it should go like this:

1. Kup runs when I'm at the office and does not ask for confirmation.
2. When I'm away from the office, Kup notices the Destination does not exist,
so it does not run/ask for confirmation.
3. When I return to the office, Kup runs as normal and does not ask for
confirmation.

In the original workflow case, if I'm being asked for confirmation because of
Power Save, I feel Kup should automatically run the backup at the next interval
if the system is no longer set for Power Save.  This will ensure more backups.

Hope some of this makes sense.

Thanks.

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

[Bluedevil] [Bug 486339] Unable to reconnect to bluetooth headphones (br-connection-profile-unavailable)

2024-04-30 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=486339

Daniel Duris  changed:

   What|Removed |Added

Summary|Unable to reconnect to  |Unable to reconnect to
   |bluetooth headphosne|bluetooth headphones
   |(br-connection-profile-unav |(br-connection-profile-unav
   |ailable)|ailable)

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

[Bluedevil] [Bug 486339] New: Unable to reconnect to bluetooth headphosne (br-connection-profile-unavailable)

2024-04-30 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=486339

Bug ID: 486339
   Summary: Unable to reconnect to bluetooth headphosne
(br-connection-profile-unavailable)
Classification: Plasma
   Product: Bluedevil
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kdeb...@staznosti.sk
  Target Milestone: ---

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

***
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
Bluetooth stopped working on trying to connect the headphones (trusted)

USB device restart and service bluetooth restart does not help.

STEPS TO REPRODUCE
1. Connect to headphones
2.  Receive error

OBSERVED RESULT
Error / no specific message given

EXPECTED RESULT
Specific message given, automatic BT system restart, if unrecoverable etc.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: X11

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

[kmail2] [Bug 486283] New: crash when opening an e-mail which failed to be sent

2024-04-29 Thread Daniel Moyne
https://bugs.kde.org/show_bug.cgi?id=486283

Bug ID: 486283
   Summary: crash when opening an e-mail which failed to be sent
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: daniel.mo...@free.fr
  Target Milestone: ---

Application: kmail (5.24.5 (23.08.5))

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.0-31-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
when opening an e-mail  which failed to be sent the mail crashes but not the
kmail application

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x77c8e6112695 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x77c8ef704cd4 in KMCommand::completed(KMCommand*) () from
/lib/x86_64-linux-gnu/libkmailprivate.so.5
#6  0x77c8ef81dc93 in KMCommand::slotPostTransfer(KMCommand::Result) ()
from /lib/x86_64-linux-gnu/libkmailprivate.so.5
#7  0x77c8e6112e16 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x77c8ef704c70 in KMCommand::messagesTransfered(KMCommand::Result) ()
from /lib/x86_64-linux-gnu/libkmailprivate.so.5
#9  0x77c8e6112e16 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x77c8e73a8266 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#11 0x77c8e73ae0eb in ?? () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#12 0x77c8e6106343 in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x77c8e6d6bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x77c8e60d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x77c8e60db94b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x77c8e6135c0f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x77c8e1c095b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x77c8e1c68717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x77c8e1c08a53 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x77c8e6135279 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x77c8e60d6a7b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x77c8e60df3e8 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x5ba6e602e1b9 in ?? ()
#24 0x77c8e562a1ca in __libc_start_call_main
(main=main@entry=0x5ba6e602d0e0, argc=argc@entry=3,
argv=argv@entry=0x7ffc0d6001d8) at ../sysdeps/nptl/libc_start_call_main.h:58
#25 0x77c8e562a28b in __libc_start_main_impl (main=0x5ba6e602d0e0, argc=3,
argv=0x7ffc0d6001d8, init=, fini=,
rtld_fini=, stack_end=0x7ffc0d6001c8) at ../csu/libc-start.c:360
#26 0x5ba6e602e8a5 in ?? ()
[Inferior 1 (process 3176) detached]

Reported using DrKonqi

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

[plasmashell] [Bug 483594] Plasma panel won't dodge windows if placed between dual monitors

2024-04-26 Thread daniel
https://bugs.kde.org/show_bug.cgi?id=483594

daniel  changed:

   What|Removed |Added

 CC||zkr...@proton.me

--- Comment #3 from daniel  ---
Can also confirm but for me it is with a monitor under my main one. I have my
panel below on my main monitor and it isn't dodging if my third monitor is set
to be under my main one.

SOFTWARE/OS VERSIONS
Operating System: Fedora 40 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7
Graphics Platform: Wayland

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

[plasmashell] [Bug 486110] New: Editing an entry in Folder View widget makes it vanish (until next session)

2024-04-25 Thread Daniel Mader
https://bugs.kde.org/show_bug.cgi?id=486110

Bug ID: 486110
   Summary: Editing an entry in Folder View widget makes it vanish
(until next session)
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: plasma-b...@kde.org
  Reporter: danielstefanmader+...@gmail.com
CC: h...@kde.org
  Target Milestone: 1.0

SUMMARY
When a desktop item in a folder view widget (e.g. showing ~/Desktop) is edited
(right click, Properties, etc.) and saved, that item vanishes temporarily from
the folder view. Log out/in brings it back. Dolphin still shows that item.

STEPS TO REPRODUCE
1. Add folder view widget to Plasma Desktop
2. Open Properties of existing item
3. Change anything, or leave unchanged
4. Close Properties by pressing OK

OBSERVED RESULT
Item disappears temporarily unteil next session.

EXPECTED RESULT
Item should be still there (with updated properties)

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240423
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 30,6 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 20UJS00K00
System Version: ThinkPad T14s Gen 1

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

[plasmashell] [Bug 483163] On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style

2024-04-25 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #29 from Daniel Duris  ---
If I press Escape key on properly shown locked screen with Breeze theme, the
screen goes blank. I have to juggle bit with a keyboard to get the locked
screen displayed again. Maybe related to the comment above.

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

[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU

2024-04-24 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=436240

Daniel Eckl  changed:

   What|Removed |Added

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

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

[korganizer] [Bug 485761] Events of newly added .ics calendar aren't shown

2024-04-23 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485761

Daniel Vrátil  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dvra...@kde.org
 Status|REPORTED|CONFIRMED

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

[korganizer] [Bug 485722] there's no way to switch to the standard 24 hour display

2024-04-23 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485722

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||dvra...@kde.org
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Daniel Vrátil  ---
Please provide at least a screenshot so we can know what "unreadable" means in
this context.

The format of date and time displayed in KOrganizer is controlled by your
locale settings, you can configure it in System Settings -> Region & Language.
If the time format in KOrganizer doesn't match what you have configured in
System Settings, please provide also screenshot of the System Settings page, so
we can try to figure out what's wrong.

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

[plasmashell] [Bug 485815] New: Impossible to match image objects (actual images, *not* URLs, nor filenames) in Clipboard to use actions

2024-04-19 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=485815

Bug ID: 485815
   Summary: Impossible to match image objects (actual images,
*not* URLs, nor filenames) in Clipboard to use actions
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard
  Assignee: plasma-b...@kde.org
  Reporter: kdeb...@staznosti.sk
  Target Milestone: 1.0

Created attachment 168693
  --> https://bugs.kde.org/attachment.cgi?id=168693=edit
the pattern is what now?

***
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
How to use action matching for images (actual images, not URLs or filenames) in
KDE Clipboard?
What one does use to match objects such as images? It does not seem to be
possible.

Use case: maybe one would like to download all images in clipboard somewhere or
upload them to cloud etc., run some actions on them

STEPS TO REPRODUCE
1. Copy an image to clipboard
2. Go to settings and configure an action
3. Eneter a pattern to match... an image object? eh...

OBSERVED RESULT
Impossible to run actions for image objects (or other file objects as well)

EXPECTED RESULT
Possibility to run actions on image objects (and other file objects such as
PDFs etc.)

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: X11

Additional information
PS: Please, add info that plasmashell includes all the useful stuff like
clipboard etc. I was trying to submit a new bug, just to spend 5 minutes
looking for clipboard widget. It is not available either in plasma or in apps,
because it is hidden under plasmashell. SO that info should be clearly stated
in the description there.

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

[kdeconnect] [Bug 446366] No way to send clipboard from Android to a desktop, if the persistent indicator is disabled.

2024-04-19 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=446366

Daniel Duris  changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 446366] No way to send clipboard from Android to a desktop, if the persistent indicator is disabled.

2024-04-19 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=446366

--- Comment #12 from Daniel Duris  ---
(In reply to John Veness from comment #11)
> I think the original bug report is now fixed, as there is now a "Send
> clipboard" button in the main UI, which works even if the persistent
> notification is hidden. Automatic clipboard sending for Android >= 10 should
> probably be discussed elsewhere.

I can confirm this workaround works well.

It would be even better if clipboard would be automatically sent without the
need for user input, but this could be opened under a different bug.

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

2024-04-17 Thread Daniel Bermond
https://bugs.kde.org/show_bug.cgi?id=478556

Daniel Bermond  changed:

   What|Removed |Added

 CC||danielberm...@gmail.com

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

[plasmashell] [Bug 476674] Segfault when taskbar shows window preview

2024-04-15 Thread Daniel M
https://bugs.kde.org/show_bug.cgi?id=476674

--- Comment #8 from Daniel M  ---
Created attachment 168568
  --> https://bugs.kde.org/attachment.cgi?id=168568=edit
New crash information added by DrKonqi

plasmashell (5.27.10) using Qt 5.15.10

This quickly occured as I was moving the mouse over an icon in the taskbar to
switch applications.

-- Backtrace (Reduced):
#11 0x7fc32486e6fa in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7fc32486ea0b in QQuickWindowPrivate::updateDirtyNodes() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7fc3248705a1 in QQuickWindowPrivate::syncSceneGraph() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#9  0x7fc322ae0cab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#12 0x7fc32314ba05 in QWindow::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5

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

[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved

2024-04-15 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485205

--- Comment #5 from Daniel Vrátil  ---
Thanks for the debug log. I regret to say that I can't see anything else in the
logs that would help narrow down the problem.

Btw I just noticed: 
Linux/KDE Plasma: Debian Bookworm 6.6.20+rpt-rpi-v8 (64-bit)

You are running on aarch64 RPI? I wonder whether there could be some
ARM-specific issue,  I think this is the first time I actually hear from
someone running KOrganizer and Akonadi on Arm :)

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

[korganizer] [Bug 485391] ToDo when enabled on Sidebar, Tasks Not Visible Until Going to the Discrete Todo view then back to Agenda.

2024-04-14 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485391

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Daniel Vrátil  ---
Hi, this issue has been fixed as part of fix for bug 484040 and will be
released in 24.05

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

[korganizer] [Bug 485185] After deleting a Todo, the next one cannot be deleted with a key

2024-04-14 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485185

Daniel Vrátil  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/pim/
   ||eventviews/-/commit/b856f11
   ||cd2498aeed3b19bfdf672549b21
   ||4d50ef
 Resolution|--- |FIXED
   Version Fixed In||24.05

--- Comment #2 from Daniel Vrátil  ---
Git commit b856f11cd2498aeed3b19bfdf672549b214d50ef by Daniel Vrátil.
Committed on 10/04/2024 at 19:56.
Pushed by dvratil into branch 'master'.

TodoView: Use current instead of selection to track active todo

Current index is implicit, so when one todo is deleted, the next one
automatically becomes current, so user can continue deleting, while
with selection, user had to manually update the selection in order to
be able to delete the next todo.
FIXED-IN: 24.05

M  +5-6src/todo/todoview.cpp
M  +1-1src/todo/todoview.h

https://invent.kde.org/pim/eventviews/-/commit/b856f11cd2498aeed3b19bfdf672549b214d50ef

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

[systemsettings] [Bug 485510] System Settings crash when trying to set auto-login

2024-04-13 Thread Daniel G
https://bugs.kde.org/show_bug.cgi?id=485510

Daniel G  changed:

   What|Removed |Added

  Component|generic-crash   |kcm_sddm
 CC||k...@david-redondo.de,
   ||k...@davidedmundson.co.uk

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

[systemsettings] [Bug 485510] System Settings crash when trying to set auto-login

2024-04-13 Thread Daniel G
https://bugs.kde.org/show_bug.cgi?id=485510

--- Comment #1 from Daniel G  ---
Created attachment 168480
  --> https://bugs.kde.org/attachment.cgi?id=168480=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[systemsettings] [Bug 485510] New: System Settings crash when trying to set auto-login

2024-04-13 Thread Daniel G
https://bugs.kde.org/show_bug.cgi?id=485510

Bug ID: 485510
   Summary: System Settings crash when trying to set auto-login
Classification: Applications
   Product: systemsettings
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: d...@live.ca
  Target Milestone: ---

Application: systemsettings (6.0.3)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.6-zen1-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.3 [CoredumpBackend]

-- Information about the crash:
In System Settings > Color & Themes > Login Screen (SDDM) > Behavior,
check the box to enable automatic login, then exit System Settings and it will
crash without applying the setting.
In addition, the 'Apply' button is greyed out and can't be clicked.

This happens with kcmutils 6.1.0, but not 6.0.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x77f69bafa86d in std::__uniq_ptr_impl >::_M_ptr (this=,
this=) at /usr/include/c++/13.2.1/bits/unique_ptr.h:199
#6  std::unique_ptr
>::get (this=, this=) at
/usr/include/c++/13.2.1/bits/unique_ptr.h:470
[...]
#9  KPageWidget::currentPage (this=0x55cb) at
/usr/src/debug/kwidgetsaddons/kwidgetsaddons-6.1.0/src/kpagewidget.cpp:124
#10 0x77f69c1eec68 in operator() (__closure=0x55cb56812e50) at
/usr/src/debug/systemsettings/systemsettings-6.0.3/core/ModuleView.cpp:282
#13 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55cb56812e40, r=, a=,
ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522


Reported using DrKonqi

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

[kscreenlocker] [Bug 485085] Unlocked desktop with apps flashes before kscreenlocker obscures the locked screen after wake-up from sleep

2024-04-13 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=485085

--- Comment #2 from Daniel Duris  ---
Another thing that seems related - once on a locked screen, if I press Esc key,
it goes to blank/black screen, where nothing is shown, not even a cursor.
Pressing Esc once more goes back to lockscreen. Esc used to defocus out of the
"enter password" dialog, now it does this. Definitely not a feature as not even
a background is shown.

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

[kwin] [Bug 484218] Windows "clicking through", plasma menu not clickable on X11

2024-04-12 Thread Daniel Bermond
https://bugs.kde.org/show_bug.cgi?id=484218

Daniel Bermond  changed:

   What|Removed |Added

 CC||danielberm...@gmail.com

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

[plasmashell] [Bug 485313] Containment (plus panel) misplaced after turning screen off and on again

2024-04-11 Thread Daniel Schmitz
https://bugs.kde.org/show_bug.cgi?id=485313

Daniel Schmitz  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Daniel Schmitz  ---
(In reply to Nate Graham from comment #3)
> Ok, then in that case plasma misplaced the whole containment rather than
> crashing or something.
> 
> Is this a setup where you have a docked laptop with the lid closed and are
> exclusively using the external screen?

Yes, that's correct. The laptop screen is closed.

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

[plasmashell] [Bug 485313] Panel gone after turning screen off and on again

2024-04-11 Thread Daniel Schmitz
https://bugs.kde.org/show_bug.cgi?id=485313

Daniel Schmitz  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from Daniel Schmitz  ---
It's just the panel, that vanishes. 
I turned the screen off and on. Panel is gone, plasmashell is still running:
```
ps -e | grep -i plasmashell
   2238 ?00:01:18 plasmashell
```

-- 
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.

2024-04-11 Thread Daniel Hurtado
https://bugs.kde.org/show_bug.cgi?id=480573

Daniel Hurtado  changed:

   What|Removed |Added

 CC||batmansgehi...@gmail.com

--- Comment #2 from Daniel Hurtado  ---
I'm experiencing the same issue here on openSUSE Tumbleweed

Elisa: 24.02.01
QT: 6.6.3
KDE Plasma: 6.0.3
KDE Framerworks: 6.0.0

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

[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved

2024-04-10 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485205

Daniel Vrátil  changed:

   What|Removed |Added

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

--- Comment #2 from Daniel Vrátil  ---
(just changing status)

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

[korganizer] [Bug 485207] Error while trying to create calendar item. Error was: Invalid parent collection

2024-04-10 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485207

Daniel Vrátil  changed:

   What|Removed |Added

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

--- Comment #2 from Daniel Vrátil  ---
(just changing status)

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

[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved

2024-04-10 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485205

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Hmm, this is weird, any changes should be written into the iCal file
immediately. I suspect there might be some deeper problem with your Akonadi
(also considering your other bug report).

Could you please run the following commands in terminal and create one or two
new events in KOrganizer?

akonadictl stop
QT_LOGGING_RULES="*=true;qt.*=false" korganizer &> log.txt

Once done, please attach the log.txt file here (double-check the log for any
personal data before uploading it) so we can try to better understand what
might be wrong.

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

[korganizer] [Bug 485207] Error while trying to create calendar item. Error was: Invalid parent collection

2024-04-10 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485207

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Hi, thanks for the report.  I can't reproduce it locally just by following your
description, could you please tell me a bit more?

1) Could you please specify in which view (agenda/month view/etc.) does this
happen? 
2) Do you have multiple calendars, or just a single one?
3) Do you have some calendar marked as default?
4) What kind of calendar is it (ical, DAV, Google, etc.?)

If you have more than one calendar, you should get a dialog that lets you
select the calendar to paste into. If you have only one calendar, the event
should automatically get pasted into it.

Could you please run KOrganizer from terminal with the following command:

  QT_LOGGING_RULES="*=true;qt.*=false" korganizer

then try to reproduce the bug and provide here the log that's printed to the
console?

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

[krita] [Bug 485305] too big on phone

2024-04-10 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=485305

--- Comment #2 from Daniel  ---
Oh. I see, thank you

On Wed, 10 Apr 2024, 15:06 Tiar,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=485305
>
> Tiar  changed:
>
>What|Removed |Added
>
> 
>  CC||tamtamy.tym...@gmail.com
>  Status|REPORTED|RESOLVED
>  Resolution|--- |NOT A BUG
>
> --- Comment #1 from Tiar  ---
> I'm sorry, but we don't support Krita on phones (only on Android tablets,
> which
> have bigger screens) for this very reason.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[plasmashell] [Bug 485313] New: Panel gone after turning screen off and on again

2024-04-10 Thread Daniel Schmitz
https://bugs.kde.org/show_bug.cgi?id=485313

Bug ID: 485313
   Summary: Panel gone after turning screen off and on again
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: danielschm...@posteo.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY

Panel gone after turning screen off and on again

STEPS TO REPRODUCE
1. turn screen off
2. turn screen on

OBSERVED RESULT

Panel gone.

EXPECTED RESULT

Panel not gone.


SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i7-1265U
Memory: 62,5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: LENOVO
Product Name: 21C1CTO1WW
System Version: ThinkPad L14 Gen 3


ADDITIONAL INFORMATION

I you have 2:45 minutes to spare, this demonstration video shows the problem:

https://www.youtube.com/watch?v=PZqI5IB7ULM=88s

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

[kde] [Bug 485305] New: too big on phone

2024-04-10 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=485305

Bug ID: 485305
   Summary: too big on phone
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Android 13.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: woox...@gmail.com
  Target Milestone: ---

Created attachment 168331
  --> https://bugs.kde.org/attachment.cgi?id=168331=edit
screenshot of the krita ui on my smasung s23 ultra.

Hrllo, i have installed the pjone version on an samsungs23 ultra, the problem i
have is that the ui turns out to be too big and i cannot create new files, load
files ect ect. Screenshot added.

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

[Bluedevil] [Bug 485306] New: Bluetooth tray icon showing not connected, but device works

2024-04-10 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=485306

Bug ID: 485306
   Summary: Bluetooth tray icon showing not connected, but device
works
Classification: Plasma
   Product: Bluedevil
   Version: 5.27.11
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: system tray
  Assignee: plasma-b...@kde.org
  Reporter: daniel.e...@gmx.de
CC: m...@ratijas.tk
  Target Milestone: ---

SUMMARY

When pairing a device - in my case a headset Jabra Evolve2 65 - the bluetooth
tray icon shows it as connected and I can disconnect it in context menu. When
later I want to reconnect the device, then it technically works, but the icon
still shows "unconnected" and in context menu - while the battery level of the
connected device is shown - it is still listed as unconnected and shows me a
"connect" button.

STEPS TO REPRODUCE
1. Pair a bluetooth device
2. Switch device off and on again
3. wait for it to connect itself

OBSERVED RESULT
Device is connected and can be used.
The icon still shows no connected devices.
When clicking the icon, the device list shows the battery level of the device.
The list shows no "disconnect" button for this device, but "connect".

EXPECTED RESULT
The icon should show one device as connected

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.6.25-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11850H @ 2.50GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 5521

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

[Bluedevil] [Bug 485306] Bluetooth tray icon showing not connected, but device works

2024-04-10 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=485306

--- Comment #1 from Daniel Eckl  ---
bluetoothctl also shows it not connected, but shows battery level, just like
Plasma does. So maybe this is an underlying problem not connected to Plasma?

bluetoothctl info "70:BF:92:D7:FB:63"
Device 70:BF:92:D7:FB:63 (public)
Name: Jabra Evolve2 65
Alias: Jabra Evolve2 65
Class: 0x00240404 (2360324)
Icon: audio-headset
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: bluetooth:v0067p24A3d0207
Battery Percentage: 0x64 (100)

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

[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU

2024-04-09 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=436240

--- Comment #17 from Daniel Eckl  ---
I'm not 100 confident if my issue is the same bug. My freezes are not as long
as the OP describes. Mine feel like just a few milliseconds. Thus I can't tell
for sure if mouse and keyboard are affected, too. I realize it only when
watching video which I mostly do using mpv. Video stops then until the popup is
fully opaque. It does not freeze when popup disappears. Consecutive popups
don't freeze. I sadly can't tell how long the timespan without popups has to be
until the next one triggers it again.

I only use Intel Graphics, the Nvidia Optimus one is too buggy on linux.

System information:

> # inxi -G
> Graphics:
>   Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
>   Device-2: NVIDIA TU117M [GeForce MX450] driver: nvidia v: 550.67
>   Device-3: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
> type: USB
>   Device-4: Logitech StreamCam
> driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
>   Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 23.2.5 driver: X:
> loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1: 1920x1080
> 2: 1920x1080 3: 1920x1080~60Hz
>   API: EGL v: 1.5 drivers: iris,nvidia,swrast
> platforms: x11,surfaceless,device
>   API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.2-manjaro1.1
> renderer: Mesa Intel UHD Graphics (TGL GT1)
>   API: Vulkan v: 1.3.279 drivers: intel,nvidia surfaces: xcb,xlib

chosen parts from mpv verbose output:
> [vd] Looking at hwdec h264-vaapi...
> [vo/gpu] Loading hwdec drivers for format: 'vaapi'
> [vo/gpu] Loading hwdec driver 'vaapi'
> [vo/gpu/vaapi] using EGL dmabuf interop
> [vo/gpu/vaapi] Trying to open a x11 VA display...
> [vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.20
> [vo/gpu/vaapi] Going to probe surface formats (may log bogus errors)...
> [vo/gpu/vaapi] Done probing surface formats.
> [...]
> [vd] Using hardware decoding (vaapi).
> [...]
> [cplayer] VO: [gpu] 1920x1080 vaapi[nv12]

vainfo shows:
> vainfo: VA-API version: 1.20 (libva 2.20.1)
> vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 ()

Compositing part from kinfocenter:
> Compositing
> ===
> Compositing is active
> Compositing Type: OpenGL
> OpenGL vendor string: Intel
> OpenGL renderer string: Mesa Intel(R) UHD Graphics (TGL GT1)
> OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.2-manjaro1.1
> OpenGL platform interface: GLX
> OpenGL shading language version string: 4.60
> Driver: Intel
> GPU class: Tiger Lake
> OpenGL version: 4.6
> GLSL version: 4.60
> Mesa version: 24.0.2
> X server version: 1.21.1
> Linux kernel version: 6.6.25
> Direct rendering: Requires strict binding: yes
> GLSL shaders:  yes
> Texture NPOT support:  yes
> Virtual Machine:  no
> OpenGL 2 Shaders are used

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

[korganizer] [Bug 483504] holiday display doesn't update after picking holidays

2024-04-08 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483504

Daniel Vrátil  changed:

   What|Removed |Added

   Version Fixed In||24.05
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/pim/
   ||korganizer/-/commit/37bf211
   ||9cf46302df5c266a886ac575998
   ||44030d
 Status|ASSIGNED|RESOLVED

--- Comment #2 from Daniel Vrátil  ---
Git commit 37bf2119cf46302df5c266a886ac57599844030d by Daniel Vrátil.
Committed on 08/04/2024 at 15:50.
Pushed by dvratil into branch 'master'.

Remove options from KOPrefs that already exist in CalendarSupport::KCalPrefs

Some of the holiday-related options were duplicated in both KOPrefs (KOrganizer
config) and KCalPrefs (CalendarSupport config used by other components like
EventViews). While both objects operate on top of the same config file, if the
holidays option got changed through one of the objects, the other one was
unaware
of the change.

This caused a weird behavior where re-configuring holidays in KOrganizer showed
up only where KOPrefs object was used to read the configuration, but wouldn't
show up in event views, which use KCalPrefs until the application was
restarted.
FIXED-IN: 24.05

M  +2-2src/calendarview.cpp
M  +2-2src/kocorehelper.h
M  +8-7src/prefs/koprefsdialogtime.cpp
M  +0-17   src/settings/korganizer.kcfg

https://invent.kde.org/pim/korganizer/-/commit/37bf2119cf46302df5c266a886ac57599844030d

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

[korganizer] [Bug 485185] After deleting a Todo, the next one cannot be deleted with a key

2024-04-07 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485185

Daniel Vrátil  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[korganizer] [Bug 485185] New: After deleting a Todo, the next one cannot be deleted with a key

2024-04-07 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=485185

Bug ID: 485185
   Summary: After deleting a Todo, the next one cannot be deleted
with a key
Classification: Applications
   Product: korganizer
   Version: 6.0.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: todoview
  Assignee: kdepim-b...@kde.org
  Reporter: dvra...@kde.org
  Target Milestone: ---

Deleting a Todo with [Del] key automatically selects the next todo, but the
[Del] key doesn't work for it, one has to either click it, or go to the next
one and then go back to the previous one with arrow keys, after that [Del] key
works again to delete the Todo.

The view only reacts to "Selection" change, but the view automatically
re-selecting the next item after the orignal one was deletected doesn't count
as a selection, I guess.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: git master
KDE Plasma Version: 6.0
KDE Frameworks Version:  git master
Qt Version: 6.6

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

[kscreenlocker] [Bug 485085] New: Unlocked desktop with apps flashes before kscreenlocker obscures the locked screen after wake-up from sleep

2024-04-05 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=485085

Bug ID: 485085
   Summary: Unlocked desktop with apps flashes before
kscreenlocker obscures the locked screen after wake-up
from sleep
Classification: Plasma
   Product: kscreenlocker
   Version: 6.0.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kdeb...@staznosti.sk
  Target Milestone: ---

SUMMARY
Unlocked screen flashes showing potentially private info before kscreenlocker
kicks in and obscures the screen

STEPS TO REPRODUCE
1. Sleep KDE
2. Wake up computer
3. Flash of unlocked screen before kscreenlocker locks the screen

OBSERVED RESULT
Flash of unlocked screen before kscreenlocker locks the screen

EXPECTED RESULT
Kscreenlocker launched immediately, unlocked screen not visible

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: X11

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

[neon] [Bug 484987] Repair failed for Repairing failed offline update in Discover on update+reboot

2024-04-03 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=484987

--- Comment #3 from Daniel Duris  ---
And solution posted here:
https://discuss.kde.org/t/fatal-error-error-while-installing-package-trying-to-overwrite-usr-lib-x86-64-linux-gnu-libkcolorpicker-so-0-which-is-also-in-package-libkcolorpicker0-and-gwenview-no-longer-starts-up/13435

sudo dpkg --remove --force-remove-reinstreq libkcolorpicker0
$ sudo apt --fix-broken install

However, I understand these are some colliding  packages, however my bug report
is mostly about UI / UX of the failed repair. If Discover is unable to fix this
(however easy it seems to be anyhow), it should notify the user why it is
unable to do it and what should user do in order to fix it.

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

[neon] [Bug 484987] Repair failed for Repairing failed offline update in Discover on update+reboot

2024-04-03 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=484987

--- Comment #2 from Daniel Duris  ---
[code]
:~$ sudo pkcon update
Getting updates [=]
Finished[=]
Loading cache   [=]
Testing changes [=]
Finished[ ] (0%)
The following packages have to be updated:
libkcolorpicker-qt6-0-0.3.1-0xneon+22.04+jammy+release+build2.amd64   
QToolButton-like widget with color selection popup menu (lib)
Proceed with changes? [N/y] y

[=]
Updating packages   [=]
Loading cache   [=]
Running [=]
Finished[=]
Fatal error: Error while installing package: trying to overwrite
'/usr/lib/x86_64-linux-gnu/libkColorPicker.so.0', which is also inpackage
libkcolorpicker0
[/code]

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

[neon] [Bug 484987] Repair failed for Repairing failed offline update in Discover on update+reboot

2024-04-03 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=484987

--- Comment #1 from Daniel Duris  ---
Created attachment 168104
  --> https://bugs.kde.org/attachment.cgi?id=168104=edit
notifications

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

[neon] [Bug 484987] New: Repair failed for Repairing failed offline update in Discover on update+reboot

2024-04-03 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=484987

Bug ID: 484987
   Summary: Repair failed for Repairing failed offline update in
Discover on update+reboot
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: kdeb...@staznosti.sk
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

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

SUMMARY
Discover shows bunch of messages

STEPS TO REPRODUCE
1. Update system
2. Restart

OBSERVED RESULT
Failed...

EXPECTED RESULT
Success

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.

[korganizer] [Bug 483707] When selecting a end date for a recurring event the wrong date is saved

2024-04-02 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483707

Daniel Vrátil  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/fram
   ||eworks/kcalendarcore/-/comm
   ||it/f74313db7456f20a16c7a741
   ||33218b85b123c093
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
   Version Fixed In||6.1.0

--- Comment #2 from Daniel Vrátil  ---
Git commit f74313db7456f20a16c7a74133218b85b123c093 by Daniel Vrátil.
Committed on 29/03/2024 at 14:31.
Pushed by cullmann into branch 'master'.

Fix conversion of date-only icaltimetype to UTC QDateTime

The code in readICalDateTime converts the values in icaltimetype structure
to a QDateTime, using the timezone specified in the icaltimetype. If the
icaltimetype is day-only (e.g. in all-day incidence) then it does not
have any timezone information and so Qt::LocalTime is assumed, and a new
QDateTime is constructed that happens on the midnight (beginning) of the
specified day, in user's current local timezone.

In some cases, the function is asked to return the QDateTime in UTC timezone
(for fields that the RFC mandates be always in UTC, like RRULE's UNTIL).
If the user's local timezone is in positive UTC offset, the QDateTime
gets converted to UTC, which shifts those \"all-day\" QDateTimes back
by one day. Later in the code, when it realizes it should be dealing only
with a date, the timezone information is discarded and we end up with a
QDate(Time) that is off by one day compared to what's stored in the iCal data.

This fixes simplifies the handling of day-only icaltimetype and makes sure
to construct the QDateTime already in the correct timezone (i.e. UTC) so
no more conversions are necessary.
FIXED-IN: 6.1.0

M  +31   -0autotests/testicalformat.cpp
M  +1-0autotests/testicalformat.h
M  +4-4src/icalformat_p.cpp

https://invent.kde.org/frameworks/kcalendarcore/-/commit/f74313db7456f20a16c7a74133218b85b123c093

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

[kwin] [Bug 484797] New wayland mouse warp cursor flickers and skips when it is captive to certain applications

2024-04-01 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

Daniel Ellis  changed:

   What|Removed |Added

Summary|New wayland mouse warp  |New wayland mouse warp
   |cursor flickers, skips when |cursor flickers and skips
   |moving over a capturing |when it is captive to
   |surface |certain applications

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

[kwin] [Bug 484797] New wayland mouse warp cursor flickers, skips when moving over a capturing surface

2024-04-01 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

Daniel Ellis  changed:

   What|Removed |Added

Summary|New wayland mouse warp  |New wayland mouse warp
   |cursor flickers, skips when |cursor flickers, skips when
   |'captured' by the active|moving over a capturing
   |application |surface

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

[kwin] [Bug 484797] New wayland mouse warp cursor flickers, skips when 'captured' by the active application

2024-04-01 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

Daniel Ellis  changed:

   What|Removed |Added

Summary|New wayland mouse warp  |New wayland mouse warp
   |cursor flickers, skips when |cursor flickers, skips when
   |moving over a capturing |'captured' by the active
   |surface |application

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

[kwin] [Bug 484797] New wayland mouse warp cursor flickers, skips when moving over a capturing surface

2024-04-01 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

Daniel Ellis  changed:

   What|Removed |Added

Summary|Wayland mouse warp cursor   |New wayland mouse warp
   |flickers, skips |cursor flickers, skips when
   ||moving over a capturing
   ||surface

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

[krename] [Bug 484786] KRename service not appearing in Dolphin context menu

2024-04-01 Thread Daniel Mader
https://bugs.kde.org/show_bug.cgi?id=484786

Daniel Mader  changed:

   What|Removed |Added

 CC||danielstefanmader+kde@gmail
   ||.com

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

[neon] [Bug 484813] New: Major crash of the whole system, system unusable, SDDM+Plasma unable to boot up

2024-03-31 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=484813

Bug ID: 484813
   Summary: Major crash of the whole system, system unusable,
SDDM+Plasma unable to boot up
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: kdeb...@staznosti.sk
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY
After the latest upgrade the whole system became unusable except for switching
to the console.

STEPS TO REPRODUCE
1. Hard to say, large update in past two weeks with about 1,2 GB of data messed
up the whole system
2. pkcon update clearly failing, removing some absolute necessary dependencies
3. apt full-upgrade installing everything, but still not working
4. had to reinstall everything by forcing apt to --reinstall
5. probably some config files from ~/.config were an issue for neon/plasma to
fail, I can provide these as I have backed them up
6. once the whole config dir was removed (and everything force reinstalled) the
system was usuable again - ofc had to reconfigure everything for hours from the
defaults

OBSERVED RESULT
System unusable, both SDDM and plasma unable to boot

EXPECTED RESULT
Everything working

SOFTWARE/OS VERSIONS (after fixing the system)
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Various info from the logs or while trying to launch plasmashell (taken from my
browser search history) (also a short rant - inability to find clear logs in
/var/logs of plasma /kde /neon is tragic for cases like this):
failed to find a kirigami platform plugin for style fusion
binding loop detected
graphsplasmoid does not match the format 
applications.menu not found in Qlist /etc/xdg
offer service offset line 333 kbuildservicefactory (i.e. kbuildsyscoca6 failing
with some ASSERT error on this line)
kbuildsycoca6 Q_ASSERT(offer.service()->offset() != 0);
sysdeps unix sysv poll no such file
locale changed to kr_KO.UTF-8 LANG when trying to fix the system (very weird as
it wasn't even configured to this before ever) - e.g. after forcing apt to
reinstall both neon-desktop and kde-full, plasma-desktop etc.

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

[kwin] [Bug 484797] Wayland mouse warp cursor flickers, skips

2024-03-31 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

--- Comment #2 from Daniel Ellis  ---
Created attachment 167975
  --> https://bugs.kde.org/attachment.cgi?id=167975=edit
Moving cursor in straight lines - cursor jumps around

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

[kwin] [Bug 484797] Wayland mouse warp cursor flickers, skips

2024-03-31 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

--- Comment #1 from Daniel Ellis  ---
Created attachment 167974
  --> https://bugs.kde.org/attachment.cgi?id=167974=edit
Flickering while moving through menus

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

[kwin] [Bug 484797] New: Wayland mouse warp cursor flickers, skips

2024-03-31 Thread Daniel Ellis
https://bugs.kde.org/show_bug.cgi?id=484797

Bug ID: 484797
   Summary: Wayland mouse warp cursor flickers, skips
Classification: Plasma
   Product: kwin
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ninjaqu...@protonmail.com
  Target Milestone: ---

Created attachment 167973
  --> https://bugs.kde.org/attachment.cgi?id=167973=edit
Video showing the cursor being weird

https://invent.kde.org/plasma/kwin/-/issues/85

SUMMARY

The mouse cursor flickers while in motion in Star Citizen, which was previously
affected by the camera-snapping bug which has been resolved with the recent
mouse-warp commit:

https://invent.kde.org/plasma/kwin/-/commit/630ba5fab4b02c2b496553c79d4a315da9271b53

- This doesn't affect all areas (menus appear unaffected)
- The cursor behaves "normally" when moving the cursor over the game window
when it is unfocused
- Having a few windows open in the background seems to make the issue more
pronounced

STEPS TO REPRODUCE
1. Launch a game that was previously affected by the snap-to-bottom-left issue
(i.e Star Citizen)
2. Summon the cursor (i.e. F while in first person in star citizen OR open the
inventory (I)
3. Observe where the cursor appeared
4. Summon the cursor again, observe
5. Repeat 2-4 a few times

OBSERVED RESULT
The cursor appears in different locations

EXPECTED RESULT
The cursor is consistently centered

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.0.3
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
VRR is active, the framerate is relatively high - the cursor is flickering *a
lot*.
The input is smooth in the video, but the cursor can be skipping multiple times

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

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-30 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=483163

Daniel Duris  changed:

   What|Removed |Added

Version|6.0.1   |6.0.3

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

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-30 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=483163

Daniel Duris  changed:

   What|Removed |Added

   Version Fixed In|6.0.2   |

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

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-30 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #19 from Daniel Duris  ---
(In reply to Daniel Duris from comment #18)
> I can confirm that switching to Breeze Light under Plasma Style removed
> black locking screen. Switching back to Breeze and black lock screen is
> immediately back.

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Graphics Processor: AMD Radeon Graphics

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

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-30 Thread Daniel Duris
https://bugs.kde.org/show_bug.cgi?id=483163

Daniel Duris  changed:

   What|Removed |Added

 CC||kdeb...@staznosti.sk

--- Comment #18 from Daniel Duris  ---
I can confirm that switching to Breeze Light under Plasma Style removed black
locking screen. Switching back to Breeze and black lock screen is immediately
back.

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

[frameworks-kiconthemes] [Bug 484639] Fallback to Breeze ignored by KIconLoader because of wrong global initialization order

2024-03-28 Thread Daniel Bermond
https://bugs.kde.org/show_bug.cgi?id=484639

Daniel Bermond  changed:

   What|Removed |Added

 CC||danielberm...@gmail.com

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

[korganizer] [Bug 483823] New event button does not use currently selected date as default

2024-03-27 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483823

Daniel Vrátil  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/pim/
   ||eventviews/-/commit/7267eae
   ||b9acfbe35f562ae4ad3be64313c
   ||85a2e1
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
   Version Fixed In||24.02.2

--- Comment #3 from Daniel Vrátil  ---
Git commit 7267eaeb9acfbe35f562ae4ad3be64313c85a2e1 by Daniel Vrátil.
Committed on 27/03/2024 at 14:03.
Pushed by dvratil into branch 'release/24.02'.

Don't overwrite valid date in eventDurationHint()

The view's hint function is called whenever a new event/todo/journal
is being created from KOrganizer. When the new incidence is being
created via context menu in the side-pane calendar preview, the selected
date might be different from the date currently selected in the main
view. In such case, the view should only provide a hint (e.g. about
duration or allday-ness of the new event) but shouldn't replace the
valid dates.
FIXED-IN: 24.02.2

M  +9-0src/agenda/agendaview.cpp
M  +9-0src/month/monthview.cpp
M  +19   -4src/timeline/timelineview.cpp

https://invent.kde.org/pim/eventviews/-/commit/7267eaeb9acfbe35f562ae4ad3be64313c85a2e1

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

[korganizer] [Bug 483707] When selecting a end date for a recurring event the wrong date is saved

2024-03-26 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483707

Daniel Vrátil  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dvra...@kde.org
 Status|REPORTED|CONFIRMED

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

[korganizer] [Bug 483822] 23.08.2 -> 24.02 upgrade: all caldav calenders use now a new colors in the views

2024-03-26 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483822

Daniel Vrátil  changed:

   What|Removed |Added

Version|5.14.0  |6.0.0
   Version Fixed In||24.02.2

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

[korganizer] [Bug 483822] 23.08.2 -> 24.02 upgrade: all caldav calenders use now a new colors in the views

2024-03-26 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483822

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Daniel Vrátil  ---
This has been fixed in git master in the meanwhile:

https://commits.kde.org/pim/eventviews/982bed25ef8dd971033ddf8e4a3ee73f85678e75
https://commits.kde.org/pim/eventviews/b63758052aa58cd0958597925b3af4eaa3f7f59c
https://commits.kde.org/pim/eventviews/6785553c39bca4d6cb483eceb99d5b32b8345737

I have cherry-picked the commits to release/24.02 branch, so it will be fixed
in 24.02.2.

There's still the separate issue of not being able to reset the calendar color
to default, I'll look into it.

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

[korganizer] [Bug 483823] New event button does not use currently selected date as default

2024-03-26 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=483823

Daniel Vrátil  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||dvra...@kde.org

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

[Merkuro] [Bug 484529] New: Merkuro Contacts does not alphabetically sort contacts after changing contact name

2024-03-26 Thread Daniel Rees
https://bugs.kde.org/show_bug.cgi?id=484529

Bug ID: 484529
   Summary: Merkuro Contacts does not alphabetically sort contacts
after changing contact name
Classification: Applications
   Product: Merkuro
   Version: 24.02.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: d...@danrees.me
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 167797
  --> https://bugs.kde.org/attachment.cgi?id=167797=edit
Contacts screenshot

STEPS TO REPRODUCE
1. Edit a contact with no name (e.g. only email address) to include a name

OBSERVED RESULT
Edited contacts don't move into alphabetical order

EXPECTED RESULT
Contacts should be automatically sorted into alphabetical order once changes
made to name. 

Also, there should be an option to sort by surname or first name.

SOFTWARE/OS VERSIONS
Arch Linux / Plasma 6.0.2

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

[Merkuro] [Bug 484528] New: Keyboard shortcut / menu option to delete contact in Merkuro Contact

2024-03-26 Thread Daniel Rees
https://bugs.kde.org/show_bug.cgi?id=484528

Bug ID: 484528
   Summary: Keyboard shortcut / menu option to delete contact in
Merkuro Contact
Classification: Applications
   Product: Merkuro
   Version: 24.02.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: d...@danrees.me
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY

It is possible to press "Delete contact" button to (obviously) delete a
contact. 

I would expect press 'Del' key on the keyboard should have the same effect by
default. There is no option in keyboard shortcuts to map this action either.
Similarly I would expect Edit -> Delete or a similar menu item to provide for
deleting a contact.

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

[korganizer] [Bug 484040] Filters don't work

2024-03-26 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=484040

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/pim/
   ||korganizer/-/commit/fe21a20
   ||a78587f6bf1c693a435028f8bf9
   ||964854
   Version Fixed In||24.02.3
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Daniel Vrátil  ---
Git commit fe21a20a78587f6bf1c693a435028f8bf9964854 by Daniel Vrátil.
Committed on 26/03/2024 at 14:38.
Pushed by dvratil into branch 'release/24.02'.

Fix calendar view filters not being applied

Selecting a filter in View -> Filters did not apply cause the
filter to be applied to the individual CollectionCalendars,
only to the global ETMCalendar, which is not used as a source
of events, though.
FIXED-IN: 24.02.3

M  +26   -0src/calendarview.cpp
M  +9-0src/calendarview.h

https://invent.kde.org/pim/korganizer/-/commit/fe21a20a78587f6bf1c693a435028f8bf9964854

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

[Breeze] [Bug 484485] New: Breeze dark theme change bug

2024-03-25 Thread Daniel Rees
https://bugs.kde.org/show_bug.cgi?id=484485

Bug ID: 484485
   Summary: Breeze dark theme change bug
Classification: Plasma
   Product: Breeze
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color scheme
  Assignee: plasma-b...@kde.org
  Reporter: d...@danrees.me
  Target Milestone: ---

SUMMARY

Changing theme from breeze to breeze-dark results in panel being non-responsive
/ not changing theme in panel itself.

STEPS TO REPRODUCE
1. Open system settings
2. Select breeze dark theme while breeze them is selected

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

[plasmashell] [Bug 484465] New: Panel settings position incorrect

2024-03-25 Thread Daniel Rees
https://bugs.kde.org/show_bug.cgi?id=484465

Bug ID: 484465
   Summary: Panel settings position incorrect
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: d...@danrees.me
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 167751
  --> https://bugs.kde.org/attachment.cgi?id=167751=edit
Screen shot

***
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

Panel settings box covers add widgets / add panel etc bar when in panel edit
mode - making the underlying window impossible to access.

Position in panel settings box does not correctly move panel to bottom or right
when panel in 'top' position - instead it moves the panel settings window
itself.

STEPS TO REPRODUCE
1. Move panel to 'top' position following clean install 
2. Right click on panel to enter edit mode

Arch Linux  / Plasma 6.0.2

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

[Ruqola] [Bug 481400] Login using Personal Access Token

2024-03-25 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=481400

--- Comment #13 from Daniel Eckl  ---
I think the PAT part is absolutely flawless. I noticed that when I add a new
server and enter the server url with a trailing slash like
"https://chat.server.name/; the interface connects like forever, simply
removing the slash works fine. I guess that was already the case before and
this is unrelated.

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

[korganizer] [Bug 476642] Wrong calculation in week recurrence after 15 iterations

2024-03-25 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=476642

--- Comment #25 from Daniel Vrátil  ---
Ha, this might be the key!

> but on the weeks 18-24.03.2024 and 25-31.03.2024 it is again incorrectly 
> absent for 2 weeks in a row

Coincidentally, those dates are immediately around DST change dates in Europe:

DST end: October 29th, 2023 (affects next immediate recurrence, should be on
November 4th, is on Nov 11th)
DST start: March 31st, 2024 (affects previous immediate recurrence, should be
on March 23rd, is missing)

This massively narrows down the scope of code I need to dig through now :-)
I'll see if I can spot the bug in the code or create some artificial testcase.
Still curious what's could be the last bit of settings that I'm missing that
makes the bug to manifest...

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

[korganizer] [Bug 484040] Filters don't work

2024-03-25 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=484040

--- Comment #3 from Daniel Vrátil  ---
Git commit fd6d6bd3d7c24b95a8d91b0233ada61a08658738 by Daniel Vrátil.
Committed on 22/03/2024 at 14:22.
Pushed by dvratil into branch 'release/24.02'.

Apply current view filter on the Todo model as well

Previously the Todo model was derived from ETMCalendar, which internally
had a CalFilterProxyModel to filter out incidences based on a CalFilter.
Nowadays we are building right on top of an ETM, so we need to apply the
filter manually.

It's a little hacky solution, but it is achieved by taking the current
filter from one of the active calendars and manually filtering each
Todo through it in the TodoViewSortFilterProxyModel.
FIXED-IN: 24.02.3

M  +9-1src/todo/todoview.cpp
M  +23   -2src/todo/todoviewsortfilterproxymodel.cpp
M  +12   -0src/todo/todoviewsortfilterproxymodel.h

https://invent.kde.org/pim/eventviews/-/commit/fd6d6bd3d7c24b95a8d91b0233ada61a08658738

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

[plasmashell] [Bug 484436] New: Plasma crashed while moving pannel

2024-03-25 Thread Daniel Stellmon
https://bugs.kde.org/show_bug.cgi?id=484436

Bug ID: 484436
   Summary: Plasma crashed while moving pannel
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dste...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-16-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Plasma crashed and lost all the information about the pannel on my main
monitor. I moved the pannel from the top of the screen to the bottom, where I
prefer it, and Plasma crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 1343 (plasmashell)
   UID: 1000 (zyzyx)
   GID: 1000 (zyzyx)
Signal: 11 (SEGV)
 Timestamp: Mon 2024-03-25 01:43:56 CDT (43s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (zyzyx)
   Boot ID: 3d7d0bfd5b07427d8be746080824172f
Machine ID: 359606d9e3ec41c2bf66e2f46063cd40
  Hostname: JarJar
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.3d7d0bfd5b07427d8be746080824172f.1343.171134903600.zst
(present)
  Size on Disk: 49.1M
   Message: Process 1343 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64
Stack trace of thread 1343:
#0  0x7fc9950aed14 pthread_sigmask (libc.so.6 + 0x8fd14)
#1  0x7fc99505b239 sigprocmask (libc.so.6 + 0x3c239)
#2  0x7fc9976dee9b _ZN6KCrash15setCrashHandlerEPFviE
(libKF5Crash.so.5 + 0x4e9b)
#3  0x7fc9976dfb3e _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b3e)
#4  0x7fc99505b050 n/a (libc.so.6 + 0x3c050)
#5  0x7fc996c77c86 _ZN5QtQml18qmlExecuteDeferredEP7QObject
(libQt5Qml.so.5 + 0x277c86)
#6  0x7fc997149059
_ZN16QQuickTransition7prepareER5QListI17QQuickStateActionERS0_I12QQmlPropertyEP23QQuickTransitionManagerP7QObject
(libQt5Quick.so.5 + 0x149059)
#7  0x7fc99713e997
_ZN23QQuickTransitionManager10transitionERK5QListI17QQuickStateActionEP16QQuickTransitionP7QObject
(libQt5Quick.so.5 + 0x13e997)
#8  0x7fc9954dd50d _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x2dd50d)
#9  0x7fc996362fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#10 0x7fc9954b16f8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b16f8)
#11 0x7fc995508c31 _ZN14QTimerInfoList14activateTimersEv
(libQt5Core.so.5 + 0x308c31)
#12 0x7fc9955094c4 n/a (libQt5Core.so.5 + 0x3094c4)
#13 0x7fc993f017a9 g_main_context_dispatch
(libglib-2.0.so.0 + 0x547a9)
#14 0x7fc993f01a38 n/a (libglib-2.0.so.0 + 0x54a38)
#15 0x7fc993f01acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#16 0x7fc995509836
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309836)
#17 0x7fc9954b017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b017b)
#18 0x7fc9954b82d6 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2b82d6)
#19 0x561a0aecbdc3 n/a (plasmashell + 0x26dc3)
#20 0x7fc99504624a n/a (libc.so.6 + 0x2724a)
#21 0x7fc995046305 __libc_start_main (libc.so.6 + 0x27305)
#22 0x561a0aecbee1 n/a (plasmashell + 0x26ee1)

Stack trace of thread 1349:
#0  0x7fc99511b15f __poll (libc.so.6 + 0xfc15f)
#1  0x7fc99692fcd6 n/a (libQt5WaylandClient.so.5 + 0x7acd6)
#2  0x7fc9952cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#3  0x7fc9950a8134 n/a (libc.so.6 + 0x89134)
#4  0x7fc9951287dc n/a (libc.so.6 + 0x1097dc)

Stack trace of thread 1351:
#0  0x7fc9952cc2af _ZN6QMutex6unlockEv 

[Ruqola] [Bug 481400] Login using Personal Access Token

2024-03-25 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=481400

--- Comment #11 from Daniel Eckl  ---
I'm using Ruqola nightly right now and PAT Login works flawlessly, thank you so
much!

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

[dolphin] [Bug 3212] Option to hide backup files as well as dotfiles?

2024-03-24 Thread Daniel Scharrer
https://bugs.kde.org/show_bug.cgi?id=3212

Daniel Scharrer  changed:

   What|Removed |Added

 CC||dan...@constexpr.org

--- Comment #86 from Daniel Scharrer  ---
Please revert this. This 100% goes against user expectations on a unix system.

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

[korganizer] [Bug 481031] Crash when opening

2024-03-22 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=481031

--- Comment #3 from Daniel Vrátil  ---
Git commit 9bf3506cd0788d164ac3fe41a7510bb6143a2866 by Daniel Vrátil.
Committed on 22/03/2024 at 09:17.
Pushed by dvratil into branch 'master'.

MemoryCalendar: log details about duplicate events before asserting

When trying to insert an incidence into a MemoryCalendar that has a UID
that is already present in the calendar, first log as much as possible
before asserting that it's the same insert being re-inserted.

This does not fix anything, but might help with diagnostics, and provides
some useful and actionable output before asserting.

M  +8-3src/memorycalendar.cpp

https://invent.kde.org/frameworks/kcalendarcore/-/commit/9bf3506cd0788d164ac3fe41a7510bb6143a2866

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

[korganizer] [Bug 482400] Bug KOrganizer creazione/modifica eventi/attività

2024-03-22 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=482400

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #3 from Daniel Vrátil  ---
OK, not much I can do with this info, sorry. Closing.

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

[korganizer] [Bug 484040] Filters don't work

2024-03-22 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=484040

Daniel Vrátil  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||dvra...@kde.org

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

[korganizer] [Bug 476642] Wrong calculation in week recurrence after 15 iterations

2024-03-22 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=476642

--- Comment #22 from Daniel Vrátil  ---
Oh and also version of Qt (at least the qtbase package
(qt-base/qt5-base/qtbase-qt5... depends on the distro), please.

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

[korganizer] [Bug 476642] Wrong calculation in week recurrence after 15 iterations

2024-03-22 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=476642

Daniel Vrátil  changed:

   What|Removed |Added

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

--- Comment #21 from Daniel Vrátil  ---
Thanks for all the data, unfortunately I wasn't able to reproduce the problem
in any of three different VMs.

Could you please specify distro and exact KOrganizer version? Can you think of
any other special settings you might have that could influence this?

Also, could you please check whether the bug is also present in e.g. Agenda
view in week view (e.g. whether the event is shown correctly on week 44 or
whether it's incorrectly shifted to week 45)?

Also, in the small calendar preview in the top-left corner, the dates on which
an even occur should be highlighted in bold. Do  you see the correct boldened
dates (i.e. 1.11. and 15.11. or is 8.11. boldened?)

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

[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU

2024-03-21 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=436240

Daniel Eckl  changed:

   What|Removed |Added

   Platform|openSUSE|Manjaro
Version|5.21.4  |5.27.11

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

[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU

2024-03-21 Thread Daniel Eckl
https://bugs.kde.org/show_bug.cgi?id=436240

Daniel Eckl  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #13 from Daniel Eckl  ---
I have this problem every day and I don't understand why it can be closed just
if one person hasn't seen it for some time.

If one needs a recent reproduction scenario then please just ask.

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

[kpat] [Bug 484059] New: KPatience crashs on undo function

2024-03-20 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=484059

Bug ID: 484059
   Summary: KPatience crashs on undo function
Classification: Applications
   Product: kpat
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: k...@istiophorus.org
CC: kde-games-b...@kde.org
  Target Milestone: ---

SUMMARY

KPatience 24.02.0 crashes on clicking undo function.

STEPS TO REPRODUCE
1.  Open KPat, Start a game, e.g. "Grandfather"
2.  Click redeal
3.  Click undo

OBSERVED RESULT
The window freezes and has to be terminated forcefully.

ADDITIONAL INFORMATION
GDB / debuginfod does not find debugging symbols, however gdb shows "alloc():
invalid next size" with following backtrace:
# …
[New Thread 0x7fff969196c0 (LWP 23412)]
[Thread 0x7fff969196c0 (LWP 23412) exited]
realloc(): invalid next size

Thread 1 "kpat" received signal SIGABRT, Aborted.
0x75aab32c in ?? () from /usr/lib/libc.so.6
(gdb) bt
#0  0x75aab32c in ??? () at /usr/lib/libc.so.6
#1  0x75a5a6c8 in raise () at /usr/lib/libc.so.6
#2  0x75a424b8 in abort () at /usr/lib/libc.so.6
#3  0x75a43395 in ??? () at /usr/lib/libc.so.6
#4  0x75ab52a7 in ??? () at /usr/lib/libc.so.6
#5  0x75ab934c in ??? () at /usr/lib/libc.so.6
#6  0x75aba1a6 in realloc () at /usr/lib/libc.so.6
#7  0x7622e4e8 in QArrayData::reallocateUnaligned(QArrayData*, void*,
long long, long long, QArrayData::AllocationOption) () at
/usr/lib/libQt6Core.so.6
#8  0x77c89d5c in ??? () at /usr/lib/libkcardgame.so
#9  0x77c6d3b0 in ??? () at /usr/lib/libkcardgame.so
#10 0x77c7818b in KCardPile::insert(int, KCard*) () at
/usr/lib/libkcardgame.so
#11 0x5557acbc in ??? ()
#12 0x5557fe19 in ??? ()
#13 0x76190ca9 in ??? () at /usr/lib/libQt6Core.so.6
#14 0x76ae2077 in QAction::activate(QAction::ActionEvent) () at
/usr/lib/libQt6Gui.so.6
#15 0x771feb1c in ??? () at /usr/lib/libQt6Widgets.so.6
#16 0x7720d245 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /usr/lib/libQt6Widgets.so.6
#17 0x7731f6fe in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/libQt6Widgets.so.6
#18 0x77145065 in QWidget::event(QEvent*) () at
/usr/lib/libQt6Widgets.so.6
#19 0x770f438b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt6Widgets.so.6
#20 0x770f6be8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt6Widgets.so.6
#21 0x76139818 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt6Core.so.6
#22 0x770f2327 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /usr/lib/libQt6Widgets.so.6
#23 0x77157a97 in ??? () at /usr/lib/libQt6Widgets.so.6
#24 0x77158db0 in ??? () at /usr/lib/libQt6Widgets.so.6
#25 0x770f438b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt6Widgets.so.6
#26 0x76139818 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt6Core.so.6
#27 0x7676f9e5 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib/libQt6Gui.so.6
#28 0x767da85c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt6Gui.so.6
#29 0x76bb26c4 in ??? () at /usr/lib/libQt6Gui.so.6
#30 0x74622f69 in ??? () at /usr/lib/libglib-2.0.so.0
#31 0x746813a7 in ??? () at /usr/lib/libglib-2.0.so.0
#32 0x74621162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#33 0x763739c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#34 0x76143d6e in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#35 0x7613c2b8 in QCoreApplication::exec() () at
/usr/lib/libQt6Core.so.6
#36 0x5557234d in ??? ()
#37 0x75a43cd0 in ??? () at /usr/lib/libc.so.6
#38 0x75a43d8a in __libc_start_main () at /usr/lib/libc.so.6
#39 0x555748d5 in ??? ()
(gdb)

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

[kwin] [Bug 483503] Window rules: Force app to specific screen don't work with Wayland

2024-03-18 Thread daniel
https://bugs.kde.org/show_bug.cgi?id=483503

daniel  changed:

   What|Removed |Added

 CC||pop...@gmail.com

--- Comment #1 from daniel  ---
I have the same issue with Dolphin, konsole, system settings... pretty much
everything  starts on the wrong screen no matter what settings I change on
Wayland session.

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

  1   2   3   4   5   6   7   8   9   10   >