Bug#1010494: Re: Bug#1010494: RFS: usbrelay/1.0-1 -- USB HID relay driver
On Thu, May 05 2022, Tobias Frost wrote: > I've just gave you access rights to the repo on salsa, you should be able to > commit directly. > For the review and upload, an git reference or mentors upload will works both > for me. [...] > ✔. You can remove the "moreinfo" tag on this bug to signal that it is ready. Thanks Tobias. Yesterday, Jan offered me off-list to review and possibly upload the package, so I'll work with him and announce the result here. -Michal
Bug#1010494: Re: Bug#1010494: RFS: usbrelay/1.0-1 -- USB HID relay driver
Hi Jan and Tobias, @Jan good to hear from you. @Tobias, thanks for useful suggestions, see my reactions below. On Tue, May 03 2022, Jan Dittberner wrote: > As you might have guessed I'm busier than I would like and do usually need a > bit of time to respond. > > It would have been a good idea to contact me directly or via a wishlist bug > requesting a package update. I would have answered a wishlist bug > requesting an usbrelay upstream version update. The RFS came a bit > surprisingly. A short mail before starting the work would have been nice. I > had contact with Darryl Bond in the past and responded to his > requests. I apologize for not contacting you. I'm also in contact with Darryl Bond and I understood that he tried to contact you recently, but without success. It might have been my misunderstanding. > I would be happy to have a co-maintainer for usbrelay. @Michal you may add > yourself to Uploaders if you are interested in taking care of the package in > the future. Yes, I'll add myself. I'm using this software quite extensively and will be happy to help with packaging. @Jan How shall I proceed now? I've implemented the changes suggested by Tobias, but I need to test the result again with the hardware, for which I'll need a day or two. What then? Shall I upload a new version to mentors.d.o or send salsa merge request or both? > Please run lintian with the flags -i -v -E --pedantic to get the maximum > output. I recommend using pbuilder or sbuild to build in a clean > environment. I usually use sbuild in combination with git-buildpackage to do > my package builds. Both sbuild and pbuilder can lintian automatically after > a finished package build. Thanks. On Tue, May 03 2022, Tobias Frost wrote: > Ok, let me check the package: (I'm using the mentors version for the review) > - As said earlier, depending if you want a Team upload or follow the ITS, this > needs some entry in d/changelog, depending how you want to proceed... > - debian/io.github.darrylb123.usbrelay.metainfo.xml should possible brought > upstream, > shouldn't it (no need to change for the upload, but I guess this is > not debian specific) I'll send that (as well as other parts) upstream. I first wanted to know what changes are required for Debian and then send the final version upstream. > - d/rules >- (bikeshed -- no need to change) I'd prefer to use d/clean instead of > overriding the clean target; overrides are harder to maintain :) I didn't notice this possibility - it's definitely nicer! > - the man page is still in the debian directory -- it can be deleted as > it is now part of upstream. Upstream has usbrelay.1, I've added usbrelayd.8. As mentioned above, I'll send it upstream later. > - same for the udev rules. Upstream rules are slightly different - looser permissions, different group. > - d/usbrelay.install has a hard-coded architecture-dependent path. That will > break build on > archs != amd64. Good catch. > - d/postinst (and postrm): > The username is not correct. According to Debian Policy, 4.9.1, it must > start with an "_" > I guess also that you don't want/need a homedirectory for that uses, so its > $HOME > should be /nonexistent in this case. (Policy 9.2.3) > HOWEVER, let me suggest something else: > Use the DynamicUser feature from systemd: > > DynamicUser=yes > SupplementaryGroups=plugdev > > in the service file should make postint/postrm no longer be needed. That's definitely a good thing. > - Lintian has a few remarks: (my related remarks in brackets) > W: usbrelay source: no-nmu-in-changelog > W: usbrelay source: source-nmu-has-incorrect-version-number 1.0-1 > (will be gone once the changelog mentions the team upload or after the > salvage procedure is done) > I: usbrelay source: debian-rules-parses-dpkg-parsechangelog (line 20) > (see abovr) > I: usbrelay source: older-debian-watch-file-standard 3 > (could be updated to version 4, just s/3/4/ in the header) done > I: usbrelayd: package-supports-alternative-init-but-no-init.d-script > lib/systemd/system/usbrelayd.service > (can be ignored) > I: usbrelay source: patch-not-forwarded-upstream > debian/patches/0002-Mention-README-in-the-man-page.patch > I: usbrelay source: patch-not-forwarded-upstream debian/patches/gcc9.patch > (see below) > I: usbrelayd: systemd-service-file-missing-documentation-key > [lib/systemd/system/usbrelayd.service] > (possibly ask upstream to ammend the service file accordingly) Added, will send upstream later. > X: usbrelay source: debian-watch-does-not-check-gpg-signature [debian/watch] > (it would be nice if upstream could pgp-sign their tarballs, so noone can > tamper with them. > They sign their commits already, so a key would be available. Not > required for this upload.) I think that tarballs are created automatically by GitHub upon tagging the release. I guess that for that, we would need to generate tarballs locally, sign them and upload
Bug#1010494: RFS: usbrelay/1.0-1 -- USB HID relay driver
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for package "usbrelay": * Package name: usbrelay Version : 1.0-1 Upstream Author : Darryl Bond * URL : https://github.com/darrylb123/usbrelay * License : GPL-2+, CC-BY-SA-4.0 * Vcs : https://salsa.debian.org/wentasah/usbrelay Section : electronics The package is officially maintained by DD Jan Dittberner, but he seems to be no longer active, at least with this package. I contribute to the development of the upstream package and from time to time, users report problems that are caused by too old version of the package in the Debian archive. Having more recent version in Debian would be beneficial. The updated package is based on the version already in Debian and introduces two additional binary packages to cover new functionality provided by upstream. I tried to prepare the updated package as well as I can, but this is my first attempt to prepare official Debian packaging so I'm open to suggestions for improvement. The packaging is inspired by official documentation as well as by Fedora packaging, which was created recently by other contributors. The source builds the following binary packages: usbrelay - USB HID relay driver python3-usbrelay - Python bindings for USB HID relay driver usbrelayd - MQTT client for USB HID relay driver To access further information about this package, please visit the following URL: https://mentors.debian.net/package/usbrelay/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/u/usbrelay/usbrelay_1.0-1.dsc Changes since the last upload: usbrelay (1.0-1) unstable; urgency=medium . * New upstream version 1.0 * Drop "v" prefix from the watch file * Drop 0001-make-CFLAGS-LDFLAGS-and-CPPFLAGS-customizable.patch * Update gcc9.patch (Closes: Bug#916557) * Pass Debian package version to the build system * Use upstream man page rather than Debian one * Override lintian soname error * Add python3-usbrelay package * Add usbrelayd package providing interface to MQTT * Update udev rules * Bump debhelper compatibility to 13 (no changes) * Bump Standards-Version to 4.6.0 (no changes) * Update copyright information * Announce the hardware support using AppStream * Add usbrelayd(8) manpage * Fix spelling error Additional comments can be found in some commit messages at https://salsa.debian.org/wentasah/usbrelay/-/commits/master. Regards, -- Michal Sojka
Bug#1000389: certbot: Renewal failures are not reported to the administrator under systemd
Package: certbot Version: 1.12.0-2 Severity: normal Dear Maintainer, on systemd-based systems, certificate renewal is run via combination of systemd timer and service. When the service fails, the systemd service is marked as failed, but the administrator is not notified about that. I'd appreciate if the administrator is notified via email in the same way as with cron. I'm not sure what is the best way to implement this. The systemd-cron package provides cron-failure@.service and the services generated by that package contain "OnFailure=cron-failure@%i.service". Perhaps, something like this should be implemented even in the certbot package. -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages certbot depends on: ii debconf [debconf-2.0] 1.5.77 ii python33.9.2-3 ii python3-certbot1.12.0-2 certbot recommends no packages. Versions of packages certbot suggests: ii python-certbot-doc 1.12.0-2 ii python3-certbot-apache 1.10.1-1 pn python3-certbot-nginx -- debconf information: certbot/remove_live_certs: true
Bug#964906: Same problem here after bullseye upgrade
I experience this after upgrading to bullseye too. Based on my
investigations, the problem is a race between invocation of `btrfs
device scan` in initramfs and kernel block device detection. The scan
is run at the time, when only one of the devices needed for RAID1 has
been detected by the kernel. It appears that initramfs waits for the
root device to be detected by the kernel in `local_device_setup` but
this function is not aware that it needs to wait for both RAID1
devices. Specifically, I have `root=UUID=` on the kernel command
line and initramfs translates this to /dev/sdb2 via blkid. Initramfs
is not aware of the other needed device /dev/sda2.
If this happens to anybody, you can boot into your system as follows:
Boot with the following on the kernel command line:
break=premount
When the initramfs shell prompt appears wait a second and exit. By
that time all block devices will be detected and boot will proceed
normally.
To ensure that my system boots without manual intervention, I applied
the following workaround. I added
/etc/initramfs-tools/scripts/local-top/btrfs-raid1-wait file containing:
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
prereqs)
prereqs
exit 0
;;
esac
. /scripts/functions
while ! test -b /dev/sda2 || ! test -b /dev/sdb2; do
echo "Waiting for BTRFS RAID1 devices"
sleep 1
done
echo "Done"
Then the initramfs needs to be updated:
update-initramfs -k 5.10.0-8-amd64 -u
Bug#948513: auto-multiple-choice-common: Should depend on liblocale-codes-perl
On Tue, Jan 14 2020, Alexis Bienvenüe wrote: > Thanks for the report. > > Le jeudi 09 janvier 2020 à 17:22 +0100, Michal Sojka a écrit : >> I was able to get rid of it by manually installing >> liblocale-codes-perl so I think that auto-multiple-choice-common >> should depend on this package. > > That looks strange because auto-multiple-choice-common already depends > on liblocale-codes-perl: > >> Versions of packages auto-multiple-choice-common depends on: >> ii liblocale-codes-perl 3.62-1 I see. I generated the bug report after I installed the package manually and that's why it was listed as dependency. If I uninstall liblocale-codes-perl, the list of dependencies would look differently: Versions of packages auto-multiple-choice-common depends on: ii ghostscript 9.50~dfsg-5 ii imagemagick 8:6.9.10.23+dfsg-2.1+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+b2 ii libarchive-zip-perl 1.67-1 ii libclone-perl 0.43-2 ii libdbd-sqlite3-perl 1.64-1+b1 ii libdbi-perl 1.642-1+b2 ii libfile-mimeinfo-perl 0.29-1 ii libglib-object-introspection-perl 0.048-1 ii libgraphics-magick-perl 1.4+really1.3.34+hg16181-1 ii libgtk3-perl 0.036-1 ii liblocale-gettext-perl1.07-4 ii libperl5.22 [libio-compress-perl] 5.22.2-5 ii librsvg2-common 2.46.4-1 ii libtext-csv-perl 2.00-1 ii libxml-simple-perl2.25-1 ii libxml-writer-perl0.625-1 ii netpbm2:10.0-15.3+b2 ii perl [libio-compress-perl]5.30.0-9 ii perl-modules-5.22 [liblocale-codes-perl] 5.22.2-5 ii poppler-utils 0.71.0-6 ii tex-common6.13 ii texlive-fonts-extra 2019.20191208-1 ii texlive-fonts-recommended 2019.20191208-4 ii texlive-latex-base2019.20191208-4 ii texlive-latex-extra 2019.20191208-1 ii texlive-latex-recommended 2019.20191208-4 ii unzip 6.0-25 It can bee seen that liblocale-codes-perl is provided by perl-modules-5.22. That's because perl-modules-5.22 has the following dependencies: Replaces: liblocale-codes-perl (<< 3.34) Provides: liblocale-codes-perl Breaks: liblocale-codes-perl (<< 3.34) perl-modules-5.22 is a left-over package from older distributions (in Aptitude marked as "Obsolete"). If I uninstall it, liblocale-codes-perl is automatically installed and AMC works fine. So maybe, AMC should depend on liblocale-codes-perl (>= 3.34). Alternatively, conflicting with perl-modules-5.22 would also help, but this might force users to uninstall all (obsolete) packages depending on it, which is not good. So I guess the versioned dependency on liblocale-codes-perl is a better solution. Best regards, -Michal
Bug#948513: auto-multiple-choice-common: Should depend on liblocale-codes-perl
Package: auto-multiple-choice-common Version: 1.4.0-2 Severity: normal Dear Maintainer, when I run auto-multiple-choice, I get the following error: Can't locate Locale/Language.pm in @INC (you may need to install the Locale::Language module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/lib/AMC/perl/AMC-gui.pl line 43. BEGIN failed--compilation aborted at /usr/lib/AMC/perl/AMC-gui.pl line 43. I was able to get rid of it by manually installing liblocale-codes-perl so I think that auto-multiple-choice-common should depend on this package. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages auto-multiple-choice-common depends on: ii ghostscript 9.50~dfsg-5 ii imagemagick 8:6.9.10.23+dfsg-2.1+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+b2 ii libarchive-zip-perl 1.67-1 ii libclone-perl 0.43-2 ii libdbd-sqlite3-perl 1.64-1+b1 ii libdbi-perl 1.642-1+b2 ii libfile-mimeinfo-perl 0.29-1 ii libglib-object-introspection-perl 0.048-1 ii libgraphics-magick-perl 1.4+really1.3.33+hg16117-1 ii libgtk3-perl 0.036-1 ii liblocale-codes-perl 3.62-1 ii liblocale-gettext-perl1.07-4 ii libperl5.22 [libio-compress-perl] 5.22.2-5 ii librsvg2-common 2.46.4-1 ii libtext-csv-perl 2.00-1 ii libxml-simple-perl2.25-1 ii libxml-writer-perl0.625-1 ii netpbm2:10.0-15.3+b2 ii perl [libio-compress-perl]5.30.0-9 ii perl-modules-5.22 [liblocale-codes-perl] 5.22.2-5 ii poppler-utils 0.71.0-6 ii tex-common6.13 ii texlive-fonts-extra 2019.20191208-1 ii texlive-fonts-recommended 2019.20191208-4 ii texlive-latex-base2019.20191208-4 ii texlive-latex-extra 2019.20191208-1 ii texlive-latex-recommended 2019.20191208-4 ii unzip 6.0-25 Versions of packages auto-multiple-choice-common recommends: ii fonts-linuxlibertine 5.3.0-4 pn libemail-address-perl ii libemail-mime-perl1.946-1 pn libemail-sender-perl ii libfilesys-df-perl0.92-6+b5 pn libnet-cups-perl pn libopenoffice-oodoc-perl ii libsys-cpu-perl 0.61-2+b5 ii pdftk 2.02-5+b1 ii pdftk-java [pdftk]3.0.6-1 ii qpdf 9.1.0-1 ii sensible-utils0.0.12+nmu1 ii texlive-xetex 2019.20191208-4 auto-multiple-choice-common suggests no packages. -- no debconf information
Bug#939524: pylint: Emacs startup file refers to missing files
Package: pylint Version: 2.2.2-2 Severity: normal Dear Maintainer, the package installs /etc/emacs/site-start.d/50pylint.el, which setups hooks and autoloads referring to pylint.el, which is not included in the binary package. This causes Emacs failures when opening any *.py file. Could you please either remove 50pylint.el or include the missing *.el files in the package? Thank you. -Michal -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pylint depends on: ii python3 3.7.3-1 ii python3-astroid 2.1.0-2 ii python3-isort 4.3.4+ds1-1.1 ii python3-logilab-common 1.4.3-2 ii python3-mccabe 0.6.1-2 ii python3-setuptools 41.2.0-1 Versions of packages pylint recommends: ii python3-tk 3.7.4-3 Versions of packages pylint suggests: pn pylint-doc -- no debconf information
Bug#850795: libboost1.62-doc: Missing HTML documentation
Package: libboost1.62-doc Severity: normal Dear Maintainer, this package does not have any HTML files in /usr/share/doc/libboost1.62-doc/HTML directory. I consider this a bug, because libboost1.58-doc contains HTML documentation in /usr/share/doc/libboost1.58-doc/HTML/. Best regards -Michal Sojka -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#837895: lightdm-gtk-greeter: GUI does not run, black screen, on startup
Hi all, I'm still having this problem with current sid. When I added "active-monitor=0" to /etc/lightdm/lightdm-gtk-greeter.conf, as suggested in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785055, the problem disappeared. -Michal
Bug#820445: fp-utils-3.0.0: Breaks LaTeX installation
Package: fp-utils-3.0.0 Version: 3.0.0+dfsg-4 Severity: normal Dear Maintainer, this package breaks my LaTeX installation. When I compile my LaTex document, I get the following error: ! Package caption Error: For a successful cooperation we need at least version (caption)`2004/02/13 v1.2' of package listings, (caption)but only version (caption)`2002/04/01 1.0 (Carsten Heinz)' (caption)is available. The reason seems to be that fp-utils includes an old version of listings.sty package, which LaTeX finds before the version shipped in texlive-latex-recommended package. Best regards. -Michal -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fp-utils-3.0.0 depends on: ii fpc-source-3.0.0 3.0.0+dfsg-4 ii libc6 2.22-5 Versions of packages fp-utils-3.0.0 recommends: ii fp-compiler-3.0.0 3.0.0+dfsg-4 fp-utils-3.0.0 suggests no packages. -- no debconf information
Bug#797814: mosh: Cannot install in unstable
Package: mosh Version: 1.2.5-1 Severity: important Dear Maintainer, an attempt to install mosh in unstable results in this error message: The following packages have unmet dependencies: mosh : Depends: libprotobuf9 but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#785936: ghc-mod: Cannot be installed on unstable
Source: ghc-mod Version: 5.2.1.1-3 Severity: important Dear Maintainer, ghc-mode cannot be installed on unstable, because it depends on unavailable package ghc ( 7.6.3+). Best regards, -Michal -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772838: nginx: /etc/hosts is ignored during boot
Package: nginx
Version: 1.6.2-5
Severity: normal
Dear Maintainer,
I have the following in my nginx configuration:
server {
listen mylocalserver:80;
server_name mylocalserver;
# ...
}
and the following line in /etc/hosts:
127.0.1.2 mylocalserver
When nginx is started during boot it fails and the following appears
in the log:
Dec 11 14:25:25 steelpick nginx[1800]: nginx: [emerg] host not found in
mylocalserver:80 of the listen directive in
/etc/nginx/sites-enabled/mylocalserver:2
Dec 11 14:25:25 steelpick nginx[1800]: nginx: configuration file
/etc/nginx/nginx.conf test failed
When I start nginx manually (systemctl start nginx.service) after
logging in, it starts correctly. I would like nginx to start correctly
even during boot.
I tried to debug the problem a bit and the following is what I found.
I verified that nginx is started after networking.service, that
loopback interface is up and that `getent hosts mylocalserver` prints
the correct address when executed before nginx is started.
I also compared the strace output of the failed command
/usr/bin/strace /usr/sbin/nginx -t -q -g 'daemon on; master_process on;
The difference between strace of failed nginx invocation during boot
and manual invocation via systemctl is that during manual invocation
/etc/gai.conf is consulted, whereas during boot, it is not.
diff --git a/nginx.strace.fail.txt b/nginx.strace.ok.txt
index 9242fa7..1b0a561 100644
--- a/nginx.strace.fail.txt
+++ b/nginx.strace.ok.txt
[...]
open(/etc/resolv.conf, O_RDONLY|O_CLOEXEC) = 6
-fstat(6, {st_mode=S_IFREG|0644, st_size=86, ...}) = 0
-mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fc033c61000
-read(6, # Generated by NetworkManager\nse..., 4096) = 86
+fstat(6, {st_mode=S_IFREG|0644, st_size=147, ...}) = 0
+mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f63e868d000
+read(6, # Generated by NetworkManager\nse..., 4096) = 147
read(6, , 4096) = 0
close(6)= 0
-munmap(0x7fc033c61000, 4096)= 0
+munmap(0x7f63e868d000, 4096)= 0
open(/etc/hosts, O_RDONLY|O_CLOEXEC) = 6
fstat(6, {st_mode=S_IFREG|0644, st_size=969, ...}) = 0
-mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fc033c61000
+mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f63e868d000
read(6, 127.0.0.1\tlocalhost\n127.0.1.1\tst..., 4096) = 969
read(6, , 4096) = 0
close(6)= 0
-munmap(0x7fc033c61000, 4096)= 0
+munmap(0x7f63e868d000, 4096)= 0
+open(/etc/gai.conf, O_RDONLY|O_CLOEXEC) = 6
+fstat(6, {st_mode=S_IFREG|0644, st_size=2614, ...}) = 0
+fstat(6, {st_mode=S_IFREG|0644, st_size=2614, ...}) = 0
+mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f63e868d000
+read(6, # Configuration for getaddrinfo(..., 4096) = 2614
+read(6, , 4096) = 0
+close(6)= 0
+munmap(0x7f63e868d000, 4096)= 0
+futex(0x7f63e7331f64, FUTEX_WAKE_PRIVATE, 2147483647) = 0
+socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
+connect(6, {sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr(127.0.0.1)}, 16) = 0
+getsockname(6, {sa_family=AF_INET, sin_port=htons(59592),
sin_addr=inet_addr(127.0.0.1)}, [16]) = 0
+close(6)= 0
+socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 6
+connect(6, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6,
::1, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
+getsockname(6, {sa_family=AF_INET6, sin6_port=htons(42666),
inet_pton(AF_INET6, ::1, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0},
[28]) = 0
+close(6)= 0
open(/etc/nginx/fastcgi.conf, O_RDONLY) = 6
fstat(6, {st_mode=S_IFREG|0644, st_size=1034, ...}) = 0
pread(6, \nfastcgi_param SCRIPT_FILENAME ..., 1034, 0) = 1034
[...]
After this part the output differs even more. The failed invocation
queries external DNS server for mylocalserver (with negative
response), while the correct invocation obtains the correct address
from /etc/hosts. Note that the strace output shows that /etc/hosts is
read in both cases.
Another difference seen in the strace output is that the content of
/etc/resolv.conf is different. I do not think that this matters but
for completeness, I include both versions of resolv.conf as well.
During the failed invocation, the content is:
# Generated by NetworkManager
search felk.cvut.cz
nameserver 2001:718:2:1611:0:1:0:90
while during the correct one:
# Generated by NetworkManager
search feld.cvut.cz felk.cvut.cz
nameserver 147.32.192.2
nameserver
Bug#766788: libreoffice-writer: Crashes with stack smashing detected
On Po, říj 27 2014, Rene Engelhard wrote: On Mon, Oct 27, 2014 at 11:24:43AM +0100, Michal Sojka wrote: I can reproduce this in both unstable and testing (1:4.3.3~rc2~git20141011-1). I cannot reproduce this in the version And why are you then not marking it as such? How can I do that next time? https://www.debian.org/Bugs/Reporting does not mention how to mark multiple version. You add 1:4.3.3~rc2~git20141011-1 in Version: and the BTS then knows it also affect 1:4.3.3~rc2-1 (see [1]) from libreoffice.org (LibreOffice_4.3.2_Linux_x86-64_deb.tar.gz). And with 4.3.3 rc1? (Or rc2 which would be in the next days) You right now compare a 4.3.2 with a -between-4.3.3-rc1-and-rc2 or 4.3.3 rc2 ;) After the crash the following information appears on the terminal: *** stack smashing detected ***: /usr/lib/libreoffice/program/soffice.bin terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x72faf)[0x7fdd44a1ffaf] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fdd44aa30a7] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7fdd44aa3070] But given it runs into the fortify functions it probably won't appear in 4.3.3 rc1 upstream until it's a real crash also there; upstream doesn't use those hardening flags. I was able to reproduce this in my own build of libreoffice. Any hint But probably without hardening or with? With. I run eval $(dpkg-buildflags --export=sh) which corresponds to export CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security export CPPFLAGS=-D_FORTIFY_SOURCE=2 export CXXFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security export FCFLAGS=-g -O2 -fstack-protector-strong export FFLAGS=-g -O2 -fstack-protector-strong export GCJFLAGS=-g -O2 -fstack-protector-strong export LDFLAGS=-Wl,-z,relro export OBJCFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security export OBJCXXFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security before compiling. Same backtrace or something else? Probably the same, but with more information: #0 0x003e6d435077 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x003e6d436458 in __GI_abort () at abort.c:89 #2 0x003e6d472fb4 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x3e6d56360b *** %s ***: %s terminated\n) at ../sysdeps/posix/libc_fatal.c:175 #3 0x003e6d4f60a7 in __GI___fortify_fail (msg=msg@entry=0x3e6d5635f3 stack smashing detected) at fortify_fail.c:31 #4 0x003e6d4f6070 in __stack_chk_fail () at stack_chk_fail.c:28 #5 0x73ea42c3 in HbLayoutEngine::layout (this=0x16cf0d0, rLayout=..., rArgs=...) at /home/wsh/src/libreoffice/vcl/generic/glyphs/gcach_layout.cxx:541 #6 0x73be0f13 in OutputDevice::ImplLayout (this=this@entry=0xf2bf60, rOrigStr=..., nMinIndex=nMinIndex@entry=0, nLen=nLen@entry=130, rLogicalPos=..., nLogicalWidth=nLogicalWidth@entry=0, pDXArray=0x0) at /home/wsh/src/libreoffice/vcl/source/outdev/text.cxx:1289 #7 0x73be151d in OutputDevice::GetTextBreak (this=0xf2bf60, rStr=..., nTextWidth=nTextWidth@entry=9638, nIndex=nIndex@entry=0, nLen=nLen@entry=130, nCharExtra=nCharExtra@entry=0) at /home/wsh/src/libreoffice/vcl/source/outdev/text.cxx:1336 #8 0x7fffd68dd2fb in SwFont::GetTxtBreak (this=0x16f2290, rInf=..., nTextWidth=nTextWidth@entry=9638) at /home/wsh/src/libreoffice/sw/source/core/txtnode/fntcache.cxx:2455 #9 0x7fffd6849b5f in SwTxtSizeInfo::GetTxtBreak (this=this@entry=0x7fff9b00, nLineWidth=nLineWidth@entry=9638, nMaxLen=nMaxLen@entry=130, nComp=nComp@entry=0) at /home/wsh/src/libreoffice/sw/source/core/text/inftxt.cxx:421 #10 0x7fffd6846aca in SwTxtGuess::Guess (this=this@entry=0x7fff8ca0, rPor=..., rInf=..., nPorHeight=optimized out) at /home/wsh/src/libreoffice/sw/source/core/text/guess.cxx:163 #11 0x7fffd688d5dd in SwTxtPortion::_Format (this=0x7fffe401b000, rInf=...) at /home/wsh/src/libreoffice/sw/source/core/text/portxt.cxx:303 #12 0x7fffd6863ded in SwTxtFormatter::BuildPortions (this=this@entry=0x7fff9d00, rInf=...) at /home/wsh/src/libreoffice/sw/source/core/text/itrform2.cxx:535 #13 0x7fffd6865155 in SwTxtFormatter::FormatLine (this=this@entry=0x7fff9d00, nStartPos=optimized out) at /home/wsh/src/libreoffice/sw/source/core/text/itrform2.cxx:1545 #14 0x7fffd6838957 in SwTxtFrm::FormatLine (this=this@entry=0x7fffdc112000, rLine=..., bPrev=bPrev@entry=true) at /home/wsh/src/libreoffice/sw/source/core/text/frmform.cxx:1126 #15 0x7fffd683e814 in SwTxtFrm::_Format (this=this@entry=0x7fffdc112000, rLine=..., rInf=..., bAdjust=bAdjust@entry=false) at /home/wsh/src/libreoffice/sw/source/core/text/frmform.cxx:1488 #16 0x7fffd683f7f9 in SwTxtFrm::_Format (this=this@entry=0x7fffdc112000, pPara=optimized out) at /home/wsh/src/libreoffice/sw/source/core/text
Bug#767167: gnome-control-center: Sound output device disappears after suspend/resume
Package: gnome-control-center Version: 1:3.14.1-1 1:3.14.0-1 Severity: normal Dear Maintainer, after fresh boot of my computer, output tab of gnome-control-center sound (GCCS) shows two output devices: HDMI/DisplayPort and LineOut. After suspend/resume, the LineOut device always disappears and sometimes (not always) no sound goes out of the LineOut device. The expected state is that both devices are still visible in GCCS and sound always goes from LineOut. In the no sound case (or when I select HDMI/DiplayPort manually in GCCS), there is no way to get sound out of LineOut device again by only using GCCS. It is, however, possible to use pavucontrol to restore the sound output, but the LineOut device is still missing in GCCS. The sound can be restored by going to the Configuration tab of pavucontrol and changing Profile of Built-in Audio from Digital Stereo (HDMI) Output + Analog Stereo Input to Analog Stereo Output (unplugged). Note that the LineOut device (known as Built-in Audio in pavucontrol) does not have HDMI output and HDMI does not appear in pavucontrol Profile list box before suspend/resume. Thank you. -Michal -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.37-3+b1 ii apg2.2.3.dfsg.1-2 ii colord 1.2.1-1+b1 ii desktop-file-utils 0.22-1 ii gnome-control-center-data 1:3.14.1-1 ii gnome-desktop3-data3.14.0-1 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-settings-daemon 3.14.0-2 ii gsettings-desktop-schemas 3.14.0-1 ii libaccountsservice00.6.37-3+b1 ii libatk1.0-02.14.0-1 ii libc6 2.19-11 ii libcairo-gobject2 1.12.16-5 ii libcairo2 1.12.16-5 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libcheese-gtk233.14.0-1 ii libcheese7 3.14.0-1 ii libclutter-1.0-0 1.20.0-1 ii libclutter-gtk-1.0-0 1.6.0-1 ii libcolord-gtk1 0.1.25-1.1+b1 ii libcolord2 1.2.1-1+b1 ii libcups2 1.7.5-5 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-6.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgl1-mesa-glx [libgl1] 10.3.1-1 ii libglib2.0-0 2.42.0-2 ii libgnome-bluetooth13 3.14.0-1 ii libgnome-desktop-3-10 3.14.0-1 ii libgoa-1.0-0b 3.14.0-1 ii libgoa-backend-1.0-1 3.14.0-1 ii libgrilo-0.2-1 0.2.11-2 ii libgtk-3-0 3.14.3-1 ii libgtop2-7 2.28.5-2 ii libibus-1.0-5 1.5.8-3 ii libkrb5-3 1.12.1+dfsg-10 ii libmm-glib01.4.0-1 ii libnm-glib-vpn10.9.10.0-3 ii libnm-glib40.9.10.0-3 ii libnm-gtk0 0.9.10.0-2 ii libnm-util20.9.10.0-3 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-01.36.8-2 ii libpolkit-gobject-1-0 0.105-7 ii libpulse-mainloop-glib05.0-13 ii libpulse0 5.0-13 ii libpwquality1 1.2.3-1 ii libsmbclient 2:4.1.11+dfsg-2 ii libsoup2.4-1 2.48.0-1 ii libupower-glib30.99.1-3 ii libwacom2 0.8-1 ii libx11-6 2:1.6.2-3 ii libxi6 2:1.7.4-1 ii libxml22.9.1+dfsg1-4 Versions of packages gnome-control-center recommends: ii cracklib-runtime 2.9.2-1 ii cups-pk-helper 0.2.5-2 ii gkbd-capplet 3.6.0-1 ii gnome-online-accounts 3.14.0-1 ii gnome-user-guide 3.14.0-1 ii gnome-user-share 3.14.0-1 ii iso-codes 3.56-1 ii libnss-myhostname 0.3-9 ii mesa-utils 8.2.0-1 ii mousetweaks3.12.0-1 ii network-manager-gnome 0.9.10.0-2 ii policykit-1-gnome 0.105-2 pn realmd none ii rygel 0.24.0-1 ii rygel-tracker 0.24.0-1 ii system-config-printer 1.4.6-1 Versions of packages gnome-control-center suggests: ii gstreamer1.0-pulseaudio 1.4.3-1+b1 ii libcanberra-gtk-module 0.30-2.1 ii libcanberra-gtk3-module 0.30-2.1 ii x11-xserver-utils7.7+3 -- 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#767167: Clarification
HDMI does not appear in pavucontrol Profile list box before suspend/resume. Sorry, the above sentence is not true. The rest of the bug report is (hopefully) correct. -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766788: libreoffice-writer: Crashes with stack smashing detected
On Sat, Oct 25 2014, Rene Engelhard wrote: found 766788 1:4.3.3~rc2~git20141011-1 severity 766788 normal thanks Hi, On Sat, Oct 25, 2014 at 09:00:37PM +0200, Michal Sojka wrote: LibreOffice Writer crashes after performing the following steps: 1. Start lowriter (when started from terminal, an error message can be seen, otherwise the crash is silent). 2. Press '[' and keep it pressed for several seconds. 3. After about one and half line is filled with '[', lowriter crashes. And that is important? I consider crashes as important bugs. In what way? Why would anyone do something like that in a document? I expected that if it crashes with '[', it might also crash with other text. But yes, currently, this is only my speculation. I can reproduce this in both unstable and testing (1:4.3.3~rc2~git20141011-1). I cannot reproduce this in the version And why are you then not marking it as such? How can I do that next time? https://www.debian.org/Bugs/Reporting does not mention how to mark multiple version. from libreoffice.org (LibreOffice_4.3.2_Linux_x86-64_deb.tar.gz). And with 4.3.3 rc1? (Or rc2 which would be in the next days) You right now compare a 4.3.2 with a -between-4.3.3-rc1-and-rc2 or 4.3.3 rc2 ;) After the crash the following information appears on the terminal: *** stack smashing detected ***: /usr/lib/libreoffice/program/soffice.bin terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x72faf)[0x7fdd44a1ffaf] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fdd44aa30a7] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7fdd44aa3070] But given it runs into the fortify functions it probably won't appear in 4.3.3 rc1 upstream until it's a real crash also there; upstream doesn't use those hardening flags. I was able to reproduce this in my own build of libreoffice. Any hint how to best debug this with gdb? Thanks -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766788: libreoffice-writer: Crashes with stack smashing detected
Package: libreoffice-writer Version: 1:4.3.3~rc2-1 Severity: important Dear Maintainer, LibreOffice Writer crashes after performing the following steps: 1. Start lowriter (when started from terminal, an error message can be seen, otherwise the crash is silent). 2. Press '[' and keep it pressed for several seconds. 3. After about one and half line is filled with '[', lowriter crashes. I can reproduce this in both unstable and testing (1:4.3.3~rc2~git20141011-1). I cannot reproduce this in the version from libreoffice.org (LibreOffice_4.3.2_Linux_x86-64_deb.tar.gz). After the crash the following information appears on the terminal: *** stack smashing detected ***: /usr/lib/libreoffice/program/soffice.bin terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x72faf)[0x7fdd44a1ffaf] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fdd44aa30a7] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7fdd44aa3070] /usr/lib/libreoffice/program/libvcllo.so(+0x471840)[0x7fdd405c1840] /usr/lib/libreoffice/program/libvcllo.so(+0x272f6a)[0x7fdd403c2f6a] /usr/lib/libreoffice/program/libvcllo.so(_ZNK12OutputDevice12GetTextBreakERKN3rtl8OUStringEliil+0x4d)[0x7fdd403c37bd] /usr/lib/libreoffice/program/../program/libswlo.so(+0x689b76)[0x7fdd12dbeb76] /usr/lib/libreoffice/program/../program/libswlo.so(+0x6191c3)[0x7fdd12d4e1c3] /usr/lib/libreoffice/program/../program/libswlo.so(+0x616563)[0x7fdd12d4b563] /usr/lib/libreoffice/program/../program/libswlo.so(+0x64eb5d)[0x7fdd12d83b5d] /usr/lib/libreoffice/program/../program/libswlo.so(+0x62eefc)[0x7fdd12d63efc] /usr/lib/libreoffice/program/../program/libswlo.so(+0x630123)[0x7fdd12d65123] /usr/lib/libreoffice/program/../program/libswlo.so(+0x609640)[0x7fdd12d3e640] /usr/lib/libreoffice/program/../program/libswlo.so(+0x60e8a4)[0x7fdd12d438a4] /usr/lib/libreoffice/program/../program/libswlo.so(+0x60f701)[0x7fdd12d44701] /usr/lib/libreoffice/program/../program/libswlo.so(+0x61094e)[0x7fdd12d4594e] /usr/lib/libreoffice/program/../program/libswlo.so(+0x536e93)[0x7fdd12c6be93] /usr/lib/libreoffice/program/../program/libswlo.so(+0x534a6a)[0x7fdd12c69a6a] /usr/lib/libreoffice/program/../program/libswlo.so(+0x56bba1)[0x7fdd12ca0ba1] /usr/lib/libreoffice/program/../program/libswlo.so(+0x56beba)[0x7fdd12ca0eba] /usr/lib/libreoffice/program/../program/libswlo.so(+0x56d9bd)[0x7fdd12ca29bd] /usr/lib/libreoffice/program/../program/libswlo.so(_ZN11SwViewShell13ImplEndActionEb+0x775)[0x7fdd12fb6f35] /usr/lib/libreoffice/program/../program/libswlo.so(_ZN11SwCrsrShell9EndActionEb+0x333)[0x7fdd12a82c43] /usr/lib/libreoffice/program/../program/libswlo.so(_ZN11SwEditShell12EndAllActionEv+0x52)[0x7fdd12bfb8a2] /usr/lib/libreoffice/program/../program/libswlo.so(_ZN11SwEditShell7Insert2ERKN3rtl8OUStringEb+0x154)[0x7fdd12be5514] /usr/lib/libreoffice/program/../program/libswlo.so(_ZN10SwWrtShell6InsertERKN3rtl8OUStringE+0x2af)[0x7fdd132d17cf] /usr/lib/libreoffice/program/../program/libswlo.so(+0xa1653f)[0x7fdd1314b53f] /usr/lib/libreoffice/program/../program/libswlo.so(+0xa1deae)[0x7fdd13152eae] /usr/lib/libreoffice/program/libvcllo.so(+0x1dec08)[0x7fdd4032ec08] /usr/lib/libreoffice/program/libvcllo.so(+0x1e155d)[0x7fdd4033155d] /usr/lib/libreoffice/program/libvclplug_gtklo.so(+0x587a2)[0x7fdd33c927a2] /usr/lib/libreoffice/program/libvclplug_gtklo.so(+0x59d13)[0x7fdd33c93d13] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_cclosure_marshal_VOID__STRINGv+0x80)[0x7fdd3be32ec0] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x10474)[0x7fdd3be30474] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x8e7)[0x7fdd3be4a057] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x52a)[0x7fdd3be4aefa] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_cclosure_marshal_VOID__STRINGv+0x80)[0x7fdd3be32ec0] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x10474)[0x7fdd3be30474] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x8e7)[0x7fdd3be4a057] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x52a)[0x7fdd3be4aefa] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1192a0)[0x7fdd333f02a0] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x119b7d)[0x7fdd333f0b7d] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x11ba03)[0x7fdd333f2a03] /usr/lib/libreoffice/program/libvclplug_gtklo.so(+0x5a0b4)[0x7fdd33c940b4] /usr/lib/libreoffice/program/libvclplug_gtklo.so(+0x5a2f5)[0x7fdd33c942f5] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x13295f)[0x7fdd3340995f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x145)[0x7fdd3be30245] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x21f3c)[0x7fdd3be41f3c] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xae5)[0x7fdd3be4a255] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7fdd3be4a9af] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x249adc)[0x7fdd33520adc]
Bug#764375: geximon: Attempt to unlock mutex that was not locked
Package: geximon Version: 0.7.7-2.1 Severity: important Dear Maintainer, I freshly installed geximon and run it from the command line. The result is the following error message: Attempt to unlock mutex that was not locked [1]3375 abort geximon No GUI windows appears, just the message. Best regards, -Michal -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages geximon depends on: ii python 2.7.8-1 ii python-gtk2 2.24.0-4 Versions of packages geximon recommends: ii exim4-base 4.84-2 ii sudo1.8.10p3-1 geximon 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#762275: Solution
Hi, I also have the same (or similar) problem. This is what I found. The solution that worked for me is at the end of the mail. # dpkg -i /var/cache/apt/archives/systemd_215-4_amd64.deb (Reading database ... 729731 files and directories currently installed.) Preparing to unpack .../systemd_215-4_amd64.deb ... Unpacking systemd (215-4) over (215-4) ... Setting up systemd (215-4) ... dpkg: error processing package systemd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.8.6-2) ... Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: systemd # dpkg -i -D2 /var/cache/apt/archives/systemd_215-4_amd64.deb (Reading database ... 729731 files and directories currently installed.) Preparing to unpack .../systemd_215-4_amd64.deb ... D02: fork/exec /var/lib/dpkg/info/systemd.prerm ( upgrade 215-4 ) D02: fork/exec /var/lib/dpkg/tmp.ci/preinst ( upgrade 215-4 ) Unpacking systemd (215-4) over (215-4) ... D02: fork/exec /var/lib/dpkg/info/systemd.postrm ( upgrade 215-4 ) D02: process_archive info installed /var/lib/dpkg/tmp.ci/postinst as /var/lib/dpkg/info/systemd.postinst D02: process_archive info installed /var/lib/dpkg/tmp.ci/md5sums as /var/lib/dpkg/info/systemd.md5sums D02: process_archive info installed /var/lib/dpkg/tmp.ci/conffiles as /var/lib/dpkg/info/systemd.conffiles D02: process_archive info installed /var/lib/dpkg/tmp.ci/triggers as /var/lib/dpkg/info/systemd.triggers D02: process_archive info installed /var/lib/dpkg/tmp.ci/preinst as /var/lib/dpkg/info/systemd.preinst D02: process_archive info installed /var/lib/dpkg/tmp.ci/prerm as /var/lib/dpkg/info/systemd.prerm D02: process_archive info installed /var/lib/dpkg/tmp.ci/postrm as /var/lib/dpkg/info/systemd.postrm D02: process_archive tmp.ci script/file '..' contains dot D02: process_archive tmp.ci script/file '/var/lib/dpkg/tmp.ci/control' is control D02: process_archive tmp.ci script/file '.' contains dot Setting up systemd (215-4) ... D02: fork/exec /var/lib/dpkg/info/systemd.postinst ( configure 208-8 ) dpkg: error processing package systemd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.8.6-2) ... D02: fork/exec /var/lib/dpkg/info/dbus.postinst ( triggered /usr/share/dbus-1/system-services /etc/dbus-1/system.d ) Processing triggers for man-db (2.6.7.1-1) ... D02: fork/exec /var/lib/dpkg/info/man-db.postinst ( triggered /usr/share/man ) Errors were encountered while processing: systemd # sh -x /var/lib/dpkg/info/systemd.postinst configure 208-8 + set -e + [ configure = triggered ] + dpkg --compare-versions 208-8 lt 214-1 + systemctl enable getty@tty1.service + systemctl enable remote-fs.target + dpkg --compare-versions 208-8 lt 204-1 + dpkg --compare-versions 208-8 lt 33-1 + dpkg --compare-versions 208-8 lt 204-9 + dpkg --compare-versions 208-8 lt 204-8 + dpkg --compare-versions 208-8 lt 40-1 + systemd-machine-id-setup + addgroup --quiet --system systemd-journal After running 'delgroup systemd-journal', it was possible install the package. -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762275: Solution
On Sat, Sep 27 2014, Michael Biebl wrote: Am 27.09.2014 um 13:08 schrieb Michal Sojka: + addgroup --quiet --system systemd-journal After running 'delgroup systemd-journal', it was possible install the package. With the amount of information from the original bug submitter, it's hard to tell if this is the same issue as yours. In your case, you apparently had an existing systemd-journal group, which was not a system group, so addgroup errors out. This is not a bug in the Debian package. Most likely you had created that group yourself in the past. Yes, that's right. It's a annoying that --quiet suppress the error message in this case. -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763055: adduser: --quiet should not suppress fatal error messages
Package: adduser Version: 3.113+nmu3 Severity: normal Dear Maintainer, according to the man page, --quiet is supposed to suppress only informational messages, not errors or warnings. However there are cases when addgroup returns a non-zero exit code without printing any message, for example, when the group to be created already exists with a different GID. I think that, at least, the following pieces of code should not have the if $verbose suffix. printf STDERR (gtx(The group `%s' already exists and is not a system group. Exiting.\n), $new_name) if $verbose; exit RET_OBJECT_ALREADY_EXISTS; printf STDERR (gtx(The group `%s' already exists, but has a different GID. Exiting.\n), $new_name) if $verbose; exit RET_OBJECT_ALREADY_EXISTS; See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762275#32. Best regards, -Michal -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages adduser depends on: ii debconf [debconf-2.0] 1.5.53 ii passwd 1:4.2-2+b1 ii perl-base 5.20.1-1 adduser recommends no packages. Versions of packages adduser suggests: ii liblocale-gettext-perl 1.05-8+b1 ii perl-modules5.20.1-1 -- debconf information: adduser/title: adduser/homedir-permission: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762275: Solution
On Sat, Sep 27 2014, Michael Biebl wrote: Am 27.09.2014 um 15:09 schrieb Michal Sojka: Yes, that's right. It's a annoying that --quiet suppress the error message in this case. Agreed. I think quiet should suppress non-fatal warnings/errors only, but not messages which will cause it to exit with non-zero return code. We added --quiet only because users were concerned / confused when they saw messages as reported in #759175, which are non-fatal. Michal, do you mind filing a bug report against adduser? No problem, it's at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763055 -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694861: #694861 - gnome-control-center: Wired options button is disabled when the network is misconfigured
On Mon, Apr 28 2014, althaser wrote: Hey Michal, Could you please still reproduce this issue with newer gnome-control-center version like 1:3.4.3.1-2 or 1:3.8.3-7 ? Hi, the problem is no longer present in 1:3.8.3-7. I think this bug can be closed. Thanks, -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681210: amtterm: SoL connection terminates with ERROR: redir_data: unknown r-buf 0x29
Hi, this problem is fixed upstream. See the top two commits at https://www.kraxel.org/cgit/amtterm/log/?h=0ece5135fef56dbd0d94957c334655a57adb7212. Can you please update the package to the upstream (unfortunately unreleased) version? Thank you, -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736911: python-couchdb: Configuration file is ignored by couchdb
Package: python-couchdb Version: 0.8-1 Severity: normal Dear Maintainer, configuration file /etc/couchdb/default.d/python-couchdb should have the .ini extension to not be ignored by couchdb. See the attached patch. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-couchdb depends on: ii libjs-jquery 1.7.2+dfsg-3 ii python 2.7.5-5 ii python-cjson 1.0.5-4+b1 ii python-simplejson 3.3.2-1 ii python-support 1.0.15 python-couchdb recommends no packages. Versions of packages python-couchdb suggests: ii couchdb 1.4.0-3wsh1 -- no debconf information From 967c47aaffa82243cf700aa879fdf58f2069001f Mon Sep 17 00:00:00 2001 From: Michal Sojka sojk...@fel.cvut.cz Date: Tue, 28 Jan 2014 08:47:46 +0100 Subject: [PATCH] Append .ini to the configuration file name couchdb ignores files without .ini extension. --- debian/extra/python-couchdb | 2 -- debian/extra/python-couchdb.ini | 2 ++ debian/install | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) delete mode 100644 debian/extra/python-couchdb create mode 100644 debian/extra/python-couchdb.ini diff --git a/debian/extra/python-couchdb b/debian/extra/python-couchdb deleted file mode 100644 index f201768..000 --- a/debian/extra/python-couchdb +++ /dev/null @@ -1,2 +0,0 @@ -[query_servers] -python=/usr/bin/couchpy diff --git a/debian/extra/python-couchdb.ini b/debian/extra/python-couchdb.ini new file mode 100644 index 000..f201768 --- /dev/null +++ b/debian/extra/python-couchdb.ini @@ -0,0 +1,2 @@ +[query_servers] +python=/usr/bin/couchpy diff --git a/debian/install b/debian/install index e7a9dce..e9f92e0 100644 --- a/debian/install +++ b/debian/install @@ -2,4 +2,4 @@ couchdb-dumpusr/bin/ couchdb-loadusr/bin/ couchpy usr/bin/ -debian/extra/python-couchdbetc/couchdb/default.d/ +debian/extra/python-couchdb.inietc/couchdb/default.d/ -- 1.8.5.2
Bug#728693: js2-mode: Package initialization is broken
Package: js2-mode Version: 0~20120726-3 Severity: important Dear Maintainer, the Debian-specific initialization of this package does not work (at least with emacs24) and makes the package unusable without additional user intervention. The problems are that the package is searched for in a wrong directory and that the appropriate autoloads are not defined. The attached patch fixes all those problems for me. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages js2-mode depends on: ii emacs23 [emacsen] 23.4+1-4.1 ii emacs24 [emacsen] 24.3+1-2 ii emacsen-common 2.0.5 js2-mode recommends no packages. js2-mode suggests no packages. -- Configuration Files: /etc/emacs/site-start.d/50js2-mode.el changed [not included] -- no debconf information diff --git a/debian/js2-mode.emacsen-startup b/debian/js2-mode.emacsen-startup index d89c8f1..b8ecbf5 100644 --- a/debian/js2-mode.emacsen-startup +++ b/debian/js2-mode.emacsen-startup @@ -8,11 +8,13 @@ (message Package js2-mode removed but not purged. Skipping setup.)) ((not (file-exists-p (concat /usr/share/ (symbol-name debian-emacs-flavor) - /site-lisp/debian-el/js2-mode/js2-mode.elc))) + /site-lisp/js2-mode/js2-mode.elc))) (message Package debian-el not fully installed. Skipping setup.)) (t (debian-pkg-add-load-path-item (concat /usr/share/ (symbol-name debian-emacs-flavor) /site-lisp/js2-mode)) + (autoload 'js2-minor-mode js2-mode) + (autoload 'js2-mode js2-mode) (add-to-list 'auto-mode-alist '(\\.js$ . js2-mode
Bug#722909: shotwell: Shotwell crashes on library updates
Package: shotwell
Version: 0.12.3-2
Severity: important
Tags: patch
Dear Maintainer,
Shotwell in Wheezy crashes on library updates, which renders this
version of package unusable for me. The attached upstream patch fixes
the problem for me. Would it be possible to include a patched version
in wheezy-updates?
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages shotwell depends on:
ii dbus-x11 1.6.8-1+deb7u1
ii libatk1.0-0 2.4.0-2
ii libc62.13-38
ii libcairo-gobject21.12.2-3
ii libcairo21.12.2-3
ii libexif120.6.20-3
ii libexiv2-12 0.23-1
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libgee2 0.6.4-2
ii libgexiv2-1 0.4.1-3
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libgomp1 4.7.2-5
ii libgphoto2-2 2.4.14-2
ii libgphoto2-port0 2.4.14-2
ii libgstreamer-plugins-base0.10-0 0.10.36-1.1
ii libgstreamer0.10-0 0.10.36-1.2
ii libgtk-3-0 3.4.2-6
ii libgudev-1.0-0 175-7.2
ii libjavascriptcoregtk-3.0-0 1.8.1-3.4
ii liblcms2-2 2.2+git20110628-2.2
ii libpango1.0-01.30.0-1
ii libraw5 0.14.6-2
ii librest-0.7-00.7.12-3
ii librsvg2-common 2.36.1-1
ii libsoup2.4-1 2.38.1-2
ii libsqlite3-0 3.7.13-1+deb7u1
ii libstdc++6 4.7.2-5
ii libunique-3.0-0 3.0.2-1
ii libwebkitgtk-3.0-0 1.8.1-3.4
ii libx11-6 2:1.5.0-1+deb7u1
ii libxml2 2.8.0+dfsg1-7+nmu1
ii shotwell-common 0.12.3-2
shotwell recommends no packages.
shotwell suggests no packages.
-- no debconf information
From: Lucas Beeler lu...@yorba.org
Subject: Replaces an assertion with a short-circuit return and a
debug message.
Origin: upstream, http://redmine.yorba.org/projects/shotwell/repository/revisions/18585950ca73cb21ee246cc608d3a193c4bbb085
Bug: http://redmine.yorba.org/issues/5155
Applied-Upstream: 0.14.0
---
src/DirectoryMonitor.vala |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/DirectoryMonitor.vala b/src/DirectoryMonitor.vala
index 8071afd..73c6a3d 100644
--- a/src/DirectoryMonitor.vala
+++ b/src/DirectoryMonitor.vala
@@ -507,8 +507,12 @@ public class DirectoryMonitor : Object {
}
protected virtual void internal_notify_file_discovered(File file, FileInfo info) {
-bool updated = files.update(file, info);
-assert(updated);
+if (!files.update(file, info)) {
+debug(DirectoryMonitor.internal_notify_file_discovered: %s discovered but not added to file map,
+file.get_path());
+
+return;
+}
notify_file_discovered(file, info);
}
--
1.7.10.4
Bug#679917: korganizer: cannot add ics calendar files
Hi, the workaround described by Stuart works for me. Thanks. -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694861: gnome-control-center: Wired options button is disabled when the network is misconfigured
Package: gnome-control-center Version: 1:3.4.2+git20121016.29d7c0-1 Severity: normal Dear Maintainer, when wired network is misconfigured, there is no way to fix the configuration using gnome-control-center, because the Options button is always disabled. In my case I selected Network - Wired - Options - IPv4 Settings - Method = Link-Local only. This rendered the wired network to be Disconnected (even though the cable was connected) and the Options button became disabled. There was no way to change the settings back using Gnome UI. I was able to fix it by using nm-connection-editor. This bug is similar to #653815 (Options button for wireless network), which already seems to be resolved. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.21-7 ii apg2.2.3.dfsg.1-2 ii desktop-file-utils 0.20-0.1 ii gnome-control-center-data 1:3.4.2+git20121016.29d7c0-1 ii gnome-desktop3-data3.4.2-1 ii gnome-icon-theme 3.4.0-2 ii gnome-icon-theme-symbolic 3.4.0-2 ii gnome-menus3.4.2-4 ii gnome-settings-daemon 3.4.2+git20120925.a4c817-2 ii gsettings-desktop-schemas 3.4.2-2 ii libatk1.0-02.4.0-2 ii libc6 2.13-35 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libcanberra-gtk3-0 0.28-5 ii libcanberra0 0.28-5 ii libcheese-gtk213.4.2-2 ii libcheese3 3.4.2-2 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango0 1.10.2-6 ii libcogl9 1.10.2-6 ii libcolord1 0.1.21-1 ii libcomerr2 1.42.5-1 ii libcups2 1.5.3-2.4 ii libdbus-1-31.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libfontconfig1 2.9.0-7 ii libgcrypt111.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgnome-bluetooth10 3.4.2-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgnome-menu-3-0 3.4.2-4 ii libgnomekbd7 3.4.0.2-1 ii libgnutls262.12.20-2 ii libgoa-1.0-0 3.4.2-1 ii libgssapi-krb5-2 1.10.1+dfsg-2 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-4 ii libgtop2-7 2.28.4-3 ii libjson-glib-1.0-0 0.14.2-1 ii libk5crypto3 1.10.1+dfsg-2 ii libkrb5-3 1.10.1+dfsg-2 ii libnm-glib40.9.4.0-6 ii libnm-gtk0 0.9.4.1-2 ii libnm-util20.9.4.0-6 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libpolkit-gobject-1-0 0.105-1 ii libpulse-mainloop-glib02.0-6 ii libpulse0 2.0-6 ii libsocialweb-client2 0.25.20-2 ii libupower-glib10.9.17-1 ii libwacom2 0.6-1 ii libx11-6 2:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxdamage11:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.1-1 ii libxklavier16 5.2.1-1 ii libxml22.8.0+dfsg1-6 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.3-2 ii gnome-online-accounts 3.4.2-1 ii gnome-session 3.4.2.1-3 ii gnome-user-guide 3.4.2-1+build1 ii iso-codes 3.40-1 ii mesa-utils 8.0.1-2+b3 ii mousetweaks3.4.2-1 ii policykit-1-gnome 0.105-2 Versions of packages gnome-control-center suggests: ii gnome-screensaver 3.4.1-1 ii gstreamer0.10-pulseaudio 0.10.31-3+nmu1 ii libcanberra-gtk-module0.28-5 ii x11-xserver-utils 7.7~3 ii xscreensaver 5.15-3 -- 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#693894: gnome-terminal: wrapper script does not handle -x option
Package: gnome-terminal
Version: 3.4.1.1-2
Severity: normal
Dear Maintainer,
gnome-terminal.wrapper does not handler -x option. This option is used by
nautilus-open-terminal package; in my case it runs x-terminal-emulator -x
The attached patch fixes the problem for me.
Best regards,
-Michal
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5.4 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-terminal depends on:
ii gconf-service 3.2.5-1+build1
ii gnome-terminal-data3.4.1.1-2
ii gsettings-desktop-schemas 3.4.2-2
ii libatk1.0-02.4.0-2
ii libc6 2.13-37
ii libgconf-2-4 3.2.5-1+build1
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-3
ii libgtk-3-0 3.4.2-4
ii libice62:1.0.8-2
ii libpango1.0-0 1.30.0-1
ii libsm6 2:1.2.1-2
ii libvte-2.90-9 1:0.32.2-1
ii libx11-6 2:1.5.0-1
Versions of packages gnome-terminal recommends:
ii dbus-x11 1.6.8-1
ii gvfs 1.12.3-1+b1
ii yelp 3.4.2-1+b1
gnome-terminal suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/bin/gnome-terminal.wrapper (from gnome-terminal
package)
diff --git a/debian/gnome-terminal.wrapper b/debian/gnome-terminal.wrapper
index ef3b75f..28c68d1 100644
--- a/debian/gnome-terminal.wrapper
+++ b/debian/gnome-terminal.wrapper
@@ -69,6 +69,11 @@ while ($opt = shift(@ARGV))
}
last;
}
+elsif ($opt eq '-x')
+{
+ push(@args, '-x', @ARGV);
+ last;
+}
elsif ($opt eq '-h' || $opt eq '--help')
{
push(@args, '--help');
Bug#693894: gnome-terminal: wrapper script does not handle -x option
On Wed, Nov 21 2012, Simon McVittie wrote: reassign 693894 nautilus-open-terminal retitle 693894 runs x-terminal-emulator with non-Policy option -x tags 693894 - patch thanks On 21/11/12 14:22, Michal Sojka wrote: gnome-terminal.wrapper does not handler -x option. This option is used by nautilus-open-terminal package; in my case it runs x-terminal-emulator -x nautilus-open-terminal shouldn't be doing that, so I'm reassigning this bug there. x-terminal-emulator isn't guaranteed to support the -x option, only -e and -T (Policy 11.8.3). In particular, -x won't work if your x-terminal-emulator points to xterm. As noted in #457846 and #488974, gnome-terminal's -x option is a nicer command-line interface than xterm -e, but it's non-standard. If n-o-t can't be adapted to work with any Policy-compliant x-terminal-emulator, hard-coding gnome-terminal (the real one, not the wrapper) would also work, with some loss of functionality (inability to launch a configured non-GNOME terminal that happens to support -x in a way compatible with gnome-terminal). Michal, which version of nautilus-open-terminal are you running? I'm running 0.19-2+b1. Thanks, -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689411: ess: ESS breaks filladapt in non-ESS modes
Package: ess Version: 12.09-1 Severity: normal Dear Maintainer, My .emacs contains (require 'filladapt) - filladapt is from emacs-goodies-el package. After installing ess, filladapt stopped working. This happens not only in ESS modes but also in other modes, which is especially annoying. When filladapt functionality is requested (M-q) the foollowing apears in *Messages* buffer: setq: Wrong number of arguments: #[(arg) ÂÃÄ \) [filladapt-inside-filladapt arg t filladapt-fill-paragraph fill-paragraph] 3 (/usr/share/emacs23/site-lisp/emacs-goodies-el/filladapt.elc . 10604) *P], 2 Steps to reproduce the problem: 1. Start emacs: emacs -q 2. M-x load-library filladapt RET 3. Open a text file: C-x C-f /tmp/test.txt RET 4. Invoke fill-paragraph: M-q I believe that the problem has something to do with advising fill-paragraph function with ess-roxy-fill-advice. I tried running (ad-deactive 'fill-paragraph) but it didn't help. The problem can be reproduced in both emacs23 and emacs24. Best regards, -Michal -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ess depends on: ii dpkg 1.16.8 ii emacs23 [emacsen] 23.4+1-4 ii emacs24 [emacsen] 24.2+1-1 ii install-info 4.13a.dfsg.1-10 ess recommends no packages. Versions of packages ess suggests: pn jags none pn pspp none ii r-base-core 2.15.1-5 pn xlispstatnone -- 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#682720: Emacs24 support
Hi,
the following patch should IMHO add support for emacs24 in auctex.
Cheers,
-Michal
diff --git a/debian/auctex.bug-script.eperl b/debian/auctex.bug-script.eperl
index 77689d0..856d144 100644
--- a/debian/auctex.bug-script.eperl
+++ b/debian/auctex.bug-script.eperl
@@ -32,7 +32,7 @@ cat 3 EOF
EOF
: # Default flavors: only GNU/Emacsen, XEmacs comes with its own AUCTeX ://
-FLAVORS=${*:-emacs23 emacs-snapshot}
+FLAVORS=${*:-emacs23 emacs24 emacs-snapshot}
for FLAVOR in ${FLAVORS}; do
if [ -x /usr/bin/${FLAVOR} ]; then
diff --git a/debian/auctex.emacsen-install.eperl
b/debian/auctex.emacsen-install.eperl
index 8e19656..7cfb97f 100644
--- a/debian/auctex.emacsen-install.eperl
+++ b/debian/auctex.emacsen-install.eperl
@@ -105,7 +105,7 @@ function do_update_auctex_elisp () {
case ${FLAVOR} in
(emacs)
;;
-(emacs23|emacs-snapshot)
+(emacs23|emacs24|emacs-snapshot)
do_install ${FLAVOR}
do_update_auctex_elisp ${FLAVOR}
;;
diff --git a/debian/auctex.triggers b/debian/auctex.triggers
index 4e97158..614a0af 100644
--- a/debian/auctex.triggers
+++ b/debian/auctex.triggers
@@ -1,3 +1,4 @@
interest /usr/share/texmf
interest /usr/share/texmf-texlive
interest auctex-install-emacs23
+interest auctex-install-emacs24
diff --git a/debian/control b/debian/control
index ca6585b..eaf2948 100644
--- a/debian/control
+++ b/debian/control
@@ -4,12 +4,12 @@ Section: tex
Maintainer: Davide G. M. Salvetti sa...@debian.org
Uploaders: OHURA Makoto oh...@debian.org
Standards-Version: 3.9.3
-Build-Depends-Indep: debhelper (= 8), emacs23, eperl, ghostscript,
po-debconf, tex-common, texlive-latex-base, texinfo, texi2html (=1.76)
+Build-Depends-Indep: debhelper (= 8), emacs23 | emacs24, eperl, ghostscript,
po-debconf, tex-common, texlive-latex-base, texinfo, texi2html (=1.76)
Homepage: http://www.gnu.org/software/auctex/
Package: auctex
Architecture: all
-Depends: emacs23, preview-latex-style, dpkg (= 1.15.4) | install-info,
${misc:Depends}
+Depends: emacs23 | emacs24, preview-latex-style, dpkg (= 1.15.4) |
install-info, ${misc:Depends}
Recommends: ghostscript, texlive-latex-recommended, xpdf | evince | evince-gtk
Suggests: catdvi, dvipng, lacheck
Breaks: emacspeak (= 17.0-1)
diff --git a/debian/update-auctex-elisp.eperl b/debian/update-auctex-elisp.eperl
index d01de69..003900d 100644
--- a/debian/update-auctex-elisp.eperl
+++ b/debian/update-auctex-elisp.eperl
@@ -42,7 +42,7 @@ while true; do
esac
done
: # Default flavors: only GNU, XEmacs comes with its own AUCTeX ://
-FLAVORS=${*:-'emacs23 emacs-snapshot'}
+FLAVORS=${*:-'emacs23 emacs24 emacs-snapshot'}
LOGMASK='/var/lib/auctex/%s/CompilationLog'
if [ -n ${_UPDATE_AUCTEX_ELISP_DAEMON_MODE} ]; then
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682720: The forgotten patch
tags 682720 patch
thanks
I forgot to attach the patch.
diff --git a/debian/auctex.postinst.eperl b/debian/auctex.postinst.eperl
index 5681e13..9376623 100644
--- a/debian/auctex.postinst.eperl
+++ b/debian/auctex.postinst.eperl
@@ -84,24 +84,24 @@ db_stop
case ${1} in
(triggered)
RUN_UPDATE_AUCTEX_ELISP=true
- while true; do
- case ${2} in
+ for trigger in ${2}; do
+ case ${trigger} in
('')
break
;;
: #Triggered by the Emacs install script ://
(auctex-install-*)
- FLAVORS=${FLAVORS}${FLAVORS:+' '}${2#auctex-install-}
+ FLAVORS=${FLAVORS}${FLAVORS:+ }${trigger#auctex-install-}
shift
;;
: #New (La)TeX macros: need to rescan for all flavors ://
(/*)
- FLAVORS=${FLAVORS}${FLAVORS:+' '}all
+ FLAVORS=${FLAVORS}${FLAVORS:+ }all
shift
;;
(*)
echo 2 ${PROGNAME}: \
- Unsupported trigger: ${2}
+ Unsupported trigger: ${trigger}
exit 1
;;
esac
--
1.7.10.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686366: auctex: Wrong trigger iteration and quoting
Package: auctex Version: 11.86-10.1 Severity: normal Dear Maintainer, triggers are passed to the maintainer script as a single argument. Therefore it is not possible to iterate over them with 'shift'. The attached patch changes the iteration loop type from while to for. It also fix incorrect quoting in adding space delimiter. The same kind of problem is reported in #675752, but the patch attached there does not replace all instances of the errornous code. Regards, -Michal -- Package-specific info: Content of '/usr/share/emacs/site-lisp/auctex' d41d8cd98f00b204e9800998ecf8427e /usr/share/emacs/site-lisp/auctex/.nosearch 3366a99dd44e27fa57e0bcc130c4fa1c /usr/share/emacs/site-lisp/auctex/bib-cite.el 5e59995360ee103714cbb9c827362002 /usr/share/emacs/site-lisp/auctex/context-en.el 1829a4905363692bf8eee2c451e0274a /usr/share/emacs/site-lisp/auctex/context-nl.el 19918a10a7209a5c5634ba6bd3028951 /usr/share/emacs/site-lisp/auctex/context.el 762c149dfbb34fd320b76af25f2af63e /usr/share/emacs/site-lisp/auctex/font-latex.el f176261b5a5511cbe1401ee72ffb8947 /usr/share/emacs/site-lisp/auctex/images/amstex.xpm d33121019448617a3ad3bcafdeb8db40 /usr/share/emacs/site-lisp/auctex/images/bibtex.xpm 1a43d6438010bceb374ab0a5f2bd05a8 /usr/share/emacs/site-lisp/auctex/images/dropdown.xpm 41f1ae0341ae2e307d92a7b8b815f868 /usr/share/emacs/site-lisp/auctex/images/dvipdf.xpm 2e4b8669b0168f32247411be3f999437 /usr/share/emacs/site-lisp/auctex/images/dvips.xpm 55f7600cadc3a209e94bacf6bbc42a7c /usr/share/emacs/site-lisp/auctex/images/error.xpm c29ad797273fd27201a40bd939a95fe0 /usr/share/emacs/site-lisp/auctex/images/exec.xpm 79b958849511c67d6b13ef9f5b3673e8 /usr/share/emacs/site-lisp/auctex/images/execbibtex.xpm a8570e26e9f96b6f527cdbe218d6c55f /usr/share/emacs/site-lisp/auctex/images/execdvips.xpm e647bc601aef2dc71b134a989df1adff /usr/share/emacs/site-lisp/auctex/images/execerror.xpm 4610ec6133f89ceb441c43dfee077361 /usr/share/emacs/site-lisp/auctex/images/execpdftex.xpm c9cd1fc9fe4fd122cbf900fae654a67b /usr/share/emacs/site-lisp/auctex/images/exectex.xpm 6a6b9af945d4735f048ea8e475f8d9b8 /usr/share/emacs/site-lisp/auctex/images/execviewdvi.xpm 466466f6d1867510b058a9c184ffce5d /usr/share/emacs/site-lisp/auctex/images/execviewpdf.xpm 39d8ccaffb40b0c118e000f45272db05 /usr/share/emacs/site-lisp/auctex/images/execviewps.xpm 6767e2583c668dcb47495197b9e8cb65 /usr/share/emacs/site-lisp/auctex/images/gv.xpm ff9c61ef5148a0cacd5422d7c0d99396 /usr/share/emacs/site-lisp/auctex/images/jumpdvi.xpm ece6608586b591f50f20d17cdb316a1c /usr/share/emacs/site-lisp/auctex/images/ltx-symb-turn-off.xpm b1f10de33dcf1b5ca9ac6155c13683a3 /usr/share/emacs/site-lisp/auctex/images/ltx-symb-turn-on.xpm 44e35faa18ab34f3c13ac3b0082bcc47 /usr/share/emacs/site-lisp/auctex/images/pdftex.xpm 84673eb20ac3be7bf0eb4e84e23e828f /usr/share/emacs/site-lisp/auctex/images/prverr16.xpm 59e6a0dddb00ab16c4209a2e4c6e283d /usr/share/emacs/site-lisp/auctex/images/prverr20.xpm 30dc2ada41625cb24ea459bd62f7386c /usr/share/emacs/site-lisp/auctex/images/prverr24.xbm 225929f8131bdd7b9b8207494a59619a /usr/share/emacs/site-lisp/auctex/images/prverr24.xpm 0dac3d8eb00c902037cc5fa6a03e53e3 /usr/share/emacs/site-lisp/auctex/images/prvtex-cap-up.xpm 40feb30f80d3606f32ba54b57ba18af5 /usr/share/emacs/site-lisp/auctex/images/prvtex12.xbm e1b3c9d6a6eb6fb6f096736cdfc059cf /usr/share/emacs/site-lisp/auctex/images/prvtex12.xpm 32406fc4b893b48d2996c424f61ea238 /usr/share/emacs/site-lisp/auctex/images/prvtex16.xbm cc4101ee6a3ab6a1f4e9991b91b3ff0b /usr/share/emacs/site-lisp/auctex/images/prvtex16.xpm d4dbe057a8d3b2facd61cf7583c1e97c /usr/share/emacs/site-lisp/auctex/images/prvtex20.xpm f25ba1b984b095c9c561e5443f3d77a3 /usr/share/emacs/site-lisp/auctex/images/prvtex24.xbm 28ac0855d853f606dd91e3cfacaa8a14 /usr/share/emacs/site-lisp/auctex/images/prvtex24.xpm 6ce704103821329336489e990bc6f267 /usr/share/emacs/site-lisp/auctex/images/prvwrk12.xpm 5607f4e8bc0eb555206e6a3542205f45 /usr/share/emacs/site-lisp/auctex/images/prvwrk14.xpm 878a72cde3bb6f0ea6d586cff56e619c /usr/share/emacs/site-lisp/auctex/images/prvwrk16.xpm 41811748a97673381115957d42a6529b /usr/share/emacs/site-lisp/auctex/images/prvwrk20.xpm 254fc07db6a03a8a24f762135a403433 /usr/share/emacs/site-lisp/auctex/images/prvwrk24.xbm 9690511307f3693e6f28e4db93fdc58c /usr/share/emacs/site-lisp/auctex/images/prvwrk24.xpm e30a80ecb0711ceb42a2ca966ad74bbb /usr/share/emacs/site-lisp/auctex/images/pspdf.xpm 5cc696e2c69ae401c0c223d84d013c8e /usr/share/emacs/site-lisp/auctex/images/sep.xpm 861fc288565e624ce8b34c1fc42e3496 /usr/share/emacs/site-lisp/auctex/images/tex.xpm 338158cc358b16daf9b58ee54bd14bad /usr/share/emacs/site-lisp/auctex/images/view.xpm 8147722e0061799437edf36d4466e5ab
Bug#682720: SorryFcc: /home/wsh/mail/feld/Sent
Sorry, the patch should have been for #686366. -M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686366: The forgotten patch
tags 686366 patch
thanks
I forgot to attach the patch.
diff --git a/debian/auctex.postinst.eperl b/debian/auctex.postinst.eperl
index 5681e13..9376623 100644
--- a/debian/auctex.postinst.eperl
+++ b/debian/auctex.postinst.eperl
@@ -84,24 +84,24 @@ db_stop
case ${1} in
(triggered)
RUN_UPDATE_AUCTEX_ELISP=true
- while true; do
- case ${2} in
+ for trigger in ${2}; do
+ case ${trigger} in
('')
break
;;
: #Triggered by the Emacs install script ://
(auctex-install-*)
- FLAVORS=${FLAVORS}${FLAVORS:+' '}${2#auctex-install-}
+ FLAVORS=${FLAVORS}${FLAVORS:+ }${trigger#auctex-install-}
shift
;;
: #New (La)TeX macros: need to rescan for all flavors ://
(/*)
- FLAVORS=${FLAVORS}${FLAVORS:+' '}all
+ FLAVORS=${FLAVORS}${FLAVORS:+ }all
shift
;;
(*)
echo 2 ${PROGNAME}: \
- Unsupported trigger: ${2}
+ Unsupported trigger: ${trigger}
exit 1
;;
esac
--
1.7.10.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682720: Updated patch
This is an updated patch for emacs24 support. It turned out that
previously I sent the older version of the patch without the change in
debian/auctex.emacsen-startup.eperl.
Today is not my day. Sorry for the noise.
-Michal
---
debian/auctex.bug-script.eperl |2 +-
debian/auctex.emacsen-install.eperl |2 +-
debian/auctex.emacsen-startup.eperl |2 +-
debian/auctex.triggers |1 +
debian/control |4 ++--
debian/update-auctex-elisp.eperl|2 +-
6 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/debian/auctex.bug-script.eperl b/debian/auctex.bug-script.eperl
index 77689d0..856d144 100644
--- a/debian/auctex.bug-script.eperl
+++ b/debian/auctex.bug-script.eperl
@@ -32,7 +32,7 @@ cat 3 EOF
EOF
: # Default flavors: only GNU/Emacsen, XEmacs comes with its own AUCTeX ://
-FLAVORS=${*:-emacs23 emacs-snapshot}
+FLAVORS=${*:-emacs23 emacs24 emacs-snapshot}
for FLAVOR in ${FLAVORS}; do
if [ -x /usr/bin/${FLAVOR} ]; then
diff --git a/debian/auctex.emacsen-install.eperl
b/debian/auctex.emacsen-install.eperl
index 8e19656..7cfb97f 100644
--- a/debian/auctex.emacsen-install.eperl
+++ b/debian/auctex.emacsen-install.eperl
@@ -105,7 +105,7 @@ function do_update_auctex_elisp () {
case ${FLAVOR} in
(emacs)
;;
-(emacs23|emacs-snapshot)
+(emacs23|emacs24|emacs-snapshot)
do_install ${FLAVOR}
do_update_auctex_elisp ${FLAVOR}
;;
diff --git a/debian/auctex.emacsen-startup.eperl
b/debian/auctex.emacsen-startup.eperl
index 924e454..406b3e4 100644
--- a/debian/auctex.emacsen-startup.eperl
+++ b/debian/auctex.emacsen-startup.eperl
@@ -5,7 +5,7 @@
;;; form (unload-feature 'tex-site) (i.e., put that string into your
;;; ~/.emacs to disable AUCTeX completely).
-(if (member debian-emacs-flavor '(emacs23 emacs-snapshot))
+(if (member debian-emacs-flavor '(emacs23 emacs24 emacs-snapshot))
: # skip if removed and not purged ://
(if (file-exists-p /usr/share/emacs/site-lisp/auctex/tex.el)
(progn
diff --git a/debian/auctex.triggers b/debian/auctex.triggers
index 4e97158..614a0af 100644
--- a/debian/auctex.triggers
+++ b/debian/auctex.triggers
@@ -1,3 +1,4 @@
interest /usr/share/texmf
interest /usr/share/texmf-texlive
interest auctex-install-emacs23
+interest auctex-install-emacs24
diff --git a/debian/control b/debian/control
index ca6585b..eaf2948 100644
--- a/debian/control
+++ b/debian/control
@@ -4,12 +4,12 @@ Section: tex
Maintainer: Davide G. M. Salvetti sa...@debian.org
Uploaders: OHURA Makoto oh...@debian.org
Standards-Version: 3.9.3
-Build-Depends-Indep: debhelper (= 8), emacs23, eperl, ghostscript,
po-debconf, tex-common, texlive-latex-base, texinfo, texi2html (=1.76)
+Build-Depends-Indep: debhelper (= 8), emacs23 | emacs24, eperl, ghostscript,
po-debconf, tex-common, texlive-latex-base, texinfo, texi2html (=1.76)
Homepage: http://www.gnu.org/software/auctex/
Package: auctex
Architecture: all
-Depends: emacs23, preview-latex-style, dpkg (= 1.15.4) | install-info,
${misc:Depends}
+Depends: emacs23 | emacs24, preview-latex-style, dpkg (= 1.15.4) |
install-info, ${misc:Depends}
Recommends: ghostscript, texlive-latex-recommended, xpdf | evince | evince-gtk
Suggests: catdvi, dvipng, lacheck
Breaks: emacspeak (= 17.0-1)
diff --git a/debian/update-auctex-elisp.eperl b/debian/update-auctex-elisp.eperl
index d01de69..003900d 100644
--- a/debian/update-auctex-elisp.eperl
+++ b/debian/update-auctex-elisp.eperl
@@ -42,7 +42,7 @@ while true; do
esac
done
: # Default flavors: only GNU, XEmacs comes with its own AUCTeX ://
-FLAVORS=${*:-'emacs23 emacs-snapshot'}
+FLAVORS=${*:-'emacs23 emacs24 emacs-snapshot'}
LOGMASK='/var/lib/auctex/%s/CompilationLog'
if [ -n ${_UPDATE_AUCTEX_ELISP_DAEMON_MODE} ]; then
--
1.7.10.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661171: xdg-utils: xdg-open does not interpret %i and %c in .desktop files
Package: xdg-utils Version: 1.1.0~rc1+git20111210-6 Severity: normal Dear Maintainer, when I run xdg-open with PDF file, my pdf viewer (okular) is called with wrong arguments. This causes it to open two windows - one with the requesed pdf file and one which attempts to open file named %i. The latter attempt fails and I have to confirm the error message and close the unwanted window manually. This is annoying. Details: $ XDG_UTILS_DEBUG_LEVEL=5 xdg-open x.pdf DE generic Running mimetype -b /home/me/x.pdf Checking /home/me/.local/share//applications/mimeapps.list /home/me/.local/share:/usr/local/share/:/usr/share/ My /home/me/.local/share//applications/mimeapps.list contains the following line: application/pdf=kde4-okularApplication_pdf.desktop kde4-okularApplication_pdf.desktop contains 'Exec=okular %U %i -caption %c' When I run 'bash -x xdg-open x.pdf' the tail of the output is: ++ grep -E '^Exec(\[[^]=]*])?=' /usr/share//applications/kde4/okularApplication_pdf.desktop ++ cut -d= -f 2- ++ last_word ++ read first rest ++ echo '%U %i -caption %c' + arguments='%U %i -caption %c' ++ echo x.pdf ++ sed -e 's/[\\]/\\/g' + local sed_escaped_url=x.pdf ++ echo %U %i -caption '%c' ++ sed -e 's*%[fFuU]*x.pdf*g' + arguments_exec='x.pdf %i -caption %c' + '[' -x /usr/bin/okular ']' + grep -iq '%[fFuU]' + echo %U %i -caption '%c' + eval /usr/bin/okular 'x.pdf' %i -caption '%c' ++ /usr/bin/okular x.pdf %i -caption %c -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xdg-utils depends on no packages. Versions of packages xdg-utils recommends: ii libfile-mimeinfo-perl 0.16-1 ii libnet-dbus-perl 1.0.0-1+b1 ii libx11-protocol-perl 0.56-2 ii x11-utils 7.6+4 ii x11-xserver-utils 7.6+3 Versions of packages xdg-utils suggests: ii gvfs-bin 1.10.1-2 -- 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#606229: emacs: Please provide debugging symbols
Hi, any chance that emacs gets the -dbg package? Crashes are more and more frequent and without -dbg it is hard to debug them. -Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594295: Squeeze?
Hi all, I've just discovered ControlPersist option and found that it is not supported in Squeeze. Are there any chances to get these patches to a Squeeze point release? Thanks, Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612560: [compiz] Crashes with gitk
Package: compiz Version: 0.8.4-4 Severity: important Tags: patch Compiz crashes when gitk is running and one press Alt-Tab to switch applications. Details and solution can be found at https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/579112. The patch is available at http://git.compiz.org/compiz/core/commit/?h=compiz-0.8id=1bed3dbcea6473f84745ec7a1f936c4f5d3b3a01ss=1 and it is also included in upstream versions 0.8.6 and 0.9.0. Thanks Michal --- System information. --- Architecture: amd64 Kernel: Linux 2.6.37-amd64 Debian Release: wheezy/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.cz.debian.org 500 unstabledebian.pengutronix.de 500 unstabledeb.opera.com 500 testing dl.google.com 500 stable dl.google.com 1 experimentalftp.cz.debian.org --- Package information. --- Depends (Version) | Installed ===-+-= compiz-core(= 0.8.4-4) | 0.8.4-4 compiz-plugins (= 0.8.4-4) | 0.8.4-4 compiz-gtk (= 0.8.4-4) | 0.8.4-4 compiz-gnome (= 0.8.4-4) | 0.8.4-4 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== compizconfig-settings-manager| 0.8.4-2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600291: hal: Pressing Shift-Left generates incorrectly BrightnessDown
Package: hal
Version: 0.5.14-3
Severity: normal
When I put my laptop (HP 6710b) into a docking station and use
external keyboard, certain keyboard combinations (e.g. Shift-Left),
generate BrightnessDown keycode. When that happend and the external
keyboard switches to some strange mode where normal keys doesn't work
and arrows generates BrightnessDown even without shift. The external
keyboard starts working again only after I press Fn-F9/10 on the
internal laptop keyboard i.e. real brightnes down/up keys.
This happens only if I boot or resume the laptop in the docking
station. Everything works correctly when laptop is booted outside and
then it is put into the dock.
What follow are two different output from lshal which are (I hope)
relevant to the problem.
1) When there is the problem with external keyboard (keymap.data
contains e012:brightnessdown for two devices):
udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX0_port_logicaldev_input'
info.addons.singleton = {'hald-addon-input'} (string list)
info.capabilities = {'input', 'input.keyboard', 'input.keypad', 'input.keys',
'input.keymap', 'button'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX0_port'
(string)
info.product = 'AT Raw Set 2 keyboard' (string)
info.subsystem = 'input' (string)
info.udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX0_port_logicaldev_input'
(string)
input.device = '/dev/input/event9' (string)
input.keymap.data = {'e001:fn_esc', 'e009:battery', 'e00a:screenlock',
'e00b:camera', 'e00c:media', 'e00e:dvd', 'e031:help', 'e033:f23', 'e057:wlan',
'e012:brightnessdown', 'e017:brightnessup', 'e06e:switchvideomode',
'e008:presentation', 'e059:help'} (string list)
input.originating_device =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX0_port' (string)
input.product = 'AT Raw Set 2 keyboard' (string)
linux.device_file = '/dev/input/event9' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio1/input/input9/event9'
(string)
udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port'
info.linux.driver = 'atkbd' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042' (string)
info.product = 'i8042 KBD port' (string)
info.subsystem = 'serio' (string)
info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port'
(string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'serio' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio0' (string)
serio.description = 'i8042 KBD port' (string)
serio.id = 'serio0' (string)
udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input'
info.addons.singleton = {'hald-addon-input'} (string list)
info.capabilities = {'input', 'input.keyboard', 'input.keypad', 'input.keys',
'input.keymap', 'button'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port'
(string)
info.product = 'AT Translated Set 2 keyboard' (string)
info.subsystem = 'input' (string)
info.udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input'
(string)
input.device = '/dev/input/event4' (string)
input.keymap.data = {'e001:fn_esc', 'e009:battery', 'e00a:screenlock',
'e00b:camera', 'e00c:media', 'e00e:dvd', 'e031:help', 'e033:f23', 'e057:wlan',
'e012:brightnessdown', 'e017:brightnessup', 'e06e:switchvideomode',
'e008:presentation', 'e059:help'} (string list)
input.originating_device =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port' (string)
input.product = 'AT Translated Set 2 keyboard' (string)
linux.device_file = '/dev/input/event4' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio0/input/input4/event4'
(string)
2) When the external keyboard works correctly (e012:brightnessdown
appears only once):
udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX0_port'
info.parent = '/org/freedesktop/Hal/devices/platform_i8042' (string)
info.product = 'i8042 AUX0 port' (string)
info.subsystem = 'serio' (string)
info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX0_port'
(string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'serio' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio1' (string)
serio.description = 'i8042 AUX0 port' (string)
serio.id = 'serio1' (string)
udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port'
info.linux.driver = 'atkbd' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042' (string)
info.product = 'i8042 KBD port' (string)
info.subsystem = 'serio' (string)
info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port'
(string)
Bug#588450: [emacs23] M-x semantic-mode gives Failed to find version for newly installed cedet
Package: emacs23 Version: 23.2+1-2 Severity: normal I'm not able to use semantic-mode. Whenever I run semantic-mode, I get Failed to find version for newly installed cedet message. According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581648#10, I have uninstalled the standalone cedet related packages, but it didn't help. Thanks, Michal --- System information. --- Architecture: amd64 Kernel: Linux 2.6.34-1-amd64 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.cz.debian.org 500 unstabledebian.pengutronix.de 500 unstabledeb.opera.com 500 testing dl.google.com 500 stable dl.google.com 1 experimentalftp.cz.debian.org --- Package information. --- Depends(Version) | Installed -+-== emacs23-bin-common (= 23.2+1-2) | 23.2+1-2 libasound2 ( 1.0.18) | 1.0.23-1 libatk1.0-0 (= 1.29.3) | 1.30.0-1 libc6 (= 2.3) | 2.11.1-2 libcairo2 (= 1.2.4) | 1.8.10-4 libdbus-1-3 (= 1.1.1) | 1.2.24-1 libfontconfig1(= 2.8.0) | 2.8.0-2.1 libfreetype6 (= 2.2.1) | 2.3.11-1 libgconf2-4 (= 2.27.0) | 2.28.1-3 libgif4 (= 4.1.4) | 4.1.6-9 libglib2.0-0 (= 2.12.0) | 2.24.1-1 libgpm2 (= 1.20.4) | 1.20.4-3.3 libgtk2.0-0 (= 2.8.0) | 2.20.1-1 libice6 (= 1:1.0.0) | 2:1.0.6-1 libjpeg62| 6b-16.1 libm17n-0 (= 1.5.5) | 1.5.5-1 libncurses5(= 5.7+20100313) | 5.7+20100313-2 libotf0 (= 0.9.10) | 0.9.10-1 libpango1.0-0(= 1.14.0) | 1.28.0-1 libpng12-0 (= 1.2.13-4) | 1.2.43-1 librsvg2-2 (= 2.26.0) | 2.26.3-1 libsm6 | 2:1.1.1-1 libtiff4 | 3.9.2-3+b1 libx11-6 | 2:1.3.3-3 libxft2 ( 2.1.1) | 2.1.14-2 libxpm4 | 1:3.5.8-1 libxrender1 | 1:0.9.5-2 zlib1g (= 1:1.1.4) | 1:1.2.3.4.dfsg-3 Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== emacs23-common-non-dfsg| 23.2+1-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577745: Wrong load path in 50git-core.el
Package: git Version: 1:1.7.0.4-2 Severity: normal The load path should be changed from git-core to git. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31.12-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcurl3-gnutls 7.20.0-3+b1 Multi-protocol file transfer libra ii libdigest-sha1-perl 2.12-1 NIST SHA-1 message digest algorith ii liberror-perl 0.17-1 Perl module for error/exception ha ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii perl-modules5.10.1-12Core Perl modules ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages git recommends: ii less 436-1 pager program similar to more ii openssh-client [ssh-client] 1:5.4p1-2 secure shell (SSH) client, for sec ii patch 2.6-2 Apply a diff file to an original ii rsync 3.0.7-2fast remote file copy program (lik Versions of packages git suggests: pn git-arch none (no description available) ii git-cvs 1:1.7.0.4-2 fast, scalable, distributed revisi pn git-daemon-run none (no description available) ii git-doc 1:1.7.0.4-2 fast, scalable, distributed revisi ii git-email1:1.7.0.4-2 fast, scalable, distributed revisi ii git-gui 1:1.7.0.4-2 fast, scalable, distributed revisi ii git-svn 1:1.7.0.4-2 fast, scalable, distributed revisi ii gitk 1:1.7.0.4-2 fast, scalable, distributed revisi pn gitweb none (no description available) -- no debconf information From b565c79d78d9d60e6474f00944ac10db80c519fd Mon Sep 17 00:00:00 2001 From: Michal Sojka sojk...@fel.cvut.cz Date: Wed, 14 Apr 2010 08:53:32 +0200 Subject: [PATCH] Fix emacs load path --- debian/git.emacsen-startup |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/debian/git.emacsen-startup b/debian/git.emacsen-startup index 5e8df73..c7309b0 100644 --- a/debian/git.emacsen-startup +++ b/debian/git.emacsen-startup @@ -11,7 +11,7 @@ ;; From http://www.emacswiki.org/cgi-bin/wiki/Git (add-to-list 'load-path - /usr/share/doc/git-core/contrib/emacs + /usr/share/doc/git/contrib/emacs 'append) (autoload 'git-get-env-strings git nil) -- 1.7.0.4
Bug#577745: Wrong load path in 50git-core.el
On Wed, 14 Apr 2010, Michal Sojka wrote: Package: git Version: 1:1.7.0.4-2 Severity: normal The load path should be changed from git-core to git. I found that this change does not solve my problem - I want to be able to run git-blame-mode and it stopped to work after recent updates. Emacs support in git package is only enabled for Emacs 23 and it is claimed that git support is already present in Emacs 23.x, but apt-file search didn't find neither git.el nor git-blame.el in other package than git. emacs/changelog.Debian.gz doesn't mention any change regarding to git, so I do not know why it worked earlier and not now. If I disable the check for Emacs version in /etc/emacs/site-start.d/50git-core.el, everything work as I expect. Could this check be removed from the Debian package? Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577745: Wrong load path in 50git-core.el
On Wed, 14 Apr 2010, Jonathan Nieder wrote: reassign 576887 git merge 577745 576887 thanks Hi Michal, Michal Sojka wrote: I found that this change does not solve my problem - I want to be able to run git-blame-mode and it stopped to work after recent updates. Emacs support in git package is only enabled for Emacs 23 and it is claimed that git support is already present in Emacs 23.x, but apt-file search didn't find neither git.el nor git-blame.el in other package than git. Could you try the startup file at [1]? More generally, if you have any thoughts on the comments to http://bugs.debian.org/576887, that would be great. It looks like there is a fix there, but testing and confirmation is always welcome. Hi Jonathan, the file you pointed me to looks correctly, but I was not able to test it. It is necessary to replace all occurrences of 'git-core' with 'git' (which I did), but also the .el must be compiled and put to /usr/share/emacs*/site-lisp/git-core. The latter is done by the provided emacsen-install script, which must be invoked somehow during postinst. It seems that debhelper manages this automatically, but your debian/rules do not use debhelper and I don't know how to setup proper postinst. If you let me know how to do it, I'll test it. emacs/changelog.Debian.gz doesn't mention any change regarding to git, so I do not know why it worked earlier and not now. Did you upgraded emacs during that time? Yes. Thanks, Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558101: (no subject)
Hi,
I was also hit by this bug. Here are my findings:
The problem was caused by the value of TeX-command-list. In my case, the entry
for latex invocation was:
(LaTeX %l \%(mode)\\input{%t}\ TeX-run-TeX nil
(latex-mode doctex-mode)
:help Run LaTeX)
If I changed it to the following and it started to work.
(LaTeX %l %(mode) \\\input{%t}\ TeX-run-TeX nil
(latex-mode doctex-mode)
:help Run LaTeX)
However, the real problem was probably the presence of an old version of
/usr/share/emacs23/site-lisp/auctex/tex.elc. After deleting that file and
running emacs egain, the value magically changed to:
(LaTeX %`%l%(mode)%' %t TeX-run-TeX nil
(latex-mode doctex-mode)
:help Run LaTeX)
So, I reinstalled auctex to generate the .elc again and it seems to work now.
Michal
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550421: (no subject)
Hi, I was also hit by this bug. Since I do not need emacs21 anymore, simple uninstalling that (obsolete) package solved the problem. Best regards Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535815: [battery-stats] Please, support other than the first battery
Package: battery-stats
Version: 0.3.5-1
Severity: wishlist
Tags: patch
Hi,
on my laptop, the internal battery is detected as the second one. The first
battery, which is the only handled by battery-stats, is the external one. The
attached patch adds command line option to select which battery is monitored
by battery-stats-collector.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.30-amd64
Debian Release: squeeze/sid
500 unstableftp.cz.debian.org
500 unstabledeb.opera.com
--- Package information. ---
Depends (Version) | Installed
==-+-=
logrotate | 3.7.7-3
gnuplot (= 4.0.0) | 4.2.5-2
gzip(= 1.3.2) | 1.3.12-8
libacpi0 | 0.2-4
libapm1 (= 3.2.0-7) | 3.2.2-13
libc6 (= 2.2.5) | 2.9-13
Package's Recommends field is empty.
Package's Suggests field is empty.
From f21c4035cbfa256374e8bb6a60e83a4e4c870807 Mon Sep 17 00:00:00 2001
From: Michal Sojka sojk...@fel.cvut.cz
Date: Sat, 4 Jul 2009 21:16:45 +0200
Subject: [PATCH 1/2] Added an option to select which battery to monitor
---
src/battery-stats-collector.c | 48 +++-
1 files changed, 37 insertions(+), 11 deletions(-)
diff --git a/src/battery-stats-collector.c b/src/battery-stats-collector.c
index 52370a2..2e5a57e 100644
--- a/src/battery-stats-collector.c
+++ b/src/battery-stats-collector.c
@@ -42,6 +42,7 @@ static struct option long_options[] = {
{ syslog, no_argument, NULL, 's' },
{ flush, required_argument, NULL, 'F' },
{ ignore-missing-battery, no_argument, NULL, 'I' },
+{ battery-num, required_argument, NULL, 'b' },
{ NULL, 0, NULL, 0 }
};
@@ -58,6 +59,8 @@ static void show_usage(void);
static char *myname = battery-stats-collector;
static char *myversion = 0.3.3;
+static int battery_num = 0;
+
static int do_syslog = 0;
#define COMPLAIN(loglevel, args...) if (do_syslog) syslog(loglevel, ## args); \
else { fprintf(stderr,%s: , myname); fprintf(stderr, ##args); }
@@ -77,7 +80,7 @@ int main(int argc, char **argv)
int c;
char *end;
- c = getopt_long(argc, argv, o:i:Vh1sF:, long_options, option_index);
+ c = getopt_long(argc, argv, o:i:Vh1sF:b:, long_options, option_index);
if (c == -1)
break;
@@ -143,6 +146,21 @@ int main(int argc, char **argv)
}
break;
+ case 'b':
+ battery_num = strtol(optarg, end, 10);
+ if (*end != 0)
+ {
+ fprintf(stderr, %s: Invalid battery number '%s'\n, myname, optarg);
+ exit(2);
+ }
+
+ if (battery_num 0)
+ {
+ fprintf(stderr, %s: Invalid negative battery number '%s'\n, myname, optarg);
+ exit(2);
+ }
+ break;
+
default:
/* getopt_long will already have complained on stderr ... */
fprintf(stderr,%s: Try %s --help for options\n, myname, myname);
@@ -180,10 +198,12 @@ int main(int argc, char **argv)
switch(retval)
{
case SUCCESS:
- COMPLAIN(LOG_INFO, Number of batteries: %i.%s\n,
- libacpi_global-batt_count,
- libacpi_global-batt_count 1 ?
- Reading info from first battery only. : );
+ COMPLAIN(LOG_INFO, Number of batteries: %i.\n,
+ libacpi_global-batt_count);
+ if (libacpi_global-batt_count 1) {
+ COMPLAIN(LOG_INFO,
+ Reading info from battery %d only.\n, battery_num);
+ }
break;
case NOT_SUPPORTED:
COMPLAIN(LOG_WARNING, You have more than %i batteries.
@@ -371,16 +391,22 @@ static void apm_fulldump(struct apm_info *ai)
static void acpidump(FILE *output, const int ignore_missing_battery,
global_t *libacpi_global)
{
-int rc = read_acpi_batt(0);
+int rc;
+
+if (battery_num = libacpi_global-batt_count) {
+ COMPLAIN(LOG_ERR,Battery %d doesn't exist. The number of batteries is: %d.\n, battery_num, libacpi_global-batt_count);
+ return;
+}
+rc = read_acpi_batt(battery_num);
if (rc != SUCCESS)
{
- COMPLAIN(LOG_ERR,read_acpi_batt(0) failed with error code %d\n, rc);
+ COMPLAIN(LOG_ERR,read_acpi_batt(%d) failed with error code %d\n, battery_num, rc);
return;
}
-if (!batteries[0].present)
+if (!batteries[battery_num].present)
{
if (!ignore_missing_battery) {
- COMPLAIN(LOG_WARNING, Battery 0 absent\n);
+ COMPLAIN(LOG_WARNING, Battery %d absent\n, battery_num);
}
return;
}
@@ -392,10 +418,10 @@ static void acpidump(FILE *output, const int ignore_missing_battery,
return;
}
-check_and_write_log_line(output, batteries[0].percentage,
+check_and_write_log_line(output, batteries[battery_num].percentage,
(libacpi_global-adapt.ac_state == P_BATT) ? 2 :
((libacpi_global-adapt.ac_state == P_AC) ? 1 : 0),
- batteries[0].remaining_time);
+ batteries[battery_num].remaining_time);
}
#endif
--
1.6.3.1
Bug#520669: [acpi-support-base] CheckPolicy doesn't detect Power Devil in KDE4
Package: acpi-support-base Version: 0.109-11 Severity: normal When KDE4.2 is running, pressing power button switches the computer off regardless of settings in Power Management module under System settings. This is probably because KDE4 is not detected in CheckPolicy in /usr/share/acpi- support/policy-funcs. --- System information. --- Architecture: i386 Kernel: Linux 2.6.28.2 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.cz.debian.org 500 unstabledeb.opera.com 500 testing dl.google.com 500 stable dl.google.com 101 experimentalftp.cz.debian.org --- Package information. --- Depends(Version) | Installed -+-=== acpid (= 1.0.4) | 1.0.8-6 console-utilities| -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519782: [kdevelop] Menu items are missing (Cannot connect PluginController)
Package: kdevelop Version: 4:3.5.3-3 Severity: important After starting kdevelop, many menu items are missing. It is even not possible to create a new project. When started from terminal, the following message appears: QObject::connect: Cannot connect PluginController::loadingPlugin(const QString ) to (null)::message(const QString ) --- System information. --- Architecture: i386 Kernel: Linux 2.6.28.2 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.cz.debian.org 500 unstabledeb.opera.com 500 testing dl.google.com 500 stable dl.google.com 101 experimentalftp.cz.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== kdelibs4c2a (= 4:3.5.9) | 4:3.5.10.dfsg.1-1+b1 libacl1 (= 2.2.11-1) | 2.2.47-2 libapr1(= 1.2.7) | 1.3.3-3 libaprutil1 | 1.2.12+dfsg-8 libart-2.0-2 (= 2.3.18) | 2.3.20-2 libattr1(= 2.4.41-1) | 1:2.4.43-2 libaudio2 | 1.9.1-5 libc6 (= 2.3.6-6~) | 2.9-4 libdb4.6 | 4.6.21-13 libfam0 | 2.7.0-13.3 libfontconfig1 (= 2.4.0) | 2.6.0-3 libfreetype6 (= 2.3.5) | 2.3.7-2 libgcc1 (= 1:4.1.1) | 1:4.3.3-5 libice6 (= 1:1.0.0) | 2:1.0.5-1 libidn11 (= 0.5.18) | 1.12-1 libjpeg62 | 6b-14 libpcre3 (= 7.7) | 7.8-2 libpng12-0 (= 1.2.13-4) | 1.2.35-1 libqt3-mt (= 3:3.3.8b) | 3:3.3.8b-5+b1 libsm6| 2:1.1.0-2 libstdc++6 (= 4.2.1) | 4.3.3-5 libsvn1(= 1.5.0) | 1.5.6dfsg-1 libuuid1(= 1.05) | 1.41.3-1 libx11-6 | 2:1.2-1 libxcursor1( 1.1.2) | 1:1.1.9-1 libxext6 | 2:1.0.4-1 libxft2( 2.1.1) | 2.1.13-3 libxi6| 2:1.2.1-1 libxinerama1 | 2:1.0.3-2 libxrandr2| 2:1.3.0-1 libxrender1 | 1:0.9.4-2 libxt6| 1:1.0.5-3 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-13 kdevelop-data (= 4:3.5.3-3) | 4:3.9.83~svn891234-1 kdebase-bin | 4:4.2.1-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519696: [hplip] hp-systray at 100% CPU
Package: hplip
Version: 3.9.2-1
Severity: normal
Hi, this is additional information to closed bug #503723 and an upstream bug.
I've sent it upstream at https://bugs.launchpad.net/hplip/+bug/305807 and
sending the same information here for convenience of Debian users.
If I do strace -p
pid, I can see:
read(7, , 236) = 0
select(8, [7], [], [7], {1, 0}) = 1 (in [7], left {0, 97})
read(7, , 236) = 0
select(8, [7], [], [7], {1, 0}) = 1 (in [7], left {0, 97})
read(7, , 236) = 0
select(8, [7], [], [7], {1, 0}) = 1 (in [7], left {0, 97})
read(7, , 236) = 0
select(8, [7], [], [7], {1, 0}) = 1 (in [7], left {0, 97})
read(7, , 236) = 0
select(8, [7], [], [7], {1, 0}) = 1 (in [7], left {0, 97})
read(7, , 236) = 0
select(8, [7], [], [7], {1, 0}) = 1 (in [7], left {0, 97})
read(7, , 236) = 0
...
I used gdb to track it down:
(gdb) bt
#0 posix_read (self=0x0, args=0x83a1fcc) at ../Modules/posixmodule.c:6101
#1 0x080ced6a in PyEval_EvalFrameEx (f=0x8313ddc, throwflag=0) at
../Python/ceval.c:3612
#2 0x080d00c5 in PyEval_EvalCodeEx (co=0xb7b7f7b8, globals=0x8381acc,
locals=0x0, args=0x81790b8, argcount=2, kws=0x81790c0, kwcount=0,
defs=0x8383118, defcount=2, closure=0x0)
at ../Python/ceval.c:2875
#3 0x080ce9fc in PyEval_EvalFrameEx (f=0x8178f7c, throwflag=0) at
../Python/ceval.c:3708
#4 0x080d00c5 in PyEval_EvalCodeEx (co=0xb7f0ea88, globals=0xb7f5eacc,
locals=0xb7f5eacc, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0,
defcount=0, closure=0x0)
at ../Python/ceval.c:2875
#5 0x080d02d7 in PyEval_EvalCode (co=0xb7f0ea88, globals=0xb7f5eacc,
locals=0xb7f5eacc) at ../Python/ceval.c:514
#6 0x080ed71f in PyRun_FileExFlags (fp=0x816e008, filename=0xbfbb8b8d
/usr/bin/hp-systray, start=257, globals=0xb7f5eacc, locals=0xb7f5eacc,
closeit=1, flags=0xbfbb7548)
at ../Python/pythonrun.c:1273
#7 0x080ed9ea in PyRun_SimpleFileExFlags (fp=0x816e008,
filename=0xbfbb8b8d /usr/bin/hp-systray, closeit=1, flags=0xbfbb7548)
at ../Python/pythonrun.c:879
#8 0x08059357 in Py_Main (argc=1, argv=0xbfbb7614) at ../Modules/main.c:532
#9 0x08058722 in main (argc=0, argv=0xb7c75ec8) at ../Modules/python.c:23
The problematic place in python source is here:
(gdb) pyframe
/usr/share/hplip/hpdio.py (94): run
Since the read() reads a pipe and returns 0, probably the other end of
pipe was closed. The pipe is created at systray.py:122 and is used to
communicate with something called hpssd (see lines 134 and 141). So I
guess there is some problem with the hpssd, which is not correctly
handled in hpdio.py.
Regards
Michal Sojka
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.28.2
Debian Release: squeeze/sid
500 unstablewww.debian-multimedia.org
500 unstableftp.cz.debian.org
500 unstabledeb.opera.com
500 testing dl.google.com
500 stable dl.google.com
101 experimentalftp.cz.debian.org
--- Package information. ---
Depends (Version) | Installed
==-+-
libc6(= 2.3.6-6~) | 2.9-4
libcups2(= 1.3.8) | 1.3.9-15
libdbus-1-3 (= 1.0.2) | 1.2.12-1
libsane (= 1.0.11-3) | 1.0.19-26
libsnmp15 (= 5.4.1~dfsg) | 5.4.1~dfsg-12
libssl0.9.8 (= 0.9.8f-5) | 0.9.8g-15
libusb-0.1-4 (= 2:0.1.12) | 2:0.1.12-13
python( 2.6) | 2.5.4-2
python(= 2.5) | 2.5.4-2
python-support (= 0.7.1) | 0.8.7
python-dbus (= 0.80) | 0.83.0-1
python-imaging | 1.1.6-3
coreutils (= 5.1.0) | 7.1-2
lsb-base(= 3) | 3.2-20
adduser (= 3.34) | 3.110
cups (= 1.1.20) | 1.3.9-15
hplip-data ( 3.9.2) | 3.9.2-1
hplip-data( 3.9.2.1) | 3.9.2-1
--- Output from package bug script ---
error: NOT FOUND! This is a REQUIRED/RUNTIME ONLY dependency. Please make sure
that this dependency is installed before installing or running HPLIP.
HP Linux Imaging and Printing System (ver. 3.9.2)
Dependency/Version Check Utility ver. 14.1
Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling
the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper
dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball
has the proper dependencies installed to successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default
Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled
On Saturday 01 of March 2008 15:22:22 you wrote: ok, those two logs look perfect. Not a single Splashy related string or executing in them. can you try to edit /etc/default/splashy and change CHVT_TTY to 7 ? Great, this helped. Now, kdm starts properly. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled
On Wednesday 27 of February 2008 04:04:32 Luis Mondesi wrote: Can you change the first line of /etc/init.d/kdm and send us the output? The line should read: !#/bin/sh -x The output is in attachment. Please note that a new version of Splashy was released and /etc/lsb-base-logging.sh included here will address this issue. You can get the latest version of this script from our Git repository directly: http://git.debian.org/?p=splashy/splashy.git;a=blob_plain;f=scripts/lsb-bas e-logging.sh;hb=HEAD I've tried this script, but KDM didn't start as before. Shall I try to use the whole splashy from this repo? Michal + set -e + HEED_DEFAULT_DISPLAY_MANAGER=true + DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager + PATH=/bin:/usr/bin:/sbin:/usr/sbin + DAEMON=/usr/bin/kdm + PIDFILE=/var/run/kdm.pid + UPGRADEFILE=/var/run/kdm.upgrade + KDMRC=/etc/kde3/kdm/kdmrc + BACKGROUNDRC=/etc/kde3/kdm/backgroundrc + grep -q Theme=@@@ToBeReplacedByDesktopBase@@@ /etc/kde3/kdm/kdmrc + '[' -n '' ']' + '[' -n '' ']' + '[' -n '' ']' + '[' -n '' ']' + '[' -e /var/run/kdm.upgrade ']' + SSD_ARGS='--pidfile /var/run/kdm.pid --exec /usr/bin/kdm' + case $1 in + '[' -e /etc/X11/default-display-manager ']' + '[' true = true ']' ++ cat /etc/X11/default-display-manager + '[' /usr/bin/kdm '!=' /usr/bin/kdm ']' + echo -n 'Starting K Display Manager: kdm' Starting K Display Manager: kdm+ start-stop-daemon --start --quiet --pidfile /var/run/kdm.pid --exec /usr/bin/kdm -- + echo . . + exit 0 + set -e + HEED_DEFAULT_DISPLAY_MANAGER=true + DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager + PATH=/bin:/usr/bin:/sbin:/usr/sbin + DAEMON=/usr/bin/kdm + PIDFILE=/var/run/kdm.pid + UPGRADEFILE=/var/run/kdm.upgrade + KDMRC=/etc/kde3/kdm/kdmrc + BACKGROUNDRC=/etc/kde3/kdm/backgroundrc + grep -q Theme=@@@ToBeReplacedByDesktopBase@@@ /etc/kde3/kdm/kdmrc + '[' -n '' ']' + '[' -n '' ']' + '[' -n '' ']' + '[' -n '' ']' + '[' -e /var/run/kdm.upgrade ']' + SSD_ARGS='--pidfile /var/run/kdm.pid --exec /usr/bin/kdm' + case $1 in + echo -n 'Stopping K Display Manager: kdm' Stopping K Display Manager: kdm+ '[' '!' -f /var/run/kdm.pid ']' ++ cat /var/run/kdm.pid ++ tr -d '[:blank:]' + DAEMONPID=3870 + KILLCOUNT=1 + '[' '!' -e /var/run/kdm.upgrade ']' + start-stop-daemon --stop --quiet --pidfile /var/run/kdm.pid --exec /usr/bin/kdm + sleep 1 + '[' 1 -le 5 ']' + stillrunning ++ cat /proc/3870/cmdline + expr '' : /usr/bin/kdm + rm -f /var/run/kdm.pid /var/run/kdm.upgrade + false + break + stillrunning ++ cat /proc/3870/cmdline + expr '' : /usr/bin/kdm + rm -f /var/run/kdm.pid /var/run/kdm.upgrade + false + rm -f /var/run/kdm.upgrade + echo . . + exit 0
Bug#467078: initramfs-tools: Network configuration can't work with multiple interfaces
Package: initramfs-tools
Version: 0.85h
Severity: normal
Tags: patch
If I want several computers to boot from the same ramdisk (with NFS
root) and some computers have multiple network interfaces, the DEVICE
variable can't be set to a specific value (e.g. eth0). Ipconfig from
klibc supports a mode, where DHCP request is sent to all interfaces
and the one receiving the first DHCP offer is used. This perfectly
suits my needs, but it can't be used with initramfs scripts because
the interface name in not known in advance and the DEVICE variable is
set to something like ::.
I have used the following patch to solve it:
--- initramfs-tools-0.85h.orig/scripts/nfs 2008-02-22 21:47:43.0
+0100
+++ initramfs-tools-0.85h/scripts/nfs 2008-02-22 21:48:48.0 +0100
@@ -36,8 +36,9 @@
;;
esac
- # source relevant ipconfig output
- . /tmp/net-${DEVICE}.conf
+ # source ipconfig output (if DEVICE refers to multiple
+ # interfaces we don't know the exact name)
+ . /tmp/net-*.conf
# get nfs root from dhcp
if [ x${NFSROOT} = xauto ]; then
The bug is also present in unstable, but I didn't test this patch:
--- initramfs-tools-0.91e.orig/scripts/functions2008-02-22
20:15:06.0 +0100
+++ initramfs-tools-0.91e/scripts/functions 2008-02-22 20:20:10.0
+0100
@@ -302,6 +302,7 @@
;;
esac
- # source relevant ipconfig output
- . /tmp/net-${DEVICE}.conf
+ # source ipconfig output (if DEVICE refers to multiple
+ # interfaces we don't know the exact name)
+ . /tmp/net-*.conf
}
Please note, that Debian version of klibc-utils contains a bug (see
http://www.zytor.com/pipermail/klibc/2008-February/002209.html) so I
use a patched version.
Regards
Michal Sojka
-- Package-specific info:
-- /proc/cmdline
boot=NFS root=/dev/nfs nfsroot=147.32.86.9:/srv/diskless/debian,ro,tcp ro
-- /proc/filesystems
cramfs
-- lsmod
Module Size Used by
i915 17728 2
drm61332 3 i915
ipv6 226272 22
dm_snapshot15552 0
dm_mirror 19152 0
dm_mod 50232 2 dm_snapshot,dm_mirror
ide_disk 14848 2
ide_cd 36064 0
cdrom 32544 1 ide_cd
com20020_pci6460 0
com200204992 1 com20020_pci
arcnet 12428 2 com20020_pci,com20020
generic 4868 0 [permanent]
tsdev 7520 0
snd_intel8x0 30332 0
snd_ac97_codec 83104 1 snd_intel8x0
snd_ac97_bus2400 1 snd_ac97_codec
snd_pcm_oss38368 0
snd_mixer_oss 15200 1 snd_pcm_oss
snd_pcm68676 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 20996 1 snd_pcm
snd47012 6
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
shpchp 33024 0
soundcore 9248 1 snd
pci_hotplug28704 1 shpchp
ata_piix 13896 0
psmouse35016 0
parport_pc 32132 0
i2c_i8017468 0
rtc12372 0
serio_raw 6660 0
parport33256 1 parport_pc
piix9444 0 [permanent]
ide_core 110504 4 ide_disk,ide_cd,generic,piix
snd_page_alloc 10184 2 snd_intel8x0,snd_pcm
intel_rng 5088 0
i2c_core 19680 1 i2c_i801
libata 89396 1 ata_piix
pcspkr 3072 0
scsi_mod 124168 1 libata
floppy 53156 0
intel_agp 22204 1
agpgart29896 3 drm,intel_agp
evdev 9088 1
nfs 202828 3
lockd 54344 2 nfs
nfs_acl 3584 1 nfs
sunrpc138812 4 nfs,lockd,nfs_acl
e100 32232 0
3c59x 40360 0
mii 5344 2 e100,3c59x
ehci_hcd 28136 0
uhci_hcd 21164 0
usbcore 112644 3 ehci_hcd,uhci_hcd
thermal13608 0
processor 28840 1 thermal
fan 4804 0
unionfs68740 1
sky2 36164 0
-- kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages initramfs-tools depends on:
ii busybox 1:1.1.3-4 Tiny utilities for small and embed
ii cpio 2.6-17 GNU cpio -- a program to manage ar
ii klibc-utils
Bug#465729: KDM doesn'd display login screen when splashy is enabled
Package: splashy Version: 0.3.8-1 Severity: important After booting with splashy enabled, kdm do not show its login screen. I have a nvidia card with proprietary drivers. kdm process is running but not kdm_greet. No keyboard shortcuts (Alt-Fx, Esc, F2) are working. If I log in from another machine using SSH and execute /etc/init.d/kdm restart, the login screen appears. Here are some logs from my system: /var/log/kdm.log after boot: Note that your system uses syslog. All of kdm's internally generated messages (i.e., not from libraries and external programs/scripts it uses) go to the daemon.* syslog facility; check your syslog configuration to find out to which file(s) it is logged. PAM logs messages related to authentication to authpriv.*. This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080131-1) Current Operating System: Linux resox 2.6.24-1-686 #1 SMP Wed Feb 6 15:20:27 UTC 2008 i686 Build Date: 01 February 2008 03:49:13AM 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: Thu Feb 14 11:41:38 2008 (==) Using config file: /etc/X11/xorg.conf After some time or if /etc/init.d/kdm stop is executed, the following lines apears in kdm log: Fatal server error: xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call and in case of timeout this appears in syslog: Feb 14 11:24:21 resox kdm: :0[4171]: Hung in XOpenDisplay(:0), aborting Feb 14 11:24:21 resox kdm: :0[4171]: Cannot connect to :0, giving up Feb 14 11:24:21 resox kdm[4160]: Display :0 cannot be opened When kdm is started manualy by /etc/init.d/kdm start the kdm log looks like: Note that your system uses syslog. All of kdm's internally generated messages (i.e., not from libraries and external programs/scripts it uses) go to the daemon.* syslog facility; check your syslog configuration to find out to which file(s) it is logged. PAM logs messages related to authentication to authpriv.*. This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080131-1) Current Operating System: Linux resox 2.6.24-1-686 #1 SMP Wed Feb 6 15:20:27 UTC 2008 i686 Build Date: 01 February 2008 03:49:13AM 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: Thu Feb 14 11:37:33 2008 (==) Using config file: /etc/X11/xorg.conf (II) Module ddc already built-in (EE) Failed to load module type1 (module does not exist, 0) (II) Module ramdac already built-in expected keysym, got XF86KbdLightOnOff: line 70 of pc
Bug#451275: kpowersave: Suspend to Disk/RAM only locks screen
On Thursday 15 of November 2007 15:01:05 Michael Biebl wrote: Michal Sojka schrieb: If I execute /etc/acpi/sleep.sh of s2ram -f -p -m, suspend to ram works. If /etc/acpi/sleep.sh is from acpi-support, s2ram from the uswsusp package, or whas that a or instead of of? Of course I meant or. Please follow the instructions at http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html and send me the necessary quirks for your laptop. I will then add them to the hal-info package and everyone can benefit. As you said, that s2ram -f -p -m works for you, the quirks are probably power_management.quirk.vbemode_restore and power_management.quirk.vbe_post in your fdi file. I have added the following lines to /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-hp.fdi and now Suspend to RAM works. match key=system.hardware.product contains=6710b (GB893EA#AKB) merge key=power_management.quirk.vbe_post type=booltrue/merge merge key=power_management.quirk.vbemode_restore type=booltrue/merge /match Since I'm not sure what are the correct attributes for the match tag, here I provide the output of lshal | grep system.hardware: system.hardware.primary_video.product = 10754 (0x2a02) (int) system.hardware.primary_video.vendor = 32902 (0x8086) (int) system.hardware.product = 'HP Compaq 6710b (GB893EA#AKB)' (string) system.hardware.serial = 'CNU7400C4C' (string) system.hardware.uuid = '84212E75-9715-E011-0C80-6D990E423129' (string) system.hardware.vendor = 'Hewlett-Packard' (string) system.hardware.version = 'F.0B' (string) Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452836: wpasupplicant: Kill switch doesn't take interface down
Package: wpasupplicant Version: 0.6.0-4 Severity: normal Hi, if I press the kill switch on my laptop with ipw3945, the interface is not taken down. It means, that even if I'm connected to a wired network, I'm not able to use it, because there are invalid routes in the routing table. I've found an workaround, but it is not very convenient. If I press the kill switch two times (i.e. I switch wifi on again and then quickly off), then the interface is taken down. In NetworkManager, the kill switch works as I expect, but I cannot use it to take care of my network interfaces, because its capabilities are to limited for my needs. Regards Michal -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wpasupplicant depends on: ii adduser 3.105 add and remove users and groups ii libc6 2.6.1-6GNU C Library: Shared libraries ii libdbus-1-3 1.1.1-3simple interprocess messaging syst ii libncurses5 5.6+20071013-1 Shared libraries for terminal hand ii libreadline5 5.2-3 GNU readline and history libraries ii libssl0.9.8 0.9.8g-3 SSL shared libraries ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip Versions of packages wpasupplicant recommends: ii dhcp3-client3.0.6.dfsg-1 DHCP client -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452371: network-manager: Scripts in if-up.d are executed with PHASE=up instead of PHASE=post-up
Package: network-manager Version: 0.6.5-3 Severity: normal Tags: patch According to interfaces(5) scripts in /etc/network/if-up.d/ should be executed with PAHSE equal to post-up. NetworkManager sets this to up. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser 3.105add and remove users and groups ii dbus1.1.1-3 simple interprocess messaging syst ii dhcdbd 3.0-1D-Bus interface to the ISC DHCP cl ii hal 0.5.10-2 Hardware Abstraction Layer ii ifupdown0.6.8high level tools to configure netw ii iproute 20070313-1 Professional tools to control the ii iputils-arping 3:20070202-3 Tool to send ICMP echo requests to ii libc6 2.6.1-6 GNU C Library: Shared libraries ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst ii libdbus-glib-1-20.74-1 simple interprocess messaging syst ii libgcrypt11 1.2.4-2 LGPL Crypto library - runtime libr ii libglib2.0-02.14.3-1 The GLib library of C routines ii libgpg-error0 1.4-2library for common error values an ii libhal1 0.5.10-2 Hardware Abstraction Layer - share ii libiw29 29-1 Wireless tools - library ii libnl1-pre6 1.0~pre6-6 Library for dealing with netlink s ii libnm-util0 0.6.5-3 network management framework (shar ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip ii wpasupplicant 0.6.0-4 Client support for WPA and WPA2 (I Versions of packages network-manager recommends: ii network-manager-kde 1:0.2-2KDE systray applet for controlling -- no debconf information Index: network-manager-0.6.5/debian/network-manager-dispatcher.script === --- network-manager-0.6.5.orig/debian/network-manager-dispatcher.script 2007-11-22 11:07:26.0 +0100 +++ network-manager-0.6.5/debian/network-manager-dispatcher.script 2007-11-22 11:08:39.0 +0100 @@ -19,7 +19,7 @@ case $2 in up) export MODE=start - export PHASE=up + export PHASE=post-up exec run-parts /etc/network/if-up.d ;; down)
Bug#451275: kpowersave: Suspend to Disk/RAM only locks screen
On Wednesday 14 of November 2007 19:30:16 Michael Biebl wrote: Hi Michal, could you please try the hal version (0.5.10-2) from unstable? Hi, even with 0.5.10-2, everything is the same - behavior and messages on stdout. Then I've tried to add myself to the powerdev group. And it seems this helped a little bit. I guess, this should be mentioned in README.Debian. Maybe, a message box with an error message is good idea. Now, I'm able to do Suspend to Disk successfully, but Suspend to RAM only switches to the text console, writes there something about my ethernet drivers and then returns back to the locked X screen. If I execute /etc/acpi/sleep.sh of s2ram -f -p -m, suspend to ram works. If the problem is because I need to use -f with s2ram, I have already report this to suspend-devel (http://sourceforge.net/mailarchive/forum.php?thread_name=200711141959.23616.sojkam1%40fel.cvut.czforum_name=suspend-devel) Thanks for your help, Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451275: kpowersave: Suspend to Disk/RAM only locks screen
Package: kpowersave Version: 0.7.3-1 Severity: normal Hi, if I choose Suspend to RAM or Suspend to Disk from KPowersave menu, no suspend happend and only screen is locked. I guess it has somethink to do with the messages written to stdout when kpowersave is executed from command line: kpowersave: WARNING: Unknown error while aquire org.freedesktop.Policy.Power interface kpowersave: ERROR: Could not send dbus message: The name org.freedesktop.PolicyKit was not provided by any .service files kpowersave: ERROR: Could not send dbus message: The name org.freedesktop.PolicyKit was not provided by any .service files kpowersave: ERROR: Could not send dbus message: The name org.freedesktop.PolicyKit was not provided by any .service files kpowersave: WARNING: Property: power_management.can_standby for: /org/freedesktop/Hal/devices/computer doesn't exist. kpowersave: WARNING: Property: battery.remaining_time for: /org/freedesktop/Hal/devices/acpi_C23B doesn't exist. kpowersave: WARNING: Property: battery.remaining_time for: /org/freedesktop/Hal/devices/acpi_C23B doesn't exist. kpowersave: WARNING: Property: battery.serial for: /org/freedesktop/Hal/devices/acpi_C23A doesn't exist. kpowersave: ERROR: Could not send dbus message: The name org.freedesktop.PolicyKit was not provided by any .service files kpowersave: ERROR: Could not send dbus message: The name org.freedesktop.PolicyKit was not provided by any .service files kpowersave: ERROR: Could not send dbus message: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface org.freedesktop.Hal.Device.SystemPowerManagement member SetPowerSave error name (unset) destination org.freedesktop.Hal) kpowersave: ERROR: Could not call/set SetPowerSave on HAL, could be a bug in HAL spec After chosing Suspend to RAM, additial messages appear: kpowersave: ERROR: Could not get argument from reply: Argument 0 is specified to be of type int32, but is actually of type string kpowersave: kpowersave: WARNING: dbusHAL::callBackSuspend dbus_message_get_args failed, maybe timouted I'm running it on HP Compaq 6710b laptop. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kpowersave depends on: ii hal 0.5.9.1-6 Hardware Abstraction Layer ii kdelibs4c2a 4:3.5.7.dfsg.1-7core libraries and binaries for al ii libc62.6.1-1+b1 GNU C Library: Shared libraries ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst ii libgcc1 1:4.2.2-3 GCC support library ii libhal1 0.5.9.1-6 Hardware Abstraction Layer - share ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3 ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxss1 1:1.1.2-1 X11 Screen Saver extension library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension Versions of packages kpowersave recommends: ii acpi-support 0.103-1scripts for handling many ACPI eve ii hibernate 1.97-1 smartly puts your computer to slee ii pm-utils 0.99.2-3 utilities and scripts for power ma ii powersaved0.14.0-8 power management daemon -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307822: Solved
Hi, I've found this old bug and realized that it is solved in the current version of KOrganizer in testing (3.5.7). So I guess you can close it. Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435335: emacs-goodies-el: Please include newer version of tabbar.el.
Package: emacs-goodies-el Version: 26.13-1 Severity: wishlist Please include newer version of tabbar.el from http://emhacks.sourceforge.net/. This fixes several problem and adds new usefull features. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23-rc1 (PREEMPT) Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash Versions of packages emacs-goodies-el depends on: ii bash 3.1dfsg-8 The GNU Bourne Again SHell ii emacs21 [emacsen] 21.4a+1-5 The GNU Emacs editor ii emacs22-gtk [emacsen] 22.1+1-1 The GNU Emacs editor (with GTK use Versions of packages emacs-goodies-el recommends: ii dict 1.10.2.dfsg-3.2 Dictionary Client ii perl-doc 5.8.8-7 Perl documentation ii wget 1.10.2-3retrieves files from the web -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395286: Clicking korganizer daemon icon don't start korganizer
Package: korganizer Version: 4:3.5.5-1 Severity: normal I'm able to run korganizer from command line, but clicking the korganizer daemon icon don't start it. When I do it, in ~/.xsession-errors, I get the following: korganizer: 'url' missing. korganizer: Use --help to get a list of available command line options. Doing ps -ef|grep korgnaizer when I click the icon gives me: ... korganizer --import I fixed this problem by modifying /usr/share/applications/kde/korganizer.desktop. I changed the line: Exec=korganizer --import %u to Exec=korganizer I don't know if this is the proper solution. Michal -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686-smp Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages korganizer depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-2 core libraries and binaries for al ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libfontconfig1 2.4.1-2 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-17GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.5-1 KDE calendaring library ii libkdepim1a4:3.5.5-1 KDE PIM library ii libkpimexchange1 4:3.5.5-1 KDE PIM Exchange library ii libkpimidentities1 4:3.5.5-1 KDE PIM user identity information ii libpng12-0 1.2.8rel-7PNG library - runtime ii libqt3-mt 3:3.3.7-1 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-17 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-2 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-3 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages korganizer recommends: ii kghostview4:3.5.5-1 PostScript viewer for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368550: Recompilation helps
Hello, I had the same problem with flags. I tried to recompile the package and now flags are displayed correctly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361286: vim-common: Syntax error in commented-out part of vimrc
Package: vim-common
Version: 1:6.4-007+1
Severity: minor
Tags: patch
Uncommenting the following part in vimrc leads to errors on
startup. The patch fixes this.
--- /etc/vim/vimrc.dpkg-dist2006-02-12 15:39:20.0 +0100
+++ vimrc.dpkg-dist-fixed 2006-04-07 19:18:23.0 +0200
@@ -54,7 +54,7 @@
reopening a file
if has(autocmd)
au BufReadPost * if line('\) 0 line('\) = line($)
-\| exe normal g'\ | endif
+\| exe normal g'\ | endif
endif
Set paper size from /etc/papersize if available (Debian-specific)
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686-smp
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Versions of packages vim-common depends on:
ii libc6 2.3.6-4GNU C Library: Shared libraries an
Versions of packages vim-common recommends:
ii vim 1:6.4-007+1 Vi IMproved - enhanced vi editor
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358360: initramfs-tools: Doesn't find hdd (module ide-disk)
Package: initramfs-tools Version: 0.57b Severity: important The description of this bug is the same as for #344754. The only difference is the version of package. The solution presented in #344754 works in my case as well. The problem appears with standard Debian kernel 2.6.15-1-686-smp. I haven't tried any other kernels. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686-smp Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages initramfs-tools depends on: ii busybox 1:1.01-4 Tiny utilities for small and embed ii cpio 2.6-11 GNU cpio -- a program to manage ar ii klibc-utils 1.2.4-1small statically-linked utilities ii udev 0.084-1/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307822: korganizer: Next X days view is not remebered and is switched to week view after restart
Package: korganizer Version: 4:3.3.2-3 Severity: minor When I set the Show next X days option to 7 days and choose a view mode show next 7 days, after restart this view mode is not remebered and KOrganizer starts in week view mode. This means that the view starts on Monday instead of today. If I setup the view mode to show other number of days than 7, the mode is remembered correctly. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.7 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages korganizer depends on: ii kdelibs4 4:3.3.2-4.0.2 KDE core libraries ii ktnef4:3.3.2-3 KDE TNEF viewer ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libc62.3.2.ds1-21GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-12 GCC support library ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library ii libidn11 0.5.13-1.0 GNU libidn library, implementation ii libkcal2a4:3.3.2-3 KDE calendaring library ii libkdepim1 4:3.3.2-3 KDE PIM library ii libkgantt0 4:3.3.2-3 KDE gantt charting library ii libkpimexchange1 4:3.3.2-3 KDE PIM Exchange library ii libkpimidentities1 4:3.3.2-3 KDE PIM user identity information ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session Management ii libstdc++5 1:3.3.5-12 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii perl 5.8.4-8 Larry Wall's Practical Extraction ii xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295195: Without an -emulator argument, seyon fails to start.
Package: seyon Version: 2.20c-16 Severity: normal When I run seyon without any command line options, it fails and prints the following message. Option --tclass is no longer supported in this version of gnome-terminal; you might want to create a profile with the desired setting, and use the new --window-with-profile option Two --title options given for one tab root logged off pts/1 from localhost at 11:18. If I start it with -emulator xterm option, it works. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages seyon depends on: ii debconf 1.4.42 Debian configuration management sy ii gnome-terminal [x-termin 2.8.2-1 The GNOME 2 terminal emulator appl ii konsole [x-terminal-emul 4:3.3.2-1 KDE X terminal emulator ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxaw7 4.3.0.dfsg.1-10 X Athena widget set library ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii libxmu6 4.3.0.dfsg.1-10 X Window System miscellaneous util ii libxpm4 4.3.0.dfsg.1-10 X pixmap library ii libxt6 4.3.0.dfsg.1-10 X Toolkit Intrinsics ii rxvt [x-terminal-emulato 1:2.6.4-6.2 VT102 terminal emulator for the X ii xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu ii xterm [x-terminal-emulat 4.3.0.dfsg.1-10 X terminal emulator -- debconf information: seyon/device: /dev/modem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292531: kmail: Kmail silently exits after choosing Open With on an attachment
Package: kmail
Version: 4:3.3.1-3
Severity: normal
I have an email with multiple graphic attachements (PNG files) in my Inbox.
I choose one picture in the Description window (list of attachements) and
then click right mouse button in the displayed picture and chooseOpen With
from menu. After few seconds of busy 100% load kmail silently exits.
Here is the end of output from strace:
access(/usr/lib/qt3/plugins/codecs/., F_OK) = -1 ENOENT (No such file or
directory)
open(/home/sojka/.DCOPserver_glab__0, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(3, local/glab:/tmp/.ICE-unix/dcop53..., 4096) = 51
close(3)= 0
munmap(0xb7ffe000, 4096)= 0
socket(PF_FILE, SOCK_STREAM, 0) = 3
uname({sys=Linux, node=glab, ...}) = 0
connect(3, {sa_family=AF_FILE, path=/tmp/.ICE-unix/dcop5335-1106811332},
37) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
write(3, \0\1\0\0\0\0\0\0, 8) = 8
read(3, \0\1\0\0\0\0\0\0, 8) = 8
access(/home/sojka/.ICEauthority, R_OK) = 0
open(/home/sojka/.ICEauthority, O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, \0\3ICE\0\0\0-local/glab:/tmp/.ICE-un..., 4096) = 185
read(4, , 4096) = 0
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, \0\2\1\1\6\0\0\0\0\0\0\0\0\0\0\0\3\0MIT\0\0\0\3\0001.0..., 56) =
56
read(3, \0\3\0\0\1\0\0\0, 8) = 8
read(3, \0\0\0\0\0\0\0\0, 8) = 8
access(/home/sojka/.ICEauthority, R_OK) = 0
open(/home/sojka/.ICEauthority, O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, \0\3ICE\0\0\0-local/glab:/tmp/.ICE-un..., 4096) = 185
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, \0\4\1\1\3\0\0\0\20\0\0\0\0\0\0\0R\30\255eh\271N\257\307..., 32)
= 32
read(3, \0\6\0\0\2\0\0\0, 8) = 8
read(3, \3\0MIT\0\0\0\3\0001.0\0\0\0, 16) = 16
access(/home/sojka/.ICEauthority, R_OK) = 0
open(/home/sojka/.ICEauthority, O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, \0\3ICE\0\0\0-local/glab:/tmp/.ICE-un..., 4096) = 185
read(4, , 4096) = 0
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, \0\7\1\0\7\0\0\0\1\1\0\0\0\0\0\0\4\0DCOPN\257\3\0KDE?\336..., 64)
= 64
read(3, \0\3\0\0\1\0\0\0, 8) = 8
read(3, \0\0MIT\0\0\0, 8) = 8
access(/home/sojka/.ICEauthority, R_OK) = 0
open(/home/sojka/.ICEauthority, O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, \0\3ICE\0\0\0-local/glab:/tmp/.ICE-un..., 4096) = 185
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, \0\4\1\0\3\0\0\0\20\0\0\0\0\0\0\0R\30\255eh\271N\257\307..., 32)
= 32
read(3, \0\10\0\2\2\0\0\0, 8) = 8
read(3, \3\0KDE\0\0\0\3\0002.0\0\0\0, 16) = 16
getsockopt(3, SOL_SOCKET, SO_PEERCRED, \327\24\0\0\350\3\0\0\350\3\0\0,
[12]) = 0
getuid32() = 1000
getpid()= 7877
write(3, \1\2\1\0H\0\0\0\0\0\0\0, 12) = 12
write(3, \0\0\0\0\0\0\0\vDCOPServer\0\0\0\0\1\0\0\0\0\25regi..., 53) = 53
write(3, \0\0\0\17anonymous-7877\0, 19) = 19
read(3, \2\3\0\0027\0\0\0, 8) = 8
read(3, \240\0\0\0, 4)= 4
read(3, \0\0\0\vDCOPServer\0\0\0\0\0\0\0\0\tQCString\0..., 55) = 55
write(3, \1\2\1\0[\0\0\0\240\0\0\0, 12) = 12
write(3, \0\0\0\17anonymous-7877\0\0\0\0\vDCOPServe..., 81) = 81
write(3, \0\0\0\6kmail\0, 10) = 10
read(3, \2\3\0\0023\0\0\0, 8) = 8
read(3, \240\0\0\0, 4)= 4
read(3, \0\0\0\vDCOPServer\0\0\0\0\17anonymous-787..., 51) = 51
write(3, \1\2\1\0a\0\0\0\2\0\0\0, 12) = 12
write(3, \0\0\0\17anonymous-7877\0\0\0\0\6kmail\0\0\0\0..., 61) = 61
write(3, \0\0\0\f/home/sojka\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0..., 36) =
36
read(3, \2\5\0\2!\0\0\0, 8) = 8
read(3, \2\0\0\0, 4) = 4
read(3, \0\0\0\6kmail\0\0\0\0\17anonymous-7877\0\0\0\0..., 33) = 33
read(3, \2\6\0\0021\0\0\0, 8) = 8
read(3, \2\0\0\0, 4) = 4
read(3, \0\0\0\6kmail\0\0\0\0\17anonymous-7877\0\0\0\0..., 49) = 49
close(3)= 0
exit_group(0) = ?
-- System Information:
Debian Release: 3.1
APT prefers
Bug#291334: showimg: Bad dependencies
Package: showimg Severity: important When trying to install showimg, apt wants to remove my KDE. See the following apt output: # apt-get install showimg Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: kdelibs-bin kdelibs4 libkonq4 libopenexr2 perl-suid The following packages will be REMOVED: kde kde-amusements kde-core kdeaddons kdeadmin kdeartwork kdebase kdeedu kdegames kdegraphics kdemultimedia kdenetwork kdepim kdetoys kdeutils kdewebdev The following NEW packages will be installed: libopenexr2 perl-suid showimg The following packages will be upgraded: kdelibs-bin kdelibs4 libkonq4 3 upgraded, 3 newly installed, 16 to remove and 220 not upgraded. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9-swsusp2 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290310: kdeprint: Unable to create the Foomatic driver
Package: kdeprint Version: 4:3.3.1-4 Severity: important When adding a new network printer (TCP), after the Driver Selection dialog, the following box appears: Unable to load the requested driver: Unable to create the Foomatic driver [HP-LaserJet_4200,Postscript]. Either that driver does not exist, or you don't have the required permissions to perform that operation. This message appears also in the case when I run the kprinter as root. I have set the currently used printing system as LPR/LPRng. In the following list, there are same package versions I thing thay have something to do with my problem. ||/ Name Version Description +++-=-=-== un foo2zjs none(no description available) pn foomatic-bin none(no description available) ii foomatic-db 20041203-1linuxprinting.org printer support - database ii foomatic-db-engine3.0.2-2 linuxprinting.org printer support - programs un foomatic-db-gimp-printnone(no description available) ii foomatic-db-hpijs 1.5-20041013-1linuxprinting.org printer support - database for HPIJS printers ii foomatic-filters 3.0.2-3 linuxprinting.org printer support - filters ii foomatic-filters-ppds 20041013-1linuxprinting.org printer support - prebuilt PPD files ii foomatic-gui 0.7.4.2 GNOME interface for configuring the Foomatic printer filter system ii gnulpr1.2 GNUlpr printing system. rc lpr 2000.05.07-5 BSD lpr/lpd line printer spooling system ii lpr-ppd 0.72-4BSD lpr/lpd line printer spooling system -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages kdeprint depends on: ii enscript 1.6.4-5 Converts ASCII text to Postscript, ii gv 1:3.6.1-3 PostScript and PDF viewer for X ii kdelibs4 4:3.3.1-4 KDE core libraries ii libart-2.0-2 2.3.16-6Library of functions for 2D graphi ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6 client library to control the FAM ii libgcc1 1:3.4.3-7 GCC support library ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library ii libidn11 0.5.2-3 GNU libidn library, implementation ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libstdc++5 1:3.3.5-6 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii poster 20020830-2 Create large posters out of PostSc ii psutils 1.17-17 A collection of PostScript documen ii xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
