Archive for the ‘openSUSE’ Category

Making GNOME more Usable

Saturday, February 5th, 2011

And while I am at it, some hints on getting GNOME a small little bit more usable. The problem is mostly the default window manager, and the gripes I’m having with it are basically the same that Linus Torvalds had some years ago. I want my window buttons to be configurable. To be more precise, I want the “maximize” button to behave like in almost every other window manager: 3 different mouse buttons, 3 different button actions: “maximize”, “maximize horizontally”, “maximize vertically”.
Linus’ problems have been addressed, and I’m explaining a lame workaround for my wishes to get something slightly similar to what I want. My workaround does only work because of the fixes for Linus’ problems.

After looking into the code I understood that the window buttons are only used with left-click, right and middle click are handled by the “window titlebar action” instead.

So I redefined the window titlebar mouse actions to do maximize horizontally / vertically on right click and double click. (I am pretty accustomed to having middle button on title bar put the window into the background, but I might change that).

So here’s what you have to do.

  • open regedit.exe gconf-editor
  • browse to /apps/metacity/general
  • change action_double_click_titlebar to toggle_maximize_vertically
  • change action_right_click_titlebar to toggle_maximize_horizontally

While you are at it, you might also enable resize_with_right_button, which restores even some more sanity.

For all those asking why I’m not using a different window manager with GNOME: been there, tried that, but the integration of them all was pretty horrible (keyboard shortcuts no longer easily configurable, …) and I want somehting that just works and does not always get in my way. If I wanted that, I could have kept KDE.

OpenStack “bexar” packages for openSUSE and SLES11SP1 are ready

Thursday, February 3rd, 2011

Shortly after the OpenStack “bexar” (spoken “bear”) release was ready, my packages finished building and are available at the isv:B1-Systems:OpenStack Build Service repo.

Grab them, while they are still hot!

The ride might still be a bit bumpy as the whole OpenStack development is very Ubuntu centric, and thus some of the dependencies, especially to old versions of python stuff are tricky to find. However, first results look promising.

I’ll update here soon with some short hints on how to configure and use the whole lot.

Thanks go to my colleagues Christian Berendt and Andre Nähring at B1 Systems GmbH who have been tireless in testing packages and reporting packaging bugs and other problems. Thanks also to Gregory Haskins with whom I started the packaging effort early in december.

DeLorean?

Wednesday, February 2nd, 2011

Check out this bugreport. Sometimes I’m wondering if Takashi has a time machine, allowing him to jump back in time in order to fix reported bugs in such an amazingly short time… ;-)

“Could not find any loop device.” WTF?

Thursday, January 13th, 2011
susi:~ # mount /space/FACTORY.iso /mnt/ -oloop
mount: Could not find any loop device. Maybe this kernel does not know
       about the loop device? (If so, recompile or `modprobe loop'.)

WTF? That never happened to me before, so I assumed (obviously) that something was broken in current FACTORY and filed a bug.

Finally we found out, that the loop module was always unconditionally loaded on every machine by boot.localfs, which is no longer run since I switched to systemd.

As Kay pointed out in the bug, it is very easy to fix:

susi:~ # echo loop > /etc/modules-load.d/loop.conf

At least until someone fixes the Kernel’s loop device behaviour ;)

plasmoid-networkmanagement - How to connect?

Saturday, October 23rd, 2010

After Will’s talk about new KDE Features for 11.4 on the openSUSE Conference, I thought I’d finally give the networkmanagement plasmoid a try and installed it.
While it looks neat and apparently would show additional information about my connection (compared to knetworkmanager), I was unable to find a button or other UI element that would allow me to connect to a 3G Network.

Has anyone managed to use this for connecting? How?

I was just lucky that I had nm-applet installed, otherwise I would not even have had a way to get online at all… :-)

Rebuilding a single kernel module

Wednesday, April 28th, 2010

Due to Bug 596844, I had to rebuild the i915 module with a patch. I have done things like that quite often over the last years, and every time I have to dig through the documentation, so I’ll put it up here in the hope that I’ll find it easier in the future and that it might be useful for somebody else ;)

There are only a few steps, following the README.SUSE in the kernel-source package:

  • install the kernel-syms and kernel-source packages
  • copy the kernel sources to some other place where you have write access as a normal user (this is not in the README, but I hate doing stuff like that as root, so I’m doing it anyway)
  • patch the source
  • build the module

Or, as an almost-copy’n'pasteable list of commands:

cd /tmp
cp -a /usr/src/linux/ . # do not only copy the symlink ;)
cd linux/drivers/gpu/drm/i915/
patch < /tmp/i915-nofbc.diff # your diff
make -C /usr/src/linux-obj/x86_64/desktop M=$(pwd)
ls -l i915.ko

You need to adjust the directory given to “make -C” to your desired kernel flavour, of course, but that’s it. Copy the module over to /lib/modules and reboot (I usually save the old module somewhere else, in case something goes wrong, but you probably figured that out already).

Claws-Mail trick of the day: plugins

Monday, April 12th, 2010

Today I found another useful trick for claws-mail users. I switched from an old i586 machine to a brand new x86-64 thinkpad. I copied my $HOME over. Then I wondered, where all my claws-mail plugins had gone.

Starting it from the command line showed (wrapped for your reading pleasure):

** (claws-mail:9938): WARNING **: plugin loading error:
   /usr/lib/claws-mail/plugins/rssyl.so:
   cannot open shared object file:
   No such file or directory

Uhm, yes. This is an 64bit system, so the plugins are installed in /usr/lib64/claws-mail/…
Two possible solutions to the problem came into my mind.

  • creating a softlink from /usr/lib64/claws-mail to /usr/lib/claws-mail
  • changing the configuration

The second method was actually easier, and is probably more future-proof (If I reinstall the machine, I might forget to create that link…)

I checked the config file in ~/.claws-mail/clawsrc and found a section

[Plugins_GTK2]
/usr/lib/claws-mail/plugins/rssyl.so
/usr/lib/claws-mail/plugins/pgpcore.so
/usr/lib/claws-mail/plugins/smime.so
/usr/lib/claws-mail/plugins/pgpmime.so
/usr/lib/claws-mail/plugins/pgpinline.so

I simply duplicated the plugins and substituted /usr/lib with /usr/lib64. As a result, I now get the “plugin loading error”-lines on both machines, because the i586 can only find the plugins in /usr/lib and the x86-64 only those in /usr/lib64, but since claws-mail does not really care and just works, I also just ignore them.

It will be interesting what happens once I use the GUI to add another plugin, but I will care for that when it happens :)

PAN/NAP made even easier…

Tuesday, March 23rd, 2010

I wrote last year about how to use bluetooth networking to connect to the internet via a mobile phone. Since then, I had heard rumours that NetworkManager was now able to do this as well, but I actually never managed to find out how to do that (admittedly, I never looked too hard).
Today I checked again.
Since those are the “reference implementations”, I started GNOME’s nm-applet and bluetooth-applet instead of knetworkmanager and kbluetooth. I still could not find anything related to bluetooth in nm-applet’s UI. Then I looked a bit farther and found Dan Williams’ post about it.
Long story short: I deleted my phone from bluetooth-applet’s “known hosts” and re-paired it again. There it asked me if I want to access the internet via my mobile phone, which I confirmed. After that, nm-applet has now an entry for “PANU” which is the Phone’s connection.
Working well and pretty cool, too. One more workaround that’s not needed anymore.

For completeness, I also tried to remove and pair the phone with kbluetooth, but apart from it not working at all (never asking for a PIN), it also did not ask for the internet connection stuff. So for now, if you want Bluetooth networking, just use nm-applet and bluetooth-applet.

$HOME full? WTF?

Wednesday, January 27th, 2010

Today I discovered that my $HOME was nearly full. My machine has only moderate space for the encrypted /home partition, but there were almost 2GB free until a few days ago, so I decided to look where the space went.

It was easy: ~/.xsession-errors was over 1,5GB. I looked who was wanting to tell me lots of important stuff and found out that about every KDE4 program produced several debug lines, almost every second.
Since I doubt that anybody will ever want to look at 1,5GB logfiles, I just decided to redirect it to /dev/null in /usr/bin/startkde. Now only my submitrequest number 30607 needs to be accepted into KDE:KDE4:Factory:Desktop, so that everyone benefits from this solution.

Note: it took 15 days for the logfile to get that big, but to be honest: I don’t want to reboot every two weeks, only to keep KDE4 from crapping my home directory.
Second Note: If there had been any significant updates in FACTORY in the last two months, I would probably not even have noticed the problem, but there were none ;)

More KDE4 rants

Saturday, December 19th, 2009

Seeing that I apparently hit a nerve for some people with my last post, here is the next thing that really annoys me every day in KDE4.

Notifications.

Those ugly passive pop-ups that appear on the display near the area where you have configured the “system tray” to be on the panels. From the beginning they were an example of uglyness. After quite some time they at least stopped to be drawn one over the other, so they are no longer totally unusable, but they still are not pretty.
One example: most of them are too small, so that the text they should show me gets cut off and I have to guess what the system wants to tell me.

As much as I detest GNOME, their unobtrusive notifications in the lower right corner are much more stylish and less disturbing than the KDE4 ones.

And it is not QT’s fault: a proprietary application like skype, using QT, can do it in almost the same way as GNOME, so it is definitely possible.