I just had this issue on a 32-bit machine.
I went from 1.98~20100107-1 to 1.98~20100115-1 and was unbootable.
I wouldn't even get the grub prompt. I would get the "error: no such
disk" and reboot.
I was able to boot a knoppix disk and mount up all my partitions and
everything hardware wise is fi
I get the same with a wired connection.
iface eth0 inet dhcp
I get messages that the pid file name is too long.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Downgrading "ifupdown" to the unstable version 0.6.9 fixes the issue of
pid file name being too long.
The bug still exists in the experimental version 0.7~alpha3.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...
Package: udev
Version: 146-2
Severity: normal
*** Please type your report below this line ***
When running "ifup eth0" I get an "Illegal number" error below:
# ifup eth0
Internet Systems Consortium DHCP Client 4.1.0
Copyright 20
The error comes from /lib/udev/hotplug.functions from this block.
If I comment it out I don't get the error.
if [ "$UDEV_LOG" -a "$UDEV_LOG" -ge 7 ]; then
DEBUG=yes
fi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
That works.
I get an "error" at the end of the output:
# ifup eth0
Internet Systems Consortium DHCP Client 4.1.0
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:1e:4f:e4:c6:3c
Sending on LPF/eth0/0
Package: isc-dhcp-client
Version: 4.1.0-1
Severity: important
*** Please type your report below this line ***
dhclient provided with isc-dhcp-client 4.1.0-1 can't handle the default
pid file name used when using ifup.
# ifup eth0
/var/run/dhclient.eth0.pid: interface name too long (is 26)
My int
Thanks for the info OdyX!
I DL'ed and installed xserver-xorg-video-intel_2.7.99.901-3_amd64.deb
and then installed the xorg-core -3 and restarted just fine.
Apelete -
I assume once you installed the new intel driver you also installed the
-core -3? I would guess since there is a ABI change tha
Just a FYI -
This is the same with KDM / KDE.
KDM comes up but once it tries to go to the desktop X crashes.
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4ede76]
1: /usr/bin/X(xf86SigHandler+0x39) [0x483249]
2: /lib/libc.so.6 [0x7f8a03358d90]
3: /usr/lib/libdrm_intel.so.1 [0x7f8a0116432c]
4: /
Subject: cups or ghostscript needs to depend on ghostscript-cups
Package: ghostscript-cups
Version: 8.64~dfsg-10
Severity: important
*** Please type your report below this line ***
cups or ghostscript needs to depend or recommend ghostscript-cups.
Without ghostscript-cups I was missing /usr/lib/cu
I get this same error when trying to update samba-common from
3.4.0~pre1-1 to 3.4.0~pre2-1
The upgrade at the moment would break smbclient and smbfs anyway but
that may have something to do with it.
Uncaught exception: ./generic/problemresolver/choice.h:294: const
typename PackageUniverse::versio
Package: python-apt
Version: 0.7.90
Severity: important
Version 0.7.90 for amd64 depends on:
libapt-inst-libc6.7-6-1.1
libapt-pkg-libc6.7-6-4.6
Which are unavailable.
apt and apt-utils 0.7.21 provide:
libapt-pkg-libc6.9-6-4.7
and
I had the same issue on a Intel 82Q35 Express.
I for a couple days now haven't had any issues by switching to use UXA
and KMS (kernel-based mode setting).
I am not sure which fixed it but I don't have corruption.
To enable UXA I put this in the Device section of xorg.conf:
Option "AccelM
Yes downgrading worked.
Upgrading to 1.2.7 broke "splashy test" and then downgrading right away
fixed it.
So now is this a splashy issue or a libdirectfb?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
Package: splashy
Version: 0.3.13-3
Severity: important
On boot I get the error:
Splashy ERROR: Couldn't splashy_start_splasy(). Error -3
and then:
Splashy ERROR: Connection refused
I am using the Debian compiled kernels so spla
Package: xserver-xorg-video-intel
Version: 2:2.2.0-1
Severity: normal
I am not sure if this is a bug with xserver-xorg-video-intel or xserver-xorg.
When I try to switch to a virtual console (ctrl-alt-F?) I get only a blank
screen.
The monitor goes into power save mode.
I am still able to type
Package: squid
Version: 2.6.1-3
Severity: important
I have squid 2.6.1-3 setup as a transparent proxy and it is denying my tivo
from getting through.
>From the access log:
1153942317.226 5 192.168.0.5 TCP_DENIED/403 1494 POST
http://204.176.49.2:1/tivo-service/mercury.cgi - NONE/- text/html
Package: bittorrent
Version: 3.4.2-3sarge0.1
Followup-For: Bug #317334
I have this in the SPARC version too.
-- System Information:
Debian Release: 3.1
Architecture: sparc (sparc64)
Kernel: Linux 2.6.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages bittorrent depends on
18 matches
Mail list logo
