[IMPORTANT] Some filepaths will change.

johnraff · 2016-04-19 02:24:51

In an attempt to make our installed filepaths a bit less cumbersome ( see this discussion ) the latest packages now on the repo will move some things around.

tl:dr

IMPORTANT If you haven't yet upgraded, or if upgrading broke your LightDM login, read this post.

Almost everything should be taken care of automatically and go on working as before, and new users will get the new setup, but existing users will want to do one thing. In a terminal:

ln -sT /usr/share/images/bunsen/wallpapers ~/Pictures/wallpapers/bunsen

This will make sure there's a symlink in your wallpapers directory pointing to the BunsenLabs wallpapers. Now in the menu go to Preferences>Choose Wallpaper and set your wallpaper again.

details

Packages are not allowed to edit users' personal files, so you will also find that a couple of menu items pointing to help files will bring up empty pages because the help files have moved. Check /usr/share/bunsen/skel/.config/openbox/menu.xml and adjust your own ~/.config/openbox/menu.xml.
Also, your last wallpaper may not be recorded correctly, so you might have to choose your wallpaper again.

System file locations like /usr/bin don't change.
File paths that went bunsen/bunsen-packagename are simplified, eg /usr/lib/bunsen/bunsen-common > /usr/lib/bunsen/common
The biggest change is where image files are stored. Everything now goes under /usr/share/images/bunsen/.
Desktop backgrounds are in "wallpapers", grub and login backgrounds in their own directories.
(See the above forum thread for the detailed discussion.)

If you hit any other issues, please post here for help.

Last edited by johnraff (2016-04-21 03:23:16)

hhh · 2016-04-19 02:43:39

Almost everything should be taken care of automatically and go on working as before, and new users will get the new setup, but existing users will want to do one thing. In a terminal: ...

Silly point, but this will be after a sudo apt update && sudo apt upgrade. I'm not on either of my BL partitions to test it ATM.

Horizon_Brave · 2016-04-19 02:57:09

Jeez, you call this simplified?!? /usr/lib/bunsen/common I'm lost already!

Kidding of course! Great work, Raff and congrats and above all thanks for the updating and time it must have taken to get all of the other dependent packages edited and changed around for the move. When you say it's on the repo, does that mean, it's live and ready to go with an update/upgrade?

Just out of curiosity, what are some of the files that you had to modify to get this whole switch over to work?

Eraph · 2016-04-19 03:15:20

Nice work, folks!

ghorvath · 2016-04-19 05:16:13

After a reboot I have my conkys as they should be, except they are not transparent anymore. Which file should I change (and how) to get transparency back? Thanks.

+1 for a list of files changed, even some commit messages on github are fine.

Also +1 for this particular thread. I would appreciate a similar thread for all "bigger" changes. Maybe we could have a whole section dedicated to such changelog posts in the forum?

johnraff · 2016-04-19 07:40:35

I should have put it in the first post, but the packages affected, and the versions where the changes kick in, are:
bunsen-common 8.8-1
bunsen-configs 8.7-1
bunsen-docs 8.1-1
bunsen-images 8.5-1
bunsen-pipemenus 8.9-1
bunsen-welcome 8.10-1

You can go to GitHub and check each of those repos to see what changed.

EDIT: Putting it together went in two steps: first, change the install paths for files affected, second, edit any references to those files in other files.

@ghorvath I had the same thing. I think it's the compositor using a cached version of the wallpaper image. Anyway, when I reset the wallpaper from the menu (don't forget to add the symlink mentioned above first), transparency came back.

Last edited by johnraff (2016-04-19 08:08:18)

damo · 2016-04-19 15:39:36

BLOB Themes Manager

Don't forget to change the image filepaths for any saved themes in `~/.config/blob`, if you were using BL images. The affected files could be:

LISTMSG.txt
lightdm-gtk-greeter.conf
bg-saved.cfg (for nitrogen)
.fehbg (for feh)

ghorvath · 2016-04-19 19:32:44

Hm, indeed, transparency came back after resetting the wallpaper.

However, my wallpaper was the original one which had the bunsenlabs flame and logo lower right (not simply right). Where can I find this wallpaper? It was not in the symlink directory I added...

damo · 2016-04-19 20:48:15

ghorvath wrote:

....
However, my wallpaper was the original one which had the bunsenlabs flame and logo lower right (not simply right). Where can I find this wallpaper? It was not in the symlink directory I added...

Presumably wherever you saved it to, since there isn't a default BL desktop background with that layout. Were you using the lightdm login background as a wallpaper? (/images/bunsen/login/default.png)

EDIT: BL images are now all installed in `/usr/share/images/bunsen`.

johnraff · 2016-04-20 02:27:54

LightDM config issue
During the package upgrade a dialogue window might come up saying:

dpkg wrote:

Configuration file '/etc/lightdm/lightdm.conf.bunsen'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** lightdm.conf.bunsen (Y/I/N/O/D/Z) [default=N] ?

This only happens if you have customized lightdm.conf.

Although dpkg says the "default" is "N", you should CHOOSE Y.
(Make a backup of /etc/lightdm/lightdm.conf.bunsen if you can't remember what changes you put in.)

If you choose "N", LightDM will refuse to log in! (*)
If it's already happened, then you'll have to edit /etc/lightdm/lightdm.conf.bunsen by hand. Press Ctrl+Alt+F2 to get to a console screen and login from there. Now either

startx

to get a desktop, find /etc/lightdm/lightdm.conf.bunsen in Thunar, use "Open as root" to edit it and find line 114, which reads 'session-setup-script=/usr/lib/bunsen/bunsen-configs/bl-user-setup'. Change it to:

session-setup-script=/usr/lib/bunsen/configs/bl-user-setup

Alternatively, don't use startx but

sudo nano  /etc/lightdm/lightdm.conf.bunsen

and make the edit in the terminal. Then press Ctrl+d to exit the terminal and Ctrl+Alt+F7 to get back to LightDM which should now accept your login.

(*) The reason LightDM will not login with the old config file is that it refers to a login script that no longer exists at that location.

Last edited by johnraff (2016-04-22 02:09:31)

ghorvath · 2016-04-20 12:00:32

damo wrote:

ghorvath wrote:
....
However, my wallpaper was the original one which had the bunsenlabs flame and logo lower right (not simply right). Where can I find this wallpaper? It was not in the symlink directory I added...
Presumably wherever you saved it to, since there isn't a default BL desktop background with that layout. Were you using the lightdm login background as a wallpaper? (/images/bunsen/login/default.png)
EDIT: BL images are now all installed in `/usr/share/images/bunsen`.

Yes, I believe I used that. (Actually, that was somehow put as wallpaper automatically, I never set my wallpaper manually. However, now I cannot choose it, because it is in a different folder than images/bunsen/wallpaper :-( )

Does it have some config files I can edit?
Thanks.

xaos52 · 2016-04-20 12:04:10

Creating the link mentioned in the top post of this thread should be sufficient.

damo · 2016-04-20 13:22:46

ghorvath wrote:

... However, now I cannot choose it, because it is in a different folder than images/bunsen/wallpaper :-( )
....

Add a location in Nitrogen -> Preferences -> Add;

or directly edit `~/.config/nitrogen/nitrogen.cfg`;

or put a symlink to it in the wallpapers directory;

or copy it into the wallpapers directory;

or copy it into your Pictures directory;

or etc etc....

xaos52 wrote:

Creating the link mentioned in the top post of this thread should be sufficient.

The default bl-login-background image (`default.png`) is now in `usr/share/images/bunsen/login`

Last edited by damo (2016-04-20 13:26:55)

ghorvath · 2016-04-20 14:54:29

Thanks, I decided to create another symlink.

jalexander9 · 2016-04-20 15:57:05

To be clear, I made changes to lightdm, and also lost the login-screen-background.

I edited the file:

/etc/lightdm/lightdm-gtk-greeter.conf.bunsen

with:

background=/usr/share/images/bunsen/login/bl-login-background

Also, I deleted old images and refreshed new ones from 'galternatives'.

The login-screen background works at login boot sequence now.

EDIT: BTW thanks to all who worked on this @johnraff, @xaos52, @damo, et. al. !!

Last edited by jalexander9 (2016-04-20 16:00:38)

AndyMender · 2016-04-20 19:02:12

For what it's worth, the symlink method works for wallpapers alright. Nitrogen sees them and conky retains its transparency.

Thank you everyone for developing BunsenLabs and great contact with the community .

hhh · 2016-04-21 02:11:22

@johnraff, I missed that this update could break lightdm and chose the default. I needed to reboot for the fix to work.

Please add [IMPORTANT!!!] or similar to the OP subject, this is a must-read announcement. Thanks!

Horizon_Brave · 2016-04-21 03:03:02

Hmm... So doesn't this mean, that any change we make that modifies the /etc/lightdm/lightdm* config files will cause this same thing? If we make a change that changes the conf files, and then have users upgrade, it'll give them the same overwrite prompt with N being the default right?

johnraff · 2016-04-21 03:35:56

@hhh added [IMPORTANT]

@Horizon_Brave Yes, if you modify any file under /etc (config file), then later if a new version of the package which put it there ships a modified version, dpkg will spot that your changes are in danger of being overwritten and put up that dialogue.

Sometimes neither option is right! You might want to incorporate the package developers' improvements but also keep some of your tweaks... (That's what's happening to some people here.)

In such cases I'd say the way to go is make a backup of your current file (dpkg also makes backups in some cases), let the package upgrade, and then go and see if you want to put back any of the tweaks you had in before.

damo · 2016-04-21 17:29:16

menu.xml help entries

If you get a blank text window, you may need to edit the command to reflect the new docs path

/usr/share/bunsen/docs/helpfile-menu.txt

#1 2016-04-19 02:24:51

[IMPORTANT] Some filepaths will change.

#2 2016-04-19 02:43:39

Re: [IMPORTANT] Some filepaths will change.

#3 2016-04-19 02:57:09

Re: [IMPORTANT] Some filepaths will change.

#4 2016-04-19 03:15:20

Re: [IMPORTANT] Some filepaths will change.

#5 2016-04-19 05:16:13

Re: [IMPORTANT] Some filepaths will change.

#6 2016-04-19 07:40:35

Re: [IMPORTANT] Some filepaths will change.

#7 2016-04-19 15:39:36

Re: [IMPORTANT] Some filepaths will change.

#8 2016-04-19 19:32:44

Re: [IMPORTANT] Some filepaths will change.

#9 2016-04-19 20:48:15

Re: [IMPORTANT] Some filepaths will change.

#10 2016-04-20 02:27:54

Re: [IMPORTANT] Some filepaths will change.

#11 2016-04-20 12:00:32

Re: [IMPORTANT] Some filepaths will change.

#12 2016-04-20 12:04:10

Re: [IMPORTANT] Some filepaths will change.

#13 2016-04-20 13:22:46

Re: [IMPORTANT] Some filepaths will change.

#14 2016-04-20 14:54:29

Re: [IMPORTANT] Some filepaths will change.

#15 2016-04-20 15:57:05

Re: [IMPORTANT] Some filepaths will change.

#16 2016-04-20 19:02:12

Re: [IMPORTANT] Some filepaths will change.

#17 2016-04-21 02:11:22

Re: [IMPORTANT] Some filepaths will change.

#18 2016-04-21 03:03:02

Re: [IMPORTANT] Some filepaths will change.

#19 2016-04-21 03:35:56

Re: [IMPORTANT] Some filepaths will change.

#20 2016-04-21 17:29:16

Re: [IMPORTANT] Some filepaths will change.

Board footer