Bug#1067547: FTBFS: "vsnprintf is so broken we can't compensate. Sorry."

The check for whether snprintf and vsnprintf honors its length argument was failing due to the use of -Werror=implicit-function-declaration in Debian's builds now. https://sourceforge.net/p/wmweatherplus/git/ci/393394818cf4aa9b34071297a6947409cb19d74b/ should fix it for you.

Bug#989315: composer: Needs update for GitHub token format change

Package: composer Version: 2.0.9-2 On March 4, 2021, GitHub announced a change to the format of their tokens: https://github.blog/changelog/2021-03-04-authentication-token-format-updates/ A few days later, Composer updated their token validation regex to account for the new token format:

Bug#989260: exim4-config: Default configuration enables sieve filters but cannot deliver from them

Package: exim4-config Version: 4.94.2-6 The default configuration provided by exim4-config allows for sieve filters to be used in ~/.forward, but if a user attempts to configure such a filter their mail delivery will most likely break. More specifically, the keep action (including the default

Bug#986117: yarnpkg is not compatible with node-proper-lockfile 3.0.0+

Package: yarnpkg Version: 1.22.10+~cs22.25.14-2 Yarn uses proper-lockfile to implement its `--mutex=file:whatever` option. Its package.json depends on proper-lockfile ^2.0.0, which had the calling convention lockfile.lock( file, options, callback ) In proper-lockfile 3.0.0 they removed that

Bug#980775: your initial example also fails with upstream

On Sat, 23 Jan 2021 15:37:08 +0100 Paolo Greppi wrote: > you need to add the following as in my previous message: > >cd foo >yes '' | yarn init >cd .. Yes. The example was simplified to show exactly the bug at hand, not to fully work. I confirm that your patch fixes the bug I was

Bug#980775: yarnpkg is not compatible with node-uuid 7.0.0+

Package: yarnpkg Version: 1.22.10+~cs22.25.14-1 >From https://www.npmjs.com/package/uuid/v/7.0.1#default-export-removed: > Default Export Removed > > uuid@3 was exporting the Version 4 UUID method as a default export: > > const uuid = require('uuid'); // <== REMOVED! > > This usage pattern was

Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

Package: node-mkdirp Version: 1.0.4-2 Severity: critical I don't know whether to report this against node-mkdirp for breaking compatibility, or yarnpkg for depending on "node-mkdirp (>= 0.5.1)" rather than "node-mkdirp (>= 0.5.1), node-mkdirp (<<1.0.0)". Either way, things are currently broken in

Bug#970525: docker.io: Unable to start minikube/kubernetes containers: unable to find user 0: invalid argument

On Sun, Sep 20, 2020 at 09:58:45AM +0700, El boulangero wrote: > Do you know what's special with the `tianon/true` image? On what OS/release > is it based? It's an image that contains only a single binary that returns 0. That binary uses no libraries, not even libc. It's intended as an extremely

Bug#970525: docker.io: Unable to start minikube/kubernetes containers: unable to find user 0: invalid argument

Here's a simpler test case: $ sudo dpkg -i docker.io_19.03.12+dfsg1-4_amd64.deb (Reading database ... 257350 files and directories currently installed.) Preparing to unpack docker.io_19.03.12+dfsg1-4_amd64.deb ... Unpacking docker.io (19.03.12+dfsg1-4) over (19.03.12+dfsg1-3) ...

Bug#933230: acpid: Race during startup can result in event devices not being opened

Package: acpid Version: 1:2.0.31-2 When using netlink and the input layer, acpid opens the existing devices in /dev/input/event* first and only after sets an inotify to be told about newly created devices. If an event device is created between the time acpid reads the directory and the time it

Bug#919019: Interval timers with CLOCK_*_CPUTIME_ID fail to reschedule with 4.19.13-1

Package: linux-image-4.19.0-1-amd64 Version: 4.19.13-1 The attached test program should print about 100 lines each for "Hit CLOCK_MONOTONIC!", "Hit CLOCK_PROCESS_CPUTIME_ID!", and "Hit CLOCK_THREAD_CPUTIME_ID!". On my laptop running kernel linux-image-4.19.0-1-amd64 version 4.19.13-1, however,

Bug#909109: php-memcached package is missing support for PHP 7.0, 7.1, and 7.3

Package: php-memcached Version: 3.0.4+2.2.0-3 For some reason the current version of the package only contains the extension files for PHP 7.2, while Debian currently also has packages php7.0, php7.1, and php7.3. $ dpkg -c php-memcached_3.0.4+2.2.0-3_amd64.deb drwxr-xr-x root/root 0

Bug#909111: php-redis package is missing support for PHP 7.0, 7.1, and 7.3

Package: php-redis Version: 4.1.1-1 For some reason the current version of the package only contains the extension files for PHP 7.2, while Debian currently also has packages php7.0, php7.1, and php7.3. $ dpkg -c php-redis_4.1.1-1_amd64.deb drwxr-xr-x root/root 0 2018-08-19 09:14 ./

Bug#909110: Extraneous 'L' in /usr/bin/phpize7.3

Package: php7.3-dev Version: 7.3.0~alpha3-1 There's an extraneous 'L' at the end of line 14 of /usr/bin/phpize7.3 which causes it to fail to copy the files necessary for "make test". $ phpize7.3 Configuring for: PHP Api Version: 20180606 Zend Module Api No: 20180606 Zend

Bug#901353: wmifs segfaults occasionally

Package: wmifs Version: 1.8-1 I noticed that wmifs was randomly crashing on my laptop. I have no idea how to reproduce it besides letting it run for a long time, it didn't seem to be associated with hibernation or anything else obvious. If I have multiple instances running, usually only one will

Bug#850660: nodejs-dev: npm conflicts transitively with libssl-dev since nodejs-dev 4.7.2~dfsg-1

It looks like this is fixed with nodejs version 8.9.3~dfsg-1. * Backport #16130: support both openssl 1.0.1 and 1.1.0 Add openssl/fixups.patch to take care of additional fixes. * Build against latest ssl-dev version Only took a year...

Bug#879475: php-igbinary: Please recompile to support php7.1

Package: php-igbinary Version: 2.0.1-1 The package does not contain the shared library compiled for php 7.1, only for php 7.0. Simply recompiling it locally with dpkg-buildpackage produces a package that contains the necessary shared library and other infrastructure, and seems to function

Bug#879477: php-redis: Please recompile to support php7.1

Package: php-redis Version: 3.1.2-1 The package does not contain the shared library compiled for php 7.1, only for php 7.0. Simply recompiling it locally with dpkg-buildpackage produces a package that contains the necessary shared library and other infrastructure, and seems to function correctly.

Bug#879476: php-msgpack: Please recompile to support php7.1

Package: php-msgpack Version: 2.0.2+0.5.7-1 The package does not contain the shared library compiled for php 7.1, only for php 7.0. Simply recompiling it locally with dpkg-buildpackage produces a package that contains the necessary shared library and other infrastructure, and seems to function

Bug#872879: wmaker menu lost most of my apps

On Fri, Aug 25, 2017 at 06:03:20PM -0400, Doug Torrance wrote: > Ok, great! So it seems like the issue was that the WMRootMenu in your home > directory was no longer pointing to the correct file. > > Do you think the correct fix to this bug would be better documentation for > the change? Or

Bug#872879: wmaker menu lost most of my apps

On Tue, Aug 22, 2017 at 08:58:01AM -0400, Doug Torrance wrote: > What are the contents of your ~/GNUstep/Defaults/WMRootMenu One line: /etc/GNUstep/Defaults/menu.hook Removing ~/GNUstep/Defaults/WMRootMenu brings back some/most of the applications, although all the submenus are somewhat

Bug#872879: wmaker menu lost most of my apps

Package: wmaker Version: 0.95.8-2 After upgrading from 0.95.8-1 to 0.95.8-2, the menu seems to have lost the vast majority of my applications. ~/.xsession-errors tells me the following: /usr/lib/WindowMaker/wmaker(configureMenu(rootmenu.c:1513)): warning: using default menu file

Bug#857050: firefox no longer plays sound without pulseaudio daemon

For the record, the upstream bug asking them to reverse this poor decision is at https://bugzilla.mozilla.org/show_bug.cgi?id=1345661

Bug#854407: procps: kill -l doesn't work

Package: procps Version: 2:3.3.12-3 POSIX specifies that "kill -l " should print the symbolic name of the signal (without the SIG prefix). The binary supplied by procps ignores the signum argument. $ /bin/kill -l 11 HUP INT QUIT ILL TRAP ABRT BUS FPE KILL USR1 SEGV USR2 PIPE ALRM TERM STKFLT

Bug#850660: nodejs-dev: npm conflicts transitively with libssl-dev since nodejs-dev 4.7.2~dfsg-1

I've been unable to upgrade nodejs and nodejs-dev thanks to this issue: I need npm for some things, but also php7.0-dev (which depends on libssl-dev) for something else.

Bug#842952: firefox: Things that are still bad with GTK+3 enabled

One thing that has really been bugging me is that the buttons in webpages are crazily large, breaking the layout of sites that expect buttons to have more normal dimensions. Selection lists, input fields, checkboxes, and radio buttons are also enough larger to be annoying. In 49.0-4: button:

Bug#826407: Missing dependency on php-igbinary

Package: php-redis Version: 2.2.7-394-g892f928+2.2.7-3 After upgrading to the mentioned version of the package, I see the following warning when running PHP. PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20151012/redis.so' - /usr/lib/php/20151012/redis.so: undefined

Bug#805519: wmifs: Buffer overflow on startup. Process crashes.

This recently started happening to me locally. In my case, at least, it turns out to be due to wmifs blindly assuming all interface names are 8 bytes or shorter (including the trailing nul). Looks like IFNAMSIZ has been 16 for some time now. --- wmifs.c.orig2016-04-19 07:34:59.873085155

Bug#815794: [php-maint] Bug#815794: Broken symlink: /usr/lib/php5/build/ltmain.sh

On Wed, Feb 24, 2016 at 04:26:50PM +0100, Ondřej Surý wrote: > On Wed, Feb 24, 2016, at 16:24, ano...@users.sourceforge.net wrote: > > On Wed, Feb 24, 2016 at 03:52:42PM +0100, Ondřej Surý wrote: > > > Yeah, > > > > > > just use php-dev (that pulls php7.0-dev); src:php5 is going away from > > >

Bug#815794: [php-maint] Bug#815794: Broken symlink: /usr/lib/php5/build/ltmain.sh

On Wed, Feb 24, 2016 at 03:52:42PM +0100, Ondřej Surý wrote: > Yeah, > > just use php-dev (that pulls php7.0-dev); src:php5 is going away from > unstable and testing when we finish the transition to PHP 7.0. I wonder how many of the incompatible changes in PHP 7 will require working around in

Bug#815794: Broken symlink: /usr/lib/php5/build/ltmain.sh

Package: php5-dev Version: 5.6.17+dfsg-3 The file /usr/lib/php5/build/ltmain.sh is symlinked to ../../../share/libtool/config/ltmain.sh, which does not exist in the libtool package as of version 2.4.6-0.1 (it was present in 2.4.2-1.11). The new path seems to be

Bug#777140: Using mdadm to install Debian on Intel RST RAID array stopped working between Wheezy 7.8 and Jessie RC1

I ran into this problem recently on an ASUS UX301L. Worse, I ran into it after *upgrading* to Jessie, the system wouldn't even boot anymore because it couldn't assemble the root device. After narrowing it down to mdadm and IMSM, I came across this workaround:

Bug#800445: nf_conntrack: table full, dropping packet

On Sat, Oct 03, 2015 at 02:33:22AM +0100, Ben Hutchings wrote: > > I think I found the fix for this, but please can you test the attached > patch? (Instructions for building a patched kernel package are at > .)

Bug#800445: nf_conntrack: table full, dropping packet

Package: linux-image-4.2.0-1-amd64 Version: 4.2.1-2 After booting the kernel image provided by this package and attempting to connect to the Internet, network access doesn't actually work. The message "nf_conntrack: table full, dropping packet" is repeatedly logged. Comparing the contents of the

Bug#755726: alsa-utils: arecord doesn't exit when -d is specified

What seems to be going on here is that the loop in capture() is expecting pcm_read() to return the passed-in count, while pcm_read() is insisting that the count be equal to the chunk size. Thus the last read for the timelimit is considered to have failed, and it then gets stuck in a loop creating

Bug#561281: util-linux hwclock problems with rtc not in utc, resolved?

Wow, old bug. I don't have my system clock set to local time anymore, so I'm not able to test this. Sorry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#741532: fonts-linuxlibertine: Odd font priority for Linux Libertine,Times

Package: fonts-linuxlibertine Version: 5.3.0-2 Expected result: $ fc-match 'Linux Libertine O,Times' LinLibertine_R.otf: Linux Libertine O Regular $ fc-match 'Linux Libertine,Times' LinLibertine_R.otf: Linux Libertine O Regular Actual result: $ fc-match 'Linux Libertine O,Times'

Bug#628654: xbindkeys: New release blocks seahorse

This should have been in the NEWS.Debian file, so apt-listchanges would have flagged it on upgrade. I rebooted my laptop this morning and had to track down why xbindkeys suddenly wasn't running. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#737247: gparted resizes partition to smaller than the filesystem

On Wed, Feb 05, 2014 at 01:14:23PM -0500, Phillip Susi wrote: The end sector also is not aligned to a 1 MiB boundary. The explanation for that seems simple enough: this drive itself is not a multiple of 1 MiB in size, the partition was using the whole drive, and I never told gparted to change

Bug#737694: Should support Interface name

Package: network-manager-vpnc Version: 0.9.8.6-1 For firewall rules, it would be nice if the VPN interface could be configured to have a predictable name instead of generic tun0. It turns out vpnc already supports this, we just need to expose the option in NetworkManager. diff -urN

Bug#571438: Does not set up root device on boot

Looking into this bug again, it seems that it's the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1011704. udev apparently needs OPTIONS+=db_persist set at some point in the initrd or it throws away the necessary information. I've made this change locally (adding the attached file

Bug#720434: Bug #720434: php5-cli installs incorrect /etc/php5/cli/php.ini

found 720434 5.5.8+dfsg-3 thanks Does no one care about fixing this bug? It seems simple enough, just use the right config file. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

On Mon, Feb 03, 2014 at 07:45:39PM +, Mike Fleetwood wrote: Can you confirm the version of Debian you are using as my attempt to re-create the bug on my normal distribution didn't find an issue. I'm using unstable. gparted version 0.17.0-4. On Mon, Feb 03, 2014 at 02:02:34PM -0700,

Bug#737247: gparted resizes partition to smaller than the filesystem

Package: gparted Version: 0.17.0-4 I tried to shrink-and-move a partition on an external hard drive. It seems that gparted shrunk the parition to 93768726 4K blocks, but then resized the parition to only 750149807 512-byte sectors (93768725.875 4K blocks). The post-shrink e2fsck then errored out

Bug#736965: Network detection fails in 2014-01-28 daily installer

Package: installation-reports Preparing to install Debian on my new T430, which has an e1000e on eth0 and an Intel Centrino Advanced-N 6205 (supported with iwlwifi and non-free firmware) as wlan0. I formatted a USB stick, copied the contents of boot.img.gz,[1] copied the netinst ISO,[2] and

Bug#720434: php5-cli installs incorrect /etc/php5/cli/php.ini

Package: php5-cli Version: 5.5.2+dfsg-1 When attempting to run a command-line PHP program that has run in the past, I received errors that pcntl_signal was disabled. It appears that sometime recently php5-cli started copying its php.ini from /usr/share/php5/php.ini-production instead of

Bug#720433: libapache2-mod-php5: Segmentation fault in 5.5.2+dfsg-1

Package: libapache2-mod-php5 Version: 5.5.2+dfsg-1 Severity: important After upgrading php and apache this afternoon, I receive many segfaults from my local MediaWiki installation. Downgrading libapache2-mod-php5 and the various php5-* packages to 5.5.1+dfsg-2 fixes the problem. Backtrace:

Bug#711689: No longer ignores '.dpkg-dist' files in /etc/laptop-mode/conf.d/

Package: laptop-mode-tools Version: 1.63-2 I noticed today that my console bell wasn't working, despite the volume being set appropriately. Having seen this issue before, I quickly found that /sys/module/snd_hda_intel/parameters/power_save was being set to 2 instead of 0 whenever I unplugged the

Bug#669883: notification-daemon crashes in gdk_pixbuf_scale_simple

Ok, I think I have this worked out. GTK is throwing a critical warning, and since notification-daemon calls g_log_set_always_fatal (G_LOG_LEVEL_ERROR | G_LOG_LEVEL_CRITICAL) it results in SIGTRAP where most GTK-using programs will just output a message to stderr. The problem seems to be that

Bug#669883: notification-daemon crashes in gdk_pixbuf_scale_simple

Same problem here, although I'm not sure what switching to the default Gnome theme would entail. I note that downgrading libgtk-3-0 and libgtk-3-common to 3.2.3-1 makes the problem go away. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#615020: xdm: ConsoleKit support

It's sad that upstream doesn't seem to care about this bug. I refreshed the patch against 1.1.11. Nothing has changed in the patch itself, just the diff metadata and contexts so it will actually apply. diff -bBurN a/debian/control b/debian/control --- a/debian/control 2011-10-23

Bug#636323: notification-daemon: crashes on wrong type of 'transient' hint

found 636323 0.7.2-1 tags 636323 patch thanks This patch against 0.7.2-1 seems to fix the problem. What it does is check the type of the incoming hint and use the appropriate g_variant_get_* function. It also applies the same fix for the resident and action-icons hints. ---

Bug#639356: Bluez udev rules attempt to access /usr when /usr may not be mounted

Package: bluez Version: 4.96-1 The file /lib/udev/rules.d/97-bluetooth.rules installed by this package contains calls to programs in /usr, which may not be mounded at the time it is first used during boot. This causes error messages to be printed during boot as udev complains about being unable

Bug#639359: lintian should check if udev rules attempt to access programs in /usr

Package: lintian Version: 2.5.2 Severity: wishlist Rules installed into /lib/udev/rules.d may be called at boot before /usr is mounted. Any rules files installed into this directory that attempt to access binaries in /usr will fail with an error message printed at boot, and whatever the rule was

Bug#634325: cups-polld does not properly handle network errors, uses 100% CPU in loop

found 634325 1.4.8-2 fixed 634325 1.5.0-1 thanks The patch seems to have been applied upstream in 1.5.0. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#634325: cups-polld does not properly handle network errors, uses 100% CPU in loop

Package: cups Version: 1.4.7-1 Tags: patch If cups-polld runs into a network error after connecting to a remote IPP server while polling, it will wind up in an endless loop using 100% CPU. This can be quickly tested using the following procedure: 1. Configure cups with BrowsePoll to poll a

Bug#624678: I can confirm this bug

On Fri, Jul 08, 2011 at 07:21:01PM +0530, Ritesh Raj Sarraf wrote: That should be it. Please let me know if that fixes the problem. I suspect the %k in /lib/udev/lmt-udev won't get expanded correctly, in this line: exec /usr/sbin/laptop_mode force modules=usb-autosuspend

Bug#624678: 99-laptop-mode.rules uses programs in /usr

On Sun, May 01, 2011 at 12:56:18AM +0530, Ritesh Raj Sarraf wrote: On 04/30/2011 07:11 PM, ano...@users.sourceforge.net wrote: The file 99-laptop-mode.rules installed by this package contains calls to programs in /usr, which may not be mounted at the time it is first used during boot. This

Bug#624678: 99-laptop-mode.rules uses programs in /usr

On Sun, May 01, 2011 at 10:09:41PM +0530, Ritesh Raj Sarraf wrote: I'm not sure about this error. I've not seen it on my laptop. That rule is supposed to run when there's an Add event in the USB subsystem. Does it generate events at boot time? Yes. Can you give me steps on how to reproduce

Bug#624678: 99-laptop-mode.rules uses programs in /usr

Package: laptop-mode-tools Version: 1.57-1 The file 99-laptop-mode.rules installed by this package contains calls to programs in /usr, which may not be mounted at the time it is first used during boot. This causes numerous error messages to be printed during boot as udev complains about being

Bug#556694: FTBFS with binutils-gold

Here is a patch to configure.ac to make it pull in the needed libraries. Note that the selinux check must be moved, otherwise PKG_CHECK_MODULES skips setting XDM_LIBS entirely; as an alternative, you could have it set some other variable than XDM_LIBS and merge it in later. --- a/configure.ac +++

Bug#568169: devicekit-disks forgets dm devices on udevadm trigger

Package: devicekit-disks Version: 009-2 Executing udevadm trigger causes devicekit-disks to forget all dm devices (i.e. lvm volumes and luks cleartext devices). See the attached session transcript. Script started on Tue 02 Feb 2010 01:16:31 PM EST # devkit-disks --enumerate

Bug#567363: evince cannot correctly save some pdf forms

Package: evince Version: 2.28.2-1 Some PDF forms, such as http://www.irs.gov/pub/irs-pdf/f1040es.pdf, can be opened with evince and edited fine, but when saving all the changes are forgotten and the modified fields in the saved version can no longer be edited. When saving, evince outputs the

Bug#566174: gtk apps set WM_COMMAND incorrectly on the leader window

Package: libgtk2.0-0 Version: 2.18.6-1 Gtk apps but don't set WM_COMMAND correctly on their leader window. Most end up setting it to just the filename component of argv[0], while a few that call g_set_prgname before gtk_init set it to whatever name was passed to g_set_prgname, which may not even

Bug#566174: gtk apps set WM_COMMAND incorrectly on the leader window

I suppose it would help if I actually sent the testcase. /* gcc -Wall foo.c -o foo `pkg-config --cflags --libs gtk+-2.0` */ #include gtk/gtk.h int main(int argc, char **argv){ g_set_prgname(this-will-be-wrong); gtk_init(argc, argv);

Bug#565479: Vorbis plugin should support METADATA_BLOCK_PICTURE

Package: xmms2-plugin-vorbis Version: 0.6DrMattDestruction-7 Severity: wishlist Tags: patch Just as mp3 files can contain embedded cover art via the APIC frame, vorbis files can contain images in a METADATA_BLOCK_PICTURE comment. See http://wiki.xiph.org/index.php/VorbisComment#Cover_art for

Bug#547382: Detect windows recovery partitions (fix provided)

I'm not sure if it came that way or if it got changed by the Debian installer (snapshot from 2009-12-11), but the recovery partition on my new Thinkpad T500 is type 7 rather than 27. The recovery partition is also detected as Vista rather than 7, FWIW. This check along the same lines as the

Bug#561243: Obsolete udev rules

Package: barry-util Version: 0.15-1 udev has begun complaining about the use of certain keys deprecated since 2006. It issues the following complaints related to this package's rules file: udevd[1337]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event

Bug#561281: /lib/udev/rules.d/85-hwclock.rules screws up time on udevadm trigger if hw clock is not UTC

Package: util-linux Version: 2.16.2-0 /lib/udev/rules.d/85-hwclock.rules attempts to adjust the system clock when /dev/rtc0 becomes available. However, it uses --systz rather than --hctosys, which means that instead of reading the RTC it just assumes that the system clock is the correct UTC time

Bug#561126: Please work around Firefox bug 492459 (Websites are no longer rendered if SSL requests for JavaScripts are blocked by a proxy)

Package: privoxy Version: 3.0.15-2 Severity: wishlist Tags: patch Firefox (and thus Iceweasel) since 3.0.10 has a bug[1] in which it will wait forever for a javascript file to load if the SSL proxy (e.g. privoxy) returns a failure status code in response to the CONNECT. Since javascript must be

Bug#514463: Poor bounds checking causes abnormal exits or crashes

Package: gfpoken Version: 0.31-2 There are small regions to the right of and below the grid that cause gfpoken to fail when they are clicked, due to poor bounds checking in the click event handlers. For example: 1. Clicking the right region in line with the top row of the grid manipulates the

Bug#465388: wmacpi doesn't work with sysfs

On Wed, Feb 13, 2008 at 10:14:40PM +0100, Julien BLACHE wrote: I've just uploaded 2.2~rc1-4, please tell me how well/bad it goes. Works fine, thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#465388: wmacpi doesn't work with sysfs

Package: wmacpi Version: wmacpi-2.2~rc1 wmacpi fails to give any battery data on my system (2.6.24.2 from kernel.org, also tested on 2.6.24.1). This seems to be due to the fact that wmacpi attempts to access BAT1/energy_*, while these values are not available on my laptop. $ ls