Here's mine, it occurs in 16.04.3 with VLC 2.2.8 even, really bad HANG,
VLC unusable!
Code:
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 21
model : 2
model name : AMD FX-8370 Eight-Core Processor
stepping: 0
microcode :
"This is because you didn't first upgrade update-manager."
I figured something like that. I was convinced that it must have been an
error on my part after repeating several more tests with no issue. Chalk
that up to either too little (or too much) coffee.
--
You received this bug notification
I've run several tests and it looks good to me, so I think we're good to
go.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1611982
Title:
HWE upgrade from vivid to
I've run several more tests today and all seems well. I can only assume
that the failure in comment #17 was an error on my part. So I think
we're good to go.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-lts-xenial in Ubuntu.
I have no idea why I had that previous failure. I've since run two more
tests. One was a repeat test beginning with a fresh install of Ubuntu
GNOME 14.04.3 i386 (just like above) and it worked fine. I ran another
test beginning with a fresh install of Ubuntu GNOME 14.04.2 amd64 and it
also worked
I still encountered a failure beginning with Ubuntu GNOME Trusty i386
w/Vivid HWE. There was a kernel upgrade prior to performing the HWE
upgrade (most recent prior updates performed on 2016-08-07 followed by
installing update-manager from proposed):
Start-Date: 2016-08-13 09:58:41
Commandline:
So I'd want to check for the presence of xserver-xorg-video-r128-lts-
xenial and xserver-xorg-video-mach64-lts-xenial after the HWE upgrade?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati-lts-xenial in Ubuntu.
I have the same problem. I'm using this keyboard
http://www.pccomponentes.com/nox_krom_konker_pro_gaming.html it needs
the scroll lock key to turn on the backlight, so I need to put xmodmap
-e "add mod3 =Scroll_Lock" everytime I log in my session.
--
You received this bug notification because
It's an umbrella rather than a specific package, so:
lance@lance-AMD-desktop:~$ apt-cache policy xorg-lts*
xserver-xorg-lts-vivid:
Installed: (none)
Candidate: 3:10
Version table:
3:10 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
xserver-xorg-lts-wily:
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Kyle Brophy (kylebrophy) => (unassigned)
--
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/bugs/1507255
Title:
@ jerrylamos, which HWE stack is in use? It mostly depends on what
installation media is used (unless physical action is taken to upgrade
the HWE stack):
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A14.04.x_Ubuntu_Kernel_Support
Based on my most recent results it seemed to
Xenial looks good testing Ubuntu GNOME 20160218 amd64:
ubuntu-gnome@ubuntu-gnome:~$ uname -a
Linux ubuntu-gnome 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
ubuntu-gnome@ubuntu-gnome:~$ apt-cache policy xserver-xorg-video-intel
It took a considerable amount of searching but the sna vs uxa issue does
have at least two upstream bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=1226531
https://bugzilla.redhat.com/show_bug.cgi?id=1226743
I believe that should be sufficient. It's a known issue. I'll have to
look at
Ubuntu Trusty 20160217 amd64 is still affected so I doubt that a fix
will land for 14.04.4. That will be problematic for less advanced users
affected because both the Wily and the updated Trusty images offered
from the main download page(s) will fail to work.
To me the obvious simple "workaround"
As far as reporting upstream to move the status from incomplete back to
confirmed - I have no idea what I'm doing :^(
Is this an X bug as originally thought? Or a kernel bug as now seems to
be the case? I clearly can't create a new bugzilla account and file a
bug report when I have no idea what
I took time to check Wily and the results are similar. This bug is
present with the 4.2.0-27.30 kernel but the 4.2.0-29.31 kernel is OK.
So I'm guessing the updated intel driver fails to build properly with
kernels prior to 4.2.0-29
--
You received this bug notification because you are
Looking at the 14.04.4 RC again this AM I find that the 4.2.0-29.23
kernel is OK, but this bug is present with 4.2.0-27.21. So this is
apparently not so much an X bug as a kernel bug??
AFAIK Xenial is (or at least has been) affected by this also and I'll be
testing the Beta 1 candidates next
Lubuntu Trusty is affected to a much lesser degree so I was at least
able to install it. I'm going to try the newest kernel from proposed
tomorrow.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
The Trusty images had been good up through 20160214 but the 20160215
image is affected again. They appear to be using:
xserver-xorg-video-intel-lts-wily
2:2.99.917+git20150808-0ubuntu4~trusty2
So I need to dig a bit deeper.
--
You received this bug notification because you are a member of
I was surprised testing the Trusty Daily Ubuntu GNOME 20160207 amd64
image to find that it works OK in a live session so just making a note
for my own use regarding version:
xserver-xorg-video-intel-lts-wily
2:2.99.917+git20150808-0ubuntu4~trusty2
--
You received this bug notification because
Not surprisingly this also affects the Trusty dailies based on testing
Ubuntu GNOME Trusty 20160124 amd64 since they have the Wily HWE. So the
flavors participating may want to mention it in their release notes,
recommending that users affected use the archived 14.04.1 images.
** Tags added:
Still affects Ubuntu GNOME Xenial 20160121 amd64. So I guess I'll have
to create a Bugzilla account and try to figure out their bug filing
process when I have time.
** Tags added: amd64 xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I incorrectly staed above:
"The graphics are so badly garbled I can only file this bug on an
unaffected OS where I've held back the update on just that one package
to about Alpha 2 status"
That should have said "Beta 1 status" so I'll correct that accordingly.
** Description changed:
This
Public bug reported:
This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The graphics
are so badly garbled I can only file this bug on an unaffected OS where
I've held back the update on just that one package to about Alpha 2
status:
lance@lance-INTEL-desktop:~$ apt-cache policy
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed = Fix
I've tested both the Lubuntu 20150330 i386 and amd64 images on two
totally different sets of hardware.
Both fail to boot to the live DE on this hardware:
Intel Atom CPU 230 @ 1.60GHz
Intel 82945G/GZ Integrated Graphics Controller (rev 02)
Intel N10/ICH 7 Family High Definition Audio Controller
No idea why the explanatory text disappeared with comment #24 but that's
a pic of what the screen displays when the i386 image freezes.
This pic is what the screen displays when the amd64 image freezes.
** Attachment added: freeze_amd64.JPG
** Attachment added: freeze_i386.JPG
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361870/+files/freeze_i386.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1291644 ***
https://bugs.launchpad.net/bugs/1291644
Public bug reported:
Apport just asked if I wanted to file this report after booting the
Lubuntu Vivid image. I said yes in hopes that some info may be provided
in regards to bug #1432843.
ProblemType:
No surprise but since the 14.04.2 20150217 images still have 3.16.0-30
generic they are affected.
Since it's a hardware specific corner issue I don't know if it's worth
mentioning in the release notes or not.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I believe I encountered the same issue while working on bug #1412602
which is unrelated to this bug.
In the process of testing the nouveau driver with an nVidia C61 [GeForce
7025 / nForce 630a] chipset on Ubuntu GNOME Trusty with the Utopic HWE
and 3.16.0-31-generic from trusty-proposed I
** Description changed:
I've been testing the Ubuntu GNOME Vivid daily images in anticipation of
Alpha 2 and I noticed that with this specific hardware I get no graphics
at all other than a blank screen (see attached photo):
AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce
OK I did some more testing last night and this AM, so here's a quick
recap to reduce any confusion (both for others and myself):
Vivid: This is fixed in 3.18.0-13 generic. I verified that this AM by
testing the Ubuntu GNOME Vivid 20150215 amd64 iso.
Utopic: This is fixed in 3.16.0-31 generic
Regarding Trusty with the OEM 3.13 series kernel: This is NOT fixed in
3.13.0-46-generic from trusty-proposed. That can be verified because
using the nouveau.config=NvMSI=0 boot parameter gets me past the screen
corruption/X freeze. So evidently the upstream fix has not yet trickled
down to the
Sorry to take so long getting back to this. The affected PC is usually
used as my media center but I've now been able to move it into my
testing suite so hopefully once 14.04.2 milestone testing is out of the
way I'll be able to respond more quickly and efficiently.
Regarding the screen
I was encountering some issues installing 14.04.1 which I'll get into
later, but for now I moved on to testing 14.04.2, this one installed w
/Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150203), and
while 3.16.0-30-generic was affected I pulled 3.16.0-31-generic from
trusty-proposed
@ Tim Lunn,
This is totally unrelated, but to be certain that Vivid is working
properly w/3.18.0-13-generic I've been using it to post all of these
messages and on the last boot apport presented me with a gdm error so I
accepted the automated reporting which is bug #1421991. Poorly written
for
It turns out that both 14.04 and 14.04.1 are affected by this bug. I had
to look in the installer log to see what version I'd begun with (and
have been running on that box as my stable OS) = Ubuntu 14.04 LTS
Trusty Tahr - Alpha i386 (20140129). So I was undoubtedly able to
install Trusty at that
Hi Tim,
As far as I can tell ATM the only difference in most of these
crashes/freezes/screen-corruptions is the frequency with which they
occur and the screen color depending on what point during boot and/or
operation the freeze occurs.
Like this is the pic I included with original bug report:
I have been able to reproduce that a few times in a gnome-shell session
but it's not specific to any one task. It crashed/froze twice just
looking for logs and once again while launching Firefox. OTOH I can use
the classic session w/o a problem - in fact I'm streaming the nightly
news right now.
@ Joseph Salisbury,
There seemed to be some improvement in Ubuntu GNOME Utopic with the
amd64 version of 3.16.7-031607-generic, at least I was able to boot that
kernel w/o adding the nouveau.config=NvMSI=0 boot parameter, but then
after spending a couple of minutes fiddling around when I
Perhaps oddly (perhaps not oddly at all) I decided to reboot and select
GNOME Classic rather than booting into the standard GNOME Shell and it
seems to work fine - no screen tearing or X-freezes under fairly heavy
use. So maybe nouveau itself is simply not capable of running GNOME
Shell.
I find
@ Joseph Salisbury,
I'll be glad to do that but it'll be a couple of days due to prior
commitments.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1412602
Title:
No live
Trusty 3.13.0-44 was OK but 3.13.0-45 is affected.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1412602
Title:
No live DE in Vivid using nouveau
The latest two daily builds are failing for what must be a totally
unrelated issue because they're also failing with different hardware so
I went back to testing the Ubuntu GNOME Alpha 2 live image and it does
boot successfully with the boot parameter nouveau.config=NvMSI=0. So do
we need to edit
I tried the 3.19.0-031900rc5-generic mainline kernel on that
installation and both mutter and compiz based DE's work OK with nouveau,
but the nvidia module fails to build properly against that kernel. I
haven't yet researched what kernel we intend to ship with Vivid.
I started some testing with
Oh, I forgot to mention that I have tried the nomodeset boot parameter
to no avail.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1412602
Title:
No live DE in Vivid using
Public bug reported:
I've been testing the Ubuntu GNOME Vivid daily images in anticipation of
Alpha 2 and I noticed that with this specific hardware I get no graphics
at all other than a blank screen (see attached photo):
AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce 7025 / nForce
Here's what Ubuntu GNOME Vivid 20150119 i386 boots to when it should
display Try or Install. I was able to enter the advanced boot menu and
run check disc for defects so I know it's not just a bad burn.
** Attachment added: IMG_4799.JPG
Can someone with authorization change the status in xserver-xorg-video-
openchrome-lts-saucy from Incomplete to Won't fix?
That should end any action needed on this bug report. Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: xserver-xorg-video-openchrome-lts-saucy (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1205643
Title:
VIA P4M800
Just setting up my test suite for Trusty final testing and I see that
we've moved the xserver-xorg-video-openchrome (1:0.3.1-0ubuntu2.2) saucy
from saucy-proposed to saucy-main which is great. But we should now
probably update the Saucy status from won't fix to fix released.
Then maybe Maarten
And the apt/term log
** Attachment added: term.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+attachment/4076654/+files/term.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
BTW if you can get this into the Precise daily I'll be glad to test them
but remember we're on the brink of Trusty so testing could be delayed
several days.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
Thanks Alberto, yes it worked but it was sloppy on my end.
The vesa driver does not work well here (too much screen tearing) so I
had to approach this by installing Lubuntu Saucy and then handling the
rest in a chroot, but the attached apt logs should show you what I have.
I will not however
@ Andrea,
The 12.04 and 12.04.1 images use the same basic kernel and X-stack
(other than bug fixes and security updates) so I suspect you're dealing
with an additional issue. You should first of all rule out a bad
disc/USB (depending on which you're using to install) by entering the
advanced boot
@ Andrea,
Yes, 12.04.4 ships with the Saucy Hardware Enablement Stack:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
So those images won't work with VIA P4M800 graphics. I prefer using the
archived 12.04.1 images because I have too many computers spread out
over too large of an area and
I reported this on the QA Tracker for 12.04.4 just in case the Release
Team thinks it warrants a mention in the release notes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
I think Saucy, and the 13.10 hardware enablement stack for Precise
should both be marked won't fix because they're only supported through
July of this year. But I'm not qualified to mark it as such.
I will continue to test Edubuntu Trusty w/Flashback (Metacity) to watch
for any regressions before
** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy)
Assignee: Erick Brunzell (lbsolost) = (unassigned)
** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy)
Status: In Progress = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X
Well, I think it should show fix released for Trusty, but a dev will
have to decide if Saucy and the Saucy hardware enablement stack for
12.04.4 are going to get a won't fix or what.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Still working in Edubuntu Trusty 20140121.1 i386 :^)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1205643
Title:
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy
Hi Bartosz.
I assume you want those from Saucy and and the Saucy Hardware Enablement
Stack in the 12.04.4 candidates. Is that correct?
I'm just preparing for Trusty Alpha 2 testing for flavors so it could be
next week before I get back to this.
--
You received this bug notification because you
To the best of my knowledge this effected only Lubuntu Precise and
Quantal. If so it really could be marked won't fix since neither of
those images will be respun. Or we could wait and see if it pops up
again in Trusty
--
You received this bug notification because you are a member of
** Summary changed:
- VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy Trusty
+ VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
I recently noticed that the Saucy Hardware Enablement Stack had been
added to the Precise daily builds so I tested Ubuntu Precise i386
20140118 and not surprisingly it has the same problem as Saucy with the
P4M800 chips.
I personally prefer using the archived Ubuntu 12.04.1 i386 images
because
@ Andrea,
I totally understand what you're saying. I should first say that I'm not
a dev, just an end user/tester that also maintains a relatively large
number of PC's.
Are you aware that Saucy is only supported until July 2014?
https://wiki.ubuntu.com/Releases
IMHO Precise is a much better
Thanks Christopher,
I'm just marking this invalid because (a) it only effected Ubuntu GNOME
before it became an official flavor, and (b) I've not seen the issue in
Raring, Saucy, or Trusty.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug
Also just tried Edubuntu Trusty Alpha 1 and it's working fine in
flashback w/metacity mode so I think this could be marked fix
released???
Any thoughts Maarten?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in
Thanks for the reminder Andrea.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1205643
Title:
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy Trusty
To manage
Support for P4M800 seems to be OK with Xubuntu Trusty 20131218 i386.
Thanks Maarten :^)
I will follow up later.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1205643
@ Maarten Lankhorst,
Yes. When I boot the Lubuntu Trusty 20131129 i386 DVD to the llive DE on
that VIA P4M800 box I just get a blank screen, but you can tell the
backlight is on.
Booting the same image on my Intel box shows this version info:
lubuntu@lubuntu:~$ dpkg -s
** Summary changed:
- VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy
+ VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy Trusty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
Still broken in Lubuntu Trusty 20131129 i386.
** Tags added: saucy trusty
--
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/1205643
Title:
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy
To
Well I'd prefer finding out what broke in the openchrome driver,
otherwise I prefer sticking with 12.04 which is supported until April
2017.
--
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/1205643
It had been suggested at the Lubuntu QA mailing list the following logs
might be helpful:
/var/log/Xorg.0.log
/var/log/dmesg
/var/log/syslog
So I pulled the same from a lateral install in a dual boot after a blank
screen boot and I'm attaching all three.
** Attachment added: Xorg.0
Seems I can't add more than one at a time so here's #2.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1205643/+attachment/3800609/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
And #3.
** Attachment added: dmseg
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1205643/+attachment/3800610/+files/dmseg
--
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/1205643
Title:
Things have changed just a bit between the Alpha 2 images and the first
of the Beta 1 testing images. I now no longer freeze while the progress
bar is showing, but I still boot to a blank screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I experienced also this problem. I am using the version raring tail 13.04.
Can anyone here tell me how can I see the download link for the deb files at
https://launchpad.net/~sarvatt/+archive/sru1/+build/3118995
And Terry S (itsterry) #34 files seems not be working anymore. Hoping
someone will
Bug #1037895 may be a duplicate of this.
--
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/bugs/988290
Title:
Resolution change with KVM switch on Precise
To manage notifications
OK, I've been testing the Lubuntu Quantal 20121014 i386 image
intensively on two sets of hardware, but I have not tested at all in a
VM.
On my old VIA C7 w/P4M800 graphics I can NOT reproduce this regardless
of whether I choose Try or Install from the boot menu.
But on my Intel Atom 230 w/Intel
I just happened to think that my old P4M800 will not even begin to
render 3D graphics so I wondered if it's possible to use a boot
parameter edit to make my Intel i945 ignore 3D capability?
Maybe nomodeset?
Or maybe just a stupid idea ;^(
--
You received this bug notification because you are a
I just installed Lubuntu Precise final in order to perform Lubuntu i386
Quantal upgrade testing and even the Lubuntu i386 Precise final will
display this behavior. If you don't drag the installer windows around
you can see still see window-over-window behavior.
Since a picture is worth a thousand
Just checking this again in Lubuntu Precise final and all seems well if
I begin from the live desktop, but if I begin by selecting Install
rather than Try I get this behavior.
I did take some pics but I'm now waiting for a camera battery to
recharge. And I will of course have to double check the
Here's the shots from Lubuntu Precise. I'll follow up closer with
Quantal ASAP.
** Attachment added: shots.tar.gz
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1057120/+attachment/3398444/+files/shots.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1063267
Title:
Xorg crashed with SIGABRT in CloseWellKnownConnections()
To manage notifications about
*** This bug is a duplicate of bug 1061580 ***
https://bugs.launchpad.net/bugs/1061580
I assume bug 1061580 must be marked private. Can someone with the know-
how and ability please mark it public ;^)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Just out of curiosity I tried installing Lubuntu QQ alpha 3 on the
aforementioned hardware. All went fine other than one totally unrelated
ubiquity bug.
After installing I applied the available updates, I did NOT enable
proposed, but then it's no longer able to boot into that old (circa
2007) VIA
Thanks Lars. It sounds like I need to file a new bug report.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1041625
Title:
X not starting after install [openchrome]
To
OK, did you look at those pics in comment #16?
Lots of font config errors followed by:
Starting Mount network filesystems
Stopping Mount network filesystems
The third pic in that set is the easiest to read but it only shows about
the left half of the screen.
I'm fairly well convinced that
** Attachment added: rec_mode_errors.tar.gz
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1041625/+attachment/3281483/+files/rec_mode_errors.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Oops, that attachment was supposed to be accompanied by this text:
Trying to boot or even update through recovery mode after enabling
networking displays these '/lib/udev/mtp-probe' errors.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
BTW this is the box that I use for testing both ubiquity and d-i so it's
really important to me. I'd really like to test all of the recent
installer changes on bare metal ;^)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
After installing a fresh Lubuntu i386 alpha3 and upgrading only 'libmtp-
common' and 'libmtp9' I get a very slow boot - I mean 3 to 4 minutes!
From looking at the changelogs I seriously doubt that this is actually
an xserver bug but I lack the tech knowledge to proceed so any help
would be
Lars, I'm not sure this is related but I'm unable to even boot Lubuntu
i386 20120827 to the live desktop on my old VIA box:
VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA
I did some more fiddling and I'm fairly well convinced that this is
actually a 'gnome-screensaver' bug.
I first booted into an Lubuntu Precise and installed 'gnome-desktop-
environment' which I know is Gnome version 3.0 rather than the Gnome
version 3.2 + bits of 3.4 that Ubuntu Precise uses.
*** This bug is a duplicate of bug 988290 ***
https://bugs.launchpad.net/bugs/988290
** This bug has been marked a duplicate of bug 988290
Resolution change with KVM switch on Precise
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I actually didn't spend much time at all on it ;^)
I've just been battling some health issues and I did a very lax job of
testing over the past several months. I've been grouchy too :^(
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I need to do more cross testing to be certain but this evening I was
testing Xubuntu Precise i386 (20120801.1) and I don't see this. So maybe
it's actually a 'gnome-screensaver' bug
I'm guessing it's not limited to only 'xserver-xorg-video-intel' ATM but
I really must do more studying. It is
1 - 100 of 138 matches
Mail list logo
