3 Jul 2007 13:15
6 Jul 2007 14:18
problem with statusbar_external
I use the latest snapshot (20070608) and statusbar_external script this way:
In my cfg_ion.lua I have:
-- ---
statusbar_external = {
...
}
dopath ("statusbar_external")
dopath("mod_statusbar")
-- ---
and on startup ion says:
Ion startup error log:
>> Errors starting ion-statusd:
/usr/lib/ion3/bin/ion-statusd: Unable to find 'statusd_cpufreq' on
search path.
/usr/lib/ion3/bin/ion-statusd: Unable to find 'statusd_acpibat' on
search path.
/usr/lib/ion3/bin/ion-statusd: Unable to find 'statusd_cpupolicy'
on search path.
These are meters, defined in statusbar_external={}. And they work
fine! But such message is being displayed on each startup. Should I
try to fix statusbar_external.lua in any way or is it a mod_statusbar
issue?
6 Jul 2007 14:52
Re: problem with statusbar_external
* Vladimir Chizhov <jagoterr@...> [070706 14:30]: > Should I try to fix statusbar_external.lua in any way or is it a > mod_statusbar issue? Quoting http://modeemi.fi/~tuomov/repos/ion-scripts-3/ : If you are using ion-3ds-20060107 or later, using statusd_exec.lua instead of this old version is suggested. -- -- Bye, Andreas
6 Jul 2007 18:18
RandR revisited
Hi,
I have just upgraded my trusty Slackware box to recently released
12.0. This brings about an upgrade to the X.org 7.1 X server.
Unfortunately, the ion2 module mod_xrandr-2 has stopped working. I
have debugged the issue as much as I could, and I am afraid I am not
proficient enough in X programming to carry on.
Here's what seems to be going on:
- XRandR registring and so on works.
- Ion (and mod_xrandr) also get the X event notifications for randr
events.
- However, the call
FIND_WINDOW_T(rev->root,WScreen)
in mod_xrandr.c returns NULL, suggesting that Ion is unable to get a
hold of a WScreen object that is correlated with rev->root (rev
being the notification event), if I understand correctly.
What is going wrong here all of a sudden? Can anybody offer me some
advice as to how to proceed from here?
Thanks in advance,
Toby.
--
--
Expect the worst, it's the least you can do.
6 Jul 2007 19:20
Re: RandR revisited
On 2007-07-06, Tobias Dussa <tdussa@...> wrote: > Unfortunately, the ion2 module mod_xrandr-2 has stopped working. How about upgrading to Ion3? -- -- Tuomo
7 Jul 2007 10:03
Re: RandR revisited
Tuomo, I'm sorry I'm ripping this thread apart, but for some reason, I have not yet received your reply. I did, however, see it in the online archives, so I'll answer to it. Your question was why I didn't upgrade to ion3. Mainly, the reason is that Ion3 is still just an RC, while Ion2 is labled "stable". Thus, for my production machine, I preferred to stick to ion2. Now, I have tested ion3 on my upgraded machine, and the xrandr problem went away, admittedly. However, I have to say that I do have a hard time migrating my config files from ion2 to ion3.Either way, I was under the impression that ion2 was still "the" officially supported stable version, so I assumed that you'd be interested to hear about the xrandr problem, and I had hoped that someone could help me fix it. Cheers, Toby. -- -- I am Gates of Borg. Resistance is futile. You will be assimilated. From now on, you will finance... us.
7 Jul 2007 10:20
Re: RandR revisited
On 2007-07-07, Tobias Dussa <tdussa@...> wrote: > Either way, I was under the impression that ion2 was still "the" > officially supported stable version, so I assumed that you'd be > interested to hear about the xrandr problem, and I had hoped that > someone could help me fix it. Ion2 may still (for a few months) be grudgingly officially supported, but mod_xrandr has never been properly supported. It's just something that is available, and I'm not going to start going to lengths to debug problems with an old Ion2 version, now that Ion3 will be released soon(tm). (Just one more RC, hopefully...) -- -- Tuomo
7 Jul 2007 11:07
Re: RandR revisited
Tobias Dussa <tdussa@...> writes: > Your question was why I didn't upgrade to ion3. Mainly, the reason is > that Ion3 is still just an RC, while Ion2 is labled "stable". Thus, for > my production machine, I preferred to stick to ion2. I (and lots of other people) have been using ion3 for years on my production machine without real troubles. So, stability is not really an argument indeed. -- -- Matthieu
8 Jul 2007 11:51
ion-3rc-20070708
This third "rc" release again simply fixes some minor problems in the previous release. -- -- Tuomo
7 Jul 2007 11:57
Re: RandR revisited
Hi, On Sat, Jul 07, 2007 at 11:07:41AM +0200, Matthieu Moy wrote: > > Your question was why I didn't upgrade to ion3. Mainly, the reason is > > that Ion3 is still just an RC, while Ion2 is labled "stable". Thus, for > > my production machine, I preferred to stick to ion2. > I (and lots of other people) have been using ion3 for years on my > production machine without real troubles. So, stability is not really > an argument indeed. I have never said so. Indeed, I have never really used ion3 at all. All I am saying is that, according to the web page, ion2 is the current stable release. That's all. It may very well be that ion3 is very stable already, but that is not the point. It is not labeled the current "stable" (production) version, so I didn't use it, because apparently the developers themselves don't think that ion3 is good enough to be labeled "stable" yet (although that may not be far down the road). Cheers, Toby. -- -- If "Microsoft Word" is the right tool to write longer texts, then why is it not called "Microsoft Sentence" or "Microsoft Paragraph"?
RSS Feed