Mga7 and Konqeuror

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

Mga7 and Konqeuror

Postby rodgoslin » Jul 14th, '19, 06:12

Not sure whether this is a bug, or not. I use Konqueror as a file manage, since it's one of the best I've ever had to work with. I was a tad disappointed in Mga6 when Konqueror was stripped of one of it's best attributes, the sidebar. I had hoped it would be back in Mga7, but no such luck. However, I find an odd thing. Konqueror can only be deployed once, which is a bit disconcerting. And, having dismissed it, either by closing the window, or quitting the program, it cannot be started again. On clicking on the icon, the usual action flashing symbol at the cursor, comes on. There is a longish wait, the flashing disappears, and that is that. No Konqueror. I've tried raising it at the command line. There the normal prompt returns almost instantly and still no Konqueror. Running ps -ax, indicates that the process is still running. Killing the process brings back the ability to raise it. So quitting the program or closing the window, is not stopping the process, but i have no idea why a second instance of Konqueror cannot be raised, while the first is still running
rodgoslin
 
Posts: 492
Joined: Nov 19th, '11, 01:31

Re: Mga7 and Konqeuror

Postby ITA84 » Jul 14th, '19, 11:46

I've just tried this on my system (never used Konqueror before) and it has the same problem. Ran with gdb to see if there were any silent crashes or anything unusual, but it just spawns 3 threads that all exit normally, and then quits without errors (0 return code). Maybe it could be traced better, but you should open a bug report in any case. In the journal I could find these messages:

Code: Select all
lug 14 11:43:00 hpdv6 konqueror[4339]: Please register the custom scheme 'error' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler.
lug 14 11:43:00 hpdv6 konqueror[4339]: Please register the custom scheme 'help' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler.
lug 14 11:43:00 hpdv6 konqueror[4339]: Please register the custom scheme 'about' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler.
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::begin: Paint device returned engine == 0, type: 1
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::translate: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::setClipRect: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::font: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::setFont: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::setPen: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::setPen: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::setBrush: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QPainter::drawRects: Painter not active
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:02 hpdv6 konqueror[4339]: QWidget::paintEngine: Should no longer be called
lug 14 11:43:12 hpdv6 konqueror[4339]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
lug 14 11:43:35 hpdv6 konqueror[4339]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
lug 14 11:45:39 hpdv6 konqueror[4339]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
ITA84
 
Posts: 199
Joined: Mar 5th, '13, 18:15

Re: Mga7 and Konqeuror

Postby rodgoslin » Jul 14th, '19, 22:45

I've submitted a bug report on this. No reply yet
rodgoslin
 
Posts: 492
Joined: Nov 19th, '11, 01:31

Re: Mga7 and Konqeuror

Postby isadora » Jul 15th, '19, 08:07

Would be great, if you included link to your report. :)
..........bird from paradise..........

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
—Antoine de Saint-Exupéry
User avatar
isadora
 
Posts: 2744
Joined: Mar 25th, '11, 16:03
Location: Netherlands

Re: Mga7 and Konqeuror

Postby rodgoslin » Jul 15th, '19, 08:44

https://bugs.mageia.org/show_bug.cgi?id=25123

There's nothing in the report that was not in the post to the forum
rodgoslin
 
Posts: 492
Joined: Nov 19th, '11, 01:31

Re: Mga7 and Konqeuror

Postby dbg » Jul 16th, '19, 02:29

I added this to the bug report:

The fix is to start konqueror go to setting/performance
uncheck "Always try to have one preloaded instance"

press OK and konqueror will correctly close and can be restarted.
dbg
 
Posts: 70
Joined: Mar 30th, '11, 22:28
Location: Grants Pass, Oregon

Re: Mga7 and Konqeuror

Postby rodgoslin » Jul 16th, '19, 04:07

How odd. I did that and it did work. Konqueror closed and opened properly. On a whim, I re-ticked the "Always try to have one preloaded instance" option. and konqueror still opened and closed properly. I then re-booted the machine and it still worked properly. Looks like the problem lies in the initial set of conditions. It'll not help anyone opening konqueror for the very first time, without the knowledge of this fix.
rodgoslin
 
Posts: 492
Joined: Nov 19th, '11, 01:31

Re: Mga7 and Konqeuror

Postby rodgoslin » Jul 16th, '19, 09:29

I later unchecked the "Always try to have one preloaded instance" option, when I found that I had an unwanted window with Konqueror, whenever I re-booted the machine. I can't imagine why anyone would want to have something they hadn't asked for, automatically loaded.
rodgoslin
 
Posts: 492
Joined: Nov 19th, '11, 01:31


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron