Bug#634131: [Debian-olpc-devel] Bug#634131: python-hulahop: import error in python import hulahop

Jonas Smedegaard 17 July 2011 18:40 Yes, I experience same error myself. Try as a temporary (ugly!) workaround

Bug#634131: python-hulahop: import error in python import hulahop

Package: python-hulahop Version: 0.8.1-1 Severity: serious Justification: import hulahop fails I'm attempting to learn pyjamas. However, import hulahop fails. I have xulrunner-1.9.1 and xulrunner5.0 Python error is: Python 2.6.7 (r267:88850, Jul 10 2011, 09:55:27) [GCC 4.6.1] on linux2 Type

Bug#560788: (no subject)

The file is in the package libmysqlclient-dev (5.1.41-3) which I did not have installed and was not a dependency (I suppose it shouldn't be, being a -dev). I filed against openoffice.org-base because Base is where I saw the bug, and I assumed it may be related to the efforts of fix the last bug

Bug#560788: Another followup, to be clear

Sorry, just to be clear: I did already have the package libmysqlclient16 installed. The error goes away only after installing package libmysqlclient-dev (5.1.41-3) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas

Bug#533128:

xorg.conf is red herring. I removed the file xorg.conf $ gksu shows the same error (shown once as the password/command dialog comes up, and once more after root/gnome-termial is requested) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe".

Bug#533128:

I get it simply with gksu gnome-terminal the error happens after the authentication dialog. > (gksu:9543): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion > `atom != GDK_NONE' failed > is repeated four times. Subsequent repeats of the command give no authentication dialog (fair e

Bug#531428: beagle-backend-evolution no longer indexes evolution

Package: beagle-backend-evolution Version: 0.3.9-3 Severity: grave Justification: renders package unusable beagle-backend-evolution doesn't index evolution, I suppose since the change to sqlite. It's driving me crazy :-) Since indexing evolution is the purpose of this package, the fact that it

Bug#522104: Alt-F8

Just curious: when it appears to have hung or crashed, does typing ALT-F8 solve things? -- Tim Richardson t...@tim-richardson.net Skype: te.richardson Mobile: +61 458998541Melbourne, Australia. signature.asc Description: This is a digitally signed message part

Bug#510564: Bug correct and patch submitted for upstream (in #511744)

I am not confident of doing force merge to merge 510564 and 511744, I think 511744 should be the lead bug report. It is now assigned to libsmbclient with a patch pending upstream review, but it is only serverity important.

Bug#510564: Easy fix: modify the case-sensitive setting of the samba share

I just noticed that this Debian bug refers to ext3 shares mounted via Samba, whereas the Ubuntu launchpad discussion is about NTFS shares. The debian report (above) is correct with the default settings for a samba share. However, the correct behaviour is easily reached: modify the samba share so

Bug#505270: a better solution

I've made a version of splashy which uses a signal to exit rather than wait a whole second in the local-premount script. I'll test it more thoroughly tonight my time and then send patches. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Bug#510564: this should not be grave

The original launchpad report doesn't mention data loss, but it does indicate a bug in Nautilus which causes 'inconvenience'. However, Windows users probably have similar but not identical problems. According to that report 1. NTFS is case-sensitive, so the underlying file system is case sensitive

Bug#505270:

I did a sleep 0.5 All three machines are fixed with this. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#505270:

By the way, if you change the script in /usr/share/initramfs-tools/... per my last comment, you also need to do update-initramfs -u -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#505270: A solution

Thanks to #splashy and Mattkijs Kooijman, we have a solution. It's not a very good solution, but it proves we know what the problem is: The solution is to delay the init process for one or two seconds after splashy boot ie change /usr/share/initramfs-tools/scripts/local-premount/splashy and add

Bug#505270:

Neil, hi. I'm the original reporter, although by now I think it is clear that many people see this bug. For me, it is 100% reproducible. I only use stock Lenny i386 kernels, and I don't have /usr on a separate partition. I certainly use initramfs, since I'm using a stock kernel. I reproduce this

Bug#505270: Update

I changed splashy_video.c to enable directFB debug and info messages to console. I see an error when init_font tries video.dfb->CreateFont The first attempt at this always fails. It's the second attempt which seems interesting. the message from directFB is (!) Direct/Interface Could not open int

Bug#505270:

v 03.13 shows the same behaviour as 0.3.12. That is, splashy doesn't work with the same error messages. Also, the /tmp/directfbrc hack fixes it just the same. I wonder why there was so much confidence that a fix was found. Have the developers managed to reproduce the bug yet on their own systems

Bug#505270:

> re debian bug 505270 > does this help you: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505270#27 > > (my file /etc/directfbrc is attached) > > and after creating the /etc/directfbrc file, try this: > > sudo update-initramfs -u > Hi, I confirm the problem is resolved by adding this f

Bug#505270:

Also, /boot/grub/menu.lst extract ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.26-1-686 root(hd0,0) kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet vga=791 splash initrd /boot/initrd.img-2.6.26-1-686 -- To UNSUBSCRIBE, ema

Bug#505270:

Luis, I sent the 4MB initrd image to your gmail account via yousentit It's available for 7 days. regards Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#505270: More infor re splashy bug 505270

> Tim, > > Is it possible that your problem is related to /etc/splashy/config.xml ? > > Try copying this file to /root/config.xml and purging Splashy 0.3.10 > (dpkg --purge splashy) (from Lenny) and installing the Sid version > (0.3.12), then copy your config.xml back to /etc/splashy. > > Lui

Bug#508071: Perhaps a dup of 504389 (which has an easy fix)

This is probably a duplicate of bug 504389 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504389 To find out, go into shutdown, and then when it appears to be stuck, press Alt-F8 If that's the case, then you have bug 504389. Please let us know. I submitted a patch for 504389. You can also

Bug#505270:

Installing splashy 0.3.10 works even when I leave all other packages at the sid version, including libsplashy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#505270: splashy fails at boot: Couldn't splashy_start_splash error -10

> > Connection refused. > > Couldn't splashy_start_splash. Error -10 > > Reading the code a -10 error seems to indicate a problem with fonts. Are you > using the default theme/font? On all machines, only the default theme is used. The package with extra themes is not installed. > > After booti

Bug#505270: a workaround .

In the process of trying to debug this, I discovered that I can make it boot properly if I create the file /etc/directfbrc and include this one line in the file log-file=/tmp/directfb.log I had no directfbrc file on my system. An empty file doesn't help. My attempt to make the log file was to

Bug#505270:

Purge and re-install unfortunately did not help me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#504604:

In the launchpad bug report (the link above) there is a discussion about why OOo now behaves like this. I understood from this discussion that upstream deliberate made this change for improved Excel compatibility. I'm an experienced Excel user, and I certainly expect Excel to behave the way OOo now

Bug#504323:

What happens if you create a new user, log in as the new user, and try starting OOo? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#504604: Could not reproduce

To simplify this, I think you are saying that in v2.4, you see that a formula like this =if(A1-B1<>0;1;C1) returns an error 529 when C1 contains "" and A1 and B1 are empty I made a simplied test case in OOo 2.4 (the lenny version) The formula behaves the same in 2.4 and 3.0. My 3.0 is the experiem

Bug#504604: Could not reproduce

To simplify this, I think you are saying that in v2.4, you see that a formula like this =if(A1-B1<>0;1;C1) returns an error 529 when C1 contains "" and A1 and B1 are empty I made a simplied test case in OOo 2.4 (the lenny version) The formula behaves the same in 2.4 and 3.0. My 3.0 is the experiem

Bug#486400: it is working now

I confirm that on all three machines I could test on, this bug is no longer occuring. All three machines resumed successfully from suspend and hibernate. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#486400:

I will try again to reproduce it three machines I have running Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#495530: Unable to reproduce, plus there is an easy fix

I removed my IMPA password, and tried to reproduce this on an IMAP account. I couldn't not reproduce it with the following two attempts: 1) do not save a password, and interactively enter an incorrect password. I received an error message that the password was incorrect. 2) I stored an incorrect

Bug#501903:

For what it's worth, I use the cups web interface quite a bit on three machines, one Sid and two Lenny, and haven't noticed any problems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#487673: Please ignore my comment on the bug

I had a separate problem not related to this report. lsb-release was not returning the distribution ID because of a mistake in a non-Debian package installation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#487673:

I have lenny with python-apt 0.7.7.1 I seem to have this bug. this is the last few lines of terminal output when I run gksu --desktop /usr/share/applications/software-properties.desktop /usr/bin/software-properties-gtk "/var/lib/python-support/python2.5/softwareproperties/SoftwareProperties

Bug#486400: Grave bug

Laptop top users can't really use splashy because of this bug; I'm surprised this is not an RC bug. I wouldn't want this to be in a stable release because I'm a Debian enthusiast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#482483: usplash crashes machine during startup

Package: usplash Version: 0.5.19-1 Severity: critical Justification: breaks the whole system I installed usplash onto kernel 2.6.25-2 In non-quiet mode, the boot process displays messages. The console becomes garbled at the bottom of the screen (looks like white noise) and then then the machine

Bug#422800:

Matijs, Does icedove handle this situation differently (in case this bug is the reason you moved to icedove)? -- Tim Richardson <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#440274:

traffic shaping script. Tagging "grave" makes it an RC bug which is stopping a newer version from entering testing. -- Tim Richardson [EMAIL PROTECTED] +31 610 899 815 The Netherlands -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Tro

Bug#466395: gpgp: Does not install: five dependency failures

Package: gpgp Version: 0.4-12+b1 Severity: grave Justification: renders package unusable With current testing and/or sid repositories, dependency failure causes installation to fail. gpgp: Depends: gdk-imlib11 but it is not going to be installed Depends: libgnome32 but it is not going to be in

Bug#461331: cupsys: Sharing printers via web interface crashes cups server

Package: cupsys Version: 1.3.5-1 Severity: grave Justification: renders package unusable After I install a printer connected to the server via USB, I want to share it. Choosing "Share published printers connected to this system" and then clicking the button "Change Settings" from localhost:631

Bug#455079: Cannot add tomboy to panel

Package: tomboy Version: 0.8.2-1 Severity: grave Justification: renders package unusable What happens: when adding tomboy to the panel, this dialog box appears: The panel encountered a problem while loading "OAFIID:TomboyApplet". Do you want to delete the applet from your configuration.' Either an

Bug#451849: closed: thanks, it works for me.

You are correct, the bug is fixed for me. Thank you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#451849: openoffice.org-gnome: wiping out contents of files on shared drives when opening

Holesovsky wrote: > Hi Tim, > > On Tuesday 20 of November 2007, Tim Richardson wrote: > > > your new packages do not demonstrate the bug. I successfully opened a > > file; it was not destroyed. > > Good - now could you please test if the file is correctly saved? >

Bug#451849: openoffice.org-gnome: wiping out contents of files on shared drives when opening

Rene, your new packages do not demonstrate the bug. I successfully opened a file; it was not destroyed. regards Tim On Tue, 2007-11-20 at 11:26 +0100, Rene Engelhard wrote: > Hi, > > > Tim Richardson wrote: > > Rene Engelhard wrote: > >> > >> 09:55 <@ke

Bug#451849: openoffice.org-gnome: wiping out contents of files on shared drives when opening

Rene Engelhard wrote: 09:55 <@kendy_> _rene_: Can you please ask him if the size of the file stays untouched? File size is set to zero bytes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#451849: openoffice.org-gnome: wiping out contents of files on shared drives when opening

Rene Engelhard wrote: Hi, Tim Richardson wrote: When opening files on a shared folder (in one case, a Windows share, in another case, a share from another Debian box) the file is zeroed out when the file is opened. Irretrievable data loss. No warning. Something to do with gnome Vfs

Bug#451849: openoffice.org-gnome: wiping out contents of files on shared drives when opening

11-18 at 23:41 +0100, Rene Engelhard wrote: > Hi, > > Tim Richardson wrote: > > When opening files on a shared folder (in one case, a Windows share, in > > another case, a share from another Debian box) the file is zeroed out > > when the file is opened. Irr

Bug#451849: openoffice.org-gnome: wiping out contents of files on shared drives when opening

Package: openoffice.org-gnome Version: 1:2.3.0.dfsg-2 Severity: grave Justification: causes non-serious data loss When opening files on a shared folder (in one case, a Windows share, in another case, a share from another Debian box) the file is zeroed out when the file is opened. Irretrievable d

Bug#447846: fixing binNMUs

> This is due ABI change on APT and will be fixed once binNMUs finish > > A new-user question: What does 'fixing binNMUs' mean and how long does it take? thanks Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]