You are not logged in.
It's only a slight annoyance as everything seem to work fine otherwise, but an annoyance never the less.
I haven't been able to find a solution anywhere, though I'm not the only one suffering from this problem.
here my .xsession-errors: http://pastebin.com/c8gQ3vkP
There's probably something I've missed. There is after all still a lot I don't know.
Hope you can help.
Best regards.
Last edited by zacariaz (2012-07-02 14:04:39)
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
Are you using phonon-vlc? If so it's probably this.
Offline
Apparently the it's a bug revolving around ALSA, though that don't help me much.
yes I am using phonon-vlc (I think), but I'm afraid I don't see how that is relevant.
In any case, thanks for the link. Was an interesting read.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
From your errors zacariaz, I had a similar error with Amarok crashing on start up a couple of days ago.
The solution was to delete the Amarok config. files in my home (/home/???/.???).
One of the small annoyances with a rolling release such as Arch is you will come across conflicts with your old config. files not playing nice with changes to upgraded packages.
The solution that works for me (after a backup of course) is to boot into a live Linux such as "Parted Magic" & remove all my /home/???/.??? (config.) files. Rebooting back into your desktop you will find a vanilla KDE.
I have been using Arch for about four years now & have had to do this only twice.
The less harsh method would be to find & remove the problem config. file, but if you are not sure exactly what is misbehaving you can end up wasting more time than restarting with vanilla settings.
Last edited by straykat (2012-07-01 23:40:53)
Offline
From your errors zacariaz, I had a similar error with Amarok crashing on start up a couple of days ago.
The solution was to delete the Amarok config. files in my home (/home/???/.???).
One of the small annoyances with a rolling release such as Arch is you will come across conflicts with your old config. files not playing nice with changes to upgraded packages.
The solution that works for me (after a backup of course) is to boot into a live Linux such as "Parted Magic" & remove all my /home/???/.??? (config.) files. Rebooting back into your desktop you will find a vanilla KDE.
I have been using Arch for about four years now & have had to do this only twice.
The less harsh method would be to find & remove the problem config. file, but if you are not sure exactly what is misbehaving you can end up wasting more time than restarting with vanilla settings.
I am aware that there are certain problems from time to time, when deal with a rolling release, however, this issue occurred after a fresh install.
However, your advice was one of those I read about, though I didn't actually try it. The reason for that is simple. The reason I did a fresh install at all, was due to me deleting my entire config folder by mistake. I didn't think it was worth the effort to try and sort it all out. ![]()
In any case I did do something, though I don't recall what. It had to do with some sort of config script I think and it worked, so sorry for not remembering to mark the thread solved.
Will do so now.
Best regards and thanks.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline