Andreas,
Your statement is too general as the problem seems to depend on the
kernel. I will try to clarify based on my experience, which is not
exhaustive by any measure:
Qemu is fixed in Cosmic (18.10) 64-bit running kernel 4.18.0-11-generic
(but does NOT work in kernel 4.18.0-10-generic). I did
FIXED!!!
As soon as I finished the lengthy post above (#41) I upgraded Xubuntu
18.10 64-bit from kernel 4.18.0-10-generic to 4.18.0-11-generic and I
can now boot the Windows 10 guest. Everything works, although the
Windows 10 screen does not quite fit in the QEMU window (a bit too long)
and none o
I could not upgrade from Xubuntu 18.04 to Xubuntu 18.10, due to possible
demise of 32-bit support, so I have done a fresh install of Xubuntu
18.10 64-bit. Windows 10 guest will still not boot, but now I get the
BIOS flash and the Windows 10 Logo, on which it stays indefinitely with
100% cpu. Here i
qemu-system-x86 broken when running kernel 4.15.0-38-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
Fully updated Xubuntu 18.04.
--
You received this bug notification because you are a
qemu-system-x86 broken when running kernel 4.15.0-36-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
Fully updated Xubuntu 18.04.
--
You received this bug notification because you are a
qemu-system-x86 broken when running kernel 4.15.0-34-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
qemu-system-x86 broken when running kernel 4.15.0-33-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Since it appears that the problem is not my Xubuntu software setup (see
post #33), I thought that maybe it is my hardware setup, which is rather
old. So here is my hardware setup for you to consider:
Dell Inspiron 518 desktop (2008?)
Dell DG33M04/Foxconn G33M Motherboard
Intel G33 + ICH9 chipset
8
qemu-system-x86 broken when running kernel 4.15.0-32-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I booted from the Xubuntu 18.04.1 Install ISO, installed qemu, copied
and modified some files to adjust for user name and permissions, and ran
my Windows 10 qemu-system-x86 script - same result (black screen
displays and qemu-system-x86 runs at 100% cpu indefinitely). Totally
black screen immediate
qemu-system-x86 broken when running kernel 4.15.0-30-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Upgraded to xubuntu 18.04.1 (sudo do-release-upgrade) and kernel
4.15.0-29-generic. Same problem when running qemu-system-x86 (1:2.11
+dfsg-1ubuntu7.4) - black screen displays and qemu-system-x86 runs at
100% cpu indefinitely. Totally black screen immediately - no bios
flashes.
I thought this woul
qemu-system-x86 broken when running kernel 4.4.0-131 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
qemu-system-x86 broken when running kernel 4.4.0-130 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
qemu-system-x86 broken when running kernel 4.4.0-128 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
qemu-system-x86 broken when running kernel 4.4.0-127 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17678
"... try the even newer 4.4.0-224 kernel?"
Could not find 4.4.0-224 kernel.
Installed and booted 4.8.0-58-generic and qemu-system-i386 worked OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767857
Also fails (4.4.0-124 kernel) when trying to boot from
xubuntu-18.04-desktop-i386 ISO - same result (black screen displays and
qemu-system-x86 runs at 100% cpu indefinitely).
qemu-system-i386 -name xubuntu-18.04-desktop-i386 -pidfile
/tmp/xubuntu-18.04-desktop-i386.pid -m 2047M -cpu host -smp 1 -e
Also fails (4.4.0-124 kernel) when trying to boot from WinPE ISO - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
qemu-system-i386 -name windows-10-PE -pidfile /tmp/windows-10-PE.pid -m
2047M -cpu host -smp 1 -enable-kvm -rtc clock=host,base=localtime
-machi
sudo pidstat -t -p 4063
Linux 4.4.0-124-generic (desktop) 05/08/2018 _i686_ (2 CPU)
09:43:39 PM UID TGID TID%usr %system %guest%CPU CPU
Command
09:43:39 PM 1000 4063 -0.013.010.013.04 1
qemu-system-i38
09:43:39 PM 1000
qemu-system-x86 broken when running kernel 4.4.0-124 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17678
ChristianEhrhardt:
I assume you want stats from when qemu is failing while running kernel
4.4.0-122. Since I am running kernel 4.4.0-119 so that I can use the VM,
that would require a reboot which would be inconvenient at this time. If
you could give me some specific commands to use to get what yo
QEMU command:
qemu-system-i386 -name windows-10-pro -pidfile /tmp/windows-10-pro.pid -m 2047M
-cpu host -smp 1 -enable-kvm -rtc clock=host,base=localtime -machine
type=ubuntu -k en-us -drive
file=/media/V-BOX/KVM/Win10/Win10-VM.qcow2,if=virtio,media=disk,format=qcow2,index=0
-drive
file=/media
qemu-system-x86 broken when running kernel 4.4.0-121 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17678
Public bug reported:
Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
system-x86 works fine running a Windows 10 VM.
ProblemType: Bug
DistroRe
I tried Budgie and standard Gnome Shell sessions. They don't have this
problem. Only the Ubuntu session (both xorg and wayland).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (
I also have it with Intel integrated graphics on both of my desktops,
connecting through DisplayPort. I hope this will help to find the
problem. But if its the display cable type, how come that there are only
few occurrences of the bug?
--
You received this bug notification because you are a memb
So what are the steps for fixing the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712698
Title:
Uninstalling Dash To Dock does not restore Ubuntu Dock
To manage notifications about this
Sorry, this may be not exactly the problem I have. My problem is that I
get a new window regardless there is one already running or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926509
Title:
N
Now I have this in 16.10.
It is quite disruptive for my workflow as I end up with many unwanted terminal
windows, except getting to the one I want to use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This problem recently appeared in trusty. For working with tex/latex
this is really disruptive.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/145637
Title:
Monitor document ch
Now the crash happens in trusty as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this b
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892697
Title:
[Macmini5,3, Cirrus Logic CS4206, Headphone Out, No sound at
I think this was a problem in the development version and was gone in
the release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892696
Title:
Xorg crash
To manage notifications about this bug go t
*** This bug is a duplicate of bug 1236951 ***
https://bugs.launchpad.net/bugs/1236951
Public bug reported:
The upgrade from raring to saucy stopped with this error message.
After manually updating the packages I still receive this error message.
ProblemType: Package
DistroRelease: Ubuntu 1
Public bug reported:
got this message while upgrading to saucy
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: emacs24 24.3+1-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date:
Yes, this is happening in raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go t
Same on 12.10. Bit of searching reveals that this is a theme issue.
Workaround: switching to the adwaita theme, you get black font.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021344
Title:
Annot
Thanks for the instructions! I managed to get unity working. I had to
purge/reinstall many packages, but I guess that was due to the fact that
at some point I tried this ppa:
https://launchpad.net/~makson96/+archive/fglrx (which did not work 3
days ago).
--
You received this bug notification beca
It seems that the change did not go into Quantal. Any special reason for that?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892697
Title:
[Macmini5,3, Cirrus Logic CS4206, Headphone Out, N
Hey Dave,
Thanks for the answer! Now I can better phrase what the problem is.
I don't care too much about 3D (no gaming for instance) but I use unity.
If this was known before and going back to the open-source driver is an
option then why is it not done during the upgrade?
What happened here is
Public bug reported:
Upgrading from Precise breaks the whole system as Unity does not start.
I managed to install icewm, that's how I can use the computer now.
I tried the PPA https://launchpad.net/~makson96/+archive/fglrx but it
did not work.
I tried to install the previous Catalyst driver man
crash while trying to install rar for file-roller
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028640
Title:
session-installer crashed with TypeError in _on_property_changed():
could not convert
It took a while to figure out the exact steps, but here they are:
1. Open a terminal.
2. Invoke HUD by hitting Alt
3. Type pr
4. Choose Profile preferences
5. Hit enter
The window appears but also apports start collecting information on
crash.
--
You received this bug notification because you a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954977
Title:
setting profile preferences and trying HUD I got crash message
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Public bug reported:
It is a bit mysterious as the terminal itself did not crash.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-terminal 3.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: wl nvidia
ApportV
*** This bug is a duplicate of bug 946474 ***
https://bugs.launchpad.net/bugs/946474
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952610
Title:
unity-scope-vi
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945942
Title:
nautilus crashed with SIGSEGV in g_main_context_dispatch()
To manage notifications about this bug go to:
So this python script makes it work, but has to be executed after each
boot/suspend. One can just put this into an init script, but that does
not seem to be a nice solution.
** Attachment added: "hda.py"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/892697/+attachment/2737439/+fil
Same in Precise, I connected an external harddrive, nautilus could only
show a blank windowframe, then crashed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/804891
Title:
nautilus crashed with SIGS
Yes, it works here as well. Strange enough, but I had to unmute the
Surround speaker and muting the front speaker has no effect at all
(maybe I did something differently).
I wonder whether the HDMI audio output is just the same kind of
rerouting, or more involved.
Anyhow, this workaround is fine
I tried connecting to a monitor with speakers by an HDMI cable. That
also does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892697
Title:
[Macmini5,3, Cirrus Logic CS4206, Headphone Out,
Public bug reported:
After a fresh install there was no sound at all. I added the line
options snd-hda-intel model=mbp55
to alsa-base.conf, now there is sound but only through the internal speaker,
while in Sound Settings only 'Analog Headphones' appears. The same with
model=imac27. With model=
Now I think eog is crashing, since I can reproduce the bug from command
line without nautilus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892696
Title:
Xorg crash
To manage notifications about t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892697
Title:
[Macmini5,3, Cirrus Logic CS4206, Headphone Out, No sound at all
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Attachment added: "xsession-errors"
https://bugs.launchpad.net/bugs/892696/+attachment/2602493/+files/xsession-errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892696
Title:
Xorg crash
T
Public bug reported:
In nautilus I try open an image file, the eog window appears, then crash
and I get back to login screen. The crash can be reproduced.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux
Still an issue in Oneiric.
I also followed teagu-wisc, but I copied the content to a USB stick and
mounted that one. Just in case you don't fit inti the memory.
Installing Ubuntu on MacAir2,1 without the Apple SuperDrive is a
nightmare.
--
You received this bug notification because you are a m
Fresh update, clean reboot, starting Firefox, clicking on a link and I
got this crash message. For the next click I could load the page though.
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/862161
I got the apport message about the crash when my laptop was waking up
from suspend mode. And strangely, the running emacs session did not seem
to be affected at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847236
Title:
[i945gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Public bug reported:
The system survives this, but there is this message about crashing.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
.tmp.unity.suppor
I would also like to see this fixed downstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720089
Title:
gretl crashes right after start
To manage notifications about this bug go to:
https://bug
ubuntu 11.04/64 - Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18)
Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11 ms exchange 0.16
and
ubuntu 10.10/64 - Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18)
Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11 ms exchange 0.16..
both syste
Any workaround for this in Lucid?
--
can't use the search in okular when using mozplugger
https://bugs.launchpad.net/bugs/343182
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
ht
Sorry for the false alarm, it was a buried setting in the http filtering that
was blocking the file. Was not in firewall settings, but web filtering. Yes,
I should have checked that one also before reporting. Sorry again.
DJS
--
Says it cannot find file andale32.exe
https://bugs.launchpad.ne
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/15627393/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/15627394/DpkgTerminalLog.gz
--
Says it cannot find file andale32.exe
https://bugs.launchpad.net/bugs/243283
You received
Public bug reported:
Binary package hint: msttcorefonts
Perform update and tried to install msttcorefonts. Fails with a message
that it cannot find andale32.exe.
ProblemType: Package
Architecture: i386
Date: Thu Jun 26 11:32:34 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: subprocess post-insta
I removed VLC and was then able to upgrade to Gutsy from the alternate
CD. Installed VLC afterward and everything is working fine.
On 2/1/08, Pedro Villavicencio <[EMAIL PROTECTED]> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug
This bug is still present in Gutsy Tribe 2. I am using the 64-bit
version.
uname -a
Linux ubuntu 2.6.22-7-generic #1 SMP Mon Jun 25 17:07:55 GMT 2007 x86_64
GNU/Linux
--
USB ports: connect-debounce failed, port disabled
https://bugs.launchpad.net/bugs/88530
You received this bug notification be
70 matches
Mail list logo
