** Tags removed: lucid
--
Only root can start X at a reasonable resolution
https://bugs.launchpad.net/bugs/669002
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
https://lists.ubu
I'm now convinced that my problem is a different bug, as it is not
related to the SAVAGE driver, so I've created a bugtracker entry for it:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/669002
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launc
** Attachment added: "Xorg.0.log file from failed 'startx' attempt"
https://bugs.launchpad.net/bugs/669002/+attachment/1717833/+files/Xorg.0.log.nb.doesntwork
--
Only root can start X at a reasonable resolution
https://bugs.launchpad.net/bugs/669002
You received this bug notification because
Public bug reported:
Binary package hint: xorg
After upgrading from 10.04 to 10.10 on 2010-10-29, I've experienced the
following show-stopper a problem: I'm using gdm. However, upon entering
the correct password at gdm, the screen blinks and the gdm login screen
is built up again.
In order to st
I've just upgraded from 10.04 to 10.10; now I'm experiencing a problem
which is, superficially at least, very similar. I'm using gdm however.
Upon entering the correct password at gdm, the screen blinks and the gdm
login screen is built up again. Another similarity is that this is also
with the SAV
Hugh,
what I did is that I installed from the Ubuntu 8.10 server CD. IIRC I then
installed GNOME manually with apt-get (which of course pulled in X11) and used
an old xorg.conf file.
--
install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You
There's currently a team forming for jointly maintaining the CrossWire
packages (e.g. sword, gnomesword, bibletime) for Ubuntu and Debian.
The current package maintainer in Debian has just created a new
mailing list and has invited everyone who is interested to join:
http://lists.alioth.debian.org/
There's currently a team forming for jointly maintaining the CrossWire
packages (e.g. sword, gnomesword, bibletime) for Ubuntu and Debian.
The current package maintainer in Debian has just created a new
mailing list and has invited everyone who is interested to join:
http://lists.alioth.debian.org/
There's currently a team forming for jointly maintaining the CrossWire
packages (e.g. sword, gnomesword, bibletime) for Ubuntu and Debian.
The current package maintainer in Debian has just created a new
mailing list and has invited everyone who is interested to join:
http://lists.alioth.debian.org/
Public bug reported:
The summary says it all, this package needs updating to upstream version
1.5.11
** Affects: sword (Ubuntu)
Importance: Undecided
Status: New
--
needs updating to upstream version 1.5.11
https://bugs.launchpad.net/bugs/320558
You received this bug notification
Public bug reported:
Binary package hint: bibletime
The subject says it all... this package needs updating to upstream
version 1.6.5.1.
** Affects: bibletime (Ubuntu)
Importance: Undecided
Status: New
--
needs updating to upstream version 1.6.5.1
https://bugs.launchpad.net/bugs/3
Ok, done.
Well, I didn't try installing your package on the live CD system (I'd be
surprised if that's possible), but I made a jaunty alpha 3 install on a
disk partition that has no valuable data. I had to use the "alternate"
install CD for this: Installation with the "desktop" CD totally fails
Actually what the package does is that it tries to download (and then
install fonts from)
http://support.wolfram.com/mathematica/systems/windows/general/file/MathFonts_TrueType_41.exe
This fails because the link is broken at support.wolfram.com: The server
now redirects to http://support.wolfram.
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/20394872/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/20394873/DpkgTerminalLog.gz
--
package ttf-mathematica4.1 4 failed to install: post-installation script
terminated abnor
Public bug reported:
Binary package hint: ttf-mathematica4.1
I installed this system today using the "server" install CD (even though
it is a desktop system, because the "desktop" CD fails to install on
this machine), then installed gnome and a couple of other things
manually. Then went looking
I can confirm that the bug is NOT fixed in Intrepid 8.10 for me either.
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What happens in gutsy's install process is that during xserver-xorg
postinst, MONITOR_IDENTIFIER is set to "Generic Monitor", for which
(somewhat reasonable) hsync and vrefresh values are then obtained from
the monitors database.
--
[hardy beta] install failure (regression) with ProSavageDDR grap
Maybe in the case that no useful hsync and vrefresh info can be obtained
from the monitor (in my case, a Highscreen MS 2195P), the installation
system should ask the user to make a selection from a list?
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.
** Attachment added: "dmesg from the hardy beta install made with "safe
graphics mode""
http://launchpadlibrarian.net/13414635/dmesg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification becau
** Attachment added: "Xorg.0.log from the install made with "safe grphics mode""
http://launchpadlibrarian.net/13414620/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because
** Attachment added: "dmesg from gutsy"
http://launchpadlibrarian.net/13414612/dmesg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "'lspci -vvnn' output from gutsy"
http://launchpadlibrarian.net/13414598/lspci
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs
Xorg.0.log from gutsy
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/13414584/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubunt
** Attachment added: "dmesg from hardy beta ("Normal" install mode) when I
arrived in console text mode"
http://launchpadlibrarian.net/13414566/dmesg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug n
** Attachment added: "'lspci -vvnn' output from hardy bety"
http://launchpadlibrarian.net/13414555/lspci
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Xorg.0.log from hardy beta ("Normal" install mode) when I
arrived in console text mode"
http://launchpadlibrarian.net/13414136/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received
Public bug reported:
Binary package hint: ubiquity
On my desktop PC, installing from the Hardy Beta iso fails unless "safe
graphics mode" is chosen (which results in an install that uses a low
graphics resolution). Ehat happens when trying to install in normal
mode is not always the same. Somet
27 matches
Mail list logo
