Found the problem - for some reason the systemctl service getty@tty[1-4] has a
prerequisite of /dev/tty0 existing. If it is not, all the tty[1-4] do not
start. (tty1 fails, the others are not tried)
SEE below - "ConditionPathExists=/dev/tty0 was not met"
systemctl status getty@tty1
○
Just a thought, should we change the name of this report from cgroups to
something "lxc-console only works for console tty0, not tty[1-4]" in
impish?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
to re-create the issue,
1 clean install of impish
# probably need sudo or be root for the following
2 boot into impish and install all updates
3 apt get install "lxc lxcfs lxc-utils lxc-templates lxctl"
4 lxc-create -n test -t ubuntu
5 lxc-start test
6 lxc-console -n test
# the above command FAILS
other information:-
container installed is from ubuntu template
can start/stop container
lxc-attach works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947811
Title:
cgroups broken in impish
To
Public bug reported:
fresh install, all updates installed.
install lxc + lxcfs
symptom - can't sudo lxc-console -n lxcmachine (lxc-console works, but no
reponse/tty)
symptom - sudo ls -laF /var/lib/lxcfs
produces:-
---
ls: cannot access
Original crashing of mythtv now fixed on ubuntu 20.04 libmysqlclient21
version 8.0.21-0ubuntu0.20.04.3 with mariadb server.
--
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/1877504
Title:
Never mind, my problem is solved, although there seems to be some
tidying up to be done.
Thanks again,
Kim
On 15/5/20 9:47 pm, Maciej Borzecki wrote:
> Double checked with snap-store from beta channel. The button is there,
> but it seems off.
>
> When I connected the interface, the UI button
Of course there is a button after you do the manual connection, but I
take your point.
Thanks again.
On 15/5/20 8:45 pm, Maciej Borzecki wrote:
> FWIW there should be a button which you can click in the snap-store.
> Sadly there does not seem to be one for the `dvb` interface.
>
> ** Also
Hi,
Yes, it works. Thanks.
I obviously need to do a course on the ins and outs of snap. There
appears to be a lot of stuff to be configured than I'm used to.
Cheers for that,
Kim
On 15/5/20 3:18 am, Maciej Borzecki wrote:
> ```
> [7f9a84000bb0] dtv stream error: cannot access DVR:
I can confirm that the test program above causes segfault with current
libmysqlclient21 but not with previous version, using mariadb as the
server.(sorry, it took me a while to get all the dependencies together
to compile and execute the program.)
--
You received this bug notification because
After the release of Focal, I did a fresh install with mariadb server.
I did a mysqldump backup of the existing mythtv (bionic) mariadb
database and installed mythtv (mythbackend + mythfrontend + plugins) and
configured it to work with the current setup.
This all worked almost perfectly, just
Public bug reported:
A snap installation of vlc will not allow vlc to play TV. A repo installation
of vlc works as expected.
When run from command line, get the following messages:-
--snap version--
user@host:~$ /snap/bin/vlc Desktop/vlc_playlist.xspf
VLC media
Public bug reported:
disk partitioning is non-standard (sda8 is flagged as bios_grub) with
uefi bios.
I probably need to save all partitions and re-partition and reformat
disk, then allow clean install of uefi boot
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63
Public bug reported:
Log files continually fill up with following error messages every couple of
seconds, then the wifi fails until reboot :-
Feb 16 08:33:25 pio kernel: [ 261.084034] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Feb 16 08:33:29 pio kernel: [
Sorry, I still don't understand. All versions of the kernel are broken.
What would I bisect against? In any case, the result would still be a
broken kernel, and would be of no help to isolate the problem. To me,
it would appear to be a waste of time to do this.
--
You received this bug
Christoper, I don't quite understand. All versions of trusty show a
fault, as well as the newest version of upstream kernel. The early
versions of trusty show the fault at boot, while the later versions show
the fault some time after boot. What would the basis of the bisection
be? If it was
yes - it still happens (happened) with trusty. I use a backup program
called backintime which uses rsync, and I backup the laptop to an nfs4
mount. During the backup, the nfs4 server crashes just as specified
above in trusty (kernel 3.13.0-32-generic). The backup program then
stops, leaving the
This was NOT happening in precise, and WAS happening with early versions
of trusty. I had a test partition with trusty to check it, prior to
fresh install of trusty. It was clear that this was happening with
trusty from boot. I filed a bug report for trusty, along with upstream
kernels that
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242936/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
nfs4
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242935/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
apport information
** Tags added: apport-collected trusty
** Description changed:
Aug 7 01:05:46 mike kernel: [60329.252525] PGD 5b4ac067 PUD 5b4ad067 PMD 0
Aug 7 01:05:46 mike kernel: [60329.252532] Oops: [#1] SMP
Aug 7 01:05:46 mike kernel: [60329.252538] Modules linked in:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242943/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242942/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242939/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
nfs4
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242945/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242941/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242938/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242940/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
nfs4
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242946/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242944/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242947/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1353730/+attachment/4242937/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Clarifying :-
+This particular problem never happened in precise.
+All trusty kernels have had this problem to some extent, the initial
release of trusty had this problem from boot, then sometime later
(sometime just before the time that bug 1318837 was closed - 28/8/14) it
changed to be
Error messages still appearing with upstream kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383555
Title:
ieee80211
Oct 22 09:57:54 pio kernel: [ 26.272675] ieee80211 phy0: rt2x00_set_chip:
Info - Chipset detected - rt: 2560, rf: 0003, rev: 0004
Oct 23 07:55:11 pio kernel: [ 25.644870] ieee80211 phy0: rt2x00_set_chip:
Info - Chipset detected - rt: 2560, rf: 0003, rev: 0004
Oct 23 08:40:30 pio kernel: [
I have installed upstream kernel :- uname -a gives -
$ uname -a
Linux pio 3.18.0-031800rc1-generic #201410192135 SMP Mon Oct 20 01:37:04 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
Since it is currently an intermittent fault, I will run it for a couple
of days.
When I reported this fault
I originally marked this as a bug in precise, but said that since it
seemed to fixed in later version of trusty, I wasn't going to follow up,
and it was closed. It is now an issue again, annoying because of the
logs filling up, critical because of the lockup of the entire PC.
--
You received
Public bug reported:
Doesn't happen immediately after kernel reboot. Will eventually cause
wireless connection to fail, and cause computer to lock up. Need to use
ALT-SYSREQREISUB to reboot, as all other method frozen. Fills up logs
with above messages many times per minute. Originally
After latest updates, problem has gone away. I will continue to use it
for a while to ensure that wireless doesn't freeze as it had beofre.
If, I will open new problem.
For me, please assume that this problem is fixed.
uname gives :- Linux host 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13
further investigation :-
I have 4 partitions on 2 disks mounted in fstab, then these 4 partitions
(ext4) are mounted with bind to /exports for eventual nfs4 export.
After reboot, some of these partitions are mounted, (according to mount)
but are empty. If these /exports bind directories are
Public bug reported:
Aug 7 01:05:46 mike kernel: [60329.252525] PGD 5b4ac067 PUD 5b4ad067 PMD 0
Aug 7 01:05:46 mike kernel: [60329.252532] Oops: [#1] SMP
Aug 7 01:05:46 mike kernel: [60329.252538] Modules linked in: rfcomm bnep
bluetooth nfsd auth_rpcgss nfs_acl nfs lockd sunrpc
I don't know how to download the particular versions 3.14.0-RC2 and
3.14.0-RC3, as RC2 is bad and RC3 is good (relatively).
eg, what version number do I put in for the following example, given the
about versions? :-
git bisect good v3.13-rc4
How do I list the available kernels in git?
I
I've tried many of the intructions, but am unable to download the
appropriate git kernel sources, and do not know enough about how to
manipulate the repositories to be able to be any help.
In the meantime, the current updated kernel 3.13.0-29 still has the same error,
but now ubuntu trusty
have tried many kernels from mainline kernels
kernels from current, up to and including 3.14.0-rc2 exhibit error as
described above.
kernels 3.14.0-rc3 and above DO NOT exhibit error as descibed above.
I have looked at changes log for for 3.14.0-rc3 for obvious changes that
may be implicated,
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to
kernel-fixed-upstream
The kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.15-rc5-utopic/ fixes the problem. (no filling of logs
with message ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0
failed to flush.)
It has other problems, but since it is an RC, will wait for
Public bug reported:
Happens continuously after boot/reboot, finally fails, followed by
authentication failure. Happens 100% of the time.
Doesn't happen with 12.04 Precise. (clean install of trusty to separate
partition)
cat /proc/version_signature
Ubuntu 3.13.0-24.47-generic 3.13.9
sudo
apport information
** Tags added: apport-collected trusty
** Description changed:
Happens continuously after boot/reboot, finally fails, followed by
authentication failure. Happens 100% of the time.
Doesn't happen with 12.04 Precise. (clean install of trusty to separate
partition)
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110993/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110994/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110997/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110998/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110996/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110999/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4110995/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111004/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111001/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111002/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
added apport, changed status to confirmed as requested via email
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111006/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111005/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111003/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111007/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1318837/+attachment/4111000/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Same chhipset, same problem, HP DM2, Ubuntu precise, wl module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/414724
Title:
wl driver (Broadcom) does not receive ARP packets (broadcasts)
To manage
happened just after logging into unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175836
Title:
compiz.real crashed with SIGSEGV in g_slice_alloc()
To manage notifications about this bug go to:
Hi, the one specified in the text above, viz. ppa:roignac/cheese-daily
(Vadim Rutkovsky (roignac) https://launchpad.net/%7Eroignac wrote on
2012-06-18: )
On 30/06/12 13:52, deschmit wrote:
what ppa do you use?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
. Have done it all but Cheese still will
not open all I get is an error report box.
Best Regards
Tony
On 19/06/12 14:28, Kim Tyler wrote:
After downloading the packages from the ppa (I didn't want to include
the ppa in my repositories) I did a dpkg -icheese package names
In detail, after
(It would be better to mail me directly kit...@gmail.com with your
direct email address)
Cheers,
Kim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917757
Title:
cheese crashed with SIGSEGV in
and good luck,
Kim
On 19/06/12 19:02, Tony Ware wrote:
How do I do this? I know the removal bit but not ppa dpkg -i
On 19/06/12 00:32, Kim Tyler wrote:
Confirm not crashing. (deleted distro cheese using apt-get remove,
installed new cheese from ppa using dpkg -i).
Working again! (yay
Confirm not crashing. (deleted distro cheese using apt-get remove,
installed new cheese from ppa using dpkg -i).
Working again! (yay!).
NOTE:- many, many resolution options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not occuring anymore. I was trying to configure mythtv backend,
and it kept on crashing. By hand configuration of text files, it was
enogh to get most of it going and bypass the above problem.
This problem is not occurring anymore - fixed? Please close if
appropriate
--
You received
After last set of updates today, the problem has gone away. I have
restarted several times and unity-greeter does not crash. I did notice
however, that the background image of the selected user comes up in
unity-greeter if it is a static image. If it is a changing image, you
get the default
If you change the unity-greeter to another user without it crashing
(continually hitting up and down arrows while unity-greeter is
crashing), you can change back to your normal user and log in as normal.
Loging out will cause the problems to recommence.
--
You received this bug notification
I can confirm that using the up-down arrow keys at the login prompt
(while unity-greeter is continually crashing and restarting) to try to
cycle between usual user, another user and the guest session will
eventually cause the unity-greeter to stop crashing, and allow the user
to log in as usual
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969589
Title:
unity-greeter continually crashing and restarting
To manage notifications about this bug go to:
Public bug reported:
Mar 31 07:45:58 eeepc kernel: [44854.125767] unity-greeter[20806]: segfault at
0 ip 080509ce sp bf877090 error 4 in unity-greeter[8048000+2b000]
Mar 31 07:45:58 eeepc kernel: [44854.694043] composite sync not supported
Mar 31 07:45:59 eeepc kernel: [44855.162691] composite
have to remotely ssh in to kill lightdm - very difficult on console
because screen continually changes console
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969589
Title:
unity-greeter continually
Exactly - I installed ssh server and remotely logged in to kill lightdm
- much easier. With ssh -X, you can remotely use windows.
Cheers,
On 31/03/12 09:26, Paul White wrote:
I'm going to mark this as also affects me as I've also experienced
this bug twice this week.
The screen refresh
No - looking good.
Cheers,
Kim
On 26/10/11 09:30, Bryce Harrington wrote:
Hi, just checking back in for status. Have you seen more of these
lockups since the release or within the last few weeks?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Incomplete
--
No. Just the dialogue box pop-up.
On 13/10/11 04:07, Bryce Harrington wrote:
Hi Kim, did your computer actually freeze / lock up after this? From
the logs it appears the gpu hung but immediately reset itself.
Did you experience any symptoms other than the crash dialog popping up?
**
*** This bug is a duplicate of bug 862523 ***
https://bugs.launchpad.net/bugs/862523
Public bug reported:
after update (new kernel), reboot and login to unity
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 862523 ***
https://bugs.launchpad.net/bugs/862523
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869695
Title:
[i915gm] False GPU lockup EIR: 0x0010
*** This bug is a duplicate of bug 862523 ***
https://bugs.launchpad.net/bugs/862523
Public bug reported:
just after update-reboot-login
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic
*** This bug is a duplicate of bug 862523 ***
https://bugs.launchpad.net/bugs/862523
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868822
Title:
[i915gm] False GPU lockup EIR: 0x0010
I am using unity 2d now, and the background is OK.(fault in normal
ubuntu unity) I have intel graphics adapter (eeepc 1000HD)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832603
Title:
updated packages, restarted system. Logged in with ubuntu unity
desktop. system locked up solid - had to hold down power button to
close it down.
Restarted, logged in again, system working fine. No crashes, desktop
background in correct place and right mouse click working OK.
Appears to be
It happened after coming back after screensaver activated (blank with
no lock)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/862938
Title:
compiz assert failure: *** glibc detected *** compiz:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863760
Title:
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x7f86
To manage notifications about this bug go to:
Public bug reported:
crash occurred after opening update manager to update packages. Screen
had been previously in blank screen saver.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Hi - tried bzr command to branch and cd - OK
kit284@eeepc:~/test-gsd-fix$ bzr bd -- -b
bzr: ERROR: unknown command bd
Any thoughts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832603
Title:
kit284@eeepc:~/test-gsd-fix$ bzr bd -- -b
Building using working tree
Building package in merge mode
Purging the build dir: /home/kit284/build-area/gnome-settings-daemon-3.2.0
Looking for a way to retrieve the upstream tarball
Upstream tarball already exists in build directory, using that
Building
confirm no crashes - now have another problem:-
Background graphic now displaced down and right. Right click on actual
background works OK. Right click on non-background (initially black,
holds last image of window over that part of background) does nothing -
no menu.
Fonts still corrupted in
Public bug reported:
I had just reported that no crashes, and reporting other problems, and
changed the screen resolution from 1024x600 to 800x600 to see if it
changed background problem (see above) and this problem happened.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/862988
Title:
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 856423 ***
https://bugs.launchpad.net/bugs/856423
Public bug reported:
happens many times per day, even when idle (or return from screen saver-
blank)
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
*** This bug is a duplicate of bug 856423 ***
https://bugs.launchpad.net/bugs/856423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860209
Title:
[i915gm] False GPU lockup EIR: 0x0010
*** This bug is a duplicate of bug 856423 ***
https://bugs.launchpad.net/bugs/856423
fonts are also getting corrupted, fonts for mozilla and terminal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
doesn't seem to be any real problem, but bug report comes up
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850828
Title:
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x7d8e0001
To manage notifications about this bug go to:
1 - 100 of 186 matches
Mail list logo
