Bug 147518 - Impossible to start Libreoffice 7.3.0.3 in any mode
Summary: Impossible to start Libreoffice 7.3.0.3 in any mode
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (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-18 13:51 UTC by Davide Soresinetti
Modified: 2022-09-30 03:54 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
dump (350.25 KB, application/vnd.tcpdump.pcap)
2022-03-02 11:09 UTC, Davide Soresinetti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Davide Soresinetti 2022-02-18 13:51:23 UTC
Description:
libreoffice --norestore --safe-mode
dbus[9775]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2760.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace


Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x41eb3)[0x7f665754feb3]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x42074)[0x7f6657550074]
/lib/x86_64-linux-gnu/libc.so.6(+0x46520)[0x7f6657307520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0xf8)[0x7f665735b808]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f6657307476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7f66572ed7b7]
/lib/x86_64-linux-gnu/libdbus-1.so.3(+0xbed6)[0x7f66569dced6]
/lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_warn_return_if_fail+0x0)[0x7f6656a03620]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x17f)[0x7f66569f28af]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x1b6)[0x7f66569f3d86]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x9d)[0x7f66569f3fdd]
/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x18a)[0x7f66522fc23a]
/lib/x86_64-linux-gnu/libcups.so.2(+0x73d41)[0x7f6655b2ed41]
/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x81)[0x7f6655ade591]
/usr/lib/libreoffice/program/libmergedlo.so(+0x367972b)[0x7f665abf272b]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x44b58)[0x7f6657552b58]
/lib/x86_64-linux-gnu/libc.so.6(+0x98927)[0x7f6657359927]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x7f66573e99e4]


Steps to Reproduce:
1.libreoffice
2.libreoffice --norestore --safe-mode
3.libreoffice --safe-mode

Actual Results:
dbus[9775]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2760.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace


Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x41eb3)[0x7f665754feb3]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x42074)[0x7f6657550074]
/lib/x86_64-linux-gnu/libc.so.6(+0x46520)[0x7f6657307520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0xf8)[0x7f665735b808]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f6657307476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7f66572ed7b7]
/lib/x86_64-linux-gnu/libdbus-1.so.3(+0xbed6)[0x7f66569dced6]
/lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_warn_return_if_fail+0x0)[0x7f6656a03620]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x17f)[0x7f66569f28af]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x1b6)[0x7f66569f3d86]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x9d)[0x7f66569f3fdd]
/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x18a)[0x7f66522fc23a]
/lib/x86_64-linux-gnu/libcups.so.2(+0x73d41)[0x7f6655b2ed41]
/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x81)[0x7f6655ade591]
/usr/lib/libreoffice/program/libmergedlo.so(+0x367972b)[0x7f665abf272b]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x44b58)[0x7f6657552b58]
/lib/x86_64-linux-gnu/libc.so.6(+0x98927)[0x7f6657359927]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x7f66573e99e4]

Expected Results:
same result with different version of libreoffice.

Lenovo P70 with 2 external monitor in display port.
nvidia M600M as display board.
driver noveau


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
OpenGL vendor string: nouveau
OpenGL renderer string: NV117
OpenGL core profile version string: 4.3 (Core Profile) Mesa 21.2.6
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.3 (Compatibility Profile) Mesa 21.2.6
OpenGL shading language version string: 4.30
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
Comment 2 Davide Soresinetti 2022-03-02 11:08:04 UTC
arn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
warn:vcl.gdi:70317:70317:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0xFFFF
dbus[70317]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2760.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
warn:desktop:70317:70974:desktop/source/app/crashreport.cxx:61: minidump generated: /tmp/3fe08a10-c7f8-45b8-48b8e792-764dd148.dmp
warn:desktop:70317:70974:desktop/source/app/crashreport.cxx:61: minidump generated: /tmp/3fe08a10-c7f8-45b8-48b8e792-764dd148.dmp
Comment 3 Davide Soresinetti 2022-03-02 11:09:35 UTC
Created attachment 178618 [details]
dump

warn:desktop:70317:70974:desktop/source/app/crashreport.cxx:61: minidump generated: /tmp/3fe08a10-c7f8-45b8-48b8e792-764dd148.dmp
warn:desktop:70317:70974:desktop/source/app/crashreport.cxx:61: minidump generated: /tmp/3fe08a10-c7f8-45b8-48b8e792-764dd148.dmp
Comment 4 Buovjaga 2022-03-02 11:32:32 UTC
So was this with 7.3.1?
Comment 5 QA Administrators 2022-08-30 04:39:11 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2022-09-30 03:54:41 UTC
Dear Davide Soresinetti,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp