Bug 421386 - crashes when editing a panel
Summary: crashes when editing a panel
Status: RESOLVED FIXED
Alias: None
Product: lattedock
Classification: Unmaintained
Component: application (other bugs)
Version First Reported In: git (master)
Platform: Manjaro Linux
: NOR major
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-12 04:02 UTC by Andres
Modified: 2020-07-17 21:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
docter konki log (13.61 KB, text/plain)
2020-05-12 04:02 UTC, Andres
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andres 2020-05-12 04:02:38 UTC
Created attachment 128381 [details]
docter konki log

SUMMARY
latte crashes when editing a panel. also, I have a panel on the top and on the left edge of the screen and it sometimes won't show the top panel

STEPS TO REPRODUCE
1. open latte
2. edit a panel
3. crash

OBSERVED RESULT

crash and misbehaving auto-hide left panel
EXPECTED RESULT

no crash and left panel hides when not in use and unhide when the mouse is brought over 
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.6.12-24-tkg-pds
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 15.6 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 Michail Vourlakos 2020-05-12 06:11:19 UTC
Try to clear your cache with Latte-dock --cc and restart Latte,

If that does not help you can follow https://userbase.kde.org/LatteDock/How_to_report_multi_screen_issues
Comment 2 Tyler Brown 2020-05-12 07:36:20 UTC
I get this issue when I try to edit a panel that is either using a 3rd party Indicator theme or whenever I try to set a 3rd party Indicator theme, such as the Unity on W7 indicators. Latest version pulled from Phabricator within the last couple of hours.
Comment 3 Michail Vourlakos 2020-05-12 08:46:38 UTC
(In reply to Tyler Brown from comment #2)
> I get this issue when I try to edit a panel that is either using a 3rd party
> Indicator theme or whenever I try to set a 3rd party Indicator theme, such
> as the Unity on W7 indicators. Latest version pulled from Phabricator within
> the last couple of hours.

you mean that it crashes only when you are trying to choose a 3rd party indicator?
Comment 4 Tyler Brown 2020-05-12 09:29:17 UTC
(In reply to Michail Vourlakos from comment #3)
> (In reply to Tyler Brown from comment #2)
> > I get this issue when I try to edit a panel that is either using a 3rd party
> > Indicator theme or whenever I try to set a 3rd party Indicator theme, such
> > as the Unity on W7 indicators. Latest version pulled from Phabricator within
> > the last couple of hours.
> 
> you mean that it crashes only when you are trying to choose a 3rd party
> indicator?

Both. It'll crash when I try to choose one, but it also crashes when I open "Edit Panel" on a panel that already has a 3rd party indicator set.
Comment 5 Michail Vourlakos 2020-05-12 12:00:16 UTC
check please if that commit https://invent.kde.org/kde/latte-dock/-/commit/3ad89c10a4e5a0fb5c6b102232da8be99f777485

fixes it
Comment 6 Michail Vourlakos 2020-05-12 12:20:38 UTC
(In reply to Michail Vourlakos from comment #5)
> check please if that commit
> https://invent.kde.org/kde/latte-dock/-/commit/
> 3ad89c10a4e5a0fb5c6b102232da8be99f777485
> 
> fixes it

indicators config properties are shown/updated ok?
Comment 7 Andres 2020-05-12 15:12:30 UTC
(In reply to Michail Vourlakos from comment #1)
> Try to clear your cache with Latte-dock --cc and restart Latte,
> 
> If that does not help you can follow
> https://userbase.kde.org/LatteDock/How_to_report_multi_screen_issues

it happens with only a single screen aswell and clearing the cache did not fix it. 

```
latte-dock --cc
Cache directory found and cleared...
KCrash: Attempting to start /usr/bin/latte-dock
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = latte-dock path = /usr/bin pid = 190896
KCrash: Arguments: /usr/bin/latte-dock --cc
KCrash: Attempting to start /usr/lib/drkonqi
Cache directory found and cleared...
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 469, resource id: 0, major code: 20 (GetProperty), minor code: 0

[1]+  Stopped                 latte-dock --cc

 zany130 zany130E0B0 andres-pc zany130E0B0 ~ zany130E0B0 Unable to start Dr. Konqi
Re-raising signal for core dump handling.

[1]+  Segmentation fault      (core dumped) latte-dock --cc

```
Comment 8 Michail Vourlakos 2020-05-12 16:37:05 UTC
(In reply to andresdortiz from comment #7)
> (In reply to Michail Vourlakos from comment #1)
> > Try to clear your cache with Latte-dock --cc and restart Latte,
> > 
> > If that does not help you can follow
> > https://userbase.kde.org/LatteDock/How_to_report_multi_screen_issues
> 
> it happens with only a single screen aswell and clearing the cache did not
> fix it. 
> 
> ```
> latte-dock --cc
> Cache directory found and cleared...
> KCrash: Attempting to start /usr/bin/latte-dock
> KCrash: crashing... crashRecursionCounter = 2
> KCrash: Application Name = latte-dock path = /usr/bin pid = 190896
> KCrash: Arguments: /usr/bin/latte-dock --cc
> KCrash: Attempting to start /usr/lib/drkonqi
> Cache directory found and cleared...
> qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 469, resource
> id: 0, major code: 20 (GetProperty), minor code: 0
> 
> [1]+  Stopped                 latte-dock --cc
> 
>  zany130 zany130E0B0 andres-pc zany130E0B0 ~ zany130E0B0 Unable to start Dr.
> Konqi
> Re-raising signal for core dump handling.
> 
> [1]+  Segmentation fault      (core dumped) latte-dock --cc
> 
> ```

what is your crash report?
Comment 9 Michail Vourlakos 2020-05-12 16:55:09 UTC
1. Have you build Latte yourself OR you are using a prebuild package?
2. As long as you install Latte by yourself you can also try the following:
  a. close Latte
  b. remove everything in /usr/lib64/qt5/qml/org/kde/latte/
  c. install Latte
  d. start Latte
3. I suppose you have already installed latest indicators version from kde store
Comment 10 Michail Vourlakos 2020-05-12 16:57:24 UTC
Oh... I need to republish the three indicators in the kde store. I thought I had already done that...

Until then you can try to update them from their github repos
Comment 11 Andres 2020-05-12 17:30:04 UTC
I was using the git package from the aur I saw that there was an update so I installed it and it seems to fix the issues I mentioned
Comment 12 Tyler Brown 2020-05-12 19:15:57 UTC
I pulled down the latest Unity indicator from Git and that resolved the issues on my end.