Bug#1061731: load config: Key file does not have group “redfish”
Hello, As a workaround, purging and then reinstalling fwupd and dependencies fixed the problem on my machine. Regards, Matthew -- ** email: wimac...@gmail.com **
Bug#965948: mutt: Incorrect handling of whitespace in aliases file
Package: mutt
Version: 1.14.5-1
Severity: minor
X-Debbugs-Cc: m.foul...@blueyonder.co.uk
Dear Maintainer,
Before version 1.14.15-1, mutt used to ignore extra whitespace between
the end of the long name and the beginning of the email address in the
aliases file. Given an aliases file organised into columns
alias alice Alice Aardvark
alias bobBob Bee
typing "mutt alice" would have generated an email with
To: Alice Aardvark
Since the update to 1.14.15-1, all whitespace following the long name is
preserved exactly and you get
To: Alice Aardvark
This does not break anything but has led me to remove all unnecessary
white space from my aliases file, making it much harder to read.
Please would you reinstate the previous behaviour.
Thanks, Matthew
-- Package-specific info:
Mutt 1.14.5 (2020-06-23)
Copyright (C) 1996-2020 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: Linux 5.7.0-1-amd64 (x86_64)
ncurses: ncurses 6.2.20200212 (compiled with 6.2)
libidn2: 2.3.0 (compiled with 2.3.0)
hcache backend: tokyocabinet 1.4.48
Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.3.0-14'
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-9-aHzuVo/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
gcc version 9.3.0 (Debian 9.3.0-14)
Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man'
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var'
'--disable-option-checking' '--disable-silent-rules'
'--libdir=\${prefix}/lib/x86_64-linux-gnu' '--runstatedir=/run'
'--disable-maintainer-mode' '--disable-dependency-tracking'
'--with-mailpath=/var/mail' '--enable-compressed' '--enable-debug'
'--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap'
'--enable-smtp' '--enable-pop' '--enable-sidebar' '--enable-dotlock'
'--enable-exact-address' '--disable-fmemopen' '--with-curses' '--with-gnutls'
'--with-gss' '--with-idn2' '--with-mixmaster' '--with-sasl' '--without-gdbm'
'--without-bdb' '--without-qdbm' '--with-tokyocabinet'
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2
-fdebug-prefix-map=/build/mutt-4iFDK5/mutt-1.14.5=. -fstack-protector-strong
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2
-fdebug-prefix-map=/build/mutt-4iFDK5/mutt-1.14.5=. -fstack-protector-strong
-Wformat -Werror=format-security
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK
+USE_POP +USE_IMAP +USE_SMTP
-USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO
+HAVE_REGCOMP -USE_GNU_REGEX
+HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET
+HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_FUTIMENS
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
+EXACT_ADDRESS -SUN_ATTACHMENT
+ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR
+HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_LIBIDN2 +HAVE_GETSID
+USE_HCACHE
+USE_SIDEBAR +USE_COMPRESSED +USE_INOTIFY
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
To contact the developers, please mail to .
To report a bug, please contact the Mutt maintainers via gitlab:
https://gitlab.com/muttmua/mutt/issues
-- System Information:
Debian Release: bullseye/sid
APT
Bug#883939: Reproduce " smbclient failing to connect with default protocol SMB3_11"
I now have a Debian laptop again and can confirm that bug 883939 still exists. Nothing has changed. As I have already explained, however, the problem I am experiencing seems to be specific to the (outdated?) ONTAP 9 software running on the NetApp file server. It may not be worth attempting to fix it in Debian. Regards, Matthew On Mon, Feb 18, 2019 at 10:38:32AM -0800, Matthew Foulkes wrote: Hi Mathieu, I am visiting the US until the end of March and do not have access to a computer running Debian at the moment. Sorry. I will be buying a new laptop in a couple of weeks and will install Debian when it arrives, but cannot help you until then. Regards, Matthew On Mon, Feb 18, 2019 at 01:39:23PM +0100, Mathieu Parent wrote: Hello all, Are you able to reproduce this bug on latest stretch (2:4.5.16+dfsg-1) and/or latest buster (2:4.9.4+dfsg-3, -2 is ok). Regards -- Mathieu Parent -- ** email: m.foul...@blueyonder.co.uk phone: 07905 505676 ** -- ** email: m.foul...@blueyonder.co.uk phone: 07905 505676 **
Bug#923362: libpam-runtime: dpkg-reconfigure libpam-runtime disables systemd profile
Hi again, On Tue, Feb 26, 2019 at 05:00:47PM -0800, Steve Langasek wrote: Is the debconf prompt shown when you run dpkg-reconfigure? Is the systemd option shown in the list of options? (Will be listed as: "Register user sessions in the systemd control group hierarchy") If presented, is it selected or unselected when the list is shown? Did you select it or not? The debconf prompt is shown and the systemd option is shown too, with the wording you gave above and a "[*]" to indicate that it is currently selected. Even when I go straight to the "Ok" prompt to complete the reconfiguration process without making any changes to the list of selected options, the systemd pam module is disabled. Next time I start dpkg-reconfigure, the systemd option is shown as "[ ]" instead of "[*]". I can select it and hit space to add a star, but this has no practical effect; it is still disabled next time I start dpkg-reconfigure. To re-enable the systemd pam module I have to run 'pam-auth-update --enable systemd'. Regards, Matthew -- ** email: m.foul...@blueyonder.co.uk phone: 07905 505676 **
Bug#923362: libpam-runtime: dpkg-reconfigure libpam-runtime disables systemd profile
Hi Steve, Thanks for your help. Tar archives of the contents of /var/lib/pam before and after running 'dpkg-reconfigure libpam-runtime' are attached as pam.before.tar and pam.after.tar. Before running 'dpkg-reconfigure libpam-runtime', the output of 'debconf-show libpam-runtime' is: libpam-runtime/title: libpam-runtime/conflicts: libpam-runtime/no_profiles_chosen: libpam-runtime/override: false * libpam-runtime/profiles: unix, systemd, gnome-keyring After running 'dpkg-reconfigure libpam-runtime' but making no changes, the output changes to: libpam-runtime/override: false libpam-runtime/no_profiles_chosen: libpam-runtime/conflicts: * libpam-runtime/profiles: unix, gnome-keyring libpam-runtime/title: Running 'pam-auth-update --enable systemd' restores the original debconf output. The computer was installed only this weekend using the latest Debian Buster alpha installer. The 'debsums -ce' command says that all configuration files are in their default states. Best wishes, Matthew On Tue, Feb 26, 2019 at 03:34:53PM -0800, Steve Langasek wrote: Control: tags -1 moreinfo unreproducible On Tue, Feb 26, 2019 at 02:01:42PM -0800, Matthew Foulkes wrote: Package: libpam-runtime Version: 1.3.1-5 Severity: normal Dear Maintainer, Running the dpkg-reconfigure libpam-runtime command offers the user a list of pam profiles to enable or disable. Whether or not the user decides to make any changes, dpkg-reconfigure always silently disables the systemd profile, breaking a lot of desktop functionality. Attempts to use dpkg-reconfigure to re-enable the systemd profile fail silently. The problem can be fixed by running pam-auth-update --enable systemd but reappears whenever dpkg-reconfigure is used again. I cannot reproduce this problem locally. Please attach the contents of your /var/lib/pam directory and the output of the command 'debconf-show libpam-runtime'. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- ** email: m.foul...@blueyonder.co.uk phone: 07905 505676 ** pam.before.tar Description: Unix tar archive pam.after.tar Description: Unix tar archive
Bug#923362: libpam-runtime: dpkg-reconfigure libpam-runtime disables systemd profile
Package: libpam-runtime Version: 1.3.1-5 Severity: normal Dear Maintainer, Running the dpkg-reconfigure libpam-runtime command offers the user a list of pam profiles to enable or disable. Whether or not the user decides to make any changes, dpkg-reconfigure always silently disables the systemd profile, breaking a lot of desktop functionality. Attempts to use dpkg-reconfigure to re-enable the systemd profile fail silently. The problem can be fixed by running pam-auth-update --enable systemd but reappears whenever dpkg-reconfigure is used again. Best wishes, Matthew -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpam-runtime depends on: ii debconf [debconf-2.0] 1.5.70 ii libpam-modules 1.3.1-5 libpam-runtime recommends no packages. libpam-runtime suggests no packages. -- debconf-show failed
Bug#883939: Reproduce " smbclient failing to connect with default protocol SMB3_11"
I agree that it was probably two separate issues. As I explained in Message #44, my problem appeared to be NetApp specific. The administrator of the NetApp server to which I was trying to connect told me it was running ONTAP 9, which supports SMB 3.1.0 but not SMB 3.1.1. Assuming he was right, this explained most of my problem, except why smbclient was unable to negotiate the use of a mutually supported protocol. It did look like Samba bug 13009, but I was definitely running 4.7.3. I guess the problem was out-of-date software on the NetApp server. Matthew On Wed, Feb 20, 2019 at 09:31:59PM +0100, Mathieu Parent wrote: Le lun. 18 févr. 2019 à 16:06, David Sanders a écrit : Mattieu, I just tried connecting to a Windows 10 machine with and without the "client max protocol = SMB3_10" directive in my smb.conf. I can connect without a problem with the directive present, however when I comment it out I get the following error message: protocol negotiation failed: NT_STATUS_CONNECTION_RESET So either there's a bug with this version or something is screwy with the configuration on the Windows machine. It's not a big problem for me because the work around fixes it. I am running stretch 9.8 with samba 2:4.5.16+dfsg-1 Thanks for your feedback. I'm confused because there may be two different problems here. Matthew Foulkes's "protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE" looks like upstream https://bugzilla.samba.org/show_bug.cgi?id=13009, against NetApp, and which is fixed in 4.7.0 (i.e Debian buster), but Matthew's original report was already 4.7.3. David Sanders's "protocol negotiation failed: NT_STATUS_CONNECTION_RESET" is against Windows 10 and is still not fixed with 2:4.5.16+dfsg-1. Maybe fixed on buster (2:4.9.4+dfsg-3)? It looks like https://bugzilla.samba.org/show_bug.cgi?id=12863 fixed in 4.7.12. Regards -- Mathieu Parent -- ** email: m.foul...@blueyonder.co.uk phone: 07905 505676 **
Bug#883939: Reproduce " smbclient failing to connect with default protocol SMB3_11"
Hi Mathieu, I am visiting the US until the end of March and do not have access to a computer running Debian at the moment. Sorry. I will be buying a new laptop in a couple of weeks and will install Debian when it arrives, but cannot help you until then. Regards, Matthew On Mon, Feb 18, 2019 at 01:39:23PM +0100, Mathieu Parent wrote: Hello all, Are you able to reproduce this bug on latest stretch (2:4.5.16+dfsg-1) and/or latest buster (2:4.9.4+dfsg-3, -2 is ok). Regards -- Mathieu Parent -- ** email: m.foul...@blueyonder.co.uk phone: 07905 505676 **
Bug#883939: RE: smbclient failing to connect with default protocol SMB3_11
I have now heard from the administrators of the file server to which I had trouble connecting. It turns out not to be a Windows machine but a Netapp system running ONTAP 9. This supports SMB 3.1.0 but not 3.1.1, explaining the problem. Although I am surprised that smbclient and the Netapp SMB server are unable to negotiate an automatic downgrade to SMB 3.1.0, I don't think this problem is worth reporting to the Samba developers. It may be just how the SMB protocol works. I won't close this bug myself because David Sanders reported seeing similar problems when connecting to a Windows 10 SMB server. If someone else wants to close it, however, I will not object. Matthew On Fri, 24 Aug 2018 14:55:43 +0200 =?windows-1252?Q?L.P.H._van_Belle?= wrote: Only thing i can suggest atm for this one is post your problem on the samba list. If you do, post the windows server version your using also. And preffered also the linux os and smb.conf ( if needed anonymized ). This might be a regression or a "still" not fixed bug. Best regards, Louis > -Oorspronkelijk bericht- > Van: Matthew Foulkes [mailto:m.foul...@blueyonder.co.uk] > Verzonden: vrijdag 24 augustus 2018 13:56 > Aan: 883...@bugs.debian.org; L.P.H. van Belle > Onderwerp: Re: smbclient failing to connect with default > protocol SMB3_11 > > Hi Louis, > > Thanks for your help, but this bug does not seem to be quite > the same as > any of the ones you listed. I can connect when I specify "client max > protocol" values of SMB3_10, SMB3_02, SMB2, or NT1, but not > with SMB3 or > SMB3_11. > > Best wishes, Matthew > > -- > ** > email: m.foul...@blueyonder.co.uk > phone: (020) 8286 9910 > ** > > -- ** Matthew Foulkes Department of Physics +44 20 7594 7607 Imperial College Londonwmc.foul...@imperial.ac.uk London SW7 2AZ www.imperial.ac.uk/people/wmc.foulkes **
Bug#883939: smbclient failing to connect with default protocol SMB3_11
Hi Louis, Thanks for your help, but this bug does not seem to be quite the same as any of the ones you listed. I can connect when I specify "client max protocol" values of SMB3_10, SMB3_02, SMB2, or NT1, but not with SMB3 or SMB3_11. Best wishes, Matthew -- ** email: m.foul...@blueyonder.co.uk phone: (020) 8286 9910 **
Bug#883939: Reproducible on sid?
Hi Mathieu, Yes, I can still reproduce the bug on a current buster system. Nothing seems to have changed. Best wishes, Matthew On Fri, Aug 24, 2018 at 07:44:21AM +0200, Mathieu Parent wrote: Hi, Can you reproduce this bug on current buster or sid? (2:4.8.4+dfsg-2)? Regards -- Mathieu Parent -- ** email: m.foul...@blueyonder.co.uk phone: (020) 8286 9910 **
Bug#883939: smbclient failing to connect with default protocol SMB3_11
Package: smbclient Version: 2:4.7.3+dfsg-1 Severity: important Dear Maintainer, Today, for the first time for years, I tried to use smbclient to access files on a Windows file server at work. After discovering that the Thunar file manager was unable to connect, I tried smbclient. The command smbclient -d 10 -W IC -U wmcfoulkes //icnas2.cc.ic.ac.uk/wmcfoulkes failed with the error message protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE as did: smbclient -m SMB3 -d 10 -W IC -U wmcfoulkes //icnas2.cc.ic.ac.uk/wmcfoulkes smbclient -m SMB3_11 -d 10 -W IC -U wmcfoulkes //icnas2.cc.ic.ac.uk/wmcfoulkes Specifying "-m SMB3_10" or any lower protocol version on the command line solved the problem. Setting "client max protocol = SMB3_10" in /etc/samba/smb.conf fixed Thunar too. It is possible that the Windows server (to which I do not have access) does not support SMB3_11, but I would have expected automatic negotiation to a lower protocol version to work. I have attached the logs obtained when smbclient is run with "-d 10 -m SMB3_11" and "-d 10 -m SMB3_10". Best wishes, Matthew -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smbclient depends on: ii dpkg 1.19.0.4 ii libarchive13 3.2.2-3.1 ii libbsd0 0.8.6-3 ii libc6 2.25-3 ii libpopt0 1.16-10+b2 ii libreadline7 7.0-3 ii libsmbclient 2:4.7.3+dfsg-1 ii libtalloc22.1.10-2 ii libtevent00.9.34-1 ii samba-common 2:4.7.3+dfsg-1 ii samba-libs2:4.7.3+dfsg-1 smbclient recommends no packages. Versions of packages smbclient suggests: pn cifs-utils pn heimdal-clients -- no debconf information INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 Processing section "[global]" doing parameter workgroup = WORKGROUP doing parameter dns proxy = no doing parameter log file = /var/log/samba/log.%m doing parameter max log size = 1000 doing parameter syslog = 0 WARNING: The "syslog" option is deprecated doing parameter panic action = /usr/share/samba/panic-action %d doing parameter server role = standalone server doing parameter passdb backend = tdbsam doing parameter obey pam restrictions = yes doing parameter unix password sync = yes doing parameter passwd program = /usr/bin/passwd %u doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . doing parameter pam password change = yes doing parameter map to guest = bad user doing parameter usershare allow guests = yes pm_process() returned Yes lp_servicenumber: couldn't find homes added interface enp0s25 ip=192.168.1.34 bcast=192.168.1.255 netmask=255.255.255.0 Netbios name list:- my_netbios_names[0]="BEE" Client started (version 4.7.3-Debian). Opening cache file at /var/cache/samba/gencache.tdb tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: No such file or directory Attempt to open gencache.tdb has failed. sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up icnas2.cc.ic.ac.uk#20 (sitename (null)) Opening cache file at /var/cache/samba/gencache.tdb tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: No such file or directory Attempt to open gencache.tdb has failed. no entry for icnas2.cc.ic.ac.uk#20 found. resolve_hosts: Attempting host lookup for name icnas2.cc.ic.ac.uk<0x20> remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 2 addresses for icnas2.cc.ic.ac.uk#20:
Bug#820927: xfce4-pulseaudio-plugin panel icon invisible when panel is transparent
Package: xfce4-pulseaudio-plugin Version: 0.2.4-1 Severity: minor Dear Maintainer, I run xfce4 with the standard Xfce desktop style and the Faenza icon set. If I make the panel transparent by setting its "Alpha" to 0, the xfce4-pulseaudio-plugin panel icon disappears. I would expect the icon's background to become transparent to match the panel, but the foreground becomes transparent too. The icon still takes up space on the panel and appears on mouse-over, but is invisible otherwise. Changing the icon set and/or modifying the icon files installed by xfce4-pulseaudio-plugin in /usr/share/icons/hicolor has no effect. Switching to any other "Xfce-" desktop style also has no effect. If I change to the "Raleigh" style, the foreground and background of the xfce4-pulseaudio-plugin icon are *both* non-transparent, with the background a pale gray color. This may or may not be related to bug 808942. Thanks for your help. Matthew -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-pulseaudio-plugin depends on: ii libatk1.0-0 2.20.0-1 ii libc62.22-5 ii libcairo-gobject21.14.6-1+b1 ii libcairo21.14.6-1+b1 ii libdbus-1-3 1.10.8-1 ii libdbus-glib-1-2 0.106-1 ii libgdk-pixbuf2.0-0 2.32.3-1.2 ii libglib2.0-0 2.48.0-1 ii libgtk-3-0 3.18.9-1 ii libkeybinder-3.0-0 0.3.1-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libpulse-mainloop-glib0 8.0-2 ii libpulse08.0-2 ii libxfce4panel-2.0-4 4.12.0-4 ii libxfce4ui-2-0 4.12.1-2 ii libxfce4util74.12.1-2 ii libxfconf-0-24.12.0-2+b1 Versions of packages xfce4-pulseaudio-plugin recommends: ii pavucontrol 3.0-3+b2 xfce4-pulseaudio-plugin suggests no packages. -- no debconf information
Bug#784972: Same problem with PPTP VPN connection
Upgrading to plasma-nm 4:5.4.0-1 fixed this bug for me. Matthew
Bug#784972: Same problem with PPTP VPN connection
PPTP VPN connections suffer from the same problem. I have an up-to-date Debian testing system with KDE and XFCE desktops installed. PPTP VPN connections created using the network-manager-gnome systray icon in XFCE behave in exactly the same way as PPTP connections created using the plasma-nm systray icon in KDE: the new connection can be seen from both desktops (regardless of which was used to create it) but only works in XFCE. When I connect using the network-manager-gnome applet in XFCE, a VPN password dialog appears and everything works fine; when I try to connect using the plasma-nm applet in KDE, no password dialog appears, the plasma-nm systray applet tells me that it "needs authorisation", and the connection fails. Sometimes, if I look very carefully, I think I can see a password dialog appear very briefly, but it disappears so fast I cannot be sure. It looks as if plasma-nm has forgotten how to ask for VPN passwords. Matthew
Bug#719627: reported upstream as kernel bug 61861
Reported upstream at bugzilla.kernel.org as requested. Bug number: 61861 URL: https://bugzilla.kernel.org/show_bug.cgi?id=61861 -- ** email: m.foul...@blueyonder.co.uk phone: (020) 8286 9910 ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719627: linux-image-3.10-2-amd64: ten minute delay during boot
Googling for hp dc5800 boot problems suggested adding pci=nommconf to the kernel command line. This cures the problem. Other reports discussing this problem are at least three years old. Does its reappearance indicate a regression in kernel 3.10? Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719627: linux-image-3.10-2-amd64: ten minute delay during boot
Hi Ben, On Tue, Aug 13, 2013 at 09:43:14PM +0200, Ben Hutchings wrote: Does this problem go away if you add 'blacklist=tpm_tis' to the kernel command line? Blacklisting tpm_tis makes no difference. The boot process still pauses at exactly the same point. The pause this time was only about five minutes long, but I was booting in single-user mode and had set boot-delay=100 to allow me to inspect the boot messages as they scrolled past, so not everything was identical. Thanks for your help. Matthew -- ** email: m.foul...@blueyonder.co.uk phone: (020) 8286 9910 ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709378: ifupdown: ifup tries to bring up lo twice if lo appears in /etc/network/interfaces
Hi Andrew, On Wed, May 22, 2013 at 11:21:51PM +0200, Andrew Shadura wrote: Hello, On Wed, 22 May 2013 22:13:21 +0100 Matthew Foulkes m.foul...@blueyonder.co.uk wrote: Since ifupdown 0.7.43 entered testing, I have noticed ifup -v lo and ifdown -v lo attempting to bring the loopback interface up/down twice. Please elaborate that. I have specifically changed the internal definition of the loopback interface so that it is *not* brought up twice. If that's not working, it must be a bug. My old amd64 desktop running Debian testing has been continuously upgraded for some years. The external eth0 interface is managed by network manager. The only other network interface is lo: root@bee:~# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:23:7d:46:35:93 inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::223:7dff:fe46:3593/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:69562 errors:0 dropped:0 overruns:0 frame:0 TX packets:36327 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:94305442 (89.9 MiB) TX bytes:5700800 (5.4 MiB) Interrupt:19 Memory:f300-f302 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3504 (3.4 KiB) TX bytes:3504 (3.4 KiB) I have not changed the default networking configuration as far as I can remember. If /etc/network/interfaces is blank, I get the following: root@bee:~# ifdown -v lo Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/upstart run-parts: executing /etc/network/if-down.d/wpasupplicant run-parts --verbose /etc/network/if-post-down.d run-parts: executing /etc/network/if-post-down.d/avahi-daemon run-parts: executing /etc/network/if-post-down.d/wpasupplicant ip link set down dev lo 2/dev/null root@bee:~# ifup -v lo ip link set up dev lo 2/dev/null Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-daemon run-parts: executing /etc/network/if-up.d/mountnfs run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart run-parts: executing /etc/network/if-up.d/wpasupplicant However, if /etc/network/interfaces contains the lines auto lo iface lo inet loopback the output changes to: root@bee:~# ifdown -v lo Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/upstart run-parts: executing /etc/network/if-down.d/wpasupplicant run-parts --verbose /etc/network/if-post-down.d run-parts: executing /etc/network/if-post-down.d/avahi-daemon run-parts: executing /etc/network/if-post-down.d/wpasupplicant Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/upstart run-parts: executing /etc/network/if-down.d/wpasupplicant run-parts --verbose /etc/network/if-post-down.d run-parts: executing /etc/network/if-post-down.d/avahi-daemon run-parts: executing /etc/network/if-post-down.d/wpasupplicant ip link set down dev lo 2/dev/null root@bee:~# ifup -v lo ip link set up dev lo 2/dev/null Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-daemon run-parts: executing /etc/network/if-up.d/mountnfs run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart run-parts: executing /etc/network/if-up.d/wpasupplicant Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-daemon run-parts: executing /etc/network/if-up.d/mountnfs run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart run-parts: executing /etc/network/if-up.d/wpasupplicant It seems that ifdown and ifup are running all of the if-down-*.d and if-up-*.d scripts twice. Unless ifup/ifdown can be made smarter about dealing with multiple definitions, perhaps you should recommend that all mention of lo be omitted from /etc/network/interfaces from now on? The documentation available via man
Bug#709378: ifupdown: ifup tries to bring up lo twice if lo appears in /etc/network/interfaces
Package: ifupdown Version: 0.7.43 Severity: normal Dear Maintainer, Since ifupdown 0.7.43 entered testing, I have noticed ifup -v lo and ifdown -v lo attempting to bring the loopback interface up/down twice. I guess this is because ifup/ifdown now predefine lo internally as an auto interface. They bring lo up/down once for the internal definition and once for the definition in /etc/network/interfaces (which will be present in almost all systems upgraded from wheezy). Unless ifup/ifdown can be made smarter about dealing with multiple definitions, perhaps you should recommend that all mention of lo be omitted from /etc/network/interfaces from now on? The documentation available via man interfaces and in /usr/share/doc/ifupdown/examples would need changing to reflect this. Regards, Matthew -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.10 ii initscripts 2.88dsf-41 ii iproute 20120521-3+b4 ii libc62.17-3 ii lsb-base 4.1+Debian9 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5+deb70u3 ii net-tools 1.60-25 ii ppp2.4.5-5.1+b1 pn rdnssd none -- 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#680985: network-manager-gnome should depend on gnome-keyring
Package: network-manager-gnome Version: 0.9.4.1-1+b1 Severity: normal nm-applet cannot store or retrieve wireless passwords unless gnome-keyring is installed, but the network-manager-gnome package does not depend on, recommend, or suggest the installation of gnome-keyring. This is confusing for people who want to use nm-applet in non-gnome environments, where gnome-keyring may not already be installed. Please consider making network-manager-gnome depend on gnome-keyring. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager-gnome depends on: ii dbus-x11 1.6.0-1 ii dpkg 1.16.4.3 ii gconf-service 3.2.5-1 ii gconf23.2.5-1 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-33 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libdbus-1-3 1.6.0-1 ii libdbus-glib-1-2 0.100-1 ii libgconf-2-4 3.2.5-1 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgnome-bluetooth10 3.4.1-1 ii libgnome-keyring0 3.4.1-1 ii libgtk-3-03.4.2-2 ii libnm-glib-vpn1 0.9.4.0-5 ii libnm-glib4 0.9.4.0-5 ii libnm-gtk00.9.4.1-1+b1 ii libnm-util2 0.9.4.0-5 ii libnotify40.7.5-1 ii libpango1.0-0 1.30.0-1 ii network-manager 0.9.4.0-5 ii policykit-1-gnome 0.105-2 Versions of packages network-manager-gnome recommends: pn gnome-bluetooth none ii iso-codes 3.36-1 pn libpam-keyring none ii mobile-broadband-provider-info 20120402-1 ii plasma-widgets-workspace [notification-daemon] 4:4.8.4-3 Versions of packages network-manager-gnome suggests: pn network-manager-openvpn-gnome none ii network-manager-pptp-gnome 0.9.4.0-2 pn network-manager-vpnc-gnome none -- 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#627808: /init: 239: mv: not found
Package: initramfs-tools Version: 0.99 Severity: normal After installing initramfs-tools 0.99, the following error message started appearing very early in the boot process: /init: 239: mv: not found Fortunately, the system still boots. Unpacking /boot/initrd.img-2.6.38-2-amd64 showed that line 239 of the init script is at the end of an if block containing two mv commands related to /run and udev. After installing busybox (which initramfs-tools recommends but does not require) and running update-initramfs -u, the error message vanished. I do not pretend to understand how the initrd system works, but if busybox is now required I guess that initramfs-tools should depend on it. If not, this may be a bug. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 2.4M May 24 18:01 /boot/initrd.img-2.6.38-2-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 root=UUID=0b7e18a7-8daa-400b-b785-77e83e31f0a9 ro quiet -- resume RESUME=UUID=b63932f9-3f86-4f3f-94a0-2e1d84b9e7c6 -- /proc/filesystems ext3 fuseblk -- lsmod Module Size Used by ppdev 12725 0 lp 17190 0 fuse 61520 1 loop 22515 0 firewire_sbp2 17825 0 option 24802 0 usb_wwan 17206 1 option usbhid 39900 0 sg 25769 0 hid72616 1 usbhid sr_mod 21824 0 cdrom 35134 1 sr_mod radeon717227 2 snd_intel8x0 30802 1 snd_ac97_codec106189 1 snd_intel8x0 ttm52155 1 radeon firewire_ohci 30887 0 drm_kms_helper 26893 1 radeon usbserial 31986 2 option,usb_wwan drm 165567 4 radeon,ttm,drm_kms_helper ohci_hcd 26400 0 ehci_hcd 39529 0 firewire_core 47683 2 firewire_sbp2,firewire_ohci ac97_bus 12510 1 snd_ac97_codec natsemi30961 0 pata_amd 13276 0 snd_pcm67327 2 snd_intel8x0,snd_ac97_codec skge 40243 0 usbcore 122908 7 option,usb_wwan,usbhid,usbserial,ohci_hcd,ehci_hcd i2c_nforce212584 0 i2c_algo_bit 12834 1 radeon power_supply 13475 1 radeon floppy 56861 0 snd_seq44678 0 crc_itu_t 12347 1 firewire_core shpchp 31221 0 snd_timer 22658 2 snd_pcm,snd_seq snd_seq_device 13155 1 snd_seq snd52280 8 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_seq,snd_timer,snd_seq_device soundcore 13014 1 snd tpm_tis13125 0 evdev 17475 7 i2c_core 23725 5 radeon,drm_kms_helper,drm,i2c_nforce2,i2c_algo_bit edac_core 35344 0 edac_mce_amd 17103 0 pcspkr 12579 0 k8temp 12531 0 pci_hotplug26711 1 shpchp parport_pc 22191 1 parport31650 3 ppdev,lp,parport_pc tpm17756 1 tpm_tis tpm_bios 12903 1 tpm snd_page_alloc 12969 2 snd_intel8x0,snd_pcm serio_raw 12878 0 nls_base 12753 1 usbcore processor 27431 0 button 12994 0 ext3 112218 2 jbd41698 1 ext3 mbcache12930 1 ext3 sd_mod 35501 4 crc_t10dif 12348 1 sd_mod sata_nv26519 3 ata_generic12479 0 libata147240 3 pata_amd,sata_nv,ata_generic scsi_mod 161457 5 firewire_sbp2,sg,sr_mod,sd_mod,libata fan12674 0 thermal17330 0 thermal_sys17939 3 processor,fan,thermal -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /sys/block fd0 loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 sda sr0 -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup keymap klibc thermal udev -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-7 GNU cpio -- a program to manage ar ii findutils
Bug#620869: xfce4-panel: Cannot rearrange panel items
Package: xfce4-panel Version: 4.6.4-1 Severity: normal Tags: upstream Since libgtk2.0-0 was updated from version 2.20.1-2 to version 2.24.3-1~sid1, it has become impossible to rearrange items on the xfce4 panel. The usual right-click-move makes the entire panel go grey but the panel item cannot be dragged or dropped. This may be related to the following two bug reports https://bugzilla.xfce.org/show_bug.cgi?id=6818 https://bugzilla.gnome.org/show_bug.cgi?id=634765 The bug may be in libgtk2, but the xfce report looks more likely to produce (or have produced already) a fix. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-panel depends on: ii exo-utils 0.3.107-1 Utility files for libexo ii libatk1.0-01.32.0-1+sid1 The ATK accessibility toolkit ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra ii libexo-0.3-0 0.3.107-1 Library with extensions for Xfce ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.28.2-1 The GLib library of C routines ii libgtk2.0-02.24.3-1~sid1 The GTK+ graphical user interface ii libice62:1.0.7-1 X11 Inter-Client Exchange library ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libsm6 2:1.2.0-1 X11 Session Management library ii libstartup-notificatio 0.10-1library for program launch feedbac ii libwnck22 2.30.4-3 Window Navigator Construction Kit ii libx11-6 2:1.4.1-5 X11 client-side library ii libxfce4util4 4.6.2-1 Utility functions library for Xfce ii libxfcegui4-4 4.6.4-1 Basic GUI C functions for Xfce4 ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime xfce4-panel recommends no packages. xfce4-panel 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#616705: kdemultimedia-kio-plugins: unexpected permissions on files ripped from CD
Package: kdemultimedia-kio-plugins Version: 4:4.4.5-1 Severity: normal When I use drag and drop within dolphin to rip a CD, the ogg files created have permissions 400 (i.e. r), which is inconsistent with my umask of 022. This is unexpected and therefore confusing. For example, if you try to use amarok to change the track information, the attempt fails silently without producing an error message. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdemultimedia-kio-plugins depends on: ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii libcdparanoia0 3.10.2+debian-10 audio extraction tool for sampling ii libflac81.2.1-3 Free Lossless Audio Codec - runtim ii libkcddb4 4:4.4.5-1CDDB library for KDE Platform (run ii libkde3support4 4:4.4.5-3the KDE 3 Support Library for the ii libkdecore5 4:4.4.5-3the KDE Platform Core Library ii libkdeui5 4:4.4.5-3the KDE Platform User Interface Li ii libkio5 4:4.4.5-3the Network-enabled File Managemen ii libogg0 1.2.0~dfsg-1 Ogg bitstream library ii libqtcore4 4:4.6.3-4Qt 4 core module ii libqtgui4 4:4.6.3-4Qt 4 GUI module ii libstdc++6 4.5.2-4 The GNU Standard C++ Library v3 ii libvorbis0a 1.3.2-1 The Vorbis General Audio Compressi ii libvorbisenc2 1.3.2-1 The Vorbis General Audio Compressi kdemultimedia-kio-plugins recommends no packages. Versions of packages kdemultimedia-kio-plugins suggests: ii lame 3.98.4-0.0 LAME Ain't an MP3 Encoder -- 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#594452: network-manager-kde: more information on peap/mschapv2 problem
Package: network-manager-kde
Severity: normal
I have a very similar problem using knetworkmanager to connect to my
unversity's WPA2 Enterprise network.
If I run wpa_supplicant by hand
/etc/init.d/network-manager stop
ifconfig wlan0 up
wpa_supplicant -i wlan0 -c wpa_supplicant.conf -B
iwconfig wlan0 essid Imperial-WPA
dhclient wlan0
with the following wpa_supplicant.conf file
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=Imperial-WPA
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
anonymous_identity=ic\myusername
identity=ic\myusername
password=mypassword
phase1=peapver=0
phase2=auth=MSCHAPV2
}
everything works fine. However, if I use knetworkmanager with the
settings
SSID:Imperial-WPA
Security:WPA/WPA2 Enterprise
Authentication: Protected EAP (PEAP)
CA Certificate: blank
Use System CA Certs: unchecked
PEAP Version:Version 0
Inner Authentication:MSCHAPv2
Username:ic\myusername
Password mypassword
it does not work. Choosing to use the System CA Certs and/or replacing
the backslashes by forward slashes makes no difference.
If NetworkManager is started with the '--log-level=DEBUG
--log-domains=SUPPLICANT' options, trying to connect using
knetworkmanager yields the following messages /var/log/daemon.log:
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added 'ssid'
value 'Imperial-WPA'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added
'scan_ssid' value '1'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added
'key_mgmt' value 'WPA-EAP'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added
'password' value 'omitted'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added 'eap'
value 'PEAP'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added
'fragment_size' value '1300'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added 'phase1'
value 'peapver=0'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added 'phase2'
value 'auth=MSCHAPV2'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added 'identity'
value 'ic\myusername'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: added
'anonymous_identity' value 'ic\myusername'
Oct 19 13:29:41 mackerel NetworkManager[4763]: info Config: set interface
ap_scan to 1
Oct 19 13:29:43 mackerel wpa_supplicant[4098]: Trying to associate with
00:26:cb:1d:b1:fc (SSID='Imperial-WPA' freq=5320 MHz)
Oct 19 13:29:43 mackerel wpa_supplicant[4098]: Associated with
00:26:cb:1d:b1:fc
Oct 19 13:29:43 mackerel wpa_supplicant[4098]: CTRL-EVENT-EAP-STARTED EAP
authentication started
Oct 19 13:30:06 mackerel wpa_supplicant[4098]: CTRL-EVENT-DISCONNECTED -
Disconnect event - remove keys
All the settings look the same as those in the wpa_supplicant.conf file.
Could the problem be caused by the backslashes in the identity and
anonymous_identity or the punctuation characters in the password? It
might also be a timeout problem, since the connection process is very
slow.
Using nm-applet instead of knetworkmanager did not help, so the culprit
may be network-manager.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager-kde depends on:
ii kdebase-runtime 4:4.4.5-1runtime components from the offici
ii knm-runtime 0.1~svn1141976-1 KDE NetworkManagement infrastructu
ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.4.5-2GCC support library
ii libkdecore5 4:4.4.5-1the KDE Platform Core Library
ii libkdeui5 4:4.4.5-1the KDE Platform User Interface Li
ii libqt4-dbus 4:4.6.3-1+b1 Qt 4 D-Bus module
ii libqt4-network 4:4.6.3-1+b1 Qt 4 network module
ii libqt4-svg 4:4.6.3-1+b1 Qt 4 SVG module
ii libqtcore4 4:4.6.3-1+b1 Qt 4 core module
ii libqtgui4 4:4.6.3-1+b1 Qt 4 GUI module
ii libsolid4 4:4.4.5-1Solid Library for KDE Platform
ii libsolidcontrol44:4.4.5-3library for Solid based network ma
ii libstdc++6 4.4.5-2 The GNU Standard C++ Library v3
network-manager-kde recommends no packages.
network-manager-kde 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#598824: lxpanel: lxde desktop switcher applet update problems
Package: lxpanel Version: 0.5.6-1 Severity: normal After new windows are opened or existing windows are moved, the little picture of the desktop in the lxde desktop pager does not update properly. When a new window is opened, the pager forgets about most of the windows already open and shows either a blank desktop or just the window that last had focus. When windows are moved around, the picture does not update at all. A correct representation of the state of the desktop is not drawn until one of the open windows is clicked with the mouse. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxpanel depends on: ii libasound2 1.0.23-1 shared library for ALSA applicatio ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.4.2-1 FreeType 2 font engine, shared lib ii libglib2.0-02.24.2-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-1+b1 The GTK+ graphical user interface ii libmenu-cache1 0.3.2-2 an implementation of the freedeskt ii libpango1.0-0 1.28.1-1 Layout and rendering of internatio ii libx11-62:1.3.3-3X11 client-side library ii lxmenu-data 0.1.1-1 freedesktop.org menu specification ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages lxpanel recommends: ii manpages-dev 3.25-1 Manual pages about using GNU/Linux Versions of packages lxpanel suggests: ii iceweasel [www-browser] 3.5.13-1 Web browser based on Firefox ii konqueror [www-browser] 4:4.4.5-1 advanced file manager, web browser ii lxsession [lxsession-lite]0.4.4-3a lightweight X11 session manager ii menu 2.1.44 generates programs menu for all me ii w3m [www-browser] 0.5.2-9WWW browsable pager with excellent -- 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#575959: [Pkg-lyx-devel] Bug#575959: lyx-common: revtex4 lyx template no longer works
Hi Sven, After purging LyX and reverting the changes I had made to get RevTeX working in the past, I installed LyX 1.6.7 from unstable. Opening lyx and choosing File - New From Template ... - revtex4.lyx now works fine. Choosing File - New From Template ... - revtex.lyx appears to work until you try to run latex on the document, when a pop-up appears with the error meessage LaTeX Error: File 'revtex.sty' not found. This may cause difficulties for users with LyX or LaTeX documents made using old versions of revtex, but fixing the problem would require adding the old revtex.sty file to the texlive-publishers package. It is not really a LyX problem. Once these tests were finished I purged the unstable version of LyX and re-installed Lyx 1.6.6 from testing. This produced exactly the same results as 1.6.7. Are you sure the problem I reported had not been fixed already? Thanks for your help. Matthew -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 South Kensington Campus email: wmc.foul...@imperial.ac.uk London SW7 2AZ www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575959: lyx-common: revtex4 lyx template no longer works
Package: lyx-common
Version: 1.6.5-1
Severity: normal
Tags: patch
The version of revtex that comes with Debian squeeze/testing
texlive-publishers package is now 4-1, so the revtex4 template provided
by lyx-common no longer works. Trying to create a new document using
the revtex4 template produces the error message
The layout file requested by this document, revtex4.layout, is not
usable. This is probably because a LaTeX class or style file
required by it is not available. See the Customization documentation
for more information. LyX will not be able to produce output.
It is possible to fix the problem by:
(i) renaming /usr/share/lyx/layouts/revtex4.layout to
/usr/share/lyx/layouts/revtex4-1.layout and changing
the line
\DeclareLaTeXClass{article (REVTeX 4)}
to
\DeclareLaTeXClass{article (REVTeX 4-1)}
(ii) renaming /usr/share/lyx/templates/revtex4.lyx to
/usr/share/lyx/templates/revtex4-1.lyx and changing
the line
\textclass revtex4
to
\textclass revtex4-1
This was a trial and error solution and may not be the right way to
do it, but it worked for me.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lyx-common depends on:
ii dpkg 1.15.5.6 Debian package management system
ii python2.5.4-9An interactive high-level object-o
ii python-support1.0.7 automated rebuilding support for P
ii tex-common2.07 common infrastructure for building
Versions of packages lyx-common recommends:
ii lyx 1.6.5-1Document Processor
lyx-common 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#562970: iceweasel: same behaviour in KDE4
Package: iceweasel Version: 3.5.6-1 Severity: normal Just to add that similar behaviour (the cursor continues bouncing for approximately 30 seconds longer than it should) occurs on my machine when iceweasel 3.5.6-1 is started from KDE 4.3 in squeeze. I also have version 0.10-1 of libstartup-notification0 installed. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iceweasel depends on: ii debianutils 3.2.2 Miscellaneous utilities specific t ii fontconfig2.8.0-2generic font configuration library ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libglib2.0-0 2.22.3-1 The GLib library of C routines ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface ii libnspr4-0d 4.8.2-1NetScape Portable Runtime Library ii libstdc++64.4.2-8The GNU Standard C++ Library v3 ii procps1:3.2.8-2 /proc file system utilities ii psmisc22.8-1 utilities that use the proc file s ii xulrunner-1.9.1 1.9.1.6-1 XUL + XPCOM application runner iceweasel recommends no packages. Versions of packages iceweasel suggests: pn latex-xft-fonts none (no description available) pn libkrb53 none (no description available) ii mozplugger1.13.0-1 Plugin allowing external viewers t pn ttf-mathematica4.1none (no description available) ii xfonts-mathml 3 Type1 Symbol font for MathML pn xprintnone (no description available) pn xulrunner-1.9.1-gnome-support none (no description available) -- 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#530886: problem resolved
I discovered yesterday that kde desktop effects now work fine, as long as the firmware-linux package is installed; if firmware-linux is not installed KDE refuses to use compositing and does not say why, but the machine no longer freezes. I don't know which of the many updates since May cured the problem (and it would be hard to find out), but guess it was the switch to kde 4.3 or the recent Xorg upgrade. As far as I am concerned this bug can now be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
I have no more spare time to devote to this but did make a little progress before my time ran out. First, I built the src package using export CFLAGS_APPEND=-DDEBUG -DG_HAVE_ISO_VARARGS dpkg-buildpackage -rfakeroot -uc -us -b If I understand correctly, this should cause a message to be printed every time a button press event is received. Running this version from the command line using xfce4-power-manager --nodaemon first produces the output xfce4-power-manager --no-daemon ** (xfce4-power-manager:15603): WARNING **: Metadata for error domain xfpm-error-quark already registered TRACE[xfpm-battery.c:418] xfpm_battery_refresh_primary(): battery state : ((XfpmBatteryState) BATTERY_FULLY_CHARGED) TRACE[xfpm-battery.c:343] xfpm_battery_refresh_common(): battery state change : ((XfpmBatteryState) BATTERY_FULLY_CHARGED) TRACE[xfpm-supply.c:223] xfpm_supply_refresh_tray_icon(): Tray icon configuration: : ((XfpmShowIcon) SHOW_ICON_WHEN_BATTERY_PRESENT) TRACE[xfpm-supply.c:223] xfpm_supply_refresh_tray_icon(): Tray icon configuration: : ((XfpmShowIcon) SHOW_ICON_WHEN_BATTERY_PRESENT) TRACE[xfpm-button-xf86.c:164] xfpm_button_xf86_xevent_key(): Grabbed key 222 : ((XfpmButtonKey) BUTTON_POWER_OFF) (xfce4-power-manager:15603): xfce4-power-manager-CRITICAL **: could not map keysym 1008ffa8 to keycode (xfce4-power-manager:15603): xfce4-power-manager-CRITICAL **: could not map keysym 1008ffa7 to keycode TRACE[xfpm-button-xf86.c:164] xfpm_button_xf86_xevent_key(): Grabbed key 150 : ((XfpmButtonKey) BUTTON_SLEEP) (xfce4-power-manager:15603): xfce4-power-manager-CRITICAL **: could not map keysym 1008ff02 to keycode but nothing is added when I press the sleep or hibernate buttons. It looks as if xfpm is unaware of the button presses, even though hal notices them. FWIW, I also tried building xfpm without optimisation, only to see it crash with a SIGSEGV. By rebuilding without stripping the debugging symbols export CFLAGS=-g -O0 -DDEBUG -DG_HAVE_ISO_VARARGS export DEB_BUILD_OPTIONS=nostrip dpkg-buildpackage -rfakeroot -uc -us -b and running xfce4-power-manager --no-daemon through gdb, I obtained the following information about the crash: gdb xfce4-power-manager GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (gdb) run --no-daemon Starting program: /usr/bin/xfce4-power-manager --no-daemon [Thread debugging using libthread_db enabled] [New Thread 0x7f6cc9d6c7b0 (LWP 7086)] ** (xfce4-power-manager:7086): WARNING **: Metadata for error domain xfpm-error-quark already registered TRACE[xfpm-battery.c:418] xfpm_battery_refresh_primary(): battery state : ((XfpmBatteryState) BATTERY_FULLY_CHARGED) TRACE[xfpm-battery.c:343] xfpm_battery_refresh_common(): battery state change : ((XfpmBatteryState) BATTERY_FULLY_CHARGED) TRACE[xfpm-supply.c:223] xfpm_supply_refresh_tray_icon(): Tray icon configuration: : ((XfpmShowIcon) SHOW_ICON_WHEN_BATTERY_PRESENT) TRACE[xfpm-supply.c:223] xfpm_supply_refresh_tray_icon(): Tray icon configuration: : ((XfpmShowIcon) SHOW_ICON_WHEN_BATTERY_PRESENT) TRACE[xfpm-button-xf86.c:164] xfpm_button_xf86_xevent_key(): Grabbed key 222 : ((XfpmButtonKey) BUTTON_POWER_OFF) (xfce4-power-manager:7086): xfce4-power-manager-CRITICAL **: could not map keysym 1008ffa8 to keycode (xfce4-power-manager:7086): xfce4-power-manager-CRITICAL **: could not map keysym 1008ffa7 to keycode TRACE[xfpm-button-xf86.c:164] xfpm_button_xf86_xevent_key(): Grabbed key 150 : ((XfpmButtonKey) BUTTON_SLEEP) (xfce4-power-manager:7086): xfce4-power-manager-CRITICAL **: could not map keysym 1008ff02 to keycode Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f6cc9d6c7b0 (LWP 7086)] 0x00412fdf in xfpm_brightness_hal_init (brg=Cannot access memory at address 0x6e696c2d656b6f62 ) at xfpm-brightness-hal.c:518 518 } (gdb) backtrace #0 0x00412fdf in xfpm_brightness_hal_init (brg=Cannot access memory at address 0x6e696c2d656b6f62 ) at xfpm-brightness-hal.c:518 Cannot access memory at address 0x6e696c2d656b6f7a It looks to be an unrelated
Bug#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
On Wed, Aug 19, 2009 at 04:33:52PM +0200, Yves-Alexis Perez wrote: but nothing is added when I press the sleep or hibernate buttons. It looks as if xfpm is unaware of the button presses, even though hal notices them. xfpm uses X keys, not hal ones, so that may very well be the problem, especially since it only detect BUTTON_SLEEP. BUTTON_HIBERNATE is not detected for me (on the current version, should be fixed upstream) but BUTTON_SUSPEND and BUTTON_SLEEP are. Do you use thinkpad-acpi? Yes. Could you use lsinput to find out which input event is the “ThinkPad Extra Buttons” one (here it's the 3) and run: It's 7. sudo input-events 3 (or your number) Press Fn+F4 and Fn+F12 and tell me what is reported by that. Running input-events 7 as root, I obtain: # on pressing the sleep key 15:49:00.986062: EV_KEY KEY_SLEEP pressed 15:49:00.986073: EV_SYN code=0 value=0 15:49:00.986077: EV_KEY KEY_SLEEP released 15:49:00.986081: EV_SYN code=0 value=0 # on pressing the hibernate key 15:49:05.190784: EV_KEY KEY_SUSPEND pressed 15:49:05.190794: EV_SYN code=0 value=0 15:49:05.190799: EV_KEY KEY_SUSPEND released 15:49:05.190802: EV_SYN code=0 value=0 Surprisingly, pressing the sleep key within input-events *does* cause the system to sleep, even though it has no effect normally. Pressing the hibernate key has no effect either way. Which kernel version do you use, btw? The standard Debian testing kernel: Linux version 2.6.30-1-amd64 (Debian 2.6.30-5) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Mon Aug 3 12:28:22 UTC 2009 Best wishes, Matthew -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 South Kensington Campus email: wmc.foul...@imperial.ac.uk London SW7 2AZ www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
On Wed, Aug 19, 2009 at 05:05:42PM +0200, Yves-Alexis Perez wrote: On mer, 2009-08-19 at 15:55 +0100, Matthew Foulkes wrote: Running input-events 7 as root, I obtain: # on pressing the sleep key 15:49:00.986062: EV_KEY KEY_SLEEP pressed 15:49:00.986073: EV_SYN code=0 value=0 15:49:00.986077: EV_KEY KEY_SLEEP released 15:49:00.986081: EV_SYN code=0 value=0 # on pressing the hibernate key 15:49:05.190784: EV_KEY KEY_SUSPEND pressed 15:49:05.190794: EV_SYN code=0 value=0 15:49:05.190799: EV_KEY KEY_SUSPEND released 15:49:05.190802: EV_SYN code=0 value=0 Surprisingly, pressing the sleep key within input-events *does* cause the system to sleep, even though it has no effect normally. Pressing the hibernate key has no effect either way. Yeah, the hibernate stuff is known (fixed upstream). The sleep one is weird. I don't know why it'd work only if you listen to it :/ Are you sure it was configured correctly in the preferences? (I'm not on the box right now but maybe it changes depending on if you're on AC or battery). This is no longer happening. I have rebooted and the ThinkPad Extra Buttons have moved to /dev/input/event6 (perhaps because I disconnected an external USB mouse). Typing Fn-F4 when running input-events 6 now does nothing. This is weird. -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 South Kensington Campus email: wmc.foul...@imperial.ac.uk London SW7 2AZ www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
I don't use tpb. Since running input-events no longer makes any difference, I cannot test whether it was really xfpm that put the laptop to sleep those two times. Sorry. I guess that xfpm had crashed or stopped working, and that the /etc/acpi/sleep.sh script was responsible for putting the laptop to sleep. I have tested that script before: when it detects a running power manager it exits without doing anything; when it fails to detect a running power manager it puts the laptop to sleep. -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 South Kensington Campus email: wmc.foul...@imperial.ac.uk London SW7 2AZ www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
On Wed, Aug 19, 2009 at 04:19:05PM +0100, Yves-Alexis Perez wrote: On mer, 2009-08-19 at 16:19 +0100, Matthew Foulkes wrote: Pulling out the power cable makes no difference. xfpm notices that the computer is on battery, but Fn-F4 still does nothing. Mystifying. One possible difference is that input-events is running as root. Could it be a permissions issue? I am a member of the powerdev group and have just added myself to the polkituser group, but with no effect. I don't think so. I mean, in that case if wouldn't work when you select “Suspend” in xfpm tray icon menu. Make sure that, when running input-events, it's xfpm which receive the event and put the laptop in suspend to ram (it should be noted in the debug log). Maybe check with polkit-auth and ck-list-sessions just to be sure you have the rights to do what you want but I don't think it's the problem. I really think xfpm is not receiving the key press in the general case, and fail to understand why it does when input-events is running (unless, maybe something else usualy grabs the input device and prevents that? Do you use something else like tpb?) I don't use tpb. Since running input-events no longer makes any difference, I cannot test whether it was really xfpm that put the laptop to sleep those two times. Sorry. -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 South Kensington Campus email: wmc.foul...@imperial.ac.uk London SW7 2AZ www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542237: kdebase-bin: powerdevil ignores suspend and hibernate keys
Package: kdebase-bin Version: 4:4.2.4-1 Severity: normal Suspend and hibernate work on my Thinkpad R61 using pm-utils and using the powerdevil GUI in kde4, but the sleep (Fn-F4) and hibernate (Fn-F12) buttons on the keyboard do not work. When the sleep and hibernate keys are pressed, acpi_listen reports the following acpi events button/sleep SBTN 0080 button/suspend SUSP 0080 lshal -m reports 09:15:11.876: computer_logicaldev_input_6 condition ButtonPressed = sleep 09:15:14.277: computer_logicaldev_input_6 condition ButtonPressed = hibernate and xev reports KeyPress event, serial 31, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 975061, (164,3), root:(1121,523), state 0x0, keycode 223 (keysym 0x1008ff10, XF86Standby), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 31, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 975061, (164,3), root:(1121,523), state 0x0, keycode 223 (keysym 0x1008ff10, XF86Standby), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 34, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 980721, (164,3), root:(1121,523), state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 980721, (164,3), root:(1121,523), state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False dbus-monitor --session type='signal',interface='org.freedesktop.PowerManagement' reports nothing. I do not understand how powerdevil learns about acpi events and do not know what information you need to investigate the problem, but I'd be happy to help any way I can. I see the same symptoms using xfce4-power-manager in xfce4, so the problem may lie at a lower level of the system. If this bug should have been filed against a different package, please let me know which one. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdebase-bin depends on: ii kdebase-data 4:4.2.4-1 shared data files for the KDE 4 ba ii kdebase-runtime 4:4.2.4-2 runtime components from the offici ii kdelibs5 4:4.2.4-1 core libraries for all KDE 4 appli ii libc6 2.9-23 GNU C Library: Shared libraries ii libqt4-dbus 4:4.5.2-1 Qt 4 D-Bus module ii libqt4-xml4:4.5.2-1 Qt 4 XML module ii libqtcore44:4.5.2-1 Qt 4 core module ii libqtgui4 4:4.5.2-1 Qt 4 GUI module ii libstdc++64.4.1-1The GNU Standard C++ Library v3 ii libx11-6 2:1.2.2-1 X11 client-side library kdebase-bin recommends no packages. kdebase-bin 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#542238: xfce4-power-manager: ignores suspend and hibernate keys
Package: xfce4-power-manager Version: 0.8.2-1 Severity: normal Suspend and hibernate work on my Thinkpad R61 using pm-utils and using the xfce4-power-manager GUI in xfce4, but the sleep (Fn-F4) and hibernate (Fn-F12) buttons on the keyboard do not work. When the sleep and hibernate keys are pressed, acpi_listen reports the following acpi events button/sleep SBTN 0080 button/suspend SUSP 0080 lshal -m reports 09:15:11.876: computer_logicaldev_input_6 condition ButtonPressed = sleep 09:15:14.277: computer_logicaldev_input_6 condition ButtonPressed = hibernate and xev reports KeyPress event, serial 31, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 975061, (164,3), root:(1121,523), state 0x0, keycode 223 (keysym 0x1008ff10, XF86Standby), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 31, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 975061, (164,3), root:(1121,523), state 0x0, keycode 223 (keysym 0x1008ff10, XF86Standby), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 34, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 980721, (164,3), root:(1121,523), state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x301, root 0x6b, subw 0x0, time 980721, (164,3), root:(1121,523), state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False dbus-monitor --session type='signal',interface='org.freedesktop.PowerManagement' reports no dbus events. I do not understand how xfce4-power-manager learns about acpi events and do not know how to investigate the problem further, but would be happy to provide additional information if asked. I see the same symptoms when using powerdevil in kde4, so the problem may lie at a lower level of the system. If this bug should have been filed against a different package, please let me know which one. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-power-manager depends on: ii hal 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer ii libc62.9-23 GNU C Library: Shared libraries ii libcairo21.8.8-2 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.16-2simple interprocess messaging syst ii libdbus-glib 0.82-1 simple interprocess messaging syst ii libglib2.0-0 2.20.4-1The GLib library of C routines ii libgtk2.0-0 2.16.1-2The GTK+ graphical user interface ii libnotify1 [ 0.4.5-1 sends desktop notifications to a n ii libpango1.0- 1.24.5-1Layout and rendering of internatio ii libx11-6 2:1.2.2-1 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfce4util 4.6.1-1 Utility functions library for Xfce ii libxfcegui4- 4.6.1-1 Basic GUI C functions for Xfce4 ii libxfconf-0- 4.6.1-1 Client library for Xfce4 configure ii xfce4-power- 0.8.2-1 power manager for Xfce desktop, ar xfce4-power-manager recommends no packages. Versions of packages xfce4-power-manager suggests: ii xfce4-power-manager-plugins 0.8.2-1power manager plugins for Xfce pan -- 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#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
On Tue, Aug 18, 2009 at 06:15:19PM +0100, Yves-Alexis Perez wrote: On mar, 2009-08-18 at 18:12 +0100, Matthew Foulkes wrote: The output from lshal is attached. Looks similar to yours, although the suspend and hibernate keys *both* fail on by R61 machine. Yeah, that's weird. In the xfpm preferences, do you see actions for suspend and hibernate, besides the power one? Only actions for the suspend button are shown in the preferences; the hibernate button is not mentioned. The preferences allows me to associate various actions with the suspend button, including hibernation, but in fact nothing happens when I press the suspend button. Both suspend and hibernate work when I select them from the right-click menu of the xfce4-power-manager panel icon. Cheers, Matthew -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 South Kensington Campus email: wmc.foul...@imperial.ac.uk London SW7 2AZ www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542238: [Pkg-xfce-devel] Bug#542238: xfce4-power-manager: ignores suspend and hibernate keys
On Tue, Aug 18, 2009 at 06:31:28PM +0100, Matthew Foulkes wrote: On Tue, Aug 18, 2009 at 06:15:19PM +0100, Yves-Alexis Perez wrote: On mar, 2009-08-18 at 18:12 +0100, Matthew Foulkes wrote: The output from lshal is attached. Looks similar to yours, although the suspend and hibernate keys *both* fail on by R61 machine. Yeah, that's weird. In the xfpm preferences, do you see actions for suspend and hibernate, besides the power one? Only actions for the suspend button are shown in the preferences; the hibernate button is not mentioned. The preferences allows me to associate various actions with the suspend button, including hibernation, but in fact nothing happens when I press the suspend button. It's actually called the sleep button in the preferences, not the suspend button. Sorry for adding to the naming confusion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530419: apologies for reforwarding confusion
Sorry for temporarily changing the forwarding address for this bug. A mix up over bug numbers. Fixed now. Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526619: exo-utils: exo-open --launch WebBrowser does not work when preferred browser is Debian Sensible Browser
Package: exo-utils Version: 0.3.101-1 Severity: normal With the preferred web browser set to Debian Sensible Browser, clicking the help button on the main xfce4 menu does not work. Iceweasel starts but attempts to open the mangled URL file:///home/matthew/'file:///usr/share/xfce4/doc/C/index.html' The problem can be reproduced by running exo-open --launch WebBrowser file:///usr/share/xfce4/doc/C/index.html directly. It seems that exo-open runs sensible-browser with the URL 'file:///usr/share/xfce4/doc/C/index.html' where the single quotatation marks are embedded in the string. These quotation marks are not stripped off when the URL is passed first to sensible-browser and then to x-www-browser, which finally execs a command equivalent to typing /usr/lib/iceweasel/firefox-bin -a iceweasel \'file:///usr/share/xfce4/doc/C/index.html\' into a terminal. The quotation marks embedded in the URL confuse iceweasel. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29.2 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages exo-utils depends on: ii eject2.1.5+deb1+cvs20081104-5ejects CDs and operates CD-Changer ii libatk1.0-0 1.24.0-2The ATK accessibility toolkit ii libc62.9-4 GNU C Library: Shared libraries ii libdbus-1-3 1.2.12-1simple interprocess messaging syst ii libexo-0.3-0 0.3.101-1 Library with extensions for Xfce ii libglib2.0-0 2.20.0-2The GLib library of C routines ii libgtk2.0-0 2.16.1-2The GTK+ graphical user interface ii libhal-stora 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share ii libhal1 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share ii libpango1.0- 1.24.0-3+b1 Layout and rendering of internatio ii libxfce4util 4.6.1-1 Utility functions library for Xfce exo-utils recommends no packages. exo-utils 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#406272: avahi-daemon: Please try to avoid host lookup
Package: avahi-daemon Version: 0.6.16-2 Followup-For: Bug #406272 This is a real annoyance for anyone booting a machine on a local network with no DNS server available. The host command in the line OUT=`LC_ALL=C host -t soa local. 21` from /etc/network/if-up.d/avahi-daemon hangs for quite a time before deciding that it cannot reach a DNS server. Is there any way to make the host command give up more quickly (I tried the -W flag but it didn't seem to work) or else to check that a DNS server is available before running the host command in the first place? -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.2 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages avahi-daemon depends on: ii adduser 3.101Add and remove users and groups ii dbus1.0.2-1 simple interprocess messaging syst ii libavahi-common30.6.16-2 Avahi common library ii libavahi-core4 0.6.16-2 Avahi's embeddable mDNS/DNS-SD lib ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libcap1 1:1.10-14support for getting/setting POSIX. ii libdaemon0 0.10-1 lightweight C library for daemons ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li Versions of packages avahi-daemon recommends: ii libnss-mdns 0.9-0.1NSS module for Multicast DNS name -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383048: python-central: will not upgrade because of error in /usr/bin/pycentral
Package: python-central Version: 0.5.4 Severity: important The local variable called ppos in function update_bytecode_files of /usr/bin/pycentral is used (on line 695) before it has has been defined. This caused the post-installation script to fail when I attempt to upgrade python-central today. Adding the line pos = len(self.shared_prefix) at the beginning of the function allowed the upgrade to proceed, although I am not sure this was the right thing to do. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.8 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-central depends on: ii python2.4.3-10 An interactive high-level object-o python-central recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378840: xcalendar-i18n: pixmap and help file location problem
Hello, On Wed, Jul 26, 2006 at 04:01:14AM +0900, Taketoshi Sano wrote: Hi. on Wed, 19 Jul 2006 10:09:24 +0100, with Bug#378840: xcalendar-i18n: pixmap and help file location problem, Matthew Foulkes [EMAIL PROTECTED] wrote: When xcalendar starts, the following error messages appear: Warning: Cannot convert string /usr/local/lib/X11/xcalendar/larrow.xbm to type Pixmap Warning: Cannot convert string /usr/local/lib/X11/xcalendar/rarrow.xbm to type Pixmap Warning: Cannot convert string /usr/local/lib/X11/xcalendar/quit.xbm to type Pixmap Warning: Cannot convert string /usr/local/lib/X11/xcalendar/qmark.xbm to type Pixmap Although xcalendar still works, various buttons and arrows in the user interface are replaced by text descriptions and the help screen is unavailable. I checked it on my system, but I can't find this problem. The pixmap and help files are present in /usr/share/xcalendar, but xcalendar is looking for them in /usr/local/lib/X11/xcalendar. A temporary workaround is to link /usr/share/xcalendar to /usr/local/lib/X11/xcalendar. Checking by strings /usr/bin/xcalendar |grep -i local just outputs localtime, so xcalendar binary doesn't contain /usr/local/... path in it. Maybe conffiles or environment variables affects on your system, I suppose. Won't you please check it by grep -i map /etc/X11/app-defaults/XCalendar and by set |grep -i map ? Sorry for the delay -- I have been away for a week and did not see your email until today. The good news is that you are right: the problem was my fault. A few months ago, because xcalendar was temporarily broken in unstable, I built it from source and installed it under /usr/local. Although I had removed this version when xcalendar again became available via apt-get, I had forgotten to delete /usr/local/etc/X11/app-defaults/XCalendar. I apologise for having wasted your time. -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 Prince Consort Road email: [EMAIL PROTECTED] London SW7 2BW www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378840: xcalendar-i18n: pixmap and help file location problem
Package: xcalendar-i18n Version: 4.0.0.i18p1-13.2 Severity: normal When xcalendar starts, the following error messages appear: Warning: Cannot convert string /usr/local/lib/X11/xcalendar/larrow.xbm to type Pixmap Warning: Cannot convert string /usr/local/lib/X11/xcalendar/rarrow.xbm to type Pixmap Warning: Cannot convert string /usr/local/lib/X11/xcalendar/quit.xbm to type Pixmap Warning: Cannot convert string /usr/local/lib/X11/xcalendar/qmark.xbm to type Pixmap Although xcalendar still works, various buttons and arrows in the user interface are replaced by text descriptions and the help screen is unavailable. The pixmap and help files are present in /usr/share/xcalendar, but xcalendar is looking for them in /usr/local/lib/X11/xcalendar. A temporary workaround is to link /usr/share/xcalendar to /usr/local/lib/X11/xcalendar. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.6 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages xcalendar-i18n depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library ii libsm61:1.0.0-4 X11 Session Management library ii libx11-6 2:1.0.0-7 X11 client-side library ii libxaw7 1:1.0.1-5 X11 Athena Widget library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxmu6 1:1.0.1-3 X11 miscellaneous utility library ii libxt61:1.0.0-5 X11 toolkit intrinsics library xcalendar-i18n recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378469: [Buildd-tools-devel] Bug#378469: backgrounded schroot processes do not terminate
Dear Roger,
The trace.log file produced by running
$ strace -o trace.log schroot -c ia32 -p oowriter
is attached. I did not know how to trace a version of schroot running in the
background (adding an ampersand to the command above would presumably put
strace into the background, not schroot) and did not try.
Your suggestion of redirecting stdin
$ schroot -c ia32 -p oowriter /dev/null
works! When oowriter's quit button is clicked, the schroot process quits
along with the oowriter process. This is the behaviour we were hoping to
see.
I don't think it likely that oowriter is opening stdin, so I guess that
the redirection of stdin is affecting schroot, not oowriter. This
suggests that the schroot termios restore is confused, as you suspected.
Although I speak C++ and would not have found it difficult to comment
out the lines you removed from schroot-base-main.cc, patching and
rebuilding a debian package from source was a new adventure for me!
Given your enthusiasm, however, I felt I had better try. To my surprise,
it was all surprisingly simple (although the build took a while).
Your patch also worked. Running the patched version
$ schroot -c ia32 -p oowriter
without the stdin redirection and quitting oowriter caused the schroot
process to quit too.
I think this provides enough information to pin down the problem.
I'll be away and out of email contact from tomorrow until Saturday 29th
July.
Best wishes, Matthew
--
**
Matthew Foulkes
Department of Physicsphone: (020) 7594 7607
Imperial College London fax: (020) 7594 7604
Prince Consort Road email: [EMAIL PROTECTED]
London SW7 2BW www: www.imperial.ac.uk/research/cmth
**
execve(/usr/bin/schroot, [schroot, -c, ia32, -p, oowriter], [/* 36
vars */]) = 0
uname({sys=Linux, node=dolphin, ...}) = 0
brk(0) = 0x5a3000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2b95860ab000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=69455, ...}) = 0
mmap(NULL, 69455, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2b95860ad000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/libuuid.so.1, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\200\16\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=10616, ...}) = 0
mmap(NULL, 1057536, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2b95861ac000
mprotect(0x2b95861ae000, 1049344, PROT_NONE) = 0
mmap(0x2b95862ae000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x2b95862ae000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/libpam.so.0, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0P\35\0\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=34088, ...}) = 0
mmap(NULL, 1080864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2b95862af000
mprotect(0x2b95862b7000, 1048096, PROT_NONE) = 0
mmap(0x2b95863b6000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x7000) = 0x2b95863b6000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/liblockdev.so.1, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\220\16\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=11120, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2b95863b7000
mmap(NULL, 1062152, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2b95863b8000
mprotect(0x2b95863bb000, 1049864, PROT_NONE) = 0
mmap(0x2b95864ba000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x2b95864ba000
mmap(0x2b95864bb000, 1288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2b95864bb000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libboost_program_options-gcc-mt-1_33_1.so.1.33.1, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\3203\1\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=225776, ...}) = 0
mmap(NULL, 1272728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2b95864bc000
mprotect(0x2b95864f1000, 1055640, PROT_NONE) = 0
mmap(0x2b95865f1000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x35000) = 0x2b95865f1000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT
Bug#378469: [Buildd-tools-devel] Bug#378469: backgrounded schroot processes do not terminate
I looked at the source but am not expert enough to investigate this myself. Sorry. The ideal behaviour, in my view, would be for schroot -c ia32 -p any_program to be equivalent to logging in to the chroot, changing to the right working directory, running any_program and then logging out of the chroot. At the moment this is not the case. If the termios restore is indeed the problem, one might ask whether this ought to be the job of schroot. I don't understand why schroot feels it has to fix problems caused by any_program? Would bash do something equivalent? If so, it might be worth investigating the approach used there. I am way out of my depth here and don't know what I am talking about, so I'll drop out of this discussion from now on. Sorry to have been awkward. Thanks again for your help. The enthusiasm of the Debian maintainers never ceases to amaze me. Matthew -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 Prince Consort Road email: [EMAIL PROTECTED] London SW7 2BW www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378469: backgrounded schroot processes do not terminate
Package: schroot Version: 0.99.3-1 Severity: minor I use schroot to run 32-bit programs such as openoffice on an AMD64 system. Commands such as $ schroot -c ia32 -p oowriter work fine. But if the command is backgrounded $ schroot -c ia32 -p oowriter the schroot process is *not* killed when oowriter exits: $ jobs [1]+ Stopped schroot -c ia32 -p oowriter It is necessary to kill these stopped processes explicitly to get rid of them, which is a little annoying. My schroot.conf file is: [ia32] description=Debian unstable (32 bit) location=/var/chroot/sid-ia32 priority=3 groups=users personality=linux32 On a separate issue, the DESCRIPTION section of the schroot man page discusses the -d option, which does not seem to exist. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.6 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages schroot depends on: ii libboost-program-options1.33. 1.33.1-4 program options library for C++ ii libboost-regex1.33.1 1.33.1-4 regular expression library for C++ ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-8 GCC support library ii liblockdev1 1.0.3-1Run-time shared library for lockin ii libpam0g 0.79-3.1 Pluggable Authentication Modules l ii libstdc++64.1.1-8The GNU Standard C++ Library v3 ii libuuid1 1.39-1 universally unique id library schroot recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370273: orage: segfaults when saving events
Package: orage
Version: 4.3.90.1-1
Severity: important
I installed orage on my amd64 system for the first time this
morning. It starts OK but segfaults every time I try to save
a new calendar event. I have no idea of the cause of the
problem.
In case it helps, the last few lines of the output of
ltrace orage are:
gethostname(???, 140737484716665)= 0
getuid() = 1000
malloc(17) = 0x86cf10
memset(0x86cf10, '\000', 17) = 0x86cf10
snprintf(, 4476925, \377\377\377\377\377\377\377\377...) = 16
pthread_once(0x563ac0, 0x42b220, 16, 0x86cf1f, 0) = 0
pthread_getspecific(2, 0x42b220, 16, 0x86cf1f, 0) = 0x6e4690
g_snprintf(0x563540, 1000, 0x442adc, 0x86cf10, 1000) = 35
malloc(56) = 0x891fd0
malloc(40) = 0x892010
malloc(152) = 0x8bb4b0
memset(0x8bb4d0, '\000', 120)= 0x8bb4d0
malloc(56) = 0x876760
malloc(40) = 0x8767a0
malloc(152) = 0x8bd480
memset(0x8bd4a0, '\000', 120)= 0x8bd4a0
malloc(56) = 0x8bd520
malloc(40) = 0x8bd560
malloc(152) = 0x8bd590
memset(0x8bd5b0, '\000', 120)= 0x8bd5b0
malloc(56) = 0x8bd630
malloc(40) = 0x8bd670
malloc(152) = 0x8bd6a0
memset(0x8bd6c0, '\000', 120)= 0x8bd6c0
__strdup(0x442aec, 0x442aec, 0, 0x8bd738, 0) = 0x892040
malloc(56) = 0x8bd740
malloc(40) = 0x8bd780
malloc(152) = 0x8bd7b0
memset(0x8bd7d0, '\000', 120)= 0x8bd7d0
__strdup(0x563540, 0x563540, 0, 0x8bd848, 0) = 0x8bd850
malloc(80) = 0x8bd880
malloc(40) = 0x8bd8e0
malloc(40) = 0x8bd910
malloc(32) = 0x8bd940
malloc(32) = 0x8bd970
malloc(32) = 0x8bd9a0
malloc(32) = 0x8bd9d0
malloc(32) = 0x8bda00
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
The last few lines of the output of strace orage are:
open(/home/matthew/.config/xfce4/orage/orage.ics, O_RDWR|O_CREAT,
0644) = 6
fcntl(6, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0
read(6, B, 1) = 1
read(6, E, 1) = 1
read(6, G, 1) = 1
read(6, I, 1) = 1
read(6, N, 1) = 1
read(6, :, 1) = 1
read(6, V, 1) = 1
read(6, C, 1) = 1
read(6, A, 1) = 1
read(6, L, 1) = 1
read(6, E, 1) = 1
read(6, N, 1) = 1
read(6, D, 1) = 1
read(6, A, 1) = 1
read(6, R, 1) = 1
read(6, \n, 1)= 1
read(6, V, 1) = 1
read(6, E, 1) = 1
read(6, R, 1) = 1
read(6, S, 1) = 1
read(6, I, 1) = 1
read(6, O, 1) = 1
read(6, N, 1) = 1
read(6, :, 1) = 1
read(6, 2, 1) = 1
read(6, ., 1) = 1
read(6, 0, 1) = 1
read(6, \n, 1)= 1
read(6, P, 1) = 1
read(6, R, 1) = 1
read(6, O, 1) = 1
read(6, D, 1) = 1
read(6, I, 1) = 1
read(6, D, 1) = 1
read(6, :, 1) = 1
read(6, -, 1) = 1
read(6, /, 1) = 1
read(6, /, 1) = 1
read(6, X, 1) = 1
read(6, f, 1) = 1
read(6, c, 1) = 1
read(6, e, 1) = 1
read(6, /, 1) = 1
read(6, /, 1) = 1
read(6, O, 1) = 1
read(6, r, 1) = 1
read(6, a, 1) = 1
read(6, g, 1) = 1
read(6, e, 1) = 1
read(6, /, 1) = 1
read(6, /, 1) = 1
Bug#109846: sshd: disabling passwords is confusing
Hi, I too have been bitten by this. Having set PasswordAuthentication no in /etc/sshd_config on sid, it took me several months (until I accidentally deleted my authorized_keys file) to realise that password authentication was still possible. The sshd and sshd_config man pages do not explain that it is necessary to set PasswordAuthentication no and at least one of: ChallengeResponseAuthentication no UsePAM no to disable password-based authentication completely. I guess there are plenty of other Debian users running systems with weak passwords, unaware that they may be vulnerable because their ssh setup is weaker than they thought. Better documentation would help here, preferably in /etc/sshd_config. Matthew -- ** Matthew Foulkes Department of Physicsphone: (020) 7594 7607 Imperial College London fax: (020) 7594 7604 Prince Consort Road email: [EMAIL PROTECTED] London SW7 2BW www: www.imperial.ac.uk/research/cmth ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
