You are not logged in.
the Screen Layout Editor - System - Metacity this: gconf is not available
I'm sorry, I'm not sure I understand, do you mean arandr?
Please provide exact details of what you did to produce this error so that we can try to reproduce this.
A full error message rather than a vague summary would also be much more useful, thanks.
Perhaps also have a quick read of the "How to report a problem" link on my signature, that explains things
Last edited by Head_on_a_Stick (2018-03-22 07:49:45)
Offline
^I suspect that might be Menu/Preferences/Display/Display Settings -> Opens Screen Layout Editor -> System
Offline
where is alpha 6.iso
Do you think we are really close to finish line?
Offline
^I think we are as close as the day is long! 8) No worries, it's just getting better.
As for alpha 6: Have a look at here.
Offline
Yesterday I noticed that there is different versions for the different archs.
Alpha5 for i386, and alpha6 for amd64...
Yes, other fixes went in at the same time so alpha6 is slightly different.
Eventually there will be:
amd64
i386
that should be the same, apart from architecture, and also a
CD-ROM sized i386 non-PAE
for older machines, with a reduced set of applications installed to get the iso down to under 700MB.
And thanks for the feedback about the /etc/grub/default line. This glitch goes back some time - at least to the Deuterium release - and I'm still trying to get to the bottom of it.
Last edited by johnraff (2018-03-23 06:47:01)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
the /etc/grub/default line
^ I can confirm that "initrd=/install/initrd.gz" line is not present in a Debian stretch system, I tried a VM installation with a netinstall ISO and GRUB_CMDLINE_LINUX was empty.
Offline
If I would like to prevent light-locker from starting at all I should add this line to the bottom of the file:
Hidden=true
Nothing has changed from previous releases ?
Offline
I am using alpha6.iso, booting loading whole iso into live mode.
In firefox looking at some of my webpages the font Sans Serif looks like Times new Roman.
Did you not load all the fonts yet in the testing version?
Offline
@Pink Unicorn
sudo apt uninstall light-locker
will completely uninstall light-locker.
Offline
If I would like to prevent light-locker from starting at all I should add this line to the bottom of the file:
Hidden=true
Nothing has changed from previous releases ?
The method is still the same, yes.
https://forums.bunsenlabs.org/viewtopic.php?id=2080
In firefox looking at some of my webpages the font Sans Serif looks like Times new Roman.
Did you not load all the fonts yet in the testing version?
We have removed some font packages, yes, but sans-serif should not look like Times New Roman.
What is the output of:
fc-match sans-serif
Offline
johnraff wrote:the /etc/grub/default line
^ I can confirm that "initrd=/install/initrd.gz" line is not present in a Debian stretch system, I tried a VM installation with a netinstall ISO and GRUB_CMDLINE_LINUX was empty.
Man... just spent a fun-packed couple of hours trying to figure this out.
The point I've got to, I think, is the structure of the installer's boot command.
To test: start a debian install iso (live sessions are irrelevant here) and as soon as you get to the first prompt (choose language) switch to tty2 and run 'cat /proc/cmdline'
You can also look in an already installed system's /var/log/installer/syslog
With BL isos you'll get something like:
BOOT_IMAGE=/install/gtk/vmlinuz video=vesa:ywrap,mtrr vga=788 -- quiet initrd=/install/gtk/initrd.gz
But with the Debian netinstalll iso I just booted, the -- is right at the end.
Why that's important is what took much gruelling grepping and googling, but essentially grub-pc's postinstall script looks at /var/cache/debconf/config.dat and fetches linux_cmdline:
Name: grub2/linux_cmdline
Template: grub2/linux_cmdline
Value: initrd=/install/gtk/initrd.gz
Owners: grub-pc
Flags: seen
This is then written into /etc/default/grub as GRUB_CMDLINE_LINUX.
That debconf data is written by debian-installer's grub-installer module, using the di-utils module to query the above command line and fetch any user-added parameters. Any arguments before the -- are ignored, those which come after are passed to debconf (after some filtering).
This bug report was a hint: https://bugs.debian.org/cgi-bin/bugrepo … bug=395920
So, what remains is to figure out why our command line is being set up that way, in contrast to, say, the Debian netinstall. The grub menu entries on the iso look OK, with the initrd file set separately, eg:
label install
menu label ^Text based install
linux /install/vmlinuz
initrd /install/initrd.gz
append vga=788 -- quiet
So why is initrd=/install/initrd.gz being appended after the --??
I have to go out now, so the rest will have to wait a bit. A beer later this evening will probably taste good though...
Last edited by johnraff (2018-03-24 06:45:03)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Also, the live-tools package is present in the installed system and the live-tools.service is enabled.
Offline
Also, the live-tools package is present in the installed system and the live-tools.service is enabled.
A bug/feature in live-build? live-tools has stayed installed on every build we've done IIRC, in spite of the install message about 'removing live components', or similar.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Also, the live-tools package is present in the installed system and the live-tools.service is enabled.
Ah! Thanks for catching that. Our patched live-installer udeb should have got rid of it, just as live-build promises, but my last upgrade of the package was broken because I wanted to use quilt this time, which does not make files added by a patch executable. I've now added a small section to debian/rules which should have fixed it. We won't know for sure till the next iso build though. (I'm going to throw in debian-installer-launcher too, just to see if it's got any chance of working.)
@hhh Yes it's a live-build bug (Debian #655198) which I actually fixed with our local live-installer udeb, so Deuterium had no leftover live-tools.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
So, what remains is to figure out why our command line is being set up that way, in contrast to, say, the Debian netinstall...
...why is initrd=/install/initrd.gz being appended after the --??
Bit more: with an EFI system (ie EFI enabled in VB) the boot menu uses Grub not Isolinux, and booting BL alpha6 shows /proc/cmdline with no odd initrd entry. I didn't take it all the way to install, but I've no reason to think it would have that unwanted line in /etc/default/grub, since it's being initially pulled from /proc/cmdline.
By comparison, Debian's firmware-9.0.0-amd64-netinst.iso also looked OK under EFI, and if booted under Isolinux, had a command line ending with ---, explaining why it's OK.
So, there's something different in the Isolinux department...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
OK I think we can fix the extraneous GRUB_CMDLINE_LINUX line issue.
Here's the Debian netinstall Isolinux config file snippet for the expert install:
label expert
menu label E^xpert install
kernel /install.amd/vmlinuz
append priority=low vga=788 initrd=/install.amd/initrd.gz ---
And ours:
label expert
menu label ^Expert installer (text)
linux /install/vmlinuz
initrd /install/initrd.gz
append priority=low vga=normal -- quiet
And Syslinux Wiki:
[3.71+] An initrd can be specified in a separate statement (INITRD) instead of as part of the APPEND statement. This functionally appends "initrd=initrd_file" to the kernel command line.
But what seems to happen is that the initrd statement is appended after the other parameters added with the 'append' statement, so comes after the '--'. That has the consequences previously suspected for the installer:
anything that is passed after the '--' are appended to the default options for the installed system. everything before the '--' is only used by the installer itself.
It looks as if the Debian netinstall is getting round this issue by putting the initrd statement inside the 'append' string instead of declaring it separately. I suggest we do the same in our install menu items for Isolinux.
(And take out the 'quiet' in the expert install too.)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I use rEFInd for multi-partition, multi-system, multi-ISO USB booting.
There are 2 kinds of ISO's^^: non-problematic & problematic. Non-problematic ISO content could be just copied to fat32 partition and booted with rEFInd then. Problematic ISO's must be dd'ed to partition, sometimes there are also non rEFInd startable ISO's too.
Of course that is just USB booting. We also appreciate when ISO's could be just booted by manual grub entry from hard drive as loopback device as I properly remember (Debian has some problem with that - one should use rare grub command line switches).
That said Alpha6 does not start when copied to usb partition & booted from rEFInd, just drops to grub command line. Any ideas?
Last edited by dobl (2018-03-26 09:08:13)
Offline
We also appreciate when ISO's could be just booted by manual grub entry from hard drive as loopback device
^ That can be done with our current image, see the "SharpBang" entry in this grub.cfg:
Offline
I tried to install Alpha 6, but the step where you install the system, after the partioning, failed. I tried both automatic guided partioning, selecting the largest continuous free space (30 gigabytes after the Windows partition, it split that into 22GB for root, and 8GB for swap), as well as creating an ext4 partition myself of 30GB.
I used legacy boot, not UEFI boot, in my install attempt. I also checked the MD5 hash after the installation failed to make sure my download was correct, and it matches the MD5 hash of the forum post: 6dcb91986f4101c318adad07ece0ed6b
The current version of BunsenLabs installs and runs perfectly, also using legacy boot on the same laptop: a ThinkPad X220.
Sadly I don't know how to save any kind of error or log from the installer to help troubleshoot. It didn't even give an error, it just said it failed the install the system step.
Offline
Head on a Stick
In firefox looking at some of my webpages the font Sans Serif looks like Times new Roman.
Did you not load all the fonts yet in the testing version?
We have removed some font packages, yes, but sans-serif should not look like Times New Roman.
What is the output of:
fc-match sans-serif
The output i get from fc-match sans-serif
is
NotoSans-Regular.ttf: "Noto Sans" "Regular"
Offline