Bug 147162 - Starting Calc on 7.3.0.3 crashes - All other progs from libreoffice starting ok
Summary: Starting Calc on 7.3.0.3 crashes - All other progs from libreoffice starting ok
Status: RESOLVED DUPLICATE of bug 147135
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.3.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-03 17:46 UTC by willy_wuchtig
Modified: 2022-02-04 12:40 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description willy_wuchtig 2022-02-03 17:46:11 UTC
Description:
Starting Calc 7.2.5.2 is working fine
Starting Calc 7.3.0.3 crashes. 
Everything else from 7.3.0.3 is also working fine (like draw & writer)

Steps to Reproduce:
1.start calc in menu or terminal
2.
3.

Actual Results:
no window is opening
crash-dump will be generated

Expected Results:
window should open


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
OpenGL vendor string: AMD
OpenGL renderer string: Radeon RX550/550 Series (POLARIS12, DRM 3.41.0, 5.13.0-27-generic, LLVM 12.0.0)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.0.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
Comment 1 Buovjaga 2022-02-03 17:51:46 UTC
Please copy and paste here the contents of your Help - About by clicking the copy button. This allows us to know more about your system.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 willy_wuchtig 2022-02-03 18:11:26 UTC
Version: 7.3.0.3 / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded
Comment 3 Buovjaga 2022-02-03 18:20:09 UTC
Which desktop environment? Is session X11 or Wayland?
Comment 4 willy_wuchtig 2022-02-03 18:26:43 UTC
(In reply to Buovjaga from comment #3)
> Which desktop environment? Is session X11 or Wayland?

X11
Comment 5 Buovjaga 2022-02-03 18:33:23 UTC
Distro and desktop environment? GNOME, KDE...?
Comment 6 willy_wuchtig 2022-02-03 18:49:41 UTC
(In reply to Buovjaga from comment #5)
> Distro and desktop environment? GNOME, KDE...?

Kernel: 5.13.0-27-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 
    wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal
Comment 7 willy_wuchtig 2022-02-04 11:48:55 UTC
Starting Calc with: SAL_USE_VCLPLUGIN=gen libreoffice7.3 --calc
(try to start the prog with Visual Class Library = x11 and not with gtk3)  
>
Version: 7.3.0.3 / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: x11
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Result: Calc still crashing
Comment 8 Buovjaga 2022-02-04 12:36:49 UTC
Maybe you could try Linux-rpm_deb-x86_64@tb87-TDF-dbg from https://dev-builds.libreoffice.org/daily/master/current.html

First make sure that you have gdb installed.
Then launch the debug-build LibreOffice like

program/soffice --backtrace

After the crash it should create a gdbtrace.log file. You could attach the file to this report.

This is the same process as described in https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Comment 9 Xisco Faulí 2022-02-04 12:40:46 UTC
it looks like a duplicated of bug 147135

*** This bug has been marked as a duplicate of bug 147135 ***