>A few days ago I sent a proposal to add a HAL backend for power
>management. Meanwhile, I fixed call Suspend and added support for
>governor (not tested).
>
>I also noticed that setting the brightness and governor is in
>condition
>WITH_UPOWER, although in fact uses Trinity DBus daemon => has
>nothing to
>do with upower. I added to the option WITH_TDEHWLIB_DAEMONS and
>fixed
>incorrect WITH_UPOWER conditions.
>
>Please test it. At the same time I'm waiting for your opinions -
>incorporate it or not?
To test these improvements, an operating system with HAL installed
is needed?
Darrell
>I's not the session manager changes. It looks like the failure is
>due to
>the changes to the TDEApplication API that allowed Bug 760 to be
>fixed.
>I'll need to see why smoke is failing to parse tdeapplication.h
>(yet
>*again*).
Ok. With libtqt-perl I see this build failure message:
/bin/ld: cannot find -lsmoketqt
Darrell
>Hello,
>
>A few days ago I sent a proposal to add a HAL backend for power
>management. Meanwhile, I fixed call Suspend and added support for
>governor (not tested).
>
>I also noticed that setting the brightness and governor is in
>condition
>WITH_UPOWER, although in fact uses Trinity DBus daemon => has
>nothing to
>do with upower. I added to the option WITH_TDEHWLIB_DAEMONS and
>fixed
>incorrect WITH_UPOWER conditions.
>
>Please test it. At the same time I'm waiting for your opinions -
>incorporate it or not?
Just curious, not trying to make trouble, but do these changes and
the recent TDEApplication API changes mean the hard freeze was
lifted? I don't have a problem with that, I'm just curious of the
project status.
Darrell
>Tim,
>
>With the latest git from today, I see the foolowing build errors:
>
>x_10.cpp:16439:5: error: 'x_TDEApplication::x_TDEApplication(bool,
>
>bool)' cannot be overloaded
>x_10.cpp:16418:5: error: with
>'x_TDEApplication::x_TDEApplication(bool, bool)'
>x_10.cpp:16446:5: error:
>'x_TDEApplication::x_TDEApplication(bool)'
>cannot be overloaded
>x_10.cpp:16425:5: error: with
>'x_TDEApplication::x_TDEApplication(bool)'
>x_10.cpp:16453:5: error: 'x_TDEApplication::x_TDEApplication()'
>cannot be overloaded
>x_10.cpp:16432:5: error: with
>'x_TDEApplication::x_TDEApplication()'
I'm presuming this has something to do with the latest session
manager changes. I was able to build both packages until then.
Darrell
>> Was the release announcement for 3.5.13.2 sent to any media
>folks?
>>
>It was on major russian news feeds dedicated to the opensource
>software.
>Can't say anything about world-wide feeds.
Not exactly helping our own cause. :-(
Darrell
Tim,
k3bhalconnection.cpp:845:70: error: no matching function for call
to 'TDEStorageDevice::mountDevice(const TQString&, TQString&)'
Proposed patch, based upon today's tdebase patch:
diff -urN k3b/libk3bdevice/k3bhalconnection.cpp
k3b.new/libk3bdevice/k3bhalconnection.cpp
--- k3b/libk3bdevice/k3bhalconnection.cpp 2013-04-05
22:32:35.000000000 -0500
+++ k3b.new/libk3bdevice/k3bhalconnection.cpp 2013-08-09
21:35:42.121489109 -0500
@@ -840,9 +840,9 @@
TDEStorageDevice* sdevice =
static_cast<TDEStorageDevice*>(hwdevice);
// FIXME
- // Options from 'options' are not currently loaded into
'optionString'
- TQString optionString;
- TQString mountedPath = sdevice->mountDevice(mountPoint,
optionString);
+ // Options from 'options' are not currently loaded into
'mountOptions'
+ TDEStorageMountOptions mountOptions;
+ TQString mountedPath = sdevice->mountDevice(mountPoint,
mountOptions);
if (mountedPath.isNull()) {
return org_freedesktop_Hal_CommunicationError;
}
@@ -869,8 +869,8 @@
TDEStorageDevice* sdevice =
static_cast<TDEStorageDevice*>(hwdevice);
// FIXME
- // Options from 'options' are not currently loaded into
'optionString'
- TQString optionString;
+ // Options from 'options' are not currently loaded into
'mountOptions'
+ TQString mountOptions;
if (!sdevice->unmountDevice(NULL)) {
// Unmount failed!
The patch allowed be to build k3b, although you know more than me
what is happening.
Darrell
>Looks good, go ahead and push. What is happening is that it was
>brought
>to my attention that the TDE HW library API inadvertently assumed
>the
>usage of pmount in all cases. Therefore, I updated the API to use
>a more
>generic method of specifying mount options; apparently I missed a
>few
>users of the TDE HW library such as k3b.
Pushed in commit 8633f5b9.
Darrell
>if you are interested in another tester for Slackware 14.0, and
>you
>can point me towards some up-to-date instructions on how to
>acquire
>and compile R14.0, I'd be happy to give it a try and report on any
>issues I find.
I no longer have my web site running, where originally I had that
documentation and build scripts. If you are interested then contact
me directly off list. I don't want to offer my build scripts
publicly. My build scripts are complex because I am one of the main
testers for Trinity. I need flexibility with how I compile and
test. That said, I would enjoy seeing somebody reduce the build
scripts to a point that theoretically could become slackbuilds.org
compatible. :-)
As a side note, would be nice if there was somebody using 13.1 or
13.37 who could compile Trinity with HAL support to ensure that
part of Trinity still functions as expected. I've gone full 14.0
here on all systems because that reduces my own time and overhead.
Probably likewise for you. That said, if there were simpler build
scripts (like the KDE3 scripts in Slackware 12.2) and a basic wiki
(we could add such a page to the Trinity wiki), then others running
13.1 or 13.37 could test and enjoy Trinity too. :-)
There are other Slackers who want to run Trinity (browse the LQ
forum), but there are no wiki pages or build scripts to make that
more accessible for Slackers. :-( Possibly if we work together we
could make that happen?
Darrell
>I am unable to login through TDM when the account uses IceWM. I
>can
>login with KDM (4.10.2) using IceWM. This seems to affect all
>accounts.
>
>No problems with IceWM when logging in from the command line and
>startx.
>
>No problems using TDM with other window managers or desktops, such
>
>as Xfce or Fluxbox.
>
>Anybody else experience this or confirm?
I see the following in the xsession-error log:
/usr/bin/icewm-session: /usr/bin/icewm-session: cannot execute
binary file
The file is chmod 755 and works fine from startx.
I get a similar error message when trying to use twm:
/usr/bin/twm: /usr/bin/twm: cannot execute binary file
The problem affects root as well as non-root accounts.
Darrell