Bug 396856 - Latte crash on disconnecting the second screen
Summary: Latte crash on disconnecting the second screen
Status: RESOLVED WORKSFORME
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.8.1
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-25 20:01 UTC by vandalhj
Modified: 2018-11-12 16:05 UTC (History)
0 users

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


Attachments
My layout (11.48 KB, text/plain)
2018-07-25 20:04 UTC, vandalhj
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vandalhj 2018-07-25 20:01:15 UTC
Application: Latte Dock (latte-dock), signal: Segmentation fault

Each time i disconnect second screen it crash, then start again, so it's just minor annoyance. Didn't encountered it in earlier version (7.94?).
Comment 1 Michail Vourlakos 2018-07-25 20:03:15 UTC
(In reply to vandalhj from comment #0)
> Application: Latte Dock (latte-dock), signal: Segmentation fault
> 
> Each time i disconnect second screen it crash, then start again, so it's
> just minor annoyance. Didn't encountered it in earlier version (7.94?).

I tried to reproduce this in my system and I cant...
can you test master branch of Latte?
Comment 2 vandalhj 2018-07-25 20:04:23 UTC
Created attachment 114124 [details]
My layout
Comment 3 Michail Vourlakos 2018-07-25 20:08:07 UTC
When Latte crashes at the systray kcrash is appearing, does it provide any meaningful backtrace?
Comment 4 Michail Vourlakos 2018-10-03 19:09:24 UTC
is this still valid with Latte 0.8.1?
Comment 5 vandalhj 2018-10-03 23:04:27 UTC
(In reply to Michail Vourlakos from comment #4)
> is this still valid with Latte 0.8.1?

Yes,but it show the layout as broken. I cloned upper dock and put it on another screen, which is often disconnected (external monitor). After i plug out the screen, the sigfault appears. Right now i removed dock from said monitor (i prefer it this way, more space) and there are no crashes, but i just wonder why it started from .7, and wasn't problem before.
Comment 6 Michail Vourlakos 2018-10-04 06:18:24 UTC
(In reply to vandalhj from comment #5)
> (In reply to Michail Vourlakos from comment #4)
> > is this still valid with Latte 0.8.1?
> 
> Yes,but it show the layout as broken. I cloned upper dock and put it on
> another screen, which is often disconnected (external monitor). After i plug
> out the screen, the sigfault appears. Right now i removed dock from said
> monitor (i prefer it this way, more space) and there are no crashes, but i
> just wonder why it started from .7, and wasn't problem before.

If the layout triggers a broken layout message then it creates crashes in plenty of cases. Best way is to recreate your layout from scratch to be sure that is valid. 

For crash reports only a meaningful backtrace can help: https://github.com/psifidotos/Latte-Dock/wiki/How-to-Report-Crashes


First thing I would try in your system is the following:
Use the Default Layout without changing anything, copy that dock and place it at the second screen.
Try afterwards to disconnect your second screen, does it crash?
Comment 7 Andrew Crouthamel 2018-10-21 05:02:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2018-11-12 16:05:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!