You are not logged in.

#1 2019-12-10 03:35:43

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 6,194
Website

Testing Lithium iso discussion

A testing isofile for BL Lithium is now available, announcement here.

If any community members have the time and hardware to install BL Lithium from this, then any feedback and bug reports will be very welcome! smile

Comments are welcome on this thread, but bug reports, especially if likely to need discussion, are better in their own thread in the Bug Reports section.

Thank you for your patience!

NB: The BL backports repository and bunsen-images-extra package are not yet available, so attempts to enable them from 'bl-welcome' will fail. m(._.)m

Last edited by johnraff (2019-12-11 02:09:11)


John

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Offline

#2 2019-12-10 12:04:06

damo
....moderator....
Registered: 2015-08-20
Posts: 5,419

Re: Testing Lithium iso discussion

Coming to you from a new bare-metal install (after finally managed to install by disabling Hybrid graphics on this laptop)

Skylake
Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] 
Using nouveau

The bl-welcome update has a problem with some repos though, because the packages haven't been finalized and built yet.

ERROR MESSAGE:
E: The repository 'https://pkg.bunsenlabs.org/debian buster-backports Release' does not have a Release file.

ERROR MESSAGE:
E: Package 'bunsen-images-extra' has no installation candidate

hardinfo throws some gtk gui errors, and doesn't load until a blank popup is closed.

I like that the root theme uses a mono font - nice and distinctive. There is a glitch though - the root prompt needs some love sad

damo@lithium-dev:~$ cd /tmp
damo@lithium-dev:/tmp$

root@lithium-dev:/etc/apt/sources.list.d# 

But easily fixed by bringing in my personal .bashrc's.

Apart from that, all looks sweet so far smile

Now to dig out my nvidia notes and do battle with hybrid graphics, kernel parameters and optimus!


Be Excellent to Each Other...

FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#3 2019-12-10 13:02:02

iMBeCil
WAAAT?
From: Edrychwch o'ch cwmpas
Registered: 2015-09-29
Posts: 692

Re: Testing Lithium iso discussion

Tried install in VirtualBox, everything went smoothly, except what damo also notices about missing 'Release file':

$ sudo apt update
[sudo] password for someuser: 
Hit:1 https://kelaino.bunsenlabs.org/~johnraff/debian lithium InRelease
Hit:3 https://deb.debian.org/debian buster InRelease                           
Hit:4 https://deb.debian.org/debian-security buster/updates InRelease
Hit:5 https://deb.debian.org/debian buster-updates InRelease                  
Hit:6 https://deb.debian.org/debian buster-backports InRelease                
Ign:2 https://eu.pkg.bunsenlabs.org/debian buster-backports InRelease        
Err:7 https://eu.pkg.bunsenlabs.org/debian buster-backports Release
  404  Not Found [IP: 78.47.156.207 443]
Reading package lists... Done
E: The repository 'https://pkg.bunsenlabs.org/debian buster-backports Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

EDIT1:
Effectively, if backports are enabled then bl-welcome ends with error.

EDIT2:
Conclusion: at this time, install goes OK, except:
- do not select backports (neither one) in bl-welcome (no 'Release file')
- do not select bunsen-images-extra in bl-welcome (package doesn't exist)
(I selected all other options in bl-welcome, i.e. answered 'Y' everywhere. And 'F' for AdobeFlash.)

EDIT3:
Cannot install full LibreOffice (via RightClick-System-Install SlecetedPackages). It seems bl-meta-libreoffice is not there yet:

$ sudo apt install bl-meta-libreoffice
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package bl-meta-libreoffice

(LibreOffice base installation works.)

I hope it will be easy to rectify those omissions smile

Last edited by iMBeCil (2019-12-10 14:02:24)


Postpone all your duties; if you die, you won't have to do them ..

Offline

#4 2019-12-10 13:41:02

iMBeCil
WAAAT?
From: Edrychwch o'ch cwmpas
Registered: 2015-09-29
Posts: 692

Re: Testing Lithium iso discussion

A note about 'vi(m)' editor in current install: there is a 'vi' command (editor), but no 'vim' command.
The command 'vi' starts vi-improved, i.e. the 'vi' really is 'vim'.

In debian installs (I checked several of them), there are always both 'vi' and 'vim' (pointing to the same vi-improved).
Do not change it if this is by design ...


Postpone all your duties; if you die, you won't have to do them ..

Offline

#5 2019-12-10 14:08:18

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 178

Re: Testing Lithium iso discussion

worked like a charm:

Machine:   Type: Laptop System: LENOVO product: 20ASS34900 v: ThinkPad L440
           Mobo: LENOVO model: 20ASS34900 v: SDK0E50519 UEFI [Legacy]: LENOVO v: J4ET79WW(1.79) date: 05/06/2015
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0
           chip ID: 8086:0416
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: compton resolution: 1368x768~60Hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.3.6 compat-v: 3.0 direct render: Yes
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
           bus ID: 00:03.0 chip ID: 8086:0c0c
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel
           bus ID: 00:1b.0 chip ID: 8086:8c20
           Sound Server: ALSA v: k4.19.0-6-amd64
Network:   Device-1: Intel Ethernet I217-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: 5080 bus ID: 00:19.0
           chip ID: 8086:153b
           IF: enp0s25 state: up speed: 100 Mbps duplex:
           Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 bus ID: 02:00.0 chip ID: 8086:08b2
           IF: wlp2s0 state: up

The installer loaded driver for wiffi but not for the "ThinkPad trackpad".

Love the colour theme. Now I don not need to change terminal colour the first I do... (can not stand transparent background in the terminal...)

Last edited by rbh (2019-12-10 15:34:25)


// Regards rbh

Offline

#6 2019-12-10 14:30:09

dmontaine
Member
Registered: 2017-02-14
Posts: 10

Re: Testing Lithium iso discussion

HP 15z
AMD Ryzen™ 5 processor
AMD Radeon™ Vega 8 Graphics
16 GB memory
512 GB PCIe® NVMe™ M.2 SSD

Mouse did not work during installation, installed using keyboard, fine after installation
Had to download the following firmware from the Debian repository:
firmware-iwlwifi_20190717-2_all.deb
firmware-realtek_20161130-5_all.deb

As noted by others, most optional items could not load during welcome script.

Most installation options on the menu,such as Libre Office complain about the Bunsen Labs repository not having a release file.

Last edited by dmontaine (2019-12-10 14:58:04)

Offline

#7 2019-12-10 19:09:43

unklar
Member
Registered: 2015-10-31
Posts: 992

Re: Testing Lithium iso discussion

Thanks, guys!

This is an absolute feast for my eyes. cool
After playing with the Live-iso this morning, I wanted to install it in QEMU after lunch. But it became the 2.HDD, because everything went so well.

inxi -Fzrx
System:    Host: francescoPC Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 
           Distro: BunsenLabs GNU/Linux 10.0 (Lithium) base: Debian GNU/Linux 10 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5Q-PRO v: Rev 1.xx serial: <filter> BIOS: American Megatrends v: 2102 
           date: 02/23/2009 
CPU:       Topology: Quad Core model: Intel Core2 Quad Q9400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 21330 
           Speed: 2000 MHz min/max: 2003/2670 MHz Core speeds (MHz): 1: 2000 2: 2002 3: 2002 4: 2000 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 
           vendor: PC Partner Limited driver: radeon v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 82801JI HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet vendor: ASUSTeK driver: ATL1E v: N/A 
           port: cc00 bus ID: 02:00.0 
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Techsan Co B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card driver: b2c2_flexcop_pci v: kernel 
           port: ec00 bus ID: 05:01.0 
Drives:    Local Storage: total: 465.77 GiB used: 10.24 GiB (2.2%) 
           ID-1: /dev/sda vendor: Seagate model: ST3250820AS size: 232.89 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WD2502ABYS-23B7A0 39M4511 42C0463IBM size: 232.89 GiB 
Partition: ID-1: / size: 9.79 GiB used: 3.25 GiB (33.2%) fs: ext4 dev: /dev/sdb8 
           ID-2: swap-1 size: 14.63 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A gpu: radeon temp: 50 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://deb.debian.org/debian buster main non-free contrib
           2: deb https://deb.debian.org/debian-security buster/updates main contrib non-free
           3: deb https://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian lithium main
Info:      Processes: 150 Uptime: 3h 14m Memory: 7.79 GiB used: 1.27 GiB (16.3%) Init: systemd runlevel: 5 Compilers: gcc: N/A 
           Shell: bash v: 5.0.3 inxi: 3.0.32 

After all, lithium will replace helium and GRUB will manage all my distributions again. I am very confident.

Your the best!   big_smile

Offline

#8 2019-12-10 19:13:49

Huldalumi
Member
From: Finland
Registered: 2019-05-15
Posts: 25

Re: Testing Lithium iso discussion

Esprimo mobile v5535
Intel celeron cpu1.86gz
Ram 8gb
Sis on board grahics
Hdd 80gb

Thanks for all the hard work guys well worth the wait.
Sis graphics
Wifi
Both working and now I can even access my phones memory card fantastic
The installation was trouble free as always.
Only one little thing when I ran gdebi the box changes colour to white
Also I really like the new look and the live menu.
Sorry gushing a bit but well done to the whole development team

Last edited by Huldalumi (2019-12-10 19:16:46)


yeah,well, thats just like, your opinion man
The Dude

Offline

#9 2019-12-10 19:17:47

damo
....moderator....
Registered: 2015-08-20
Posts: 5,419

Re: Testing Lithium iso discussion

Huldalumi wrote:

...
Only one little thing when I ran gdebi the box changes colour to white
...

Root apps need to have the theme set using root privileges,  which is a reason for having them set to a different theme so they are distinguishable.

Without a policykit file for pkexec, one way is to do

$ sudo -i
...
# obconf &
# lxappearance &
# exit

Be Excellent to Each Other...

FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#10 2019-12-10 19:46:05

Huldalumi
Member
From: Finland
Registered: 2019-05-15
Posts: 25

Re: Testing Lithium iso discussion

Thanks damo
I'll get that done tomorrow.


yeah,well, thats just like, your opinion man
The Dude

Offline

#11 2019-12-10 23:39:16

Dr.Strangelove
New Member
From: A movie from the early 60s
Registered: 2019-12-10
Posts: 1

Re: Testing Lithium iso discussion

This got me excited enough to register after some weeks of serious lurking.

Thank you so much, downloading now for an install on a Thinkpad T410.

Last edited by Dr.Strangelove (2019-12-10 23:44:48)


"Strangelove? What kind of a name is that? That ain't no Kraut name, is it, Stainesey?"
"He changed it when he became a citizen. Used to be Merkwuerdigeliebe."

Offline

#12 2019-12-11 03:31:34

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 6,194
Website

Re: Testing Lithium iso discussion

iMBeCil wrote:

do not select backports (neither one) in bl-welcome (no 'Release file')
- do not select bunsen-images-extra in bl-welcome (package doesn't exist)

Thanks - the announcement has been updated with that info, EXCEPT I think the Debian backports option already works OK.

It seems bl-meta-libreoffice is not there yet

...and never will be. The package name is bunsen-meta-libreoffice, and you've found a bug in the install pipemenu. ops Now fixed in the GitHub code, and a new package version will go out, maybe a bit later just in case there are some other bugs to fix.

A note about 'vi(m)' editor in current install: there is a 'vi' command (editor), but no 'vim' command.
The command 'vi' starts vi-improved, i.e. the 'vi' really is 'vim'.
In debian installs (I checked several of them), there are always both 'vi' and 'vim' (pointing to the same vi-improved).
Do not change it if this is by design ...

Actually, we do not ship vi-improved by default, and vi is a symlink to vim-tiny, as set by Debian. We have made no changes to the Debian setup, though, beyond choosing not to ship the full vim, which is no longer required in a minimal Debian install.

Anyway, thanks for the feedback!


John

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Offline

#13 2019-12-11 03:35:38

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 6,194
Website

Re: Testing Lithium iso discussion

Thanks everybody for the feedback, and please keep it coming! smile


John

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Offline

#14 2019-12-11 09:23:39

iMBeCil
WAAAT?
From: Edrychwch o'ch cwmpas
Registered: 2015-09-29
Posts: 692

Re: Testing Lithium iso discussion

^You're welcome, glad to be of help.


Postpone all your duties; if you die, you won't have to do them ..

Offline

#15 2019-12-11 14:17:25

unklar
Member
Registered: 2015-10-31
Posts: 992

Re: Testing Lithium iso discussion

I did the installation a second time (again from the stick).  wink
The reason was the confusing statements of the Debian Installer regarding an already existing swap partition.
Yesterday the default option "Install-GUI" , today the same in "expert mode"...

Although the installation was much faster today, I don't understand why the simple question "Do you want to use the existing swap or do you want to create a new swap" is still not used in the installer. Instead you have to click on "do not use swap". Until the installer has understood what you want.
After the first start the existing swap must always be added to the fstab.

Observation:
1) Yesterday the installation of keepassxc was displayed in the default theme.
Today the window is displayed in white.
I always install via the terminal via "sudo apt install keepassxc".
After a reboot the standard theme is also present here.

2) the default tint2 clock setting in the lower right corner showed yesterday (corresponding to %I:%M) the time 6:32 (PM), although it was 18:32 here. All other tint2 configurations showed the time correctly. The login screen also displays the time correctly.
My changes both in the GUI and in the configuration file to " %H:%M " show the time display unclean.
In the second installation it is clear.

=======================================
Current memory consumption (open: Terminal; FF; Thunar; keepassxc) with ps_mem

sudo ./ps_mem.py
 Private  +   Shared  =  RAM used	Program

200.0 KiB +  21.5 KiB = 221.5 KiB	sh
280.0 KiB +  30.5 KiB = 310.5 KiB	agetty
308.0 KiB +  66.5 KiB = 374.5 KiB	cron
420.0 KiB +  44.5 KiB = 464.5 KiB	xcape
472.0 KiB +  50.5 KiB = 522.5 KiB	dbus-launch
688.0 KiB +  17.5 KiB = 705.5 KiB	ssh-agent
612.0 KiB + 133.5 KiB = 745.5 KiB	xfconfd
736.0 KiB +  97.5 KiB = 833.5 KiB	dconf-service
808.0 KiB + 134.5 KiB = 942.5 KiB	gvfs-mtp-volume-monitor
812.0 KiB + 138.5 KiB = 950.5 KiB	gvfsd-metadata
956.0 KiB + 173.5 KiB =   1.1 MiB	at-spi2-registryd
  1.0 MiB + 120.5 KiB =   1.1 MiB	gvfs-goa-volume-monitor
  1.0 MiB + 233.5 KiB =   1.2 MiB	at-spi-bus-launcher
  1.1 MiB + 207.5 KiB =   1.3 MiB	sudo
  1.1 MiB + 273.5 KiB =   1.3 MiB	gvfsd
  1.2 MiB + 181.5 KiB =   1.3 MiB	ntpd
  1.2 MiB + 159.5 KiB =   1.4 MiB	gvfs-gphoto2-volume-monitor
  1.0 MiB + 526.5 KiB =   1.5 MiB	alsactl
  1.3 MiB + 306.5 KiB =   1.6 MiB	gvfsd-dnssd
  1.4 MiB + 380.5 KiB =   1.8 MiB	gvfsd-network
  1.5 MiB + 415.5 KiB =   1.9 MiB	gvfsd-trash
  1.3 MiB + 779.5 KiB =   2.0 MiB	systemd-logind
  2.0 MiB +  68.5 KiB =   2.1 MiB	smartd
  1.6 MiB + 612.5 KiB =   2.2 MiB	upowerd
  2.1 MiB +  80.5 KiB =   2.2 MiB	rsyslogd
  2.3 MiB +  74.5 KiB =   2.4 MiB	bash
  2.4 MiB + 194.5 KiB =   2.6 MiB	systemd-udevd
  2.6 MiB + 185.5 KiB =   2.8 MiB	wpa_supplicant
  2.6 MiB + 294.5 KiB =   2.9 MiB	polkitd
  2.4 MiB + 564.5 KiB =   2.9 MiB	dbus-daemon (3)
  3.2 MiB +  21.5 KiB =   3.2 MiB	haveged
  2.6 MiB + 704.5 KiB =   3.3 MiB	gvfs-udisks2-volume-monitor
  3.3 MiB +  69.5 KiB =   3.4 MiB	xbindkeys
  3.3 MiB + 188.5 KiB =   3.5 MiB	gvfsd-fuse
  3.3 MiB + 273.5 KiB =   3.6 MiB	dhclient
  3.2 MiB + 490.5 KiB =   3.7 MiB	gvfs-afc-volume-monitor
  3.1 MiB + 740.5 KiB =   3.8 MiB	systemd-journald
  4.3 MiB + 332.5 KiB =   4.6 MiB	ModemManager
  4.3 MiB + 338.5 KiB =   4.7 MiB	gnome-keyring-daemon
  4.8 MiB + 426.5 KiB =   5.2 MiB	compton
  4.6 MiB + 643.5 KiB =   5.2 MiB	udisksd
  4.6 MiB + 643.5 KiB =   5.2 MiB	jgmenu
  4.6 MiB + 788.0 KiB =   5.4 MiB	lightdm (2)
  4.6 MiB + 940.5 KiB =   5.5 MiB	tint2
  5.8 MiB +   1.3 MiB =   7.1 MiB	NetworkManager
  3.9 MiB +   4.2 MiB =   8.1 MiB	systemd (3)
  7.8 MiB + 528.5 KiB =   8.3 MiB	conky
  8.3 MiB +   1.1 MiB =   9.4 MiB	light-locker
 10.2 MiB + 956.5 KiB =  11.1 MiB	openbox
 10.2 MiB +   1.2 MiB =  11.4 MiB	tumblerd
 10.7 MiB +   2.6 MiB =  13.3 MiB	pulseaudio
 33.2 MiB +   1.6 MiB =  34.8 MiB	xfce4-power-manager
 33.1 MiB +   1.8 MiB =  34.8 MiB	clipit
 33.2 MiB +   1.8 MiB =  35.0 MiB	xfce4-notifyd
 33.4 MiB +   2.2 MiB =  35.6 MiB	pnmixer
 33.7 MiB +   2.0 MiB =  35.7 MiB	polkit-gnome-authentication-agent-1
 34.5 MiB +   2.0 MiB =  36.5 MiB	x-terminal-emul
 39.0 MiB +   3.7 MiB =  42.6 MiB	thunar
 32.0 MiB +  22.9 MiB =  54.9 MiB	Xorg
 60.7 MiB +   2.3 MiB =  63.1 MiB	nm-applet
 54.1 MiB +  10.9 MiB =  65.0 MiB	keepassxc
200.5 MiB +  38.6 MiB = 239.2 MiB	x-www-browser
216.2 MiB +  73.7 MiB = 290.0 MiB	firefox-esr (5)
---------------------------------
                          1.1 GiB
=================================

Offline

#16 2019-12-11 19:24:11

Narmo
Bad Wolf
From: Poland
Registered: 2015-09-29
Posts: 53

Re: Testing Lithium iso discussion

Great job guys, everything works so far like a charm (except already mentioned and explained repo issues tongue).

System:    Host: wolf Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 
           Distro: BunsenLabs GNU/Linux 10.0 (Lithium) base: Debian GNU/Linux 10 
Machine:   Type: Desktop Mobo: ASRock model: H81M-DG4 serial: <filter> BIOS: American Megatrends v: P1.00 date: 10/31/2014 
CPU:       Topology: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP arch: Haswell rev: 3 L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25592 
           Speed: 900 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: Micro-Star MSI driver: nouveau v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: NV117 v: 4.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Device-2: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: d000 
           bus ID: 03:00.0 
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.64 TiB used: 1012.14 GiB (27.2%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-00BN5A0 size: 931.51 GiB 
           ID-2: /dev/sdb type: USB vendor: Seagate model: Expansion Desk size: 2.73 TiB 
Partition: ID-1: / size: 27.37 GiB used: 3.40 GiB (12.4%) fs: ext4 dev: /dev/sda6 
           ID-2: /home size: 420.18 GiB used: 197.4 MiB (0.0%) fs: ext4 dev: /dev/sda7 
           ID-3: swap-1 size: 9.31 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 23.0 C mobo: N/A gpu: nouveau temp: 28 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://deb.debian.org/debian buster main non-free contrib
           2: deb https://deb.debian.org/debian-security buster/updates main contrib non-free
           3: deb https://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen-buster-backports.list 
           1: deb https://pkg.bunsenlabs.org/debian buster-backports main
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian lithium main
           Active apt repos in: /etc/apt/sources.list.d/debian-buster-backports.list 
           1: deb https://deb.debian.org/debian buster-backports main contrib non-free
Info:      Processes: 160 Uptime: 44m Memory: 7.73 GiB used: 2.18 GiB (28.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A 
           Shell: bash v: 5.0.3 inxi: 3.0.32

Offline

#17 2019-12-11 21:12:51

iMBeCil
WAAAT?
From: Edrychwch o'ch cwmpas
Registered: 2015-09-29
Posts: 692

Re: Testing Lithium iso discussion

I don't know if this deserves separate thread, but I stumbled(!) on these (I put '#' at the beginning of lines which seem wrong):

$ man bl-xdg-autostart
BL-XDG-AUTOSTART(1)              User Commands             BL-XDG-AUTOSTART(1)

NAME
       bl-xdg-autostart - a script provided by bunsen-configs

DESCRIPTION
#       /usr/bin/env: 'python': No such file or directory

AUTHORS
       Written by the BunsenLabs team.
... [cut]

and

$ man bl-xbk
BL-XBK(1)                        User Commands                       BL-XBK(1)

NAME
       bl-xbk - a script to parse xbindkeys keybindings

DESCRIPTION
#       mkdir:  cannot  create directory '~': Permission denied bl-xbk a script
#       to parse xbindkeys keybindings

       Usage: bl-xbk [--xbindkeys-rc <file>] [--kbinds-text <file>]

       Parse xbindkeys config file and output the formatted result to  a  text
       file.

   Optional arguments:
       -h|--help
              show this help message and exit

... [cut]

A few other 'man bl-something-something' worked OK.

Is this some sort of bug during creation of the bl-something-something packages?

(Note: fresh install, on bare metal HPCompaq 6720s, bl-welcome successfully executed.)

EDIT:
Also affected:
- bl-install
- bl-kb
- bl-notify-broadcast
- bl-recent-files-pipemenu
- bl-setlocale
- bl-sshconfig-pipemenu
- bl-user-setup
- bl-xinerama-prop

Last edited by iMBeCil (2019-12-11 21:27:23)


Postpone all your duties; if you die, you won't have to do them ..

Offline

#18 2019-12-11 22:03:25

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 178

Re: Testing Lithium iso discussion

unklar wrote:

I did the installation a second time (again from the stick).  wink
I don't understand why the simple question "Do you want to use the existing swap or do you want to create a new swap" is still not used in the installer.

That is how Debian Installer works. You can ask the Debian Installer Team to implement that. Contactinfo on https://wiki.debian.org/DebianInstaller/Team.
Rewrite the installer, is quite a heavy work I suppose...

unklar wrote:

2) the default tint2 clock setting in the lower right corner showed yesterday (corresponding to %I:%M) the time 6:32 (PM), although it was 18:32 here. All other tint2 configurations showed the time correctly. The login screen also displays the time correctly.

Default setting for clock on tint2, is 12 hour setting. 6:32 (PM) and 18:32, is the same time, expressed differently only.

unklar wrote:

My changes both in the GUI and in the configuration file to " %H:%M " show the time display unclean.
In the second installation it is clear.

I don't understand this. Is there some misstyping?
Did you spare $HOME forsecond installation?

Last edited by rbh (2019-12-11 22:23:20)


// Regards rbh

Offline

#19 2019-12-11 22:47:32

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 178

Re: Testing Lithium iso discussion

iMBeCil wrote:

$ man bl-xdg-autostart

...
DESCRIPTION
     /usr/bin/env: 'python': No such file or directory

I get that answer only when running it in root terminal...

When running as normal user, I only get answer that screensaver is running. Though ps -ef | grep saver or screnn, does not list it.


// Regards rbh

Offline

#20 2019-12-11 23:12:57

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 178

Re: Testing Lithium iso discussion

I get that answer only when running it in root terminal...
When running as normal user, I only get answer that screensaver is running. Though ps -ef | grep saver or screnn, does not list it.

Sorry tired and distracted. When I ran "bl-xdg-autostart", I got the answer about screesaver.


// Regards rbh

Offline

#21 2019-12-12 06:05:46

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 6,194
Website

Re: Testing Lithium iso discussion

iMBeCil wrote:

I don't know if this deserves separate thread, but I stumbled(!) on these (I put '#' at the beginning of lines which seem wrong):

$ man bl-xdg-autostart
BL-XDG-AUTOSTART(1)              User Commands             BL-XDG-AUTOSTART(1)

NAME
       bl-xdg-autostart - a script provided by bunsen-configs

DESCRIPTION
#       /usr/bin/env: 'python': No such file or directory
### etc

A few other 'man bl-something-something' worked OK.

Is this some sort of bug during creation of the bl-something-something packages?

Yes that's what it is. The man pages are auto-generated when the packages are built from source, and a couple of the python scripts throw errors because some necessary library is not available at build time. They should all (2 or 3?) be fixable by the time we do the official release. But thanks, and I'll make sure it's on the TODO list.

EDIT: just saw your list (thank you for checking!) and had no idea so many man pages were broken like that. yikes In some cases the scripts should be tweakable to output the --help message and exit before the missing library is called, in other cases, just add a package to the build-deps.

Last edited by johnraff (2019-12-12 06:21:06)


John

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Offline

#22 2019-12-12 10:23:23

unklar
Member
Registered: 2015-10-31
Posts: 992

Re: Testing Lithium iso discussion

rbh wrote:
unklar wrote:

My changes both in the GUI and in the configuration file to " %H:%M " show the time display unclean.
    In the second installation it is clear.

I don't understand this. Is there some misstyping?
Did you spare $HOME forsecond installation?

No
Both times were superimposed on each other  big_smile

Offline

#23 2019-12-12 20:13:01

PackRat
jgmenu user Numero Uno
Registered: 2015-10-02
Posts: 1,159

Re: Testing Lithium iso discussion

On the keybindings list in the conky there is:

Super     Main Menu

which works, and you also have the Super + Space keybinding for the main menu.

Seems redundant to have two. Personally, I would keep the Super + Space binding and edit the conky. Drop the Super key only binding.

Everything works out of the box on a Toshiba Laptop - well done, Toshibas are kind of finicky with Linux.

Last edited by PackRat (2019-12-12 20:15:58)


You must unlearn what you have learned.
    -- yoda

Offline

#24 2019-12-13 01:38:14

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 6,194
Website

Re: Testing Lithium iso discussion

PackRat wrote:

On the keybindings list in the conky there is:

Super     Main Menu

which works, and you also have the Super + Space keybinding for the main menu.
Seems redundant to have two. Personally, I would keep the Super + Space binding and edit the conky. Drop the Super key only binding.

The way the Super-only binding works (xcape) means that the super-space binding has to exist too. The one-key menu was added for convenience, but you can edit or disable it in ~/.config/bunsen/autostart, this section:

    ## Alias Super key to Super+Space for single-key menu.
    ## See 'man xcape' for other possibilities.
    xcape -e 'Super_L=Super_L|space'

If you disable it, then you can remove xcape too of course.


John

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Offline

#25 2019-12-13 01:56:51

PackRat
jgmenu user Numero Uno
Registered: 2015-10-02
Posts: 1,159

Re: Testing Lithium iso discussion

^ Cool

The live session runs really smooth. Nice work.


You must unlearn what you have learned.
    -- yoda

Offline

Board footer

Powered by FluxBB