[intrepid] gtk2-engines-ubuntulooks can't be installed

Bug #285417 reported by Nizar Kerkeni
88
This bug affects 10 people
Affects Status Importance Assigned to Milestone
human-theme (Ubuntu)
Invalid
Undecided
Unassigned
ubuntulooks (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: gtk2-engines-ubuntulooks

intrepid beta on amd64
after to day update i cant install the blubuntu-theme package due to gtk2-engines-ubuntulooks dependency problem :

nizarus@dell:~$ sudo apt-get install gtk2-engines-ubuntulooks
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  human-theme ubuntu-artwork ubuntu-desktop
The following NEW packages will be installed:
  gtk2-engines-ubuntulooks
0 upgraded, 1 newly installed, 3 to remove and 1 not upgraded.
Need to get 41.7kB of archives.
After this operation, 377kB disk space will be freed.
Do you want to continue [Y/n]?

Related branches

Revision history for this message
Julian Alarcon (julian-alarcon) wrote :

I confirm that.. I made an upgrade from Hardy to Intrepid, and I get this little bug.

Changed in ubuntulooks:
status: New → Confirmed
Revision history for this message
Dave roi (daveroi) wrote :

I confirm this exists on both an upgrade and a clean install using the RC live CD.

Revision history for this message
David Santamaría Rogado (howl) wrote :

This bug is still there, tropic is also affected, it can be installed because he package doesn't have ubuntulooks as dependence but when trying to use gnome advise that ubuntulooks need to be installed in order to proper show the theme.

In fact the bug is that gtk2-engines-ubuntulook package replaces ubuntu-artwork < 7, the actual version of ubuntu-artwork is much higher but it doesn't care. Can be deleted the replace rule in ubuntulooks as a possible fix?

And also, this is another bug but very close to it, tropic-theme should depend in ubuntulooks.

Revision history for this message
elli222 (elliot-purdy) wrote :

To fix this, you need to make a modification to the Human-Theme package, and the gtk2-ubuntulooks package.
In gtk-ubuntulooks package:
the ./usr/share/themes/Human directory should be renamed to somthing else, like
 /usr/share/themes/Human-Ubuntulooks
the conrol file line Replaces: ubuntu-artwork must be removed

in Human-Theme package:
the control file must be edited so that it doesn't conflict with ubuntulooks nor replace it.

I have done these, and rebuilt the deb packages with these changes in them. They appear to work flawlessly.

What a stupid reason to conflict!

if you want my packages, just ask me. I don't really feel confident in uploading them here since nobody knows who i am. But if there is demand i will upload them :)

Revision history for this message
Greg Unger (mr-ory) wrote :

i've noticed this bug as well. i'm currently running linux mint felicia, and i can't install the latest update to mint-artwork-gnome because it depends on ubuntulooks.

@ elli222: i would be interested in your deb packages. or if you could point me to the location of the control files in the respective source packages i would recompile them myself (i'm not afraid of compiling source, but i'm no whiz :) ).

Revision history for this message
elli222 (elliot-purdy) wrote :

Instructions are VERY hard to explain, but i will have a go regardless.

Download the appropriate deb packages for your architecture.
Extract the "control.tar" and the "data.tar" from the package.deb into a "working directory" these directories should be separate, and have nothing inside that is not relevant.
There should now be one folder, called usr, and one file called control.
Create a new directory called DEBIAN, in capitals. Put the control file in there.
Edit the control file. Depending on what package it is:
For example, you are editing the new-human control file, you want to remove the ubuntulooks package from replaces AND conflicts. Also (this is important) make the version number higher. Like, put an 'a' after it. then save.

Do the same to the other control file.

THIS IS VITAL!
In the ubuntulooks package, rename the directory /WORKINGDIR/usr/share/themes/Human to /WORKINGDIR/usr/share/themes/Human-Ubuntulooks

Now, go into the working directory's root. Open up a terminal there and type:
   dpkg-deb -b WORKINGDIR /packagename.deb

This will make a debian package called packagename.deb in the directoy you are currently in.

Install and enjoy, ask me for any help.

Revision history for this message
Greg Unger (mr-ory) wrote :

thanks elli222! your instructions made sense.

i also googled it, and found this howto: http://ariejan.net/2008/05/04/how-to-compile-packages-on-debianubuntu-by-hand/

different method, but same end results.

Revision history for this message
Bernhard (b.a.koenig) wrote :

Can confirm this bug on my intrepid.

Revision history for this message
Emilio (turl) wrote :
Revision history for this message
Emilio (turl) wrote :
Revision history for this message
Emilio (turl) wrote :

There are fixed packages on my PPA, if anyone wants them

My PPA: https://launchpad.net/~turl/+archive/

These were created with slightly modified versions of the debdiffs (I just changed intrepid-proposed to intrepid, PPAs won't allow intrepid-proposed)

Revision history for this message
Bryce Harrington (bryce) wrote :

Please do not subscribe ubuntu-core-dev to bugs, it spams too many people unnecessarily.

Revision history for this message
Martin Pitt (pitti) wrote :

Ken, AFAIR -ubuntulooks got deprecated some time ago, wasn't it? Would it actually be correct to drop the conflict, given that it was probably introduced to fix upgrades?

I'd appreciate if you could shed some light on how it is supposed to behave, and which packages are obsolete. Thanks!

Revision history for this message
Kenneth Wimer (kwwii) wrote :

Yes, we removed ubuntulooks from the default installation during intrepid because it is simply no longer supported and in the meantime quite buggy. We included the conflict so that we can upgrade it properly but this can probably be removed now.

Revision history for this message
Bernhard (b.a.koenig) wrote :

But then it should probably be removed from the archives, I can still see it in aptitude:

> aps ubuntulooks
p gtk2-engines-ubuntulooks - 'ubuntulooks' theme for GTK+ 2.x

Revision history for this message
Ms_Angel_D (mrsangeld) wrote :

Would it be possible for someone to post a fix for this for intrepid I don't feel confident in trying to follow elli222's instructions.

Revision history for this message
Greg Unger (mr-ory) wrote :

@ MetalHellsAngel

Add Emilio's PPA to your sources.list. He posted a link to it earlier in this thread.

Edit /etc/apt/sources.list with your favorite text editor, and add
"deb http://ppa.launchpad.net/turl/ubuntu intrepid main"
to the end of the file.

Then update and upgrade apt. Once you've done that, you should be able to install ubuntulooks without any problems.

Revision history for this message
Ms_Angel_D (mrsangeld) wrote :

Thank you very much for explaining that Greg, I don't know how I missed the post. Also thank you very much for the quick reply.

Angel

Revision history for this message
Ms_Angel_D (mrsangeld) wrote :

This bug still exists in Jaunty

Revision history for this message
Casey J Peter (caseyjp1) wrote :

@ Kenneth and Martin

Still an issue with jaunty.

You probably SHOULD remove the conflict as there a ton of themes out there that depend on ubuntulooks, and buggy or not, most users would just click "yes" to remove the default human stuff by accident which would MORE bork their systems than just getting rid of that little conflict as well as add unnecessary grief with bug reports and messed upgrades down the road.

@ Emilio - in the meantime thanks for the ppa. Solved my problem big time with Orange-LinstaBlackPlastic theme issues.

Revision history for this message
Dan Martin (bithooked) wrote :

This still exists in Karmic. I really don't understand this. If there's a PPA, then there's a bzr fork with the fixed code to resolve this issue. Everyone says "file bugs". But here's an example: a bug's been filed, the code has been written, and is in bzr which means it can be easily patched upstream in a matter of minutes. Yet it isn't.

With DVCS (bzr), launchpad, etc, this community has extremely efficient tools, yet we don't seem to be operating nearly as efficiently as we should. This simple-to-fix bug was filed 1 year and nearly 3 releases ago. Is there something we in the community can do to speed up simple fixes like this that clearly aren't getting attention?

The ppa doesn't have Karmic packages for ubuntulooks, so the ppa cannot be used as a solution unless it is updated.

Revision history for this message
Ms_Angel_D (mrsangeld) wrote :

Emilio can you please update the fix for Karmic as this fix isn't working now.

Thanks,
Angel

Revision history for this message
Sam Townsend (stownsend42) wrote :
Revision history for this message
Sam Townsend (stownsend42) wrote :

After applying this, all you have to do is remove gtk2-engines-ubuntulooks from Conflicts and Replaces in human-theme.

Changed in ubuntulooks (Ubuntu):
assignee: nobody → Ubuntu Sponsors for universe (ubuntu-universe-sponsors)
Changed in ubuntulooks (Ubuntu):
assignee: Ubuntu Sponsors for universe (ubuntu-universe-sponsors) → nobody
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Much smaller debdiff to fix the issue.

Note this bug brakes upgrades from Hardy -> Lucid

Revision history for this message
Kenneth Wimer (kwwii) wrote :

So which of these fixes works properly? I like the idea of changing the name of the theme to ubuntulooks, it makes sense and avoids the problem of not being able to install the new version next to the old.

Revision history for this message
Sam Townsend (stownsend42) wrote :

Well, I've confirmed that my debdiff works in Karmic (it's copied straight from my PPA, which works) and it allows the Human-ubuntulooks to still exist. Considering that the package is unchanged in Lucid, it should work there too.

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Hi,

After reading all the posts, I don't even understand why we should keep this package in the archive for Lucid: the only rdepends in the archive is human-theme, because of the conflicts/replace, and installing it in a lucid environment will be quite bad.

I suppose this is why this bug report has not received any attention from the sponsors in a so long timeframe.

My opinion is that a removal for lucid would be better, rather than breaking upgrade from hardy to lucid (both LTS ).
Waiting for another motu's opinion on that topic

Fabrice

Revision history for this message
David Santamaría Rogado (howl) wrote :

Fabrice that is not the solution, the solution has been made by the users but is needed to be included. There are 3rd party themes that use this engine, so removal shouldn't be a solution.

Changed in ubuntulooks (Ubuntu):
assignee: nobody → Fabrice Coutadeur (fabricesp)
status: Confirmed → In Progress
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Hi,

I've tested upgrade from Hardy to Lucid with both packages (updated and not updated), and in both cases, gtk2-engines-ubuntulooks get removed by ubuntu-theme.
So no upgrade problem from Hardy to Lucid because of that.

Also, this mean that without modifying ubuntu-theme, this patch won't be of any use, as installing gtk2-engines-ubuntulooks will always uninstall human-theme and ubuntu-artwork.

Even if I still think the best thing to do is to delete this package from Lucid, to avoid users uninstalling necessary stuff, I'll add a task for human-theme and subscribe main-sponsors to have their opinion on this change.

Fabrice

Changed in ubuntulooks (Ubuntu):
assignee: Fabrice Coutadeur (fabricesp) → nobody
status: In Progress → Triaged
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

on the contrary, sponsoring this change for Lucid will led to upgrade problems from Hardy. So It may be sponsored only after lucid, but not before.
Please subscribe again Universe and Main sponsors after the release of Lucid.

Revision history for this message
Martin Pitt (pitti) wrote :

I also agree that we should just remove gtk2-engines-ubuntulooks from the lucid archive entirely. It's been obsolete since intrepid, human-theme replaces it, so I'd rather see third-party themes getting fixed.

Revision history for this message
Martin Pitt (pitti) wrote :

2010-02-11 08:41:33 INFO Removing candidates:
2010-02-11 08:41:33 INFO ubuntulooks 0.9.12-12 in lucid
2010-02-11 08:41:33 INFO gtk2-engines-ubuntulooks 0.9.12-12 in lucid amd64
2010-02-11 08:41:33 INFO gtk2-engines-ubuntulooks 0.9.12-12 in lucid armel
2010-02-11 08:41:33 INFO gtk2-engines-ubuntulooks 0.9.12-12 in lucid i386
2010-02-11 08:41:33 INFO gtk2-engines-ubuntulooks 0.9.12-12 in lucid ia64
2010-02-11 08:41:33 INFO gtk2-engines-ubuntulooks 0.9.12-12 in lucid powerpc
2010-02-11 08:41:33 INFO gtk2-engines-ubuntulooks 0.9.12-12 in lucid sparc
2010-02-11 08:41:33 INFO Removed-by: Martin Pitt
2010-02-11 08:41:33 INFO Comment: superseded by gtk2-engines-murrine in intrepid, LP #285417
2010-02-11 08:41:33 INFO 7 packages successfully removed.

Changed in ubuntulooks (Ubuntu):
status: Triaged → Fix Released
Changed in human-theme (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.