** Attachment added: "journalctl -b0 from successful screen activation"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.
** Attachment added: "dmesg from functional boot"
https://bugs.launchpad.net/ubuntu/+sou
This is still 100% reproducible. I have attached the dmesg below.
** Attachment added: "dmesg from 2019/06/06"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5269157/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs
I did plug/unplug the monitor because if I do that enough times is
generally resolves the problem until the next time I reboot. It has not
done so this time. I also tried a new cable, but that does not fix the
problem either.
--
You received this bug notification because you are a member of Ubunt
It seems unlikely to be a cable or signal problem since I can eventually
coax it into working, and it continues working until I reboot. If it
were a cable problem or something about the signal I would have to
physically modify the connection to create and/or correct the problem.
Since the mere act
** Attachment added: "output of journalctl -b0 > journal.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267691/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Attachment added: "output of xrandr > xrandr.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267692/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I tried that and it didn't fix the problem. I am attaching the output of
some of those files again for further data.
** Attachment added: "dmesg output ( on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267690/+files/dmesg.txt
--
You received this
** Attachment added: "output of lspci -k"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267341/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830
** Attachment added: "output of xrandr > xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267344/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Attachment added: "output of journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267343/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: "Image of the screen corruption"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267340/+files/IMG_20190528_160705.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267342/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830792
Ti
Public bug reported:
On my system I have two display: one in landscape, and one in portrait.
The landscape display is fine, but the portrait display is corrupted. If
I unplug the display from the computer for some time and then plug it
back in it will occasionally fix the problem.
Once the proble
To reproduce it, try switching the order of your displays. For example,
make the display on port 0 be on the right of the display on port 1
(instead of the "natural" order of 0=left, 1=right.) I also notice that
changing the orientation of the primary display to "portrait right"
causes problems, wh
Yes, they are very similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825004
Title:
Ubuntu loses display settings on reboot, corrupts displays
To manage notifications about this bug go to:
htt
Public bug reported:
I have two displays, one on display port, and one on VGA. The display
port display is a Seiki Pro 40" display in landscape at 3840x2160. The
VGA is an HP 24" display in portrait at 1920x1200.
If I boot with either display by itself, everything works fine. If I
plug in the oth
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
I can confirm that it's not fixed. Rebooting has become a major problem
for me because it loses my display settings, corrupts the displays, and
I spend 20 minutes fixing everything.
--
You received this bu
I can also confirm this problem. It happens to me in Unity on a
repeatable basis: whenever I click the mouse on the desktop to draw a
selection, everything freezes momentarily. It doesn't happen when
resizing or moving windows, just when I click on the desktop. However,
it does happen if I try to m
Happens to me everytime I start eclipse now. Eclipse ran fine for quite
some time. Then in the middle of a session it aborted, and now I get
this:
cnelson@tdvm:~$ /store/local/eclipse/eclipse -clean
Xlib: extension "RANDR" missing on display ":0".
#
# A fatal error has been detected by the Java R
I don't know. I abandoned this technology since it clearly was not
ready for production use. I have not had the time to try it out again
and see if it has been fixed in the latest release.
On Sat, Nov 29, 2008 at 11:52 AM, JaysonRowe <[EMAIL PROTECTED]> wrote:
> Since it's been a very long time
I experience this (or possibly a separate issue with similar
appearances), KDE4.1 systray corruption under Intrepid. It only appears
when I'm using the intel video driver; if I force it to vesa everything
works properly. Possibly a problem with compositing, or the intel xorg
driver?
--
[Intrepi
WIndows 2003 x64 Standard
On Sun, May 11, 2008 at 12:42 PM, Nick Barcet <[EMAIL PROTECTED]>
wrote:
> Can you please specify which OS you are installing?
> Destroy acts for me as a "pull the plug" equivalent. It is not recommended
> to do so, but rarely causes fatal damage to the vm.
>
> --
> virt
Destroy turns the machine off but:
(1) It is not clear that that is a good thing to do from the warnings and the
fact that the functionality is "hidden" beneath a contect menu instead in the
console.
(2) After choosing destroy I can no longer restart the VM. I get errors saying
the the VNC fai
I select an ISO and I have permission to the file.
--
creating a new virtual machine with ide disk and cd-rom does not work
https://bugs.launchpad.net/bugs/228686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/14395575/Dependencies.txt
--
virt-manager can't stop VM
https://bugs.launchpad.net/bugs/228690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Public bug reported:
Binary package hint: virt-manager
After creating a new virtual machine, there was no cd-rom attached (I
filed another bug since I specified an .ISO during VM creation). Since
the HDD was empty, the system was unable to boot. Well enough so far.
Realizing that it didn't se
I currently experience this same problem. I am running the full release
of Ubuntu 8.04, x864-64 with all the latest updates installed as of
today.
--
Unable to run Virtual Machine
https://bugs.launchpad.net/bugs/217311
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/14395351/Dependencies.txt
--
creating a new virtual machine with ide disk and cd-rom does not work
https://bugs.launchpad.net/bugs/228686
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: virt-manager
When creating a new virtual machine, I am asked all the right questions.
However, when the machine goes to start, the CD-ROM is not present in
the hardware list.
When I add a new CD-ROM drive, the IDE hda disk goes away, but the cd-
rom hdc
30 matches
Mail list logo
