Bug 469534 - Crash on startup when offline
Summary: Crash on startup when offline
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.27.4
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-09 15:15 UTC by Phoebe Harris
Modified: 2024-06-07 03:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Output of gdb debugging (25.22 KB, text/plain)
2023-05-09 15:15 UTC, Phoebe Harris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Phoebe Harris 2023-05-09 15:15:34 UTC
Created attachment 158803 [details]
Output of gdb debugging

SUMMARY

When disconnected from the internet, opening Discover will result in a segmentation fault. 

If Discover has recently opened while connected to the internet, it will not crash again, even when disconnected. However, given enough time between opening, this behaviour returns. 


STEPS TO REPRODUCE
1. Turn internet off
2. Open Discover 

OBSERVED RESULT

Discover crashes

EXPECTED RESULT

Discover displays its cached apps, the same as if it had been loaded online recently and then reopened when offline. 

Note: The crash handler only displayed "The crash information could not be generated". The attached trace is from running `gdb plasma-discover` and downloading debug symbols. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Running a slightly odd kernel (6.2.8-eupnea, from the Depthboot project). I don't think this would cause an issue(?), but figured it would be polite to mention.
Comment 1 Tobias Fella 2023-05-10 09:09:29 UTC
Your gdb output is missing a backtrace, could you provide one as well?
Comment 2 Phoebe Harris 2023-05-10 10:09:05 UTC
(In reply to Tobias Fella from comment #1)
> Your gdb output is missing a backtrace, could you provide one as well?

Oops, my mistake. 

As I mentioned, the KDE Crash Reporter is failing to generate a backtrace. How may I do so with gdb (or otherwise fix the crash reporter)?
Comment 3 Phoebe Harris 2023-05-16 10:04:40 UTC
Okay, I figured it out. Here's the backtrace

```
#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007f6e4f69f2d3 in __pthread_kill_internal (signo=11, threadid=<optimized out>) at pthread_kill.c:78
#2  0x00007f6e4f64fa08 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x00007f6e51d1d81f in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.106.0/src/kcrash.cpp:626
#4  0x00007f6e4f64fab0 in <signal handler called> () at /usr/lib/libc.so.6
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007f6e4f69f2d3 in __pthread_kill_internal (signo=11, threadid=<optimized out>) at pthread_kill.c:78
#7  0x00007f6e4f64fa08 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#8  0x00007f6e4f64fab0 in <signal handler called> () at /usr/lib/libc.so.6
#9  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=15, no_tid=no_tid@entry=0) at pthread_kill.c:44
#10 0x00007f6e4f69f2d3 in __pthread_kill_internal (signo=15, threadid=<optimized out>) at pthread_kill.c:78
#11 0x00007f6e4f64fa08 in __GI_raise (sig=15) at ../sysdeps/posix/raise.c:26
#12 0x00007f6e4ea52210 in g_closure_invoke (closure=0x7f6de8003f00, return_value=0x0, n_param_values=3, param_values=0x7f6dfdfbc930, invocation_hint=0x7f6dfdfbc8b0)
    at ../glib/gobject/gclosure.c:832
#13 0x00007f6e4ea80427 in signal_emit_unlocked_R.isra.0
    (node=node@entry=0x56045ba71560, detail=detail@entry=0, instance=instance@entry=0x7f6de8005850, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7f6dfdfbc930) at ../glib/gobject/gsignal.c:3851
#14 0x00007f6e4ea70095 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7f6dfdfbcb00)
    at ../glib/gobject/gsignal.c:3565
#15 0x00007f6e4ea70324 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at ../glib/gobject/gsignal.c:3622
#16 0x00007f6e4e532eeb in emit_closed_in_idle (user_data=0x7f6dec0096e0) at ../glib/gio/gdbusconnection.c:1375
#17 0x00007f6e4e70f53b in g_main_dispatch (context=0x56045ba79130) at ../glib/glib/gmain.c:3460
#18 g_main_context_dispatch (context=0x56045ba79130) at ../glib/glib/gmain.c:4200
#19 0x00007f6e4e76c219 in g_main_context_iterate.constprop.0 (context=0x56045ba79130, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4276
#20 0x00007f6e4e70e1a2 in g_main_context_iteration (context=context@entry=0x56045ba79130, may_block=may_block@entry=1) at ../glib/glib/gmain.c:4343
#21 0x00007f6e16921fde in dconf_gdbus_worker_thread (user_data=0x56045ba79130) at ../dconf/gdbus/dconf-gdbus-thread.c:82
#22 0x00007f6e4e73c315 in g_thread_proxy (data=0x56045ba792a0) at ../glib/glib/gthread.c:831
#23 0x00007f6e4f69d44b in start_thread (arg=<optimized out>) at pthread_create.c:444
#24 0x00007f6e4f720e40 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
```
Comment 4 Bug Janitor Service 2023-05-31 03:45:22 UTC
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!
Comment 5 Phoebe Harris 2023-05-31 09:49:33 UTC
Whoops, I didn't realise it was the submitter that was supposed to remove NEEDSINFO after providing a backtrace
Comment 6 Harald Sitter 2024-05-08 06:35:26 UTC
Looks like a bug in dconf. I am guessing this has since resolved itself?
Comment 7 Bug Janitor Service 2024-05-23 03:45:25 UTC
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!
Comment 8 Bug Janitor Service 2024-06-07 03:46:15 UTC
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!