[Bug 1754199] Re: Mounted Volume ICON not displayed on desktop
I am experiencing the same problem on bionic. My system is an upgrade from artful. The NFS shares are mounted at: /media/sharename I don't know whether it is relevant, but I am still using the Unity 7 desktop on bionic. The shortcuts of the NFS mounts were visible in nautilus on artful, where I was also using the Unity 7 desktop. -- 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/1754199 Title: Mounted Volume ICON not displayed on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
** Also affects: onboard 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
As marmuta said above, the auto-show (auto-hide) needs the accessibility framework to be enabled. In fact, it is the accessibility framework that informs onboard about when to appear and hide. Thus, it is not possible to use the auto-show feature without enabling the accessibility framework. We might perhaps add an option Do not ask again to the dialog about enabling the accessibility framework. And if the user enables it, each time Onboard starts up, it would automatically enable the accessibility framework, unless the user enabled the new option and clicked to not enable the accessibility framework. For Till's needs, a corresponding gsettings key without a GUI might even be sufficient. -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041570] [NEW] Executable bit lost when extracting file by dragging them to nautilus
Public bug reported: How to reproduce: - Download Onboard version 0.98.0 from the following web page: https://launchpad.net/onboard/+download - Open the tarball and drag the files that are located in the scripts folder to a nautilus window; the files in the nautilus window have lost the executable bit However, if I extract the tarball by using Ark, the files in the script folder have their executable bit set. Running Ubuntu quantal development branch. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1041570 Title: Executable bit lost when extracting file by dragging them to nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1041570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426675] Re: Left handed mouse settings no longer working after system update
GNOME has switched from gconf to gsettings. It might be well possible that the corresponding key is now handled by gsettings. You can have a look at the gsettings keys by using the dconf-editor. -- 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/426675 Title: Left handed mouse settings no longer working after system update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/426675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 706980] [NEW] Cannot add a separator into a menu
Public bug reported:
Binary package hint: alacarte
As alacarte does not add separators into menus, I launched it from
terminal and here is what I get when I click on the button to create a
separator:
[code]
Traceback (most recent call last):
File /usr/share/alacarte/Alacarte/MainWindow.py, line 325, in
on_new_separator_button_clicked
self.editor.createSeparator(parent, after=after)
File /usr/share/alacarte/Alacarte/MenuEditor.py, line 250, in
createSeparator
self.__positionItem(parent, ('Separator',), before, after)
File /usr/share/alacarte/Alacarte/MenuEditor.py, line 694, in __positionItem
current = parent.contents.index(item)
ValueError: ('Separator',) is not in list
[/code]
Could anybody please have a look at it ?
Thanks
** Affects: alacarte (Ubuntu)
Importance: Undecided
Status: New
--
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/706980
Title:
Cannot add a separator into a menu
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 525735] Re: Mouse accessibility in assistive technologies doesn't work
The user reporting the issue might have wanted to report the issue caused in mousetweaks by some changes to the X server. If so, this bug thread might be closed as this incompatibility with the X server has been fixed in mousetweaks about a month ago: http://git.gnome.org/browse/mousetweaks/commit/?id=d117f069f942dc40b7425d0383b2c56a2b537c03 @tgpraveen Is this bug still an issue for you? -- Mouse accessibility in assistive technologies doesn't work https://bugs.launchpad.net/bugs/525735 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 530430] Re: [lucid] gnome keyboard preferences can't apply system wide
I can confirm the bug; here is how to reproduce it: - Type gnome-keyboard-properties in the terminal to open the Keyboard Preferences - Switch to the layout tab and click on the Apply System-Wide button The terminal displays: Caught remote method exception org.freedesktop.PolicyKit1.Error.Failed: Error parsing subject struct -- [lucid] gnome keyboard preferences can't apply system wide https://bugs.launchpad.net/bugs/530430 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196378] Re: onboard fails to upgrade hardy heron
Hi Vagner, Could you please tell me why you marked this bug as new for onboard? -- onboard fails to upgrade hardy heron https://bugs.launchpad.net/bugs/196378 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426675] Re: Left handed mouse settings no longer working after system update
The issue, about the left handedness of the mouse not working when activated by using the gconf key, does not occur anymore on the development version of Ubuntu lucid. -- Left handed mouse settings no longer working after system update https://bugs.launchpad.net/bugs/426675 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426675] Re: Left handed mouse settings no longer working after system update
I don't know for the touchpad, but it is simple to reproduce the problem for a normal mouse on the current karmic: Simply open the configuration editor and activate the left_handed gconf key and click with the left mouse button some item: the contextual menu does not appear, but the item gets selected as if a primary click occurred instead of a secondary click. However, if I used the Mouse control panel instead of the configuration editor to activate the left handedness of the mouse, the problem does not occur. Finally, I have been told that the problem is fixed in some 2.29.x version in GNOME, but for the moment I have not been able to verify it with Ubuntu lucid, as lucid does not start up properly here. -- Left handed mouse settings no longer working after system update https://bugs.launchpad.net/bugs/426675 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426675] Re: Left handed mouse settings no longer working after system update
It is an accessibility issue: for example, the onscreen keyboard that ships by default with Ubuntu toggles the left handedness gconf key to let the users that can only use one mouse button perform secondary clicks. But it does not work because of the issue described above. As a work around, I assume that these users can keep the Mouse control panel open to toggle the handedness of the mouse. -- Left handed mouse settings no longer working after system update https://bugs.launchpad.net/bugs/426675 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426675] Re: Left handed mouse settings no longer working after system update
The problem is not completely fixed for the mouse either: In fact, it is possible to switch to a left-handed mouse by using the corresponding setting in the mouse control panel and it works. However it does not work if you use the gconf-editor to activate the left-handed gconf key. If you set the mouse to left-handed by using the corresponding gconf key, you can see the setting in the mouse control panel reflecting the change, but the mouse does not behave as a left- handed mouse: for example a click with the left mouse button does not show the contextual menu. I do not know whether it is related to the problem with the touchpad. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Released = New -- Left handed mouse settings no longer working after system update https://bugs.launchpad.net/bugs/426675 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426675] Re: Left handed mouse settings no longer working after system update
Does anybody know whether it is an Ubuntu specific bug or if I should also file a bug for it at bugzilla in GNOME? -- Left handed mouse settings no longer working after system update https://bugs.launchpad.net/bugs/426675 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 439800] Re: Gdm should not ship at-spi-registryd-wrapper.desktop in /usr/share/gdm/autostart/LoginWindow, and at-spi should ship a desktop file in this directory instead.
I can confirm the problem. To solve the problem I just copied the corresponding file from /etc/xdg/autostart -- Gdm should not ship at-spi-registryd-wrapper.desktop in /usr/share/gdm/autostart/LoginWindow, and at-spi should ship a desktop file in this directory instead. https://bugs.launchpad.net/bugs/439800 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 130368] Re: RFE: add an item to options menu to start onscreen keyboard
The new gdm (version 2.26) offers an accessibilty dialog containing an item to start the onscreen keyboard. Ubuntu only has to configure it to use the onscreen keyboard it is shipping. Here is a bug thread about how to do it. https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/423831 -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 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 423831] [NEW] gdm 2.26: a11y should use onboard and not gok that is missing
Public bug reported: Binary package hint: gdm The new GDM (GDM 2.26) offers an Accessibility Dialog to start different assistive tools, among others an onscreen keyboard. By default, GDM is configured to start the onscreen keyboard GOK. However, GOK is not shipped with Ubuntu; the onscreen keyboard named onboard is shipped with Ubuntu. So GDM should be configured to launch onboard instead of GOK when the user activates the onscreen keyboard in the Accessibility Dialog of GDM. To change the configuration of GDM from GOK to onboard the following has to be done: - Remove the gok.desktop file from the autostart directory of GDM; under Ubuntu it is: /usr/share/gdm/autostart/LoginWindow/ - Add a desktop file for onboard to the autostart directory of GDM (where we just removed the gok.desktop file). The desktop file for onboard has to contain a specific AutostartCondition in order to link it to the screen_keyboard_enabled gconf key that is controlled by the onscreen keyboard item of the Accessibility Dialog of GDM. You can find an onboard.desktop file with the correct AutostartCondition attached to this bug thread. (In fact, it is the file that I am already using for a few weeks to start onboard instead of GOK during GDM.) You can have a look at the Accessibility Configuration Section of the GDM manual for more background information about how it works; this manual is already shipping with the current development version of Ubuntu. To put it short, all that is necessary to do in order to configure GDM to start onboard instead of GOK is to replace the file gok.desktop in /usr/share/gdm/autostart/LoginWindow/ with the file onboard.desktop supplied in this bug thread. By the way, launchpad bug #130368 is solved in the new GDM in Ubuntu once it is correctly configured. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gdm 2.26: a11y should use onboard and not gok that is missing https://bugs.launchpad.net/bugs/423831 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 423831] Re: gdm 2.26: a11y should use onboard and not gok that is missing
** Attachment added: desktop file to launch onboard as onscreen keyboard during GDM http://launchpadlibrarian.net/31278914/onboard.desktop -- gdm 2.26: a11y should use onboard and not gok that is missing https://bugs.launchpad.net/bugs/423831 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395591] Re: Installing GDM 2.26 doesn't update /etc/X11/default-display-manager
I have a similar problem with gdm_2.26.1-0ubuntu7_i386: I am not able to properly install it and it does not get started when I boot the development version of Ubuntu karmic. You can find the output of sudo apt-get install gdm in the installation_by_cli.txt file. When I also install xdm and kdm, I am asked what Window Manager should be default, but gdm is not in the list; probably because it has not been properly installed. ** Attachment added: Output of sudo apt-get install gdm http://launchpadlibrarian.net/29043035/installation_by_cli.txt -- Installing GDM 2.26 doesn't update /etc/X11/default-display-manager https://bugs.launchpad.net/bugs/395591 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395591] Re: Installing GDM 2.26 doesn't update /etc/X11/default-display-manager
I manually edited /etc/X11/default-display-manager and wrote /usr/sbin/gdm into it; now it is working. -- Installing GDM 2.26 doesn't update /etc/X11/default-display-manager https://bugs.launchpad.net/bugs/395591 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217270] Re: seahorse does not recognize seahorse-agent/ssh-agent as a caching agent
gnome-keyring-daemon and ssh-agent share a purpose seahorse-agent (s-a) and gpg-agent (g-a) share a purpose The first on each line to start wins. How can I make my session start the gnome-keyring-daemon before the ssh-agent? Same question for the seahorse-agent and the gpg-agent. Thanks in advance. -- seahorse does not recognize seahorse-agent/ssh-agent as a caching agent https://bugs.launchpad.net/bugs/217270 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 302819] [NEW] gconf-schemas --unregister not removing empty /apps/appname
Public bug reported: Hello, Suppose that we have a file called mytesting.schemas with the following content: gconfschemafile schemalist schema key/schemas/apps/my_app/my_key/key applyto/apps/my_app/my_key/applyto ownermy_app/owner typeint/type default42/default locale name=C shortA short description of this key/short longA longer description here. We can have lots of text here, describing what the possible values are, and what they mean. /long /locale /schema schema key/schemas/apps/my_app/my_other_key/key applyto/apps/my_app/my_other_key/applyto ownermy_app/owner typebool/type default1/default locale name=C shortA short description of this key/short longA longer description here. We can have lots of text here, describing what the possible values are, and what they mean. /long /locale /schema /schemalist /gconfschemafile The following command in the terminal registers the schemas in the gconf database: sudo gconf-schemas --register /path/to/mytesting.schemas The following command in the terminal only partially removes the keys from the gconf database: sudo gconf-schemas --unregister /path/to/mytesting.schemas In fact, /schemas/apps/my_app and /apps/my_app remain listed in the gconf database. However, the command sudo gconf-schemas --register-all called after the unregister command, makes /schemas/apps/my_app and /apps/my_app disappear from the gconf database. Should /schemas/apps/my_app and /apps/my_app not already disappear with the gconf-schemas --unregister command? Cheers ** Affects: gconf2 (Ubuntu) Importance: Undecided Status: New -- gconf-schemas --unregister not removing empty /apps/appname https://bugs.launchpad.net/bugs/302819 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 302819] Re: gconf-schemas --unregister not removing empty /apps/appname
/schemas/apps/my_app and /apps/my_app remain listed in the gconf-editor even after restarting the session. Could you please give me the exact gconftool command to use? I tried for example sudo gconftool-2 --recursive-unset /apps/my_app but it did not remove anything. -- gconf-schemas --unregister not removing empty /apps/appname https://bugs.launchpad.net/bugs/302819 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285873] [NEW] gdmsetup does not set a11y gconf key
Public bug reported: Hello, I am running gdm 2.20.8-0ubuntu3 on the Ubuntu 8.10 development version. When I enable Assistive Technology by using gdmsetup (I don't know whether there is another way to enable it), the gconf key /desktop/gnome/interface/accessibility remains set to FALSE instead of getting the value TRUE. Assistive Technology seems however to work correctly as - I it is possible to start assistive tools by mouse gestures - the assistive tool named mousetweaks, that needs atspi to function, works properly at gdm (We had to disable the gconf key check in the code of mousetweaks, otherwise mousetweaks would not start up as the AT gconf key shows FALSE even if AT is running.) Could anybody please look at the problem, as the Assistive Tools that rely on that key to check whether AT is running will not get the correct information? Please, don't hesitate to contact me if you need additional information. Thanks in advance. ** Affects: gdm Importance: Unknown Status: Unknown ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #556946 http://bugzilla.gnome.org/show_bug.cgi?id=556946 ** Also affects: gdm via http://bugzilla.gnome.org/show_bug.cgi?id=556946 Importance: Unknown Status: Unknown -- gdmsetup does not set a11y gconf key https://bugs.launchpad.net/bugs/285873 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: add gestures for mousetweaks, onboard and gok in direct selection mode http://launchpadlibrarian.net/18647795/AccessDwellMouseEvents.in.diff_v3 -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 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 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
I saw that the original gesture definition of gdm do not include a gesture to start gok in direct selection mode. (It only contains gestures to start gok in dwelling and in automatic scanning mode.) So I enhanced my patch with a gesture to start gok in direct selection mode. So the correct patch now is the one that ends with _v3. -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 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 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: AccessDwellMouseEvents.in.modified_v3 http://launchpadlibrarian.net/18647878/AccessDwellMouseEvents.in.modified_v3 -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 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
Re: [Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
Hi Martin, Thanks for looking at it. You can find an explanation about how to use gestures on the following page: https://help.ubuntu.com/community/Accessibility/OnboardAndMousetweaksAtGDM In ubuntu intrepid you don't need anymore to do everything that is explained on that page. After applying the patch of the bug thread, you can jump immediately to point 4 of the explanation of the page linked above. Remarks: - the gesture command for mousetweaks in the patch are a little different as that on the help page; the command on the help page is for older versions of mousetweaks - Currently on my system, when I perform the gesture to start mousetweaks, I get an error dialog telling me that I have to enable Assistive Technology. The author of mousetweaks does not have that problem. Could you please tell us whether mousetweaks starts up correctly (the window to choose click type appears) or whether you also get that dialog. In any case, the fact that mousetweaks tries to start is a sign that the gesture works; the problem lies probably somewhere between mousetweaks and atspi (or with my installation). Cheers Francesco PS: CC'ing this email to Gerd Kohlberger, the author of mousetweaks. Martin Pitt wrote: How can this be tested? (Sorry, I have no experience with gestures). I'll upload it once it's clear how to test it. Thank you! -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 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 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
I changed the definition for the gestures to start up mousetweaks and onboard a little: - it now uses @AT_BINDIR@ instead of the real path - I moved the ClickType window further down on the screen for the case somebody uses it in conjunction to gok Please ignore the preceding files and use those that end with _v2. -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: AccessDwellMouseEvents.in.modified_v2 http://launchpadlibrarian.net/17533652/AccessDwellMouseEvents.in.modified_v2 -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: AccessDwellMouseEvents.in.diff_v2 http://launchpadlibrarian.net/17533664/AccessDwellMouseEvents.in.diff_v2 -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] [NEW] RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
Public bug reported: Ubuntu supplies onboard as onscreen keyboard. However there is no gesture defined in AccessDwellMouseEvents to start it during the login. The same is also true for mousetweaks. So I created a patch to add the definitions to start onboard and mousetweaks to gdm-2.20.8/gui/modules/AccessDwellMouseEvents of the source package. As I have only very little experience with patching, I will also add the original and the modified file to this thread. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: AccessDwellMouseEvents.diff http://launchpadlibrarian.net/17292573/AccessDwellMouseEvents.diff -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: AccessDwellMouseEvents.in.original http://launchpadlibrarian.net/17292581/AccessDwellMouseEvents.in.original -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 264834] Re: RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)
** Attachment added: AccessDwellMouseEvents.in.modified http://launchpadlibrarian.net/17292584/AccessDwellMouseEvents.in.modified -- RFE: Add gesture to start onboard and mousetweaks at login (patch supplied) https://bugs.launchpad.net/bugs/264834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 130368] Re: RFE: add an item to options menu to start onscreen keyboard
Ubuntu 8.04 ships versions of onboard and mousetweaks that are appropriate to be used during the GDM session. However, users still have to configure GDM to use them. The following document explains how it can be done: https://help.ubuntu.com/community/Accessibility/OnboardAndMousetweaksAtGDM -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 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 190554] Re: Add mousetweaks dependency for its main inclusion request
Yes, I posted the main inclusion request bug for mousetweaks and subscribed it to the MIR approval team shortly before opening this bug thread. There was not any reply or status change to the MIR bug yet: https://bugs.edge.launchpad.net/ubuntu/+source/mousetweaks/+bug/190208 Thanks for reviewing and accepting the mousetweaks dependency for the gnome-control-center. -- Add mousetweaks dependency for its main inclusion request https://bugs.launchpad.net/bugs/190554 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 190554] [NEW] Add mousetweaks dependency for its main inclusion request
Public bug reported: Mousetweaks is the package that implements the features that appeared in the Accessibility tab of the Mouse control panel. It was decided to add mousetweaks as a dependency to the gnome-control- center to get mousetweaks into the main repository because it would not have been possible with mousetweaks added as a recommend. The main inclusion request bug for the mousetweaks package can be found here: https://bugs.edge.launchpad.net/ubuntu/+source/mousetweaks/+bug/190208 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Add mousetweaks dependency for its main inclusion request https://bugs.launchpad.net/bugs/190554 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190554] Re: Add mousetweaks dependency for its main inclusion request
Here is the debdiff that adds mousetweaks to the dependency list; I have added it to both debian/control and debian/control.in. ** Attachment added: gnome-control-center_2.21.90-0ubuntu2.debdiff http://launchpadlibrarian.net/11850686/gnome-control-center_2.21.90-0ubuntu2.debdiff -- Add mousetweaks dependency for its main inclusion request https://bugs.launchpad.net/bugs/190554 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135903] Re: gutsy: at-spi-registryd not starting automatically during gdmlogin
The problem has been fixed upstream: it was due because gdm looked for at-spi-registryd at a wrong location. Now it is possible to specify the location of the at-spi-registryd via the --with-at-spidir configure argument. You can find more information in this thread on the gnome mailing list: http://mail.gnome.org/archives/gdm-list/2007-September/msg00017.html -- gutsy: at-spi-registryd not starting automatically during gdmlogin https://bugs.launchpad.net/bugs/135903 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 130368] Re: RFE: add an item to options menu to start onscreen keyboard
Here you can find the source of the current version of onboard and mousetweaks: https://code.launchpad.net/onboard/ http://gerdk.blogspot.com/ As long as the new version of mousetweaks (probably 0.2.4) is not available, I suggest to use mousetweaks without the Clicktype window. This way, the user will only be able to do the single left click by dwelling, but for gdm, it is enough. Moreover, the problem of at-spi-registryd seems to be on the way to be fixed: https://lists.ubuntu.com/archives/ubuntu-desktop/2007-September/001167.html I will attach debian packages of the current onboard and mousetweaks for the case anybody would like to test it. ** Attachment added: mousetweaks-0.2.2-gutsy.deb http://launchpadlibrarian.net/9102912/mousetweaks_0.2.2-0ubuntu1_gutsy_i386.deb -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 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 130368] Re: RFE: add an item to options menu to start onscreen keyboard
** Attachment added: onboard-0.88-20070828-gutsy.deb http://launchpadlibrarian.net/9102921/onboard_0.88_070828.deb -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 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 130368] Re: RFE: add an item to options menu to start onscreen keyboard
If we restrict ourselves to using the Plain greeter and a dwell gesture to start onboard, the only thing needed is a new line that defines the dwell gesture to start onboard. Considering that onboard is installed by default (I think at least so) with Ubuntu, that should not cause any problems. However, things are not so streamlined for mousetweaks, as it will probably not be part of the default installation... I hope it will be the case for gutsy+1. You can find more details on the following page that I have prepared: https://wiki.ubuntu.com/Accessibility/doc/OnboardAndDwellAtGDM If you are going to add the line to start onboard by a dwell gesture already for gutsy, I will edit the wiki page accordingly. (when I will be back from holidays in mid September). Onboard has to include all the enhancements done until 28082007 included. -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 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 135903] Re: gutsy: at-spi-registryd not starting automatically during gdmlogin
The problem has probably been identified; have a look at this message (and maybe following messages) in the gdm mailing list in gnome: http://mail.gnome.org/archives/gdm-list/2007-August/msg00112.html -- gutsy: at-spi-registryd not starting automatically during gdmlogin https://bugs.launchpad.net/bugs/135903 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 135903] gutsy: at-spi-registryd not starting automatically during gdmlogin
Public bug reported: During the gdmlogin session, at-spi-registryd should be automatically started when Assistive Technology is enabled (I don't know for sure whether it should also be automatically started if Assistive Technology is not enabled.) It does start automatically in Ubuntu 7.04,but it does not start anymore in 7.10. However, if I define a gesture to start at-spi-registryd in the dwell gesture configuration of gdm, I can start it without a problem. This shows that it is probably not a problem of gdm and at-spi-registryd running simultaneously. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gutsy: at-spi-registryd not starting automatically during gdmlogin https://bugs.launchpad.net/bugs/135903 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135903] Re: gutsy: at-spi-registryd not starting automatically during gdmlogin
** Bug watch added: GNOME Bug Tracker #471978 http://bugzilla.gnome.org/show_bug.cgi?id=471978 ** Also affects: gdm via http://bugzilla.gnome.org/show_bug.cgi?id=471978 Importance: Unknown Status: Unknown -- gutsy: at-spi-registryd not starting automatically during gdmlogin https://bugs.launchpad.net/bugs/135903 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 125722] Re: gnome-at-properties - 'Accessible Login' button broken
I confirm this too. As this button merely opens the Login Window preferences dialogue under the menu System-Administration, simply open it that way until it has been fixed. (gdmsetup is in fact the Login Window preferences dialogue) -- gnome-at-properties - 'Accessible Login' button broken https://bugs.launchpad.net/bugs/125722 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 133674] gutsy gnome-at-properties: no gksu/disable-grab option per gui in gnome-at-properties
You have been subscribed to a public bug: A user that does its typing with an onscreen keyboard is not able to enter the password into the gksu dialogue, because it is a modal dialogue. In Feisty, there was a checkbox in the Assistive Technology settings that was called Password dialogues as floating windows and that transformed the gksu dialogue into a modeless dialogue by setting the gconf key /apps/gksu/disable-grab to true. Please, add such a checkbox to gnome-at-properties of gutsy. Meanwhile, users can do the same by typing the following into a terminal: gconftool-2 --set /apps/gksu/disable-grab --type bool true ** Affects: bugzilla (upstream) Importance: Undecided Status: Invalid ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: Triaged -- gutsy gnome-at-properties: no gksu/disable-grab option per gui in gnome-at-properties https://bugs.launchpad.net/bugs/133674 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash on error when locating bonobo factory
You were right; after uninstalling the local copy, the bug does not occur anymore. Sorry: I thought that the copy that I installed manually had been overwritten by the update from the repository. -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 128776] Re: nautilus crash on error when locating bonobo factory
I made another backtrace today. Nautilus hangs at the point where the crash occurs when it is attached to gdb. I assumed that the problem has occurred at that point and called the backtrace command of gdb. After quitting gdb, nautilus was again responsive. ** Attachment added: gdb-nautilus.txt http://launchpadlibrarian.net/8819797/gdb-nautilus.txt -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 128776] Re: nautilus crash on error when locating bonobo factory
** Attachment added: nautilus-debug-log.txt http://launchpadlibrarian.net/8819800/nautilus-debug-log.txt -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 128776] Re: nautilus crash on error when locating bonobo factory
I wonder whether I should not remove the bonobo indication in the title as it does not appear anymore on my system. -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 128776] Re: nautilus crash on error when locating bonobo factory
Synaptic Package Manager tells me that nautilus 1:2.19.6-0ubuntu2 is installed on my ubuntu gutsy installation and that it is also the latest version. -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 128776] Re: nautilus crash on error when locating bonobo factory
The crashes do still happen if I try to open a folder so that it opens in the same window. However, if I open a folder by choosing open in a new window from the contextual menu (right click), it opens in another window without anything crashing. -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 130368] Re: RFE: add an item to options menu to start onscreen keyboard
** Bug watch added: GNOME Bug Tracker #463713 http://bugzilla.gnome.org/show_bug.cgi?id=463713 ** Also affects: gdm (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=463713 Importance: Unknown Status: Unknown -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash on error when locating bonobo factory
Yes, it is still occurring in my uptodate gutsy. I first told about it still happening in bug 127826,and I was told to file a new bug. (So I filed this one.) By the way, I want to point out that when I do a trace with gdb, the crash hangs before the nautilus window disappears and I have to force quit it -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 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 130368] RFE: add an item to options menu to start onscreen keyboard
Public bug reported: At the gdm login screen, there is an Options menu, that enables users to change their keyboard and language settings. I would suggest to add an item to this menu to start the onscreen keyboard that is shipped with ubuntu and that is called onboard. This would be welcome for people that only have the pointer as input. (for example tabletpc users or disabled users) Appearantly, some people have onboard running at the login screen by applying a little hack: http://ubuntuforums.org/showthread.php?t=267051 Consequently, I hoped that making it appear using an additional item in the Options menu will not be very difficult. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- RFE: add an item to options menu to start onscreen keyboard https://bugs.launchpad.net/bugs/130368 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash on error when locating bonobo factory
Despite the updates, it continues to crash systematically, so that it that it is not possible to navigate through folders. (For the moment I am using Thunar, but it does not seem to work well either as it seems to hang sometimes.) -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash on error when locating bonobo factory
** Attachment added: nautilus-debug-log.txt http://launchpadlibrarian.net/8666192/nautilus-debug-log.txt -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash on error when locating bonobo factory
I tried to produce a backtrace with gdb, but the nautilus window hangs when I try to open a subfolder until I quit gdb. I will attach the file pruduced by gdb: ** Attachment added: gdb-nautilus.txt http://launchpadlibrarian.net/8666187/gdb-nautilus.txt -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 127826] Re: nautilus crash opening directory
I have opened a new bug report. You can find it here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/128776 Unfortunately, the crash does not launch apport. Maybe that you can tell me how I can make it launch apport? -- nautilus crash opening directory https://bugs.launchpad.net/bugs/127826 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] nautilus crash because cannot locate bonobo factory
Public bug reported: Binary package hint: nautilus Nautilus crashes when I change from list view to icon view; and viceversa. It also crashes when I try to open a folder in the nautilus window. I get an error dialog telling me that it could not locate the bonobo factory. As my dist-upgrade from feisty to gutsy went not completely smooth, I reinstalled with Synaptic Package Manager everything that was found by doing a bonobo search and that was marked as installed. But it did not solve the problem. Unfortunately, the crash does not launch apport; however it dumps a core and a nautilus error-log in my home directory. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash because cannot locate bonobo factory
** Attachment added: nautilus-bonobo-error-dialog http://launchpadlibrarian.net/8586375/nautilus-bonobo-error-dialog.png ** Summary changed: - nautilus crash because cannot locate bonobo factory + nautilus crash on error when locating bonobo factory -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128776] Re: nautilus crash on error when locating bonobo factory
** Attachment added: nautilus debug log http://launchpadlibrarian.net/8586400/nautilus-debug-log.txt -- nautilus crash on error when locating bonobo factory https://bugs.launchpad.net/bugs/128776 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 127826] Re: nautilus crash opening directory
I am running nautilus 1:2.19.5-0ubuntu2 and it still crashes when I try to open a folder; each time producing a core file in my home directory. (maybe it is because I don't have a clean system) -- nautilus crash opening directory https://bugs.launchpad.net/bugs/127826 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 127966] Re: nautilus crashes/reloads on directory change
*** This bug is a duplicate of bug 127826 *** https://bugs.launchpad.net/bugs/127826 ** This bug has been marked a duplicate of bug 127826 nautilus crash opening directory -- nautilus crashes/reloads on directory change https://bugs.launchpad.net/bugs/127966 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 127961] Re: Nautilus crashing
*** This bug is a duplicate of bug 127826 *** https://bugs.launchpad.net/bugs/127826 ** This bug has been marked a duplicate of bug 127826 nautilus crash opening directory -- Nautilus crashing https://bugs.launchpad.net/bugs/127961 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
