Bug#853231: Please update xsensor to newer fork
Hi Jeremy, I am no longer actively maintaining Xsensors and just sent a request to orphan the package in bug #839654. I'm not familiar with the process of replacing a package with a fork. Perhaps the next maintainer can look into this. Regards, Nanley On Mon, Jan 30, 2017 at 10:20 AM, Jeremy Newton wrote: > Package: xsensors > Version: 0.70 > Severity: wishlist > > I forked xsensors a while ago due to upstream no longer being active. > > Please consider changing the xsensors debian package to my fork, as it has > some bug fixes and new features, including GTK3 support, preferences and > appdata: > https://github.com/Mystro256/xsensors > > Thanks!
Bug#665668: xsensors chokes on unsupported sensor features
Hi John, I traced through the xsensors source and discovered that the author already implements a feature-checking mechanism like your patch. I noticed that the actual problem was the early termination in the start_gui function's while loop. A new revision containing the fix should be on its way. Thank you for bringing this unfavorable behavior to light. Looking at the 'fix-feature-parse.patch' file, for future patches I would recommend limiting comments to explaining your code if it's hard to understand. If you would like to talk about your patch and comment on the structure of the application, I would recommend doing that through email or possibly putting that information in the patch header (see http://dep.debian.net/deps/dep3/ ). Thanks again, Nanley On Fri, May 25, 2012 at 11:22 PM, John Vogel jvog...@stny.rr.com wrote: Hi Nanley, Thanks for taking the time to look into this. If you see any need for improvements in the patches, I will be interested to see what you have to say. My time at present is very limited, but I'll be glad to help as much as I'm able. Cheers, John On 05/10/2012 08:21 PM, Nanley Chery wrote: Hi John, Thank you very much for your patches! I have recently finished a semester of school and thus will have time to review your work in the coming weeks. I appreciate your patience on this issue. Thanks, Nanley
Bug#665504: xsensors chokes on command line optins
Hi John, Testing out xsensor's command line options work well on my system. I only seem to get the GUI failed error as a result of there being no sensors loaded on my computer. As such I have written a patch to notify the user of this situation. Please test it and let me know if this resolves your issue. It seems your patch would fix the instance of a user giving a command-line option as well as a chip name, such as: $xsensors -f coretemp0 (but it should work without the option) Is this how you get the above error? I am a bit hesitant to apply this patch since specifying a chipname is not an official upstream feature.. I will have to consult other maintainers on how to proceed for the future maintainability of this package. Thanks, Nanley On Sat, Mar 24, 2012 at 11:47 AM, John Vogel jvog...@stny.rr.com wrote: Package: xsensors Version: 0.70-2 Severity: important Tags: patch Dear Maintainer, On new hardware and fresh installation, xsensors failed to start. From the command line, I got the error GUI failed!. Tried various options, but nothing helped. After running it through gdb and seeing a problem with the command line parsing, I came up with the patch that is attached to this bug report. This fixes the command line problem. Now that I could get xsensors to handle the command line, I found another problem. When setting up the subfeatures for the chip, if it finds something other than a temp, fan, or volt feature, it stops processing sensors and displays what it has (including an empty tab for sensor it choked on). Patch forthcoming. Regards, John Vogel jvog...@stny.rr.com -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/6 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 xsensors depends on: ii libatk1.0-0 2.2.0-2 ii libc6 2.13-27 ii libcairo2 1.10.2-7 ii libfontconfig1 2.8.0-3.1 ii libfreetype62.4.8-1 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-02.30.2-6 ii libgtk2.0-0 2.24.10-1 ii libpango1.0-0 1.29.4-3 ii libsensors4 1:3.3.1-2 Versions of packages xsensors recommends: ii lm-sensors 1:3.3.1-2 xsensors suggests no packages. -- no debconf information setup-sensors.patch Description: Binary data
Bug#665668: xsensors chokes on unsupported sensor features
Hi John, Thank you very much for your patches! I have recently finished a semester of school and thus will have time to review your work in the coming weeks. I appreciate your patience on this issue. Thanks, Nanley On 3/24/2012 11:04 PM, John Vogel wrote: Package: xsensors Version: 0.70-2 Severity: important Tags: patch Dear Maintainer, Here is the other patch I mentioned in #665504 as forthcoming. When add_sensor_tab() probes the sensor's subfeatures, if it finds one that is upsupported by xsensors, it stops probing. If any supported senors have already been set up, then these get displayed (as well as the empty tab for the unsupported sensor). If no supported sensors are setup before this choke, then all subsequent sensors are ignored and the console sees: Couldn't parse chipname_of_chip! Exiting! GUI failed! Attached patch just does a quick loop through the sensor's features. If a supported feature is found, it allows add_sensor_tab() to do it's thing. If not, it forces the outer loop to skip to the next sensor, if there is one. For your convience, I also attached a rolled patch that also covers #665504 and this report. Regards, John Vogeljvog...@stny.rr.com -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/6 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 xsensors depends on: ii libatk1.0-0 2.2.0-2 ii libc6 2.13-27 ii libcairo2 1.10.2-7 ii libfontconfig1 2.8.0-3.1 ii libfreetype62.4.8-1 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-02.30.2-6 ii libgtk2.0-0 2.24.10-1 ii libpango1.0-0 1.29.4-3 ii libsensors4 1:3.3.1-2 Versions of packages xsensors recommends: ii lm-sensors 1:3.3.1-2 xsensors suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625435: Package fixes
Hey Matthias, I have prepared a new revision which should fix this bug. I'm currently just waiting for an upload. Thanks, Nanley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622005: patch for the issue
Hello Andreas, Thank you for the patch. It seems this bug is simply a problem stemming from the usage of deprecated GTK+ API. I am not so sure that we should change the compiler options. I unfortunately do not have the time to delve into it right now, but I will in a couple weeks. Thanks again, Nanley On Fri, 2011-04-15 at 23:27 +0200, Andreas Moog wrote: tag 622005 + patch user ubuntu-de...@lists.ubuntu.com usertags 622005 + origin-ubuntu natty ubuntu-patch thanks *** /tmp/tmpJpiFAK In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/ftbfs_werror.patch: Don't compile with -Werror * debian/patches/ftbfs_gtkfunction.patch: Don't use deprecated GtkFunction Both patches fix a FTBFS (LP: #755940) (Closes: #622005) Thanks for considering the patch. -- System Information: Debian Release: squeeze/sid APT prefers natty APT policy: (500, 'natty') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-8-generic (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#384428: xsensors needs unclutter -noevents
reassign 384428 unclutter #thanks Looking at other reports online it seems that unclutter has this problem with many gtk apps [1] and the fix Therefore, I'm reassigning this bug to unclutter. Maybe the maintainer can merge this with the related unclutter bug [2]. Thanks. [1] https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/385034 http://www.mail-archive.com/fvwm-work...@lists.math.uh.edu/msg14134.html http://code.google.com/p/xmonad/issues/detail?id=45 http://tech.groups.yahoo.com/group/links-browser/message/2145 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266118 On Sun, 2010-01-10 at 17:32 +0100, Marc-Jano Knopp wrote: quit On Sun, 2010-01-10, at 16:08:27 (+0100), Nanley Chery wrote: Please try again with version 0.60 as it provides support for these chipsets. Tried 0.60, and the problem still persists, although the load is not 100 % anymore, but 50 % on each of my 2 cpu cores (AMD64, 2 x 2.6 GHz). -noevents still prevents this behavior, with the potential problems noted my the original bug report (Emacs and maybe others). Regards Marc-Jano -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562905: sensors-applet: new upstream version (2.2.5) available
Package: sensors-applet Version: 2.2.4-2 Severity: wishlist Please update sensors-applet to version 2.2.5, Changelog (2.2.4 - 2.2.5) : * Add support for ATI GPUs using proprietary driver * Add support for monitoring disk temperatures via devicekit-disks * Add zh_CN translation * Cleanup old compatibility code and drop support for older version of GTK+ and Glib - now require 2.14 for both Upstream: http://sensors-applet.sourceforge.net/index.php?content=source Downstream: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/380669 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#446530: I have 0.60 mostly packaged
Hi Nick, I run Ubuntu and I've been working on packaging 0.60. I have attached, the debian directory compressed with my changes. I have a couple questions about some of the files: * debian/copyright: I tried updating it to the new debhelper suggested file, but I wasn't sure writing your name with (C) was legally, morally, or technically correct? The last section especially. * debian/changelog: Most other changes is mentioned here. + changes not mentioned: files updated as per lintian recommendations - rules control. Thanks debian.tar.lzma Description: application/lzma-compressed-tar
