> /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb7161000+0x3713b7)
>    [0xb74d23b7]

Thanks for the report. We are sorry that we cannot help you with your problem, but we are not able to support binary-only drivers. If you would be able to reproduce this issue using only open source software, please, reopen this bug with the additional information, but in meantime I have no choice than to close this bug as CANTFIX (because we really cannot fix it).

The open source 'nouveau' driver (in package xorg-x11-drv-nouveau) is the recommended alternative for users of Nvidia graphic chips.  It is used by default in Fedora 11 and later if you remove any customizations that explicitly set the video driver.  The older "nv" driver may be needed in some cases.  It is also available in older Fedora releases.  Install the packages xorg-x11-drv-nouveau or xorg-x11-drv-nv and override the X server's default choice if necessary.  See https://fedoraproject.org/wiki/Features/NouveauAsDefault for more information.

If you used a non-packaged version of the driver from the Nvidia website please clean your system from additional libraries and software it installed. For users who are experiencing problems installing, configuring, or using the unsupported 3rd party proprietary "nvidia" video driver, Nvidia provides indirect customer support via an online web based support forum.  Nvidia monitors these web forums for commonly reported problems and passes them on to Nvidia engineers for investigation.  Once they've isolated a particular problem, it is often fixed in a future video driver update.

The NVNews Nvidia Linux driver forum is located at:

	http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14

Once you have reported this issue in the Nvidia web forums, others who may have experienced the particular problem may be able to assist.  If there is a real bug occuring, Nvidia will be able to determine this, and will likely resolve the issue in a future driver update for the operating system releases that they officially support.

While we does not support the proprietary nvidia driver, users requiring technical support may also find the various X.Org, XFree86, and Red Hat/Fedora mailing lists helpful in finding assistance:

X.Org mailing lists:
	http://www.freedesktop.org/XOrg/XorgMailingLists

XFree86 mailing lists:
	http://www.xfree86.org/sos/lists.html

Red Hat/Fedora mailing lists:
	https://listman.redhat.com/mailman/listinfo

Other problems are made worse with the nouveau driver!

If you don't want to help people with problems then don't bother, but there was no problem with Fedora 10 (with the same driver) and it is only in Fedora 12 that problems have surfaced. I am 100% convinced that it has nothing whatsoever to do with the video driver, but may be connected with the keyboard driver, as recent feedback from other sources on the net indicate.

I am sorry, but you are just putting petty politics before common sense.

(In reply to comment #2)
> Other problems are made worse with the nouveau driver!

yes, but we are working on it and it is getting better every release. As I wrote in comment 1, if you are able to reproduce this problem with fully-nvidia-clean computer (see https://fedoraproject.org/wiki/Xorg/3rd_Party_Video_Drivers for more information), then please reopen this bug with additional information.

> I am sorry, but you are just putting petty politics before common sense.  

No, it is not petty politics. I personally cannot care less what driver people use for their pleasure, but we really cannot debug nvidia driver, and there are many many instances when (not only) Xorg server crashes mysteriously with it. Moreover, there are rumours (I have never installed nvidia driver myself, so that's just what I hear from the second hand) that nvidia driver doesn't deal well with the current kernels in F12.

To be completely forthright, I can completely understand that somebody who needs high-end graphics on nvidia has to use their binary-only driver. However, this solution is not free of problems ... the price you pay for it is that we cannot help you if it doesn't work (aside from other issues, as you have to be careful about upgrading your kernel).

OK. After much work I have a working machine with nouveau installed!
My screen in a mess, because I can't get better than 1024x768 resolution (I was using 1920x1200 before) but it will do just for this report.

Firstly I found a similar report here:

https://bugs.freedesktop.org/show_bug.cgi?id=24487

This was on a system with no nvidia card at all.

My previous F10 system (Xorg 1.5.3) was fine. Since upgrading to Fedora 12 (Xorg 1.7.1) the problem has shown itself.

Now, with nouveau, I don't get a backtrace, but the server restarts itself. The only info of note is from the system messages file:

Dec  9 23:27:09 linux kernel: hub 3-2:1.0: USB hub found
Dec  9 23:27:09 linux kernel: hub 3-2:1.0: 4 ports detected
Dec  9 23:27:09 linux kernel: usb 3-2.3: new low speed USB device using uhci_hcd and address 9
Dec  9 23:27:09 linux kernel: usb 3-2.3: New USB device found, idVendor=046d, idProduct=c03d
Dec  9 23:27:09 linux kernel: usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec  9 23:27:09 linux kernel: usb 3-2.3: Product: USB-PS/2 Optical Mouse
Dec  9 23:27:09 linux kernel: usb 3-2.3: Manufacturer: Logitech
Dec  9 23:27:09 linux kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Dec  9 23:27:09 linux kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2.3/3-2.3:1.0/input/input9
Dec  9 23:27:09 linux kernel: generic-usb 0003:046D:C03D.0007: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-2.3/input0
Dec  9 23:27:09 linux kernel: usb 3-2.4: new low speed USB device using uhci_hcd and address 10
Dec  9 23:27:10 linux kernel: usb 3-2.4: New USB device found, idVendor=04b4, idProduct=0101
Dec  9 23:27:10 linux kernel: usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec  9 23:27:10 linux kernel: usb 3-2.4: Product: PS/2 Keyboard & Mouse
Dec  9 23:27:10 linux kernel: usb 3-2.4: Manufacturer: Cypress
Dec  9 23:27:10 linux kernel: usb 3-2.4: configuration #1 chosen from 1 choice
Dec  9 23:27:10 linux kernel: input: Cypress PS/2 Keyboard & Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2.4/3-2.4:1.0/input/input10
Dec  9 23:27:10 linux kernel: generic-usb 0003:04B4:0101.0008: input,hidraw1: USB HID v1.00 Keyboard [Cypress PS/2 Keyboard & Mouse] on usb-0000:00:1d.1-2.4/input0
Dec  9 23:27:10 linux kernel: input: Cypress PS/2 Keyboard & Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2.4/3-2.4:1.1/input/input11
Dec  9 23:27:10 linux kernel: generic-usb 0003:04B4:0101.0009: input,hidraw2: USB HID v1.00 Mouse [Cypress PS/2 Keyboard & Mouse] on usb-0000:00:1d.1-2.4/input1
Dec  9 23:27:10 linux kernel: Process 4930(Xorg) has RLIMIT_CORE set to 0
Dec  9 23:27:10 linux kernel: Aborting core

Well, finally a backtrace!

This time it crashed, unlike the restart that happened last time.

(**) Cypress PS/2 Keyboard & Mouse: (accel) acceleration profile 0
(II) Cypress PS/2 Keyboard & Mouse: initialized for relative axes.
(II) config/hal: removing device Logitech USB-PS/2 Optical Mouse
(II) Logitech USB-PS/2 Optical Mouse: Close
(II) UnloadModule: "evdev"
(II) config/hal: removing device Cypress PS/2 Keyboard & Mouse
(II) Cypress PS/2 Keyboard & Mouse: Close
(II) UnloadModule: "evdev"
(II) config/hal: removing device Cypress PS/2 Keyboard & Mouse
(II) Cypress PS/2 Keyboard & Mouse: Close
(II) UnloadModule: "evdev"
(II) config/hal: Adding input device Logitech USB-PS/2 Optical Mouse
(**) Logitech USB-PS/2 Optical Mouse: always reports core events
(**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
(II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
(II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
(II) Logitech USB-PS/2 Optical Mouse: Found relative axes
(II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
(II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
(**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
(**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
(**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
(II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.

Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e587c]
1: /usr/bin/Xorg (0x8048000+0x5eb66) [0x80a6b66]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
3: /lib/libc.so.6 (0x43020000+0x70ebd) [0x43090ebd]
4: /lib/libc.so.6 (__libc_malloc+0x5e) [0x430921fe]
5: /usr/bin/Xorg (Xalloc+0x2a) [0x80a770a]
6: /usr/bin/Xorg (0x8048000+0xecb06) [0x8134b06]
7: /usr/bin/Xorg (0x8048000+0xed40b) [0x813540b]
8: /usr/bin/Xorg (0x8048000+0x261f7) [0x806e1f7]
9: /usr/bin/Xorg (0x8048000+0x1a8c5) [0x80628c5]
10: /lib/libc.so.6 (__libc_start_main+0xe6) [0x43036bb6]
11: /usr/bin/Xorg (0x8048000+0x1a4b1) [0x80624b1]
Segmentation fault at address 0x4000088

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support 
         at http://bodhi.fedoraproject.org/
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Thank you very much. Of course, reopening.

In all that talk about nvidia I forgot to ask you about the most basic stuff. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Don't bother with the logs, closing as duplicate of bug 545834

*** This bug has been marked as a duplicate of bug 545834 ***

Created attachment 389239 [details]
Fedora 12 and a KVM Switch my Iogear KVM Bug report 02-05-10.odt

I have an IOGear MiniView USB (G-CS104U) 4-port KVM Switch that I have been using with Fedora,  since Fedora (Blag) 5 and have never had any problems until now, with Fedora 12. This KVM Switch works well with every operating system I have Tried from Win 3.1, 95,98, Me, 2000, Win XP and Vista. Along with Other Linux Distro's such as DSL, Puppy, Dabian, Blag 5 to 9. Basically I have used this switch with over 20 different Linux Distro's for the last 5 years and never had any problems with the systems locking up because of the switch. I may have never even figured out what was locking up Fedora 12 if it weren't for these posts on the Fedora Forum Fedora 12 and a KVM Switch, http://forums.fedoraforum.org/showthread.php?t=235138 I am now running Fedora 12 Constantine on an Intel Core 2 1.8ghz with Intel On-board Video, with 1gb of System Memory (see attached screen shot for details at Bug 545231). 

 
The only problems related to the USB KVM I have ever experienced was on older machines. And I am able to fix this by just leaving a PS2 Mouse and or Keyboard Plugged into the machine as a backup way to control the machine. Usually if I leave the KVM set on the machine long enough, the USB hooks back up and starts working again. But this work around method Does Not work with Fedora 12. The problem even seemed to get worse. I tried both PS2 and USB Mouse and Keyboards as a Work around to no avail. I have only ever had this problem with Older Bios in machines pre year 2000. This machine has a brand new mother board, that I just put in last month. I also had Fedora 12 running on an Intel P4 machine with a 64mb Nvidia Video Card and 1gb of Ram. It had had the same locking up problem. Also, the P4 was logging out or crashing back into the log in screen (the Gateway GT5408 does this some to, but seems better after a few updates). Probably crashing, because all open windows are always lost and had to be recovered when the programs were reopened. This Problem makes Fedora 12 Unusable for me, since I use 3 to 4 computers at a time every day to do my work. I hope you guys can figure this one out... I read allot on the Fedora Forum about whether or not it is a problem with the Nvidia Drivers, which I haven't used on the Nvidia Card at all. After 2 months of building up that system and working with you guys on other ABRT and SElinux Bugs, that system crashed and the files on that HD are not accessible now. So I will have to reformat it. Even though I have worked on Operating Systems, fixing and testing them for the last 10 years.... I'm not a Coder so I can't figure this out for my self. But I think these guys are right about the problem being with the USB Code in Fedora 12. What else could it be? I love the new features in Fedora 12 and hate to go back wards. But I can't work with a system that constantly locks up. So, just to show MS, what were made of... lets fix this!;) 

Thanks,

Don

Created attachment 389240 [details]
Fedora-12-Gateway-GT5408-System-info.png

Fedora-12-Gateway-GT5408-System-info.png is the image mentioned in my comment... I have an IOGear MiniView USB (G-CS104U) 4-port KVM Switch that I have been using with Fedora,  since Fedora (Blag) 5 and have never had any problems until now, with Fedora 12. This KVM Switch works well with every operating system I have Tried from Win 3.1, 95,98, Me, 2000, Win XP and Vista. Along with Other Linux Distro's such as DSL, Puppy, Dabian, Blag 5 to 9. Basically I have used this switch with over 20 different Linux Distro's for the last 5 years and never had any problems with the systems locking up because of the switch. I may have never even figured out what was locking up Fedora 12 if it weren't for these posts on the Fedora Forum Fedora 12 and a KVM Switch...