[SOLVED] LXDE Log-in issues

[MasterSplinter]

Greetings,

This is the LEAST of my issues at the moment but, for those who care to know about a user's experience: LXDE seems to have a unique issue that the KDE Desktop log-in doesn't. I've had this issue happen on two occasions (so far) that seemingly happen after playing around with modules. This is on a WYSE Thin Client V90L (800Mhz 512Mb RAM / 512Mb Flash HDD).

Issue:
32-bit V1.0 RC1:
Boot into LXDE Mode via GRUB or LILO (not sure of the default boot loader) and get to the GUI log-in screen. Typing in correctly the User and Password will make the screen go blueish-gray then white then take you back to the GUI log-in screen. You can type the correct credentials several times with out being able to pass the log-in screen.

Just as a test, I type in the wrong credentials, and there is no flash on the screen what so ever... the prompt goes back to user name seemliness. If I use the KDE log-in option at the GRUB/LILO prompt, there is no issue logging in.

---

On the first occasion this happened to me, I was installing Slax modules off the Slax site and just executing them naively by double clicking them. At the time, GParted modules was what I was playing with. After learning that wasn't the best way to operate modules, I reformatted the drive and started over. The second occasion I was a lot more careful about what I used. I placed converted (community recommended) modules into /porteus/modules/ without executing them at all. I also made sure that I did only one module at a time, as I tested their functionality. After discovering that LXDE was doing the exact same log-in issue as the first occasion, I removed all modules from /porteus/modules/, rebooted in to LXDE mode, and found that LXDE was still with a log-in issue.

I'd be happy to test any suggestions.

-MS

[fanthom]

"I was installing Slax modules off the Slax site"
slax modules comes (many times) with poor quality and ofter are outdated (fits slax perfectly but can cause troubles for Porteus). be careful with them.
when you are saving changes then removing of modules may be not enough as all updated files will be still present in changes folder/container. you may have to delete changes as well.
The best idea is to test untrusted modules in Always Fresh mode.

[MasterSplinter]

Posted after 1 minute 50 seconds:

"I was installing Slax modules off the Slax site"
slax modules comes (many times) with poor quality and often are outdated (fits slax perfectly but can cause troubles for Porteus). be careful with them.
when you are saving changes then removing of modules may be not enough as all updated files will be still present in changes folder/container. you may have to delete changes as well.
The best idea is to test untrusted modules in Always Fresh mode.

Thank you.

I've noticed that the /porteus/changes folder has sub folders in it, such as: /dev, /etc, /var, and /usr.

Is it okay to just delete the /changes/ folder? Will it recreate itself as needed?

yes, you can delete everything inside your /changes folder. You can back it up first if you want to keep anything.

all of the files inside the folders in /changes get mapped into the live filesystem at startup, after all modules are loaded, so the /changes directory is a mirror of the file structure in your root directory from the live system, but only has files that have been modified

if you boot with changes=/porteus/ again, it will repopulate your changes, with a new set.

Sweet. I'll try that.

___________________________________________________

That fixed it!

I renamed my /porteus/changes folder to /changes.old to test... and LXDE now lets me log in.

Thank you!!

I shall keep this in mind!



-MS

[Ahau]

Glad to hear it, MS!!

You can also use the "Always Fresh" boot option, which lacks the changes= cheatcode. This will ignore everything in your changes directory (or save.dat), and boot a clean install (except it will start up modules in /porteus/modules, apply rootcopy files and magic folders)

I actually quit using saved changes a while back -- I simply had too many porteus installs on my USB drive to spare room to save all their changes! Also, I play around with stuff too much, and mess things up, so I was always having to delete my changes and start over again. It's a bit of a pain sometimes, when I have to make sure that I save everything to my flash drive (or it is gone forever), but this way I can tool around to my heart's content, and everything I destroy will come back safe and sound on reboot

[brokenman]

One thing i love about Porteus, is that i can boot into 'always fresh' mode ALWAYS and i can go nuts. I can leave crap lying around, i can accidentally delete my entire /usr folder just to see what will happen. I can try things that i suspect will break porteus. If i want to save something permanently i save it to a hard drive. It's like having a bachelor house that automagically cleans itself .... and doesn't nag you about it.

[wread]

@brokenman
I know the issue of the display manager in LXDE; it happens to me only when I log in as root. If I log in as guest, the display manager behaves correctly.

IMO Ponce is the right man to solve it....

Cheers

I see you are now in br! Soon you will be samba server specialist
________________________________________________________________________________________________________
The Porteus Community never sleeps!