[Bug 421261] Re: xterm background colour used to be black, now white

2010-11-11 Thread Pierfrancesco Caci
Please note that xterm looks for ~/.Xdefaults-hostname, not
~/.Xdefaults:

ik5...@penny:~ $ strace xterm pippo 21
ik5...@penny:~ $ grep Xdefault pippo
open(/home/ik5pvx/.Xdefaults-penny, O_RDONLY) = 4

Setting *customization: -color in there solves this.
Another workaround is to: 
cat /etc/X11/app-defaults/XTerm-color /etc/X11/app-defaults/XTerm  ~/XTerm
and comment out the call to include XTerm at the beginning:
!#include XTerm

Pf

-- 
xterm background colour used to be black, now white
https://bugs.launchpad.net/bugs/421261
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 514303] Re: tlf crashes on hitting ENTER

2010-08-29 Thread Pierfrancesco Caci
Hello,
I get a similar crash. Strace attached.


** Attachment added: pippo
   
https://bugs.launchpad.net/ubuntu/+source/tlf/+bug/514303/+attachment/1527188/+files/pippo

-- 
tlf crashes on hitting ENTER
https://bugs.launchpad.net/bugs/514303
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 590275] Re: ssh init script doesn't use the /etc/default/ssh file

2010-07-17 Thread Pierfrancesco Caci
This is not just a wishlist. The package as it is now breaks expected behaviour 
(the one you get after 15 years of using /etc/init.d style startup scripts)
and is not properly documented in the obvious places (README.Debian, for 
example), with only a mention of 
this new behaviour buried in changelog.Debian.gz.

Furthermore, and most importantly, the daemon behaves differently if you
start it with old style init scripts, or with new style upstart commands:

# cat /etc/default/ssh | grep -v '#'
SSHD_OPTS='-p 11210'
SSHD_OOM_ADJUST=-17
# service ssh start
ssh start/running, process 23950
# lsof -n | grep LISTEN | grep ssh
sshd  23950   root3u IPv4   24579273  0t0
TCP  *:ssh (LISTEN)
sshd  23950   root4u IPv6   24579275  0t0
TCP  *:ssh (LISTEN)
# service ssh stop
ssh stop/waiting
# /etc/init.d/ssh start
 * Starting OpenBSD Secure Shell server sshd [ OK ] 
# lsof -n | grep LISTEN | grep ssh
sshd  23983   root3u IPv4   24589208  0t0
TCP  *:11210 (LISTEN)
sshd  23983   root4u IPv6   24589210  0t0
TCP   *:11210 (LISTEN)

This means that someone changing the configuration and restarting the daemon 
the old way will not find the daemon listening
on the inteded port after a reboot. 

The old style startup script should be modified to output a message
urging the user to change his habit to upstart commands. 

The /etc/default/ssh file should be modified to include a prominent warning
that the file itself is deprecated and not used by upstart anymore.

The package as it is now may cause a machine to become unreachable if an 
external firewall is configured to allow a certain non-standard port, while
the daemon starts listening on 22 because /etc/default/ssh is not used anymore.

Pf

-- 
ssh init script doesn't use the /etc/default/ssh file
https://bugs.launchpad.net/bugs/590275
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.

-- 
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 590275] Re: ssh init script doesn't use the /etc/default/ssh file

2010-07-17 Thread Pierfrancesco Caci
Colin, I did more tests and here's another issue:

sshd is stopped, and the 2 config files have these contents:

# grep -v '#' /etc/default/ssh
SSHD_OPTS='-p 12345'
SSHD_OOM_ADJUST=-17

 # tail -1 /etc/init/ssh.conf
exec /usr/sbin/sshd -p 11210

# service ssh start
ssh start/running, process 30569

# ps ax | grep sshd
30569 ?Ss 0:00 /usr/sbin/sshd -p 11210

# /etc/init.d/ssh start
 * Starting OpenBSD Secure Shell server sshd
   [ OK ]

# ps ax | grep sshd
30569 ?Ss 0:00 /usr/sbin/sshd -p 11210

so far, this is the expected behaviour.  Now I stop again the daemon,
and start it again, but this time with the old style init script first

# /etc/init.d/ssh start
 * Starting OpenBSD Secure Shell server sshd
   [ OK ] 

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345

# service ssh start
ssh start/running, process 31614

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345
31614 ?Ss 0:00 /usr/sbin/sshd -p 11210

Result: 2 daemons running, on different ports.

Also, the init script is no longer able to stop the daemon it started:

# service ssh stop
ssh stop/waiting

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345

# /etc/init.d/ssh stop
 * Stopping OpenBSD Secure Shell server sshd
   [ OK ] 

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345


Pf

-- 
ssh init script doesn't use the /etc/default/ssh file
https://bugs.launchpad.net/bugs/590275
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.

-- 
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 590275] Re: ssh init script doesn't use the /etc/default/ssh file

2010-07-17 Thread Pierfrancesco Caci
This is not just a wishlist. The package as it is now breaks expected behaviour 
(the one you get after 15 years of using /etc/init.d style startup scripts)
and is not properly documented in the obvious places (README.Debian, for 
example), with only a mention of 
this new behaviour buried in changelog.Debian.gz.

Furthermore, and most importantly, the daemon behaves differently if you
start it with old style init scripts, or with new style upstart commands:

# cat /etc/default/ssh | grep -v '#'
SSHD_OPTS='-p 11210'
SSHD_OOM_ADJUST=-17
# service ssh start
ssh start/running, process 23950
# lsof -n | grep LISTEN | grep ssh
sshd  23950   root3u IPv4   24579273  0t0
TCP  *:ssh (LISTEN)
sshd  23950   root4u IPv6   24579275  0t0
TCP  *:ssh (LISTEN)
# service ssh stop
ssh stop/waiting
# /etc/init.d/ssh start
 * Starting OpenBSD Secure Shell server sshd [ OK ] 
# lsof -n | grep LISTEN | grep ssh
sshd  23983   root3u IPv4   24589208  0t0
TCP  *:11210 (LISTEN)
sshd  23983   root4u IPv6   24589210  0t0
TCP   *:11210 (LISTEN)

This means that someone changing the configuration and restarting the daemon 
the old way will not find the daemon listening
on the inteded port after a reboot. 

The old style startup script should be modified to output a message
urging the user to change his habit to upstart commands. 

The /etc/default/ssh file should be modified to include a prominent warning
that the file itself is deprecated and not used by upstart anymore.

The package as it is now may cause a machine to become unreachable if an 
external firewall is configured to allow a certain non-standard port, while
the daemon starts listening on 22 because /etc/default/ssh is not used anymore.

Pf

-- 
ssh init script doesn't use the /etc/default/ssh file
https://bugs.launchpad.net/bugs/590275
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 590275] Re: ssh init script doesn't use the /etc/default/ssh file

2010-07-17 Thread Pierfrancesco Caci
Colin, I did more tests and here's another issue:

sshd is stopped, and the 2 config files have these contents:

# grep -v '#' /etc/default/ssh
SSHD_OPTS='-p 12345'
SSHD_OOM_ADJUST=-17

 # tail -1 /etc/init/ssh.conf
exec /usr/sbin/sshd -p 11210

# service ssh start
ssh start/running, process 30569

# ps ax | grep sshd
30569 ?Ss 0:00 /usr/sbin/sshd -p 11210

# /etc/init.d/ssh start
 * Starting OpenBSD Secure Shell server sshd
   [ OK ]

# ps ax | grep sshd
30569 ?Ss 0:00 /usr/sbin/sshd -p 11210

so far, this is the expected behaviour.  Now I stop again the daemon,
and start it again, but this time with the old style init script first

# /etc/init.d/ssh start
 * Starting OpenBSD Secure Shell server sshd
   [ OK ] 

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345

# service ssh start
ssh start/running, process 31614

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345
31614 ?Ss 0:00 /usr/sbin/sshd -p 11210

Result: 2 daemons running, on different ports.

Also, the init script is no longer able to stop the daemon it started:

# service ssh stop
ssh stop/waiting

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345

# /etc/init.d/ssh stop
 * Stopping OpenBSD Secure Shell server sshd
   [ OK ] 

# ps ax | grep sshd
31604 ?Ss 0:00 /usr/sbin/sshd -p 12345


Pf

-- 
ssh init script doesn't use the /etc/default/ssh file
https://bugs.launchpad.net/bugs/590275
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 102232] lvm initialization hangs during boot or when running /etc/init.d/lvm start

2007-04-03 Thread Pierfrancesco Caci
Public bug reported:

Binary package hint: lvm-common

Updated system yesterday (2007.04.02), relevant updated packages were 
lvm-common, mdadm and udev.
While the update finally seems to have fixed a long standing race condition in 
mdadm preventing boot, 
it seems to have broken lvm. The system will freeze at lvm start (right after 
turning up the parport).
If I interrupt the process (alt-sysrq-e) I can do a mount -a and it will find 
all the volumes correctly. From that point on, 
I can resume the boot process by forcing a telinit 1; telinit 2

Also, running /etc/init.d/lvm start seems to hang at the same point.


ii  lvm-common 1.5.20ubuntu12   The Logical Volume Manager for Linux (common
ii  lvm2   2.02.06-2ubuntu9 The Linux Logical Volume Manager
ii  mdadm  2.5.6-7ubuntu5   tool to administer Linux MD arrays (software
ii  udev   108-0ubuntu1 rule-based device node and kernel event mana

Linux penny 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64
GNU/Linux

** Affects: lvm-common (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
lvm initialization hangs during boot or when running /etc/init.d/lvm start
https://bugs.launchpad.net/bugs/102232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102232] Re: lvm initialization hangs during boot or when running /etc/init.d/lvm start

2007-04-03 Thread Pierfrancesco Caci
$ sudo dpkg-query -W devmapper dmsetup libdevmapper1.02 udev volumeid 
libvolume-id0 lvm2 lvm-common mdadm
No packages found matching devmapper.
dmsetup 2:1.02.08-1ubuntu6
libdevmapper1.022:1.02.08-1ubuntu6
udev108-0ubuntu1
volumeid108-0ubuntu1
libvolume-id0   108-0ubuntu1
lvm22.02.06-2ubuntu9
lvm-common  1.5.20ubuntu12
mdadm   2.5.6-7ubuntu5

the rest of the info you requested later when I get back home :)

-- 
lvm initialization hangs during boot or when running /etc/init.d/lvm start
https://bugs.launchpad.net/bugs/102232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102232] Re: lvm initialization hangs during boot or when running /etc/init.d/lvm start

2007-04-03 Thread Pierfrancesco Caci
the following evms packages are installed

ii  evms 2.5.5-18ubuntu2 Enterprise Volume Management System (core)
ii  evms-cli 2.5.5-18ubuntu2 Enterprise Volume Management System (CLI)
ii  evms-ncurses 2.5.5-18ubuntu2 Enterprise Volume Management System 
(ncurses
ii  libevms-2.5  2.5.5-18ubuntu2 Enterprise Volume Management System 
(library

I've never used it actually, so if this is the culprit, I can as well
get rid of it.

-- 
lvm initialization hangs during boot or when running /etc/init.d/lvm start
https://bugs.launchpad.net/bugs/102232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102232] Re: lvm initialization hangs during boot or when running /etc/init.d/lvm start

2007-04-03 Thread Pierfrancesco Caci
so, booting with init=/bin/bash, making chmod -x /etc/init.d/lvm and finally 
exec /sbin/init
I can boot and this is the output of the lvm script as you requested:

 $ cat /root/lvm.log 
+ modprobe lvm
+ modprobe lvm-mod
+ modprobe dm-mod
+ set -e
+ . /lib/lsb/init-functions
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ . /etc/lsb-base-logging.sh
+ . /etc/default/rcS
+ TMPTIME=0
+ SULOGIN=no
+ DELAYLOGIN=no
+ UTC=yes
+ VERBOSE=no
+ EDITMOTD=yes
+ FSCKFIX=no
+ test -x /sbin/lvmiopversion -a -x /sbin/vgscan -a -x /sbin/vgchange
+ test -f /etc/default/lvm-common
+ . /etc/default/lvm-common
/etc/init.d/lvm: 57: Syntax error: Bad substitution


as a side note, the evms scripts returns failed during the boot
process.

-- 
lvm initialization hangs during boot or when running /etc/init.d/lvm start
https://bugs.launchpad.net/bugs/102232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102232] Re: lvm initialization hangs during boot or when running /etc/init.d/lvm start

2007-04-03 Thread Pierfrancesco Caci
purging all evms packages seems to have cured the problem.
nice

-- 
lvm initialization hangs during boot or when running /etc/init.d/lvm start
https://bugs.launchpad.net/bugs/102232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66128] mythweb postinst fails with Syntax error: Bad substitution

2006-10-14 Thread Pierfrancesco Caci
Public bug reported:

Hello, 
after upgrading the whole mythtv suite from dapper to edgy,
mythweb remains stuck with the following error in postinst:


E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up mythweb (0.20-0.6ubuntu3) ...
/var/lib/dpkg/info/mythweb.postinst: 31: Syntax error: Bad substitution
dpkg: error processing mythweb (--configure):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 mythweb

This is fully reproducible by removing the package (with --force-
depends) and reinstalling.

ii  mythplugins0.20-0.6ubuntu Wrapper package for MythTV plugins
iF  mythweb0.20-0.6ubuntu Web interface add-on module for MythTV


Thanks

Pf

** Affects: mythplugins (Ubuntu)
 Importance: High
 Assignee: Sebastian Dröge
 Status: Confirmed

-- 
mythweb postinst fails with Syntax error: Bad substitution
https://launchpad.net/bugs/66128

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs