Re: [Bug 1257058] Re: low graphics mode boot error
Thanks for the info- I thought the unpopulated list was a bug because the procedure you describe is not that self evident. I have never seen an unpopulated dropdown list that fills in after you type something into it. Someone else classified this as medium priority, but it has a lot of people confused and in danger of being locked out of their systems. Now every time I do an update, I make sure there is no .failsafe file reintroduced before I shut down and my system runs fine. On 12/03/2013 09:43 AM, Quinn Balazs wrote: To edit your original post, click the little yellow exclamation point above the bug description. To edit the package you have to type a package name into the choose field, and click the small magnifying glass to get a list of all possible packages that include that term. Generally this issue is caused by a combination of a kernel update and your graphics drivers. We'll file this against the linux package for the time being. Please run apport-collect 1257085 which will gather a bunch of logs and post them attached to this report so that we can get a better idea of what's going on here. ** Package changed: ubuntu = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257058 Title: low graphics mode boot error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1257058] Re: low graphics mode boot error
2d reply The apport-collect came back with you are not the originator of this bug. And I am not sure how comfortable I am at sending out a complete system snapshot, if that is what it is. Is there a way to run this locally and then send out the txt file? On 12/03/2013 09:43 AM, Quinn Balazs wrote: To edit your original post, click the little yellow exclamation point above the bug description. To edit the package you have to type a package name into the choose field, and click the small magnifying glass to get a list of all possible packages that include that term. Generally this issue is caused by a combination of a kernel update and your graphics drivers. We'll file this against the linux package for the time being. Please run apport-collect 1257085 which will gather a bunch of logs and post them attached to this report so that we can get a better idea of what's going on here. ** Package changed: ubuntu = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257058 Title: low graphics mode boot error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257058] Re: low graphics mode boot error
CORRECTION: not sudo rm /etc/X11/xorg.conf but rm /etc/X11/xorg.conf.failsafe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257058 Title: low graphics mode boot error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1257058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257058] [NEW] low graphics mode boot error
Public bug reported: Ubuntu 12.04 64 bit with Gnome fallback System starts with message the system is running in low graphics mode, the desktop does not come up, and the system is locked from all further entries. After one or more system restarts it boots normally. Problem discussed in http://askubuntu.com/questions/141606/how-to-fix-the-system-is- running-in-low-graphics-mode-error with several possible solutions. One that works is to sudo rm /etc/X11/xorg.conf - as long as this file is gone, there are no more boot errors. However this file keeps re- appearing and it seems to be re-introduced by the update linux- firmware_1.79.9_all.deb. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257058 Title: low graphics mode boot error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1257058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257058] Re: low graphics mode boot error
When I go to select a package, the select one dropdown list is unpopulated, and I am not sure exactly what you mean by a package name. Also, I cannot figure out how to EDIT the original bug. I had to add a comment to correct an incomplete file name. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257058 Title: low graphics mode boot error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1257058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878828] Re: amarok crashes with segmentation fault
problem gets fixed if i delete the /.kde/share/apps/amarok folder THANKS!! Worked like a charm for fixing startup segmentation faults on Ubuntu 12.04-64 bit when all else failed. 11/1/2012 The more things change, the more they stay the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878828 Title: amarok crashes with segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/878828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033825] [NEW] Incorrect greyed out selections in Gnome Fallback
Public bug reported: Ubuntu 12.04 amd64 logging into Gnome Classic environment- not Unity. Context menus on the desktop have options greyed out that should not be, at least if greyed-out still means a choice that is not a current option. For example, if I create a new folder on the desktop then right click it, there are selections in the context menu such as rename, move to trash, and others that are greyed out, but if I click on them, they work anyway (as I think they should). Attached screenshot shows a new folder that has been right-clicked displaying the inaccurate context menu. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: context inaccurate menu ** Description changed: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033825 Title: Incorrect greyed out selections in Gnome Fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033825] Re: Incorrect greyed out selections in Gnome Fallback
I don't see my screenshot attachment, so here it is again. ** Attachment added: incorrect greyed selections.png https://bugs.launchpad.net/ubuntu/+bug/1033825/+attachment/3251046/+files/incorrect%20greyed%20selections.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033825 Title: Incorrect greyed out selections in Gnome Fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033825] Re: Incorrect greyed out selections in Gnome Fallback
This is not an application that can be found on any menu making it easy to identify a responsible executable as far as I can see. It is an entire ENVIRONMENT- tightly integrated into the OS, similar to Unity. The Software Center and Synaptic only identify it by NAME and version- Gnome Desktop Environment 1:3.0+6ubuntuU3. There is no numeric or other identifying package code. The package ID select field in the bug report is no help because typing Gnome returns a too broad error, and several other attempts like Gnome Desktop Environment report no matches. It would have been helpful if the robot provided a list of alternatives relating to Gnome from which to choose. At some point, someone who is familiar with the architecture has to read the bug and identify the package rather than generate automated messages because a field was left empty. The report is brief, straightforward, concisely written, and reproducable on any machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033825 Title: Incorrect greyed out selections in Gnome Fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027186] [NEW] HP Deskjet (880C) Wrong Colors in Precise
Public bug reported: Precise 12.04 with Gnome Fallback After a fresh install of Precise with all of its auto detection and configuration, HP 880C Deskjet printer prints wrong colors- teal skin tones for example. If I boot Lucid instead, output for same photo is perfect. Searching Synaptic for HP brings up multiple drivers and apps Precise put on my system based (I assume) on the printer it autodetected. I have no clue where to begin. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027186 Title: HP Deskjet (880C) Wrong Colors in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1027186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 458811] Re: lm-sensors not working on Intel d945gclf
LM Sensors addresses some of this if you can navigate their site and then figure out what they are talking about. . If you join their mailing list, your inbox will be swamped with notes and code that will really make you ask what are they talking about? Good luck.http://lists .lm-sensors.org/mailman/listinfo/ -- lm-sensors not working on Intel d945gclf https://bugs.launchpad.net/bugs/458811 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583089] Re: orage loses preferences
Thanks for the debugging reference- I put it in right in SpeedDial and also the bug reporting guide. This problem arose after changing Orage settings then returning it to the original settings. I DID have the hide button checked, but it failed to work, showing the calendar on the desktop at each subsequent reboot. At the time I submitted this I was using Xubuntu Lucid, which I have since uninstalled due to a critical failure that I could not get resolved through the community- an inability to log in after running a dozen sessions or so. A reinstall did the same. Since then I have installed regular Ubuntu instead of Xubuntu. I installed Orage in Ubuntu, even though it is an XFCE tailored application and it seems to be working fine so far, so I can't give you any more details on this. Thanks for your prompt response. Orage is a great little applet- we don't all need the complexity (and unreliability) of the Evolution calendar. Hoping Orage will keep working OK. I will take careful notes of the current settings, but I am a little shy about experimenting with them and going back to the original settings again. -- orage loses preferences https://bugs.launchpad.net/bugs/583089 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147163] Re: Evolution does not notify on missed alarms
2 days later, I DO have evolution-exchange -data in SysMon. If the workaround does not work in Lucid Beta 1, does anyone know if it works in Lucid final release? -- Evolution does not notify on missed alarms https://bugs.launchpad.net/bugs/147163 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147163] Re: Evolution does not notify on missed alarms
I don't know if you call this a bug, but for me it is. And it has been there for a very long time- at least since Feisty 7.04, and seems to be important to a lot of people. I switched to Mozilla Sunbird because of it, but now Sunbird is not available for Lucid. If I miss an appointment because I was not on my system for a few days, I like to be notified so I can apologize and reschedule. If it seems to matter to a number of people, why is it so hard to fix? -- Evolution does not notify on missed alarms https://bugs.launchpad.net/bugs/147163 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147163] Re: Evolution does not notify on missed alarms
Lucid I don't have evolution-exchange -data in SysMon, so I guess I can't try the work around. -- Evolution does not notify on missed alarms https://bugs.launchpad.net/bugs/147163 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583089] [NEW] orage loses preferences
Public bug reported: Binary package hint: orage Xubuntu Lucid. Orage always opens with the main window on screen, even when you set it to hide or minimized. I have calendar (orage) in startup so I do not miss alarms. I need it to show up on the task bar ONLY (or in the pager if there is an alarm) but I do not want to start each session by closing the main calendar window displayed on the desktop screen. Repeated attempts to reset this from orage and from xfce settings manager have failed. This program worked fine for about two weeks, but now it will NOT retain its preference settings. It makes no difference whether I log out saving or not saving the current session. ** Affects: orage (Ubuntu) Importance: Undecided Status: New -- orage loses preferences https://bugs.launchpad.net/bugs/583089 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66597] EDGY nautilus crash when GNOME starts
Public bug reported: Binary package hint: nautilus Subject: Nautilus startup crash EDGY 6.06 UPGRADE Distribution: Ubuntu 6.10 (edgy) Package: nautilus Severity: major Version: GNOME2.14.1 2.7.x Gnome-Distributor: Ubuntu Synopsis: Nautilus startup crash EDGY 6.06 UPGRADE Bugzilla-Product: nautilus Bugzilla-Component: Builds Bugzilla-Version: 2.7.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: I upgraded from dapper to edgy on a thinkpad 390e. The prolem is that nautilus crashes right after you start gnome. Steps to reproduce the crash: 1. Login 2. GNOME loads 3. Nautilus Crash error Expected Results: Nautilus crashes when starup occurs How often does this happen? everytime you startup, will not go away after closing it Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225573728 (LWP 4587)] [New Thread -1227048032 (LWP 4611)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xe410 in __kernel_vsyscall () #0 0xe410 in __kernel_vsyscall () #1 0xb776634b in __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7e798e6 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #3 signal handler called #4 0xb7cf31e5 in _gtk_menu_is_empty () from /usr/lib/libgtk-x11-2.0.so.0 #5 0xb7cf2930 in _gtk_menu_is_empty () from /usr/lib/libgtk-x11-2.0.so.0 #6 0xb7cf2930 in _gtk_menu_is_empty () from /usr/lib/libgtk-x11-2.0.so.0 #7 0xb7cf2930 in _gtk_menu_is_empty () from /usr/lib/libgtk-x11-2.0.so.0 #8 0xb7cf3984 in _gtk_menu_is_empty () from /usr/lib/libgtk-x11-2.0.so.0 #9 0xb7cf3a67 in gtk_ui_manager_ensure_update () from
[Bug 66597] Re: EDGY nautilus crash when GNOME starts
[EMAIL PROTECTED]:~$ gnome-session-remove nautilus (this just hangs there, i just ctrl c it) [EMAIL PROTECTED]:~$ gdb nautilus GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i486-linux-gnu...(no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. (gdb) run Starting program: /usr/bin/nautilus (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type return to continue, or q return to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225770336 (LWP 6508)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type return to continue, or q return to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type return to continue, or q return to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1227244640 (LWP 6515)] Program received signal SIGINT, Interrupt. [Switching to Thread -1225770336 (LWP 6508)] 0xe410 in __kernel_vsyscall () (gdb) thread apply all bt Thread 2 (Thread -1227244640 (LWP 6515)): #0 0xe410 in __kernel_vsyscall () #1 0xb750f803 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb76c6813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0xb76c6b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #4 0xb77b57e0 in link_set_io_thread () from /usr/lib/libORBit-2.so.0 #5 0xb76e138f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0 #6 0xb772f504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb751951e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread -1225770336 (LWP 6508)): #0 0xe410 in __kernel_vsyscall () #1 0xb7732816 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb77988e9 in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0 #3 0xb779d33d in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0 #4 0xb779d53e in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0 #5 0xb77a9d32 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0 #6 0xb77d681a in Bonobo_ActivationContext_activateMatchingFull () from /usr/lib/libbonobo-activation.so.4 #7 0xb77d9139 in bonobo_activation_activate () from /usr/lib/libbonobo-activation.so.4 ---Type return to continue, or q return to quit--- #8 0xb77d9390 in bonobo_activation_activate_from_id () from /usr/lib/libbonobo-activation.so.4 #9 0x08069f89 in
Re: [Bug 66597] Re: EDGY nautilus crash when GNOME starts
On Tue, 17 Oct 2006 16:39:06 -0400, Sebastien Bacher [EMAIL PROTECTED] wrote: Program received signal SIGINT, Interrupt., that doesn't look like a crash, rather stopped by user action. Are you sure it crashed? I thought i noted that i did that, since it wouldnt go? As soon as gnome loads, nautilus error box comes up. -- EDGY nautilus crash when GNOME starts https://launchpad.net/bugs/66597 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66597] Re: EDGY nautilus crash when GNOME starts
when you told me to do gnome-session-remove nautilus , it dosnt do anything, it just..its blank -- EDGY nautilus crash when GNOME starts https://launchpad.net/bugs/66597 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
