This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
Hey Prateek,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Loris,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Ed,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run thi
Hey Cecco,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Peter,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Hans-Juergen,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best
Hey jedioetzi,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to
Hey David,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Eduardo,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Jaakan,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Brian,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
It is not an issue in Lucid. I don't know about Natty, but I presume
not. It can be closed.
If I have a close button, I don't see it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
Hey dualityim,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to
Hey Isak,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
[Expired for xserver-xorg-video-openchrome (Ubuntu) because there has
been no activity for 60 days.]
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserv
Hey jiplen,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Nick,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Andrew,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey nukul,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Юрий,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Ezequiel,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey Greg,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey nmsrnm1,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Luka,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Sebastien,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to
Hey Nick,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Grzegorz,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey toal193,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Bipul`,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Bendetto,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey SchneiderIS,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best t
Hey Arun,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Ahmed,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Dariusz,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Moritz,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Christopher,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best t
Hey Azelphur,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey Sandro,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Erno,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Stephen,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey PEIGNOT,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey LexRiver,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey Jason,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Freedric,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey nakki,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey holtzermann17,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best
Hey 16777216,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey Pedro,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey vik,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run th
Hey Panshul,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Mário,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Xetani,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey karlrt,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Břetislav,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to
Hey James,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Daniel,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Dmitry,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Qiyam,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under
Hey Giovanni,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey Mitchell,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Hey Jacek,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Hendrik,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey martonmiklos,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best
Hey Renan,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey hal,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run th
Hey Thomas,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Jari,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey archim,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Brendan,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey James,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Alex,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey James,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Hasen,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Alex,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Kcj1993,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Milton,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Murz,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run t
Hey Solaris,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to ru
Hey Simon,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
Hey Christopher,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best t
Hey C.,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run thi
1 - 100 of 1419 matches
Mail list logo
