I created a new user accout, so as to test whether it was system-wide or user settings-related. It worked fine (for this test and the further ones, I tried 3 logins).
I removed ~/.config/xfce from my user files (I'm talking about the usual user, not the new one) -> issue still happened.
I removed all ~/.config/ from my user files -> no issue
I put back all the stuff piece by piece, trying to log in from times to times. I had no issue and I finally ended up with all my former config back and still no issue !
In the end, I couldn't isolate the guilty config file.
I suppose something was screwed in my panel config or something (which I believe is a bug in the first place since I don't remember messing much doing dodgy stuff with the command line), and while going through the process of isolating the bad file, I took the whole thing through a state where it got "cured". Sounds kinda silly, doesn't it ?
Anyway, while the issue was almost systematic, it has not happened since.
So long, bug. I guess I can close the report. I'll reopen if needed.
Again, I know the information provided is not worth much to the developper, but please tell us (users) what else to provide to help in such cases.
Ok, now it's weird.
I created a new user accout, so as to test whether it was system-wide or user settings-related. It worked fine (for this test and the further ones, I tried 3 logins).
I removed ~/.config/xfce from my user files (I'm talking about the usual user, not the new one) -> issue still happened.
I removed all ~/.config/ from my user files -> no issue
I put back all the stuff piece by piece, trying to log in from times to times. I had no issue and I finally ended up with all my former config back and still no issue !
In the end, I couldn't isolate the guilty config file.
I suppose something was screwed in my panel config or something (which I believe is a bug in the first place since I don't remember messing much doing dodgy stuff with the command line), and while going through the process of isolating the bad file, I took the whole thing through a state where it got "cured". Sounds kinda silly, doesn't it ?
Anyway, while the issue was almost systematic, it has not happened since.
So long, bug. I guess I can close the report. I'll reopen if needed.
Again, I know the information provided is not worth much to the developper, but please tell us (users) what else to provide to help in such cases.