The proposed pkg fixes my issue!
nfs-common/focal-proposed,now 1:1.3.4-2.5ubuntu3.7 amd64 [installed]
Installed from proposed repo.
Mounted via pam_mount upon ssh login using krb5p; NFSv4 successful mount
with vers=4.0 which I could not do before upgrading from focal-updates
This fixes my issue! https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/2063381
nfs-common/focal-proposed,now 1:1.3.4-2.5ubuntu3.7 amd64 [installed]
Installed from proposed repo.
Mounted via pam_mount upon ssh login using krb5p; NFSv4 successful mount
with vers=4.0 which I could not do
Andreas,
Thanks for the information! Much appreciated, I did not find that bug in my
searches for NFS related things. Will definitely give this new package a try
later today on our test server, thanks again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but
Public bug reported:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now it appears to
Public bug reported:
It is not possible to mount a btrfs subvolume by supplying the name to
the subvol= argument. The mount only works by using subvolid=ID where
ID is the subvolume ID. If you try to mount using the name, No such
file or directory is returned.
# sudo btrfs subvolume list /home
*** This bug is a duplicate of bug 1362884 ***
https://bugs.launchpad.net/bugs/1362884
Here is the dmesg output at the time of the error message:
[8.515396] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid 2
transid 100593 /dev/dm-0
[8.525319] BTRFS info (device dm-0):
** Package changed: ubuntu = upstart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426782
Title:
Boot fails with encyprted BTRFS RAID1 array - open ctree failed
To manage notifications
Today's update to the 3.13.46-77 kernel did not change the behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426782
Title:
Boot fails with encyprted BTRFS RAID1 array - open ctree failed
To
OK, the workaround from OpenSUSE did NOT work (with the 3.16 kernel).
Same behavior as before. The steps I performed were:
copy /lib/udev.rules.d/64-btrfs.rules to /etc/udev/64-btrfs.rules
The line
IMPORT{builtin}=btrfs ready $devnode
was already present in the original rules file, so I did
https://cards.linaro.org/browse/TCWG-531
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364979
Title:
fbb ftbfs on arm64
To manage notifications about this bug go to:
** Changed in: gcc-linaro
Importance: Undecided = Medium
** Changed in: gcc-linaro
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295738
Title:
[4.8 Regression]
** Changed in: gcc-linaro
Assignee: (unassigned) = Kumar Venkataramanan (venkataramanan-kumar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295738
Title:
[4.8 Regression] unable to find a
I can confirm Redstorm's experience. I successfully built the module on
kernel 3.8.0.29 (Linux Mint 15 KDE x64).
The module loaded right away with modprobe and appears to work on an n
network, but it's connecting in b/g mode and the speed has not been
higher than 5.5 MBit/s.
A Dlink PCIE wifi
Confirmed on Fedora x64 with Gnome 3.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/677783
Title:
Redshift does not quit upon logout from session
To manage notifications about this bug go to:
This affects me as well. I've tried the 2.6.38 Kernel on an up-to-date
Maverick system where wireless normally works fine, on the Natty Beta
live disk and a test install of Natty beta. I stay connected but
experience about 30% packet loss to my router.
I'm using the ath9k driver in 802.11n
This bug also affects me. I am running an i5-660 (clarkdale) using the
onboard graphics. I use the edgers PPA. Happy to provide any output
that might be relevant.
--
Notifications clipped on Intel with xorg-edgers
https://bugs.launchpad.net/bugs/649838
You received this bug notification
Public bug reported:
Binary package hint: xorg
Hello, I am using a Gateway NV5927U laptop and the screen brightness is
unchangeable via the keyboard controls. The brightness is stuck at 100%
and changing values inside of /proc/acpi/video/GFX0 have no effect on
the brightness. Please let me
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52145001/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52145003/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52145004/Dependencies.txt
**
** Description changed:
Binary package hint: xorg
Hello, I am using a Gateway NV5927U laptop and the screen brightness is
unchangeable via the keyboard controls. The brightness is stuck at 100%
and changing values inside of /proc/acpi/video/GFX0 have no effect on
- the brightness.
** Description changed:
Binary package hint: xorg
Hello, I am using a Gateway NV5927U laptop and the screen brightness is
unchangeable via the keyboard controls. The brightness is stuck at 100%
and changing values inside of /proc/acpi/video/GFX0 have no effect on
the brightness.
Yes, I'm still having this issue on Lucid 64-bit. After booting on
battery power the Gnome indicator claims my battery is charged and
connected to AC power. I can access the correct charge level by opening
the power statistics window, or by plugging and unplugging the AC
adapter.
My hardware
** Attachment added: lspci -vvnn output
http://launchpadlibrarian.net/43241482/lspci%20-vvnn%20output.odt
--
Display switching not possible on HP Pavillion dv3510nr notebook [Karmic
Regression]
https://bugs.launchpad.net/bugs/28
You received this bug notification because you are a
** Attachment added: dmesg output
http://launchpadlibrarian.net/43241548/dmesg%20output.odt
--
Display switching not possible on HP Pavillion dv3510nr notebook [Karmic
Regression]
https://bugs.launchpad.net/bugs/28
You received this bug notification because you are a member of Ubuntu
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/43241606/Xorg.0.log
--
Display switching not possible on HP Pavillion dv3510nr notebook [Karmic
Regression]
https://bugs.launchpad.net/bugs/28
You received this bug notification because you are a member of Ubuntu
Bugs, which
On further investigation, it's possible that this is an ACPI code
binding issue. I noticed that when I push FN+F4 (my display switch key)
in terminal or a word processor, I get p just as if I were typing that
key. Maybe it's as simple as reassigning the function key to the
appropriate keycode.
** Description changed:
Binary package hint: xserver-xorg-video-nouveau
When running the noveau driver on an HP Pavillion dv3510nr Notebook
(running Lucid Lynx beta 1 x64), it is not possible to switch display
modes using the laptop's FN+F4 key. This notebook has an NVIDIA 9300M
-
** Description changed:
Binary package hint: xserver-xorg-video-nouveau
When running the noveau driver on an HP Pavillion dv3510nr Notebook
(running Lucid Lynx beta 1 x64), it is not possible to switch display
modes using the laptop's FN+F4 key. This notebook has an NVIDIA 9300M
I can confirm this bug on Lucid beta 1 x64 with an HP Pavillon dv3510nr
laptop using the VGA port. The noveau driver boots beautifully as long
as an external is not connected. If it is, boot hangs at the screen
that says ubuntu and shows five orange dots underneath. I can
activate the external
hp Pavillon dv3510nr volume up/down keys repeating forever
Problem occured on Ubuntu 9.10 and persists in Lucid Beta 1
This temporary fix addressing the lack of a keyup event for these media buttons
worked fine for me:
http://ubuntuforums.org/showthread.php?t=974723
--
volume control doesn't
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
When running the noveau driver on an HP Pavillion dv3510nr Notebook
(running Lucid Lynx beta 1 x64), it is not possible to switch display
modes using the laptop's FN+F4 key. This notebook has an NVIDIA 9300M
graphics card.
Public bug reported:
When I boot my HP Pavillion dv3510nr notebook on battery power, the
battery indicator displayed by Gnome indicates that the computer is
plugged in, and the tooltip reads laptop battery is fully charged.
However, if I open up Gnome Power Manager I can see that the battery is
I have the same problem running 64-bit Ubuntu Karmic (2.6.31-16 kernel)
on an HP dv3510nr notebook.
--
[Karmic] battery is charged (when discharging) and unaccurate remaining battery
time
https://bugs.launchpad.net/bugs/491771
You received this bug notification because you are a member of
33 matches
Mail list logo
