the mdadm in 8.04 allready supports --incremental
--
degraded raid partitions will not mount at boot time
https://bugs.launchpad.net/bugs/214054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
According to the man page the mdadm in 8.04 supports the --incremental mode for
use in hotplug setups.
(like the udev rules driven assembly in ubuntu)
https://wiki.ubuntu.com/HotplugRaid
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notifi
*** This bug is a duplicate of bug 120375 ***
https://bugs.launchpad.net/bugs/120375
** This bug has been marked a duplicate of bug 120375
cannot boot raid1 with only one disk
--
degraded raid partitions will not mount at boot time
https://bugs.launchpad.net/bugs/214054
You received this
Public bug reported:
Binary package hint: mdadm
(8.04)
"mdadm --assemble --scan --no-degraded" creates inactive arrays that
will not start with a subsequent "mdadm --assemble --scan (--run)"
(N.B. that is what the the udev rules and boot scripts are trying to do
instead of using --incremental)
(The array will be crated inactive only if degraded of course)
--
-ARs fails with prior --no-degraded assemblies
https://bugs.launchpad.net/bugs/244792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Public bug reported:
Binary package hint: mdadm
When an external drive with a raid 1 member (say /dev/sdc1) gets disconnected
and is subsequently re-added with "mdadm --add /dev/md0 /dev/sdd1" mdadm quits
with "segmentation fault".
The udev rules supplied for mdadm should trigger a "mdadm --
Public bug reported:
Binary package hint: mdadm
(ubuntu 8.04)
When --incremental is used to assemble array incrementally (as is envisioned
for udev hotplugging)
--incremental --scan --run does not start anything.
"mdadm --incremental --scan --run" does not start the arrays that have
been part
Public bug reported:
Binary package hint: mdadm
There is inconsistency in the --no-degraded and --incremental option.
They will start degraded arrays, if they have been --run degraded
before.
Its clearer to report problems and and do interventions when staring degraded
raids stays the resposi
I added notes on how to adjust the ubuntu hotplug setup to cope with raid
devices at:
https://wiki.ubuntu.com/BootDegradedRaid
See under "Implementation".
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member
Public bug reported:
Binary package hint: acpi-support
The different power management packages in ubuntu are patched.
Where ist the documentation about the design reasoning and configuration
decisions.
Obviously part of the policy is that CPU frequency and powersettings are
controlled by deskto
Public bug reported:
Binary package hint: acpi-support
(ubuntu 8.04)
/etc/acpi/power.sh is called when switching between battery and AC. It
then includes the scripts in /etc/acpi/battery.d and /etc/acpi/ac.d .
After this it conditionally sets the laptop_mode and then hdparm -B and
-S values.
T
Public bug reported:
Binary package hint: acpi-support
When operating a laptop on AC but within a moving vehicle, disk idleing
("laptop-mode") is needed even on AC. Not nessecarily to lett the disk spin
down, but to leave the heads parked long enoght periods of time for shock
protection.
(http
Public bug reported:
Binary package hint: acpi-support
/etc/acpi/power.sh sets fixed hdparm values but gets called only when switching
from/to AC.
Disk spin-down and head parking should not be activated without controlled disk
idling. The regular uncoordinated logging or journaling activity m
Public bug reported:
Binary package hint: acpi-support
/etc/acpi/power.sh sets fixed hdparm values but gets called only when switching
power supply.
Disk spin-down and head parking should not be activated without controlled disk
idling. The regular uncoordinated logging or journaling activity
Public bug reported:
Binary package hint: acpi-support
Scripts in /etc/acpi/start.d and resume.d don't get executed.
For example setting the hdparm -B values there, as a workaround for Bug
# # (missing hdparm -B setting during boot and resume) does not work in
ubuntu 8.04.
Why are those useless
Public bug reported:
Binary package hint: laptop-mode-tools
Laptop-mode won't be activated unless ENABLE_LAPTOP_MODE=true is also
set in /etc/default/acpi-support. (/etc/init./laptop-mode checks that)
Therefor two places exist in ubuntu where disk-idleing (aka laptop-mode)
needs to be anabled. T
Public bug reported:
Binary package hint: laptop-mode-tools
Include scripts that call "/usr/bin/laptop_mode auto" in in /etc/acpi/ac.d,
battery.d, resume.d and start.d.
It is suggested to acpi-support to stop calling laptop-mode-tools and hdparm
directly.
#244831, #244832, #244833, #244836
Disk-idleing (aka "laptop-mode") and power states are quite separate things.
https://wiki.ubuntu.com/PowerManagement
Since ubuntu by default ships with laptop-mode-tools (thus disabled)
which handles all the things associated with disk-idleing,
(like mount options, hdparm options, low battery ex
Same in hardy
maybe putting a script in a pm-tools directory to lock the screens (and
open consoles Alt-Ctrl-F1, ...)
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Disk-idleing (aka "laptop-mode") and power states are quite separate things.
https://wiki.ubuntu.com/PowerManagement
Since ubuntu by default ships with laptop-mode-tools (thus disabled)
which handles all the things associated with disk-idleing,
(like mount options, hdparm options, low battery ex
Disk-idleing (aka "laptop-mode") and power states are quite separate things.
https://wiki.ubuntu.com/PowerManagement
Since ubuntu by default ships with laptop-mode-tools (thus disabled)
which handles all the things associated with disk-idleing,
(like mount options, hdparm options, low battery ex
Public bug reported:
Binary package hint: laptop-mode-tools
The lm-profiler is very helpful to identfy processes that write to the disk
periodically.
Since there are still disk spinn-up events without any write access
reported and no user activity going on, it would be good to have lm-
profile
This bug report is inteded to document the adaption of laptop-mode-
tools.
Wouldn't the patch to pm-tools be the matter of a pm-tools bugreport?
Though this bugreports may be linked with current pm-tools package
interfering with package laptop-mode-tools, I do think this bug needs to
be separate
I also noticed that mdadm -E also reported the member device flaged as
"write-mostly", even though I have never set this.
It may have been the installer because it was on a usb drive, I tested
on a new install but have not seen that.
So it may have been set during suspend/resume or have been pa
Public bug reported:
ubuntu 8.04 (2.6.24-19)
When mounting an ext3 fs with -t ext2 (to stop the constant journal
updates even no data is written or read), or when setting the mount
option in fstab, the kernel does not honor this.
The mount command lists the mount as ext2 but the filesystem is st
Using --incremental (Bug #157981) avoids this bug with ubuntu udev
hotplugging.
--
-ARs fails with prior --no-degraded assemblies
https://bugs.launchpad.net/bugs/244792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
/usr/share/initramfs-tools/scripts/local in 8.04 contains a checking
loop.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
--
mount script doesn't poll if root device has been initialized, preventing
udev+mdadm/lvm/cryptsetup to do its job
https://bugs.launchpad
Hi, some feedback about the patches.
Does it matter if call_failure_hooks is allways called?
"mdadm --run --scan" will start all arrays degraded not only the one needed for
the rootfs (and its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
After
# We've given up,
A while loop is calling panic. An if statement might look better.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
This applies to both initramfs and init.d scripts.
(root and home raids with devices on external disks take longer)
sleep 0.1 seconds intervalls are probably ok
** Summary changed:
- crypdisk setup does not wait properly for its devices to appear
+ crypdisk setup does not wait properly for its
Thank you for your comments and I'm sorry me slowly commenting overlapped with
your updated patches. (Of course you just worked to fast ;-), and fixed things
beforehand, perfect. :)
It's good to see that happen, and I've seen the merrit of the while loop
in intrepid now. It looks much better th
Hallo Reinhard,
are you refering to udev settling?
One of my usb disks is so slow in initializing, that it won't even trigger an
udev event until 8 seconds after udev has been started in initramfs.
Is the intrepid initramfs-tools/scripts/local-top/cryptroot viewable
somewhere on the web?
--
cry
I think it can be understood that using "mdadm --assemble --scan" instead of
doing selective "mdadm --run " calls on all devices ${ROOT} depends on
could be a reasonable and quick fix, if the information is not available
somwhere allready. Full support here.
My interest lies in getting the alg
Ok, a timeout loop looking for (slower) source devices sounds just what
I was missing / suffering from in hardy. I whish there were a webcvs or
somthing, would make it easier to compare/check, maybe there is and I
don't know. http://packages.ubuntu.com seems unavailable.
You may change status if y
> clearer when staring degraded raids stays the resposibility of startup
scripts.
Or the user manually starting an array. (possibly by right clicking)
Then, when two array disks are pluged in and it doesn't come up it is
always clear they the array is not complete.
--
inconsistency with the --n
Public bug reported:
Binary package hint: hdparm
Mention that (in debian and ubuntu) hdparm settings may be set by a script
startup script or when a device is plugged in by udev rules.
And that some packages like laptop-mode-tools can take care of setting some
hdparm parameters dynamicly during
Public bug reported:
Binary package hint: thunar
If there are two partiontions thunar will umount both if one is
unmounted. This is good because it makes unpluging save.
With one partition mounted through fstab though the error message does
not relate to the partition that one tried to unmount.
Public bug reported:
Binary package hint: debian-installer
On systems that are set up statically mdadm.conf is often used to list
the md devices that should be set up and the startup script just calls
mdadm --assemble --scan.
But on systems oriented towards hotplug ability this prevents arrays
f
Public bug reported:
Binary package hint: debian-installer
Following is a little informative text for the "set up users and
passwords" stage:
---
It is easy for multiple users to collaborate on a debian/ubuntu system.
Just keep in mind that access to files always depends on the permissions
of t
I just noticed that with slowly-appearing drives (with md devices on it) the md
device will not exist on the regular run of init-premount/mdadm. But since
introducing another waiting loop into the coldplug driven boot does not make
much sence it'll be preferable to just do degration with failur
Ah, packages server is back up.
I see the whole rootdelay loop has been copied from the local script and
also the dropping to the console when ${cryptsource} is missing.
But the recent local script will execute additional failure hooks. For
example degraded arrays will only get started by these.
Public bug reported:
Binary package hint: grub
(I don't know if this is grub or grub-installer)
It would be nice if grub-install could default to always setup the boot
sector of the / or /boot partition to be chainloadable also (as a
backup).
* Recovering from an overwritten MBR would be as ea
Hi, concerning the boot process you can test the current patches
https://wiki.ubuntu.com/BootDegradedRaid
for Bug #120375
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Well, the issue filed here, is
autocreated mdadm.conf prevents autodetection of cold- and hotplugging.
I found out not only the ARRAY lines, but also the homehost prevents
autotection of arrays.
The homehost feature may have been good to prevent systems with global
"mdadm --assemble --scan" boo
Just checked that the same applies for encrypted non-rootfilesystems,
too. (/etc/init.d/cryptdisks*) If for example external disks are slow
crypdisk fails.
Since md and lvm devices are set up by udev: init.d/cryptdisk-early and
cryptdisks (or just cryptdisk.functions) need to contain a timeout loo
4 of the 5 bugs taged as duplicates use a separate home array,
the fix will not let such systems boot degraded.
WARNING:
The mdadm - 2.6.7-3ubuntu2fix uses "mdadm --assemble --scan" on a system based
on udev hotplugging.
It will start all partly attatched arrays in degraded mode.
When any memb
To reproduce change /etc/udev/rules.d/85-mdadm* to do "mdadm
--incremental /dev/%k" and reboot.
After initramfs drops you to a console try mdadm --incremental manually.
--
--incremental not creating device nodes
https://bugs.launchpad.net/bugs/251663
You received this bug notification because yo
You can make your fat filesystem permissions look like matching to your default
umask.
Mount options:
for umask 002: dmask=002,fmask=113
for umask 022: dmask=022,fmask=133
(do not use the unspecific umask option)
As a workaround adjust your personal hal vfat mount options in the
gconf-edito
More information on a corresponging debian bug, that has been closed by
maintainers without resolving.
http://bugs.debian.org/344278
--
can't easily use unison-gtk to sync a local folder to my VFAT USB drive
https://bugs.launchpad.net/bugs/118283
You received this bug notification because you a
You can make your fat filesystem permissions look like matching to your
default umask.
Mount options:
for umask 002: dmask=002,fmask=113
for umask 022: dmask=022,fmask=133
(do not use the unspecific umask option)
As a workaround adjust your personal hal vfat mount options in the
gconf-editor, bu
More info in Bug #252351
--
The default umask should be set to 077. XDG_PUBLICSHARE_DIR should have umask
022
https://bugs.launchpad.net/bugs/204577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
It's ment to inform the user during install and GPL of course.
--
provide some info about users and file permissions
https://bugs.launchpad.net/bugs/252351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Oh, the problem with the current state is that umask is set all over the
place in shell config files, xsessions, and do not work for ssh logins
for example.
--
pam_umask.so missing in common-session
https://bugs.launchpad.net/bugs/253096
You received this bug notification because you are a member
Public bug reported:
pam_umask.so determines the umask (from system and user config files (see man
page)) and sets it accordingly.
The umask should not be set in common-session because it would override
all user specific configs, but the option usergroups is neccessary to
let it check if ubuntu
Public bug reported:
Ubuntu uses private user groups.
In order for the users to belong be added to the users group by default
/etc/security/groups needs to contain a line like this one:
*; *; *; Al-2400; users
(Context is also Bug #252351)
** Affects: pam (Ubuntu)
Importance
Public bug reported:
pam_umask.so is now included in libpam-modules.
** Affects: pam-umask (Ubuntu)
Importance: Undecided
Status: New
--
remove obsolete package pam-umask from repository
https://bugs.launchpad.net/bugs/253213
You received this bug notification because you are a m
initramfs/scripts/local in 8.04 does have a timeout loop for the root
device.
The remaining mdadm bug numbers are listed on
https://wiki.ubuntu.com/BootDegradedRaid
** Changed in: initramfs-tools
Status: New => Fix Released
--
mount script doesn't poll if root device has been initialized
Don't forget to "update-initramfs -k all -u" with the new udev rule
before rebooting, though.
--
--incremental not creating device nodes
https://bugs.launchpad.net/bugs/251663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Hello Steve,
thank you for improving ubuntu.
The example came from the pam_umask man page, maybe I had some typo.
There is some history why this bug should be fixed. It is a regression that is
now easy to fix.
Before pam was introduced "login" provided the central point to set the UMASK
value
FYI here is a summary of a Sep 2005 discussion in debian, by now it may be
added that, as pam_umask supports the "usergroups" feature, it is no longer
neccessary to set the umask to 002 for all users, with pam_umask's "usergroups"
feature it will check if users are in a private primary user gro
Actually, libpam-modules are installed by default and this new
pam_umask.so should be enabled in common-session by default (Bug
#253096).
pam_umask now recovers the umask functionality that login once had for
pam systems. (see man pam_umask) It gets the users umask from several
places.
That means
See Bug #253096 for the current state of umask setting.
--
login.defs references libpam-umask which is a obsolete package
https://bugs.launchpad.net/bugs/245210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
See Bug #253096 for the current state of umask setting.
--
/etc/login.defs umask cleanup
https://bugs.launchpad.net/bugs/71295
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Hello Steve,
yes, it may be that the adduser maintainer could change his package,
adding redundant group configuration to all users. But other than that,
some GUI tools don't seem to always rely on adduser (configuration) or
even (debian) policy for user and group ids, unfortunately. (It's
underst
Public bug reported:
Binary package hint: unison
Within the graphical profile wizard the right button aborts and the left button
is OK.
** Affects: unison (Ubuntu)
Importance: Undecided
Status: New
--
OK buttons in profile wizard reversed
https://bugs.launchpad.net/bugs/253283
Public bug reported:
Binary package hint: kdebase
To reproduce configure a domain that provides service discovery information in
kcontrolcenter / zeroconf.
For example "dns-sd.org".
Then you will be able to browse their published services under Network
shortcut in KDE.
But when following the
This is ubuntu 8.04 (hardy)
--
Links retrieved over dns-sd (service discovery) not working
https://bugs.launchpad.net/bugs/253282
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Public bug reported:
Binary package hint: unison
When files gets renamed in replica A, unison shows that the original file is
getting deleted in replica B and the renamed file is copied again.
This is particulary unfortunate with picture archives, as they get more
often renamed but less often
Sorry prior post was ment for another bug, the race condition with
degraded raids in this bug has different behaviour mentioned in
aformentioned kernle list archive.
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because you are a mem
When this occurs the drives are accessed continously, system hangs.
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
When this bug occurs the drives are accessed continously, system hangs.
--
-ARs fails with prior --no-degraded assemblies
https://bugs.launchpad.net/bugs/244792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Just to state that I am indifferent wether this is fixed with pam_group
or by adding to the default groups in adduser.
pam_group wouldn't intruduce much redundant info and fix existing
systems/users, too.
real group memberships would work for cron/at jobs? (But maybe they use
pam session I don't
Oh, hi,
To browse dns service discovery entries click the button on the right from the
"K" in the Controlbar (Kicker), then choose Network and then Network Services.
Or in Dophin it is: system:/remote/zeroconf/
** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
Links retrieved ov
Hi, thanks for the reply.
There seems to be at least two ways to mount partitions automatically.
One is the hotplug system mounts partitions, the other is it the
partition is mentioned in fstab and gets mounted during boot.
1. the specific steps or actions you took that caused you to encounter
When this bug is a regression from changes made to udev, is full on in
9.04 and needs syncing from the well and completely maintainded debian
package, how can it be marked incomplete?
** Changed in: gpsd (Ubuntu)
Status: Incomplete => Confirmed
--
gpsd depends on nonexistent /lib/udev/hot
Public bug reported:
Binary package hint: gpsd
Other apps seem to avoid the garmin_gsm kernel module for usb devices
and access those devices using the hotplug USB subsystem, instead of the
device created by garmin_gsm.
** Affects: gpsd (Ubuntu)
Importance: Undecided
Status: New
-
Why is the hotplug mechanism disabled by default in ubuntu?
As everything is hotplug enabled it seem gps devices are expected to be
hotplugable too.
--
gpsd depends on nonexistent /lib/udev/hotplug.functions
https://bugs.launchpad.net/bugs/367197
You received this bug notification because you a
I am sorry I don't understand what you are talking about.
On my ubuntu 9.04 system there is certenly no garmin_gsm module loaded
when connecting the device.
Plus I need to manually mount an usbfs and put add some udev line.
I don't know how is anyone suppost to know about this marble when you
ma
can't it be tagged 9.04?
** Changed in: gpsd (Ubuntu)
Status: Invalid => New
--
gpsd depends on blacklisted garmin_gps module
https://bugs.launchpad.net/bugs/388917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Full workaround to use garmin USB device in 9.04:
in /etc/modprobe/blacklist.conf:
#blacklist garmin_gps
The udev rule to add:
#cat /etc/udev/rules.d/51-garmin.rules
SYSFS{idVendor}=="091e", SYSFS{idProduct}=="0003", MODE="666"
The Filesystem to mount:
/etc/fstab:
none /proc/bus/usb us
You might want to set it to fix commited, if this is the case?
But then if garmin_gps is loaded by udev rules, wont't it again break
other packages that use usb: to fetch trackdata from the device?
--
gpsd depends on blacklisted garmin_gps module
https://bugs.launchpad.net/bugs/388917
You receiv
For the workaround, it is better to leave garmin_gps blacklisted
(stadard) so that it wont be loaded during boot, and just "sudo modprobe
garmin_gps" and "gpsd /dev/gps" when you need gpsd. (For gpsdrive,
tangoGPS etc.).
--
gpsd depends on blacklisted garmin_gps module
https://bugs.launchpad.net/
Blacklisting garmin_gps is not a bug. It allows apps to use libusb
instead.
Bug #236682 "garmin_gps.ko assumes you're using usbfs" exists.
--
gpsd depends on blacklisted garmin_gps module
https://bugs.launchpad.net/bugs/388917
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: gpsd
When a USB device, that is created by the garmin_gps module is specified,
the may not be needed/or should rather look in /dev/bus/usb for garmin_gps
devices.
An older report is: garmin.c: /proc/bus/usb is deprecated
http://developer.berlios.de/bugs
The mentioned report on berlios is wrongly set to won't fix, possible
due to misunderstanding it to request a switch to libusb.
--
gpsd checks on obsolete /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/388995
You received this bug notification because you are a member of Ubuntu
Bugs, which
Here is the output:
#ls -ld /sys/module/garmin_gps/drivers/*
/sys/module/garmin_gps/drivers/*/* /sys/module/garmin_gps/drivers/*/*/*
lrwxrwxrwx 1 root root0 2009-06-18 16:18
/sys/module/garmin_gps/drivers/usb:garmin_gps ->
../../../bus/usb/drivers/garmin_gps
lrwxrwxrwx 1 root root0 2009
> Best thing is probably to switch the gpsr to NMEA and just use that...
Even if my device supported it, I would think it would not help with
setting up the USB conectivity.
With
1) the udev rule to apply correct permissions to usb device (that shoud come
installed with some default init packag
Ah, here is a thread to refer to
http://www.nabble.com/gpsd---garmin-driver-broken-due-to-use-of--proc-bus-usb-td16342438.html
--
gpsd checks on obsolete /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/388995
You received this bug notification because you are a member of Ubuntu
Bugs, which
>>Best thing is probably to switch the gpsr to NMEA and just use that...
>Even if my device supported it, I would think it would not help with setting
>up the USB conectivity.
Got it, garmin usb binary format is diffrent from garmin serial binary.
Cornfiming: "large piece of crap" and forerunne
Public bug reported:
Binary package hint: gpsd
/usr/share/doc/gpsd/README.Debian.gz is missing in unbuntu.
No documentation is provided that and how /etc/default/gpsd has to be
configured (with dpkg-reconfigure).
Taken from Bug #367197:
Note that in order for gpsd.hotplug.wrapper to work at all
> But at the end I'd expect that the garmin stuff is just removed from
gpsd.
Yes, when the garmin_gps module or a garmin-userspace-driver layer that
can use libusb provides a serial tty device for gpsd, the garmin stuff
should probably be removed from gpsd.
(For devices that don't provide NMEA, t
Please include a pam-auth-profile to support the user private group
theme.
So that a debconf setting will put the line
"session optional pam_umask.so usergroups"
into the common-session config.
--
pam_umask.so missing in common-session
https://bugs.launchpad.net/bugs/253096
You received this bug
PAM may be more appropriate then shell rc files (etc/pam.d)
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
See "man pam_env", /etc/security/pam_env.conf and /etc/environment for
a solution to your problem.
If gdm used to source /etc/profile, and now stopped this misbehaviour,
that is good.
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
You received this bug
Hope the solution above helps to understand this bug as "invalid"?
Shell config files are supposed to work only for (even specific) shells, pam is
more a global method.
** Changed in: ubuntu
Status: New => Invalid
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.ne
Hope the solution above helps to understand this bug as "invalid"?
Shell config files are supposed to work only for (even specific) shells, pam is
more a global method.
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
You received this bug notification beca
Public bug reported:
Binary package hint: coreutils
Example: copying files from CD/vfat/etc. into the filesystem.
The files (all) will keep their executable bit and stay read only.
Even with the --no-preserver=mode option the current umask is ignored
(or only used in a substracting way when cr
Public bug reported:
pam_umask is the new and only facility to set the umask consistently for
different login shells, X, ssh, cron, ... .
But, pam_umask is not called in common-session. Instead the old
workaround since the introduction of pam once broke the login.defs UMASK
setting is still used
Public bug reported:
Binary package hint: base-files
Setting the umask in /etc/profile only works for some shells. It was
introduced into debian as a workaround, when the switch from login to
PAM broke the UMASK setting in /etc/login.defs.
Since recently pam_umask is included in pam, and provide
The comments in /etc/login.defs really need to be updated.
Here is an updated version of the section on login configuration
initialisation:
--8<- cut here --
#
# Login configuration initializations:
#
# ERASECHAR Terminal ERASE character ('\010' = backspace).
# KILLC
1 - 100 of 1101 matches
Mail list logo
