[OUTDATED]Please help us test the Helium beta ISO

vinzv · 2018-04-13 10:11:19

artux wrote:

For now I have not tried other themes, but apparently the Raleigh theme has some problems.

Not really, it's just a Gtk2-only theme. So every Gtk3 application will look broken, obviously.
If you really need Raleigh there are some efforts on porting it to Gtk3 you could try: https://github.com/vlastavesely/raleigh-reloaded

mrneilypops · 2018-04-13 15:39:49

Helium beta 3 installed.
Sources updated as above.
nvida drivers installed and configured.
Grub install fine on my triple boot machine.
Running very nice thus far...keep up the great work!

Last edited by mrneilypops (2018-04-13 15:42:46)

artux · 2018-04-13 22:11:54

vinzv wrote:

Not really, it's just a Gtk2-only theme. So every Gtk3 application will look broken, obviously.
If you really need Raleigh there are some efforts on porting it to Gtk3 you could try: https://github.com/vlastavesely/raleigh-reloaded

Thanks, with your explanation I understood the cause of the malfunction.
My curiosity: why propose themes based on Gtk2, even knowing that the Gtk3 applications would not work well?
But this is not a problem for me: I chose Raleigh just because I liked it, but I also like the theme you use (Bunsen-He).
(I also tried Beam - the default theme - and it works fine too, I guess because it's based on Gtk3).

Thank you all.

vinzv · 2018-04-13 22:21:24

artux wrote:

My curiosity: why propose themes based on Gtk2, even knowing that the Gtk3 applications would not work well?

Raleigh is part of the package libgtk2.0-common, a core package of Gtk2. So to rip it out BL devs would have to rebuild a very crucial package from Debian and keep maintaining it.
Furthermore it makes sense to have such a theme available even if they do not work 100% right, just in case to have some simple fallback solution.

artux · 2018-04-14 17:00:42

Thanks vinzv, I understand.

citizen · 2018-04-15 14:16:43

Installed yesterday everything worked like a charm... congrats.

Do i need to install again when final version is out ?

Head_on_a_Stick · 2018-04-15 14:45:07

citizen wrote:

Do i need to install again when final version is out ?

No, it should be "good to go", the Debian packages are fixed now for the lifetime of the stretch release and any future BunsenLabs packages will be pushed out when ready rather than to a schedule.

We may tweak the user-level configuration[1] further though and these changes will only be applied automatically for any new users created after the configuration package has been updated — any existing users will have to merge the changes manually.

[1] By this I mean the general desktop configuration such as the openbox & tint2 themes, autostart items, conky[2] and suchlike.

[2] "Conky" is it's own plural, there are no "conkys" or "conkies"

Last edited by Head_on_a_Stick (2018-04-15 14:47:41)

alef · 2018-04-15 15:30:24

Hi,

I'm finally installing beta3 on one of my machines, no more just testing from a live USB. Feedback:

related to debian Stretch rather than bunsenLabs itself: the installer complained about wifi firmware not supported, and prompted me to load some non-free ucode firmware files in a removable drive. I ignored it, but right in the following step I could select wifi network, and connect to it.
in GRUB's main menu, there is a 'High Contrast Text option, below the list of distros. When I select this option, the screen's header and footer (grub version and instructions, respectively) are in white on dark grey background). The list of distros, however, is still in default colors

alef · 2018-04-15 17:20:46

One more remark:

While the current theme is very pleasing to the eye, the output of commands important for a developer, like `git diff` does not make it easy to spot the added lines. they are in blue, they do not stand out from the text around.

Here's what just happened to me, while maintaining a script I'm using to configure linux on my machines:

* moved text from one place in a script file to another line.
* did some other stuff for a few minutes
* ran `git diff` before running a commit
* output gave me the false impression that I had deleted these lines, I couldn't find them in the diff.

Red lines for deleted content are easy to spot, no problem there.

I'll fix this on my setup, but you might want to apply some updates in the default theme as well. Happy to send a pull request in case you're interested.

Head_on_a_Stick · 2018-04-15 18:27:57

alef wrote:

the installer complained about wifi firmware not supported, and prompted me to load some non-free ucode firmware files in a removable drive. I ignored it, but right in the following step I could select wifi network, and connect to it

How strange, does your wireless work in the installed system?

I will wager that you are using a Broadcom card, this will show if I'm right:

lspci -knn | grep -iA2 net

alef wrote:

in GRUB's main menu, there is a 'High Contrast Text option, below the list of distros. When I select this option, the screen's header and footer (grub version and instructions, respectively) are in white on dark grey background). The list of distros, however, is still in default colors

Yes, that is the expected behaviour — the grey background only comes into effect if the menuentry is edited by pressing "e".

alef wrote:

Happy to send a pull request in case you're interested.

Yes please, thanks for catching that.

Just out of interest, does the "Hydrogen" profile in terminator work with the `git diff` output?

I find the text more readable with that theme.

pamir · 2018-04-16 06:35:08

I have been running alpha 6 with no errors yet. Installed perfectly on ASUS laptop.

Not sure why but the last 2 versions of Bunsenlabs, `synclient` line present in ~/.config/openbox/autostart

does not always run. Tap to click and edge scrolling sometimes does not load, and has to be manually typed in, is there a workaround or can that be corrected?

hhh · 2018-04-16 18:30:50

artux wrote:

vinzv wrote:
Not really, it's just a Gtk2-only theme. So every Gtk3 application will look broken, obviously.
If you really need Raleigh there are some efforts on porting it to Gtk3 you could try: https://github.com/vlastavesely/raleigh-reloaded
Thanks, with your explanation I understood the cause of the malfunction.
My curiosity: why propose themes based on Gtk2, even knowing that the Gtk3 applications would not work well?

Raleigh is a legacy theme, it doesn't offer GTK3 support. Open /usr/share/themes/Raleigh and there's only a gtk-2.0 folder there. It's offered because it's offered in a default Debian install, which we try and stick to as much as possible. Sorry that it's a confusion.

Beam and the other default themes are based on Greybird (by shimmerproject), and they are GTK3 compatible (gtk-2.0 and gtk-3.0 themes are included).

alef · 2018-04-16 19:35:07

Head_on_a_Stick wrote:

How strange, does your wireless work in the installed system?

Yes, it works fine. Some forum online gave the advice to just ignore the error message, as in some cases it's a false negative.

$ lspci -knn | grep -iA2 net
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) I218-V [8086:15a3] (rev 03)
	Subsystem: Lenovo Device [17aa:2227]
	Kernel driver in use: e1000e
--
04:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095b] (rev 59)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5210]
	Kernel driver in use: iwlwifi

Head_on_a_Stick wrote:

Just out of interest, does the "Hydrogen" profile in terminator work with the `git diff` output?
I find the text more readable with that theme.

Yes, definitely.

altman · 2018-04-17 17:58:16

Doing great on my end on an old HP Pavilion dv7 Notebook.

Actually Helium on it & Hydrogen on an older Dell.

Edits:Mistakes

Last edited by altman (2018-04-18 10:56:24)

Doodle · 2018-04-22 00:48:00

Everything's great so far, though I noticed something when downloading deb files. If I open them right from my browser's downloads, every time I enter my password it fails. If I use the terminal or open gdebi-gtk as root and input my password then it works fine. Not sure what would cause that.

Head_on_a_Stick · 2018-04-22 10:42:34

Doodle wrote:

If I open them right from my browser's downloads, every time I enter my password it fails.

^ That's a protective feature — gdebi thunar has special permissions to run as root but the browser does not.

EDIT: s/gdebi/thunar/

Last edited by Head_on_a_Stick (2018-04-22 15:37:02)

DeepDayze · 2018-04-22 15:26:38

Head_on_a_Stick wrote:

Doodle wrote:
If I open them right from my browser's downloads, every time I enter my password it fails.
^ That's a protective feature — gdebi has special permissions to run as root but the browser does not.

That makes sense, as I used to be able to open debs from within the browser with gdebi and then get prompted for the admin password. Now it does not work that way any longer as I also now have to open the downloads folder and find the deb I downloaded then rightclick and select "Install with gdebi". Then it works as it asks for the password and only then goes ahead and installs the package. I can see this is a good (but irritating) change however as there are debs out there that harbor malicious code (especially if downloaded from sites outside of Debian's purview).

Head_on_a_Stick · 2018-04-22 15:42:56

^ Actually, I've just installed a .deb using firefox & gdebi and it worked fine so I'm wrong about that.

What are you folks actually doing?

I downloaded the .deb using firefox then opened a new tab and entered /home in the URL bar, navigated to Downloads, clicked on the .deb and chose "install with gdebi" and asked it to install the package, it threw up a password dialogue and then went ahead.

DeepDayze · 2018-04-22 15:48:48

Head_on_a_Stick wrote:

^ Actually, I've just installed a .deb using firefox & gdebi and it worked fine so I'm wrong about that.
What are you folks actually doing?
I downloaded the .deb using firefox then opened a new tab and entered /home in the URL bar, navigated to Downloads, clicked on the .deb and chose "install with gdebi" and asked it to install the package, it threw up a password dialogue and then went ahead.

I was attempting to install a deb directly from a site where I rightclicked the link to the deb then when I get the save menu I ensure I see open with gdebi. gdebi opens and when I clicked install i don't get prompted for the admin password and then gdebi closes. I did find the package was downloaded to temp folder and when I opened that in my file manager I rightclicked and selected install with gdebi. At that time it worked as expected by prompting for admin password and then proceeded to install the package.

Head_on_a_Stick · 2018-04-22 16:48:15

DeepDayze wrote:

I was attempting to install a deb directly from a site where I rightclicked the link to the deb then when I get the save menu I ensure I see open with gdebi

I don't see that option with the right-click context menu in firefox-esr, which browser are you using?

What was the site?

#81 2018-04-13 10:11:19

Re: [OUTDATED]Please help us test the Helium beta ISO

#82 2018-04-13 15:39:49

Re: [OUTDATED]Please help us test the Helium beta ISO

#83 2018-04-13 22:11:54

Re: [OUTDATED]Please help us test the Helium beta ISO

#84 2018-04-13 22:21:24

Re: [OUTDATED]Please help us test the Helium beta ISO

#85 2018-04-14 17:00:42

Re: [OUTDATED]Please help us test the Helium beta ISO

#86 2018-04-15 14:16:43

Re: [OUTDATED]Please help us test the Helium beta ISO

#87 2018-04-15 14:45:07

Re: [OUTDATED]Please help us test the Helium beta ISO

#88 2018-04-15 15:30:24

Re: [OUTDATED]Please help us test the Helium beta ISO

#89 2018-04-15 17:20:46

Re: [OUTDATED]Please help us test the Helium beta ISO

#90 2018-04-15 18:27:57

Re: [OUTDATED]Please help us test the Helium beta ISO

#91 2018-04-16 06:35:08

Re: [OUTDATED]Please help us test the Helium beta ISO

#92 2018-04-16 18:30:50

Re: [OUTDATED]Please help us test the Helium beta ISO

#93 2018-04-16 19:35:07

Re: [OUTDATED]Please help us test the Helium beta ISO

#94 2018-04-17 17:58:16

Re: [OUTDATED]Please help us test the Helium beta ISO

#95 2018-04-22 00:48:00

Re: [OUTDATED]Please help us test the Helium beta ISO

#96 2018-04-22 10:42:34

Re: [OUTDATED]Please help us test the Helium beta ISO

#97 2018-04-22 15:26:38

Re: [OUTDATED]Please help us test the Helium beta ISO

#98 2018-04-22 15:42:56

Re: [OUTDATED]Please help us test the Helium beta ISO

#99 2018-04-22 15:48:48

Re: [OUTDATED]Please help us test the Helium beta ISO

#100 2018-04-22 16:48:15

Re: [OUTDATED]Please help us test the Helium beta ISO

Board footer