FS#24408 - Latest E17 Update Broke - Error Loading Modules Popups When Logging In

Attached to Project: Arch Linux
Opened by Das (DasFox) - Monday, 23 May 2011, 20:59 GMT
Last edited by Ronald van Haren (pressh) - Friday, 01 July 2011, 16:04 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Latest E17 Update Broke - Error Loading Modules


Additional info: Running Arch x86 - E17
* package version(s) E17 SVN through pacman -Syu updates
* config and/or log files etc.


Steps to reproduce: Latest E17 updates seems to have broke something, now when logging into E17 I am
given around 30 popup messages that there was a problem loading modules.

Please see the attached image.

I hope we can get a fix for this soon...

THANKS
   e17.jpg (959 KiB)
This task depends upon

Closed by  Ronald van Haren (pressh)
Friday, 01 July 2011, 16:04 GMT
Reason for closing:  No response
Comment by Ronald van Haren (pressh) - Tuesday, 24 May 2011, 12:08 GMT
I think you either didn't update all packages or you should try to run e17 without a user directory.
Comment by Das (DasFox) - Sunday, 05 June 2011, 04:11 GMT
I did the update properly and updated everything it had to update at the time, it is not user error...

It might run fine if I create a new user or without it as you suggest but either way I don't want to have to create my user account over, I have to much stuff going on with.

I've used Linux 11 years I'm a Tech and a Geek and I can honestly tell you that last update of E broke for me....


THANKS
Comment by Ronald van Haren (pressh) - Monday, 06 June 2011, 10:04 GMT
Remember that e17 is still unstable/alpha quality and that therefore config breakages may or may not occur at any time. It is impossible for me to say if that is what happened from the screenshot you posted. Easiest way to see is to move your e17 config directory somewhere else and see if it works (you can always copy it back later and should not take you more than 30 seconds to tell).

If it doesn't work I need some output to see what is happening. If it does work you can either look at the output if there is something obvious, cross your fingers and hope a new snapshot will solve it, or continue using your new config. I understand that you don't want to create a new config but that is a risk you take when running alpha quality software.


Loading...