xsensors (0.70-1) unstable; urgency=low
* New upstream release.
- Swap voltage limits depending on the chip wiring. (Closes: #441138)
- Provides support for all libsensors4 supported chips. (Closes: #460170)
* Dropped previous patches due to upstream switching to newer
xsensors (0.70-1) unstable; urgency=low
* New upstream release.
- Swap voltage limits depending on the chip wiring. (Closes: #441138)
- Provides support for all libsensors4 supported chips. (Closes: #460170)
* Dropped previous patches due to upstream switching to newer
** Changed in: xsensors (Debian)
Status: Unknown = Fix Committed
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in ubuntu.
** Changed in: xsensors (Debian)
Status: Unknown = Fix Committed
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: xsensors (Debian)
Importance: Undecided = Unknown
** Changed in: xsensors (Debian)
Status: Fix Released = Unknown
** Changed in: xsensors (Debian)
Remote watch: None = Debian Bug tracker #460170
--
[hardy] Error opening config file: /etc/sensors.conf
** Changed in: xsensors (Debian)
Importance: Undecided = Unknown
** Changed in: xsensors (Debian)
Status: Fix Released = Unknown
** Changed in: xsensors (Debian)
Remote watch: None = Debian Bug tracker #460170
--
[hardy] Error opening config file: /etc/sensors.conf
This proposed update has been in hardy-proposed for half a year without
any feedback. Therefore it was removed from hardy-proposed again.
** Changed in: xsensors (Ubuntu Hardy)
Status: Fix Committed = Won't Fix
** Changed in: xsensors (Ubuntu Intrepid)
Status: Fix Committed = Won't
This proposed update has been in hardy-proposed for half a year without
any feedback. Therefore it was removed from hardy-proposed again.
** Changed in: xsensors (Ubuntu Hardy)
Status: Fix Committed = Won't Fix
** Changed in: xsensors (Ubuntu Intrepid)
Status: Fix Committed = Won't
Did anyone test the packages in hardy or intrepid -proposed and can give
some feedback here? Thanks!
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Did anyone test the packages in hardy or intrepid -proposed and can give
some feedback here? Thanks!
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Tags: fixed
** Changed in: xsensors (Debian)
Importance: Unknown = Undecided
** Changed in: xsensors (Debian)
Status: Fix Committed = New
** Changed in: xsensors (Debian)
Remote watch: Debian Bug tracker #460170 = None
** Changed in: xsensors (Debian)
Status: New = Fix
Tags: fixed
** Changed in: xsensors (Debian)
Importance: Unknown = Undecided
** Changed in: xsensors (Debian)
Status: Fix Committed = New
** Changed in: xsensors (Debian)
Remote watch: Debian Bug tracker #460170 = None
** Changed in: xsensors (Debian)
Status: New = Fix
skrimpy-
If you run 'xsensors' and you get a tiny minimized-looking window that
is blank when you expand the bug is fixed. This is NOT the bug. This
simply means that you either don't have the sensors setup or they don't
exist for your hardware- try sudo sensors-detect as was mentioned. The
I'm just going to assume my hardware is incompatible with xsensors and
bow out of this then, because I've done everything suggested and it's
still not working. I think I've been pretty extensive in what's going
on in my earlier posts and I don't want to hold up a bug fix if the
problem is on my
I'm trying to test this with my Hardy install and things are not going
well. I'm not familiar with testing proposed packages so maybe I'm
doing something wrong.
But I've tried adding the -proposed repositories using the above FAQ on
how to and I keep getting this error:
W: GPG error:
That error just means that you've added something from a PPA here but
you haven't added the key to authenticate the packages. It will still
allow you to install the packages.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug
I'm feeling dense here so tell me if I'm doing something wrong:
I added the packages as specified.
Entered aptitude via this command: sudo aptitude -t hardy-proposed
did a search and located xsensors
used + to add it to install, then g and g to install it.
it installed, but it's still not
When you say it isn't working, what do you mean? Is it giving you an
error?
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
when I open the program this is what happens:
First it opens in an extremely small window (I have to hunt for it)
When I expand it it's just a blank white window - no information.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this
That is the original bug exactly as I remember it.
On Fri, Sep 11, 2009 at 9:31 AM, skrimpy milkand...@gmail.com wrote:
when I open the program this is what happens:
First it opens in an extremely small window (I have to hunt for it)
When I expand it it's just a blank white window - no
maybe this is an issue with my hardware... I tried launching xsensors
from the command line and got error:
Sensor 'adm1025' not supported by xsensors!
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you
I don't know what all that stuff you were referring to above regarding
adding packages, etc. has to do with getting Xsensors to work but all
things being equal, if you have a stock installation of Jaunty and you
install Xsensors from Synaptic and then afterwards go to the terminal
and run the
wpshooter, I am not using Jaunty - I'm on Hardy.
I tried what you suggested, including a reboot of my system and Xsensors
is still not working (the same problem is occuring both from the menu
and the command line)
--
[hardy] Error opening config file: /etc/sensors.conf
Sorry, I missed that.
Then you are correct. Does not as of yet work on Hardy.
I don't think it would work on the previous version (Gutsy) either. But
I believe that it did work on the version that came before Gutsy.
This is one reason why I switched to Jaunty.
I think the efforts to get it
Please try the version from hardy-proposed. If you don't want to add the
repository, you can get the .deb from here:
https://edge.launchpad.net/ubuntu/+source/xsensors/0.50-1ubuntu2.8.04
Direct link for i386:
see comment #28. I'm on Jaunty now but the fix worked fine for me on
Hardy. I believe it was a one line change involving the location of the
configuration file that determines which sensors should be used/polled.
--
[hardy] Error opening config file: /etc/sensors.conf
I am pretty positive I already installed that version via aptitude after
following the instructions above.
I'm further led to believe I already installed it because when I
downloaded the .deb you linked to I was informed by the package
installer that the status was Same version is already
Dillinger417 I've tried the /etc/sensors.conf change referenced above
and it didn't work for me.
I looked at your comment #28 but I didn't really understand what steps
you went through. Could you explain it?
and wpshooter - in regards to upgrading from Hardy - I've considered it
but the
That should say Jaunty...
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Right, but this bug is about the backported fix for Hardy and Intrepid,
we need people to test these.
Thanks!
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Xsensors works fine in both Jaunty and also under the latest version of
Karmic that I tested.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Anyone else who can test this? This is lingering in -proposed for three
months already. I'll remove it from -proposed soon if we can't get any
feedback.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you
** Branch linked: lp:ubuntu/karmic/xsensors
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/hardy-proposed/xsensors
** Branch linked: lp:ubuntu/intrepid-proposed/xsensors
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Nice work on the fix guys, but I'm no longer using Hardy; someone else
will have to give feedback on this bug :(
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Accepted xsensors into intrepid-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: xsensors (Ubuntu
motu-sru ping?
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm not sure that this is really worth an SRU, can this please be
ack'ed/nack'ed by motu-sru?
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm attaching the debdiff for a SRU to Hardy. I've also uploaded it for
Intrepid (changing hardy-proposed to intrepid-proposed, and
0.50-1ubuntu2.8.04 to 0.50-1ubuntu2.8.10 in debian/changelog).
There's some config.* noise in the patch but getting ride of it requires
modifying debian/rules, so
I tested the the patch ( xsensors_0.50-1ubuntu3.diff.gz ) on my Hardy
machine using pbuilder and it fixed the issue without any new problems.
I would like to see this get submitted for an SRU, so I subscribed
ubuntu-universe-sponsors since I cannot upload. Hopefully that was the
correct next step
No, it is fixed in Jaunty. If the fix there works fine (can someone
please confirm this?) doing a Stable Release Update for Intrepid and
Hardy can be considered. See
https://wiki.ubuntu.com/StableReleaseUpdates
--
[hardy] Error opening config file: /etc/sensors.conf
I will test it in Jaunty.
Will post results when I have finished.
Thanks.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Xsensors seems to install work just fine under Jaunty daily build for
me.
Now if we could get it to work for us persons that are still using Hardy
and/or Intrepid.
Thanks.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug
Thanks for your patch. I've upload it :).
There was a bit of junk in the debdiff (namely, the automatic changes to
config.{guess,sub} and accidentally touching the previous changelog
entry.), though, which you should try to avoid in the future. Also, the
urgency (in debian/changelog) should
This bug was fixed in the package xsensors - 0.50-1ubuntu3
---
xsensors (0.50-1ubuntu3) jaunty; urgency=low
* Check for sensors3.conf if sensors.conf doesn't exist (LP: #206280)
-- Felipe Xavier lipe.lok...@gmail.com Sun, 11 Jan 2009 22:45:55
-0200
** Changed in: xsensors
Is this problem with the Xsensors program fixed for the Hardy version of
Ubuntu ?
If so, how do I get it ? I do not see any 0.50-lubuntu3 in Synaptic in
Hardy. I see 0.50-lubuntu2 but not 3.
Thanks.
--
[hardy] Error opening config file: /etc/sensors.conf
** Changed in: xsensors (Ubuntu)
Status: Fix Released = Confirmed
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Felipe:
What does status FIX RELEASED, mean in the e-mail that I received
regarding this bug ?
I installed xsensors from Synaptic, then ran sensors-detect, restarted
machine and still NOTHING when clicking on xsensors on the systems tools
menu.
I am running Hardy. I have all available updates
I suggest an upstream version update for xsensors (
xsensors_0.50-1ubuntu3 ) that fix this bug.
** Attachment added: xsensors_0.50-1ubuntu3.diff.gz
http://launchpadlibrarian.net/21113464/xsensors_0.50-1ubuntu3.diff.gz
--
[hardy] Error opening config file: /etc/sensors.conf
And here is the debdiff file.
** Attachment added: xsensors_0.50-1ubuntu3.debdiff
http://launchpadlibrarian.net/21113474/xsensors_0.50-1ubuntu3.debdiff
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because
So is this too late to include in Hardy? ( comment #9 -
https://bugs.launchpad.net/ubuntu/+source/lm-
sensors/+bug/206280/comments/9 )
Shouldn't the nomination for hardy be set as Invalid then?
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You
Unsubscribing ubuntu-main-sponsors as there is currently nothing to
sponsor.
What does that mean ? It would be nice to give a PLAIN/COMMON
explanation instead of these type of messages.
If this is supposed to mean that this bug is fixed, then I beg to differ
!!!
Thanks.
--
[hardy] Error
2008/11/23 wpshooter [EMAIL PROTECTED]:
Unsubscribing ubuntu-main-sponsors as there is currently nothing to
sponsor.
What does that mean ?
That nobody has provided a fix, so there's no need for the
ubuntu-main-sponsors team (who reviews patches and if they are okay
uploads them to Ubuntu) to
Unsubscribing ubuntu-main-sponsors as there is currently nothing to
sponsor.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: lm-sensors (Ubuntu)
Importance: Undecided = High
** Changed in: xsensors (Ubuntu Hardy)
Importance: Undecided = High
** Changed in: lm-sensors (Ubuntu Hardy)
Importance: Undecided = High
--
[hardy] Error opening config file: /etc/sensors.conf
** Changed in: xsensors (Ubuntu)
Status: Triaged = Fix Released
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
this hasn't been fixed. using latest (64bit) package in hardy's
repository, newly installed system about 2 days old.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is
this hasn't been fixed. using latest packages in hardy's repository,
newly installed system about 2 days old.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@tyme
This bug is fixed for intrepid, not hardy. (Though I believe it
should, as the app simply doesn't function correctly.)
On Thu, Jun 26, 2008 at 4:46 PM, tyme [EMAIL PROTECTED] wrote:
this hasn't been fixed. using latest packages in hardy's repository,
newly installed system about 2 days
seems to be solved with the last update of tonight. Bye
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I confirm this also testing intrepid-64bit
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Declining the nomination for Hardy as it is already too late for this.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: xsensors (Ubuntu)
Status: New = Triaged
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
try 'xsensors -c /etc/sensors3.conf' or copy /etc/sensors3.conf to
/etc/sensors.conf
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@pkundtz: Yes, doing that would let xsensors work; however, the problem
lies far deeper than that - as shown in the debian bug report.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of
I have also been having this problem...
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Final Freeze in four days!
politelyIs there any chance this bug will be fixed?/politely
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Chuck: can you take a look at it?
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm preparing a merge against the latest version in Debian.
** Changed in: xsensors (Ubuntu)
Status: New = In Progress
** Changed in: xsensors (Ubuntu)
Status: In Progress = New
** Changed in: lm-sensors (Ubuntu)
Assignee: (unassigned) = Siegfried Gevatter (RainCT) (rainct)
The latest lm-sensors Debian revision should fix this.
It can be downloaded from:
http://ftp.de.debian.org/debian/pool/main/l/lm-sensors/lm-sensors_2.10.5-5.dsc
A debdiff to preserve the existing Ubuntu change is attached.
** Changed in: lm-sensors (Ubuntu)
Assignee: Siegfried Gevatter
** Changed in: xsensors (Debian)
Status: Unknown = Fix Committed
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net/bugs/206280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- [hardy] xsensors creates misnamed sensors.conf
+ [hardy] Error opening config file: /etc/sensors.conf
** Description changed:
Binary package hint: xsensors
I installed xsensors 0.50 from add/remove. I clicked on the icon and the
program didn't start. I ran it in
72 matches
Mail list logo
