Loses theme at each relaunch

[mcharron]

Environent

Ubuntu 15.10
Albert 0.8.6
Source: ppa

The problem is : when I restart my computer, my chosen theme (Yosemite Dark) is not saved, it'll apply the first theme in the list. I don't know why, it worked when I was under Ubuntu 15.04, and since I upgrade, it does not work anymore.

Any solution ?
Thanks

[ManuelSchneid3r]

@mcharron When you run albert in terminal, do you get a message that albert not been shut down properly?

[mcharron]

Yes !

Critical: Application has not been terminated graciously

That's the reason ?

[ManuelSchneid3r]

@mcharron Did you just restart your pc or do you get this message everytime? Yep thats the reason. Seema like albert crashes is /var/crash empty?

[mcharron]

I restart my computer once a week (shutdown friday, start monday). Here's the last lines of /var/crash/_usr_bin_albert.1000.crash :

Title: albert crashed with SIGSEGV in QObjectPrivate::connectImpl()
UnreportableReason: This package is not officially supported by Ubuntu. Remove each third-party packages and retry.
UpgradeStatus: Upgraded to wily on 2016-04-08 (11 days ago)

The message is in french (cause my system is in french), I translated it. It seems like Albert doesn't like Ubuntu 15.10 :(

Oh and it crashed this morning for no reason, it doesn't crash usually.

[ManuelSchneid3r]

@mcharron I had a bad grade, mais je sais un peu francais. Living close to alsace we learned it at school. Well I guess to read the backtrace its enough. How big is albert.1000.crash? Can you somehow ship it? E.g. By dropbox link, if you use it, or google drive.

[mcharron]

Ahah nice :) I put it on Gdrive.

https://drive.google.com/open?id=0B6Wz_C5Iqv_BNEM2MXNucWl4X28

Here it comes !

[ManuelSchneid3r]

Albert 0.8.6

Are you sure? apport reports albert 0.8.7.2-1~webupd8~vivid0 [origin: unknown]

[mcharron]

Oh my bad, I upgrade to 0.8.7 yesterday.

[leakypixel]

A workaround to save the config file is to gracefully close albert with kill -s TERM $(pidof albert).

[ManuelSchneid3r]

Hm. Somehow I cant show the backtrace. I setup a VM of 15.10. Are you able to reproduce the issue?

[leakypixel]

I am having the same problem on a clean install of lubuntu 15.10. Sending a TERM signal to the process results in a clean exit, whereas reboot/shutdown of the OS results in a dirty/non-graceful exit.

[mcharron]

Yes, I'm able to reproduce. I juste have to restart my PC.

That's what append this morning, I start my computer each monday, and my theme reseted :(

The stacktrace is the same, the error too. It seems that one package makes Albert crash...

[ManuelSchneid3r]

Could you please post the stack trace here? Somehow when I print it it is empty. Looks like webupd8 did not build the tag v0.8.7.2, but something else, maybe HEAD... and its not a debug build.

[ghost]

Probably related. I'm using 0.8.8 from the Arch AUR.
When running in a terminal, ctrl-c causes albert to close uncleanly. The expected behaviour was that it would be intercepted for a clean exit.

[ShawnMcCool]

I'm running from the Arch AUR and every time I close Albert, no matter how it was closed.. When I restart I'm back at the default theme with the default plugins enabled.

[blasphemite]

I'm having the same issue, v0.8.8

[ManuelSchneid3r]

@ShawnMcCool even if you close it by Alt-F4 or SIGTERM?

To those using the aur package, could you please send me the backtrace of the crash? Just use 'coredumpctl gdb' and in gdb 'bt' for backtrace. I have still no clue where to start.

[blasphemite]

@blasphemite amending to say all of my prefs are reset on reboot, not just the theme. Also using ppa

[ManuelSchneid3r]

@mcharron @blasphemite @ShawnMcCool @leakypixel please provide information about display manager, desktop environment and the way you reboot.

[mcharron]

Display manager ? Xfce, that's what you mean ?

Desktop env: Ubuntu 15.10 64bits, 8go ram, Athlon X2 2.7GHz

The way I reboot : "Power button" (in the sidebar) -> shutdown. And then press the physical button on my pc to start it

[ManuelSchneid3r]

Display manager ? Xfce, that's what you mean ?

LightDM, GDM, KDM, SDDM, Slim. Check this wiki. I guess you are using lightdm, under xubuntu. Are you absolutely sure that you used the power button when albert failed? Not e.g. the albert system extension or the terminal?

[leakypixel]

Machine 1:
Distro: Lubuntu, Display manager: LXDM, Environment: LXDE, Reboot method: reboot from terminal. This machine is shut down/rebooted often (work computer). From PPA.

Machine 2:
Distro: Arch, Display manager: LXDM, Environment: LXDE, Reboot method: reboot from terminal. This machine is shut down/rebooted very rarely (personal computer). From AUR.

[mcharron]

Ok my bad, yes I'm using lightdm, under Xubuntu. Yes, when I shutdown my computer Albert is currently running (daemon), but I didn't see when it failed : my computer is shutting down, I have no error message....

It launches at boot, so I guess it's the system extension that loads

[ManuelSchneid3r]

It launches at boot, so I guess it's the system extension that loads

I failed in asking precise :D I have to rephrase my question. Are you absolutely sure that you used the power button in the xfce panel to restart/shutdown your machine before you received the message from albert telling you that it was not terminated graciously? And are you sure that you did not use the albert system extension, e.g.

, or the command reboot, systemctl reboot or any other system controlling commands in the terminal to reboot?

This is pedantic I know, but I have to make sure if we're all suffering the same issue.

[mcharron]

Mmh, I'm not really receiving the message that Albert was not terminated graciously, I'm just seeing that my theme is reseted, and in the /var/crash the message is displayed right after launching my PC :/

[ManuelSchneid3r]

Please update.

[blasphemite]

Distro: GalliumOS
Display manager: LXDM
I reboot via the "shutdown" and "restart" buttons. I am positive that I did not use the Albert system extension or any system commands

[ghost]

Arch + openbox, shutting down with poweroff in Albert, which in turn is configured to use "systemctl poweroff -i", results in improper shutdown message

[ManuelSchneid3r]

@blasphemite LXDE is known to just kill all apps on session quit. Ridiculous. #182
@mcharron The binaries somehow differ (wow should I worry?) so I cant run GDB on it. Can you please post a backtrace on the next crash?

[mcharron]

Ok i'll do it on next crash !

[ManuelSchneid3r]

I opened a collective issue #197 for termination / serialization problems on unix. If you want to track it make sure you watch it. Please continue any discussion related to this problem in #197.