abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: nautilus component: nautilus crash_function: nautilus_icon_container_search_preedit_changed executable: /usr/bin/nautilus kernel: 2.6.35.6-48.fc14.x86_64 package: nautilus-2.32.1-1.fc14 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290161612 uid: 500 How to reproduce ----- 1.a 2. 3.
Created attachment 461685 [details] File: backtrace
*** Bug 655308 has been marked as a duplicate of this bug. ***
*** Bug 654477 has been marked as a duplicate of this bug. ***
*** Bug 654469 has been marked as a duplicate of this bug. ***
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Opened a folder in nautilus containing Inkscape .svg and also .png files 2. Double clicked on images to view them 3. Crash Comment ----- There were some fonts and linked bitmaps missing in the SVG files I was viewing in nautilus, so double clicking on the .svg files resulted in overflowing text, etc.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. While using Inkscape Comment ----- N/A
*** Bug 655370 has been marked as a duplicate of this bug. ***
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I pressed the right control button while pressing the l button. 2. (my right control is set as a compose key) 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Not sure. Was mucking around with external monitor attached to my laptop dock (output selected as "Twinview" in nvidia settings, so it doubles the resolution of each workspace), moving my mouse. Was about to disable the external monitor using nvidia-settings. Comment ----- See above. Was in a hurry and did not have time to collect more specifics.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I opened teh broswer nautilus 2.I run a video whith vlc 3.I closed the vlc a after 4.i clos the nautilus and appear the messanger about the falling of pakage of nautilus
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I didn't even notice this crash, so I don't know how to reproduce... 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. did nothing special 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Pressed the power button. 2. Clicked "shut-down" 3. reboot computer and noticed the crash report.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. login 2. update 3. logout 4. login 5. crash Comment ----- You should really expand the "Errors UUID" stuff to actual code fuction ID's, it should be a last case scenario to work with the user to figure out what's going wrong. It's bad business, it's not the users fault the software crashed! Either way, the dumps should provide enough information and if not, then request more information from the users, attempt to differenciate the information to eliminate user customizations and work from there. Older days: fix it yourself Old days: ask the customer who posts a bunch of conjecture in forums and hope someone can actually reach out and figure out what the problem really is and not what the user thinks it is... days: Add build uuid to identify various versions of software involved in the crash today: use uuid, ask the customer see a pattern? future: use the uuid to identify the build, use codes to identify the error. use the errors in future builds to be thrown with the error... think of the opportunities to being able to identify, upon submission, the error type/class... as well as the build id. $0.02
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. closing with extra panel open 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Was using Divergence theme from gnome-look.org 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Closed nautalis window which was open with smb:// shared drive active. There was one other window open, which had local directories visible.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I closed a nautilus window with the "X" in the corner 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Shutting Down the Notebook 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 1 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Don't know. Didn't notice it happen. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I have no idea. Abrtd just triggered in the middle of work. I did not even had a nautilus window open.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I had a folder open in a nautilus window 2.I clicked on the "X" icon on top right corner of the window 3.it crashed - I likely wouldn't have noticed if Automatic Bug Reporting Tool wasn't kicking in. Comment ----- I tried opening and closing the window again, nothing happened. The one which crashed had been open some hours in background, not sure if that's relevant.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crash was reported after returning from suspend to ram 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.i was seeing a email 2.and the crash happens 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.1 2.2 3.3
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open Home 2. Browse to Pictures 3. Open folder containing photos
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. <
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don't know how to reproduce it. I don't remember which Nautilus windows were open when it was triggered.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I don't now 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. no idea 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. accidentally hit a random key while hovering (mouse) over a link to a SAN (CIFS) mounted dir 2. 3. Comment ----- Unable to deliberately reproduce at this time but will add info as soon as I can reliably recreate it.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. searching files 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Was using nautilus to browse files and folders 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.idunno 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. View some ttf files in nautilus 2. 3. Comment ----- I was viewing some TTF files under nautilus
*** Bug 656288 has been marked as a duplicate of this bug. ***
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. i work in firefox online 2. nauti was open whit a ssh login 3. my DSL line crashes Comment ----- after re-connect whit firefox crashes nautilus....
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Can't say how to reproduce this...
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Browsing files using keyboard navigation to type folder names 2. Nautilus froze (blacken windows forever) when pressing enter 3. Killed it with killall 4. Started a new nautilus windows and enter in a sub-directory when it crashed
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start Gnome 2.start Firefox 3.crash Comment ----- Also crash kernel
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I am really so novice to detect that 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.power on te computer 2.use 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.It just crashed, no clue why. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.try to type some keys so to do 'quick find' in nautilus to list my file 2.try to right click on the highlighted file 3.crash
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.was using nautilus, started from bash 2. # nautilus 3. Close nautilus, crash
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.not sure how it crashed. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- FYI... PCBSD with KDE asks if you know what you were doing when the crash occurred...and gives the user a "Yes" or "No" option... no takes you to the submit without typing in this info... but then again too.. if you're trying to deter users from actually submitting accurate numbers of crashes... then... well.... I guess forcing them to type these silly messages in is a good idea!!! Comment ----- Thanks for the opportunity to add more crap on the redhat bugzilla servers... if I type enough I may just increase the server storage needs by .0000001%... woot woot!!... Either way, I'm still thoroughly against this forced "What did YOU do to crash YOUR system..." crap. bugs is bugs... just collect as much data as you can from the system.. it doesn't have an opinion or a misconception about what may or may not have happened... and, really.. for transparency's sake.. I'd like to see the stats for how many bug reports have useful info, then and now (as confirmed by the developer that clicks that capture button that reads "Yep, user bob's comments and steps to reproduce really nailed the bug down fixed it 37.8% faster!")... and.... maybe a survey of developers to see how many bugs need to be closed!solved because of inaccurate dump data and nothing from the user as opposed bugs closed&solved because of user info.... I'm guessing the dumps provide the needed info, and if not... then it should be fixed in the code... you can't fix every single scenario on everybody's system... but trying to force users... trying to help the distro... to write down what they did ...it's detrimental, or maybe just mental.. It's what I used to have to do in 1996, ping a user via email... ask them what they were doing when they were online... cause of some error in a log or a crashed process... ugh.. by the time the buddy list developer said he needed a bigger database server and larger system with more processors... I laughed at him and said "do you know what you're doing?" cause his code was crashing and his answer was always the "users have odd setups, ping them to find out" or "I need more hardware"... how about start putting more catches in the code to actually describe what the code was doing.. or attempting to do when it crashed... you know... like "I, nautilus was attempting to violate the 1st rule by harming a human.. or referencing a bad pointer in memory.. address...blah... etc"... you get the point.. if you're not throwing errors in your functions, or don't have a function to handle errors in your code.. .you'll only get debug and memory dumps and hope the last few lines of code were captured.... Think of it this way... if you were to read somebody else's logging and troubleshoot errors... what would you need to know, to know what the code was doing when it crashed? without throwing it into debug (developers love debug, it's great for coding, sucks for supporting, not all operations has debuggers or memory dump readers...etc..or root access for that matter) and work on a way to make your code smarter, more chatty and easier to catch bugs... Worked with many smart developers that weren't arrogant and they were willing to write more code to better log and catch functions... think of this way.. if your attempting to read a file be ready to catch the file not found, the file pointer broken, the file locked...etc not just "I couldn't do it". The way I think of it (Operations background) about 99% of code is about 80% ready for production even when it's considered "gold". I say this only because most developers build code for use, not support (nothing wrong with that) but they use tools that not everybody uses, or should use for that matter to troubleshoot code... This leads to somebody having to run around and capture all of that missing stuff about what was happening, what was running, what build were they...etc.. one developer to one bug smasher... not one developer and 100 bug smashers to collect all of the data needed... anyway, in conclusion... make the code smarter, the abrt smarter, capture function details to know what something was doing, stop asking users for info and you can look at the humorous comments in bug reports to see, this wasn't a good idea... who's was it anyway? Zdenek? Jiri? $.02
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Close a Nautilus window 2. 3. Comment ----- In the same time I used the Software Update, so it can be related to this ...
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.closed nautilus file browser with 2 tabs open 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.click bob/Downloads 2.click tree node arrow to expand Downloads subfolders 3.crash
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No special steps 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Closed brasero Comment ----- List of open windows atm : Lotus notes 8.5.2 Google chrome xmms Oracle VM Virtual box
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I really do not know. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Don't remember or wasn't around at the time Comment ----- Honestly, I don't know how this happened. It occurred on a Sunday night and I was either not really paying attention or I wasn't at the machine when the crash was reported. I just now noticed the issue in ABRT so I'm posting for information purposes.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Closing a nautilus window to a remote SMB server
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Close nautilus-window 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I clicked on the top left hand close window icon on a directory window that had been up several hours. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I opened nautilus. 2. Go in a media-drawer (mainly .mp3-files) 3. deleted some .mp3-files 4. opened the trashcan, emptied the trashcan, close the trashcan 5. close nautilus and then the crash occured
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just finished Nautilus. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.A copy qhile I have many tab in nautilus on ssh, samba, etx4 and ntfs folders 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- nautilus crashed when I closed it.. first time that this happened. Comment ----- I had 2 tabs open ( /tmp/ and a network share (nfs connection) with some 50GB of data in it)
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Have two windows open? 2. Trigger the Scale Window Picker in compiz. 3. Close a nautilus window with middle click (you need the Scale Addons plugin for that).
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I believe it was when i was messing around with compiz 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Type a character for quick selection 2. Press enter on the seleted folder or files 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not sure 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. browsing a pdf file while downloadthemall firefox plugin is downloading files. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open nautilus 2. Press a character for quick selection 3. Press enter 4. nautilus crashes Comment ----- OS : Fedora 14 Linux Kernel 2.6.35.6-48.fc14.x86_64 CPU : Intel T7300 RAM : 2 GB
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I don't know 2. 3. Comment ----- I only noticed this the next day.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. open a folder, without thumbnails 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.update by PackageKit 2.log off as suggested by update 3.log on back Then found this crash signaled by abtrd Comment ----- tz
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.1 2. 3. Comment ----- Sorry I dont knw ow to reproduce it
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start nautilus 2.crash 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Multiple Nautilus windows were open. One window pointing to an SMB share, two pointing to two separate SFTP mounts on separate hosts. 2.No activity was being performed when system crash occurred. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.??? 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Closed nautilus 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crashed after closing/saving a file in OpenOffice 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. The crash happened a few hours after I updated the kernel.x86_64 0:2.6.35.9-64.fc14 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not really sure, just tried to close the window, and it crashed. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Only closed nautilus.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open Nautilus 2. Press a character for quick selection 3. Press enter
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open 3 nautilus windows. 2. Closed every single one of them, after modifying the names of some mp3 files. 3. When closing the third window, got nautilus crash report.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- yum update
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Close Nautilus
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No idea. 2. 3. Comment ----- Nautilus crashed while having only one window open, which wasn't even focused/on top. The window might have been of a remote SFTP folder (not sure, as I said the window was not focused, I was not looking at it, and it had been open for a while).
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I opened Firefox and pasted the following URL into the location bar : https://bugzilla.redhat.com/show_bug.cgi?id=655267 2.Browser crashed. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just closed Nautilus 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.open and then crash... as usual 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Did nothing special... 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Accessing an nfs directory over a wireless link
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I closed the Nautilus 2. 3.
nautilus-2.32.2-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/nautilus-2.32.2-1.fc14
nautilus-2.32.2-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update nautilus'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/nautilus-2.32.2-1.fc14
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. restart IBus input method framework 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.No clue 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Unknown. Happened in the background? One USB filesystem mounted. Comment ----- ABRT said the crash file was too large, which might be a secondary problem needing fixing.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. close firefox 2. close nautilus 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Received an email in thunderbird (IMAP server) with a SWF in attach 2. Save attachment to a location mounted in .gvfs 3. Attachment was saved corectly 4. crash notification from ABRT
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Tried to logout 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Instalado tema GTK2 com icones 2.Logo atualizacão do sistema 3.Network manager parou 4.Nautilus travou
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.1 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don not know why?
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. can't remember 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Display switching. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Instalé las primeras actualizaciones 2.Seleccioné reiniciar el equipo 3.e inmediatamente me dió este aviso. Comment ----- Me salió el aviso al reiniciar el equipo despues de instalar la primera actualizacion tras la instalación.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I don't really remember what caused this crash. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.unknown 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Ctrl + q
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. tried clicking on an icon in a nautilus window. This also killed gnome-panel 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Click the Eject-Icon next to an external hard drive in the "Places" window 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Connected a Canon 7D camera 2. Browsed one of the folders containing ~1000 pictures 3. Disconnected the camera Comment ----- It doesn't happen every time (has only happened twice in the last 6 months).
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Opened nautilus from desktop icon ; 2. not sure if it applies but before crash I was testing out vpnc and att vpn dialer configs. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. je ne sais pas 2. 3. Comment ----- je ne sais pas ce qui c'est passé et je ne sais pas comment le reproduire.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Downloaded http://live.gnome.org/GnomeMarketing/MarketingMaterial/Presentations?action=AttachFile&do=get&target=GNOMETemplate 2. Opened Nautilus and went to the Download folder 3. Clicked on the downloaded file 4. Crash
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. nothing special 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open nautilus 2. Type a file/folder's name for quick selection 3. Press 'Esc' to cancel
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. unmounted usb device
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.When I pressed ctrl+L key combination Nautilus had crashed. 2.I don't know how to reproduce it. 3. Comment ----- 1. When I pressed ctrl+L key combination Nautilus had crashed. 2. I don't know how to reproduce it. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.wait for the system about 6 hours. 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. crashes in vmware 7.1 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Pulsar "n" 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. www
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Exited from calibre 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. just press ctlr + c 2. 3. happened once in a lifetime
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Openning pictures with the Gimp 2. 3. Comment ----- Random crashes of X to login after openning multiple picture for editing, closing these and openning others.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I was just updating via yum then it crashed. Dropbox is installed Comment ----- Dropbox is installed
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.i just open it normal without any thing , just crash so nothing new i can add here 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.sorry, no idea... 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. too much time passed since it happened, I don't remember what was going on - sorry!
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Boot up 2. Log in 3. Comment ----- The crash was reported on login after a cold boot.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.upgrading the pc 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I closed about 6 Nautilus windows, and I believe just one of them crashed upon close Comment ----- I guess I would try opening a bunch of nautilus windows and then close them. It's also possible that nautilus was replaced in some yum update, while nautilus was running, and perhaps that's what confused it when it shut down.
nautilus-2.32.2-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.