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 to add /usr/lib/xulrunner-5.0 to a file below /etc/ld.so.conf.d/ and invoke ldconfig. When I tried that, another error occured which might be unrelated. Please report back if above works. ...or even better: help dig into the code and figure out a solution - I am clueless :-/ I'm guessing this problem is linked to sugar-hulahop-0.8.1 not building.
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 "help", "copyright", "credits" or "license" for more information. >>> import hulahop Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.6/dist-packages/hulahop/__init__.py", line 29, in from hulahop._hulahop import shutdown ImportError: libpyxpcom.so: cannot open shared object file: No such file or directory >>> -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.39-3.slh.1-aptosid-686 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-hulahop depends on: ii libatk1.0-0 2.0.1-2ATK accessibility toolkit ii libc6 2.13-10Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra ii libfontconfig12.8.0-3generic font configuration library ii libfreetype6 2.4.4-2FreeType 2 font engine, shared lib ii libgcc1 1:4.6.1-4 GCC support library ii libgdk-pixbuf2.0-02.23.5-2 GDK Pixbuf library ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.5-2 GTK+ graphical user interface libr ii libnspr4-0d 4.8.8-2NetScape Portable Runtime Library ii libpango1.0-0 1.28.4-1 Layout and rendering of internatio ii python2.6.7-1interactive high-level object-orie ii python-gobject2.28.6-4 Python bindings for the GObject li ii python-gtk2 2.24.0-2 Python bindings for the GTK+ widge ii python-xpcom 1:2.0~hg20110502-2 XPCOM bindings for Python ii python2.6 2.6.7-3An interactive high-level object-o python-hulahop recommends no packages. Versions of packages python-hulahop suggests: pn sugar-web-activity (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 report I filed regarding trying to use the native connector in Base. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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...@lists.debian.org
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". Trouble? Contact listmas...@lists.debian.org
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 enough), no error messages and no root gnome-terminal, just silent failure. My laptop does not need to be in dual-head mode to reproduce, but xorg.conf has this: > # If you have edited this file but would like it to be automatically updated > # again, run the following command: > # sudo dpkg-reconfigure -phigh xserver-xorg > > Section "Device" > Identifier "Configured Video Device" > EndSection > > > Section "Screen" > Identifier "Default Screen" > Monitor "Configured Monitor" > Device "Configured Video Device" > SubSection "Display" > Virtual 2560 1024 > EndSubSection > EndSection -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 doesn't work seems to justify grave. I'm filing this bug because I'd like to know what's happening. Evolution 2.24 and 2.26 have been out for a while and I can't find a bug report to track this in Debian. Fast searching if email is indispensable to me, for what it's worth. Ubuntu has bug reports so other people are seeing this problem. Unfortunately, I seem to lack the necessary skills or magical ability to learn anything of practical use from Ubuntu bug reports. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages beagle-backend-evolution depends on: ii beagle0.3.9-3indexing and search tool for your ii libevolution5.0-cil 0.20.0-1 CLI bindings for Evolution ii libgconf2.0-cil 2.24.1-4 CLI binding for GConf 2.24 ii libglib2.0-0 2.20.1-2 The GLib library of C routines ii libglib2.0-cil2.12.8-2 CLI binding for the GLib utility l ii libgmime2.2a-cil 2.2.22-4 CLI binding for the MIME library ii libmono-corlib2.0-cil 2.0.1-6Mono core library (for CLI 2.0) ii libmono-posix2.0-cil 2.0.1-6Mono.Posix library (for CLI 2.0) ii libmono-sqlite2.0-cil 2.0.1-6Mono Sqlite library (for CLI 2.0) ii libmono-system2.0-cil 2.0.1-6Mono System libraries (for CLI 2.0 beagle-backend-evolution recommends no packages. beagle-backend-evolution suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 that the case-senstive parameter is set to true. This allows file.txt and file.TXT to be two separate files. I tested this with two Debian machines: a Lenny server and a Lenny client. I administer samba with swat. Using swat, the case-senstive setting is under "advanced" options for the share. The default setting is "auto" which causes the potential data-loss bug. -- 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 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". Trouble? Contact listmas...@lists.debian.org
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. 2. below, an interesting part of the launchpad entry: > > 1) Mount a remote NTFS Windows share (I am using CIFS at /etc/fstab). > 2) Create a file named 123.abc in this volume (touch, gedit, > whatever). > 3) Open Nautilus and select the mounted volume in the left panel. > 4) In the right panel, locate the file you have just created in Step > 2. > 5) Right click over the file and select "rename". Try to rename it to > "123.ABC". > > Nautilus will tell you there already is a file with that name, which > is not true because the mounted volume is not FAT but NTFS (case > sensitive). > > Alternatively, use Nautilus to access the NTFS share using a "smb://" > address and try to perform Steps 4 and 5: It will work. > > Regards, > Effenberg > > The Nautilus bug is shared by Windows apps, apparently: >From http://support.microsoft.com/kb/100625 > In NTFS, you can create unique file names, stored in the same > directory, that differ only in case. For example, the following > filenames can coexist in one directory on an NTFS volume: > CASE.TXT > case.txt > case.TXT > However, if you attempt to open one of these files in a Win32 > application, such as Notepad, you would only have access to one of the > files, regardless of the case of the filename you type in the Open > File dialog box. > > Other inconsistencies also exist. The Windows NT Command Prompt and > File Manager correctly display the names of the files. However, normal > commands, such as COPY, fail when you attempt to access one or more > filenames that differ only in case. This is not a grave bug, I think. I use remotedly mounted Windows drives frequently at work, and haven't noticed this (I never expect NTFS drives to be case sensitive). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 sleep 2 #smaller values probably work so that the code looks like grep -q '\(VESA\|VGA\)' /proc/fb || exit /sbin/splashy boot sleep 2 #smaller values probably work The problem (my theory) the splashy scripts forks and exits quickly, while its child process does the work of initialising directfb. This fast exit of splashy lets the init process continue. (thanks Matthijs) On my computers, and other computers, this sets up a race condition. It seems that initramfs is being unmounted while the splashy children are working to setup directfb. directfb finds that the file system has gone by the time the call to CreatFont happens. This is probably only a matter of milliseconds. In v 3.10, the earlier start of splashy boot avoided this problem. The workaround hack to set up a directfb log file also probably causes enough of a delay to avoid the problem (as guessed by directfb developers) A sleep in local-premount at the end of the splashy script is a crude mechanism to buy enough time for the child process to finish its initialisation of directfb -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 on a laptop with a completely reinstalled lenny/sid (separate /home partition). I repeat that I in fact see this problem on all three of my machines, all of which are using standard lenny i386 installs, none of them with a separate /usr partition. Agree that it is not reproducible on virtual machines. I've put some more info about the bug at comment 161, the result of some hours of work on my part. I have narrowed down where the bug is happening quite specifically. directfb complains that it can't find one of its standard directories. Clearly this is do with changes after splashy 0.3.10, when this bug did not occur. I suppose the significant change is the move of the script to local-premount. Some people report intermittent problems. The workaround may work simply because of timing changes (according to directfb developers). I suppose there is no chance that the initramfs is unmounted while the splashy script is running? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 interface directory /usr/lib/directfb-1.0-0/interfaces/IDirectFBFont --> No such file or directory when I use kernel parameter break=premount to get an initramfs shell, I see that such a directory does exist. Point 1: On the laptop I am using, this is 100% reproducible Point 2: As soon as I introduce the /etc/directfbrc file with the contents as described above, the second call to CreateFont succeeds. The message is loaded default implementation of IDirectFBFont regards Tim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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? Unfortunately, I can't get a virtual machine to show this bug, only my three real machines. I'd be more than happy to test any proposed fixes before they are packaged. I'm trying to follow development via the mailing list, now I will try to learn IRC. If the Lenny deep freeze is just around the corner, I suggest using my mysterious fix (the /tmp/directfbfc fix documented earlier in this bug report) while we work out what is really happening because at least then this bug could be closed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 file. Thanks. -- +---+ | gpe92 | +---+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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. > > Luis, I think you are following a false lead. See below for my "clues", but first, I followed your request: 1) I reverted to 0.3.10 and verified that it worked. Then, I copied config.xml as you suggested 2) I purged and went back to Sid. libsplashy and uswsusp were also updated. After the updgrade, I verified that the bug reappeared (splashy flashes momentarily, and then it disappears, as described earlier in the bug report) Then I copied the saved config.xml to /etc/splashy (Of course, bug 504389 appeared after going back to 0.3.12, for which I have submitted a patch http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504389 ) 3) The saved config file made no difference. The startup behavious of 0.3.12 is still broken. I actually see this on all three machines running Debian, one of them being an AMD desktop with Nvidia video so it has nothing to do with intel graphics. My clues: :-) It is very strange that a very simple fix solves the problem: creating /etc/directfbrc and putting in a path to the log-file as I described earlier. That is, this content in /etc/directfbrc solves the problem. log-file=/tmp/directfb.log Move that file, and the bug reappears. 100% guaranteed. It also fixes it on all three of my machines. Clue part 2: change the log-file path to be /root/directfb.log and the bug reappears. So it only fixes the problem when /tmp is used There is not actually any log file created in /tmp. I hope this is a huge clue, but I don't know enough about directfb to make any sense of it. My wild guess is that without /etc/directfbrc, directfb falls back to a default location that is not writable. Why would that affect this new version of splashy? Change of execution to premount, maybe? Also strange: I can not duplicate the error on any virtualbox machines. I even made a virtual machine with a separate /home partition. Couldn't reproduce it. > > The new file calls the themes from /usr/share/splashy/themes/. I just > want to rule out that this is not the cause of your problem. Can you > send a copy of your initrd (/boot/initrd.img-`uname -r`) and > /etc/fstab to my email? > I will send my initrd.img via yousendit.com /etc/fstab is: # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 /dev/hda1 / ext3errors=remount-ro 0 1 /dev/hda6 /home ext3defaults0 2 /dev/hda5 noneswapsw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 easily workaround it by editing the file /etc/init.d/splashy go to line 181 which is /sbin/splashy_chvt 8 and before that line add a new line sleep 2 although my patch is more elegant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 booting what do you see if you launch "splashy test"? (hit esc to quit) > sudo splashy test works well. Some more info: On the laptop I am writing this on, the boot image very briefly appears, and then disappears with the error message. At each change of run level, the Connection Refused message is generated. On my desktop, I get the -10 error message and connection refused only once. The next run level change starts splashy successfully. I think the error 10 is not really a font issue. Earlier in the bug report I posted a workaround I stumbled upon while looking in the directfb code: the creation of /etc/directfbrc and adding a path to the debug file. As soon as I follow those steps, splashy works normally at boot. I tested Lenny RC1 installer by making a new virtual machine. Splashy in this perfectly new installation works fine. So I wonder if something is not upgrading properly in the startup scripts despite purging and resinstalling. > filippo > -- > Filippo Giunchedi - http://esaurito.net > PGP key: 0x6B79D401 > random quote follows: > > In God we trust, everybody else pays cash. > -- somewhere in England -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 capture output of the macroDFBCHECK but it doesn't seem to work. I hope this is helpful to someone who knows directfb well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 does. OOo 3 (the release version) behaves the same way as the Lenny OOo package as far as I can tell (I'm using the Debian packages in experimental,which work great). So your request to move Lenny to v3 won't change the functionality. If the above doesn't make sense or is incorrect, then please help by clarifying the differences between your report and the launchpad discussion. Also, I don't see what the data loss is. This functionality change doesn't actually change anything in your document, as I understand it. Are you sure that it qualifies as a "grave" bug? regards Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 experiemental version. In both cases, the formula evaluates to "" I think you are trying to report this: https://bugs.launchpad.net/openoffice/+bug/210153 but if I am correct, it would mean that while you think you have empty cells in T10 and Z10, you don't. So I don't understand your report. bug504604_1.ods Description: application/vnd.oasis.opendocument.spreadsheet
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 experiemental version. In both cases, the formula evaluates to "" I think you are trying to report this: bug504604_1.ods Description: application/vnd.oasis.opendocument.spreadsheet
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 password, shutdown evolution and restarted. It started, and when it attempted to retrieve email, it gave a dialog message that the password was incorrect. I don't think this bug should be critical because even if it could be reproduced, it only requires the password to be deleted (probably for most people, via the Gnome tool Accessories -> Passwords and Encryption Keys, then choose tab Passwords. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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.py", line 450, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python2.5/site-packages/aptsources/distro.py", line 85, in get_sources "Error: could not find a distribution template") aptsources.distro.NoDistroTemplateException -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 hangs shortly into the boot process. In quite mode, gdm appears not to start and I can not access any virtual terminals. I must force the computer to shutdown. Dell d420. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages usplash depends on: ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii initramfs-tools 0.92a tools for generating an initramfs ii libc6 2.7-10 GNU C Library: Shared libraries ii libusplash0 0.5.19-1 userspace bootsplash library ii usplash-theme-debian [usplash 4 Debian usplash theme usplash recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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:
On my ADSL connection, the bandwidth control works as expected. Possibly, this bug is only present on very high bandwidth connections I challenge the severity grave since the package is not rendered unusable for people on normal domestic broadband connections, who are the target of this simple 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". Trouble? Contact [EMAIL PROTECTED]
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 installed Depends: libgnomesupport0 but it is not going to be installed Depends: libgnomeui32 but it is not going to be installed Depends: libgtk1.2 but it is not going to be installed -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 causes the server to crash. That is, it fails to restart. The error is cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting! The only way I can restore is to copy the default config file. -- Scstem Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cupsys depends on: ii adduser3.105 add and remove users and groups ii cupsys-common 1.3.5-1 Common UNIX Printing System(tm) - ii debconf [debconf-2 1.5.17Debian configuration management sy ii ghostscript [gs-es 8.61.dfsg.1~svn8187-2 The GPL Ghostscript PostScript/PDF ii gs-esp 8.61.dfsg.1~svn8187-2 Transitional package ii libavahi-compat-li 0.6.21-4 Avahi Apple Bonjour compatibility ii libc6 2.7-5 GNU C Library: Shared libraries ii libcupsimage2 1.3.5-1 Common UNIX Printing System(tm) - ii libcupsys2 1.3.5-1 Common UNIX Printing System(tm) - ii libdbus-1-31.1.2-1 simple interprocess messaging syst ii libgnutls132.0.4-1 the GNU TLS library - runtime libr ii libkrb53 1.6.dfsg.3~beta1-2MIT Kerberos runtime libraries ii libldap2 2.1.30.dfsg-13.5 OpenLDAP libraries ii libpam0g 0.99.7.1-5Pluggable Authentication Modules l ii libpaper1 1.1.23library for handling paper charact ii libslp11.2.1-7.1 OpenSLP libraries ii lsb-base 3.1-24Linux Standard Base 3.1 init scrip ii perl-modules 5.8.8-12 Core Perl modules ii poppler-utils [xpd 0.6.2-1 PDF utilitites (based on libpopple ii procps 1:3.2.7-5 /proc file system utilities ii ssl-cert 1.0.14Simple debconf wrapper for openssl Versions of packages cupsys recommends: ii avahi-utils 0.6.21-4 Avahi browsing, publishing and dis ii cupsys-client 1.3.5-1Common UNIX Printing System(tm) - ii foomatic-filters 3.0.2-20061031-1.2 linuxprinting.org printer support ii smbclient 3.0.28-2 a LanManager-like simple client fo -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp, dnssd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 answer result in the same error if I repeat the add to panel. How to duplicate the bug: Try to add tomboy to the panel by invoking "Add to panel..." from a right-click on the panel Other data: from .xsession-errors ** (gnome-panel:3513): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:TomboyApplet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_9/prefs;background=none:;orient=down;size=x-small;locked_down=false ~ -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tomboy depends on: ii gconf2 2.20.1-1 GNOME configuration database syste ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libatk1.0-0 1.20.0-1 The ATK accessibility toolkit ii libc6 2.7-4GNU C Library: Shared libraries ii libcairo2 1.4.10-1.2 The Cairo 2D vector graphics libra ii libgconf2.0-cil 2.16.0-8 CLI binding for GConf 2.16 ii libglib2.0-02.14.4-2 The GLib library of C routines ii libglib2.0-cil 2.10.2-3 CLI binding for the GLib utility l ii libgmime2.2-cil 2.2.11-2 CLI binding for the MIME library ii libgnome2.0-cil 2.16.0-8 CLI binding for Gnome 2.16 ii libgnomecanvas2-0 2.20.1.1-1 A powerful object-oriented display ii libgnomeprint2.2-0 2.18.2-1 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-02.18.1-1 GNOME 2.2 print architecture User ii libgtk2.0-0 2.12.3-1 The GTK+ graphical user interface ii libgtk2.0-cil 2.10.2-3 CLI binding for the GTK+ toolkit 2 ii libgtkspell02.0.10-3+b1 a spell-checking addon for GTK's T ii libmono-addins-gui0.2-c 0.3~svn.r90520-1 GTK# frontend library for Mono.Add ii libmono-addins0.2-cil 0.3~svn.r90520-1 addin framework fir extensible CLI ii libmono-corlib2.0-cil 1.2.5.1-2Mono core library (2.0) ii libmono-system2.0-cil 1.2.5.1-2Mono System libraries (2.0) ii libmono2.0-cil 1.2.5.1-2Mono libraries (2.0) ii libndesk-dbus-glib1.0-c 0.4.1-1 CLI implementation of D-Bus (GLib ii libndesk-dbus1.0-cil0.6.0-1 CLI implementation of D-Bus ii libpanel-applet2-0 2.20.2-2 library for GNOME Panel applets ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii libxml2 2.6.30.dfsg-3GNOME XML library ii mono-runtime1.2.5.1-2Mono runtime ii zlib1g 1:1.2.3.3.dfsg-7 compression library - runtime tomboy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
Hi Jan. A small modification works. The file was saved successfully and reopens just fine. By the way, the bug I saw was not that files were zeroed out (ie, they were not filled with zero bytes), but that the file was replaced with a 0 byte length file. On Wed, 2007-11-21 at 10:47 +0100, Jan 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? > > - open the file > - do a slight modification > - save > > Is it OK after that, or is zeroed? Thank you in advance! > > Regards, > Jan > -- 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, 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 <@kendy_> _rene_: Can you please ask him if the size of the file > >> stays > >> untouched? > > > > File size is set to zero bytes > > Can you try the following packages (which disable the patches we have > in ooo-build compared to plain upstream for GnomeVFS) and whether that > makes a difference? > > http://people.debian.org/~rene/openoffice.org/test/gvfs > > Regards, > > Rene > -- 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: 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 perhaps. The error occurs in Writer and Calc (the only two parts of openoffice.org I tested). I saw this happen with a number of small documents that opened just fine if they were first copied to the local hard drive. And since when does that happen? With the upgrade to 2.3.0.dfsg-1 or later or before it (i.e.. with 2.2.1-x or 2.3.0-x)? Unfortunately I don't really have either nfs nor smb here to test currently so... I'll ask upstream whether this is known... Regards, Rene By the way, I am not using nfs on the Linux server I mentioned. The URL to the file indicates sftp, and I thought I was using samba. It normally "just works". Of course, the share on the Windows machine is smb. -- 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
I noticed it in the last few days. 2.3.0.dfsg-1 and -2 came fast after one another, but it would have very likely been one of those. I don't often edit documents on the machine running sid, but I do sometimes and documents getting wiped out is a bug that is quite noticeable. On Sun, 2007-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. Irretrievable data loss. No warning. > > Something to do with gnome Vfs perhaps. The error occurs in Writer and > > Calc (the only two parts of openoffice.org I tested). > > I saw this happen with a number of small documents that opened just fine > > if they were first copied to the local hard drive. > > And since when does that happen? With the upgrade to 2.3.0.dfsg-1 or > later or before it (i.e.. with 2.2.1-x or 2.3.0-x)? > > Unfortunately I don't really have either nfs nor smb here to test > currently so... > I'll ask upstream whether this is known... > > Regards, > > Rene > -- 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
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 data loss. No warning. Something to do with gnome Vfs perhaps. The error occurs in Writer and Calc (the only two parts of openoffice.org I tested). I saw this happen with a number of small documents that opened just fine if they were first copied to the local hard drive. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages openoffice.org-gnome depends on: ii gconf22.20.1-1 GNOME configuration database syste ii libc6 2.6.1-6GNU C Library: Shared libraries ii libgcc1 1:4.2.2-3 GCC support library ii libgconf2-4 2.20.1-1 GNOME configuration database syste ii libglib2.0-0 2.14.3-1 The GLib library of C routines ii libgnomevfs2-01:2.20.1-1 GNOME Virtual File System (runtime ii liborbit2 1:2.14.7-0.1 libraries for ORBit2 - a CORBA ORB ii libstdc++64.2.2-3The GNU Standard C++ Library v3 ii libstlport4.6c2 4.6.2-3STLport C++ class library ii openoffice.org-core 1:2.3.0.dfsg-2 OpenOffice.org office suite archit ii openoffice.org-gtk1:2.3.0.dfsg-2 GTK Integration for OpenOffice.org openoffice.org-gnome recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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]
