I still have this problem with Ubuntu release 10.04 64bit.
$ apt-cache policy gvfs
gvfs:
Installed: 1.6.1-0ubuntu1build1
Candidate: 1.6.1-0ubuntu1build1
Version table:
*** 1.6.1-0ubuntu1build1 0
500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
100 /var/li
Still present in 12.04 64bit.
$ apt-cache policy gvfs
gvfs:
Installed: 1.12.1-0ubuntu1.1
Candidate: 1.12.1-0ubuntu1.1
Version table:
*** 1.12.1-0ubuntu1.1 0
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64
Packages
100 /var/lib/dpkg/status
1.12.1-0ubuntu
And present in 12.04.
$ apt-cache policy gvfs
gvfs:
Installed: 1.12.1-0ubuntu1
Candidate: 1.12.1-0ubuntu1
Version table:
*** 1.12.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status
--
You received this bug notification
I confirm the very same bug on 64-bit Oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout and subsequent login
To manage notifications
I'd like to confirm sighting of the .gvfs "Transport endpoint is not
connected" bug in Xubuntu 11.10 Oneiric.
The problem is as described in the post from 2008-06-20 in this thread:
Thunar won't show the contents of /home/ubuntu, due to the issue with .gvfs .
And ls -la of /home/ubuntu shows broke
Send fix to me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout and subsequent login
To manage notifications about this bug go to:
https://
Leveraging off oyvinst's script (comment #14)...
I worked around this bug by doing a little bit more:
# Quick and dirty hack to unmount ~/.gvfs directory on logout.
if test -d "$HOME/.gvfs" ; then
for f in "$HOME/.gvfs"
do
/bin/fusermount -zu "$HOME/.gvfs/$f" 1>/dev/null 2>&1 || true
do
Tried davidvoo quick workaround, but it didn’t work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout and subsequent login
To manage notifi
quick workaround is:
$ sudo -i
Password:
# fusermount -u /root/.gvfs
#exit
$ df -h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout and sub
I have the same behaviour as osomon, pretty annoying. is there any
chance to get it fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout
I can confirm the bug on natty with the same symptoms that osomon is
seeing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout and subsequent
I’m seeing this issue in Natty.
It is a fresh install, my home directory is encrypted and it has
annoying consequences, such as Déjà-Dup failing to backup my home
directory because of ~/.gvfs ("Transport endpoint is not connected").
And since the .gvfs folder cannot be browsed to, I can’t even add
** Also affects: gvfs (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212789
Title:
gvfs fuse mount is not functional after logout and subsequent l
** Changed in: gvfs
Importance: Unknown => High
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
those new comments are a different issue, did you read the bug title
before commenting?
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The latest 'fix' doesn't fix the bug for me. This is my situation for if
you want to try to reproduce it:
1. Make a Samba share on another server. Mine are unpublished i.e. you don't
see them when browsing the network, but you can "cd" and log into them after
which they become visible in Nautilu
Elaboration about point 2 above: I use Gnome Commander to open a source
code file by navigating via the ~/.gvfs directory
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ub
The fix in hardy-proposed doesn't seem to fix my ftp mounts. They still
disappear and I have to re-mount them after logout/login. Is that
supposed to work that way? It's really annoying and seems like a
definite regression from Feisty/Gutsy. I much prefer having my ftp
mounts stay available.
P
Does this also fix the problem with CIFS mounts?
They are not properly unmounted on logout either, resulting in the
system hanging on logout waiting for server responses and flooding the
terminal with CIFS communication errors.
One has to manually unmount them before logout to circumvent this.
-
Copied to hardy-updates.
** Changed in: gvfs (Ubuntu Hardy)
Status: Fix Committed => Fix Released
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: gvfs (Ubuntu Hardy)
Target: None => ubuntu-8.04.1
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
New version also works fine here, which means i can browse my network
shares after logout/login, bug is fixed, thanks.
** Tags added: verification-done
** Tags removed: verification-needed
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212
New version works well for me on hardy-proposed, I can still browse
network shares and get ~/.gvfs mounts.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Copied to intrepid.
** Changed in: gvfs (Ubuntu)
Status: Fix Committed => Fix Released
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
seems to have fixed the issue for my systems. the only thing i tested
was the login/logout problem.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
the bug has been fixed upstream and a new version should be uploaded
tomorrow as an hardy update candidate
** Changed in: gvfs (Ubuntu)
Status: Triaged => Fix Committed
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You receiv
** Changed in: gvfs
Status: New => Fix Released
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
jhansonxi wrote:
This bug is causing a security issue for me. I'm using pam_mount to unlock and
mount a LUKS/dm-crypt volume to my home directory at login. At logout it
doesn't unmount and lock because fuse.gvfs has ~/.gvfs open. The script
suggested in comment #14 did not solve the issue.
Try
This bug is causing a security issue for me. I'm using pam_mount to
unlock and mount a LUKS/dm-crypt volume to my home directory at login.
At logout it doesn't unmount and lock because fuse.gvfs has ~/.gvfs
open. The script suggested in comment #14 did not solve the issue.
--
gvfs fuse mount is
i would be glad to continue this over an email thread. if anyone wants
to continue the discussion, please include me (jmcantrell [at] gmail
[dot] com).
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification
I admit that this discussion does not belong to this bug any more and
that's why some people refuse to see the problem. Has anyone of you
(jmcantrell, Sebastien) actually read my last comment? Let's quit it and
if someone suggests a more suitable place to continue this discussion,
I'd be happy to j
ross: oh? because i prefer simplicity and standards over entertaining
every goofy "enhancement" that comes along, i am close minded? wow...
and since we're on the topic, i actually find the automatic creation
of those various folders to be frivolous and unnecessary. if a user
wants a music director
one of the changes that would make things smoother is
http://bugzilla.gnome.org/show_bug.cgi?id=528670 for example, but this
discussion should really be moved to an another bug now
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You re
jmcantrell: There didn't seem to be a problem adding the folders Music,
Pictures, Videos, etc to the user's home directory. I'm not fighting the
directory structure. You'd know that if you read the whole thread. I'm
done arguing with your close mindedness.
Sebastien: Perhaps showing the implementa
yes, there is a problem. it's called "Bug 212789", which this
silliness has nothing to do with. the file system hierarchy is there
for a reason. try to resist the urge to fight it.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You re
nobody deny there is some issues, but having implementation details
showed to user might not be the best changer to do there, anyway
somebody should open a new gvfs bug about the issue
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
Yo
ma2414ma: don't waste your time, they are totally unwilling to see
reason no matter how many examples you give. They refuse to admit there
is a problem.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification
i'm sorry, i completely disagree. user-space tools should not be
polluting the rest of the system. having a directory, like /tmp, that
is writable by everyone is not the same thing as having a directory
that is owned by some specific user.
not to mention, i may have my home folder permissions set
Hm, I'm not so sure that mounting user-space volumes outside of the home
folder is a no-no - if there's a folder for that purpose, I think it
should be used to mount also the .gvfs stuff (just as it is used now to
mount USB drives and so on). There are some folders outside the home
that are writeab
** Changed in: gvfs (Ubuntu Hardy)
Target: None => ubuntu-8.04.1
** Changed in: gvfs (Ubuntu)
Target: ubuntu-8.04.1 => None
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you a
i could go into a rant about capitalization and whitespace in system
paths, but i'll save that for another day. there is already a
directory for system level mountpoints. it's called /mnt. the ubuntu
equivalent to mac's /Volumes appears to be /media. i'm not exactly
clear on what the difference is,
i completely agree with sebastien.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I agree that it should just work without ever needing to know how, but
because of examples like those already given by myself and ma2414ma, not
all applications are using gvfs (and some, like VLC don't play nice with
it) yet, and it could be quite some time (or never) before they do.
Providing a vi
the reason why it's not a standard directory is because implementation
details should not be showed to the users, they don't care what a mount
is and what is the mountpoint, those should simply listed as mounted
locations and being easily accessible in the file manager, file
selectors and other des
those comments are not really constructive there, gedit has issues
because it's still using gnome-vfs and claim supporting vfs uris so
nautilus call it using those uris, the way to fix that is to switch
gedit to use gvfs and not to display implementation details to the user.
try opening a text file
So as long as you have the option to quickly get rid of it, you'd be
happy? Using a symlink by default would be a great help to new users,
while taking less than two seconds to delete if you didn't want it,
which would be jmcantrell's case.
--
gvfs fuse mount is not functional after logout and su
i would want it hidden if i either don't use it or don't care about it.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
ma2414ma said it better than I probably could. I even have problems
opening files in gedit for editing using gvfs via FTP. It tries to load
them, then just stops and leaves you with a blank window. Another
directory in the home directory may not be the best way to do it, but
neither is a hidden fol
jmcantrell: Then Ubuntu should create a symlink to ~/.gvfs called
~/Volumes by default (since there are some default folders like
~/Documents anyway). If you're unhappy with that, just delete the
symlink.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpa
Of course I can make a symlink, but as Ross Peoples correctly writes,
Ubuntu is for human beings and not (just) for Linux nerds. That's why it
should just work. I understand that /Volumes is not the right location,
but then it should be ~/Volumes and not a hidden folder.
Concerning the question wh
it's perfectly clear why it SHOULD be hidden, by default. If it were a
real directory (vs a symlink), how would those of us (myself included)
who want to hide the directory do so?
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You rec
could you describe exactly in what situations those mounts are not
accessible, using in preference an application installed in the default
installation?
openin something from nautilus should transparently call software which
don't support vfs uris using the .gvfs directories, the fileselectors
hav
Ok, as mentioned, for NEW users or others who are not as computer
literate, having to explain that their share is in a hidden using a
seemly strange name is not user-friendly. It's supposed to be Linux for
Human Beings. If I shared out my movies folder, and set it up on my
girlfriend's laptop so th
About the comments regarding the 'hidden' .gvfs directory etc., what's
stopping you from creating a symlink called "My Nice Shares" or whatever
that points to the .gvfs directory, then it will be visible?
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpa
VLC is a widely used application and even though this may be their
problem, don't count on them to fix it because they still haven't fixed
a simple gui bug reported 5 years ago. But I'm not singling out VLC
here, there are other applications I have come across that have the same
behavior when it co
I think that ~/.gvfs is an appropriate location for fuse mounts. If
you want them to be more visible, then do: ln -s .gvfs Volumes. To
have gvfs create a real directory called "Volumes" in the home folder
doesn't seem like the "right" thing to do. To have it mount them in
/Volumes is definitely not
what you describe seems to be a vlc issue, it should not claim
supporting vfs uris if it doesn't
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Try opening a file located on a gvfs mount using VLC or some other non-
gnome application, and you'll see why. Even though the applications may
use the Gnome file dialog, the dialog itself sometimes hides connected
shares, depending on the application. VLC is one example of such an
application. The
why do you think that it would be better to have the mountpoints
displayed? those are listed as mounts and the .gvfs mounts should
automatically be used in a transparent way when you use an application
not handling the gvfs locations directly
--
gvfs fuse mount is not functional after logout and
Yes, it's installed by default now. However, please make the mount point
more visible - I suggest not to mount it within the home directory, but
for example in /Volumes. Would that create problems for a multi-user
environment? In Mac OS X, that's exactly the central location where
everything gets m
> the .gvfs mount point functionality sometimes (or rather often) just
breaks without reason
>the issue seems to be a server crash, are you using the hardy-proposed
update which has a fix for some issues?
The only computer I am having this problem on is a fresh install Hardy
64 bit (DellXPS410.)
nobody is wanting to replace fstab, there is no only desktop users
running linux
to get a stacktrace you can attach gdb to process and see if that's
crashing, the issue there is that the mountpoint is not unmounter
between session, if you get crashes that's a different issue
--
gvfs fuse mount i
In Hardy Beta, you had to manually install it. I was not aware they had
included it by default in the official release, but I am very glad they
did. The only other real complaint (besides stability) that I have with
it is the location of the shares. I really think they should be
somewhere more visi
It is installed by default (I was the one who proposed its inclusion!)
I too am bitten by gvfs-fuse-daemon segfaults, despite being on
0.2.3-0ubuntu5 from proposed-updates :( Is there an easy 'debug build'
which could provide more info / full backtrace?
--
gvfs fuse mount is not functional aft
> why isn't gvfs-fuse installed by default?
it is installed on hardy
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
ma2412ma:
"Suppose gvfs is working, wouldn't it be a good idea to make this more obvious
to the users and not hide it somewhere as a hidden folder?"
I have asked the same question in multiple places without answer. To
further the question, why isn't gvfs-fuse installed by default? When a
user mou
** Changed in: gvfs (Ubuntu Hardy)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Confirmed
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug
hi, is it ok for non developers to post here ?
I get this too.
[EMAIL PROTECTED]:~$ sudo find / -name avast
find: /home/mick/.gvfs: Permission denied
/usr/bin/avast
[EMAIL PROTECTED]:~$ find / -name avast
find: /home/mick/.gvfs: Transport endpoint is not connected
/usr/bin/avast
--
gvfs fuse
I, too, am seeing the bad mount state after logout/login. Another
particularly high profile user has also seen it:
http://arstechnica.com/reviews/os/hardy-heron-review.ars/5
This seems like it might be a somewhat widespread issue, and a
relatively simple work-around is available. Perhaps a SRU
Craig, and other folks suffering from the segfault issue: that is a
separate issue, and you should create a separate ticket to deal with it.
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you
It seems there are 2 different bugs being mentioned here.
I'm only experiencing what ma2412ma is (on Ubuntu 8.04), the frequent
segfaulting of gvfs-fuse-daemon with ls -la returning "d? ? ? ? ? ?
.gvfs" as output.
It happens when I'm editing files with gedit and browsing with Gnome Comman
** Changed in: gvfs
Status: Unknown => New
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=531516
** Changed in: gvfs (Ubuntu)
Importance: Medium => High
Status: Confirmed => Triaged
Target: None =>
I'm also experiencing this bug. I'd like to add the output of ls -la in my
home, which seems strange to me:
d? ? ? ? ?? .gvfs
Question 2: Suppose gvfs is working, wouldn't it be a good idea to make
this more obvious to the users and not hide it somewhere a
I am not getting the "transport endpoint" error, but ~/.gvfs locations
are not working after logout. I created an sftp bookmark with Connect
to Server, and when I link to it, the link is actually to ~/.gvfs as
expected, but after reboot the ~/.gvfs folder has disappeared, and
doesn't even reappear
i am seeing the same behavior... "transport endpoint is not connected".
is there anything that i can disable to get this to go away? i don't use
windows shares.
i ended up creating a shell script called "gnome-session" in my bin
folder that unmounts the folder first, then runs the real gnome-sessi
Yep, sorry for the confusion, although both bugs bit me :).
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
right, you commented on a bug which is different from the one you were
having, you should better open a new bug when the description doesn't
match exactly yours, that makes easier to track issues
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bug
I worked around this bug by adding:
# Quick and dirty hack to unmount ~/.gvfs directory on logout.
if test -d "$HOME/.gvfs" ; then
/bin/fusermount -zu "$HOME/.gvfs" 1>/dev/null 2>&1 || true
fi
to the `/etc/gdm/PostSession/Default' script.
--
gvfs fuse mount is not functional after logout and
However, the latest update doesn't fix the logout/login problem. So this
bug cannot be closed as a result. I guess ~/.gvfs isn't properly
unmounted on logout, so gvfs-fuse-daemon refuses to start on subsequent
login. Sorry for bringing in the unrelated problem of daemon segfault
into this bug repor
I am unable to reproduce the crash using the latest gvfs update from
hardy-proposed ((0.2.3-0ubuntu5). Opening files under ~/.gvfs with
Firefox works fine and no crash occurs in gvfs-fuse-daemon.
So this:
* debian/patches/94_from_svn_fix_referencing_issues.patch:
- change from SVN, fix refer
I have hardy-proposed enabled, but haven't received the updated gvfs
package yet (still at verison 0.2.3-0ubuntu4 from main/release). I'm
using a Norwegian mirror, so maybe it hasn't propagated there, yet ?
I'll just install the updated package manually and report back.
--
gvfs fuse mount is not
Here's the very reproducible crash with gvfs-fuse-daemon debug output
enabled:
unique: 51, opcode: GETATTR (3), nodeid: 5, insize: 56
unique: 52, opcode: RELEASE (18), nodeid: 5, insize: 64
RELEASE[134851312] flags: 0x8000
unique: 53, opcode: LOOKUP (1), nodeid: 3, insize: 48
LOOKUP /oyvind-home p
>From the syslog when gvfs-fuse-daemon died:
Apr 27 15:05:31 blackelf kernel: [153199.221146] gvfs-fuse-daemo[31253]:
segfault at 72656e65 eip b7ef5e76 esp b49b90a0 error 4
This happened when accessing a mount through the smb:// protocol under
~/.gvfs using Firefox.
More debugging info can be pr
> the .gvfs mount point functionality sometimes (or rather often) just
breaks without reason
the issue seems to be a server crash, are you using the hardy-proposed
update which has a fix for some issues?
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) =
I'd like to add that the .gvfs mount point functionality sometimes (or
rather often) just breaks without reason (with transpoint endpoint not
connected error), even though no logout/login has been done. So it's a
more generic problem.
--
gvfs fuse mount is not functional after logout and subseque
Confirming that a work-around is to manually unmount the ~/.gvfs using:
$ fusermount -u ~/.gvfs
Then close/unmount all opened remote locations in Nautilus and log out
and back in, again. This restores the .gvfs-functionality for me.
--
gvfs fuse mount is not functional after logout and subsequen
Seeing this as well (clean Hardy install from release-candidate image,
all updates as of Apr 22 2008 applied). The ~/.gvfs mountpoint becomes
unusable after logout/login, with "transport endpoint not connected"
error. Observed with both sftp:// and smb://.
--
gvfs fuse mount is not functional aft
I too suffer from same issue, tried using Nick Frolov's advice on manually
unmounting the .gvfs folder.
The problem is only half solved...
ls -la |grep .gvfs
dr-x-- 2 user user 0 2008-04-19 18:35 .gvfs
Notice the permissions on folder?
on my 64bit systemm the folder has also write perm
Changed to "Confirmed" since I'm experiencing the exact same behavior,
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a m
Confirmed, I just filed a bug about pulseaudio not working after logging
in again. Perhaps a console-kit issue?.
I have long dropped the use of 'startx' but use straight GDM. Although
many problems arose with it, namely SCIM the environment variables not
being exported unless you fiddle with the f
I noticed that manual unmounting of $HOME/.gvfs before logout resolves
the issue. Probably it should be automated somehow?
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of U
92 matches
Mail list logo
