Debris 2.0 RC1

[Renegat3]

Changes in RC1:

No really much since we're closing in on the final.

- removed the "X server failsafe" routine, since it caused even more trouble in the end.
+ ePDFview scrolls the pages via mouse wheel again.
+ Ubuntu security updates.
+ Code fixes in shell scripts

R3

[JR]

Downloaded & installed as soon as I saw your post, couldn't wait.
Running nicely, no problems whatsoever. Swap activation OK now,
Audacious defaults to ALSA plugin so no need to change that.
I've got latest Adobe Flashplayer running, Wine + IrfanView as photo viewer,
Xine to play videos, nVidia graphics card driver with 3D support.
As I said, no issues. Yet ... 2 things I must bring to your kind attention:

Please consider opening a 'Testing' subforum for 2.0 RC1, just in case
somebody else is more successful bug hunting than me 

And the marketing department might wish to add a www.debrislinux.org
Firefox bookmark. (Haven't you had one before?)

Good job!

JR

[Renegat3]

Please consider opening a 'Testing' subforum for 2.0 RC1, just in case
somebody else is more successful bug hunting than me 

Done.

And the marketing department might wish to add a www.debrislinux.org
Firefox bookmark. (Haven't you had one before?)

The problem is, that FF switched from a simple html file, to save the bookmarks in a database-type of file. Unfortunately, in that file, they also save the translation of some of the entries of the bookmarks menu. So, if I make a bookmark with a German locale, some part of the bookmarks menu will be saved in German too. No matter what the actual system locale will be, certain parts of the menu will be in German - just because of the saved bookmarks. Ingeniously designed...
I tried to go around it somehow, but I couldn't do it. In the end I just dropped the bookmark and focused on more pressing issues. Perhaps I revisit the issue at some point. It is actually bugging me.

R3

[pianonut]

Although I've downloaded debris before, last night was my first live-disk testing session.
Beautiful!
I have one comment:  When I chose to restart at the end of my live-disk session, the disk popped out
as expected but a set of error messages appeared (in green - sorry but didn't record the actual error
message).  Have others had the same result?

Do note that I had established a root password and had mounted sda1 so that I had access to my usual
home partition but by the time I ended the session I had umounted sda1 so that 'locate' would only work over
the debris filesystems.

I installed aptitude,flashplayer (via the .tar.gz version), and a few other applications with no problems.  I'm not sure
what debris does with the update-manager.  Does this update the ubuntu hardy packages or debris packages?  I suppose that info
is in sources.list.

Now I want to try debris on some systems with minimal RAM and/or troublesome hard disks...
Many thanks for your hard work!

     pianonut

[Renegat3]

I have one comment:  When I chose to restart at the end of my live-disk session, the disk popped out
as expected but a set of error messages appeared (in green - sorry but didn't record the actual error
message).  Have others had the same result?

Yes, I have one system with an old CDR drive where those I/O errors appear occasionally. I can't pin it down, though. Could be the IDE controller, or an issue with optical drive, or both.

I installed aptitude,flashplayer (via the .tar.gz version), and a few other applications with no problems.  I'm not sure
what debris does with the update-manager.  Does this update the ubuntu hardy packages or debris packages?

Both.

Now I want to try debris on some systems with minimal RAM and/or troublesome hard disks...
Many thanks for your hard work!

Thank you.

R3

[MoonMind]

I have one comment:  When I chose to restart at the end of my live-disk session, the disk popped out
as expected but a set of error messages appeared (in green - sorry but didn't record the actual error
message).  Have others had the same result?

Yes, I have one system with an old CDR drive where those I/O errors appear occasionally. I can't pin it down, though. Could be the IDE controller, or an issue with optical drive, or both.

Same here on two dated boxes - no critical problem whatsoever, though you might have to switch off manually in some cases. Seems to happen on laptops because after eject, the drive can no longer be handled by the tools running (it needs to be closed manually). But I recall that happening on other old systems, too.

M.

[Renegat3]

Seems to happen on laptops because after eject, the drive can no longer be handled by the tools running (it needs to be closed manually).

Not quite. There should be one error message, saying it can't close the tray - or something like that. However, the controller can still communicate with the drive. That's why you get the "tray open", or "can't close" message. The I/O errors occur, if the controller can't "talk" to the drive anymore - hence the Input/Output errors.
Come to think of it, it actually be a firmware issue/bug of the optical drive. After getting the tray-open command, it just goes bye-bye. OTOH since my drive is a CDR which still works nicely and also ejects the CD after burning without hanging itself up...

Well, as I said, I can't pin it.

R3

[alloydog]

This has been around for donkey's ears. I remember it from BeatrIX days. I still get it on laptops if the tray is left open when you hit enter.