RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

Sector11 · 2015-07-20 16:25:45

damo wrote:

Calm down chaps, we've had enough unpleasantness recently

Agreed ... been a roller coaster lately.

hhh · 2015-07-20 17:37:44

It's just that he's had nothing to contribute from his first post on. Who has time for that?

exidux wrote:

It does not read as if this has any plan or purpose beyond wanting to attract a select user base of Crunchbang refugees.

Fine, none of this for you...

64 bit live session, Bunsen-Blackish themes, fdpowermon applet

Head_on_a_Stick · 2015-07-20 19:02:45

Sector11 wrote:

Bunsen - like most other Linux distros comes with "iptables" installed and set to a comfortable default.

Which is to say: no settings at all.

Check with:

sudo iptables -nvL --line-numbers

I usually have no rules set on my Arch system so this gives:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination

I have a simple stateful firewall [1] that gives:

empty@Arch ~ % sudo iptables -nvL --line-numbers     
Chain INPUT (policy DROP 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         
1        0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
2        0     0 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0           
3        0     0 DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0            ctstate INVALID
4        0     0 UDP        udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ctstate NEW
5        0     0 TCP        tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x17/0x02 ctstate NEW
6        0     0            icmp --  *      *       0.0.0.0/0            0.0.0.0/0            icmptype 8 recent: SET name: ping_limiter side: source mask: 255.255.255.255
7        0     0 DROP       icmp --  *      *       0.0.0.0/0            0.0.0.0/0            icmptype 8 recent: UPDATE seconds: 4 hit_count: 6 name: ping_limiter side: source mask: 255.255.255.255
8        0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0            icmptype 8
9        0     0 REJECT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            recent: SET name: TCP-PORTSCAN side: source mask: 255.255.255.255 reject-with tcp-reset
10       0     0 REJECT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0            recent: SET name: UDP-PORTSCAN side: source mask: 255.255.255.255 reject-with icmp-port-unreachable
11       0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            reject-with icmp-proto-unreachable

Chain FORWARD (policy DROP 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         

Chain TCP (1 references)
num   pkts bytes target     prot opt in     out     source               destination         
1        0     0 REJECT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            recent: UPDATE seconds: 60 name: TCP-PORTSCAN side: source mask: 255.255.255.255 reject-with tcp-reset

Chain UDP (1 references)
num   pkts bytes target     prot opt in     out     source               destination         
1        0     0 REJECT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0            recent: UPDATE seconds: 60 name: UDP-PORTSCAN side: source mask: 255.255.255.255 reject-with icmp-port-unreachable

But this really is totally pointless and I don't use it at all.

As I mentioned in my reply to @exidux. gufw is a fantastic GUI front end for ufw that can be used by people who like needless bloat on their systems (and by those who actually do need a firewall).

[1] https://wiki.archlinux.org/index.php/Si … l_firewall

Sector11 · 2015-07-20 19:49:18

8)

 20 Jul 15 | 16:37:21 ~
    $ sudo iptables -nvL --line-numbers
[sudo] password for sector11: 
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination         
 
 20 Jul 15 | 16:37:30 ~
    $

OK, then If I've *never in my Linux history* changed the iptables - although I looked at 'firestarter' (?) in my Ubuntu days but felt like a maze-challanged rat in a maze, so just left it all these years - I'm guessing I "don't need one" as you put it. ?¿?

@hhh - that looks sweet!

Head_on_a_Stick · 2015-07-20 20:06:52

Sector11 wrote:

I'm guessing I "don't need one" as you put it. ?¿?

Yes.

You have never had a firewall on your system.

As I said, they are only needed if you have any listening services and you have to set up such services yourself...

Sector11 · 2015-07-20 20:31:35

YOU HEAR THAT NORTON AND M$

hhh · 2015-07-20 21:29:33

Someone created #bunsenlabs on twitter, it has some cool links.
https://twitter.com/hashtag/bunsenlabs

Here's one to a nice review of the features and flaws of the alpha1 live ISO...
https://www.youtube.com/watch?v=8-G_g1I2h3c

Last edited by hhh (2015-07-20 21:29:58)

vlax · 2015-07-20 21:59:54

by curiosity, is this version of BL using systemd?

hhh · 2015-07-20 22:02:48

Yes, we're staying with Debian defaults. To use sysvinit...

sudo apt-get install sysvinit-core systemd-shim systemd-sysv-

Source...
https://wiki.debian.org/FAQsFromDebianUser#systemd

damo · 2015-07-20 22:08:50

Nice supportive review.

I'm relieved that the main menu gets a thumbs-up! O:)

Sector11 · 2015-07-20 22:21:22

hhh wrote:

Someone created #bunsenlabs on twitter, it has some cool links.
https://twitter.com/hashtag/bunsenlabs
Here's one to a nice review of the features and flaws of the alpha1 live ISO...
https://www.youtube.com/watch?v=8-G_g1I2h3c

Really nice reviews .. we're on the right track.

vlax · 2015-07-20 22:36:58

thnx

hhh wrote:

Yes, we're staying with Debian defaults. To use sysvinit...
sudo apt-get install sysvinit-core systemd-shim systemd-sysv-
Source...
https://wiki.debian.org/FAQsFromDebianUser#systemd

hhh · 2015-07-20 23:11:09

Here's a test... compare these builds to the nonfree LXDE live builds...
http://cdimage.debian.org/cdimage/unoff … rent-live/

Since we're using torrents and with the help of our excellent seeders (thank you!), the 64 bit BL iso downloaded for me in 20 minutes, 30 minutes for 32 bit. Debian's live torrent links are all dummies at the moment, so it was almost 5 hours of leaving a browser open and hoping wifi didn't drop before I had the Debian LXDE 64 bit Live ISO.

That ISO is 1.2 G, ours is currently ~680MB for 64 bit.

Booting the LXDE ISO, RAM usage is great, but there's no touchpad configuration, no notifications, no compositing, theming is very limited, no conky, no gparted. The Hydrogen ISO is way more usable in it's live session.

corenominal's week-old reply to my PM about the Live ISO release and all the developments...

corenominal wrote:

Blimey, nice work, it looks awesome. You guys rock!

Last edited by hhh (2015-07-20 23:27:50)

hhh · 2015-07-20 23:42:44

LXDE Live, pic or it didn't happen.

Tim70 · 2015-07-20 23:59:27

hhh wrote:

LXDE Live, pic or it didn't happen.
http://i.imgur.com/cxFggdCm.png

It reminds me of Windows Vista for some reason.

exidux · 2015-07-21 02:57:46

hhh wrote:

exidux wrote:
With an attitude like that...
Ass-face, you ain't seen nothin' yet. I don't want to hear whinging and FUD from someone who hasn't booted the ISO???!? Shocker!!!!!
Eat some cookies and shut up.

I do not know if you realize it, but that answer is so childish that it might as well be retarded... ass-face ? eat cookies ? FUD ? Shocker ?

I was interested in what you where doing so i asked a simple question and noted something about some possible extra default security. You permanently lost a user, and a possible tester. Have a nice day sir.

KrunchTime · 2015-07-21 04:51:58

exidux wrote:

So it remains a leap of faith like with all new or small less known distribtions.

CrunchBang was once new and small and required a leap of faith. I took that leap and am glad I did.

smacz · 2015-07-21 10:19:19

My good buddy and I used to hang around a 24hour coffee shop that attracted a lot of riff raff. His most oft-used phrase was

Don't feed the racoons.

Bringing it back to the alpha release, I took some time to install it and just had some questions about the setup.

First of all, there were some "failed to execute child process" errors on the root menu for:

catfish
gftp
hexchat
gnumeric
gigolo
gcalculator

Those are fixed by downloading the respective packages, so I'll assume that those will probably just be added to the next .iso or abandoned from the root menu.

The one that had me scratching my head (the most) was the lack of a bl-media-player in the root menu. I mean, it's like the fifth sixth option down. It too, returned a "failed to execute child process" error. So I decided to investigate.

I pulled up (root menu again) "System" --> "Edit Default Applications", entered in my root passwd, and...nothing. This concerned me.

I figured out that 'galternatives' wasn't installed. It was only an apt-get away, so I pulled that down and gave it another run. After entering in my root passwd this time, I pulled up the GUI to see that there indeed was no bl-media-player entry. Ok, so I hit the [NEW] button (image of a blank sheet of paper under 'File'), and...nothing. Really?

So I searched around a little and found that galternatives is likely orphaned? But regardless, there's a thread in the Ubuntu forums describing the same problems. Following the rabbithole there's a claim that the issue was fixed in 0.13.5+nmu3.

# apt-cache policy galternatives
galternatives:
  Installed: 0.13.5+nmu3
  Candidate: 0.13.5+nmu3
...

So that's a question for upstream. And if someone wants to confirm the same issues then I'll submit a bug report.

However, back to the issue at hand: (TL;DR - MPV via the Root Menu is borked -- you can now skip to the last few paragraphs)

Via the CLI using 'update-alternatives', I created bl-media-player, and linked it to the only media player that was installed, a.k.a mpv.

Now, when mpv is ran without any arguments, switches, or flags from the CLI, all it does is output it's "help/basic options" text. So naturally running that from the root menu (via the "Media Player" entry) doesn't really do anything. @damo knows this.

In his change to bl-alternatives commit, he puts in the if-elif statement under bl-multimedia pipemenu:

elif [[ "$curApp" = "mpv" ]];then # set mpv to start with gui window
-	menuItem "$curAppName" "$curApp --force-window --idle"

I've never used mpv without any file specified, so I decided to give it a try. Turns out there is absolutely nothing you can do with mpv in that state. There is no way to specify a file, to give it any kind of input. In that use case, there is no valid reason to start it like that. Granted, if the media is, say, selected from thunar -- in that case mpv works perfectly. But I'm not talking about that.

So I guess that brings me to my question: what can be done to make the sixth entry down in the root menu usable?

If mpv is to be the default media player, then it might be better to define in the pipemenu entries that it is to spawn a new terminal and run in there. That would output the command options, and the user can then manipulate the program from the command line.

Or the program could test to see if it was mpv being called by bl-media-player, and popup with a warning letting the user know to use it from the command line. At that point though, why even have the menu entry in the first place?

Otherwise, I would suggest replacing it (at least in the root menu) with a more fitting program, such as SMPlayer or VLC. Those both have valid GUI interfaces[1] for the use case that I am describing.

Of course there may be other ways to work around the problem that I'm not savvy enough to think of, and this is most probably an executive-level decision to be made, but I certainly wanted to bring it to the attention of the devs. My apologies if there is already a discussion regarding this, but I was unable to find one.

*Deep breath* Now that I got that off my chest, who's the one responsible for adding the "Thank you" after you input the sudo password for the bl-welcome script? That absolutely made my day.

[1] I know, I know...it's like saying ATM machine, but it made more sense reading it that way than it did without the redundancy.

hhh · 2015-07-21 13:09:33

smacz wrote:

catfish
gftp
hexchat
gnumeric
gigolo
gcalculator
Those are fixed by downloading the respective packages, so I'll assume that those will probably just be added to the next .iso or abandoned from the root menu.

Right now the plan is to add them back, along with geany, vlc, etc...

what can be done to make the sixth entry down in the root menu usable?

VLC will be set as bl-media-player.

Thanks very much for the feedback!

damo · 2015-07-21 15:31:03

@smacz

The issue with Media Player is due to "bl-media-player" rather than the mpv command, I think. Running this command via menu, dmenu or terminal gets me a window saying "Drop files to play here"

mpv  --force-window --idle

I'll raise an issue on github about bl-media-player though.

mpv is there because of previous requests for a lightweight media player, but @hhh reckons it will be VLC, and I can live with that

hhh · 2015-07-21 15:42:23

damo wrote:

mpv is there because of previous requests for a lightweight media player, but @hhh reckons it will be VLC, and I can live with that

It's actually there because @johnraff and I agreed it would be a good idea to strip down the first ISO builds, both to see what packages were necessary to get a working desktop and to avoid dependency issues with the early builds. Hence also leafpad instead of geany as both vlc and geany pull in a lot of dependencies. As a result, we've discovered that a CD sized ISO is possible, but the plan is for the next release to be more feature-complete, as #! was.

smacz · 2015-07-21 21:03:52

damo wrote:

Running this command via menu, dmenu or terminal gets me a window saying "Drop files to play here"
mpv  --force-window --idle

I don't return any prompt like that, through any of those launch options.

hhh wrote:

Right now the plan is to add them back, along with geany, vlc, etc...

Sounds good to me!

Last edited by smacz (2015-07-21 21:05:04)

Tim70 · 2015-07-21 21:38:11

Just wondering, when is the expected time for the next release, or is there a release schedule that I have not noticed?

brontosaurusrex · 2015-07-21 22:14:07

Some pretty nice makeups popping out
http://entornosgnulinux.com/2015/07/04/ … me-evopop/

smacz · 2015-07-21 22:34:57

@Tim70 Basically it'll be out when it's ready. The community here wants to thouroughly vet anything that is to be released before it's put out into the wild. So no, there's no real timeframe.

Last edited by smacz (2015-07-21 22:35:29)

CrunchBang Linux

SEARCH

#126 2015-07-20 16:25:45

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#127 2015-07-20 17:37:44

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#128 2015-07-20 19:02:45

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#129 2015-07-20 19:49:18

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#130 2015-07-20 20:06:52

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#131 2015-07-20 20:31:35

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

YOU HEAR THAT NORTON AND M$

#132 2015-07-20 21:29:33

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#133 2015-07-20 21:59:54

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#134 2015-07-20 22:02:48

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#135 2015-07-20 22:08:50

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#136 2015-07-20 22:21:22

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#137 2015-07-20 22:36:58

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#138 2015-07-20 23:11:09

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#139 2015-07-20 23:42:44

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#140 2015-07-20 23:59:27

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#141 2015-07-21 02:57:46

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#142 2015-07-21 04:51:58

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#143 2015-07-21 10:19:19

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#144 2015-07-21 13:09:33

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#145 2015-07-21 15:31:03

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#146 2015-07-21 15:42:23

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#147 2015-07-21 21:03:52

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#148 2015-07-21 21:38:11

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#149 2015-07-21 22:14:07

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

#150 2015-07-21 22:34:57

Re: RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2)

Board footer