gtk-qt-engine 1:1.1+svn20080816-0ubuntu4~hardy1~ppa1 stopped working on Hardy

Bug #270531 reported by JW on 2008-09-15
14
Affects Status Importance Assigned to Milestone
gtk-qt-engine (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: gtk-qt-engine

Linux my_machine 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux
KDE 3.5.10
Kubuntu 8.04.1

Yesterday I updated to gtk-qt-engine 1:1.1+svn20080816-0ubuntu4~hardy1~ppa1. After restarting kdm the use of KDE styles in GTK applications no longer works, nor is it available under System Settings (or Control Center).

I expected to still have KDE styles applied to my GTK applications. I am not seeing that at all. I am seeing the default boxy style (raleigh?).

Please tell me what information I can provide to help diagnose this. I also have KDE4 installed in case that matters.

Thanks!

giorgosts (tsipoti) wrote :

I can confirm this. Gtk-qt-engine works in kde4 but is broken in kde3.5.10

Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please try and recreate this bug using a version of the package from an offical Ubuntu repository (not a PPA).

 Thanks!

Changed in gtk-qt-engine:
status: New → Incomplete
JW (arch0njw) wrote :

Chris: understood. Is there a way I can find the owner of this particular package to let them know they uploaded something buggy?

JW (arch0njw) wrote :

Chris: Nevermind. I found the person -- they are also on the "Almost Kubuntu Bugs" alias.

giorgosts (tsipoti) wrote :

There is no such notice though on the front page of kubuntu, where the packages for kde4.1.1 are advertised, that the packages are personal and the kubuntu team does not even take bug reports. http://www.kubuntu.org/news/kde-4.1.1

JW (arch0njw) wrote :

Then it looks like the answer is...
$ sudo apt-get install gtk-qt-engine=1:0.8-1ubuntu2
... until the PPA package owner fixes this.

I agree that if these are going to be unsupported and otherwise dismissed on launchpad, there should be something stated on the Kubuntu page effectively saying (politely): "Don't bother reporting this bug on launchpad, because this is not supported."

I am now writing this in a much prettier Firefox with all KDE styles applied. Likewise, the GTK styles and fonts module is available via the System Settings.

Now to figure out how to get aptitude to obey my hold command on that package -- seems to want to ignore it. But that's a different issue.

I guess if PPA packages are not supported, this can get closed. I don't like that solution, but if thems the rules, then thems the rules.

TD-Linux (bztdlinux) wrote :

Hmm, I have a similar problem.

Oddly, this package IS in the official repositories, but the version reported is ppa1. Is this possibly from the Kubuntu KDE 4 repositories? If so, it's not named correctly.

Chris Coulson (chrisccoulson) wrote :

TD-Linux - This is in the Kubuntu KDE4 repositories, which is a PPA (not an officially supported Ubuntu repository). The versions of this package in Ubuntu can be found at https://launchpad.net/ubuntu/+source/gtk-qt-engine

JW - As this is describing a bug in a package not officially supported by Ubuntu, I'm going to close this bug report. I have mailed the maintainers of this PPA (kubuntu-members-kde4).

Please reopen this bug report if you can recreate the problem with the official package.

Changed in gtk-qt-engine:
status: Incomplete → Invalid
Harald Sitter (apachelogger) wrote :

I really wonder how Chris contacted us, so that I didn't notice. Maybe magic. Anyway, I'd appreciate contacting us _before_ closing such bug reports, since the Kubuntu team is kind of officially supporting these packages.

Everyone please give
https://lists.ubuntu.com/archives/kubuntu-users/2008-September/031527.html
a read. It explains why the break occured, why we decided to do it, how to reverse it, and why you shouldn't have respositories in your sources.list which are not used anyway.

Chris Coulson (chrisccoulson) wrote :

Harald - I sent an e-mail to <email address hidden> with the number of this bug report in the title. I'm not a member of the mailing list, so perhaps it is awaiting approval from a moderator?

JW (arch0njw) wrote :

Harald, thanks for the update on this.

I appreciate that the KDE4 team needed to make a decision in order to keep things moving ahead. However, folks like me (running 3.5.x and using KDE4 apps) are hit on the head by this. For me, this is not an "unused repository" as you stated. I like to make the most of the ability of KDE4 and KDE3 to run side-by-side so I can get what I feel is the best of both worlds -- that is one of the key things I enjoy about Linux.

Now I am faced with deciding what I want to break, GTK in KDE3 or Konqueror in KDE4. I can't help but feel the decision shouldn't be one I need to make. If there is a fundamental technological reason why these two things cannot "live in harmony", I understand. But I do need to ask if there is anyway this can be made to work out without going through programming calisthenics or contortions. I enjoyed both things living next to each other at one point in time.

Harald Sitter (apachelogger) wrote :

@Chris: possible, we are subscribed to the KDE relevant bugs anyway...

@JW: If flash was open source I would try finding out why it doesn't want to live with the old gtk-qt in harmony (I guess Qt 3, which gets pulled in by the gtk-qt-engine and Qt 4 from Konqueror 4 clash and cause the crash) but for now, we don't have the resources to do a trial-n-error investigation. I can assure you, if we had an easy solution at hand to make both work properly, we wouldn't hesitate fixing this issue.

JW (arch0njw) wrote :

@Harald: Understood, and thank you for taking the time to explain this. I hope I am not the only one to benefit from those details.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers