Hi,
I can't speak for the issue raised by Alexander.
Though the original issue I've reported is gone after having moved away
from wdm. Still happily using xdm :)
Cheers
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Seems like the same problem here.
Linux guest (VirtualBox) trying to access a Windows share (on host,
Windows 7).
# cat /proc/10254/stack
[c121e547] wait_for_response.isra.5+0x97/0xf0
[c121f41b] SendReceive+0xeb/0x240
[c1202ff5] CIFSSMBNegotiate+0x155/0x6e0
[c1224945] cifs_negotiate+0x15/0x60
Hi,
just came across the same issue.
Luckily linux-image-2.6.32-5-686 from squeeze was still installed.
An update of initramfs using update-initramfs -u -k 3.2.0-4-486 while
running 2.6.32 appears to have solved the problem. I've not modified
/etc/initramfs-tools/modules (file is still empty).
I recently switched from wmii to i3 for managing my windows.
This didn't cure the problem.
Switching from wdm to xdm seems to resolve the problem.
It's just a day of testing so far, though looks pretty promising.
I'll report back in a few days...
Cheers,
Florian
--
To UNSUBSCRIBE, email
The issue still occurs.
Maybe this piece of kernel log is pointing to something more useful:
plugin-containe[3683]: segfault at b2d025e4 ip b664a4e6 sp b2389034
error 6 in libpthread-2.11.3.so[b664+15000]
It's always printed if the problem occurs.
Cheers
Florian
--
To UNSUBSCRIBE,
Just coincidentally stumbled over .xsession-errors.
Shortly after the session start at 12:55 the xserver was restarted.
Is this output below of any help? Or just a consequence?
Thanks.
Xsession: X session started for flo at Sat Dec 24 12:55:57 CET 2011
XIO: fatal IO error 11 (Resource
Am 26.10.2011 23:47, schrieb Julien Cristau:
Is there anything I can do to trap that obscure piece of software
sending SIGQUIT?
IIRC the times I've seen this it was plymouth or something stealing the
console out from under X. Maybe check for things opening
/dev/tty[0-9]*.
I don't have
Am 07.10.2011 20:43, schrieb Julien Cristau:
Fatal server error:
Caught signal 3 (Quit). Server aborting
OK, I missed this one the first time. I don't think that's a bug in X,
something on your system is sending us SIGQUIT when they shouldn't.
Is there anything I can do to trap that obscure
Am 07.10.2011 19:39, schrieb Julien Cristau:
There seems to be 0 content in your mail other than the logs added by
reportbug. You'll have to do better.
Thanks for your advice.
I did enter some information on the first screen presented by
reportbug. Unfortunately it got lost for a reason I
Package: xserver-xorg-dev
Version: 2:1.4.2-10.lenny2
Severity: important
These headers refer to #include pixman/pixman.h, which should be
pixman-1/pixman.h provided by package libpixman-1-dev on Lenny:
/usr/include/xorg/fb.h
/usr/include/xorg/miscstruct.h
/usr/include/xorg/picture.h
This
Package: libpixman-1-dev
Version: 0.10.0-2
Severity: important
This header refers to #include pixman/pixman-version.h, which should be
pixman-1/pixman-version.h
Other packages depending on this package are unusable, e.g. xserver-xorg-dev.
Florian
-- System Information:
Debian Release:
Brice Goglin schrieb:
Florian Boelstler wrote:
Package: xserver-xorg-dev
Version: 2:1.4.2-10.lenny2
Severity: important
These headers refer to #include pixman/pixman.h, which should be
pixman-1/pixman.h provided by package libpixman-1-dev on Lenny:
/usr/include/xorg/fb.h
/usr/include
Package: icedove
Version: 2.0.0.19-1
Followup-For: Bug #488970
Issue still exists with current version in Lenny.
No matter for which custom field of an email header a filter is applied.
Any idea to circumvent this problem?
It has been working with the version of Icedove found in Etch.
TIA
Package: imapsync
Version: 1.252-1
Severity: normal
When an IMAP server contains a folder named like an email address
syncing fails (e.g. folder name is [EMAIL PROTECTED]).
It seems imapsync treats that name as the account name on the
target IMAP server.
When source folder is renamed before to a
Could be a problem in binutils, which is not fixed in Etch as of today
(#393841).
Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391445 for
an archived bug, which contains the full story.
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Can confirm behavior described by Hector.
Patch makes it properly work on Etch.
Please apply provided patch.
Thanks,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: mga-vid-common
Version: 2.6.18-2
Severity: important
After upgrading to Etch mga-vid wasn't properly setup for udev.
/etc/udev/mga-vid-common.rules was in place, but not symlinked from
e.g. /etc/udev/rules.d.
Since latest mga-vid driver device file is now called /dev/mga_vid0 all
Package: xine-ui
Version: 0.99.4+dfsg+cvs2006-1
Severity: wishlist
It seems that mga/xmga is not available any more in xine.
It was supported by xine in Sarge, Etch seems to have dropped support
for Matrox backend scaler.
I couldn't find any appropriate changelog entries.
mga-vid driver is
Can confirm behavior and workaround described by Vincent Bernat.
Using linux-source-2.6.17-6 and linux-source-2.6-17-8.
Cheers,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
version 1.0.2-2.sarge1.0.8b.2 from asac works fine here as well on two
systems running Sarge.
Thanks,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Steve Langasek wrote:
Yep, this is not a bug in the Debian package. Please get rid of this stale
old version of libdc.so.0 from /usr/local.
*OUCH*, I didn't notice that.
I am wondering where that lib came from...
Anyway, thanks for your help.
Cheers,
Florian
--
To UNSUBSCRIBE, email
Steve Langasek wrote:
Ok. Could you please send the output of ldd /usr/bin/valknut?
sure:
[EMAIL PROTECTED]:~$ ldd /usr/bin/valknut
libdc.so.0 = /usr/local/lib/libdc.so.0 (0x4002e000)
libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0x400a2000)
libxml2.so.2 =
Steve Langasek wrote:
Ok, I did a little more digging, and it looks like the missing symbol may
actually belong to libdc0 rather than to valknut itself. Could you make
sure you have libdc0 version 0.3.7-2 installed?
libdc0 (0.3.7-2) is installed. I also reinstalled it. Same result.
Thanks
Package: valknut
Version: 0.3.7-1
Severity: grave
Justification: renders package unusable
We believe that the bug you reported is fixed in the latest version of
valknut, which is due to be installed in the Debian FTP archive:
dcgui-qt_0.3.7-1_i386.deb
to
Package: kernel-patch-suspend2
Version: 2.1.8.9-1
Severity: important
Just tried to build a kernel using make-kpkg with
kernel-source-2.6.8-16. The message given as follows:
E: no applicable suspend2 patch found for this kernel. With a recent
E: kernel, this usually means that I have not yet
Steve Langasek wrote:
Ok, so it sounds like this was an unrelated extension problem.
Confirmed. After removing everything from the extensions directory
(SwitchProxy) and XUL.mfasl Firefox works well.
Reinstallation of SwitchProxy rendered it unusable again.
signature.asc
Description: OpenPGP
Steve Langasek wrote:
I was referring to the initial bug report:
Whenever I try to write anything in the address bar or google search bar
the Firefox chases (I uninstalled all extensions and wiped out all
configuration files)
In my situation Firefox freezes and sometimes renders KDE unusable.
Package: mozilla-firefox
Version: 1.0.2-1
Followup-For: Bug #299486
Can confirm described behaviour on kernel 2.6.8 built from official
Debian kernel-source-2.6.8-15 (Applied Debian patches kernel-patch-mppe,
kernel-patch-suspend2).
mozilla-firefox-gnome-support is not installed.
-- System
Steve Langasek wrote:
There is a lot of different behavior described in this bug report. Please
confirm it with a backtrace and a description of what you did that caused a
crash, so that we know whether your crash is actually related.
I was referring to the initial bug report:
Whenever I try to
Package: kernel-patch-suspend2
Version: 2.1.8.2-5
Severity: normal
After successful application of the patch a make-kpkg clean fails:
W: suspend2 patch not applied.
Patch /usr/src/kernel-patches/all/2.6.8/unpatch/suspend2 failed.
The message patch not applied is definitely wrong.
Florian
Package: kernel-patch-suspend2
Version: 2.1.8.2-4
Severity: important
Tried to apply patch on kernel-source-2.6.8-15 from Sarge:
Applying 200-agp-resume-support ...
Applying 202-ne2k ...
Applying 203-ali5451 ...
Applying 208-e820-table-support ...
Applying 210-workthreads ...
Applying
Hi there,
there are many people out there using Debian today.
Some of them own a Epson EPL-based printer.
From time to time we meet people who come across the same problem on
and on.
George described the problem already.
I have prepared a Debian package found on my personal site [1] to help
Hi,
just want to mention that I can reproduce the problem with a kernel
built from kernel-source-2.6.8-12 using:
cdda2wav -t 1 dev=ATA:1,0,0
and
cdda2wav -t 1 dev=ATAPI:0,0,0
However it does not occur when I specify the device as
cdda2wav -t 1 dev=/dev/hdc
I can also state that paranoia mode
Problem seems to be solved now (2.6.8-12)
Thanks,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
34 matches
Mail list logo
