it seems that ppc is having a problem with X, too, but i don't think
it's the same problem. furthermore, i don't think any apple computer (i
realize there are other ppc machines out there but they tend to be more
rare) ever had a chipset supported by openchrome. someone correct me if
i'm wrong.
Does that fix ppc too Lars?
--
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 manage notifications about this
Lars try adding video=ofonly. Either way please file a new bug for ppc.
--
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
I don't have the exact same symptoms. It'll start X, but it looks all 16
bit. There is another solution: boot parameters
video=radeonfb:xresxyres[-bpp][@refresh] where xres is
xresolution, yres is yresolution (use whatever's native to your machine;
you can look it up online), bpp is optional, and
arild, please go to vt (ctrl-alt-f1 or rather since you're on a ppc fn-
ctrl-alt/option-f1) and use the terminal to get your /var/log/Xorg.0.log
and post it here.
easiest way:
1. plug in ethernet
2. sudo ifconfig eth0 up
3. sudo dhclient eth0 (assuming you get your ips from dhcp)
4. sudo apt-get
Public bug reported:
i put a lot of information here before it was suggested to make a new bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518
but to summarize the only way i could get X to start was by turning of KMS,
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i
--
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/1061790
Title:
misbehaving X on quantal ppc w/ nvidia geforce fx go5200
To manage notifications about this bug go to:
** Description changed:
i put a lot of information here before it was suggested to make a new bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518
but to summarize the only way i could get X to start was by turning of KMS,
e.g. nomodeset or nouveau.modeset=0 boot
good point. you can see dmesg/Xorg.0.log for the default boot here:
http://paste.ubuntu.com/1254953/
and indeed No devices detected is at the bottom
if it's relevant to anyone curious, here's the same info for nomodeset:
http://paste.ubuntu.com/1255047/
--
You received this bug notification
using lubuntu desktop i386 20141014, i have no problems. don't have an
amd64 machine handy at present.
--
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/1378423
Title:
Virtualbox boots to black
another successful test:
image: Xubuntu i386 20141016
vm: VirtualBox 4.3.18-96516~Ubuntu~raring
host: Kubuntu 14.04
boots straight to the try/install screen without having to flip virtual
terminals or anything.
i'm guessing this is either a host hardware conflict of some kind or
It appears that this affects a very specific chip. That being said, I
can't do much to help diagnose this. With that in mind, it would be
useful to find out exactly what conditions are required for this to
occur. Is it only that particular package? It should be tested across
different OS versions
You guys that do have this bug should update the bug description so that
it includes the following sections:
STEPS TO REPRODUCE
1.
EXPECTED RESULTS
*
ACTUAL RESULTS
*
AFFECTS
* images
* Lubuntu amd64/i386 starting 20150316
* hardware
*
DOES NOT AFFECT
* images
* Xubuntu (correct?)
*
Note here https://bugs.launchpad.net/ubuntu-cdimage/+bug/1441843 that
/usr/lib/xorg/modules/drivers is missing most of its drivers due to the
fact that most, if not all, of the xserver-xorg-video-* packages are
missing. My guess is that this is the problem: they're not in the
manifest! Compare
Can you guys get virtual terminals, out of curiousity? If so, I'd be
interested to see /var/log/syslog and /var/log/Xorg.0.log and
/var/log/lightdm/lightdm.log. Betcha they jive with that other bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
*** This bug is a duplicate of bug 1441843 ***
https://bugs.launchpad.net/bugs/1441843
Confirmed this is a bug in the seed. Julien is on it and it should be
resolved in time for release. This doesn't affect X but I can't remove
that it seems. Alberto? I'm going to dupe this against the other
*** This bug is a duplicate of bug 1424362 ***
https://bugs.launchpad.net/bugs/1424362
** This bug is no longer a duplicate of bug 1434220
lubuntu crash on start
** This bug has been marked a duplicate of bug 1424362
permissions issues in LXDE as of Vivid Lubuntu Final Beta
--
You
Is this not the same problem you described in the other bug you recently
made?
--
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/1430358
Title:
lubuntu crash on start
To manage
*** This bug is a duplicate of bug 1450785 ***
https://bugs.launchpad.net/bugs/1450785
** This bug has been marked a duplicate of bug 1450785
X server fails to start on Lubuntu Vivid desktop
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Speaking as a member of the Ubuntu Community Council, I'm going to have
to ask that we dial down the tone here. As you know, the Code of Conduct
(https://www.ubuntu.com/about/about-ubuntu/conduct) means that we should
act with respect and consideration, act collaboratively and work towards
Again: let's keep any further discussion about people directed towards
community-coun...@lists.ubuntu.com and let's keep the bug report for
talking about the actual software. In other words, no more comments
about the CoC violations in this bug report. Let's get back to talking
about the software.
We need to talk about software here, not personal issues. You both are
going to stop attacking each other, defending yourself against each
other, and talk about software. If you cannot talk about the software
without getting these other issues intermingled here, do not comment at
all.
Since you
Phillip and bodhi, I know this is something we have discussed before,
but I'm going to say it again and hopefully for the last time: please
keep your comments civil. You can disagree with each other all you want,
but do it respectfully, please. If you see yourself using the word "you"
(or if it's
One more thing. The corrected version is actually in proposed:
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati/1:18.0.1-2
I do not recommend enabling proposed in general, especially for
something so crucial to the whole system. However, since it seems you're
doing testing and not on a
bodhi, having the Technical Board review Phillip's posts might be
completely reasonable so as to finally end this conversation once and
for all. That has no bearing on the moderation, though.
The entire Ubuntu Community is bound by the terms of the Code of
Conduct, which, in short, means being
Marking as invalid. Talked to Lyn and she said that the original
hardware is gone, so can't test it on that. Additionally, she tried on
other hardware and couldn't reproduce.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Invalid
** Changed in: xserver-xorg-input-mouse (Ubuntu)
26 matches
Mail list logo
