[Bug 1184007] Re: menu mouse-scrolling up down does not appear on first try on large menus
Moving this to gtk+3.0. I believe it is gtk 3 specific. It is not just limited to gedit, it happens with any app using indicator-appmenu (I notice it most often under okular on pdfs with lots of bookmarks). But it is also not indicator-appmenu specific because the following code, when run with: UBUNTU_MENUPROXY=0 ./test-menu will exhibit the behavior as well. When compiled with: gcc -o test-menu test-menu.c $(pkg-config --cflags --libs gtk+-3.0); the weird first time no scrollbars behavior occurs. But it works fine if using: gcc -o test-menu test-menu.c $(pkg-config --cflags --libs gtk+-2.0); ** Summary changed: - menu mouse-scrolling up down does not appear on first try + menu mouse-scrolling up down does not appear on first try on large menus ** Package changed: gtk+2.0 (Ubuntu) = ubuntu ** Package changed: ubuntu = gtk+3.0 (Ubuntu) ** Attachment added: test-menu.c https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1184007/+attachment/3686109/+files/test-menu.c -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1184007 Title: menu mouse-scrolling up down does not appear on first try on large menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1184007/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181312] [NEW] Race to start gnome-settings-daemon in upstart user session
Public bug reported: It appears if enabling the upstart user session ( https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes#Upstart_User_Sessions_.28technology_preview.29 ) there is a race between gnome-session and upstart for who starts gnome-settings-daemon first. Most of the time on my system, it seems like upstart wins. I'm guessing in that case, gnome-session tries to start it, fails and gives up, which is fine. When gnome-session wins however, upstart continues to respawn gnome- settings-daemon indefinitely, usually causing the wrong icon theme to load, and causing flickering on the desktop (most noticeable in a conky window, but affecting other windows as well). Since it is a race, it is difficult to reproduce, but it can be forced by: 1) enable upstart user sessions 2) mkdir -p ~/.config/upstart/ 3) echo manual ~/.config/upstart/gnome-settings-daemon.override 4) Log into the ubuntu session 5) initctl start gnome-settings-daemon; Running: initctl stop gnome-settings-daemon; will stop the endless respawn of gnome-settings-daemon when finished testing. My current workaround is to disable /etc/xdg/gnome-settings- daemon.desktop from starting, and let upstart take it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.4-0ubuntu8 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 17 12:34:23 2013 InstallationDate: Installed on 2011-10-11 (583 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to raring on 2013-04-24 (22 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1181312 Title: Race to start gnome-settings-daemon in upstart user session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1181312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181312] Re: Race to start gnome-settings-daemon in upstart user session
Ah, in that case this may just be a bug with my setup. $HOME/.config/autostart/ is likely read before any of those directories, and I have a copy of gnome-settings-daemon.desktop in there. Thanks for the information. I'll delete it and continue testing, but this bug is probably invalid. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1181312 Title: Race to start gnome-settings-daemon in upstart user session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1181312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1177012] Re: Selecting default application in System Settings does not present predictable results.
I think I worked out at least part of the problem, so might not be a gnome-control-center bug after all. gnome-control-center uses the mimetype video/x-ogm+ogg to determine the default Video app in Default Applications. SMplayer does not have this mimetype in its smplayer.desktop file, but instead has video/x-ogm. None of the other video players that I see have that specific mimetype in their .desktop files, so when gnome-control-center sets the default for the mimetypes present in the .desktop file, a line: video/x-ogm=smplayer.desktop will still exist in ~/.local/share/applications/mimeapps.list. The curious part is why should it care? It asks for video/x-ogm+ogg, which is set correctly. The problem is that when glib loads the mimetypes from mimeapps.list, it calls a function xdg_mime_unalias_mime_type() on video/x-ogm, and as it happens, /usr/share/mime/aliases has a line video/x-ogm video/x-ogm+ogg. So if video/x-ogm=smplayer.desktop happens to appear later in mimeapps.list, it will end up overwriting the true default value in the hashtable. I find that if I change the mimetype in smplayer.desktop to video/x-ogm+ogg and delete the video/x-ogm=smplayer.desktop line from mimeapps.list, then gnome-control-center will again correctly let me switch between totem, vlc and smplayer as defaults. So that might be a fix, in smplayer instead. Might be a bit fragile though, since if another app comes along doing the same thing, it will expose the same bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1177012 Title: Selecting default application in System Settings does not present predictable results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1177012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1036752] Re: [quantal] [regression] Gnome Classic has no compiz plugins loaded
Hi Sam, Yes the COMPIZ_CONFIG_PROFILE environment variable is still used, but if unset or the empty string compiz first checks GNOME_DESKTOP_SESSION_ID, which in quantal is currently set to 'this-is-deprecated'. If it is set, then it returns the section name as gnome_session. Doesn't really matter though, it will default to Default.ini even if the section is missing, but as far as I can tell there isn't any code that reads an ini from /etc/compizconfig/ (and just dropping a Default.ini file in there and loading the gnome classic session only loads the core and ccp plugins). I took a look at the natty package to see how it was handled there, and the code seems basically the same, so I don't think it would load an ini from /etc/compizconfig/ there either. The only difference I noticed was that /etc/compizconfig/config in natty looks like: [kde4_session] backend = kconfig4 integration = true plugin_list_autosort = true [kde_session] backend = kconfig integration = true plugin_list_autosort = true [gnome_session] backend = gconf integration = true plugin_list_autosort = true [general] backend = ini plugin_list_autosort = true [general_ubuntu] backend = gconf integration = true plugin_list_autosort = true profile = unity We only have the [general] and [general_ubuntu] sections in quantal (with the ubuntu section using gsettings now instead of gconf). We can't use gconf for gnome_session since that backend was dropped in the transition. I'd like to use gsettings but I can't figure out how to make it work since we would need to set defaults for the same key with different paths (or run a script when the user logs in checking if the key is set and then setting it, I don't really like that idea). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1036752 Title: [quantal] [regression] Gnome Classic has no compiz plugins loaded To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1036752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1036752] Re: [quantal] [regression] Gnome Classic has no compiz plugins loaded
Alright, ideally I would use gsettings, but I cannot figure out how to set up the default plugins without running some sort of script in the user session to set the keys if they are not already set. So, my thought is that we can just use the ini backend but with the attached patch to compizconfig/libcompizconfig/backend/source/ini.c. This patch allows compiz to fallback to a .ini profile in /etc/compizconfig/ to read settings if the value is not already set in the user .ini file in ~/.config/compiz-1/compizconfig/. With the addition of a simple Default.ini to /etc/compizconfig/ such as: [core] s0_active_plugins = core;composite;opengl;compiztoolbox;decor;vpswitch;snap;mousepoll;resize;place;move;wall;grid;regex;imgpng;session;gnomecompat;animation;fade;workarounds;scale;expo;ezoom the Gnome Classic session will load up with a nice default set of plugins. Technically it only needs to fallback for a List option to fix this issue, but I added them all anyway. Probably needs some testing and perhaps fixing. ** Patch added: compiz_system_ini_v3.patch https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1036752/+attachment/3353860/+files/compiz_system_ini_v3.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1036752 Title: [quantal] [regression] Gnome Classic has no compiz plugins loaded To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1036752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1036752] Re: [quantal] [regression] Gnome Classic has no compiz plugins loaded
I noticed that when loading ccsm in the gnome classic session it outputs: Backend: ini I can force it to use the gsettings backend by adding: [gnome_session] backend = gsettings profile = Default to /etc/compizconfig/config, but it will just load the unity active- plugins from /usr/share/glib-2.0/schemas/10_compiz- gnome.gschema.override, and I don't see any way to override this, even though the schema is relocatable. Looking at the migration scripts, it seems like: [org.compiz.core:/org/compiz/profiles/unity/plugins/core/] active-plugins=[..] should work (and then we could create one for Default or gnome-classic or whatever), but it doesn't, compiz will only load core and ccp plugins. Using the ini backend would be fine too, but it doesn't read any from /etc/compizconfig/, choosing instead to create a blank file in ~/.config/compiz-1/compizconfig/, so I can't override that unless I create/copy a Default.ini file there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1036752 Title: [quantal] [regression] Gnome Classic has no compiz plugins loaded To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1036752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1036752] Re: [quantal] [regression] Gnome Classic has no compiz plugins loaded
Though it does work with the gsettings backend if the settings are set at the user level with either ccsm or: gsettings set org.compiz.core:/org/compiz/profiles/Default/plugins/core/ active-plugins ['core','composite','opengl','decor','move','imgpng','place','resize']; So I guess it is just from the gsettings vendor overrides that you can't use the setting path. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1036752 Title: [quantal] [regression] Gnome Classic has no compiz plugins loaded To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1036752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041756] Re: gnome-control-center and desktop environment crashes when trying to change full name in User Accounts
Updated the debdiff, forgot to bump the gtk+3.0 build-depends to 3.5.13 for the new gtk_entry_set_attributes() function in the patch. ** Patch added: gnome-control-center_fix-big-editable-labels-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041756/+attachment/3310419/+files/gnome-control-center_fix-big-editable-labels-v2.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1041756 Title: gnome-control-center and desktop environment crashes when trying to change full name in User Accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041756] Re: gnome-control-center and desktop environment crashes when trying to change full name in User Accounts
Attaching a debdiff with the upstream commit that fixes the issue. ** Patch added: gnome-control-center_fix-big-editable-labels.debdiff https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041756/+attachment/3305931/+files/gnome-control-center_fix-big-editable-labels.debdiff ** Changed in: pango1.0 (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1041756 Title: gnome-control-center and desktop environment crashes when trying to change full name in User Accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1036260] Re: Running gtester-report on gtester output raises KeyError
Thanks for the bug report. I found an upstream bug here: https://bugzilla.gnome.org/show_bug.cgi?id=668035 and I submitted a simple patch to fix it. You can workaround the issue by manually adding: info packagePACKAGENAME/package versionVERSION/version revisionREVISION/revision /info to the generated xml. It seems that is exactly what glib does, to collect multiple reports together. (See Makefile.decl in the glib source) ** Bug watch added: GNOME Bug Tracker #668035 https://bugzilla.gnome.org/show_bug.cgi?id=668035 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=668035 Importance: Unknown Status: Unknown ** Changed in: glib2.0 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1036260 Title: Running gtester-report on gtester output raises KeyError To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1036260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1027594] Re: Launcher icon size slider vanished from appearance tab - no way to change icon size.
Thanks for the bug report. However, I cannot reproduce this bug. I am going to move this to gnome-control-center. Can you add the output of: apt-cache policy gnome-control-center; Maybe you have a PPA overriding the default package. A screenshot of the Appearance dialog may also be helpful. Thanks. ** Package changed: dash (Ubuntu) = gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1027594 Title: Launcher icon size slider vanished from appearance tab - no way to change icon size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1027594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1027594] Re: Launcher icon size slider vanished from appearance tab - no way to change icon size.
One more idea, try running in a terminal: XDG_CURRENT_DESKTOP=Unity gnome-control-center; It will only show that option in a unity session, but maybe your XDG_CURRENT_DESKTOP environment variable is overwritten somewhere. If the above works, check: echo $XDG_CURRENT_DESKTOP; -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1027594 Title: Launcher icon size slider vanished from appearance tab - no way to change icon size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1027594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1027594] Re: Launcher icon size slider vanished from appearance tab - no way to change icon size.
Thanks for the screenshots. It turns out I am able to reproduce this in the unity-2d session. Bug #1005136 is about adding the option for that session. Please check: echo $DESKTOP_SESSION; to see if you are running the ubuntu-2d session. If so, either try the Ubuntu session or there are workarounds for 12.04 listed at this askubuntu question: http://askubuntu.com/questions/82395/how-can-i -change-the-size-of-unity-2d-launcher-icons Sorry for the confusion. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1027594 Title: Launcher icon size slider vanished from appearance tab - no way to change icon size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1027594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1000317] Re: CTRL+D exits terminal
CTRL+D sends EOF to the shell, indicating the end of input, so the shell exits, which causes gnome-terminal to exit. You can verify this by running another bash session in the terminal: bash then press CTRL+D. That instance of bash will exit but gnome-terminal will remain open. Another example, and probably the most common one on ubuntu systems is running a python interactive shell. If you type exit it will echo: Use exit() or Ctrl-D (i.e. EOF) to exit I am going to mark this bug as invalid, if you feel there really is a bug here, feel free to reopen. ** Changed in: gnome-terminal (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1000317 Title: CTRL+D exits terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1000317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 967924] Re: rhythmbox DAAP plugin causes crash when saving settings
Have you tested this since the updates to glib 2.32 and gtk 3.4? I marked this as confirmed last night since I could reproduce it consistently, but since the updates today, I can no longer reproduce the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/967924 Title: rhythmbox DAAP plugin causes crash when saving settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/967924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 917071] Re: gedit crashed with SIGSEGV in _gtk_tree_selection_internal_select_node()
This is fixed in 3.3.8-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/917071 Title: gedit crashed with SIGSEGV in _gtk_tree_selection_internal_select_node() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/917071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 917071] Re: gedit crashed with SIGSEGV in _gtk_tree_selection_internal_select_node()
It isn't limited to gedit, but seems to affect any GtkTreeView. I believe it is fixed upstream though: http://git.gnome.org/browse/gtk+/commit/gtk/gtktreeview.c?id=022c576bd2764dc1fc48e46ad97aa95287c175cc Rebuilt gtk with the patch and I can't reproduce the crash. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/917071 Title: gedit crashed with SIGSEGV in _gtk_tree_selection_internal_select_node() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/917071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 910195] Re: nautilus crashed with SIGSEGV in g_str_hash()
Looks like this is the same bug as in https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/908787 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/910195 Title: nautilus crashed with SIGSEGV in g_str_hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/910195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 908787] Re: nautilus crashed with SIGSEGV in g_str_hash()
Found the problem, it is actually caused by ubuntuone-client (specifically libsyncdaemon). Due to a recent change from bug #859635 , the library is registering a dbus message marshaller for VOID__POINTER, however the type registered is actually VOID__BOXED, which happens to be the same type as DeviceChanged from UDisks (DBusGObjectPath is a boxed type). So there is an unnecessary (it is a standard type, and just maps to g_cclosure_marshal_VOID__POINTER anyway) and incorrect entry in the marshal_table of dbus-glib, and we get the error message as above: GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed when g_cclosure_marshal_VOID__POINTER is called, and then everything dies because object_path is NULL. I think the best fix to this would be to just remove the marshaller registration in ubuntuone-client/libsyncdaemon/syncdaemon- authentication.c. (tested a rebuild with it commented out and no crash, but I don't use ubuntuone so didn't test any of that code, but again, it should be unnecessary since it just maps to a standard marshaller). ** Also affects: ubuntuone-client (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/908787 Title: nautilus crashed with SIGSEGV in g_str_hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/908787/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 908787] Re: nautilus crashed with SIGSEGV in g_str_hash()
I can reproduce this in precise as well. Here is a slightly better backtrace: 1) gdb nautilus 2) run Computer:// 3) Double click a partition in the nautilus window 4) Following backtrace: (gdb) run Computer:// Starting program: /usr/bin/nautilus Computer:// [Thread debugging using libthread_db enabled] [New Thread 0xb68feb70 (LWP 14782)] [New Thread 0xb60fdb70 (LWP 14783)] [New Thread 0xb58d3b70 (LWP 14784)] Initializing nautilus-gdu extension GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed Program received signal SIGSEGV, Segmentation fault. g_str_hash (v=0x0) at /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c:1661 1661/build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c: No such file or directory. in /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c (gdb) bt #0 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c:1661 #1 0xb7374a38 in g_hash_table_lookup_node (hash_return=synthetic pointer, key=0x0, hash_table=0x8783ee8) at /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c:385 #2 g_hash_table_lookup (hash_table=0x8783ee8, key=0x0) at /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c:1058 #3 0xb50493b9 in gdu_pool_get_by_object_path (pool=0x832acf0, object_path=0x0) at gdu-pool.c:2217 #4 0xb50479b6 in device_changed_signal_handler (proxy=0x87e4090, object_path=0x0, user_data=0x832acf0) at gdu-pool.c:1528 #5 0xb7444f8a in g_cclosure_marshal_VOID__POINTER (closure=0x87ce5a0, return_value=0x0, n_param_values=2, param_values=0x87ec5c0, invocation_hint=0xbfffee90, marshal_data=0x0) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gmarshal.c:609 #6 0xb502017a in marshal_dbus_message_to_g_marshaller (closure=0x87ce5a0, return_value=0x0, n_param_values=3, param_values=0x87d4048, invocation_hint=0xbfffee90, marshal_data=0x0) at dbus-gproxy.c:1734 #7 0xb7442dac in g_closure_invoke (closure=0x87ce5a0, return_value=0x0, n_param_values=3, param_values=0x87d4048, invocation_hint=0xbfffee90) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gclosure.c:774 #8 0xb74540c5 in signal_emit_unlocked_R (node=0x82be698, detail=2861, instance=0x87e4090, emission_return=0x0, instance_and_params=0x87d4048) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3302 #9 0xb745b942 in g_signal_emit_valist (instance=0x87e4090, signal_id=220, detail=2861, var_args=0xb044 ) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3033 #10 0xb745bad3 in g_signal_emit (instance=0x87e4090, signal_id=220, detail=2861) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3090 #11 0xb5020820 in dbus_g_proxy_emit_remote_signal (message=0x8427ce0, proxy=optimized out) at dbus-gproxy.c:1787 #12 dbus_g_proxy_manager_filter (user_data=0x87c98d0, message=0x8427ce0, connection=optimized out) at dbus-gproxy.c:1354 #13 dbus_g_proxy_manager_filter (connection=0x87d0568, message=0x8427ce0, user_data=0x87c98d0) at dbus-gproxy.c:1195 #14 0xb693e441 in dbus_connection_dispatch () from /lib/i386-linux-gnu/libdbus-1.so.3 #15 0xb50189ad in message_queue_dispatch (source=0x878fb98, callback=0, user_data=0x0) at dbus-gmain.c:90 #16 0xb738528a in g_main_dispatch (context=0x81f3b80) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:2513 #17 g_main_context_dispatch (context=0x81f3b80) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3050 #18 0xb7385695 in g_main_context_iterate (dispatch=1, block=-122090, context=0x81f3b80, self=optimized out) user_data=0x0) at dbus-gmain.c:90 #16 0xb738528a in g_main_dispatch (context=0x81f3b80) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:2513 #17 g_main_context_dispatch (context=0x81f3b80) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3050 #18 0xb7385695 in g_main_context_iterate (dispatch=1, block=-122090, context=0x81f3b80, self=optimized out) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3121 #19 g_main_context_iterate (context=0x81f3b80, block=-122090, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3058 #20 0xb7385771 in g_main_context_iteration (context=0x81f3b80, may_block=1) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3182 #21 0xb753862c in g_application_run (application=0x81c5c08, argc=2, argv=0xb374) at /build/buildd/glib2.0-2.31.4.tested/./gio/gapplication.c:1548 #22 0x08067ae4 in ?? () #23 0xb7178113 in __libc_start_main (main=0x8067a20, argc=2, ubp_av=0xb374, init=0x8158bd0, fini=0x8158c40, rtld_fini=0xb7feebc0, stack_end=0xb36c) at libc-start.c:226 #24 0x08067b1d in ?? () Backtrace stopped: Not enough registers or memory available to unwind further The NULL object_path above when libgdu receives the DeviceChanged signal from udisks seems to be the cause, but interestingly, running: dbus-monitor --system
[Bug 821511] Re: gsettings man page does not exist.
*** This bug is a duplicate of bug 817944 *** https://bugs.launchpad.net/bugs/817944 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #817944, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 817944 gsettings.1.gz contains only 1 line -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/821511 Title: gsettings man page does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/821511/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 800215] Re: alacarte object has no attribute 'startswith'
** Changed in: alacarte (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/800215 Title: alacarte object has no attribute 'startswith' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/800215/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 800215] Re: alacarte object has no attribute 'startswith'
Marking this as confirmed. The gnome-menus package includes a patch that renames /etc/xdg/menus/applications.menu to gnome-applications.menu. Including a minimal patch that allows alacarte to run. However it is possible for tree.get_menu_file() to return None if both ~/.config/menus /gnome-applications.menu and /etc/xdg/menus/gnome-applications.menu are missing, and alacarte should probably check for this and handle it gracefully. This will not fix the problem of the Applications menu being empty. Copying ~/.config/menus/gnome-applications.menu back to applications.menu will populate the menu, so it seems gnome-panel doesn't handle this change yet either. There is a bug for this: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/798951 ** Patch added: rename-menu.patch https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/800215/+attachment/2177507/+files/rename-menu.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/800215 Title: alacarte object has no attribute 'startswith' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/800215/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 798951] Re: Applications menu fails to open due to change to /etc/xdg/menus/gnome-applications.menu
Marking as confirmed. Rebuilt with the following patch, which just renames all of the applications.menu references, and it seems to be working. ** Patch added: panel-rename-menu.patch https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/798951/+attachment/2177585/+files/panel-rename-menu.patch ** Changed in: gnome-panel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/798951 Title: Applications menu fails to open due to change to /etc/xdg/menus/gnome- applications.menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/798951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 654867] [NEW] gedit python console NameError when changing colors
Public bug reported: Binary package hint: gedit In Maverick gedit-2.30.3-1ubuntu1: When configuring the Python Console plugin, changing the Command Color results in a python NameError: Traceback (most recent call last): File /usr/lib/gedit-2/plugins/pythonconsole/config.py, line 129, in on_colorbutton_command_color_set self.config.color_command = colorbutton.get_color().to_string() File /usr/lib/gedit-2/plugins/pythonconsole/config.py, line 59, in lambda lambda self, value: self.gconf_set_str(GCONF_KEY_COMMAND_COLOR, value)) File /usr/lib/gedit-2/plugins/pythonconsole/config.py, line 81, in gconf_set_str v = PythonConsoleConfig.gconf.Value(gconf.VALUE_STRING) NameError: global name 'gconf' is not defined This can be fixed by including the prefix PythonConsoleConfig. to two of the gconf references in /usr/lib/gedit-2/plugins/pythonconsole/config.py . A patch will be attached. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gedit 2.30.3-1ubuntu1 [modified: usr/lib/gedit-2/plugins/pythonconsole/config.py] ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Oct 4 17:51:49 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gedit ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- gedit python console NameError when changing colors https://bugs.launchpad.net/bugs/654867 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 654867] Re: gedit python console NameError when changing colors
** Patch added: gedit-pythonconsole-gconf.patch https://bugs.launchpad.net/bugs/654867/+attachment/1672331/+files/gedit-pythonconsole-gconf.patch ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/654867/+attachment/1672332/+files/Dependencies.txt -- gedit python console NameError when changing colors https://bugs.launchpad.net/bugs/654867 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
