** Changed in: evince (Fedora)
Status: New => Invalid
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I had thought that Philip had given all the needed info (and more)
reopening, since of course, this is still present in Jaunty
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
nautilus and evince should n
I found it especially frustrating on the laptop when autofs tries to
mount shares that are inaccessible. It sometimes causes autofs to hang,
and long delays starting evince. A good workaround I'm using is to make
the .recently-used.xbel file immutable after clearing Recent Documents
in GNOME.
As
one task is enough that seems rather a gtk issue then
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Package changed: nautilus (Ubuntu) => gtk+2.0 (Ubuntu)
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received t
the bug should be sent to bugzilla.gnome.org by somebody who consider
the behaviour buggy which I don't, the software need to stat recent
files to list only those which are available and can be used
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243
** Summary changed:
- nautilus and evince should not accesses smb mounts at startup
+ nautilus and evince should not access smb mounts at startup
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you a
** Summary changed:
- nautilus and evince should not accesses smb mounts at startup
+ nautilus and evince should not access smb mounts at startup
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you a
I had thought that Philip had given all the needed info (and more)
reopening, since of course, this is still present in Jaunty
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
nautilus and evince should n
I found it especially frustrating on the laptop when autofs tries to
mount shares that are inaccessible. It sometimes causes autofs to hang,
and long delays starting evince. A good workaround I'm using is to make
the .recently-used.xbel file immutable after clearing Recent Documents
in GNOME.
As
one task is enough that seems rather a gtk issue then
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Package changed: nautilus (Ubuntu) => gtk+2.0 (Ubuntu)
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received t
the bug should be sent to bugzilla.gnome.org by somebody who consider
the behaviour buggy which I don't, the software need to stat recent
files to list only those which are available and can be used
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243
I had thought that Philip had given all the needed info (and more)
reopening, since of course, this is still present in Jaunty
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
nautilus and evince should n
I found it especially frustrating on the laptop when autofs tries to
mount shares that are inaccessible. It sometimes causes autofs to hang,
and long delays starting evince. A good workaround I'm using is to make
the .recently-used.xbel file immutable after clearing Recent Documents
in GNOME.
As
one task is enough that seems rather a gtk issue then
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Package changed: nautilus (Ubuntu) => gtk+2.0 (Ubuntu)
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received t
the bug should be sent to bugzilla.gnome.org by somebody who consider
the behaviour buggy which I don't, the software need to stat recent
files to list only those which are available and can be used
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243
** Changed in: evince (Fedora)
Status: New => Invalid
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Summary changed:
- nautilus and evince should not accesses smb mounts at startup
+ nautilus and evince should not access smb mounts at startup
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you a
** Changed in: evince (Fedora)
Status: New => Invalid
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Summary changed:
- nautilus and evince should not accesses smb mounts at startup
+ nautilus and evince should not access smb mounts at startup
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you a
I had thought that Philip had given all the needed info (and more)
reopening, since of course, this is still present in Jaunty
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
nautilus and evince should n
I found it especially frustrating on the laptop when autofs tries to
mount shares that are inaccessible. It sometimes causes autofs to hang,
and long delays starting evince. A good workaround I'm using is to make
the .recently-used.xbel file immutable after clearing Recent Documents
in GNOME.
As
one task is enough that seems rather a gtk issue then
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Package changed: nautilus (Ubuntu) => gtk+2.0 (Ubuntu)
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received t
the bug should be sent to bugzilla.gnome.org by somebody who consider
the behaviour buggy which I don't, the software need to stat recent
files to list only those which are available and can be used
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243
** Changed in: evince (Fedora)
Status: New => Invalid
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I had thought that Philip had given all the needed info (and more)
reopening, since of course, this is still present in Jaunty
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
nautilus and evince should n
I found it especially frustrating on the laptop when autofs tries to
mount shares that are inaccessible. It sometimes causes autofs to hang,
and long delays starting evince. A good workaround I'm using is to make
the .recently-used.xbel file immutable after clearing Recent Documents
in GNOME.
As
one task is enough that seems rather a gtk issue then
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Package changed: nautilus (Ubuntu) => gtk+2.0 (Ubuntu)
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received t
the bug should be sent to bugzilla.gnome.org by somebody who consider
the behaviour buggy which I don't, the software need to stat recent
files to list only those which are available and can be used
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243
** Changed in: evince (Fedora)
Status: New => Invalid
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Summary changed:
- nautilus and evince should not accesses smb mounts at startup
+ nautilus and evince should not access smb mounts at startup
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you a
** Summary changed:
- nautilus and evince should not accesses smb mounts at startup
+ nautilus and evince should not access smb mounts at startup
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you a
I had thought that Philip had given all the needed info (and more)
reopening, since of course, this is still present in Jaunty
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
nautilus and evince should n
I found it especially frustrating on the laptop when autofs tries to
mount shares that are inaccessible. It sometimes causes autofs to hang,
and long delays starting evince. A good workaround I'm using is to make
the .recently-used.xbel file immutable after clearing Recent Documents
in GNOME.
As
one task is enough that seems rather a gtk issue then
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Package changed: nautilus (Ubuntu) => gtk+2.0 (Ubuntu)
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received t
the bug should be sent to bugzilla.gnome.org by somebody who consider
the behaviour buggy which I don't, the software need to stat recent
files to list only those which are available and can be used
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243
** Changed in: evince (Fedora)
Status: New => Invalid
--
nautilus and evince should not access smb mounts at startup
https://bugs.launchpad.net/bugs/243250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
36 matches
Mail list logo
