When I try to login with “konqueror”, the browser crashes on the login page.
I don’t know what changed. This worked when I last logged in (Monday, as I recall). It does not work today. I have not done any software updates in the meantime, so it looks as if a forum/novell/attachmate change has caused this.
Login with firefox still works.
An update: I switched to KHTML (instead of WebKit). It no longer crashed. But it did not respond to clicking “Login” on the login screen.
I then turned off adblock, and was able to login but the forum home page looked a mess with KHTML. So I’m back logged in with konqueror, rekonq and akregator (which share the login cookie). I have not tried doing only the Adblock disable.
Hmm, although I said I did not update, it is possible that adblock updated its EasyList. I’ll experiment more when I next need to login.
Well, I am using only Konqueror, and don’t have any problems accessing the forums, neither with WebKit nor with KHTML. (although with KHTML the WYSIWYG editor doesn’t work, but that’s nothing new…)
But then, I have adblock disabled. Or rather it is enabled, but no single filter is activated.
Hm, actually I could just reproduce the crash on the login page that you mentioned with WebKit.
It seems to crash in the JavaScript engine.
I usually login with KHTML, since that’s my default engine that I prefer, so haven’t noticed earlier.
Yes, that’s what seemed likely to me. The login page loads. My credentials are filled in from kwallet, and then it crashes (with no further clicks from me). So it looks like javascript problems.
The crash happens in akregator (where I first noticed it), in rekonq and in konqueror.
Recently, I have been doing the login with akregator, and reading the forum with rekonq. I guess I can switch konqueror to KHTML, turn off adblock in konqueror, and go back to using akregator to login (it seems to be using konqueror or konqueror settings behind the scenes), and read the forums with rekonq which will still use WebKit.
Something changed since Monday. I’m not sure what.
The backtrace looked quite similar to the one in this bug report:
https://bugs.webkit.org/show_bug.cgi?id=110017
But that should be fixed since two years.:\
OTOH, I cannot reproduce a crash on the sites mentioned in that bug report. So it’s probably not related. (or the sites have changed…)
The crash happens in akregator (where I first noticed it), in rekonq and in konqueror.
All of them use libQtWebKit4.
Recently, I have been doing the login with akregator, and reading the forum with rekonq. I guess I can switch konqueror to KHTML, turn off adblock in konqueror, and go back to using akregator to login (it seems to be using konqueror or konqueror settings behind the scenes), and read the forums with rekonq which will still use WebKit.
You could also switch back to WebKit in Konqueror after logging in, or only switch to KHTML for logging in via the “View” menu.
Akregator uses the “KDE service association” for text/html (i.e. either khtml or kwebkitpart, which you can configure in Konqueror’s settings), just like Konqueror does.
So yes, it does use the “konqueror settings” for the HTML engine.
Something changed since Monday. I’m not sure what.
Probably. I cannot tell when I last tried to login using WebKit.
Still, WebKit shouldn’t crash.
I tried with other WebKit based browsers (rekonq5 and epiphany), and couldn’t reproduce the crash there, so it seems to be specific to QtWebKit4 (maybe it’s just too old? :P)
Unfortunately Qt4 is not really in development any more AFAIK (although I think there will still be a final bugfix release), and WebKit is even deprecated in Qt5 as they added Chromium’s engine (which was originally based on WebKit) recently instead, so I’m not really confident that this has a chance to be fixed…
I have had the same problem and resolved it by switching to KHTML to log in and then switching back to WebKit.
Today I noticed that KHTML reported a bug in the code which I think is that the opening tag is in a condition. Sorry the button for inserting code is missing and trying to put the code in manually creates an error.
Sorry, having problems with the previous post - cannot edit even though it still offers the option. The initial HTML tag in the page is inside a condition.
I am running into a new problem today.
I logged in this morning, at somewhere around 8:30 local time (approx 7 hours before now).
Around an hour ago, I found that I was not logged in. I had thought that the login cookie should be valid for at least 9 hours).
I could not login. Using “konqueror” with KHTML, clicking “login” on the forum page just redirects back to that forum page.
Using “konqueror” with WebKit, there seems to be a weird redirect loop.
Using “firefox”, I get a message “the page is redirecting in a way that cannot complete”.
I finally managed with qupzilla-qt5 (from the KDE:EXTRA repo).
With both “firefox” and “konqueror” (WebKit), I also tried login to the bugzilla. I had the same redirect problem.
Something seems to be broken somewhere.
I had/have similar problems here too. Also KHTML prints an error about the page redirecting to itself. And even osc (the OBS command line client) doesn’t work, it just hangs when I start it and it only comes back with an error message after minutes or even not at all until I kill it.
So yes, there definitely is a problem somewhere.
Strange though, Firefox does work fine here at the moment, including logging in to the forum and OBS. :\
It looks as if it might have been fixed. I was able to login with konqueror (and KHTML). It looked as if firefox login was working, but I did not complete the login because I don’t need to be logged in on many different browsers at the same time.
Indeed. I didn’t notice any problems any more this morning.
I’m logged in again with Konqueror now (here and in Bugzilla), and osc worked fine as well…
I spoke too early. It is back to broken (redirect loop) both with konqueror and firefox.
Since “chromium” seems to work, I’ll use that today.
Hm, it works fine here with both now.
But for Firefox I had to delete some cookies to make it work again (I also got that redirect loop), deleting all from opensuse.org and attachmate.com fixed it.
I configured konqueror for KHTML, and made sure adblock was off. I closed konqueror and akregator, which should delete session cookies. Then I reopened them.
Next, I logged into the forums with akregator. I got a NetIQ page saying that I was logged in for 540 minutes. Then I again opened the forum main page and it showed me logged out.
I repeated the closes and reopens, and this time tried to login with konqueror. And that got me the redirect loop.
Next, I tried midori, but it crashes on the login page. I guess whatever problem we have with WebKit and konqueror also happens with the gtk libraries for webkit. But “chromium” worked.
That won’t remove persistent cookies.
And I suppose those are the problem now.
So try to delete them explicitely, in Konqueror’s and/or Firefox’s settings.
Again, both work fine here now, Firefox only after deleting those cookies.
I guess whatever problem we have with WebKit and konqueror also happens with the gtk libraries for webkit.
And it’s totally unrelated to WebKit, as it happens in Firefox too.
My guess is that during the time there were problems, invalid cookies were sent. If your browser saved them, you still have the problem. Removing them manually should fix it.
A followup to this.
Today, I found myself logged out (and too soon).
I tried to login again. It did not use my saved credentials from “kwallet”
Looking closely, I noticed that the login was to “microfocus” instead of to “novell”.
So I tried that using Webkit, and it was fine (and saved credentials for future use). So I no longer need to switch to KHTML for logins.
This was probably all related to the switchover to microfocus.
Yes. When I logged into the forums today, I was suddenly hit with dozens of cookies wanting to be set for microfocus throughout the login process. I refused at first and exited Firefox, then fired Firefox back up and did a little online research. After that, I was ready to allow the microfocus cookies – at least for this login – and I am now in the forums.:\
Thanks for mentioning!
I didn’t notice the change today, because I stayed logged in.
But I logged out now and can confirm what you wrote. Konqueror “forgot” my credentials (because of the changed URL), but the login page didn’t crash WebKit any more.
Phew, thanks for that. This was getting a bit annoying. No problem on one system where I still use KHTML by default, but on another system I kept forgetting to switch to KHTML and often got a crash when wanting to reply to a post.