en esta conversacion entera esta el aviso de un parche [para que
network manager funcione perfecto en kde3 knetworkmanager, la
situacion es que el iconito de redes de venenux es realmente
knetworkmanager, el cual es de kde3 , y ya saliendo kde4 estaba sin
so[porte, gracias al proyecto trinity, haora revive esto, actualizare
las fuentes el meircoles en la noche en valencia sino lo hago en los
teques..
AVISADO SALGO EL MARTES PARA ALLA VALENCIANOS.. manana completo el
remaster tutorial en el proyecto comunitario
On 9/19/11, Ilya Chernykh <anixxsus(a)gmail.com> wrote:
> On Monday 19 September 2011 18:47:43 you wrote:
>> On Monday 19 September 2011 18:03:28 Timothy Pearson wrote:
>>
>> > >> That being said, I do not believe this patch is complete. Yes, it
>> > >> compiles, but there is code that directly references
>> > >> "org.freedesktop.NetworkManagerUserSettings". According to the NM
>> > >> 0.9
>> > >> porting guide att
>> > >> http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.ht…,
>> > >> the NetworkManagerUserSettings service has been completely removed
>> > >> from
>> > >> NM
>> > >> 0.9.
>> > >
>> > > I may be wrong but seems that NetworkManagerUserSettings belongs to
>> > > knetworkmanager,
>> > > not to the NM backend.
>> >
>> > No, from what I can tell NetworkManagerUserSettings was primarily part
>> > of
>> > NetworkManager, and anything left in knetworkmanager is vestigial at
>> > this
>> > point and needs to be replaced with the new "secret agent" NM 0.9 DBus
>> > service.
>>
>> There were two services: one for server part and one for client part is
>> how I
>> understand it. And the client service is launched from knetworkmanager or
>> another applet.
>> In the NM there is no need for client service, and the client can call
>> directly the NM "agent" service.
>>
>
> In the NM 0.9 I meant.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> For additional commands, e-mail:
> trinity-devel-help(a)lists.pearsoncomputing.net
> Read list messsages on the Web archive:
> http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post:
> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
>
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
Hello, I'm trying to build kdelibs 3.5.12 on RHEL 5 (which is getting a
bit old, but still supported by RH, and widely used in companies).
When compiling krandr, it fails with the following output:
make[2]: entrant dans le répertoire «
/home/albator/rpmbuild/BUILD/kdelibs/krandr »
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I.. -I../dcop -I../kdecore -I../kio/kssl -I../kjs -I./.. -I../dcop
-I../libltdl -I../kdefx -I../kdecore -I../kdecore -I../kdecore/network
-I../kdeui -I../kio -I../kio/kio -I../kio/kfile -I..
-I/usr/lib64/qt-3.3/include -include tqt.h -I. -I/opt/trinity/include
-I/opt/trinity/include/tqt -DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG
-O2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o
lowlevel_randr.lo lowlevel_randr.c
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop -I../kdecore -I../kio/kssl
-I../kjs -I./.. -I../dcop -I../libltdl -I../kdefx -I../kdecore
-I../kdecore -I../kdecore/network -I../kdeui -I../kio -I../kio/kio
-I../kio/kfile -I.. -I/usr/lib64/qt-3.3/include -include tqt.h -I.
-I/opt/trinity/include -I/opt/trinity/include/tqt -DQT_THREAD_SUPPORT
-D_REENTRANT -DNDEBUG -O2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64
-mtune=generic -c lowlevel_randr.c -fPIC -DPIC -o .libs/lowlevel_randr.o
In file included from lowlevel_randr.c:23:
lowlevel_randr.h:102:7: warning: no newline at end of file
In file included from lowlevel_randr.c:24:
lowlevel_randr.h:29: error: expected specifier-qualifier-list before
'RRCrtc'
lowlevel_randr.h:44: error: expected specifier-qualifier-list before
'RROutput'
lowlevel_randr.h:55: error: expected specifier-qualifier-list before
'XRRScreenResources'
lowlevel_randr.h:90: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '*' token
lowlevel_randr.h:91: error: expected ')' before '*' token
lowlevel_randr.h:92: error: expected ')' before '*' token
lowlevel_randr.h:93: error: expected declaration specifiers or '...'
before 'RROutput'
[...]
and so on ... (the full log is attached to this mail)
It seems that RHEL5 Xrandr version (1.1.1) is too old for krandr.
I have no idea of what is the most reasonable way to go:
Should I try to compile a newer version of Xrandr ? Is that even
possible without compiling a lot of other stuff ?
Should I disable krandr in kdelibs makefile ? What will be the
consequences on further compiled packages ?
Should I revert all krandr-related patches to recover older KDE3
functionalities ?
Thanks in advance for your enlightenment :-)
Francois Andriot
Hello all,
I did the same (double) error twice, with obviously the same result
twice. The first time, I continue to use the system, which meant that I
did not know where was the error.
The objective was to install Firefox 5.0.
1 - I copied a directory /usr/local/firefox/ from a system used before
2 - I tried to edit a firefox icon coming also from the other system,
3 - I completely uninstalled firefox using Synaptic (that did not
removed the ~/.mozilla/).
At the end of stage 2, TDE changed their behavior: the icon (firefox)
disappeared from the office, and TDE "showed" the launch of an
application (clicking on a desktop icon) by in the magnifying. I had
initially inhibited this option (called "bouncing cursor", I think).
I do not know which of point two or three is causing the problem, but at
the following reboot, TDE showed blue cursors and finally "Can not open
theme file /opt/kde/share/apps/kdm/themes/kubuntu-kde3/ ". In the
current working installation, there is no /opt/kde/ but /opt/kde3/. Once
the session opened, there was no menu Start. (I am not ready to live
without it!)
I am currently with a screen size of 1152x864 that comes out of a
magician's hat (this is the very first time it appens with THIS
format!), while after the last system restore (and associated wasted
time), throw in usual 1280x1024. I have already indicated the unsolved
problem of ATI drivers installation in another post.
Sincerly,
Patrick
# cat /home/user/Desktop/poub/Firefox.desktop
[Desktop Entry]
Categories=Application;Network;WebBrowser;X-Ximian-Main;X-Ximian-Toplevel;
Comment=Navigateur Web
Comment[fr]=Navigateur Web
Exec[$e]=firefox %U
GenericName=
GenericName[fr]=
Icon=/usr/local/firefox/icons/mozicon128.png
MimeType=application/xhtml+xml;text/html
Name=Firefox
Name[fr]=Firefox
NotShowIn=GNOME;
Path[$e]=
StartupNotify=true
Terminal=false
TerminalOptions=
TryExec=firefox
Type=Application
X-DCOP-ServiceType=
X-KDE-SubstituteUID=false
X-KDE-Username=
X-SuSE-translate=true
Hi!
A bugreport has been filled by the SUSE legal department regarding licensing problems in kstars (part of kdeedu3).
The problem prevents inclusion of this package in distribution.
The bugreport reads as follows:
===
Whereas the README.images file in kstars is informative, it unfortunately does
not precisely state which _files_ are licensed under which license. It rather
states descriptions of images which are licensed under certain licenses.
The unacceptable licenses from the README.images file would be:
FFNP
FFE
Thus, please examine which _files_ in kstars (if any) are licensed under the
above licenses. If such files exist, they should be removed.
===
You can read the bugreport here:
https://bugzilla.novell.com/show_bug.cgi?id=718027
So can anybody please clarify which files in kstars are under which license?
Hello,
I'm compiling TQTinterface 3.5.12 on RHEL 5, but I get an error on "make
install".
I have to apply the attached patch to install correctly.
It looks like the $(MKDIR_P) comand must be written in lowercase, not
uppercase.
François Andriot
Hi all,
So KDE4 uses a technology called "Solid" that is a layer (like TQt to
Qt) to HAL/udev.
Apparently all the applications use device commands through this,
which is why the HAL -> udev
migration was near-flawless in KDE4.
Is it possible we could use this technology?
--
later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu