Feedback and Bug Reports for Porteus v2.1 RC2
- Ed_P
- Contributor
- Posts: 8658
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Feedback and Bug Reports for Porteus v2.1 RC2
RazorQT 32bit works with -vga cirrus!! What the heck?? One works with one, the other works with a different one.
Also not sure what this means.
http://img694.imageshack.us/img694/7021/lftw.png
Also not sure what this means.
http://img694.imageshack.us/img694/7021/lftw.png
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Feedback and Bug Reports for Porteus v2.1 RC2
Is this good? I assume your referring to the 2D GUI accelerators for an emulator under win?RazorQT 32bit works with -vga cirrus!!
The error about /var/run/slim.auth shouldn't hinder login (please confirm). The file is generated during login.
At first I thought it was ck-session but after booting ck-list-sessions shows only one session. If you have any clues I am all ears on this one.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- wread
- Module Guard
- Posts: 1256
- Joined: 09 Jan 2011, 18:48
- Distribution: Porteus v5.0-kde-64 bits
- Location: Santo Domingo
- Contact:
Re: Feedback and Bug Reports for Porteus v2.1 RC2
@fanthom
I did not give you accurate enough information to recreate my bug before. It goes like this:
I start the machine with two USB sticks connected, one with the OS (2.1-kde4-rc2-32) the other one has files, both are ext4 formatted.
Now I stop the files-usb, extract it and insert the fat one: the machine rejects it.
IMHO the machine learns that the usb is ext4 formatted and when a fat fs comes in, it won't accept it, but when I try the other partition (a posix one, I think it is ext3) the machine takes it without complaining.
Here the output of message:
Seems to me all normal; the one I disconnect is an 8 Gb, the one I connect is a 16 Gb with 2 partitions.
See if you can recreate it...
The same happens with a single patition fat formatted 2Gb stick:
I see no error again, but it won't get mounted!
Regards
William
I did not give you accurate enough information to recreate my bug before. It goes like this:
I start the machine with two USB sticks connected, one with the OS (2.1-kde4-rc2-32) the other one has files, both are ext4 formatted.
Now I stop the files-usb, extract it and insert the fat one: the machine rejects it.
IMHO the machine learns that the usb is ext4 formatted and when a fat fs comes in, it won't accept it, but when I try the other partition (a posix one, I think it is ext3) the machine takes it without complaining.
Here the output of message:
Code: Select all
root@porteus:~# tail /var/log/messages
Jul 15 22:27:49 porteus dbus[1338]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jul 15 22:28:16 porteus kernel: [ 122.145218] sdb: detected capacity change from 7803174912 to 0
Jul 15 22:28:16 porteus kernel: [ 122.338074] usb 1-2: USB disconnect, device number 3
Jul 15 22:28:29 porteus kernel: [ 134.417043] usb 1-2: new high-speed USB device number 5 using ehci-pci
Jul 15 22:28:29 porteus kernel: [ 134.538458] scsi4 : usb-storage 1-2:1.0
Jul 15 22:28:30 porteus kernel: [ 135.630631] scsi 4:0:0:0: Direct-Access Kingston DT 101 G2 PMAP PQ: 0 ANSI: 0 CCS
Jul 15 22:28:30 porteus kernel: [ 136.258833] sd 4:0:0:0: [sdb] 30233472 512-byte logical blocks: (15.4 GB/14.4 GiB)
Jul 15 22:28:30 porteus kernel: [ 136.259454] sd 4:0:0:0: [sdb] Write Protect is off
Jul 15 22:28:30 porteus kernel: [ 136.277267] sdb: sdb1 sdb2
Jul 15 22:28:30 porteus kernel: [ 136.280093] sd 4:0:0:0: [sdb] Attached SCSI removable disk
root@porteus:~#
See if you can recreate it...
The same happens with a single patition fat formatted 2Gb stick:
Code: Select all
root@porteus:~# tail /var/log/messages
Jul 15 22:28:30 porteus kernel: [ 136.280093] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Jul 15 22:46:21 porteus -- MARK --
Jul 15 22:56:43 porteus kernel: [ 1828.577054] usb 1-2: USB disconnect, device number 5
Jul 15 22:57:09 porteus kernel: [ 1854.434057] usb 1-2: new high-speed USB device number 6 using ehci-pci
Jul 15 22:57:09 porteus kernel: [ 1854.551874] scsi5 : usb-storage 1-2:1.0
Jul 15 22:57:10 porteus kernel: [ 1855.552765] scsi 5:0:0:0: Direct-Access MOAI USB Flash Drive 1.00 PQ: 0 ANSI: 2
Jul 15 22:57:10 porteus kernel: [ 1855.557048] sd 5:0:0:0: [sdb] 3973120 512-byte logical blocks: (2.03 GB/1.89 GiB)
Jul 15 22:57:10 porteus kernel: [ 1855.557727] sd 5:0:0:0: [sdb] Write Protect is off
Jul 15 22:57:10 porteus kernel: [ 1855.758540] sdb: sdb1
Jul 15 22:57:10 porteus kernel: [ 1855.763618] sd 5:0:0:0: [sdb] Attached SCSI removable disk
root@porteus:~#
Regards
William
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!
The Porteus Community never sleeps!
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Feedback and Bug Reports for Porteus v2.1 RC2
@EdP
modules 0-2 are shared between desktop editions so it should work the same no matter of DE you are actually using.
please run 'md5sum' on 002-xorg.xzm and check if it's the same for XFCE and RazorQT.
@wread
thanks for evaluation. i think i know what's causing this:
when you boot with stick inserted then it gets it's own entry (with respective filesystem) in /etc/fstab. if you remove it and plug another stick with different fs then you get an error as filesystem does not match the one saved in /etc/fstab.
please do a simple test for me:
delete /etc/fstab, try to recreate the error and let me know how it goes.
@brokenman, Ahau
do we need /etc/fstab at all? maybe i could never create it since it's for reference only (and cannot even be modified)?
modules 0-2 are shared between desktop editions so it should work the same no matter of DE you are actually using.
please run 'md5sum' on 002-xorg.xzm and check if it's the same for XFCE and RazorQT.
@wread
thanks for evaluation. i think i know what's causing this:
when you boot with stick inserted then it gets it's own entry (with respective filesystem) in /etc/fstab. if you remove it and plug another stick with different fs then you get an error as filesystem does not match the one saved in /etc/fstab.
please do a simple test for me:
delete /etc/fstab, try to recreate the error and let me know how it goes.
@brokenman, Ahau
do we need /etc/fstab at all? maybe i could never create it since it's for reference only (and cannot even be modified)?
Please add [Solved] to your thread title if the solution was found.
- wread
- Module Guard
- Posts: 1256
- Joined: 09 Jan 2011, 18:48
- Distribution: Porteus v5.0-kde-64 bits
- Location: Santo Domingo
- Contact:
Re: Feedback and Bug Reports for Porteus v2.1 RC2
Bingo! Tom, that was it! Deleted /etc/fstab and it bit!
Thanks!
Thanks!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!
The Porteus Community never sleeps!
- Ahau
- King of Docs
- Posts: 1331
- Joined: 28 Dec 2010, 15:18
- Distribution: LXDE & Xfce 32/64-bit
- Location: USA
Re: Feedback and Bug Reports for Porteus v2.1 RC2
LXDE/Xfce use /etc/fstab for showing internal volumes in gvfs applications (pcmanfm, thunar). If I delete /etc/fstab, they all disappear from the file manager. What about a udev rule to remove the fstab entry for removable drives when they are removed?
Please take a look at our online documentation, here. Suggestions are welcome!
- francois
- Contributor
- Posts: 6445
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: Feedback and Bug Reports for Porteus v2.1 RC2
porteus 32 bit rc2 kde edition:
- clicking left on the arrow at the right of the google box at upper right of the firefox window:
The last download will appear
- clicking right and selecting open the containing folder will:
open audacious instead of the file manager.
Thanks.
- clicking left on the arrow at the right of the google box at upper right of the firefox window:
The last download will appear
- clicking right and selecting open the containing folder will:
open audacious instead of the file manager.
Thanks.
Prendre son temps, profiter de celui qui passe.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Feedback and Bug Reports for Porteus v2.1 RC2
Mount-manager also uses fstab for something. If an alternative can be found to removing it then I would prefer the alternative.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- Ed_P
- Contributor
- Posts: 8658
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Feedback and Bug Reports for Porteus v2.1 RC2
Yes and yes it does login & startx, eventually.brokenman wrote:Is this good? I assume your referring to the 2D GUI accelerators for an emulator under win?RazorQT 32bit works with -vga cirrus!!
The error about /var/run/slim.auth shouldn't hinder login (please confirm). The file is generated during login.
At first I thought it was ck-session but after booting ck-list-sessions shows only one session. If you have any clues I am all ears on this one.
However XFCE 32bit does not with -vga cirrus. See attached images.
http://img18.imageshack.us/img18/1389/px58.png
http://img692.imageshack.us/img692/7624/axdw.png
It would be nice if a single -vga option worked for all Porteus versions.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Feedback and Bug Reports for Porteus v2.1 RC2
@Ahau, brokenman
ok - /etc/fstab stays in. would be good to have the udev rule before we go final.
@francois
i think you are referring to qmmp and this bug was closed in rc2. are you using old changes or something?
please check $HOME/.local/share/applications/mimeapps.list and make sure that you have:
@EdP
did you run md5sum on 002-xorg.xzm from Razor and XFCE ISO's? is it the same?
also - on the attached image i see udev timeout which means that some emulated hardware did not get initialized. would be nice if you could track this down and change relevant qemu component to get rid of it.
ok - /etc/fstab stays in. would be good to have the udev rule before we go final.
@francois
i think you are referring to qmmp and this bug was closed in rc2. are you using old changes or something?
please check $HOME/.local/share/applications/mimeapps.list and make sure that you have:
Code: Select all
inode/directory=kde4-dolphin.desktop;
did you run md5sum on 002-xorg.xzm from Razor and XFCE ISO's? is it the same?
also - on the attached image i see udev timeout which means that some emulated hardware did not get initialized. would be nice if you could track this down and change relevant qemu component to get rid of it.
Please add [Solved] to your thread title if the solution was found.
-
- Full of knowledge
- Posts: 2090
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: Feedback and Bug Reports for Porteus v2.1 RC2
XFCE-32bit
Installt for testing on an Ext2 usb-stick
In porteus.cfg:
APPEND initrd=initrd.xz xfce changes=/porteus
is missing, so nothing is gonna be saved by default.
Installt for testing on an Ext2 usb-stick
In porteus.cfg:
APPEND initrd=initrd.xz xfce changes=/porteus
is missing, so nothing is gonna be saved by default.
Re: Feedback and Bug Reports for Porteus v2.1 RC2
Running fresh install on my main computer and unable to run Porteus. It freeze at udev stage but the 'welcome' sound of KDE4 desktop is played some seconds after.
I'm unable to run any versions of v2.1 rc2 so far and I'm unable to retrieve any logs of errors/events.
I'm unable to run any versions of v2.1 rc2 so far and I'm unable to retrieve any logs of errors/events.
NjVFQzY2Rg==
- Rava
- Contributor
- Posts: 5424
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Re: Feedback and Bug Reports for Porteus v2.1 RC2
@Hamza
have you also tried a text / non X version, too?
You can scroll up with the keyboard and make screenshots using a real (digital) camera, if there is something interesting to see, put that up, e.g. on tinypic and link it in your post...
___________________________________
With a fresh XFCe booting up, so far all is working as it should with v2.1 RC2 x86-64, seems some of my old settings fro, 2.0 made the system act weird...
___________________________________
Found another issue:
Trying to rename the label of a USB stick using gparted results in this error:
Is there really no newer version than a pre-*** from 2001? More than 12 years old?
have you also tried a text / non X version, too?
You can scroll up with the keyboard and make screenshots using a real (digital) camera, if there is something interesting to see, put that up, e.g. on tinypic and link it in your post...
___________________________________
With a fresh XFCe booting up, so far all is working as it should with v2.1 RC2 x86-64, seems some of my old settings fro, 2.0 made the system act weird...
___________________________________
Found another issue:
Trying to rename the label of a USB stick using gparted results in this error:
Code: Select all
Set partition label to "16GB_W_G" on /dev/sdb1 00:00:00 ( ERROR )
mlabel ::"16GB_W_G" -i /dev/sdb1
mlabel: invalid option -- 'i'
Mtools version pre6-3.9.8, dated 27 May 2001
Usage: mlabel [-vscVn] [-N serial] drive:
Cheers!
Yours Rava
Yours Rava
Re: Feedback and Bug Reports for Porteus v2.1 RC2
No, nothing. Even text mode doesn't works. I'm blocked at stage of "udev" just after "additional modules".have you also tried a text / non X version, too?
NjVFQzY2Rg==
- Rava
- Contributor
- Posts: 5424
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Re: Feedback and Bug Reports for Porteus v2.1 RC2
@Hamza
You also tried it with just 000-kernel.xzm and 001-core.xzm?
Notthing in your rootcopy? Have you checked the md5 of 000-kernel.xzm and 001-core.xzm?
Have you some extras in your kernel / APPEND line in porteus.cfg?
I presume there is nothing to be seen on screen for a screenshot via camera to be taken?
You also tried it with just 000-kernel.xzm and 001-core.xzm?
Notthing in your rootcopy? Have you checked the md5 of 000-kernel.xzm and 001-core.xzm?
Have you some extras in your kernel / APPEND line in porteus.cfg?
I presume there is nothing to be seen on screen for a screenshot via camera to be taken?
Cheers!
Yours Rava
Yours Rava