[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Same behavior with k3s v1.29.5+k3s1, on Ubuntu 22.04.4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2047356 Title: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Thanks for your feedback, I feel less alone. Can you mark that this issue affects you at the top of this page (under the issue description)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2047356 Title: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Same behavior on Ubuntu 24.04 daily (2024-01-20, with Gnome 46), and on Fedora Workstation 39 (with Gnome 45) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2047356 Title: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
** Description changed:
On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes
(using default local-path storageClass), process gvfs-disks2-volume-monitor can
take around 100% of one CPU core, and process gsd-housekeeping around 25% of
one CPU core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
- Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
+ Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-with-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running (even if idle)
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details:
k3s uses containerd to run containers. The local-path storageClass mounts
local volumes (physically stored in /var/lib/rancher/k3s/storage subfolders) in
these containers.
I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for
docker
NB: Was initially reported on https://github.com/k3s-io/k3s/issues/9093
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/2047356
Title:
gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
lot of CPU with k3s workload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
I have the same behavior with Ubuntu 23.10.1 (with all current updates), using latest stable k3s (v1.28.5+k3s1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2047356 Title: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
** Description changed:
On Ubuntu 22.04.3, when running a k3s workload that uses volumes (using
default local-path storageClass), process gvfs-disks2-volume-monitor can take
around 100% of one CPU core, and process gsd-housekeeping around 25% of one CPU
core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- - Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-wit-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-wit-many-volumes.yaml"
+ - Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running.
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details: k3s uses containerd to run containers. The local-path
storageClass mounts local volumes (physically stored in
/var/lib/rancher/k3s/storage subfolders) in these containers.
- I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/b96a0909f0ebc683de817665ff090d57ced6f981/contrib/udev/80-docker.rules
does for docker
+ I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for
docker
NB: Was initially reported on https://github.com/k3s-io/k3s/issues/9093
** Description changed:
- On Ubuntu 22.04.3, when running a k3s workload that uses volumes (using
default local-path storageClass), process gvfs-disks2-volume-monitor can take
around 100% of one CPU core, and process gsd-housekeeping around 25% of one CPU
core.
+ On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes
(using default local-path storageClass), process gvfs-disks2-volume-monitor can
take around 100% of one CPU core, and process gsd-housekeeping around 25% of
one CPU core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running.
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details: k3s uses containerd to run containers. The local-path
storageClass mounts local volumes (physically stored in
/var/lib/rancher/k3s/storage subfolders) in these containers.
I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit li
[Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
** Description changed:
On Ubuntu 22.04.3, when running a k3s workload that uses volumes (using
default local-path storageClass), process gvfs-disks2-volume-monitor can take
around 100% of one CPU core, and process gsd-housekeeping around 25% of one CPU
core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-wit-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-wit-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running.
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing systemctl stop --user gvfs-udisks2-volume-monitor can be a
temporary workaround
+ Technical details: k3s uses containerd to run containers. The local-path
storageClass mounts local volumes (physically stored in
/var/lib/rancher/k3s/storage subfolders) in these containers.
+ I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/b96a0909f0ebc683de817665ff090d57ced6f981/contrib/udev/80-docker.rules
does for docker
+
NB: Was initially reported on https://github.com/k3s-io/k3s/issues/9093
** Description changed:
On Ubuntu 22.04.3, when running a k3s workload that uses volumes (using
default local-path storageClass), process gvfs-disks2-volume-monitor can take
around 100% of one CPU core, and process gsd-housekeeping around 25% of one CPU
core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-wit-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-wit-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running.
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
- Executing systemctl stop --user gvfs-udisks2-volume-monitor can be a
+ Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details: k3s uses containerd to run containers. The local-path
storageClass mounts local volumes (physically stored in
/var/lib/rancher/k3s/storage subfolders) in these containers.
I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/b96a0909f0ebc683de817665ff090d57ced6f981/contrib/udev/80-docker.rules
does for docker
NB: Was initially reported on https://github.com/k3s-io/k3s/issues/9093
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/2047356
Title:
gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
lot of CPU with k3s workload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lis
[Bug 2047356] [NEW] gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Public bug reported:
On Ubuntu 22.04.3, when running a k3s workload that uses volumes (using default
local-path storageClass), process gvfs-disks2-volume-monitor can take around
100% of one CPU core, and process gsd-housekeeping around 25% of one CPU core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default settings:
"curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-wit-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-wit-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or anything
else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of CPU,
at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl delete
-f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is always
there, when the workload is running.
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522, but
the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing systemctl stop --user gvfs-udisks2-volume-monitor can be a
temporary workaround
NB: Was initially reported on https://github.com/k3s-io/k3s/issues/9093
** Affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/2047356
Title:
gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
lot of CPU with k3s workload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"
I have the same symptoms on 3 different computers (all upgraded from Ubuntu 20.04). I do have the error message "Removing a network device that was not added" in /var/log/syslog, but not at the time when the problem occurs. My computers are always plugged to the network with an ethernet cable. I only have one gnome extension (on the 3 of them): https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet I found the workaround to hit ctrl-alt-F1 then ctrl-alt-F2: after typing my password again, my session is back -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 875878] Re: Easymp3gain Hangs when clicking Add File or Add Folder
Thanks Matthias for the suggestion. I'm using Ubuntu 12.04.3 (64 bits) and tried the packages from Saucy. The GTK version can not be installed easily because of its dependency on a newer version of libpango. But the Qt version can be installed easily and worked for me. So here is the workaround I used : - uninstall package easymp3gain-gtk from your system - download packages easymp3gain-qt and esaymp3gain-data from saucy (currently version 0.5.0+svn135-4) : http://packages.ubuntu.com/saucy/easymp3gain-qt and http://packages.ubuntu.com/saucy/easymp3gain-data - install them -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/875878 Title: Easymp3gain Hangs when clicking Add File or Add Folder To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/875878/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 875878] Re: Easymp3gain Hangs when clicking Add File or Add Folder
I faced again this same issue on another computer. Easymp3gain was working properly on 10.04. After the upgrade to 12.04, it was unusable because of this bug. Installing the debian version (and blocking this version in Synaptic) worked around the issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/875878 Title: Easymp3gain Hangs when clicking Add File or Add Folder To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/875878/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 875878] Re: Easymp3gain Hangs when clicking Add File or Add Folder
On my computer, the debian package works, but not the quantal one. The sourceforge package crashes as in comment #13 Testing both on Precise amd64, with all current updates. It's a good thing that it's fixed in Quantal, but could something be done for Precise LTS? I understand that backporting the fix on gtk can be too complicated/risky. But there seems to be a way to make it work as the debian package works? In any case, this application is currently unusable on Precise : its purpose is to modify audio files but you can't select them... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/875878 Title: Easymp3gain Hangs when clicking Add File or Add Folder To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/875878/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 969359] Re: gnome-settings-daemon consumes 100% cpu
I also noticed that when using VNC -- 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/969359 Title: gnome-settings-daemon consumes 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/969359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 304345] Re: File chooser dialog doesn't provide network access
Another workaround that can fit some needs : use the package autofs You can configure it so that it mounts your network shares in a location like /mnt/autofs/servername/share You can then put a bookmark on this directory, and it seems to be always displayed in open/save dialogs (tested on Firefox and Thunderbird) Autofs mounts and unmounts the shares automatically when they are used/unused If you need to use credentials (login/password) to connect to your SMB share, it's less straightforward but seems to work with a bit more config. See http://doc.ubuntu-fr.org/autofs_avec_samba#acces_aux_partages_avec_authentification (in French) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/304345 Title: File chooser dialog doesn't provide network access To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/304345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 304345] Re: File chooser dialog doesn't provide network access
For Firefox, a separate bug seems to exist on launchpad : https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/31471 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/304345 Title: File chooser dialog doesn't provide network access To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/304345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 304345] Re: File chooser dialog doesn't provide network access
I also face this issue. I would expect the file chooser dialog to allow me to access network bookmarks (including mounting them if they are not mounted already). It's very annoying when you want to save a file on a network share from Firefox or Thunderbird : you have to save it locally, then transfer it with nautilus. I found the following workarounds : - mount permanently the network locations in /etc/fstab : it works, but is not adapted to all situations. In my case, the server that hosts the network share is a standard PC, not a 24/7 server. So, if this PC is not up at startup time, the share is not mounted - add a bookmark for ~/.gvfs directory, as suggested by smonff : it appears in the file chooser, but is empty if the share is not mounted. So you have to mount it before - add a bookmark for ~/.gvfs AND install/configure the package gigolo : this software can automatically mount network shares. If you declare it as a startup application, it will try to connect every minute. See http://www.borpin.co.uk/2011/03/29/map-network-drive-in-ubuntu-again/ . It's still a workaround but it's the best I found so far. In any case, it would be much much easier to be able to open/save directly in a network bookmark. It is a frequent use case at home or in small organizations (several computers with shares to exchange data, but no central server) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/304345 Title: File chooser dialog doesn't provide network access To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/304345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 923749] Re: New "push mouse offscreen" feature really difficult to get
It's a bit better with the reveal sensitivity set to high. Anyway, if the "push mouse offscreen" feature might be a good idea on trackpads, I still don't find it ergonomical with a mouse. At first use, people (including me) don't seem to have the reflex to push on the left, and think the launcher does not reveal, or does not work. Another problem is that this push on the left physically moves the mouse on the left, while the cursor does not move. After a few pushes, the mouse has moved a few centimeters on the left. So you need to lift it and reposition it on the right (else it finally hits the keyboard, if you are right-handed) -- 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/923749 Title: New "push mouse offscreen" feature really difficult to get To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/923749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 192508] Re: mouse keys turns on randomly
I'm facing the same issue with the following configuration: - ubuntu 10.04.1 32bit, with remote desktop enabled (vino version 2.28.2-0ubuntu2) - ubuntu 10.04.1 64bit, connecting to the above computer with vinagre (version 2.30.2-0ubuntu1) The mouse keys activate on the first computer (the VNC server) Based on the above comments and my personal experience, I don't think it could simply be some accidental Shift-NumLock -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/192508 Title: mouse keys turns on randomly -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 357042] Re: gstreamer-properties not saved
paulocic confirmed the problem on Maverick 2 days ago. I also reproduced it on a Ubuntu 10.10 (Maverick) virtual machine. It's very easy to reproduce : see the steps in description or in comment #6 -- gstreamer-properties not saved https://bugs.launchpad.net/bugs/357042 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 364084] Re: Nautilus cannot handle "ftp" places message
I encounter the same problem on Ubuntu 9.04, with the FTP server of a Freebox (an ISP ADSL box). The FTP server is not accessible via Nautilus, because it stops on the same error message : <-- 220 Welcome to Freebox FTP Server. --> FEAT <-- 211-Extensions supported: <-- UTF8 <-- 211 End feature UTF8 supported --> OPTS UTF8 ON <-- 500 Syntax error, command unrecognized. error: Opération non prise en charge send_reply, failed: 1 It works fine on Ubuntu 10.04 and (I guess) on 9.10, certainly because they use gvfs > 1.3.4, whereas 9.04 uses 1.2.2. Do you see other workarounds than : - upgrade to 9.10 or 10.04 : this is probably the best thing to do as 9.04 will soon be unsupported - use another FTP client I quickly tried to install the gvfs package of Karmic (version 1.4.1-0ubuntu1) on Jaunty, but failed because it seems to drag too many dependencies upgrade... -- Nautilus cannot handle "ftp" places message https://bugs.launchpad.net/bugs/364084 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 357042] Re: gstreamer-properties not saved
I see the same behavior on lucid (final release). This is very annoying because gstreamer-properties is the only place where one can adjust the audio/video settings for the webcam feature of pidgin. See http://developer.pidgin.im/wiki/Using%20Pidgin#HowdoIconfiguremymicrophonewebcam It seems that some properties are saved, but not all : I had the problem when setting a custom pipeline for the default video input. Steps to reproduce : - open gstreamer-properties - go to the video tab - in the default input, choose customized, and put a custom pipeline like the following : v4l2src device="/dev/video0" ! video/x-raw-yuv,width=320,height=240 - click on test : you can see that the custom pipeline is correctly used - click on close - open gstreamer-properties again - go to the video tab : the custom pipeline has disappeared, and went back to v4l2 (in my case) Is there any workaround to adjust the video settings of a webcam, so that they are used by pidgin? -- gstreamer-properties not saved https://bugs.launchpad.net/bugs/357042 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
