[Bug 674419] [NEW] clock does not update after moving panel to different screen
Public bug reported: Binary package hint: gnome-panel Running two screens using TwinView. If I move the top panel from one screen to another the clock freezes at that time and does not update correctly. See attached screenshot for clarification :) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-panel 1:2.30.2-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Nov 12 09:55:02 2010 GConfNonDefault: /apps/panel/general/applet_id_list=[fast_user_switch_screen0,trashapplet_screen0,workspace_switcher_screen0,window_list_screen0,show_desktop_button_screen0,indicator_applet_screen0,notification_area_screen0,clock_screen0] /apps/panel/general/object_id_list=[menu_bar_screen0,object_0] /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0] InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: gnome-panel ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- clock does not update after moving panel to different screen https://bugs.launchpad.net/bugs/674419 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 674419] Re: clock does not update after moving panel to different screen
** Attachment added: Screenshot of issue https://bugs.launchpad.net/bugs/674419/+attachment/1730978/+files/Screenshot.png -- clock does not update after moving panel to different screen https://bugs.launchpad.net/bugs/674419 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 664483] [NEW] evolution segfaults on trying to open email from tomboy note
Public bug reported: Binary package hint: evolution To reproduce: 1. Create a note in tomboy 2. Drag and drop an email from evo into tomboy 3. click generated link 4. Watch evolution segfault Only seems to occur on maverick, not lucid ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu6 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Oct 21 14:17:36 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: evolution ** Affects: evolution (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug evolution maverick -- evolution segfaults on trying to open email from tomboy note https://bugs.launchpad.net/bugs/664483 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 664483] Re: evolution segfaults on trying to open email from tomboy note
-- evolution segfaults on trying to open email from tomboy note https://bugs.launchpad.net/bugs/664483 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621395] Re: $term set to dumb rather than xterm
Hi David, What information would be useful to you? If you can let me know where this is set I can dig out that particular file. Thanks. -- $term set to dumb rather than xterm https://bugs.launchpad.net/bugs/621395 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621395] Re: $term set to dumb rather than xterm
Ah, apologies. Seems this was actually a problem with Terminator. Have updated it to the latest bzr incarnation and it works now so setting this to invalid! ** Changed in: gnome-terminal (Ubuntu) Status: New = Invalid -- $term set to dumb rather than xterm https://bugs.launchpad.net/bugs/621395 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621395] [NEW] $term set to dumb rather than xterm
Public bug reported: Binary package hint: gnome-terminal On updating maverick recently I've discovered that some programs (like screen) we're having issues because the $TERM environment settings seems to have changed to dumb rather than xterm on Lucid. This should be reverted to be xterm please. ProblemType: Bug DistroRelease: Ubuntu 10.10 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 lucid -- $term set to dumb rather than xterm https://bugs.launchpad.net/bugs/621395 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621395] Re: $term set to dumb rather than xterm
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/621395/+attachment/1505547/+files/Dependencies.txt ** Description changed: Binary package hint: gnome-terminal On updating maverick recently I've discovered that some programs (like screen) we're having issues because the $TERM environment settings seems to have changed to dumb rather than xterm on Lucid. This should be reverted to be xterm please. ProblemType: Bug - DistroRelease: Ubuntu 10.04 - Package: gnome-terminal 2.29.6-0ubuntu5 - ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 - Uname: Linux 2.6.32-24-generic i686 - NonfreeKernelModules: nvidia - Architecture: i386 - Date: Fri Aug 20 21:47:37 2010 - InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) - ProcEnviron: - LANG=en_GB.utf8 - SHELL=/bin/bash - SourcePackage: gnome-terminal + DistroRelease: Ubuntu 10.10 -- $term set to dumb rather than xterm https://bugs.launchpad.net/bugs/621395 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621395] Re: $term set to dumb rather than xterm
Apologies, used ubuntu-bug on incorrect machine! Dependencies is from the wrong box -- $term set to dumb rather than xterm https://bugs.launchpad.net/bugs/621395 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 506987] [NEW] f-spot doesn't start after crashing out importing from large nfs share
Public bug reported: Binary package hint: f-spot After trying to import 37G of photos over NFS f-spot gave up, and now doesn't start giving the error message : m...@bistromath:~/Pictures$ f-spot -debug (/usr/lib/f-spot/f-spot.exe:18158): GLib-WARNING **: g_set_prgname() called multiple times [Info 14:26:11.303] Initializing DBus [Info 14:26:11.417] Initializing Mono.Addins [Info 14:26:11.576] Starting new FSpot server (f-spot 0.6.1.5) ** (/usr/lib/f-spot/f-spot.exe:18158): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:18158): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:18158): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:18158): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:18158): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Info 14:26:12.477] Starting BeagleService [Info 14:26:12.493] Hack for gnome-settings-daemon engaged (/usr/lib/f-spot/f-spot.exe:18158): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. The program '/usr/lib/f-spot/f-spot.exe' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 2945 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Loading thumbnails of each image in that 37G took _hours_. ProblemType: Bug Architecture: i386 Date: Wed Jan 13 14:22:14 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: f-spot 0.6.1.5-0ubuntu1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic-pae SourcePackage: f-spot Uname: Linux 2.6.31-16-generic-pae i686 ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- f-spot doesn't start after crashing out importing from large nfs share https://bugs.launchpad.net/bugs/506987 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 506987] Re: f-spot doesn't start after crashing out importing from large nfs share
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37849850/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/37849860/XsessionErrors.txt -- f-spot doesn't start after crashing out importing from large nfs share https://bugs.launchpad.net/bugs/506987 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 506987] Re: f-spot doesn't start after crashing out importing from large nfs share
Hmmm, it seems to start if I change the theme to Human from New Look. But it still crashes out trying to load the thumbnails when I try to import from NFS -- f-spot doesn't start after crashing out importing from large nfs share https://bugs.launchpad.net/bugs/506987 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 506987] Re: f-spot doesn't start after crashing out importing from large nfs share
That should be New Wave sorry, not New Look. -- f-spot doesn't start after crashing out importing from large nfs share https://bugs.launchpad.net/bugs/506987 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
