Possibly just a bad card. I see the same freeze and corruption with
fglrx-2:14.201-0ubuntu2. I've swapped out the video card and will see if
it still happens (it's different a hardware configuration, but just in
case).
Is there a way I can close this out ?
--
You received this bug notification b
** Summary changed:
- adeon :02:00.0: ring 0 stalled for more than 10008msec
+ radeon :02:00.0: ring 0 stalled for more than 10008msec
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392727
Ti
Occasionally this gets so bad X locks up completely
Attached is the Xorg log from such a lockup
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1392727/+attachment/4260732/+files/Xorg.0.log.old
--
You received this bug notification bec
% apt-cache policy xserver-xorg-video-radeon
xserver-xorg-video-radeon:
Installed: 1:7.4.0-2ubuntu2
Candidate: 1:7.4.0-2ubuntu2
Version table:
*** 1:7.4.0-2ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
% apt-cache poli
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1392727/+attachment/4260491/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "xdpyinfo"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1392727/+attachment/4260494/+files/xdpyinfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13927
** Attachment added: "lspci -v"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1392727/+attachment/4260490/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392727
Oops. Sorry. lspci -vvnn as root
** Attachment added: "lspci -vvnn"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1392727/+attachment/4260492/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Public bug reported:
Screen freezes and displays checkerboard like corruption. Kernel log contains:
Nov 14 07:44:35 gromit kernel: [211056.796329] radeon :02:00.0: ring 0
stalled for more than 1msec
Nov 14 07:44:35 gromit kernel: [211056.796333] radeon :02:00.0: GPU lockup
(waiting f
Ok. I've managed to re-create this via a bootable live usb image, so I'm
at least confident it's not some kruft in my system.
To reproduce from a clean install:
sudo apt-get install libpam-ldap qemu-kvm libvirt-bin
(point ldap at ldap server,)
sudo auth-client-config -a -p ldap_example
add
@serge,
In my case, no: "sudo stop libvirt-bin; sudo start libvirt-bin" does not
always completely solve the problem.
'virsh list' worked find after reboot and I was able to bring up virt-manager
as well.
% virsh list
IdName State
--
Ok. I give up. I do not understand upstart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382046
Title:
libvirt-bin unaware of uids on LDAP
To manage notifications about this bug go to:
https://bu
..err to continue #15. I added:
log_msg "libvirt-bin: starting nscd at $(date)"
/etc/init.d/nscd start
/etc/init.d/nslcd start
sleep 10
..and:
log_msg "libvirt-bin: starting libvirtd at $(date)"
exec /usr/sbin/libvirtd $libvirtd_opts
I see, in the new
I am a novice at upstart, but I don't see upstart jobs for slapd or, in
my case, ncsd. So I went ahead and did horrible things to the existing
libvirt-bin upstart job thing:
** Attachment added: "Hacked libvirt-bin.conf"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1382046/+attachme
Hmm. I take #11 back - I could have sworn I saw it, but I can't
reproduce it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382046
Title:
libvirt-bin unaware of uids on LDAP
To manage notification
I find that I need to restart libvirt-bin multiple times in order to be able to
reliably use virsh. Once will usually get virt-manager up and running, but
attempting send-key from the command line will start to fail again:
% virsh send-key Windows7 29 56 111
error: failed to connect to the hyper
Public bug reported:
With autofs 5.0.7-3ubuntu1.1 and autofs-ldap 5.0.7-3ubuntu1.1, automount
starts up fine. With the new version (5.0.8-1ubuntu1) in utopic, it
hangs shortly after displaying the ldap lookup information:
With 5.0.8-1ubuntu1
% automount -V
Linux automount version 5.0.8
Director
Well, I am now magically fixed.
I appear to have had some Bad Packages from some prior mucking around
with the ATI driver. I uninstalled xserver-xorg-core (!) and then re-
installed the stock ubuntu packages and now auto-hide plays nicely with
my dual monitors.
For reference, I appeared to have h
Same as initial report. With launcher auto-hide enabled, I can get to
and from the second monitor only by moving the mouse quickly across the
area covered by the panel and _maybe_ the bottom edge of the screen.
I'm a little surprised this isn't more widely reported.I'm also using
the radeon driver
*** This bug is a duplicate of bug 1028725 ***
https://bugs.launchpad.net/bugs/1028725
Is there any way to track the 'progress' of the private bug ? This is
rendering evolution completely unusable for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1028725 ***
https://bugs.launchpad.net/bugs/1028725
There we go:
Program received signal SIGSEGV, Segmentation fault.
e_web_view_update_fonts (web_view=0xb96bebe0) at e-web-view.c:2815
2815e-web-view.c: No such file or directory.
#0 e_web_view_update_fon
*** This bug is a duplicate of bug 1028725 ***
https://bugs.launchpad.net/bugs/1028725
Since I can't see the private bug, and this is driving me nuts:
Program received signal SIGSEGV, Segmentation fault.
0xb520e58c in e_web_view_update_fonts (web_view=0xb8c685e0)
at e-web-view.c:2809
2809
Well, I removed .ibex.index.data, .ibex.index, and .cmeta and also
folders.db (? it this even still needed - I've been carrying evolution
data around for around 10 years now). One of those made the search work.
I guess I should point out that, in my case at least, these are searches
in local maild
** Changed in: evolution (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746663
Title:
search messages function doesn't work properly
To manage notifications ab
This is still present in evolution 3.2.2 on oneric. The reason it
doesn't show up in other peoples testing is, I believe, because it
requires that the index files that evolution uses to speed the searches
need to be out of date with the actual mail. I have no idea what causes
this to happen, but, a
I can also print duplex again after switching to hpijs
--
GTK Printing Dialog: Duplex printing on HP inkjets does not work
https://bugs.launchpad.net/bugs/657357
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
I think we're talking about two separate problems. I recompiled sudo-ldap as
above, and still receive:
sudo: setresuid(user_uid, user_uid, ROOT_UID): Operation not permitted
..when I have ssl enabled in /etc/ldap.conf
In my case, the sudoers file is always local and contains:
ALL=(ALL) ALL
I can also make it work by using ldap instead of ldaps. (and am also
using a self-signed cert for the ldap server).
--
NSS using LDAP on Karmic (alpha 4) breaks 'su' and 'sudo'
https://bugs.launchpad.net/bugs/423252
You received this bug notification because you are a member of Ubuntu
Bugs, which
Eh. Going back to the Jaunty version of sudo didn't appear to help, so
maybe it's not the sudo package itself ?
This did work on Jaunty.
--
NSS using LDAP on Karmic (alpha 4) breaks 'su' and 'sudo'
https://bugs.launchpad.net/bugs/423252
You received this bug notification because you are a member
Apparently still present in RC. As a clarification, users present in
/etc/passwd can still sudo just fine. Users present only via ldap
cannot.
My suspicion is that the initial reporter had, as Scott G. suggested,
the user present both via ldap and /etc/passwd, with the result that
hitting the loca
Confirmed - -ubuntu4 w/ disable_xdamage set to true gets me an properly
updated desktop as well. Thanks!
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of
This doesn't seem to improve things for me:
dpkg -s vino:
Package: vino
Status: install ok installed
Architecture: amd64
Version: 2.26.1-0ubuntu2
gconftool-2 -g /desktop/gnome/remote_access/disable_xdamage
true
killall vino-server
Still get no updates on vncviewer. Maybe user error ?
--
Compiz
Also seeing on fglrx driver:
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.60.40
Module class: X.Org Video Driver
(--) fglrx(0): Chipset: "ATI Radeon HD 3600 Series" (Chipset = 0x9598)
x11vnc seems to work fine.
** Summary c
I can confirm that it appears to be fixed in the development version of
mesa. If anyone can reproduce it on the mesa development tree, I suspect
the developers might be better able to fix it.
--
intel gm965 freezes with 3d applications
https://bugs.launchpad.net/bugs/120834
You received this bug
'Full' requested gdb output (which doesn't actually add any value,
but..) I have libgl1-mesa-dri-dbg installed but don't get debug symbols
from i965_dri automagically ?
** Attachment added: "gdb output"
http://launchpadlibrarian.net/10344524/gdb-Xorg.txt
--
intel gm965 freezes with 3d applica
Kernel DRI debug output attached. I can get this to happen consistently
with 'skyrocket'.
** Attachment added: "DRM debug output from syslog"
http://launchpadlibrarian.net/10344511/drm_output.log
--
intel gm965 freezes with 3d applications
https://bugs.launchpad.net/bugs/120834
You received t
Sigh. I should actually include the attachment I guess.
** Attachment added: "Xorg backtrace"
http://launchpadlibrarian.net/10319870/Xorg.bt3
--
intel gm965 freezes with 3d applications
https://bugs.launchpad.net/bugs/120834
You received this bug notification because you are a member of Ubunt
I'm going to assume that this is the same problem that I'm having, in
that some gnome-screensaver modules cause X to crash. I've attached a
backtrace from a crashed X session (something to do with DRI locking
maybe ?)
Thinkpad T61 w/ 965GM graphics:
00:02.1 Display controller: Intel Corporation Mo
Ah. So what confused me was that what used to be eth0 is now eth1. After
fixing interfaces to refer to eth1, I can now boot and log in. Thanks!
--
After upgrading my server to Gutsy booting hangs at "Starting kernel log daemon"
https://bugs.launchpad.net/bugs/150006
You received this bug notifica
So after messing around with this some more, I've given up. I cannot
boot without going through single-user mode and removing the ldap
references in nsswitch.conf. After doing that, I need to add them back
in to be able to access the accounts. Note that 'id ' works fine
after adding the ldap entrie
Definitely won't continue after 5 minutes. Many hours passed with it
still 'starting kernel log daemon'
--
After upgrading my server to Gutsy booting hangs at "Starting kernel log daemon"
https://bugs.launchpad.net/bugs/150006
You received this bug notification because you are a member of Ubuntu
Same thing. Simple setup with a Dapper LDAP server and a Gutsy LDAP
client. Hangs at 'Starting kernel log daemon', although haven't had the
patience to wait to see if it'll continue after waiting 5 minutes. Also
works fine with Feisty.
--
After upgrading my server to Gutsy booting hangs at "Star
So and upgrade to Gutsy did not fix it and I still had to do break=mount
with lvm vgscan && lvm vgchange -a y to be able to boot. But them I
noticed that it was an lvm1 volume and converted it to lvm2 with lvm
convert.. that appeared to fix it for both Gutsy and Feisty (although I
can't guarantee t
Oops.
libdevmapper1.02 -> 2:1.02.08-1ubuntu10
--
[feisty] mounting LVM root broken
https://bugs.launchpad.net/bugs/83832
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is there any progress on this ? I have the exact same situation, where I
need to supply break=mount and lvm vgscan/lvm vgchange -a y to boot. I
saw this on an edgy->feisty upgraded machine, then did a clean install
of feisty elsewhere (both have boot as a 'normal' partition and lvm for
everything e
45 matches
Mail list logo
