ntesa

Sorry, I messed up the url:

http://www.kde-look.org/content/show.php?content=10955 - Feb 14 2005

I think that's kxdocker, you can get it here:

http://www.kde-look.org/content/show.phttp://www.kde-look.org/content/show.php?content=10955hp?content=10955 - Feb 14 2005

I didn't experience any menu crashes but reading the changelog for 0.5g it seem that they should be fixed now. Please let Thomas know if you're still having proglems so he can fix them. Thanks :) - Sep 13 2004

The toolbar labels background issues have been fixed in 0.5e. Please send a bug report to the author (baghira-style at gmx.net) about the other bugs if they're still present in 0.5e. Thanks. - Sep 03 2004

I can email it to you, just send me an email :) - Aug 31 2004

As Sagittarius pointed out, there's a "Configure" button next to the style dropdown which brings up the configuration window, this replaces the old kcmshell module. Sorry for the Gooddies directory build issues, it looks like it's not included in 0.5d, I just copied it from the 0.5c archive. It will probably show up again in the next release. - Aug 31 2004

The rpm doesn't install any splash screens, let alone Britney. I thought you already had a Britney splash screen installed and you couldn't switch to another one because of some theme bugs. The rpm doesn't/shouldn't change anyhing in the user's home directory. I'll test it on another mdk 10 machine tomorrow, but it doesn't make any sense to me, unless the rpms on sourceforge have been somehow altered, and it doesn't look like that anyways. You can check all the files distributed with the rpm by doing an rpm -qlp on the rpm file. Do you see any Britney splash screens there? I'll look more into it, but this doesn't make any sense at all. - Aug 22 2004

Britney rocks :) The binary rpm is build for mdk10, so you shouldn't have to rebuild unless you have newer qt or kde installed. Anyways, if you're talking about the KDE splash screen, you should be able to change it, I just tried it on my machine. Give me more details if you're still having problems, I don't understand exactly what's going on. - Aug 21 2004

If you're having problems with the 0.5 rpm please download it again and do a forced upgrade (rpm -U --force). I've recompiled it again on a standard Mandrake 10 install with the default qt libraries (3.2.3). Sorry for the inconvenience. - Aug 05 2004

In that case it might be something with your machine. I'd suggest downloading the source rpm and building it on your machine (rpmbuild --rebuild source.rpm), that should work (if you have all development packages installed). - Aug 05 2004

It works fine on my machine, but I've updated my qt libraries to 3.3.2 recently. I'll test it on a standard Mandrake 10 install and if it doesn't work I'll rebuild the rpm. Were the previous versions working fine for you? - Aug 05 2004

To get the drop shadows under the windows you'll need to apply the kwin drop shadow patch to kdebase and kdelibs, it's available here:

http://www.kde-look.org/content/show.php?content=10567 - Jul 30 2004

It's not broken, it's just that the sourceforge.net mirrors take longer to update lately. It used to take only minutes, now it looks like it takes a couple of hours. - Jul 14 2004

I'm not sure if you just used BAB or the Configure dialog to select the default style. Make sure you have the Brushed Metal style selected as the Default Style in the Baghira Config dialog (in the KDE Control Center/Style, there's a Configure button, it took me a while to find it too :). If you're running BAB, right-click on it and choose the default style, and then click on it so the icon changes to the black foot icon to select Brushed Metal for newly started apps. Hope this helps, it's not very clear to me which settings take precedence yet, but I'd assume that if you're running BAB then it will override your style settings. If it still doesn't work please send a bug report to Thomas (baghira-style at gmx.net). - Jul 04 2004

I've also uploaded the SRPM to sourceforge, I'll try to keep it up to date. Sorry for the delay, I've been kinda busy and I had to do some extensive changes to the spec file for the new version of Baghira and a couple of fixes related to icons and menu files. Usually it takes only a few changes and a recompile to upgrade to a new version, but 0.4 had lots of changes. - Jul 02 2004

You're very welcome. - Jul 02 2004

I haven't had any problems with JuK, please post a bug report here:

http://www.kde-look.org/content/show.php?content=8692

Or send an email to Thomas (baghira-style at gmx.net) with as much information as you can.

Thanks. - Jun 20 2004

Try changing your color scheme, this rpm comes with the Baghira color scheme. You don't have to define colors for every widget unless you want them to have different colors. - Jun 18 2004

I'm using the same mouse theme, it works nice with Baghira :) But I'm usually against including extra stuff in these rpms as mouse themes or splash screens are easier to install and they're not really part of Baghira. Maybe I'll make some Mandrake packages with mouse themes or other artwork, but I think a website that would put all Baghira/Aqua artwork together in one place would probably do a better job. - Jun 18 2004

Thanks, but I didn't choose the name or made this theme, I just packaged it for Mandrake :) I'm using mdkkdm and I've set it up to use the Baghira style, but it looks like it's not following the color scheme, so I had to set the color scheme for the root account in KDE to get kdm to look the same. It doesn't look bad, and I don't think kdm supports themes like gdm, except for KDE themes. To change the kdm settings use the KDE Control Center and go to System / Login Manager. - Jun 18 2004

There is a Baghira splash-screen here:

http://www.kde-look.org/content/show.php?content=8993 - Jun 18 2004

Try changing your color scheme, this rpm comes with the Baghira color scheme, you can select in in the KDE Control Center then you can change some colors if you don't like them and save your color scheme with a different name. To get the tabs align left uncheck "Force Tabs to be centered" under Tweaks. Your menus should be ok without selecting "Use button, not background Color for Menus" if your color scheme is ok. To remove the button borders in the toolbar make sure that "Draw Toolbar Button Frames" is unchecked. Also, check that "Inactive Button" is set to "Background". Hope this helps. - Jun 18 2004

I'll probably make only one rpm when/if the Baghira author will merge the two projects together, I know he had some plans to do that after KDE 3.2 was released. Right now they have different version numbers and release dates, so it doesn't really make sense to merge the rpms either. Which version number would I use for the rpm, the Baghira or Baghira-deco version number? It would create some confusion, I think. Sorry for boring you :) Maybe you should send a request to Thomas (the Baghira author) to merge the two projects together. - Jun 05 2004

I think it was DNS issues, it looks like some people were unable to resolve the domain. I've used a different domain now, hope it works better. - Nov 07 2004

I've posted a new rpm built for 10.1C. - Oct 08 2004

No problem, thanks for fixing the magicdev issues :) - Jul 30 2004

To fix your gtk2 apps change the include line in your $HOME/.gtkrc-2.0 file to point to another gtk2 theme. It should look like this:

include "/usr/share/themes/Qt/gtk-2.0/gtkrc"

You can change it to:

include "/usr/share/themes/Galaxy/gtk-2.0/gtkrc"

if you want to revert to the Mandrake default gtk2 theme (Galaxy). Or you could just copy the .gtkrc-2.0 file from your root account to your home directory. I'm guessing that the gtk2 apps don't work in your account anymore because you've probably uninstalled the rpm but your .gtkrc-2.0 file still points to the gtk-qt theme, which doesn't exist anymore. So, just uninstalling the rpm without changing the gtk2 theme in that file will not revert your system to the previous state. The theme can also be changed with the KControl module in this rpm before uninstalling it.

Did your KDE crash or did it just stop loading? That's a known issue with Mandrake, and it happens because of magicdev, it's been discussed previously here. I've sent a bug report to the gtk-qt developer (davidsansome) about magicdev and he's gonna try to fix it. It'd help if you's send him a bug report too if you experienced crashes, with as much detail as possible, mostly what KDE theme you were using, there might be some issues with some KDE themes. You could also give it a try with another KDE theme and see if it works, that way we'd know that gtk-qt doesn't work with your KDE theme and we could report it as an issue with that theme to get it fixed.

I've posted the rpm because some people requested it and the issues are not related to the rpm itself but to the gtk-qt engine. The next versions will probably have most of the bugs worked out, and it'd help if most people that experience problems send bug reports to the developer.

Hope this helps, and please provide more information about your issues if you can, hopefully most of them will be fixed soon.

Thanks :) - Jul 06 2004

Thanks :) This is a gtk2 theme, if that's what you're asking, it's just posted under gtk 1.x styles on kdelook because there's no gtk2 section yet. This theme engine doesn't work with gtk1 apps and there's nothing like this available for it as far as I know, but it shouldn't really matter too much, like you said, because most apps are already ported to gtk2 or they will/should be ported in the near future. - Jul 02 2004

I'm gonna try to answer your last posts on a technical level and try to ignore your other comments. If you run ldd on magicdev, you're gonna get this output:

$ ldd /usr/bin/magicdev | grep gtk
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0

So magicdev is a gtk2 app, and as a consequence of using the gtk2 library it will use the current gtk2 theme, in this case the gtk-qt engine. From the magicdev rpm, this is the description:

"Magicdev is a daemon that detects when a CD is removed or inserted. Magicdev handles running autorun programs on the CD, updating the File Manager, and playing audio CDs."

So, unless your machine is not configured to run supermount, magicdev is pretty much useless in kde, unless you want autorun for your CDs. As far as I know supermount is configured by default on Mandrake. There has been a discussion about magicdev and supermount on the gtk-qt page, as I mentioned before, but I'll post the link again for your convenience:

http://www.kde-look.org/content/show.php?content=9714

It's your choice if you wanna continue to use magicdev or this theme. But disabling magicdev will not prevent you from using your CD, at least not as long as you have supermount enabled.

This theme engine does work on Mandrake 10. To answer your questions, I got it to work on Mandrake 10 just by compiling and installing it, and I made an rpm based on users' requests on the gtk-qt page. I never said that it doesn't work on Mandrake 10, I said that KDE will fail to load completely if magicdev is running when using this theme engine, because magicdev starts before KDE ends loading. Maybe there are better solutions, like finding the script which starts magicdev and moving it to the end of the script to start it later, or adding it to KDE's autostart folder instead of just disabling or removing it completelly.

I'm sorry if I'd given you bad advice, but I can assure you that it wasn't malicious or with bad intentions, I was just trying to help.

And finally, as much as I'd like to take credit for this app (or theme engine), it isn't mine, it's been developed by davidsansome. - Jun 24 2004

This is a known problem with Mandrake 10.0 and has been discussed on the main gtk-qt page before:

http://www.kde-look.org/content/show.php?content=9714

The problem is that Mandrake 10 starts magicdev when starting kde and magicdev is a gtk2 app, but kde is not completely loaded yet, so the gtk-qt theme engine can't create the gtk2 theme yet. The only fix that I know of so far, is to either uninstall or disable magicdev when kde starts (but I don't know how to disable it).

Linux has "non-standards" problems as you put it just because different distributions have different packages and different behaviours, so this problem would happen on any Linux distro that starts a gtk2 app when kde starts, although I'm not aware of any other distros doing this, except for Mandrake 10.

I'll add a note to the description, thanks for the heads up :) - Jun 20 2004

Make sure your $HOME/.gtkrc-2.0 looks something like this:

# This file was written by KDE
# You can edit it in the KDE control center, under "GTK styles and fonts"

include "/usr/share/themes/Qt/gtk-2.0/gtkrc"

style "user-font"
{
font_name="Lucida Sans 10"
}
widget_class "*" style "user-font"

You'll probably have a different font there, but the include line should be the same. You can set this by using the KControl module as I explained in my previous post.

If your gtk2 apps still don't look like your kde apps, please send an email to the gtk-qt author (mememe at davidsansome.com) or post a bug report on the gtk-qt page here:

http://www.kde-look.org/content/show.php?content=9714

Good luck! - Jun 20 2004

This style is only for gtk2 apps, so gtk1 apps will still look the same. As far as I know gnucash is still based on gtk1, and gimp1 is also based on gtk1, only gimp2 is based on gtk2. Under the "KDE Control Center/LookNFeel/GTK styles and fonts" make sure you select "Use my KDE style in GTK applications" and "Use my KDE fonts in GTK applications". So it should work if you have the right settings and only for gtk2 apps. - Jun 20 2004

Thanks, I'll update the menu file and build an updated rpm. - Jun 18 2004

Nice desktop. Could you please tell me what font are you using and where can I get it? :) Thanks. - Oct 11 2004

Sorry for not answering, I didn't check the messages on this page in a long time, and now kompose 0.4.1 has been released and it compiles ok on mdk 10 :) - Aug 26 2004

I was able to compile it only after installing qt-3.3.2. Mandrake 10 comes with qt-3.2.3 and it seems that Kompose is using some features that are not present in that version. - Aug 02 2004

What version of qt do you have installed? I wasn't able to compile it and I've used the prefix. Thanks. - Aug 02 2004

I think what gerv means is that someone can't make icons based on their artwork and distribute them. Or maybe someone just can't make icons for the mozilla products at all without their consent, although that's not very clear and there are lots of icons available for all mozilla products, mostly in the Mac community, some of them even based on original mozilla artwork. It's not very clear to me what the problem is in this case yet, but if these icons infringe on any copyrights I think some solution should be found and copyrights should be respected. On the other hand, I don't agree with the poster posting these icons again after the original author removed them. I think it's up to the original author to decide if he wants to find a solution and continue to distribute them or not. Anyways, to me it seems that so far both sides in this debate are a bit over the edge. I think some clarification is needed from the mozilla project, and I'm not sure that gerv is representing their official view on this matter, but again, if that is their official position then it should be enforced and respected. - Jul 07 2004

As far as I know the Firefox menus don't follow the gtk2 themes, so this is not really a problem with this engine but with Firefox. I haven't tried Firefox 0.9 yet, but 0.8 had this behaviour. - Jun 20 2004

I've made a Mandrake 10 rpm, you can get it here:

http://www.kde-look.org/content/show.php?content=13545 - Jun 18 2004

I think this is happening because Mandrake 10 starts magicdev (in the background) when kde starts, and magicdev is a gtk2 app so gtk-qt is trying to use the kde theme, but kde isn't loaded yet. You could disable magicdev if you don't use it, but I don't know of any fix. - Jun 16 2004

Is the top bar a Karamba theme or is it kicker? I was wondering about the rounded corners, if it's kicker. Nice desktop btw. - Jun 20 2004

You have to start bab (from konsole, in the background: bab &) and then click on its systray icon to switch it to brushed metal (the icon will become black). Then logout from KDE and log back in, all your apps should be in brushed metal now. - Jun 12 2004

Thanks :) I've changed that line and uploaded a new archive with the fix. - Jun 06 2004

I think this is a problem inherited from the analogClock theme that I've used the python code from. The first time you load the theme it doesn't show the clock, but if you close and open the theme again it should show up. I think it might be related to the fact that the first time you run it there's not config file for it or it could be a SuperKaramba bug. - Jun 05 2004

Well, then you could just resize the clock to a smaller size, the analogClock code that I've used supports resizing, there are a few options for that. You should also disable "Use fast image scaling" for this theme to make it look smoother. I've tried it at a smaller size and it looks nicer, but I also disabled the seconds dial and I've changed the update interval in the theme file to 5 seconds, the resizing would probably kill your cpu otherwise. - Jun 05 2004

Zooming is kinda different, it's resizing the images (usually to a smaller size, which helps), and SuperKaramba has a resizeImageSmooth method, but the clock is rotating the dial images instead. Maybe using something like ImageMagick from Python to rotate or blur/smooth the images would make a difference, I'll give it a try. - Jun 04 2004

I'm hosting those rpms on my server and I don't experience any connectivity problems. It might be routing issues between your ISP and mine, but I didn't get any reports from other people about this. Maybe I'll try hosting them somewhere else instead, thanks for the notice. - Jun 04 2004

I've got it from http://www.bombiadesign.com/desktop_archive.html and it's called Blocks (Blue). - Jun 04 2004

Edit $HOME/.kde/share/config/kdesktoprc and in the [FMSettings] section add this line:

ShadowParameters=0,1,16.0,192.0,2,4,0,0,0,0

You should disable the shadow before updating that file, and then enable it again.

Here's a howto posted by abby a while ago:

http://www.kde-look.org/content/show.php?content=12380 - Jun 02 2004