Installing BunsenLabs Helium-dev

Head_on_a_Stick · 2017-11-22 22:08:17

Excellent, thanks for testing!

bigbenaugust · 2017-11-27 16:16:49

Did the pulseaudio config in dev change recently? I rebooted after a couple of weeks (maybe?) and now I have no audio. Did I miss a note a long the way, or do I need to just blow away my .config directory and catch up?

Head_on_a_Stick · 2017-11-27 19:36:21

Well, here's the latest (dev) version of the autostart file:

https://raw.githubusercontent.com/Bunse … /autostart

We have moved away from the custom bl-start-pulseaudio-x11 script, pnmixer doesn't need that tweak.

If your system used to have volumeicon then you may also have to delete ~/.config/autostart/pulseaudio.desktop to allow PA to start "naturally" again (ie, in the absence of our custom script).

bigbenaugust · 2017-11-27 19:51:10

Head_on_a_Stick wrote:

Well, here's the latest (dev) version of the autostart file:
https://raw.githubusercontent.com/Bunse … /autostart
We have moved away from the custom bl-start-pulseaudio-x11 script, pnmixer doesn't need that tweak.
If your system used to have volumeicon then you may also have to delete ~/.config/autostart/pulseaudio.desktop to allow PA to start "naturally" again (ie, in the absence of our custom script).

I did notice the bl-start-pulseaudio-x11 script wasn't there anymore.

The autostart on this machine (installed end of June-ish) has pnmixer instead of volumeicon.

Head_on_a_Stick · 2017-11-27 20:35:49

So is PA running?

pgrep pulseaudio >/dev/null 2>&1 && echo yup || echo nope

Last edited by Head_on_a_Stick (2017-11-27 20:38:25)

bigbenaugust · 2017-11-27 21:17:25

baugust@hatchibombotar:~$ ps aux | grep pulseaudio | grep -v grep
baugust   1655  0.0  0.0 1157708 13808 ?       S<l  Nov21   0:20 /usr/bin/pulseaudio --start --log-target=syslog

Oddly, it is. I thought pulse still had separate root and user sessions processes and assumed it was the root one. Yet that is my name on the process.

Head_on_a_Stick · 2017-11-27 21:22:40

Can we see

amixer

bigbenaugust · 2017-11-27 21:44:15

After an uncomfortable amount of audio troubleshooting in a cubicle environment, my headphone jack is muted and neither alsamixer, nor pavucontrol, nor the keyboard mute button is of any assistance. Weird.

Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 65536
  Mono:
  Front Left: Playback 23704 [36%] [on]
  Front Right: Playback 23704 [36%] [on]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch cswitch-joined
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 65536
  Front Left: Capture 10190 [16%] [on]
  Front Right: Capture 10190 [16%] [on]

Head_on_a_Stick · 2017-11-27 21:48:47

Do you have a "live" ISO image available?

Hardware failure is always a possibility

bigbenaugust · 2017-11-27 22:00:23

Two sets of headphones and two cables later, it would have to be the jack that crapped out...

bigbenaugust · 2017-11-27 22:10:11

bigbenaugust wrote:

Two sets of headphones and two cables later, it would have to be the jack that crapped out...

Updated and rebooted. Everything works now.

bigbenaugust · 2017-11-28 14:28:26

Soo... sorry for wasting the collective's time. ;P

Head_on_a_Stick · 2017-11-28 17:22:27

^ No worries, glad you got to the bottom of it

johnraff · 2017-11-29 02:01:41

Head_on_a_Stick wrote:

We have moved away from the custom bl-start-pulseaudio-x11 script, pnmixer doesn't need that tweak.
If your system used to have volumeicon then you may also have to delete ~/.config/autostart/pulseaudio.desktop to allow PA to start "naturally" again (ie, in the absence of our custom script).

Good catch! Come to think of it, I'm surprised we haven't had more people reporting no sound after that bunsen-configs upgrade. I'll put a note in "helium-dev notes" to delete that file. I suppose 'bl-user-setup --refresh' could have a '--purge' option to actually delete any user files not present in skel, and make $HOME a clone of skel. A bit fierce maybe? Only for devs and very recent installs.

bigbenaugust · 2017-11-29 14:31:24

You might call it --reinit instead of --refresh...

bigbenaugust · 2017-11-29 17:33:39

I just ran it and re-added the couple of customizations I had. Looks great.

Head_on_a_Stick · 2017-11-30 07:25:05

johnraff wrote:

I suppose 'bl-user-setup --refresh' could have a '--purge' option to actually delete any user files not present in skel, and make $HOME a clone of skel. A bit fierce maybe? Only for devs and very recent installs.

Well, we could try the standard Debian dialog that asks about "Maintainer Scripts" but it is particularly inscrutable and I never know what to do when it asks

Alternatively, Arch & Alpine place .new files in the folder if the original configuration file has been changed and expect the user to diff and merge them.

Another option is OpenBSD's sysmerge(8) utility that compares the files for the user:

https://gist.githubusercontent.com/Head … 1/sysmerge

EDIT: we'll need mksh (or ksh93) in the base system for that though

Last edited by Head_on_a_Stick (2017-11-30 07:26:15)

bigbenaugust · 2017-11-30 14:52:36

Is there any particular reason why tint2 is exactly 1 pixel down from the top of the screen?

Head_on_a_Stick · 2017-11-30 16:33:50

^ Yes, we set the Openbox desktop to leave a clear margin at the top of the screen to allow use of the right-click menu even if an application is full-screened.

Edit rc.xml to change it (look for the <margins></margins> bit):

https://github.com/BunsenLabs/bunsen-co … c.xml#L167

I think it is actually a vestige from our #! days — tint2 is configured to allow the openbox menu to show when right-clicked on so it doesn't seem to be needed at all really (IMO).

bigbenaugust · 2017-11-30 16:36:50

Head_on_a_Stick wrote:

^ Yes, we set the Openbox desktop to leave a clear margin at the top of the screen to allow use of the right-click menu even if an application is full-screened.
Edit rc.xml to change it (look for the <margins></margins> bit):
https://github.com/BunsenLabs/bunsen-co … c.xml#L167
I think it is actually a vestige from our #! days — tint2 is configured to allow the openbox menu to show when right-clicked on so it doesn't seem to be needed at all really (IMO).

Oh, I did fix it... I have this habit of switching desktops using the top of the panel and it was getting annoying.

#141 2017-11-22 22:08:17

Re: Installing BunsenLabs Helium-dev

#142 2017-11-27 16:16:49

Re: Installing BunsenLabs Helium-dev

#143 2017-11-27 19:36:21

Re: Installing BunsenLabs Helium-dev

#144 2017-11-27 19:51:10

Re: Installing BunsenLabs Helium-dev

#145 2017-11-27 20:35:49

Re: Installing BunsenLabs Helium-dev

#146 2017-11-27 21:17:25

Re: Installing BunsenLabs Helium-dev

#147 2017-11-27 21:22:40

Re: Installing BunsenLabs Helium-dev

#148 2017-11-27 21:44:15

Re: Installing BunsenLabs Helium-dev

#149 2017-11-27 21:48:47

Re: Installing BunsenLabs Helium-dev

#150 2017-11-27 22:00:23

Re: Installing BunsenLabs Helium-dev

#151 2017-11-27 22:10:11

Re: Installing BunsenLabs Helium-dev

#152 2017-11-28 14:28:26

Re: Installing BunsenLabs Helium-dev

#153 2017-11-28 17:22:27

Re: Installing BunsenLabs Helium-dev

#154 2017-11-29 02:01:41

Re: Installing BunsenLabs Helium-dev

#155 2017-11-29 14:31:24

Re: Installing BunsenLabs Helium-dev

#156 2017-11-29 17:33:39

Re: Installing BunsenLabs Helium-dev

#157 2017-11-30 07:25:05

Re: Installing BunsenLabs Helium-dev

#158 2017-11-30 14:52:36

Re: Installing BunsenLabs Helium-dev

#159 2017-11-30 16:33:50

Re: Installing BunsenLabs Helium-dev

#160 2017-11-30 16:36:50

Re: Installing BunsenLabs Helium-dev

Board footer