This problem looks very similiar to
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747333
Title:
apparmor rules deny lease backup
To
Public bug reported:
Occasionally, I see this in my logs:
Feb 4 02:27:07 giskard2 dhcpd[11485]: Can't backup lease database
/var/lib/dhcp/dhcpd.leases to /var/lib/dhcp/dhcpd.leases~: Operation not
permitted
Feb 4 02:27:07 giskard2 kernel: [237980.192671] audit: type=1702
*** This bug is a duplicate of bug 1431179 ***
https://bugs.launchpad.net/bugs/1431179
Ahh, in fact, I've found that by modifying
/lib/systemd/system/usb_modeswitch@.service and changing ExecStart to
be:
...
ExecStart=/bin/echo %i
...
Will cause udev to handle the device normally. So it is
*** This bug is a duplicate of bug 1431179 ***
https://bugs.launchpad.net/bugs/1431179
The same problem occurs with Ubuntu 16.04 LTS.
Cold-boot, particularly, this seems to fail.
Basically the problem is that usb_modeswitch_dispatcher is called with
incorrect arguments.
# systemctl --all
*** This bug is a duplicate of bug 1431179 ***
https://bugs.launchpad.net/bugs/1431179
However, calling, usb_modeswitch_dispatcher with the following:
# /usr/sbin/usb_modeswitch_dispatcher --switch-systemd 1-9:1.0
Seems to work fine.
--
You received this bug notification because you are a
@pitti, whilst you have a fix released as noted in the latest comment -
and the duplicate there is a class of modems (Huawei, which I also have)
where this still continues to fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This was automatically done for me whilst upgrading from 14.04 LTS to
16.04 LTS.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth 0.9.2-3ubuntu13.1
ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
Uname: Linux 3.13.0-95-generic x86_64
Considering that the 'bind9' package ships the root key (in
/etc/bind/bind.keys), I see no reason why it should not also be shipped
in the dnsutils package as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Considering that the 'bind9' package ships the root key (in
/etc/bind/bind.keys), I see no reason why it should not also be shipped
in the dnsutils package as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
dig, as supplied, will not validate a DNSSEC domain.
The +sigchase option should cause validation to occur but it does not.
As noted in http://bryars.eu/2010/08/validating-and-exploring-dnssec-
with-dig/ if a file called 'trusted-key.key' is present then dig will
use that.
Just a note on this 3 year old bug.
The gauge on the root servers has been gauged - DNSSEC was turned on
many years ago.
You can enable and turn this on by default and the traffic will be
neglible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
dig, as supplied, will not validate a DNSSEC domain.
The +sigchase option should cause validation to occur but it does not.
As noted in http://bryars.eu/2010/08/validating-and-exploring-dnssec-
with-dig/ if a file called 'trusted-key.key' is present then dig will
use that.
Public bug reported:
I am being bitten by the *exact* set of circumstances as in Debian bug #675016
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675016
In my case, it brought my network to a complete standstill, until I had
someone physically go and visit the machine.
This appears to have
** Bug watch added: Debian Bug tracker #675016
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675016
** Also affects: ifupdown via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675016
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Public bug reported:
1)
Description:Ubuntu 12.04.1 LTS
Release:12.04
2)
# apt-cache policy ppp
ppp:
Installed: 2.4.5-5ubuntu1
Candidate: 2.4.5-5ubuntu1
Version table:
*** 2.4.5-5ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100
Public bug reported:
1)
Description: Ubuntu 12.04.1 LTS
Release: 12.04
2)
# apt-cache policy ppp
ppp:
Installed: 2.4.5-5ubuntu1
Candidate: 2.4.5-5ubuntu1
Version table:
*** 2.4.5-5ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100
Public bug reported:
Hi,
This is with version: 4.2.4-5ubuntu2wf1, which is a backport to precise
of the current raring dhcp verion (4.2.4-5ubuntu2).
The only modification is changing the targeted release.
I was under the impression that ISC DHCP (now) supported prefix
delegation.
# dhclient
As noted in http://d.root-servers.org/renumber.html, the change will be
done on the 3rd Jan and the old IP address will be retried 6 months
later.
Could we get proposed-update packages before the 3rd Jun (when the old
IP will stop responding)?
I'm presuming that the Ubuntu guys are waiting until
As noted in http://d.root-servers.org/renumber.html, the change will be
done on the 3rd Jan and the old IP address will be retried 6 months
later.
Could we get proposed-update packages before the 3rd Jun (when the old
IP will stop responding)?
I'm presuming that the Ubuntu guys are waiting until
christopher.penal...@gmx.com wrote:
Anand Kumria, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please provide the information following
https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, can you
, Christopher M. Penalver
christopher.penal...@gmx.com wrote:
Anand Kumria, this bug report is being closed due to your last comment
regarding you no longer using Ubuntu. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
I have:
indicator-sound (0.7.9-0ubuntu2.1) oneiric-proposed; urgency=low
installed, and apport came up and directed me to this error.
Unhelpfully, it has not offered a bug pattern or core dump or anything.
However this occurred when I plugged in an external keyboard and used
the sound control
Public bug reported:
Whilst performing an upgrade from 11.04 - 11.10, I saw this message fly
by the upgrade terminal:
Processing triggers for initramfs-tools ...
dpkg: error: version '2.6.38.7-30.fc15.x86_64' has bad syntax: invalid
character in revision number
update-initramfs: Generating
#134 indicates that #6 is the reason for marking as wontfix and not open
to SRU.
#6 just says that it happens on logout.
Actually, this is a particularly egregious and annoying bug.
It happens on shutdown too.
It means that a laptop will lock-up, and you need to forcibly power it
off, and then
Confirming that this works against tightvnc servers (running Windows XP /
Windows Vista / Windows 7) - which is what I tested against.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598597
Title:
*** This bug is a duplicate of bug 817119 ***
https://bugs.launchpad.net/bugs/817119
Odd that this is marked as duplicate of a later bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/815401
This fix should also be done for the packages in Ubuntu LTS too (How do I mark
a bug as such in Launchpad?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/817119
Title:
Receiving a video
I've asked on IRC, and was told it was OK to subscribe the stable-sru team.
I was also told that https://wiki.ubuntu.com/StableReleaseUpdates is
geared towards the people uploading a fix (i.e. developers and not bug
reporters)
So, it isn't clear to me what other things I should do apart from
Public bug reported:
Hi,
openssh can lookup a host's key in the DNS (via the SSHFP record) and
use it compare hosts presented public key.
VerifyHostKeyDNS yes
I believe that is the connection is secured via DNSSEC that this option
will allow for the host's key to be automagically accepted.
Meant to say that /etc/ssh/config would be the place to put the default
configuration.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/825825
Title:
have DNS based verification
Public bug reported:
Hi,
openssh can lookup a host's key in the DNS (via the SSHFP record) and
use it compare hosts presented public key.
VerifyHostKeyDNS yes
I believe that is the connection is secured via DNSSEC that this option
will allow for the host's key to be automagically accepted.
Meant to say that /etc/ssh/config would be the place to put the default
configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/825825
Title:
have DNS based verification occur by default
To
*** This bug is a duplicate of bug 537934 ***
https://bugs.launchpad.net/bugs/537934
Amusing that the bug I'm a duplicate of was reported after me.
But so long as you are looking it, cool.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: 0004-dnssec-in-options.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2257805/+files/0004-dnssec-in-options.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
DNSSEC will place an additional burden on the network and, in particular, the
infrastructure based DNS servers.
The rationale to have the root key defined here but not used is that
will use some of the existing DNS infrastructure (via use of RFC5011)
and allow server operators to gauge load.
I
Note, I just checked Fedora 15 and the root key is setup similarly and is
*enabled* by default as well.
So you might just want to do so within Ubuntu as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: 0004-dnssec-in-options.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2257805/+files/0004-dnssec-in-options.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
DNSSEC will place an additional burden on the network and, in particular, the
infrastructure based DNS servers.
The rationale to have the root key defined here but not used is that
will use some of the existing DNS infrastructure (via use of RFC5011)
and allow server operators to gauge load.
I
Note, I just checked Fedora 15 and the root key is setup similarly and is
*enabled* by default as well.
So you might just want to do so within Ubuntu as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: 0001-Add-a-named.conf.keys-file-for-storing-various-keys.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256290/+files/0001-Add-a-named.conf.keys-file-for-storing-various-keys.patch
--
You received this bug notification because you are a member
** Patch added: 0002-Install-the-named.conf.keys-file.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256307/+files/0002-Install-the-named.conf.keys-file.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: 0003-Include-the-named.conf.keys-file.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256349/+files/0003-Include-the-named.conf.keys-file.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: 0001-Add-a-named.conf.keys-file-for-storing-various-keys.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256290/+files/0001-Add-a-named.conf.keys-file-for-storing-various-keys.patch
--
You received this bug notification because you are a member
** Patch added: 0002-Install-the-named.conf.keys-file.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256307/+files/0002-Install-the-named.conf.keys-file.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: 0003-Include-the-named.conf.keys-file.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256349/+files/0003-Include-the-named.conf.keys-file.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
libdbi is now clear in the later version of Ubuntu.
Any progress on an updated rrdtool?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rrdtool in Ubuntu.
https://bugs.launchpad.net/bugs/605871
Title:
[needs-packaging] rrdtool
libdbi is now clear in the later version of Ubuntu.
Any progress on an updated rrdtool?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605871
Title:
[needs-packaging] rrdtool 1.4.4
To manage
Public bug reported:
Hi,
It would be great if empathy support RFC6189 (ZRTP) across the various
protocols which support it.
Typically SIP and XMPP/Jingle since they both use RTP; just as having
OTR for messaging is useful, having ZRTP is useful for confidentially of
voice communications as
Hi Jordon,
You indicated in https://bugs.freedesktop.org/show_bug.cgi?id=16891 that
there would be a monthly update.
And earlier you indicated that people should watch:
https://bugs.freedesktop.org/show_bug.cgi?id=16891 and
https://bugs.freedesktop.org//show_bug.cgi?id=29904
Do you have a code
Public bug reported:
When installing linux-image-generic-lts-backport-maverick on Lucid (10.04) this
occurred.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/786113
Title:
package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to
install/upgrade: bcmwl kernel module failed to build
--
ubuntu-bugs
** Changed in: bind9 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/782614
Title:
make configuring DNSSEC validation easier
--
** Changed in: bind9 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782614
Title:
make configuring DNSSEC validation easier
--
ubuntu-bugs mailing list
All versions of BIND that Ubuntu has ever published could do with improvements
in making DNSSEC easier.
However, as noted in the linked instructions, the specific suggestions
apply to Bind 9.7+
Which, according to http://packages.ubuntu.com/search?keywords=bind9 is
Ubuntu 10.04 (Lucid) and
All versions of BIND that Ubuntu has ever published could do with improvements
in making DNSSEC easier.
However, as noted in the linked instructions, the specific suggestions
apply to Bind 9.7+
Which, according to http://packages.ubuntu.com/search?keywords=bind9 is
Ubuntu 10.04 (Lucid) and
Public bug reported:
Binary package hint: bind9
As noted here:
http://wiki.debian.org/DNSSEC#BIND9
The are some configuration changes required to enable DNSSEC validation.
I think it would be nicer if things could be made easier.
Create an empty file /etc/bind/named.conf.keys
Include the
Public bug reported:
Binary package hint: bind9
As noted here:
http://wiki.debian.org/DNSSEC#BIND9
The are some configuration changes required to enable DNSSEC validation.
I think it would be nicer if things could be made easier.
Create an empty file /etc/bind/named.conf.keys
Include the
Hi guys,
I am very happy to confirm that this worked great.
First it was gave me an indication that the remote server was not
responding (as per
http://bitcube.co.uk/content/puppet-errors-explained) and then it
correclt diagnosed a mismatched server identity.
Thanks for getting this fix in.
Hi guys,
I am very happy to confirm that this worked great.
First it was gave me an indication that the remote server was not
responding (as per
http://bitcube.co.uk/content/puppet-errors-explained) and then it
correclt diagnosed a mismatched server identity.
Thanks for getting this fix in.
This is an off-by-one snprintf fix; I think this warrants being backported to
Ubuntu 10.04 LTS (Lucid)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598597
Title:
Vinagre closes connection to
In Lucid's case the file is src/gvnc.c but I can confirm it works when gtk-vnc
is rebuilt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598597
Title:
Vinagre closes connection to tightvncserver
Public bug reported:
Binary package hint: bind9
1.
root@ns3:~# lsb_release -rd
Description:Ubuntu 10.04.2 LTS
Release:10.04
2.
ot@ns3:~# apt-cache policy bind9
bind9:
Installed: 1:9.7.0.dfsg.P1-1ubuntu0.1
Candidate: 1:9.7.0.dfsg.P1-1ubuntu0.1
Version table:
***
Public bug reported:
Binary package hint: bind9
1.
root@ns3:~# lsb_release -rd
Description:Ubuntu 10.04.2 LTS
Release:10.04
2.
ot@ns3:~# apt-cache policy bind9
bind9:
Installed: 1:9.7.0.dfsg.P1-1ubuntu0.1
Candidate: 1:9.7.0.dfsg.P1-1ubuntu0.1
Version table:
***
Public bug reported:
On an IPv6 network, routes have a marked lifetime.
So, if you are connected to two IPv6 networks you may have multiple
default routes.
Not such a problem.
kalki:[~]% ip -6 route
2001:44b8:75ee:19d2::/64 dev eth1 proto kernel metric 256 expires 22sec mtu
1500 advmss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711299
Title:
ipv6 routes which expire are not deleted quickly
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
See if you can contact someone from the Canonical server team. Personally I'd
also try to contact the ntp maintainer via IRC too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
https://bugs.launchpad.net/bugs/104525
See if you can contact someone from the Canonical server team. Personally I'd
also try to contact the ntp maintainer via IRC too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104525
Title:
Public bug reported:
Binary package hint: puppet
Hi,
There are many versions of puppet, fortunately lucid (10.04) has a
relatively new version (merely called legacy from puppetlabs).
Unfortunately it has a number of bugs / issues, one of which I have
recently encountered is an underlying bug
Public bug reported:
Binary package hint: puppet
Hi,
There are many versions of puppet, fortunately lucid (10.04) has a
relatively new version (merely called legacy from puppetlabs).
Unfortunately it has a number of bugs / issues, one of which I have
recently encountered is an underlying bug
StabeUpdateRequest for Ubuntu 10.04 LTS.
IMPACT: As additional distributions switch to generating their initrd
using dracut, grub2 will become unable to boot them.
FIXED: The bug has been fixed upstream in os-prober version 1.39
(included in Ubuntu 10.10)
As the bug has been fixed in a newer
As an interesting data point, I installed the propreitary NVidia drivers and
suspend / resume work perfectly (same kernel).
So I think that this is related to how Noveau does something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Jeremy,
I read the wiki page you indicated. (It would be good if you could
duplicate this bug and file it against the appropriate web person to
have this machine removed from the certified list -- since it seems to
be incorrect).
According to that page, I looked at:
Public bug reported:
Hi,
Ubuntu fails to correctly suspend / resume on this device.
Despite is being marked as certified. I am unclear if the certification
is done by the vendor or Canonical.
But http://webapps.ubuntu.com/certification/hardware/201001-4955/ is
clearly not correct.
--
fails to suspend / resume on certified hardware
https://bugs.launchpad.net/bugs/675573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Without an explanation as to why this marked, remarking as 'new'.
I have experienced this error (Error 22) when wubi has finished copying
the files but not completed setup of the boot environment.
Thus leaving the user without a working install when done via wubi.
** Changed in: ubuntu
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/654468/+attachment/1671048/+files/Dependencies.txt
--
uno-libs3 has no changelog
https://bugs.launchpad.net/bugs/654468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: openoffice.org
In update-manager, uno-libs3 is offered as an update but displays nothing in
the 'changes' section:
Changes for the versions:
1.6.1+OOo3.2.1-6ubuntu1
1.6.1+OOo3.2.1-7ubuntu1
The list of changes is not available yet.
Please use
OK - sorry that I've been unable to update this bug.
I have four kernels on my system (currently).
kernel | attempt 1 | attempt 2 | attempt 3
--
2.6.32-24-gen| good| good| good
2.6.35-19-gen| bad
Sure - in progress. It appears that Launchpad relies on a text browser to
support button type=submit ... in order to authenticate. Which w3m does not
support.
(sigh.)
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621691/+files/Dependencies.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621693/+files/GdmLog1.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621694/+files/GdmLog2.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621702/+files/UdevDb.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: DRM.card0.DVI.I.1.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621690/+files/DRM.card0.DVI.I.1.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621695/+files/Lspci.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621696/+files/Lsusb.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621698/+files/ProcCpuinfo.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621699/+files/ProcInterrupts.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621697/+files/PciDisplay.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621705/+files/XorgLogOld.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621692/+files/GdmLog.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621701/+files/RelatedPackageVersions.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a
apport information
** Tags added: apport-collected
** Description changed:
X no longer starts when using linux-image-2.6.35-20-generic (2.6.35-20.29)
but X starts when using
linux-image-2.6.32-24-generic (2.6.32-24.42)
I am using the free Noveau drivers.
ProblemType: Bug
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621689/+files/CurrentDmesg.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621700/+files/ProcModules.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621703/+files/UdevLog.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/640432/+attachment/1621704/+files/XorgLog.txt
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: xserver-xorg-video-nouveau (Ubuntu Maverick)
Status: Incomplete = Confirmed
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
tried with 2.6.35-22.33; no change.
I noticed this in the X log file:
[12.064] (II) Initializing built-in extension GESTURE
[12.068] (II) AIGLX error: dlopen of /usr/lib/dri/nouveau_dri.so failed
(/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or
directory)
** Summary changed:
- X does not start (noveau)
+ X does not start (nouveau)
--
X does not start (nouveau)
https://bugs.launchpad.net/bugs/640432
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
1 - 100 of 382 matches
Mail list logo
