Bug#977458: micro: Please register micro for the editor alternative
Package: micro Version: 2.0.6-2~bpo10+1 Severity: wishlist Please could you register /usr/bin/micro for the 'editor' alternative? The description is in policy 11.4 -M-
Bug#922641: postgresql-common: pg_upgradecluster doesn't preserve ownership of the public schema
Package: postgresql-common Version: 199.pgdg90+1 Severity: normal If I upgrade a cluster from v10 to v11 using pg_upgradecluster (in its dump-and-restore variant), in the new cluster each database has a public schema owned by user 'postgres', no matter who owned it before. Further, in databases where the public schema had been dropped it reappears in the new cluster. I'm using the pgdg packages, but as I understand it you don't mind bug reports for those here. postgresql-10: 10.7-1.pgdg90+1 postgresql-11: 11.2-1.pgdg90+1 Steps to reproduce: -- as root: pg_createcluster --start 10 bugtest -- as user postgres: export PGCLUSTER=10/bugtest createdb schematest1 createdb schematest2 createuser user1 createuser user2 psql -c'drop schema public' schematest1 psql -c'alter schema public owner to user1' schematest2 psql -c'grant usage on schema public to user2' schematest2 psql -c'\dn+' schematest1 « List of schemas Name | Owner | Access privileges | Description --+---+---+- (0 rows) » psql -c'\dn+' schematest2 « List of schemas Name | Owner | Access privileges | Description +---+---+ public | user1 | user1=UC/user1 +| standard public schema | | =UC/user1+| | | user2=U/user1 | (1 row) » -- as root: pg_upgradecluster 10 bugtest -- as user postgres: export PGCLUSTER=11/bugtest psql -c'\dn+' schematest1 « List of schemas Name | Owner | Access privileges | Description +--+--+ public | postgres | postgres=UC/postgres+| standard public schema | | =UC/postgres | (1 row) » psql -c'\dn+' schematest2 « public | postgres | user1=UC/postgres+| standard public schema | | =UC/postgres +| | | user2=U/postgres | List of schemas Name | Owner +-- public | postgres (1 row) »
Bug#492901: please suppress the edns-disabled log category
I think it would be better to leave the edns-disabled category enabled. Nowadays these messages are much rarer in normal circumstances, so they're less of a problem (also, Debian's default logcheck rules make logcheck ignore them). Last week my employer's ISP did something which broke many outgoing DNS requests using EDNS, and the sudden appearance of large numbers of "disabling EDNS" and "reducing the advertised EDNS UDP packet size" messages in Bind's logs made it much easier to identify the problem (and work around it with 'edns no' until it was fixed).
Bug#893569: barman: Mail from /etc/cron.d/barman should be delivered to root
Package: barman Version: 2.1-1 Severity: normal The barman package installs /etc/cron.d/barman, which runs a command as user barman. At present the package doesn't take any special action to control where mail from cron is sent, so if there is any error output it will normally end up in /var/mail/barman where it's unlikely anyone will see it. I think the more usual approach in Debian packages is to arrange for this mail to be delivered to root, either by setting MAILTO=root in the cron.d file itself or by adding an entry in /etc/aliases for user barman from postinst. (The logcheck package provides an example of both of these things.)
Bug#891976: localechooser: Unhelpful modifications to /root/.profile when locale "C" is chosen
Package: localechooser
Version: 2.69
Severity: normal
Tags: d-i
If I install Stretch using Debian-Installer and select language 'C' ('no
localisation'), and default locale 'C', then I end up with the following
lines at the end of /root/.profile:
# Installed by Debian Installer:
# no localization for root because C
# cannot be properly displayed at the Linux console
LANG=C
LANGUAGE=C
This is mostly harmless, but it causes trouble if I later change
/etc/default/locale (eg to C.UTF-8).
This seems to have been going on for the last several Debian releases.
sources.debian.net suggests that these lines are added by the
post-base-installer.d/05localechooser script.
The intention is apparently that those lines would be added if the
selected language is one which has "no chance to be displayed at the
Linux console", so I think adding them when the C locale was chosen is a
bug.
I don't understand how the code it's using to decide whether to do this
ends up firing for "C", but in any case it appears to be broken:
- it evidently hasn't been updated for changes to the format of the
languagelist file ('cut -f 2-3' seems appropriate for the version in
etch but not the version in lenny);
- it fails to ignore comment lines.
Perhaps terminals have improved sufficiently that this feature should
just be removed altogether.
Bug#890946: debian-policy: Editor policy is inconsistent with sensible-editor's behaviour
Ian Jackson wrote: I think #482274 should probably simply be reverted. From the POV of the policy package: I think existing policy is correct. A bug should be filed against sensible-editor saying that #482274 should be reverted so that programs which use sensible-editor conform to policy. I have filed #891795 against sensible-utils.
Bug#891795: /usr/bin/sensible-editor: The select-editor mechanism should be removed
Package: sensible-utils Version: 0.0.11 Severity: normal Background: Policy 11.4 describes the mechanism for determining the user's preferred editor: - check the EDITOR environment variable and use it if set; - (optionally): check the VISUAL environment variable and use it if set; - otherwise, use /usr/bin/editor (which is managed as a dpkg alternative). sensible-editor was invented as a convenient way for packages to implement this behaviour in programs whose source code doesn't do so already. In #482774, sensible-editor's behaviour was changed, adding a new helper script named 'select-editor', and is now roughly as follows: - check EDITOR and VISUAL as per policy; - if neither is set, check a ~/.selected-editor configuration file; - if that doesn't provide an editor, offer the user a list of editors and record their choice in ~/.selected-editor The list that select-editor provides comes from the dpkg alternatives system. If one of the editors in the list is 'nano', it's annotated with "< easiest". Problems: The intent of this change was to make life easier for inexperienced users, who might not find it easy to edit .bashrc to change an environment variable. But this does not work well, for a number of reasons. 1) Many (I believe most) programs shipped in Debian which invoke an editor implement the environment variable check and fallback directly, rather than using sensible-editor. 2) If the system administrator has selected a system-wide alternative which their users will find more friendly than nano, select-editor ends up making their lives worse. 3) If the user selects an editor via select-editor which is later removed (eg a versioned emacs), things go badly (see #753670). Of these I think the first is the most serious. The effect is that users see inconsistent behaviour depending which program is launching an editor. They can think they've told the system their preferred editor once, then find it's not used later. Or they can find they normally get an editor they're comfortable with, then on one occasion be presented with a list of unfamiliar names and end up with nano. I asked about this on Debian policy (#890946), and received the response that sensible-editor wasn't intended as a point where enhancements could be made, and a recommendation that #482774 should be reverted so that programs which use sensible-editor conform to policy.
Bug#890946: debian-policy: Editor policy is inconsistent with sensible-editor's behaviour
Package: debian-policy Version: 4.1.3.0 Severity: normal Policy 11.4 describes the mechanism for determining the user's preferred editor: - check the EDITOR environment variable and use it if set; - (optionally): check the VISUAL environment variable and use it if set; - otherwise, use /usr/bin/editor (which is managed as a dpkg alternative). It goes on to state that this is what sensible-editor implements (and so a program may invoke sensible-editor and be Policy-compliant). But this is untrue: sensible-editor hasn't behaved like this since late 2010. Its current behaviour is roughly as follows: - check EDITOR and VISUAL as per policy; - if neither is set, check a ~/.selected-editor configuration file; - if that doesn't provide an editor, offer the user a list of editors and record their choice in ~/.selected-editor The rationale for this behaviour is in bug 482774 [1]. The list it provides comes from the dpkg alternatives system, but doesn't indicate which alternative is the one currently selected system-wide. It's apparently in alphabetical order (rather than using alternatives priority). If one of the editors in the list is 'nano', it's annotated with "< easiest". The effect is that users see inconsistent behaviour depending on whether the program launching the editor is using sensible-editor or implementing the policy mechanism directly (which in my experience is much more common). They can think they've told the system their preferred editor once, then find it's not used later. Or they can find they normally get an editor they're comfortable with, then on one occasion be presented with a list of unfamiliar names and end up with nano. Ideally I think Policy would permit exactly one of these behaviours, but at any rate what it currently says is untrue so something should change. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482774
Bug#884134: python-rpy: Incompatible with the version of R in stretch
Package: python-rpy Version: 1.0.3-30 Severity: grave Installing and importing the stretch version of python-rpy fails with the stretch version of R: « apt install python-rpy python Python 2.7.13 (default, Nov 24 2017, 17:33:09) [GCC 6.3.0 20170516] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import rpy Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/rpy.py", line 134, in """ % RVERSION) RuntimeError: No module named _rpy3033 RPy module can not be imported. Please check if your rpy installation supports R 3.3.3. If you have multiple R versions installed, you may need to set RHOME before importing rpy. For example: >>> from rpy_options import set_options >>> set_options(RHOME='c:/progra~1/r/rw2011/') >>> from rpy import * » I see python-rpy is providing _rpy3011.so, not _rpy3033.so . -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-rpy depends on: ii libc6 2.24-11+deb9u1 ii python2.7.13-2 ii python-numpy [python-numpy-abi9] 1:1.12.1-3 ii r-base-core 3.3.3-1 python-rpy recommends no packages. Versions of packages python-rpy suggests: pn python-rpy-docs -- no debconf information
Bug#872868: debian-policy: section numbers missing
For what it's worth, I've submitted a Sphinx patch which implements section numbering in plain text: https://github.com/sphinx-doc/sphinx/pull/4218 I haven't interacted with Sphinx upstream before so I don't know whether they're likely to respond quickly. -M-
Bug#867715: openssl: "unknown group" error messages from 'openssl speed' ECDSA and ECDH
Package: openssl Version: 1.1.0f-3 Severity: normal Running 'openssl speed', I see error messages from ECDSA and ECDH: ECDSA failure. 4146407744:error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group:../crypto/ec/ec_curve.c:3100: amd ECDH failure. 4146645312:error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group:../crypto/ec/ec_curve.c:3100: 4146645312:error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group:../crypto/ec/ec_curve.c:3100: The errors seem to be reliably reproducible, with the same error messages except that in each case the first number changes. Full output follows: % openssl speed ecdsa Doing 160 bit sign ecdsa's for 10s: 94968 160 bit ECDSA signs in 9.98s Doing 160 bit verify ecdsa's for 10s: 33582 160 bit ECDSA verify in 10.00s Doing 192 bit sign ecdsa's for 10s: 94465 192 bit ECDSA signs in 10.00s Doing 192 bit verify ecdsa's for 10s: 25142 192 bit ECDSA verify in 9.98s Doing 224 bit sign ecdsa's for 10s: 72176 224 bit ECDSA signs in 10.00s Doing 224 bit verify ecdsa's for 10s: 18713 224 bit ECDSA verify in 10.00s Doing 256 bit sign ecdsa's for 10s: 115773 256 bit ECDSA signs in 9.98s Doing 256 bit verify ecdsa's for 10s: 50658 256 bit ECDSA verify in 10.00s Doing 384 bit sign ecdsa's for 10s: 24252 384 bit ECDSA signs in 9.98s Doing 384 bit verify ecdsa's for 10s: 6327 384 bit ECDSA verify in 10.00s Doing 521 bit sign ecdsa's for 10s: 11092 521 bit ECDSA signs in 10.00s Doing 521 bit verify ecdsa's for 10s: 2917 521 bit ECDSA verify in 10.00s Doing 163 bit sign ecdsa's for 10s: 39258 163 bit ECDSA signs in 10.00s Doing 163 bit verify ecdsa's for 10s: 16076 163 bit ECDSA verify in 10.00s Doing 233 bit sign ecdsa's for 10s: 20407 233 bit ECDSA signs in 10.00s Doing 233 bit verify ecdsa's for 10s: 9629 233 bit ECDSA verify in 10.00s Doing 283 bit sign ecdsa's for 10s: 13373 283 bit ECDSA signs in 10.00s Doing 283 bit verify ecdsa's for 10s: 5377 283 bit ECDSA verify in 10.00s Doing 409 bit sign ecdsa's for 10s: 5472 409 bit ECDSA signs in 10.00s Doing 409 bit verify ecdsa's for 10s: 2708 409 bit ECDSA verify in 10.00s Doing 571 bit sign ecdsa's for 10s: 2251 571 bit ECDSA signs in 10.00s Doing 571 bit verify ecdsa's for 10s: 1144 571 bit ECDSA verify in 10.00s Doing 163 bit sign ecdsa's for 10s: 39505 163 bit ECDSA signs in 9.98s Doing 163 bit verify ecdsa's for 10s: 15082 163 bit ECDSA verify in 10.00s Doing 233 bit sign ecdsa's for 10s: 20490 233 bit ECDSA signs in 10.00s Doing 233 bit verify ecdsa's for 10s: 8940 233 bit ECDSA verify in 10.00s Doing 283 bit sign ecdsa's for 10s: 13441 283 bit ECDSA signs in 9.98s Doing 283 bit verify ecdsa's for 10s: 4926 283 bit ECDSA verify in 9.98s Doing 409 bit sign ecdsa's for 10s: 5451 409 bit ECDSA signs in 10.00s Doing 409 bit verify ecdsa's for 10s: 2447 409 bit ECDSA verify in 10.00s Doing 571 bit sign ecdsa's for 10s: 2282 571 bit ECDSA signs in 10.00s Doing 571 bit verify ecdsa's for 10s: 1020 571 bit ECDSA verify in 10.00s ECDSA failure. 4146407744:error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group:../crypto/ec/ec_curve.c:3100: OpenSSL 1.1.0f 25 May 2017 built on: reproducible build, date unspecified options:bn(64,32) rc4(8x,mmx) des(long) aes(partial) blowfish(ptr) compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/lib/ssl\"" -DENGINESDIR="\"/usr/lib/i386-linux-gnu/engines-1.1\"" signverifysign/s verify/s 160 bit ecdsa (secp160r1) 0.0001s 0.0003s 9515.8 3358.2 192 bit ecdsa (nistp192) 0.0001s 0.0004s 9446.5 2519.2 224 bit ecdsa (nistp224) 0.0001s 0.0005s 7217.6 1871.3 256 bit ecdsa (nistp256) 0.0001s 0.0002s 11600.5 5065.8 384 bit ecdsa (nistp384) 0.0004s 0.0016s 2430.1632.7 521 bit ecdsa (nistp521) 0.0009s 0.0034s 1109.2291.7 163 bit ecdsa (nistk163) 0.0003s 0.0006s 3925.8 1607.6 233 bit ecdsa (nistk233) 0.0005s 0.0010s 2040.7962.9 283 bit ecdsa (nistk283) 0.0007s 0.0019s 1337.3537.7 409 bit ecdsa (nistk409) 0.0018s 0.0037s547.2270.8 571 bit ecdsa (nistk571) 0.0044s 0.0087s225.1114.4 163 bit ecdsa (nistb163) 0.0003s 0.0007s 3958.4 1508.2 233 bit ecdsa (nistb233) 0.0005s 0.0011s 2049.0894.0 283 bit ecdsa (nistb283) 0.0007s 0.0020s 1346.8493.6 409 bit ecdsa (nistb409) 0.0018s 0.0041s545.1244.7 571 bit ecdsa (nistb571) 0.0044s 0.0098s228.2102.0 253 bit ecdsa (X25519) 0.s 0.s inf inf % openssl speed ecdh Doing 160 bit ecdh's for 10s: 40040 160-bit ECDH ops
Bug#865378: guake: WM_CLASS is unhelpful ("Main.py")
Package: guake Version: 0.8.8-1 Severity: normal In Jessie (guake 0.4.4), guake's WM_CLASS X property (according to xprop) was: WM_CLASS(STRING) = "guake", "Guake" In Stretch, it's the less informative WM_CLASS(STRING) = "guake", "Main.py" This makes it less convenient to configure window managers to give Guake special treatment. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (200, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages guake depends on: ii gconf2 3.2.6-4+b1 ii libgtk2.0-0 2.24.31-2 ii notification-daemon 3.20.0-1+b1 ii python 2.7.13-2 ii python-dbus 1.2.4-1+b1 ii python-gconf 2.28.1+dfsg-1.2 ii python-glade22.24.0-5.1 ii python-keybinder 0.3.1-1 ii python-notify0.1.1-4 ii python-vte 1:0.28.2-5+b2 ii python-xdg 0.25-4 ii python2.72.7.13-2 guake recommends no packages. guake suggests no packages. -- no debconf information
Bug#741512: clamav-base configure error ('/usr/share/doc/clamav-base/examples/clamd.conf does not exist!')
Package: clamav Version: 0.98.1+dfsg-1+deb6u1 Severity: normal Upgrade to clamav 0.98.1+dfsg-1+deb6u1 (from squeeze-updates) failed with the following error: Setting up clamav-base (0.98.1+dfsg-1+deb6u1) ... Error: The new file /usr/share/doc/clamav-base/examples/clamd.conf does not exist! dpkg: error processing clamav-base (--configure): subprocess installed post-installation script returned error exit status 1 The following was sufficient to work around the problem: cp /usr/share/doc/clamav-base/examples/clamd.conf.sample /usr/share/doc/clamav-base/examples/clamd.conf dpkg --pending --configure -- System Information: Debian Release: 6.0.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages clamav depends on: ii clamav-freshclam [c 0.98.1+dfsg-1+deb6u1 anti-virus utility for Unix - viru ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libclamav6 0.98.1+dfsg-1+deb6u1 anti-virus utility for Unix - libr ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages clamav recommends: ii clamav-base 0.98.1+dfsg-1+deb6u1 anti-virus utility for Unix - base Versions of packages clamav suggests: ii clamav-docs 0.98.1+dfsg-1+deb6u1 anti-virus utility for Unix - docu -- 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#741512: clamav-base configure error ('/usr/share/doc/clamav-base/examples/clamd.conf does not exist!')
On 2014-03-13 12:31, Andreas Cadhalpun wrote: I couldn't reproduce this in a virtual machine: * install squeeze 6.0.9 * install clamav 0.97.8+dfsg-1~squeeze1 * update clamav to 0.98.1+dfsg-1~squeeze1 From which version did you upgrade? 0.97.8+dfsg-1~squeeze1 The following was sufficient to work around the problem: cp /usr/share/doc/clamav-base/examples/clamd.conf.sample /usr/share/doc/clamav-base/examples/clamd.conf dpkg --pending --configure Did you remove this file manually before? No. I think the file was renamed from clamd.conf.sample to clamd.conf in the 0.98.1 package. On the system in question, /etc/clamav/clamd.conf has been modified, and I have 'clamav-base/debconf: false'. This seems to be related to #295565 . # debconf-show clamav-base clamav-base/ScanMail: true clamav-base/AddGroups: Debian-exim clamav-base/Bytecode: true clamav-base/FollowDirectorySymlinks: false * clamav-base/debconf: false clamav-base/BytecodeSecurity: TrustSigned clamav-base/BytecodeTimeout: 6 clamav-base/numinfo: clamav-base/TCPAddr: any clamav-base/ReadTimeout: 180 clamav-base/TcpOrLocal: UNIX clamav-base/FollowFileSymlinks: false clamav-base/MaxThreads: 12 clamav-base/MaxDirectoryRecursion: 0 clamav-base/StreamMaxLength: 25 clamav-base/User: clamav clamav-base/TCPSocket: 3310 clamav-base/LocalSocketGroup: clamav clamav-base/ArchiveMaxFiles: 1000 clamav-base/LogSyslog: false clamav-base/socket-note: clamav-base/FixStaleSocket: true clamav-base/SelfCheck: 3600 clamav-base/LocalSocketMode: 666 clamav-base/ScanRAR: false clamav-base/ScanArchive: true clamav-base/MaxConnectionQueueLength: 15 clamav-base/ArchiveMaxRecursion: 5 clamav-base/ArchiveMaxFileSize: 10 clamav-base/LogFile: /var/log/clamav/clamav.log clamav-base/LogTime: true clamav-base/LocalSocket: /var/run/clamav/clamd clamav-base/ArchiveMaxCompressionRatio: 500 -M- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739369: joe-jupp: ^W (cut) often broken in jmacs if '-marking' is enabled
Package: joe-jupp Version: 3.1.26-1 Severity: normal If I use jmacs with 'marking' in the configuration, often (but not always) ^W (cut) fails. Also, sometimes the 'region' highlighting fails to appear, and this seems to correspond to the times when ^W doesn't fail. To reproduce: cat .jmacsrc EOF :include /etc/jupp/jmacsrc -marking EOF cat /tmp/testfile.txt EOF 12345 EOF jmacs /tmp/testfile.txt ctrl-SPC ctrl-e ctrl-w jmacs rings the bell and says 'No block' at the bottom of the screen. It should delete the '12345'. Also observed in 3.1.21-1 3.1.25-1~bpo70+1 -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable'), (200, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.12-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages joe-jupp depends on: ii jupp 3.1.26-1 joe-jupp recommends no packages. joe-jupp 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#697402: bzr-gtk: causes crash in pydoc -k when python-gtk2 is also installed
Debian has in the past contained Python packages which have side-effects when imported which are worse than just crashing the calling process (for example, I've had pydoc crash my window manager). Arguably all such cases are bugs in those packages, but it seems likely that such bugs will appear again. And of course the user might have local Python packages which do dangerous things when imported. So I think pydoc is just wrong to believe it can safely call pkgutil.walk_packages() with no explicit path. (This behaviour can be particularly entertaining when combined with zsh's tab-completion for 'python -m', which currently calls pydoc in a similar way [#691638].) -M- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683147: ERROR: install script from emacs-goodies-el package failed
This problem no longer occurs with the current emacs-snapshot. The failing code in emacs-goodies-el was the following from eproject.el: (setf (getf (nth 3 (assoc type eproject-project-types)) key) value)) So I assume it was the same as this upstream bug report. http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12191 -M- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659474: spamassassin: sa-compile problem on upgrade
Package: spamassassin Version: 3.3.2-2 Severity: normal I recently upgraded from Squeeze to testing, and the spamassassin upgrade (to version 3.3.2-2) didn't go smoothly. I have sa-compile enabled. I got the following error when dpkg tried to configure spamassassin: Running sa-compile (may take a long time) In file included from /usr/include/sys/param.h:28, from /usr/lib/perl/5.10/CORE/perl.h:671, from body_0.xs:2: /usr/include/linux/param.h:4:23: error: asm/param.h: No such file or directory In file included from /usr/include/sys/socket.h:40, from /usr/include/netinet/in.h:25, from /usr/lib/perl/5.10/CORE/perl.h:1151, from body_0.xs:2: /usr/include/bits/socket.h:370:24: error: asm/socket.h: No such file or directory In file included from /usr/include/bits/errno.h:25, from /usr/include/errno.h:36, from /usr/lib/perl/5.10/CORE/perl.h:1208, from body_0.xs:2: /usr/include/linux/errno.h:4:23: error: asm/errno.h: No such file or directory In file included from /usr/include/sys/ioctl.h:27, from /usr/lib/perl/5.10/CORE/perl.h:1370, from body_0.xs:2: /usr/include/bits/ioctls.h:24:24: error: asm/ioctls.h: No such file or directory make: *** [body_0.o] Error 1 command 'make /tmp/.spamassassin9777NhcLWftmp/log' failed: exit 2 dpkg: error processing spamassassin (--configure): subprocess installed post-installation script returned error exit status 25 After libc6-dev was upgraded (from 2.11.3-2 to 2.13-26), reconfiguring spamassassin worked fine. So I suppose the dependencies need tweaking. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.39 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages spamassassin depends on: ii libarchive-tar-perl none ii libhtml-parser-perl 3.69-1+b1 ii libnet-dns-perl 0.66-2+b2 ii libnetaddr-ip-perl 4.058+dfsg-2 ii libsocket6-perl 0.23-1+b2 ii libsys-hostname-long-perl 1.4-2 ii libwww-perl 6.03-1 ii perl5.14.2-7 ii perl-modules [libio-zlib-perl] 5.14.2-7 Versions of packages spamassassin recommends: ii gcc4:4.6.2-4 ii gnupg 1.4.11-3 ii libc6-dev 2.13-26 ii libio-socket-inet6-perl2.69-2 ii libmail-spf-perl 2.007-2 ii make 3.81-8.1 ii perl [libsys-syslog-perl] 5.14.2-7 ii re2c 0.13.5-1 ii spamc 3.3.2-2 Versions of packages spamassassin suggests: pn libdbi-perl 1.616-1+b2 pn libio-socket-ssl-perl 1.54-1 pn libmail-dkim-perl none pn libnet-ident-perl none pn perl [libcompress-zlib-perl] 5.14.2-7 pn pyzor 1:0.5.0-2 pn razor none -- Configuration Files: /etc/default/spamassassin changed [not included] -- 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#644788: Bug#654116: RFH: screen -- terminal multiplexor with VT100/ANSI terminal emulation
Axel Beckert a...@debian.org wrote: Simon McVittie wrote: Would it be enough for the your old screen binary is /tmp/screen-yhpoe8r/screen notice to also say if your /tmp is mounted noexec, you might need to copy it elsewhere to run it? That's my current plan -- with the noexec notice just being displayed if /tmp actually is mounted noexec. Will you need something similar if /tmp is mounted nosuid? I think that's more common. -M- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625758: 'adduser --disabled-login' does not behave as documented.
Package: adduser Version: 3.112+nmu2 Severity: normal The adduser manpage in squeeze contains the following: --disabled-login Do not run passwd to set the password. The user won't be able to use her account until the password is set. --disabled-password Like --disabled-login, but logins are still possible (for exam‐ ple using SSH RSA keys) but not using password authentication. Similar text has been there for many years, but it hasn't really been true in Debian since whenever 'UsePAM yes' became the default in sshd_config: an account created using --disabled-login can still be used to log in using public-key authentication without a password being set. I think either the adduser manpage should be changed to not imply that disabled-login will prevent SSH public-key logins, or else adduser --disabled-login should be changed to do the equivalent of 'chage -E 1'. Versions of packages adduser depends on: ii debconf [de 1.5.36.1 Debian configuration management sy ii passwd 1:4.1.4.2+svn3283-2+squeeze1 change and administer password and ii perl-base 5.10.1-17minimal Perl system -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613861: 'userv --builtin parameter' fails
Package: userv Version: 1.0.5-0.2 Severity: normal 'userv --builtin parameter' fails. For example, on a clean installation: % userv --builtin parameter calling-user uservd: configuration override data:1: found newline (or comment followed by newline), expected linear whitespace uservd: error encountered while parsing configuration userv: uservd reports that service failed 'execute-builtin parameter' from a configuration file is fine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613862: userv: Breakage with comments inside control structures
Package: userv Version: 1.0.5-0.2 Severity: normal Comments inside 'if/fi' cause problems: they are properly ignored when the condition is true, but they give an error (which stops processing) when the condition is false. For example, with the following configuration file: if glob service runbuiltin reset # comment execute-builtin parameter calling-user-shell fi % userv mjw xxx uservd: /home/mjw/.userv/rc:3: not a directive (or conditional operator) while looking for control structure end uservd: request rejected userv: uservd reports that service failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586425: compiz-plugins: Commands plugin doesn't close FDs before executing the command
Package: compiz-plugins Version: 0.8.4-4 Severity: normal The compiz 'commands' plugin doesn't close file descriptors before executing a command. In the setup I'm using, this means all programs (eg, xterms) launched from compiz get the following unwanted open FDs: 3 - /usr/share/pyshared/FusionIcon/interface_gtk/__init__.py 4 - /usr/share/pyshared/FusionIcon/interface_gtk/main.py 5 - anon_inode:inotify 7 - anon_inode:inotify -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (989, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.34 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages compiz-plugins depends on: ii compiz-core 0.8.4-4 OpenGL window and compositing mana ii gconf2 2.28.1-3 GNOME configuration database syste ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst ii libdecoration0 0.8.4-4 Compiz window decoration library ii libglib2.0-02.24.1-1 The GLib library of C routines ii libglu1-mesa [libglu1] 7.7.1-3 The OpenGL utility library (GLU) ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libpng12-0 1.2.43-1 PNG library - runtime ii librsvg2-2 2.26.3-1 SAX-based renderer library for SVG ii libx11-62:1.3.3-3X11 client-side library ii libxml2 2.7.7.dfsg-2 GNOME XML library ii libxrender1 1:0.9.5-2X Rendering Extension client libra compiz-plugins recommends no packages. compiz-plugins 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#572775: xserver-xorg-video-radeon: xeyes causes X server to crash
Michel Dänzer wrote: Does this still happen with a newer xserver-xorg-video-radeon, e.g. 1:6.12.5-1 from sid? If so, please try to get a backtrace with gdb, preferably with xserver-xorg-core-dbg and xserver-xorg-video-radeon-dbg installed. This symptom no longer occurs with xserver-xorg-video-radeon 1:6.12.5-1. My mission-critical xeyes usage can now resume. -M- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543506: postgresql-common: pg_upgradecluster doesn't preserve per-database ACLs or configuration parameters
Package: postgresql-common Version: 94lenny1 Severity: normal pg_upgradecluster doesn't preserve the contents of pg_database.datconfig or pg_database.datacl. (That is, it doesn't preserve the results of 'GRANT foo ON DATABASE bar TO baz' or 'ALTER DATABASE name SET foo TO bar'.) I think bug 539772 is a specific case of this issue. This information isn't provided by either pg_dump or pg_dumpall -g. It is included in the output of pg_dumpall -s, in the 'Database creation' section. Possible strategies for implementing this in pg_upgradecluster might be to parse the information out of the 'pg_dumpall -s' output, or to duplicate the dumpCreateDB logic from pg_dumpall. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496355: texmacs: Segfaults on file close
I also built 1.0.6.15 from source, but I saw the same crash on file close as in the original report. Now that guile-1.8 1.8.5 has entered Lenny (1.8.5+1-4), I do not see the crash with the (same) locally-built texmacs 1.0.6.15, but I still see it with the Debian build (ie, 1:1.0.6.14-1). -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496355: texmacs: Segfaults on file close
Package: texmacs Version: 1:1.0.6.14-1 Severity: important texmacs usually segfaults when I close a file. I think it may happen exactly when there is more than one buffer open. Steps to reproduce: rm -rf ~/.TeXmacs texmacs File - New File - Close document -- TeXmacs output: Welcome to TeXmacs 1.0.6.14 -- Since this seems to be the first time you have run this version of TeXmacs, I will first analyze your system in order to set up some TeX paths in the correct way. This may take some seconds; the result can be found in /home/mjw/.TeXmacs/system/settings.scm -- TeXmacs] kpsepath works with your TeX distribution TeXmacs] kpsewhich works with your TeX distribution TeXmacs] mktextfm works with your TeX distribution TeXmacs] mktexpk works with your TeX distribution TeXmacs] texhash works with your TeX distribution TeXmacs] Trying to create ecrm10.123pk from 300 dpi mktexpk: Mismatched mode ljfour and resolution 300; ignoring mode. mktexpk: /home/mjw/.texmf-var/fonts/pk/cx/jknappen/ec/ecrm10.123pk already exists. /home/mjw/.texmf-var/fonts/pk/cx/jknappen/ec/ecrm10.123pk TeXmacs] Metafont works with 300 dpi ec-fonts -- Installation completed successfully ! I will now start up the editor -- TeXmacs] With linked TrueType support zsh: segmentation fault (core dumped) texmacs -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (989, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages texmacs depends on: ii findutils 4.4.0-2 utilities for finding files--find, ii ghostscript-x [gs-gpl] 8.62.dfsg.1-3 The GPL Ghostscript PostScript/PDF ii groff 1.18.1.1-20 GNU troff text-formatting system ii gs-gpl 8.62.dfsg.1-3 Transitional package ii guile-1.8-libs 1.8.4+1-2 Main Guile libraries ii libc6 2.7-13GNU C Library: Shared libraries ii libfreetype6 2.3.7-1 FreeType 2 font engine, shared lib ii libgcc11:4.3.1-2 GCC support library ii libgmp3c2 2:4.2.2+dfsg-3Multiprecision arithmetic library ii libltdl3 1.5.26-4 A system independent dlopen wrappe ii libstdc++6 4.3.1-2 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.4-2 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii locate 4.4.0-2 maintain and query an index of a d ii texlive-base 2007.dfsg.1-3 TeX Live: Essential programs and f ii texlive-extra-utils2007.dfsg.2-3 TeX Live: TeX auxiliary programs ii texlive-font-utils 2007.dfsg.2-3 TeX Live: TeX font-related program ii texlive-math-extra 2007.dfsg.3-2 TeX Live: Advanced math typesettin ii texmacs-common 1:1.0.6.14-1 WYSIWYG mathematical text editor u ii xbase-clients 1:7.3+15 miscellaneous X clients - metapack ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages texmacs recommends: ii imagemagick 7:6.3.7.9.dfsg1-2+b2 image manipulation programs ii ispell 3.1.20.0-4.4 International Ispell (an interacti ii libjpeg-progs 6b-14Programs for manipulating JPEG fil ii librsvg2-bin2.22.2-2 command-line and graphical viewers ii libtiff-tools 3.8.2-10 TIFF manipulation and conversion t ii netpbm 2:10.0-12Graphics conversion tools ii texmacs-extra-fonts 0.2 extra fonts for the mathematical t ii xfig1:3.2.5-rel-2Facility for Interactive Generatio Versions of packages texmacs suggests: ii python2.5.2-1An interactive high-level object-o ii wget 1.11.4-1 retrieves files from the web -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413959: glark: colons on file names are interpreted as separators
According to the glark manpage, this a feature. You have to specify --no-split-as-path to disable it. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371857: i810 doesn't restore console properly with vga=ext.
Brice Goglin wrote: That's very strange. There should be a full PCI scan in your log before the intel driver is even loaded, right between the lines below. It doesn't appear at all here. (--) using VT number 7 (II) Addressable bus resource ranges are It seems to mean that something is going wrong in the server core. Did you change something apart from upgrading xserver-xorg-video-intel? Is this problem reproducible? Even after a reboot? Apparently for some reason /proc didn't get mounted that time when I booted into the unstable installation, and that was the cause of the above trouble. Sorry for the noise. I can confirm that xserver-xorg-video-intel 2:2.0.0-5 restores the console properly with vga=ext, so I think this bug can be closed. I'm still seeing a form of the freezes which I described in [EMAIL PROTECTED] , but I'll report that as a separate bug. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371857: i810 doesn't restore console properly with vga=ext.
Brice Goglin wrote: Is there a chance you try xserver-xorg-core 1.3 (in testing) and xserver-xorg-video-intel 2.0 (in experimental)? The latter is a major rework of the driver for intel graphic chipsets. I tried with the following combination (from today's sid): xserver-xorg-core 2:1.3.0.0.dfsg-6 xserver-xorg-video-intel 2:2.0.0-1 This crashes if I switch to the console and then back to X (I wasn't using vga=ext in this case). At first, after I switched back, it was working partially (the window decorations didn't draw, but I could type into a terminal). Then it became unresponsive except for the mouse pointer. ctrl-alt-backspace wouldn't kill it, but alt-sysrq did. Xorg.log shows this from the switch to console and back: (II) AIGLX: Suspending AIGLX clients for VT switch (II) intel(0): xf86UnbindGARTMemory: unbind key 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 (II) intel(0): xf86UnbindGARTMemory: unbind key 2 (II) intel(0): xf86UnbindGARTMemory: unbind key 3 (II) intel(0): xf86UnbindGARTMemory: unbind key 4 (II) intel(0): xf86UnbindGARTMemory: unbind key 5 (II) intel(0): xf86UnbindGARTMemory: unbind key 6 (II) intel(0): xf86UnbindGARTMemory: unbind key 7 (II) intel(0): xf86UnbindGARTMemory: unbind key 8 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) AIGLX: Resuming AIGLX clients after VT switch (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007bf000 (pgoffset 1983) (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x007c (pgoffset 1984) (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x007c4000 (pgoffset 1988) (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x007c5000 (pgoffset 1989) (II) intel(0): xf86BindGARTMemory: bind key 4 at 0x007c9000 (pgoffset 1993) (II) intel(0): xf86BindGARTMemory: bind key 5 at 0x007d (pgoffset 2000) (II) intel(0): xf86BindGARTMemory: bind key 6 at 0x0500 (pgoffset 20480) (II) intel(0): xf86BindGARTMemory: bind key 7 at 0x0600 (pgoffset 24576) (II) intel(0): xf86BindGARTMemory: bind key 8 at 0x0900 (pgoffset 36864) (II) intel(0): Output configuration: (II) intel(0): Pipe A is on (II) intel(0): Display plane A is now enabled and connected to pipe A. (II) intel(0): Pipe B is off (II) intel(0): Display plane B is now disabled and connected to pipe B. (II) intel(0): Output VGA is connected to pipe A (II) intel(0): [drm] dma control initialized, using IRQ 21 (II) Configured Mouse: ps2EnableDataReporting: succeeded I'll try with the version from experimental next. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371857: i810 doesn't restore console properly with vga=ext.
I wrote: I'll try with the version from experimental next. I have tried with xserver-xorg-video-intel 2:2.0.0-5 from experimental (and still xorg-server 2:1.3.0.0.dfsg-6) This was not a success. X will not start at all. It says: (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: ISA (EE) No devices detected. Fatal server error: no screens found It looks like it's completely failing to perform the PCI scan. Complete log and xorg.conf below. -M- X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian Current Operating System: Linux xingu 2.6.21 #1 Thu Jun 21 22:25:59 BST 2007 i686 Build Date: 01 June 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jul 1 22:28:47 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Vision Master Pro 451 (**) | |--Device Motherboard video (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Loader magic: 0x81e5f60 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (--) using VT number 7 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x00ff (0x100) IX[B] (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x00ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x00ff (0x100) IX[B] (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II)
Bug#371857: i810 doesn't restore console properly with vga=ext.
Brice Goglin wrote: About a year ago, you reported a bug in the Debian BTS regarding the i810 driver not restoring the console properly with vga=ext. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? Yes, I still see exactly the same behaviour, on the same machine. I'm running etch: xserver-xorg-core2:1.1.1-21 xserver-xorg-video-i810 2:1.7.2-4 The kernel is compiled from Debian 2.6.21-4 sources -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401920: sylpheed-claws-gtk2: doesn't start, crash instead
I can reproduce this bug (still with version 2.6.0-1). Changing my gtk2 theme from 'Delightfully-Smooth' to 'thinice' gets rid of the crash. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (989, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages sylpheed-claws-gtk2 depends on: ii libaspell15 0.60.4-4 GNU Aspell spell-checker runtime l ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcompfaceg1 1:1.5.2-4Compress/decompress images for mai ii libetpan10 0.48-1 mail handling library ii libglib2.0-02.12.4-2 The GLib library of C routines ii libgnomeprint2.2-0 2.12.1-7 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-02.12.1-4 GNOME 2.2 print architecture User ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libice6 1:1.0.1-2X11 Inter-Client Exchange library ii libldap22.1.30-13.3 OpenLDAP libraries ii libpango1.0-0 1.14.8-5 Layout and rendering of internatio ii libpisock9 0.12.1-5 library for communicating with a P ii libsm6 1:1.0.1-3X11 Session Management library ii libssl0.9.8 0.9.8c-4 SSL shared libraries Versions of packages sylpheed-claws-gtk2 recommends: ii aspell-en [aspell-dictionary] 6.0-0-5.1 English dictionary for GNU Aspell ii metamail 2.7-52 implementation of MIME ii sylpheed-claws-gtk2-i18n 2.6.0-1Locale data for Sylpheed-Claws GTK ii sylpheed-claws-scripts1.0.5-5Helper scripts for Sylpheed and Sy ii xfonts-100dpi 1:1.0.0-3 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-3 75 dpi fonts for X -- no debconf information === Stack trace: #0 0xb7509947 in raise () from /lib/tls/libc.so.6 No symbol table info available. #1 0xb750b0c9 in abort () from /lib/tls/libc.so.6 No symbol table info available. #2 0xb753f08a in __libc_message () from /lib/tls/libc.so.6 No symbol table info available. #3 0xb754694f in _int_free () from /lib/tls/libc.so.6 No symbol table info available. #4 0xb75469f2 in free () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb76f3b31 in g_free () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #6 0xb6bf6b1f in ?? () from /usr/lib/gtk-2.0/2.4.0/engines/libsmooth.so No symbol table info available. #7 0x082fb0f0 in ?? () No symbol table info available. #8 0x08380a00 in ?? () No symbol table info available. #9 0x0604 in ?? () No symbol table info available. #10 0xbfa3bd04 in ?? () No symbol table info available. #11 0x in ?? () No symbol table info available. === Output of valgrind --tool=memcheck --error-limit=no sylpheed-claws-gtk2 ==15648== Memcheck, a memory error detector. ==15648== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==15648== Using LibVEX rev 1658, a library for dynamic binary translation. ==15648== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==15648== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation framework. ==15648== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==15648== For more details, rerun with: -v ==15648== /home/mjw/.sylpheed-claws/sylpheedrc: fopen: No such file or directory ==15648== Syscall param write(buf) points to uninitialised byte(s) ==15648==at 0x43299B8: write (in /usr/lib/debug/libpthread-0.10.so) ==15648==by 0x4EF226E: _X11TransWrite (in /usr/lib/libX11.so.6.2.0) ==15648==by 0x4EF7BA5: (within /usr/lib/libX11.so.6.2.0) ==15648==by 0x4EF7C7A: _XReply (in /usr/lib/libX11.so.6.2.0) ==15648==by 0x4EDDF40: XInternAtom (in /usr/lib/libX11.so.6.2.0) ==15648==by 0x4EF1D9A: XSetWMProperties (in /usr/lib/libX11.so.6.2.0) ==15648==by 0x474D779: (within /usr/lib/libgdk-x11-2.0.so.0.800.20) ==15648==by 0x474FE81: gdk_window_new (in /usr/lib/libgdk-x11-2.0.so.0.800.20) ==15648==by 0x472DA65: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.800.20) ==15648==by 0x470C18E: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.800.20) ==15648==by 0x453684E: gtk_init_check (in /usr/lib/libgtk-x11-2.0.so.0.800.20) ==15648==by 0x4536883: gtk_init (in /usr/lib/libgtk-x11-2.0.so.0.800.20) ==15648== Address 0x524CEB8 is 128 bytes inside a block of size 16,384 alloc'd ==15648==at 0x401C6CA: calloc (vg_replace_malloc.c:279) ==15648==by 0x4EE2C8D: XOpenDisplay (in /usr/lib/libX11.so.6.2.0) ==15648==by 0x472D921: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.800.20) ==15648==by 0x470C18E: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.800.20) ==15648==by 0x453684E: gtk_init_check (in
Bug#372740: Sensord won't start with lm85 chip, on current Debian kernels.
Aurelien Jarno wrote: Yes, that's seems to be the problem. As I don't have such a chip, could you please try to add an ignore line for fan1_tach_mode, and also all other lines necessary to make sensord working? Then if you send me those lines, I will be able to fix the pacakge in consequence. Ah, I though I had tried that; I must have mistyped the ignore line. The full list I end up with is: ignore in5 ignore in6 ignore in7 ignore fan1_tach_mode ignore zone1_limit ignore zone1_hyst ignore zone1_range ignore zone1_critical ignore zone1_smooth ignore zone2_limit ignore zone2_hyst ignore zone2_range ignore zone2_critical ignore zone2_smooth ignore zone3_limit ignore zone3_hyst ignore zone3_range ignore zone3_critical ignore zone3_smooth ignore pwm1_spinup ignore pwm1_min ignore pwm1_freq ignore pwm1_min_ctl ignore pwm1_invert ignore pwm1_zone ignore pwm1_spinup_ctl ignore pwm2_spinup ignore pwm2_min ignore pwm2_freq ignore pwm2_min_ctl ignore pwm2_invert ignore pwm2_zone ignore pwm2_spinup_ctl ignore pwm3_spinup ignore pwm3_min ignore pwm3_freq ignore pwm3_min_ctl ignore pwm3_invert ignore pwm3_zone ignore pwm3_spinup_ctl and now sensord is running happily. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372740: Sensord won't start with lm85 chip, on current Debian kernels.
Package: sensord Version: 1:2.10.0-5 Sensord fails to start, logging the following messages: sensord: sensord started sensord: Chip: lm85-i2c-0-2e sensord: Adapter: SMBus I801 adapter at 2000 sensord: V1.5: 1.56 sensord: -in0_min: 1.42 sensord: -in0_max: 1.58 sensord: VCore: 1.20 sensord: -in1_min: 1.18 sensord: -in1_max: 1.32 sensord: V3.3: 3.30 sensord: -in2_min: 3.13 sensord: -in2_max: 3.47 sensord: V5: 5.05 sensord: -in3_min: 4.74 sensord: -in3_max: 5.26 sensord: V12: 12.25 sensord: -in4_min: 11.38 sensord: -in4_max: 12.62 sensord: CPU_Fan: 1239.00 sensord: -fan1_min: 1100.00 sensord: Error getting sensor data: lm85/fan1_tach_mode: Can't access procfs/sysfs file sensord: sensord failed (I have the following three lines in /etc/sensors.conf: ignore in5 ignore in6 ignore in7 without them, sensord fails earlier, saying sensord: Error getting sensor data: lm85/in5: Can't access procfs/sysfs file) As I understand it, fan1_tach_mode is from a part of the lm-sensors lm85 support which is not yet included in standard kernels. My kernel is compiled from Debian 2.6.16-14 sources. libsensors3 version: 1:2.10.0-5 libsysf2s version: 2.0.0-6 % ls -1 /sys/bus/i2c/devices/0-002e/ alarms bus cpu0_vid driver fan1_input fan1_min fan2_input fan2_min fan3_input fan3_min fan4_input fan4_min hwmon:hwmon0 in0_input in0_max in0_min in1_input in1_max in1_min in2_input in2_max in2_min in3_input in3_max in3_min in4_input in4_max in4_min name power pwm1 pwm1_auto_channels pwm1_auto_pwm_freq pwm1_auto_pwm_min pwm1_auto_pwm_minctl pwm1_enable pwm2 pwm2_auto_channels pwm2_auto_pwm_freq pwm2_auto_pwm_min pwm2_auto_pwm_minctl pwm2_enable pwm3 pwm3_auto_channels pwm3_auto_pwm_freq pwm3_auto_pwm_min pwm3_auto_pwm_minctl pwm3_enable temp1_auto_temp_crit temp1_auto_temp_max temp1_auto_temp_min temp1_auto_temp_off temp1_input temp1_max temp1_min temp2_auto_temp_crit temp2_auto_temp_max temp2_auto_temp_min temp2_auto_temp_off temp2_input temp2_max temp2_min temp3_auto_temp_crit temp3_auto_temp_max temp3_auto_temp_min temp3_auto_temp_off temp3_input temp3_max temp3_min uevent vrm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365736: /etc/init.d/slony1 status can falsely claim that daemons are running.
Package: slony1-bin Version: 1.1.5-1 If multiple slon daemon instances are configured, '/etc/init.d/slony1 status' reports that they are all running if any one of them is. I think this is caused by pidofproc() falling back to /bin/pidof when the pidfile for an instance does not exist. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326193: 'Incoming Work Group' not honoured for files named with a leading dot
Package: mailscanner
Version: 4.41.3-2
When mailscanner unpacks a message's attachments to make them available
to a virus scanner, it is supposed to set each file's group to the
configured 'Incoming Work Group'. This works for most attachments, but
if an attachment's filename begins with '.', the group is left as
mailscanner's primary group.
I presume the culprit is the following line in sub Explode in Message.pm:
chown $workarea-{uid}, $workarea-{gid}, glob $explodeinto/*
-M-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
