Bug#744856: live-build produces unbootable "wheezy" image
Package: live-build Version: 4.0~alpha33-1 Severity: important Dear Maintainer, I'm trying to assemble basic Debian 7 "wheezy" iso according to the Live Manual: http://live.debian.net/manual/unstable/html/live-manual/the-basics.en.html#174 I have no confinguration files in place, just do this: $ lb config --distribution wheezy $ sudo lb build The image was built successfully, but after I've boot it up, I got on my screen: Loading, please wait... /init: .: line 220: can't open '/scripts/live' [0.922446] Kernel panic - not syncing: Attempted to kill init! [0.922755] Pid: 1, comm: init Not tainted 3.2.0-4-amd64 #1 Debian 3.2.54-2 [0.923088] Call Trace: It seems that resulting image doen't contain necessary packages to configure a live system during the boot, such as: live-boot live-boot-initramfs-tools live-config live-config-sysvinit live-tools Why so? Exactly the same approach with live-build versions 3.x installed creates a completely working image. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii debootstrap 1.0.59 ii python3 3.3.4-1 Versions of packages live-build recommends: ii cpio 2.11+dfsg-2 pn live-boot-doc pn live-config-doc ii live-manual-txt [live-manual] 1:4.0~alpha11-1 live-build suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742129: live-build: update Debian release version strings
19.03.14 18:54, Daniel Baumann wrote: > close 742129 4.0~a1-1 > thanks > > On 03/19/2014 03:13 PM, Denys Gavrysh wrote: >> Please update Debian release version strings to the latest ones in the file >> /usr/share/live/build/functions/releases.sh. Now it contains too old values: > > thanks for your report, however, we do not support building anything but > squeeze and wheezy with the 3.x version. for jessie, the 4.x version can > be used. Just to be clear. What I tried to do is built wheezy image with the 3.x version *on my jessie host system*, not to build jessie live system. By the way it's really simple to inject proper Debian release version into your configuration. Here is my auto/config file: [ -f config/binary ] && \ cat >> config/binary <
Bug#744939: live-build: bootstrap-{c,}debootstrap doesn't clean /etc/hosts
Package: live-build Version: 4.0~alpha33-1 Severity: minor Tags: upstream Dear Maintainer, I've encountered small issue in my new wheezy live system created with lasest live-build: user@debian:~$ sudo -i sudo: unable to resolve host debian root@debian:~# cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters root@debian:~# cat /etc/hostname debian root@debian:~# I have no files in includes.chroot and no customisations at all, only the package lists. Otherwise, there is the correct /etc/hosts inside the running system prepared with live-build 3.0.5-1: 127.0.0.1 localhost debian Also, local chroot/etc/chroot file is present but empty in this case. I've found that stable version of live-build is forcibly cleaning /etc/hosts in /usr/lib/live/build/bootstrap_cdebootstrap: 140 # Deconfiguring cdebootstrap configurations 141 rm -f chroot/etc/apt/sources.list 142 rm -f chroot/etc/hosts and /usr/lib/live/build/bootstrap_debootstrap: 144 # Deconfiguring debootstrap configurations 145 rm -f chroot/etc/hosts So, the script chroot_hosts performs correctly later in the build process, and live-config is able to create proper /etc/hosts during the live system boot. But the bootstrap scripts from live-build 4.0 are written in Python 3 and don't take care about /etc/hosts. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii debootstrap 1.0.59 ii python3 3.3.4-1 Versions of packages live-build recommends: ii cpio 2.11+dfsg-2 pn live-boot-doc pn live-config-doc ii live-manual-txt [live-manual] 1:4.0~alpha11-1 live-build suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745020: live-build doesn't generate splash for syslinux
Package: live-build
Version: 4.0~alpha33-1
Severity: minor
Tags: upstream
Dear Maintainer,
The image created with latest live-build doesn't show that fancy syslinux
splash screen with some useful information.
In the binary/isolinux directory I found only the raw splash.svg.in template.
There is the faulty line in the /usr/lib/live/build/binary_syslinux script:
254 for _FILE in "${_TARGET}"/*.cfg ${_TARGET}/*.svg
We have no *.svg files in the syslinux configuration directories, but only this:
$ ls -1 /usr/share/live/build/bootloaders/*linux/*.svg*
/usr/share/live/build/bootloaders/extlinux/splash.svg.in
/usr/share/live/build/bootloaders/isolinux/splash.svg.in
/usr/share/live/build/bootloaders/pxelinux/splash.svg.in
/usr/share/live/build/bootloaders/syslinux/splash.svg.in
So, we need to rename all the files to *.svg or fix the line.
Thanks.
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages live-build depends on:
ii debootstrap 1.0.59
ii python3 3.3.4-1
Versions of packages live-build recommends:
ii cpio 2.11+dfsg-2
pn live-boot-doc
pn live-config-doc
ii live-manual-txt [live-manual] 1:4.0~alpha11-1
live-build suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745134: live-build: please add man pages for lb commands
Package: live-build Version: 4.0~alpha33-1 Severity: minor Dear Maintainer, There are missing manpages in the live-build package, such as: lb(1) lb_binary(1) lb_bootstrap(1) lb_build(1) lb_chroot(1) lb_clean(1) lb_config(1) lb_source(1) Also, this kind of behaviour is unusual for me: $ lb --help No manual entry for lb See 'man 7 undocumented' for help when manual pages are not available. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii debootstrap 1.0.59 ii python3 3.3.4-1 Versions of packages live-build recommends: ii cpio 2.11+dfsg-2 pn live-boot-doc pn live-config-doc ii live-manual-txt [live-manual] 1:4.0~alpha11-1 live-build suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742129: live-build: update Debian release version strings
Package: live-build Version: 3.0.5-1 Severity: minor Dear Maintainer, Please update Debian release version strings to the latest ones in the file /usr/share/live/build/functions/releases.sh. Now it contains too old values: --- # Debian releases RELEASE_squeeze="6.0.7" RELEASE_wheezy="7.0.0" --- This affects only the disk info and boot loader menus, but it will be good for distinguishing releases. Thanks in advance. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii debootstrap 1.0.59 Versions of packages live-build recommends: ii cpio 2.11+dfsg-1 pn gnu-fdisk pn live-boot-doc pn live-config-doc ii live-manual-txt [live-manual] 1:3.0.2-1 Versions of packages live-build suggests: pn debian-keyring ii dosfstools 3.0.16-2 ii fakeroot1.18.4-2 pn git ii gpgv1.4.16-1.1 pn loadlin pn memtest86+ | memtest86 pn mtools ii parted 2.3-16 pn squashfs-tools | mtd-tools ii sudo1.8.9p5-1 pn syslinux | grub pn uuid-runtime pn win32-loader pn xorriso -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661230: lightdm: passwordless login doesn't work
Hi, I have set up lightdm to support guest accounts. The problem lies in default PAM setting in Debian. Here is the line that permits password-less logins on "secure" ttys in /etc/pam.d/common-auth file: - auth[success=1 default=ignore] pam_unix.so nullok_secure - We need just to allow blank password in any case. What I actually done is: # sed -e 's/_secure//' /etc/pam.d/common-auth > /etc/pam.d/common-auth-insecure # sed -i -e 's/common-auth/&-insecure/' /etc/pam.d/lightdm And it works, also preventing logins without password by SSH. So, according to configured central authentication policy, lightdm (which is not a plain tty AFAIK) behavior seems correct. -- Denys Gavrysh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#590600: rdiff-backup to an nfs
I confirm this bug in version 1.2.8.
NFS share mounted on /backup. Output:
# rdiff-backup /bin/ /backup/
Exception '[Errno 116] Stale NFS file handle:
'/backup/rdiff-backup-data/rdiff-backup.tmp.0/A'' raised of class ''exceptions.OSError'>':
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
334, in Backup
rpout.conn.fs_abilities.backup_set_globals(rpin, force)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/fs_abilities.py",
line 922, in backup_set_globals
dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/fs_abilities.py",
line 156, in init_readwrite
self.set_case_sensitive_readwrite(subdir)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/fs_abilities.py",
line 303, in set_case_sensitive_readwrite
upper_a.setdata()
File "/usr/lib/python2.6/dist-packages/rdiff_backup/rpath.py", line
908, in setdata
self.data = self.conn.rpath.make_file_dict(self.path)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/rpath.py", line
287, in make_file_dict
return C.make_file_dict(filename)
Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 30, in
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib/python2.6/dist-packages/rdiff_backup/Main.py", line
334, in Backup
rpout.conn.fs_abilities.backup_set_globals(rpin, force)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/fs_abilities.py",
line 922, in backup_set_globals
dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/fs_abilities.py",
line 156, in init_readwrite
self.set_case_sensitive_readwrite(subdir)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/fs_abilities.py",
line 303, in set_case_sensitive_readwrite
upper_a.setdata()
File "/usr/lib/python2.6/dist-packages/rdiff_backup/rpath.py", line
908, in setdata
self.data = self.conn.rpath.make_file_dict(self.path)
File "/usr/lib/python2.6/dist-packages/rdiff_backup/rpath.py", line
287, in make_file_dict
return C.make_file_dict(filename)
OSError: [Errno 116] Stale NFS file handle:
'/backup/rdiff-backup-data/rdiff-backup.tmp.0/A'
I just commented this lines in rpath.py file and exception has disappeared:
if os.name != 'nt':
try:
return C.make_file_dict(filename)
except OSError, error:
# Unicode filenames should be process by the
Python version
if error.errno != errno.EILSEQ and error.errno
!= errno.EINVAL:
raise
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705458: lxc-create does not pass quoted option arguments to template script
Package: lxc Version: 0.9.0~alpha3-1 Severity: normal Tags: patch upstream Dear Maintainer, It seems that quoting or escaping in option argument for template is unusable with lxc-create. For example, I'm trying to set preseed file with space in path for debian: sudo lxc-create -n debian-wheezy-amd64 -t debian -- --preseed-file="/tmp/Work files/lxc.cfg" The file is present on the filesystem, but template script just ignores it. Same result with this command: sudo lxc-create -n debian-wheezy-amd64 -t debian -- --preseed-file=/tmp/Work\ files/lxc.cfg Then I moved the file to /tmp/Work/lxc.cfg, script works as expected: sudo lxc-create -n debian-wheezy-amd64 -t debian -- --preseed-file=/tmp/Work/lxc.cfg 'lxc-create' invokes template in line 327: $template_path --path=$lxc_path/$lxc_name --name=$lxc_name $? This change fixes script behaviour: $template_path --path=$lxc_path/$lxc_name --name=$lxc_name "$@" Need to mention, quoting "$?" also works fine for my particular example, but I discovered that with other template options it some times confuses 'getopt' utility used in most templates to parse options. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.49 ii libapparmor1 2.7.103-4 ii libc6 2.13-38 ii libcap21:2.22-1.2 ii multiarch-support 2.13-38 Versions of packages lxc recommends: ii debootstrap 1.0.48 ii libcap2-bin 1:2.22-1.2 Versions of packages lxc suggests: pn debian-keyring ii gpgv1.4.12-7 pn live-debconfig-doc ii rsync 3.0.9-4 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705458: lxc-create does not pass quoted option arguments to template script
Package: lxc Version: 0.9.0-3 Followup-For: Bug #705458 Daniel, Thank you for the quick fix, but I suggest that positional parameters passed to the template script should be quoted, like I mentioned before: 334 $template_path --path=$lxc_path/$lxc_name --name=$lxc_name "$@" With unquoted $@ expansion, if some template parameter argument contains '-' or '+' symbols with space before it, even quoted or escaped, getopt from the template script raises "invalid option" errors or simply ignores the rest of parameters. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701689: lxc-create failed to execute template
Package: lxc
Version: 0.9.0~alpha2-10
Severity: normal
Tags: patch
Dear Maintainer,
I have tried to create Debian container with following command:
sudo lxc-create -n debian -t debian
It was working just fine until I changed my current directory to /var/lib/lxc.
Here is the output:
denys@pc-deg:/var/lib/lxc$ sudo lxc-create -n debian -t debian
lxc-create: No config file specified, using the default config /etc/lxc/lxc.conf
sha1sum: debian: Is a directory
/usr/bin/lxc-create: 328: /usr/bin/lxc-create: debian: not found
lxc-create: failed to execute template 'debian'
lxc-create: aborted
denys@pc-deg:/var/lib/lxc$
It seems that lxc-create script considers newly created container directory as
template.
I've added additional check to the script and the problem has gone:
--- /usr/bin/lxc-create 2013-02-09 09:12:29.0 +0200
+++ /usr/bin/lxc-create.fixed 2013-02-26 09:39:25.604605629 +0200
@@ -281,7 +281,7 @@
if [ ! -z "$lxc_template" ]; then
# Allow for a path to be provided as the template name
-if [ -x "$lxc_template" ]; then
+if [ -x "$lxc_template" ] && [ -f "$lxc_template" ]; then
template_path=$lxc_template
else
template_path=${templatedir}/lxc-$lxc_template
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.49
ii libapparmor1 2.7.103-4
ii libc6 2.13-38
ii libcap21:2.22-1.2
ii multiarch-support 2.13-38
Versions of packages lxc recommends:
ii debootstrap 1.0.44
ii libcap2-bin 1:2.22-1.2
Versions of packages lxc suggests:
pn debian-keyring
ii gpgv1.4.12-7
pn live-debconfig-doc
ii rsync 3.0.9-4
-- debconf information:
* lxc/directory: /var/lib/lxc
lxc/title:
lxc/auto: true
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701800: lxc-debian template script ignores tzdata selections in preseed file
Package: lxc
Version: 0.9.0~alpha2-10
Severity: normal
Tags: patch
Dear Maintainer,
There is the problem with tzdata package preseeding in debian (debconfig)
template.
My preseed.cfg file contains these selections among others:
##
tzdata tzdata/Areas select Europe
tzdata tzdata/Zones/Europe select Kiev
##
I had create new container with this command:
sudo lxc-create -n debian -t debian --
--preseed-file=/home/denys/Work/lxc/preseed.cfg
But default time zone in the container was set to 'Etc/UTC'.
debconf-show tzdata
tzdata/Zones/Australia:
tzdata/Zones/US:
tzdata/Zones/Asia:
* tzdata/Zones/Etc: UTC
tzdata/Zones/SystemV:
tzdata/Zones/Africa:
tzdata/Zones/America:
tzdata/Zones/Arctic:
tzdata/Zones/Pacific:
* tzdata/Areas: Etc
tzdata/Zones/Antarctica:
tzdata/Zones/Atlantic:
* tzdata/Zones/Europe: Kiev
tzdata/Zones/Indian:
Previous selection was overriden.
I have found that dpkg-reconfigure actually prefers settings in '/etc/timezone'
over debconf answers.
Removing the file and reconfiguring tzdata package again fixes timezone
configuration.
This patch implements my solution:
--- lxc-debian~ 2013-02-09 09:12:29.0 +0200
+++ lxc-debian 2013-02-27 12:32:21.317699113 +0200
@@ -262,6 +262,7 @@
# FIXME: All packages of priority of essential need to be reconfigured to
reflect choices from preseeding
if grep -qs tzdata "${_PRESEED_FILE}"
then
+Chroot "${_ROOTFS}" "rm -f /etc/timezone"
Chroot "${_ROOTFS}" "DEBIAN_FRONTEND=noninteractive DEBIAN_PRIORITY=criticial
dpkg-reconfigure tzdata"
fi
For now debian template considers tzdata preseeding.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.49
ii libapparmor1 2.7.103-4
ii libc6 2.13-38
ii libcap21:2.22-1.2
ii multiarch-support 2.13-38
Versions of packages lxc recommends:
ii debootstrap 1.0.44
ii libcap2-bin 1:2.22-1.2
Versions of packages lxc suggests:
pn debian-keyring
ii gpgv1.4.12-7
pn live-debconfig-doc
ii rsync 3.0.9-4
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714620: acpi-support: Laptop's display won't wake from DPMS off state on lid open event with xrandr method
Package: acpi-support
Version: 0.140-5
Severity: normal
Tags: patch
Dear Maintainer,
There is a problem with waking from DPMS off state then my laptop's lid is open
while using xrandr.
Usage scenario:
1. Set "DISPLAY_DPMS=xrandr" and "XRANDR_OUTPUT=LVDS1" options in
/etc/default/acpi-support files.
2. Close the lid, Laptop panel go dark.
3. Open the lid and nothing happens, screen remain dark, keyboard and mouse
movements does not help.
I have discovered that the problem lies in /etc/acpi/lid.sh on line 35:
xrandr invoked with hardcoded output 'LVDS', but my Intel KMS driver assign
'LVDS1' name.
I suggest to use variable with default value, for example:
xrandr --output ${XRANDR_OUTPUT:-LVDS} --auto
Same can be applied in /usr/share/acpi-support/screenblank:
xrandr --output ${XRANDR_OUTPUT:-LVDS} --off
This worked just fine until I have uncommented "LID_SLEEP=true" option.
I think that some race condition is happening in such case:
then lid was closed, screenblank script invokes xrandr with --off and laptop
immediately goes to sleep.
It seems display does not have time to actually turn off by xrandr, it was
turned off by pm-suspend.
And then laptop awake, lid open event occurs and display is enabling by lid.sh.
But it is turning off in next moment, that brings me to the original problem
described above.
I added 'sleep' after xrandr and it works, but it's not clean solution I
suppose.
Maybe we really don't need to do DPMS off while going to sleep?
Here are my patches:
--- debian/patches/lid.sh.diff 2013-07-01 11:45:34.0 +0300
+++ debian/patches/lid.sh.diff 2013-07-01 13:56:39.298838245 +0300
@@ -57,7 +57,7 @@
+ su $XUSER -s /bin/sh -c "xset dpms force on"
+ ;;
+ xrandr)
-+ su $XUSER -s /bin/sh -c "xrandr --output LVDS --auto"
++ su $XUSER -s /bin/sh -c "xrandr --output
${XRANDR_OUTPUT:-LVDS} --auto"
+ ;;
+ vbetool)
+ /usr/sbin/vbetool dpms on
--- debian/patches/screenblank.diff~2013-07-01 11:45:34.0 +0300
+++ debian/patches/screenblank.diff 2013-07-01 14:20:11.775168681 +0300
@@ -33,31 +33,33 @@
+ su $XUSER -s /bin/sh -c "/usr/bin/xlock -mode blank &"
+ elif [ -x /usr/bin/xtrlock ]; then
+ su $XUSER -s /bin/sh -c "/usr/bin/xtrlock &"
-+ fi
++ fi
+ fi
+
-+ case "$DISPLAY_DPMS" in
-+xset)
-+ su $XUSER -s /bin/sh -c "xset dpms force off &"
-+ ;;
-+xrandr)
-+ su $XUSER -s /bin/sh -c "xrandr --output $XRANDR_OUTPUT --off"
-+ ;;
-+vbetool)
-+ /usr/sbin/vbetool dpms off
-+ ;;
-+ esac
++ if [ x$LID_SLEEP != xtrue ]; then
++ case "$DISPLAY_DPMS" in
++xset)
++ su $XUSER -s /bin/sh -c "xset dpms force off &"
++ ;;
++xrandr)
++ su $XUSER -s /bin/sh -c "xrandr --output
${XRANDR_OUTPUT:-LVDS} --off"
++ ;;
++vbetool)
++ /usr/sbin/vbetool dpms off
++ ;;
++ esac
-xset dpms force off
-if [ x$RADEON_LIGHT = xtrue ]; then
-[ -x /usr/sbin/radeontool ] && radeontool light off
-fi
-+ if [ x$RADEON_LIGHT = xtrue ]; then
-+ [ -x /usr/sbin/radeontool ] && radeontool light off
++ if [ x$RADEON_LIGHT = xtrue ]; then
++ [ -x /usr/sbin/radeontool ] && radeontool light off
++ fi
+ fi
+else
-+ if [ -x$DISPLAY_DPMS_NO_USER = xtrue ]; then
++ if [ x$DISPLAY_DPMS_NO_USER = xtrue -a x$LID_SLEEP != xtrue ]; then
+ [ -x /usr/sbin/vbetool ] && /usr/sbin/vbetool dpms off
-+ fi
++ fi
+fi
+done
-- System Information:
Debian Release: wheezy
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714637: acpi-support: ACPI scripts can't correctly get UID of X display owner
Package: acpi-support
Version: 0.140-5
Severity: normal
Tags: patch
Dear Maintainer,
In some cases the getXuser() function from /usr/share/acpi-support/power-funcs
file can't get the user for the X display and several ACPI scripts doesn't work
properly.
I am using Slim display manager.
ck-list-sessions utility, which is used in getXuser(), reports "x11-display =
':0.0'"
instead of usual ':0' then ConsoleKit was started with Slim.
So, awk script in the function gives no output for 'uid' variable.
Here is a simple patch with workaround:
--- debian/patches/power-funcs.diff 2013-07-01 11:45:34.0 +0300
+++ debian/patches/power-funcs.diff 2013-07-01 16:19:48.070764780 +0300
@@ -31,7 +31,7 @@
+
+ user=
+ if [ -x /usr/bin/ck-list-sessions ]; then
-+ uid=$(ck-list-sessions | awk 'BEGIN { unix_user = ""; }
/^Session/ { unix_user = ""; } /unix-user =/ { gsub(/'\''/,"",$3); unix_user =
$3; } /x11-display = '\'$display\''/ { print unix_user; exit (0); }')
++ uid=$(ck-list-sessions | awk 'BEGIN { unix_user = ""; }
/^Session/ { unix_user = ""; } /unix-user =/ { gsub(/'\''/,"",$3); unix_user =
$3; } /x11-display = '\'$display'(\.0)?'\''/ { print unix_user; exit (0); }')
+
+ if [ "$uid" ]; then
+ IFS=:
-- System Information:
Debian Release: wheezy
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638750: eeepc-acpi-scripts does not show OSD
Package: eeepc-acpi-scripts Version: 1.1.12 Followup-For: Bug #638750 Hello, I see that /usr/share/acpi-support/eeepc-acpi-scripts/lib/notify.sh script is very trivial and actually uses only $ENABLE_OSD variable. Sound and brightness notifications was delegated to other services. So, why should we keep confusing legacy options? Such as: OSD_FONT='DejaVuSans 36' ENABLE_OSD_BRIGHTNESS='no' DETAILED_SOUND_INFO=no Dear Debian Eee PC Team, please consider removing these settings from /etc/default/eeepc-acpi-scripts and /usr/share/doc/eeepc-acpi-scripts/examples/eeepc-acpi-scripts.default.gz Thank you! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714644: eeepc-acpi-scripts: initscript produce silly warnings
Package: eeepc-acpi-scripts Version: 1.1.12 Severity: minor Tags: patch Dear Debian Eee PC Team, Recent Debian kernels have pciehp module as builtin. But /etc/init.d/eeepc-acpi-scripts is trying to unload the module and complaining with "FATAL" warning message while system boots up. For me it is very annoing, because it can mix with lot of other boot process output, so it's hard to see real problems when they appear. This patch premoves the warnings if we have pciehp directory in /proc, but no module available: --- debian/eeepc-acpi-scripts.init 2011-09-25 08:16:51.0 +0300 +++ debian/eeepc-acpi-scripts.init 2013-07-01 17:23:55.082981621 +0300 @@ -67,7 +67,10 @@ # - kernel 2.6.32 & newer: eeepc-laptop also works on the EeePC 900A if [ -d /sys/module/pciehp ]; then # Hmm, already present - if [ "$KERNEL" -ge 29 -a "`cat /sys/class/dmi/id/product_name`" != "900A" ]; then + if ! modinfo pciehp >/dev/null 2>&1 +# Module pciehp is builtin, do nothing +: + elif [ "$KERNEL" -ge 29 -a "`cat /sys/class/dmi/id/product_name`" != "900A" ]; then # 2.6.29 and newer on all but the EeePC 900A - unload pciehp if loaded log_warning_msg 'Module "pciehp" is loaded; trying to unload' maybe_warn modprobe -r pciehp Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714644: [Debian-eeepc-devel] Bug#714644: eeepc-acpi-scripts: initscript produce silly warnings
03.07.13 10:36, Domenico Cufalo wrote:
> Thank you very much! I applied this patch and the message about pciehp
> disappeared.
>
> However, during the boot process I can see this message of error:
>
> /etc/init.d/eeepc-acpi-scripts: 74: /etc/init.d/eeepc-acpi-scripts:
> Syntax error: "elif" unexpected (expecting "then")
Ah, sorry, missed the ending of line somehow.
This is the correct patch:
--- debian/eeepc-acpi-scripts.init 2011-09-25 08:16:51.0 +0300
+++ debian/eeepc-acpi-scripts.init 2013-07-01 17:23:55.082981621 +0300
@@ -67,7 +67,10 @@
# - kernel 2.6.32 & newer: eeepc-laptop also works on the EeePC 900A
if [ -d /sys/module/pciehp ]; then
# Hmm, already present
- if [ "$KERNEL" -ge 29 -a "`cat /sys/class/dmi/id/product_name`" !=
"900A" ]; then
+ if ! modinfo pciehp >/dev/null 2>&1; then
+# Module pciehp is builtin, do nothing
+:
+ elif [ "$KERNEL" -ge 29 -a "`cat /sys/class/dmi/id/product_name`" !=
"900A" ]; then
# 2.6.29 and newer on all but the EeePC 900A - unload pciehp if loaded
log_warning_msg 'Module "pciehp" is loaded; trying to unload'
maybe_warn modprobe -r pciehp
--
Denys Gavrysh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720483: vagrant: Getting VBoxManage error message on 'vagrant halt' and 'vagrant package'
Package: vagrant Version: 1.2.2-1 Severity: normal Dear Maintainer, Sometimes when I'm stopping VirtualBox VM with 'vagrant halt' command or packaging live VM with 'vagrant package', I receive such error: [my_vm] Attempting graceful shutdown of VM... There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. Command: ["showvminfo", "e29614d3-1225-4fd9-9940-797ade576c75", "--machinereadable"] Stderr: VBoxManage: error: The object is not ready VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine, callee nsISupports VBoxManage: error: Context: "COMGETTER(ChipsetType)(&aChipset)" at line 76 of file VBoxManageControlVM.cpp VBoxManage: error: The object is not ready VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine, callee nsISupports VBoxManage: error: Context: "COMGETTER(BandwidthControl)(bwCtrl.asOutParam())" at line 2061 of file VBoxManageInfo.cpp It happens irregular and seems VM stops successfully anyway, but 'package' command fails. I have tryied to catch the error with VBoxManage directly while VM was shutting down with no luck. So I suppose it is really a bug in vagrant. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vagrant depends on: ii bsdtar 3.1.2-7 ii curl 7.31.0-2 ii openssh-client 1:6.2p2-6 ii ruby-childprocess 0.3.9-2 ii ruby-erubis2.7.0-2 ii ruby-i18n 0.6.4-1 ii ruby-log4r 1.1.10-2 ii ruby-net-scp 1.1.1-1 ii ruby-net-ssh 1:2.6.7-1 ii ruby1.9.1 1.9.3.194-8.1+b1 Versions of packages vagrant recommends: ii virtualbox 4.2.16-dfsg-1 vagrant suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#650384: mirror submission for debian.volia.net
Package: mirrors Severity: wishlist Submission-Type: new Site: debian.volia.net Aliases: mirror.volia.net Type: leaf Archive-architecture: ALL amd64 arm armel hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 sparc Archive-http: /debian/ Archive-rsync: debian/ Backports-http: /debian-backports/ Backports-rsync: debian-backports/ CDImage-http: /debian-cd/ Old-http: /debian-archive/ IPv6: no Archive-upstream: ftp.ua.debian.org Backports-upstream: ftp.ua.debian.org CDImage-upstream: ftp.ua.debian.org Updates: twice Maintainer: Denys Gavrysh Country: UA Ukraine Location: Kiev Sponsor: Volia Broad Band www.volia.com Comment: 1 Gbit/s -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654413: mirror listing update for debian.volia.net
Package: mirrors Severity: minor Submission-Type: update Site: debian.volia.net Aliases: mirror.volia.net Type: leaf Archive-architecture: ALL amd64 arm armel hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 sparc Archive-ftp: /debian/ Archive-http: /debian/ Archive-rsync: debian/ Backports-ftp: /debian-backports/ Backports-http: /debian-backports/ Backports-rsync: debian-backports/ CDImage-ftp: /debian-cd/ CDImage-http: /debian-cd/ CDImage-rsync: debian-cd/ Old-ftp: /debian-archive/ Old-http: /debian-archive/ Old-rsync: debian-archive/ IPv6: no Archive-upstream: ftp.ua.debian.org Backports-upstream: ftp.ua.debian.org CDImage-upstream: ftp.ua.debian.org Updates: twice Maintainer: Denys Gavrysh Country: UA Ukraine Location: Kiev Sponsor: Volia Broad Band http://www.volia.com Comment: 1 Gbit/s -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645783: tzdata: Ukraine is using DST again...
Hello. Here is a patch. --- tzdata.orig/europe 2011-10-10 07:15:43.0 +0300 +++ tzdata/europe 2011-10-19 13:13:47.401728634 +0300 @@ -2651,6 +2651,14 @@ # http://www.pravda.com.ua/rus/news/2011/09/20/6600616/";> # http://www.pravda.com.ua/rus/news/2011/09/20/6600616/ # +# +# From Dmitry Nezhevenko (2011-10-18): +# According to today's decision, Ukraine will use DST again +# +# Official document (in Ukrainian) +# http://w1.c1.rada.gov.ua/pls/zweb_n/webproc4_1?id=&pf3511=41484";> +# http://w1.c1.rada.gov.ua/pls/zweb_n/webproc4_1?id=&pf3511=41484 +# # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Most of Ukraine since 1970 has been like Kiev. @@ -2665,8 +2673,7 @@ 3:00 - MSK 1990 Jul 1 2:00 2:00 - EET 1992 2:00 E-Eur EE%sT 1995 - 2:00 EU EE%sT 2011 Mar lastSun 1:00u - 3:00 - FET # Further-eastern European Time + 2:00 EU EE%sT # Ruthenia used CET 1990/1991. # "Uzhhorod" is the transliteration of the Ukrainian name, but # "Uzhgorod" is more common in English. @@ -2680,8 +2687,7 @@ 1:00 - CET 1991 Mar 31 3:00 2:00 - EET 1992 2:00 E-Eur EE%sT 1995 - 2:00 EU EE%sT 2011 Mar lastSun 1:00u - 3:00 - FET # Further-eastern European Time + 2:00 EU EE%sT # Zaporozh'ye and eastern Lugansk oblasts observed DST 1990/1991. # "Zaporizhia" is the transliteration of the Ukrainian name, but # "Zaporozh'ye" is more common in English. Use the common English @@ -2694,8 +2700,7 @@ 1:00 C-Eur CE%sT 1943 Oct 25 3:00 Russia MSK/MSD 1991 Mar 31 2:00 2:00 E-Eur EE%sT 1995 - 2:00 EU EE%sT 2011 Mar lastSun 1:00u - 3:00 - FET # Further-eastern European Time + 2:00 EU EE%sT # Central Crimea used Moscow time 1994/1997. Zone Europe/Simferopol 2:16:24 - LMT 1880 2:16 - SMT 1924 May 2 # Simferopol Mean T @@ -2720,8 +2725,7 @@ # Assume it happened in March by not changing the clocks. 3:00 Russia MSK/MSD 1997 3:00 - MSK 1997 Mar lastSun 1:00u - 2:00 EU EE%sT 2011 Mar lastSun 1:00u - 3:00 - FET # Further-eastern European Time + 2:00 EU EE%sT ###
Bug#646797: live-build: lb_config manpage is missing option "--parent-archive-areas"
Package: live-build Version: 3.0~a37-1 Severity: minor When invoking 'lb config --help' I see [--parent-archive-areas ARCHIVE_AREA|"ARCHIVE_AREAS"] option, but it's missing in corresponding manpage. -- Package-specific info: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii cdebootstrap 0.5.8 ii debootstrap 1.0.37 Versions of packages live-build recommends: pn cpio2.11-7 pn gettext-base0.18.1.1-5 pn gnu-fdisk 1.2.4-3+b1 pn live-boot-doc pn live-config-doc pn live-manual-html | live-manual Versions of packages live-build suggests: pn dosfstools 3.0.9-1 pn fakeroot1.18.1-1 pn genisoimage 9:1.1.11-2 pn memtest86+ | memtest86 pn mtools 4.0.12-1 pn parted 2.3-8 pn squashfs-tools | mtd-tools pn sudo1.8.2-2 pn syslinux | grub pn uuid-runtime pn win32-loader -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#583398: files from thunar does not work, wrong path arguement in smplayer.desktop?
Package: smplayer Version: 0.6.9-3 Followup-For: Bug #583398 Bug still exists, but now it seems even worse than in 0.6.9-2. smplayer can't open any files with UTF-8 characters in path or name. No matter how I do it, opening file in Thunar or executing 'smplayer file-name-in-utf.avi' gives same result. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smplayer depends on: ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libgcc11:4.6.0-2 GCC support library ii libqt4-network 4:4.7.3-1 Qt 4 network module ii libqt4-xml 4:4.7.3-1 Qt 4 XML module ii libqtcore4 4:4.7.3-1 Qt 4 core module ii libqtgui4 4:4.7.3-1 Qt 4 GUI module ii libstdc++6 4.6.0-2 The GNU Standard C++ Library v3 ii mplayer2:1.0~rc4.dfsg1-2 movie player for Unix-like systems ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages smplayer recommends: ii smplayer-themes0.1.20+dfsg-1 complete front-end for MPlayer - i ii smplayer-translations 0.6.9-3 complete front-end for MPlayer - t smplayer suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
