Bug 438127

https://userbase.kde.org/LatteDock/HowToReportCrashes

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!

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!

Created attachment 143115 [details]
New crash information added by DrKonqi

latte-dock (0.10.3) using Qt 5.15.2

- What I was doing when the application crashed:
Shortly after waking my computer and unlocking a previous session, I opened Plasma settings and searched for "feedback." It was around this time that I noticed the "crashed" frowning icon in Latte Dock.

Some other info that may be relevant:
- I have a dual-head setup
- My wallpaper on one monitor is static
- The wallpaper on the other monitor changes to a random selection on a schedule
- One monitor refresh rate is 144Hz; the other is 60Hz
- One monitor is connected via DVI; the other HDMI
- I do not use the standard Plasma panel at all as I replaced it with Latte Dock and a couple of widgets (Digital Clock, Panon)

-- Backtrace (Reduced):
#4  0x00007ffb8dae6860 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5
#5  0x00007ffb8db17b3c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5
#6  0x00007ffb8dafe41a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5
#7  0x00007ffb8db03b96 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5
#8  0x00007ffb8db045a5 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5

(In reply to Gabriel from comment #4)
> Created attachment 143115 [details]
> New crash information added by DrKonqi
> 
> latte-dock (0.10.3) using Qt 5.15.2
> 
> - What I was doing when the application crashed:
> Shortly after waking my computer and unlocking a previous session, I opened
> Plasma settings and searched for "feedback." It was around this time that I
> noticed the "crashed" frowning icon in Latte Dock.
> 
> Some other info that may be relevant:
> - I have a dual-head setup
> - My wallpaper on one monitor is static
> - The wallpaper on the other monitor changes to a random selection on a
> schedule
> - One monitor refresh rate is 144Hz; the other is 60Hz
> - One monitor is connected via DVI; the other HDMI
> - I do not use the standard Plasma panel at all as I replaced it with Latte
> Dock and a couple of widgets (Digital Clock, Panon)
> 
> -- Backtrace (Reduced):
> #4  0x00007ffb8dae6860 in QSGTexture::setFiltering(QSGTexture::Filtering) ()
> at /usr/lib/libQt5Quick.so.5
> #5  0x00007ffb8db17b3c in
> QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState
> const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5
> #6  0x00007ffb8dafe41a in
> QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch
> const*) () at /usr/lib/libQt5Quick.so.5
> #7  0x00007ffb8db03b96 in QSGBatchRenderer::Renderer::renderBatches() () at
> /usr/lib/libQt5Quick.so.5
> #8  0x00007ffb8db045a5 in QSGBatchRenderer::Renderer::render() () at
> /usr/lib/libQt5Quick.so.5

I also have a dual-monitor setup, but both monitors are identical models. 1440p 165Hz. 

It happens about once every 2 or 3 logins. Once I'm logged in and it crashes and I restart it, it usually doesn't crash again for the duration of that session. 

It also crashes often when coming back to Plasma after shutting down my single-GPU passthrough VM. I'll try to get a backtrace again next time it happens but the drkonqi has been telling me there's no info.

https://userbase.kde.org/LatteDock/HowToReportCrashes

1. a proper crash report is needed if it is possible to produce with steps from https://userbase.kde.org/LatteDock/HowToReportCrashes
2. can you send your latte layout file to check out your panels and docks?

Created attachment 143146 [details]
Current Latte Layout

I wouldnt be surprised if this is a crash from one of:
1. Virtual Desktop Bar.
2. Media Bar
3. Event Calendar

as this is a startup crash make sure that you have followed steps from proper latte autostarting at: 
https://psifidotos.blogspot.com/2021/08/latte-dock-v0101-bug-fix-release.html

for the applets you need to remove them one by one in order to find the faulter in case it is an applet creating the issue.

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!

(In reply to Michail Vourlakos from comment #9)
> I wouldnt be surprised if this is a crash from one of:
> 1. Virtual Desktop Bar.
> 2. Media Bar
> 3. Event Calendar
> 
> as this is a startup crash make sure that you have followed steps from
> proper latte autostarting at: 
> https://psifidotos.blogspot.com/2021/08/latte-dock-v0101-bug-fix-release.html
> 
> for the applets you need to remove them one by one in order to find the
> faulter in case it is an applet creating the issue.

Sorry I somehow missed the email notification here. 

I don't restore my Plasma sessions. I start with a clean one. And I only have one Latte instance in my Autostart. 

I can't submit the crash report as the option is always grayed out. No idea why (when things like KWin crash, the option isn't grayed out, it's not like I've removed some system component).

I've removed the mentioned widgets and will see if it changes anything. Before removing the widgets it would crash on login about 8 times out of 10. It almost never crashes during sessions after that, though.

Created attachment 143786 [details]
New crash information added by DrKonqi

latte-dock (0.10.4) using Qt 5.15.2

- What I was doing when the application crashed:
Happened again at login after removing the media widget. Will try again after removing the other widgets mentioned.

-- Backtrace (Reduced):
#4  0x00007fc537d1f860 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5
#5  0x00007fc537d50b3c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5
#6  0x00007fc537d3741a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5
#7  0x00007fc537d3cb96 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5
#8  0x00007fc537d3d5a5 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5

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!

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!

(In reply to Bug Janitor Service from comment #14)
> 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!

I've provided the info needed on two separate occasions, but no one replied. I would like this reopened.

It says to mark the bug as "REPORTED" but I've never seen that option.

https://userbase.kde.org/LatteDock/HowToReportCrashes

provided back traces are not employable.
They do not point to any related latte library and they do not provide the needed followed codepath

(In reply to Michail Vourlakos from comment #17)
> https://userbase.kde.org/LatteDock/HowToReportCrashes
> 
> provided back traces are not employable.
> They do not point to any related latte library and they do not provide the
> needed followed codepath

Alright well I'll try to use ddd and collect the correct information and provide it asap.

needs info with proper crash report

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!

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!

(In reply to Michail Vourlakos from comment #19)
> needs info with proper crash report

Okay, so I've installed ddd, and I've read the documentation, but I'm a bit curious as to how I should go about doing this. Cause the thing is, the crashes pretty much *exclusively* happen on login. They don't happen throughout the day, or anything like that. Basically about 50-60% of the time I log in to plasma, latte will crash when it attempts to load (the first notification window will pop up, and then the panels/dock will either flash for a second or not show at all, and then the crash dialog window pops up). 

I guess I could remove latte from my autostart stuff, and start it with `ddd latte-dock` after login, that's the only way I can think of, hopefully the crashes still even happen when I do it that way. I was thinking there might be a race condition (probably in a plasmoid/widget like suggested) and waiting until after login to try and start latte might not trigger any crashes. But I'll try and force it as best as I can and report back. I'll leave it as resolved worksforme unless I can reproduce with ddd in which case I'll reopen.