[krusader] [Bug 488241] Export and compress entry in context menu is missing.

[Sławek]

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

--- Comment #2 from Sławek  ---
(In reply to Alex Bikadorov from comment #1)
> This is because the current Krusader version is based on KF5 and cannot show
> the menu actions of KF6.
> It will be fixed when Krusader is ported to KF6. 
> 
> Note that the inbuild archive compress/extract functionality
> (File->Pack/Unpack) can be used as an alternative.

Thank you for explanation. Is Krusader scheduled to be ported soon?

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

[krusader] [Bug 488241] New: Export and compress entry in context menu is missing.

[Sławek]

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

Bug ID: 488241
   Summary: Export and compress entry in context menu is missing.
Classification: Applications
   Product: krusader
   Version: 2.8.1
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: slawomir.a...@gmail.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY
After an upgrade to KDE Plasma 6.x, compress and extract functions are missing
in context menu. Before en upgrade I was able to compress or extract just by
right click and select the option. Now it is not available.

STEPS TO REPRODUCE
1. Select file or folder to compress.
2. Right click with the mouse.
3. Extract or compress options are missing in context menu.

EXPECTED RESULT
Options to extract or compress should be available as it was before the
upgrade.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSuse Tumbleweed
(available in About System)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

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

[plasmashell] [Bug 487230] Repeated Plasma shell crashes after updating to Fedora KDE 40

[Sławek]

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

--- Comment #8 from Sławek  ---
It just happened for me again. I had locked screen and closed laptop lid and
the I connected laptop to the docking station and external monitor. When I
typed password to unlock screen I had again plasmashell crash report.
I am using default Breeze theme.

Stack trace is like below:
Application: plasmashell (plasmashell), signal: Aborted


This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.fedoraproject.org/>
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 3440]
[New LWP 3494]
[New LWP 3669]
[New LWP 3503]
[New LWP 7099]
[New LWP 28661]
[New LWP 3695]
[New LWP 3505]
[New LWP 28664]
[New LWP 29622]
[New LWP 18400]
[New LWP 28663]
[New LWP 3696]
[New LWP 504864]
[New LWP 7101]
[New LWP 18398]
[New LWP 3479]
[New LWP 3482]
[New LWP 3483]
[New LWP 3989]
[New LWP 4020]
[New LWP 4172]
[New LWP 3988]
[New LWP 4238]
[New LWP 4242]
[New LWP 7097]
[New LWP 18397]
[New LWP 18401]
[New LWP 29621]
[New LWP 29623]
[New LWP 276857]
[New LWP 3691]
[New LWP 504862]
[New LWP 504867]
[New LWP 3493]
[New LWP 3504]
[New LWP 504860]
[New LWP 3694]
[New LWP 4239]
[New LWP 7098]
[New LWP 7100]
[New LWP 29624]
[New LWP 276856]
[New LWP 504861]
[New LWP 504863]
[New LWP 504866]
[New LWP 504865]
[New LWP 18399]
[New LWP 4241]
[New LWP 29625]
[New LWP 3502]
[New LWP 4240]
[New LWP 28660]
[New LWP 3697]
[New LWP 504871]
[New LWP 276853]
[New LWP 276854]
[New LWP 276855]
[New LWP 3549]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fb3a18ab144 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fb39d027b00 (LWP 3440))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fb39d027b00 (LWP 3440))]

Thread 59 (Thread 0x7fb36ea006c0 (LWP 3549)):
#0  0x7fb3a191d72d in poll () from /lib64/libc.so.6
#1  0x7fb3a0c4b6a4 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb3a0bebb23 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb3a227bf83 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7fb3a1fa26b3 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7fb3a20b402f in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7fb3a214f35c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#7  0x7fb3a18a91b7 in start_thread () from /lib64/libc.so.6
#8  0x7fb3a192b39c in clone3 () from /lib64/libc.so.6

Thread 58 (Thread 0x7fb2834006c0 (LWP 276855)):
#0  0x7fb3a18a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fb3a18a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fb385a9d84d in cnd_wait () from /usr/lib64/dri/iris_dri.so
#3  0x7fb385a7b40b in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#4  0x7fb385a9d77c in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#5  0x7fb3a18a91b7 in start_thread () from /lib64/libc.so.6
#6  0x7fb3a192b39c in clone3 () from /lib64/libc.so.6

Thread 57 (Thread 0x7fb283e006c0 (LWP 276854)):
#0  0x7fb3a18a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fb3a18a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fb385a9d84d in cnd_wait () from /usr/lib64/dri/iris_dri.so
#3  0x7fb385a7b40b in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#4  0x7fb385a9d77c in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#5  0x7fb3a18a91b7 in start_thread () from /lib64/libc.so.6
#6  0x7fb3a192b39c in clone3 () from /lib64/libc.so.6

Thread 56 (Thread 0x7fb28cc006c0 (LWP 276853)):
#0  0x7fb3a18a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fb3a18a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fb3a215ba8b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt6Core.so.6
#3  0x7fb3a3ec89c9 in QSGRenderThread::processEventsAndWaitForMore() ()
from /lib64/libQt6Quick.so.6
#4  0x7fb3a3ec8c4a in QSGRenderThread::run() () from
/lib64/libQt6Quick.so.6
#5  0x7fb3a214f35c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#6  0x7fb3a18a91b7 in start_thread () from /lib64/libc.so.6
#7  0x7fb3a192b39c in clone3 () from /lib64/libc.so.6

Thread 55 (Thread 0x7fb274c006c0 (LWP 504871)):
#0  0x7fb3a18a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fb3a18a8652 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fb3a215ba0d in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/li

[plasmashell] [Bug 487230] Repeated Plasma shell crashes after updating to Fedora KDE 40

[Sławek]

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

--- Comment #6 from Sławek  ---
I saw similar crash (reported by me in
https://bugs.kde.org/show_bug.cgi?id=487180 but closed as duplicate of this
one) and I am using only default Breeze theme. I have installed some other
plasma themes but they are not used currently.

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

[plasmashell] [Bug 487180] New: plasmashell crash after unlocking screen

[Sławek]

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

Bug ID: 487180
   Summary: plasmashell crash after unlocking screen
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: 1.0

Application: plasmashell (6.0.4)

Qt Version: 6.7.0
Frameworks Version: 6.2.0
Operating System: Linux 6.8.9-300.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Forty)"
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
Many times after I unlock my screen I see window saying me that plasmashell
crashed. I use wayland now. I don't think it was similar on X11

The crash can be reproduced sometimes.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Aborted


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 1717561]
[New LWP 1717859]
[New LWP 1722546]
[New LWP 1717582]
[New LWP 1717583]
[New LWP 1717628]
[New LWP 1752777]
[New LWP 1717576]
[New LWP 1717573]
[New LWP 1717668]
[New LWP 1717585]
[New LWP 1752776]
[New LWP 1717863]
[New LWP 1717577]
[New LWP 1717572]
[New LWP 1717571]
[New LWP 1752774]
[New LWP 1717584]
[New LWP 1722547]
[New LWP 1722545]
[New LWP 1717858]
[New LWP 1717837]
[New LWP 1752773]
[New LWP 1752771]
[New LWP 1752778]
[New LWP 1752775]
[New LWP 1722548]
[New LWP 1722544]
[New LWP 1717781]
[New LWP 1717782]
[New LWP 1717783]
[New LWP 1717784]
[New LWP 1717785]
[New LWP 1717836]
[New LWP 1717841]
[New LWP 1717847]
[New LWP 1717857]
[New LWP 1717860]
[New LWP 1717861]
[New LWP 1717862]
[New LWP 1717864]
[New LWP 1752772]
[New LWP 1717865]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fe5cb6ab144 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fe5c6e55b00 (LWP 1717561))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fe5c6e55b00 (LWP 1717561))]

Thread 43 (Thread 0x7fe4c96006c0 (LWP 1717865)):
#0  0x7fe5cb71d72d in poll () from /lib64/libc.so.6
#1  0x7fe5caa876a4 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fe5caa2c667 in g_main_loop_run () from /lib64/libglib-2.0.so.0
#3  0x7fe5c7374e82 in gdbus_shared_thread_func.lto_priv () from
/lib64/libgio-2.0.so.0
#4  0x7fe5caa56863 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7fe5cb6a91b7 in start_thread () from /lib64/libc.so.6
#6  0x7fe5cb72b39c in clone3 () from /lib64/libc.so.6

Thread 42 (Thread 0x7fe565e006c0 (LWP 1752772)):
#0  0x7fe5cb6a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fe5cb6a8652 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fe5cbf5ba0d in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt6Core.so.6
#3  0x7fe5cbf587d5 in QThreadPoolThread::run() () from
/lib64/libQt6Core.so.6
#4  0x7fe5cbf4f35c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#5  0x7fe5cb6a91b7 in start_thread () from /lib64/libc.so.6
#6  0x7fe5cb72b39c in clone3 () from /lib64/libc.so.6

Thread 41 (Thread 0x7fe4ca0006c0 (LWP 1717864)):
#0  0x7fe5cb72918d in syscall () from /lib64/libc.so.6
#1  0x7fe5caa847bd in g_cond_wait () from /lib64/libglib-2.0.so.0
#2  0x7fe5ca9f15ab in g_async_queue_pop_intern_unlocked () from
/lib64/libglib-2.0.so.0
#3  0x7fe5caa57a53 in g_thread_pool_spawn_thread () from
/lib64/libglib-2.0.so.0
#4  0x7fe5caa56863 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7fe5cb6a91b7 in start_thread () from /lib64/libc.so.6
#6  0x7fe5cb72b39c in clone3 () from /lib64/libc.so.6

Thread 40 (Thread 0x7fe4cb4006c0 (LWP 1717862)):
#0  0x7fe5cb71d72d in poll () from /lib64/libc.so.6
#1  0x7fe5caa876a4 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fe5caa27b23 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fe5cc07bfa1 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7fe5cbda26b3 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7fe5cbeb402f in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7fe5cbf4f35c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#7  0x7fe5cb6a91b7 in start_thread () from /lib64/libc.so.6
#8  0x7fe5cb72b39c in 

[plasmashell] [Bug 482729] System try hidden icon menu and application menu and all other popups from the panel after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

Sławek  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 482729] System try hidden icon menu and application menu and all other popups from the panel after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

--- Comment #6 from Sławek  ---
Created attachment 166932
  --> https://bugs.kde.org/attachment.cgi?id=166932=edit
Two screens - left

After some more testing, it looks like it is not related to the amount of
external screens connected to my computer. It's related to the position of the
connected screen. When my external screen is on the left from the primary
screen, all the pop-ups are in the wrong position. When is on the right,
everything is ok.

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

[frameworks-knewstuff] [Bug 482217] Can't import icon theme

[Sławek]

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

--- Comment #4 from Sławek  ---
It looks like after the latest update, all icons themes can be installed
successfully. Strange :)

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

[plasmashell] [Bug 482729] System try hidden icon menu and application menu and all other popups from the panel after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

--- Comment #4 from Sławek  ---
I'm using Wayland.

Screen layout attached.

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

[plasmashell] [Bug 482729] System try hidden icon menu and application menu and all other popups from the panel after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

--- Comment #3 from Sławek  ---
Created attachment 166722
  --> https://bugs.kde.org/attachment.cgi?id=166722=edit
Screen layout

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

[kde] [Bug 482729] System try hidden icon menu and application menu and all other popups from the panel after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

Sławek  changed:

   What|Removed |Added

Summary|System try hidden icon menu |System try hidden icon menu
   |and application menu and|and application menu and
   |all other popups after  |all other popups from the
   |disconnecting from external |panel after disconnecting
   |monitor are shown in the|from external monitor are
   |wrong place.|shown in the wrong place.

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

[kde] [Bug 482729] System try hidden icon menu and application menu and all other popups after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

--- Comment #1 from Sławek  ---
Created attachment 166600
  --> https://bugs.kde.org/attachment.cgi?id=166600=edit
App Menu at the wrong side

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

[kde] [Bug 482729] New: System try hidden icon menu and application menu and all other popups after disconnecting from external monitor are shown in the wrong place.

[Sławek]

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

Bug ID: 482729
   Summary: System try hidden icon menu and application menu and
all other popups after disconnecting from external
monitor are shown in the wrong place.
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: slawomir.a...@gmail.com
  Target Milestone: ---

Created attachment 166599
  --> https://bugs.kde.org/attachment.cgi?id=166599=edit
Screen at the wrong location 1

SUMMARY
After upgrade to Plasma 6.0. When disconnecting external monitor from my
laptop, all pop-up windows from my panel (application menu, system try hidden
icons, bluetooth applet, network manager applet, preview of open application
etx. are shown in the wrong location. 


STEPS TO REPRODUCE
1. Disconnect external monitor from the laptop.
2. Open application menu or any other menu from the panel.
3. Window will open on the other side of the screen

EXPECTED RESULT
Windows should pop-up next to the panel.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux Neon user edition.
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Work around to get windows displayed next to the panel is to toggle panel
floating setting. After that everything is back to normal.

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

[frameworks-knewstuff] [Bug 482217] Can't import icon theme

[Sławek]

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

--- Comment #2 from Sławek  ---
(In reply to Nate Graham from comment #1)
> Are you sure? When I press it, the icon theme in installed as expected. It
> is just slow, maybe? Can you try waiting a while longer to see if it works?
> 
> If not, please report which icon theme you're trying to download.

I've checked other icon themes. You are right some of theme can be installed
some of them not.

Before system upgrade I've been using Win11 icon theme -
https://store.kde.org/p/1546069

This is not the only one which can't be installed.

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

[systemsettings] [Bug 482217] New: Can't import icon theme

[Sławek]

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

Bug ID: 482217
   Summary: Can't import icon theme
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_icons
  Assignee: plasma-b...@kde.org
  Reporter: sla...@ajon.eu
  Target Milestone: ---

SUMMARY
After upgrade of my Neon with the latest update to Plasma 6. I can't import
icon theme from net.


STEPS TO REPRODUCE
1. Open system settings
2. Go to section appearance & style -> Icons and click Get New..
3. Select icon theme of your liking.
4. Press Install button - nothing is happening.

OBSERVED RESULT
Selected Icon theme is not installed in the user folder for Icons and it is not
visible to be selected from System Settings.

EXPECTED RESULT
Icon theme should be installed or at least there should be a message with the
reason why it can't be installed.

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

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

[kwin] [Bug 417227] No keyboard shortcuts work on Wayland when using musl instead of glibc

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@kaplonski.pl

--- Comment #18 from Sławek  ---
I hit the same issue (probably) on Fedora 38 and KDE Plasma 5.27.8. No custom
shortcuts works for me at all and I see that KGlobalAccel isn't running. When I
want to run it I see error:

/usr/bin/kglobalaccel5
kf.dbusaddons: Couldn't register name 'org.kde.kglobalaccel' with DBUS -
another process owns it already!

And when I check what process owns tis name in dbus:

qdbus  org.freedesktop.DBus /org/freedesktop/DBus
org.freedesktop.DBus.GetConnectionUnixProcessID org.kde.kglobalaccel
2238

ps aux | grep 2238 
slaweq  2238  0.0  0.3 3641764 214824 ?  Sl   wrz19   0:30
/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8
--xwayland-fd 9 --xwayland-display :0 --xwayland-xauthority
/run/user/1000/xauth_oawZej --xwayland

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

[krusader] [Bug 445549] kioslave5 blocking umount

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@ajon.eu
Version|2.7.2   |2.8.0
   Platform|openSUSE|Neon

--- Comment #11 from Sławek  ---
I do face the same problem. Is there any chance that this will be fixed soon?

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

[kalendar] [Bug 464194] New: Kalendar application crashes sometimes

[Sławek]

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

Bug ID: 464194
   Summary: Kalendar application crashes sometimes
Classification: Applications
   Product: kalendar
   Version: 22.12.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: sla...@kaplonski.pl
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendar (22.12.1)

Qt Version: 5.15.8
Frameworks Version: 5.101.0
Operating System: Linux 6.0.17-300.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
This happens for me mostly during the start of the Kalendar app. Then when I
restart it, it starts normally.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x7f87b3b23ae7 in QHashData::nextNode(QHashData::Node*) () from
/lib64/libQt5Core.so.5
#5  0x7f87b5e99b3a in QHash::erase(QHash::const_iterator) () from /lib64/libKF5WidgetsAddons.so.5
#6  0x7f87b5ea137d in KViewStateSerializer::restoreSelection(QStringList
const&) () from /lib64/libKF5WidgetsAddons.so.5
#7  0x7f87b5ea1535 in KViewStateSerializerPrivate::processPendingChanges()
() from /lib64/libKF5WidgetsAddons.so.5
#8  0x7f87b5ea1687 in
QtPrivate::QFunctorSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from
/lib64/libKF5WidgetsAddons.so.5
#9  0x7f87b3cdbc26 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f87b3c58cd2 in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () from /lib64/libQt5Core.so.5
#11 0x7f87b3c61d1e in QAbstractItemModel::endInsertRows() () from
/lib64/libQt5Core.so.5
#12 0x7f87b3c856ad in
QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&,
QVector const&, QModelIndex const&, Qt::Orientation, bool) () from
/lib64/libQt5Core.so.5
#13 0x7f87b3c88199 in
QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int,
int, Qt::Orientation) () from /lib64/libQt5Core.so.5
#14 0x7f87b3c8aebd in
QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int,
int) () from /lib64/libQt5Core.so.5
#15 0x7f87b3cdbdaf in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#16 0x7f87b3c58cd2 in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () from /lib64/libQt5Core.so.5
#17 0x7f87b3c61d1e in QAbstractItemModel::endInsertRows() () from
/lib64/libQt5Core.so.5
#18 0x7f87b3c856ad in
QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&,
QVector const&, QModelIndex const&, Qt::Orientation, bool) () from
/lib64/libQt5Core.so.5
#19 0x7f87b3c88199 in
QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int,
int, Qt::Orientation) () from /lib64/libQt5Core.so.5
#20 0x7f87b3c8aebd in
QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int,
int) () from /lib64/libQt5Core.so.5
#21 0x7f87b3cdbdaf in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#22 0x7f87b3c58cd2 in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () from /lib64/libQt5Core.so.5
#23 0x7f87b3c61d1e in QAbstractItemModel::endInsertRows() () from
/lib64/libQt5Core.so.5
#24 0x7f87b63adcfa in
Akonadi::EntityTreeModelPrivate::collectionsFetched(QVector
const&) () from /lib64/libKF5AkonadiCore.so.5
#25 0x7f87b3cdbdaf in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#26 0x7f87b636c706 in
Akonadi::CollectionFetchJob::collectionsReceived(QVector
const&) () from /lib64/libKF5AkonadiCore.so.5
#27 0x7f87b636dda3 in Akonadi::CollectionFetchJobPrivate::aboutToFinish()
() from /lib64/libKF5AkonadiCore.so.5
#28 0x7f87b637bfb1 in
QtPrivate::QFunctorSlotObject const&)::{lambda()#1}, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) [clone .lto_priv.0] () from /lib64/libKF5AkonadiCore.so.5
#29 0x7f87b3cd2ec4 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#30 0x7f87b49aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#31 0x7f87b3ca8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#32 0x7f87b3cab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#33 0x7f87b3cf9897 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#34 0x7f87b1b19cbf in g_main_context_dispatch () from

[kmail2] [Bug 462387] New: Kmail crashed when trying to open new mail compose window

[Sławek]

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

Bug ID: 462387
   Summary: Kmail crashed when trying to open new mail compose
window
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

Application: kmail (5.21.3 (22.08.3))

Qt Version: 5.15.7
Frameworks Version: 5.100.0
Operating System: Linux 6.0.9-300.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.26.3 [KCrashBackend]

-- Information about the crash:
When I clicked "New mail" Kmail crashed. It happened only once so far.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x7f2fd63262c3 in QMapDataBase::freeNodeAndRebalance(QMapNodeBase*) ()
from /lib64/libQt5Core.so.5
#5  0x7f2fd4e648d7 in QMap::remove(QGpgME::Job* const&) [clone .constprop.0] [clone
.isra.0] () from /lib64/libqgpgme.so.7
#6  0x7f2fd4e533bb in
QGpgME::QGpgMEKeyForMailboxJob::~QGpgMEKeyForMailboxJob() () from
/lib64/libqgpgme.so.7
#7  0x7f2fd4e534dd in
QGpgME::QGpgMEKeyForMailboxJob::~QGpgMEKeyForMailboxJob() () from
/lib64/libqgpgme.so.7
#8  0x7f2fd64d2d01 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#9  0x7f2fd71aed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#10 0x7f2fd64a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#11 0x7f2fd64ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#12 0x7f2fd64f9897 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#13 0x7f2fcfe53cbf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#14 0x7f2fcfea9598 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#15 0x7f2fcfe50f40 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#16 0x7f2fd64f938a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#17 0x7f2fd64a6cca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#18 0x7f2fd64aed92 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#19 0x562cc1e27dbf in main ()
[Inferior 1 (process 1231857) detached]

The reporter indicates this bug may be a duplicate of or related to bug 456616.

Reported using DrKonqi

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

[kmail2] [Bug 459341] Kmail crash when trying to write recipent address in the new mail window

[Sławek]

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

--- Comment #1 from Sławek  ---
I just found out that problem is fixed when I downgraded libs:

gpgme-1.17.0-4.fc36.x86_64 to gpgme-1.15.1-6.fc36.x86_64
gpgme-devel-1.17.0-4.fc36.x86_64 to gpgme-devel-1.15.1-6.fc36.x86_64
gpgmepp-1.17.0-4.fc36.x86_64  to gpgmepp-1.15.1-6.fc36.x86_64
gpgmepp-devel-1.17.0-4.fc36.x86_64 to qgpgme-devel-1.15.1-6.fc36.x86_64
python3-gpg-1.17.0-4.fc36.x86_64 to python3-gpg-1.15.1-6.fc36.x86_64
qgpgme-1.17.0-4.fc36.x86_64 to qgpgme-1.15.1-6.fc36.x86_64
gpgmepp-devel-1.17.0-4.fc36.x86_64 to gpgmepp-devel-1.15.1-6.fc36.x86_64

So bug is probably in one of those packages in 1.17 version

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

[kmail2] [Bug 459341] New: Kmail crash when trying to write recipent address in the new mail window

[Sławek]

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

Bug ID: 459341
   Summary: Kmail crash when trying to write recipent address in
the new mail window
Classification: Unclassified
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

Application: kmail (5.20.1 (22.04.1))

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.19.9-200.fc36.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
Every time I open new mail composer window and try to write recipent's email
address, kmail crashes.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x7f1bd54550a4 in QString::QString(QString const&) () from
/lib64/libqgpgme.so.7
#5  0x7f1bd5455231 in QGpgME::QGpgMEAddUserIDJob::start(GpgME::Key const&,
QString const&, QString const&, QString const&) () from /lib64/libqgpgme.so.7
#6  0x7f1bdfca8e11 in
KMComposerWin::slotRecipientAdded(MessageComposer::RecipientLineNG*) () from
/lib64/libkmailprivate.so.5
#7  0x7f1bd6b338b6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x7f1bd5c39541 in MessageComposer::RecipientLineNG::analyzeLine(QString
const&) () from /lib64/libKF5MessageComposer.so.5
#9  0x7f1bd6b338b6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f1bd7706416 in QLineEdit::textChanged(QString const&) () from
/lib64/libQt5Widgets.so.5
#11 0x7f1bd6b33a3f in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#12 0x7f1bd770dcd9 in QWidgetLineControl::textChanged(QString const&) ()
from /lib64/libQt5Widgets.so.5
#13 0x7f1bd77114e0 in QWidgetLineControl::finishChange(int, bool, bool) ()
from /lib64/libQt5Widgets.so.5
#14 0x7f1bd7714264 in QWidgetLineControl::processKeyEvent(QKeyEvent*) ()
from /lib64/libQt5Widgets.so.5
#15 0x7f1bd7706603 in QLineEdit::keyPressEvent(QKeyEvent*) () from
/lib64/libQt5Widgets.so.5
#16 0x7f1bd46150bc in KLineEdit::keyPressEvent(QKeyEvent*) () from
/lib64/libKF5Completion.so.5
#17 0x7f1bd5340a1d in
PimCommon::AddresseeLineEdit::keyPressEvent(QKeyEvent*) () from
/lib64/libKF5PimCommonAkonadi.so.5
#18 0x7f1bd75ff630 in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#19 0x7f1bd75bbd22 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#20 0x7f1bd75c3d17 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#21 0x7f1bd6b00218 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#22 0x7f1bd761af92 in QWidgetWindow::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#23 0x7f1bd75bbd22 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#24 0x7f1bd6b00218 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#25 0x7f1bd6f3a43d in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() from /lib64/libQt5Gui.so.5
#26 0x7f1bd6f1cfbc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#27 0x7f1bc06d7e6e in xcbSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5XcbQpa.so.5
#28 0x7f1bd01c3faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#29 0x7f1bd02192c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#30 0x7f1bd01c1940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#31 0x7f1bd6b50f4a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#32 0x7f1bd6afec6a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#33 0x7f1bd6b06d32 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#34 0x559b8b194c8f in main ()
[Inferior 1 (process 6392) detached]

Reported using DrKonqi

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

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

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@kaplonski.pl

--- Comment #15 from Sławek  ---
I also experienced that error many times. Recently I proposed some workaround
for that https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/11 - I
don't know Akonadi code at all so it's really hard for me to find quickly
better solution but I hope this can help to get rid of that problem. Please
check and let me know what do You think about it.

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

[Akonadi] [Bug 449300] Google calendars not working with Akonadi at all

[Sławek]

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

--- Comment #1 from Sławek  ---
Sorry, I forgot to add info about versions

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.2-arch1-1 (64-bit)
Graphics Platform: X11

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

[Akonadi] [Bug 449300] New: Google calendars not working with Akonadi at all

[Sławek]

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

Bug ID: 449300
   Summary: Google calendars not working with Akonadi at all
   Product: Akonadi
   Version: 5.19.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@kde.org
  Reporter: sla...@kaplonski.pl
CC: kdepim-b...@kde.org
  Target Milestone: ---

SUMMARY
Since few days my Google calendars are not working in KDE destkop. I had added
2 google accounts in akonadi configured and was using Kalendar to manage
calendars from those accounts.
Since few days one of the accounts "disappeared" from the Kalendar application
- that happened from time to time earlier but restarting Google groupware agent
in akonadi console helped for it. Unfortunately recently it don't helpe
anymore.
Also calendars from my second account seems that aren't synced properly anymore
with Google calendar.

Today I made a test and created completely new user on the system. Then I
configured both google accounts there. Calendars from both aren't visible in
the Kalendar, Korganizer nor in Akonadi console (in Browser tab).


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 412471] Make Do not disturb times configurable with a repeating schedule

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@kaplonski.pl

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

[kwin] [Bug 446620] New: All apps closed when switching to the external monitor on Wayland

[Sławek]

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

Bug ID: 446620
   Summary: All apps closed when switching to the external monitor
on Wayland
   Product: kwin
   Version: 5.23.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

SUMMARY

I use laptop which is often connected to the external HiDPI screen (4K with
scaling factor set to 150%). When external monitor is plugged, laptop is
closed.
Sometimes when I use laptop without external screen and then plug it into
external monitor, all my applications are closed and I got empty desktop, like
I would just log in into it.
I don't know exactly when it happens and why it is like that. I can provide
some additional informations if You will specify what You would need from me
exactly.
I use KDE on Wayland (because scaling factor works generally better on
Wayland).

STEPS TO REPRODUCE
1. Close laptop (it should be configured to not go to sleep)
2. Plug laptop to the external HiDPI screen
3. Unlock screen

OBSERVED RESULT
All applications which were opened on the desktop are closed.

EXPECTED RESULT
All apps should stay up and running as they were on the laptop's screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.10.83-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 62,6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

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

[kaddressbook] [Bug 446580] New: Contact synchronization with google doesn't work.

[Sławek]

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

Bug ID: 446580
   Summary: Contact synchronization with google doesn't work.
   Product: kaddressbook
   Version: 5.18.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@ajon.eu
CC: to...@kde.org
  Target Milestone: ---

SUMMARY
I can't synchronize contacts with google account anymore.

After fresh install of Neon, synchronization of my contacts with google doesn't
work. Address book can be created but is not synchronized with server.


STEPS TO REPRODUCE
1. Create address book for google account.
2. Authenticate withing google to allow kaddressbook  to access your contact
details.
3. Refresh the folder - no update.

OBSERVED RESULT
Synchronization doesn't work.

EXPECTED RESULT
Synchronization of contacts should work.

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

[KScreen] [Bug 445680] Wayland - HiDPI screen scaling broken after login to the desktop

[Sławek]

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

--- Comment #4 from Sławek  ---
Thx a lot. I will be then waiting for 5.24. Now with some simple script which
uses kscreen-doctor it's easy for me to fix that resolution after log in to the
desktop at least :)

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

[KScreen] [Bug 445680] Wayland - HiDPI screen scaling broken after login to the desktop

[Sławek]

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

--- Comment #1 from Sławek  ---
I just hit this issue again after login into the desktop. Here is output of the
kscreen-doctor when resolution was broken:

kscreen-doctor -o
Output: 1 unknown eDP-1-unknown disabled connected  Panel Modes:
0:1920x1080@60*! Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr:
incapable RgbRange: Automatic 
Output: 2 Goldstar Company Ltd LG HDR 4K/345575 enabled connected primary
Unknown Modes: 0:3840x2160@30 1:2560x1440@60 2:1920x1080@60 3:1920x1080@60
4:1920x1080@60 5:1600x900@60 6:1280x1024@60 7:1280x800@60 8:1280x720@60
9:1280x720@60 10:1280x720@60 11:1024x768@60 12:800x600@60 13:720x480@60
14:720x480@60 15:640x480@60 16:640x480@60 17:640x480@60 18:3840x2160@60*!
Geometry: 0,0 2560x1440 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: incapable
RgbRange: Automatic primary


Then I run kscreen-doctor to fix it:
kscreen-doctor output.1.disable output.2.enable output.2.mode.3840x2160@60
output.2.scale.1.5

but it changed nothing. So I run:
kscreen-doctor output.1.disable output.2.enable output.2.mode.1280x800@60

which changed resolution to 1280x800 and fixed desktop that whole (huge)
desktop was displayed and mouse coursor was working properly.

Then I again run 
kscreen-doctor output.1.disable output.2.enable output.2.mode.3840x2160@60
output.2.scale.1.5

And I have fixed my desktop finally :)

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

[KScreen] [Bug 445680] New: Wayland - HiDPI screen scaling broken after login to the desktop

[Sławek]

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

Bug ID: 445680
   Summary: Wayland - HiDPI screen scaling broken after login to
the desktop
   Product: KScreen
   Version: 5.23.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

SUMMARY
I'm using Plasma on Arch Linux Lince some time and I'm pretty happy with it.
Recently I moved from FullHD external monitor to 27 inch 4K. Monitor is
connected to the TB dock (Lenovo Thunderbolt 3 Dock Gen 2) using DP port.
Because scaling on such screens is much better on Wayland IMO, I moved to the
Wayland now. And here is the problem which I have:

I configured it like: "resolution 3840x2160", "Scale 150%" - that works very
good for me. But after I e.g restart my laptop and login into plasma desktop,
it has just FullHD resolution on the screen. But the problem isn't the wrong
resolution configure really (that I could easily change in settings :). The
main issue is that in plasma settings it's still "resolution 3840x2160", "Scale
150%" thus on the screen I really see just 1/4 of the desktop (bottom left
corner). To fix it I need to run krunner and with that turn on systemsettings.
Then go to the display settings, change resolution of the screen to some other
than 3840x2160, apply and confirm new settings and then configure again correct
resolution to have everything working fine :)

There is also problem that when there is that wrong resolution configured,
mouse coursor is also working in weird way. It isn't really in the place where
it should be so to fix resolution settings first I need to do all of that
"blindly" :)


STEPS TO REPRODUCE
1. Set 4K display resolution to 3840x2160 and scalling to 1.5
2. Reboot OS or log out and then log in back to the desktop

OBSERVED RESULT
Only huge lower left corner is shown. Resolutions in Settings is OK and also
the mouse did not click in the right place on the high-DPI screen.

EXPECTED RESULT
Desktop should be displayed properly

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 62,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630


ADDITIONAL INFORMATION
On reddit someone pointed me to the bug
https://bugs.kde.org/show_bug.cgi?id=445253. It does sounds a bit similar in
terms that You cannot really set proper resolution and scalling just like that
as it looks that it's already set properly. To fix the issue You have to change
resolution to some different value, apply new settings and then set it again to
the wanted one.
But as other symptompts (huge left corner of the desktop displayed only, mouse
not working properly) I'm opening new bug for that.
If You think it's the same issue, please mark this as duplicate of the 
https://bugs.kde.org/show_bug.cgi?id=445253 :)

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

[kwin] [Bug 444275] New: Window moved from one screen to another resizes to the width of new screen

[Sławek]

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

Bug ID: 444275
   Summary: Window moved from one screen to another resizes to the
width of new screen
   Product: kwin
   Version: 5.23.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

SUMMARY
I have 2 monitor setup. One monitor positioned horizontally (1920x1080) and
another vertically (1080x1920).
When I have window, e.g. system settings but this isn't really important what
window it is, spawned on the vertical screen with width taking full width of
monitor (1080), when I move it to the horizontal screen it's automatically
resized to full width too (1920). This behavior seems odd for me as usually,
when window was full width on the vertical screen I don't want to have it full
width on the horizontal screen (which is much wider).


STEPS TO REPRODUCE
1. Run e.g. system settings on the screen with width 1080 - it needs to use
full width of screen but not full height,
2. Move the window with mouse to the other screen with with 1920 - it will be
automatically resized to take full width of the new screen automatically when
You drop it with mouse.

OBSERVED RESULT
Window resized to much wider screen automatically

EXPECTED RESULT
Window which wasn't on full screen, should remain with same size after moving
it to the other screen

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.13-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 62,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

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

[Akonadi] [Bug 444270] Some events from google calendar aren't displayed properly

[Sławek]

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

--- Comment #2 from Sławek  ---
Created attachment 142793
  --> https://bugs.kde.org/attachment.cgi?id=142793=edit
view of Google calendar

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

[Akonadi] [Bug 444270] Some events from google calendar aren't displayed properly

[Sławek]

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

--- Comment #1 from Sławek  ---
Created attachment 142792
  --> https://bugs.kde.org/attachment.cgi?id=142792=edit
View of Kalendar

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

[Akonadi] [Bug 444270] New: Some events from google calendar aren't displayed properly

[Sławek]

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

Bug ID: 444270
   Summary: Some events from google calendar aren't displayed
properly
   Product: Akonadi
   Version: 5.18.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@kde.org
  Reporter: sla...@kaplonski.pl
CC: kdepim-b...@kde.org
  Target Milestone: ---

Created attachment 142791
  --> https://bugs.kde.org/attachment.cgi?id=142791=edit
View of Korganizer

SUMMARY
I have some google calendars and some events from it aren't displayed at all in
both Korganizer and Kalenar apps. Because the issue is in both those frontend
apps I think that issue can be in Akonadi backend really. But maybe I'm wrong.

The even which I can't see was created by someone else and I was invited to it.
I accepted the invitation and in google calendar I can see it with color as it
is in my calendar now. But in Korganizer/Kalendar apps I can't see it at all.
The strange thing is that other, similar events, accepted by me in the same way
I can see in the Korganizer and Kalendar apps. So it's not the issue for all
such events.

There is also other type of events which aren't displayed in
Korganizer/Kalendar but for those events the issue is permanent, so none of
such events are displayed. The events are invitations which I didn't accepted
yet (white background in the Google calendar) and event's which I say that I
will "maybe" attend.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.13-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 62,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

ADDITIONAL INFORMATION
In attachement I added screenshots with what I see in the Korganizer, Kalendar
and Google calendar page for the same week and same calendar. I hope that it
will be more clear with those screenshots.

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

[kmail2] [Bug 443534] Kmail composer - list levels not correct after sent

[Sławek]

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

--- Comment #5 from Sławek  ---
Created attachment 142354
  --> https://bugs.kde.org/attachment.cgi?id=142354=edit
Indents test pdf

As per your request, I've attached pdf file with screenshots of the same
message in different location.
1. Composer
2. My sent folder
3. Recipient inbox

I hope this will help.

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

[kmail2] [Bug 443534] Kmail composer - list levels not correct after sent

[Sławek]

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

--- Comment #3 from Sławek  ---
Created attachment 142353
  --> https://bugs.kde.org/attachment.cgi?id=142353=edit
Indent test mbox file from sent folder

This is an export of a message in my sent folder.

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

[kmail2] [Bug 443534] New: Kmail composer - list levels not correct after sent

[Sławek]

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

Bug ID: 443534
   Summary: Kmail composer - list levels not correct after sent
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@ajon.eu
  Target Milestone: ---

Created attachment 142289
  --> https://bugs.kde.org/attachment.cgi?id=142289=edit
Test of list indent

SUMMARY
While composing the message, I'm using increase/decrease list level buttons to
create correct indent of the list.

It all looks good while composing new or replaying to message. But the message
looks completely different in sent folder. Indents keep increasing even when
you decrease the indent in to first level. For each new line indent increases

STEPS TO REPRODUCE
1. Create a message with a list which has different indents.
2. Sent a message and it will look different in your sent folder than in
compose window.

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

[kmail2] [Bug 442430] Possibility to choose composer page separately from KDE Theme - the same way as for kate

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@ajon.eu

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

[kmail2] [Bug 442430] New: Possibility to choose composer page separately from KDE Theme - the same way as for kate

[Sławek]

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

Bug ID: 442430
   Summary: Possibility to choose composer page separately from
KDE Theme - the same way as for kate
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@ajon.eu
  Target Milestone: ---

I've been thinking, that it will be a nice feature to have, if user can select
theme for message composer separately from Plasma theme. The same way as
already implemented in kate - colour theme, where you can select to edit your
text file with white background and black fonts while using dark theme for
plasma. I love dark theme for applications, but I prefer to compose my messages
with light theme.

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

[kmail2] [Bug 442416] Text highlight while composing or replaying the message

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@ajon.eu

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

[kmail2] [Bug 442416] New: Text highlight while composing or replaying the message

[Sławek]

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

Bug ID: 442416
   Summary: Text highlight while composing or replaying the
message
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@ajon.eu
  Target Milestone: ---

Created attachment 141536
  --> https://bugs.kde.org/attachment.cgi?id=141536=edit
Screen of the composer and message in sent folder

Hello guys,

While creating a new message or replaying to someone else message. I would like
to be able to highlight some text. While I'm using a different colour for each
highlight, everything works fine. When I would like to use the same colour for
all highlight in my message. When I complete and send it, only first line
remain highlighted but any other text remain the same.


STEPS TO REPRODUCE
1. Highlight few lines with the same colour while composing the message. It's
important to highlight different line with some space in between with not
highlighted text. Use the same colour for all the highlight. If using different
colour for each highlight, everything looks OK.
2. Send a completed message. 

I attached some screens to give a better idea what I mean.

OBSERVED RESULT
In Sent messages folder as well as in the recipient mail box, only first line
remain highlighted. Any other highlighted text return to normal.

EXPECTED RESULT
All highlighted text will remain highlighted, not only the first line.

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

[plasmashell] [Bug 442159] Adaptive transparency works with windows on wrong screen

[Sławek]

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

Sławek  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 442159] New: Adaptive transparency works with windows on wrong screen

[Sławek]

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

Bug ID: 442159
   Summary: Adaptive transparency works with windows on wrong
screen
   Product: plasmashell
   Version: 5.22.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: 1.0

SUMMARY
Adaptive transparency works fine but when window on different screen is
maximized


STEPS TO REPRODUCE
1. I have 3 monitors setup. The middle one is set as primary one and on this
one I have a panel.
2. Maximize window on the primary screen (middle one) - panel is still
transparent
3. Maximize window on the left screen (not primary one) - panel is becoming
solid.

OBSERVED RESULT


EXPECTED RESULT
Panel becomes solid when window on the screen with panel is maximized.

SOFTWARE/OS VERSIONS 
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Kernel Version: 5.13.13-arch1-1 (64-bit)
Graphics Platform: X11

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

[kmail2] [Bug 434582] Kmail segmentation fault

[Sławek]

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

--- Comment #2 from Sławek  ---
Hi,

I'm working on Arch Linux and AFAIK it doesn't provides packages with debug
symbols.
This is my main laptop used for work and I'm not going to remove software
installed with packages to replace it with compiled from source. So probably
You can close that bug as I will not be able to provide any more information
about it :/

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

[kmail2] [Bug 434582] New: Kmail segmentation fault

[Sławek]

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

Bug ID: 434582
   Summary: Kmail segmentation fault
   Product: kmail2
   Version: 5.16.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

SUMMARY

I just got seg fault in Kmail:

Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x7f2e940019e0 in KCalendarCore::IncidenceBase::uid() const () at
/usr/lib/libKF5CalendarCore.so.5
#5  0x7f2e58482503 in  () at /usr/lib/libKF5AkonadiCalendar.so.5
#6  0x7f2e5848b89e in  () at /usr/lib/libKF5AkonadiCalendar.so.5
#7  0x7f2e5848c577 in  () at /usr/lib/libKF5AkonadiCalendar.so.5
#8  0x7f2e9ac8ed86 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f2e9abf0f86 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5
#10 0x7f2e9ac2d608 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f2e9ac8edc0 in  () at /usr/lib/libQt5Core.so.5
#12 0x7f2e9abf0f86 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5
#13 0x7f2e9ac2d608 in  () at /usr/lib/libQt5Core.so.5
#14 0x7f2e9ac8edc0 in  () at /usr/lib/libQt5Core.so.5
#15 0x7f2e9abf0f86 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5
#16 0x7f2e9ac2d608 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f2e9ac8edc0 in  () at /usr/lib/libQt5Core.so.5
#18 0x7f2e9abf0f86 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5
#19 0x7f2e98995c7a in  () at /usr/lib/libKF5ItemModels.so.5
#20 0x7f2e9ac8edc0 in  () at /usr/lib/libQt5Core.so.5
#21 0x7f2e9abf0f86 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5
#22 0x7f2e98c4a74c in  () at /usr/lib/libKF5AkonadiCore.so.5
#23 0x7f2e98c52c69 in  () at /usr/lib/libKF5AkonadiCore.so.5
#24 0x7f2e9ac8edc0 in  () at /usr/lib/libQt5Core.so.5
#25 0x7f2e98bb5f88 in Akonadi::Monitor::itemChanged(Akonadi::Item const&,
QSet const&) () at /usr/lib/libKF5AkonadiCore.so.5
#26 0x7f2e98bc6f34 in
Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification
const&, QVector const&, Akonadi::Collection const&,
Akonadi::Collection const&) () at /usr/lib/libKF5AkonadiCore.so.5
#27 0x7f2e98bc830b in
Akonadi::MonitorPrivate::emitNotification(QSharedPointer
const&) () at /usr/lib/libKF5AkonadiCore.so.5
#28 0x7f2e98bc53dc in Akonadi::MonitorPrivate::dispatchNotifications() ()
at /usr/lib/libKF5AkonadiCore.so.5
#29 0x7f2e98bc56c4 in
Akonadi::MonitorPrivate::slotNotify(QSharedPointer
const&) () at /usr/lib/libKF5AkonadiCore.so.5
#30 0x7f2e98bc8827 in Akonadi::MonitorPrivate::handleCommands() () at
/usr/lib/libKF5AkonadiCore.so.5
#31 0x7f2e9ac84532 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#32 0x7f2e9b71f752 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#33 0x7f2e9ac57a2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#34 0x7f2e9ac5a523 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#35 0x7f2e9acb1054 in  () at /usr/lib/libQt5Core.so.5
#36 0x7f2e9507fb84 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#37 0x7f2e950d3c21 in  () at /usr/lib/libglib-2.0.so.0
#38 0x7f2e9507e3b1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#39 0x7f2e9acb0691 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#40 0x7f2e9ac563ac in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#41 0x7f2e9ac5e844 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#42 0x5633397b3181 in  ()
#43 0x7f2e9a61db25 in __libc_start_main () at /usr/lib/libc.so.6
#44 0x5633397b337e in  ()
[Inferior 1 (process 105041) detached]


STEPS TO REPRODUCE
Just run Kmail in the background. I wasn't doing anything special when it
happened.


OBSERVED RESULT
Seg fault

EXPECTED RESULT
It should run properly

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.7-arch1-1
OS Type: 64-bit
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 62,6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
(available in About System)

ADDITIONAL INFORMATION
KMail
Version 5.16.3 (20.12.3)

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

[ktimetracker] [Bug 428912] New: [RFE] Due date and date when task is mark as complete

[Sławek]

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

Bug ID: 428912
   Summary: [RFE] Due date and date when task is mark as complete
   Product: ktimetracker
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aspotas...@gmail.com
  Reporter: sla...@kaplonski.pl
  Target Milestone: ---

I think that it would be good if it would be possible to configure for each
task "due date" and also log date when task was marked as complete.

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

[KAccounts] [Bug 427063] Can't add Google account in system settings on last stable KDE Neon

[Sławek]

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

--- Comment #1 from Sławek  ---
Hi,

I have exactly same problem on Fedora 33 and KDE Plasma 5.19.5 and with KDE
Frameworks 5.73

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

[KAccounts] [Bug 427063] Can't add Google account in system settings on last stable KDE Neon

[Sławek]

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

Sławek  changed:

   What|Removed |Added

 CC||sla...@kaplonski.pl

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