Re: [Kde-hardware-devel] networkmanagement moved to extragear

On Thursday 22 July 2010 08:10:27 Ozan Çağlayan wrote: > Çarşamba 21 Temmuz 2010 günü (saat 17:28:19) Sebastian Kügler şunları > > yazmıştı: > > Hi, > > > > I've moved the networkmanagement stack from kdereview/networkmangement to > > extragear/base/networkmanagement today. The new checkout URL t

[Kde-hardware-devel] Review Request: Solid support for docking stations

--- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/5439/ --- Review request for Solid and Kevin Ottens. Summary --- Solid support fo

[Kde-hardware-devel] Re: Review Request: Update NM introspection files and rebase according C++ adapter and proxy files

; (Updated 2010-10-11 16:46:29) > > > Review request for Network Management and KNetworkManager, Solid and Will > Stephenson. > > > Summary > --- > > * Update NM introspection files using NM-0.8.1 > * Add a generator bash script for creating cpp codes of

[Kde-hardware-devel] Re: KDE networkmanagement plasma applet and disconnect issue

On Friday 14 January 2011 12:32:06 Gökçen Eraslan wrote: > Perşembe 13 Ocak 2011 günü (saat 10:46:47) Gökçen Eraslan şunları yazmıştı: > > Any ideas about that? I'm not familiar with solid, the patch may have > > mistakes. > > Anybody tried the patch? This method is very important for KNM, and a m

[Kde-hardware-devel] Re: Solid::Control usage

of all the code > there for KDE Platform 4.7, so any usage of it is unadvised. > > Will Stephenson is working on merge the Solid::Control networkmanagement > bits into a new lib which as far as I know is around 80% completed and > until March he won't be able to work on it aga

[Kde-hardware-devel] Working together on NM09 support and cleaning Solid::Control

(CCing Lamarque and Lukas as it's important that they see this, hardware-devel for info) I read Lamarque's blog [1] about adding NM09 support. For the last 2 weeks I've been working on NM09 support too [2]. Unfortunately I didn't announce this URL because I wanted to have something to show ot

[Kde-hardware-devel] Re: Working together on NM09 support and cleaning Solid::Control

On Wednesday 18 May 2011 16:53:35 Lamarque Vieira Souza wrote: > > My proposal: > > 1. Branch master as the pre09 branch and copy libs/solid/control and > > backend into it. correction: all backends > > 1.1 Tell downstreams not shipping NM09 to use this > > 2. Remove Solid::Control from workspace >

[Kde-hardware-devel] Re: Working together on NM09 support and cleaning Solid::Control

On Saturday 21 May 2011 02:05:47 Lamarque Vieira Souza wrote: > Em Wednesday 18 May 2011, Will Stephenson escreveu: > > On Wednesday 18 May 2011 16:53:35 Lamarque Vieira Souza wrote: > > > #1 should be based in nm09 instead of master in my oppinion. In > > >

[Kde-hardware-devel] udisks2

I was asked to find out what we are doing wrt udisks2 since our distro's gnomes are realigning the tectonic plates again. I see some work on a backend by Lukas in kdelibs/frameworks - is this targetting KF5 only, or could it be used with 4.x? Is the aim to have something complete for KF5, or f

Re: [Kde-hardware-devel] Solid network manager

On Tuesday 06 June 2006 15:19, Christopher Blauvelt said: > Here is the code for > the newtork manager part of solid. My goal was to start out with querying > information only and later add the modifying functions once the API has > been irone

Re: [Kde-hardware-devel] Welcome & Wifi interface

> > Nice for a start, but you may want to consider that there are > > sophisticated > > setups where a card may itself act as an access point (many cheapo home > > linux > > routers equipped with a nice card and a capable driver exist

Re: [Kde-hardware-devel] Thanks for the ideas.

rop > me a line when you get back from vacation. I hope you enjoy the rest > of it. Hi Christopher The usual way to do assign credit is to do just that, assign credit If you add (c) 2006 Will Stephenson <[EMAIL PROTECTED]> in the files that you've taken stuff from my patch, I

Re: [Kde-hardware-devel] Wifi interface (revised patch in)

On Wednesday 09 August 2006 11:38, Kevin Ottens said: > > - > >- > > > > +enum Capabilities { WEP = 0x1, WPA = 0x2, WPA2 = 0x4, PSK = 0x8, > > IEEE8021X = 0x10, WEP40 = 0x20, WEP104 = 0x40, TKIP = 0x80, CCMP = 0x100 > >

Re: [Kde-hardware-devel] Wifi interface

On Sunday 06 August 2006 17:34, Stefan Winter said: > Sure thing, I'm just going through it. Something related and important (for > me at least) first: with Solid running as a background process all the > time, I think there's something important we can achieve in wireless > networks, and whose non

Re: [Kde-hardware-devel] Wifi interface

On Wednesday 16 August 2006 18:05, Stefan Winter wrote: > > Could you explain what it is that you want it to achieve and that pissed > > off your research project (coming from another ex wlan researcher)? > > The idea of the project is to provide seamless roaming in [academic] WLAN > networks with

Re: [Kde-hardware-devel] wireless and kde 4

olid-network the last time we spoke - is this still what you're thinking of doing? Will (working on the NM backend) -- Will Stephenson IRC: Bille ___ Kde-hardware-devel mailing list Kde-hardware-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-hardware-devel

Re: [Kde-hardware-devel] wireless and kde 4

e NM yet, or maybe they need NM experts to make the switch. If you want to contribute at the layer between NM and KDE then I would install a distro with NM and KDE and explore the way it works, then you could help with the Solid backend that I am working on atm. HTH Will -- Will St

Re: [Kde-hardware-devel] [solid] bandwidth control support

On Friday 27 April 2007, Bráulio Oliveira said: > This is my first message to this mailing list, and the subject is bandwidth > control. > I'm planning to create and easy-to-use (Solid/Qt style) support for > bandwidth control using Linux packets shedulers (CFQ, HTB, ). Is this > kind of thing

Re: [Kde-hardware-devel] Solid: Patch to solve the problem with solid_export.h on kdebase

On Thursday 10 May 2007 20:48:50 Opsi wrote: > This problem has been discussed on IRC. In short, the solid_export.h > on kdebase must be moved, renamed and installed, also some little > refactoring is needed to adapt the code in kdebase/solid/control to > that change. > > Attached patch assumes the

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

cktrace. I now added a breakpoint directly before > the ASSERT to produce a backtrace, and found this: You can set a breakpoint on '_exit' to break directly on the failed assert. Will -- Will Stephenson IRC: Bille ___ Kde-hardware-devel mailin

[Kde-hardware-devel] [PATCH] filter v4l devices from hal

Some v4l devices have non-video-source interfaces such as radio devices, videotext and tv tuners. These are all reported by hal as video4linux devices. The attached patch filters out all but the video sources, please review. -- Will Stephenson IRC: Bille Index: solid/solid/backends/hal

Re: [Kde-hardware-devel] [PATCH] filter v4l devices from hal

On Monday 19 November 2007, Kevin Ottens said: > I think it would be easier and more efficient to make a call to > FindDeviceStringMatch instead of patching the way you did. What about > I'm not 100% sure it'd work as expected, but that worth a try if that could > make it work by placing only one

Re: [Kde-hardware-devel] Proposed patch for Solid::Control

On Thursday 06 March 2008 08:10:50 Christopher Blauvelt wrote: > Attached is a proposed patch to fix a couple of bugs and provide access to > some information that was already indexed internally. > Let me know you thoughts, > Chris It's good, commit it! Will -- Will Step

Re: [Kde-hardware-devel] Network Manager

nks, > Chris Is this resolved by the activeNetwork() method you added? Will -- Will Stephenson IRC: Bille ___ Kde-hardware-devel mailing list Kde-hardware-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-hardware-devel

[Kde-hardware-devel] NM 0.7 settings update

So I have the settings stuff for NM 0.7 nearly working now. 0) testservice is a test service 1) A dummy (hardwired config dialog) is shown by testservice's configure button. As in KConfigXt, some widgets are named "kcfg_SETTINGNAME" where SETTINGNAME is something in NM's dbus settings. This wid

[Kde-hardware-devel] NM 0.7 settings update, 2nd try

(apologies if anyone gets this twice) -- So I have the settings stuff for NM 0.7 nearly working now. 0) testservice is a test service 1) A dummy (hardwired config dialog) is shown by testservice's configure button. As in KConfigXt, some widgets are named "kcfg_SETTINGNAME" where SETTINGNAME is

Re: [Kde-hardware-devel] NM 0.7 settings update

On Wednesday 18 June 2008 08:07:34 you wrote: > Le Wednesday 18 June 2008, Will Stephenson a écrit : > > So I have the settings stuff for NM 0.7 nearly working now. > > [...] > > 2) A KConfigSkeleton is created at runtime by ConfigXml (from Plasma) for > > each NM

Re: [Kde-hardware-devel] inhibit suspend

On Sunday 05 October 2008 12:14:09 Dario Freddi wrote: > On Sunday 05 October 2008 00:24:31 you wrote: > > I agree that a profile is the way to go. We should add a "presentation" > > profile to the powerdevil defaults. Dario, is that OK with you? > > A "Presentation" profile was in place since a do

Re: [Kde-hardware-devel] Merging new Solid Actions control module and existing control module

On Wednesday 25 March 2009 09:10:25 Kevin Ottens wrote: > On Tuesday 24 March 2009 08:14:20 Ben Cooksley wrote: > > There are currently two control modules for Solid: one for choosing > > backends, and one for managing actions. At the end of the review of > > the managing actions module it was sugg

Re: [Kde-hardware-devel] Solid device action predicates

On Friday 10 July 2009 11:26:44 Ozan Çağlayan wrote: > Ozan Çağlayan wrote On 08-07-2009 14:47: > > Okay I've found the problem in solid/solid/predicate.cpp: > > > > In Solid::Predicate::matches, a boolean expression is returned to > > identify whether there was a match or not: > > > > > > if (d->c

[Kde-hardware-devel] possible leak?

mjansen posted this on irc just now and I am too tired to evaluate it - anyone able to say if it's a real one? Will ==17206== 6,976 bytes in 172 blocks are possibly lost in loss record 35 of 365 ==17206==at 0x4C2599E: malloc (in /usr/lib64/valgrind/amd64- linux/vgpreload_memcheck.so) ==17206

Re: [Kde-hardware-devel] Some cache in Solid? Solid::Device::listFromQuery gives outdated data

On Thursday 24 September 2009 00:45:51 Albert Astals Cid wrote: > Talking with dfaure it seems there are three solutions: > * Add a thread with an event loop to the sysinfo slave and do the solid > calls there and somehow pass the info > * Tell solid not to cache the information > What was the

Re: [Kde-hardware-devel] Some cache in Solid? Solid::Device::listFromQuery gives outdated data

On Friday 25 September 2009 20:40:20 Rafał Miłecki wrote: > 2009/9/25 Will Stephenson : > > On Thursday 24 September 2009 00:45:51 Albert Astals Cid wrote: > >> Talking with dfaure it seems there are three solutions: > >> * Add a thread with an event loop to the sys

Re: [Kde-hardware-devel] Making Konqueror(/kio?) network-aware

On Sunday 01 November 2009 22:54:22 Eduardo Robles Elvira wrote: > Is any of what I suggest in my email possible? Is it a stupid > question? Any comments? :P I'll read this and respond tomorrow Will ___ Kde-hardware-devel mailing list Kde-hardware-deve

Re: [Kde-hardware-devel] Using Solid

On Monday 02 November 2009 04:30:11 David Hubner wrote: > > > >> 3. Would be nice if it was possible to check connected status on > > > >> each NetworkInterface rather than global, or the > > > >> Solid::Networking:Notifier statusChanged function to say which > > > >> NetworkInterface caused the st

Re: [Kde-hardware-devel] new member

On Tuesday 03 November 2009 05:02:01 Vikram Dhillon wrote: > How are you guys? I am a new member here and i would like to > contribute to Solid by writing device drivers, I have never done this > before so I would appreciate some help on getting started here. Any other > suggestions are

Re: [Kde-hardware-devel] Making Konqueror(/kio?) network-aware

On Thursday 29 October 2009 17:04:39 Eduardo Robles Elvira wrote: > I don't know exactly if solid triggers network-manager, if we can get > a signal when network becomes available, if the integration should be > done at kio level instead, or if somebody is already working on this > already. Any hel

Re: [Kde-hardware-devel] [PATCH] Add docking station support to Solid

On Tuesday 24 November 2009 21:59:02 Kevin Ottens wrote: > On Saturday 21 November 2009 09:24:21 Will Stephenson wrote: > > The attached patch adds support for laptop docking stations to Solid. > > Knowing when the machine is docked will allow us to modify powersaving > > po

Re: [Kde-hardware-devel] [PATCH 32/33] input: add KEY_WIRELESS_CYCLE

On Thursday 03 December 2009 10:43:32 Johannes Berg wrote: > On Thu, 2009-12-03 at 10:22 +0100, Corentin Chary wrote: > > Dear system infrastructure people, > > Do you think a KEY_WIRELESS_CYCLE key would have any application ? > > Not really. > > The naming of the key ultimately will not matter

Re: [Kde-hardware-devel] Solid::Control not finding local loopback

On Friday 18 December 2009 00:55:39 David Hubner wrote: > Is this because networkmanager does not provide information on the loopback > device though the dbus interface? That's correct - AFAIK it was never interesting to me the networkmanager folks because our main networking priority is gettin

Re: [Kde-hardware-devel] Solid::Control not finding local loopback

On Tuesday 22 December 2009 20:29:08 David Hubner wrote: > > What are you using it for? (That might be the use case you were looking > > for ...) > > Solid Device Viewer, its in playground, its for KInfoCenter. I am > redoing most of its KCM's over Christmas as it looks like it needs work. > I sha

Re: [Kde-hardware-devel] Solid::Control not finding local loopback

On Sunday 27 December 2009 21:05:25 David Hubner wrote: > On 27/12/2009 10:19, Will Stephenson wrote: > > On Tuesday 22 December 2009 20:29:08 David Hubner wrote: > >>> What are you using it for? (That might be the use case you were looking > >>> for ...) >

Re: [Kde-hardware-devel] Solid::Control not finding local loopback

On Monday 11 January 2010 02:40:41 David Hubner wrote: > On Friday 08 Jan 2010 12:53:28 Will Stephenson wrote: > > On Sunday 27 December 2009 21:05:25 David Hubner wrote: > > > On 27/12/2009 10:19, Will Stephenson wrote: > > > > On Tuesday 22 December 20

Re: [Kde-hardware-devel] bluetooth in kde

On Monday 22 February 2010 09:51:59 Alex Fiestas wrote: > On Monday 22 February 2010 08:41:44 Ozan Çağlayan wrote: > > Alex Fiestas wrote On 14-09-2009 11:29: > > > I'll try to work on the kio as soon as we've the other basic stuff > > > supported, for example pairing of audio/modems. > > > > Hi A

[Kde-hardware-devel] Tokamak4 Network Management notes

At Tokamak 4 yesterday myself, Sebastian Kügler and Alexander Naumov got together to plan what we want to achieve with Network Management, especially the plasmoid. * Layout - AI: sebas, distribute mockups. Roughly: continue twin pane approach. LHS shows interface status overview and alterna

Re: [Kde-hardware-devel] Tokamak4 Network Management notes - progress update

On Thursday 04 March 2010 15:24:38 Sebastian Kügler wrote: > Hey Network Managers! > > I've done many of the UI changes over the last week, and I'm actually quite > pleased with the result so far. > > On Wednesday 24 February 2010 11:19:55 Will Stephenson wrote: >

Re: [Kde-hardware-devel] [GSoC] Preliminary UPnP support proposal

On Sunday 21 March 2010 16:15:46 Nikhil Marathe wrote: > Meanwhile having a library like HUpnp will keep the core pretty small. > It provides > the Control Point and device discovery support that is the basic > requirement for now. I have been in contact with Tuomo Pettinen and he is > working hard

Re: [Kde-hardware-devel] Solid Meeting

On Saturday 27 March 2010 12:31:10 Kevin Ottens wrote: > On Thursday 25 February 2010 19:48:32 Dario Freddi wrote: > > During Tokamak's Bof, the idea of having a Solid meeting popped up and > > was quite widely accepted. The topics of the meeting would be the future > > of Solid, finalizing the wor

Re: [Kde-hardware-devel] Detaching Solid::Control, and stuff

On Saturday 27 March 2010 15:49:28 Kevin Ottens wrote: > Let me recap the reasoning: > - Solid::Control was here to allow having different implementations of > policy agents in the user session; > - The fact is that there's really only one of those agents for each type > (power, network, etc.)