from:"Florian"

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

--- Comment #6 from Florian RICHER  ---
Created attachment 168473
  --> https://bugs.kde.org/attachment.cgi?id=168473=edit
More information with zagg about this bug

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia (Sub wayland session for dev)

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

--- Comment #5 from Florian RICHER  ---
Created attachment 168472
  --> https://bugs.kde.org/attachment.cgi?id=168472=edit
wayland-info command result

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia (Sub wayland session for dev)

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

--- Comment #4 from Florian RICHER  ---
Created attachment 168471
  --> https://bugs.kde.org/attachment.cgi?id=168471=edit
drm_info command result

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia (Sub wayland session for dev)

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

--- Comment #3 from Florian RICHER  ---
(In reply to Florian RICHER from comment #2)
> (In reply to Florian RICHER from comment #1)
> > src/gbm\_drv\_common.c:130: GBM-DRV error (get\_bytes\_per\_component):
> > Unknown or not supported format: 808669784
> > src/gbm\_drv\_common.c:130: GBM-DRV error (get\_bytes\_per\_component):
> > Unknown or not supported format: 808669784
> > 
> > 808669784 => DRM_FORMAT_XRGB2101010
> 
> Just a note from previous debug with zagg

https://matrix.to/#/!xdwRmYgjAuZSEhsheE:kde.org/$LZQdcr_ikww_hzelMka_EvSCiLbVheVQW__WfCZFXAw

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia (Sub wayland session for dev)

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

--- Comment #2 from Florian RICHER  ---
(In reply to Florian RICHER from comment #1)
> src/gbm\_drv\_common.c:130: GBM-DRV error (get\_bytes\_per\_component):
> Unknown or not supported format: 808669784
> src/gbm\_drv\_common.c:130: GBM-DRV error (get\_bytes\_per\_component):
> Unknown or not supported format: 808669784
> 
> 808669784 => DRM_FORMAT_XRGB2101010

Just a note from previous debug with zagg

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia (Sub wayland session for dev)

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

--- Comment #1 from Florian RICHER  ---
src/gbm\_drv\_common.c:130: GBM-DRV error (get\_bytes\_per\_component): Unknown
or not supported format: 808669784
src/gbm\_drv\_common.c:130: GBM-DRV error (get\_bytes\_per\_component): Unknown
or not supported format: 808669784

808669784 => DRM_FORMAT_XRGB2101010

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia (Sub wayland session for dev)

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

Florian RICHER  changed:

   What|Removed |Added

Summary|Can't run kwin plasma   |Can't run kwin plasma
   |mobile with nvidia  |mobile with nvidia (Sub
   ||wayland session for dev)

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia

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

Florian RICHER  changed:

   What|Removed |Added

  Flags||Wayland+, NVIDIA+

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

[kwin] [Bug 485496] Can't run kwin plasma mobile with nvidia

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

Florian RICHER  changed:

   What|Removed |Added

 CC||florian.richer@protonmail.c
   ||om

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

[kwin] [Bug 485496] New: Can't run kwin plasma mobile with nvidia

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

Bug ID: 485496
   Summary: Can't run kwin plasma mobile with nvidia
Classification: Plasma
   Product: kwin
   Version: 6.0.3
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: florian.ric...@protonmail.com
  Target Milestone: ---

Created attachment 168467
  --> https://bugs.kde.org/attachment.cgi?id=168467=edit
Log during command run

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

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

SUMMARY

When i run this command

QT_QPA_PLATFORM=wayland dbus-run-session kwin_wayland --xwayland "plasmashell
-p org.kde.plasma.mobileshell"

Nothing happens but with my laptop computer (With intel integrated GPU, it
works).

I already tried 

* QT_QPA_PLATFORM=wayland dbus-run-session kwin_wayland --xwayland
"plasmashell" (Not work)
* QT_QPA_PLATFORM=wayland dbus-run-session kwin_wayland --xwayland "konsole"
(Not work)
* QT_QPA_PLATFORM=wayland dbus-run-session konsole (Work well)



STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT

When i run command, nothing happens

EXPECTED RESULT

This work
https://invent.kde.org/plasma/plasma-mobile#test-on-a-development-machine

SOFTWARE/OS VERSIONS
NixOS :
https://github.com/NixOS/nixpkgs/tree/1042fd8b148a9105f3c0aca3a6177fd1d9360ba5/pkgs/kde
Linux : 6.8.4-zen1
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

ADDITIONAL INFORMATION

Graphics Card : NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 or NVIDIA GeForce RTX 2070
Max-Q
NVIDIA : 550.67
SESSION : Wayland

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

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

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

--- Comment #4 from Florian Weimer  ---
Based on a further suggestion from H.J., I put the strcmp implementation posted
here into glibc and ran its strcmp test suite against it. It passes. For such a
simple implementation it should have really good coverage. So I think the
posted implementation should be okay.

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

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

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

--- Comment #3 from Florian Weimer  ---
H.J. suggests to use the implementation from
<https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/i386/i686/strcmp.S;h=e71d97f2a63a2d3c31e4c1be395c1a1f5e0200ff;hb=HEAD>
(adapted for x86-64). I can submit that if there are no licensing concerns.

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

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

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

Florian Weimer  changed:

   What|Removed |Added

 CC||fwei...@redhat.com

--- Comment #2 from Florian Weimer  ---
(In reply to Mark Wielaard from comment #1)
> The proposed patch looks reasonable. Did you test it?

Sort of, the valgrind build passed, and the run-time failures are gone. Earlier
versions of the patch with an incorrect implementation failed really
spectacularly. But I do not write x86-64 assembly for a living (well, not
really), so take it with a grain of salt.

> Is there a (fedora?) glibc build that triggers this issue?

We had a glibc build bug/RPM spec file issue that resulted in rawhide binaries
not using x86-64-v3 string functions in ld.so, and I missed the incorrect glibc
upstream testsuite change at the time. We have this as a redundant test in
glibc.spec that fails the Fedora build, that's how I noticed. We are getting
better at not producing a glibc that is totally incompatible with valgrind. But
all this means that there is no Fedora build. 8-)

I can prepare a rawhide scratch build for you if this helps, though.

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

[valgrind] [Bug 485487] New: glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

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

Bug ID: 485487
   Summary: glibc built with -march=x86-64-v3 does not work due to
ld.so strcmp
Classification: Developer tools
   Product: valgrind
   Version: 3.23 GIT
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: fwei...@redhat.com
  Target Milestone: ---

Created attachment 168460
  --> https://bugs.kde.org/attachment.cgi?id=168460=edit
valgrind-amd64-redir-strcmp.patch

This was originally observed as a glibc test case failure:

[PATCH] x86_64: Suppress false positive valgrind error
   


However, the analysis was incorrect, and the test failure actually shows that
the newly built glibc is incompatible with valgrind. I think it's necessary to
add a redirector for strcmp.

We see this in Fedora with valgrind-3.22.0-7.fc40.x86_64, which already has one
AVX2 inline strcmp fix applied.

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

[yakuake] [Bug 481966] open at mouse position issues on multimonitor setup when using wayland

2024-04-02 Thread Florian Schulte

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

--- Comment #2 from Florian Schulte  ---
The main problem (window on wrong screen) has been resolved. Thank you.

However, the problem with the incomplete windows is still occurring at the
moment.

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

[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()

2024-03-19 Thread Florian Weimer

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

Florian Weimer  changed:

   What|Removed |Added

 CC||fwei...@redhat.com

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

[kwin] [Bug 483252] Can't move title-bar off screen

2024-03-11 Thread Florian Loitsch

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

--- Comment #1 from Florian Loitsch  ---
Interestingly, I can move the title bar out of the screen by resizing the
window with ALT+Right-click (but I might have changed the default setting
here).

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

[kwin] [Bug 483252] New: Can't move title-bar off screen

2024-03-11 Thread Florian Loitsch

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

Bug ID: 483252
   Summary: Can't move title-bar off screen
Classification: Plasma
   Product: kwin
   Version: 6.0.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: flor...@loitsch.com
  Target Milestone: ---

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


STEPS TO REPRODUCE
1. Use ALT+Click to move a window
2. Move it to the top or left
3. 

OBSERVED RESULT
The window is stopped at the top-border/left-border.


EXPECTED RESULT
The window continues moving.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Graphics Platform: X11

Arch Linux

ADDITIONAL INFORMATION
This is partially related to  https://bugs.kde.org/show_bug.cgi?id=475089, but
even that issue states that manual movement should still work.

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

[kwin] [Bug 482311] Video frame jump/reverse glitch with NVIDIA GPU on Wayland

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

--- Comment #16 from Florian RICHER  ---
(In reply to Florian RICHER from comment #15)
> (In reply to Zamundaaa from comment #14)
> > Yes, this is https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317, and
> > will be fixed in future versions of Xwayland and the NVidia driver.
> 
> Do you have MR nvidia side and xwayland side ?

Or fixed version

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

[kwin] [Bug 482311] Video frame jump/reverse glitch with NVIDIA GPU on Wayland

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

--- Comment #15 from Florian RICHER  ---
(In reply to Zamundaaa from comment #14)
> Yes, this is https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317, and
> will be fixed in future versions of Xwayland and the NVidia driver.

Do you have MR nvidia side and xwayland side ?

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #12 from Florian RICHER  ---
https://mycld.mrdev023.fr/s/FLAgqJkwqs3AkgF

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #11 from Florian RICHER  ---
I send you gameplay of Sons of the forest with bug

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

Florian RICHER  changed:

   What|Removed |Added

 Attachment #166360|0   |1
is obsolete||
 Attachment #166467|0   |1
is obsolete||
 Attachment #166468|0   |1
is obsolete||
 Attachment #166492|0   |1
is obsolete||

--- Comment #10 from Florian RICHER  ---
Created attachment 166493
  --> https://bugs.kde.org/attachment.cgi?id=166493=edit
Gameplay

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #9 from Florian RICHER  ---
(In reply to Florian RICHER from comment #8)
> (In reply to Nate Graham from comment #6)
> > I don't see a glitch in your video. Can you point out what I should be
> > looking at?
> 
> I add https://bugs.kde.org/attachment.cgi?id=166492

In zone  (see https://bugs.kde.org/attachment.cgi?id=166492) in the video
https://bugs.kde.org/attachment.cgi?id=166360

You can see little rollback during rendering. 
This bug is more present when i play video games with low fps

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #8 from Florian RICHER  ---
(In reply to Nate Graham from comment #6)
> I don't see a glitch in your video. Can you point out what I should be
> looking at?

I add https://bugs.kde.org/attachment.cgi?id=166492

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #7 from Florian RICHER  ---
Created attachment 166492
  --> https://bugs.kde.org/attachment.cgi?id=166492=edit
Glitched zone

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

2024-03-05 Thread Florian RICHER

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

--- Comment #5 from Florian RICHER  ---
Created attachment 166468
  --> https://bugs.kde.org/attachment.cgi?id=166468=edit
signature.asc

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

2024-03-05 Thread Florian RICHER

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

--- Comment #4 from Florian RICHER  ---
The IS encountered with all vidéo of youtube and also when i play video games
liké son of thé forest.

My attachement IS already the youtube vidéo, i crop only the video.  But i can
send you also a record when i play.


 Message d'origine 
Le 06/03/2024 00:16, Nate Graham  a écrit :

>  https://bugs.kde.org/show_bug.cgi?id=482311
>  
>  Nate Graham  changed:
>  
> What|Removed Added
>  
>   CC||n...@kde.org
>  
>  --- Comment #3 from Nate Graham  ---
>  Where's the YouTube video? I see you mousing around a web browser window on 
> the
>  megarelease announcement, and I see a PiP window on the side, but I don't 
> see a
>  glitch in a YouTube video.
>  
>  --
>  You are receiving this mail because:
>  You reported the bug.
>  You are on the CC list for the bug.

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #2 from Florian RICHER  ---
Like this bug https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

Florian RICHER  changed:

   What|Removed |Added

 CC||florian.richer@protonmail.c
   ||om

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

[kwin] [Bug 482311] Display glitch with NVIDIA / Wayland

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

--- Comment #1 from Florian RICHER  ---
It look like rollback of rendering and sometimes make a short black screen
glitch.

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

[kwin] [Bug 482311] New: Display glitch with NVIDIA / Wayland

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

Bug ID: 482311
   Summary: Display glitch with NVIDIA / Wayland
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: florian.ric...@protonmail.com
  Target Milestone: ---

Created attachment 166360
  --> https://bugs.kde.org/attachment.cgi?id=166360=edit
Glitch during play youtube vidéo

SUMMARY

When i play youtube video or when i playing at video game, i get this glitch
like in attachment.


STEPS TO REPRODUCE
1. Install Plasma  5 /  6
2. Install Nvidia Driver
3. Start with wayland

OBSERVED RESULT

Video glitch.

Note : With plasma 6 and nvidia 550 update, it's less pronunced.

EXPECTED RESULT

No glitch

SOFTWARE/OS VERSIONS
NixOS :
https://gitea.mrdev023.fr/florian.richer/nixos/src/commit/28dd029befb697df68f346b77e7474237241d672/flake.lock
KDE Plasma Version: 6.0.0
KDE Frameworks Version: ??? Not displayed
Qt Version: 6.6.2
Compositor : Wayland

ADDITIONAL INFORMATION

You can check from my NixOS flake to reproduce my bug more easily.

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

[Powerdevil] [Bug 482276] New: system tray icon for power profile not corresponding to power profile mode after restart

2024-03-03 Thread Florian Unterfrauner

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

Bug ID: 482276
   Summary: system tray icon for power profile not corresponding
to power profile mode after restart
Classification: Plasma
   Product: Powerdevil
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: prg.fl...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 166333
  --> https://bugs.kde.org/attachment.cgi?id=166333=edit
video which shows the bug

SUMMARY
after staring KDE Neon with KDE 6 the power profile system tray icon is always
set to the icon as it would be balanced, also if it is actually in Performance


STEPS TO REPRODUCE
1. set power profile to Performance (in the system tray)
2. restart
3. system tray icon for power profile is the icon for balanced, but if you
press on it and open the popup it shows correctly that the power profile is
Performance (so only the icon is the problem)

OBSERVED RESULT
system tray icon for power profile is always (after restart) Balanced, instead
of Performance, although it is set to Performance

EXPECTED RESULT
system tray icon for power profile corresponds to the power profile mode (also
after restart)

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 7,1 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620
Manufacturer: LENOVO
Product Name: 81HN
System Version: Lenovo V130-15IKB

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

[yakuake] [Bug 481966] open at mouse position issues on multimonitor setup when using wayland

2024-02-28 Thread Florian Schulte

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

Florian Schulte  changed:

   What|Removed |Added

   Keywords||wayland

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

[yakuake] [Bug 481966] open at mouse position issues on multimonitor setup when using wayland

2024-02-28 Thread Florian Schulte

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

--- Comment #1 from Florian Schulte  ---
Created attachment 166174
  --> https://bugs.kde.org/attachment.cgi?id=166174=edit
Shows the second issue mentioned in the bug report

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

[yakuake] [Bug 481966] New: open at mouse position issues on multimonitor setup when using wayland

2024-02-28 Thread Florian Schulte

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

Bug ID: 481966
   Summary: open at mouse position issues on multimonitor setup
when using wayland
Classification: Applications
   Product: yakuake
   Version: 24.02.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: m...@florian-schulte.net
  Target Milestone: ---

SUMMARY
I use a multi monitor setup (explained below) with the new plasma 6 on wayland.
When I am on desktop and I move the mouse to different monitor, yakuake is not
opened at that screen when I press the hotkey. It keeps opening on the old
monitor. But when I trigger a mouse click once on the new screen, it opens
correctly on that screen and keeps opening on that screen until I click on a
different monitor. So it seems that I need to "activate" a monitor to make
yakuake recognize the changed mouse position.

Interestingly sometimes this behaviour changes (in the same kde session): Then
it works as explained before, but only for the first open-close-cycle on the
screen where I clicked. Afterwards it opened on the previous monitor again.


Second problem is, that on the bigger screen, from time to time, only a part of
the window is visible. It seem that it has the size of the window when it was
opened on the smaller monitors. But on the right side there is not a border and
you can type into the invisible area. However this fixes itself when I close
and reopen the window again.


My yakuake settings:
Window:
 - Size / Animation:
  - Width: 100%
  - Height: 77%
  - Duration: 10ms (changing it did not have any effect)
 - Position:
  - centered,
  - Show on screen: Mouse position
  - Show on all workspaces
Behaviour (enabled options only):
 - Generic:
  - Keep window open when focus is lost
  - Keep window above othe windows
 - Dialogs:
  - Confirm exit



STEPS TO REPRODUCE
1. Move mouse to display
2. Open Yakuake using hotkey

OBSERVED RESULT
Opens on mouse screen only if it was "activated" before by clicking at least
once. Sometimes also "forgets" that a monitor was activated after opening the
window once. 

EXPECTED RESULT
Open the window on the monitor where the mouse is, no matter if clicked before
or not.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I use a multi monitor setup with a 1080p / 27inch on the left, a 1080p / 27inch
on the right and a 1440p / 32 inch monitor in the middle. They are vertically
centered, so that the middle screen sticks out a bit at the bottom and the top
((1440-1080)/2 = 180 pixels). I am using a nvidia graphics card with the
"nvidia" drivers on wayland.

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

[kwin] [Bug 480803] Windows maximize too tall

2024-02-03 Thread Florian RICHER

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

Florian RICHER  changed:

   What|Removed |Added

 CC||florian.richer@protonmail.c
   ||om

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

[kwin] [Bug 480803] New: Windows maximize too tall

2024-02-03 Thread Florian RICHER

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

Bug ID: 480803
   Summary: Windows maximize too tall
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: florian.ric...@protonmail.com
  Target Milestone: ---

SUMMARY

When you launch new application in kde plasma mobile from pmOS edge + nightly
repo https://wiki.postmarketos.org/wiki/Nightly . Application is too tall and
bottom of the app is under navigation bar.

It seem to be a kwin bug generate during maximizing of application from
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/kwin/scripts/convergentwindows/contents/ui/main.qml?ref_type=heads#L15

See kde plasma mobile issue :
https://invent.kde.org/teams/plasma-mobile/issues/-/issues/256


STEPS TO REPRODUCE
1. Install postmarketos (edge)
2. Install nightly repo https://wiki.postmarketos.org/wiki/Nightly
3. Launch application

OBSERVED RESULT

Bottom of application under navigation bar.

EXPECTED RESULT

Bottom of application correctly maximized.

SOFTWARE/OS VERSIONS
pmOS : edge (Upgrade of 03/02/2024)
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Device : Oneplus 6 (enchilada) |
https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada)

ADDITIONAL INFORMATION

- https://invent.kde.org/teams/plasma-mobile/issues/-/issues/256
-
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/kwin/scripts/convergentwindows/contents/ui/main.qml?ref_type=heads#L15

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

[kmail2] [Bug 360194] Archiving takes current date, not date of messages

2024-01-03 Thread Florian Lindner

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

Florian Lindner  changed:

   What|Removed |Added

Version|5.8.3   |5.24.4

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

[kmail2] [Bug 360194] Archiving takes current date, not date of messages

2024-01-03 Thread Florian Lindner

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

Florian Lindner  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from Florian Lindner  ---
Still present in Version 5.24.4 (23.08.4).

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

[kde] [Bug 478957] export QT_WAYLAND_DISABLE_WINDOWDECORATION=1 Not work

2023-12-23 Thread Florian RICHER

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

--- Comment #3 from Florian RICHER  ---
(In reply to Florian RICHER from comment #2)
> (In reply to Nicolas Fella from comment #1)
> > This environment variable does not do what you want it to do. It doesn't
> > affect KWin's server-side decoration in any way
> 
> Do you have any idea where the bug might be coming from? Because in
> plasma-mobile 5, window decoration was never enabled for any apps but not it
> not working

but now it not working with plasma-mobile 6 *

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

[kde] [Bug 478957] export QT_WAYLAND_DISABLE_WINDOWDECORATION=1 Not work

2023-12-23 Thread Florian RICHER

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

--- Comment #2 from Florian RICHER  ---
(In reply to Nicolas Fella from comment #1)
> This environment variable does not do what you want it to do. It doesn't
> affect KWin's server-side decoration in any way

Do you have any idea where the bug might be coming from? Because in
plasma-mobile 5, window decoration was never enabled for any apps but not it
not working

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

[kde] [Bug 478957] New: export QT_WAYLAND_DISABLE_WINDOWDECORATION=1 Not work

2023-12-23 Thread Florian RICHER

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

Bug ID: 478957
   Summary: export QT_WAYLAND_DISABLE_WINDOWDECORATION=1 Not work
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: florian.ric...@protonmail.com
  Target Milestone: ---

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


STEPS TO REPRODUCE
1. Install fedora rawhide
2. Run for example QT_WAYLAND_DISABLE_WINDOWDECORATION=1 kate

OBSERVED RESULT

Window decoration still visible

EXPECTED RESULT

Hide window decoration

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide / PostmarketOS v23.12 with Nightly build for
KDE https://wiki.postmarketos.org/wiki/Nightly
(available in About System)
KDE Plasma Version: 5.90.0 (Fedora) / 5.90.90 (PostmarketOS)
KDE Frameworks Version: 5.246.0 (Fedora) / 5.247.0 (PostmarketOS)
Qt Version: 6.6.1 on Fedora and PostmarketOS

ADDITIONAL INFORMATION

It's important for plasma-mobile because, all applications display the title
bar but it's useless.

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

[systemsettings] [Bug 477324] Apply button does not activate when changing the number in the "Lock screen automatically" spinbox

2023-12-19 Thread Florian RICHER

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

Florian RICHER  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |bad...@gmail.com
 CC||florian.richer@protonmail.c
   ||om

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

[kde] [Bug 478697] Copyright year is out of date

2023-12-19 Thread Florian RICHER

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

--- Comment #3 from Florian RICHER  ---
(In reply to Florian RICHER from comment #2)
> Fixed here https://invent.kde.org/plasma/discover/-/merge_requests/722

When is merged. I set to 2024

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

[kde] [Bug 478697] Copyright year is out of date

2023-12-19 Thread Florian RICHER

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

Florian RICHER  changed:

   What|Removed |Added

 CC||florian.richer@protonmail.c
   ||om
   Assignee|unassigned-b...@kde.org |florian.richer@protonmail.c
   ||om

--- Comment #2 from Florian RICHER  ---
Fixed here https://invent.kde.org/plasma/discover/-/merge_requests/722

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

[kscreenlocker] [Bug 478111] New: entering password while screens wake up changes focus on password input

2023-12-05 Thread Florian Hänel

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

Bug ID: 478111
   Summary: entering password while screens wake up changes focus
on password input
Classification: Plasma
   Product: kscreenlocker
   Version: 5.27.8
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: he...@gmx.de
  Target Milestone: ---

SUMMARY
When you have multiple screens and they wake up with different delays, part of
the password will end up on one screen, the rest on the next. hitting enter
then fails the login prompt

STEPS TO REPRODUCE
1. have multiple screens, session locked, screens powersaving
2. start to type password without waking the screens up first

OBSERVED RESULT
observe half of password on screen 1, half on screen 2

EXPECTED RESULT
password focus should not change 
- OR - 
there should be only one password field between both screens 
- OR - 
the password fields should be linked so that they all have the same already
entered characters

SOFTWARE/OS VERSIONS
kubuntu 23.10, plasma 5.27.8

this annoyance has existed for years though

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

[krita] [Bug 476326] White Frames/Missing Frames during Recording

2023-11-09 Thread Florian Reiser

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

Florian Reiser  changed:

   What|Removed |Added

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

--- Comment #2 from Florian Reiser  ---
Hi,

I've found a workaround for this bug. Just go to Krita Menu -> Settings ->
Configure Krita -> Display -> Canvas Acceleration

The Canvas Acceleration must be switched on. If you use "Auto" on Windows, most
probably your system has chosen Direct3D. On some systems, this could lower the
performance. See also
https://docs.krita.org/en/reference_manual/preferences/display_settings.html:

> ANGLE Direct3D (Windows Only)
> Krita will use the ANGLE compatibility layer to convert the OpenGL calls to 
> Direct3D calls. 
> Whether this works better than regular OpenGL depends on the graphics drivers 
> of the computer.

But the most effective setting to workaround this bug is to reduce the quality
of the Scaling Mode. On my system, it was already enough to switch the value
from "High Quality Filtering" to "Trilinear Filtering". But reduce it even
more, if you still encounter the bug.

Florian

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

[krita] [Bug 476326] White Frames/Missing Frames during Recording

2023-10-31 Thread Florian Reiser

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

--- Comment #1 from Florian Reiser  ---
Hi,

I've digged a little bit deeper and I fear, this seems to be a hard one. I'm
not quite sure what issues this bug, but I have an educated guess.

In the `recorder_writer.cpp`, the data of the current image is read into an
internal buffer
https://invent.kde.org/graphics/krita/-/blob/master/plugins/dockers/recorder/recorder_writer.cpp?ref_type=heads#L135

Due to the fact, that I only see the bug on a high performance system, where we
really can hold the 10Hz capturing, in combination with the usage of big
brushes (which means, Krita has something to do updating the canvas and
therefore writing continously the internal data), my guess is, that we have
maybe a race condition somewhere in the internals of the Krita data managment.

I debugged a little bit this morning and found myself in the
`KisTiledDataManager`. But the corresponding read operation is locked by a Read
Mutex:
https://invent.kde.org/graphics/krita/-/blob/master/libs/image/tiles3/kis_tiled_data_manager.cc?ref_type=heads#L699

So, maybe I'm on the totally wrong position. But maybe not. Could it be, that
we keep the Datamanger so busy in reading data, that we do not release the
mutex often enough? Maybe, its internal data can not be updated anymore? But to
give an anwser to this question, I have not enough epxerience with Krita. 
Do you have any ideas, where we could add traces in the code to track down this
nasty little beast?

Florian

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

[krita] [Bug 476326] White Frames/Missing Frames during Recording

2023-10-30 Thread Florian Reiser

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

Florian Reiser  changed:

   What|Removed |Added

 CC||reise...@gmail.com

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

[krita] [Bug 476326] New: White Frames/Missing Frames during Recording

2023-10-30 Thread Florian Reiser

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

Bug ID: 476326
Summary: White Frames/Missing Frames during Recording
Classification: Applications
Product: krita
Version: 5.2.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: major
Priority: NOR
Component: Dockers/Recorder
Assignee: krita-bugs-n...@kde.org
Reporter: reise...@gmail.com
Target Milestone: ---

Created attachment 162728
--> https://bugs.kde.org/attachment.cgi?id=162728=edit
Canvas Settings and Example Recording Video

SUMMARY
During recording with the new 10 Hz feature we had an issue with a medium sized
canvas and a big brush.
The raw PNGs, which where exported, are only correct as long as we use a small
size brush. As soon as we enlarge the size (we used the Basic-5 Size brush with
>500px, but it seems to be independent of the used brush as long as it is big
enough), several of the exported PNGs are white. And the complete build up of
the colored area was not captured. The colored area just appears from one frame
to the next (please also see the attached Show Case video).

We didn't observe any LowPerformance warnings.

STEPS TO REPRODUCE
1. Open a canvas 2000x2000 pixels and with a resolution of 300 (for additional
details see the attached Screenshot)
2. Start the recording of the Docker Recoder Plugin with a Capturing Interval
of 0.1 sec
3. Select a big brush with at least 500px
4. Build up a big colored area with your brush. Do this really fast. Probably,
it is a performance issue and therefore you must force the system into a little
bit of work.

OBSERVED RESULT
We observed the bug only on the high performance system of my wife. I can
imagine, that this has something todo with the LowPerformanceWarnings. On my
old system, I get all the time such warnings with the same setup. But not so on
my wifes system. The reson is probably, that on my system the capturing is not
taken every 100ms, becaus it is just to slow. And this could also explain, why
I don't get the same bug.

EXPECTED RESULT
Every 100 ms the current canvas should be exported as it is, without any white
frames or missing frames.

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

ADDITIONAL INFORMATION

I'm currently working on an additional Real Time Capture Mode for the Docker
Plugin, which is almost ready for a merge request
(https://invent.kde.org/freiser/krita-freiser/-/tree/freiser/RecorderRealTimeMT?ref_type=heads).
Hence, I have a complete Krita development environment setup here. And I have
dug a little bit into the Docker Recorder code, already. I'm pretty sure, that
this bug is to advanced for my Krita knowledge, I have so far :-) But I'm
willing to support you as much as I can, finding this nasty bug.
We are heavly depending on this feature to hold our deadline. Hence, we have a
big interest in fixing this as soon as possible.

Thank you in advance for your support.

Florian

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

[Reminder Daemon] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes

2023-09-17 Thread Florian Baumgärtner

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

Florian Baumgärtner  changed:

   What|Removed |Added

 CC||st...@pepelino.de

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

[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland

2023-07-09 Thread Florian Sievert

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

Florian Sievert  changed:

   What|Removed |Added

 CC||ca...@phobeus.de

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

[plasma-pa] [Bug 472107] New: On-screen messages when (un-)muting from the task bar are wrong

2023-07-09 Thread Florian

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

Bug ID: 472107
   Summary: On-screen messages when (un-)muting from the task bar
are wrong
Classification: Plasma
   Product: plasma-pa
   Version: 5.27.6
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: flor...@kleinebreil.eu
CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com
  Target Milestone: ---

SUMMARY
When you click on the microphone icon in the task bar to mute/un-mute, the
message that pops up on-screen shows the opposite of what you've done.

STEPS TO REPRODUCE
1. Click on the microphone icon in the bottom right (task bar) to mute/un-mute.

OBSERVED RESULT
If you click to mute, the message that pops up on-screen shows 'Volume 100%'.
If you click the icon again to un-mute, the message says 'Microphone Muted'.

EXPECTED RESULT
The opposite on-screen messages for the respective actions.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed/Plasma 5.27.6
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Love you folks <3

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

[kmail2] [Bug 465551] E-Mail signed with gnupg subkey not properly shown as valid when opened in composer/preview pane

2023-06-11 Thread Florian Evers

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

--- Comment #5 from Florian Evers  ---
Hi,

I confirm that signature checking works again on my system. However, I have no
idea what changed... maybe some stuff related to GnuPG, or a recent bugfix in
one of the KDE packages? Who knows... now it works. Thanks :-)

kde-apps-23.04.2
kde-frameworks-5.107.0
kde-plasma-5.27.5

Regards,
Florian

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

[kmail2] [Bug 465551] E-Mail signed with gnupg subkey not properly shown as valid when opened in composer/preview pane

2023-04-26 Thread Florian Evers

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

Florian Evers  changed:

   What|Removed |Added

 CC||florian-ev...@gmx.de

--- Comment #4 from Florian Evers  ---
Hi,

I also have this issue, on Gentoo Linux. I already updated GnuPG and some
surroundings to narrow this down. This definitely worked fine in the past, one
of the recent updates must have caused this.

kde-apps-23.04.0
kde-frameworks-5.105.0
kde-plasma-5.27.4

Regards,
Florian

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

[kwin] [Bug 467834] Screen doesn't turn on after long time sleeping (DPMS error)

2023-03-27 Thread Florian Sievert

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

Florian Sievert  changed:

   What|Removed |Added

 CC||ca...@phobeus.de

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage with certain screen arrangements

2022-12-12 Thread Florian Schrön

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

Florian Schrön  changed:

   What|Removed |Added

 CC||florian+...@itzoo.de

--- Comment #51 from Florian Schrön  ---
(In reply to Marcin Kasperski from comment #50)
> It is amazing. With this setup (smaller monitor on the left, vertically
> centered) my ~/.xsession-errors is spammed with huge volume of „Container
> window visible, stack below”:
> 
> https://pasteboard.co/FoXmuIxWfCuD.png
> 
> Moving left screen  slightly up (so tops are aligned), puff, problem gone:
> 
> https://pasteboard.co/SNQYJxFRSZMd.png
> 
> It happens immediately, Apply in Display settings window and it stops/starts.

same here with vertical monitor setup (up / down).
When aligning both to the left edge, the error is instantly gone.

With center alignment applied, the ~/.xsession-errors is flooded with
"Container window visible, stack below".
in the 15 seconds until automatic config rollback after reply i got 118966
error lines. 

> $ tail -fn0 .xsession-errors  | ts > /tmp/.xsession-errors.ts# while the 
> 15 seconds of center aligned setup
> $ grep -c "Container window visible, stack below" /tmp/.xsession-errors.ts
> 118966

Packages (@Linux Mint 21):
> plasma-workspace 4:5.24.7-0ubuntu0.1 from ubuntu/jammy-updates (contains 
> xembedsniproxy)
> plasma-desktop 4:5.24.7-0ubuntu0.1 from ubuntu/jammy-updates

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

[parley] [Bug 455400] Parley crashes every time when using configure practice on Wayland

2022-12-11 Thread Florian Dittmer

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

Florian Dittmer  changed:

   What|Removed |Added

 CC||kde-b...@pyoworks.com

--- Comment #2 from Florian Dittmer  ---
Also crashed on X11 for me whenever I click on  "Configure Practice" option.

Operating System: Gentoo Linux 2.9
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7
Kernel Version: 6.0.11-gentoo-dist (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B89
System Version: 1.0

Programm output:

Attempting to load .desktop at
"/usr/share/parley/themes/theme_reference.desktop"
tkxkb dbus error
kxkb dbus error
Create word type model for summary view
Translateshell process found
Clear summary widget
Clear summary widget
Translateshell process found
SaveAs success.
kf.i18n: Trying to convert empty KLocalizedString to QString.
kf.i18n: Trying to convert empty KLocalizedString to QString.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = parley path = /usr/bin pid = 10868
KCrash: Arguments: /usr/bin/parley 
KCrash: Attempting to start /usr/lib64/libexec/drkonqi

Developer Information:

Application: Parley (parley), signal: Segmentation fault

[KCrash Handler]
#4  0x7f6275120c6a in QByteArray::operator=(char const*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f627662d9da in KLocalizedString::KLocalizedString(char const*, char
const*, char const*, char const*, bool) () at /usr/lib64/libKF5I18n.so.5
#6  0x5653dc156619 in  ()
#7  0x5653dc15869c in  ()
#8  0x5653dc15912c in  ()
#9  0x5653dc0d0ed3 in  ()
#10 0x5653dc0cf371 in  ()
#11 0x7f62752b605c in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f6275d5ce72 in QAction::triggered(bool) () at
/usr/lib64/libQt5Widgets.so.5
#13 0x7f6275d5fbd4 in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7f6275e5c2b2 in  () at /usr/lib64/libQt5Widgets.so.5
#15 0x7f6275e5c417 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /usr/lib64/libQt5Widgets.so.5
#16 0x7f6275f5bc3a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7f6275da70fe in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#18 0x7f6275d63a2f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x7f6275d6b8ca in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7f62752821d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#21 0x7f6275d6a39d in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /usr/lib64/libQt5Widgets.so.5
#22 0x7f6275dc0b7a in  () at /usr/lib64/libQt5Widgets.so.5
#23 0x7f6275dc3d95 in  () at /usr/lib64/libQt5Widgets.so.5
#24 0x7f6275d63a2f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#25 0x7f62752821d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#26 0x7f6275727af0 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib64/libQt5Gui.so.5
#27 0x7f627570704b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib64/libQt5Gui.so.5
#28 0x7f6262f152ca in  () at /usr/lib64/libQt5XcbQpa.so.5
#29 0x7f626b98015b in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#30 0x7f626b980418 in  () at /usr/lib64/libglib-2.0.so.0
#31 0x7f626b9804cf in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#32 0x7f62752d4964 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#33 0x7f6275280bbb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#34 0x7f627528921d in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#35 0x5653dc0cd19f in  ()
#36 0x7f6274e4f34a in  () at /lib64/libc.so.6
#37 0x7f6274e4f3fc in __libc_start_main () at /lib64/libc.so.6
#38 0x5653dc0cd211 in  ()
[Inferior 1 (process 10868) detached]

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

[valgrind] [Bug 462007] New: Implicit int in none/tests/faultstatus.c

2022-11-18 Thread Florian Weimer

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

Bug ID: 462007
   Summary: Implicit int in none/tests/faultstatus.c
Classification: Developer tools
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: fwei...@redhat.com
  Target Milestone: ---

There is a definition in a test that is not accepted by C99 compilers (implicit
ints were removed in that language revision).

This should fix it:

diff --git a/none/tests/faultstatus.c b/none/tests/faultstatus.c
index 458ea8264..92a8350ab 100644
--- a/none/tests/faultstatus.c
+++ b/none/tests/faultstatus.c
@@ -190,7 +190,7 @@ int main()
return 0;
 }

-static volatile s_zero;
+static volatile int s_zero;

 static int zero()
 {

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-11-07 Thread Florian Edelmann

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

Florian Edelmann  changed:

   What|Removed |Added

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

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-10-24 Thread Florian Edelmann

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

--- Comment #11 from Florian Edelmann  ---
Thanks for investigating! I've executed the script like you requested:
> bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' 
> 'bugs/kde459911'
Its output includes the following line on startup:
> [info] kbibtex 
> (/tmp/flo-kbibtex-git-a3da32a0acdc0a4ba86f7b93436ea11c/src/program/program.cpp:63)
>  - Starting KBibTeX version "58c75501 (bugs/kde459911)"
When pressing Ctrl+D for one of the entries, Okular opens correctly. But there
is no special output, just the same Okular warning as before:
> [warning] okular (unknown:0) - Unable to open QuickAnnotatingTools XML 
> definition
When clicking the button in the edit dialog's "External" tab, Okular opens
correctly and there is this console output:
> [info] kbibtex 
> (/tmp/flo-kbibtex-git-a3da32a0acdc0a4ba86f7b93436ea11c/src/gui/field/fieldlineedit.cpp:356)
>  - About to open URL 
> "file:///home/flo/www/master-thesis/master-thesis/papers/wu2019compression.pdf"
>  with MIME type "application/pdf"
> [info] kbibtex 
> (/tmp/flo-kbibtex-git-a3da32a0acdc0a4ba86f7b93436ea11c/src/gui/field/fieldlineedit.cpp:363)
>  - KRun::runURL returned true
> [warning] okular (unknown:0) - Unable to open QuickAnnotatingTools XML 
> definition
When trying to open the PDF via the context menu, nothing happens at all. No
Okular opening, no console output.
For reference: Clicking an "external" URL via the context menu opens Firefox
with that URL correctly.

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-10-18 Thread Florian Edelmann

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

--- Comment #9 from Florian Edelmann  ---
(In reply to Thomas Fischer from comment #8)
> xdg-open wu2019compression.pdf
> kde-open wu2019compression.pdf
> kde-open5 wu2019compression.pdf

All three commands successfully open the PDF in Okular. There is a warning in
the terminal "Unable to open QuickAnnotatingTools XML definition" but that
seems to come from Okular itself and doesn't have a negative consequence.

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-10-13 Thread Florian Edelmann

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

--- Comment #7 from Florian Edelmann  ---
Created attachment 152794
  --> https://bugs.kde.org/attachment.cgi?id=152794=edit
Minimal reproduction

I am using curly braces, not quotes. But the file path is relative like in your
example:

> localfile = {wu2019compression.pdf}

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-10-03 Thread Florian Edelmann

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

--- Comment #5 from Florian Edelmann  ---
To clarify: "I did" from my previous comment refers to your last sentence
"Please use the run-kbibtex.sh script".

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-10-03 Thread Florian Edelmann

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

--- Comment #4 from Florian Edelmann  ---
(In reply to Thomas Fischer from comment #3)
> You cannot simply compile the code and run the resoluting kbibtex binary.
I did. The last line of the output from "bash run-kbibtex.sh
'https://invent.kde.org/thomasfischer/kbibtex.git' 'kbibtex/0.10'" is exactly
the mentioned error.

> Please try this here:
> bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' 
> 'bugs/kde459911'
Clicking the button in the "External" tab next to a PDF entry now opens Okular
like expected. So one bug fixed :)
In the list, Ctrl+D still works as expected, but "View document" in the context
menu still does only work for online entries, not for local PDF files.

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

[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work

2022-10-02 Thread Florian Edelmann

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

--- Comment #2 from Florian Edelmann  ---
A workaround I just discovered: Opening the PDF with the keyboard shortcut
(Ctrl+D) works fine. Using your instructions in the linked issue, I could
verify that it does still not work in the 0.9 git version.

When trying to run the 0.10 git version, I got this build error:

-- The following OPTIONAL packages have not been found:

 * Qt5NetworkAuth
 * Qt5WebEngineWidgets
 * Qt5WebKitWidgets
 * Qt5 (required version >= 5.9.0)

-- Configuring done
CMake Error at src/networking/CMakeLists.txt:59 (add_library):
  Target "kbibtexnetworking" links to target "Qt5::NetworkAuth" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?

Installing libqt5networkauth5-dev fixed the issue, so it seems to be a
misclassification as "optional dependency".

Compiling the 0.10 git version works, but it fails to start due to the
following error:

/tmp/flo-kbibtex-usr/bin/kbibtex: error while loading shared libraries:
libkbibtexprocessing.so.0: cannot open shared object file: No such file or
directory

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

[KBibTeX] [Bug 459911] New: Opening local PDF attached to Bibtex entry doesn't work

2022-10-02 Thread Florian Edelmann

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

Bug ID: 459911
   Summary: Opening local PDF attached to Bibtex entry doesn't
work
Classification: Applications
   Product: KBibTeX
   Version: 0.9.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Loading/saving files
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: florian-edelm...@online.de
  Target Milestone: ---

SUMMARY
When a local PDF is attached to a Bibtex entry (via "localfile"), I can't open
it in KBibTex's UI.

STEPS TO REPRODUCE
1. Create a new Bibtex file with an arbitrary entry, go to the entry's
"External" tab ("Extern" in German).
2. Attach a local PDF and a website link there.

OBSERVED RESULT
When clicking the "Open" button in that "External" tab for each entry, the
webpage opens in the default browser, but the PDF button does nothing.
When saving the entry, right-clicking it and selecting "View document"
("Dokument betrachten" in German), clicking the webpage entry opens it in the
default browser, while clicking the PDF entry does nothing.
There is no output in the console when starting KBibTeX there.

EXPECTED RESULT
The PDF should open in the default PDF viewer in both cases.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
Manufacturer: Dell Inc.
Product Name: XPS 15 9560

ADDITIONAL INFORMATION
Default browser: Firefox
Default PDF viewer: Okular

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

[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working

2022-08-29 Thread Florian Stahl

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

Florian Stahl  changed:

   What|Removed |Added

 CC||florian.st...@outlook.com

--- Comment #3 from Florian Stahl  ---
Same Problem for me in a VM. Can reproduce with Kate.
I added Kate to the shortcuts list and created "Meta + K" as a shortcut.
Pressing the shortcut starts the animation (bouncing icon alongside the
cursor), but then nothing happens.
Kate does function though.

Operating System: Arch Linux
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Xeon® CPU E5-2690 v4 @ 2.60GHz
Memory: 7.8 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: VMware, Inc.
Product Name: VMware7,1
System Version: None

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

[parley] [Bug 455400] Parley crashes every time when using configure practice on Wayland

2022-08-22 Thread Florian

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

--- Comment #1 from Florian  ---
Also happens with 22.04.03 on ubuntu 22.04LTS

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

[parley] [Bug 455400] Parley crashes every time when using configure practice on Wayland

2022-08-22 Thread Florian

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

Florian  changed:

   What|Removed |Added

 CC||ha...@gmx.de

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

[kmail] [Bug 53801] Need option to specify domains when downloading external references

2022-07-25 Thread Florian Lindner

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

Florian Lindner  changed:

   What|Removed |Added

Version|1.5 |5.18.80

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

[kmail] [Bug 53801] Need option to specify domains when downloading external references

2022-07-25 Thread Florian Lindner

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

Florian Lindner  changed:

   What|Removed |Added

 CC||florian.lind...@xgm.de
 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

--- Comment #6 from Florian Lindner  ---
(In reply to Björn Ruberg from comment #5)
> 
> *** This bug has been marked as a duplicate of bug 63780 ***

https://bugs.kde.org/show_bug.cgi?id=63780 is about rending HTML, this bug is
about loading external references. It is wrongly flagged as duplicate and
should still be open.

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

[okular] [Bug 456925] New: Bogus memory allocation size -- embedded pdf not shown/white page

2022-07-19 Thread Florian

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

Bug ID: 456925
   Summary: Bogus memory allocation size -- embedded pdf not
shown/white page
   Product: okular
   Version: 22.04.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: florian.streib...@gmail.com
  Target Milestone: ---

Created attachment 150745
  --> https://bugs.kde.org/attachment.cgi?id=150745=edit
pdf file not being displayed

SUMMARY
I have a figure that is included in a pdf using LaTeX beamer. 
The figure is not shown in the presentation.
When openened directly the page is empty and also no content shown.
On the console opening the pdf directly or scrolling to the page where it is
embedded yields 
'Bogus memory allocation size'

STEPS TO REPRODUCE
1. open the attached pdf

OBSERVED RESULT

a blank page is displayed, an error printed on the console

EXPECTED RESULT

showing the content of the pdf, like all other pdf viewers I tried to, e.g.
xpdf, evince, even converting to png.

ADDITIONAL INFO

I am assuming this to be different from #404526 -- not building manually, using
Arch, until now all other pdfs work just fine.

$ pdfinfo eco_middle.pdf
Producer:cairo 1.16.0 (https://cairographics.org)
CreationDate:Tue Feb  5 20:53:09 2019 CET
Custom Metadata: no
Metadata Stream: no
Tagged:  no
UserProperties:  no
Suspects:no
Form:none
JavaScript:  no
Pages:   1
Encrypted:   no
Page size:   720 x 405 pts
Page rot:0
File size:   366672 bytes
Optimized:   no
PDF version: 1.5

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

[plasmashell] [Bug 455364] Dropdowns are shifted on wayland multi monitor

2022-06-15 Thread Florian Schulte

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

--- Comment #2 from Florian Schulte  ---
Created attachment 149760
  --> https://bugs.kde.org/attachment.cgi?id=149760=edit
mixed setup

I just accidentally found out that a mixed setup also works normally. When the
left monitor is top aligned and the right monitor is shifted down, alle menus
on all screens are displayed as they should. It seems that the problem occurs
if you dont have a clearly defined origin at 0,0. A monitor that is at the very
top left position.

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

[plasmashell] [Bug 455364] Dropdowns are shifted on wayland multi monitor

2022-06-15 Thread Florian Schulte

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

--- Comment #1 from Florian Schulte  ---
Created attachment 149759
  --> https://bugs.kde.org/attachment.cgi?id=149759=edit
behavior on third screen

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

[plasmashell] [Bug 455364] New: Dropdowns are shifted on wayland multi monitor

2022-06-15 Thread Florian Schulte

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

Bug ID: 455364
   Summary: Dropdowns are shifted on wayland multi monitor
   Product: plasmashell
   Version: 5.25.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: plasma-b...@kde.org
  Reporter: m...@florian-schulte.net
CC: aleix...@kde.org, notm...@gmail.com
  Target Milestone: 1.0

Created attachment 149758
  --> https://bugs.kde.org/attachment.cgi?id=149758=edit
Screenshots merged into one file; top shows monitor setup and described
behavior

I use a multi monitor setup and switched from X11 to wayland with the new 5.25
release. I noticed some weird behavior when i open menus an applications (e.g.
dolphin). I use a triple monitor setup with two side monitors with a resolution
of 1920x1080 and a center monitor with 2560x1440. Coming from X11 I had all
monitors center aligned in the vertical direction. So the left monitor was at
coordinate 0,180 and the right one was at 4480,180. Everything was working
normally. 

On wayland the menus are shifted down by roughly 150px on the left screen. And
on the center screen the menus are moved to the right by 1645px (see
attachments). To me it seems that it tries to move the menus by an offset but
fails to take the coordinate into account correctly. On the third screen the
menus are shifted in both directions, but not as far to the right as the system
always tries to keep the menu completely on screen.

If I align all screens to the top (coordinates: 0,0; 1920,0; 4480,0) ,
everything is fine, but it does not represent my setup anymore. I used gimp to
edit the screenshots and it seems that gtk does not show this behaviour.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kde neon
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

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

[valgrind] [Bug 434764] iconv_open causes ld.so v2.28 and later to execute optimised strncmp which confuses memcheck

2022-05-16 Thread Florian Weimer

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

Florian Weimer  changed:

   What|Removed |Added

 CC||fwei...@redhat.com

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

[Breeze] [Bug 432576] Add system tray icon for Microsoft Teams (Preview)

2022-05-07 Thread Florian Edelmann

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

Florian Edelmann  changed:

   What|Removed |Added

 CC||florian-edelm...@online.de

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

[kalendar] [Bug 452848] "Kalendar Reminders" crashes when opening Kalendar

2022-05-07 Thread Florian Edelmann

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

Florian Edelmann  changed:

   What|Removed |Added

 CC||florian-edelm...@online.de

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

[kalendar] [Bug 453398] Unchecking "whole day" resets date

2022-05-04 Thread Florian Edelmann

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

Florian Edelmann  changed:

   What|Removed |Added

 CC||florian-edelm...@online.de

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

[kalendar] [Bug 453398] New: Unchecking "whole day" resets date

2022-05-04 Thread Florian Edelmann

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

Bug ID: 453398
   Summary: Unchecking "whole day" resets date
   Product: kalendar
   Version: 22.04.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: florian-edelm...@online.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
When creating a new event on some day in the future, that day is preselected.
However, checking and unchecking "whole day" (in German: "Ganztägig") resets
that date to the current day.

STEPS TO REPRODUCE
1. Double-click on any date in the future to create a new event.
2. Check and uncheck "whole day" checkbox.

OBSERVED RESULT
Start and end date is reset to today.

EXPECTED RESULT
Start and end date should stay as they are.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.24
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

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

[kalendar] [Bug 452848] "Kalendar Reminders" crashes when opening Kalendar

2022-04-22 Thread Florian Edelmann

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

Florian Edelmann  changed:

   What|Removed |Added

Summary|kalendarac crashes when |"Kalendar Reminders"
   |opening Kalendar|crashes when opening
   ||Kalendar

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

[kalendar] [Bug 452848] kalendarac crashes when opening Kalendar

2022-04-22 Thread Florian Edelmann

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

Florian Edelmann  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |claudio.cam...@gmail.com
 CC||c...@carlschwan.eu
  Component|general |general
Version|unspecified |1.0.0
Product|kde |kalendar

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

[kde] [Bug 452848] New: kalendarac crashes when opening Kalendar

2022-04-22 Thread Florian Edelmann

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

Bug ID: 452848
   Summary: kalendarac crashes when opening Kalendar
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: florian-edelm...@online.de
  Target Milestone: ---

Application: kalendarac (1.0.0)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.13.0-39-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.4 [KCrashBackend]

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

I opened the Kalendar application. The crash notification appears every time
when Kalendar is opened.

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar Reminders (kalendarac), signal: Segmentation fault

[New LWP 232862]
[New LWP 232863]
[New LWP 232864]
[New LWP 232865]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f9672c709cf in __GI___poll (fds=0x7ffc5d3fa538, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f966c628ec0 (LWP 232861))]

Thread 5 (Thread 0x7f96698ea700 (LWP 232865)):
#0  0x7f9670b924dd in g_mutex_lock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9670b4548e in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f967325c65b in QEventDispatcherGlib::processEvents
(this=0x7f9654000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f967320087b in QEventLoop::exec (this=this@entry=0x7f96698e9be0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#4  0x7f967301a442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#5  0x7f967301b623 in QThreadPrivate::start (arg=0x556e38dabc50) at
thread/qthread_unix.cpp:331
#6  0x7f9671692609 in start_thread (arg=) at
pthread_create.c:477
#7  0x7f9672c7d163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f966a0eb700 (LWP 232864)):
#0  0x7f9672c709cf in __GI___poll (fds=0x7f9660004a60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f9670b4536e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9670b454a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f967325c65b in QEventDispatcherGlib::processEvents
(this=0x7f966b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f967320087b in QEventLoop::exec (this=this@entry=0x7f966a0eabe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f967301a442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f967301b623 in QThreadPrivate::start (arg=0x556e38da46d0) at
thread/qthread_unix.cpp:331
#7  0x7f9671692609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f9672c7d163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f966a8ec700 (LWP 232863)):
#0  0x7f9672c709cf in __GI___poll (fds=0x7f965c004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f9670b4536e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9670b454a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f967325c65b in QEventDispatcherGlib::processEvents
(this=0x7f965c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f967320087b in QEventLoop::exec (this=this@entry=0x7f966a8ebbb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f967301a442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f9673b8ff4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f967301b623 in QThreadPrivate::start (arg=0x7f9673c13d80) at
thread/qthread_unix.cpp:331
#8  0x7f9671692609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f9672c7d163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f966b7d5700 (LWP 232862)):
#0  0x7f9672c709cf in __GI___poll (fds=0x7f966b7d4ae8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f967003bc1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f967003d90a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f966bf051a8 in QXcbEventQueue::run (this=0x556e38cb88c0) at
qxcbeventqueue.cpp:228
#4  0x7f967301b623 in QThreadPrivate::start (arg=0x556e38cb88c0) at
thread/qthread_unix.cpp:331
#5  0x7f9671692609 in start_t

[kalendar] [Bug 450661] Kalendar crashes when trying to enter new event's title

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

--- Comment #2 from Florian Edelmann  ---
(In reply to Claudio Cambra from comment #1)
> Have you enabled maps in Kalendar's settings?

Yes, I have.

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

[kalendar] [Bug 450661] New: Kalendar crashes when trying to enter new event's title

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

Bug ID: 450661
   Summary: Kalendar crashes when trying to enter new event's
title
   Product: kalendar
   Version: 1.0.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: florian-edelm...@online.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendar (1.0.0)

Qt Version: 5.15.3
Frameworks Version: 5.91.0
Operating System: Linux 5.13.0-28-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.1 [KCrashBackend]

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

I created a new event, filled in its time, and clicked on the summary/title
input field. That moment, the whole application crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault

[New LWP 195987]
[New LWP 195988]
[New LWP 195989]
[New LWP 195990]
[New LWP 195994]
[New LWP 195995]
[New LWP 196003]
[New LWP 196011]
[New LWP 196012]
[New LWP 196018]
[New LWP 196043]
[New LWP 196044]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f796d130aff in __GI___poll (fds=0x7ffcbb04a4f8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f7967ee09c0 (LWP 195985))]

Thread 13 (Thread 0x7f7915825700 (LWP 196044)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x563abd2b7124) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563abd2b70d0,
cond=0x563abd2b70f8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x563abd2b70f8, mutex=0x563abd2b70d0) at
pthread_cond_wait.c:638
#3  0x7f796d4de6db in QWaitConditionPrivate::wait (deadline=...,
this=0x563abd2b70d0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=this@entry=0x563abd2b70b8,
mutex=mutex@entry=0x563abd2b70b0, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f796fb46c44 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x563abd2b70a8) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x563abd2b7010) at scenegraph/qsgthreadedrenderloop.cpp:936
#7  0x7f796fb470b9 in QSGRenderThread::run (this=0x563abd2b7010) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8  0x7f796d4d8543 in QThreadPrivate::start (arg=0x563abd2b7010) at
thread/qthread_unix.cpp:331
#9  0x7f796b859609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f796d13d293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f7916026700 (LWP 196043)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x563abc14c6c0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563abc14c670,
cond=0x563abc14c698) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x563abc14c698, mutex=0x563abc14c670) at
pthread_cond_wait.c:638
#3  0x7f794663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f794663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x7f796b859609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f796d13d293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f791dacf700 (LWP 196018)):
#0  0x7f796ae208ed in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f796ae22345 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f796ae23cbf in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f796ae24312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f796ae244a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f796d719a0b in QEventDispatcherGlib::processEvents
(this=0x7f7918000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f796d6bdc9b in QEventLoop::exec (this=this@entry=0x7f791dacebe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#7  0x7f796d4d7362 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#8  0x7f796d4d8543 in QThreadPrivate::start (arg=0x563abb6c1bf0) at
thread/qthread_unix.cpp:331
#9  0x7f796b859609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f796d13d293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f7939c61700 (LWP 196012)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x563ab76efc94) at ../sysdeps/nptl/futex-interna

[kalendar] [Bug 450640] Kalendar event notification crashes

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

Florian Edelmann  changed:

   What|Removed |Added

Product|kde |kalendar
 CC||c...@carlschwan.eu,
   ||florian-edelm...@online.de
   Assignee|unassigned-b...@kde.org |claudio.cam...@gmail.com
Version|unspecified |1.0.0
  Component|general |general

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

[kde] [Bug 450640] New: Kalendar event notification crashes