Tomboy retains ugly default gtk look in KDE 4

[Robert Persson]

This might be a duplicate of #360131, but I'm not sure.

I have KDE 4 configured so that GTK apps use the same style and font as KDE apps. For the most part, when not running and app as root, this works fine. For instance gnome-terminal blends in very well. However this is not the case with Tomboy, which has that large, chunky, default GTK look. Even if I launch gnome-panel and change the style and fonts to something more KDE-like, Tomboy does not pick up on this.

I should probably add that I also experience problems when running gnome apps as root, although I imagine this would be a completely separate problem. For instance Synaptic usually has the same ugly look as Tomboy, although sometimes it switches to the preferences I set by running gnome-panel as root for no reason I can discern.

What should happen, of course, is that Tomboy should look nice in KDE.

[Pierre Rust (pierre-rust)]

I can confirm this, I've got the same problem on Kubuntu 9.10 when running tomboy.
Strange thing is, tomboy looks perfectly fine when run from the command line or from Alt+F2 (KRunner) but looks ugly when started from kde menu.

It happens that the kde menu launch "tomboy --search" ; if you remove the -- search option tomboy looks fine (thought it only appears in the systray the search window is not automatically displayed).

So it seems to be a bug in tomboy and not in kde integration.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[halfbeing (halfbeing)]

I'm the same person that filed the bug, but I'm retiring my old ID.

I honestly can't work out which package this is to do with, nor how to enter it here. I'm sorry for not replying last week when you asked whether the problem was still present with Lucid. The answer as far I can tell is no. Nor am I having the same problem with applications run as root.

[Fabio Marconi (fabiomarconi)]

Can you run in a terminal
apport-collect -p tomboy 380090
Thanks
:)Fabio

[halfbeing (halfbeing)]

I've tried, but since I am using a new user ID it won't let me. I need to unlock apport from my new ID, but I can't work out how to do it.

[Fabio Marconi (fabiomarconi)]

Hello halfbeing,
simply subscribe to this bug then run apport.
To subscribe, look in the top right side and click on the green write ' Subscribe ...'
:)Fabio

[halfbeing (halfbeing)]

Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: tomboy 1.2.1-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-23.37ubuntu1~ppa1~lucid2-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-23-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare saned video

[halfbeing (halfbeing)]

apport information

[halfbeing (halfbeing)]

erm...

robert@ermintrude:~$ apport-collect -p tomboy 380090
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/robert/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
robert@ermintrude:~$

^ ^

[Fabio Marconi (fabiomarconi)]

halfbeing, sorry.
I make a mistake.
please run again the command above

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!