Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 335130 - xfce-panel should be updated to 1.6.4 when glib is >=dev-libs/glib-2.23
Summary: xfce-panel should be updated to 1.6.4 when glib is >=dev-libs/glib-2.23
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL: http://bugzilla.xfce.org/show_bug.cgi...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 15:04 UTC by Giovani M. Faccin
Modified: 2010-08-29 15:58 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Emerge --info (emergeinfo.txt,3.87 KB, text/plain)
2010-08-29 15:41 UTC, Giovani M. Faccin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Giovani M. Faccin 2010-08-29 15:04:31 UTC
Did an emerge --sync, followed by an emerge world

This installed on the amd64 system the dev-libs/glib-2.24.1-r1  (I'm not using ~amd64 for it in package.keywords, so it's the stable version).

Once I logged in xfce, the bug discussed here just happened:

https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/503633

To solve the bug, one has to update xfce-panel to version 1.6.4, which is currently marked as ~amd64 (the current stable version is 1.6.2).

Since dev-libs/glib-2.24.1-r1 has been set stable, xfce-panel-1.6.4 should also be marked stable, otherwise people will have the window borders bug when they run an emerge --world.

Reproducible: Always

Steps to Reproduce:
1. Install the latest stable glibc on amd64; that is libs/glib-2.24.1-r1
2. Use the latest stable xfce-panel on amd64; that is xfce-panel-1.6.2

Actual Results:  
The panels in xfce got window borders, as shown here:

http://launchpadlibrarian.net/37467747/shot.png

Expected Results:  
Panels should have no borders!!

To solve the issue, simply mark xfce-panel-1.6.4 stable on amd64 (and possibly on other archs as well).
Comment 1 Ross Smith 2010-08-29 15:15:21 UTC
I have glib 2.24.1-r1 and the xfce4-panel 4.6.4 installed and I don't see any window borders on my machine.   

if you could please attach the output of emerge --info to this bug.   Also,  what window manager and desktop manager are you using?
Comment 2 Giovani M. Faccin 2010-08-29 15:24:48 UTC
Hi Ross!

The bug happens with xfce-panel-4.6.2

The solution is to install xfce-panel-4.6.4 (the one you have installed, that's why you don't suffer the issue!)

xfce-panel-4.6.2 should be masked for users who upgrade to glib 2.24.1-r1

For the other question, I'm running compiz-fusion with emerald for windows, and the xfce-panel for "start menu".
Comment 3 Ross Smith 2010-08-29 15:31:35 UTC
Sorry I misread your bug report.   I've looked at what's stable, and the combo that fixes this bug is marked  as stable for most arches, so anyone with an updated system running arch should be fine.    are you seeing this on your gentoo install?   if so, I'd suggest an emerge --sync and a emerge -avuDN world and see if it is still occurring.

also,  please do attach the output of emerge --info to this bug.  Thanks. 
Comment 4 Giovani M. Faccin 2010-08-29 15:41:30 UTC
Created attachment 245236 [details]
Emerge --info
Comment 5 Giovani M. Faccin 2010-08-29 15:44:41 UTC
Comment on attachment 245236 [details]
Emerge --info

Here's the emerge --info

I removed xfce4-panel-1.6.4 ~amd64 from /etc/portage/package.keyworkds and then ran emerge -vuDNp world

No downgrade to version 1.6.2 was listed, so it looks just like you said: the combo is stable on the tree.

I just don't know how my system installed glibc without updating xfce-panel along it. Anyway, looks like it's solved.

Thanks!
Comment 6 Ross Smith 2010-08-29 15:51:38 UTC
(In reply to comment #5)
> I removed xfce4-panel-1.6.4 ~amd64 from /etc/portage/package.keyworkds and then
> ran emerge -vuDNp world

it's good practice to put both ~amd64 and amd64 in package.keywords.   just putting ~amd64 implies that portage will only install it if it's marked unstable.   Once it's stabilized, portage will try to find a different version.  

> Anyway, looks like it's solved. 

if you have permissions would you mark this as resolved? I don't have permissions to do it my self. 

Comment 7 Giovani M. Faccin 2010-08-29 15:58:12 UTC
Sure, there it is.

Thanks!