Hi Jonas,
You state that you closed this bug because I didn't reply within
seven months.
However, I did reply on July 4 to your message from July 1 and
have been waiting since then for your reply:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628038#15
In your message you offered to prepare
On Fri, 01 Jul 2011 00:16 +0200, Jonas Meurer jo...@freesources.org
wrote:
Thanks a lot for this investigation. But the cryptsetup package changed
the way it handles loopback devices in the meantime. Upstream cryptsetup
has loopback support integrated since version 1.2.0. Therefore, I
removed
crypttab:
# target name source device key file options
name/name.enc_volnone
precheck=un_blkid,check=blkid,cipher=aes-cbc-essiv:sha256,size=256,hash=ripemd160
So I was surprised to discover *two* loopback devices configured:
saturn:/home/jdietrch# losetup -a
/dev/loop0: [0801
On Wed, 09 Feb 2011 13:16 +0100, Cyril Brulebois k...@debian.org
wrote:
Hi James,
jdiet...@fastmail.fm jdiet...@fastmail.fm (07/10/2009):
I have a Matrox Millennium G400 card. I am experiencing serious
display problems with some 3d applications.
[…]
Let me know if there are any more
Package: evince
Version: 2.30.1-2
Severity: normal
Evince segfaulted every time I tried to run it. So I created a new user
to be sure no settings were messed up, and the same thing still
happened:
-
t...@saturn:~$ evince
Just wanted to mention that this bug should probably have a severity
higher than wishlist.
I installed namebench today (from the Debian package), but had trouble
getting it to run successfully. I found that the problem had already
been reported to
Package: gnome-control-center
Version: 1:2.26.0-1
Severity: normal
File: /usr/bin/gnome-font-viewer
The subject says it all: gnome-font-viewer hangs on the attached ttf.
In a terminal window, I type the following command:
gnome-font-viewer MBFCustom.ttf
Immediately the CPU usage goes to 100% and
Package: nautilus
Version: 2.26.2-5
Tags: patch
Background:
This bugreport concerns nautilus' support for XDS. For more information
about what XDS is and the standard for implementing it, see
http://www.newplanetsoftware.com/xds/
Short version:
Nautilus doesn't implement the F fallback in the
On Thu, 11 Jun 2009 16:11 +0200, Josselin Mouette j...@debian.org
wrote:
Le jeudi 11 juin 2009 à 09:57 -0400, jdiet...@fastmail.fm a écrit :
Let me know if you have any questions, or if there's anything else I can
do to help.
Yes: why are you sending this to the Debian BTS? Such an issue
On Thu, 11 Jun 2009 18:26 +0200, Josselin Mouette j...@debian.org
wrote:
My suggestion would be to send the patch to bugzilla, then to prod the
developers on nautilus-l...@g.o and discuss the issues there, since they
don’t follow bugzilla very closely.
Thanks for your suggestion; that's what
Package: python-psycopg2
Version: 2.0.7-1
Severity: minor
There is a typo in psycopg2.NotSupportedError.__doc__:
[EMAIL PROTECTED]:~$ python
Python 2.5.2 (r252:60911, Apr 17 2008, 13:15:05)
[GCC 4.2.3 (Debian 4.2.3-3)] on linux2
Type help, copyright, credits or license for more information.
$? shows the
return value of the most recent command.) Note that the output file is
about 19MB.
[EMAIL PROTECTED]:~$ dcraw -c CRW_6903.CRW CRW_6903.ppm
[EMAIL PROTECTED]:~$ echo $?
0
[EMAIL PROTECTED]:~$ ls -l CRW_6903.ppm
-rw-r--r-- 1 jdietrch jdietrch 19046801 2008-04-30 08:27 CRW_6903.ppm
[EMAIL
, and ufraw-batch
returns 0 as it should.
[EMAIL PROTECTED]:~$ ufraw-batch CRW_6903.CRW
ufraw-batch: loaded CRW_6903.CRW
ufraw-batch: saved /home/jdietrch/CRW_6903.ppm
[EMAIL PROTECTED]:~$ echo $?
0
These next two show ufraw-batch reporting errors, but the return
value is still 0.
[EMAIL PROTECTED]:~$ ufraw
Package: ufraw
Version: 0.13-1+b1
Severity: normal
The manpage for ufraw says this:
--out-type=ppm8|ppm16|tiff8|tiff16|jpeg
But /usr/share/doc/ufraw/README.gz
says this about the UFRaw-0.13 release:
* Added option to save as PNG 8 or 16 bits.
The manpage ought to list the png formats as
Package: mlocate
Version: 0.19-1
Severity: normal
I have mlocate installed in a vserver. Every day cron mails
me a message like this:
/etc/cron.daily/mlocate:
ioprio_set: Operation not permitted
run-parts: /etc/cron.daily/mlocate exited with return code 1
Let me know if I can provide any
Hi,
I recently upgraded libgl1-mesa-dri to version 7.0.2-4
and now blender starts up without crashing.
I don't know what changed from 7.0.2-2 to 7.0.2-4 so I
don't know if the bug was fixed or just avoided somehow.
Therefore, I am not closing the bug at this time, but
rather letting you decide
Package: util-vserver
Version: 0.30.214-6
Short version:
When running the command
vserver tethys start
there is an error if the host's /etc/fstab contains a mount point
with a space.
Long version:
I have this line in the /etc/fstab of the host system:
/Linked\040Pictures
Package: mount
Version: 2.13-8
When a mount point with spaces exists, it is not umounted at shutdown.
I have this line in my fstab:
/mbf/Linked\040Pictures /mbf_employee/Linked\040Pictures none bind 0 0
Then after executing a 'shutdown -h now' I get these messages near
the end of the shutdown
Hi,
A space doesn't work, because /etc/fstab uses the space for a
delimiter between fields. What does work, though, is to put
the octal escape code for the space character: \040 .
So if you change your fstab line to the following, it should work:
/dev/a\040space /mnt/sdb1vfat
Hope this
Hi,
A space doesn't work, because /etc/fstab uses the space for a
delimiter between fields. What does work, though, is to put
the octal escape code for the space character: \040 .
So if you change your fstab line to the following, it should work:
//dorje/Documents\040and\040Settings
Package: gimp-refocus
Version: 0.9.0-1
Severity: important
When I click OK in the Refocus filter dialog box, the dialog box
disappears and the progress bar at the bottom of the GIMP window
containing my image starts progressing. However, when it has nearly
reached completion, the following
Package: libgl1-mesa-dri
Version: 7.0.1-2
Severity: important
Blender (2.45-1) crashes on startup in mga_dri.so:
guessing 'blender-bin' == '/usr/bin/blender-bin'
Compiled with Python version 2.4.4.
Checking for installed Python... got it!
/usr/bin/blender: line 46: 19547 Segmentation fault
On Thu, 04 Oct 2007 22:36:14 +0200, Brice Goglin
[EMAIL PROTECTED] said:
Your backtrace would be better if you enter 'bt full' instead of 'bt' to
display it.
Here it is:
Core was generated by `blender-bin'.
Program terminated with signal 11, Segmentation fault.
#0
23 matches
Mail list logo
