Attachment 317231 Details for Bug 235018 – testing attachment

testing attachment

getLogConf.txt (text/plain), 10.14 KB, created by Matěj Cepl on 2008-09-19 19:50:55 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Matěj Cepl

Created: 2008-09-19 19:50:55 UTC

Size: 10.14 KB

patch

obsolete

>Ask krh about the following bugs:
>
>200271    	  	   	 med   	 med   	 All   	 krh@redhat.com   	 ASSI   	   	 Takes too long to switch workspaces
>200272 			med 	med 	All 	krh@redhat.com 	NEED 		Loses maximised windows' states when restarted
>200273 			med 	med 	All 	krh@redhat.com 	NEED 		Windows are allowed to stay on top of the panel
>200274 			med 	med 	All 	krh@redhat.com 	NEED 		Looks like there's more windows than in reality
>200279 		
>
>---
>
>keywords in Status Whiteboard:
>nodedup
>thunderbird-spellchecker
>2Bupstreamed
>FF3Reproducable
>nonFF3Reproducable
>unresponsiveJavaScript
>checkRelevance
>------
>
>We haven't got any reply to the last question about reproducability of the bug with Fedora Core 6, Fedora 7, or Fedora devel. Mass closing this bug, so if you have new information that would help us fix this bug, please reopen it with the additional information.
>
>------
>
>Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
>
>Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
>
>Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
>
>We will review this issue again once you've had a chance to attach this information.
>
>Thanks in advance.
>
>----
>
>Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
>
>Please install firefox-debuginfo; in order to do this you have to enable -debuginfo repository.
>
>	yum install --enablerepo=\*debuginfo firefox-debuginfo
>
>(if you use x86_64 firefox, install firefox-debuginfo.x86_64 package).
>
>Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run
>
>	(gdb) thread apply all backtrace
>
>This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.
>
>We will review this issue again once you've had a chance to attach this information.
>
>Thanks in advance.
>
>----
>
>If this issue turns out to still be reproduceable in the latest updates for this Fedora Core release, please file a bug report in the Gnome bugzilla located at http://bugzilla.gnome.org in the "Â§Â§Â§" product.
>
>Once you've filed your bug report upstream, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
>
>Setting status to NEEDINFO, and awaiting upstream bug report URL for tracking.
>
>Thanks in advance.
>
>-----
>
>Fedora Core 5 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report.  If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX.
>
>Setting status to NEEDINFO, and awaiting information from the reporter.
>
>Thanks in advance.
>
>-----
>
>Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
>test releases. We're cleaning up the bug database and making sure important bug
>reports filed against these test releases don't get lost. It would be helpful if
>you could test this issue with a released version of Fedora or with the latest
>development / test release. Thanks for your help and for your patience.
>
>[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
>myself to the CC list for each bug, so I'll see any comments you make after this
>and do my best to make sure every issue gets proper attention.]
>
>-----
>
>Since this bugzilla report was filed, there have been several updates, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their distribution available.
>
>Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
>
>If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
>
>--
>
>Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
>
>--
>
>Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
>
>Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
>
>Closing as INSUFFICIENT_DATA.
>
>--
>
>If this issue turns out to still be reproduceable in the latest updates for this Fedora Core release, please file a bug report in the the upstream bugzilla located at http://bugzilla.mozilla.org in the particular component.
>
>Once you've filed your bug report to the upstream bugzilla, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
>
>Setting status to "NEEDINFO", and awaiting upstream bug report URL for tracking.
>
>Thanks in advance.
>
>--
>
>We found that this bug has been already registered in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=Â§Â§Â§) and believe that it is more appropriate to let it be resolved upstream.
>
>Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
>
>Thank you for the bug report.
>
>--
>
>Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
>
>Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
>
>Closing as INSUFFICIENT_DATA.
>
>--
>
>No response from reporter, no activity for a long time, closing as INSUFFICIENT_DATA. If anyone has some information on this bug, please, reopen with additional data.
>
>--
>
>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).
>
>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 Red Hat does not support the proprietary nvidia driver, users requiring technical support may also find the various X.Org, XFree86, and Red Hat 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 mailing lists:
>    https://listman.redhat.com/mailman/listinfo
>
>-----
>
>Closing per reporter's request. Please, reopen if you are able to reproduce this with currently supported distribution.
>
>-----
>
>Just note from your friendly bug triager -- I think, that the correct status of this bug according to https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow is ASSIGNED. Please, correct this bug to the right state, if I am wrong.
>
>-----
>
>In F9, input devices are hotplugged with the evdev driver. The list of 
>devices is provided by HAL, and any device using evdev will not send to 
>/dev/input/mice.
>
>If a InputDevice is configured for /dev/input/mice, it won't generate 
>any event if all mice are hotplugged through HAL. This usually looks 
>like the configuration is ignored or lost.
>
>The two options to fix this is:
>- Add Option "AutoAddDevices" "off" to the ServerLayout. This disables 
>input device hotplugging alltogether and prevents evdev from taking over.
>- Change the InputDevice section to use evdev as driver and specify the 
>device file as /dev/input/by-id/... or /dev/input/by-path/... 
>/dev/input/event0 is valid too, but those numbers may change on reboot.
>If you choose this option, you may have to specify multiple InputDevice 
>sections since evdev does not have an equivalent to /dev/input/mice.
>
>Beware that some option that are supported in the mouse driver may not 
>be available in the evdev driver. If so, you can file a feature request 
>with upstream at http://bugs.freedesktop.org/show_bug.cgi?id=16699.
>
>---
>peter.hutterer@redhat.com

Actions: View

Attachments on bug 235018: 317231