[Bug 244810] Re: inconsistency with the --no-degraded option
Example: 3 member mirroring array A) One disk fails during uptime, raid keeps running with 2 disks and on a reboot the array will get started through the --no-degraded or --incremental command with 2 disks. B) One disk fails during downtime, the array won't be started with --no-degraded or --incremental. A specific --run is necessary to start it degraded. -- inconsistency with the --no-degraded option https://bugs.launchpad.net/bugs/244810 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252345] Re: mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection
Two external drives containig a raid1 (storage for digicam) do not get detected and mounted when connected to another machine. ** Summary changed: - mdadm.conf is crated with explicit ARRAY statements prevents hotplug autodetection + mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection ** Changed in: debian-installer (Ubuntu) Status: Incomplete = Confirmed -- mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection https://bugs.launchpad.net/bugs/252345 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379233] Re: cp preserves mode with --no-preserve=mode
yeah, right a umask setting the exec bit ;-) ** Changed in: coreutils (Ubuntu) Status: Incomplete = Confirmed -- cp preserves mode with --no-preserve=mode https://bugs.launchpad.net/bugs/379233 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157981] Re: udev not using mdadm incremental
Hi, In 9.10 someone changed the mdadm udev rules to use --incremental without considering all the consequences that were already reported. https://wiki.ubuntu.com/ReliableRaid -- 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 488317] Re: installed system fails to boot with degraded raid holding cryptdisk
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- installed system fails to boot with degraded raid holding cryptdisk https://bugs.launchpad.net/bugs/488317 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251663] Re: --incremental not creating device nodes
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- --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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247153] Re: encrypted root initialisation races/fails on hotplug devices (does not wait)
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- encrypted root initialisation races/fails on hotplug devices (does not wait) https://bugs.launchpad.net/bugs/247153 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252345] Re: mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection https://bugs.launchpad.net/bugs/252345 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251646] Re: option to start selected arrays in auto-read mode (like --incremental)
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- option to start selected arrays in auto-read mode (like --incremental) https://bugs.launchpad.net/bugs/251646 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251164] Re: boot impossible due to missing initramfs failure hook integration
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- boot impossible due to missing initramfs failure hook integration https://bugs.launchpad.net/bugs/251164 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244810] Re: inconsistency with the --no-degraded option
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- inconsistency with the --no-degraded option https://bugs.launchpad.net/bugs/244810 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244808] Re: --incremental --scan --run does not start anything
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- --incremental --scan --run does not start anything https://bugs.launchpad.net/bugs/244808 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [gutsy] mdadm, initramfs missing ARRAY lines
Current state of ubuntu systems with md raid: https://wiki.ubuntu.com/ReliableRaid -- [gutsy] mdadm, initramfs missing ARRAY lines https://bugs.launchpad.net/bugs/136252 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 488158] Re: users-admin not following Debian policy
Uh, oh, I got that feeling you know ;-) Seriously, exactly as you write I was seeing the user being added to his primary private group. adduser tester produces this group entry: tester:x:1006: where users-admin produced: test:x:1005:test I had experienced much trouble before because of another tool not using adduser (with its hooks). (probably why I got suspicious so quickly) Thank you for your response and feedback. (Strange you're right, maybe adduser once belonged to base-passwd and the doc didn't get updated?) -- users-admin not following Debian policy https://bugs.launchpad.net/bugs/488158 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487729] [NEW] /etc/login.defs propagates incorrect information
Public bug reported:
The part about the UMASK setting is not correct and misleading.
As a contribution here is the corresponding section containing corrected
information (for inclusion in the next update).
--8- cut here --
#
# Login configuration initializations:
#
# ERASECHAR Terminal ERASE character ('\010' = backspace).
# KILLCHAR Terminal KILL character ('\025' = CTRL/U).
# UMASK Default umask value.
#
# The ERASECHAR and KILLCHAR are used only on System V machines.
# Prefix these values with 0 to get octal, 0x to get hexadecimal.
#
ERASECHAR 0177
KILLCHAR 025
#
# On PAM-enabled systems the UMASK setting in this file is used as a global
# default by pam_umask. (See man pam_umask for global and per user
# overrides.) Setting the umask in shell rc files (i.e. /etc/profile and
# others) is now discouraged in favour of the pam_umask mechanism.
#
# On non-PAM systems setting the umask in shell rc files, in addition
# to the UMASK setting here, can catches some more classes of user
# entries to system. (Logins through su, cron, ssh etc.)
# At the same time, using shell rc to set umask won't catch entries which use
# non-shell executables in place of login shell, like /usr/sbin/pppd for ppp
# user and alike.
# For discussion, see #314539 and #248150 as well as the thread starting at
# http://lists.debian.org/debian-devel/2005/06/msg01598.html
#
#
# UMASK 022 is the historical value in Debian,
# 027 or even 077 could be considered better for privacy if the users
# in their groups can not trust each other. There is no
# One True Answer here: Each sysadmin must make up his/her mind.
#
# Note that with login's USERGROUPS_ENAB feature, or the usergroups
# feature of pam_umask, if a user has a user private group
# the user's group permission umask byte is adjusted to match
# the user permission byte.
# This enables flawless collaboration of users in group directories
UMASK 022
--8---
** Affects: shadow (Ubuntu)
Importance: Undecided
Status: New
--
/etc/login.defs propagates incorrect information
https://bugs.launchpad.net/bugs/487729
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252351] Re: provide some info about users and file permissions
The informational text suggested is and can be updated on https://wiki.ubuntu.com/MultiUserManagement -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66328] Re: gksu breaks X apps when /etc/sudoers has NOPASSWORD:
Try checking if the /tmp/libgksu-*/.Xauthority file is created with the right ownership of the target user? -- gksu breaks X apps when /etc/sudoers has NOPASSWORD: https://bugs.launchpad.net/bugs/66328 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275304] Re: wrong ownership of .Xauthority and /tmp/libgksu-xxx
This may help tracking down this bug: The ownership is set correctly when using the the su method (by calling the gksu binary directly instead of of through the gksudo symlink AND with the -w option). This fails: $ gksudo -u firefoxuser firefox No protocol specifiedNo protocol specified Error: cannot open display: :0.0 The following works inspite of the warnings, however the password of the target user is allways required and you can not make use of the NOPASSWORD option in the sudoers file with that. $ gksu -w -u firefoxuser firefox (firefox:3439): GnomeUI-WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. (firefox:3439): GnomeUI-WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. (firefox:3439): GnomeUI-WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. --- It's quite a security shame that ubuntu ships without fully working running as different user mechanisms for so long. -- wrong ownership of .Xauthority and /tmp/libgksu-xxx https://bugs.launchpad.net/bugs/275304 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112414] Re: Error: Could not find service 'kfmclient' using Gnome
Does creating the symlink mentioned in Bug #281679 help you? -- Error: Could not find service 'kfmclient' using Gnome https://bugs.launchpad.net/bugs/112414 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379233] Re: cp preserves mode with --no-preserve=mode
Hi there, it's now a vfat fs plugged into a 9.10 system: ii coreutils 7.4-2ubuntu1 The GNU core utilities $ ls -l /media/USB/ -rwxr-xr-x 1 test.txt1 -rwxr-xr-x 1 test.txt2 $ cp /media/USB/test.txt1 . $ ls -l -rwxr-xr-x 1 test.txt1 $ cp --no-preserve=mode /media/USB/test.file2 . $ ls -l -rwxr-xr-x 1 test.txt1 -rwxr-xr-x 1 test.txt2 With --no-preserve I'd expect the new file to have the same permissions as a newly created file (umask dependent) but this is not the case. -- cp preserves mode with --no-preserve=mode https://bugs.launchpad.net/bugs/379233 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379406] Re: kuser ignores /etc/skel
*** This bug is a duplicate of bug 379397 *** https://bugs.launchpad.net/bugs/379397 Ah, thank you for clearing this. I must have missed the copy skeleton option when I first noticed that users created with kuser where set up so differently from other methods (independenly from the debian mechanisms). With the default to copy skeleton the difference might get less visible, though hooks, default group settings etc. would still be different. So I guess I can close this bug now, as duplicate of Bug #379397 / #379399, since using the debian usertools) will deal with it. ** This bug has been marked a duplicate of bug 379397 kuser is violating debian policy -- kuser ignores /etc/skel https://bugs.launchpad.net/bugs/379406 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeadmin in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 379397] Re: kuser is violating debian policy
Reasoning: Not using the debian mechanims results in not executing useradd hooks, different filepermissions, possibly not copying /etc/skel etc. (duplicates of this bug.) -- kuser is violating debian policy https://bugs.launchpad.net/bugs/379397 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] [NEW] gpsd depends on blacklisted garmin_gsm module
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 -- gpsd depends on blacklisted garmin_gsm 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367197] Re: gpsd depends on nonexistent /lib/udev/hotplug.functions
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 make the bugreport for gsmd disappear from launchpad? This took me just too long. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 usbfs 0 0
#sudo modprobe garmin_gps
#gpsd /dev/gps
--
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 mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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/bugs/388917 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388995] [NEW] gpsd checks on obsolete /proc/bus/usb/devices
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/?func=detailbugbug_id=13467group_id=2116 The issue is however unrelated to using libusb or another usb to tty layer, it prevents gsmd from working with garmin_gps on modern distros. ** Affects: gpsd (Ubuntu) Importance: Undecided Status: New -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388995] Re: gpsd checks on obsolete /proc/bus/usb/devices
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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-06-18 16:18 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0 - ../../../../devices/pci:00/:00:13.0/usb2/2-1/2-1:1.0 -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/bAlternateSetting -r--r--r-- 1 root root 4096 2009-06-18 13:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/bInterfaceClass -r--r--r-- 1 root root 4096 2009-06-18 13:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/bInterfaceNumber -r--r--r-- 1 root root 4096 2009-06-18 13:45 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/bInterfaceProtocol -r--r--r-- 1 root root 4096 2009-06-18 13:45 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/bInterfaceSubClass -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/bNumEndpoints lrwxrwxrwx 1 root root0 2009-06-18 13:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/driver - ../../../../../../bus/usb/drivers/garmin_gps lrwxrwxrwx 1 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/ep_02 - usb_endpoint/usbdev2.2_ep02 lrwxrwxrwx 1 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/ep_81 - usb_endpoint/usbdev2.2_ep81 lrwxrwxrwx 1 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/ep_83 - usb_endpoint/usbdev2.2_ep83 -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/modalias drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/power lrwxrwxrwx 1 root root0 2009-06-18 15:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/subsystem - ../../../../../../bus/usb -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/supports_autosuspend drwxr-xr-x 4 root root0 2009-06-18 13:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/ttyUSB0 -rw-r--r-- 1 root root 4096 2009-06-18 15:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/uevent drwxr-xr-x 5 root root0 2009-06-18 15:44 /sys/module/garmin_gps/drivers/usb:garmin_gps/2-1:1.0/usb_endpoint --w--- 1 root root 4096 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb:garmin_gps/bind lrwxrwxrwx 1 root root0 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb:garmin_gps/module - ../../../../module/garmin_gps drwxr-xr-x 2 root root0 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/drivers drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/holders -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/initstate drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/notes drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/parameters -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/refcnt drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/sections -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb:garmin_gps/module/srcversion --w--- 1 root root 4096 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb:garmin_gps/uevent --w--- 1 root root 4096 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb:garmin_gps/unbind lrwxrwxrwx 1 root root0 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps - ../../../bus/usb-serial/drivers/garmin_gps --w--- 1 root root 4096 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/bind lrwxrwxrwx 1 root root0 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module - ../../../../module/garmin_gps drwxr-xr-x 2 root root0 2009-06-18 16:18 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/drivers drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/holders -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/initstate drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/notes drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/parameters -r--r--r-- 1 root root 4096 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/refcnt drwxr-xr-x 2 root root0 2009-06-18 16:19 /sys/module/garmin_gps/drivers/usb-serial:garmin_gps/module/sections -r--r--r-- 1 root
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 package) 2) The usbfs mounted to /proc/bus/usb and 3) the garmin_gps module loaded aquisition of the current position works. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388995] Re: gpsd checks on obsolete /proc/bus/usb/devices
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388917] Re: gpsd depends on blacklisted garmin_gps module
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 forerunners do not provide NMEA output. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389020] [NEW] ubuntu is removing the documentation
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, one needs to 'dpkg-reconfigure gpsd', and have it start the daemon at boot, specify no device to use, let it use USB devices automatically and specify a control socket in the options to gpsd: '-F /var/run/gpsd.sock'. The control socket path is hardcoded in the hotplug script (/lib/udev/gpsd.hotplug). After dpkg-reconfigure, /etc/defaults/gpsd should have the following settings: START_DAEMON=true DAEMON_OPTS=-F /var/run/gpsd.sock DEVICES= USBAUTO=true ** Affects: gpsd (Ubuntu) Importance: Undecided Status: New -- ubuntu is removing the documentation https://bugs.launchpad.net/bugs/389020 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388995] Re: gpsd checks on obsolete /proc/bus/usb/devices
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, the driver might do the conversion to the garmin-serial binary protocoll or NMEA instead of gpsd.) In any case in the meantime at least the bugs #388917, #388995 and #389020 now document the problem and workaround for garmin usb devices. -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367197] Re: gpsd depends on nonexistent /lib/udev/hotplug.functions
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/hotplug.functions https://bugs.launchpad.net/bugs/367197 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379335] [NEW] pam_umask is missing a pam-auth-profile
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 (setting an umask in /etc/profile and unset/default umasks otherwhere). The line session optional pam_umask.so will need to be in /etc/pam.d /common-session in any case. You can use pam-auth-profile to make it at option. With the line session optional pam_umask.so usergroups even the user private group scheme is supported (if pam_umask can confirm the privacy of the group). ** Affects: pam (Ubuntu) Importance: Undecided Status: New -- pam_umask is missing a pam-auth-profile https://bugs.launchpad.net/bugs/379335 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379341] [NEW] remove/comment /etc/profile umask setting
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 provides a central facility with user overrides to set a consistent umask again. In /etc/profile please comment: # umask 022 # Setting a fixed umask in shell configuration files was only a workaround. # It is no longer needed and should not be done since the umask can be # set consistently with PAM. (See man pam_umask.) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- remove/comment /etc/profile umask setting https://bugs.launchpad.net/bugs/379341 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71295] Re: /etc/login.defs umask cleanup
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).
# KILLCHARTerminal KILL character ('\025' = CTRL/U).
# UMASK Default umask value.
#
# The ERASECHAR and KILLCHAR are used only on System V machines.
# Prefix these values with 0 to get octal, 0x to get hexadecimal.
#
ERASECHAR 0177
KILLCHAR025
#
# On PAM-enabled systems pam_umask uses UMASK as a global default.
# (Global and per user overrides are possible, see man pam_umask.)
# Therefore setting the umask in shell rc files (i.e. /etc/profile and
# others) is discouraged in favour of the pam_umask mechanism.
#
# On non-PAM systems setting the umask in shell rc files, in addition
# to the UMASK setting here, can catches some more classes of user
# entries to system. (Logins through su, cron, ssh etc.)
# At the same time, using shell rc to set umask won't catch entries which use
# non-shell executables in place of login shell, like /usr/sbin/pppd for ppp
# user and alike.
# For discussion, see #314539 and #248150 as well as the thread starting at
# http://lists.debian.org/debian-devel/2005/06/msg01598.html
#
#
# UMASK 022 is the historical value in Debian,
# 027 or even 077 could be considered better for privacy if the users
# in their groups can not trust each other. There is no
# One True Answer here: Each sysadmin must make up his/her mind.
#
# Note that with login's USERGROUPS_ENAB feature, or the usergroups
# feature of pam_umask, if a user has a user private group
# the user's group permission umask byte is adjusted to match
# the user permission byte.
# This enables flawless collaboration of users in group directories
UMASK 022
--8---
** Changed in: shadow (Ubuntu)
Status: Invalid = Confirmed
--
/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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245210] Re: login.defs references libpam-umask which is a obsolete package
jaunty no longer has this ** Changed in: shadow (Ubuntu) Status: New = Fix Released -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71295] Re: /etc/login.defs umask cleanup
The cleanup may actually be more than a wishlist item, because login.defs wrongly points out not to set UMASK and has leaves it commented out. (As was correct when pam_umask did not parse it.) -- /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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246192] Re: gksu to regular users broken
Still no gksu functionality to run apps as a differnt user (other then root) in ubuntu 9.04. (i.e. no way to quickly check your own email on the computer running all day at the reception with the account used by all the receptionists for example.) -- gksu to regular users broken https://bugs.launchpad.net/bugs/246192 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379397] [NEW] kuser is violating debian policy
Public bug reported: Binary package hint: kdeadmin All user/group managment tools have to rely on the adduser/useradd mechanism. But kuser is not even following the same rules when creating users/groups. ** Affects: kdeadmin (Ubuntu) Importance: Undecided Status: New -- kuser is violating debian policy https://bugs.launchpad.net/bugs/379397 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379399] [NEW] kuser ignores umask when creating homedirs
Public bug reported: Binary package hint: kdeadmin New homedirs get drwx-- permissions. (Instead of honoring the default drwxr-xr-x adduser setting. It is not using the adduser mechanism as stated by debian policy.) ** Affects: kdeadmin (Ubuntu) Importance: Undecided Status: New -- kuser ignores umask when creating homedirs https://bugs.launchpad.net/bugs/379399 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379399] Re: kuser ignores umask when creating homedirs
Debian policy states: Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow. (http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2) -- kuser ignores umask when creating homedirs https://bugs.launchpad.net/bugs/379399 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379406] [NEW] kuser ignores /etc/skel
Public bug reported: Binary package hint: kdeadmin kuser creates subdirecories in the homes, mimiking other OSes behaviour, but /etc/skel is not used for this. Instead /etc/skel might provide pub/, priv/ and incoming/ directories with correct permissions. And /home/groups/users/writable and /home/groups/users/readonly may be provided. Debian policy states: Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow. (http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2) ** Affects: kdeadmin (Ubuntu) Importance: Undecided Status: New ** Summary changed: - kmail ignores /etc/skel + kuser ignores /etc/skel ** Description changed: Binary package hint: kdeadmin - kmail creates subdirecories in the homes, mimiking other OSes behaviour, + kuser creates subdirecories in the homes, mimiking other OSes behaviour, but /etc/skel is not used for this. Instead /etc/skel might provide pub/, priv/ and incoming/ directories with correct permissions. And /home/groups/users/writable and /home/groups/users/readonly may be provided. Debian policy states: Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow. (http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2) -- kuser ignores /etc/skel https://bugs.launchpad.net/bugs/379406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379421] [NEW] Let groupadd create /home/group/groupname sgid directories
Public bug reported: Let groupadd have the option to create /home/group/groupname sgid directories. Sgid group directories are the means for users to easily collaborate on local files with the user private group scheme used in debian/ubuntu. Graphical tools can then adopt to this addgroup option. Debian policy states: Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow. (http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- Let groupadd create /home/group/groupname sgid directories https://bugs.launchpad.net/bugs/379421 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379431] [NEW] set up a /home/group/users directory
Public bug reported: Binary package hint: user-setup Set up a sgid /home/group/users directory for the users group if it doesn't exist, so that users are provided with a way to collaborate on local files. This will also seed the answer of how smaller groups can collaborate. For full control: The directory can contain private/, public/ and incoming/ subdirectories. The first two further containing readonly/ and writeable/ directories. ** Affects: user-setup (Ubuntu) Importance: Undecided Status: New -- set up a /home/group/users directory https://bugs.launchpad.net/bugs/379431 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379431] Re: set up a /home/group/users directory
The following example might be further enhanced: root:group (rwxrwsr-t) /home/share/group root:group (rwsrwsrwt) /home/share/group/incoming root:group (rwxrwx---) /home/share/group/private -- set up a /home/group/users directory https://bugs.launchpad.net/bugs/379431 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379421] Re: Let groupadd create /home/group/groupname sgid directories
The following example might be further enhanced: root:group (rwxrwsr-t) /home/share/group root:group (rwsrwsrwt) /home/share/group/incoming root:group (rwxrwx---) /home/share/group/private -- Let groupadd create /home/group/groupname sgid directories https://bugs.launchpad.net/bugs/379421 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379451] [NEW] provide /etc/skel/private/ and incoming/ dirs
Public bug reported: Binary package hint: base-files Please provide the directories /etc/skel/private (rwx--) and /etc/skel/incoming with appropriate permissions. In the user private group scheme used in debian/ubuntu the homedirs are created with permissions allowing the users to share and access files in each others home directories. These two directories will provide the users with a private space and a possibility give and receive files to/from other users. The following wiki page contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- provide /etc/skel/private/ and incoming/ dirs https://bugs.launchpad.net/bugs/379451 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253096] Re: pam_umask.so missing in common-session
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- pam_umask.so missing in common-session https://bugs.launchpad.net/bugs/253096 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379431] Re: set up a /home/group/users directory
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- set up a /home/group/users directory https://bugs.launchpad.net/bugs/379431 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379341] Re: remove/comment /etc/profile umask setting
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- remove/comment /etc/profile umask setting https://bugs.launchpad.net/bugs/379341 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252351] Re: provide some info about users and file permissions
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253103] Re: users not belonging to users group
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- users not belonging to users group https://bugs.launchpad.net/bugs/253103 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379421] Re: Let groupadd create /home/group/groupname sgid directories
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- Let groupadd create /home/group/groupname sgid directories https://bugs.launchpad.net/bugs/379421 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379335] Re: pam_umask is missing a pam-auth-profile
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- pam_umask is missing a pam-auth-profile https://bugs.launchpad.net/bugs/379335 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246192] Re: gksu to regular users broken
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- gksu to regular users broken https://bugs.launchpad.net/bugs/246192 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71295] Re: /etc/login.defs umask cleanup
The following wiki page now contains more information and ties together related bugs. https://wiki.ubuntu.com/MultiUserManagement -- /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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253096] Re: pam_umask.so missing in common-session
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367814] Re: LD_LIBRARY_PATH settings in /etc/profile lost
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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367814] Re: LD_LIBRARY_PATH settings in /etc/profile lost
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367814] Re: LD_LIBRARY_PATH settings in /etc/profile lost
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.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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367814] Re: LD_LIBRARY_PATH settings in /etc/profile lost
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379233] [NEW] cp preserves mode with --no-preserve=mode
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 creating the new copy), instead of using the umask for newly created files. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- cp preserves mode with --no-preserve=mode https://bugs.launchpad.net/bugs/379233 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253282] Re: Links retrieved over dns-sd (service discovery) not working
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252336] Re: error behaviour with multiple partions on one disk
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 the problem, I booted the system from a /boot partition that was on an USB device. 3. the behavior you actually encountered (in as much detail as possible). After boot the /boot partition was mounted because it is mentioned in fstab (uuid), the other partitions were mounted like hotplug devices. Then I wanted to remove the USB device. (I was not aware of /boot being mounted differently) So I right-clicked on one of the icons that stood for a partitions that resided on the USB device to have it unmounted. (And with it all the other partitions on the same device.) (It was not the /boot partition.) This gave an error message that I don't remember any more, but it did not point me to the /boot partition at all. Only after inspecting the output from mount did I notice the mounted /boot partition and could I unmount it on the console. So the error message I saw was probably related to the hotplugging system not being able to unmount the /boot partition. 2. the behavior you expected I'm not sure. The wish I formulated earlier was to display all partitions that reside on the same device in a subfolder on the desktop. For one, that way there would not be so much mess on the desktop with multiple hotplug disks attatched that contain several partitions. And second, I might have right-clicked on the folder (diskdevice) to unmount all partitions, and even if the error message did not help me, I might have noticed the /boot partition still mounted inside the folder afterwards. 4. you mention an error message; what is the exact wording? I'm sorry I don't remember. But I hope I could clarify what the problem was, even though it said somthing different. ** Changed in: thunar (Ubuntu) Status: Incomplete = New -- error behaviour with multiple partions on one disk https://bugs.launchpad.net/bugs/252336 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253319] Re: rename files instead of deleting and copying again.
Thank you for checking the command line. Well, this may then be a UI bug, now. ** Summary changed: - rename files instead of deleting and copying again. + UI not showing xferbycopying feature (renaming instead of deleting and retransfering) ** Description changed: - Binary package hint: unison + Binary package hint: unison version 2.27.57 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. + + (even though new feature xferbycopying should be true by default) This is particulary unfortunate with picture archives, as they get more often renamed but less often is the file contents changed. Can't unison queue the cases that look like filedeletions, and at the end, check if they have not just been renamed? And if that is true, just rename the file in the other replica without retransmitting all the files? Maybe this mechanism could also catch the programmed data loss mentioned under invariants in the documentation (moving a directory with ignored items). -- UI not showing xferbycopying feature (renaming instead of deleting and retransfering) https://bugs.launchpad.net/bugs/253319 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253319] Re: rename files instead of deleting and copying again.
(Tested with two local replicas.) -- rename files instead of deleting and copying again. https://bugs.launchpad.net/bugs/253319 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253319] Re: rename files instead of deleting and copying again.
Manual says: xferbycopying: The default value istrue. But the GUI does not seem to indicate that a renamed file will be copied: (a: file /b: absent) (a: deleted / b: u nchanged file) -- rename files instead of deleting and copying again. https://bugs.launchpad.net/bugs/253319 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253319] Re: rename files instead of deleting and copying again.
Oh very good, the changelog sounds just like what I was thinking about. Is this enabled by default? -- rename files instead of deleting and copying again. https://bugs.launchpad.net/bugs/253319 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268580] Re: Prompt for BOOT_DEGRADED=true|false in thre
When a disk fails in a running system a raid will run degraded. The System doesn't stop, and probably should't. The mdadm notification functionality brings this to the admins attention. So changing the default to bootdegraded=yes seems reasonable, once the patches are tested to work with enough configurations, and will be safe, if no other md devices than the ones neccessary to set up the fstab are touched. (This is when mdadm --incremental is used in udev rules and only specific raids will be run even degraded on boot with mdadm --run /dev/mdX) -- Prompt for BOOT_DEGRADED=true|false in thre https://bugs.launchpad.net/bugs/268580 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253103] Re: users not belonging to users group
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 know.) -- users not belonging to users group https://bugs.launchpad.net/bugs/253103 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244838] Re: remove laptop-mode settings from /etc/default/acpi-support
Yes, /etc/default/laptop_mode seems more sane as a second config file for laptop-mode-tools. As you mentioned in Bug #250935 we have to keep in mind that enabling the laptop-mode-tools by default is in fact a necessary change to fix the load cycling issue for example. IMHO laptop-mode-tools needs to be enabled by default. (/etc/default/laptop_mode does provide a place to optionally disable this autoinstalled package alltogether.) Whether laptop_mode (ENABLE_LAPTOP_MODE_ON_BATTERY) is enabled or not by default is another question. Since hardy, as a userfriendly distro suitable for laptops, has allways set /proc/sys/vm/laptop_mode to 2 when on battery (laptop-tools script hacked into pm-utils) I'd tend to propose that the laptop-mode.conf default (_ON_BATTERY=1) can just be kept. It steps in for the pm-utils script that got removed in intrepid. Enabling laptop-mode-tools can be considered a necessary bugfix change, and not entering /proc/sys/vm/laptop_mode on battery any more can be considered a regression. Looks as this would also make much transition magic unnecessary. The comment that debian packages have in place might suffice. -- remove laptop-mode settings from /etc/default/acpi-support https://bugs.launchpad.net/bugs/244838 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250935] Re: [intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils
Alexey, you did good in making the patch acceptable. (And since you had success, even better!) So second step would be to flip the settings the right way. hdparm -B254 needs to be reintroduced because bug #172282 has changed that setting in the meantime. (Yann who reported 254 did not work for him might very well have suffered from /etc/acpi/power.sh messing around. I happen to have a WD drive and have experienced exactly this.) -- [intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils https://bugs.launchpad.net/bugs/250935 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172282] Re: laptop-mode-tools uses hparm -B 255 instead of 254
Reopening. hdparm -B value 254 needs to be reintroduced because the fix to bug #250935 ([intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils) has migrated the old 255 setting from acpi-support into laptop-mode-tools. ** Changed in: laptop-mode-tools (Ubuntu) Status: Fix Released = Confirmed -- laptop-mode-tools uses hparm -B 255 instead of 254 https://bugs.launchpad.net/bugs/172282 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, you could have open a separate bug with your debconf patch to track your work and at the same time keep the comunity updated and able to give you feedback in a more organized manner. the default being BOOT_DEGRADED=false, which is the conservative/traditional behavior. Only some may consider this conservative behaviour a broken behavior, when a system on a redundant array of independent disks will degrade just fine when running, but won't even come up when booting. The reason for all this restrictivity with starting arrays comes from those start up scripts that use(ed) mdadm --assemble --scan to start arrays. Those run whatever (partially) connected arrays they can get hold of (in degraded mode). IMHO the right thing for start up scripts to do is to only start arrays that are needed to set up the root device and fstab, and degrade only them after a timeout. (/usr/share/initramfs-tools/hooks/cryptroot contains code to determine devices that the root device depends on.) Hotplugging can start any arrays afterwards, if it is completely attatched. The homehost feature is one suboptimal attempt to restrict array assembly. Same with the restriction with DEVICE or ARRAY definitions in mdadm.conf. Such restrictions add extra configuration burdens and should not be necessary with start up scripts that just correctly honor the root device and fstab information. In fact the homehost, and ARRAY restrictions prevent the hotplugging from beeing any better than manual configuration. Arrays still have to be configured in mdadm.conf (Bug #252345) . -- 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 Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Wow, Dustin we again wrote or comments almost simultaneously. Thank you for separating the issue. -- 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 Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I have separated out the issue of booting with degraded non-root arrays into Bug# 259145. As a user merely helping to gather info I can't say if updates to hardy (ubuntu 8.04) will be made available. Dustin? -- 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 Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 244838] Re: laptop-mode needs to be activated in /etc/default/acpi-support
Yes, I think you are right. Since the laptop-mode messing has fortunately been removed from acpi-support the setting is obsoleted there and serves only for confusion. Alexey wrote: It's interesting to know that current acpi-support in Debian unstable (1.109-5) has this comment in /etc/default/acpi-support: # Note: to enable laptop mode (to spin down your hard drive for longer # periods of time), install the laptop-mode-tools package and configure # it in /etc/laptop-mode/laptop-mode.conf. # # (Note to upgraders: earlier versions of the acpi-support package contained # an option to enable/disable laptop mode. This option has never actually # worked, and for that reason it has been removed.) (https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/250938/comments/5) --- This issue can be fixed when laptop-mode-tools and acpi-support from Debian is merged. package laptop-mode-tools: /etc/init.d/laptop-mode: drop sourcing of /etc/default/acpi-support (another packages conffile) package acpi-support: /etc/default/acpi-support: remove the ENABLE_LAPTOP_MODE setting and don't supress the above comment. -- laptop-mode needs to be activated in /etc/default/acpi-support https://bugs.launchpad.net/bugs/244838 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250935] Re: [intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils
Thank you for your comments. Then the current state I see in intrepid is this: - You still need to ENABLE_LAPTOP_MODE=1 in /etc/default/acpi-support (Bug 244838) - The /etc/laptop-mode/laptop-mode.conf default hdparm -B value has been changed from 254 to 255. This may be OK for consistency of the current state, but 254 is actually needed for many laptop harddisks to stop load cycling. (hdparm -B255 turns off the disk's apm feature, but this only turns off the spin down timer in many disks and doesn't increase the head parking timer at all, which is the issue here.) (Added that info to https://wiki.ubuntu.com/PowerManagement) Laptop-mode has always shipped with the sane defaults like 254. I see no real reason to keep suboptimal defaults from the ubuntu hack. The defaults can just be merged from the debian package I guess. -- [intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils https://bugs.launchpad.net/bugs/250935 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244838] Re: laptop-mode needs to be activated in /etc/default/acpi-support
When resposibility is reestablished for /etc/laptop-mode/laptop-mode.conf the ENABLE_LAPTOP_MODE_ON_BATTERY=yes default from debian's laptop-mode package will and can enable laptop_mode when on batteries, no problem. Package pm-utils has had a hacked laptop-tools script in hardy all the time that did just that. See https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/239419/comments/5 ** Summary changed: - laptop-mode needs to be activated in /etc/default/acpi-support + remove laptop-mode settings from /etc/default/acpi-support -- remove laptop-mode settings from /etc/default/acpi-support https://bugs.launchpad.net/bugs/244838 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59695] Re: High frequency of load/unload cycles on some hard disks may shorten lifetime
Hi, https://wiki.ubuntu.com/PowerManagement has been updated to respect the fixes for intrepid (ubuntu 8.10). You currently still need to follow the steps mentioned there for hardy (ubuntu 8.04) installs. (I guess Vincenzo Ciancia who reported his issues where fixed with recent hardy updates experienced a different bug.) -- High frequency of load/unload cycles on some hard disks may shorten lifetime https://bugs.launchpad.net/bugs/59695 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, you could have open a separate bug with your debconf patch to track your work and at the same time keep the comunity updated and able to give you feedback in a more organized manner. the default being BOOT_DEGRADED=false, which is the conservative/traditional behavior. Only some may consider this conservative behaviour a broken behavior, when a system on a redundant array of independent disks will degrade just fine when running, but won't even come up when booting. The reason for all this restrictivity with starting arrays comes from those start up scripts that use(ed) mdadm --assemble --scan to start arrays. Those run whatever (partially) connected arrays they can get hold of (in degraded mode). IMHO the right thing for start up scripts to do is to only start arrays that are needed to set up the root device and fstab, and degrade only them after a timeout. (/usr/share/initramfs-tools/hooks/cryptroot contains code to determine devices that the root device depends on.) Hotplugging can start any arrays afterwards, if it is completely attatched. The homehost feature is one suboptimal attempt to restrict array assembly. Same with the restriction with DEVICE or ARRAY definitions in mdadm.conf. Such restrictions add extra configuration burdens and should not be necessary with start up scripts that just correctly honor the root device and fstab information. In fact the homehost, and ARRAY restrictions prevent the hotplugging from beeing any better than manual configuration. Arrays still have to be configured in mdadm.conf (Bug #252345) . -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Wow, Dustin we again wrote or comments almost simultaneously. Thank you for separating the issue. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259127] Re: mdadm debconf configuration for boot_degraded=true|false
the default being BOOT_DEGRADED=false, which is the conservative/traditional behavior. Only some may consider this conservative behaviour a broken behavior, when a system on a redundant array of independent disks will degrade just fine when running, but won't even come up when booting. The reason for all this restrictivity with starting arrays comes from those start up scripts that use(ed) mdadm --assemble --scan to start arrays. Those run whatever (partially) connected arrays they can get hold of (in degraded mode). IMHO the right thing for start up scripts to do is to only start arrays that are needed to set up the root device and fstab, and degrade only them after a timeout. (/usr/share/initramfs-tools/hooks/cryptroot contains code to determine devices that the root device depends on.) Hotplugging can start any arrays afterwards, if it is completely attatched. The homehost feature is one suboptimal attempt to restrict array assembly. Same with the restriction with DEVICE or ARRAY definitions in mdadm.conf. Such restrictions add extra configuration burdens and should not be necessary with start up scripts that just correctly honor the root device and fstab information. In fact the homehost, and ARRAY restrictions prevent the hotplugging from beeing any better than manual configuration. Arrays still have to be configured in mdadm.conf (Bug #252345) . --- The default can be BOOT_DEGRADED=true, if the boot scripts refrain from using the depreceated mdadm --assemble --scan and selectively mdadm --run /dev/device. more info on: https://wiki.ubuntu.com/BootDegradedRaid -- mdadm debconf configuration for boot_degraded=true|false https://bugs.launchpad.net/bugs/259127 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259145] [NEW] home array not run when degraded on boot
Public bug reported: Binary package hint: mdadm It is said that the intrepid fix to Bug #120375 added support to mdadm and initramfs-tools for configurable booting degraded RAIDs, but a systems with /home on a degraded array doesn't come up. The particular array needs to be mdadm --run /dev/md1 after the fsck fails and the user is dropped to a console. A regular init script like /etc/init.d/mdadm-degrade (run earlier than mdadm) is missing that will run necessary arrays if they are degraded. (/usr/share/initramfs-tools/hooks/cryptroot contains code that may be usefull to determine devices that the fstab depends on.) ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- home array not run when degraded on boot https://bugs.launchpad.net/bugs/259145 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259145] Re: home array not run when degraded on boot
This issue has been separated out from Bug #120375 in order to track it separately. (Don't mark this as a duplicate, like 4 others before.) -- home array not run when degraded on boot https://bugs.launchpad.net/bugs/259145 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I have separated out the issue of booting with degraded non-root arrays into Bug# 259145. As a user merely helping to gather info I can't say if updates to hardy (ubuntu 8.04) will be made available. Dustin? -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259152] [NEW] lm-profiler: non-informational output with raid systems
Public bug reported: Binary package hint: laptop-mode-tools When the filesystem is on a raid device lm-profiler only reports only disk access by a process called md0_raid1 (the md module). Unfortunately this information does not help in identifying the processes that actually causes the disk access. ** Affects: laptop-mode-tools (Ubuntu) Importance: Undecided Status: New -- lm-profiler: non-informational output with raid systems https://bugs.launchpad.net/bugs/259152 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253283] Re: OK buttons in profile wizard reversed
Thank you for the screenshots. The button order also seems reversed in the subsequent windows to create new profiles. I noticed this because I kept hitting cancel after entering the info. -- OK buttons in profile wizard reversed https://bugs.launchpad.net/bugs/253283 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250938] Re: acpi-support should let laptop-mode-tools run properly
Alexey! I'd like to say thank you. For providing patches to the laptop-mode related things in ubuntu. It was good to see your work apear. -- acpi-support should let laptop-mode-tools run properly https://bugs.launchpad.net/bugs/250938 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250935] Re: [intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils
Hi Tormod, you asked: 3. Are some fixes needed in the pm-utils package as well? Can you reference other bug reports (with patches)? I do remeber two things, first Bug #239419 (pm-utils) pm-utils has laptop-tools script which conflicts with laptop-mode-tools has been wrongly set as a duplicate of this bug, but is actually messing with laptop-mode-tools job. IMHO the cleanest (and non misleading) fix would be to just remove the /usr/lib/pm-utils/power.d/laptop-tools script from pm-tools. (laptop- mode-tools does all that in a configurable way) And as Alexey has pointed out in a comment, as this script has (and currently is) setting /proc/sys/vm/laptop_mode unconditionaly. So it is tested is may be time now to enable laptop-mode by default with package laptop-mode-tools. (It will still only activate laptop-mode on battery by default.) But then finally Bug #59695 (High frequency of load/unload cycles on some hard disks may shorten lifetime) can be fixed. Simply by enabling CONTROL_HD_POWERMGMT=1 in laptop-mode.conf. The NOLM_AC_HD_POWERMGMT=254 setting that is present will then disable head parking by default. -- [intrepid] laptop-mode-tools needs to change its default settings to match acpi-support and add hooks for pm-utils https://bugs.launchpad.net/bugs/250935 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252351] Re: provide some info about users and file permissions
Thank you for reassigning the bug. Yes, the info should really be in the documentation, too. I have filed this from practice. Many support requests deal with (new, aka ex windows) users that have installed ubuntu not able to easily collaborate with other users on their ubuntu installation. The explanation screen is almost empty when setting up the initial user account, and the question arises in new users What,... is this good for? The info should not prevent people to get though the installer as quickly as possible. But it will set the caucious first time installers right on track, just when they have taken the time to install their system. (They won't read docs on this later on, but complain about not being able to collaborate on ubuntu.) It might be possible to make this even more brief, if for example group directories will be created with new groups by default. ubuntu is linux for humans It's not about how to fiddle with unix file permissions, but how to collaborate in an debian/ubuntu setting. FYI the issue of users not belonging to users group is now separated out into Bug #253103 (Please comment if you think that that is a bug that needs fixing, as there is some hesitance.) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253096] Re: pam_umask.so missing in common-session
The wording of man pam_umask seems pretty much the same as what used to be in login.defs before. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=login.defs.diff;att=1;bug=282822 I have also made the experience that some graphical user managment tools do not keep gids eqal to uids and that tools create subdirecories in the homes, mimiking other OSes behaviour, but /etc/skel is not used for this. The writers of desktop environment tools do not seem to allways follow unix philosophy. I noticed debian policy states: Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow. (http://www.debian.org/doc/debian-policy/ch- opersys.html#s9.2) --- Just as you write, configuring pam_umask to provide unified means to set the umask for all sessions does not yet automatically (re)enhence default permission handling. If the default umask enables easy usability of permission handling, or does pretty much not support it, it should maybe be less the the result of the shiped pam implementation and adhere to the all time shiped configuration. (USERGROUPS_ENAB yes) Which grants 002 only if it's pretty safe and a feature, many times reported to not work properly and hacked around. (Even though many ubuntu users may have never noticed, and may just think file permissions just allways are like an inflexible pita style thing.) As the user groups created by default have all the time been private ones, it should be pretty save to let the 022-002 mapping do its work for them. The corner case being of course those that are really using sticky sgid directories without actually figuring out to change the umask. Meaning those that manually change filepermissions every time to be able to collaborate with other users, even when they decide to expicitly save stuff into special group places instead of saving into more private (sub)dirs. If we find a good name for that behaviour, we could actually provide sticky non-sgid subdirectory examples to publish something readonly within a group. (Does /home/share/group/writings /home/share/group/readings compare to /home/user/private?) From the point of the implemented private user groups, if you want that other members of a group can work on a file together with you, they need to be in a group with them and you have to save the file into a special setgid directory, if not keep the file at home, in a private place if you don't want others to be able to read it. For shared write access you save it under the (sgid) group directory. This seems to be the feature and having to fiddle with file permissions is bugging users. Private user groups with umask 002 and a nice set of default directories are quite a feature, I would say. They should be save as long as filessystems are not transfered verbatim to systems with other group setups, but then, when transfering filesystems to other machines one allways has to watch for differences in IDs, anyway. All copy processes should honor the umask on the target systems, if not explicitly overridden to preserve permissions and numerical ids. Maybe I just don't understand that much of the private user group approach that I see it as quite important to provide it for ubuntu users to easily share and lock up files by choosing the location and not having to fiddle with file permissions. From experience though, I've gotton complaints about those ever complicated and never satisfying file permissions, and wishes to just do away with them, but with private user groups, umask 002, the almost self explanatory fact that access depends on the location where you put stuff (directiory) _and_ file permissions, and by providing some (sample) directories, users fiddling and getting fed up with filepermissions gets allmost a non issue. Ok, just save that privately in our ... group dir (/home/share/.../private), I'll take care of it! (Hmm, you made me think of grouip/writings now and I seem to like that idea.) What would be another way to provide good collaboration experience? If ubuntu really allways intended to ship current user and file permission setup with that umask, and the 022 setting in effect together with USERGROUPS_ENAB yes has not been just a result one wasn't particularily aware of, stemming from the once missing pam functionallity, waiting for a fix, and admins adjusting umask settings for multi user systems, what is the reason to ship private user groups? Comparing to umask 022 systems with all users belonging to the users group, users do not only have to manualy give write permission, to say to the users group in the simpliest case, but also need to change the group ownership on any file to collaboorate on it with others. (Note that its asumed the users group is usable and not empty.) This state does not look too consistent and in the best interest of the users to me, and might be just due to an unfortunate effect that the introduction of pam once had in debian. --- It's probably a
[Bug 253103] Re: users not belonging to users group
I agree, there are of course much more fine grained methods than the group of all users. And to be honest when adminstering larger systems the users group is probably not good for much more then giving all users write access to some device, or to files that are served on the net. Now, it's not unlikely that, as you are familiar with things like creating groups and adequate directory hierachies or ACLs, we tend to just go directly to what we know exists. When we think more like a beginner, as new to the GNU of linux, or how we often get to know things, they may not be aquainted with directory and file permissions etc. at first. But if we asume for a moment we see a directory called /home/share/users with a private subdirectory, where all users of a family computer can put stuff for all to update and modify. (Possibly including group/writings and group/readings subdirs.) It's foreseeable that finer grained group control might come to mind at some point. But then the answer is allready there, too. The next thoughts are special user groups, how the group direcotries are used is already old news then. In a sense the users group is the only group that can be set up by default, to work with right away and it serves as a seed. It is already there, usable if not just left empty and visible with a users group directory, for human beings to discover the logic of file permissions. And its a reasonable answer to the question: I can easily share files around the globe, but how do I share files with my honney who has another account on our ubuntu machine at home? Though, it is a little addition, using pam_group for this should be rather light on ressources and not make any server without users or really large multi-user setups run less perfect. (And keep /etc/group (or ldap etc.) less cluttered.) As a modern distribution, oriented towards usability, ubuntu of course used pam from the start, it may just feel like a regression for users were able to use unix file permissions that way for ages. Without the users group the easiest but not recomendable way is to resort to the bad habit of granting world write access. There is no risk associated with users belonging to the users group, or is there? Honestly, I did consider fixing users not belonging to the users group a non-issue. Just somthing that has been forgotten at some point of time. I consider the users group as a feature that can be used but does not have to. But if it is to be used it has to be set up to contain all users, there is no other way around it. -- users not belonging to users group https://bugs.launchpad.net/bugs/253103 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
