Loving Mageia3 but opera is messed up?

[jtwdyp]

I'm still getting used to Mageia3. As a multi-booter running multiple Linux, I'm not very surprised to find that some things work differently from one distribution to the next. So far I'm pleased with Mageia's overall performance... But there are two things I've noticed that I'd like
to understand...

Opera works about the same as the opera implementations in any of the other Linux I've got installed. Just like the others, the latest version of Opera insists on resetting the default search engine to google upon every browser restart. But it's not that hard to simple reset the default to one of my choosing before I start using the search bar...

And again this works. But the visual representation of the assorted preferences dialogs is messed up:

In the image you can also see that the tab bar contains ghost images of closed tabs... I note that everything works, it's just a little bit visually disconcerting.

What's up with that??? Has anybody else experienced it??

I don't think it's an NVidia issue as every thing else is rendered beautifully...

Next: what I mean by "X tty!=7"... {sorry to take so many words to explain what I mean... But my brain doesn't think concisely.}

I'm a startx user. With systemd that means I set default.target to multi-user.target rather than graphical.target, and when/if I'm ready for X to start I use startx from the tty command line...

Used to be that no mater which one of the 6 tty (virtual consoles) set up by default in most distros I'm using when I initialize X with startx, X's display screen would effectively be on tty7... That is if I used <ctrl>+<alt>+<Fkey> {where <Fkey> was any one of the first six Fkeys} I would find myself in the corresponding tty, IE <ctrl>+<alt>+<F3> would put me in tty3.

Once in one of the tty, I no longer needed to use the <ctrl> key but could switch from one tty to the next with just <alt>+<Fkey>... But if I did an <alt>+<F7> I'd find myself back on the X server's screen.

I's also worthy of note that If I locked up my desktop so bad that I couldn't logout, I could (if the <ctrl>+<alt>+<Fkey> shortcut was still working) switch back to the tty from which I'd run startx and kill the X server with a ^C...

In recent months I've noticed that some distros will sometimes hijack one of the 6 tty's (or at least it's <alt>+<Fkey> shortcut leaving me with just 5 viable tty including the one busy running the startx command...

But Mageia 3 is the first distro that I've seen consistently reuse the SAME tty that I ran startx on for the X server's screen Making it impossible to switch back to it and interrupt the X server with ^C... Though nothing stops me from logging in to one of the other tty as root and using the kill command...

My question is: was this done deliberately? If so why?

[isadora]

My advise jtwdyp, to have better results for finding solutions for all your issues:
use one topic for each problem, this makes chances finding a solution greater, and keeps the forum organized.

Thanks, and a nice day!

[doktor5000]

For opera, this works fine here.
Maybe it's a problem with old opera settings or the theme you're using.
Please try with a freshly created user.

For the other issue, startx is not supported anymore, as systemd is used for login session control.
Then you would have X server on tty1, by the way. But please start a separate thread for that, as advised already by isadora.

[jtwdyp]

My advise jtwdyp, to have better results for finding solutions for all your issues:
use one topic for each problem, this makes chances finding a solution greater, and keeps the forum organized.

Thanks, and a nice day!

OK... lesson learned, will try to remember that from now on...

For opera, this works fine here.
Maybe it's a problem with old opera settings or the theme you're using.

I suppose that could be. I did try to reuse an existing ~/.opera directory to preserve my custom standard_menu_1.ini, bookmarks, etc... But this method worked fine with my recent reinstall of Sabayon which allegedly uses the same opera version...

Please try with a freshly created user.

Will certainly test that before manually recreating all my opera settings from scratch...

[jtwdyp]

For opera, this works fine here.
Maybe it's a problem with old opera settings or the theme you're using.
Please try with a freshly created user.

Will certainly test that before manually recreating all my opera settings from scratch...

As you can see the freshly created user account's 1st opera session did the same thing. so it's not peculure to my opera configuration or other user settings... And as you may recognize, this was from an xfce session, which eliminates my chosen DE/WM of E17's unusual ways as a candidate for the problem as well.

Are you sure it's the same version that works properly for you?

I got:

[doktor5000]

Yes, as that's the only opera version available currently for Mageia 3.

Bildschirmfoto2_21.png (139.31 KiB) Viewed 3898 times

Please show the output of

Code: Select all

grep -i driver /var/log/Xorg.0.log

[jtwdyp]

Code: Select all

 ~
UnderTree=-> grep -i driver /var/log/Xorg.0.log
[  1341.822] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[  1341.822]    X.Org Video Driver: 13.1
[  1341.822]    X.Org XInput driver : 18.0
[  1341.951] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[  1341.960]    ABI class: X.Org Video Driver, version 13.1
[  1342.057]    Module class: X.Org Video Driver
[  1342.058] (II) v4l driver for Video4Linux
[  1342.058] (II) NVIDIA dlloader X Driver  304.88  Wed Mar 27 14:28:14 PDT 2013
[  1342.058] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  1342.704] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[  1343.277]    Module class: X.Org XInput Driver
[  1343.277]    ABI class: X.Org XInput driver, version 18.0
[  1343.277] (II) Using input driver 'evdev' for 'Power Button'
[  1343.359] (II) Using input driver 'evdev' for 'Power Button'
[  1343.361] (II) No input driver specified, ignoring this device.
[  1343.361] (II) No input driver specified, ignoring this device.
[  1343.362] (II) No input driver specified, ignoring this device.
[  1343.363] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[  1343.364] (II) Using input driver 'evdev' for 'ImExPS/2 Logitech Explorer Mouse'
[  1343.366] (II) No input driver specified, ignoring this device.
 ~
UnderTree=->


[doktor5000]

Also using nvidia driver here ...

[ghmitch]

I am not sure I understand what is going on here. I've changed my preferred search engine in Opera and am not seeing a nag screen NOR am I seeing Google resurrected as a result. OR ... is this occurring only after you reboot the system?

[jtwdyp]

Also using nvidia driver here ...

:Sigh: I guess I can live with it... except for needing to reset my default search engine and occasionally using {tools:Quick preferences:Edit site preferences} to add/remove javascript permissions, I don't spend much time in the preferences dialogs anyway... And those two functions I do often enough that the poorly displayed dialog isn't much of a problem for me... {I could almost complete either of those two tasks blindfolded}

Though if anyone else has this problem, or thinks they know what the matter could be, please do speak-up...

Any all suggestions welcome.

I am not sure I understand what is going on here. I've changed my preferred search engine in Opera and am not seeing a nag screen NOR am I seeing Google resurrected as a result. OR ... is this occurring only after you reboot the system?

I'm not sure what you mean by a nag screen. I took snapshots of the appearance issues I'm having with the preferences dialogs whenever I decide to ditch google as a default. Which for me happens every time I start an opera session.

And no I don't have to reboot the system for google to reclaim default search engine status. All I gotta do is start a new opera session. That problem isn't limited to Mageia BTW see:
http://my.opera.com/community/forums/topic.dml?id=1648442
for more details on that.

[doktor5000]

Well, you could take a look at https://bugs.mageia.org/show_bug.cgi?id=6103

[jtwdyp]

Well, you could take a look at https://bugs.mageia.org/show_bug.cgi?id=6103

I spent some time poking around that URL, and as far as I can tell it was talking about a problem between nvidia drivers and kde...

And nothing I read seemed to indicate that the problem only affected 1 single application...

The only application that is getting this video corruption in my case is Opera.

I previously ruled out any SINGLE {DE/WM} by having the problem regardless if I started E17 or xfice.
I eliminated the possibility that it was old settings in my home directory by having the problem with a new user.

And now I've eliminated the Nvidia driver itself by having the same problem using the vesa driver instead with said never customized new user running xfce...



A copy of the Xorg.0,log from that session can be found at:

http://pastebin.com/ckSpwqwr

Since for the most part Opera works well enough, for my purposes I think I'll just live with it. If I ever find a solution, or if some future upgrade fixes the problem, I'll post that here and then mark thread solved.

Thanks for the suggestions!

[doktor5000]

You may also want to take this up to opera forums, as on other configurations it works here just fine.

[jtwdyp]

You may also want to take this up to opera forums, as on other configurations it works here just fine.

That's a good idea... But since the Opera 12.15 installed to any of my other 4 Linux distros on the same machine, via their respective package managers, (zypper/apt-get/equo) do not do this, They will most likely call it a distro specific problem...

:sigh:

Still it might be worth a try.

Thanks