(Solved) Using BL netinstall script in XFCE Debian jessie system

dhalgren · 2016-02-16 05:38:59

Can the install script be safely used on a jessie system with xfce installed? --to get a bunsen experience. (I've had my fun with xfce, but wanna go back to bunsen now, but don't wanna completely reinstall.)

Mod Note: Split from https://forums.bunsenlabs.org/viewtopic.php?id=1265
-HoaS

Last edited by dhalgren (2016-02-18 23:15:58)

Head_on_a_Stick · 2016-02-16 08:11:11

dhalgren wrote:

Can the install script be safely used on a jessie system with xfce installed?

I'm not sure TBH.

I think that the BL stuff will take preference (ie, LightDM will be set as the display manager) thanks to /etc/alternatives but I'm not 100% on that.

If you can wait, I can try it in a VM tonight and report back.

dhalgren · 2016-02-16 09:18:37

HoaS, sounds good to me, I'm happy to wait and let you test,
I also don't care if the Bunsen stuff takes precedence, I'll just be happy to be back with Bunsen without needing to completely re-install.

hhh · 2016-02-16 14:43:50

dhalgren wrote:

Can the install script be safely used on a jessie system with xfce installed? --to get a bunsen experience.

I don't think anyone's tried that. The way to go though is to add our repository(s) and install bunsen-* and log into the new session, but no one's tested that yet either AFAIK. Now that rc2 is out, it's first on my ToDo list.

Head_on_a_Stick · 2016-02-16 20:04:01

@dhalgreen:

Just installed xfce jessie (from a live ISO image) in a VM then downloaded and ran johnraff's script (from the graphical desktop, naturally) and it installed everything without error

Rebooted to a swish BunsenLabs GRUB theme & LightDM theme but the "Default Xsession" in LightDM starts XFCE (unsurprisingly).

To get the BL desktop, simply select "openbox" from the little wrench-symbol menu (next to the logout button) in the Log In screen.

It all seems to work just fine but please back up any and all important data before attempting this yourself.

hhh · 2016-02-17 01:36:54

^Nice!

I included the BL repositories to a jessie Live LXDE (non-free) install, updated, and ran...

sudo apt install bunsen-*

That worked too (took forever, the jessie live builds are already so out of date)...
https://forums.bunsenlabs.org/viewtopic … 090#p19090

dhalgren · 2016-02-17 01:45:07

Well, it worked, and it didn't work, all at once.

I was using compton and tint2 in xfce, and neither will start as they are supposed to from the autostart.xml

Also, nitrogen does not restore the wallpaper. Otherwise, it is all fine and dandy.

I am assuming that the existing xfce installation is interfering with bunsen configs, but I have no idea of what to remove or change, except to purge xfce, which I don't want to do at this moment. So any suggestions would be appreciated.

But it is nice to be at home, even if it isn't perfect.

EDIT: Interestingly, when going back into xfce after the process, my tint2 is now the bunsen tint2, and not what I had previously configured. I don't mind that at all. It's rather nice to have my favourite configured better than I did.

Last edited by dhalgren (2016-02-17 02:15:32)

johnraff · 2016-02-17 05:22:58

dhalgren wrote:

I am assuming that the existing xfce installation is interfering with bunsen configs, but I have no idea of what to remove or change, except to purge xfce, which I don't want to do at this moment. So any suggestions would be appreciated.

Try

pgrep -af xfce

and see what xfce processes are running - it might give you an idea of something to remove or disable. On standard BL I get

7961 xfce4-volumed
7976 xfce4-power-manager
7978 /usr/lib/i386-linux-gnu/xfce4/xfconf/xfconfd
7999 /usr/lib/i386-linux-gnu/xfce4/notifyd/xfce4-notifyd

so anything other than that might be causing the trouble.

dhalgren · 2016-02-17 06:20:47

@johnraff

This seems not to be an issue:

bruce@debian:~$ pgrep -af xfce
3299 xfce4-power-manager
3301 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd

In at least the sense that this is all I get when I log in without tints or conky or compositing running. I will have a (largely uneducated)poke around and try to find the problem.

If worst comes to worst, I can always do a clean install, though it is quite easy to just start everything up manually.

Are the xsession errors of any use? Here is my most recent error file, which refers to tiint2 and conky, but I lack the knowledge to know what it means in practical terms:

Xsession: X session started for bruce at Wednesday 17 February  16:41:36 AEST 2016
localuser:bruce being added to access control list
openConnection: connect: No such file or directory
cannot connect to brltty at :0
Conky: statfs64 '/media/disk': No such file or directory
Conky: forked to background, pid is 1411

Conky: desktop window (e0) is root window
Conky: window type - desktop
Conky: drawing to created window (0x2400001)
Conky: drawing to double buffer
Conky: statfs64 '/media/disk': No such file or directory
NOT SANDBOXED
[fresh  1424] not implemented: PPB_OpenGLES2VertexArrayObject;1.0
[fresh  1424] not implemented: PPB_OpenGLES2DrawBuffers(Dev);1.0
Vector smash protection is enabled.
[fresh  1424] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh  1424] [PPB] {zilch} ppb_flash_set_instance_always_on_top instance=11, on_top=1
[fresh  1424] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh  1424] [PPB] {zilch} ppb_flash_set_instance_always_on_top instance=12, on_top=1
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
1455691514960	addons.productaddons	ERROR	Request failed certificate checks: [Exception... "SSL is required and URI scheme is not https."  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory
Conky: statfs64 '/media/disk': No such file or directory

Last edited by dhalgren (2016-02-17 06:51:40)

dhalgren · 2016-02-18 01:42:14

It seems to have something to do with the .desktop files in ~/.config/autostart

Simply deleting these files does not solve the problem, but editing them does. E.g.,

The entry for compton now reads:

[Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=Compton
Comment=
Exec=compton
OnlyShowIn=XFCE;OPENBOX;
StartupNotify=false
Terminal=false
Hidden=false

and this results in compton autostarting when it did not previously do so. Doing the same for tint2 and conky causes them to autostart also.

I was using pnmixer previously, and there was an entry for it, so I changed it to include openbox and now it works, taking precedence over volti in the openbox autostart file.

This may have something to do with my previously trying lxde for the first time, but I doubt it because all lxde config files have been removed, AFAIK. It seems to be the xfce way of doing things, but only further research will answer that for me.

There is no entry for clipit (or nitrogen) in the autostart folder, so I will have a go at creating these files and see if it resolves the remaining autostart problems.

johnraff · 2016-02-18 01:50:41

This is one way to go, but ~/.config/openbox/autostart is an easier place to start things up on an openbox setup. However, you need to be careful not to start the same processes in both ways simultaneously.

dhalgren · 2016-02-18 02:17:06

@johnraff

Indeed, I had a similar thought and decided to have another look at the openbox autostart, getting to it via the menu. What I found was a completely empty file which did not exist when I looked at the folder in thunar.

With the certainty of no knowledge at all, I renamed "autostart.xml" to "autostart", removed the xfce autostart folder, logged out and back in, and voila. Everything running perfectly, including the bl-welcome script.

As often is the case, the answer was much simpler than I had imagined, and the solution easy.

I can now say that using your netinstall script works in an existing system, with perhaps the smallest modification necessary.

Cheers, and thanks. Nice to be back using BL!

Bruce

#1 2016-02-16 05:38:59

(Solved) Using BL netinstall script in XFCE Debian jessie system

#2 2016-02-16 08:11:11

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#3 2016-02-16 09:18:37

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#4 2016-02-16 14:43:50

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#5 2016-02-16 20:04:01

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#6 2016-02-17 01:36:54

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#7 2016-02-17 01:45:07

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#8 2016-02-17 05:22:58

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#9 2016-02-17 06:20:47

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#10 2016-02-18 01:42:14

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#11 2016-02-18 01:50:41

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

#12 2016-02-18 02:17:06

Re: (Solved) Using BL netinstall script in XFCE Debian jessie system

Board footer