Bug 11597 - Firefox 24 - improper borders of dropdown menus
Summary: Firefox 24 - improper borders of dropdown menus
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-04 22:27 CET by darkduck
Modified: 2013-11-09 10:55 CET (History)
6 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
screenshot with the missing menu borders (36.09 KB, image/png)
2013-11-04 22:41 CET, darkduck
Details
menu with borders (31.24 KB, image/png)
2013-11-04 23:04 CET, Florian Hubold
Details
urpmi-log (60.52 KB, text/plain)
2013-11-09 00:40 CET, darkduck
Details

Description darkduck 2013-11-04 22:27:33 CET
Description of problem:
When using Firefox 24 (currently in updates-testing) in Mageia 3 KDE 64-bit, the dropdown menus at the top of the windows don't have proper borders/shading, especially on the left part of the menu. It makes the menu barely usable.


Version-Release number of selected component (if applicable):
Firefox 24.1.0


How reproducible:
Use the drop-down menu at the top. For the best effect, hide (unselect) the Menu bar checkbox.


Steps to Reproduce:
1.Hide Menu bar
2.Select Firefox - New Tab menu
3.The new list of the New Tab menu items does not have proper borders.


Reproducible: 

Steps to Reproduce:
Comment 1 darkduck 2013-11-04 22:41:14 CET
Created attachment 4475 [details]
screenshot with the missing menu borders

CC: (none) => darkduck

Comment 2 Florian Hubold 2013-11-04 23:02:38 CET
Looks good here. What theme do you use?

CC: (none) => doktor5000

Comment 3 Florian Hubold 2013-11-04 23:04:35 CET
Created attachment 4477 [details]
menu with borders
Comment 4 darkduck 2013-11-04 23:08:19 CET
(In reply to Florian Hubold from comment #2)
> Looks good here. What theme do you use?

Desktop theme = Air.
Window Decorations = Oxygen.
Comment 5 claire robinson 2013-11-05 08:27:10 CET
I was about to validate the update :\

Is the problem relieved if you quit firefox then
$ mv ~/.mozilla ~/.mozbak

and then restart firefox. Or create a new system user and log in as the new user then test firefox there.

This helps to rule out a possible settings or extension issue.
claire robinson 2013-11-05 08:29:15 CET

CC: (none) => eeeemail, luigiwalser

Comment 6 darkduck 2013-11-05 21:24:40 CET
(In reply to claire robinson from comment #5)
> I was about to validate the update :\
> 
> Is the problem relieved if you quit firefox then
> $ mv ~/.mozilla ~/.mozbak
> 
> and then restart firefox. Or create a new system user and log in as the new
> user then test firefox there.
> 
> This helps to rule out a possible settings or extension issue.

Unfortunately, this does not help... 8-(
Comment 7 Bill Wilkinson 2013-11-07 13:45:46 CET
Could not reproduce using kde/oxygen-air and default firefox theme.  Nuvola (ff theme) also works normally.

CC: (none) => wrw105

Comment 8 darkduck 2013-11-07 13:47:45 CET
Any additional help from me to help with the bug? Any logs/debugs/etc? I am happy to help, just guide me. :)
Comment 9 claire robinson 2013-11-07 15:10:01 CET
Can you ensure you've updated any relevant packages from the list here please.
https://bugs.mageia.org/show_bug.cgi?id=11370#c20

Also could you say what graphics card you use and with which driver

lspcidrake will give you some help here

Can you then change the driver to use vesa and reboot and see if that solves the problem.

Firefox 24 uses hardware rendering.
Comment 10 darkduck 2013-11-07 21:47:27 CET
Card:NVIDIA GeForce 8100 to GeForce 360: NVIDIA Corporation|G86M [GeForce 8400M GT] [DISPLAY_VGA] (rev: a1)

I am not quite sure I understand how I can update all the packages from that list. Some of them are not installed in my system (libsqlite3-devel), others have older version, but MCC does not offer the update (libsqlite3 has version 3.7.16.1 but the list show 3.7.17-1)
Comment 11 darkduck 2013-11-07 22:26:15 CET
I tried to activate VESA driver in MCC instead of NVIDIA. After reboot, the process hangs with a message about Plymouth and login prompt on a black screen. I had to manually revert /etc/X11/xorg.conf from backup in another TTY to make the system boot.
Comment 12 James Kerr 2013-11-07 23:35:24 CET
(In reply to darkduck from comment #10)
To install all of the packages in the list, if you have a 64bit installation, you need to enable core32bit/updates_testing as well as core/updates_testing.
Comment 13 darkduck 2013-11-07 23:48:42 CET
(In reply to James Kerr from comment #12)
> (In reply to darkduck from comment #10)
> To install all of the packages in the list, if you have a 64bit
> installation, you need to enable core32bit/updates_testing as well as
> core/updates_testing.

it doesn't help... 8-(
Comment 14 claire robinson 2013-11-08 07:34:08 CET
It's not straight forward unfortunately. The lib's listed will actually be lib64's on a 64bit system. You shouldn't install the 32bit libs or enable the 32bit Testing media for this update.

MageiaUpdate doesn't 'see' the updates in Testing as the media is not marked as an update media by default. Also the MCC tool used to edit your medias will not allow you to put a tick in that column by default.

Please use, as root, 'drakrpm-edit-media --expert' and place a tick in the Updates column against Core Updates Testing. You can then enable that media and MageiaUpdate will be able to see those packages.

Please manually select them rather than installing everything from Testing and then disable the media again. There is a QA wiki page with pictures here:
https://wiki.mageia.org/en/Enabling_the_Testing_media

Thanks!
Comment 15 darkduck 2013-11-08 23:30:09 CET
(In reply to claire robinson from comment #14)
> It's not straight forward unfortunately. The lib's listed will actually be
> lib64's on a 64bit system. You shouldn't install the 32bit libs or enable
> the 32bit Testing media for this update.
> 
> MageiaUpdate doesn't 'see' the updates in Testing as the media is not marked
> as an update media by default. Also the MCC tool used to edit your medias
> will not allow you to put a tick in that column by default.
> 
> Please use, as root, 'drakrpm-edit-media --expert' and place a tick in the
> Updates column against Core Updates Testing. You can then enable that media
> and MageiaUpdate will be able to see those packages.
> 
> Please manually select them rather than installing everything from Testing
> and then disable the media again. There is a QA wiki page with pictures here:
> https://wiki.mageia.org/en/Enabling_the_Testing_media
> 
> Thanks!

I ticked the "update" checkbox for testing-update repository (not 32-bit), then reloaded the media.
Unfortunately, neither updater, not package installer shows newer versions. I checked for libsqlite3 and libnspr. They're not in the "Update" list, and installer still show the previous version.
Is there any way to force install/update the listed packages from update repository, maybe from a command line?
Comment 16 Dave Hodgins 2013-11-09 00:11:13 CET
Try "urpmi --auto-update".

CC: (none) => davidwhodgins

Comment 17 darkduck 2013-11-09 00:14:34 CET
(In reply to Dave Hodgins from comment #16)
> Try "urpmi --auto-update".

It gives quite a lot of packages for deletion due to missing packages. One of them, for example, is 
libqtwebkit2.2_4-2.3.2-1.1.mga3.i586


I wouldn't go for such an "update".
Comment 18 Dave Hodgins 2013-11-09 00:36:23 CET
Please run "urpmi --auto-update --debug 2>&1 | tee /tmp/urpmi-log.txt".
Feel free to say n to the update. Attach the file /tmp/urpmi-log.txt to
this bug report.
Comment 19 darkduck 2013-11-09 00:40:10 CET
Created attachment 4499 [details]
urpmi-log
Comment 20 darkduck 2013-11-09 00:40:34 CET
(In reply to Dave Hodgins from comment #18)
> Please run "urpmi --auto-update --debug 2>&1 | tee /tmp/urpmi-log.txt".
> Feel free to say n to the update. Attach the file /tmp/urpmi-log.txt to
> this bug report.

Done
Comment 21 Dave Hodgins 2013-11-09 08:21:27 CET
Thank you. I'm going to close this bug as invalid.
The problems have nothing to do with Mageia rpm packages.
The problem is caused by packages from packages.mageialinux.ru, and/or packages from dl.google.com.

The Mageia project can only support packages provided
by the Mageia project. If you choose to also install
packages from other package providers, you'll have to
work with those package providers, to solve problems
that do not exist, when using Mageia only packages.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 22 claire robinson 2013-11-09 10:55:11 CET
Thankyou for your efforts darkduck. In light of this and it being quite likely you have not had all the relevant packages installed I have validated the security update for firefox in bug 11370.  As a critical security update
for widely deployed software we cannot delay it any longer than necessary.

This will soon be pushed as an update for everybody to install and will at least resolve the issue of not having any relevant firefox packages installed from the Testing media.

I'm sorry we weren't able to resolve this for you. It may also be due to an incomplete mesa installation from Testing. Unfortunately when external medias are used it makes it impossible for us to debug/verify issues like this as we cannot know what has been installed/configured by any external packages. So far in our tests you have been the only person to report this issue, but thankyou for doing so.

Note You need to log in before you can comment on or make changes to this bug.