You are not logged in.

Pages: 1 2

#1 2021-03-22 06:26:51

cyborge
Member
Registered: 2021-01-08
Posts: 30

Display stuck at start and Latte dock crashed

Recently I started facing this issue , when i start my laptop the display get stuck and nothing seems to work .
Latte-Dock crashed in background , only the mouse cursor works.
I have to wait for some time and then restart the latte dock from terminal.
Is there any specific command output i need to give because after restarting the latte dock i wont have any crash reports.
I'm using :
Plasma-desktop 5.21.3-1
latte-dock-git

Last edited by cyborge (2021-03-29 07:57:44)

Offline

#2 2021-03-22 08:03:29

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,326

Re: Display stuck at start and Latte dock crashed

The journal/systemd stores crash reports: https://wiki.archlinux.org/index.php/Co … _core_dump

Symptom-wise this just sounds like the early KMS race especially so if you use auto-login,  check: https://wiki.archlinux.org/index.php/Ke … _KMS_start

Offline

#3 2021-03-22 13:17:09

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

V1del wrote:

The journal/systemd stores crash reports: https://wiki.archlinux.org/index.php/Co … _core_dump

Symptom-wise this just sounds like the early KMS race especially so if you use auto-login,  check: https://wiki.archlinux.org/index.php/Ke … _KMS_start

coredumpctl gave :

PID: 888 (latte-dock)
           UID: 1000 (chandan)
           GID: 1000 (chandan)
        Signal: 11 (SEGV)
     Timestamp: Thu 2021-03-18 11:22:15 IST (4 days ago)
  Command Line: /usr/bin/latte-dock
    Executable: /usr/bin/latte-dock
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (chandan)
       Boot ID: 67193fcd43e440a3a3b8dd5db4017729
    Machine ID: 9eae7df7e9ca42dcb1093f06a22dcef2
      Hostname: cyborge
       Storage: /var/lib/systemd/coredump/core.latte-dock.1000.67193fcd43e440a3a3b8dd5db4017729.888.1616046735000000.zst (inaccessible)
       Message: Process 888 (latte-dock) of user 1000 dumped core.
                
                Stack trace of thread 888:
                #0  0x00007f0a1d17aef5 raise (libc.so.6 + 0x3cef5)
                #1  0x00007f0a1eea4189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
                #2  0x00007f0a1d17af80 __restore_rt (libc.so.6 + 0x3cf80)
                #3  0x0000558e23743f80 n/a (latte-dock + 0x70f80)
                #4  0x0000558e237701c5 n/a (latte-dock + 0x9d1c5)
                #5  0x0000558e2375acb3 n/a (latte-dock + 0x87cb3)
                #6  0x0000558e2379ab73 n/a (latte-dock + 0xc7b73)
                #7  0x0000558e2379bbe4 n/a (latte-dock + 0xc8be4)
                #8  0x0000558e237b5b2c n/a (latte-dock + 0xe2b2c)
                #9  0x0000558e237ab424 n/a (latte-dock + 0xd8424)
                #10 0x0000558e2375b415 n/a (latte-dock + 0x88415)
                #11 0x0000558e2382e0b1 n/a (latte-dock + 0x15b0b1)
                #12 0x00007f0a1dba5066 n/a (libQt5DBus.so.5 + 0x21066)
                #13 0x00007f0a1dba865b n/a (libQt5DBus.so.5 + 0x2465b)
                #14 0x00007f0a1dba8a8b n/a (libQt5DBus.so.5 + 0x24a8b)
                #15 0x00007f0a1dbab478 n/a (libQt5DBus.so.5 + 0x27478)
                #16 0x00007f0a1d911532 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2532)
                #17 0x00007f0a1e62a752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
                #18 0x00007f0a1d8e4a2a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a2a)
                #19 0x00007f0a1d8e7523 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b8523)
                #20 0x00007f0a1d93e054 n/a (libQt5Core.so.5 + 0x30f054)
                #21 0x00007f0a1bd8eb84 g_main_context_dispatch (libglib-2.0.so.0 + 0x53b84)
                #22 0x00007f0a1bde2c21 n/a (libglib-2.0.so.0 + 0xa7c21)
                #23 0x00007f0a1bd8d3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                #24 0x00007f0a1d93d691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e691)
                #25 0x00007f0a1d8e33ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #25 0x00007f0a1d8e33ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
           PID: 888 (latte-dock)
           UID: 1000 (chandan)
           GID: 1000 (chandan)
        Signal: 11 (SEGV)
     Timestamp: Thu 2021-03-18 11:22:15 IST (4 days ago)
  Command Line: /usr/bin/latte-dock
    Executable: /usr/bin/latte-dock
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (chandan)
       Boot ID: 67193fcd43e440a3a3b8dd5db4017729
    Machine ID: 9eae7df7e9ca42dcb1093f06a22dcef2
      Hostname: cyborge
       Storage: /var/lib/systemd/coredump/core.latte-dock.1000.67193fcd43e440a3a3b8dd5db4017729.888.1616046735000000.zst (inaccessible)
       Message: Process 888 (latte-dock) of user 1000 dumped core.
                
                Stack trace of thread 888:
                #0  0x00007f0a1d17aef5 raise (libc.so.6 + 0x3cef5)
                #1  0x00007f0a1eea4189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
                #2  0x00007f0a1d17af80 __restore_rt (libc.so.6 + 0x3cf80)
                #3  0x0000558e23743f80 n/a (latte-dock + 0x70f80)
                #4  0x0000558e237701c5 n/a (latte-dock + 0x9d1c5)
                #5  0x0000558e2375acb3 n/a (latte-dock + 0x87cb3)
                #6  0x0000558e2379ab73 n/a (latte-dock + 0xc7b73)
                #7  0x0000558e2379bbe4 n/a (latte-dock + 0xc8be4)
                #8  0x0000558e237b5b2c n/a (latte-dock + 0xe2b2c)
                #9  0x0000558e237ab424 n/a (latte-dock + 0xd8424)
                #10 0x0000558e2375b415 n/a (latte-dock + 0x88415)
                #11 0x0000558e2382e0b1 n/a (latte-dock + 0x15b0b1)
                #12 0x00007f0a1dba5066 n/a (libQt5DBus.so.5 + 0x21066)
                #13 0x00007f0a1dba865b n/a (libQt5DBus.so.5 + 0x2465b)
                #14 0x00007f0a1dba8a8b n/a (libQt5DBus.so.5 + 0x24a8b)
                #15 0x00007f0a1dbab478 n/a (libQt5DBus.so.5 + 0x27478)
                #16 0x00007f0a1d911532 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2532)
                #17 0x00007f0a1e62a752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
                #18 0x00007f0a1d8e4a2a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a2a)
                #19 0x00007f0a1d8e7523 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b8523)
                #20 0x00007f0a1d93e054 n/a (libQt5Core.so.5 + 0x30f054)
                #21 0x00007f0a1bd8eb84 g_main_context_dispatch (libglib-2.0.so.0 + 0x53b84)
                #22 0x00007f0a1bde2c21 n/a (libglib-2.0.so.0 + 0xa7c21)
                #23 0x00007f0a1bd8d3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                #24 0x00007f0a1d93d691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e691)
                #25 0x00007f0a1d8e33ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #26 0x00007f0a1d8eb844 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc844)
                #27 0x0000558e2370e73b n/a (latte-dock + 0x3b73b)
                #28 0x00007f0a1d165b25 __libc_start_main (libc.so.6 + 0x27b25)
                #29 0x0000558e2370f03e _start (latte-dock + 0x3c03e)
                
                Stack trace of thread 942:
                #0  0x00007f0a1ca739ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                #1  0x00007f0a1ca6d260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                #2  0x00007f0a12648cec n/a (iris_dri.so + 0x4edcec)
                #3  0x00007f0a126474c8 n/a (iris_dri.so + 0x4ec4c8)
                #4  0x00007f0a1ca67299 start_thread (libpthread.so.0 + 0x9299)
                #5  0x00007f0a1d23d053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 945:
                #0  0x00007f0a1d23237f __poll (libc.so.6 + 0xf437f)
                #1  0x00007f0a1bde2baf n/a (libglib-2.0.so.0 + 0xa7baf)
                #2  0x00007f0a1bd8d3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                #3  0x00007f0a1d93d6ac _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6ac)
                #4  0x00007f0a1d8e33ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #5  0x00007f0a1d6fbd12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
                #6  0x00007f0a1db9b098 n/a (libQt5DBus.so.5 + 0x17098)
                #7  0x00007f0a1d6fceff n/a (libQt5Core.so.5 + 0xcdeff)
                #8  0x00007f0a1ca67299 start_thread (libpthread.so.0 + 0x9299)
                #9  0x00007f0a1d23d053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 943:
                #0  0x00007f0a1ca739ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                #1  0x00007f0a1ca6d260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                #2  0x00007f0a12648cec n/a (iris_dri.so + 0x4edcec)
                #3  0x00007f0a126474c8 n/a (iris_dri.so + 0x4ec4c8)
                #4  0x00007f0a1ca67299 start_thread (libpthread.so.0 + 0x9299)
                #5  0x00007f0a1d23d053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 909:
                #0  0x00007f0a1d23237f __poll (libc.so.6 + 0xf437f)
                #1  0x00007f0a1faf763b n/a (libxcb.so.1 + 0xc63b)
                #2  0x00007f0a1faf937b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
                #3  0x00007f0a19588131 n/a (libQt5XcbQpa.so.5 + 0x5e131)
                #4  0x00007f0a1d6fceff n/a (libQt5Core.so.5 + 0xcdeff)
                #5  0x00007f0a1ca67299 start_thread (libpthread.so.0 + 0x9299)
                #6  0x00007f0a1d23d053

And I have already added the required things to mkinitcpio.conf

Last edited by cyborge (2021-03-22 13:28:12)

Offline

#4 2021-03-22 13:41:33

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,326

Re: Display stuck at start and Latte dock crashed

And you regenerated the images?

Offline

#5 2021-03-22 14:05:10

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

V1del wrote:

And you regenerated the images?

Yes, I have pacman hooks for that, it gets regenerated after every update,

Offline

#6 2021-03-26 04:31:59

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

Now even KDE started crashing. When I start laptop, the display gets stuck at desktop wallpaper . I see no latte dock, no application bars , no options to close applications if launched using terminal .

Offline

#7 2021-03-26 07:52:58

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

kwin crashed, try https://wiki.archlinux.org/index.php/In … ver_(i965)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#8 2021-03-26 20:39:49

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

After doing this the system didn't even boot. I had to delete that conf file from tty session to boot again.

I don't know why this is happening.
Sometimes Kwin is crashing
Latte dock is marked zombie process when I check in tasks and then getting killed .(this happening everytime I start laptop)

Last edited by cyborge (2021-03-26 20:40:36)

Offline

#9 2021-03-26 20:52:55

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

the system didn't even boot. I had to delete that conf file from tty

That's contradictive. The system *did* boot, but I assume your display server (SDDM?) failed?

Also what "conf file"? You didn't create the configuration from the tearing section, did you?
You're supposed to export MESA_LOADER_DRIVER_OVERRIDE=i965 somewhere. Is that what you did and how?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#10 2021-03-27 04:13:54

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

the system didn't even boot. I had to delete that conf file from tty

That's contradictive. The system *did* boot, but I assume your display server (SDDM?) failed?

Also what "conf file"? You didn't create the configuration from the tearing section, did you?
You're supposed to export MESA_LOADER_DRIVER_OVERRIDE=i965 somewhere. Is that what you did and how?

Oh I think I did something else.
How can I export it. Do I have to add it to mkinitcpio.conf or anything else..

Offline

#11 2021-03-27 06:20:42

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

https://wiki.archlinux.org/index.php/En … _variables

Where exactly depends on how you start your session /etc/profile* is read everywhere.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#12 2021-03-28 20:01:57

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

https://wiki.archlinux.org/index.php/En … _variables

Where exactly depends on how you start your session /etc/profile* is read everywhere.

Tried this , after doing this it started crashing everytime.
And latte-dock doesn't work ,with or without adding i965

Last edited by cyborge (2021-03-28 20:04:21)

Offline

#13 2021-03-28 20:15:10

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

Can you please state what precisely you did and what is "it" that "started crashing everytime"?
Esp. since "it" is apparently not latte-dock?

Also please provide updated coredumps for latte-dock.

Assuming it's no GL related, the present coredumps show latte-dock crashing in some n/a symbol and it seems it responds to some dbus IO.
=> Build latte-dock locally, https://wiki.archlinux.org/index.php/Arch_Build_System and add 

options=(debug !strip)

to the PKGBUILD, https://wiki.archlinux.org/index.php/De … ing_Traces

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#14 2021-03-29 02:21:47

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

Can you please state what precisely you did and what is "it" that "started crashing everytime"?
Esp. since "it" is apparently not latte-dock?

Also please provide updated coredumps for latte-dock.

Assuming it's no GL related, the present coredumps show latte-dock crashing in some n/a symbol and it seems it responds to some dbus IO.
=> Build latte-dock locally, https://wiki.archlinux.org/index.php/Arch_Build_System and add 

options=(debug !strip)

to the PKGBUILD, https://wiki.archlinux.org/index.php/De … ing_Traces

I added the MESA_LOADER_DRIVER_OVERRIDE=i965 in /etc/environment file .

Here is the latest coredump for latte-dock

           PID: 655 (latte-dock)
           UID: 1000 (chandan)
           GID: 1000 (chandan)
        Signal: 11 (SEGV)
     Timestamp: Mon 2021-03-29 07:47:22 IST (2min 29s ago)
  Command Line: /usr/bin/latte-dock
    Executable: /usr/bin/latte-dock
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (chandan)
       Boot ID: af4ebd5f540b4d5294ebf0a23b48801d
    Machine ID: c2955e1dca09471aa10c753e2269a126
      Hostname: arch
       Storage: /var/lib/systemd/coredump/core.latte-dock.1000.af4ebd5f540b4d5294ebf0a23b48801d.655.1616984242000000.zst
       Message: Process 655 (latte-dock) of user 1000 dumped core.
                
                Stack trace of thread 655:
                #0  0x00007f4e43a04ef5 raise (libc.so.6 + 0x3cef5)
                #1  0x00007f4e4572e189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
                #2  0x00007f4e43a04f80 __restore_rt (libc.so.6 + 0x3cf80)
                #3  0x0000556a13d877e0 n/a (latte-dock + 0x747e0)
                #4  0x0000556a13db1cb5 n/a (latte-dock + 0x9ecb5)
                #5  0x0000556a13d9c7b3 n/a (latte-dock + 0x897b3)
                #6  0x0000556a13ddca53 n/a (latte-dock + 0xc9a53)
                #7  0x0000556a13dde7e4 n/a (latte-dock + 0xcb7e4)
                #8  0x0000556a13df87ac n/a (latte-dock + 0xe57ac)
                #9  0x0000556a13dedfd4 n/a (latte-dock + 0xdafd4)
                #10 0x0000556a13d9cf15 n/a (latte-dock + 0x89f15)
                #11 0x0000556a13e708e1 n/a (latte-dock + 0x15d8e1)
                #12 0x00007f4e4442f066 n/a (libQt5DBus.so.5 + 0x21066)
                #13 0x00007f4e4443265b n/a (libQt5DBus.so.5 + 0x2465b)
                #14 0x00007f4e44432a8b n/a (libQt5DBus.so.5 + 0x24a8b)
                #15 0x00007f4e44435478 n/a (libQt5DBus.so.5 + 0x27478)
                #16 0x00007f4e4419b532 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2532)
                #17 0x00007f4e44eb4752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
                #18 0x00007f4e4416ea2a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a2a)
                #19 0x00007f4e44171523 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b8523)
                #20 0x00007f4e441c8054 n/a (libQt5Core.so.5 + 0x30f054)
                #21 0x00007f4e42618f9c g_main_context_dispatch (libglib-2.0.so.0 + 0x53f9c)
                #22 0x00007f4e4266ca49 n/a (libglib-2.0.so.0 + 0xa7a49)
                #23 0x00007f4e426166f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
                #24 0x00007f4e441c7691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e691)
                #25 0x00007f4e4416d3ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #26 0x00007f4e44175844 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc844)
                #27 0x0000556a13d4f73b n/a (latte-dock + 0x3c73b)
                #28 0x00007f4e439efb25 __libc_start_main (libc.so.6 + 0x27b25)
                #29 0x0000556a13d5003e _start (latte-dock + 0x3d03e)
                
                Stack trace of thread 728:
                #0  0x00007f4e426669c9 g_mutex_lock (libglib-2.0.so.0 + 0xa19c9)
                #1  0x00007f4e42618b3c g_main_context_prepare (libglib-2.0.so.0 + 0x53b3c)
                #2  0x00007f4e4266c8f6 n/a (libglib-2.0.so.0 + 0xa78f6)
                #3  0x00007f4e426166f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
                #4  0x00007f4e441c76ac _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6ac)
                #5  0x00007f4e4416d3ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #6  0x00007f4e43f85d12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
                #7  0x00007f4e44425098 n/a (libQt5DBus.so.5 + 0x17098)
                #8  0x00007f4e43f86eff n/a (libQt5Core.so.5 + 0xcdeff)
                #9  0x00007f4e432f1299 start_thread (libpthread.so.0 + 0x9299)
                #10 0x00007f4e43ac7053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 681:
                #0  0x00007f4e43abc37f __poll (libc.so.6 + 0xf437f)
                #1  0x00007f4e4638163b n/a (libxcb.so.1 + 0xc63b)
                #2  0x00007f4e4638337b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
                #3  0x00007f4e3fb40131 n/a (libQt5XcbQpa.so.5 + 0x5e131)
                #4  0x00007f4e43f86eff n/a (libQt5Core.so.5 + 0xcdeff)
                #5  0x00007f4e432f1299 start_thread (libpthread.so.0 + 0x9299)
                #6  0x00007f4e43ac7053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 721:
                #0  0x00007f4e432fd9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                #1  0x00007f4e432f7260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                #2  0x00007f4e3d27e38c n/a (i965_dri.so + 0x1c138c)
                #3  0x00007f4e3d27daa8 n/a (i965_dri.so + 0x1c0aa8)
                #4  0x00007f4e432f1299 start_thread (libpthread.so.0 + 0x9299)
                #5  0x00007f4e43ac7053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 720:
                #0  0x00007f4e432fd9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                #1  0x00007f4e432f7260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                #2  0x00007f4e3d27e38c n/a (i965_dri.so + 0x1c138c)
                #3  0x00007f4e3d27daa8 n/a (i965_dri.so + 0x1c0aa

And on building latte-dock-git manually , it simply gets build and installed , nothing happens there. I added the options you gave in PKGBUILD

UPDATE: This is happening with latte-dock-git version not with latte-dock

Last edited by cyborge (2021-03-29 03:06:47)

Offline

#15 2021-03-29 05:59:08

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

This is happening with latte-dock-git version not with latte-dock

…

it simply gets build and installed , nothing happens there. I added the options you gave in PKGBUILD

The point is to get a better backtrace - is the lasted posted backktrace already for the debug enabled build??

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#16 2021-03-29 07:02:54

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

This is happening with latte-dock-git version not with latte-dock

…

it simply gets build and installed , nothing happens there. I added the options you gave in PKGBUILD

The point is to get a better backtrace - is the lasted posted backktrace already for the debug enabled build??

I was not sure, took again . Latest coredump with backtrace enabled

           PID: 686 (latte-dock)
           UID: 1000 (chandan)
           GID: 1000 (chandan)
        Signal: 11 (SEGV)
     Timestamp: Mon 2021-03-29 12:30:37 IST (1min 54s ago)
  Command Line: /usr/bin/latte-dock
    Executable: /usr/bin/latte-dock
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (chandan)
       Boot ID: b3e727d9abd94f3fa8fba71808432c7c
    Machine ID: c2955e1dca09471aa10c753e2269a126
      Hostname: arch
       Storage: /var/lib/systemd/coredump/core.latte-dock.1000.b3e727d9abd94f3fa8fba71808432c7c.686.1617001237000000.zst
       Message: Process 686 (latte-dock) of user 1000 dumped core.
                
                Stack trace of thread 686:
                #0  0x00007f81c8d12ef5 raise (libc.so.6 + 0x3cef5)
                #1  0x00007f81caa3c189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
                #2  0x00007f81c8d12f80 __restore_rt (libc.so.6 + 0x3cf80)
                #3  0x0000557022e657e0 _ZN7QStringC4ERKS_ (latte-dock + 0x747e0)
                #4  0x0000557022e8fcb5 _ZNK5Latte7Layouts12Synchronizer19currentLayoutsNamesEv (latte-dock + 0x9ecb5)
                #5  0x0000557022e7a7b3 _ZNK5Latte7Layouts7Manager19currentLayoutsNamesEv (latte-dock + 0x897b3)
                #6  0x0000557022ebaa53 _ZN5Latte8Settings10Controller7Layouts11initLayoutsEv (latte-dock + 0xc9a53)
                #7  0x0000557022ebc7e4 _ZN5Latte8Settings10Controller7LayoutsC2EPNS0_7Handler10TabLayoutsE (latte-dock + 0xcb7e4)
                #8  0x0000557022ed67ac _ZN5Latte8Settings7Handler10TabLayoutsC2EPNS0_6Dialog14SettingsDialogE (latte-dock + 0xe57ac)
                #9  0x0000557022ecbfd4 _ZN5Latte8Settings6Dialog14SettingsDialogC2EP7QWidgetPNS_6CoronaE (latte-dock + 0xdafd4)
                #10 0x0000557022e7af15 _ZN5Latte7Layouts7Manager23showLatteSettingsDialogEib (latte-dock + 0x89f15)
                #11 0x0000557022f4e8e1 _ZN16LatteDockAdaptor18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv (latte-dock + 0x15d8e1)
                #12 0x00007f81c973d066 n/a (libQt5DBus.so.5 + 0x21066)
                #13 0x00007f81c974065b n/a (libQt5DBus.so.5 + 0x2465b)
                #14 0x00007f81c9740a8b n/a (libQt5DBus.so.5 + 0x24a8b)
                #15 0x00007f81c9743478 n/a (libQt5DBus.so.5 + 0x27478)
                #16 0x00007f81c94a9532 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2532)
                #17 0x00007f81ca1c2752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
                #18 0x00007f81c947ca2a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a2a)
                #19 0x00007f81c947f523 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b8523)
                #20 0x00007f81c94d6054 n/a (libQt5Core.so.5 + 0x30f054)
                #21 0x00007f81c7926f9c g_main_context_dispatch (libglib-2.0.so.0 + 0x53f9c)
                #22 0x00007f81c797aa49 n/a (libglib-2.0.so.0 + 0xa7a49)
                #23 0x00007f81c79246f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
                #24 0x00007f81c94d5691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e691)
                #25 0x00007f81c947b3ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #26 0x00007f81c9483844 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc844)
                #27 0x0000557022e2d73b main (latte-dock + 0x3c73b)
                #28 0x00007f81c8cfdb25 __libc_start_main (libc.so.6 + 0x27b25)
                #29 0x0000557022e2e03e _start (latte-dock + 0x3d03e)
                
                Stack trace of thread 754:
                #0  0x00007ffd2577b6e8 n/a (linux-vdso.so.1 + 0x6e8)
                #1  0x00007ffd2577ba47 __vdso_clock_gettime (linux-vdso.so.1 + 0xa47)
                #2  0x00007f81c8d9d015 __clock_gettime (libc.so.6 + 0xc7015)
                #3  0x00007f81c94d4f92 n/a (libQt5Core.so.5 + 0x30df92)
                #4  0x00007f81c94d383a _ZN14QTimerInfoList17updateCurrentTimeEv (libQt5Core.so.5 + 0x30c83a)
                #5  0x00007f81c94d3e16 _ZN14QTimerInfoList9timerWaitER8timespec (libQt5Core.so.5 + 0x30ce16)
                #6  0x00007f81c94d53ef n/a (libQt5Core.so.5 + 0x30e3ef)
                #7  0x00007f81c7926b30 g_main_context_prepare (libglib-2.0.so.0 + 0x53b30)
                #8  0x00007f81c797a8f6 n/a (libglib-2.0.so.0 + 0xa78f6)
                #9  0x00007f81c79246f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
                #10 0x00007f81c94d56ac _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6ac)
                #11 0x00007f81c947b3ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
                #12 0x00007f81c9293d12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
                #13 0x00007f81c9733098 n/a (libQt5DBus.so.5 + 0x17098)
                #14 0x00007f81c9294eff n/a (libQt5Core.so.5 + 0xcdeff)
                #15 0x00007f81c85ff299 start_thread (libpthread.so.0 + 0x9299)
                #16 0x00007f81c8dd5053 __clone (libc.so.6 + 0xff053)
                
                Stack trace of thread 749:
                #0  0x00007f81c860b9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                #1  0x00007f81c8605260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                #2  0x00007f81be58438c n/a (i965_dri.so

Offline

#17 2021-03-29 07:11:19

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

See?

                #3  0x0000557022e657e0 _ZN7QStringC4ERKS_ (latte-dock + 0x747e0)
                #4  0x0000557022e8fcb5 _ZNK5Latte7Layouts12Synchronizer19currentLayoutsNamesEv (latte-dock + 0x9ecb5)
                #5  0x0000557022e7a7b3 _ZNK5Latte7Layouts7Manager19currentLayoutsNamesEv (latte-dock + 0x897b3)
                #6  0x0000557022ebaa53 _ZN5Latte8Settings10Controller7Layouts11initLayoutsEv (latte-dock + 0xc9a53)
                #7  0x0000557022ebc7e4 _ZN5Latte8Settings10Controller7LayoutsC2EPNS0_7Handler10TabLayoutsE (latte-dock + 0xcb7e4)
                #8  0x0000557022ed67ac _ZN5Latte8Settings7Handler10TabLayoutsC2EPNS0_6Dialog14SettingsDialogE (latte-dock + 0xe57ac)
                #9  0x0000557022ecbfd4 _ZN5Latte8Settings6Dialog14SettingsDialogC2EP7QWidgetPNS_6CoronaE (latte-dock + 0xdafd4)
                #10 0x0000557022e7af15 _ZN5Latte7Layouts7Manager23showLatteSettingsDialogEib (latte-dock + 0x89f15)
                #11 0x0000557022f4e8e1 _ZN16LatteDockAdaptor18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv (latte-dock + 0x15d8e1)

The symbols changed. It tries to show the settings dialog and stumbles over some layouts.
=> Move away the latte configuration?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#18 2021-03-29 07:14:59

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

See?

The symbols changed. It tries to show the settings dialog and stumbles over some layouts.
=> Move away the latte configuration?

Yes I have Edna layout installed, what should i do now.
Remove all configs or switch to default layout.

Offline

#19 2021-03-29 07:18:35

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

I don't even know what you're talking about, but just from context, i'd first switch to the default layout…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#20 2021-03-29 07:21:01

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

I don't even know what you're talking about, but just from context, i'd first switch to the default layout…

I was saying that, in latte-dock I have "edna" layout installed .
Now I'll switch to default layout any check again.

Offline

#21 2021-03-29 07:23:07

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

I understood as much, but I'm not using plasma, have never used latte-dock and no idea what the "edna layout" is or implies ;-)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#22 2021-03-29 07:29:47

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

seth wrote:

I understood as much, but I'm not using plasma, have never used latte-dock and no idea what the "edna layout" is or implies ;-)

OK .
But still the issue exists, I guess I'll delete this thread and create a new one with proper logs and info .
Thanks for all the help. :}

Last edited by cyborge (2021-03-29 07:30:06)

Offline

#23 2021-03-29 07:51:27

seth
Member
Registered: 2012-09-03
Posts: 63,049

Re: Display stuck at start and Latte dock crashed

Please don't use "closed" (that's for mods and locked threads) and just move away the latte-dock config.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#24 2021-03-29 09:27:28

bwidlar
Member
Registered: 2018-02-06
Posts: 29

Re: Display stuck at start and Latte dock crashed

I had problems with X today (no nvidia dri).
I fix the issue adding this:

Section "Device"
   Identifier "Device0"
   Driver "nvidia"
EndSection

to a .conf file to directory /etc/X11/xorg.conf.d

Offline

#25 2021-03-29 09:43:20

cyborge
Member
Registered: 2021-01-08
Posts: 30

Re: Display stuck at start and Latte dock crashed

bwidlar wrote:

I had problems with X today (no nvidia dri).
I fix the issue adding this:

Section "Device"
   Identifier "Device0"
   Driver "nvidia"
EndSection

to a .conf file to directory /etc/X11/xorg.conf.d

Thanks for help . But with this sddm didn't start .

Offline

Pages: 1 2

Board footer

Powered by FluxBB