[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #11 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 Maxi Schimmel changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 --- Comment #10 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 Aleix Pol changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #9 from Aleix Pol --- That -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 --- Comment #8 from Aleix Pol --- There's not much we can do with this valgrind output. Maybe passing --track-origins=yes would help? Also there's a memory management issue fixed in KF 5.51 Kirigami, I would suggest updating to it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Christoph Feck --- Information was provided with comment #4, changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 --- Comment #6 from Maxi Schimmel --- Andrew, thanks for your comment. I sent an attachment with valgrind output. I apologize but I don't have any knowledge about valgrind's output. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 Andrew Crouthamel changed: What|Removed |Added Keywords||triaged --- Comment #5 from Andrew Crouthamel --- 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 set the bug status 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! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 --- Comment #4 from Maxi Schimmel --- Created attachment 115855 --> https://bugs.kde.org/attachment.cgi?id=115855=edit Valgrind output My valgrind output with 'zypper sh' open on konsole. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 --- Comment #3 from Fabian Vogt --- (In reply to Maxi Schimmel from comment #2) > Hi, thanks for your help and interest. > Today I notice that all time when I tried to start Discover had opened > 'zypper sh' on a konsole tab. > I closed it and Discover starts fine. > Can you try the same combination? > Thanks! Still working fine here. Discover shows the "System management is locked by the application with pid 31551 (zypper)." message as expected. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 --- Comment #2 from Maxi Schimmel --- Hi, thanks for your help and interest. Today I notice that all time when I tried to start Discover had opened 'zypper sh' on a konsole tab. I closed it and Discover starts fine. Can you try the same combination? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399714] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=399714 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Fabian Vogt --- I can't reproduce that issue here. Please install valgrind and upload the output of "valgrind plasma-discover". -- You are receiving this mail because: You are watching all bug changes.
