Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Yes, this NAS unit also has 512M of RAM. Unfortunately, setting "innodb_flush_method=fsync" did not work. However, setting "innodb_use_native_aio=OFF" did work, but only after deleting the corrupted InnoDB files in /var/lib/mysql. On Thu, Dec 21, 2023 at 09:25:20AM +0200, Tuukka Pasanen wrote: Hello, Memory is still 512 MB? Thing that pops to my eye in 10.11 is mysqld: 2023-12-20 10:23:53 0 [ERROR] InnoDB: File ./ibdata1: 'aio read' returned OS error 0. Cannot continue operation As on 10.5 is used fsync not O_DIRECT which is default from 10.6 you can try (not promising anything) get it 10.11 working (more slowly though) with: innodb_flush_method=fsync More on change here: https://mariadb.com/kb/en/innodb-system-variables/#innodb_use_native_aio Sincerely, Tuukka Scott Barker kirjoitti 21.12.2023 klo 0.20: On my secondard ARM NAS, I downgraded from bookworm to bullseye, and installed mariadb 10.5 from scratch (no pre-existing /var/lib/mysql or /etc /mysql). Everything worked without issues. From syslog: mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql mysqld: 2023-12-20 7:58:07 0 [Note] Starting MariaDB 10.5.21-MariaDB-0+deb11u1 source revision bed70468ea08c2820647f5e3ac006a9ff88144ac as process 2250 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Uses event mutexes mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Number of pools: 1 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using generic crc32 instructions mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using Linux native AIO mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Completed initialization of buffer pool mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 128 rollback segments are active. mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 10.5.21 started; log sequence number 45079; transaction id 20 mysqld: 2023-12-20 7:58:07 0 [Note] Plugin 'FEEDBACK' is disabled. mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Loading buffer pool(s) from / var/lib/mysql/ib_buffer_pool mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Buffer pool(s) load completed at 231220 7:58:07 mysqld: 2023-12-20 7:58:07 0 [Note] Server socket created on IP: '127.0.0.1'. mysqld: 2023-12-20 7:58:07 0 [Note] Reading of all Master_info entries succeeded mysqld: 2023-12-20 7:58:07 0 [Note] Added new Master_info '' to hash table mysqld: 2023-12-20 7:58:07 0 [Note] /usr/sbin/mariadbd: ready for connections. mysqld: Version: '10.5.21-MariaDB-0+deb11u1' socket: '/run/mysqld/ mysqld.sock' port: 3306 Debian 11 I then proceeded to upgrade from bookworm all packages containing libraries to which /usr/sbin/mariadbd and /usr/lib/mysql/plugin/* were linked, one at a time, restarting mariadb after each package was installed, and there were no issues. I then upgraded the rest of the system to bookworm, a few packages at a time, excluding the mariadb packages. I restarted mariadb after each batch of packages, and there were no issues, including after reboot into the new kernel. I then renamed /var/lib/mysql to /var/lib/mysql.bak and ran: dpkg-reconfigure -plow mariadb-server-10.5 mariadb-server-core-10.5 Again, no issues - /var/lib/mysql was re-created and mariadbd started just fine, with the same syslog entries as above. I then copied /var/lib/mysql to /var/lib/mysql-10.5 and upgraded mariadb with: apt upgrade mariadb-server-10.5 Here is the entire output, you can see the errors at the end: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-core-10.5 The following NEW packages will be installed: libnuma1 liburing2 mariadb-client mariadb-client-core mariadb-server mariadb-server-core The following packages will be upgraded: mariadb-server-10.5 1 upgraded, 6 newly installed, 3 to remove and 0 not upgraded. Need to get 12.7 MB of archives. After this operation, 28.0 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://deb.debian.org/debian bookworm/main armel mariadb-server-10.5 armel 1:10.11.4-1~deb12u1 [22.7 kB] Get:2 https://deb.debian.org/debian bookworm/main armel mariadb-client-core armel 1:10.11.4-1~deb12u1 [75
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
opefully help mysqld: diagnose the problem, but since we have already crashed, mysqld: something is definitely wrong and this may fail. mysqld: mysqld: Server version: 10.11.4-MariaDB-1~deb12u1 source revision: mysqld: key_buffer_size=134217728 mysqld: read_buffer_size=131072 mysqld: max_used_connections=0 mysqld: max_threads=153 mysqld: thread_count=1 mysqld: It is possible that mysqld could use up to mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466625 K bytes of memory mysqld: Hope that's ok; if not, decrease some variables in the equation. mysqld: mysqld: Thread pointer: 0x0 mysqld: Attempting backtrace. You can use the following information to find out mysqld: where mysqld died. If you see no messages after this, something went mysqld: terribly wrong... mysqld: stack_bottom = 0x0 thread_stack 0x49000 mysqld: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains mysqld: information that should help you find out what is causing the crash. mysqld: Writing a core file... mysqld: Working directory at /var/lib/mysql mysqld: Resource Limits: mysqld: Limit Soft Limit Hard Limit Units mysqld: Max cpu time unlimitedunlimitedseconds mysqld: Max file size unlimitedunlimitedbytes mysqld: Max data size unlimitedunlimitedbytes mysqld: Max stack size8388608 unlimitedbytes mysqld: Max core file size0unlimitedbytes mysqld: Max resident set unlimitedunlimitedbytes mysqld: Max processes 1904 1904 processes mysqld: Max open files3218332183files mysqld: Max locked memory 8388608 8388608 bytes mysqld: Max address space unlimitedunlimitedbytes mysqld: Max file locksunlimitedunlimitedlocks mysqld: Max pending signals 1904 1904 signals mysqld: Max msgqueue size 819200 819200 bytes mysqld: Max nice priority 00 mysqld: Max realtime priority 00 mysqld: Max realtime timeout unlimitedunlimitedus mysqld: Core pattern: core mysqld: mysqld: Kernel version: Linux version 6.1.0-16-marvell (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 Debian 6.1.67-1 (2023-12-12) mysqld: mysqld_safe: mysqld from pid file /run/mysqld/mysqld.pid ended /etc/init.d/mariadb[4054]: 0 processes alive and '/usr/bin/mariadb-admin --defaults-file=/etc/mysql/debian.cnf ping' resulted in /etc/init.d/mariadb[4054]: #007/usr/bin/mariadb-admin: connect to server at 'localhost' failed /etc/init.d/mariadb[4054]: error: 'Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)' /etc/init.d/mariadb[4054]: Check that mariadbd is running and that the socket: '/run/mysqld/mysqld.sock' exists! After the upgrade, a "diff" on the two mysql folders shows: Only in mysql/: ddl_recovery.log Only in mysql/: debian-10.11.flag Only in mysql-10.5/: debian-10.5.flag Binary files mysql-10.5/ib_logfile0 and mysql/ib_logfile0 differ Only in mysql/: ibtmp1 No other files changed. I then added these two lines in the [server] section of /etc/mysql/mariadb.conf.d/50-server.cnf: innodb = OFF default-storage-engine = MyISAM Then I ran: apt install -f After this, mariadbd started successfully, but without the InnoDB engine, as can be seen in syslog: mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql mysqld: 2023-12-20 11:01:31 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 5560 mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'InnoDB' is disabled. mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'FEEDBACK' is disabled. mysqld: 2023-12-20 11:01:32 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. mysqld: 2023-12-20 11:01:32 0 [Note] Server socket created on IP: '127.0.0.1'. mysqld: 2023-12-20 11:01:32 0 [Note] /usr/sbin/mariadbd: ready for connections. mysqld: Version: '10.11.4-MariaDB-1~deb12u1' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 12 /etc/mysql/debian-start[5589]: Upgrading MySQL tables if necessary. /etc/mysql/debian-start[5599]: Checking for insecure root accounts. /etc/mysql/debian-start[5603]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables On Tue, Dec 19, 2023 at 08:07:16AM -0700, Scott Barker wrote: For myself, I am not using XEN/KVM/
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
For myself, I am not using XEN/KVM/Docker. I am installing this on a NAS device with an ARM chip and only 512M of RAM. I tried adding a 2G swap file, but it did not make a difference. I was able to start mariadb by disabling INNODB and using MyISAM instead with the options: --innodb=OFF --default-storage-engine=MyISAM On Mon, Dec 18, 2023 at 09:23:55AM +0200, Tuukka Pasanen wrote: Hello, Have you monitored that is memory exhausted at the installation? This could lead error like that. I assume your XEN/KVM/Docker base machine is some older system with not so fancy CPU or is there any particular reason to use armel build? Sincerly, Tuukka Scott Barker kirjoitti 17.12.2023 klo 19.15: Same result with the latest kernel: Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: Prior to the installation, /var/lib/mysql did not exist. After installation: 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 /var/lib/mysql 61975 4 -rw-rw 1 mysql mysql 52 Dec 17 09:56 /var/lib/mysql/aria_log_control 61983 12304 -rw-rw 1 mysql mysql 12582912 Dec 17 09:56 /var/lib/mysql/ibdata1 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 /var/lib/mysql/debian-10.11.flag 61990 98404 -rw-rw 1 mysql mysql 100663296 Dec 17 09:56 /var/lib/mysql/ib_logfile101 61982 16 -rw-rw 1 mysql mysql 16384 Dec 17 09:56 /var/lib/mysql/aria_log.0001 uname -a reports: Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: Hi Scott and Kr! Did you note this line? 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 Can you include the output of `find /var/lib/mysql -ls` so we can see what files your system has? What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. What does `uname -a` yield? The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/ +archive/ubuntu/mariadb-10.11/+builds?build_text=_state=all. At https:// ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to regression in subselect which is unrelated to what you reported. -- Scott Barker -- To unsubscribe, send mail to 1058706-unsubscr...@bugs.debian.org. -- Scott Barker
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Same result with the latest kernel: Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: Prior to the installation, /var/lib/mysql did not exist. After installation: 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 /var/lib/mysql 61975 4 -rw-rw 1 mysql mysql52 Dec 17 09:56 /var/lib/mysql/aria_log_control 61983 12304 -rw-rw 1 mysql mysql 12582912 Dec 17 09:56 /var/lib/mysql/ibdata1 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 /var/lib/mysql/debian-10.11.flag 61990 98404 -rw-rw 1 mysql mysql 100663296 Dec 17 09:56 /var/lib/mysql/ib_logfile101 6198216 -rw-rw 1 mysql mysql 16384 Dec 17 09:56 /var/lib/mysql/aria_log.0001 uname -a reports: Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: Hi Scott and Kr! Did you note this line? 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 Can you include the output of `find /var/lib/mysql -ls` so we can see what files your system has? What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. What does `uname -a` yield? The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/ +archive/ubuntu/mariadb-10.11/+builds?build_text=_state=all. At https:// ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to regression in subselect which is unrelated to what you reported. -- Scott Barker -- To unsubscribe, send mail to 1058706-unsubscr...@bugs.debian.org. -- Scott Barker
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Prior to the installation, /var/lib/mysql did not exist. After installation: 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 /var/lib/mysql 61975 4 -rw-rw 1 mysql mysql52 Dec 17 09:56 /var/lib/mysql/aria_log_control 61983 12304 -rw-rw 1 mysql mysql 12582912 Dec 17 09:56 /var/lib/mysql/ibdata1 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 /var/lib/mysql/debian-10.11.flag 61990 98404 -rw-rw 1 mysql mysql 100663296 Dec 17 09:56 /var/lib/mysql/ib_logfile101 6198216 -rw-rw 1 mysql mysql 16384 Dec 17 09:56 /var/lib/mysql/aria_log.0001 uname -a reports: Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: Hi Scott and Kr! Did you note this line? 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 Can you include the output of `find /var/lib/mysql -ls` so we can see what files your system has? What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. What does `uname -a` yield? The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/ +archive/ubuntu/mariadb-10.11/+builds?build_text=_state=all. At https:// ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to regression in subselect which is unrelated to what you reported. -- Scott Barker
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Package: mariadb-server-core Version: 1:10.11.6-1 Severity: important Dear Maintainer, On a fresh install of mariadb on armel architecture, mariadb fails to start. This happens with the version of mariadb in Debian stable (bookworm, version 1:10.11.4-1~deb12u1) and Debian testing (trixie, version 1:10.11.6-1). There were no existing databases, and the folder /var/lib/mysql did not exist prior to the install. Here is the error shown when dpkg perform the install and tries to start mariadbd: Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231214 14:51:33 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-error configuration options for --syslog to take effect. 231214 14:51:33 mysqld_safe Logging to '/tmp/tmp.AUoKfplrEX.err'. 231214 14:51:33 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql Running '/etc/init.d/mariadb start' failed with error log: 231214 14:51:33 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql 2023-12-14 14:51:33 0 [Note] Starting MariaDB 10.11.6-MariaDB-1 source revision as process 23044 2023-12-14 14:51:33 0 [Note] InnoDB: Compressed tables use zlib 1.3 2023-12-14 14:51:33 0 [Note] InnoDB: Number of transaction pools: 1 2023-12-14 14:51:33 0 [Note] InnoDB: Using generic crc32 instructions 2023-12-14 14:51:33 0 [Note] InnoDB: Using liburing 2023-12-14 14:51:33 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2023-12-14 14:51:33 0 [Note] InnoDB: Completed initialization of buffer pool 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 2023-12-14 14:51:33 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrite buffer. 2023-12-14 14:51:33 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption 2023-12-14 14:51:33 0 [Note] InnoDB: Starting shutdown... 2023-12-14 14:51:34 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2023-12-14 14:51:34 0 [Note] Plugin 'FEEDBACK' is disabled. 2023-12-14 14:51:34 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded 2023-12-14 14:51:34 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2023-12-14 14:51:34 0 [ERROR] Aborting 231214 14:51:34 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended failed! invoke-rc.d: initscript mariadb, action "start" failed. dpkg: error processing package mariadb-server (--install): installed mariadb-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: mariadb-server -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 5.10.0-26-marvell (UP) Kernel taint flags: TAINT_WARN Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages mariadb-server-core depends on: ii libatomic1 12.2.0-14 ii libc6 2.36-9+deb12u3 ii libcrypt1 1:4.4.33-2 ii libelogind0 [libsystemd0] 246.10-1debian1 ii libnuma1 2.0.16-1 ii libpcre2-8-0 10.42-1 ii libssl33.0.11-1~deb12u2 ii libstdc++6 13.2.0-7 ii liburing2 2.3-3 ii mariadb-common 1:10.11.6-1 ii zlib1g 1:1.2.13.dfsg-1 mariadb-server-core recommends no packages. mariadb-server-core suggests no packages. -- no debconf information
Bug#991678: new upstream versions
LXC versions 4.0.9 and above seem to fix Debian bug #978065 (After upgrade lxc to 4.0.5-1, cannot start with lxc.cap.drop sys_admin). Therefore, including a newer version of LXC in bullseye would fix this potential security issue. Maybe a newer version of LXC could be included in bullseye-backports or bullseye-proposed-updates in the meantime? -- Scott Barker
Bug#941379: xfce4-mailwatch-plugin: please consider adding support for secret-tool and/or libsecret
Package: xfce4-mailwatch-plugin Version: 1.2.0-3 Severity: normal Dear Maintainer, Please consider adding support for secret-tool or libsecret for retrieving passwords, instead of storing them in plaintext. -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xfce4-mailwatch-plugin depends on: ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libexo-1-0 0.12.4-1 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgcrypt20 1.8.4-5 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u1 ii libgnutls30 3.6.7-4 ii libgtk2.0-0 2.24.32-3 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpangoft2-1.0-01.42.4-7~deb10u1 ii libxfce4ui-1-0 4.12.1-3 ii libxfce4util74.12.1-3 ii xfce4-panel 4.12.2-1 xfce4-mailwatch-plugin recommends no packages. xfce4-mailwatch-plugin suggests no packages. -- debconf-show failed
Bug#939282: davmail: Please consider making libopenjfx-java a Recommends instead of a Depends
Package: davmail Version: 5.1.0.2891-2 Severity: normal davmail is capable of running as a headless server, however, the dependency on libopenjfx-java brings in many extra X11 packages that are unnecessary in headless mode. Please consider making libopenjfx-java a Recommends: instead of a Depends: so that davmail can be used on a minimal server without X11 packages. Thank you. -- System Information: Debian Release: 9.9 APT prefers oldstable APT policy: (990, 'oldstable'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-0.bpo.5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#933880: khal aborts when piping an ics file from another program, such as mutt
Package: khal Version: 1:0.9.10-1.1 Severity: normal The problem is due to a test done against /dev/tty Please consider cherry-picking https://github.com/pimutils/khal/pull/861 for inclusion in the Debian package, as it fixes the issue. Thank you. -- System Information: Debian Release: 9.9 APT prefers oldstable APT policy: (990, 'oldstable'), (500, 'proposed-updates'), (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-0.bpo.5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages khal depends on: ii python33.5.3-1 ii python3-atomicwrites 1.1.5-1 ii python3-click 6.6-1 ii python3-configobj 5.0.6-2 ii python3-dateutil 2.5.3-2 ii python3-icalendar 4.0.3-2 ii python3-pkg-resources 33.1.1-1 ii python3-tz 2016.7-0.3 ii python3-tzlocal1.3-1 ii python3-urwid 1.3.1-2+b1 ii python3-xdg0.25-4 Versions of packages khal recommends: pn python3-setproctitle Versions of packages khal suggests: pn khal-doc -- debconf-show failed
Bug#913612: openresolv: metric logic is flawed
Package: openresolv
Version: 3.8.0-1
Severity: normal
The documentation for the -m options says:
Set the metric of the interface when adding it, default of 0. Lower metrics
take precedence.
However, if you assign any metric to an interface, it will actually take
precedence over any interface which doesn't have a metric defined and isn't
in the interface_order or dynamic_order. Hence, the default metric is
actually one more than 999. For example:
# /sbin/resolvconf -i
lo.unbound wlan0
# cat myvpn_resolvconf | /sbin/resolvconf -m 99 -a myvpn
# /sbin/resolvconf -i
lo.unbound myvpn wlan0
# find /run/resolvconf/ -type f
/run/resolvconf/interfaces/myvpn
/run/resolvconf/interfaces/lo.unbound
/run/resolvconf/interfaces/wlan0
/run/resolvconf/metrics/099 myvpn
I'm attaching a trivial patch that fixes this behaviour.
-- System Information:
Debian Release: 9.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- /sbin/resolvconf2016-04-20 13:30:01.0 -0600
+++ resolvconf 2018-11-12 17:04:16.296605415 -0700
@@ -404,13 +404,15 @@
fi
done
done
+ for i in *; do
+ [ ! -e "$METRICDIR/"*" $i" ] && list="$list $i"
+ done
if [ -d "$METRICDIR" ]; then
cd "$METRICDIR"
for i in *; do
[ -f "$i" ] && list="$list ${i#* }"
done
fi
- list="$list *"
fi
cd "$IFACEDIR"
Bug#913602: openresolv: wrong config location for unbound
Package: openresolv Version: 3.8.0-1 Severity: normal The included resolvconf.conf file saves the unbound configuration to: /var/cache/unbound/resolvconf_resolvers.conf However, in Debian, unbound only looks for config files in: /etc/unbound/unbound.conf.d/ This is easily fixed after installation, but the install package should really have the correct location to start with. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#872379: chkrootkit hangs when egrepping files in /dev in lxc containers
Package: chkrootkit
Version: 0.50-4+b2
Severity: normal
lxc bind-mounts pts devices over files in /dev when starting a container,
but "find" ignores bind mounts when evaluating file types.
Therefore, a bind-mounted device like this:
$ ls -l /dev/console
c--x--x--x 1 root tty 136, 1 Aug 16 15:53 /dev/console
Still shows up when running "find" to look for regular files:
$ find /dev -type f
/dev/console
Because of this behaviour, the chkrootkit command:
files=`${find} ${ROOTDIR}dev -type f -exec ${egrep} -l "^[0-5] " {} \;`
ends up hanging while trying to egrep /dev/console
This can be avoided by adding an -fstype argument to the find command:
files=`${find} ${ROOTDIR}dev -type f ! -fstype devpts -exec ${egrep} -l
"^[0-5] " {} \;`
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages chkrootkit depends on:
ii binutils 2.28-5
ii debconf [debconf-2.0] 1.5.61
ii libc6 2.24-11+deb9u1
ii net-tools 1.60+git20161116.90da8a0-1
ii openssh-client 1:7.4p1-10+deb9u1
ii procps 2:3.3.12-3
chkrootkit recommends no packages.
chkrootkit suggests no packages.
Bug#865587: wordpress: Upgrade from jessie (wordpress 4.1) to stretch (wordpress 4.7) loses all theme and menu settings
I was using the theme from the wordpress-theme-twentyfifteen debian package, which installed to /usr/share/wordpress/wp-content/themes/twentyfifteen, with a symlink to that created in /var/lib/wordpress/wp-content/themes/. I had customized colours and added a logo to the theme using the wordpress admin web interface, which I believe just saves the customizations in the wordpress database. Upon upgrade from wordpress 4.1 to wordpress 4.7, when I logged on as the admin, I was prompted to perform a wordpress DB upgrade, which I accepted. After that, when I went to my wordpress page, it had reverted to the default look from the twentyfifteen theme. I assume the DB upgrade failed to preserve the customizations. I was able to redo my colour and logo changes in the admin web interface. On Fri, Jun 30, 2017 at 10:46:19PM +, Craig Small wrote: > > > On Fri, Jun 23, 2017 at 8:39 AM Scott Barker <sc...@mostlylinux.ca> wrote: > > I had a working install of wordpress 4.1+dfsg-1+deb8u14 on jessie, with > customized colours, logos, etc. Upon updating to stretch and wordpress > 4.7.5+dfsg-2, all theme customizations were lost. > > This sounds like where you had put these themes wasn't quite where we > expected. > They should still be there though. > Do you know what directory these files were? > > Also, when you mean customization, how were you doing this? Was it adjusting > the existing theme (that is generally a bad idea) or you had your own themes > you downloaded elsewhere. > What do you mean by "lost"? It went back to the default look? The themes > failed > to work? The adjustments to the themes reverted? Or perhaps wordpress just > gave > a blank white screen. > > Generally these sorts of problems are an interaction of WP_CONTENT_DIR defined > in /etc/wordpress and the home directory defined in apache. > > - Craig > > > > > > -- > Craig Small https://dropbear.xyz/ csmall at : enc.com.au > Debian GNU/Linux https://www.debian.org/ csmall at : debian.org > Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees > GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- Scott Barker
Bug#865587: wordpress: Upgrade from jessie (wordpress 4.1) to stretch (wordpress 4.7) loses all theme and menu settings
Source: wordpress Version: 4.7.5+dfsg-2 Severity: important I had a working install of wordpress 4.1+dfsg-1+deb8u14 on jessie, with customized colours, logos, etc. Upon updating to stretch and wordpress 4.7.5+dfsg-2, all theme customizations were lost. If this is expected behaviour, the user should be presented with a warning prior to the upgrade proceeding. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#863856: getmail4: please use run-parts --list or similar to enumerate the config files in ~/.getmail/config/
Package: getmail4 Version: 4.53.0-1 Severity: wishlist The getmails script considers every file in ~/.getmail/config/ to be a valid config file, including any backup files from editors like vim, emacs, etc. To avoid this, please consider using "run-parts --list $HOME/.getmail/config/" to enumerate the config files, instead of "for file in $HOME/.getmail/config/*" Thank you. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#863849: davmail: Please include headless jre packages as dependencies
Package: davmail Version: 4.7.3.2438-2 Severity: wishlist It is possible to run davmail completely headless, for example on a standalone server. Please consider including the headless java runtime packages in the Depends header. For example: default-jre | java6-runtime | java7-runtime | java8-runtime | default-jre-headless | java6-runtime-headless | java7-runtime-headless | java8-runtime-headless Thank you. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages davmail depends on: pn libswt-cairo-gtk-3-jni | libswt-cairo-gtk-3.5-jni pn libswt-gtk-3-java | libswt-gtk-3.6-java | libswt-gtk-3.5-java | lib pn openjdk-7-jre | openjdk-6-jre | oracle-java7-jre | sun-java6-jre davmail recommends no packages. davmail suggests no packages.
Bug#863143: wicd pm script prevents wireless wake on lan (WoWLAN) from working
Package: wicd Version: 1.7.4+tb2-3 Severity: normal Dear Maintainer, The pm-utils script provided with wicd prevents wireless wake on lan from working: - /usr/lib/pm-utils/sleep.d/55wicd runs /usr/share/wicd/daemon/suspend.py - /usr/share/wicd/daemon/suspend.py invokes the Disconnect and SetSuspend methods in /usr/share/wicd/daemon/wicd-daemon.py - The SetSuspend method in /usr/share/wicd/daemon/wicd-daemon.py also invokes the Disconnect method in /usr/share/wicd/daemon/wicd-daemon.py - The Disconnect method in /usr/share/wicd/daemon/wicd-daemon.py invokes the Wireless.Disconnect() method in /usr/lib/python2.7/dist-packages/wicd/networking.py - The Wireless.Disconnect() method in /usr/lib/python2.7/dist-packages/wicd/networking.py takes down the wireless interface, which disassociates it from the access point, making wireless wake on lan impossible. Over-riding or blacklisting 55wicd fixes the problem, but it would probably be better to change one of the python methods involved to check the state of wireless wake on lan (as set by sudo iw phy0 wowlan enable ...) before taking the interface down completely. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wicd depends on: ii wicd-daemon 1.7.4+tb2-3 ii wicd-gtk [wicd-client] 1.7.4+tb2-3 wicd recommends no packages. wicd suggests no packages. Versions of packages wicd-gtk depends on: ii python-glade2 2.24.0-5.1 ii python-gtk22.24.0-5.1 pn python:any ii wicd-daemon1.7.4+tb2-3 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-9+b1 pn python-notify Versions of packages wicd-daemon depends on: ii adduser 3.115 ii dbus 1.10.18-1 ii debconf 1.5.60 ii ethtool 1:4.8-1+b1 ii iproute2 4.9.0-1 ii iputils-ping 3:20161105-1 ii isc-dhcp-client 4.3.5-3 ii lsb-base 9.20161125 ii net-tools1.60+git20161116.90da8a0-1 ii psmisc 22.21-2.1+b2 ii python-dbus 1.2.4-1+b1 ii python-gobject 3.22.0-2 ii python-wicd 1.7.4+tb2-3 pn python:any ii wireless-tools 30~pre9-12+b1 ii wpasupplicant2:2.4-1 Versions of packages wicd-daemon recommends: ii rfkill 0.5-1+b1 ii wicd-gtk [wicd-client] 1.7.4+tb2-3 Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-17 Versions of packages python-wicd depends on: pn python:any -- debconf information: * wicd/users:
Bug#861717: nodm init script checks for NODM_XINIT even though nodm now ignores that variable
Package: nodm Version: 0.13-1 Severity: normal >From the README.md file: * `NODM_XINIT` Was used by older versions of nodm as the path to the xinit program, but it is now ignored. Also, nodm does not depend upon the xinit package (nor any other package that depends upon xinit), and so will fail to start on systems which, for example, don't install xinit and instead start a single X application, such as minimal kiosk systems. References to NODM_XINIT should probably be removed from the init script. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#860915: cloud-initramfs-tools: Please re-enable generation of the overlayroot package
Source: cloud-initramfs-tools Version: 0.18.debian5 Severity: wishlist Dear Maintainer, Please re-enable generation of the overlayroot package. Debian stretch now includes the overlay filesystem module. Thank you. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#836932: login to blank screen after upgrade to 0.9
We have a similar problem, and have tracked it to an issue with PAM. We're using libpam-ldap here, and replacing the "@include common-session" line in /etc/pam.d/xrdp-sesman with the content of /etc/pam.d/common-session, then commenting out the "session optional pam_ldap.so" line fixes the problem. -- Scott Barker
Bug#855960: flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2
I know the db entry for the NETGEAR ReadyNAS Duo v2 is missing from this installer image, which is the one I've been using: http://ftp.debian.org/debian/dists/jessie/main/installer-armel/20150422+deb8u4+b2/images/kirkwood/netboot/marvell/openrd/uInitrd On Fri, Mar 17, 2017 at 04:28:46PM -0700, Martin Michlmayr wrote: > * Scott Barker <sc...@mostlylinux.ca> [1969-12-31 17:52]: > > Please add suuport for NETGEAR ReadyNAS Duo v2. The db entry that works for > > me is: > > Thanks, I added this in git. > > Do we also have to create any installation images in debian-installer? > > -- > Martin Michlmayr > http://www.cyrius.com/ -- Scott Barker
Bug#855965: libdebian-installer: Please add support for NETGEAR ReadyNAS Duo v2
Package: libdebian-installer
Version: 0.108
Severity: wishlist
Dear Maintainer,
Please add support for NETGEAR ReadyNAS Duo v2, which uses a "kirkwood"
processor:
# cat /proc/device-tree/model
NETGEAR ReadyNAS Duo v2
# cat /proc/cpuinfo
processor : 0
model name : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS: 1594.36
Features: swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part: 0x131
CPU revision: 1
Hardware: Marvell Kirkwood (Flattened Device Tree)
Revision:
Serial :
I believe you can add this to map_hardware[] :
{ "NETGEAR ReadyNAS Duo v2" , "kirkwood" },
Thank you.
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Bug#855960: flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2
Package: flash-kernel Version: 3.70~bpo8+1 Severity: wishlist Dear Maintainer, Please add suuport for NETGEAR ReadyNAS Duo v2. The db entry that works for me is: Machine: NETGEAR ReadyNAS Duo v2 DTB-Id: kirkwood-netgear_readynas_duo_v2.dtb DTB-Append: yes Mtd-Kernel: uImage Mtd-Initrd: minirootfs U-Boot-Kernel-Address: 0x8000 U-Boot-Initrd-Address: 0x Required-Packages: u-boot-tools Bootloader-Sets-Incorrect-Root: yes Thank you. -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 3.16.0-4-kirkwood Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.56 ii devio 1.2-1+b1 ii initramfs-tools0.120+deb8u2 ii linux-base 3.5 ii mtd-utils 1:1.5.1-1 ii ucf3.0030 Versions of packages flash-kernel recommends: ii u-boot-tools 2014.10+dfsg1-5 flash-kernel suggests no packages. -- debconf information: flash-kernel/linux_cmdline: quiet
Bug#854662: linux-image-4.9.0-0.bpo.1-marvell: please enable CONFIG_SENSORS_G762
Package: src:linux Version: 4.9.2-2~bpo8+1 Severity: wishlist Dear Maintainer, I am installing debian on a Netgear ReadyNAS Duo v2, and so far everything works except some of the sensors, because CONFIG_SENSORS_G762 is not set: $ grep CONFIG_SENSORS_G762 /boot/config-4.9.0-0.bpo.1-marvell # CONFIG_SENSORS_G762 is not set Please consider enabling this feature. Thank you. -- Package-specific info: ** Version: Linux version 4.9.0-0.bpo.1-marvell (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 Debian 4.9.2-2~bpo8+1 (2017-01-26) ** Command line: root=/dev/md0 console=ttyS0,115200 earlyprintk reason=normal mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2); ** Not tainted ** Kernel log: [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.9.0-0.bpo.1-marvell (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 Debian 4.9.2-2~bpo8+1 (2017-01-26) [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] OF: fdt:Machine model: NETGEAR ReadyNAS Duo v2 [0.00] bootconsole [earlycon0] enabled [0.00] Memory policy: Data cache writeback [0.00] On node 0 totalpages: 65536 [0.00] free_area_init_node: node 0, pgdat c059d218, node_mem_map cfdf8000 [0.00] Normal zone: 512 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 65536 pages, LIFO batch:15 [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [0.00] Kernel command line: root=/dev/md0 console=ttyS0,115200 earlyprintk reason=normal mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2); [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Memory: 241080K/262144K available (3796K kernel code, 397K rwdata, 1124K rodata, 300K init, 298K bss, 21064K reserved, 0K cma-reserved, 0K highmem) [0.00] Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xffc0 - 0xfff0 (3072 kB) vmalloc : 0xd080 - 0xff80 ( 752 MB) lowmem : 0xc000 - 0xd000 ( 256 MB) pkmap : 0xbfe0 - 0xc000 ( 2 MB) modules : 0xbf00 - 0xbfe0 ( 14 MB) .text : 0xc0008000 - 0xc03bd2c8 (3797 kB) .init : 0xc04fd000 - 0xc0548000 ( 300 kB) .data : 0xc0548000 - 0xc05ab7e8 ( 398 kB) .bss : 0xc05ab7e8 - 0xc05f6060 ( 299 kB) [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] clocksource: orion_clocksource: mask: 0x max_cycles: 0x, max_idle_ns: 9556302233 ns [0.06] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [0.008266] Console: colour dummy device 80x30 [0.012817] Calibrating delay loop... 1594.36 BogoMIPS (lpj=3188736) [0.042766] pid_max: default: 32768 minimum: 301 [0.047596] Security Framework initialized [0.051784] Yama: disabled by default; enable with sysctl kernel.yama.* [0.058590] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.065292] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.073254] CPU: Testing write buffer coherency: ok [0.078286] ftrace: allocating 16938 entries in 34 pages [0.109047] Setting up static identity map for 0x8200 - 0x823c [0.115169] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1 [0.122672] devtmpfs: initialized [0.130442] VFP support v0.3: not present [0.134688] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [0.144697] pinctrl core: initialized pinctrl subsystem [0.150947] NET: Registered protocol family 16 [0.155764] DMA: preallocated 256 KiB pool for atomic coherent allocations [0.163874] cpuidle: using governor ladder [0.168070] cpuidle: using governor menu [0.172333] Feroceon L2: Enabling L2 [0.176022] Feroceon L2: Cache support initialised. [0.181173] [Firmware Info]: /ocp@f100/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set [0.195085] No ATAGs? [0.201235] clocksource: Switched to clocksource orion_clocksource [0.218696] VFS: Disk quotas dquot_6.6.0 [0.222792] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [0.236187] NET: Registered protocol family 2 [0.241328] TCP established hash table entries: 2048 (order: 1, 8192 bytes) [0.248386] TCP bind hash
Bug#814819: xmltv-util: The computation used by tv_grab_na_dd for --offset is incorrect
Package: xmltv-util
Version: 0.5.63-2
Severity: normal
tv_grab_na_dd uses the --offset option in a way that does not allow negative
offsets (ie. grabbing data for the previous X days). The attached patch
fixes the issue, and does not break positive offsets.
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (103, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages xmltv-util depends on:
pn libarchive-zip-perl
ii libdata-dump-perl 1.22-1
ii libdate-manip-perl6.47-1
pn libdatetime-format-iso8601-perl
pn libdatetime-format-strptime-perl
ii libdatetime-perl 2:1.12-1
ii libdatetime-timezone-perl 1:1.75-2+2015g
ii libhtml-parser-perl 3.71-1+b3
pn libhtml-tableextract-perl
ii libhtml-tree-perl 5.03-1
pn libhttp-cache-transparent-perl
ii libio-stringy-perl2.110-5
ii libjson-perl 2.61-1
ii libparse-recdescent-perl 1.967009+dfsg-1
pn libsoap-lite-perl
ii libterm-readkey-perl 2.32-1+b1
pn libtext-bidi-perl
ii libtext-iconv-perl1.7-5+b2
pn libwww-mechanize-perl
ii libwww-perl 6.08-1
pn libxml-dom-perl
pn libxml-libxml-perl
pn libxml-libxslt-perl
ii libxml-parser-perl2.41-3
ii libxml-twig-perl 1:3.48-1
pn libxml-writer-perl
pn libxmltv-perl
ii perl [libio-compress-perl]5.20.2-3+deb8u3
ii perl-modules 5.20.2-3+deb8u3
Versions of packages xmltv-util recommends:
pn liblingua-preferred-perl
pn libterm-progressbar-perl
ii libunicode-string-perl2.09-5+b2
Versions of packages xmltv-util suggests:
pn liblinux-dvb-perl
pn liblog-tracemessages-perl
pn libtext-kakasi-perl
pn xmltv-gui
--- /usr/bin/tv_grab_na_dd 2012-06-29 19:22:43.0 -0600
+++ tv_grab_na_dd 2016-02-15 09:45:09.167082293 -0700
@@ -638,7 +638,7 @@
#
# TMS bug causes errors around UTC midnight, so let's bump it by a second
#
-my $start = DateCalc("00:00:01","+ $opt_offset days") || die "ERROR: Can't compute <$opt_offset> days\n";
+my $start = DateCalc("00:00:01","$opt_offset days") || die "ERROR: Can't compute <$opt_offset> days\n";
my $stop = DateCalc($start,"+ $opt_days days") || die "ERROR: Can't compute <$opt_days> days\n";
#
Bug#778650: freerdp-x11: Alt key gets stuck with -grab-keyboard option when using Alt-Tab to switch between local X windows
Package: freerdp-x11 Version: 1.1.0~git20140921.1.440916e+dfsg1-2+b1 Severity: normal When running xfreerdp with the -grab-keyboard option, using Alt-Tab to switch local windows results in the remote Windows session thinking that the Alt key is still pressed when returning focus to the xfreerdp window, whether returning with Alt-Tab or using the mouse. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (103, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages freerdp-x11 depends on: ii libc6 2.19-13 ii libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-client1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-common1.1.01.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-core1.11.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-crypto1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-gdi1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-locale1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-primitives1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-rail1.11.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libfreerdp-utils1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libjpeg62-turbo 1:1.3.1-11 ii libssl1.0.0 1.0.1k-1 ii libwinpr-crt0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-crypto0.11.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-dsparse0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-environment0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-file0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-handle0.11.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-heap0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-input0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-interlocked0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-library0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-path0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-pool0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-registry0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-rpc0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-sspi0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-synch0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-sysinfo0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-thread0.11.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libwinpr-utils0.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxfreerdp-client1.1 1.1.0~git20140921.1.440916e+dfsg1-2+b1 ii libxi62:1.7.4-1+b2 ii libxinerama1 2:1.1.3-1+b1 ii libxkbfile1 1:1.0.8-1 ii libxrender1 1:0.9.8-1+b1 ii libxv12:1.0.10-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages freerdp-x11 recommends: ii libfreerdp-plugins-standard 1.1.0~git20140921.1.440916e+dfsg1-2+b1 freerdp-x11 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#766271: Please package new version 0.5.66 to fix tv_grab_na_dd
There is a new thread regarding this at: http://forums.schedulesdirect.org/viewtopic.php?f=3t=2614 where it says: Tribune is now directing *ALL* traffic to our SD-DD server. We don't know how long Tribune will keep their DNS active, so you should still change your applications. So it appears that the current version of xmltv-util in debian should continue to work for now, but could stop working at any random point in the future. -- Scott Barker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766270: xmltv-utils: Please package new version
Package: xmltv-utils Version: 0.5.63-2 Severity: important Dear Maintainer, The version of tv_grab_na_dd in xmltv-utils 0.5.63-2 will stop working as of Nov 1, according to these forum posts at schedulesdirect.org: http://forums.schedulesdirect.org/viewtopic.php?f=3t=2578 http://forums.schedulesdirect.org/viewtopic.php?f=7t=2577 http://forums.schedulesdirect.org/viewtopic.php?f=8t=2599 tv_grab_na-dd in version 0.5.66 of xmltv has been updated to use the new datadirect replacement service according to it's Changelog: 2014-09-30 15:30 rmeden * grab/na_dd/tv_grab_na_dd.in: switch na_dd to new data direct server Alternatively, just the URL in tv_grab_na_dd.in could be updated, as per the forum post http://forums.schedulesdirect.org/viewtopic.php?f=8t=2599: The best way to use the new SD-DD service is by updating your application. In your code, replace the two TMS hostnames with dd.schedulesdirect.org. WSDL: http://dd.schedulesdirect.org/tech/tmsdatadirect/schedulesdirect/tvDataDelivery.wsdl Service: http://dd.schedulesdirect.org/schedulesdirect/tvlistings/xtvdService Thank you. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (103, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766270: Please close
Sorry, I reported this bug against an non-existent package name. I have re-filed the bug report against the correct package, and this bug report may be closed. -- Scott Barker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766271: xmltv-util: Please package new version 0.5.66 to fix tv_grab_na_dd
Package: xmltv-util Version: 0.5.63-2 Severity: important Dear Maintainer, The version of tv_grab_na_dd in xmltv-util 0.5.63-2 will stop working as of Nov 1, according to these forum posts at schedulesdirect.org: http://forums.schedulesdirect.org/viewtopic.php?f=3t=2578 http://forums.schedulesdirect.org/viewtopic.php?f=7t=2577 http://forums.schedulesdirect.org/viewtopic.php?f=8t=2599 tv_grab_na-dd in version 0.5.66 of xmltv has been updated to use the new datadirect replacement service according to it's Changelog: 2014-09-30 15:30 rmeden * grab/na_dd/tv_grab_na_dd.in: switch na_dd to new data direct server Alternatively, just the URL in tv_grab_na_dd.in could be updated, as per the forum post http://forums.schedulesdirect.org/viewtopic.php?f=8t=2599: The best way to use the new SD-DD service is by updating your application. In your code, replace the two TMS hostnames with dd.schedulesdirect.org. WSDL: http://dd.schedulesdirect.org/tech/tmsdatadirect/schedulesdirect/tvDataDelivery.wsdl Service: http://dd.schedulesdirect.org/schedulesdirect/tvlistings/xtvdService Thank you. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (103, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xmltv-util depends on: ii libarchive-zip-perl 1.38-1 ii libdata-dump-perl 1.22-1 ii libdate-manip-perl6.47-1 ii libdatetime-format-iso8601-perl 0.08-1 ii libdatetime-format-strptime-perl 1.5600-1 ii libdatetime-perl 2:1.12-1 ii libdatetime-timezone-perl 1:1.75-1+2014h ii libhtml-parser-perl 3.71-1+b2 ii libhtml-tableextract-perl 2.11-1 ii libhtml-tree-perl 5.03-1 ii libhttp-cache-transparent-perl1.1-1 ii libio-stringy-perl2.110-5 ii libjson-perl 2.61-1 ii libparse-recdescent-perl 1.967009+dfsg-1 ii libsoap-lite-perl 1.11-1 ii libterm-readkey-perl 2.32-1+b1 ii libtext-bidi-perl 2.09-2 ii libtext-iconv-perl1.7-5+b2 ii libwww-mechanize-perl 1.73-2 ii libwww-perl 6.08-1 ii libxml-dom-perl 1.44-1 ii libxml-libxml-perl2.0116+dfsg-1+b1 ii libxml-libxslt-perl 1.92-1+b1 ii libxml-parser-perl2.41-3 ii libxml-twig-perl 1:3.44-1 ii libxml-writer-perl0.625-1 ii libxmltv-perl 0.5.63-2 ii perl [libio-compress-perl]5.20.1-1 ii perl-modules 5.20.1-1 Versions of packages xmltv-util recommends: ii liblingua-preferred-perl 0.2.4-4 ii libterm-progressbar-perl 2.16-1 ii libunicode-string-perl2.09-5+b2 Versions of packages xmltv-util suggests: pn liblinux-dvb-perl none ii liblog-tracemessages-perl 1.4-3 pn libtext-kakasi-perlnone pn xmltv-gui 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#762211: lightdm crashes on startup, system falls back to console
I had this same problem, and while digging around for the cause, I found the file /usr/share/lightdm/lightdm.conf.d/01_debian.conf. If I try to set any of the options listed in that file in /etc/lightdm/lightdm.conf, lightdm crashes. Perhaps lightdm cannot handle an option being set twice? -- Scott Barker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750847: Still a problem with XFCE panel 4.10.1-1
This is still a problem with the XFCE 4.10.1-1 panel. -- Scott Barker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735043: [Pkg-owncloud-maintainers] Bug#735043: libqtkeychain0: Please update to version 0.2.0 which includes gnome keyring support
My apologies - I saw the version bump in the git changelog, and assumed that meant it was released. As an FYI, I checked out the latest version from github and compiled it, and it works just fine with the gnome keyring. On Sun, Jan 12, 2014 at 10:38:40PM +0100, Sandro Knauß wrote: Hello, Please upgrade to version 0.2.0, which includes gnome keyring support. Either I'm blind or version 0.2.0 isn't released. According to upstream it isn't taged: https://github.com/frankosterfeld/qtkeychain/releases where did you see the release of 0.2.0? I only found the request for the new version at the bug report, that is not closed: https://github.com/frankosterfeld/qtkeychain/issues/21 If it is released I'll package it and will ship it. Regards, sandro -- Scott Barker Linux Consultant sc...@mostlylinux.ca http://www.mostlylinux.ca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735043: libqtkeychain0: Please update to version 0.2.0 which includes gnome keyring support
Package: libqtkeychain0 Version: 0.1.0-2~bpo70+1 Severity: normal Please upgrade to version 0.2.0, which includes gnome keyring support. Otherwise, owncloud-client (which depends upon libqtkeychain0) stores users' passwords in cleartext in the owncloud.cfg file on non-KDE desktop environments. -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-0.bpo.3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libqtkeychain0 depends on: ii libc6 2.13-38 ii libgcc11:4.7.2-5 ii libqt4-dbus4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii multiarch-support 2.13-38 libqtkeychain0 recommends no packages. libqtkeychain0 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#671122: mail-notification: TLSv1 connections fail with libssl1.0.0 version 1.0.1b-1
On Wed, May 02, 2012 at 07:43:03AM +0200, Stephen Kitt wrote: I suppose it worked with version 1.0.0h-1, can you confirm? That is correct - no problems with 1.0.0h-1. There are some other packages still having problems with 1.0.1b-1, so it would appear that some things aren't fixed yet (perhaps unrelated to this problem in particular). mail-notification doesn't do anything fancy with openssl though... I do have occasional access to an Exchange 2003 server so I'll try to reproduce the bug on my end. Thanks, Stephen. Much appreciated. -- Scott Barker Linux Consultant sc...@mostlylinux.ca http://www.mostlylinux.ca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671122: mail-notification: TLSv1 connections fail with libssl1.0.0 version 1.0.1b-1
Package: mail-notification Version: 5.4.dfsg.1-5 Severity: important Dear Maintainer, After upgrading to libssl1.0.0 version 1.0.1b-1, mail-notification can no longer connect via SSL/TLS to IMAP on Exchange 2003. The error is: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number This seems to be related to all of the other problems people have been having with libssl1.0.0 1.0.0h-1 I tried rebuilding mail-notification using the libssl1.0.0 version 1.0.1b-1 headers, but that did not solve the problem. I am filing this bug against mail-notification since the consensus seems to be that version 1.0.1b-1 of libssl1.0.0 is supposed to fix this problem. -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mail-notification depends on: ii gconf-service3.2.3-4 ii gconf2 3.2.3-4 ii gnome-icon-theme 3.4.0-2 ii gstreamer0.10-tools 0.10.36-1 ii libatk1.0-0 2.4.0-2 ii libbonobo2-0 2.24.3-1 ii libc62.13-30 ii libcairo-gobject21.10.2-7 ii libcairo21.10.2-7 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgconf-2-4 3.2.3-4 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.0-4 ii libgmime-2.6-0 2.6.7-1 ii libgnome-keyring03.4.1-1 ii libgnome2-0 2.32.1-2 ii libgnomevfs2-0 1:2.24.4-1 ii libgnomevfs2-extra 1:2.24.4-1 ii libgtk-3-0 3.2.3-1 ii libnotify4 0.7.5-1 ii liborbit21:2.14.19-0.1 ii libpango1.0-01.29.4-3+b1 ii libpopt0 1.16-3 ii libsasl2-2 2.1.25.dfsg1-4 ii libssl1.0.0 1.0.1b-1 ii libx11-6 2:1.4.4-4 ii libxml2 2.7.8.dfsg-9 ii xfce4-notifyd [notification-daemon] 0.2.2-1 Versions of packages mail-notification recommends: pn fetchyahoo none pn getlive none pn mail-notification-evolution none mail-notification 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#666449: Upgrade of openssl to 1.0.1-2 breaks connection to gmail
I don't know if the attached patch will fix the problem with gmail, but it does fix a similar problem connecting to an Exchange 2003 server by forcing a SSLv3 connection. -- Scott Barker Linux Consultant sc...@mostlylinux.ca http://www.mostlylinux.ca --- /usr/share/pyshared/offlineimap/imaplibutil.py.orig 2011-08-10 13:44:58.0 -0600 +++ /usr/share/pyshared/offlineimap/imaplibutil.py 2012-04-27 09:03:31.099857027 -0600 @@ -183,7 +183,7 @@ self.sslobj = ssl.wrap_socket(self.sock, self.keyfile, self.certfile, ca_certs = self._cacertfile, - cert_reqs = requirecert) + cert_reqs = requirecert, ssl_version=ssl.PROTOCOL_SSLv3) except NameError: #Python 2.4/2.5 don't have the ssl module, we need to #socket.ssl() here but that doesn't allow cert @@ -193,7 +193,7 @@ #allow us to easily check it. So bail out here. raise Exception(SSL CA Certificates cannot be checked with python =2.6. Abort) self.sslobj = socket.ssl(self.sock, self.keyfile, - self.certfile) + self.certfile, ssl_version=ssl.PROTOCOL_SSLv3) else: #ssl.wrap_socket worked and cert is verified (if configured),
Bug#665452: libssl1.0.0: breaks HTTPS download of some sites
For those people experiencing this problem with offlineimap, the attached patch fixes the problem for me by forcing SSLv3 connections. -- Scott Barker Linux Consultant sc...@mostlylinux.ca http://www.mostlylinux.ca --- /usr/share/pyshared/offlineimap/imaplibutil.py.orig 2011-08-10 13:44:58.0 -0600 +++ /usr/share/pyshared/offlineimap/imaplibutil.py 2012-04-27 09:03:31.099857027 -0600 @@ -183,7 +183,7 @@ self.sslobj = ssl.wrap_socket(self.sock, self.keyfile, self.certfile, ca_certs = self._cacertfile, - cert_reqs = requirecert) + cert_reqs = requirecert, ssl_version=ssl.PROTOCOL_SSLv3) except NameError: #Python 2.4/2.5 don't have the ssl module, we need to #socket.ssl() here but that doesn't allow cert @@ -193,7 +193,7 @@ #allow us to easily check it. So bail out here. raise Exception(SSL CA Certificates cannot be checked with python =2.6. Abort) self.sslobj = socket.ssl(self.sock, self.keyfile, - self.certfile) + self.certfile, ssl_version=ssl.PROTOCOL_SSLv3) else: #ssl.wrap_socket worked and cert is verified (if configured),
Bug#575424: [Pkg-xfce-devel] Bug#575424: libexo-0.3-0: exo-compose-mail-0.3 should pass mailto URLs to mutt unbroken
Unfortunately, it has been so long since I reported this issue that I no longer recall what problem I was having. I'm not even sure if the patch is valid anymore. Feel free to close the bug - if I encounter a problem again, I'll send an update. On Thu, Apr 07, 2011 at 01:06:11PM +0200, Yves-Alexis Perez wrote: On jeu., 2010-03-25 at 12:05 -0600, Scott Barker wrote: mutt can handle mailto URLs just fine. Instead of breaking the mailto URL apart and passing in separate parameters, exo-compose-mail-0.3 should use logic for mutt similar to the logic for balsa. The attached patch fixes this. What would be the rationale for this? Is this an improvement? In what? Regards, -- Yves-Alexis -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612083: libdate-manip-perl: ParseRecur breaks for some recur definitions
Package: libdate-manip-perl Version: 6.11-1 Severity: normal ParseRecur fails on some recur definitions. For example, these: perl -e'use Date::Manip; @dates=ParseRecur(0:0:1*6:0:0:0**2007120800:00:00*2011013000:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:1*6:0:0:0**2008081600:00:00*2011013000:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:1*6:0:0:0**2010061200:00:00*2011013000:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:2*5:0:0:0**2008081500:00:00*2011011500:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:2*5:0:0:0**2009011600:00:00*2011011500:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:3*4:0:0:0**2010102100:00:00*2011011400:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:3*6:0:0:0**2011011500:00:00*2011011600:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:6*6:0:0:0**2011012900:00:00*2011012900:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:12*2:0:0:0**2011030800:00:00*2011030800:00:00*,undef,undef,3 years);' all produce the error: Can't use an undefined value as an ARRAY reference at /usr/share/perl5/Date/Manip/Recur.pm line 1066. However, these all work fine: perl -e'use Date::Manip; @dates=ParseRecur(0:0:3*6:0:0:0**2010112000:00:00*2011012300:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:4*6:0:0:0**2011010800:00:00*2011010900:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:8*6:0:0:0**2010120400:00:00*2010120500:00:00*,undef,undef,3 years);' perl -e'use Date::Manip; @dates=ParseRecur(0:0:12*2:0:0:0**2011012500:00:00*2011012600:00:00*,undef,undef,3 years);' -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdate-manip-perl depends on: ii libyaml-syck-perl 1.12-1 Perl module providing a fast, ligh ii perl 5.10.1-17 Larry Wall's Practical Extraction libdate-manip-perl recommends no packages. libdate-manip-perl suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607750: mirage: screenshots broken
Package: mirage Version: 0.9.5.1-1 Severity: normal When trying to take a screenshot, it does not work, and mirage outputs the following: Traceback (most recent call last): File /usr/lib/pymodules/python2.6/mirage.py, line 2342, in screenshot self.screenshot_delay = int(delay.get_text()) ValueError: invalid literal for int() with base 10: '' Screenshots will work if the delay is hard-coded by editing /usr/lib/pymodules/python2.6/mirage.py, and changing line 2342 from: self.screenshot_delay = int(delay.get_text()) to: self.screenshot_delay = 2 So there is something wrong related to the int(delay.get_text()) bit. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mirage depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libx11-62:1.3.3-4X11 client-side library ii python 2.6.6-3+squeeze2 interactive high-level object-orie ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge ii python-support 1.0.10 automated rebuilding support for P mirage recommends no packages. Versions of packages mirage suggests: ii gimp 2.6.10-1The GNU Image Manipulation Program ii imagemagick 8:6.6.0.4-3 image manipulation programs ii menu 2.1.44 generates programs menu for all me -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605036: hamster-applet: file monitoring does not always work
Package: hamster-applet Version: 2.30.2-2 Severity: normal When using a synchronization tool like unison (and perhaps dropbox), the file monitoring is not working. The changelog for the new version of hamster-applet (2.32.1) claims to fix this. It would be appreciated if the new version of hamster-applet could be packaged in time for the next Debian release. Thank you. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hamster-applet depends on: ii gconf22.28.1-6 GNOME configuration database syste ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libfontconfig12.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libpango1.0-0 1.28.3-1 Layout and rendering of internatio ii python2.6.6-3+squeeze1 interactive high-level object-orie ii python-cairo 1.8.8-1+b1 Python bindings for the Cairo vect ii python-dbus 0.83.1-1 simple interprocess messaging syst ii python-evolution 2.30.0-3 Python bindings for the evolution ii python-gconf 2.28.1-1 Python bindings for the GConf conf ii python-gnome2 2.28.1-1 Python bindings for the GNOME desk ii python-gnomeapplet2.30.0-3 Python bindings for the GNOME pane ii python-gobject2.21.4+is.2.21.3-1 Python bindings for the GObject li ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge ii python-notify 0.1.1-2+b2 Python bindings for libnotify ii python-support1.0.10 automated rebuilding support for P ii python-wnck 2.30.0-3 Python bindings for the WNCK libra ii python-xdg0.19-2 Python library to access freedeskt hamster-applet recommends no packages. hamster-applet 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#605036: patch
The attached patch, cherry-picked from the git repository, fixes the problem. The original patch was from the db.py file, but the affected code is still in configuration.py in the current Debian version. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott diff -urbBw hamster-applet-2.30.2/src/hamster/configuration.py hamster-applet-2.30.2.local1/src/hamster/configuration.py --- hamster-applet-2.30.2/src/hamster/configuration.py 2010-11-26 09:39:22.0 -0700 +++ hamster-applet-2.30.2.local1/src/hamster/configuration.py 2010-11-26 09:35:39.0 -0700 @@ -91,7 +91,11 @@ if gio_file.query_info(gio.FILE_ATTRIBUTE_ETAG_VALUE).get_etag() == self.last_etag: # ours return +elif event == gio.FILE_MONITOR_EVENT_CREATED: +# treat case when instead of a move, a remove and create has been performed +self.storage.con = None +if event in (gio.FILE_MONITOR_EVENT_CHANGES_DONE_HINT, gio.FILE_MONITOR_EVENT_CREATED): logging.info(DB file has been modified externally. Calling all stations) self.storage.dispatch_overwrite()
Bug#598536: live-config: config.d/ config files not parsed on live media
Package: live-config
Version: 3.0~a8-1
Severity: normal
Tags: patch
There is a typo in /lib/live/config.sh
The attached patch should fix the problem.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (900, 'testing'), (700, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages live-config depends on:
ii live-config-sysvinit [live-co 3.0~a8-1 Debian Live - System Configuration
Versions of packages live-config recommends:
pn live-toolsnone (no description available)
ii sudo 1.7.4p4-2 Provide limited super user privile
ii user-setup1.34 Set up initial user and password
Versions of packages live-config suggests:
ii wget 1.12-2.1 retrieves files from the web
-- no debconf information
--- /lib/live/config.sh 2010-09-26 01:15:06.0 -0600
+++ config.sh 2010-09-29 13:57:12.0 -0600
@@ -237,7 +237,7 @@
if ls /live/image/live/config.d/* /dev/null 21
then
- for FILE in /live/image/live/config.d/*
+ for _FILE in /live/image/live/config.d/*
do
. ${_FILE}
done
Bug#598375: live-config: hooks on media do not run
Package: live-config Version: 2.0.7+20100926.070409~60squeeze+1 Severity: normal The 999-hooks script allows filesystem and media as options to the hooks= boot argument, however, it tries to use wget to copy them, and wget just complains Scheme missing. If there is no scheme specified, the script should just use cp. Note also that the man page for live-config incorrectly states medium as an option for the hooks= boot argument, instead of media. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-config depends on: ii live-c 2.0.7+20100926.070409~60squeeze+1 Debian Live - System Configuration Versions of packages live-config recommends: ii sudo 1.7.4p4-2 Provide limited super user privile ii user-setup1.34 Set up initial user and password Versions of packages live-config suggests: ii wget 1.12-2.1 retrieves files from the web -- 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#598375: live-config: hooks on media do not run
I specified hooks=medium, so the script found the hooks in /live/hooks/*, but then uses them as raw filenames, without pre-pending file:// to them. On Tue, Sep 28, 2010 at 07:09:02PM +0200, Daniel Baumann wrote: tag 598375 moreinfo thanks On 09/28/2010 05:19 PM, Scott Barker wrote: The 999-hooks script allows filesystem and media as options to the hooks= boot argument, however, it tries to use wget to copy them, and wget just complains Scheme missing. If there is no scheme specified, the script should just use cp. it should do the right thing if your filesystem or medium hooks are in the format of a file:// url. are you using it with file:// prefix? Note also that the man page for live-config incorrectly states medium as an option for the hooks= boot argument, instead of media. updated the script to match the manpage (it should not be plural here). -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598375: live-config: hooks on media do not run
I'm pretty sure that the first for loop in the script is incorrect as well.
The case statement uses ${LIVE_HOOKS} instead of ${_HOOK}, which doesn't
work if more than one hook is defined.
--
Scott Barker sc...@mostlylinux.ca
Linux Consultant http://www.mostlylinux.ca/scott
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598375: live-config: hooks on media do not run
There is also a faulty if statement on line 56. This is incorrect:
if $(echo ${_HOOK} | grep file:\/\/)
this is correct:
if (echo ${_HOOK} | grep file:\/\/)
Probably file:\/\/ could also just be file://.
I think in the sed statement, file\:// could just be file:// as well.
--
Scott Barker sc...@mostlylinux.ca
Linux Consultant http://www.mostlylinux.ca/scott
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590791: [Pkg-samba-maint] Bug#590791
] libsmb/clikrb5.c:729(ads_krb5_mk_req) ads_krb5_mk_req: server marked as OK to delegate to, building forwardable TGT [2010/09/02 17:40:35, 2] lib/interface.c:340(add_interface) added interface eth0 ip=fe80::21a:a0ff:fea7:4f75%eth0 bcast=fe80:::::%eth0 netmask=::::: [2010/09/02 17:40:35, 2] lib/interface.c:340(add_interface) added interface eth0 ip=10.0.0.166 bcast=10.0.0.255 netmask=255.255.255.0 [2010/09/02 17:40:35, 4] libads/dns.c:620(ads_dns_lookup_ns) ads_dns_lookup_ns: 3 records returned in the answer section. DNS update failed! [2010/09/02 17:40:35, 2] utils/net.c:779(main) return code = -1 -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
After applying the latest kernel package, all of my VMs started just fine as well. All i386. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
Thanks, I tested that, and it does seem to work. Hopefully this bug is being worked on by someone upstream. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
I am experiencing this problem as well. I have read through this bug report, and the most recent entry suggesting purging util-vserver does not make any sense. If you purge that package, you lose the utilities you need to start the virtual servers. If you re-install it from lenny sources, the problem persists. Just wondering if anyone has a solution for this yet, short of stopping and restarting all affected vservers after reboot. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577795: feed2imap: please add the maildir patches from upstream
Package: feed2imap Version: 0.9.4-1 Severity: wishlist Upstream has added the capability to save feeds directly to maildir folders. Please pull the patches from upstream's git repository and include them in the debian package. Thank you. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages feed2imap depends on: ii libfeedparser-ruby1.80.7-1 Ruby library to parse ATOM/RSS fee ii librmail-ruby1.8 0.17-1.1lightweight mail library for Ruby ii ruby 4.4 An interpreter of object-oriented ii ruby1.8 1.8.7.249-2 Interpreter of object-oriented scr Versions of packages feed2imap recommends: ii libopenssl-ruby1.8 1.8.7.249-2 OpenSSL interface for Ruby 1.8 Versions of packages feed2imap suggests: ii claws-mail [imap-client] 3.7.5-1Fast, lightweight and user-friendl pn imap-server none (no description available) ii mutt [imap-client]1.5.20-7 text-based mailreader supporting M -- 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#575423: libexo-0.3-0: parsing of mailto urls in exo-compose-mail-0.3 is case sensitive
Package: libexo-0.3-0
Version: 0.3.106-1
Severity: normal
exo-compose-mail-0.3 ignores the subject and body in the following URL
because they are capitalized:
mailto:mutt-announce-requ...@mutt.org?subject=subscribe%20mutt%20announceBody=subscribe
The attached patch makes the URL parser case-insensitive.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libexo-0.3-0 depends on:
ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-3 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.20-2 simple interprocess messaging syst
ii libexo-common 0.3.106-1libexo common files
ii libfontconfig1 2.8.0-2 generic font configuration library
ii libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii libglib2.0-02.22.4-1 The GLib library of C routines
ii libgtk2.0-0 2.18.9-2 The GTK+ graphical user interface
ii libhal-storage1 0.5.14-2 Hardware Abstraction Layer - share
ii libhal1 0.5.14-2 Hardware Abstraction Layer - share
ii libnotify1 [libnotify1- 0.4.5-1 sends desktop notifications to a n
ii libpango1.0-0 1.26.2-2 Layout and rendering of internatio
ii liburi-perl 1.52-1 module to manipulate and access UR
ii libxfce4util4 4.6.1-2 Utility functions library for Xfce
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
libexo-0.3-0 recommends no packages.
libexo-0.3-0 suggests no packages.
-- no debconf information
--- /usr/lib/libexo-0.3-0/exo-compose-mail-0.3 2009-12-12 08:09:37.0
-0700
+++ exo-compose-mail-0.32010-03-25 11:59:16.0 -0600
@@ -42,33 +42,33 @@
# mailto:-components
my @to = ();
my @cc = ();
my $subject = undef;
my $body = undef;
my @attachments = ();
# parse the mailto:-address
my @headers = $mailtoUrl-headers();
for (my $n = 0; $n $#headers; $n += 2) {
- if ($headers[$n] eq 'to') {
+ if ($headers[$n] =~ /^to$/i) {
push (@to, $headers[$n + 1]);
}
- elsif ($headers[$n] eq 'cc') {
+ elsif ($headers[$n] =~ /^cc$/i ) {
push (@cc, $headers[$n + 1]);
}
- elsif ($headers[$n] eq 'subject') {
+ elsif ($headers[$n] =~ /^subject$/i ) {
$subject = $headers[$n + 1];
}
- elsif ($headers[$n] eq 'body') {
+ elsif ($headers[$n] =~ /^body$/i ) {
$body = $headers[$n + 1];
}
- elsif ($headers[$n] eq 'attach') {
+ elsif ($headers[$n] =~ /^attach$/i ) {
# be sure to add as file:-URI
my $f = $headers[$n + 1];
push(@attachments, ($f =~ m/^file:\//) ? URI-new($f) :
URI::file-new_abs($f));
}
}
# start with only the binary name
my @argv = ($binary);
# add style-specific parameters
Bug#575424: libexo-0.3-0: exo-compose-mail-0.3 should pass mailto URLs to mutt unbroken
Package: libexo-0.3-0
Version: 0.3.106-1
Severity: normal
mutt can handle mailto URLs just fine. Instead of breaking the mailto URL
apart and passing in separate parameters, exo-compose-mail-0.3 should use
logic for mutt similar to the logic for balsa. The attached patch fixes
this.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libexo-0.3-0 depends on:
ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-3 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.20-2 simple interprocess messaging syst
ii libexo-common 0.3.106-1libexo common files
ii libfontconfig1 2.8.0-2 generic font configuration library
ii libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii libglib2.0-02.22.4-1 The GLib library of C routines
ii libgtk2.0-0 2.18.9-2 The GTK+ graphical user interface
ii libhal-storage1 0.5.14-2 Hardware Abstraction Layer - share
ii libhal1 0.5.14-2 Hardware Abstraction Layer - share
ii libnotify1 [libnotify1- 0.4.5-1 sends desktop notifications to a n
ii libpango1.0-0 1.26.2-2 Layout and rendering of internatio
ii liburi-perl 1.52-1 module to manipulate and access UR
ii libxfce4util4 4.6.1-2 Utility functions library for Xfce
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
libexo-0.3-0 recommends no packages.
libexo-0.3-0 suggests no packages.
-- no debconf information
--- exo-compose-mail-0.3.old2010-03-25 11:59:45.0 -0600
+++ exo-compose-mail-0.32010-03-25 11:59:47.0 -0600
@@ -178,21 +178,21 @@
}
elsif ($style eq 'mutt') {
# generate the parameters for mutt
+ my $mailto = 'mailto:' . ((@to 0) ? uri_escape($to[0]) : ) . '?';
+ for (my $n = 1; $n @to; $n++) {
+ $mailto .= 'cc=' . uri_escape($to[$n]) . '';
+ }
for my $cc (@cc) {
- push (@argv, '-c', $cc);
+ $mailto .= 'cc=' . uri_escape($cc) . '';
}
+ $subject and $mailto .= 'subject=' . uri_escape($subject) . '';
+ $body and $mailto .= 'body=' . uri_escape($body);
+
+ # and add the parameters to the argv
+ push (@argv, $mailto);
for my $uri (@attachments) {
push (@argv, '-a', $uri-path ());
}
- $subject and push (@argv, '-s', $subject);
- for my $to (@to) {
- push (@argv, $to);
- }
-
- # mutt needs an address, if we don't have
- # any, just append an empty string and mutt
- # will prompt for the To: address
- (not @to) and push (@argv, '');
}
else {
print STDERR $0: Unsupported style '$style'.\n;
Bug#529520: [Pkg-xfce-devel] Bug#529520: orage: segfault when importing an iCal file
Attached is a backtrace. Note that if orage is running, and it's calendar window is visible, all I get is a failure message as follows: Starting program: /usr/bin/orage Appt2016-12774.ics [Thread debugging using libthread_db enabled] ** (orage:31544): WARNING **: import failed file=Appt2016-12774.ics Program exited normally. Only if orage is not running (File - Quit in the calendar window) does the segmentation fault occur. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott backtrace Description: Binary data
Bug#529520: [Pkg-xfce-devel] Bug#529520: orage: segfault when importing an iCal file
I also am experiencing these problems when trying to import an ical file without a UID. On the first attempt, I get the fail message. On the second attempt, I get a segfault. Shouldn't orage generate a UID if it is missing? -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561970: libdate-manip-perl: cannot be used in taint (-T) mode
Package: libdate-manip-perl
Version: 6.05-1
Severity: normal
Perl scripts cannot be run in taint mode when using Date::Manip. This simple
perl script:
#!/usr/bin/perl -T
use Date::Manip;
fails with the following message:
Insecure $ENV{PATH} while running with -T switch at
/usr/share/perl5/Date/Manip/TZ.pm line 588.
Compilation failed in require at ./test line 3.
BEGIN failed--compilation aborted at ./test line 3.
This seems to be a result of the TZ methods including commands to be run
with the _cmd subroutine.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libdate-manip-perl depends on:
ii libyaml-syck-perl 1.07-1 fast, lightweight YAML loader and
ii perl 5.10.1-8 Larry Wall's Practical Extraction
libdate-manip-perl recommends no packages.
libdate-manip-perl suggests no packages.
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561970: libdate-manip-perl: cannot be used in taint (-T) mode
Following up, it appears that the problem is that Date::Manip::TZ does not understand SystemV timezones as used by Debian. My /etc/timezone file contains: SystemV/MST7MDT Changing it to: America/Edmonton fixes the insecure path taint error. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548752: Same problem
I am having the same problem upgrading to 0.72.2-2. From the web interface: GLPI SETUP Update Database connection successful Update - 0.72.1 Work ended. (0 Sec(s)) Update - 0.72.2 Work in progress... 0.72.2 reorder search.constant Error during the database updateDuplicate entry '11-34-0' for key 'display' -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548752: 548752
Dropping and re-creating the glpi_display table from the SQL statements in /usr/share/dbconfig-common/data/glpi/install/mysql seems to work fine. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: xfce4-utils: sessions started with startxfce4 lose hal/dbus functionality
Just to bring this bug report back to it's original focus, I note that bugs 526006 and 520720 have been closed, and consolekit has been changed to properly use ck-launch-session for users of startx at the console. There are now many ways to start xfce4 at the console with a correct consolekit session, but the two best seem to be: 1) The Debian way: Set xfce4-session as the default session manager for X (with update-alternatives) and use startx at the console to start xfce4. This will provide a minimal xfce4 session. For a more complete xfce4 session, the user can put exec /usr/bin/startxfce4 in $HOME/.xsession, so that various environment variables are set correctly for xfce4. 2) The xfce4 way: Put exec ck-launch-session /etc/xdg/xfce4/xinitrc in $HOME/.config/xfce4/xinitrc, make $HOME/.config/xfce4/xinitrc executable, and use startxfce4 to start xfce4. This will ensure the various environment variables are set correctly for xfce4, and will also ensure that a correct consolekit session is started. For either method, libpam-ck-connector can be installed or not installed, it doesn't matter. For method 2), perhaps one day the xfce4 developers will include ck-launch-session in the startxfce4 script (as they did for dbus), and then the xinitrc customization will no longer be necessary. For users of gdm/kdm/xdm, I do not know if it is possible to get more than the minimal xfce4 session - it will depend if those display managers call startxfce4 and/or set the correct environment variables. As I don't use gdm/kdm/xdm, I cannot test that. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: [Pkg-xfce-devel] Bug#526009: xfce4-utils: sessions started with startxfce4 lose hal/dbus functionality
On 09/01/09 15:41, Yves-Alexis Perez wrote:
Thanks for the summary, it'll definitely be quite helpful for users. It
might be a good idea to push that to the xfce4{-session} README.Debian.
Would you license it to GPL or something? :)
Please feel free to include it in the README.Debian file if you think it
will be helpful.
1) The Debian way:
Set xfce4-session as the default session manager for X (with
update-alternatives) and use startx at the console to start xfce4.
This will provide a minimal xfce4 session. For a more complete xfce4
session, the user can put exec /usr/bin/startxfce4 in $HOME/.xsession,
so that various environment variables are set correctly for xfce4.
And this is the preferred way :)
2) The xfce4 way:
Put exec ck-launch-session /etc/xdg/xfce4/xinitrc in
$HOME/.config/xfce4/xinitrc, make $HOME/.config/xfce4/xinitrc
executable, and use startxfce4 to start xfce4. This will ensure the
various environment variables are set correctly for xfce4, and will also
ensure that a correct consolekit session is started.
In fact, even method 1) will enable that, since startxfce4 will
run /etc/xdg/xfce4/xinitrc (or $HOME/.config/xfce4/xinitrc if it
exists)
True, but only if exec /usr/bin/startxfce4 is put into
$HOME/.xsession. Otherwise, it appears that the Debian startx process
just runs /usr/bin/x-session-manager, which for xfce4 is xfce4-session,
not startxfce4. (I determined this by looking at
/etc/X11/Xsession.d/50x11-common_determine-startup).
For either method, libpam-ck-connector can be installed or not
installed, it doesn't matter.
For method 2), perhaps one day the xfce4 developers will include
ck-launch-session in the startxfce4 script (as they did for dbus), and
then the xinitrc customization will no longer be necessary.
It's already not necessary, imho.
I have confirmed that if the user just runs startxfce4 without making
any other customizations to the xfce4 or X11 startup process,
ck-launch-session does not get used, and thus the original problem remains.
For users of gdm/kdm/xdm, I do not know if it is possible to get more
than the minimal xfce4 session - it will depend if those display
managers call startxfce4 and/or set the correct environment variables.
As I don't use gdm/kdm/xdm, I cannot test that.
Then don't worry, they already call (gdm at least does) startxfce4.
I note that gdm uses the .desktop files in /usr/share/xsessions to
determine what session managers are available. If startx used a similar
mechanism, then using $HOME/.xsession to spawn startxfce4 would become
unnecessary too.
--
Scott Barker sc...@mostlylinux.ca
Linux Consultant http://www.mostlylinux.ca/scott
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529613: gvfs-backends: gphoto2 backend blocks UMS/MSC access to devices
This no longer seems to be an issue. It looks like it was fixed by a combination of recent changes to libgphoto2-2 (I have 2.4.6-1) and hal-info (I have 20090716-1): http://gphoto.svn.sourceforge.net/viewvc/gphoto/branches/libgphoto2-2_4/libgphoto2/libgphoto2_port/usb/libusb.c?r1=12026r2=12025pathrev=12026 http://cgit.freedesktop.org/hal-info/commit/?id=b6d3ed743f58eff42c0dbdcbf8e7598a589e1584 In any event, for my Walkman (NWZ-A829), the problem has been fixed. If other people still encounter the problem with their music players, I suggest the real problem may now lie with hal-info, and not gvfs-backends. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541276: iso-scan should prefer the ISO image for the release in /etc/default-release
Package: iso-scan Severity: normal I am trying to put together a USB stick with both lenny and squeeze installers on it. However, iso-scan always finds the lenny ISO only. If more than one ISO is found, iso-scan should prefer the one that matches /etc/default-release in the initrd. Alternatively, can the ability to pre-seed the ISO image path be added? Thank you. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539646: [Pkg-xfce-devel] Bug#539646: xfce4-terminal: background image no longer works
On 08/03/09 03:40, Yves-Alexis Perez wrote: It seems to work fine here. What picture are you trying to set? With which options? All pictures I have tried (jpg, gif, pnm, bmp, png) do not work. Tiled, Centered, Scaled and Stretched all do not work. Please let me know what else I can do to help debug this. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539646: xfce4-terminal: background image no longer works
Package: xfce4-terminal Version: 0.4.0-1 Severity: normal Background images no longer work - transparency is always in effect. Transparency options work, as do solid colour backgrounds. Just background images seem to be broken. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages xfce4-terminal depends on: ii exo-utils0.3.101-2 Utility files for libexo ii libatk1.0-0 1.26.0-1The ATK accessibility toolkit ii libc62.9-12 GNU C Library: Shared libraries ii libdbus-1-3 1.2.16-2simple interprocess messaging syst ii libdbus-glib-1-2 0.80-4 simple interprocess messaging syst ii libexo-0.3-0 0.3.101-2 Library with extensions for Xfce ii libglib2.0-0 2.20.1-2The GLib library of C routines ii libgtk2.0-0 2.16.1-2The GTK+ graphical user interface ii libpango1.0-01.24.0-3+b1 Layout and rendering of internatio ii libvte9 1:0.20.5-1 Terminal emulator widget for GTK+ ii libx11-6 2:1.2.2-1 X11 client-side library ii libxfce4util44.6.1-1 Utility functions library for Xfce Versions of packages xfce4-terminal recommends: ii dbus-x11 1.2.16-2 simple interprocess messaging syst xfce4-terminal 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#465109: updated patch
Attached is an updated patch that works with amd64. I just changed the
xpm icon buffer to an array of unsigned long (instead of CARD32). I'm
sure that is not the correct approach, but it seems to work just fine.
--
Scott Barker sc...@mostlylinux.ca
Linux Consultant http://www.mostlylinux.ca/scott
diff -urbBw wmctrl-1.07/Makefile.am wmctrl-1.07.mine/Makefile.am
--- wmctrl-1.07/Makefile.am 2005-01-03 11:48:35.0 -0700
+++ wmctrl-1.07.mine/Makefile.am2008-02-10 10:43:28.0 -0700
@@ -1,7 +1,7 @@
AM_CFLAGS = -Wall
AM_CPPFLAGS = @X_CFLAGS@ @GLIB_CFLAGS@
-LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu @X_EXTRA_LIBS@ @GLIB_LIBS@
+LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu -lXpm @X_EXTRA_LIBS@ @GLIB_LIBS@
bin_PROGRAMS = wmctrl
wmctrl_SOURCES = main.c
diff -urbBw wmctrl-1.07/Makefile.in wmctrl-1.07.mine/Makefile.in
--- wmctrl-1.07/Makefile.in 2005-01-28 20:33:05.0 -0700
+++ wmctrl-1.07.mine/Makefile.in2008-02-10 10:43:29.0 -0700
@@ -115,7 +115,7 @@
AM_CFLAGS = -Wall
AM_CPPFLAGS = @X_CFLAGS@ @GLIB_CFLAGS@
-LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu @X_EXTRA_LIBS@ @GLIB_LIBS@
+LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu -lXpm @X_EXTRA_LIBS@ @GLIB_LIBS@
bin_PROGRAMS = wmctrl
wmctrl_SOURCES = main.c
diff -urbBw wmctrl-1.07/debian/changelog wmctrl-1.07.mine/debian/changelog
--- wmctrl-1.07/debian/changelog2008-02-10 11:19:54.0 -0700
+++ wmctrl-1.07.mine/debian/changelog 2008-02-10 11:17:49.0 -0700
@@ -1,3 +1,9 @@
+wmctrl (1.07-6local1) unstable; urgency=low
+
+ * Add ability to change application icons.
+
+ -- Scott Barker sc...@mostlylinux.ca Sun, 10 Feb 2008 11:17:26 -0700
+
wmctrl (1.07-6) unstable; urgency=low
* Reverted CARD32 patch, which was broken on amd64; use fix from Chris
diff -urbBw wmctrl-1.07/debian/control wmctrl-1.07.mine/debian/control
--- wmctrl-1.07/debian/control 2008-02-10 11:19:54.0 -0700
+++ wmctrl-1.07.mine/debian/control 2008-02-10 11:19:42.0 -0700
@@ -2,7 +2,7 @@
Section: x11
Priority: optional
Maintainer: Decklin Foster deck...@red-bean.com
-Build-Depends: debhelper (= 4.0.0), x11proto-core-dev, libx11-dev,
libxmu-dev, libglib2.0-dev (= 2.4.0)
+Build-Depends: debhelper (= 4.0.0), x11proto-core-dev, libx11-dev,
libxmu-dev, libxpm-dev, libglib2.0-dev (= 2.4.0)
Standards-Version: 3.6.2
Package: wmctrl
diff -urbBw wmctrl-1.07/main.c wmctrl-1.07.mine/main.c
--- wmctrl-1.07/main.c 2008-02-10 11:19:54.0 -0700
+++ wmctrl-1.07.mine/main.c 2008-02-10 11:08:05.0 -0700
@@ -34,6 +34,8 @@
#include X11/Xatom.h
#include X11/cursorfont.h
#include X11/Xmu/WinUtil.h
+#include X11/xpm.h
+#include X11/Xmd.h
#include glib.h
#define _NET_WM_STATE_REMOVE0/* remove/unset property */
@@ -64,6 +66,7 @@
argument and list of possible states is given
below.\n \
-r WIN -N STRSet the name (long title) of the window.\n \
-r WIN -I STRSet the icon name (short title) of the window.\n \
+ -r WIN -M PATH Set the mini-icon of the window to the xpm bitmap in
PATH.\n \
-r WIN -T STRSet both the name and the icon name of the window.\n \
-k (on|off) Activate or deactivate window manager's\n \
\showing the desktop\ mode. Many window managers\n \
@@ -264,7 +267,7 @@
}
}
-while ((opt = getopt(argc, argv,
FGVvhlupidmxa:r:s:c:t:w:k:o:n:g:e:b:N:I:T:R:)) != -1) {
+while ((opt = getopt(argc, argv,
FGVvhlupidmxa:r:s:c:t:w:k:o:n:g:e:b:N:I:T:R:M:)) != -1) {
missing_option = 0;
switch (opt) {
case 'F':
@@ -296,7 +299,7 @@
case 'r':
options.param_window = optarg;
break;
-case 't': case 'e': case 'b': case 'N': case 'I': case 'T':
+case 't': case 'e': case 'b': case 'N': case 'I': case 'T': case
'M':
options.param = optarg;
action = opt;
break;
@@ -356,7 +359,7 @@
ret = wm_info(disp);
break;
case 'a': case 'c': case 'R':
-case 't': case 'e': case 'b': case 'N': case 'I': case 'T':
+case 't': case 'e': case 'b': case 'N': case 'I': case 'T': case 'M':
if (! options.param_window) {
fputs(No window was specified.\n, stderr);
return EXIT_FAILURE;
@@ -677,6 +680,64 @@
}/*}}}*/
+void window_set_mini_icon (Display *disp, Window win, /* {{{ */
+char *path, char mode) {
+XpmImage xpmImage;
+XpmInfo xpmInfo;
+Colormap colormap;
+CARD32 *xpmColors;
+XColor xc;
+char *c;
+unsigned long *iconBuffer;
+int iconBufferSize;
+int i;
+
+if (XpmReadFileToXpmImage(path, xpmImage, xpmInfo) != 0) {
+ fputs(Invalid icon path.\n, stderr);
+ return EXIT_FAILURE;
+}
+
+colormap = DefaultColormap(disp, DefaultScreen(disp));
+xpmColors = (CARD32 *)g_malloc0
Bug#529613: gvfs-backends: gphoto2 backend blocks UMS/MSC access to devices
I have noticed that a NativePriority= line has to be added to the file as well. I am using NativePriority=3. I don't actually know what that means, but it keeps gvfs from emitting error messages. Since I am unsure of the mechanics of all of this, it's probably best if the bug gets forwarded upstream, and/or if the fix is co-ordinated with ubuntu bug 330383. On 05/20/09 10:26, Josselin Mouette wrote: Le mercredi 20 mai 2009 à 08:26 -0600, Scott Barker a écrit : Package: gvfs-backends Version: 1.2.2-2 Severity: normal As in Ubuntu bug 330383 (https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/330383), the gphoto2 backend is blocking mounting MTP capable devices as USB storage. The work-around in the Ubuntu bug fixes this in Debian as well: /usr/share/gvfs/remote-volume-monitors/gphoto2.monitor: [RemoteVolumeMonitor] Name=GProxyVolumeMonitorGPhoto2 DBusName=org.gtk.Private.GPhoto2VolumeMonitor #IsNative=false IsNative=true I imagine that this would then break MTP access to cameras, but cannot confirm. Could you please get upstream’s recommendations then? I’m not against including this patch, but only if it doesn’t break more than what it fixes. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529613: gvfs-backends: gphoto2 backend blocks UMS/MSC access to devices
Package: gvfs-backends Version: 1.2.2-2 Severity: normal As in Ubuntu bug 330383 (https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/330383), the gphoto2 backend is blocking mounting MTP capable devices as USB storage. The work-around in the Ubuntu bug fixes this in Debian as well: /usr/share/gvfs/remote-volume-monitors/gphoto2.monitor: [RemoteVolumeMonitor] Name=GProxyVolumeMonitorGPhoto2 DBusName=org.gtk.Private.GPhoto2VolumeMonitor #IsNative=false IsNative=true I imagine that this would then break MTP access to cameras, but cannot confirm. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages gvfs-backends depends on: ii gvfs 1.2.2-2 userspace virtual filesystem - ser ii libarchive1 2.6.2-1 Single library to read/write tar, ii libavahi-cli 0.6.25-1Avahi client library ii libavahi-com 0.6.25-1Avahi common library ii libavahi-gli 0.6.25-1Avahi glib integration library ii libc62.9-4 GNU C Library: Shared libraries ii libcdio-cdda 0.78.2+dfsg1-3 library to read and control digita ii libcdio-para 0.78.2+dfsg1-3 library to read digital audio CDs ii libcdio7 0.78.2+dfsg1-3 library to read and control CD-ROM ii libdbus-1-3 1.2.12-1simple interprocess messaging syst ii libgconf2-4 2.26.0-1GNOME configuration database syste ii libglib2.0-0 2.20.0-2The GLib library of C routines ii libgnome-key 2.26.0-4GNOME keyring services library ii libgphoto2-2 2.4.5-1 gphoto2 digital camera library ii libgphoto2-p 2.4.5-1 gphoto2 digital camera port librar ii libhal1 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share ii libsmbclient 2:3.3.4-1 shared library for communication w ii libsoup-gnom 2.26.1-1an HTTP library implementation in ii libsoup2.4-1 2.26.1-1an HTTP library implementation in ii libxml2 2.7.3.dfsg-1GNOME XML library gvfs-backends recommends no packages. gvfs-backends 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#444182: blacklisting modules
I don't know why there is no over-ride mechanism in the kernel or kernel modules, but doesn't blacklisting present an option? For example, I could easily blacklist the piix module, which my system does not require, but that still won't work unless the ata_piix module is compiled intact without the debian patch. Or maybe udev is supposed to be able to handle this? In any event, it seems to me that all solutions ultimate require a fully-functional ata_piix module. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444182: linux-image-2.6.29-1-686: please include a kernel build without the drivers-ata-ata_piix-postpone-pata.patch patch
Package: linux-image-2.6.29-1-686 Version: 2.6.29-3 Severity: normal As the drivers-ata-ata_piix-postpone-pata.patch removes the ability to hot-swap a CD-ROM from a laptop media bay for several chipsets, please consider building a flavour of the linux kernel that does not include that patch, so that those of us with this problem can make the choice to install a functional kernel, while not breaking operation for other users. Or, perhaps create a package with only a functional ata_piix module that then creates a diversion for those of us that wish it. -- Package-specific info: ** Version: Linux version 2.6.29-1-686 (Debian 2.6.29-3) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-3) ) #1 SMP Fri May 1 16:55:14 MDT 2009 ** Command line: root=/dev/sda2 ro ** Not tainted ** Kernel log: [ 131.158904] tg3 :09:00.0: PME# disabled [ 131.159061] tg3 :09:00.0: irq 29 for MSI/MSI-X [ 131.220093] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 131.676985] iwlagn :0c:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 131.677170] iwlagn :0c:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106) [ 131.677349] iwlagn :0c:00.0: irq 30 for MSI/MSI-X [ 131.677466] iwlagn :0c:00.0: firmware: requesting iwlwifi-4965-2.ucode [ 131.722237] iwlagn loaded firmware version 228.57.2.23 [ 131.928281] Registered led device: iwl-phy0:radio [ 131.928322] Registered led device: iwl-phy0:assoc [ 131.928363] Registered led device: iwl-phy0:RX [ 131.928397] Registered led device: iwl-phy0:TX [ 131.975445] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 132.797707] tg3: eth0: Link is up at 100 Mbps, full duplex. [ 132.797716] tg3: eth0: Flow control is on for TX and on for RX. [ 132.798178] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 134.317998] Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008) [ 134.318009] bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. [ 134.405547] tg3 :09:00.0: PME# enabled [ 134.422824] bonding: bond0: doing slave updates when interface is down. [ 134.422835] bonding: bond0: Adding slave eth0. [ 134.422842] bonding bond0: master_dev is not up in bond_enslave [ 134.432279] tg3 :09:00.0: PME# disabled [ 134.452311] tg3 :09:00.0: irq 29 for MSI/MSI-X [ 134.513330] bonding: bond0: enslaving eth0 as an active interface with an up link. [ 134.607904] iwlagn :0c:00.0: PCI INT A disabled [ 134.615728] bonding: bond0: doing slave updates when interface is down. [ 134.615739] bonding: bond0: Adding slave wlan0. [ 134.615746] bonding bond0: master_dev is not up in bond_enslave [ 134.629235] iwlagn :0c:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 134.629381] iwlagn :0c:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106) [ 134.629555] iwlagn :0c:00.0: irq 30 for MSI/MSI-X [ 134.831809] Registered led device: iwl-phy0:radio [ 134.831851] Registered led device: iwl-phy0:assoc [ 134.831885] Registered led device: iwl-phy0:RX [ 134.831922] Registered led device: iwl-phy0:TX [ 134.868001] bonding: bond0: Warning: failed to get speed and duplex from wlan0, assumed to be 100Mb/sec and Full. [ 134.868038] bonding: bond0: enslaving wlan0 as an active interface with an up link. [ 134.868540] bonding: bond0: setting mode to active-backup (1). [ 134.868731] bonding: bond0: Setting MII monitoring interval to 100. [ 134.872326] bonding: bond0: Setting eth0 as primary slave. [ 135.181128] tun: Universal TUN/TAP device driver, 1.6 [ 135.181136] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 135.475624] Bridge firewalling registered [ 135.502099] device bond0 entered promiscuous mode [ 135.508513] bonding: bond0: link status definitely down for interface eth0, disabling it [ 135.508522] bonding: bond0: link status definitely down for interface wlan0, disabling it [ 135.518072] device tap0 entered promiscuous mode [ 135.524841] br0: port 2(tap0) entering learning state [ 136.070066] tg3: eth0: Link is up at 100 Mbps, full duplex. [ 136.070074] tg3: eth0: Flow control is on for TX and on for RX. [ 136.108167] bonding: bond0: link status definitely up for interface eth0. [ 136.108178] bonding: bond0: making interface eth0 the new active one. [ 136.108184] device eth0 entered promiscuous mode [ 136.108267] bonding: bond0: first active interface up! [ 136.320612] br0: port 1(bond0) entering learning state [ 138.139846] wlan0: authenticate with AP 00:1c:10:41:cd:9e [ 138.142005] wlan0: authenticated [ 138.142014] wlan0: associate with AP 00:1c:10:41:cd:9e [ 138.145821] wlan0: RX AssocResp from 00:1c:10:41:cd:9e (capab=0x431 status=0 aid=1) [ 138.145828] wlan0: associated [ 138.208173] bonding: bond0: link status definitely up for interface wlan0. [ 145.556152] br0: no IPv6 routers present [ 145.592142] bond0: no IPv6
Bug#525945: [Pkg-xfce-devel] Bug#525945: thunar fails to remount removable media when running as daemon
I did have thunar-volman installed, and the same thing was happening. I removed it to verify it wasn't thunar-volman causing the issue. I have consolekit and policykit installed, and spent several hours debugging that new level of complexity as well. I used to use startxfce4, and had to switch to using startx with 'exec ck-launch-session startxfce4' in $HOME/.xsession to make mounting (and suspend/hibernate) work at all in the new model. I have verified that my console session is correct (via ck-list-sessions) and that I have the correct authorizations as well (via polkit-auth). The only way I have been able to reproduce the error consistently is by running thunar as a daemon, mounting a USB device (by clicking on it in thunar), unmounting it (by right-clicking on it in thunar), unplugging it, plugging it back in, and trying to mount it again (by clicking on it in thunar). On 04/27/09 23:58, Yves-Alexis Perez wrote: On lun, 2009-04-27 at 20:40 -0600, Scott Barker wrote: When thunar is running as a daemon, a removable device that is unmounted, unplugged, and plugged back in cannot be re-mounted. The error is org.freedsekop.hal.storage.mount-removable no -- (action, result). If the thunar daemon is terminated, and thunar is started manually from a terminal or from the xfce4 menu instead, this error does not occur. Hmhm, strange. I see you don't use thunar-volman (this is fine). Hal is installed, but are consolekit and policykit installed too? Do you start Xfce using a display manager, startx, startxfce4, something like that? Cheers, -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: [Pkg-xfce-devel] Bug#525945: Bug#525945: thunar fails to remount removable media when running as daemon
On 04/28/09 05:48, Yves-Alexis Perez wrote:
It happens with all the usb devices you tried?
Is there something in /var/log/syslog during the various mount/umounts?
Could you try lshal -m during those operations, too?
It happens with all usb thumbdrive-type devices (actual usb thumbdrives,
my Sony Reader and my Sony Walkman) and with external USB hard drives.
There is nothing in syslog except the normal output from the kernel
(dmesg), and there is nothing unusual in that output, and nothing
different from in the past when this problem did not occur prior to
upgrading from lenny to squeeze.
Attached are two logs from lshal -m, one with thunar run as a foreground
process, the other with it running as a daemon. There is no other output
to any other logs related to this problem.
The only other thing I have noticed during testing is that every time
the device is removed and re-inserted, a new [scsi_eh_X] process appears
in the process list, where 'X' is incremented each time. Similarly, in
the kernel output (dmesg), when the device is scanned, it gets a
different scsi device ID (as in 'sd XX:0:0:0: [sdb] ...', where XX
increments each time).
Perhaps thunar is somehow caching hardware state when running as a
daemon, and the change in scsi ID is not being picked up?
--
Scott Barker sc...@mostlylinux.ca
Linux Consultant http://www.mostlylinux.ca/scott
Start monitoring devicelist:
-
07:51:04.893: usb_device_1976_6025_091155002041A100 added
07:51:04.912: usb_device_1976_6025_091155002041A100_if0 added
07:51:04.942: usb_device_1976_6025_091155002041A100_usbraw added
07:51:09.882: usb_device_1976_6025_091155002041A100_if0_scsi_host added
07:51:09.885: usb_device_1976_6025_091155002041A100_if0_scsi_host_scsi_device_lun0 added
07:51:10.034: storage_serial__USB_2_0_091155002041A100_0_0 added
07:51:10.039: storage_serial__USB_2_0_091155002041A100_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
07:51:10.136: volume_uuid_0021_CB1F added
07:51:14.176: volume_uuid_0021_CB1F property volume.mount_point = '/media/DISK_IMG'
07:51:14.191: volume_uuid_0021_CB1F property volume.is_mounted = true
07:51:19.699: volume_uuid_0021_CB1F property volume.mount_point = ''
07:51:19.700: volume_uuid_0021_CB1F property volume.is_mounted = false
07:51:23.528: usb_device_1976_6025_091155002041A100_if0_scsi_host_scsi_device_lun0 removed
07:51:23.531: usb_device_1976_6025_091155002041A100_if0_scsi_host removed
07:51:23.532: volume_uuid_0021_CB1F removed
07:51:23.554: usb_device_1976_6025_091155002041A100_if0 removed
07:51:23.558: usb_device_1976_6025_091155002041A100_usbraw removed
07:51:23.558: usb_device_1976_6025_091155002041A100 removed
07:51:23.558: storage_serial__USB_2_0_091155002041A100_0_0 removed
07:51:26.909: usb_device_1976_6025_091155002041A100 added
07:51:26.918: usb_device_1976_6025_091155002041A100_if0 added
07:51:26.944: usb_device_1976_6025_091155002041A100_usbraw added
07:51:31.905: usb_device_1976_6025_091155002041A100_if0_scsi_host added
07:51:31.907: usb_device_1976_6025_091155002041A100_if0_scsi_host_scsi_device_lun0 added
07:51:32.030: storage_serial__USB_2_0_091155002041A100_0_0 added
07:51:32.034: storage_serial__USB_2_0_091155002041A100_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
07:51:32.163: volume_uuid_0021_CB1F added
07:51:33.518: volume_uuid_0021_CB1F property volume.mount_point = '/media/DISK_IMG'
07:51:33.519: volume_uuid_0021_CB1F property volume.is_mounted = true
07:51:35.139: volume_uuid_0021_CB1F property volume.mount_point = ''
07:51:35.156: volume_uuid_0021_CB1F property volume.is_mounted = false
07:51:37.610: usb_device_1976_6025_091155002041A100_if0_scsi_host_scsi_device_lun0 removed
07:51:37.612: usb_device_1976_6025_091155002041A100_if0_scsi_host removed
07:51:37.613: volume_uuid_0021_CB1F removed
07:51:37.631: usb_device_1976_6025_091155002041A100_if0 removed
07:51:37.631: usb_device_1976_6025_091155002041A100_usbraw removed
07:51:37.633: usb_device_1976_6025_091155002041A100 removed
07:51:37.635: storage_serial__USB_2_0_091155002041A100_0_0 removed
Start monitoring devicelist:
-
07:52:51.142: usb_device_1976_6025_091155002041A100 added
07:52:51.150: usb_device_1976_6025_091155002041A100_if0 added
07:52:51.173: usb_device_1976_6025_091155002041A100_usbraw added
07:52:56.139: usb_device_1976_6025_091155002041A100_if0_scsi_host added
07:52:56.141: usb_device_1976_6025_091155002041A100_if0_scsi_host_scsi_device_lun0 added
07:52:56.291: storage_serial__USB_2_0_091155002041A100_0_0 added
07:52:56.301: storage_serial__USB_2_0_091155002041A100_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
07:52:56.384: volume_uuid_0021_CB1F added
07:53:10.288: usb_device_1976_6025_091155002041A100_if0_scsi_host_scsi_device_lun0 removed
07:53:10.291
Bug#525945: [Pkg-xfce-devel] Bug#525945: Bug#525945: Bug#525945: thunar fails to remount removable media when running as daemon
On 04/28/09 08:27, Yves-Alexis Perez wrote: When running as a foreground process, you didn't quit between the first connect and the second one, did you? In both cases (daemon and foreground), I left the thunar window open as I unmounted, removed, reconnected and tried to remount the device. It looks to me like a hal problem (device correctly appears in the kernel logs, but not in hal). Sorry - I should have noted that in the case of running thunar as a daemon, it wouldn't even mount the device the first time I reconnected it, so the log I sent in that case does not show repeated insertion and removal. It seems that once a device has been inserted, mounted, and unmounted, thunar as a daemon can no longer mount it anymore, while thunar as a foreground process can. Doing lshal -m while thunar is running as a daemon, and inserting and removing the device repeatedly, hal is noticing it every time, while thunar continues to not mount the device. I don't think thunar caches anything. It relies on hal events to notice that a removable device appeared. What's weird is that thunar influences hal, which seems really very weird. I just tried something different - I launched thunar as a daemon from a terminal window, and then everything worked fine. So, the difference seems to be launching thunar as a daemon via the window manager. I've been launching it by going to the menu and choosing Settings - File Manager, which launches /usr/bin/Thunar --daemon if it is not already running. Of course, I've also been launching thunar from the window manager menu as well (directly in the top-level menu as File Manager), so I'm not sure what is different about how thunar is invoked between those two menus. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: Info received ([Pkg-xfce-devel] Bug#525945: Bug#525945: Bug#525945: thunar fails to remount removable media when running as daemon)
Following up on my last entry, it seems that the problem must exist in the way thunar is started when the thunar-settings script spawns thunar as a daemon. The problem always occurs when thunar is launched that way, and never occurs when run directly as a daemon, nor when run as a foreground process. Something to do with dbus-send or the way it invokes thunar? -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: Info received (Bug#525945: Info received ([Pkg-xfce-devel] Bug#525945: Bug#525945: Bug#525945: thunar fails to remount removable media when running as daemon))
I traced through the scripts in /etc/X11/Xsession, and found that dbus-launch is pre-pended to $STARTUP after $STARTUP is set to $HOME/.xsession, so my method of invoking xfce4 from the console turns into: dbus-launch --exit-with-session $HOME/.xsession $HOME/.xsession contains: exec ck-launch-session startxfce4 So, my entire session, *except* dbus is in the ck-launch-session. I confirmed this by creating a script to run polkit-auth and direct the output to a file. When this script is run from thunar launched as a daemon by dbus, the necessary authorization are missing. I am going to purge libpam-ck-connector so that the stock squeeze Xsession scripts can use ck-launch-session as designed, and see what happens then. On 04/28/09 08:54, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 525...@bugs.debian.org, as before. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: Info received (Bug#525945: Info received (Bug#525945: Info received ([Pkg-xfce-devel] Bug#525945: Bug#525945: Bug#525945: thunar fails to remount removable media when running as daemo
Purging libpam-ck-connector and reducing my .xsession to just 'exec startxfce4' has fixed the problem. Feel free to close this bug report. I will file a wishlist item for libpam-ck-connector for a warning to be added to the package description that users who start X from a text shell instead of a graphical manager should not install libpam-ck-connector unless they really have a good reason to do so. I will also file a wishlist item against xfce4-utils that the documentation on whether to use 'startx' or 'startxfce4' should be clarified. Thank you for the assistance, and sorry to trouble you. On 04/28/09 09:09, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 525...@bugs.debian.org, as before. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526006: please add a warning to the libpam-ck-connector description for users of startx
Package: libpam-ck-connector Severity: wishlist Users who start their X session using startx from a text terminal will have a lengthy debugging session facing them after their next full logout/logon if they install libpam-ck-connector. All sorts of things will not work correctly, including suspend/hibernate, mounting of removable media, access to pulse-audio, etc. This is due to the new consolekit/policykit method of doing things, and the fact that libpam-ck-connector sets XDG_SESSION_COOKIE in the text logon, preventing the Xsession scripts from correctly adding ck-launch-session in the $STARTUP command (see bug # 520720 at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520720 for an as-yet inconclusive discussion on this matter) There are various fixes available for this, but they are either non-obvious, introduce security holes, or involve customizations that will prevent the end user from benefitting from future improvements to the debian X startup procedure (due to having xinitrc, xsessionrc and/or xsession files in the home directory). The simplest solution to this problem is to purge libpam-ck-connector. After doing so, I have had no more issues related to consolekit/policykit. I would like to suggest that a warning be added to the description for libpam-ck-connector, for example: If you use startx from a text terminal to start your X session, you probably should not install this package, as it is likely to prevent you from accessing most dbus and hal related functionality in your X session, such as suspend/hibernate, mounting of removable media, access to pulseaudio devices, etc. In addition, please change the control file for the consolekit package to only Suggest libpam-ck-connector, instead of Recommending it, so that it is not installed by default. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-ck-connector depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii libck-connector0 0.3.0-2ConsoleKit libraries ii libdbus-1-3 1.2.12-1 simple interprocess messaging syst ii libpam-runtime1.0.1-9Runtime support for the PAM librar ii libpam0g 1.0.1-9Pluggable Authentication Modules l libpam-ck-connector recommends no packages. libpam-ck-connector suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: xfce4-utils: sessions started with startxfce4 lose hal/dbus functionality
Package: xfce4-utils Version: 4.6.0-2 Severity: wishlist With the new consolekit/policykit method of doing things, starting an xfce4 session using startxfce4 from a text terminal will cause the user to lose hal/dbus functionality such as suspend/hibernate, mounting of removable media, access to pulseaudio devices, etc. The startx script in the xinit package, however, works fine (provided the user does not have libpam-ck-connector installed, see bug # 526006 at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526006) since it sources /etc/X11/Xsession.d/90consolekit, which handles launching the X session using ck-launch-session as required. However, I have noticed some differences between starting xfce4 with startx vs. starting it with startxfce4, most notable of which is that the font chosen in the User Interface Preferences seems to be ignored. I assume this is the result (directly or indirectly) of the fact that startxfce4 sets assorted shell variables via /etc/xdg/xfce4/xinitrc that startx does not. The cleanest way around this issue that I could find is to start the X session with: startx /usr/bin/startxfce4 Until/unless startxfce4 is adapted to use ck-launch-session, perhaps this could be documented somewhere obvious? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages xfce4-utils depends on: ii exo-utils0.3.100-2 Utility files for libexo ii gnome-terminal [x-terminal-e 2.24.3-3The GNOME 2 terminal emulator appl ii libc62.9-4 GNU C Library: Shared libraries ii libglib2.0-0 2.20.0-2The GLib library of C routines ii libgtk2.0-0 2.14.7-5The GTK+ graphical user interface ii libxfce4util44.6.0-2 Utility functions library for Xfce ii libxfcegui4-44.6.0-2 Basic GUI C functions for Xfce4 ii libxml-parser-perl 2.36-1.1+b1 Perl module for parsing XML files ii x11-xserver-utils7.4+2 X server utilities ii xfce4-terminal [x-terminal-e 0.2.8-5 Xfce terminal emulator ii xinit1.1.1-1 X server initialisation tool ii xterm [x-terminal-emulator] 242-1 X terminal emulator Versions of packages xfce4-utils recommends: ii dbus-x11 1.2.12-1 simple interprocess messaging syst ii thunar1.0.0-2File Manager for Xfce ii xdg-user-dirs 0.10-1 tool to manage well known user dir ii xfce4-panel 4.4.2-6The Xfce4 desktop environment pane ii xfwm4 4.6.0-2window manager of the Xfce project ii xinput1.3.0-1Runtime configuration and test of ii xscreensaver 5.05-3 Automatic screensaver for X Versions of packages xfce4-utils suggests: ii xfce4-session 4.4.2-6Xfce4 Session Manager -- 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#525945: [Pkg-xfce-devel] Bug#525945: Info received (Bug#525945: Info received (Bug#525945: Info received ( Bug#525945: Bug#525945: Bug#525945: thunar fails to remount removable media when running
On 04/28/09 10:15, Yves-Alexis Perez wrote: I'm not sure this is a good idea. I'm investigating shutdown bugs for another user, and we just managed to find that, if you don't use gdm, then you _need_ libpam-ck-connector so you have the correct rights, and can shutdown. I can shutdown and hibernate just fine without libpam-ck-connector, from my graphical session. I'm now starting xfce with: startx /usr/bin/startxfce4 Starting with just 'startxfce4' from the command prompt won't work, though. Perhaps something similar has to be done for gnome and KDE? Also, I am not trying to do any dbus/hal stuff from my initial text terminal logon, so I can't say what would happen there without libpam-ck-connector. I don't really know what happens to you, but it seems that the “first” Thunar is outside of consolekit, somethingg like that? That seems to be it exactly. If thunar is started as a daemon using the settings menu, it is invoked with the thunar-settings script, which uses dbus to launch thunar, and the way I was invoking xfce4 before was not including dbus in the ck-launch-session command. Now that I am using startx /usr/bin/startxfce4 to start xfce4, everything is working fine, including when thunar gets launched via dbus in thunar-settings. I think (but I'm not yet really sure) that, if you're not using gdm (and kdm, maybe), then you need to have libpam-ck-connector installed, and you should start xfce using startxfce4 or startxfce4, but anyway beware of that consolekit stuff. I don't really know what you are trying to do with your .xsession and the ck-launch-session stuff. All I did was step through what happens in the /etc/X11/Xsession.d/* scripts, to determine what the final xinit client command would be. It matters what order things are invoked in. My original method (using my .xsession file in my home directory) resulted in the xinit client being: ssh-agent dbus-launch ck-session-launch --exit-with-session $HOME/.xsession Where my .xsession file then exec'd startxfce4. This resulted in everything except dbus being launched within ck-session-launch. Thus thunar being launched via dbus in thunar-settings did not get the right policykit authorizations, which caused my initial problem. Removing my .xsession file and starting instead with 'startx /usr/bin/startxfce4' results in the xinit client being: ssh-agent ck-session-launch dbus-launch --exit-with-session /usr/bin/startxfce4 As you can see, dbus is now included in the ck-session-launch. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: [Pkg-xfce-devel] Bug#525945: Info received (Bug#525945: Info received (Bug#525945: Info received ( Bug#525945: Bug#525945: Bug#525945: thunar fails to remount removable media when running
Sorry, I thought I had deleted my .xsession file in some of my earlier testing, but apparently I had not. Starting xfce4 with: startx /usr/bin/startxfce4 actually does not work. However, putting this into $HOME/.xsession: exec /usr/bin/startxfce4 and then starting xfce4 with just: startx does work. My apologies for my earlier incorrect statements. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: xfce4-utils: sessions started with startxfce4 lose hal/dbus functionality
Sorry, I thought I had deleted my .xsession file in some of my earlier testing, but apparently I had not. Starting xfce4 with: startx /usr/bin/startxfce4 actually does not work. However, putting this into $HOME/.xsession: exec /usr/bin/startxfce4 and then starting xfce4 with just: startx does work. My apologies for my earlier incorrect statements. I still feel that this should be documented somewhere. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: [Pkg-xfce-devel] Bug#526009: xfce4-utils: sessions started with startxfce4 lose hal/dbus functionality
On 04/28/09 13:27, Yves-Alexis Perez wrote: It'd be nice to have a single summary point for those hal related issues, please. It's already difficult to follow on the two bugs (Thunar and xfce4-session) and the mailing list, opening yet another one will add more complexity. Please pick one bug where we can discuss this and stay on it? No problem, I understand. Let me know which bug you prefer the ongoing discussion to occur in, and feel free to close the others. startxfce4 is “the xfce way” to start Xfce. startx is “the debian way” to start a desktop environment. That's what I thought, thanks for confirming. Yes. I thought it was already documented, but not really. So we should add this to the README.Debian. Basically, we'd rather not divert from upstream on the startup script, but we still want to have the Debian stuff properly set. So startxfce4 should be used by the Debian stuff, meaning: - display managers (which already use the Debian infrastructure, /etc/X11/Xsession.d) should call startxfce4 - users should either * run startx /usr/bin/startxfce4 * put startxfce4 in their .xsession and use only startx (not sure about this one). I guess this should be correctly indicated in the README.Debian of xfce4-utils. That would be great. Although, 'startx /usr/bin/startxfce4' won't currently work, as it bypasses the Xsession.d/* scripts, and so ck-launch-session won't be called. To force startxfce4 to be used, perhaps update-alternatives should point x-session-manager to startxfce4 instead of xfce4-session? That would also eliminate the need for users to put startxfce4 in their .xsession file. I think I will test that right now. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: [Pkg-xfce-devel] Bug#526009: xfce4-utils: sessions started with startxfce4 lose hal/dbus functionality
On 04/28/09 13:39, Yves-Alexis Perez wrote: Hmhm, I need to do some tests, but now, it shouldn't. startx should definitely run stuff in /etc/X11/Xsession.d/ and did so last time I tried. Looking at the startx script, it appears that if you do not provide a client on the command line, startx will invoke 'xinit $HOME/.xinitrc' or if there is no $HOME/.xinitrc file, then it will invoke 'xinit /etc/X11/xinit/xinitrc'. If you do provide a client on the command line (for example, 'startx /usr/bin/startxfce4'), then startx will invoke 'xinit $client' (eg. xinit /usr/bin/startxfce4), bypassing /etc/X11/xinit/xinitrc completely, meaning /etc/X11/Xsession will not be run. Of course, if the user has their own .xinitrc file, /etc/X11/Xsession may also be bypassed, but I'm mostly concerned about the out of the box experience for users, since I prefer to do all of my customizations in a way that can move forward with improvements made to the Debian system by all of the great maintainers that put the effort in, without having to rework my customizations along the way. Well, the thing is, startxfce4 is _not_ a session manager, so that would defeat the x-session-manager alternative purpose, I think. Not sure if “just a session manager” is useful by itself, but… That is true. I guess that ultimately the problem is that /bin/login can't set up a consolekit session for the tty created by xinit, and the X folks don't seem to have added consolekit integration to xinit (in spite of this comment I came across: https://bugzilla.redhat.com/show_bug.cgi?id=229172#c10). -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: Attempt to summarize
On 04/28/09 14:29, Yves-Alexis Perez wrote: From a display manager, /etc/X11/Xsession.d/90consolekit will always be run, and position correctly the ck stuff. This is the simple case :) From the console: - either libpam-ck-connector is installed - either it's not If it's installed, consolekit stuff will be positionned at login, and should be propagated to any desktop run from there. And that's why 90consolekit should _not_ be run, and why the pam module sets a variable to be sure. That makes sense, except that the consolekit stuff appears to not be propagated. Perhaps the true cause of these problems is a bug in consolekit? Although from my readings on consolekit, it is not intended to propagate sessions across changing ttys (as in text login tty - xinit tty). If it's not installed, the console login won't have consolekit stuff, and if we want a complete desktop experience, we _need_ to use 90consolekit, and so run stuff in /etc/X11/Xsession.d (and still run startxfce4). The only way to do that (that I know) is to put: exec startxfce4 in .xsession, and run: startx (no .xinitrc, no startx /usr/bin/startxfce4 or anything else). There are other ways (* see below), but that is by far the easiest and cleanest at the moment. So, if we document that in README.Debian, everything should work fine for most user, wether they use a DM (case 1) or not, and have libpam-ck-connector installed (2a) or not (2b). But we have a problem with 2a because in some cases which you exposed in I don't remember which bug, that the ck session on console wasn't propagated to the desktop session. Could you give (on that bug) a summary of how to reproduce this? Reproducing it appears to be straight-forward: 0) remove .xsession, .xinitrc, and other similar X customization files 1) install libpam-ck-connector 2) kill all /sbin/login processes (so login reloads the pam stack) 3) log out and log back in 4) run polkit-auth (all necessary permissions will be present) 5) run startxfce4 6) run polkit-auth from a terminal (most permissions are now missing) Alternatively: 0) - 4) same as above 5) ensure /etc/alternatives/x-session-manager links to xfce4-session 6) run startx 7) run polkit-auth from a terminal, and most permissions are missing I will put this information in the thunar bug as well. * Other ways I have found that work: - symlink /etc/alternatives/x-session-manager to /usr/bin/startxfce4 (but this defeats the true purpose of alternatives in this case) - custom $HOME/.config/xfce4/.xinitrc or $HOME/.xinitrc with ck-launch-session in an appropriate place (but this prevents the user from benefitting from future improvements to the Debian X startup process in /etc) I'm sure there are other ways, but they will probably all be messy and non-Debian-standard. I did have another thought - if there is stuff that startxfce4 does that xfce4 requires, maybe that stuff, or a call to startxfce4 itself, should be integrated somehow into /etc/X11/Xsession.d/*? Something like what is done in /etc/X11/Xsession.d/55gnome-session_gnomerc? Then the alternative just needs to be pointed to xfce4-session, and no .xsession in the home dir is required - seamless for the user. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: Summary for thunar stuff
I agree that, for this bug, nothing needs to be done. Thunar is behaving properly, provided that xfce is started correctly (that is, in a manner which sets up consolekit and policykit to behave properly). Thunar was just the unlucky program which triggered my investigation into startx/startxfce4/consolekit/policykit. On 04/28/09 14:44, Yves-Alexis Perez wrote: Ok, so, in the end, for this issue. Like xfce4-session, I don't think, in the end, we should Recommends: libpam-ck-connector. The rationale is that Thunar already Recommends: hal (and that may switch to a Depends soon), which Depends on consolekit, which Recommends libpam-ck-connector anyway. As per the summary on xfce4-utils bug, if we properly document the various ways to start Xfce, we shouldn't have any problem anymore. What do you think (just for stuff related to this bug)? Cheers, -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: [Pkg-xfce-devel] Bug#526009: Attempt to summarize
On 04/28/09 15:15, Yves-Alexis Perez wrote: On mar, 2009-04-28 at 14:56 -0600, Scott Barker wrote: On 04/28/09 14:29, Yves-Alexis Perez wrote: But we have a problem with 2a because in some cases which you exposed in I don't remember which bug, that the ck session on console wasn't propagated to the desktop session. Could you give (on that bug) a summary of how to reproduce this? Reproducing it appears to be straight-forward: [...] I will put this information in the thunar bug as well. Please don't. It's _really_ messy. Thunar needs a correctly setup consolekit, xfce4-session too. For most Xfce users this will be documented in xfce4-utils:README.Debian and/or xfce4:README.Debian. And this is the bug where we discuss it. Not the other ones, please. Right, sorry, I won't. I mis-interpreted your wording asking for a summary on how to reproduce as asking for it in the other bug report. Yeah, it's been quite some time since I first though of putting all startxfce4 stuff into /etc/X11/Xsession.d and only keep a stub. But I don't really want to divert too much from upstream and other distros. It could be as simple as: BASESTARTUP=`basename $STARTUP | cut -d\ -f1` if [ $BASESTARTUP = xfce4-session -o \ \( $BASESTARTUP = x-session-manager -a \ `readlink /etc/alternatives/x-session-manager` = \ /usr/bin/xfce4-session \) ]; then STARTUP=/usr/bin/startxfce4 fi However, this may be as undesirable as pointing x-session-manager at /usr/bin/startxfce4. Obviously, you and others can make the best decision in this regard. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526006: please add a warning to the libpam-ck-connector description for users of startx
Please see also bugs 525945 and 526009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525945 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526009 I still believe libpam-ck-connector should be made a suggests of consolekit, but Yves may disagree. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526009: [Pkg-xfce-devel] Bug#526009: Attempt to summarize
On 04/28/09 15:47, Yves-Alexis Perez wrote: Ok. I've tested and we have indeed propagation problems. I'm not sure how it's supposed to be handled, but I think it's a bug in consolekit. I don't exactly know how it should be done, but: - either the authentication propagates from console to X - either the 90consolekit shouldn't prevent ck-launch What do you think? I think someone who has more intimate knowledge of consolekit should be consulted to clarify the propagation issue. If, in fact, propagation does not occur, then it may be best to leave libpam-ck-connector uninstalled, unless there is some pressing reason it would be needed in a text terminal-only environment. However, I also found this method to fix the issue: - libpam-ck-connector can be installed or not, doesn't matter - don't use a $HOME/.xsession file - put the following in $HOME/.config/xfce4/xinitrc: #!/bin/sh exec ck-launch-session /etc/xdg/xfce4/xinitrc - chmod +x $HOME/.config/xfce4/xinitrc Now you can start xfce with 'startxfce4' instead of 'startx', and everything works fine, regardless of libpam-ck-connector. This method just over-rides the default exec at the very end of /usr/bin/startxfce4, inserting ck-launch-session before calling /etc/xdg/xfce/xinitrc. I'm sure that the upstream xfce developers will run across this consolekit problem soon (if they haven't already), and may patch /usr/bin/startxfce4 appropriately anyway. So, that makes two fairly simple methods which work fine (one for the 'debian way' and one for the 'xfce way'), but you and the other maintainers will need to determine which is best. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525945: thunar fails to remount removable media when running as daemon
Package: thunar Version: 1.0.0-2 Severity: normal When thunar is running as a daemon, a removable device that is unmounted, unplugged, and plugged back in cannot be re-mounted. The error is org.freedsekop.hal.storage.mount-removable no -- (action, result). If the thunar daemon is terminated, and thunar is started manually from a terminal or from the xfce4 menu instead, this error does not occur. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages thunar depends on: ii desktop-file-utils 0.15-2 Utilities for .desktop files ii exo-utils0.3.100-2 Utility files for libexo ii libatk1.0-0 1.24.0-2The ATK accessibility toolkit ii libc62.9-4 GNU C Library: Shared libraries ii libcairo21.8.6-2+b1 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.12-1simple interprocess messaging syst ii libdbus-glib-1-2 0.80-3 simple interprocess messaging syst ii libexo-0.3-0 0.3.100-2 Library with extensions for Xfce ii libfreetype6 2.3.9-4 FreeType 2 font engine, shared lib ii libglib2.0-0 2.20.0-2The GLib library of C routines ii libgtk2.0-0 2.14.7-5The GTK+ graphical user interface ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library ii libpango1.0-01.24.0-3+b1 Layout and rendering of internatio ii libsm6 2:1.1.0-2 X11 Session Management library ii libthunar-vfs-1-21.0.0-2 VFS abstraction used in thunar ii libx11-6 2:1.2.1-1 X11 client-side library ii libxfce4util44.6.0-2 Utility functions library for Xfce ii shared-mime-info 0.30-2 FreeDesktop.org shared MIME databa ii thunar-data 1.0.0-2 Provides thunar documentation, ico Versions of packages thunar recommends: ii dbus-x11 1.2.12-1simple interprocess messaging syst ii gamin0.1.10-1File and directory monitoring syst ii hal 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer pn thunar-volma none (no description available) ii xdg-user-dir 0.10-1 tool to manage well known user dir ii xfce4-panel 4.4.2-6 The Xfce4 desktop environment pane Versions of packages thunar suggests: pn thunar-archive-plugin none (no description available) ii thunar-media-tags-plugin 0.1.2-1Media tags plugin for Thunar file -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#442278: icedove: need symlink for xfce preferred applications
Package: icedove Version: 2.0.0.19-1 Severity: normal Without the symlink, one cannot set thunderbird (icedove) as the preferred application in xfce without setting up a custom command. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages icedove depends on: ii debianutils 3.0.1 Miscellaneous utilities specific t ii fontconfig 2.6.0-3 generic font configuration library ii libatk1.0-0 1.22.0-1The ATK accessibility toolkit ii libc62.9-4 GNU C Library: Shared libraries ii libcairo21.8.6-2+b1 The Cairo 2D vector graphics libra ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.9-4 FreeType 2 font engine, shared lib ii libgcc1 1:4.3.3-3 GCC support library ii libglib2.0-0 2.20.0-2The GLib library of C routines ii libgtk2.0-0 2.14.7-5The GTK+ graphical user interface ii libhunspell-1.2- 1.2.8-2 spell checker and morphological an ii libjpeg626b-14 The Independent JPEG Group's JPEG ii libnspr4-0d 4.7.1-4 NetScape Portable Runtime Library ii libnss3-1d 3.12.2.with.ckbi.1.73-1 Network Security Service libraries ii libpango1.0-01.22.4-2Layout and rendering of internatio ii libpng12-0 1.2.35-1PNG library - runtime ii libstdc++6 4.3.3-3 The GNU Standard C++ Library v3 ii libx11-6 2:1.2-1 X11 client-side library ii libxft2 2.1.13-3FreeType-based font drawing librar ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxrender1 1:0.9.4-2 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii psmisc 22.6-1 Utilities that use the proc filesy ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime icedove recommends no packages. Versions of packages icedove suggests: pn icedove-gnome-support none (no description available) pn latex-xft-fonts none (no description available) ii libthai0 0.1.9-4Thai language support library -- debconf information: icedove/browser: Debian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#489203: mencal does not account for daylight savings time
Package: mencal
Version: 2.3-7
Severity: normal
Tags: patch
mencal does not account for daylight savings time when calculating the
variable '$day' in the markdays() subroutine, resulting in fractional
values for '$day', which breaks mencal if the start date and current
date are in different daylight savings time states.
This may actually be due to changed behaviour in POSIX::mktime back in
2007, where mktime now sets isdst=-1 by default, instead of setting
isdst=0 by default.
The included patch fixes this problem simply by ensuring that '$day' is
an integer.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages mencal depends on:
ii perl 5.10.0-11 Larry Wall's Practical Extraction
mencal recommends no packages.
-- no debconf information
--- /usr/bin/mencal 2006-07-29 17:57:14.0 -0600
+++ mencal 2008-07-03 15:26:01.0 -0600
@@ -184,7 +184,7 @@
sub markdays {
my ($self, $begin, $end, $date, $length) = (shift, shift, shift, shift,
shift);
-my $day = ($date - $begin) / (24 * 3600) + 1;
+my $day = int(($date - $begin) / (24 * 3600) + 1);
my $limit = $date + $length;
$limit = $end if ($end $limit);
while ($date $limit) {
Bug#448206: #448206 update-manager: Does not integrate with apt-listchanges
If others report the problem fixed, I don't object to closing the bug. I no longer use update-manager because it did not use aptitude to perform updates, and aptitude seems to be the official package manager now. On 06/24/08 03:49, Thibaut Paumard wrote: Hi, you have reported this bug last year: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448206 Update-manager has been update since then. Given the answer received on Jan, 14th, I am tempted to close the bug now. Is the current behavior OK for you? Best regards, Thibaut. -- Scott Barker [EMAIL PROTECTED] Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481131: netapplet: please integrate changes from Joachim Nilsson
Package: netapplet
Version: 1.0.8-2local1
Severity: normal
Tags: patch
Joachim Nilsson has made some useful patches to netapplet available at
http://vmlinux.org/jocke/bzr/index.py/repositories
I have attached a diff including two of his patches; one fixes scanning
for access points, the other downs the interface before reassociating
with a new access point and upping the interface.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages netapplet depends on:
ii libart-2.0-2 2.3.20-1 Library of functions for 2D graphi
ii libatk1.0-01.22.0-1 The ATK accessibility toolkit
ii libbonobo2-0 2.22.0-1 Bonobo CORBA interfaces library
ii libbonoboui2-0 2.22.0-1 The Bonobo UI library
ii libc6 2.7-10GNU C Library: Shared libraries
ii libcairo2 1.6.4-1+b1The Cairo 2D vector graphics libra
ii libgconf2-42.22.0-1 GNOME configuration database syste
ii libglade2-01:2.6.2-1 library to load .glade files at ru
ii libglib2.0-0 2.16.3-2 The GLib library of C routines
ii libgnome-keyring0 2.22.1-1 GNOME keyring services library
ii libgnome2-02.20.1.1-1The GNOME 2 library - runtime file
ii libgnomecanvas2-0 2.20.1.1-1A powerful object-oriented display
ii libgnomeui-0 2.20.1.1-1The GNOME 2 libraries (User Interf
ii libgnomevfs2-0 1:2.22.0-2GNOME Virtual File System (runtime
ii libgtk2.0-02.12.9-3 The GTK+ graphical user interface
ii libice62:1.0.4-1 X11 Inter-Client Exchange library
ii libiw2929-1 Wireless tools - library
ii liborbit2 1:2.14.12-0.1 libraries for ORBit2 - a CORBA ORB
ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio
ii libpopt0 1.10-3lib for parsing cmdline parameters
ii libsm6 2:1.0.3-1+b1 X11 Session Management library
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxml22.6.32.dfsg-2 GNOME XML library
ii lsb-base 3.2-11Linux Standard Base 3.2 init scrip
Versions of packages netapplet recommends:
ii gnome-system-tools2.20.0-2 Cross-platform configuration utili
-- no debconf information
diff -urbBw netapplet-1.0.8/debian/changelog
netapplet-1.0.8local/debian/changelog
--- netapplet-1.0.8/debian/changelog2008-05-13 10:28:13.0 -0600
+++ netapplet-1.0.8local/debian/changelog 2008-05-13 10:27:50.0
-0600
@@ -1,3 +1,19 @@
+netapplet (1.0.8-2local1) unstable; urgency=low
+
+ * src/netdaemon.c:
+- Scanning for access points (SIOCSIWSCAN) always failed so the scanning
+ function fell back to reporting the already associated access point.
+ Fixed by properly initializing the wrq struct, as is done by iwlist.c
+ in wireless-tools.
+- Fix netdaemon_do_change_essid_debian() so that it properly takes the
+ iface down before associating to a new access point and then also
+ brings the iface back up again. This actually works well with the
+ Debian logical mapping stanzas and the netapplet can now be used
+ instead of running ifup manually with different mappings, e.g.
+ ifup eth2=ZyXEL or ifup eth2=WRT54GL.
+
+ -- Joachim Nilsson [EMAIL PROTECTED] Wed, 11 Jul 2007 23:48:04 +0200
+
netapplet (1.0.8-2) unstable; urgency=low
* Added LSB formatted dependency on init script (Closes: #460911)
diff -urbBw netapplet-1.0.8/src/netdaemon.c netapplet-1.0.8local/src/netdaemon.c
--- netapplet-1.0.8/src/netdaemon.c 2008-05-13 10:28:13.0 -0600
+++ netapplet-1.0.8local/src/netdaemon.c2008-05-13 10:26:24.0
-0600
@@ -1099,6 +1099,13 @@
if (fd 0)
return;
+/*
+ * Here we should look at the command line args and set the IW_SCAN_
flags
+ * properly
+ */
+wrq.u.data.pointer = NULL; /* Later */
+wrq.u.data.flags = 0;
+wrq.u.data.length = 0;
strncpy (wrq.ifr_name, interface, IFNAMSIZ);
if (ioctl (fd, SIOCSIWSCAN, wrq) = 0) {
ScanningInfo *si;
@@ -1189,6 +1196,19 @@
}
}
+/**
+ * debian can make use of network mapping stanzas, which we don't support
+ * here (yet). Instead we follow the SuSE notion of distrust and make
+ * sure to bring down the interface before picking it up with a new ESSID.
+ *
+ * With proper support for mapping we should instead do it like this;
+ *
+ * 1. Find logical interface, in /etc/network/interfaces
Bug#471769: ifenslave-2.6: pre-up script should only skip enslaving interfaces if auto is used
Package: ifenslave-2.6 Version: 1.1.0-8 Severity: normal The current pre-up script will not enslave any interface which has already been brought up by ifupdown. This breaks some configurations, such as when wpasupplicant is being used via it's ifupdown integration for a wireless interface that is being slaved with a wired interface. In such a configuration, the wireless interface must be ifup'd before it can be enslaved to the bonding device. A simple fix for this is for the pre-up script to only refuse to enslave interfaces chosen by slaves auto, and to honour explicit device listings (such as slave eth0 wlan0). The attached patch implements this fix. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages ifenslave-2.6 depends on: ii libc6 2.7-6 GNU C Library: Shared libraries Versions of packages ifenslave-2.6 recommends: ii net-tools 1.60-19The NET-3 networking toolkit -- no debconf information --- ifenslave-2.6-1.1.0/debian/pre-up 2008-03-19 16:20:33.0 -0600 +++ /etc/network/if-pre-up.d/ifenslave 2008-03-19 16:21:54.0 -0600 @@ -30,6 +30,7 @@ ;; all) INTERFACES=`grep eth /proc/net/dev|sed 's/\(\ *\)\(eth[^:]*\)\(.*\)/\2/'` + AUTOIF=yes ;; *) INTERFACES=$IF_SLAVES @@ -66,7 +67,7 @@ fi ifconfig $IFACE up for slave in $INTERFACES ; do - if grep -q ^$slave= $IFSTATE ; then + if ( [ $AUTOIF ] grep -q ^$slave= $IFSTATE ) ; then echo Not enslaving interface $slave since it is already configured else ifconfig $slave down
Bug#465109: wmctrl: add ability to change application icon
Package: wmctrl
Version: 1.07-6
Severity: wishlist
Tags: patch
I needed the ability to change the icon for applications (I use xfce,
which provides no native way of doing this), so I modified wmctrl to
include this capability. The patch is attached to this email if you are
interested.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages wmctrl depends on:
ii libc6 2.7-6GNU C Library: Shared libraries
ii libglib2.0-02.14.5-2 The GLib library of C routines
ii libice6 2:1.0.4-1X11 Inter-Client Exchange library
ii libsm6 2:1.0.3-1+b1 X11 Session Management library
ii libx11-62:1.0.3-7X11 client-side library
ii libxmu6 2:1.0.4-1X11 miscellaneous utility library
wmctrl recommends no packages.
-- no debconf information
diff -urbBw wmctrl-1.07/Makefile.am wmctrl-1.07.mine/Makefile.am
--- wmctrl-1.07/Makefile.am 2005-01-03 11:48:35.0 -0700
+++ wmctrl-1.07.mine/Makefile.am 2008-02-10 10:43:28.0 -0700
@@ -1,7 +1,7 @@
AM_CFLAGS = -Wall
AM_CPPFLAGS = @X_CFLAGS@ @GLIB_CFLAGS@
-LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu @X_EXTRA_LIBS@ @GLIB_LIBS@
+LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu -lXpm @X_EXTRA_LIBS@ @GLIB_LIBS@
bin_PROGRAMS = wmctrl
wmctrl_SOURCES = main.c
diff -urbBw wmctrl-1.07/Makefile.in wmctrl-1.07.mine/Makefile.in
--- wmctrl-1.07/Makefile.in 2005-01-28 20:33:05.0 -0700
+++ wmctrl-1.07.mine/Makefile.in 2008-02-10 10:43:29.0 -0700
@@ -115,7 +115,7 @@
AM_CFLAGS = -Wall
AM_CPPFLAGS = @X_CFLAGS@ @GLIB_CFLAGS@
-LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu @X_EXTRA_LIBS@ @GLIB_LIBS@
+LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu -lXpm @X_EXTRA_LIBS@ @GLIB_LIBS@
bin_PROGRAMS = wmctrl
wmctrl_SOURCES = main.c
diff -urbBw wmctrl-1.07/debian/control wmctrl-1.07.mine/debian/control
--- wmctrl-1.07/debian/control 2008-02-10 11:09:53.0 -0700
+++ wmctrl-1.07.mine/debian/control 2008-02-10 10:54:15.0 -0700
@@ -2,7 +2,7 @@
Section: x11
Priority: optional
Maintainer: Decklin Foster [EMAIL PROTECTED]
-Build-Depends: debhelper (= 4.0.0), x11proto-core-dev, libx11-dev, libxmu-dev, libglib2.0-dev (= 2.4.0)
+Build-Depends: debhelper (= 4.0.0), x11proto-core-dev, libx11-dev, libxmu-dev, libxpm-dev libglib2.0-dev (= 2.4.0)
Standards-Version: 3.6.2
Package: wmctrl
diff -urbBw wmctrl-1.07/main.c wmctrl-1.07.mine/main.c
--- wmctrl-1.07/main.c 2008-02-10 11:09:53.0 -0700
+++ wmctrl-1.07.mine/main.c 2008-02-10 11:08:05.0 -0700
@@ -34,6 +34,8 @@
#include X11/Xatom.h
#include X11/cursorfont.h
#include X11/Xmu/WinUtil.h
+#include X11/xpm.h
+#include X11/Xmd.h
#include glib.h
#define _NET_WM_STATE_REMOVE0/* remove/unset property */
@@ -64,6 +66,7 @@
argument and list of possible states is given below.\n \
-r WIN -N STRSet the name (long title) of the window.\n \
-r WIN -I STRSet the icon name (short title) of the window.\n \
+ -r WIN -M PATH Set the mini-icon of the window to the xpm bitmap in PATH.\n \
-r WIN -T STRSet both the name and the icon name of the window.\n \
-k (on|off) Activate or deactivate window manager's\n \
\showing the desktop\ mode. Many window managers\n \
@@ -264,7 +267,7 @@
}
}
-while ((opt = getopt(argc, argv, FGVvhlupidmxa:r:s:c:t:w:k:o:n:g:e:b:N:I:T:R:)) != -1) {
+while ((opt = getopt(argc, argv, FGVvhlupidmxa:r:s:c:t:w:k:o:n:g:e:b:N:I:T:R:M:)) != -1) {
missing_option = 0;
switch (opt) {
case 'F':
@@ -296,7 +299,7 @@
case 'r':
options.param_window = optarg;
break;
-case 't': case 'e': case 'b': case 'N': case 'I': case 'T':
+case 't': case 'e': case 'b': case 'N': case 'I': case 'T': case 'M':
options.param = optarg;
action = opt;
break;
@@ -356,7 +359,7 @@
ret = wm_info(disp);
break;
case 'a': case 'c': case 'R':
-case 't': case 'e': case 'b': case 'N': case 'I': case 'T':
+case 't': case 'e': case 'b': case 'N': case 'I': case 'T': case 'M':
if (! options.param_window) {
fputs(No window was specified.\n, stderr);
return EXIT_FAILURE;
@@ -677,6 +680,64 @@
}/*}}}*/
+static int window_set_mini_icon (Display *disp, Window win, /* {{{ */
+char *path, char mode) {
+XpmImage xpmImage;
+XpmInfo xpmInfo;
+Colormap colormap;
+CARD32 *xpmColors;
+XColor xc;
+char *c;
+CARD32 *iconBuffer;
+int iconBufferSize;
Bug#465109: Acknowledgement (wmctrl: add ability to change application icon)
The previous patch had an error in the debian/control file. The attached
patch fixes that problem.
On 02/10/08 11:24, Debian Bug Tracking System wrote:
Thank you for the problem report you have sent regarding Debian.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Decklin Foster [EMAIL PROTECTED]
If you wish to submit further information on your problem, please send
it to [EMAIL PROTECTED] (and *not* to
[EMAIL PROTECTED]).
If you have filed this report in error and wish to close it, please
send mail to [EMAIL PROTECTED] with an explanation
why the bug report should be closed.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Scott Barker [EMAIL PROTECTED]
Linux Consultant http://www.mostlylinux.ca/scott
diff -urbBw wmctrl-1.07/Makefile.am wmctrl-1.07.mine/Makefile.am
--- wmctrl-1.07/Makefile.am 2005-01-03 11:48:35.0 -0700
+++ wmctrl-1.07.mine/Makefile.am2008-02-10 10:43:28.0 -0700
@@ -1,7 +1,7 @@
AM_CFLAGS = -Wall
AM_CPPFLAGS = @X_CFLAGS@ @GLIB_CFLAGS@
-LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu @X_EXTRA_LIBS@ @GLIB_LIBS@
+LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu -lXpm @X_EXTRA_LIBS@ @GLIB_LIBS@
bin_PROGRAMS = wmctrl
wmctrl_SOURCES = main.c
diff -urbBw wmctrl-1.07/Makefile.in wmctrl-1.07.mine/Makefile.in
--- wmctrl-1.07/Makefile.in 2005-01-28 20:33:05.0 -0700
+++ wmctrl-1.07.mine/Makefile.in2008-02-10 10:43:29.0 -0700
@@ -115,7 +115,7 @@
AM_CFLAGS = -Wall
AM_CPPFLAGS = @X_CFLAGS@ @GLIB_CFLAGS@
-LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu @X_EXTRA_LIBS@ @GLIB_LIBS@
+LDADD = @X_LIBS@ @X_PRE_LIBS@ -lX11 -lXmu -lXpm @X_EXTRA_LIBS@ @GLIB_LIBS@
bin_PROGRAMS = wmctrl
wmctrl_SOURCES = main.c
diff -urbBw wmctrl-1.07/debian/changelog wmctrl-1.07.mine/debian/changelog
--- wmctrl-1.07/debian/changelog2008-02-10 11:19:54.0 -0700
+++ wmctrl-1.07.mine/debian/changelog 2008-02-10 11:17:49.0 -0700
@@ -1,3 +1,9 @@
+wmctrl (1.07-6local1) unstable; urgency=low
+
+ * Add ability to change application icons.
+
+ -- Scott Barker [EMAIL PROTECTED] Sun, 10 Feb 2008 11:17:26 -0700
+
wmctrl (1.07-6) unstable; urgency=low
* Reverted CARD32 patch, which was broken on amd64; use fix from Chris
diff -urbBw wmctrl-1.07/debian/control wmctrl-1.07.mine/debian/control
--- wmctrl-1.07/debian/control 2008-02-10 11:19:54.0 -0700
+++ wmctrl-1.07.mine/debian/control 2008-02-10 11:19:42.0 -0700
@@ -2,7 +2,7 @@
Section: x11
Priority: optional
Maintainer: Decklin Foster [EMAIL PROTECTED]
-Build-Depends: debhelper (= 4.0.0), x11proto-core-dev, libx11-dev,
libxmu-dev, libglib2.0-dev (= 2.4.0)
+Build-Depends: debhelper (= 4.0.0), x11proto-core-dev, libx11-dev,
libxmu-dev, libxpm-dev, libglib2.0-dev (= 2.4.0)
Standards-Version: 3.6.2
Package: wmctrl
diff -urbBw wmctrl-1.07/main.c wmctrl-1.07.mine/main.c
--- wmctrl-1.07/main.c 2008-02-10 11:19:54.0 -0700
+++ wmctrl-1.07.mine/main.c 2008-02-10 11:08:05.0 -0700
@@ -34,6 +34,8 @@
#include X11/Xatom.h
#include X11/cursorfont.h
#include X11/Xmu/WinUtil.h
+#include X11/xpm.h
+#include X11/Xmd.h
#include glib.h
#define _NET_WM_STATE_REMOVE0/* remove/unset property */
@@ -64,6 +66,7 @@
argument and list of possible states is given
below.\n \
-r WIN -N STRSet the name (long title) of the window.\n \
-r WIN -I STRSet the icon name (short title) of the window.\n \
+ -r WIN -M PATH Set the mini-icon of the window to the xpm bitmap in
PATH.\n \
-r WIN -T STRSet both the name and the icon name of the window.\n \
-k (on|off) Activate or deactivate window manager's\n \
\showing the desktop\ mode. Many window managers\n \
@@ -264,7 +267,7 @@
}
}
-while ((opt = getopt(argc, argv,
FGVvhlupidmxa:r:s:c:t:w:k:o:n:g:e:b:N:I:T:R:)) != -1) {
+while ((opt = getopt(argc, argv,
FGVvhlupidmxa:r:s:c:t:w:k:o:n:g:e:b:N:I:T:R:M:)) != -1) {
missing_option = 0;
switch (opt) {
case 'F':
@@ -296,7 +299,7 @@
case 'r':
options.param_window = optarg;
break;
-case 't': case 'e': case 'b': case 'N': case 'I': case 'T':
+case 't': case 'e': case 'b': case 'N': case 'I': case 'T': case
'M':
options.param = optarg;
action = opt;
break;
@@ -356,7 +359,7 @@
ret = wm_info(disp);
break;
case 'a': case 'c': case 'R':
-case 't': case 'e': case 'b': case 'N': case 'I
Bug#464071: gozer: right justification ignores X offset
Package: gozer
Version: 0.7.nofont.1-3
Severity: normal
Tags: patch
When using right justification (-j right) and a background image (-G
imagefile), the X offset (-x xoffset) is ignored, and the text is right
justified on the entire background image, instead of being right
justified against the X offset.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_CA.iso8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages gozer depends on:
ii giblib11.2.4-5 wrapper library for imlib2, and ot
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libfreetype6 2.3.5-1+b1FreeType 2 font engine, shared lib
ii libimlib2 1.4.0-1 powerful image loading and renderi
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
gozer recommends no packages.
-- no debconf information
Only in gozer-0.7.nofont.1: gozer.spec
diff -urbBw gozer-0.7.nofont.1/src/main.c gozer-0.7.nofont.1.patched/src/main.c
--- gozer-0.7.nofont.1/src/main.c 2008-02-04 13:57:50.0 -0700
+++ gozer-0.7.nofont.1.patched/src/main.c 2008-02-04 13:01:46.0
-0700
@@ -169,7 +169,14 @@
opt.fn_r, opt.fn_g, opt.fn_b, opt.fn_a);
break;
case JUST_RIGHT:
+ if (opt.x)
+ {
+ x = opt.x - ww;
+ }
+ else
+ {
x = (((opt.bg_resize bgw) ? bgw : w) - ww);
+ }
gib_imlib_text_draw(image, fn, style, x, y, p, IMLIB_TEXT_TO_RIGHT,
opt.fn_r, opt.fn_g, opt.fn_b, opt.fn_a);
