[Bug 87175] Re: totem segfaults with xinerama and nvidia
this bug seems similar to https://launchpad.net/ubuntu/+source/linux- restricted-modules-2.6.17/+bug/58232 but my bug has only recently started happening. I'd like to attach helpful files like a coredump, xtrace, strace, etc. but I don't know how. If someone could tell me I will post as much helpful info as I can. -- totem segfaults with xinerama and nvidia https://launchpad.net/bugs/87175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87175] Re: totem segfaults with xinerama and nvidia
I'd also like to add that unlike the above-mentioned gnome-terminal bug, totem still segfaults when I turn off compositing in xorg.conf I can't find any workarounds to get totem to work while xinerama is on. -- totem segfaults with xinerama and nvidia https://launchpad.net/bugs/87175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87175] totem segfaults with xinerama and nvidia
Public bug reported: Totem fails to load completely when using the proprietary nvidia driver and with xinerama enabled. When I run totem from terminal, the gtk window loads for about a 1/4 second and then closes, and I get is the following message in the terminal: Segmentation fault (core dumped) ** Affects: linux-restricted-modules-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- totem segfaults with xinerama and nvidia https://launchpad.net/bugs/87175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87175] Re: totem segfaults with xinerama and nvidia
OK I found two helpful files in my /var/crash, I'm not sure if the clear_console crash is related to the totem crash, but apport *did* notify me that clear_console crashed the very first time totem crashed, so I will attach it anyway. ** Attachment added: /var/crash/_usr_bin_totem.1000.crash http://librarian.launchpad.net/6511605/_usr_bin_totem.1000.crash -- totem segfaults with xinerama and nvidia https://launchpad.net/bugs/87175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87175] Re: totem segfaults with xinerama and nvidia
here is the clear_console crash ** Attachment added: /var/crash/_usr_bin_clear_console.1000.crash http://librarian.launchpad.net/6511607/_usr_bin_clear_console.1000.crash -- totem segfaults with xinerama and nvidia https://launchpad.net/bugs/87175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73718] Update notifier's pop-up interrupts you while watching Totem in full-screen view
Public bug reported: When I am watching a movie full-screen and ubuntu needs updates, update- notifier will pop up a notification, interrupting the user experience. Basically the pop-up gets laid on the top window layer over the totem window. It's really quite annoying because the window won't go away until I satisfy update-notifier. I'm not sure if this is a problem with totem, update-notifier, or dbus. It really kills the user experience when you're at the most intense part of the movie and ubuntu's pop-up is nagging you to apply security updates to tar. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Update notifier's pop-up interrupts you while watching Totem in full-screen view https://launchpad.net/bugs/73718 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70262] inconsistent user experience--orange button doesn't feel like a button
Public bug reported: Binary package hint: update-notifier When a user clicks on the orange update-notifier button on the panel, the button ought to exhibit button-like behavior. More specifically, the orange button should depress when clicked, and return to normal when mouse button is released. The current behavior of the update-notifier button is inconsistent because surrounding buttons, such as the logout button (the door icon), the volume button, and the date/time button all give *immediate* feedback when clicked (whether it's depressing itself, calling another window immediately, etc.). The orange update-notifier button, however, can take as long as two whole seconds to respond after being clicked on a slow computer. I have been confused in the past whether the button requires a single or double-click to work, and as a result several windows were called up at the same time two seconds later because I clicked too many times. This problem can probably be remedied by giving the user immediate feedback that his/her click actually *did* something, such as depressing the orange button. ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: Unconfirmed -- inconsistent user experience--orange button doesn't feel like a button https://launchpad.net/bugs/70262 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57630] Re: there are multiple menu entries for f-spot in alacarte menu editor in a new edgy install
-- there are multiple menu entries for f-spot in alacarte menu editor in a new edgy install https://launchpad.net/bugs/57630 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57630] there are multiple menu entries for f-spot in alacarte menu editor in a new edgy install
Public bug reported: there are duplicate entries in alacarte menu editor (by navigating the menus by System--Preferences--Menu Layout). Incidentally, the menu entry called F-spot Photo Viewer crashes mono, but the entry called F-spot Photo Manger does not. ** Affects: f-spot (Ubuntu) Importance: Untriaged Status: Unconfirmed -- there are multiple menu entries for f-spot in alacarte menu editor in a new edgy install https://launchpad.net/bugs/57630 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57622] Re: Menu Layout Crashes (alacarte menu editor)
here's the python crash log: ** Description changed: I'm not sure whether to file this as a bug with Alacarte (found in System--Preferences--Menu Layout) or as a bug with python 2.4. - I attempted to open the menu item called Menu Layout, it failed to - load, and then crashed. The problem report told me to attach + I attempted to open the menu item called Menu Layout, it loaded + briefly, and then crashed. The problem report told me to attach /var/crash/_usr_bin_python2.4.1000.crash , though it seems to me that the developers would want me attach more info specifically about alacarte (like a crash log). I don't know where that would be. I can also provide any further info about my system if needed. -- Menu Layout Crashes (alacarte menu editor) https://launchpad.net/bugs/57622 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57626] Re: Network Monitor Icons look stretched out on 1280x768 resolution
-- Network Monitor Icons look stretched out on 1280x768 resolution https://launchpad.net/bugs/57626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57629] Re: Tried to launch alacarte menu editor after opening and closing f-spot, alacarte fails to load/crashes
-- Tried to launch alacarte menu editor after opening and closing f-spot, alacarte fails to load/crashes https://launchpad.net/bugs/57629 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57622] Menu Layout Crashes (alacarte menu editor)
Public bug reported: I'm not sure whether to file this as a bug with Alacarte (found in System--Preferences--Menu Layout) or as a bug with python 2.4. I attempted to open the menu item called Menu Layout, it loaded briefly, and then crashed. The problem report told me to attach /var/crash/_usr_bin_python2.4.1000.crash , though it seems to me that the developers would want me attach more info specifically about alacarte (like a crash log). I don't know where that would be. I can also provide any further info about my system if needed. ** Affects: python2.4 (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Menu Layout Crashes (alacarte menu editor) https://launchpad.net/bugs/57622 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57626] Network Monitor Icons look stretched out on 1280x768 resolution
Public bug reported: On a fresh install of Edgy on my 1280x768 laptop, the signal-strength bars are horizontally stretched and there is a lot of white space on both sides of the signal-strength bars. ** Affects: gnome-netstatus (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Network Monitor Icons look stretched out on 1280x768 resolution https://launchpad.net/bugs/57626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57628] Re: there are multiple menu entries for evolution in a new edgy install
-- there are multiple menu entries for evolution in a new edgy install https://launchpad.net/bugs/57628 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57628] there are multiple menu entries for evolution in a new edgy install
Public bug reported: when opening up alacarte menu editor, there are duplicate entries for evolution to add to the Applications--Office submenu. Furthermore, there are duplicate entries for evolution in both the Applications--Internet and Applications--Office submenus. This seems to go against Ubuntu's and gnome's minimalism. ** Affects: evolution (Ubuntu) Importance: Untriaged Status: Unconfirmed -- there are multiple menu entries for evolution in a new edgy install https://launchpad.net/bugs/57628 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57629] Tried to launch alacarte menu editor after opening and closing f-spot, alacarte fails to load/crashes
Public bug reported: I opened f-spot for 1 second, then closed it. I then launched alacarte menu editor by clicking on System--Preferences--Menu Layout. The computer froze for about 5 seconds, then I received a crash report for mono-jit. The crash report is attached. ** Affects: mono (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Tried to launch alacarte menu editor after opening and closing f-spot, alacarte fails to load/crashes https://launchpad.net/bugs/57629 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
