*** 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
*** 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
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
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
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
** 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
** 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
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
** 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
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
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
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
** 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
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
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
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
** 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
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,
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
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
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
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
** 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
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
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.
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
** 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
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
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
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
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
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
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:
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
** 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
** 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
** 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
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
** 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
** 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
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
/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
** 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
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
** 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
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
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
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 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,
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,
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:
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
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
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
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.
--
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.
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
** 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
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:
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
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
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
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
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
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
** 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
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,
67 matches
Mail list logo
