Bug 468481 - Labplot Crashes when attempting to import data and there is no spreadsheet.
Summary: Labplot Crashes when attempting to import data and there is no spreadsheet.
Status: RESOLVED FIXED
Alias: None
Product: LabPlot2
Classification: Applications
Component: general (show other bugs)
Version: 2.10.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Alexander Semke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-13 19:57 UTC by Dar Elliott
Modified: 2023-04-15 17:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dar Elliott 2023-04-13 19:57:20 UTC
SUMMARY
When attempting to import data from a file if there is no spreadsheet available to receive the data the desktop crashes.

STEPS TO REPRODUCE
1. Open new Labplot Project.
2. Do not open a spreadsheet or any workbooks etc.
3. Open the import data dialog and select a file, type appears to be irrelevant.
4. Attempt to select the target data container.

OBSERVED RESULT
Full crash of desktop environment and all running apps. 

EXPECTED RESULT
Option for "New Spreadsheet" or similar.

SOFTWARE/OS VERSIONS
Linux: Fedora Linux 37.20230413.0 (Silverblue)
Kernel: Linux 6.2.9-200.fc37.x86_64 x86_64
Gnome Version: 43.4
Display Server: Wayland
Device: Acer Swift 3 SF316-51
KDE Plasma Version: N/A, as on Gnome Desktop
Relevant Flatpaks: 
Adwaita theme  org.kde.KStyle.Adwaita 5.15-22.08
KDE Application Platform org.kde.Platform 5.15-22.08              
LabPlot org.kde.labplot2 2.10.0

ADDITIONAL INFORMATION
There is an obvious workaround, namely opening a new spreadsheet before importing data. This bug is hence hardly urgent.
Comment 1 Alexander Semke 2023-04-13 21:19:59 UTC
(In reply to D3mon from comment #0)
> SUMMARY
> When attempting to import data from a file if there is no spreadsheet
> available to receive the data the desktop crashes.
> 
> STEPS TO REPRODUCE
> 1. Open new Labplot Project.
> 2. Do not open a spreadsheet or any workbooks etc.
> 3. Open the import data dialog and select a file, type appears to be
> irrelevant.
> 4. Attempt to select the target data container.
> 
> OBSERVED RESULT
> Full crash of desktop environment and all running apps. 
What do you mean with the full crash of the desktop environment and all app? Is it like the whole desktop is frozen when you try open that drop-down list for the target data container?
Comment 2 Dar Elliott 2023-04-13 21:42:40 UTC
(In reply to Alexander Semke from comment #1)
> (In reply to D3mon from comment #0)
> > SUMMARY
> > When attempting to import data from a file if there is no spreadsheet
> > available to receive the data the desktop crashes.
> > 
> > STEPS TO REPRODUCE
> > 1. Open new Labplot Project.
> > 2. Do not open a spreadsheet or any workbooks etc.
> > 3. Open the import data dialog and select a file, type appears to be
> > irrelevant.
> > 4. Attempt to select the target data container.
> > 
> > OBSERVED RESULT
> > Full crash of desktop environment and all running apps. 
> What do you mean with the full crash of the desktop environment and all app?
> Is it like the whole desktop is frozen when you try open that drop-down list
> for the target data container?

The desktop environment hangs momentarily, then blacks out and returns to login screen.
Upon logging again all apps had closed and login scripts ran, as if after a reboot.
Bug persists between reboots and clean app install.
Comment 3 Alexander Semke 2023-04-15 08:13:46 UTC
(In reply to D3mon from comment #2)
> The desktop environment hangs momentarily, then blacks out and returns to
> login screen.
> Upon logging again all apps had closed and login scripts ran, as if after a
> reboot.
> Bug persists between reboots and clean app install.
This looks like an issue in the window manager/system. I'd assume it also happens in other cases when you need to open such a combo box.  Is it possible for you to validate this and also with X11?
Comment 4 Dar Elliott 2023-04-15 17:40:08 UTC
(In reply to Alexander Semke from comment #3)
> (In reply to D3mon from comment #2)
> > The desktop environment hangs momentarily, then blacks out and returns to
> > login screen.
> > Upon logging again all apps had closed and login scripts ran, as if after a
> > reboot.
> > Bug persists between reboots and clean app install.
> This looks like an issue in the window manager/system. I'd assume it also
> happens in other cases when you need to open such a combo box.  Is it
> possible for you to validate this and also with X11?

Issue no longer occurs following latest update of Labplot Flatpak. Issue not present under X11, again following latest update. Unknown if it was present under X11 before update. Marking this Bug as resolved. Thank you for your time.
Comment 5 Dar Elliott 2023-04-15 17:50:20 UTC
(In reply to D3mon from comment #4)
> (In reply to Alexander Semke from comment #3)
> > (In reply to D3mon from comment #2)
> > > The desktop environment hangs momentarily, then blacks out and returns to
> > > login screen.
> > > Upon logging again all apps had closed and login scripts ran, as if after a
> > > reboot.
> > > Bug persists between reboots and clean app install.
> > This looks like an issue in the window manager/system. I'd assume it also
> > happens in other cases when you need to open such a combo box.  Is it
> > possible for you to validate this and also with X11?
> 
> Issue no longer occurs following latest update of Labplot Flatpak. Issue not
> present under X11, again following latest update. Unknown if it was present
> under X11 before update. Marking this Bug as resolved. Thank you for your
> time.

Some additional information:
Bug was not noticed with any other combo box while using Labplot under Wayland. I updated all Flatpaks today, and then tested for the bug under both X11 and Wayland, on both the laptop on which the bug was originally noted and on a desktop.  Following the update, which I believe was an update of some Lab plot dependencies rather than of the app itself, the bug is no longer present under both X11 and Wayland. It appears to have been resolved by the update to some of the dependencies. Again, thank you for your time.