ISO testing 201410

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
Arjen Balfoort
Site Admin
Posts: 9223
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

ISO testing 201410

Postby Arjen Balfoort » 07 Oct 2014 13:58

I have created the upcoming ISOs with the current testing repository.

The sources are pointing to production. So, if you want to add packages to your testing system, you'll need to replace "/production" with "/testing" in /etc/apt/sources.list (don't forget to apt-get update after you saved sources.list).

You can download the ISOs here: http://downloads.solydxk.nl/dev

And here's the testing sheet:
SolydXK UP-ISO test cases.ods
(74.6 KiB) Downloaded 91 times


SolydXK needs you!
Development | Testing | Translations

User avatar
timber
Posts: 539
Joined: 11 Aug 2013 21:01
Location: Pacific Northwest

Re: ISO testing 201410

Postby timber » 07 Oct 2014 18:39

Downloading solydk64_201410.iso
Will let you know how it goes.

timber
timber

Samsung R580-M430 @ 2.27GHz - 8 GB RAM
Geforce 310M w/ nvidia-driver
SolydX/SolydM - Kernel 3.14-2-amd64 - Update Pack: 2014.07.15
SolydK - Kernel 3.14-2-amd64 - Update Pack: 2014.07.15
SolydKBE - Kernel 3.2.0-4-amd64 - LTS Update Pack: 2014.07.15

User avatar
just
Posts: 297
Joined: 07 Nov 2013 08:06
Location: Rovaniemi, Finland

Re: ISO testing 201410

Postby just » 07 Oct 2014 18:59

good news! with the latest dev isos
  • solydk64_201410.iso 06-Oct-2014 11:18 1.7G
  • solydx64_201410.iso 07-Oct-2014 04:46 1.3G
live-installer finally starts!

that's the only one, for now. more details.
  1. dd-made media are non bootable: "Operation System not found".
  2. UNetbootbin remains the only tool that allows to prepare it.
  3. in both X and K live-installer can be normally launched now by a default (standard) user, with the desktop icon, from menu, from terminal.
  4. neither in X nor in K live installer terminates correctly. installation doesn't finish.
  5. X and K installers behave differently one from another. maybe because of the different release dates - 6 for K, 7 for X.
  6. solydx: installer starts to present its pages in sequence:
    1. Language - OK
    2. Timezone - OK
    3. Keyboard layout - OK
    4. User info - OK
    5. Hard drive - KO, is blank, no drives list
    6. Partitioning - KO, is blank, no partitions list
    7. without / and other partitions the installer can't proceed ("Need to select at least / ...")
    8. user may only click Back button or close the installer, without terminating the installation.
  7. solydk: installer starts and presents in sequence all of its pages, from Language to Summary. then installation starts:
    1. formatting / partition - OK
    2. indexing files - OK
    3. copying files - KO. installer's window closes. without completing the installation.
X and K was tested on two different computers - behave identically on both.

if it could be useful, these are live-installer executions in terminal.

1. solydx

Code: Select all

solydxk@solydxk ~ $ su -
Password: 
solydxk ~ # live-installer
>>> squashfs path = /lib/live/mount/medium/live/filesystem.squashfs
>>> Distribution edition: solydx64
>>> Gateway: None
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout gb  -compact
munmap: Invalid argument
libv4l2: warning v4l2 mmap buffers still mapped on close()
Color: #550000
Image: /usr/share/live-installer/timezone/timezone_-10.0.png
Coords: 358.0 128.0
Closest timezone Europe/Dublin
Color: #2b1100
Image: /usr/share/live-installer/timezone/timezone_0.0.png
Color: #2b1100
Image: /usr/share/live-installer/timezone/timezone_0.0.png
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout us  -compact
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout gb  -compact
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout gb  -compact
solydxk ~ # 
2. solydk

Code: Select all

solydxk@solydxk ~ $ live-installer
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout gb  -compact
munmap: Invalid argument
libv4l2: warning v4l2 mmap buffers still mapped on close()
Color: #550000
Image: /usr/share/live-installer/timezone/timezone_-10.0.png
Coords: 358.0 126.0
Closest timezone Europe/Dublin
Color: #2b1100
Image: /usr/share/live-installer/timezone/timezone_0.0.png
Color: #2b1100
Image: /usr/share/live-installer/timezone/timezone_0.0.png
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout us  -compact
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout gb  -compact
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout gb  -compact
 ## INSTALLATION 
Template path: /usr/share/live-installer/slideshow/template.html
 --> Installation started
umount2: No such file or directory
umount: /target/dev/shm: not found
umount2: No such file or directory
umount: /target/dev/pts: not found
umount2: Invalid argument
umount: /target/dev/: not mounted
umount2: Invalid argument
umount: /target/sys/: not mounted
umount2: Invalid argument
umount: /target/proc/: not mounted
 --> Mounting partitions
 ------ Mounting /lib/live/mount/medium/live/filesystem.squashfs on /source/
EXECUTING: 'mount -o loop -t squashfs /lib/live/mount/medium/live/filesystem.squashfs /source/'
 ------ Mounting partition /dev/sdb6 on /target/
EXECUTING: 'mount -t ext4 /dev/sdb6 /target'
EXECUTING: 'umount /target'
EXECUTING: 'mkfs.ext4 /dev/sdb6'
 --> Mounting partitions
 ------ Mounting /lib/live/mount/medium/live/filesystem.squashfs on /source/
EXECUTING: 'mount -o loop -t squashfs /lib/live/mount/medium/live/filesystem.squashfs /source/'
 ------ Mounting partition /dev/sdb6 on /target/
EXECUTING: 'mount -t ext4 /dev/sdb6 /target'
 ------ Mounting /dev/sdb16 on /target/1st
EXECUTING: 'mount -t ext4 /dev/sdb16 /target/1st'
 --> Indexing files
 --> Copying files
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_context: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_context_get_language: assertion 'context != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_context_get_metrics: assertion 'PANGO_IS_CONTEXT (context)' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_font_metrics_get_approximate_char_width: assertion 'metrics != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_font_metrics_get_approximate_digit_width: assertion 'metrics != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_set_width: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_extents: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: GtkWarning: IA__gdk_draw_layout: assertion 'PANGO_IS_LAYOUT (layout)' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_width: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_line_count: assertion 'layout != NULL' failed
  gtk.main()
*** Error in `/usr/bin/python2.7': double free or corruption (fasttop): 0x00007f3bb4001570 ***
>>> squashfs path = /lib/live/mount/medium/live/filesystem.squashfs
>>> Distribution edition: solydk64
>>> Gateway: None
solydxk@solydxk ~ $ 

User avatar
timber
Posts: 539
Joined: 11 Aug 2013 21:01
Location: Pacific Northwest

Re: ISO testing 201410

Postby timber » 08 Oct 2014 01:34

solydk64_201410.iso (06-Oct-2014 11:18 1.7G)
md5sum checked -OK

Live Session: -All OK
  • Live USB boots fine (Unetbootin used on USB stick)
    Live session checks out fine (see attached)
Install (via "Install SolydXK" button) -Fails
  • Slight hang at Hard Drive selection (seems longer than usual, maybe 6-7 seconds)
    New Partitions (/ and /home assigned separate partitions)
    Formatting of / partition - OK
    Indexing fies - OK
    Fails <1 second after Summary screen closes and file copying starts
Via command line:

Code: Select all

solydxk solydxk # live-installer
>>> squashfs path = /lib/live/mount/medium/live/filesystem.squashfs
>>> Distribution edition: solydk64
>>> Gateway: None
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout us  -compact
munmap: Invalid argument
libv4l2: warning v4l2 mmap buffers still mapped on close()
Color: #550000
Image: /usr/share/live-installer/timezone/timezone_-10.0.png
Coords: 103.0 176.0
Closest timezone America/Los_Angeles
Color: #aa0000
Image: /usr/share/live-installer/timezone/timezone_-8.0.png
Color: #aa0000
Image: /usr/share/live-installer/timezone/timezone_-8.0.png
>>> Keyboard.loadCodes cmd = ckbcomp -model pc106 -layout us  -compact
 ## INSTALLATION 
Template path: /usr/share/live-installer/slideshow/template.html
 --> Installation started
umount2: No such file or directory
umount: /target/dev/shm: not found
umount2: No such file or directory
umount: /target/dev/pts: not found
umount2: Invalid argument
umount: /target/dev/: not mounted
umount2: Invalid argument
umount: /target/sys/: not mounted
umount2: Invalid argument
umount: /target/proc/: not mounted
 --> Mounting partitions
 ------ Mounting /lib/live/mount/medium/live/filesystem.squashfs on /source/
EXECUTING: 'mount -o loop -t squashfs /lib/live/mount/medium/live/filesystem.squashfs /source/'
 ------ Mounting partition /dev/sda17 on /target/
EXECUTING: 'mount -t ext4 /dev/sda17 /target'
EXECUTING: 'umount /target'
EXECUTING: 'mkfs.ext4 /dev/sda17'
 --> Mounting partitions
 ------ Mounting /lib/live/mount/medium/live/filesystem.squashfs on /source/
EXECUTING: 'mount -o loop -t squashfs /lib/live/mount/medium/live/filesystem.squashfs /source/'
 ------ Mounting partition /dev/sda17 on /target/
EXECUTING: 'mount -t ext4 /dev/sda17 /target'
 ------ Mounting /dev/sda18 on /target/home
EXECUTING: 'mount -t ext4 /dev/sda18 /target/home'
 --> Indexing files
 --> Copying files
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_context: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_context_get_language: assertion 'context != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_context_get_metrics: assertion 'PANGO_IS_CONTEXT (context)' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_font_metrics_get_approximate_char_width: assertion 'metrics != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_font_metrics_get_approximate_digit_width: assertion 'metrics != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_set_width: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_extents: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_line_get_extents: assertion 'LINE_IS_VALID (line)' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_width: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: PangoWarning: pango_layout_get_line_count: assertion 'layout != NULL' failed
  gtk.main()
/usr/lib/live-installer/main.py:23: GtkWarning: IA__gdk_draw_layout: assertion 'PANGO_IS_LAYOUT (layout)' failed
  gtk.main()
/usr/bin/live-installer: line 11:  6121 Segmentation fault      $LAUNCHER /usr/bin/python2.7 -tt /usr/lib/live-installer/main.py $*
solydxk solydxk #
Attachments
SolydXK UP-ISO test cases.ods
(75 KiB) Downloaded 86 times
timber

Samsung R580-M430 @ 2.27GHz - 8 GB RAM
Geforce 310M w/ nvidia-driver
SolydX/SolydM - Kernel 3.14-2-amd64 - Update Pack: 2014.07.15
SolydK - Kernel 3.14-2-amd64 - Update Pack: 2014.07.15
SolydKBE - Kernel 3.2.0-4-amd64 - LTS Update Pack: 2014.07.15

User avatar
just
Posts: 297
Joined: 07 Nov 2013 08:06
Location: Rovaniemi, Finland

Re: ISO testing 201410

Postby just » 08 Oct 2014 05:31

sorry for not attaching test reports earlier. doing it now.

only a note about shutdown times.

on ATI computer the shutdown from a live session is normal and fast, takes only some seconds.

on NVIDIA computer the shutdown is fast only if nothing has been done during the live session. if some apps were opened, some tests have been done, the shutdown takes about 5 min to complete. remaining with a white fixed cursor in the top left corner on the black shutdown screen.
Attachments
SolydXK UP-ISO test cases (just-SolydK).ods
solydk64-201410-dev-20141006-1118
(54.05 KiB) Downloaded 72 times
SolydXK UP-ISO test cases (just-SolydX).ods
solydx64-201410-dev-20141007-0446
(53.78 KiB) Downloaded 84 times

User avatar
Arjen Balfoort
Site Admin
Posts: 9223
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: ISO testing 201410

Postby Arjen Balfoort » 08 Oct 2014 07:01

I can fix the live-installer, but it'll take some time until the new ISOs are built and uploaded.

In the mean time you can run this command before you start the live-installer:

Code: Select all

sudo sed -ie 's/.*gtk.gdk.threads_init()/gtk.gdk.threads_init()\ngtk.gdk.threads_enter()/' /usr/lib/live-installer/frontend/gtk_interface.py


SolydXK needs you!
Development | Testing | Translations

User avatar
Arjen Balfoort
Site Admin
Posts: 9223
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: ISO testing 201410

Postby Arjen Balfoort » 08 Oct 2014 07:32

I've removed the IRC test from the testing sheet: we don't have a freenode channel anymore.


SolydXK needs you!
Development | Testing | Translations

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 08:03

Downloading a first iso. SolydK32
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 08:41

Trying a VM install first (Solydk32). The installer in the Hard Drive section (after User Info) doesn't show any disks. Clicked forward and nothing listed again, so there's no way to select partitions. Refresh doesn't do anything. Edited the drive with Gparted but the new partitions don't show up either.

I'll try to make a USB iso and let's see what happens.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
just
Posts: 297
Joined: 07 Nov 2013 08:06
Location: Rovaniemi, Finland

Re: ISO testing 201410

Postby just » 08 Oct 2014 08:45

Schoelje wrote:
...we don't have a freenode channel anymore.
OK, that's why irc clients don't autoconnect.

Schoelje wrote:
...you can run this command before you start the live-installer: sed -ie...
from that less than nothing i know about stream editing syntax, the command should be applied in SolydX, which presents the empty Hard Drive and Partitioning pages in installer. nevertheless, i've tried it in X and in K :shock: . the result is the same in both: live-installer starts, but immediately stucks at the first - Language - selection page.

English (United States) is preselected, no other one can be selected. Forward, Back, Quit buttons don't respond. Closing the window with X pops up a warning: "This window might be busy and is not responding. Do you want to terminate the application?" Yes.

will wait for new isos.

ps. all my tests are done on real metal, not in VM.

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 08:49

Got these notifications during startup. They last visible for about 1 sec. Not even enough time to read them, so I had to repeat this a few times to get a screen capture of both, but here they are.

Image
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Arjen Balfoort
Site Admin
Posts: 9223
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: ISO testing 201410

Postby Arjen Balfoort » 08 Oct 2014 08:55

@just
Odd, I ran the command and completed the install after...will investigate later.
[EDIT]
Ah, I always run my commands as su. Did you add sudo in front of the command?

@snap
I saw them too, but all seems to work okay.


SolydXK needs you!
Development | Testing | Translations

User avatar
just
Posts: 297
Joined: 07 Nov 2013 08:06
Location: Rovaniemi, Finland

Re: ISO testing 201410

Postby just » 08 Oct 2014 08:58

Snap wrote:
Got these notifications during startup...
same here. but only in K, not in X. have not enough patience to capture it.

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 09:12

Hey, just. I never had issues with dd before, but for some reason I cannot erase my flashdrives anymore. I'm getting an error of not enough disk space remaining. Maybe the issue is within dd and not in the isos?

I'll try a different stick whenever this one stops and reports the error. It takes forever to stop now.

BTW, Yesterday I read somewhere that some folks were having issues mounting USB drives after the last Debian updates. Specially in Xfce IIRC. Maybe this issue is related to this weird dd behavior.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 09:22

@snap
I saw them too, but all seems to work okay.
No way to install here. No disks listed at all or a way to select any partition.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 09:25

Hey, dd succeed this time. But it took like 20 minutes to complete. :shock: Gonna try to erase the MBR now. Let's see what happens.

PS, done. This was fast. Going for the iso.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 10:02

Another 20 minutes... It never took me so long to copy an iso into a flash drive. No errors reported, but it doesn't boot.

Downloading SolydX32.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
just
Posts: 297
Joined: 07 Nov 2013 08:06
Location: Rovaniemi, Finland

Re: ISO testing 201410

Postby just » 08 Oct 2014 10:36

[offtopic]
Snap wrote:
...Maybe this issue is related to this weird dd behavior.
with years gone, i've learned to tolerate many things, but not such thoughts about dd. dd is the only tool on earth that works always and fails never :lol: .

speaking seriously about some dd "errors", it could be simply a human ones. for example, if one tries something like this on a 512K device:

dd if=/dev/zero of=/dev/sdc bs=900

he will inevitably get the "no space left on device" error! but that's not a dd error, that's a human one. if the multiple of used bs doesn't exactly equals the real physical device capacity there always be such an error! which really is not an error, every usable byte on a device will be perfectly filled with zeros.

one could do something like:

dd if=solydk64_201410.iso of=/dev/sdc bs=10G

on a 4G device, and will inevitably get the "no space left on device" error, but the stick will be perfectly functioning and bootable (if the iso allows it). again, it's not a dd error but a human one.

the "speed" of dd depends on used bs. lower bs is, slower the speed. but higher the probability to match exactly the really available physical device capacity. with bs of 1 byte there will never be an "out of space" error! but dd will work forever...

sorry for off-topic :)
[/offtopic]

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: ISO testing 201410

Postby Snap » 08 Oct 2014 11:42

One of the best OTs I've ever seen. :lol: Thanks!

I was using bs=4M as usual with this and other flashdrives. Dunno why this time it was incredibly slow neither understand how to set the bs part so well. Do you mean that the needed multiples of the bs value to complete the image should be < or = the physical drive size to get no errors?

Sorry to keep going OT a bit more. but this is so important.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Arjen Balfoort
Site Admin
Posts: 9223
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: ISO testing 201410

Postby Arjen Balfoort » 08 Oct 2014 15:01

live-installer uses inxi to list the drives, but when I run the command:

Code: Select all

inxi -c0 -D
Error 5: dependency not met: uptime not found in path.
For distribution installation package names and missing apps information, run: inxi --recommends
I checked if uptime existed:

Code: Select all

$ dpkg -S uptime
diversion by live-tools from: /usr/share/man/man1/uptime.1.gz
diversion by live-tools to: /usr/share/man/man1/uptime.orig.procps.1.gz
python-pexpect-doc: /usr/share/doc/python-pexpect-doc/examples/uptime.py
diversion by live-tools from: /usr/share/man/man1/uptime.1.gz
diversion by live-tools to: /usr/share/man/man1/uptime.orig.procps.1.gz
procps: /usr/share/man/man1/uptime.1.gz
diversion by live-tools from: /usr/bin/uptime
diversion by live-tools to: /usr/bin/uptime.orig.procps
diversion by live-tools from: /usr/bin/uptime
diversion by live-tools to: /usr/bin/uptime.orig.procps
procps: /usr/bin/uptime
/usr/bin is in PATH.

So, what is happening here? :o

Creating a symbolic link:

Code: Select all

sudo ln -s /usr/bin/uptime.orig.procps /usr/bin/uptime
Now, inxi returned the drives and live-installer continues as expected.

Going to check if we really need live-tools.


SolydXK needs you!
Development | Testing | Translations


Return to “Testing Zone”

Who is online

Users browsing this forum: Bing [Bot] and 5 guests