Bug#913221: qt5keychain-dev: should install the generated .pri file so it can be used as a Qt module

Package: qt5keychain-dev Version: 0.9.0-2 Severity: important Dear Maintainer, by adding the line > usr/lib/*/qt5/mkspecs/modules/qt_Qt5Keychain.pri to debian/qt5keychain-dev.install the generated package will install the .pri file in the appropriate directory and will allow using qt5keychain as

Bug#885755: RM: grcm -- ROM; grcm does not appear to have an upstream anymore

Package: ftp.debian.org Severity: normal grcm latest version will get 10 years old during 2018, and the latest news on its upstream website are from 2008 as well. I am not using grcm anymore and its popcon is very low. I think it's time to let it go. Best, Luca

Bug#883072: [Pkg-swan-devel] Bug#883072: strongswan-libcharon: Upgrade to 5.6.1-2 changed cypher proposals, can't connect to VPN anymore

cor...@debian.org> wrote: > On Wed, 2017-11-29 at 10:54 +0100, Luca Niccoli wrote: >> Is there a specific reason the default cipher proposal by >> strongswan doesn't offer aes256-sha256-prfsha256-modp1024 anymore? >> Would it be possible to add it back? > > Hi,

Bug#883072: strongswan-libcharon: Upgrade to 5.6.1-2 changed cypher proposals, can't connect to VPN anymore

Package: strongswan-libcharon Version: 5.6.1-2 Severity: normal Dear Maintainer, I've recently upgraded from strongswan 5.6.0-2 to 5.6.1-2, and two of my existing VPN configurations, pointing to pfSense servers, stopped working with an "Invalid secrets" error. Digging in the computer and pfSense

Bug#881745: fswebcam: build dependency libgd2-noxpm-dev does not exist

Hi James, I have a uploaded a new version on mentors.debian.net, you can see it at https://mentors.debian.net/package/fswebcam Would you be willing to sponsor an upload? Best, Luca On 14 November 2017 at 19:26, James Cowgill wrote: > Source: fswebcam > Version: 20140113-1

Bug#854856: transmission-daemon does not launch correctly when using systemd

Package: transmission-daemon Version: 2.92-2 Severity: important Dear Maintainer, it appears the systemd service file for transmission-daemon does not pass a configuration directory when launching the daemon, which will try to use its home directory /home/transmission-daemon, which doesn't exist

Bug#773791:

This seems an upstream bug that should be fixed in text version (which from the PTS seems to have been just uploaded to unstable): https://wiki.strongswan.org/issues/1429 The new version has still to propagate to my mirror so I couldn't verify it yet. Cheers, Luca

Bug#781505: chromium-l10n: Should depend on the same version of chromium

Package: chromium-l10n Version: 38.0.2125.101-2 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, as you can see from the installation details, when upgrading chromium I forgot to update chromium-l10n as well. The result is quite funny: the strings in the UI have

Bug#761316: printer-driver-splix depends on ghostscript-cups, which is not built anymore by src:ghostscript

Hi, I actually had this fix ready, but I did not have access to my printer and I wanted to give it a run before pushing to the repo. Anyway, I just tested the new package and it work fine. Didier, as a rule always consider me OK with team uploads! Cheers, Luca

Bug#761316: printer-driver-splix depends on ghostscript-cups, which is not built anymore by src:ghostscript

Hi, I will look into this in the next few days. The dependency should be on the gstoraster executable which is now indeed in cups-filter. Thanks for the report, Luca

Bug#712118: marked as done (RFS: splix/2.0.0+svn308-1)

On 3 January 2014 12:14, Didier 'OdyX' Raboud o...@debian.org wrote: I'm awfully sorry to have failed to answer you earlier, let's correct that now. That's no problem, I've been caught up with work stuff so I dropped the ball as well. Could you make your git repository available somewhere so

Bug#712118: marked as done (RFS: splix/2.0.0+svn308-1)

reopen 712118 thank you Hi Didier and Till, I'm reopening the RFS bug for splix. I've uploaded a new version of splix that merges the last upstream changes (mainly dropping patches that have been accepted upstream), sets the maintainer as the Debian Printing Team and moves the packaging to a git

Bug#712118: New version of splix

Hi Didier, it took me some time but I moved the splix packaging to git. The new dsc is available at: http://mentors.debian.net/debian/pool/main/s/splix/splix_2.0.0+svn308-1.dsc The git repo lives on my local machine, I think I cannot push it to alioth as I am not a DD. I will also answer some of

Bug#708212: Please upload latest SVN snapshot

Here's the link to the dsc: http://mentors.debian.net/debian/pool/main/s/splix/splix_2.0.0+svn308-1.dsc Cheers, Luca On 2 June 2013 13:03, Luca Niccoli lultimou...@gmail.com wrote: Hi Didier and Till, I've uploaded to mentors a new version of splix. The changes are: - move to the lates

Bug#708212: Please upload latest SVN snapshot

Hi Didier and Till, I've uploaded to mentors a new version of splix. The changes are: - move to the lates svn snapshot - copy fixed splix.ppd-updater from Ubuntu - add conditional apport hook for Ubuntu and derivatives - add get-orig-source target - used dpkg-buildflags to import hardening flags

Bug#696240: Please add support for Samsung ML-2160 series

Hi Berhard, could you try the printer with the attached ppd? Thanks, Luca On 18 December 2012 16:09, Bernhard bewoe...@yahoo.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: printer-driver-splix Version: 2.0.0+svn306-2 Severity: wishlist Please add support for the

Bug#670823: printer-driver-splix: drv files are not properly pre-processed during build.

Package: printer-driver-splix Version: 2.0.0+svn306-1 Severity: grave Justification: renders package unusable Dear Maintainer (that would be me), always remember to remove and readd the printer when you try your soon-to-be-uploaded version of splix, otherwise old PPDs will prevent you to see

Bug#457650: Transition to .drv - defs files missing in the package

Hi, see #670823 Thanks for the report, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#457650: splix: jbigkit packaged for Debian

This is good news , I will work on packaging a JBIG enabled version in the next days! Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#655918: splix: diff for NMU version 2.0.0+svn300-1.1

On Feb 1, 2012 7:45 PM, Didier Raboud o...@debian.org wrote: Dear maintainer, I've prepared an NMU for splix (versioned as 2.0.0+svn300-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Hi Didier, the debdiff looks fine. Thank you for the NMU,

Bug#649258: override: splix:oldlibs/extra

Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear ftp-masters, splix is now a dummy package to manage the transition to the new binary package, printer-driver-splix. Therefore it should be moved to oldlibs and extra priority. Cheers, Luca -BEGIN

Bug#648755: lintian: arch-dep-package-has-big-usr-share is probably to eager.

check is not about that, and remains flawed. Cheers, Luca Niccoli - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (995, 'unstable'), (991, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF

Bug#647534: Please rename splix to printer-driver-splix

Hi Didier, thank you for the patch, I plan to work on this by next weekend. I will also consider moving the package to team maintenance, but before I need to do some homework and understand how this will change my work flow. Cheers, Luca -- To UNSUBSCRIBE, email to

Bug#647536: splix: Please replace the postinst with a ppd-updater trigger

Hi, for some time now (in fact, since its 1.5.0-3 version), cups offers a way to trigger for driver updates on package upgrade, by simply putting a file under /usr/share/cups/ppd-updaters/. Cups will then watch for this file and trigger a driver update. Hi Didier, Thank you for this patch

Bug#634330: splix: only 1st job prints

Hi Sebastian, what do you mean with first job? Does the printer start printing again if you - power cycle it - restart cups - either of the first two options - both of the first two options or you need to restart your computer? Thanks, Luca -- To UNSUBSCRIBE, email to

Bug#618847:

I hit this bug, and the upstream patch indeed fixes it. Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#615151: aptitude: manually upgrading packages marked A removes A flag

I just realized this as well; the last new version in aptitude dates back to october, I wonder whether it's possible that it slipped unnoticed during these months or whether it may depend on some changes somewhere else. Anyway, it's really annoying... Cheers, Luca -- To UNSUBSCRIBE, email to

Bug#533468: print failure on PowerPC

Hi Ulrich, could you please try the patch I attached? It's basically the one you proposed, bot without the biteswapping in __compare(): since the functions compares two native-endian uint32 counters that keep track of how many times a byte pattern is present in the page, the byteswap should make

Bug#617819: O: splix -- Driver for Samsung's SPL2 (bw) and SPLc (color) laser printers

retitle 617819 ITA: splix -- Driver for Samsung's SPL2 (bw) and SPLc (color) laser printers owner 617819 ! thank you I am planning to adopt splix, since I've been taking care of it in the last period. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#616542: [Debian-eeepc-devel] Bug#616542: eeepc-acpi-scripts: fails to purge

tag 616542 + pending thank you Fixed in git. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#565097: splix: New errors with gcc-4.5

severity 565097 serious thank you I realize now that gcc-4.4 is passing --no-copy-dt-needed-entries to the linker as well, so splix FTBFS in plain sid. Raising severity accordingly. Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#531319: splix: printing from acroread fails

tag 531319 +moreinfo thank you Hi Martin, Soenke, you submitted a bug report to against splix to debian some time ago. [0] I tried to reproduce it, both with acroread and using the command Soenke posted, but failed (i.e. it printed fine). Could you please try again with an up-to-date system?

Bug#477088: splix: ML-1520P prints rubbish outside page dimensions

found 477088 2.0.0-2.2 forwarded 477088 http://sourceforge.net/support/tracker.php?aid=3198295 thank you On 3 March 2011 01:18, Endel Soolo endel.so...@gmail.com wrote: Here is a picture of test page, printed on A4 paper using landscape A5 paper settings:

Bug#616298: eglibc: FTBFS with current sid

Source: eglibc Version: 2.11.2-13 Severity: important User: peter.fritzs...@gmx.de -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I tried to build eglibc in an up-to-date pbuilder chroot, ant it fails complaining for unresolved symbols due to the fact that --no-add-needed is now passed by

Bug#436991: splix: Xerox Phaser 6110: when printing in 1200x600 the printout is stretched

Hi Sam, quite a long time ago you submitted a bug report against splix to the debian BTS. You can find it at [0]. Could you verify if the problem persists with the present version of splix? Thanks, Luca [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436991 -- To UNSUBSCRIBE, email to

Bug#477088: splix: ML-1520P prints rubbish outside page dimensions

Hi Endel, Carlos you submitted a bug report against splix to debian some time ago [0]. Could you check whether it still applies to the present version of splix? Thanks, Luca [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477088 -- To UNSUBSCRIBE, email to

Bug#565097: splix: New errors with gcc-4.5

There's a new build error with gcc-4.5, due to the fact that it now passes --no-copy-dt-needed-entries to the linker. I'm going to prepare an NMU that fixes both the problems and look for a sponsor to upload it (I also see you are in the low threshold NMU list). I'd also be interested in taking

Bug#612611: [Pkg-xfce-devel] Bug#612611: xfce4-power-manager: Does not work with DBus activated HAL

On 9 February 2011 16:27, Yves-Alexis Perez cor...@debian.org wrote: In the meantime, remember that unstable is supposed to be unstable, especially after a release, so it might make sense to stay on testing for now. Someone has to take the bullet for people using testing =), and I can live

Bug#612611: xfce4-power-manager: Does not work with DBus activated HAL

Package: xfce4-power-manager Version: 0.8.5-2 Severity: grave Tags: patch Justification: renders package unusable The new HAL version in sid doesn't start anymore at boot time; it gets activated whenever something connects to its dbus interface. Since xfce4-power-manager checks if HAL is running

Bug#610278: [Debian-eeepc-devel] Bug#610278: eeepc-acpi-scripts: Backlight settings are forgotten when moving the mouse

On 17 January 2011 01:18, Jeremy Salwen jeremyb...@gmail.com wrote: in /etc/default/grub .  I'm not 100% certain which package this bug report belongs in, but this is my best guess, as it seems to be responsible for backlight settings. eeepc-acpi-scripts doesn't do any idle dimming; actually,

Bug#609911: [Debian-eeepc-devel] Bug#609911: Bug#609911: eeepc-acpi-scripts: Wireless cannot be switched off with EEEPC 1016P

On 14 January 2011 14:06, Ben Hutchings b...@decadent.org.uk wrote: I think it would be better to make this a quirk in the kernel, if that's possible.  There is an existing blacklist that modifies the kernel's responses to OSI queries.  If you can provide the sys_vendor and product_version

Bug#609911: [Debian-eeepc-devel] Bug#609911: Bug#609911: eeepc-acpi-scripts: Wireless cannot be switched off with EEEPC 1016P

Do you think it would be acceptable to ship a grub 2 hook that appends acpi_osi=Linux to the kernel command line if update-grub is run on an affected model? I think it is technically feasible and reasonably safe, but I don't know how late it is to ship something that messes with the boot system.

Bug#598097: [Debian-eeepc-devel] Bug#598097: Make detect_x_display go away to solve this

On 13 November 2010 13:20, Ben Armstrong sy...@sanctuary.nslug.ns.ca wrote: I'm going to see what other keys (if any) rely on detect_x_display, and see if we can apply the same approach. Now that acpi-support x detection has been fixed, we really should rely on it instead of on our own

Bug#598097: [Debian-eeepc-devel] Bug#598097: Bug#598097: Make detect_x_display go away to solve this

I have a changeset ready but will not be able to try it in the next few days. Should I commit it any way? It's just a bit more than search and replace (detect_x_display also exported $user - while getXconsole exports $USER - and $home - but it doesn't seem used anywhere) Cheers, Luca -- To

Bug#598097: [Debian-eeepc-devel] Bug#598097: Bug#598097: Bug#598097: Make detect_x_display go away to solve this

Well, it wasn't even necessary to change $user to $XUSER, getXconsole sets the former as well as the latter. Committed. Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#603796: [Pkg-acpi-devel] Bug#603796: acpi-support: getXconsole depends on Xserver running as X and not Xorg

On 18 November 2010 12:54, Michael Meskes mes...@debian.org wrote: Could it be that this patch breaks other display managers? feivel:~# for pid in `ps -U user that's actually logged in  -o pid=`; do grep -z XAUTHORITY /proc/$pid/environ; done feivel:~# It seems my system using kdm does

Bug#591813: [Pkg-acpi-devel] Bug#591813: Bug#591813: acpi-support: Widespred use of su $user is (sometimes?) broken

On 2 September 2010 15:40, Michael Meskes mes...@debian.org wrote: On Sun, Aug 29, 2010 at 02:49:49PM +0200, Luca Niccoli wrote: I'm wondering if what triggered the problem is the switch do gdm3; are you using it as well? No, unless it sneaked in somehow. :-) Ok, now after an update neither

Bug#603796: acpi-support: getXconsole depends on Xserver running as X and not Xorg

Package: acpi-support Version: 0.137-5 Severity: normal Tags: patch The regex in getXconsole to find the X display searches for /X , but X nowadays runs as Xorg. The attached patch will match against both. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy:

Bug#603796: acpi-support: getXconsole depends on Xserver running as X and not Xorg

retitle 603796 power-funcs makes incorrect assumptions about Xorg thank you Actually, there's also the problem that getXuser assumes XAUTHORITY is placed in the user home; this is false with gdm3. The attached patch (that includes and supersedes the previous one) parses the environment of the

Bug#600494: readahead-fedora: RUN_IN_BACKGROUND is not effective

Package: readahead-fedora Version: 2:1.5.6-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Both the init scripts have: if [ $RUN_IN_BACKGROUND = yes ] $SHOULD_COLLECT; then (readahead in background) But there should really be: if [ $RUN_IN_BACKGROUND = yes ] [

Bug#523322: [Pkg-xfce-devel] Bug#523322:

On 5 September 2010 10:30, Yves-Alexis Perez cor...@debian.org wrote: I've uploaded a fixed version, could you check that it indeed fix the problem? I'm waiting for it to pass some days in unstable before asking a freeze exception. It does, thank you. Cheers, Luca -- To UNSUBSCRIBE,

Bug#521437: Is the bug you reported still affecting bootchart?

tag 521437 + moreinfo unreproducible thank you Hi, you submitted a bug against hal and bootchart a long time ago. [0] We would need your help to see if the problem still exists. If it does, are you by chance using splashy? Some of the error messages you reported made me think so. Cheers, Luca

Bug#595495:

I really don't care about the severity as long as it is RC, but if you think this is not a critical bug than you should take action to get [0] corrected: critical makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on

Bug#595495:

severity 595495 critical thank you It actually happened to me, goodbye /usr/lib32, with all the libraries in there. Then trying to reinstall some 32bit library adds even more files to /emul/ia32-linux, which will trigger the problem again even if the old package that left over a file there is

Bug#595495:

P.S. Severity set to critical since it breaks unrelated packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322:

On 1 September 2010 07:31, Yves-Alexis Perez cor...@debian.org wrote I'm not using an older version, I'm using a more recent version :) ii  gnome-keyring  2.30.3-1       GNOME keyring services (daemon and tools) I'm using that too. Probably the version of Xfce you're using has the bug fixed

Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322: Bug#523322:

On 1 September 2010 12:23, Yves-Alexis Perez cor...@debian.org wrote: dbus is usually started using 75dbus_dbus-launch. On my system it's gpg-agent - dbus-launch - startxfce4. It might depend on how you start Xfce (if dbus isn't started when startxfce4 is run, it will start it itself), but

Bug#523322:

Hi, I've been using an xfce4-session package patched with the two patches linked in the previous mail, and I've not had problems in the last three months. Are you planning to upload a patched version in squeeze? I feel gnome-keyring has become quite an important part for many GTK programs, so it

Bug#523322: [Pkg-xfce-devel] Bug#523322:

On 31 August 2010 23:24, Yves-Alexis Perez cor...@debian.org wrote: Hmh, to be honest, gnome-keyring is started properly here (though I'm not using 4.6 on that box and can't check on another one). Maybe if you're not using 4.6 you have an old version of gnome-keyring as well? The way it was

Bug#523322: [Pkg-xfce-devel] Bug#523322:

On 31 August 2010 23:52, Luca Niccoli lultimou...@gmail.com wrote: It doesn't work; SSH Key Agent doesn't even show up as an option among the autostarted applications in xfce4-session-settings . Mmm, it just needed to be copied to /etc/xdg/autostart; it doesn't work anyway (the variables

Bug#594894: wpasupplicant: wpa_supplicant doesn't set WEP key with ath9k cards

Package: wpasupplicant Version: 0.6.10-2 Severity: important In my wpa_supplicant config file I have entries like: network={ ssid=Network key_mgmt=NONE wep_key0=aa } It used to work, but I have tried again recently and while wpa_gui reported I associated

Bug#591813: [Pkg-acpi-devel] Bug#591813: acpi-support: Widespred use of su $user is (sometimes?) broken

On 16 August 2010 16:11, Michael Meskes mes...@debian.org wrote: # xrandr --output LVDS --off it works; if I run It doesn't for me, so this may depend on your settings. # su $user -c xset dpms force off or # su $user -s /bin/sh -c xset dpms force off with $user set to the user that owns

Bug#536666: qtpfsgui can't save HDR files

Hi, this bug has been reported more than a year ago and I submitted a patch three months ago (in which I now realized I forgot a semicolon; a corrected one is attached). Is someone interested in uploading a patched version? Otherwise I can prepare a NMU and ask my usual sponsor whether he's

Bug#572942: Proposal to adopt mtkbabel

Hi Uwe, I write to ping you about your mtkbabel package in debian. There's a new version that fixes support for some gps models that are not supported by the old one, which is really important if you happen to own one. If you don't have time for/are not interested in maintaining the package any

Bug#574349: splix doesn't work at all on armel

Hi Jeroen, I write to ping you about a very annoying bug in splix: it doesn't print on armel because of alignment issues. I have prepared a minimal patch that only fixes that without touching the code path. are you planning on pulling it any time soon? This bug is really annoying since it

Bug#536666:

severity 53 grave thank you Raising severity to grave, since after all qtpfsgui makes you lose the HDR file you just created, causing data loss. As a side note, the new binNMUed version doesn't crash on saving the file, it just silently fails to do it. Cheers, Luca -- To UNSUBSCRIBE,

Bug#574349:

severity 574349 grave thank you Raising severity to grave, since this bug makes the package unusable on a supported architecture. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#593176: fswebcam: New homepage URL

Hi Geoff, I'm away from home this week, but I'll prepare an upload next one. Thanks, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#591813: acpi-support: Widespred use of su $user is (sometimes?) broken

Package: acpi-support Version: 0.137-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, while testing the lid.sh script I noticed that it didn't blank the screen. It boils down to this: if from a root shell I set $DISPLAY and run # xset dpms force off or # xrandr --output LVDS

Bug#591815: acpi_fakekey manpage is installed both in acpi-support and in acpi-fakekey

Package: acpi-support Version: 0.137-3 Severity: serious Justification: Policy 7.4 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, in the source package the manpage for acpi_fakekey is present both in debian/acpi-support.manpages and in debian/acpi-fakekey.manpages; this makes the packages

Bug#589625: [Pkg-acpi-devel] Bug#589625: acpi-support: Providing the option to suspend on lid close would be useful

tags 589625 +patch thank you On 4 August 2010 22:45, Michael Meskes mich...@fam-meskes.de wrote: Here is a patch meant to be added at the end of the current quilt series plus a patch against the default file. Cheers, Luca lid-sleep.diff Description: plain/text default.diff Description:

Bug#589625: acpi-support: Providing the option to suspend on lid close would be useful

On 19 July 2010 12:47, Luca Niccoli lultimou...@gmail.com wrote: Would you accept a patch that, depending on a variable set in /etc/default/acpi-support (off by default) would suspend the laptop? Thanks, Hi, have you thought about this? This bug is blocking the integration of eeepc-acpi

Bug#589625: acpi-support: Providing the option to suspend on lid close would be useful

Package: acpi-support Version: 0.137-3 Severity: normal Hi, on eeepc-acpi-scripts we suspend the laptop by default on lid close. This is because there were some concerns that leaving it on would lead to overheating; this hypothesis is probably unfounded, but still we would like to keep an

Bug#572942: mtkbabel doesn't work with Holux M-241 fw 1.13 due to log format change

Hi Uwe, Are you planning to package the new version of mtkbabel for squeeze? The old one doesn't support some new gps models and firmware, which is kinda annoying if you own one. If you are not interested in this package any more, I would be glad to maintain it (I'm not a DD but I'm already

Bug#574349: splix performs unaligned memory access; prints blank pages an armel

Hi, are you planning on pulling this patch any time soon? This bug is really annoying since it prevents using splix on any ARM print server. If you don't have time at the moment, I could prepare a NMU and see if my sponsor is keen to upload it. Cheers, Luca -- To UNSUBSCRIBE, email to

Bug#586366: closed by Luca Niccoli lultimou...@gmail.com (Bug#586366: fixed in fswebcam 20100622-1)

Could you please send me a call trace? run strace -ocalls.txt -d V4L1:/dev/video0 a.jpg and send calls.txt If you manage to get one from the old version, that could prove useful too. Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#586366: closed by Luca Niccoli lultimou...@gmail.com (Bug#586366: fixed in fswebcam 20100622-1)

Oh, and please would you check file permissions for /dev/video0? Just in case... Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#587662: deluge-gtk: hangs on exit

Package: deluge-gtk Version: 1.2.3-1 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Deluge hangs on exit, and needs a sigkill to rest in peace. This is solved upstream in changeset 5766e049876ff67ee6e8e3c502a8da3bb09405a0 Cheers, Luca - -- System Information:

Bug#581312: [Pkg-acpi-devel] Bug#581312: acpi-support: Wireless toggling is broken

Sleeping 5 seconds before bringing up the interfaces improves reliability a lot (At times I was still getting wpa_supplicant not connecting because the interface was down). Cheers, Luca state-funcs Description: Binary data

Bug#586924: [Pkg-acpi-devel] Bug#586924: Acknowledgement (acpi-support: Rules calling acpi_fakekey cause events to be reported tiwce)

On 24 June 2010 10:33, Michael Meskes mes...@debian.org wrote: Which version of the Eee PC do you have? Please have a look into /etc/acpi/asus-brn-up.sh for instance. It already checks for the original Eee PC and does nothing on these systems. Apparently the same action should be done on

Bug#581312: [Pkg-acpi-devel] Bug#581312: acpi-support: Wireless toggling is broken

Ah, it seems I misunderstood. I thought every solution would need poking and you just chose wicd among the alternatives. If this line is only needed for wicd users I'm perfectly fine with it. To be perfectly fair, I'm sure only that wicd needs poking and wpa_supplicant on its own doesn't. But

Bug#586924: [Pkg-acpi-devel] Bug#586924: Acknowledgement (acpi-support: Rules calling acpi_fakekey cause events to be reported tiwce)

Hi, I remembered that we're doing the same kind of test in eeepc-acpi-scripts (only the other way around), by using test -d /sys/bus/platform/devices/eeepc || exit 0 It would be good for consistency if you would use test -d /sys/bus/platform/devices/eeepc exit 0 to bail out on eeepcs. The

Bug#586366: fswebcam: double free or corruption (fasttop) with stv680 that works with V4L1 0x0000000000c57280 ***

Hi timo, a new version of fswebcam has been uploaded and should hit the archive soon. I'm reasonably sure it should fix the double free problem; it could be that you still get Trying source module v4l1... Error opening device: open: No such file or directory if you don't explicitly specify V4L1

Bug#581312: [Pkg-acpi-devel] Bug#581312: acpi-support: Wireless toggling is broken

On 23 June 2010 08:46, Michael Meskes mes...@debian.org wrote: Exactly. We would need at least a Recommend here. Why? using wicd doesn't enhance acpi-support, nor it is necessary in any way. If the problem is the error message, the amended version attached avoids it. (wpa_supplicant and

Bug#586924: acpi-support: Rules calling acpi_fakekey cause events to be reported tiwce

Package: acpi-support Version: 0.136-3 Severity: important New kernels (since some time before 2.6.32) synthesize XF86 keyboard event themselves (at least in asus_acpi and eeepc-laptop, but from a look at the sources I reckon it's generally true for modules in drivers/platform/x86); since

Bug#586924: Acknowledgement (acpi-support: Rules calling acpi_fakekey cause events to be reported tiwce)

Moreover, /etc/acpi/events/asus-brightness-* (which have only the purpose of synthesizing keyboard events) catch a whole lot of unrelated hotkeys on EEEPCs, making acpi-support unusable on them (basically almost every hotkey dims your screen down). This problem was masked by a bug in acpi-fakekey,

Bug#581312: [Pkg-acpi-devel] Bug#581312: acpi-support: Wireless toggling is broken

On 15 June 2010 18:47, Michael Meskes mes...@debian.org wrote: Is it possible to keep the old stuff as a fall back solution? Would that make sense at all? I think it would be hard to do (the main problem is that rfkill devices are not uniquely linked to wireless interfaces, so trying to use

Bug#577603:

reassign 577603 acpi-fakekey 0.136-3 thank you I guess now that acpi_fakekey has its own package, this report should be assigned to it; but I mainly wanted to say that I'm hitting this bug as well, on two different machines (both sid). If I'm in the console, and run acpi_fakekey 5, a 4 gets

Bug#581312: [Pkg-acpi-devel] Bug#581312: acpi-support: Wireless toggling is broken

On 13 May 2010 01:40, Luca Niccoli lultimou...@gmail.com wrote: This is my first attempt. It's supposed to be a drop-in replacement for /usr/share/acpi-support/state-funcs I still have to try it with lenny's kernel, though (will try before next week) This is a revised version, the previous

Bug#581518: fswebcam: New upstream release 20100405

On 13 May 2010 16:07, Philip Heron p...@sanslogic.co.uk wrote: Yes, hopefully within a couple of weeks. Cool, I'll wait and package that then. Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#569720:

Hi, this is most probably due to both eeepc-acpi-scripts and something in your windows environment both handling the volume keys. The way to solve it is to change /etc/defaults/eeepc-acpi-scripts so that FnF_MUTE, FnF_VOLUMEDOWN and FnF_VOLUMEUP are set to 'NONE'. The default will be probably

Bug#569720:

Hi, this is most probably due to both eeepc-acpi-scripts and something in your windows environment both handling the volume keys. The way to solve it is to change /etc/defaults/eeepc-acpi-scripts so that FnF_MUTE, FnF_VOLUMEDOWN and FnF_VOLUMEUP are set to 'NONE'. The default will be probably

Bug#581518: fswebcam: New upstream release 20100405

On 13 May 2010 13:57, Patrick Matthäi pmatth...@debian.org wrote: Please package it :) The new upstream version is really the one in debian now, with patches merged. I thought I'd wait until closer to the release, and then package it just for the sake of cleanness if there aren't new versions.

Bug#581312: [Pkg-acpi-devel] Bug#581312: acpi-support: Wireless toggling is broken

On 12 May 2010 13:20, Michael Meskes mes...@debian.org wrote: Sure, feel free to send patches. This is my first attempt. It's supposed to be a drop-in replacement for /usr/share/acpi-support/state-funcs I still have to try it with lenny's kernel, though (will try before next week) Cheers,

Bug#581312: acpi-support: Wireless toggling is broken

Package: acpi-support Version: 0.136-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 /usr/share/acpi-support/state-funcs begins with IFACE_NAMES=`cut -d: -f1 -s /proc/net/wireless` and then uses strings in $IFACE_NAMES to know wich interfaces are to be turned off and on. But if

Bug#578889: acpi-support: please remove unnecessary asus-eee-* rules

Package: acpi-support Version: 0.133-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The three rules /etc/acpi/events/asus-eee-* only synthetize keysyms, but this is done already by the kernel in squeeze. The lenny kernel does not (AFAICS from the source), but Eee users at the

Bug#578264: amarok: crashes at startup

Package: amarok Version: 2.3.0-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The new debian version doesn't even make it to the screen. Worked fine with 2.3.0-1 Here's the backtrace from the KDE crash handler: Application: Amarok

Bug#578264: amarok: crashes at startup

That fixed it. Installing an updated version of the same script that caused the crash doesn't bring troubles too. I wonder how this happened just with a new debian (not upstream) version of amarok... FTR, the culprit was Ultimate Lyrics. Cheers, Luca -- To UNSUBSCRIBE, email to

Bug#562884:

Wouldn't a suid program specifically designed to exempt processes from the OOM killer be a huge security bug? Every user would be able to kill a machine by memory starvation. What makes more sense to me would be to let root choose to disable the most security sensible SysRq keys. Cheers, Luca

Bug#562884:

Luca Niccoli wrote: What makes more sense to me would be to let root choose to disable the most security sensible SysRq keys. Err, actually I meant to default disabling them. Setting /proc/sys/kernel/sysrq to 448 would seem reasonable. Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs

  1   2   3   >