[Bug 1506744] Re: Newly installed applications do not show in the dash
To elaborate on the previous remark: why didn't we just replace: menu_monitor_queue_event (event_info); with: g_timeout_add_seconds (2, menu_monitor_queue_event, event_info); (and make sure menu_monitor_queue_event() returns FALSE)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
The latest patch looks good to me, but with a couple of notes (no need to fix these): - using the _full() version of the timeout call is not necessary here - now that this patch is simplified it becomes easy to see how all of this is just putting values into one structure and then later moving them into another structure. It seems like we could have just used the first structure type, or even just fixed the other queue mechanism to add the delay. Oh well. No real gain from making that change at this point. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
The patch in comment 42 is not acceptable, for two big reasons. First: you need to hold a ref on the GFile object when you put it into the info struct. This means that you cannot simply use g_free for the struct: you need to write a custom free func that handles the unref as well. Also: you can't cast g_source_remove() to a GDestroyNotify and expect that to work... one takes a pointer, and the other an int. This may randomly work on some architectures, sometimes, but you cannot rely on this. The entire act of keeping the list is slightly suspect. At the sprint I think I mentioned that it would be better to have one global timeout that is set (and reset) when any activity happens. The timeout would run after the activity died down, and it would handle all things together in one go. In that case, you'd still need a list, except for the info objects themselves. It's also fine to keep the list of the timeout IDs, but you can't free it in the way that you're doing in the current patch. Another nice approach, if you want to avoid running the callbacks after teardown: store a weak pointer to the main object in each of the info structs (g_object_add_weak_pointer). The info structs are then used as the user_data to the timeout (this assumes you keep the multiple timeouts). If you find the weak pointer to be empty, then just return without doing anything. That also means that you don't need to handle the "cleanup" -- it will happen automatically. It also means that you can avoid the custom free function if you are clever: the timeout will always run once, and you can do the cleanup from the normal handler (taking care regarding the early exit discussed above). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1383486] Re: menu to select zoom doesn't drop down
This was fixed upstream here: https://git.gnome.org/browse/gtk+/commit/?id=a1af365566161067c4eb246a1c66e7914f119537 Unfortunately this doesn't backport cleanly. I'll try to rebase the patch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1383486] Re: menu to select zoom doesn't drop down
It will work if we also take 0dcffe3cd421555926e74002d5297d6dac0886e7, which is another bugfix that may be worth having. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1383486] Re: menu to select zoom doesn't drop down
Both have been pushed upstream on gtk-3-12 branch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
GLib completely changed the implementation of GMutex from being based on POSIX primatives to being based on a home-grown solution that is substantially faster (and with room for further improvements). This caused deadlocks/crashes in some Vala programs, and I wonder if the same thing is going on with Mono. See this bug: https://bugzilla.gnome.org/show_bug.cgi?id=733500 ** Bug watch added: GNOME Bug Tracker #733500 https://bugzilla.gnome.org/show_bug.cgi?id=733500 -- 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/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
The new mutex implementation detects the (error) case when you try to unlock a mutex that is not locked. Callers are supposed to acquire the Gtk lock before calling gtk_main() and I guess gnome-do isn't doing that... POSIX silently ignores this... -- 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/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
Invalid for glib since the bug is confirmed as being in gnome-do (not acquiring the lock before gtk_main). ** Changed in: glib2.0 (Ubuntu) Status: New = Invalid -- 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/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
** Also affects: do Importance: Undecided Status: New -- 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/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/do/+bug/1344386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296233] Re: increase in number of wakeups in recent release in indicator-datetime
This is my fault indeed. I introduced the code that added this watch without remembering that it does the wrong thing in the case of missing directories. I think the correct fix here is to reevaluate our approach to dealing with missing files in the inotify monitor... -- 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/1296233 Title: increase in number of wakeups in recent release in indicator-datetime To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1296233/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284647] Re: gsettings crashed with SIGSEGV in g_settings_backend_dispatch_signal()
Confirmed GLib bug: https://bugzilla.gnome.org/show_bug.cgi?id=710367 ** Bug watch added: GNOME Bug Tracker #710367 https://bugzilla.gnome.org/show_bug.cgi?id=710367 -- 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/1284647 Title: gsettings crashed with SIGSEGV in g_settings_backend_dispatch_signal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1284647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free
This is not the same as the error we were seeing before: that error was an invalid read on memory that was just before a piece of memory that was allocated through the slice allocator. There is no gslice in this trace... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1246516 Title: Memory from slice allocator passed to PyObject_Free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1246516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222053] Re: per-session gsettings overrides
Worth noting that it's already possible to add new directories to the schema search path via GSETTINGS_SCHEMA_DIR. -- 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/1222053 Title: per-session gsettings overrides To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1222053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 922968] Re: shouldn't queue a second suspend if the machine is already suspending
hi James, Unfortunately we handle suspend in a much more ad-hoc way on precise. There is no logind or systemd-shim through which all suspend requests are handled. These changes are therefore not really possible to backport. -- 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/922968 Title: shouldn't queue a second suspend if the machine is already suspending To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 922968] Re: shouldn't queue a second suspend if the machine is already suspending
We fixed this issue in saucy by moving responsibility for handling suspend into systemd-shim and adding a check there to ignore suspend requests that come in during a very small window after waking up. From personal reports, this has solved the issue for everyone who has tried it. I'm not totally happy with the solution -- I would prefer if we had one based on the timestamps of the source of the suspend (ie: clicking a menu item with the mouse, lid-close events, etc) and were able to compare that with the time of the suspend itself. This requires some changes to logind, though. This has been discussed with upstream and we're waiting. -- 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/922968 Title: shouldn't queue a second suspend if the machine is already suspending To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159036] Re: gedit 3.7 doesn't display application menu
*** This bug is a duplicate of bug 999827 *** https://bugs.launchpad.net/bugs/999827 This is an old bug in the appmenu indicator. gedit gives an appmenu via GMenu but also has oldschool GtkMenu menus for the menubar. Unity can't deal with both of these at the same time. ** This bug has been marked a duplicate of bug 999827 App menus aren't shown in the panel if the app is also exporting menus via dbusmenu -- 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/1159036 Title: gedit 3.7 doesn't display application menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1159036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1154370] [NEW] [precise SRU] crash due to improper handling of / in GSettings
Public bug reported:
GSettings in GLib 2.32.3 has a bug where the changed signal is emitted
for child settings objects as if they were keys ending with /.
That was fixed upstream and merged into the glib-2-32 stable branch
here:
https://git.gnome.org/browse/glib/commit/?h=glib-2-32id=e6f659a898595ba944bd02f0509b14694d1c26e7
GLib 2.32.4 was since released and contains the fix.
This fix is needed because there exists software (muffin) that contains
code along these lines:
void
change_event_handler (GSettings *settings, const gchar *key, gpointer user_data)
{
...
g_settings_get_value (settings, key);
...
}
and it's invalid to pass a key containing / to g_settings_get_value()
(causing crashes).
This only happens when entire paths are reset (such as when running
'dconf update'). That makes the issue relatively rare but it's
affecting corporate deployments (Google, specifically).
We should either do an SRU with just the patch linked to above to
(ideally) QA and SRU the entire GLib 2.32.4 release to precise.
** Affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: ubuntu = glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
Milestone: None = precise-updates
--
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/1154370
Title:
[precise SRU] crash due to improper handling of / in GSettings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1154370/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153567] Re: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code
Note also that this depends on the systemd-shim MIR being approved: bug 1153633 -- 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/1153567 Title: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153567/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153567] Re: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code
You need to ensure that you manually install the PPA versions of all 5 components listed above (since at least one of them is out of date in the PPA at the time of writing). Also need to install systemd-shim (which will eventually make it into at least a recommends of ubuntu- desktop at some point, I assume). -- 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/1153567 Title: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153567/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Ready to go, imho. Marga: one tiny point that I missed the first time around. GObject signals are nominally written like signal-name rather than signal_name. Your patch is fine as-is -- it's mostly a matter of style in this case. -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Functionally, the patch looks pretty good to me. Thanks for the attention to detail with respect to the signal disconnection. One small detail is that the function you introduce should be marked 'static' (since it is not used outside of the current file). Otherwise, everything else looks fine. A comment about why this function exists is probably also reasonable since it's non-obvious from just looking at it. -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
The issue specifically: 'dconf update' emits a signal that says everything has changed Meanwhile, we have the configuration migration stuff watching for changes and assuming that if there was a change in dconf it means that we should sync it up to gconf. The trouble comes that everything has changed actually only means everything has *potentially* changed. One way we can work around this is the change-event signal on GSettings. It allows two things: 1) We can find out the difference between everything changed and one thing changed. 2) We can return TRUE here to stop the signal from going further. -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1070905] [NEW] a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema
Public bug reported: We have a patch in the control-centre that depends on a schema that may not be installed (if overlay scrollbars have been removed). This causes the entire control centre to crash when trying to open the a11y panel if overlay scrollbars have been uninstalled (which is something particularly likely to be done by a user requiring a11y features, since overlay scrollbars are known to cause issues for these users). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1070905 Title: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1070905] Re: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema
hi Will, Two notes: 1) you don't need to set this variable to NULL -- it will already be NULL by virtue of being in a GObject priv structure. 2) the code further down calls g_settings_set() on the object without first checking if it will be NULL, so in the case that you don't do g_settings_new() there will be a crash (or probably at least critical) there. -- 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/1070905 Title: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044322] Re: indicator-messages-service crashed with assert in g_menu_exporter_name_vanished()
Fixed upstream here: http://git.gnome.org/browse/glib/commit/?id=3766b7b5cd0f22d2773c7efc8b52fc2f214d0372 Distro backport coming soon... -- 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/1044322 Title: indicator-messages-service crashed with assert in g_menu_exporter_name_vanished() To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1044322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1058250] Re: conditionalise empathy u-o-a dependency
This is empathy 3.5.92-0ubuntu2 in Q. ** Changed in: empathy (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1058250 Title: conditionalise empathy u-o-a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1058250] [NEW] conditionalise empathy u-o-a dependency
Public bug reported: Empathy currently has a hard dependency on ubuntu-online-accounts. ubuntu-online-accounts is currently not working. A workaround is to directly run empathy-accounts from the commandline, but this is hardly discoverable. Ideally, we should only have this patch butchery enabled when running under Unity and disabled otherwise (ie: you get the normal Empathy accounts dialog). Also: Empathy (via ubuntu-online-accounts) currently hard-depends on libqt, which is just a little bit odd... ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1058250 Title: conditionalise empathy u-o-a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 968268] Re: Cannot permanently add wallpaper to 'Pictures Folder'
Seb: we discussed this on IRC a few weeks ago and I mentioned that this is a known and intended side effect. Also note that the wallpaper is never really added to the pictures folder -- just to a cache directory that appears under Pictures Folder in the UI (which is a bit of a lie, imho). It is my understanding that the existing behaviour (after the patch) is the correct behaviour and that if you set an image as your wallpaper then you should not delete it after. -- 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/968268 Title: Cannot permanently add wallpaper to 'Pictures Folder' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/968268/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 974938] Re: Process gsettings prevents logging in
Looking at these traces I have a hard time beleiving this is a glib/gsettings problem. It rather looks like some deadlock between fork() and the ldap nss module... -- 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/974938 Title: Process gsettings prevents logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 974938] Re: Process gsettings prevents logging in
Can you get a backtrace of the stuck gsettings process? -- 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/974938 Title: Process gsettings prevents logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 965493] Re: cpu race between nautilus, hud- and unity-service
Fix is committed upstream now too. -- 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/965493 Title: cpu race between nautilus, hud- and unity-service To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/965493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 915241] Re: Update menubar patches
updated patch ** Patch added: 043_ubuntu_menu_proxy.patch https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/915241/+attachment/2669362/+files/043_ubuntu_menu_proxy.patch -- 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/915241 Title: Update menubar patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/915241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 730183] Re: evince crashed with SIGSEGV in getenv()
Is it possible that setenv() is being called from another thread? This could end up being a huge can of worms -- all of our libraries do things like calling into gettext() from random arbitrary worker threads and gettext() calls (thread-unsafe) getenv(). In effect, it's not safe to call setenv() from any program that uses GLib, which is a bit scary. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/730183 Title: evince crashed with SIGSEGV in getenv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/730183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334865] Re: gvfsd-trash crashed with SIGSEGV in IA__g_file_equal()
i'm quite certain this is the same as bug 332554 that '??' appearing in the stack trace is almost certainly dir_watch_parent_changed() since this is a signal handler that calls g_file_equal(). -- gvfsd-trash crashed with SIGSEGV in IA__g_file_equal() https://bugs.launchpad.net/bugs/334865 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 333791] Re: gvfsd-trash crashed with SIGSEGV in g_closure_invoke()
it's calling g_vfs_job_failed_from_error with error == NULL. -- gvfsd-trash crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/333791 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 333791] Re: gvfsd-trash crashed with SIGSEGV in g_closure_invoke()
which is because trash_item_restore NEVER EVER EVER sets error. *doh* will have a patch for this quite soon :) -- gvfsd-trash crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/333791 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332554] Re: gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a()
Ok. Fixed upstream... I hope :) (gvfs svn revision 2261) -- gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a() https://bugs.launchpad.net/bugs/332554 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332554] Re: gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a()
i have some approximate idea of what the problem is and i can reproduce a variant of this bug. it's an insane logic problem and i have to think about it a little more. i'll have a fix in a little while. -- gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a() https://bugs.launchpad.net/bugs/332554 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 325701] Re: gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
Thanks for your reply. I'm going to assume, then, that this is a duplicate of #318661. If you get any additional crashers please report them. Cheers ** Changed in: gvfs (Ubuntu) Status: Triaged = Fix Released -- gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2() https://bugs.launchpad.net/bugs/325701 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 325701] Re: gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
Hi Bogdan If you can remember: how long had you been logged in when the crash occurred? Although this is flagged as being a crasher in version 1.1.5, I am suspicious of the accuracy of that information. Séb packaged 1.1.5 on the 2nd and this bug is reported on the 5th. Even if you are very good about doing updates, I guess it wouldn't be until the 3rd or 4th until you had 1.1.5 on your machine. If you had been logged in from before that time then you would have actually been running 1.1.4 (or earlier). 1.1.4 had a known heap corruption bug in it that was fixed in 1.1.5. If you were really running 1.1.5 then this is another bug still unsolved. If you were using 1.1.4 or earlier, though, then I'd like to close this bug as it is very likely already fixed. Cheers -- gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2() https://bugs.launchpad.net/bugs/325701 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 323321] Re: Emptying deleted symbolic links in Trash deletes folder contents.
The bug was in gvfs. ** Changed in: nautilus (Ubuntu) Status: New = Invalid -- Emptying deleted symbolic links in Trash deletes folder contents. https://bugs.launchpad.net/bugs/323321 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201786] Re: ssh Agent admitted failure to sign using the key
I have this problem on my computer at work but on none of my other computers. Two things that are unique about my work computer compared to the others 1) It has been upgraded many times (since breezy, I think) 2) It is non-Intel (PowerPC). Is everyone else here falling under one or both of these categories? Perhaps it will help find the cause -- ssh Agent admitted failure to sign using the key https://bugs.launchpad.net/bugs/201786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 181893] Re: clicking on an https link when the remote site has invalid credentials does not work
this happens for me too, on hardy. even going directly to a site with invalid security information (by typing the https:// url into the address bar) doesn't work at all. it's as if the hook from gecko into epiphany to show the are you sure? dialog is broken. ** Changed in: epiphany-browser (Ubuntu) Status: Incomplete = New -- clicking on an https link when the remote site has invalid credentials does not work https://bugs.launchpad.net/bugs/181893 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 141120] omg insane evolution plugin overload!!
Public bug reported: just installed gutsy evolution, out of the box, has about a million evolution plugins installed -- all of which are enabled. this makes evolution slow and more prone to crashes i've disabled just about all of them now, but it'd be nice if the majority were disabled by default. some examples of particularly comical enabled-by-default plugins: - spam filtering ones: don't almost all ISPs do this now? - copy tool - A test plugin which demonstrates a popup menu plugin which lets you copy things to the clipboard. - default mail client - bug you on startup if you decided to make evo not your default - face - attach a face pixmap to outgoing email (glad i haven't accidentally sent any mail since i installed gutsy...) - mail notification -- i just personally find this one excessively annoying and there's no obvious option in the preferences to disable it - mark all read - mark all messages in a folder as read (if you don't like to do the select-all thing, i guess?) - various groupwise and exchange stuff -- not used by the vast majority of people and easily-enabled by those who know they need it - prefer plain text -- i kid you not: This plugin is unsupported demonstration code only. and enabled by default ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- omg insane evolution plugin overload!! https://bugs.launchpad.net/bugs/141120 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57784] Re: after xrandr desktop icons can go missing
*mumble* Yes. The problem still exists. ** Changed in: nautilus (Ubuntu) Status: Rejected = Confirmed -- after xrandr desktop icons can go missing https://launchpad.net/bugs/57784 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92614] vrms doesn't like to tango
Public bug reported: Binary package hint: tango-icon-theme [EMAIL PROTECTED]:~$ vrms Non-free packages installed on acquiesce tango-icon-theme Tango Icon theme 1 non-free packages, 0.1% of 1435 installed packages. ** Affects: tango-icon-theme (Ubuntu) Importance: Undecided Status: Unconfirmed -- vrms doesn't like to tango https://launchpad.net/bugs/92614 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 70368] Re: bug-buddy can block 'x-session-manager', preventing new X processes
I had this problem too and just filed directly upstream. Dan Winship has proposed a fix to bug buddy to make it avoid registering for session management (thus breaking the loop). -- bug-buddy can block 'x-session-manager', preventing new X processes https://launchpad.net/bugs/70368 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84324] bogus recently used file causes endless loop of crashes
Public bug reported: Binary package hint: libgtk2.0-0 more recently used badness causing the panel to crash there are other bugs like this but they've all been closed (some saying this is fixed for dapper). this one is happening in up-to-date edgy right now. copy this text to your ~/.recently-used.xbel file and watch it go! ?xml version=1.0 encoding=UTF-8? xbel version=1.0 xmlns:bookmark=http://www.freedesktop.org/standards/desktop-bookmarks; xmlns:mime=http://www.freedesktop.org/standards/shared-mime-info; bookmark href=file:///home/desrt/code/desrt/panel/doc/html/panelobject.html#PANEL-OBJECT-GET-PATH added=2007-02-10T04:59:57Z modified=2007-02-10T04:59:57Z visited=2007-02-10T04:59:57Z info metadata owner=http://freedesktop.org; mime:mime-type type=text/html/ bookmark:groups bookmark:groupgedit/bookmark:group /bookmark:groups bookmark:applications bookmark:application name=gedit exec=gedit %u timestamp=1171083597 count=1/ /bookmark:applications /metadata /info /bookmark /xbel ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: Unconfirmed -- bogus recently used file causes endless loop of crashes https://launchpad.net/bugs/84324 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41931] Re: Copying files from OS X causes errors with icon files
*** This bug is a duplicate of bug 18562 *** ** This bug has been marked a duplicate of bug 18562 nautilus gives perplexing error message while copying some files to vfat -- Copying files from OS X causes errors with icon files https://launchpad.net/bugs/41931 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 56610] Re: Automatic search from address entry doesn't work anymore
superficially, it works. -- Automatic search from address entry doesn't work anymore https://launchpad.net/bugs/56610 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63025] Re: MacBook doesn't dim monitor on battery
*** This bug is a duplicate of bug 72287 *** ** This bug has been marked a duplicate of bug 72287 Apple MacBook backlight brightness doesn't work -- MacBook doesn't dim monitor on battery https://launchpad.net/bugs/63025 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 61502] Re: Macbook backlight support
*** This bug is a duplicate of bug 72287 *** ** This bug is no longer a duplicate of bug 63025 MacBook doesn't dim monitor on battery ** This bug has been marked a duplicate of bug 72287 Apple MacBook backlight brightness doesn't work -- Macbook backlight support https://launchpad.net/bugs/61502 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 72287] Re: Apple MacBook backlight brightness doesn't work
It turns out that on suspend/resume, the backlight control register is clobbered to all-zeros. The only way to fix this is to use vbetool to save/restore the BIOS state. This is currently broken on the macbook due to the init scripts being out of order (vbesave runs before acpid, and on macbook this causes vbesave to fail to detect that we're a laptop). There is, however, another fix. The attached program (which is a hackish modification of part of the patch submitted upstream) will reset the value of the register. This seems to be sufficient to get the card working properly again (ie: no need for a full vbetool state restore). Link with -lpci. This code needs to be somewhere -- be it in the kernel, the X server, HAL or the system resume scripts -- but only run for Macbooks. I'm guessing that for now, HAL or system resume scripts is the easy answer. Also: to do this properly we should probably look at the value of the backlight at suspend, save this value, then write the same value back on resume. The current code just sets to max value on resume. David is currently romping around in the aussie outback. I'll try to nail him down to find out what he thinks :) ** Attachment added: unclobber the backlight register on resume http://librarian.launchpad.net/5827146/fixbacklight.c -- Apple MacBook backlight brightness doesn't work https://launchpad.net/bugs/72287 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63025] Re: MacBook doesn't dim monitor on battery
*** This bug is a duplicate of bug 72287 *** no. the macbook backlight support definitely won't work on any ubuntu live cd that has yet been released. -- MacBook doesn't dim monitor on battery https://launchpad.net/bugs/63025 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 72287] Re: Apple MacBook backlight brightness doesn't work
Hi Martin Patch is written and has been sent upstream. David has said that he will try to make a release in the coming weeks, so should be good to go for feisty. Cheers ** Bug watch added: Freedesktop Bugzilla #9702 https://bugs.freedesktop.org/show_bug.cgi?id=9702 ** Also affects: hal (upstream) via https://bugs.freedesktop.org/show_bug.cgi?id=9702 Importance: Unknown Status: Unknown -- Apple MacBook backlight brightness doesn't work https://launchpad.net/bugs/72287 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 72287] Re: Apple MacBook backlight brightness doesn't work
Hi Martin I'm more or less using what I describe on that page. I'm working on a better solution for the longterm. Maybe I'll get some time to hack on it this week at the conference. (I wouldn't be suprised if I don't, though) :) I'll keep you posted. -- Apple MacBook backlight brightness doesn't work https://launchpad.net/bugs/72287 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 22606] Re: the panel calendar applet treats 'all day' appointments incorrectly
yes. ** Changed in: gnome-panel (Ubuntu) Status: Needs Info = Confirmed -- the panel calendar applet treats 'all day' appointments incorrectly https://launchpad.net/bugs/22606 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 71264] patch to get better backtraces
Public bug reported: Binary package hint: bug-buddy use this. ** Affects: bug-buddy (Ubuntu) Importance: Undecided Status: Unconfirmed -- patch to get better backtraces https://launchpad.net/bugs/71264 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 71264] Re: patch to get better backtraces
and then modify /usr/share/bug-buddy/gdb-cmd to read like this: signal SIGTRAP bt thread apply all bt full q ** Attachment added: foo. http://librarian.launchpad.net/5041870/libgnomeui-crash.patch -- patch to get better backtraces https://launchpad.net/bugs/71264 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 61186] system-tools-backends abuses the timers in a big way
Public bug reported: Binary package hint: system-tools-backends 20 wakeups per second from the system-tools-backends perl script. caused by this line in /usr/share/system-tools- backends-2.0/scripts/SystemToolsBackends.pl Net::DBus::Reactor-main-add_timeout (50, Net::DBus::Callback-new(method = \Utils::Monitor::do_monitor_files)); every 50 milliseconds. crikey! since ubuntu doesn't even have Sys::Gamin, this results in a call to a handler that returns immediately (so it's entirely useless). a fix for this problem is to comment that line out. see upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=356649 ** Affects: gst (upstream) Importance: Unknown Status: Unknown ** Affects: system-tools-backends (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Confirmed -- system-tools-backends abuses the timers in a big way https://launchpad.net/bugs/61186 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45173] Re: invalid semantic overloading of gnome-logout icon in Human theme
Daniel: does the activity on this bug mean that you're reconsidering it? :) -- invalid semantic overloading of gnome-logout icon in Human theme https://launchpad.net/bugs/45173 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57784] after xrandr desktop icons can go missing
Public bug reported: Binary package hint: nautilus 1) Do xrandr -o left 2) Enjoy your rotated desktop for a bit. Make sure to move some icons to the bottom of the screen. 3) Get bored of this. 4) xrandr -o normal. The icons that you moved to the bottom are gone now. You have no way to get them back except clean up by name. When the size of the desktop changes nautilus should bring the icons back within the limits of the desktop. ** Affects: nautilus (Ubuntu) Importance: Untriaged Status: Unconfirmed -- after xrandr desktop icons can go missing https://launchpad.net/bugs/57784 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 56738] Re: Thumbnailing slows copying files
wow. i got bit by this just yesterday but had no idea what was causing it. this bug is incredibly evil. -- Thumbnailing slows copying files https://launchpad.net/bugs/56738 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 54445] Re: [edgy] Gaim crashes when I click on save icon
This is probably the same as the muine crasher. Essentially: dbus locking has two states: initialised and not If it's not initialised then the function to allocate a lock returns a bogus value (0xabcdef) and the lock and unlock functions are no-ops. If it's initialised then the new function returns real values and the lock and unlock functions actually use those values. The problem is the following sequence: 1) Allocate a lock (get pointer 0xabcdef). 2) Initialise locking 3) Use your lock from (1) Because you're using the real locking function with the bogus (0xabcdef) pointer, you get a crash. A workaround is to make sure that locking is initialised very early in your application. This can be done with dbus_g_thread_init or even by simply doing GnomeVFS initialisation early (since this does the thread init for you). -- [edgy] Gaim crashes when I click on save icon https://launchpad.net/bugs/54445 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 54261] every single gtk app wakes up on button or modifier key press
Public bug reported: Binary package hint: libgtk2.0-0 i reported this bug to mclasen at guadec. he fixed it very rapidly in gtk 2.9. upstream bug is here: http://bugzilla.gnome.org/show_bug.cgi?id=346079 12:28 desrt mclasen; i imagine it wouldn't be very hard to cherry-pick your xkb fix out of gtk 2.9 and stick it in dapper? 12:29 mclasen desrt: I'm sure seb can handle it 12:29 mclasen its a one-line fix the patch is here: http://cvs.gnome.org/viewcvs/gtk%2B/gdk/x11/gdkdisplay-x11.c?r1=1.73r2=1.74 ** Affects: gtk+2.0 (Ubuntu) Importance: Untriaged Status: Unconfirmed -- every single gtk app wakes up on button or modifier key press https://launchpad.net/bugs/54261 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 54261] Re: every single gtk app wakes up on button or modifier key press
this will have a small effect on battery performance on laptops but not too much. it's probably worth including only if doing another libgtk release for another reason. that said, it would personally make my life easier (and the lives of other people stracing their apps to find out if they wake up inappropriately). -- every single gtk app wakes up on button or modifier key press https://launchpad.net/bugs/54261 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39024] Re: [Dapper] Gedit fails to save to remote location if creating new file while using sftp
It looks like upstream has rewritten a bunch of that code. Near as I can tell their rewrite addresses the issue. -- [Dapper] Gedit fails to save to remote location if creating new file while using sftp https://launchpad.net/bugs/39024 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45918] sftp module can't handle partially valid hostkeys, gives confusing error
Public bug reported: [EMAIL PROTECTED]:~$ ssh vanilla Warning: the RSA host key for 'vanilla' differs from the key for the IP address '71.19.4.161' Offending key for IP in /home/desrt/.ssh/known_hosts:91 Matching host key in /home/desrt/.ssh/known_hosts:95 Are you sure you want to continue connecting (yes/no)? yes [EMAIL PROTECTED]'s password: If I have this sort of error when connecting to a host over ssh then trying to open a nautilus window with sftp://vanilla/ locks for a while (30 seconds?) and then pops up this strange dialog: Could not open location 'sftp://vanilla/home/ian' Details: Unknown error code: 46 ** Affects: gnome-vfs2 (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- sftp module can't handle partially valid hostkeys, gives confusing error https://launchpad.net/bugs/45918 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39024] Re: [Dapper] Gedit fails to save to remote location if creating new file while using sftp
** Attachment added: new version http://librarian.launchpad.net/2758978/gnome-vfs-0ubuntu8.debdiff -- [Dapper] Gedit fails to save to remote location if creating new file while using sftp https://launchpad.net/bugs/39024 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45173] Re: invalid semantic overloading of gnome-logout icon in Human theme
This isn't such a problem, as the gnome-shutdown icon exists in other themes (and is even a power switch!) -- invalid semantic overloading of gnome-logout icon in Human theme https://launchpad.net/bugs/45173 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39024] Re: [Dapper] Gedit fails to save to remote location if creating new file while using sftp
The protocol error happens, not on first save, but rather, if the file does not yet exist on the remote host. You can get it to happen by opening a file in gedit, erasing the file on the remote host (logged in, using 'rm') then clicking 'save'. When I do this, however, I don't get an empty file -- the file is actually saved correctly. -- [Dapper] Gedit fails to save to remote location if creating new file while using sftp https://launchpad.net/bugs/39024 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39024] Re: [Dapper] Gedit fails to save to remote location if creating new file while using sftp
The problem is caused by iobuf_read_file_info() in the gnome-vfs sftp
method.
if (id != expected_id || type != SSH2_FXP_ATTRS) {
buffer_free (msg);
return GNOME_VFS_ERROR_PROTOCOL_ERROR;
}
else if (type == SSH2_FXP_STATUS) {
gnome_vfs_file_info_clear (info);
status = buffer_read_gint32 (msg);
buffer_free (msg);
return sftp_status_to_vfs_result (status);
}
Notice that it's actually impossible for the (type == SSH2_FXP_STATUS)
to ever be true and that in this case the PROTOCOL_ERROR is incorrectly
returned.
I've written a patch to move the order of the code around to the logical
order. The patch fixes the problem.
** Changed in: gedit (Ubuntu)
Status: Needs Info = Rejected
** Also affects: gnome-vfs2 (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
** Changed in: gnome-vfs2 (Ubuntu)
Status: Unconfirmed = In Progress
--
[Dapper] Gedit fails to save to remote location if creating new file while
using sftp
https://launchpad.net/bugs/39024
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44579] Re: gnome-screensaver flickers every 30 seconds
** Attachment added: new version to deal with new ubuntuversion number http://librarian.launchpad.net/2735224/stop_30second_flicker.debdiff -- gnome-screensaver flickers every 30 seconds https://launchpad.net/bugs/44579 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44579] Re: gnome-screensaver flickers every 30 seconds
Uploaded by ogra (thanks). ** Changed in: gnome-screensaver (Ubuntu) Status: Unconfirmed = Fix Released -- gnome-screensaver flickers every 30 seconds https://launchpad.net/bugs/44579 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45472] panel sets invalid style on applet handles on startup
Public bug reported: Binary package hint: gnome-panel the panel, on startup, sets the wrong style on the handles of applets. instead of being drawn in a specific colour (if that's the setting you have on your panel) they're drawn with a normal theme (grey) background. this happens in lots of different themes. furthermore, switching themes doesn't fix the problem. the problem can only be fixed by going into panel properties, changing the background type to normal then changing back to the coloured background. ** Affects: gnome-panel (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- panel sets invalid style on applet handles on startup https://launchpad.net/bugs/45472 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45472] Re: panel sets invalid style on applet handles on startup
i should clarify: this only happens when you have a background _colour_ set with no transparency. -- panel sets invalid style on applet handles on startup https://launchpad.net/bugs/45472 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45173] Re: invalid semantic overloading of gnome-logout icon in Human theme
I'm not questioning using this icon. It's a very nice icon and it makes a lot sense to use it for the new logout dialog. If you use it, though, you should name it properly (as gnome-shutdown - since it's a switch). Calling it gnome-logout is conceptually wrong and causes brokenness. It's also sort of weird that we now have two separate switch icons. -- invalid semantic overloading of gnome-logout icon in Human theme https://launchpad.net/bugs/45173 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33002] Re: logout dialog UI objections
I should point out bug 45173 here since it definitely falls into the category of logout dialog UI objection. -- logout dialog UI objections https://launchpad.net/bugs/33002 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45169] gnome-volume-manager running in a background login hijacks hotplugged storage devices
Public bug reported: Binary package hint: gnome-volume-manager 1. log in user 'kiley' 2. switch to new user 3. log in user 'katie' 4. katie plugs in her mp3 player 5. the g-v-m in kiley's session mounts the device, preventing katie from using it. ** Affects: gnome-volume-manager (Ubuntu) Severity: Critical Priority: (none set) Status: Unconfirmed ** Changed in: gnome-volume-manager (Ubuntu) Severity: Normal = Critical -- gnome-volume-manager running in a background login hijacks hotplugged storage devices https://launchpad.net/bugs/45169 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45169] Re: gnome-volume-manager running in a background login hijacks hotplugged storage devices
erp. sorry. just upgraded now :) ** Changed in: gnome-volume-manager (Ubuntu) Status: Unconfirmed = Fix Released -- gnome-volume-manager running in a background login hijacks hotplugged storage devices https://launchpad.net/bugs/45169 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45173] invalid semantic overloading of gnome-logout icon in Human theme
Public bug reported: Binary package hint: ubuntu-artwork The /usr/share/icons/Human/48x48/actions/gnome-logout.png icon has been changed to a power switch to deal with the confusion caused by the Ubuntu logout dialog. Unfortunately, this is semantically broken and the brokenness manifests itself if you have the 'upstream_session' flag set on your panel config. I now have a logout and shutdown item in my panel. The panel correctly displays the logout icon for the logout menu item. However, the icon incorrectly shows a power switch (which would be more suitable for the shutdown item). Suggested fix: restore the logout icon to its previous state (ie: the door with the arrow) and use the new (very pretty, btw) power switch icon to replace the old power switch icon that is currently used for the Shut Down item (gnome/24x24/apps/gnome-shutdown.png). If the 'shutdown' idea is what the designers of the new logout dialog would like to be associated with its entry in the menu then please use gnome-shutdown for this purpose instead of breaking gnome-logout. ** Affects: ubuntu-artwork (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- invalid semantic overloading of gnome-logout icon in Human theme https://launchpad.net/bugs/45173 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44579] gnome-screensaver flickers every 30 seconds
Public bug reported: Binary package hint: gnome-screensaver gnome-screensaver flickers every 30 seconds. if you have a screensaver like Swirl this causes the entire screen to go black until it gets repainted (which takes a while). To see: 1. Use swirl as your screensaver. 2. Lock the screen. 3. Wait 30 seconds. ** Affects: gnome-screensaver (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- gnome-screensaver flickers every 30 seconds https://launchpad.net/bugs/44579 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44579] Re: gnome-screensaver flickers every 30 seconds
Ok. The problem is caused by the so-called watchdog timer. It calls gtk_window_present every 30 seconds. gtk_window_present includes a call to gdk_window_show which causes the flicker. ** Attachment added: debdiff to fix the problem http://librarian.launchpad.net/2619784/stop_30second_flicker.debdiff -- gnome-screensaver flickers every 30 seconds https://launchpad.net/bugs/44579 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44579] Re: gnome-screensaver flickers every 30 seconds
I'm quite positive that it's a gnome-screensaver bug. You can see flickering with other hacks too -- the only different is that with swirl the display is very static and doesn't get updated frequently. The attached patch actually fixes the problem (which, btw does not occur when I do what you describe above). -- gnome-screensaver flickers every 30 seconds https://launchpad.net/bugs/44579 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33002] Re: logout dialog UI objections
The problem you mention is addressed in bug 39371. -- logout dialog UI objections https://launchpad.net/bugs/33002 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12893] Re: Shouldn't put .Trash-$USER on removable devices
Some ideas: 1) Does .Trash-desrt ever have a good purpose? - is created when files are not on same FS as homedir? - is it useful for something like /mnt/windows? - will this clutter up your c:\ drive? - maybe just never create this directory 2) Maybe don't create .Trash-desrt if the drive is on USB. 3) Maybe don't create .Trash-desrt if the drive is smaller than a certain size (2-3GB?) 4) Combination of 23 (so that USB harddrives still get it created). The answer to what should be done probably lies somewhere in the above. -- Shouldn't put .Trash-$USER on removable devices https://launchpad.net/bugs/12893 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39371] Re: fadeout effect on displaying the logout dialog box looks bad
I agree. gksudo is quite fine (I don't get the bug). -- fadeout effect on displaying the logout dialog box looks bad https://launchpad.net/bugs/39371 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 19101] Re: nautilus's clever anti-hax0r detection is really dumb
yes ** Changed in: nautilus (Ubuntu) Status: Needs Info = Confirmed -- nautilus's clever anti-hax0r detection is really dumb https://launchpad.net/bugs/19101 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 19101] Re: nautilus's clever anti-hax0r detection is really dumb
this is definitely different from bug 41772 (but caused by a similar issue -- two different systems for detecting mime type). this bug is much easier to fix and i'm astounded that it hasn't been fixed yet. -- nautilus's clever anti-hax0r detection is really dumb https://launchpad.net/bugs/19101 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41226] the escape key doesn't work in the unlock dialog
Public bug reported: Affects: gnome-screensaver (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: the escape key doesn't work in the unlock dialog sometimes clicking on the cancel button with the mouse also fails (but i can't reproduce this all the time) -- the escape key doesn't work in the unlock dialog https://launchpad.net/bugs/41226 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33002] Re: logout dialog UI objections
Is there any chance of getting the default behaviour changed to match upstream? The upstream solution is very clearly _more sane_ (even if it doesn't have all of the functionality/flash of the Ubuntu one). Some things to keep in mind: - Lock is already on the menu - Suspend/hibernate don't even work for (probably more than) half the people who use Ubuntu - Following upstream goes with the principle of least suprise (and follows the HIG to boot) - This is Dapper - we should try to not be suprising Essentially, I am asking for sane defaults here. -- logout dialog UI objections https://launchpad.net/bugs/33002 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39796] please wait while unmounting dialog ought not to be displayed for CDs
Public bug reported: Affects: nautilus (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: CDs take a while to eject and block while ejecting. this causes the please wait while unmounting dialog to be displayed. this dialog contains some mention of please wait while changes are being written to disc which is very confusing because i don't think that i'm overwriting my CD? maybe I am? uh oh. what have i done?!?! crikey. anyway... the dialog should either not be displayed at all for media that is mounted ro or should have its wording modified. -- please wait while unmounting dialog ought not to be displayed for CDs https://launchpad.net/malone/bugs/39796 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39371] Re: fadeout effect on displaying the logout dialog box looks bad
I don't understand why lowering the brightness has to produce any strage effects. I have a 24bit display and, for example, turning the bightness down on a truecolour image in GIMP would surely not produce strange effects like this. -- fadeout effect on displaying the logout dialog box looks bad https://launchpad.net/malone/bugs/39371 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39371] fadeout effect on displaying the logout dialog box looks bad
Public bug reported: Affects: gnome-panel (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: on certain backgrounds the fadeout effect on the logout dialog box looks really bad. it doesn't fade some colours properly. i'm using the Stars Pattern background from the gnome-backgrounds package with its default colours (vert grad from #332133 to #75507B) ** Attachment added: . http://librarian.launchpad.net/2075643/ugly.jpeg -- fadeout effect on displaying the logout dialog box looks bad https://launchpad.net/malone/bugs/39371 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38800] Re: avidemux crashes on a certain avi file
Patch has been accepted upstream along with a few related fixes. -- avidemux crashes on a certain avi file https://launchpad.net/malone/bugs/38800 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38800] avidemux crashes on a certain avi file
Public bug reported: Affects: gst-plugins-good0.10 (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: this upstream bug affects ubuntu. http://bugzilla.gnome.org/show_bug.cgi?id=337749 ** Bug watch added: AbiSource bug tracker #337749 http://bugzilla.abisource.com//show_bug.cgi?id=337749 ** Bug watch added: GNOME Bug Tracker #337749 http://bugzilla.gnome.org//show_bug.cgi?id=337749 -- avidemux crashes on a certain avi file https://launchpad.net/malone/bugs/38800 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38800] Re: avidemux crashes on a certain avi file
** Attachment added: this is a small patch that fixes the problem for me http://librarian.launchpad.net/1985933/fixer.patch -- avidemux crashes on a certain avi file https://launchpad.net/malone/bugs/38800 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36598] firewire dvd burner fails to coldplug into hal
Public bug reported:
https://launchpad.net/malone/bugs/36598
Affects: hal (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
If I boot my computer with my DVD drive plugged in then HAL fails to
show it in the device list. I get some sort of a strange 'iLink
interface' that I think represents the Firewire interface on the device
but I get no SCSI stuff.
The modules get loaded properly and I have nodes in /dev. I can also see it in
sysfs here:
/sys/bus/ieee1394/devices/08004609000d626e/08004609000d626e-0/host3/target3:0:0/3:0:0:0
If I powercycle the DVD drive (ie: hotplug) then it works. The new sysfs path
is:
/sys/bus/ieee1394/devices/08004609000d626e/08004609000d626e-0/host7/target7:0:0/7:0:0:0
(ie: same, except for the scsi 'host' number)
[EMAIL
PROTECTED]:/sys/bus/ieee1394/devices/08004609000d626e/08004609000d626e-0/host7/target7:0:0/7:0:0:0$
head * 2 /dev/null
== block ==
== bus ==
== device_blocked ==
0
== driver ==
== generic ==
== ieee1394_id ==
08004609000d626e:0:0
== iocounterbits ==
32
== iodone_cnt ==
0xb64
== ioerr_cnt ==
0xa9a
== iorequest_cnt ==
0xb64
== model ==
DVD RW DRU-810A
== power ==
== queue_depth ==
8
== queue_type ==
none
== rev ==
2.0d
== scsi_device:7:0:0:0 ==
== scsi_generic:sg1 ==
== scsi_level ==
0
== state ==
running
== timeout ==
0
== type ==
5
== vendor ==
SONY
and information from lshal (after I've hotplugged again):
udi = '/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e'
info.udi = '/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e'
(string)
linux.subsystem = 'ieee1394' (string)
linux.hotplug_type = 1 (0x1) (int)
info.product = 'iLINK DRIV' (string)
info.vendor = 'SONY CORPORATION LTD.' (string)
ieee1394.product = 'iLINK DRIV' (string)
ieee1394.product_id = 512 (0x200) (int)
ieee1394.vendor = 'SONY CORPORATION LTD.' (string)
ieee1394.version = 66691 (0x10483) (int)
ieee1394.specifier_id = 24734 (0x609e) (int)
ieee1394.vendor_id = 524358 (0x80046) (int)
ieee1394.guid = 576537756772950638 (0x8004609000d626e) (uint64)
info.parent = '/org/freedesktop/Hal/devices/pci_1102_4001' (string)
info.bus = 'ieee1394' (string)
linux.sysfs_path_device =
'/sys/devices/pci:00/:00:1e.0/:02:0c.2/fw-host0/08004609000d626e/08004609000d626e-0'
(string)
linux.sysfs_path =
'/sys/devices/pci:00/:00:1e.0/:02:0c.2/fw-host0/08004609000d626e/08004609000d626e-0'
(string)
udi = '/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e_scsi_host'
info.udi =
'/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e_scsi_host' (string)
linux.subsystem = 'scsi_host' (string)
linux.hotplug_type = 2 (0x2) (int)
scsi_host.host = 7 (0x7) (int)
info.product = 'SCSI Host Adapter' (string)
info.capabilities = {'scsi_host'} (string list)
info.category = 'scsi_host' (string)
info.parent = '/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e'
(string)
linux.sysfs_path_device =
'/sys/devices/pci:00/:00:1e.0/:02:0c.2/fw-host0/08004609000d626e/08004609000d626e-0/host7'
(string)
linux.sysfs_path = '/sys/class/scsi_host/host7' (string)
udi =
'/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e_scsi_host_scsi_device_lun0'
info.udi =
'/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e_scsi_host_scsi_device_lun0'
(string)
linux.subsystem = 'scsi' (string)
linux.hotplug_type = 1 (0x1) (int)
scsi.type = 'cdrom' (string)
scsi.vendor = 'SONY' (string)
scsi.model = 'DVD RW DRU-810A' (string)
info.product = 'SCSI Device' (string)
info.linux.driver = 'sr' (string)
scsi.lun = 0 (0x0) (int)
scsi.target = 0 (0x0) (int)
scsi.bus = 0 (0x0) (int)
scsi.host = 7 (0x7) (int)
info.parent =
'/org/freedesktop/Hal/devices/ieee1394_guid_8004609000d626e_scsi_host' (string)
info.bus = 'scsi' (string)
linux.sysfs_path_device =
'/sys/devices/pci:00/:00:1e.0/:02:0c.2/fw-host0/08004609000d626e/08004609000d626e-0/host7/target7:0:0/7:0:0:0'
(string) linux.sysfs_path =
'/sys/devices/pci:00/:00:1e.0/:02:0c.2/fw-host0/08004609000d626e/08004609000d626e-0/host7/target7:0:0/7:0:0:0'
(string)
udi = '/org/freedesktop/Hal/devices/storage_serial__sysfs_ieee1394_id_'
info.addons = {'hald-addon-storage', 'hald-addon-storage'} (string list)
storage.policy.desired_mount_point = 'dvdrecorder' (string)
storage.policy.mount_filesystem = 'auto' (string)
storage.policy.should_mount = true (bool)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial__sysfs_ieee1394_id_' (string)
info.udi = '/org/freedesktop/Hal/devices/storage_serial__sysfs_ieee1394_id_'
(string)
storage.cdrom.write_speeds = {'7056', '5645', '4234', '2822', '2117'} (string
list)
storage.cdrom.write_speed = 7056 (0x1b90) (int)
storage.cdrom.read_speed = 7056 (0x1b90) (int)
storage.cdrom.support_media_changed = true
[Bug 36598] firewire dvd burner fails to coldplug into hal
Public bug report changed: https://launchpad.net/malone/bugs/36598 Task: ubuntu hal Status: Unconfirmed = Fix Released Comment: Just rebooted with the latest version -- seems to be fixed, k thx. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
