This is the Debian etch Xorg.0.log file, from the system actually
running on this Averatec laptop.
** Attachment added: "Xorg.0.log from successful Debian etch installation"
http://launchpadlibrarian.net/19525269/Xorg.0.log
--
Installer fails to recognize display on Averatec 3280
https://bugs
This is the Debian etch xorg.conf file, from the system actually running
on this Averatec laptop.
** Attachment added: "xorg.conf file from Debian etch running on this Averaatec
laptop."
http://launchpadlibrarian.net/19525296/xorg.conf
--
Installer fails to recognize display on Averatec 3280
This is the generic xorg.conf file generated during the installation
attempt. Nothing exciting here!
** Attachment added: "xorg.conf file from intrepid install attempt on Averatec"
http://launchpadlibrarian.net/19525198/xorg.conf
--
Installer fails to recognize display on Averatec 3280
https:
*** This bug is a duplicate of bug 296142 ***
https://bugs.launchpad.net/bugs/296142
** This bug has been marked a duplicate of bug 296142
Installer fails to recognize display on Averatec 3280
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.
Public bug reported:
Binary package hint: xserver-xorg-video-openchrome
An attempt to install or run Intrepid 8.10 from the desktop CD fails
while the system is trying to identify the display hardware.
System: Averatec 3280 laptop
Display controller: ATI Technologies Inc Rage XL rev 39 (see Xor
** Attachment added: "Xorg.0.log from attempt to install intrepid on Averatec
3280"
http://launchpadlibrarian.net/19525011/Xorg.0.log
--
Installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/296142
You received this bug notification because you are a member of
I sent the 8.04 Feisty xorg.conf and Xorg.0.log files on 2008-11-08 -
see above.
I can send hardy 8.04 files if that will help - that's a case where I
had to overwrite the xorg.conf with the Feisty version.
I'll see what I can do regarding 8.10 files. I didn't get very far into
the live boot or i
I also have the xorg.conf and Xorg.0.log files from Hardy 8.04.1
attached above.
I'll make another attempt to get the files from the failed attempts to
boot or to start installing 8.10.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received
I finally succeeded in getting a log file from an attempt to boot the
8.10 disk. Also I was able to get the screen to start in a 1024x768
mode.
I was able to get into a console after identification of the display
failed. At that point, I was able to save the Xorg.0.log file, as
before. it is alrea
Public bug reported:
Binary package hint: xorg
After upgrading online from 8.04.1 to 8.10 (Intrepid), and starting the
new system, keyboard and mouse input to the X server are frozen.
However, if I switch to a console and restart X either by killing the
Xorg process explicitly or executing '/etc
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/19633964/dmesg.txt
--
[intrepid] X server fails to start properly on Jetway
https://bugs.launchpad.net/bugs/297927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This happens each time I reboot, but not when I restart X with ctrl-alt-
BS.
I've enclosed the last bit of my /var/log/daemon.log, covering the
installation.
What other files would be useful?
** Attachment added: "var/log/daemon.log"
http://launchpadlibrarian.net/19634232/daemon.log
--
[int
** Description changed:
Binary package hint: xorg
After upgrading online from 8.04.1 to 8.10 (Intrepid), and starting the
new system, keyboard and mouse input to the X server are frozen.
However, if I switch to a console and restart X either by killing the
Xorg process explicitly or
Possible solution:
I may have found a fix to this problem - in /etc/rc2.d, I changed the
symlink S13gdm to S90gdm to delay startup of gdm. ( S90gdm ->
../init.d/gdm)
I have only rebooted once since changing this, so more testing is
necessary.
Some concerns are that whatever the race condition i
I upgraded another system with the same type of motherboard, chipset,
and cpu. In this case, I used the alternate install CD as the primary
source of new files, allowing access to the Internet for additional
upgrades.
In this case, the symlink for starting gdm in /etc/rc2.d turned out to
be S30gdm
In my case, the installation halted from time to time, indicating that
some part of the installation crashed. Sometimes I tried using apt-get
to continue the update, and finally I clicked on the orange install-
error icon to finish.
I started the upgrade by mounting the ISO image for the alternat
For the Averatec laptop, it's 1024x768. When fed at a higher resolution, the
image is cropped to 1024x768.
On Wed, Jun 17, 2009 at 5:12 AM, Bartosz wrote:
> What is corect resolution of your monitor?
>
> --
> [K8M800] Panel on K8M800 is not supported (Averatec 3280)
> https://bugs.launchpad.net
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27398494/Dependencies.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/18
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xorg 1:7.4~5ubuntu18
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
ProcVersion:
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/27398496/LsHal.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
You recei
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "LsMod.txt"
http://launchpadlibrarian.net/27398497/LsMod.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
You recei
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "XorgConf.txt"
http://launchpadlibrarian.net/27398499/XorgConf.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
You
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "LsPci.txt"
http://launchpadlibrarian.net/27398498/LsPci.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
You recei
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "XorgLog.txt"
http://launchpadlibrarian.net/27398500/XorgLog.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
You r
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "XorgLogOld.txt"
http://launchpadlibrarian.net/27398509/XorgLogOld.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
*** This bug is a duplicate of bug 353208 ***
https://bugs.launchpad.net/bugs/353208
** Attachment added: "system.txt"
http://launchpadlibrarian.net/27398510/system.txt
--
Gutsy alternate installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/186103
You rec
Public bug reported:
Binary package hint: rhythmbox
While playing music on rhythmbox, I can't get the current music title
etc. to show up on Pidgin.
The versions are the current ones in Ubuntu 9.09 as of 3 May 2009.
pidgin:
Installed: 1:2.5.5-1ubuntu8
Candidate: 1:2.5.5-1ubuntu8
Version t
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/26301030/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/26301031/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/26301032/ProcStatus.txt
--
Rhythm
I just submitted a similar report against rhythmbox - # 371516.
Possibly this is the same problem.
--
Music tracker plugin not working with VLC media player
https://bugs.launchpad.net/bugs/345742
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This seems to be the same problem reported in bug #345742 with VLC and
pidgin, possibly the cause is the same. I'm not sure yet it's a
duplicate.
--
Rhythmbox music status not shown by Pidgin
https://bugs.launchpad.net/bugs/371516
You received this bug notification because you are a member of Ubu
But this report is against 8.04 - different Ubuntu version ... in the
case of rhythmbox, it worked for 8.10 and earlier, stopped working after
upgrading to 9.04.
--
Music tracker plugin not working with VLC media player
https://bugs.launchpad.net/bugs/345742
You received this bug notification bec
This is the Music Tracker plugin for Pidgin.
On my 8.10 system, the Pidgin is version 2.5.2.
Rhythmbox is 0.11.6
This works on the 8.10 system.
For the version(s) on the 9.04 version of Ubuntu, this does NOT work.
On Mon, May 4, 2009 at 1:38 AM, Sebastien Bacher wrote:
> there is no such opti
It's a Pidgin plugin, actually. So the bug should probably be
transferred to Pidgin. A similar bug was reported on Pidgin under
8.04, but the music player was VLC. That person is upgrading to 9.04
now, and will update his bug report.
It was suggested that I report this directly to Pidgin developer
I have now tried this with the Ubuntu 9.04 rc live disk:
I have attached an xorg.conf file which sets the following screen
resolutions, after switching to a console and executing
sudo service gdm restart
1024x768 (new)
800x600
640x480
512x384 (new)
400x300
320x240
** Attachment added: "xorg.c
This also works with the Kubuntu 9.04 rc live disk.
The only difference is that
sudo service kdm restart
restarts X, enabling the new xorg.conf file.
--
BFe: No signal with Samsung SyncMaster 570s and ProSavage8 [patch]
https://bugs.launchpad.net/bugs/294899
You received this bug notificati
Guillaume -
That's the default xorg.conf file generated by recent versions of X in
Linux. Apparently the driver and display resolution is determined
without regard to that xorg.conf file. However if settings for display
resolution and the driver are put into xorg.conf by editing it or using
an ea
On trying to run Ubuntu 9.04, Xubuntu 9.04, and Kubuntu 9.04, Beta and
RC versions from live CDs, I have these observations: The initial screen
resolution is something like 1600 x 1200, but the display only shows the
top left 1024x768 portion of this. This is barely acceptable in Ubuntu
and Xubuntu
I have no idea. I subsequently installed Debian on that laptop, and
haven't tried Ubuntu on it since (though I have hardy on four desktop
systems, including a Dell PowerEdge 400SC, with no serious problems).
Peter
On Thu, Oct 2, 2008 at 12:29 PM, Jonathan Carter <[EMAIL PROTECTED]> wrote:
> Does
On my gBox computer with a S3 Inc. VT8375 [ProSavage8 KM266/KL266]
display controller, connected to a Samsung SyncMaster 570S TFT display,
mentioned above, the hack in the previous comment does not work. The
reason is that X won't even start in low-graphics mode, and it doesn't
seem to be possible
Also, I experience a similar problem on my Averatec 3280 laptop, which
has a VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01).
Again, the output of the S3 adapter appears never to be right for the
display, even trying low-graphics mode. (I'm typing this report on the
same computer, run
I just tried booting an Intrepid 8.10 desktop disk as a live CD on this
laptop. Again, I am unable to get the display to work even in low res
mode, and am unable to get to a console to copy the xorg.conf file. I
added some comments about this to bug report # 212510. Note that this
laptop and the gB
For comparison, I tried booting a Fedora 9 live CD in all 3 systems I
mentioned above (the Dell server, the gBox with an S3 display
controller, and the Averatec laptop with an S3 display controller.
I was unable to complete booting the 2 systems with S3 controllers - the
system hung completely aft
Note that the CD, when booted as a live CD, *appears* to have the
correct drivers. However, the drivers for the S3 cards seem unable to
determine a workable screen resolution for the Samsung SyncMaster 570S
TFT display, or for the Averatec display. I have not found a way to try
to install a modifie
Public bug reported:
Binary package hint: xserver-xorg-video-savage
This occurs on trying to boot the intrepid 8.10 CD as a live CD on a gBox
computer
Display controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
Display: Samsung SyncMaster 570S TFT
While trying to boot the CD, eventually the dis
** Attachment added: "This is the xorg.conf file which works under hardy,
generated by booting a 7.04 CD. lspci shows VGA compatible controller: S3 Inc.
VT8375 [ProSavage8 KM266/KL266]"
http://launchpadlibrarian.net/19441069/xorg.conf
--
No signal with Samsung SyncMaster 750s and ProSavage
I have reported the problem with the gBox computer with the savage
display controller as a separate bug now, #294894.
--
[gutsy] [hardy]No signal with Samsung SyncMaster 750s
https://bugs.launchpad.net/bugs/212510
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Correction: I have reported the problem with the gBox computer with the
savage display controller as a separate bug now, #294899.
--
[gutsy] [hardy]No signal with Samsung SyncMaster 750s
https://bugs.launchpad.net/bugs/212510
You received this bug notification because you are a member of Ubuntu
B
The behavior when trying to boot intrepid on this Averatec laptop is
quite similar to the behavior described in bug #294899 and 212510 when
trying to boot on a gBox computer with a ProSavage8 display controller
and Samsung SyncMaster 570S display, except that the laptop's display
does not have the
That would be from hardy, since I can't boot intrepid and get at a
shell.
On Fri, Nov 7, 2008 at 1:26 AM, Bryce Harrington
<[EMAIL PROTECTED]> wrote:
> Hi peterbe,
>
>
> Thanks for including the attached files. Could you also include your
> /var/log/Xorg.0.log?
>
>
> ** Changed in: xserver-xorg-
Here is the /var/log/Xorg.0.log
In this case, I went through the motions of an actual install, rather
than a live boot. The boot failed, without installing anything, but
ended up in a shell, so that I could copy the log file to the hard disk.
A quick glance at the file tells me there is useful in
Here is the /var/log/Xorg.0.log from booting Feisty 7.04. The display
was initialized properly in 1024x768 resolution, the maximum supported
byt the Samsung display.
** Attachment added: "Xorg.0.log - feisty"
http://launchpadlibrarian.net/19496191/Xorg.0.log
--
No signal with Samsung SyncMas
Here is the xorg.conf file generated by booting feisty as a live CD.
This file may be used to solve resolution problems under Hardy as well.
** Attachment added: "xorg.conf on feisty"
http://launchpadlibrarian.net/19496270/xorg.conf
--
No signal with Samsung SyncMaster 750s and ProSavage8
htt
Here is an Xorg.0.log file generated from installing hardy on the same
system, using the alternate CD.
An attempt to boot from the live CD (desktop CD) failed. I wasn't able
to save the log file from that failed attempt.
** Attachment added: "Xorg.0.log from alternate install of hardy 8.04.1"
xorg.conf file from alternate install of hardy 8.04.1
The maximum screen resolution with this file was 800x600.
I was able to get 1024x768 resolution by replacing this with the
xorg.conf from Feisty 7.04 (see above).
** Attachment added: "xorg.conf from hardy alternate install"
http://launchp
This is marked as 'incomplete'. What is needed?
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
*** This bug is a duplicate of bug 212510 ***
https://bugs.launchpad.net/bugs/212510
1. The duplicate status is inappropriate, even though the linked
report(s) is/are very similar. Each display controller/display
combination behaves a bit differently from the others.
2. This is an update for
*** This bug is a duplicate of bug 212510 ***
https://bugs.launchpad.net/bugs/212510
Here is the corresponding xorg.conf file, generated when booting the
8.10 desktop CD on this system. With this xorg.conf file, the system
will have a maximum resolution of 800x600. With the 7.04 version of the
I hope to try this on Intrepid within a few days after its release (that
is possibly tomorrow?)
--
[gutsy] [hardy]No signal with Samsung SyncMaster 750s
https://bugs.launchpad.net/bugs/212510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This bug is NOT fixed with Intrepid 8.10 for my gBox computer with a S3
Inc. VT8375 [ProSavage8 KM266/KL266] display controller, connected to a
Samsung SyncMaster 570S TFT display. (see above).
I downloaded the 8.10 desktop ISO, and booted that on this system as a
live CD. The system was unable to
This bug is NOT fixed with Intrepid 8.10 for my gBox computer with a S3
Inc. VT8375 [ProSavage8 KM266/KL266] display controller, connected to a
Samsung SyncMaster 570S TFT display. (see bug #217004).
I downloaded the 8.10 desktop ISO, and booted that on this system as a
live CD. The system was una
This is also still NOT fixed on my Dell PowerEdge 400SC with the same
Samsung SyncMaster 570S TFT display, and an ATI Technologies Inc Rage
XL (rev 27) vga controller.
I booted the desktop 8.10 Intrepid CD, as a live CD, and in this case
the system booted completely and displayed in 800x600 low-r
Starting over, so to speak:
This is an accessibility problem. The issue is that default fonts on
many web pages are too small for many people with minor vision problems,
or people who are simply over the age of 40, to read. I suppose one
could require such people to buy 30-inch displays, but that
This is of course an upstream issue for the Mozilla project developers.
--
CSS works improperly
https://bugs.launchpad.net/bugs/257408
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
Public bug reported:
Binary package hint: xserver-xorg-driver-all
The system is a Dell PowerEdge 400SC. It has been running properly with
a 14" generic CRT monitor. A few days ago, I plugged in a Samsung
SyncMaster 570S TFT 15" flat screen monitor, which initially worked well
without a change in
I just submitted another bug (# 255561) regarding a similar problem with
the same Samsung monitor on another system (Dell PowerEdge 400SC), where
Ubuntu fails to set up xorg.conf properly, but Knoppix does.
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bu
** Attachment added: "xorg.conf generated when running Knoppix 5.1.1"
http://launchpadlibrarian.net/16603997/xorg.conf.knoppix
--
dpkg-reconfigure xserver-xorg fails on Dell PowerEdge 400sc with ati and
Samsung SyncMaster 570s
https://bugs.launchpad.net/bugs/255561
You received this bug noti
** Attachment added: "most recent xorg.conf"
http://launchpadlibrarian.net/16603984/xorg.conf.20080806113049
--
dpkg-reconfigure xserver-xorg fails on Dell PowerEdge 400sc with ati and
Samsung SyncMaster 570s
https://bugs.launchpad.net/bugs/255561
You received this bug notification because y
I've tried essentially the same thing - copying and pasting from the
Knoppix xorg.conf - that hasn't been too successful so far. But I'll try
some more, given time - I won't have much time till the 12th of August.
--
dpkg-reconfigure xserver-xorg fails on Dell PowerEdge 400sc with ati and
Samsun
This page has the specs of the Samsung monitor:
http://reviews.cnet.com/lcd-monitors/samsung-syncmaster-
570s/4507-3174_7-1589730.html
--
dpkg-reconfigure xserver-xorg fails on Dell PowerEdge 400sc with ati and
Samsung SyncMaster 570s
https://bugs.launchpad.net/bugs/255561
You received this bug
I was able to boot the Gentoo 2006 live CD (but not the 2007 version,
which failed to identify the display).
The generated xorg.conf is attached.
** Attachment added: "xorg.conf from running gentoo 2006"
http://launchpadlibrarian.net/16605221/xorg.conf.gentoo
--
dpkg-reconfigure xserver-xorg
Here is /var/log/Xorg.0.log - there is an explanation of why the higher
resolutions weren't used - but I don't quite understand that.
Look at the man pages for xrandr, dexconf, xorg.conf, etc.
Ubuntu started using a new version of xorg software very recently.
** Attachment added: "Xorg.0.log at
This problem is in fact a severe usability problem - basically it makes
Ubuntu essentially unusable for all but skilled computer geeks on the
affected systems.
I can spend hours upon hours tracking this bug down, trying to see if my
hand-edited xorg.conf file's directives will be overridden by the
I have attached Xorg.0.log for the system *I* have been reporting on in
this bug report.
It shows the reason the system rejected the 1024x768 screen mode - "(II)
VESA(0): Not using built-in mode "1024x768" (width too large for virtual
size)"
This is the same reason shown in the log for my system
This is identical to my submissions to Bug report #217004, as is shown
by the Xorg.0.log files I have attached in both bug reports. The
1024x768 mode is rejected on both systems for the same reason -
"(II) VESA(0): Not using built-in mode "1024x768" (width too large for
virtual size)"
There reall
Trying this again ...
I made sure the Style setting is as below.
I am now letting the page set font settings from both Windows and Linux
versions of the Firefox browser. Both chose a sans-serif font. For all font
sizes, Windows places the bottom links and the graphics in question
properly (with o
Excellent! I was able to duplicate this. I tried 'none', 10pt, and 11pt settings
(before the minimum was at 12 or 14pt.) From 'none' up to 10pt. the
layout was correct.
However, on my 1024x768 15-inch TFT screen, the fonts were too tiny to
read, and I had to magnify the font size. The positioning
If that's true with the BFCU website, it's also true with many sites.
By the way, the behavior is the same with the Windows version - I
just tried setting the minimum point size to 11 and larger sizes,
and see the same problem.
MS IE considers this kind of setting to be an accessibility issue -
a
Public bug reported:
Binary package hint: firefox-3.0
The web page http://www.bayfed.com/ has an improperly positioned image
near the bottom of the screen ("Equal Housing Lender" "NCUA", and so
on), and also the links nearby are in the wrong place.
The MS-Windows version of Firefox 3.0 works pro
** Attachment added: "Screenshot near bottom of page"
http://launchpadlibrarian.net/16731470/Screenshot-Bay%20Federal%20Credit%20Union%20-%20Mozilla%20Firefox.png
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16731471/Dependencies.txt
** Attachment added: "Extensio
I tried the above instructions regarding zoom settings on 3 different
computers, with different displays, running different display
resolutions.
I was unable to zoom to a state where the bug does not appear, trying
all possible zoom settings, using the menu, Ctrl+0, Ctrl++, Ctrl+-, etc.
With any
I suggest porting the old 6.06 LTS configurator to 8.04.1 LTS for cases
like this; allowing the user to use that when the auto-conf fails to
satisfy the user, or fails to work at all.
--
dpkg-reconfigure xserver-xorg fails on Dell PowerEdge 400sc with ati and
Samsung SyncMaster 570s
https://bugs
This is the same page seen with MS-Windows Firefox, on Windows XP
Professional, for reference:
Firefox version 3.0.1:
Mozilla/5.0 (Windows;U;Windows NT 5.1;en-US;
rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
I tried zooming in and out using this MS-Windows version - the links and
the graphics imag
This seems to be very similar to Bug #212510, which is reported fixed in
'intrepid'. Hopefully it will be also fixed in 8.04 LTS.
--
dpkg-reconfigure xserver-xorg fails on Dell PowerEdge 400sc with ati and
Samsung SyncMaster 570s
https://bugs.launchpad.net/bugs/255561
You received this bug notif
Regarding the Samsung SyncMaster, this seems to be the same problem as
in my reported bug #255561. I'll try and see if generating an xorg.conf
as above will work. (Using a floppy won't be necessary, I could just
mount the partition with my /home directories and copy it there,
probably as root after
I followed the advice of JacobS to boot an earlier Live CD - in
particular, I booted a 7.04 live CD, which worked, mounted my original
/home volume on a mount point I created, and saved the xorg.conf
generated by 7.04 into my old home directory. Then I rebooted into
8.04.1, and copied the 7.04 xorg
In my case, the issue is the Samsung SyncMaster 570S TFT monitor not
being recognized by automatic configuration. The workaround I used was
to boot a 7.04 live CD, save the xorg.conf file generated by that, and
then to copy that to /etc/X11 after rebooting to 8.04.1. After that I
reboot to make th
To fill in what's happened in the last few months: After failing to
install Hardy alpha6, I gave up and installed Debian 4.0 on my Averatec
laptop, so I failed to follow this up on the laptop.
However I did eventually install 8.04.1 on four desktop systems. This
went well, until I replaced a tube
I find the new way of selecting cursors not too user-friendly. It's
associated with themes - either you go through the themes-setting menus,
or go through the screen background dialog. Neither makes much sense to
me.
It's sufficienly obscure that I had to go find this bug report to find
out how to
I am having a similar problem with a gBox system with a S3 ProSavageDDR
display chip and VIA chipset on the motherboard.
I have Ubuntu 8.04.1 installed.
Here's some lspci info:
# lscpi
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
# lspci -n
01:00.0 0300: 5333:8d04
** Attachment added: "xorg.conf running Knoppix - works at 1024x768"
http://launchpadlibrarian.net/16540440/xorg.conf.knoppix
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you a
** Attachment added: "xorg.conf running Mandriva live CD"
http://launchpadlibrarian.net/16540447/xorg.conf.mandriva
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a membe
** Attachment added: "xorg.conf running feisty - 800x600"
http://launchpadlibrarian.net/16540454/xorg.conf.feisty
--
[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
Also I was able to run successfully at 1024x768 using a Gentoo live CD,
version 1.6.14. I have attached the xorg.conf file from that.
** Attachment added: "xorg.conf from Gentoo live CD"
http://launchpadlibrarian.net/16542895/xorg.conf.gentoo-2006
--
[hardy beta] install failure (regression)
A related problem is that under Gnome in hardy, the mouse setting dialog
has had cursor selection removed - it's part of theme setting now
(System -> Appearance). Also the gcursor program doesn't affect the
cursors, even though it shows the cursors that are installed.
--
Crystalcursors package do
Public bug reported:
Binary package hint: gnome-control-center
Selection of the mouse pointer has changed radically under hardy and
Gnome 2.22.3 - finding how to do this is un-obvious and obscure.
Also, pointer selection can crash Firefox. That happened to me while I
was attempting to file this
The second current way to get to theme (and thus mouse pointer)
selection, is to right-click on the screen background, bringing up a
menu which allows one to select "Appearance Preferences" in addition to
'Background' - one of these choices is "Theme" which works as above.
--
Mouse pointer selec
This shows the 'hardy' mouse preferences dialog - with the pointer
selection tab removed.
** Attachment added: "Mouse Preferences in 'hardy'"
http://launchpadlibrarian.net/16910377/MousePreferencesUbuntu8.04.1.png
--
Mouse pointer selection has become confusing under Gnome 2.22.3 under hardy
This is a mouse preferences dialog from Debian 4.0 - with Gnome 2.14.3.
This is similar to the dialog in earlier releases of Ubuntu.
** Attachment added: "Mouse preferences with pointer tab"
http://launchpadlibrarian.net/16910414/MousePreferencesDebian40.png
--
Mouse pointer selection has be
This is a screenshot of the Xcursor program from the gcursor package. It
displays the right stuff, but doesn't actually set the cursor, as
mentioned above and in Bug #138491.
** Attachment added: "Screenshot of Xcursor"
http://launchpadlibrarian.net/16910492/Screenshot-Xcursor%20Selector.png
-
I just confirmed that the same behavior occurs with Fedora 8, with the
same version of Gnome. So this is a Gnome 2.22.3 issue.
--
Mouse pointer selection has become confusing under Gnome 2.22.3 under hardy
https://bugs.launchpad.net/bugs/259195
You received this bug notification because you are a
1 - 100 of 909 matches
Mail list logo
