A couple weeks ago I did a fresh install of ubuntu-14.04.desktop.iso LTS
and the garbled text bug 1507255 was back. Usual fix of
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
worked.
Xenial new installs have been fine lately. Putting
Just got the bug 2016-3-29 fresh install today from xenial-desktop-amd64.iso
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"
Linux Lenovo2 4.4.0-16-generic #32-Ubuntu SMP Thu Mar 24 22:38:01 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
model
Starting in November 2014 Ubuntu X windows screwed up with
VGA compatible controller: Intel Corporation 4 Series Chipset Integrated
Graphics Controller (rev 03)
making Wallpaper badly hashed.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1507255
Then a couple months
Not fixed in 14.04.4 LTS. 14.04 originally did not have this garbled
problem, but a fresh install of 14.04 does.
Should I enter a new bug against 14.04 LTS since this Xenial bug is
fixed? 14.04 is supposed to be supported until 2019 I think.
--
You received this bug notification because you
I tested
http://cdimage.ubuntu.com/daily-live/current/
Wallpaper badly garbled.
Images from ubuntu O.K., but any text sent by ubuntu badly garbled
unreadable.
Fix in comment #41 works fine.
Do note, 14.04 LTS had been running fine until 1/29 update screwed up network,
so I
re-installed
That site looks like a fresh install to today's xenial 64. I've been
running an update xenial now at 4.5 RC1; I'll do a fresh install and see
what happens.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
My comments on entry #13:
gedit 20-intel.conf
Copy in the lines starting with Section and ending with EndSection:
[code]
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
[/code]
save
quit
sudo cp 20-intel.conf
Finally a workaround was posted on Launchpad - I've been battling this
bug for 11 months:
#sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf
#Add the following lines
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
#reboot
--
You
*** This bug is a duplicate of bug 1404247 ***
https://bugs.launchpad.net/bugs/1404247
Finally a workaround was posted:
#sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf
#Add the following lines
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
This bug persisted for two weeks.
Installed and updated Xenial problem no longer occurs.
Much safer for me to update Ubuntu rather than risk a bios update - a failed
bios update turns the pc into junk.
Thanks for looking at the bug.
--
You received this bug notification because you are a
Comment #8 works in Xenial Xerus as well.
Yay, I can read the screen, wallpaper is right, wonder how long the fix
will work.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
How do I tell if this Lenovo M58p has the Intel GMA4500 chip?
Wily gives me fits with hashing. Can't read text even.
Xenial slightly better. Text sent out by Ubuntu is totally hashed. Text I
type in on the terminal window is readable. Wallpaper and images are hashed
unintelligible.
Current
Public bug reported:
Message on booting up. See attached.
Came up in 1920x1080 expected 1366x768
Screen flashed a couple times, once in 1366x768, then back to max resolution
hard to read on this monitor.
Systems settings to get desired resolution.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Latest Wily:
DISTRIB_DESCRIPTION="Ubuntu 15.10"
Linux Lenovo2 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
00:02.0 VGA
Shotwell display badly hashed.
Image Viewer display just fine.
Both on the screen at the same time in the attached screenshot.
How do I get the display routine used by Image Viewer to be used by
Shotwell and Lightdm?
Note, part of screen behind the images shows badly hashed unreadable
desktop.
Comment #36, this is a desk top so the display is hooked to the VGA
port. I think there's only one display port on this Lenovo M58p.
Interesting, boot with Wily kernel,
Background Wallpaper hashed
Settings Appearance Wallpapers thumbnails hashed
Files Pictures displays same jpg fine
command
Wily getting worse and worse.
Much screen text hashed unreadable. A couple weeks ago it was just
Wallpaper.
Do note, Files Pictures select jpg displays jpg just fine. Settings
Appearance all hashed.
See attached screenshot.
Do note with hashed unreadable text as in gedit, selecting
Kernel:
linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_amd64.deb
works fine installed into Wily.
I think it's one of the last Utopic kernels
So my drill is, update or install latest Wily, verify screen display is
all screwed up,
Then install a kernel that will work.
I'm not a
Thanks for looking at the bug.
I switch between Mily looking for bugs, and LTS when I can't get
something done with Mily because I can't read the screen.
I might try another kernel from kernel-ppa/mainline.
I don't know how to downlevel X to say, whatever it was in November 2014
when everything
Update complete Wily as of display.
Appearances Background all pictures horizontally hashed, both the ubuntu
supplied ones and my jpg's.
Wallpaper horribly hashed and will not recover even with multiple
wallpaper settings. which used to clear things up until the changes of
last week.
Files
Opened a bug for gsettings failure described in comment #26:
gsettings fails to set wallpaper 1490543
Gsettings fails on both the Lenovo M58p with the hashing problem
Gsettings also fails on Acer 5253 laptop which does not have the hashing problem
In both pc's Settings Appearance Wallpapers
Wily as of
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)"
Linux Lenovo2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
model
Public bug reported:
DISTRIB_DESCRIPTION=Ubuntu Wily Werewolf (development branch)
Linux Lenovo2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
model name : Intel(R) Core(TM)2 Duo
Wily O.K. for a couple weeks and I had my hpes up. Then got dread update:
xserver intel update
Now wallpeper usually boots horizontally striped hashed, sometimes boots
wallpaper O.K.
I don't know how to down level xserver intel?
Wallpaper can be fixed by alternately doing the following once
gsettings set org.gnome.desktop.background picture-uri
'file:home/jerry/Pictures/Shark_Island.jpg'
re-does the wallpaper and can clean up the hashing.
What all does gsettings use? Likely xserver
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Bios update is in 1404247 - if it screws up I've got a dead computer.
1410 and before run just fine.
November and before 1504 ran fine. Win7 just fine. (Well, pretty slow
it's Microsoft)
1504 December and on to now pretty bad. I have to set wallpaper
multiple times.
At the moment, Wily much
As of 17 May Wily update,
xserver was updated
Now, hashing much harder to get rid of by multiple set wallpaper.
How do I tell if the bug fix is in Wily? If so, it doesn't work. If
not, when can I try the fix?
Thanks.
--
You received this bug notification because you are a member of
Wily Werewolf here, updated as of 14 may, boots normally, no Hashing.
Reboot to 15.04, screen Hashed as usual.
Reboot to Wily Werewolf, boots normally again, no Hashing.
Wonder what next updates will do
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I looked at the Lenovo support site.
The BIOS upgrade is for Win7 64 so I'll have to boot that ( if Ubuntu Grub
hasn't screwed up the Win 7 bootloader ) and see if the download and exe will
work.
Of course if a BIOS update fails I've got a dead computer.
--
You received this bug notification
Comment #11 found earlier vivid wallpaper works fine. (as does 14.10, 14.04,
...)
Nov. 10 vivid .iso fresh install on another partition.
Boots with wallpaper O.K. every time.
Vivid as of mid December updated/installed wallpaper screwed up on every boot.
This is a vivid apt-get update, apt-get
Tried kernel 4-RC2
DISTRIB_DESCRIPTION=Ubuntu Vivid Vervet (development branch)
Linux Lenovo2 4.0.0-04rc2-generic #201503031836 SMP Tue Mar 3 18:37:51 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
model name : Intel(R)
Comment #7, where is the update history found?
Likely hundreds of updates in December.
This install is a couple days old, still has the problem.
What packages are involved in Set Wallpaper?
Any way to put Set Wallpaper back to early December? All my vivid iso's are
now in February.
--
You
Testing vervid I do updates most days and installs every couple weeks.
Typically there are a whole pile of packages (!) so us users don't install
package by package so we can't tell which caused the trouble.
I reported the bug on Dec. 19 and the bug persists on every update and every
couple
Downloaded today's vivid 32 bit, booted live environment, systems settings
appearance, set wallpaper
selected ubuntu skyscraper image
all hashed up.
See attachment.
Doesn't seem to make any difference, 32 bit or 64 bit both broken.
** Attachment added: wallpaper hashed vivd 32l bit .iso
Still present on every boot. See attachment.
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION=Ubuntu Vivid Vervet (development branch)
Linux Lenovo2 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 04:35:32 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
model name : Intel(R) Core(TM)2
Jan 4 vivid 64 .iso still same problem, wallpaper vertical bars and
hashed.
Rebooted latest update vivid.
Monitor is 1920x1080., vertical bar background. Internet windows and
terminal windows fine.
Tried 1360x768. Wallpaper Vertical bars.
Tried 1280x720. Vertical bars.
Tried 1024x768.
Public bug reported:
After update this week wallpaper hashed. See attachment.
Settings Appearance change wallpaper to a different wallpaper O.K., then
back to original restores proper image.
Reboot, wallpaper hashed again.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg
Maybe the problem description is invalid, however the problem is
very real.
See also ttps://bugs.launchpad.net/ubuntu/+source/unity/+bug/1359299,
confirmed, multiple users report problem.
Utopic amd64 does not work on Lenovo ThinkCentre. Intel Core 2 duo 3.0
gHz 4 mb.
Intel Corporation 4 Series
I get a similar compiz error on amd64. In my case, booting 3.16.0.6
kernels or before work fine.
Booting amd64 3.16.0-7, -8, -9, -10 kernels on the same install the
desktop runs but compiz hence unity do not.
Booting the newer .iso the live session fails the same way. Follow
through with the
3.16.0-9 i386 32 bit boots normally. Very rarely boots to desktop and
cursor no unity.
3.16.0-9 amd64 always boots to desktop no unity. X is up, compiz hence
unity are not.
3.16..0-8 rarely boots to unity, usually to desktop and cursor only.
Viewing utopic as a black box, characteristics are
This utopic install was initially linux image 3.16.0-5.
Updated to -7 compiz and unity fail, X11 running fine to desktop no
panels.
Updated to -8 first boot from dead cold overnight boots O.K. Reboots
compiz and unity fail.
Externally acts like a race condition that works sometimes other times
This is
VGA compatible controller: Intel Corporation 4 Series Chipset Integrated
Graphics Controller (rev 03)
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Lenovo 6234
This is a major company regular pc good performance running well. Runs
Win7 fine.
DISTRIB_DESCRIPTION=Ubuntu Utopic
Seems to me to be a race condition. Sometimes booting the 3.16.0-8
level I get wallpaper, no panels. Sometimes unity actually starts like
right now.
In any case, Xorg does not seem to have any problem. The screen is
displaying if only wallpaper O.K., cursor O.K.
Booted today's utopic .iso at
With this intel hardware, utopic linux image -5 and -6 unity comes up
fine.
linux image -7 unity always fails. Xorg is running fine, wallpaper,
cursor, O.K. Try starting unity and get a bunch of errors.
linux image -8 rarely boots to a running unity. usually fails.
So I boot changing the -8
Of course, I'd happily omit 3D support if I could. As far as I know 3D
has nothing to do with firefox or google-chrome or office or whatever,
only non-functional screen appearance.
Would ubuntu-tweak turn off 3D so I could run?
Thanks.
--
You received this bug notification because you are a
I think I found it in synaptic:
xserver.xorg.video.intel 2:2.99.914-1-exp1ubuntu1
Since there's only one listed, isn't that used by both the linux image
-5 which works and linux-image -7 and -8 which don't?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
On this utopic:
linux-image -5 works if I select it at boot.
linux-image -7 wallpaper only. unity won't start, lines full of errors.
linux-image -8 wallpaper only. I presume unity will get same errors.
How do I downgrade back to
xserver-xorg-video-intel_2.99.910-0ubuntu1
I didn't see that
I'm running Utopic Development now, haven't had this problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1228991
Title:
compiz crashed with SIGSEGV in _swrast_map_texture()
To manage
On Timo's comment, anyone have any idea what the component lubuntu/lxde
uses to save the configuration? I do Preferences Monitor to set it, but
what component does that?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Acer Aspire 1 D255E Intel Atom N455 Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
MESA_GL_VERSION_OVERRIDE=1.4 to the /etc/environment
is a big help on restoring desktop action. This netbook + external monitor has
been running ubuntu fine since 10.10.
Their choice. My choice is sharp and clear and quick. I take sharp
high res digital pictures, not fuzzy out of focus. Fuzzy blurred
reminds me of 1982 when I started on pc's.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Public bug reported:
Attached is screenshot. Acer Aspire 1 D255E Intel Atom N455
00:02.0 VGA compatible controller: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
Huge window
none of the selected modes were compativle with the following modes:
Trying modes
Thanks for looking at this. #3, xdiagnose is installed.
#4 Not familiar with that bug. I'll take a look.
Attached is today's screen showing vertical black bar on top of the
dexktop.
** Attachment added: Another black bar today.
I did look at bug #123428 mine is not like that in that the vertical bar
is always there. Opening tabs doesn't fix it.
Launcher is hidden, when I mouse over the launcher appears where the
black bar is, however when launcher hides again the desktop is not
restored.
Also, as in #5, sometimes
Well, this setup doesn't have xorg.conf.g or xorg.conf. I used to use them all
the time but ubuntu deleted xorg.conf.
so I tried making an xorg.conf with the data which rebooted into into low
graphics mode.
Let me see if I can make a folder xorg.conf.g and put a member vga.conf into it.
--
Tried again with /etc/X11/xorg.g/vga.conf. No luck. What I do to get a
usable desktop is:
#!/bin/bash
xrandr --newmode 1366x768_60.00 85.25 1366 1440 1576 1784 768 771 781 798
-hsync +vsync
xrandr --addmode VGA1 1366x768_60.00
xrandr --output VGA1 --mode 1366x768_60.00
Previously with
Public bug reported:
Saucy Beta 2 3.11.0-11 booted up shortly thereafter got this internal
error. Has happened on every boot today. apt-get update dist-upgrade
ran earlier today.
Acer Aspire 1 D255E Intel Atom N455
Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics
Chris, with /etc/X11/xorg.conf.d/vga.conf as you specified booted right
up with no problem on configuration.
No big window top to bottom full of lines complaining about could not
apply stored configuration. Yay.
cat /var/log/Xorg.0.log | grep onitor
[19.831] (**) | |--Monitor default
Public bug reported:
Just happened last couple of days. There's a vertical black bar on left
side of screen. Can't get rid of it with Settings Displays or xrandr.
Acer Aspire 1 D255E with 1.5.5 external monitor set to 1366x768 (will
run up to 1920x1080).
See screen capture attached.
Launcher
Note xdiagnose is installed I could do an apport-collect 1234839 however
that does create a flood of data, only if someone is interested.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1234839
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856458/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Tags added: apport-collected ubuntu
** Description changed:
Monitor configuration in saucy beta Lubuntu is set to turn off built in
monitor and set external monitor to 1360 instead of default 1920
(squint, hard to read read 1920x1080 on a 15.5 monitor).
Save
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856461/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856464/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856463/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856465/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856462/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856467/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856466/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856469/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856468/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856470/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856495/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856494/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856473/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856474/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856483/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856485/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856486/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856496/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856493/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856497/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856484/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856500/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856475/+files/xserver.devices.txt
** Description changed:
Monitor configuration in saucy beta Lubuntu is set to turn off built in
monitor and set external monitor to 1360
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856488/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856472/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856498/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856492/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856471/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856487/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856489/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856490/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
Title:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856460/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856459/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856499/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856502/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856501/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1232426/+attachment/3856504/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1232426
apport information
** Description changed:
Monitor configuration in saucy beta Lubuntu is set to turn off built in
monitor and set external monitor to 1360 instead of default 1920
(squint, hard to read read 1920x1080 on a 15.5 monitor).
Save configuration. Reboot, saved configuration
1 - 100 of 456 matches
Mail list logo
