New ISOs in ce/testing

[Arjen Balfoort]

I'm in error. The SSD doesn't matter. After installation this happens whether the HD is marked as SSD or not. Removing quiet splash is of no use: the screen turns black and starts flashing after which there is no way of entering the system to check what happened.

I've been at it all day now. So, taking a break.

[grizzler]

Can't reproduce it here. I installed SolydK EE 9 64 in an existing VM (on my main HD) and it just boots. Was there anything special about the settings of the VM you used?

One oddity, though. With older versions, I remember you could force the quiet/splash options of the installed system off if you installed from an ISO that was started without these options. Because I wanted to see what happened during booting of the installed system, that's how I started the ISO. However, the installed system still starts with a black screen (with one line of text at the top, starting with the ISO name) and no bootup text (no plymouth either, but that never surprises me). Goes straight to the login screen after that.
The expected shutdown text does show up.

[ilu]

Here https://forums.solydxk.com/viewtopic.ph ... 956#p64954 is a bug report about a SolydK EE installer problem with disk encryption. Could you please have a look, schoelje?

[Arjen Balfoort]

I've seen it and it's a feature request, not a bug. There is no difference between the installer in EE or in the regular versions. For me it has no priority but I welcome everybody to check out Github and help coding.

[ilu]

In the posting I linked he said he can't see the boxes for the check marks on KDE EE. That sounds like a possible bug to me, maybe theme related?

Having run the EE installer through a couple of times, what I see is a slightly broken interface that permits encryption of certain, individual partitions. I say 'broken' in that the installer on my verified live DVD presents no check box for partition encryption options, as is shown in the install screen shots on this website. Activating the partition encryption seems to happen almost accidentally when one clicks on the partition, and even then, inconsistenly activated.

I wasn't talking about the rest. But I forgot to ask him which image he used... the Jan 17 one was broken, wasn't it?

[grizzler]

In the posting I linked he said he can't see the boxes for the check marks on KDE EE. That sounds like a possible bug to me, maybe theme related?

That was a problem for a while, yes. The ISOs currently in testing don't have that anymore, as far as I'm aware.

[grizzler]

Just started the upload of six newly built CE ISOs. They should appear in http://downloads.solydxk.nl/ce/testing/ some time tonight. I expect them all to be available after midnight CEST (22:00 UTC).

@Arjen,
You may want to add the files /usr/share/plasma/look-and-feel/org.kde.solydk.desktop/contents/layouts/org.kde.plasma.desktop.defaultPanel/contents/layout.js and /usr/share/plasma/look-and-feel/org.kde.solydk-dark.desktop/contents/layouts/org.kde.plasma.desktop.defaultPanel/contents/layout.js to the configs list starting at line 217 in /usr/lib/solydxk/system/adjust.py.
Also, /usr/share/solydxk/default-settings/plasma5-profile/kickoffrc (provided by solydk-system-adjustments-9) still exists, even though kickoff is no longer used in the new ISOs. What do you want to do with it? If it is kept in case someone enables kickoff, I think it should be in the configs list as well.

Installing accountsservice, creating the data subdirectory in /var/lib/lightdm and enabling the obex.service did get rid of some of the errors/issues, but not all of them.

[Arjen Balfoort]

Thanks, I've updated solydxk-system.

[xendistar]

Just started the upload of six newly built CE ISOs. They should appear in http://downloads.solydxk.nl/ce/testing/ some time tonight. I expect them all to be available after midnight CEST (22:00 UTC).

Downloaded the 64 bit version of the above, booted the iso in virtualbox no problem (choosing the virtualbox boot option). Click install select language, time zone, accept partition defaults, setup user, start the install, then within 5 minute install crashes out and takes me back to the live desktop. No errors nothing. The sha256 is correct. Anybody else having issues

Forgot to mention, it is the solydx ee version

UPDATE

Downloaded the ISO again, deleted the previous virtual machine from virtualbox, booted the iso, setup as per above, start the install and crashes again after a few minutes. Checked disk space on (real) hard disk and there is 21gb free, virtual PC is set to 8gb dynamic, won't need more than that to do an install?

[nuts2u]

Just started the upload of six newly built CE ISOs. They should appear in http://downloads.solydxk.nl/ce/testing/ some time tonight. I expect them all to be available after midnight CEST (22:00 UTC).

Downloaded the 64 bit version of the above, booted the iso in virtualbox no problem (choosing the virtualbox boot option). Click install select language, time zone, accept partition defaults, setup user, start the install, then within 5 minute install crashes out and takes me back to the live desktop. No errors nothing. The sha256 is correct. Anybody else having issues

Forgot to mention, it is the solydx ee version

UPDATE

Downloaded the ISO again, deleted the previous virtual machine from virtualbox, booted the iso, setup as per above, start the install and crashes again after a few minutes. Checked disk space on (real) hard disk and there is 21gb free, virtual PC is set to 8gb dynamic, won't need more than that to do an install?

I have never been able to install any full distro with less than a 12 to 14 Gig VDI in Virtualdisk.

[MAYBL8]

Installed Solyxee64 in VB. No issues.
These are my settings:
Memory: 1536
Video Memory: 128
Network: Bridged
Processor: 2 CPU

[xendistar]

Well I just tried to install a different distro iso (centos core as it happens) and that installed without issue. I am using Virtualbox version 5.1.6 which I get direct from oracle via their repo.

I don't have time now as I am off to bed as I am up at silly o'clock tomorrow morning but what I will do is video the setup and install process tomorrow night and hopefully catch the crash I will even download a new iso.

[Arjen Balfoort]

Just a quick install of SolydX EE 64 and SolydK EE 64 in VB with a 16G drive: no issues (see terminal output attached).

I will further check these ISOs later.

[grizzler]

I don't have time now as I am off to bed as I am up at silly o'clock tomorrow morning but what I will do is video the setup and install process tomorrow night and hopefully catch the crash

Please start the installer in a terminal and show us the output.

[xendistar]

Just a quick install of SolydX EE 64 and SolydK EE 64 in VB with a 16G drive: no issues (see terminal output attached).

I will further check these ISOs later.

Did not know you could do the live installer like that to get an output, will try and post the results.

Thanks guys

[xendistar]

OK just tried again and the samething happens although this time it got about halfway through the install. earlier attempts failed around a quarter of the way through the install (based on the progress bar)

I have attached a couple of files showing the sha256 is correct and free space (32gb)

settings.txt

(293 Bytes) Downloaded 79 times

The VB settings

Final the output of live installer

installer-log.txt

(7.52 KiB) Downloaded 72 times

[xendistar]

Ok, just tried installing SolydK-ee and had exactly the same problem, the installed crashed out at about a third of the way through, but unlike the solydx-ee install there a lot more info at the end of the output

Code: Select all

solydxk@solydxk:~$ live-installer

(main.py:2654): Gtk-WARNING **: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(main.py:2654): Gtk-WARNING **: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(main.py:2654): Gtk-WARNING **: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
awk: warning: escape sequence `\.' treated as plain `.'
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-4-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
/bin/sh: 1: cannot create dev/null: Directory nonexistent
Setting up swapspace version 1, size = 4.1 GiB (4399820800 bytes)
no label, UUID=ae65dcee-4450-406e-a2b9-93de2022786e
mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 1022208 4k blocks and 256000 inodes
Filesystem UUID: 3142d8ff-c626-4854-9de1-f3803d1202a9
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

Executing: head -n 1 /etc/debian_version | sed 's/[a-zA-Z]/0/' 2>/dev/null || echo 0
Executing: logname
Executing: cat /proc/cmdline
Executing: isoquery --iso 3166-1 | cut -f1,4-
Executing: isoquery --iso 639-2
Executing: awk -F'[@ \.]' '/UTF-8/{ print $1 }' /usr/share/i18n/SUPPORTED | uniq
Error adding locale 'anp_IN'
Error adding locale 'ayc_PE'
Error adding locale 'ast_ES'
Error adding locale 'bem_ZM'
Error adding locale 'ber_DZ'
Error adding locale 'ber_MA'
Error adding locale 'bhb_IN'
Error adding locale 'bho_IN'
Error adding locale 'brx_IN'
Error adding locale 'byn_ER'
Error adding locale 'chr_US'
Error adding locale 'cmn_TW'
Error adding locale 'crh_UA'
Error adding locale 'csb_PL'
Error adding locale 'doi_IN'
Error adding locale 'fil_PH'
Error adding locale 'fur_IT'
Error adding locale 'gez_ER'
Error adding locale 'gez_ET'
Error adding locale 'hak_TW'
Error adding locale 'hne_IN'
Error adding locale 'hsb_DE'
Error adding locale 'kok_IN'
Error adding locale 'lij_IT'
Error adding locale 'lzh_TW'
Error adding locale 'mag_IN'
Error adding locale 'mai_IN'
Error adding locale 'mhr_RU'
Error adding locale 'mni_IN'
Error adding locale 'nan_TW'
Error adding locale 'nds_DE'
Error adding locale 'nds_NL'
Error adding locale 'nhn_MX'
Error adding locale 'niu_NU'
Error adding locale 'niu_NZ'
Error adding locale 'nso_ZA'
Error adding locale 'pap_AW'
Error adding locale 'pap_CW'
Error adding locale 'quz_PE'
Error adding locale 'raj_IN'
Error adding locale 'sat_IN'
Error adding locale 'sgs_LT'
Error adding locale 'shs_CA'
Error adding locale 'sid_ET'
Error adding locale 'szl_PL'
Error adding locale 'tcy_IN'
Error adding locale 'the_NP'
Error adding locale 'tig_ER'
Error adding locale 'unm_US'
Error adding locale 'wae_CH'
Error adding locale 'wal_ET'
Error adding locale 'yue_HK'
Executing: convert /usr/share/pixmaps/faces/user-generic.png -resize x96 /tmp/live-installer-3-face.png
Executing: awk '/^[^#]/{ print $1,$2,$3 }' /usr/share/zoneinfo/zone.tab | sort -k3
Executing: setxkbmap -query | awk -F"(,|[ ]+)" '/^(model:|layout:)/ {print $2}'
Set user language: en_GB
Executing: mkdir -p /tmp/live-installer-3/tmpmount
Executing: modprobe efivars >/dev/null 2>&1
Executing: findmnt -n -o source /lib/live/mount/findiso 2>dev/null || :
Executing: LC_ALL=en_US.UTF-8 lsblk -rindo TYPE,NAME,RM,SIZE,MODEL | sort -k3,2
Executing: cat /sys/block/sda/queue/rotational
device = /dev/sda
pen_drives = []
detachable = False
Can't find model in blkid output: ['loop', 'loop0', '0', '1.9G']
('Disks: ', [('/dev/sda', 'VBOX HARDDISK (8GB)', False, False)])
Executing: awk '/^MemTotal/{ print $2 }' /proc/meminfo
mkpart primary 2MB 4402MB
mkswap /dev/sda1
mkpart primary 4403MB 100%
mkfs.ext4 -F /dev/sda2
Executing: env LANG=C cryptsetup status sda1
Command 'env LANG=C cryptsetup status sda1' returned non-zero exit status 4
Executing: blkid -o value -s TYPE /dev/sda1
Executing: blkid -o value -s TYPE /dev/sda1
Executing: lsblk -o LABEL /dev/sda1 | grep -v LABEL | grep -v "^$"
Command 'lsblk -o LABEL /dev/sda1 | grep -v LABEL | grep -v "^$"' returned non-zero exit status 1
Executing: df /dev/sda1 | grep '^/dev/sda1' | awk '{print $2,$4,$5,$6}' | tail -1
WARNING: Partition /dev/sda1 or type swap failed to mount!
Executing: env LANG=C cryptsetup status sda2
Command 'env LANG=C cryptsetup status sda2' returned non-zero exit status 4
Executing: blkid -o value -s TYPE /dev/sda2
Executing: blkid -o value -s TYPE /dev/sda2
Executing: lsblk -o LABEL /dev/sda2 | grep -v LABEL | grep -v "^$"
Command 'lsblk -o LABEL /dev/sda2 | grep -v LABEL | grep -v "^$"' returned non-zero exit status 1
Executing: mount | grep "/dev/sda2 "
Command 'mount | grep "/dev/sda2 "' returned non-zero exit status 1
Executing: mount --read-only /dev/sda2 /tmp/live-installer-3/tmpmount
Executing: df /dev/sda2 | grep '^/dev/sda2' | awk '{print $2,$4,$5,$6}' | tail -1
Executing: umount -f /dev/sda2
Executing: dd bs=512 count=1 if=/dev/sda1 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda2 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda 2>/dev/null | strings
Executing: TZ=Europe/London date +%z
Timezone: Europe/London (UTC+0100) (372, 134)
Color: #2b1100
Image: timezone_0.0.png
Executing: setxkbmap -layout gb
Executing: python3 /usr/lib/live-installer-3/generate_keyboard_layout.py gb None /tmp/live-install-keyboard-layout.png
Executing: cat /proc/cmdline
>>> Live Installation <<<
Add mount / to sorted partitions
Add mount swap to sorted partitions
Check disk ('/dev/sda', 'VBOX HARDDISK (8GB)', False, False) for ssd
disk=/dev/sda, ssd=False, detachable=False
INFO      --> Installation started
--> Installation started
INFO      Formatting /dev/sda2 as ext4 ... (1 of 4)
Executing: mount | grep "/target/dev/shm "
Command 'mount | grep "/target/dev/shm "' returned non-zero exit status 1
Executing: mount | grep "/target/dev/pts "
Command 'mount | grep "/target/dev/pts "' returned non-zero exit status 1
Executing: mount | grep "/target/dev "
Command 'mount | grep "/target/dev "' returned non-zero exit status 1
Executing: mount | grep "/target/sys/fs/fuse/connections "
Command 'mount | grep "/target/sys/fs/fuse/connections "' returned non-zero exit status 1
Executing: mount | grep "/target/sys "
Command 'mount | grep "/target/sys "' returned non-zero exit status 1
Executing: mount | grep "/target/proc "
Command 'mount | grep "/target/proc "' returned non-zero exit status 1
Formatting /dev/sda2 as ext4 ... (1 of 4)
mkfs.ext4 -F -q /dev/sda2
INFO      Formatting /dev/sda1 as swap ... (1 of 4)
Executing: lsblk -o LABEL /dev/sda2 | grep -v LABEL | grep -v "^$"
Command 'lsblk -o LABEL /dev/sda2 | grep -v LABEL | grep -v "^$"' returned non-zero exit status 1
Formatting /dev/sda1 as swap ... (1 of 4)
mkswap /dev/sda1
mkswap: /dev/sda1: warning: wiping old swap signature.
Setting up swapspace version 1, size = 4.1 GiB (4399820800 bytes)
no label, UUID=f88b60ac-3e4a-4f18-b00e-9d6bc406792c
INFO      --> Mounting partitions
Executing: lsblk -o LABEL /dev/sda1 | grep -v LABEL | grep -v "^$"
Command 'lsblk -o LABEL /dev/sda1 | grep -v LABEL | grep -v "^$"' returned non-zero exit status 1
--> Mounting partitions
INFO      Mounting /lib/live/mount/medium/live/filesystem.squashfs on /source/ (2 of 4)
Mounting /lib/live/mount/medium/live/filesystem.squashfs on /source/ (2 of 4)
mount: /lib/live/mount/medium/live/filesystem.squashfs is used as read only loop, mounting read-only
INFO      Mounting /dev/sda2 on /target (3 of 4)
Executing: mount | grep "/lib/live/mount/medium/live/filesystem.squashfs " | grep "/source/ "
Command 'mount | grep "/lib/live/mount/medium/live/filesystem.squashfs " | grep "/source/ "' returned non-zero exit status 1
Executing: mount -o loop -t squashfs /lib/live/mount/medium/live/filesystem.squashfs /source/
Mounting /dev/sda2 on /target (3 of 4)
mkdir -p /target 2>/dev/null
Executing: mount | grep "/dev/sda2 " | grep "/target "
Command 'mount | grep "/dev/sda2 " | grep "/target "' returned non-zero exit status 1
Executing: mount  -t ext4 /dev/sda2 /target
df --inodes /source | awk '/^.+?\/source$/{ print $3 }'
255602
INFO      --> Copying 255602 files
--> Copying 255602 files
rsync: write failed on "/target/usr/share/foomatic/db/source/printer/Apple-LaserWriter_16_600.xml": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]
ERROR     System copy ended abruptly.
Your system might not function properly (rsync code: 11).

(main.py:2654): Gdk-ERROR **: The program 'main.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadImplementation (server does not implement operation)'.
  (Details: serial 18710 error_code 17 request_code 20 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap

An error is mentioned (see the output at the end of the output) in the first line regarding "No space left on device"?? Followed by several other error, Maybe Schoelje or Grizzler can work out if these are only SolydK-ee error or if they would be the same for Solydx-ee as well.

For the record I ran short and long test using smart on the hard disk of the host PC last night, both test past with no errors, The host OS is Ubuntu Studio 16:10 on an Intel i7 with 8gb memory and a Nividia Geforce 8400 using driver version 340.12

I made the soldyK-ee virtual machine to the same spec as the solydx-ee virtual machine as seen in an earlier post (large image above)

[grizzler]

The "No space left on device" error is odd. You used a 8GB vdi, didn't you? I usually use 12GB, but surely 8GB should be large enough. On the other hand... Maybe you could try a slightly larger vdi? Apparently rsync thinks there really isn't enough space.

Edit
Hang on. How large was that swap space again? 4.1GiB? Oh yes! You definitely need a larger vdi.

[xendistar]

<snip>
Edit
Hang on. How large was that swap space again? 4.1GiB? Oh yes! You definitely need a larger vdi.

That fixed it, Installed SolydK-ee without issue will try SolydX-ee later.

Have to be honest and say I have not come across that issue with other distro, what selects the 4gb partition for the swap partition?

Also the hard disk is set to dynamic so I thought it would grow as the disk space was used up?

Finally, is there something missing on SoldyX-ee as to why it never gave the error that SolydK-ee gave?

[grizzler]

Have to be honest and say I have not come across that issue with other distro, what selects the 4gb partition for the swap partition?

Ultimately, you do. If you think what's suggested is too much, you make it smaller.
That said, by default the swap partition is about as large as the available RAM, to allow hibernation. I see you selected 4096MB base memory...

Also the hard disk is set to dynamic so I thought it would grow as the disk space was used up?

It will start small and grow as required, but never beyond the maximum you selected.

Finally, is there something missing on SoldyX-ee as to why it never gave the error that SolydK-ee gave?

No idea. Probably depends on how exactly the limit is reached.