[Ubuntu-x-swat] [Bug 2038857] Re: Mantic Daily Text Editor Crashed Xorg
Note: When I was looking for changed/modified files, that was related to: https://answers.launchpad.net/ubuntu/+source/subiquity/+question/708132, which is still unanswered... -- 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/2038857 Title: Mantic Daily Text Editor Crashed Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2038857/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2038857] [NEW] Mantic Daily Text Editor Crashed Xorg
Public bug reported:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and had
no way to navigate to folders... Selected menu in top bar of editor...
Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer restarted.
Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 17:58:20 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
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/2038857
Title:
Mantic Daily Text Editor Crashed Xorg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2038857/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 902636] [NEW] missing xserver-xorg-video-nv
Public bug reported: xserver-xorg-video-nv is in the repo's thru Natty. Then is not found in the repo's of Oneiric and Precise. If this package has been replced by another, there is no indication of this at Debian or X.org. On nvidia user's of Onieric and Precise(dev), this throws an error in their Xorg logs that :nv cannot be found. They tried to install this package to correct that error, but agian not found. On my search through the repo's they would use, not found -and- the trail of that package seemed to have stopped at Natty. Not a problem for me (personally), but for the users I support in the Ubuntu Installations Updates Forum ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.1.0-1.1-generic 3.1.0-rc10 Uname: Linux 3.1.0-1-generic i686 .tmp.unity.support.test.1: ApportVersion: 1.26-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Dec 10 12:16:57 2011 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.1.6, 3.1.0-1-generic, i686: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111010) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet MachineType: innotek GmbH VirtualBox ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-generic root=UUID=c0652f22-b55a-4b00-bdec-85aac3b1c29f ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu7 version.libdrm2: libdrm2 2.4.27-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xserver-xorg-video-nv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise regression single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nv in Ubuntu. https://bugs.launchpad.net/bugs/902636 Title: missing xserver-xorg-video-nv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/902636/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 902636] Re: missing xserver-xorg-video-nv
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nv in Ubuntu. https://bugs.launchpad.net/bugs/902636 Title: missing xserver-xorg-video-nv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/902636/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 902636] Re: missing xserver-xorg-video-nv
Here is one of the user's xorg log. ** Attachment added: Users Xorg.0,log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/902636/+attachment/2627374/+files/Bub.Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nv in Ubuntu. https://bugs.launchpad.net/bugs/902636 Title: missing xserver-xorg-video-nv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/902636/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 33075] Re: Dell Inspiron 8200 Nvidia proprietary driver causes display errors (vertical lines on the right, and mirror effect on the bottom)[Workaround Available]
Just saw this bug while researching another problem... Reference the question in #17, I recommend to others both the get-edid of package read-edid to get the EDID of a display using the coomand line... get-edid edid1.bin ...or if they can get gnome to display, using nvidia-settings to generate it (in NVidia XServer Settings Device Display Acquire EDID ) Current problem / limitation) with get-edid is that it will only read the first display and not of any multilples beyond that. The author of the read-edid ipackage s working on expanding that. nvidia- settings will get the EDID of displays past the first, but needs to be running in gnome to be able to run. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/33075 Title: Dell Inspiron 8200 Nvidia proprietary driver causes display errors (vertical lines on the right, and mirror effect on the bottom)[Workaround Available] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.15/+bug/33075/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Un-Identified Process causes Purple screen or Black Screen on GDM startup.
** Summary changed: - Xorg's HAL causes Purple screen or Black Screen on GDM startup. + Un-Identified Process causes Purple screen or Black Screen on GDM startup. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Un-Identified Process causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Xorg's HAL causes Purple screen or Black Screen on GDM startup.
After talking with a lot of people since filing this and seeing that triage was going in the strange directions with this problem... I spent a lot of time doing more homework and research. I spent a lot of time on IRC # grub yesterday talking with a few of their dev's and support's. I followed their advice and... I guess we'll see where this goes: GNU GRUB - Bugs: bug #33318: Unknown process in grub 1.99~rc1 is setting and passing invalid graphics data to linux kernel and Xorg. https://savannah.gnu.org/bugs/index.php?33318 You should now be able to tie this bug (LP Bug #781445) to that Upstream Bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Xorg's HAL causes Purple screen or Black Screen on GDM startup.
Adding GRUB_GFXPAYLOAD=text to /etc/default/grub tries to over-ride the variable set gfxpayload=$linux_gfx_mode in 10_linux where GNU says that if set in the/etc/defau;t/grub : ## QUOTE ## GRUB_GFXPAYLOAD_LINUX' Set to `text' to force the Linux kernel to boot in normal text mode, `keep' to preserve the graphics mode set using `GRUB_GFXMODE', `WIDTHxHEIGHT'[`xDEPTH'] to set a particular graphics mode, or a sequence of these separated by commas or semicolons to try several modes in sequence. Depending on your kernel, your distribution, your graphics card, and the phase of the moon, note that using this option may cause GNU/Linux to suffer from various display problems, particularly during the early part of the boot sequence. If you have problems, set this option to `text' and GRUB will tell Linux to boot in normal text mode. ## END QUOTE ## Which later in 10_linux checks $linux_gfx_mode and if set to text tells the kernel not to boot graphics... (translation) This is a WORKAROUND telling the kernel not to use the GRUB_GFXMODE to set GFXTERM and not use KMS. This workaround, in essence does the same as 2 other workarounds of rolling back the kernel to 2.6.37.x or to roll back the version of Grub 1.99 to GNU Grub 1.98, in that they both them would ignor the GRUB_GFXMODE call.s All three of these workarounds circumvent around the present process by crippling it or ignoring it. A correct and closer Workaround is to set the parameters of GRUB_GFXMODE and pass them using KMS and the designed process... Which is working as a viable workaround out on the Support Forum. Setting the parameters of the video hardware and monitor manually as a workaround and having it work correctly, tells me the process does work, but it ia apparently s not being set up correctly with the right data. So the real question is: What is the process that VBE is using to query hardware when GRUB_GFXMODE is set auto? HAL? VBEPROBE / VBEINFO? Then we can check what in that process is passing bad parm's or locking up hardware. Whatever this process IS. this does seem to be where this problem seems to begin. If you leave this as saying that is the fix. then you are saying that GNU Grub 1.99, the Linux 2.6.38.x series kernel and Xorg X11R7.6 are all broke by not using the process at all. Anyone of these are all upstream, but this all affects Ubuntu (us). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Xorg's HAL causes Purple screen or Black Screen on GDM startup.
Like I said. I don't have this problem on this box or my 4 other's. I do have other 2 test boxs that are currently running Oneiric Ocelot 11.10 that I could pull down to reinstall 11.04 and recreate this problem with various hardware (Intel or AMD CPU's; nvidia, ati or intel video chipsets)... Or just look out on the support forum = there's no shortage of data. As for the comment that HAL is no longer used by the xorg.conf... My xorg.conf says it is. Is it lying to me again? (attached0 Next and included in this issue is the Sandy Bridge chipsets (Dell Alienware) where the y also have NVidia SLI's or ATI Xfire's... The query process is seeing the Sandy Bridge video modes, by not going further the the other chipsets to return their data. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Xorg's HAL causes Purple screen or Black Screen on GDM startup.
I re-read edited): Timo Aaltonen wrote 14 hours ago: #4 If you need to add GRUB_GFXPAYLOAD=text to /etc/default/grub, then it's a kernel bug. As explained above-- If you manually set the variable of GRUB_GFXPAYLOAD or GFXMODE and it works... then it does not seem to be a kernel bug. Manually setting those variables and passing to the kernel verifies that the process at the kernel is working as designed. What it does point out is that the process is broken before that... Somewhere in GRUB, where it is trying to query the hardware and passing invalid data to set a mode. Manually setting that mode (GFXMODE) bypasses that process. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Xorg's HAL causes Purple screen or Black Screen on GDM startup.
Got sidetracked,- It causes a few different problems, but shares a common cause: Not being able to find and sett a valid graphics mode. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] Re: Xorg's HAL causes Purple screen or Black Screen on GDM startup.
@Bugbot- This is not an nVidia thing. The happens with nVidia, ATI Radeon, i915, Sandy Bridge, etc. This causes an nVidia chip instlled consurrent with a Sandy Bridge no to be quesried and return it's mode data. Basically, it seems to be causing graphics modes data to be returned in correctly, so that an invalid graphics mode is set. Administratively-- If you would have read ths bug report thoroughly / carefully and the referred question to launchpad about how to report it... I DON'T PERSONALLY HAVE THIS PROBLEM! Which is why I asked all over about how to report this and where to report this, before I did report this, so that ithis problem would not be marked iinvalid. Remember, I've been helping people solve this problem. Instead of having one PC worth of data, I have 100's of PC's worth solved and most share a common problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781445] [NEW] Xorg's HAL causes Purple screen or Black Screen on GDM startup.
Public bug reported: Binary package hint: xorg Refered by: https://answers.launchpad.net/ubuntu/+source/rhythmbox/+question/157114 Reference: Since implementation of KMS technologies at Ubuntu version 10.04, transitions have occurred where the graphics is first set and how, via: Kernel mode-setting (KMS) shifts responsibility for selecting and setting up the graphics mode from X.org to the kernel. When X.org is started, it then detects and uses the mode without any further mode changes. This promises to make booting faster, more graphical, and less flickery. From what I can figure out, most of this started with 10.04 when they started implementing KMS technology: (Simplistic explanation of graphical changes) - 9.10 graphics modes were dealt with in xorg and the video drivers. Grub2 introduced. - 10.04 introduces KMS, (kernel mode switching) where graphics modes were set in the kernel and passed to xorg. - 10.10 has some more changes with this... Trying to find and set the graphics modes and pass it to Xorg. - Natty and Grub 1.99 have ingrained changes tied to KMS. Grub tries to find and set the graphics using HAL from Xorg, which it then passes to the kernel, which then passes in it to Xorg. That's why we now have the graphics changes happening as soon as the Grub Menu... Most of the people that I've helped (Ubuntu Support Forum- Installations and Updates) correct their blank screen problems with Natty have been by Bypassing the GFXMODE=auto default setting, a process that starts and uses data returned by HAL. The main fix explicitely sets the GFXMODE=WIDTHxHEIGHTxDEPTH parameters of a mode that their graphics hardware supports. This fix bypasses HAL and it's query/mode set functions. Other fixes are via setting the scan rate of a monitor, which is also sopposed to be a a function of HAL. (ETC.) That first fix applies setting the 3 common parameters of GFXMODE. That third parameter is buried in the documentation I did find from GNU and Xorg... There have been a few other instances where there was some other things going on or the current kernel did not support or lost graphics support for... (The kernel in proposed fixes a lot of those) But the majority was just setting an initial mode. I have asked around and no-one wants to really point fingers, but this is a problem. No one wants talk about this new relationships between grub, the kernel and xorg to supply needed info that may come up with other work-arounds. I've asked in many places at Ubuntu and Conical (where I thought I could get some answers) about any kind of documentations... but all have been ignored. I know that kernel boot parameters are a part of it. I know that Grub 1.99's GFXMODE and GFXTERM are a part of it. I know thiat HAL and subsequently Xorg is a part of this. What I put together so far is in this sticky, which is still evolving: http://ubuntuforums.org/showthread.php?t=1743535 I know that the default of GFXMODE=auto is causing a lot of blank screens as it tries modes until it lands on one that deos not return an error code... even though that instance may be invalid or out-of-range. On some people I've helped with this, rolling back the kerenl to 2.6.37.x makes their problems disappear. You say rolling the Grub version back to 1.98 works. I'm thinking that maybe those 2 items might be doing the same thing by not passing an invalid mode or parameter. Could it? Along those line, the same fixes happen if they install the propose kernel 2.6.38.9 in the proposed repo or the 2.6.39.0 in the mainline. Which those might have fixed ported in for the bugs that have been filed on this(?) In Natty Norwhahl 11.04, HAL affects Xorg and the xorg.conf: # commented out by update-manager, HAL is now used and auto-detects devices Querying video hardware usinf xrandr: hal.1: read hal dataprocess 2951: arguments to dbus_move_error() were incorrect, assertion (dest) == NULL || !dbus_error_is_set ((dest)) failed in file dbus-errors.c line 280. This is normally a bug in some application using the D-Bus library. libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files HAL problems now seem to affect GNU Grub 1.99, Linux kernel and Xorg. This really affect this new distribution of Ubuntu (11.04) which heavily relies on this and is cauaing many problems. It no only affects the Xsession startup, but also it's shutdown. Summary: Normal users should not have to be highly skilled techies to manually bypass a broken part of a system to make a released distribution work during an install or distribution upgrade! ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version:
[Ubuntu-x-swat] [Bug 781445] Re: Yorg's HAL causes Purple screen or Black Screen on GDM startup.
** Summary changed: - Yorg's HAL causes Purple screen or Black Screen on GDM startup. + Xorg's HAL causes Purple screen or Black Screen on GDM startup. -- 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/781445 Title: Xorg's HAL causes Purple screen or Black Screen on GDM startup. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 772207] Re: version 173.14.30 is buggy for GeForce FX 5200
*** This bug is a duplicate of bug 762478 *** https://bugs.launchpad.net/bugs/762478 Wait a minute... This crossrference here says to be in error: Remember: This is a duplicate of Bug 762478 ( https://bugs.launchpad.net/ubuntu/+source/unity/+bug/762478) How is this Bug a duplicate of [nouveau] No icons shown in unity launcher, which is a compiz problem right? Nothing there seems to reference this graphics driver being installed but not being used. Rather, Is this Bug a duplicate of another Not-yet-referenced BUG? Just curious. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu. https://bugs.launchpad.net/bugs/772207 Title: version 173.14.30 is buggy for GeForce FX 5200 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
