Posts Tagged ‘errors’

GThumb but no thumb(nails)

Sunday, August 14th, 2005

GThumb without thumbnailsWhile I was ordering and sorting a bunch of holiday snaps at some point GThumb just stopped showing the thumbnails. I just got a generic icon for an image.

I have absolutely no idea what happened.

There was nothing in the GThumb preferences about not showing thumbnails, so I was a bit at a loss. Fortunately I got the idea of using the Gnome Configuration Editor, which on my Debian testing system is on Applications | System Tools | Configuration Editor and there it was. The gconf key /apps/gthumb/browser/show_thumbnails was not set.

Once the key was set to ‘true’ (by checking the box) GThumb immediately showed the thumbnails again.

So the fix was easy, but I still haven’t got a clue why it was turned off automatically in the middle of a session. (more…)

Problems with packages in Debian Testing

Monday, August 30th, 2004

There are currently some bugs in gcc related packages in Debian testing. They won’t install because they contain files owned by other packages too.

The errors are:

(Reading database ... 77290 files and directories currently installed.)
Preparing to replace gcc-3.3-base 1:3.3.4-6sarge1.1 (using .../gcc-3.3-base_1%3a3.3.4-6sarge1.2_i386.deb) ...
Unpacking replacement gcc-3.3-base ...
dpkg: error processing /var/cache/apt/archives/gcc-3.3-base_1%3a3.3.4-6sarge1.2_i386.deb (--unpack):
 trying to overwrite `/usr/share/doc/gcc-3.3-base/changelog.Debian.gz', which is also in package g++-3.3
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Preparing to replace libstdc++5 1:3.3.4-6sarge1.1 (using .../libstdc++5_1%3a3.3.4-6sarge1.2_i386.deb) ...
Unpacking replacement libstdc++5 ...
dpkg: error processing /var/cache/apt/archives/libstdc++5_1%3a3.3.4-6sarge1.2_i386.deb (--unpack):
 trying to overwrite `/usr/share/doc/libstdc++5/changelog.Debian.gz', which is also in package libstdc++5-3.3-dev
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/gcc-3.3-base_1%3a3.3.4-6sarge1.2_i386.deb
 /var/cache/apt/archives/libstdc++5_1%3a3.3.4-6sarge1.2_i386.deb

The solution is very simple, once you have figured it out:

# dpkg -i --force-overwrite
/var/cache/apt/archives/gcc-3.3-base_1%3a3.3.4-6sarge1.2_i386.deb
/var/cache/apt/archives/libstdc++5_1%3a3.3.4-6sarge1.2_i386.deb

It might affect other packages too, such as g++-3.3.

Nautilus: where do you want to go today?

Monday, August 23rd, 2004

Nautilus error messageThe new spatial nautilus is generally nice, but sometimes the mime type detection messes up.

This time I had an sftp: location open, where I have a symlink to another folder on the remote server. First the symlink is shown as a file of an unknown type, but when I double click on it to open the folder, I get an error message that, to say the least, is not very helpful.

What is exactly the correct extension for “Folder” and if I open the “Open with” menu, there nothing there.

What am I supposed to do?

Is there really no way I open the remote folder?

UPDATE: the bug report is here, so I’m not alone.

Tex font metricsUPDATE 2: I have another file, a Gnumeric file, which is regularly, but not always, recognised as a “TeX font metrics” file. I have no idea why, but it must be some pattern of bytes in its content that triggers this faulty identification. At least in this case I can open it via the “Open with” menu.

Yet another wonderful Gnome error message

Saturday, July 3rd, 2004
Error activating XKB configuration.
Probably internal X server problem.

X server version data:
The XFree86 Project, Inc
40300001
You are using XFree 4.3.0.
There are known problems with complex XKB configurations.
Try using simpler configuration or a newer version of the XFree software.
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb

So I’ve got a keyboard problem! No, I haven’t. Everything is great, every key sends exactly what it should.

Anyway, it’s an error message from the X server. Nope. It is apparently from an obscure program called gnome-settings-daemon which is started automatically by gnome-session. Only it doesn’t say so anywhere. Needless to say, there is no manual for the gnome-settings-daemon or even a –help option to help me gain some insight.

So I have a working keyboard, an annoying dialog with a misleading message at each login and a top panel that is misplaced due to this dialog taking up the top-left corner of the screen well before the window manager is even started. On top of that the login takes at least 30 seconds longer due to some problem starting this gnome-settings-daemon, which I’m inclined to believe is tried several times, since I get this message on the console at each login:

You can only run one xsettings manager at a time; exiting

I still haven’t found a way to get this dialog to disappear.

UPDATE: Well, I’m not the only one with this problem, as can be seen at http://www.gnomesupport.org/, especially

http://gnomesupport.org/forums/viewtopic.php?t=6179&highlight=xkb
http://gnomesupport.org/forums/viewtopic.php?t=6827&highlight=xkb

but there is no solution there either.

UPDATE 2004-07-17: The problem just went away today, and I’m not quite clear why. I did have a .Xmodmap file which I initially ran from my .xinitrc, that is before gnome-settings-daemon was started, and I moved that to a session startup program, so it’ll run after gnome-settings-deamon is started, but I’m not 100% sure that was the culprit. Might have been, though.

Unknown CORBA exception id: ‘IDL:omg.org/CORBA/INV_OBJREF:1.0’

Thursday, July 1st, 2004

What a wonderful informative message.

It happened when I logged into Gnome 2.6, once for each applet in the panel. Given the clarity of the message I had no doubt the applets didn’t load. I could also see they were missing in the panel 🙂

After some searching I finally discovered the solution: log out of Gnome, remove /tmp/orbit-XXX where XXX is your username, and log in again. Problem solved.

One vote from me for intelligible error messages.