[opensuse-kde] Apper in openSUSE 12.1?
Hi everyone, I just finished reading this blog post: http://dantti.wordpress.com/2011/10/10/apper-released/ and I was wondering if it will be included in openSUSE 12.1. I remember that somebody asked this already but I cannot find the mail anywhere in the mailing list. If anybody can give a reply or point me to a previous reply I'll be grateful. Cheers, Ricardo. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 10 Oct 2011 19:02:27 José Ricardo De León Solís wrote:
Hi everyone, I just finished reading this blog post: http://dantti.wordpress.com/2011/10/10/apper-released/ and I was wondering if it will be included in openSUSE 12.1. I remember that somebody asked this already but I cannot find the mail anywhere in the mailing list. If anybody can give a reply or point me to a previous reply I'll be grateful.
Ismail was in contact with Daniele about Apper and gave him a load of feedback about things that needed fixed for it to replace KPackageKit for us. Let's get his take on it. In the meantime we can package Apper 1.0 and look at it. The other mail you refer to was on 21 September from Jean Cayro. Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, Oct 11, 2011 at 9:40 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Monday 10 Oct 2011 19:02:27 José Ricardo De León Solís wrote:
Hi everyone, I just finished reading this blog post: http://dantti.wordpress.com/2011/10/10/apper-released/ and I was wondering if it will be included in openSUSE 12.1. I remember that somebody asked this already but I cannot find the mail anywhere in the mailing list. If anybody can give a reply or point me to a previous reply I'll be grateful.
Ismail was in contact with Daniele about Apper and gave him a load of feedback about things that needed fixed for it to replace KPackageKit for us. Let's get his take on it. In the meantime we can package Apper 1.0 and look at it.
The other mail you refer to was on 21 September from Jean Cayro.
Will
"Replace KPackageKit" and "included in openSUSE 12.1" are not necessarily the same thing ;) -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday, October 11, 2011 02:05:50 AM todd rme wrote:
On Tue, Oct 11, 2011 at 9:40 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Monday 10 Oct 2011 19:02:27 José Ricardo De León Solís wrote:
Hi everyone, I just finished reading this blog post: http://dantti.wordpress.com/2011/10/10/apper-released/ and I was wondering if it will be included in openSUSE 12.1. I remember that somebody asked this already but I cannot find the mail anywhere in the mailing list. If anybody can give a reply or point me to a previous reply I'll be grateful.
Ismail was in contact with Daniele about Apper and gave him a load of feedback about things that needed fixed for it to replace KPackageKit for us. Let's get his take on it. In the meantime we can package Apper 1.0 and look at it.
The other mail you refer to was on 21 September from Jean Cayro.
Will
"Replace KPackageKit" and "included in openSUSE 12.1" are not necessarily the same thing ;)
-Todd They should be. KPackageKit is an embarrasment. I always have to give a disclaimer on it when recommending openSUSE to a client. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 11 Oct 2011 06:17:13 Roger Luedecke wrote:
On Tuesday, October 11, 2011 02:05:50 AM todd rme wrote:
"Replace KPackageKit" and "included in openSUSE 12.1" are not necessarily the same thing ;)
-Todd
They should be. KPackageKit is an embarrasment. I always have to give a disclaimer on it when recommending openSUSE to a client.
Can you nicely summarize your problems with it? Apper is a rename and update of KPackageKit so it likely shares some of them. Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Tirsdag den 11. oktober 2011 16:37:20 skrev Will Stephenson:
On Tuesday 11 Oct 2011 06:17:13 Roger Luedecke wrote:
On Tuesday, October 11, 2011 02:05:50 AM todd rme wrote:
"Replace KPackageKit" and "included in openSUSE 12.1" are not necessarily the same thing ;)
-Todd
They should be. KPackageKit is an embarrasment. I always have to give a disclaimer on it when recommending openSUSE to a client.
Can you nicely summarize your problems with it? Apper is a rename and update of KPackageKit so it likely shares some of them.
On 11.4 users reported all kinds of problems with it. * Failure to install local rpms (when clicking them in Dolphin, error related to tmp files or plaindir repo, can't quite remember) * Reporting patches, saying it installed them, then 10 minutes later it would notify about the exact same patches again and fail to install them once again and so forth. * It would crash, and therefore check for updates every 5-10 minutes, instead of once per day as configured. * Taking ~15 minutes to build a cache or something Actually it would be easier to list the things that _did_ work smoothly with KPK on 11.4, than the ones which didn't (of course it's totally unclear to me if the failures should be blamed on KPK, PK or PK-zypp or d-bus.. or any of the other layers upon layers involved in the stack). However in my testing of KPK on 12.1beta it seemed to be able to install both local rpms and patches pretty smoothly, so if Apper is even better, that sounds great. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 11 October 2011 09:40:10 Will Stephenson wrote:
Ismail was in contact with Daniele about Apper and gave him a load of feedback about things that needed fixed for it to replace KPackageKit for us. Let's get his take on it. In the meantime we can package Apper 1.0 and look at it.
Hi Will, At this moment I have packaged Apper 0.7.0 (unfortunately Daniele continued the version numbering of kpackagekit) and placed it in KDE:Distro:Factory. The package is without any obsoletes/conflicts for kpackagekit, but just contains a conflict there. I thought that this would be the best way to prevent that apper is installed automatically. Also due to it's dependency on PackageKit >= 0.6.17, it only builds for 12.1/Factory. The package should be available in the next hour and I would appreciate feedback on missing translations and other issues people are experiencing. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 11 Oct 2011 12:25:42 Raymond Wooninck wrote:
The package should be available in the next hour and I would appreciate feedback on missing translations and other issues people are experiencing.
For me Apper 0.7.0 from KDF is usable but annoying, System Settings -> Software Management -> Updates Now I am prompted for a root login with: "Authentication is required to set the network proxy used for downloading packages" This does not repsect my KDE network proxy settings which are: "Connect to the Internet directly" I shouldn't be seeing this request at all. So I cancel this root auth request, and now packagekitd seems to hang in some loop while slowly consuming RAM until it's killed. Additionally, If I ignore the request, the request dialogue will eventually dissapear. If I continue in the update workflow by entering my root auth in the proxy settings request, the list of updates are shown. I can then select the updates I want and an entering another root auth to install them the installation procceeds successfully. If I perform an update workflow using the Apper systray icon, I experience the same issue with an extraaneous request to set my proxy settings in addition to the request to auth for the actuall update; but the update does at least process and is successfull. Additionally, the KDE polkit auth agent segfaulted when I relogged to test the update from systray applet workflow, I don't have symbols installed but here's the trace anyway: Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault [Current thread is 1 (Thread 0x7fbc368ce800 (LWP 6822))] Thread 3 (Thread 0x7fbc26c8e700 (LWP 6860)): #0 0x00007fbc33dfb133 in poll () from /lib64/libc.so.6 #1 0x00007fbc31773a38 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fbc31774262 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fbc3125a7d6 in ?? () from /usr/lib64/libgio-2.0.so.0 #4 0x00007fbc31798d56 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fbc31e9df05 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fbc33e0424d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fbc26463700 (LWP 7356)): #0 0x00007fbc33dd2c5d in nanosleep () from /lib64/libc.so.6 #1 0x00007fbc3179c172 in g_usleep () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fbc3176f7cc in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fbc31798d56 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fbc31e9df05 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fbc33e0424d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fbc368ce800 (LWP 6822)): [KCrash Handler] #6 0x00007fbc3150f840 in g_type_check_instance_is_a () from /usr/lib64/libgobject-2.0.so.0 #7 0x00007fbc314ee1ed in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #8 0x00007fbc30d7be1a in ?? () from /usr/lib64/libpolkit-agent-1.so.0 #9 0x00007fbc314ee310 in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #10 0x00007fbc35c4de64 in PolkitQt1::Agent::Session::~Session() () from /usr/lib64/libpolkit-qt-agent-1.so.1 #11 0x00007fbc35c4dea9 in PolkitQt1::Agent::Session::~Session() () from /usr/lib64/libpolkit-qt-agent-1.so.1 #12 0x00007fbc351d9fd8 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #13 0x00007fbc34593be4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #14 0x00007fbc34598a71 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007fbc362b2de6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #16 0x00007fbc351c367c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #17 0x00007fbc351c6a58 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #18 0x00007fbc351c6c7e in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #19 0x0000000000408e3e in ?? () #20 0x00007fbc33d4c23d in __libc_start_main () from /lib64/libc.so.6 #21 0x0000000000408ea5 in _start () So yeah it's a bit annoying to use with the double auth request, but at least the updates actually work. G -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, Oct 11, 2011 at 1:34 PM, Graham Anderson <graham.anderson@gmail.com> wrote:
On Tuesday 11 Oct 2011 12:25:42 Raymond Wooninck wrote:
The package should be available in the next hour and I would appreciate feedback on missing translations and other issues people are experiencing.
For me Apper 0.7.0 from KDF is usable but annoying,
System Settings -> Software Management -> Updates
Now I am prompted for a root login with:
"Authentication is required to set the network proxy used for downloading packages"
This does not repsect my KDE network proxy settings which are: "Connect to the Internet directly"
I shouldn't be seeing this request at all. So I cancel this root auth request, and now packagekitd seems to hang in some loop while slowly consuming RAM until it's killed.
Additionally, If I ignore the request, the request dialogue will eventually dissapear.
If I continue in the update workflow by entering my root auth in the proxy settings request, the list of updates are shown. I can then select the updates I want and an entering another root auth to install them the installation procceeds successfully.
If I perform an update workflow using the Apper systray icon, I experience the same issue with an extraaneous request to set my proxy settings in addition to the request to auth for the actuall update; but the update does at least process and is successfull.
Additionally, the KDE polkit auth agent segfaulted when I relogged to test the update from systray applet workflow, I don't have symbols installed but here's the trace anyway:
Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault [Current thread is 1 (Thread 0x7fbc368ce800 (LWP 6822))]
Thread 3 (Thread 0x7fbc26c8e700 (LWP 6860)): #0 0x00007fbc33dfb133 in poll () from /lib64/libc.so.6 #1 0x00007fbc31773a38 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fbc31774262 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fbc3125a7d6 in ?? () from /usr/lib64/libgio-2.0.so.0 #4 0x00007fbc31798d56 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fbc31e9df05 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fbc33e0424d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7fbc26463700 (LWP 7356)): #0 0x00007fbc33dd2c5d in nanosleep () from /lib64/libc.so.6 #1 0x00007fbc3179c172 in g_usleep () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fbc3176f7cc in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fbc31798d56 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fbc31e9df05 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fbc33e0424d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fbc368ce800 (LWP 6822)): [KCrash Handler] #6 0x00007fbc3150f840 in g_type_check_instance_is_a () from /usr/lib64/libgobject-2.0.so.0 #7 0x00007fbc314ee1ed in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #8 0x00007fbc30d7be1a in ?? () from /usr/lib64/libpolkit-agent-1.so.0 #9 0x00007fbc314ee310 in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #10 0x00007fbc35c4de64 in PolkitQt1::Agent::Session::~Session() () from /usr/lib64/libpolkit-qt-agent-1.so.1 #11 0x00007fbc35c4dea9 in PolkitQt1::Agent::Session::~Session() () from /usr/lib64/libpolkit-qt-agent-1.so.1 #12 0x00007fbc351d9fd8 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #13 0x00007fbc34593be4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #14 0x00007fbc34598a71 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007fbc362b2de6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #16 0x00007fbc351c367c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #17 0x00007fbc351c6a58 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #18 0x00007fbc351c6c7e in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #19 0x0000000000408e3e in ?? () #20 0x00007fbc33d4c23d in __libc_start_main () from /lib64/libc.so.6 #21 0x0000000000408ea5 in _start ()
So yeah it's a bit annoying to use with the double auth request, but at least the updates actually work.
G
Are you using 11.4? The proxy authentication issue is a problem with policykit rather than apper. Policykit should not ask for a password for this, but it does (at least for 11.4, I haven't seen the issue in 12.1). -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 11 Oct 2011 13:37:58 todd rme wrote:
Are you using 11.4? The proxy authentication issue is a problem with policykit rather than apper. Policykit should not ask for a password for this, but it does (at least for 11.4, I haven't seen the issue in 12.1).
No I'm on 12.1 Beta 1 or so... -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 11 Oct 2011 13:34:59 Graham Anderson wrote:
On Tuesday 11 Oct 2011 12:25:42 Raymond Wooninck wrote:
The package should be available in the next hour and I would appreciate feedback on missing translations and other issues people are experiencing.
For me Apper 0.7.0 from KDF is usable but annoying,
System Settings -> Software Management -> Updates
Now I am prompted for a root login with:
"Authentication is required to set the network proxy used for downloading packages"
This does not repsect my KDE network proxy settings which are: "Connect to the Internet directly"
I shouldn't be seeing this request at all. So I cancel this root auth request, and now packagekitd seems to hang in some loop while slowly consuming RAM until it's killed.
Additionally, If I ignore the request, the request dialogue will eventually dissapear.
I think this request is coming directly from packagekitd, not Apper, so it can't directly respect your user policy settings. Still a bug though. It would be interesting to find out if we can collapse all PK's policy requests into one.
If I continue in the update workflow by entering my root auth in the proxy settings request, the list of updates are shown. I can then select the updates I want and an entering another root auth to install them the installation procceeds successfully.
If I perform an update workflow using the Apper systray icon, I experience the same issue with an extraaneous request to set my proxy settings in addition to the request to auth for the actuall update; but the update does at least process and is successfull.
Additionally, the KDE polkit auth agent segfaulted when I relogged to test the update from systray applet workflow, I don't have symbols installed but here's the trace anyway:
There's a button in the crash dialog to install symbols, please get a full trace for us! Will
Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault [Current thread is 1 (Thread 0x7fbc368ce800 (LWP 6822))]
Thread 3 (Thread 0x7fbc26c8e700 (LWP 6860)): #0 0x00007fbc33dfb133 in poll () from /lib64/libc.so.6 #1 0x00007fbc31773a38 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fbc31774262 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fbc3125a7d6 in ?? () from /usr/lib64/libgio-2.0.so.0 #4 0x00007fbc31798d56 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fbc31e9df05 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fbc33e0424d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7fbc26463700 (LWP 7356)): #0 0x00007fbc33dd2c5d in nanosleep () from /lib64/libc.so.6 #1 0x00007fbc3179c172 in g_usleep () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fbc3176f7cc in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fbc31798d56 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fbc31e9df05 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fbc33e0424d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fbc368ce800 (LWP 6822)): [KCrash Handler] #6 0x00007fbc3150f840 in g_type_check_instance_is_a () from /usr/lib64/libgobject-2.0.so.0 #7 0x00007fbc314ee1ed in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #8 0x00007fbc30d7be1a in ?? () from /usr/lib64/libpolkit-agent-1.so.0 #9 0x00007fbc314ee310 in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #10 0x00007fbc35c4de64 in PolkitQt1::Agent::Session::~Session() () from /usr/lib64/libpolkit-qt-agent-1.so.1 #11 0x00007fbc35c4dea9 in PolkitQt1::Agent::Session::~Session() () from /usr/lib64/libpolkit-qt-agent-1.so.1 #12 0x00007fbc351d9fd8 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #13 0x00007fbc34593be4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #14 0x00007fbc34598a71 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007fbc362b2de6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #16 0x00007fbc351c367c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #17 0x00007fbc351c6a58 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #18 0x00007fbc351c6c7e in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #19 0x0000000000408e3e in ?? () #20 0x00007fbc33d4c23d in __libc_start_main () from /lib64/libc.so.6 #21 0x0000000000408ea5 in _start ()
So yeah it's a bit annoying to use with the double auth request, but at least the updates actually work.
G
-- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 11 Oct 2011 21:18:25 Will Stephenson wrote:
There's a button in the crash dialog to install symbols, please get a full trace for us!
I can't reproduce this crash. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hye José, I did ask it in September, this is the thread: http://lists.opensuse.org/opensuse-translation/2011-09/msg00005.html It seems that it was the plan to include it. Regards, Jean 2011/10/11 José Ricardo De León Solís <jricardo.de.leon.s@gmail.com>
Hi everyone, I just finished reading this blog post: http://dantti.wordpress.com/2011/10/10/apper-released/ and I was wondering if it will be included in openSUSE 12.1. I remember that somebody asked this already but I cannot find the mail anywhere in the mailing list. If anybody can give a reply or point me to a previous reply I'll be grateful. Cheers, Ricardo. --
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Good to hear there are plans to include it and apparently testing is required. Will test apper in beta 1. 2011/10/11 Jean Cayron <jean.cayron@gmail.com>:
Hye José,
I did ask it in September, this is the thread: http://lists.opensuse.org/opensuse-translation/2011-09/msg00005.html
It seems that it was the plan to include it.
Regards,
Jean
2011/10/11 José Ricardo De León Solís <jricardo.de.leon.s@gmail.com>
Hi everyone, I just finished reading this blog post: http://dantti.wordpress.com/2011/10/10/apper-released/ and I was wondering if it will be included in openSUSE 12.1. I remember that somebody asked this already but I cannot find the mail anywhere in the mailing list. If anybody can give a reply or point me to a previous reply I'll be grateful. Cheers, Ricardo. --
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (8)
-
Graham Anderson -
Jean Cayron -
José Ricardo De León Solís -
Martin Schlander -
Raymond Wooninck -
Roger Luedecke -
todd rme -
Will Stephenson