Public bug reported:
Binary package hint: amarok
Upon upgrading to amarok=1.4.9-0ubuntu1 (Hardy), my iPod classic is
still recognized, but silently fails to display my collection. I can
work around the problem temporarily by downgrading to
amarok=1.4.8-0ubuntu5. All other libgpod applications als
Actually, right off the bat.. g_strconcat() allocates heap memory and
returns a pointer to the string. Probably necessary to do something like
homedir = gstrconcat(g_get_home_dir(), G_DIR_SEPARATOR, NULL) and then
free(homedir) when done. Also missing NULL termination in the second
__SNIP__ and sho
Sebastien,
I didn't think of this until after you signed off IRC.
DISCLAIMER: code might crash, I'm not a C/glib guru and haven't tested
this specific patch.
You could solve both problems reported at
http://bugzilla.gnome.org/show_bug.cgi?id=525866 by doing something like
this:
__SNIP__
/* mou
Sebastien,
Perhaps we can reach a compromise by allowing mounts relative to the
user's home directory, but not the home directory itself? This would
prevent the specific issue we're reporting here.
--
gnome displays nfs mounts on the desktop
https://bugs.launchpad.net/bugs/191512
You received th
Sebastien, if you'd like to discuss this in depth I would be happy to
meet with you on Freenode. I am currently in #ubuntu, #ubuntu-devel and
#ubuntu-bugs and I'd be more than happy to speak via /query with you if
you prefer. My IRC nick is 'pawalls'.
--
gnome displays nfs mounts on the desktop
h
Sebastien,
autofs is a daemon that interacts with the Linux kernel automounter to
mount directories when they are accessed for the first time. The volumes
are mounted by "root", not by the user accessing the directory. This is
especially helpful when you have thousands of home directories exported
Would it be reasonable to only display mounts in /media on the desktop?
--
gnome displays nfs mounts on the desktop
https://bugs.launchpad.net/bugs/191512
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
To clarify, this is an issue if you use autofs with hundreds or
thousands of automount entries in autofs map. Based on my understanding,
there are two simple ways to resolve this problem while maintaining a
good user experience for flash drives and the like:
1) We can specify an inclusive list of
Yes, the version of nautilus in latest hardy/unstable still has this
problem.
--
gnome displays nfs mounts on the desktop
https://bugs.launchpad.net/bugs/191512
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Timo,
The issue is not limited to only things mounted under /media. Mounts
under /home also create desktop icons and pop up a new Nautilus window.
--
gnome displays nfs mounts on the desktop
https://bugs.launchpad.net/bugs/191512
You received this bug notification because you are a member of Ubu
This regression went away some time around Feb 20th and recently snuck
back in sometime near the beginning of this month (March). Makes it
nearly impossible to use the gnome desktop with many NFS partitions (eg.
via autofs).
** Changed in: nautilus (Ubuntu)
Sourcepackagename: None => nautilus
**
Unless I'm mistaken, this bug is already resolved in Hardy since Hardy
received the upstream kernel patch automatically.
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You received this bug notificatio
The patch linked to above applies cleanly and fixes the problem.
Attaching to the bug.
** Tags added: cherry-pick
** Tags added: patch
** Attachment added: "Patch from CITI to use kernel supported encyrption types
in GSSD"
http://launchpadlibrarian.net/11340258/nfs-utils-1.1.1-007-gssd_use_
Confirmed. This is a regression from the version of NFS in Gutsy.
--
gssd doesn't properly detect kernel supported enctypes
https://bugs.launchpad.net/bugs/180449
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
Charles,
You may need to run 'dpkg-reconfigure linux-restricted-
modules-2.6.22-14-generic' to rebuild your module list to include the
volatile modules ('depmod -a' on a fully booted system should also
work). You can check to see if this is the cause by comparing the output
of the following comman
Claude tested the above patched module and reported that everything
worked well.
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You received this bug notification because you are a member of Ubuntu
Bug
Here's the nfs.ko compiled against 2.6.22-14.47. Make sure that if you
use this you first back up the current one in /lib/modules. You can
attempt to reinsert the module into your running kernel or reboot.
** Attachment added: "Rebuilt nfs.ko against 2.6.22-14.47 with the above patch
applied"
As promised, here is the fix to unbreak NFSv4 in the 2.6.22-14.47
kernel.
I independently tested:
- Mounting NFSv4 export (sec=sys and sec=krb5)
- Reading/writing from partition, including seeks (tail)
Claude,
If you are willing to test the patch (or a new nfs.ko or linux-
image-2.6.22-14-generi
Reopening due to introduction of NFSv4 problem in patch
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Status: Fix Released => New
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You received
Claude and AZ,
The problem you are experiencing is in fact (embarrassingly) caused by
my patch at https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/164231 which was included in the 2.6.22-14.47 kernel
as part of a security update. This problem is unrelated to the OOPS that
was or
Reopening due to introduction of NFSv4 problem in patch
** Changed in: linux-source-2.6.20 (Ubuntu Feisty)
Status: Fix Released => New
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You receive
Claude,
I apologize for missing an important part of the patch in my original
submission which caused the NFSv4 regression that you are experiencing.
If I'd know that Canonical wasn't going to do quality assurance of
kernel patches to their stable release branch (despite my warning that
I'd only t
Leanne,
Thanks a lot for the update. It's good to know that a fix is in the
pipeline. I hope my previous message didn't come across as too snarky.
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You re
Leanne,
It has been a few weeks since I submitted this bug and I haven't heard
anything from the teams responsible for it. I did my best to hand over
the bug on a silver platter (at the cost of a fair deal of my own time),
so a couple answers would set my head at ease:
- Has the bug been confirme
I backported the patch above to the Gutsy kernel based on the patch at:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e89a5a43b95cdc4305b7c8e8121a380f02476636
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
The patch above also applies cleanly to Feisty's linux-
source-2.6.20-16.32 kernel and builds. The system boots successfully and
this bug is not reproducible with the patched kernel. Other NFSv3 mounts
continue to work based on my limited testing.
--
NFS regression causes subsequent mounts from s
** Tags added: patch
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
It should be obvious from my description above, but I wanted to
specifically mention that this regression makes it impossible to mount
two directories from the same block device with different options. An
example of a case that worked in Edgy but no longer works in
Feisty/Gutsy is using sec=sys for
Leann,
Yes, the problem is also reproducible in Feisty.
--
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
https://bugs.launchpad.net/bugs/164231
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
Public bug reported:
Two or more NFS mount points with the same FSID end up silently sharing
mount options.
You have an NFS server with the following mount:
/dev/sda3 => /mnt/data
And then you export two folders from that block device separately via
NFS (/etc/exports):
/mnt/data/a10.0.
Daniel,
Kevin (the reporter) is a friend of mine. He is currently in Ukraine
with no internet access, but we have the same laptop so I will try to
help out in his absence.
model=auto works and has normal volume
model=toshiba works, but volume is VERY low, even with all values maxed out in
alsami
Same problem/solution as Jose and Tzorg on my Toshiba A105-S4304:
echo "options snd-hda-intel model=3stack" >> /etc/modprobe.d/alsa-base
rmmod snd-hda-intel
modprobe snd-hda-intel
Any chance that a permanent fix will make it into Feisty before it goes
stable?
--
Intel_hda alsa/realtek codec fei
32 matches
Mail list logo
