Panel crash when adding the applet..

[floopy1962]

No description provided.

[ilgarmehmetali]

If you are using tip of the budgie-desktop git, i havent been able to follow its commits for some time now. If so i would have to check it first before commenting on this. And can you try it with version 10.3.

If you are using 10.3, can you post coredump output here.
You could run "coredumpctl | tail", check last instance of budgie-panel for its id and run "coredumpctl info id" to get its coredump.

[floopy1962]

Hi there and thanks for the reply. Pixel saver is such a useful applet, without it google chrome looks like crap :D however you can see what i got when i paste coredumpctl | tail but nothing comes out on coredumpctl info id... i'm new to solus and i'm amazed from the speed and productivity i can have here be couse there is now to many repos like in debian, ubunbtu based systems.
Btw budgie-desktop version is 10.3.1 :P

[ilgarmehmetali]

You should look at the pid column of the "coredumpctl | tail". Its 877 for your case. And use 877 instead of id. "coredumpctl info 877"

You can also start panel from terminal too,

budgie-panel --replace &

[floopy1962]

           PID: 877 (budgie-daemon)
           UID: 1000 (floopy1962)
           GID: 1000 (floopy1962)
        Signal: 11 (SEGV)
     Timestamp: Fri 2017-07-21 15:42:43 BST (18h ago)
  Command Line: budgie-daemon
    Executable: /usr/bin/budgie-daemon
 Control Group: /user.slice/user-1000.slice/session-c2.scope
          Unit: session-c2.scope
         Slice: user-1000.slice
       Session: c2
     Owner UID: 1000 (floopy1962)
       Boot ID: d888826463644f62bf98489786b77a89
    Machine ID: 744555736be547da825875c1aee14c0b
      Hostname: floopy1962-pc
       Message: Process 877 (budgie-daemon) of user 1000 dumped core.

I didn't need to restart panel since it restart it self right after i add the applet...

[renegat59]

I'm facing the same issue. Whenever i am adding the applet Budgie is crashing. Coredump also not found. Any ideas?

[artillect]

I was having the same issue, but installing xprop via eopkg solved it.