Re: [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/08/2012 16:08, Pascal Terjan wrote: On Thu, Aug 30, 2012 at 10:22 AM, Marja van Waes marj...@xs4all.nl wrote: On 22/08/2012 16:29, Pascal Terjan wrote: On Wed, Aug 22, 2012 at 11:57 AM, Marja van Waes marj...@xs4all.nl wrote: Hi all, About a help text for drakx-installer-stage2: Can someone please help documentation team with a good help text for the help button for the Add or Modify a Boot Menu Entry screen, so for the pop up screen you see in the second screenshot here (the one that pops up on top of the Bootloader Configuration screen) http://docteam.mageia.nl/installer/content/setupBootloaderAddEntry.html What is the expected kind of text? ( I have never read the help :) ) An explanation of the different fields? You didn't reply to my reply, so maybe I misunderstood. I thought you were longing to help us :þ Sorry, I was away for an extended week-end, I may have some time tomorrow @ pterjan Given our shortage of sysadmins, you still won't have time, I'll remove those Add some text lines. @ barjac Would you have time to make the necessary adjustments to the other bootloader help texts when GRUB2 becomes the default bootloader in Mageia3beta-x ? Anyway, if no one comes up with something better, we'll remove Add some text and leave the help text as it is. Cheers, marja -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQsJK4AAoJEKWubDMI5nEBthsIALfiVOtCKHCtuB9PYnRsduYV R2nzMz0y7OVjVsjMdTUO0C4z/0bA3teYqKR3cvOyn0TD3qhslIydXZq8PPk1ENV2 t7ln2HfOGqfPQKzhnKOtecSVFJg3nI9HvwGHTRW220c0l2xdxTvlXee9ZCAtnxkK 7tTaIGeTSEOdcg3ArV3JA4m2+XllKYUfCjkXmRt0xe7W678gHID6mD92ZQXTHjkk 1yGKOyz0AYnTQwRZpFBepx5f2wKSfyU9eWaC3B1o8cPN0OezNPuLzKmBecQS4bp1 YiNX9BwLNotElut6JurKjHAMLyOHecanxsWJPJMSI3mMMy0kPQEvg9zLCc/ELWs= =AlnX -END PGP SIGNATURE-
[Mageia-dev] what is this ????
Is it a joke ? https://wiki.mageia.org/en/Paid_projects Someone want to be paid for his work on Mageia Does it mean that he will give some money back to Mageia ? Such a page might need an agreement before being published ... don't you think so ?
Re: [Mageia-dev] what is this ????
PhilippeDidier a écrit : Is it a joke ? https://wiki.mageia.org/en/Paid_projects Someone want to be paid for his work on Mageia Does it mean that he will give some money back to Mageia ? Such a page might need an agreement before being published ... don't you think so ? The most stunning part of this proposal is that the author intends to use bugzilla (Mageia's infrastructure) to allow a paid developer communicating with its clients !
[Mageia-dev] Utter frustration
In Cauldron, I'm once again struggling with the inability to make configuration changes. I first met it and wrote about it when trying to get wifi working. Now I'm trying to change shutdown option, and meet the same problem again. Administrator authorisation is required to change the Login Manager settings That implies root password, to me, but Authentication failure, please try again. After that a new box pops up - Unable to authenticate/execute the action: DBus Backend error: could not contact the helper. Connection error: The name org.freedesktop.ConsoleKit was not provided by any .service files. Message error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken (code 7) Whatever is blocking these changes is a right royal PITA. If you are tempted to shut off security measures by such setting, it is asking for trouble. Caulron was behaving so well until a couple of weeks or so ago. It's driving me mad at the moment. Is there any way out of this mess? and also, asked in another thread, any way to stop it locking my screen if I look away for a couple of minutes? Anne
Re: [Mageia-dev] what is this ????
2012/11/24 PhilippeDidier philippedid...@laposte.net: Is it a joke ? https://wiki.mageia.org/en/Paid_projects That's interesting. Someone want to be paid for his work on Mageia Does it mean that he will give some money back to Mageia ? Such a page might need an agreement before being published ... don't you think so ? I prefer the better apologize than ask for permission mantra; it helps going forward - so let's discuss this: - what's the goal? bounties? - how can it be related to https://wiki.mageia.org/en/Commercial_vendors? (it's more specific, but it looks like having a related purpose) - is it appropriate to host it/link it from mageia.org? - if so, couldn't it be linked into the bugzilla with a keyword or st specific? or to a more appropriate platform? - should there be a monetary return to Mageia? (given that it should bring a code/patch/quality return already)
Re: [Mageia-dev] what is this ????
On Saturday 24. November 2012 12.58, PhilippeDidier wrote: Someone want to be paid for his work on Mageia I have no problems with people working on mageia for money, as long as they adhere to our rules. If this results in more bugs being fixed, then we are benefitting from it. Many of the kernel hackers are paid by their employers to work on the kernel. Others are paid to work with a distribution. This is not new. Such a page might need an agreement before being published ... don't you think so ? I think so, yes. The current page implies that this is a Mageia project. I have no problem with the content itself. But the content of that page belongs on the authors webpage, not on the Mageia wiki. The page should be deleted. -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Utter frustration
Just to notify Anne that the latest mails to mageia-dev arrived in 2 flavours: - 1 gnupg signed version, coming from Anne Wilson cannewil...@googlemail.com - 1 unsigned version (same text) coming from Anne Wilson an...@kde.org -- wobo
Re: [Mageia-dev] what is this ????
On Saturday 24. November 2012 15.06, Romain d'Alverny wrote: - is it appropriate to host it/link it from mageia.org? Whats more, the article author have linked to the articles from the wikis Front page. https://wiki.mageia.org/en/Main_Page (Why can any registered user edit the Front page?) -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] what is this ????
24.11.2012 17:41, Wolfgang Bornath kirjutas: 2012/11/24 Johnny A. Solbu coo...@solbu.net: On Saturday 24. November 2012 12.58, PhilippeDidier wrote: Someone want to be paid for his work on Mageia I have no problems with people working on mageia for money, as long as they adhere to our rules. If this results in more bugs being fixed, then we are benefitting from it. Many of the kernel hackers are paid by their employers to work on the kernel. Others are paid to work with a distribution. This is not new. Such a page might need an agreement before being published ... don't you think so ? I think so, yes. The current page implies that this is a Mageia project. I have no problem with the content itself. But the content of that page belongs on the authors webpage, not on the Mageia wiki. The page should be deleted. Well, actually I think the page needs some editing. As it is now it may give wrong ideas (as we see in this thread). What the page really says is that if Mageia does not offer any solution for a given bug because of lack of time or lack of interest by the developers a user is able to address the developers with a financial offer like fix this bug and I would pay 50 EuroCents. What the page does not say: it is not an advertisement of one or more Mageia developers offering paid service. It is merely a text telling the users that in a certain case this option is possible - keeping in mind that the resulting fix will still be free for all Mageia users to use. So, IMO the offer is something similar to Ubuntu's offer to be able to donate to a single project inside the distribution. With a better phrasing the page may be ok. Of course the details should be discussed in public and after that the option should be advertized in a blog. +1 on that. I have had similar idea myself. Watching bug 2317 or considering the fact that we still lack backports support. If someone is willing to pay for it to get solved then why not? And as the page says, Mageia can still refuse the solution. For example: someone wants Cinnamon to work on Mageia and someone else ports it. But it won't be imported into Mageia. They can have their own repo for it. -- Sander
Re: [Mageia-dev] [changelog] [RPM] 2 core/updates_testing firefox-17.0-3.mga2
Thierry Vignaud thierry.vign...@gmail.com writes: On 24 November 2012 01:51, dmorgan buildsystem-dae...@mageia.org wrote: dmorgan dmorgan 0:17.0-3.mga2: + Revision: 321475 - Fix xml file - Enable Opus support - New version 17.0esr 0 Much to the despair of my young nephews, it segfaults on : http://www.youtube.com/watch?v=fhCIDe92iKQ Program received signal SIGSEGV, Segmentation fault. 0x003afe4a88cd in ?? () from /usr/lib64/libmozjs185.so.1.0 (gdb) bt #0 0x003afe4a88cd in ?? () from /usr/lib64/libmozjs185.so.1.0 [...] #6 0x7fab95ae in js::IndirectProxyHandler::call(JSContext*, JSObject*, unsigned int, JS::Value*) () from /usr/lib64/firefox-17.0/libxul.so Hi, This looks strongly like #6299 (symbols conflicts between firefox's mozjs and mozjs185 pulled by libproxy). It did not occur with the initial firefox version from Mageia 2, I think it started with firefox 13. I suggest pushing to Mageia 2 updates libproxy-0.4.7-9 (or why not 0.4.10-1 since it fixes more issues). -- Olivier Blin - blino
Re: [Mageia-dev] what is this ????
2012/11/24 Johnny A. Solbu coo...@solbu.net: On Saturday 24. November 2012 15.06, Romain d'Alverny wrote: - is it appropriate to host it/link it from mageia.org? Whats more, the article author have linked to the articles from the wikis Front page. https://wiki.mageia.org/en/Main_Page A better place would be to link it from http://mageia.org/support/ but even here, it should be rephrased and more largely understood (what's the goal of it). (Why can any registered user edit the Front page?) Because it's a wiki, and most (99%) of the time, there is no abuse.
Re: [Mageia-dev] Video players
On 11/24/2012 01:28 AM, Pierre Jarillon wrote: For Mageia 3 it is necessary to read all kinds of videos. I have a set of video to test the distro. Totem is out of service but its is however the defaut reader... For some videos, Dragon is not shown in the list of players but works. http://vimeo.com/53980967 from vimeo works with Mageia 1 but not in cauldron. VLC works always. My suggestions are: - When VLC is loaded, it must become the default video viewer. - For each video type, define the viewer (Totem, Dragon) which works. Some points, specially related to Totem that is what I mainly use: - Totem/GStreamer plays all kind of videos I have given it, mainly divx/mp4/h264/mpeg2 with mp3/ac3 audio in avi/mp4/mkv containers. It all depends on your gstreamer being correctly installed. - Videos like http://vimeo.com/53980967 are just FLASH, they do not depend on Totem,VLC o Dragon. It works for me in Cauldron, as YouTube both in Flash or HTML5 formats. - Most desktops DEs have a native player (Totem for Gnome, Dragon for KDE, Parole for XFCE, ...). That should work and be the default out of the box, that is what is most integrated with each DE. Suppose that Totem was the absolutely best player regarding fomats. What would you think KDE users would say if it was made the default for KDE, forcing them to install half Gnome to see videos ? - Many desktops have some kind of 2nd-to-best player. Perhaps VLC is a good option for KDE (it is Qt based anyways), but for Gnome or XFCE (GTK based) the best next option IMHO is Gnome MPlayer (as good as as VLC). So the only problem with Totem is probably urpmi requires/suggests missing to guarantee that is plays all audio/video formats, or at least most used. And I suppose you can have the same problems with Phonon (or whatever is the KDE equivalent to GStreamer). And wrt to copyrighted decoders, the problem is the same for all, you have to use Tainted repos to get a GStreamer/VLC/MPlayer that decodes them. If you can post your video test collection somewhere, I can try to see if totem works for me with them. -- J.A. Magallon jamagallon()ono!com\ Winter is coming...
Re: [Mageia-dev] Video players
On Saturday 24. November 2012 17.25, JA Magallón wrote: And wrt to copyrighted decoders ... Unless the decoder is in the Public Domain, it is copyrighted. The Linux kernel is copyrighted. Even the GNU packages is copyrighted. Don't confuse copyrighted with proprietary. -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] what is this ????
Sander Lepik a écrit : So, IMO the offer is something similar to Ubuntu's offer to be able to donate to a single project inside the distribution. With a better phrasing the page may be ok. Of course the details should be discussed in public and after that the option should be advertized in a blog. +1 on that. I have had similar idea myself. Watching bug 2317 or considering the fact that we still lack backports support. If someone is willing to pay for it to get solved then why not? And as the page says, Mageia can still refuse the solution. For example: someone wants Cinnamon to work on Mageia and someone else ports it. But it won't be imported into Mageia. They can have their own repo for it. NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it !
Re: [Mageia-dev] Video players
On 11/24/2012 05:33 PM, Johnny A. Solbu wrote: On Saturday 24. November 2012 17.25, JA Magallón wrote: And wrt to copyrighted decoders ... Unless the decoder is in the Public Domain, it is copyrighted. The Linux kernel is copyrighted. Even the GNU packages is copyrighted. Don't confuse copyrighted with proprietary. Yeah, sorry, that's what I meant... -- J.A. Magallon jamagallon()ono!com\ Winter is coming...
Re: [Mageia-dev] Utter frustration
Le samedi 24 novembre 2012 13:33:16 Anne Wilson a écrit : In Cauldron, I'm once again struggling with the inability to make configuration changes. I first met it and wrote about it when trying to get wifi working. Now I'm trying to change shutdown option, and meet the same problem again. Administrator authorisation is required to change the Login Manager settings That implies root password, to me, but Authentication failure, please try again. [...] Just in case did you try with your normal user password ? -- Mageia Contributor
Re: [Mageia-dev] what is this ????
24.11.2012 18:55, PhilippeDidier kirjutas: NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it ! Well, we have such repos already today and you can't stop something like that. But you saw my example the wrong way. Mageia doesn't have to support those repos and problems caused by such packages. I don't like such repos either and i hope that paid people fix things in our repos. -- Sander
Re: [Mageia-dev] what is this ????
Sander Lepik a écrit : 24.11.2012 18:55, PhilippeDidier kirjutas: NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it ! Well, we have such repos already today and you can't stop something like that. But you saw my example the wrong way. Mageia doesn't have to support those repos and problems caused by such packages. That has been a problem for Mandrake with Thac repo, a problem for Mandriva with MIB repo... and sometimes it took a long (wasted) time to understand that a reported bug was induced by something imported from third repo. NB plf repo was something else : mandriva devs worked on it ! I don't like such repos either and i hope that paid people fix things in our repos. That reminds me a big controversy in Debian community some years ago... -- Sander Regards Philippe
Re: [Mageia-dev] what is this ????
I don't have problem with people working in Mageia improvements and receive payment for it, because this improvement will be free software. I remembered this blogpost about payment to develop poppler/Okular features - http://tsdgeos.blogspot.com.br/2012/06/free-software-free-to-pay.html 2012/11/24 Sander Lepik sander.le...@eesti.ee 24.11.2012 18:55, PhilippeDidier kirjutas: NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it ! Well, we have such repos already today and you can't stop something like that. But you saw my example the wrong way. Mageia doesn't have to support those repos and problems caused by such packages. I don't like such repos either and i hope that paid people fix things in our repos. -- Sander -- Filipe Saraiva http://filipesaraiva.info/
Re: [Mageia-dev] [packages-commits] [321297] imported package nemo
Em 24-11-2012 00:08, Johnny A. Solbu escreveu: On Friday 23. November 2012 22.46, Anne Nicolas wrote: There has already been zillions of discussions about this. Discussions some of us have never heard of, including me. We will not have Cinnamon. I am not talking about Cinnamon. I couldn't care less about Cinnamon, as I didn't know what it was untill now. Personally I'm happy with the current environments in Mageia. :-)= I just wanted to know if there is a list or policy or what have you, that we can read to figure out what or which type of FLOSS projects that for whatever reason is unwanted in Mageia. I didn't know there was such a thing. And if new packagers, such as myself, don't know that this or that FLOSS project or types of projects isn't allowed, how do you expect them to not import it? So my question still stands. Is there such a list or policy? If not, should we have one? If the consensus is that such a list is not a good idea or not wanted, I'm fine with it. I just wanted to raise the question. As always, I think you can start such a page in the wiki, like : http://wiki.debian.org/Games/Unsuitable
Re: [Mageia-dev] what is this ????
2012/11/24 PhilippeDidier philippedid...@laposte.net: Sander Lepik a écrit : 24.11.2012 18:55, PhilippeDidier kirjutas: NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it ! Well, we have such repos already today and you can't stop something like that. But you saw my example the wrong way. Mageia doesn't have to support those repos and problems caused by such packages. That has been a problem for Mandrake with Thac repo, a problem for Mandriva with MIB repo... and sometimes it took a long (wasted) time to understand that a reported bug was induced by something imported from third repo. NB plf repo was something else : mandriva devs worked on it ! Still, we can't prevent that *. So perhaps should we: - analyse it and find a clear model that explains it, so we can change what could be changed; - even embrace it, that is, have a strategy to have more such external repositories to merge back into ours, or to better tag/mark/recognize what can come from something we do support as Mageia (because we produced it, or because it matches our requirements) and from something we don't. * it's a symptom that means that most of Mageia (as a whole product) works for some people, but some parts of it don't (so they duplicate/manage things on their own to make it quick, or more controlled for them). Still. The bottom line of having calls for bounties, people ready to pay to have some requests in Mageia answered in a more controlled way, is perfectly fine. Having them including in their requirements that the work be merged into (if possible), or made available to the parent project is even better.
Re: [Mageia-dev] Can't win - or, best of both worlds . . .!
On 11/24/2012 02:37 AM, Anne Wilson wrote: On 24/11/2012 05:36, Frank Griffin wrote: I haven't tested since, because this was the straw on the camel's back that finally got me to pull enough teeth to find out that NM won't work in KDE without manual intervention. Once I got NM to work, I never went back. For those of us still struggling to get wireless to work, can you give more details, please? Sorry if you have done so somewhere else and I missed it. As I understand it, NM needs to parse ifcfg files to an internal format before it can work correctly with wireless. I suspect there's a way to do this with the NM CLI, but unless you speak NM well (I don't), it isn't really obvious. It's easy in GNOME, as GNOME appears to detect that it needs to be done and does it silently. So if you have GNOME installed, just log in to it, activate the interface from the dropdown at the top right, and log out again. Otherwise, from KDE, you define the interface with drakconnect (MCC), selecting to allow NM to control it. Then install plasma-applet-networkmanager (which is not installed by default for KDE because NM is not supposed to be the default for wireless yet). John Balcaen has posted that you don't need to add it to the panel (you can invoke it directly in some way I didn't follow), but before I read that I just used the panel toolbox widget Add Widgets option, search on network, double-clicked to place it on the panel, and invoked it from there. Just tell it to connect the wireless, and the parse should be done automatically. IIRC, John also posted that knetworkmanager (invoked through KDE system settings) should do as well, but I'm not sure whether the plasma-applet-networkmanager package was still required in that case. Something has probably changed since I did this, since my recollection is that the plasma applet showed a choice of interface controllers with NM selected by default, and that did the required parse. In current cauldron, both the applet and knetworkmanager give me the same display, and neither mentions NM, so maybe both the panel icon and the system settings option are executing the same thing, and the plasma package was being used under the covers. I'm a recent refugee to KDE from GNOME3, so there's a lot I don't find intuitive. There are two questions for which I don't have answers. Once you've caused the parse to be done, you should be good to go for wireless on subsequent reboots for that SSID. I'm not sure whether it needs to be redone if you switch SSIDs, but the errors you get from NM if the parse *hasn't* been done refer to errors in an ifcfg-rh which appears to be independent of SSID. So maybe it's a one-time thing, or maybe it's a one-time-per-SSID thing. The other question is what happens for DEs other than GNOME and KDE. No clue there. You can find more details in bug#2160 and bug#8169. I'm still not sure exactly what happens when. I just followed John's suggestion to install plasma-applet-networkmanager, and then bumbled around until I noticed it working. Apart from having to install the applet and invoke *something* (either the applet or knetworkmanager), it all works by magic. Just not by as much magic as it does in GNOME.
Re: [Mageia-dev] what is this ????
Op zaterdag 24 november 2012 20:09:05 schreef Romain d'Alverny: 2012/11/24 PhilippeDidier philippedid...@laposte.net: Sander Lepik a écrit : 24.11.2012 18:55, PhilippeDidier kirjutas: NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it ! Well, we have such repos already today and you can't stop something like that. But you saw my example the wrong way. Mageia doesn't have to support those repos and problems caused by such packages. That has been a problem for Mandrake with Thac repo, a problem for Mandriva with MIB repo... and sometimes it took a long (wasted) time to understand that a reported bug was induced by something imported from third repo. NB plf repo was something else : mandriva devs worked on it ! Still, we can't prevent that *. So perhaps should we: - analyse it and find a clear model that explains it, so we can change what could be changed; - even embrace it, that is, have a strategy to have more such external repositories to merge back into ours, or to better tag/mark/recognize what can come from something we do support as Mageia (because we produced it, or because it matches our requirements) and from something we don't. * it's a symptom that means that most of Mageia (as a whole product) works for some people, but some parts of it don't (so they duplicate/manage things on their own to make it quick, or more controlled for them). Still. The bottom line of having calls for bounties, people ready to pay to have some requests in Mageia answered in a more controlled way, is perfectly fine. Having them including in their requirements that the work be merged into (if possible), or made available to the parent project is even better. i guess it needs to be policy'ed: like: requiring that the fixes are done in Mageia itself (no 3rd party repository), and as usual that the fixes are done in accordance to our policies. then, structure needs to be clear with a status: [requested] To fix bug #X (preferably option Y); user donates Z [taken by user] To fix bug #X (preferably option Y) user donate Z [solved by user] To fix bug #X (preferably option Y) user donate Z [accepted] To fix bug #X (preferably option Y) user donate Z any other communcations or status, reject or whatever, doesn't need to be here and is between the parties involved. I would also ask that if possible the user who solves it donates a part to mageia, not required. lastly, i note that the page is a draft, so this could very well mean that the person who wrote this planned to bring this in a meeting. in short, i don't really see any issue with it.
Re: [Mageia-dev] what is this ????
2012/11/24 AL13N al...@rmail.be: like: requiring that the fixes are done in Mageia itself (no 3rd party repository), and as usual that the fixes are done in accordance to our policies. You can't: 1) it's free software. 2) those changes will be first done on a separate repository before being pushed for inclusion. I would also ask that if possible the user who solves it donates a part to mageia, not required. I wouldn't: - the person that opens the bounty already invested money into the change (and to have it pushed to the master project); - the person that takes the bounty and does/pushes the change already invested her time and skills.
Re: [Mageia-dev] what is this ????
Op zaterdag 24 november 2012 20:52:42 schreef Romain d'Alverny: 2012/11/24 AL13N al...@rmail.be: like: requiring that the fixes are done in Mageia itself (no 3rd party repository), and as usual that the fixes are done in accordance to our policies. You can't: 1) it's free software. 2) those changes will be first done on a separate repository before being pushed for inclusion. I would also ask that if possible the user who solves it donates a part to mageia, not required. I wouldn't: - the person that opens the bounty already invested money into the change (and to have it pushed to the master project); - the person that takes the bounty and does/pushes the change already invested her time and skills. I'm not following 100%, does this mean there are already quite specific usecases for this? what's wrong with asking that the people who fix this do this, to do this in upstream? i didn't say first or whatever, if someone fixes something for them only, it would be nice of all the other mageians can profit from it... and the latter was just a suggestion, it's not required.
Re: [Mageia-dev] Can't win - or, best of both worlds . . .!
Le 24 nov. 2012 16:39, Frank Griffin f...@roadrunner.com a écrit : On 11/24/2012 02:37 AM, Anne Wilson wrote: On 24/11/2012 05:36, Frank Griffin wrote: I haven't tested since, because this was the straw on the camel's back that finally got me to pull enough teeth to find out that NM won't work in KDE without manual intervention. Once I got NM to work, I never went back. For those of us still struggling to get wireless to work, can you give more details, please? Sorry if you have done so somewhere else and I missed it. As I understand it, NM needs to parse ifcfg files to an internal format before it can work correctly with wireless. I suspect there's a way to do this with the NM CLI, but unless you speak NM well (I don't), it isn't really obvious. It's only happening if you choose to not change the default networkmanager configuration aka using the ifcfg plugin which means read only support for ifcfg files. I'm personally using instead the keyfile plugin (the upstream default). It's easy in GNOME, as GNOME appears to detect that it needs to be done and does it silently. So if you have GNOME installed, just log in to it, activate the interface from the dropdown at the top right, and log out again. Otherwise, from KDE, you define the interface with drakconnect (MCC), selecting to allow NM to control it. Then install plasma-applet-networkmanager (which is not installed by default for KDE because NM is not supposed to be the default for wireless yet). John Balcaen has posted that you don't need to add it to the panel (you can invoke it directly in some way I didn't follow), but before I read that I just used the panel toolbox widget Add Widgets option, search on network, double-clicked to place it on the panel, and invoked it from there. Just tell it to connect the wireless, and the parse should be done automatically. IIRC, John also posted that knetworkmanager (invoked through KDE system settings) should do as well, but I'm not sure whether the plasma-applet-networkmanager package was still required in that case. knetworkmanager is just the name of the source rpm and the original binary which is long dead...So currently it's just a virtual package pulling the plasma applet package. Something has probably changed since I did this, since my recollection is that the plasma applet showed a choice of interface controllers with NM selected by default, and that did the required parse. In current cauldron, both the applet and knetworkmanager give me the same display, and neither mentions NM, so maybe both the panel icon and the system settings option are executing the same thing, and the plasma package was being used under the covers. They're the same thing indeed. I'm a recent refugee to KDE from GNOME3, so there's a lot I don't find intuitive. There are two questions for which I don't have answers. Once you've caused the parse to be done, you should be good to go for wireless on subsequent reboots for that SSID. I'm not sure whether it needs to be redone if you switch SSIDs, but the errors you get from NM if the parse *hasn't* been done refer to errors in an ifcfg-rh which appears to be independent of SSID. So maybe it's a one-time thing, or maybe it's a one-time-per-SSID thing. Suggest here: drop all ifcfg configuration files and switch to keyfile plugin.
Re: [Mageia-dev] Utter frustration
On 11/24/2012 08:20 AM, Anne Wilson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In Cauldron, I'm once again struggling with the inability to make configuration changes. I first met it and wrote about it when trying to get wifi working. Now I'm trying to change shutdown option, and meet the same problem again. Administrator authorisation is required to change the Login Manager settings Do you have an I-take-everything cauldron or a pick-and-choose cauldron ? Nobody ever seems to announce policy changes on this ML, but I gather that the winds of favor have moved from ConsoleKit to PolicyKit (or maybe it's the other way around), so if, for example, ConsoleKit is now deprecated but you still have packages installed that want it, you might be getting the errors you mention below. Unable to authenticate/execute the action: DBus Backend error: could not contact the helper. Connection error: The name org.freedesktop.ConsoleKit was not provided by any .service files. Message error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken (code 7) Caulron was behaving so well until a couple of weeks or so ago. It's driving me mad at the moment. Is there any way out of this mess? and also, asked in another thread, any way to stop it locking my screen if I look away for a couple of minutes. This was covered extensively in another thread. KDE Power Management is AFU at the moment. If you have set PM to not turn off the display no mattter what, it rolls the dice and chooses some random value for dpms, which determines when the screen blanks (thanks, Colin). There's an open KDE bug for it. At present, about all you can do to stay sane is put xset -dpms in your rc.local and also at the tail end of whatever scripts you use for urpmi --auto-update (as any update to KDE PM will probably undo the -dpms).
Re: [Mageia-dev] what is this ????
Le 24/11/2012 20:59, AL13N a écrit : Op zaterdag 24 november 2012 20:52:42 schreef Romain d'Alverny: 2012/11/24 AL13Nal...@rmail.be: like: requiring that the fixes are done in Mageia itself (no 3rd party ... what's wrong with asking that the people who fix this do this, to do this in ... and the latter was just a suggestion, it's not required. I think Romain meant you can ask, not require ;-)
Re: [Mageia-dev] Utter frustration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/11/12 15:29, Wolfgang Bornath wrote: Just to notify Anne that the latest mails to mageia-dev arrived in 2 flavours: - 1 gnupg signed version, coming from Anne Wilson cannewil...@googlemail.com - 1 unsigned version (same text) coming from Anne Wilson an...@kde.org My apologies. When I realised that the message had gone out under my gmail address I assumed it would be dropped (yes, two in the last 24 hours :-( ). I've now subscribed the gmail address set to NOMAIL, so if I slip up it shouldn't cause any problems - I won't need to re-send. Again, apologies. Anne - -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCxKzkACgkQj93fyh4cnBeuUQCdHJp1VlTHVMDcpq9MfoXHPy+P qCwAn3oT5kxQmsG5WCLjIWq/fV3uvYER =Wx0d -END PGP SIGNATURE-
Re: [Mageia-dev] Can't win - or, best of both worlds . . .!
On 11/24/2012 02:59 PM, John Balcaen wrote: Suggest here: drop all ifcfg configuration files and switch to keyfile plugin. OK, in the spirit of Anne's original question, can you tell us exactly what the keyfile plugin is and does, and how to use it ? I'll volunteer to do a fresh install and test it.
Re: [Mageia-dev] Utter frustration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/11/12 17:00, Balcaen John wrote: Le samedi 24 novembre 2012 13:33:16 Anne Wilson a écrit : In Cauldron, I'm once again struggling with the inability to make configuration changes. I first met it and wrote about it when trying to get wifi working. Now I'm trying to change shutdown option, and meet the same problem again. Administrator authorisation is required to change the Login Manager settings That implies root password, to me, but Authentication failure, please try again. [...] Just in case did you try with your normal user password ? I did :-) Anne - -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCxLWUACgkQj93fyh4cnBf0AgCfXujyy2MTnDxw7XpcBZpPpYMU ZcQAn1UoeICwC1h9iWnaLJm1tbA+5DAw =vcpn -END PGP SIGNATURE-
Re: [Mageia-dev] Utter frustration
Frank Griffin f...@roadrunner.com writes: Do you have an I-take-everything cauldron or a pick-and-choose cauldron ? Nobody ever seems to announce policy changes on this ML, but I gather that the winds of favor have moved from ConsoleKit to PolicyKit (or maybe it's the other way around), so if, for example, ConsoleKit is now deprecated but you still have packages installed that want it, you might be getting the errors you mention below. We had a thread about deprecating hal (replaced by udisks2), policykit (replaced by polkit) and consolekit (replaced by systemd logind). Before obsoleting these, we made sure that all packages requiring them had been fixed to use the replacement. -- Olivier Blin - blino
Re: [Mageia-dev] Can't win - or, best of both worlds . . .!
2012/11/24 Frank Griffin f...@roadrunner.com On 11/24/2012 02:59 PM, John Balcaen wrote: Suggest here: drop all ifcfg configuration files and switch to keyfile plugin. OK, in the spirit of Anne's original question, can you tell us exactly what the keyfile plugin is and does, and how to use it ? I'll volunteer to do a fresh install and test it. The keyfile plugin as said earlier is the default native plugin to use with networkmanager [1] In order to introduce nm on distribution using ifcfg files (redhat/fedora) the ifcfg-rh plugin has been wrote to read make nm able to use them ( avoid interferences between nm the « old » scripts). So to use it you simply need to configure networkmanager by editing /etc/NetworkManager/NetworkManager.conf For example on my workstation i've got : cat NetworkManager.conf [main] plugins=keyfile dns=dnsmasq [keyfile] hostname=aker.cauldron.lan.littleboboy.net it's mean that i'm using the keyfile plugin (read [1] or man NetworkManager.conf for more details) ask nm to to also start dnsmasq for me. I also setup the hostname to set in nm in the keyfile section. There's also no need to do a « fresh » install to test/use it. [1] https://live.gnome.org/NetworkManager/SystemSettings -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Video players
Le samedi 24 novembre 2012 17:25:02, JA Magallón a écrit :
If you can post your video test collection somewhere, I can try to
see if totem works for me with them.
Sorry for the delay. I have uploaded a kit (33 files 500MB) of videos on
http://pjarillon.free.fr/docs/demos/
Some types of videos are given with the command file
$ ls | while read f;do file $f;done|awk -F: '{print $2 : $1}' | sort
Some formats 19/9 are displayed at 4/3 ratio.
As I said previously VLC works fine in every case.
--
Pierre Jarillon - http://pjarillon.free.fr/
Vice-président de l'ABUL : http://abul.org
Microsoft est à l'informatique ce que McDonald est à la gastronomie
Re: [Mageia-dev] Utter frustration
On 11/24/2012 03:35 PM, Olivier Blin wrote: We had a thread about deprecating hal (replaced by udisks2), policykit (replaced by polkit) and consolekit (replaced by systemd logind). Before obsoleting these, we made sure that all packages requiring them had been fixed to use the replacement. If that's my mistake, I apologize. But that was the point of my mix-and-match question: either we missed fixing something or else she's got an old package in there, since the error messages indicate that *something* is looking for a ConsoleKit systemd service file.
Re: [Mageia-dev] what is this ????
On 11/24/2012 02:59 PM, AL13N wrote: I'm not following 100%, does this mean there are already quite specific usecases for this? This is conceptually no different than someone offering to pay a developer to engineer a change to a Mageia package for himself. It's open-source, so what's the problem ? Unless he tries to distribute it, there's no violation. Whether it gets included in the official distribution is up to us. Whether the developer wants to submit the change to upstream (if there *is* an upstream) is up to him. Whether we want to do the same if he doesn't (assuming we've accepted it) is up to us. I don't accept that this drains effort away from the distro. If we had significant interest in expending our own effort to do whatever he wants done, we'd have done it. If we don't, we lose nothing in terms of community effort by letting him do it.
Re: [Mageia-dev] [changelog] [RPM] 2 core/updates_testing firefox-17.0-3.mga2
On 24 November 2012 17:01, Olivier Blin mag...@blino.org wrote:
Much to the despair of my young nephews, it segfaults on :
http://www.youtube.com/watch?v=fhCIDe92iKQ
(...)
This looks strongly like #6299 (symbols conflicts between firefox's
mozjs and mozjs185 pulled by libproxy).
It did not occur with the initial firefox version from Mageia 2, I think
it started with firefox 13.
I suggest pushing to Mageia 2 updates libproxy-0.4.7-9 (or why not
0.4.10-1 since it fixes more issues).
It fixed this crash
Now just add the proper conflict tag in order to have a smooth upgrade:
Conflicts: %{_lib}proxy1 0.4.10
(also in cauldron)
[Mageia-dev] The category in file kalgebra.desktop
In the kalgebra.desktop file the category is as: Categories=Qt;KDE;Education;Math; and with the desktop-file-validation there is a warning: kalgebra.desktop: error: (will be fatal in the future): value Math in key Categories in group Desktop Entry requires another category to be present among the following categories: Education;Science -- Dimitrios Glentadakis
