| Summary: | Doesn't work at all - options to open new tabs disabled, 'unknown protocol konq' on startup | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | temp.o5kdx |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | stefano.crocco |
| Priority: | NOR | ||
| Version First Reported In: | 24.08.3 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Multiple dialogs on startup.
File menu disabled |
||
|
Description
temp.o5kdx
2024-11-22 01:54:48 UTC
Created attachment 176026 [details]
Multiple dialogs on startup.
Created attachment 176027 [details]
File menu disabled
I tried creating a Neon virtual machine, installing Konqueror and launching from the Alt-F2 launcher. It works correctly. How did you start Konqueror? Could you please check whether you have the same issue with a new user? If not, it means it's a configuration problem (In reply to Stefano Crocco from comment #3) > I tried creating a Neon virtual machine, installing Konqueror and launching > from the Alt-F2 launcher. It works correctly. > > How did you start Konqueror? Could you please check whether you have the > same issue with a new user? If not, it means it's a configuration problem It works on a new user account. How would I troubleshoot this? It's hard to tell, especially because that error message isn't produced by Konqueror itself but from one of the libraries that Konqueror uses. As first thing, you can try changing the option "When a new Tab is created" in the "General" tab of Konqueror configuration dialog to "Show My Start Page" and enter a directory in the field on the right. Now when you launch Konqueror, it should start in the directory you chose. If it works, it means that the problem lies in the fact that, for some reason, Konqueror isn't able to find the WebEngine part it needs to display the starting page. At this point, you can try entering a web address in the location bar and see if Konqueror is able to correctly display it. If this works, try entering konq:about in the location bar. If you see the introduction page, it means that the problem with the "konq" protocol only happens at startup. The next thing you can do is launching Konqueror from a terminal emulator like Konsole and look at the debug output. Unfortunately, most of the debug output is hidden by default. To enable it, you should launch Konqueror using the command: QT_LOGGING_RULES=org.kde.konqueror.debug=true konqueror which will show debug messages from Konqueror. You can also try looking at the ~/.config/kpartsrc file and check whether WebEnginePart is mentioned somewhere in it. (In reply to Stefano Crocco from comment #5) > It's hard to tell, especially because that error message isn't produced by > Konqueror itself but from one of the libraries that Konqueror uses. > > As first thing, you can try changing the option "When a new Tab is created" > in the "General" tab of Konqueror configuration dialog to "Show My Start > Page" and enter a directory in the field on the right. Now when you launch > Konqueror, it should start in the directory you chose. If it works, it means > that the problem lies in the fact that, for some reason, Konqueror isn't > able to find the WebEngine part it needs to display the starting page. At > this point, you can try entering a web address in the location bar and see > if Konqueror is able to correctly display it. If this works, try entering > konq:about in the location bar. If you see the introduction page, it means > that the problem with the "konq" protocol only happens at startup. When I do this, it simply launches the URL in my default browser, including for konq:about. Same behavior if I set Konqueror as my default browser. > The next thing you can do is launching Konqueror from a terminal emulator > like Konsole and look at the debug output. Unfortunately, most of the debug > output is hidden by default. To enable it, you should launch Konqueror using > the command: > QT_LOGGING_RULES=org.kde.konqueror.debug=true konqueror > which will show debug messages from Konqueror. Where do I find the logs? When I run this it just returns to the command prompt as though I had run it as konqueror &. No messages are shown. > You can also try looking at the ~/.config/kpartsrc file and check whether > WebEnginePart is mentioned somewhere in it. That file doesn't exist. (In reply to temp.o5kdx from comment #6) > (In reply to Stefano Crocco from comment #5) > > It's hard to tell, especially because that error message isn't produced by > > Konqueror itself but from one of the libraries that Konqueror uses. > > > > As first thing, you can try changing the option "When a new Tab is created" > > in the "General" tab of Konqueror configuration dialog to "Show My Start > > Page" and enter a directory in the field on the right. Now when you launch > > Konqueror, it should start in the directory you chose. If it works, it means > > that the problem lies in the fact that, for some reason, Konqueror isn't > > able to find the WebEngine part it needs to display the starting page. At > > this point, you can try entering a web address in the location bar and see > > if Konqueror is able to correctly display it. If this works, try entering > > konq:about in the location bar. If you see the introduction page, it means > > that the problem with the "konq" protocol only happens at startup. > > When I do this, it simply launches the URL in my default browser, including > for konq:about. Same behavior if I set Konqueror as my default browser. This makes me think that you choose to open html pages in an external application rather than display them inside Konqueror. Please, go to the File Associations page of Konqueror configuration dialog, expand the "text" element in the list and select the "html" entry (you can also enter text/html in the filter box to make finding the entry easier). Now, switch to the "Embedding" tab on the right: which entry is selected among those in the "Left Click Action in Konqueror" box? Try setting it first to "Use settings for text group" and, if nothing changes, to "Show file in embedded viewer". This should force Konqueror to always show html pages itself rather than opening in an external application. > > The next thing you can do is launching Konqueror from a terminal emulator > > like Konsole and look at the debug output. Unfortunately, most of the debug > > output is hidden by default. To enable it, you should launch Konqueror using > > the command: > > QT_LOGGING_RULES=org.kde.konqueror.debug=true konqueror > > which will show debug messages from Konqueror. > Where do I find the logs? When I run this it just returns to the command > prompt as though I had run it as konqueror &. > No messages are shown. Most likely, this is because you have preloading enabled in Konqueror. Go to the Performance page in Konqueror configuration dialog and ensure that both check boxes are unchecked. Launch again Konqueror, then close all windows (this is just to be sure that Konqueror has really been closed). At this point, you should be able to launch it again with QT_LOGGING_RULES=org.kde.konqueror.debug=true konqueror and see the debug output. > > > You can also try looking at the ~/.config/kpartsrc file and check whether > > WebEnginePart is mentioned somewhere in it. > > That file doesn't exist. Then the problem isn't there. > This makes me think that you choose to open html pages in an external > application rather than display them inside Konqueror. Please, go to the > File Associations page of Konqueror configuration dialog, expand the "text" > element in the list and select the "html" entry (you can also enter > text/html in the filter box to make finding the entry easier). Now, switch > to the "Embedding" tab on the right: which entry is selected among those in > the "Left Click Action in Konqueror" box? Try setting it first to "Use > settings for text group" and, if nothing changes, to "Show file in embedded > viewer". This should force Konqueror to always show html pages itself rather > than opening in an external application. This was what finally worked! Though I have no idea why it would not default to using the embedded viewer; I haven't seen or changed that setting since installing Konqueror. > Most likely, this is because you have preloading enabled in Konqueror. Go to > the Performance page in Konqueror configuration dialog and ensure that both > check boxes are unchecked. Launch again Konqueror, then close all windows > (this is just to be sure that Konqueror has really been closed). At this > point, you should be able to launch it again with > QT_LOGGING_RULES=org.kde.konqueror.debug=true konqueror > and see the debug output. Preloading was already turned off - even now starting this way simply returns to the command prompt. Now that the browser does render pages - if I set it to remember the previous session, then it opens up with the last open web page and 5 additional blank windows. Also it doesn't respect the default browser setting and hijacks it. Even if I change the default browser in Plasma system settings back to what I had before, after a while it reverts to Konqueror. (In reply to temp.o5kdx from comment #8) > Now that the browser does render pages - if I set it to remember the > previous session, then it opens up with the last open web page and 5 > additional blank windows. I couldn't reproduce this. Please, try opening the file ~/.local/share/konqueror/last_session (after shutting Konqueror down): there should be a line starting with "Number of Windows": what is the number reported in that line? > Also it doesn't respect the default browser setting and hijacks it. Even if > I change the default browser in Plasma system settings back to what I had > before, after a while it reverts to Konqueror. Does this happen every time you run Konqueror? If not, did it happen after you did something special? Since I have Konqueror as my default browser, I never observed this kind of behavior, so I need help to find out when it happens. You should, however, open different bug reports for both these issues. I'm going to close this one as the issue it was about has been solved. |