Bug 489612 - Cairo-Dock loses 3d and extra views when Fedora 10 update is applied.
Summary: Cairo-Dock loses 3d and extra views when Fedora 10 update is applied.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cairo-dock
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-10 22:08 UTC by Charlie Wyse
Modified: 2009-04-02 19:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-02 19:47:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
sysreport (489.23 KB, application/x-bzip)
2009-03-10 22:11 UTC, Charlie Wyse
no flags Details

Description Charlie Wyse 2009-03-10 22:08:10 UTC
Description of problem:
I installed cairo-dock and was able to selected many types of 3d views such as Mac OSX style, or caroussel.  A ran a "yum update" and this broke it to where now I just have default which is a 2d backdrop.

Version-Release number of selected component (if applicable):
cairomm-1.6.2-1.fc10.x86_64
pycairo-1.4.12-4.fc10.x86_64
cairo-1.8.0-1.fc10.i386
pycairo-devel-1.4.12-4.fc10.x86_64
cairo-dock-1.6.3-0.3.rc1.fc10.x86_64
cairo-dock-themes-1.6.3-0.3.rc1.fc10.x86_64
cairo-1.8.0-1.fc10.x86_64
cairo-devel-1.8.0-1.fc10.x86_64
cairo-dock-plug-ins-1.6.3-0.3.rc1.fc10.x86_64


How reproducible:
Fairly easy, I just install off of cd, then update.

Steps to Reproduce:
1. Install Fedora off of cd.  Update cairo-dock and cairo-dock-themes
2. Open cairo-dock and look at personalasation and see all the nifty 3d views.
3. run "yum -y update"
4. Open cairo-dock and look at personalasation and see only _default_ which is a 2d view and vastly less attractive.
  
Actual results:
ugly 2d views

Expected results:
purdy 3d views.

Additional info:
I went through the .spec and updated every package that was in there, but that didn't seem to cause it.  I'll include a sysreport with my package list.  Going through 1 package at a time and restarted X over this is becoming a bit teadious, I'm hoping whomever maintains this package could just give me a few to update rather than all 485 packages.

Comment 1 Charlie Wyse 2009-03-10 22:11:00 UTC
Created attachment 334725 [details]
sysreport

Updated sysreport

Comment 2 Charlie Wyse 2009-03-10 22:44:39 UTC
Problem starts with an update of 1 of these packages.  I updated firefox qt/pygtk and there dependencies and it broke, so something in here, does not like cairo-3d.  anyone?
  devhelp.x86_64 0:0.22-5.fc10                                                  
  firefox.x86_64 0:3.0.7-1.fc10                                                 
  pygtk2.x86_64 0:2.13.0-3.fc10                                                 
  pygtk2-codegen.x86_64 0:2.13.0-3.fc10                                         
  pygtk2-devel.x86_64 0:2.13.0-3.fc10                                           
  pygtk2-doc.x86_64 0:2.13.0-3.fc10                                             
  pygtk2-libglade.x86_64 0:2.13.0-3.fc10                                        
  qt.x86_64 1:4.4.3-10.fc10                                                     
  qt.i386 1:4.4.3-10.fc10                                                       
  qt-devel.x86_64 1:4.4.3-10.fc10                                               
  qt-mysql.x86_64 1:4.4.3-10.fc10                                               
  qt-x11.x86_64 1:4.4.3-10.fc10                                                 
  qt-x11.i386 1:4.4.3-10.fc10                                                   
  xorg-x11-server-Xephyr.x86_64 0:1.5.3-13.fc10                                 
  xulrunner.x86_64 0:1.9.0.7-1.fc10                                             
  xulrunner-devel.x86_64 0:1.9.0.7-1.fc10                                       
  zenity.x86_64 0:2.24.1-1.fc10

Comment 3 Charlie Wyse 2009-04-02 19:47:17 UTC
Todays update of new cairo-dock fixed the problem.  So... yea, closing ticket.


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