Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 21:56, Frank Griffin wrote: > Wow. I was assuming all along that the problem stemmed from a > massive upgrade from some MGA2 system. If you installed a 3rd > April beta, had it working perfectly, and something uploaded to > cauldron in th

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 19:50, Frank Griffin wrote: > On 04/10/2013 02:21 PM, Anne Wilson wrote: >> Out of curiosity I tried the distro upgrade. It appeared to >> complete, but booted to a blank screen, so I didn't waste any >> more ti

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 13:07, Frank Griffin wrote: > On 04/10/2013 07:31 AM, Anne Wilson wrote: I think there may be some misunderstandings, so I'll try to correct them inline. > Interesting. I guess you didn't configure eth0 from the Instal

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 12:15, Colin Guthrie wrote: > 'Twas brillig, and Frank Griffin at 10/04/13 12:00 did gyre and > gimble: >>> >>> Starting afresh, I followed the steps up to running XFdrake >>> (but not running XFdrake yet). I tried 'ifup eth0' but >>> 'R

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 12:00, Frank Griffin wrote: >> >> Starting afresh, I followed the steps up to running XFdrake (but >> not running XFdrake yet). I tried 'ifup eth0' but 'Running in >> chroot. Ignoring request'. After "exit" this changed to "Running >> in

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 20:48, Frank Griffin wrote: > On 04/08/2013 02:41 PM, Anne Wilson wrote: >> No, it doesn't. When I ran XFdrake the test did display >> colours, though at a resolution I wouldn't want to work with :-) >> Ho

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 20:48, Frank Griffin wrote: > On 04/08/2013 02:41 PM, Anne Wilson wrote: >> No, it doesn't. When I ran XFdrake the test did display >> colours, though at a resolution I wouldn't want to work with :-) >> Ho

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/13 00:55, David W. Hodgins wrote: > On Mon, 08 Apr 2013 12:52:06 -0400, Anne Wilson > wrote: > >> Rebooting, nothing has changed. I get grub, lots of disk >> activity led flickering, but no output to the screen, with

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 22:49, Colin Guthrie wrote: > 'Twas brillig, and Thomas Backlund at 08/04/13 22:43 did gyre and > gimble: >> Colin Guthrie skrev 9.4.2013 00:31: >>> 'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre >>> and gimble: >> >>>

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 18:28, Frank Griffin wrote: > On 04/08/2013 12:52 PM, Anne Wilson wrote: >> Something very odd is happening, indeed. Remember this was a >> functioning system before I did the updates. >> >> Rebooting, nothi

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 17:22, Frank Griffin wrote: > On 04/08/2013 12:13 PM, Anne Wilson wrote: >> OK, moving on. Listing /mnt/etc/systemd/system/ I have no >> default.target link, so I assume I have to make one. Is that >> >>

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 16:37, Frank Griffin wrote: > On 04/08/2013 11:03 AM, Anne Wilson wrote: >> modprobe: FATAL: Module shpchp not found modprobe: FATAL: Module >> snd_hda_intel not found >> >> How do I get these? >> > I&

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 13:20, Thomas Backlund wrote: > Frank Griffin skrev 4.4.2013 19:12: >> On 04/04/2013 10:59 AM, Anne Wilson wrote: >>> Not much progress. My usual method of editing the kernel line >>> to get a level 3 boot doe

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 13:12, Frank Griffin wrote: > Or, you can boot the classic install ISO, and one of the GUI > choices should be Rescue. > > Once you get the Rescue panel, select Go to Console. Then type > "drvinst", since rescue tends to lag modern hardw

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/04/13 14:48, Frank Griffin wrote: > On 04/07/2013 09:25 AM, Anne Wilson wrote: >> On rebooting there was a good deal of disk activity light >> flickering, but a completely black screen. > Follow the instructions to boot into

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/13 17:12, Frank Griffin wrote: > On 04/04/2013 10:59 AM, Anne Wilson wrote: >> Not much progress. My usual method of editing the kernel line to >> get a level 3 boot doesn't work - same blank (but lit) screen. >> Fa

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 17:50, Anne Wilson wrote: > > This is an Acer Aspire One 533, with Intel N550 chipset, everything > on-board. I wasn't doing anything unusual, so there does seem to > be a real problem. Tomorrow I'll try to ge

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 14:48, Sandro CAZZANIGA wrote: > Le 03/04/2013 15:46, Anne Wilson a écrit : >> On 03/04/13 14:37, Sandro CAZZANIGA wrote: >>> Le 03/04/2013 15:36, Anne Wilson a écrit : >>>> I've just come acr

Re: [Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 14:37, Sandro CAZZANIGA wrote: > Le 03/04/2013 15:36, Anne Wilson a écrit : >> I've just come across a bug in the software installer - where >> should it be reported? >> >> Anne >> > >

[Mageia-dev] M3 beta - where to report problems?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've just come across a bug in the software installer - where should it be reported? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFcMEIACgkQj93fyh

Re: [Mageia-dev] Why is AHCI statically compiled into kernel?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 19:14, AL13N wrote: > Op donderdag 7 maart 2013 12:18:09 schreef Anne Wilson: >> On 07/03/13 12:03, AL13N wrote: >>>> On 07/03/13 04:38, R James wrote: >>> [...] >>> >>>>> So

Re: [Mageia-dev] Why is AHCI statically compiled into kernel?

On 07/03/13 12:03, AL13N wrote: >> On 07/03/13 04:38, R James wrote: > [...] >>> So the 'nickname' feature you request is available with a little >>> pre-install preparation and post-install config file editing. >>> >>> Hope this helps -- RJ >>> >> Thanks. It will help a lot for my own use. Howev

Re: [Mageia-dev] Why is AHCI statically compiled into kernel?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 09:55, jpbfree wrote: > Le 07/03/2013 10:27, Anne Wilson a écrit : On 07/03/13 04:38, R > James wrote: >>>> On Wed, Mar 6, 2013 at 1:37 PM, AL13N >>> <mailto:al...@rmail.be>> wrote: >>>> >

Re: [Mageia-dev] Why is AHCI statically compiled into kernel?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 04:38, R James wrote: > On Wed, Mar 6, 2013 at 1:37 PM, AL13N > wrote: > >> >> While I appreciate the intention, from a user PoV, those UUIDs >> mean b* all. It would be really nice if, when they are first >>

Re: [Mageia-dev] Why is AHCI statically compiled into kernel?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/03/13 17:11, Colin Guthrie wrote: > Anything that relies on ordering is just broken by design. We need > to handle things gracefully regardless of the order they are > detected. This is why UUIDs are the defacto method for filesystem > identifica

Re: [Mageia-dev] Critical Samsung UEFI bug: "Booting Linux using UEFI can brick Samsung laptops"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/02/13 07:27, Thomas Backlund wrote: > Johnny A. Solbu skrev 1.2.2013 06:57: >> http://www.h-online.com/open/news/item/Booting-Linux-using-UEFI-can-brick-Samsung-laptops-1793958.html >> >> >> >> "Booting Linux using UEFI just once on various Sams

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/13 14:16, Angelo Naselli wrote: >> Which is already the case in mageia 2 for the live cd at least. >> However nepomuk is more & more intricated in KDE so we'll >> probably won't be able to do it for mga4 for sure & eventually >> mga3. The goo

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/13 12:43, AL13N wrote: > Op donderdag 3 januari 2013 10:34:26 schreef Anne Wilson: >> On 02/01/13 16:35, AL13N wrote: >>> you're symptoms look like OOM >>> >>> ie: out of memory >> >>

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/13 14:11, Angelo Naselli wrote: > Il 03/01/2013 11:41, Anne Wilson ha scritto: >> On 03/01/13 10:35, Guillaume Rousse wrote: >>> Le 03/01/2013 11:30, Anne Wilson a écrit : >>>>> imho: nepomuk is

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/13 12:57, AL13N wrote: > Op donderdag 3 januari 2013 10:48:07 schreef Robert Wood: >> The first thing I do on a fresh install is uninstall it. It's a >> truly awful piece of software! That and the akandi thing just >> render the whole system u

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/13 10:35, Guillaume Rousse wrote: > Le 03/01/2013 11:30, Anne Wilson a écrit : >>> imho: nepomuk is a beast and uses too much memory. >>> >> Like many people, I don't see any advantage. > What prevents you

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/01/13 16:35, AL13N wrote: > you're symptoms look like OOM > > ie: out of memory > When all is quiet, this morning, Mem on this 32-bit system is 2898M - 1708M free. If I get chance to check it when things start to go wrong, before it gets crit

Re: [Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/01/13 16:35, AL13N wrote: > Op woensdag 2 januari 2013 11:55:06 schreef Anne Wilson: >> This last couple of days I've had frequent total freezes of my >> M2 system. If I can get to the System Activity monitor i

[Mageia-dev] Frequent freezes in M2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This last couple of days I've had frequent total freezes of my M2 system. If I can get to the System Activity monitor in time I can kill akonadi_nepomuktag_resource and I can work again - if I'm too late I have to hard reset. There must be some way t

Re: [Mageia-dev] hplip broken?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16/12/12 22:25, Adrien Guichard wrote: > I cannot print on my photosmart 3100 , which used to work > like charm for ages... > > First I tried in mcc, but no way to detect my printer, then I do > try "HP Device Manager" which shows my printer, but c

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/11/12 12:26, Frank Griffin wrote: > On 11/30/2012 07:13 AM, Anne Wilson wrote: >> >> Before doing all that, can you explain the significance of the >> suffixes here? >> >> ls /usr/lib/ | grep powerdevil >&

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/11/12 22:35, Frank Griffin wrote: > On 11/29/2012 11:58 AM, Anne Wilson wrote: >> >> OK, done that. As you expected, it returned >> >> /usr/lib/libpowerdevilcore.so.0.1.0 /usr/lib/packagekitd >> /usr/lib/li

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/11/12 16:38, Frank Griffin wrote: > On 11/26/2012 08:33 AM, Anne Wilson wrote: >> >> Perfect. The 'find' returns >> >> /usr/lib/libpowerdevilcore.so.0.1.0 /usr/lib/packagekitd >> /usr/lib/libpolkit

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/11/12 13:33, Anne Wilson wrote: > On 25/11/12 17:22, Liam R E Quin wrote: >> On Sun, 2012-11-25 at 14:01 +0000, Anne Wilson wrote: > >>>> Since there's no identification in the message, all I could >>>&g

Re: [Mageia-dev] Hello Mageia!!!!

On 26/11/2012 18:54, Joseph Wang wrote: > I would like to attend the weekly meeting, but I'm in Asia. > May I suggest that you leave an IRC window open overnight, then, read the backscroll, and simply reply to the channel at a more convenient time if you see things that need comment? Time zones d

Re: [Mageia-dev] Mailing-list archives and robots

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/11/2012 16:54, Christian Lohmaier wrote: > Hi Sander, *, > > On Mon, Nov 26, 2012 at 4:08 PM, Sander Lepik > wrote: >> >> Good point! So we are probably missing links to our archives (as >> i can't find anything that links to mageia-dev archiv

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/11/12 17:22, Liam R E Quin wrote: > On Sun, 2012-11-25 at 14:01 +0000, Anne Wilson wrote: > >>> Since there's no identification in the message, all I could >>> suggest is a brute-force search of all files on the r

[Mageia-dev] Incredibly slow bootup in Cauldron - FYI

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is purely informational - hoping that someone searching archives will find it useful. Cauldron had recently been incredibly slow at bootup - 17 minutes to get to a functional desktop. It is now back to the normal time for the netbook, between 1

Re: [Mageia-dev] Locking screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/11/2012 13:50, Luc Menut wrote: > Le 23/11/2012 21:07, Anne Wilson a écrit : >> After today's Cauldron update I find that my screen is locked >> frequently, requiring my password to unlock it. Since I >> normally wo

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/11/2012 13:01, Frank Griffin wrote: > On 11/25/2012 04:04 AM, Anne Wilson wrote: >> Is there somewhere I could check to find out what it is? > > Since there's no identification in the message, all I could suggest > is

Re: [Mageia-dev] Can't win - or, best of both worlds . . .!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/11/2012 20:38, John Balcaen wrote: > > > > 2012/11/24 Frank Griffin > > > On 11/24/2012 02:59 PM, John Balcaen wrote: > > > Suggest here: drop all ifcfg configuration files and switch to > keyfile plugin. > >

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/11/12 20:05, Frank Griffin wrote: > On 11/24/2012 08:20 AM, Anne Wilson wrote: >>> >> In Cauldron, I'm once again struggling with the inability to make >> configuration changes. I first met it and wrote about

Re: [Mageia-dev] Utter frustration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/11/12 20:57, Frank Griffin wrote: > 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 th

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 &

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) comi

[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 Mana

[Mageia-dev] Utter frustration

-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 aut

Re: [Mageia-dev] Can't win - or, best of both worlds . . .!

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 stru

[Mageia-dev] Locking screen

After today's Cauldron update I find that my screen is locked frequently, requiring my password to unlock it. Since I normally work with two laptops at the same time - Cauldron and M2 - this is a huge nuisance to me. Where can I change that setting? Anne

[Mageia-dev] Locking screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After today's Cauldron update I find that my screen is locked frequently, requiring my password to unlock it. Since I normally work with two laptops at the same time - Cauldron and M2 - this is a huge nuisance to me. Where can I change that setting?

Re: [Mageia-dev] [Bug 8177] rm command can't delete file, unless using the full path for the rm binary "/bin/rm"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/11/2012 15:27, EatDirt wrote: > On 22/11/12 15:45, Michael Wood wrote: >> >> >> Or if you happy to run rm as it was written and risk deleting >> something you didn't want too, then comment out the alias (and >> any others that get on your nerve

Re: [Mageia-dev] USB speaker systems

On 22/11/2012 01:31, David W. Hodgins wrote: > On Wed, 21 Nov 2012 19:39:15 -0500, Richard Couture > wrote: > >> I was looking at the Bose Companion 5 speaker system and noticed that it >> intefaces with the computer via USB. >> >> Am I going to run into problems with Mageia if I buy it? > > Acc

Re: [Mageia-dev] USB speaker systems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/11/2012 01:31, David W. Hodgins wrote: > On Wed, 21 Nov 2012 19:39:15 -0500, Richard Couture > wrote: > >> I was looking at the Bose Companion 5 speaker system and noticed >> that it intefaces with the computer via USB. >> >> Am I going to run

Re: [Mageia-dev] Problem with Totem packages?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/11/2012 13:39, Olav Vitters wrote: > You really like VLC :) So do I :-) It plays whatever you throw at it. Not as pretty as some, perhaps, but by heck, it works, and works everywhere :-) Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4

Re: [Mageia-dev] Not very important require about mail checker.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/11/2012 10:29, André Salaün wrote: > Hello ! > > Is it possible to reintroduce gnubiff in Mageia 3. All mail > checkers (in mga 2) depend on a wm. In kde they don't check the > mail spooler, only kmail, gmail, thunderbird etc. Gnubiff is more

Re: [Mageia-dev] System policy prevents modification of network settings for all users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/11/12 17:42, Bo Lan wrote: > On Wed, 2012-11-14 at 17:14 +0000, Anne Wilson wrote: >> I've been seeing this message every few minutes for the past >> week or so (Cauldron on my netbook, BCM4313). It request a >> pass

[Mageia-dev] digikam updates problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've added updates-testing to my sources, hoping to test HPLIP (which hasn't offered me an update of that package yet). Most of the proposed update installed, but it ended with Installation failed:file /usr/share/kde4/servicetypes/kipiplugin.desk

Re: [Mageia-dev] System policy prevents modification of network settings for all users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/11/12 17:42, Bo Lan wrote: > On Wed, 2012-11-14 at 17:14 +0000, Anne Wilson wrote: >> I've been seeing this message every few minutes for the past >> week or so (Cauldron on my netbook, BCM4313). It request a >> pass

[Mageia-dev] System policy prevents modification of network settings for all users

I've been seeing this message every few minutes for the past week or so (Cauldron on my netbook, BCM4313). It request a password, but no indication of what password. I've tried the network password, the root password and the user password. All I ever get is a minute's delay, then the same messag

[Mageia-dev] System policy prevents modification of network settings for all users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been seeing this message every few minutes for the past week or so (Cauldron on my netbook, BCM4313). It request a password, but no indication of what password. I've tried the network password, the root password and the user password. All I eve

Re: [Mageia-dev] Draft of a Letter to the Software Freedom Law Center (SFLC).

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/2012 10:52, Wolfgang Bornath wrote: > 2012/11/8 Trish Fraser : >> >> >>> Hi Donald and Johnny, >>> >>> On Thu, 8 Nov 2012 09:15:09 + Donald Stewart >>> wrote: >>> On 8 November 2012 00:45, Johnny A. Solbu wrote: >

Re: [Mageia-dev] Draft of a Letter to the Software Freedom Law Center (SFLC).

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/2012 10:03, Wolfgang Bornath wrote: > 2012/11/8 Anne Wilson : >> >>> This is an official letter, and therefore should have the >>> official address to the recipient. >>> >>> Consider using a

Re: [Mageia-dev] Draft of a Letter to the Software Freedom Law Center (SFLC).

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/2012 09:15, Donald Stewart wrote: > On 8 November 2012 00:45, Johnny A. Solbu > wrote: > > On Tuesday 06 November 2012 23:39, Shlomi Fish wrote: >> Dear sirs or madams, > > To me, this sounds a little to generic, a

Re: [Mageia-dev] Packages not updating?

On 29/10/2012 20:01, AL13N wrote: > Op maandag 29 oktober 2012 19:52:47 schreef Anne Wilson: >> Earlier today I did a big update on Cauldron. Since then my wireless >> connection has not been working. I started to gather information to >> report this, but when I asked MCC f

Re: [Mageia-dev] Packages not updating?

On 30/10/2012 11:16, Christian Lohmaier wrote: > Hi Anne, *, > > On Mon, Oct 29, 2012 at 8:29 PM, Anne Wilson > wrote: >> >> Earlier today I did a big update on Cauldron. Since then my >> wireless connection has not been working. I started to gather >> in

[Mageia-dev] Packages not updating?

Earlier today I did a big update on Cauldron. Since then my wireless connection has not been working. I started to gather information to report this, but when I asked MCC for hardware detection I was immediately told that broadcom-wl-kernel and two other packages (one was broadcom-wl-kernel-netbo

[Mageia-dev] Packages not updating?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Earlier today I did a big update on Cauldron. Since then my wireless connection has not been working. I started to gather information to report this, but when I asked MCC for hardware detection I was immediately told that broadcom-wl-kernel and two o

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release taskcoach-1.3.20-1.mga3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/10/12 12:32, Thierry Vignaud wrote: > This is Mageia Linux, we don't care about other OSes, especially in > description If one has to work in a Windows environment (or other, for that matter) at times, then knowing that an application is cross-p

Re: [Mageia-dev] Failed Cauldron update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/10/12 13:21, Nicolas Lécureuil wrote: > Le lundi 8 octobre 2012 14:19:54 Nicolas Lécureuil a écrit : >> Le lundi 8 octobre 2012 13:14:14 Anne Wilson a écrit : >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>&g

[Mageia-dev] Failed Cauldron update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been away from Cauldron for a while, but trying to update today I get The following packages have to be removed for others to be upgraded: digikam-2.9.0-1.mga3.i586 (due to missing marble-common) marble-4.9.1-1.mga3.i586 (due to missing marble-

Re: [Mageia-dev] Any progress on the NFS mount problem? - SOLVED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/10/12 02:31, Colin Guthrie wrote: > 'Twas brillig, and Guillaume Rousse at 01/10/12 21:41 did gyre and > gimble: >> With NFSv4, the server remaps its actual filesystem (/home, for >> instance) in a pseudo-filesystem, which is seen by clients as

Re: [Mageia-dev] Any progress on the NFS mount problem? - SOLVED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 GOT IT!!! Remembered that you said it would mount as /, to which I don't have access of course. I removed 'fsid=0', restarted, and all is well. I can see all my data! Thanks for your patience. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4

Re: [Mageia-dev] Any progress on the NFS mount problem? - One step further

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/12 20:16, Anne Wilson wrote: >> Argh!! re-reading those lines, it's giving the IP address >> instead of the mount point. > > Garbage. Ignore. > > I've obviously stared at this too long and I'm not

Re: [Mageia-dev] Any progress on the NFS mount problem? - One step further

> Argh!! re-reading those lines, it's giving the IP address instead of the > mount point. Garbage. Ignore. I've obviously stared at this too long and I'm not making any sense at all now. Anne

Re: [Mageia-dev] Any progress on the NFS mount problem? - One step further

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/12 19:02, Guillaume Rousse wrote: > Le 01/10/2012 17:46, Anne Wilson a écrit : >> The good news (after rebooting server and client) that the server >> now is running nfs and nfs_acl > Over IPv4, or over IPv6 only as prev

Re: [Mageia-dev] Any progress on the NFS mount problem? - One step further

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/12 12:18, Guillaume Rousse wrote: > Le 22/09/2012 21:16, Anne Wilson a écrit : >> udp0 0 *:nfs *:* unfsd > Ouch... You're running an obsolete alternative nfs server. You > should uninsta

Re: [Mageia-dev] Any progress on the NFS mount problem? - One step further

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 01 Oct 2012 13:18:36 Guillaume Rousse wrote: > Le 22/09/2012 21:16, Anne Wilson a écrit : >> udp0 0 *:nfs *:* >> >> unfsd > > Ouch... You're running an obsolete alte

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 16:09, Thomas Backlund wrote: > Colin Guthrie skrev 27.9.2012 15:31: >> 'Twas brillig, and Anne Wilson at 27/09/12 11:02 did gyre and >> gimble: >>> >>> While the new reboot is completing, and whi

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 14:37, Colin Guthrie wrote: > Ahh a nice simple answer in the end! > > I probably should have been more persistant in asking this question > initially (I think I did mention it in an earlier mail, but also > asked a whole bunch of other

[Mageia-dev] Possible X/RandR problem in M3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I often work with my netbook connected to a VGA monitor. The Configure Display page shows LVDS size 1280 x 720 (Auto) VGA1 size 1024 x 768 Those settings look correct. The problem comes with the Primary Output setting. If I set LVDS as Primary out

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 13:40, Anne Wilson wrote: > On 27/09/12 13:31, Colin Guthrie wrote: >> Oh I would disagree. I think intel is more common (but I base >> this on very little evidence!) Certainly I *always* ensure I have >> an int

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 13:31, Colin Guthrie wrote: > Oh I would disagree. I think intel is more common (but I base this > on very little evidence!) Certainly I *always* ensure I have an > intel card in anything I purchase. Their Open Source commitment is > just m

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 09:59, Anne Wilson wrote: > On 26/09/12 23:20, AL13N wrote: > >> this is normal behavior for gmail, it's why i stopped using it: > >> it works like this, if you are on a mailing list, and it ends up >>

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 10:15, Colin Guthrie wrote: > Does it work when forcing a runlevel 3 boot instead. This is > closer to a proper boot and likely a better testing environment. I > presume the getty's are showing for you in level 3? > To my surprise, the sam

Re: [Mageia-dev] M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/09/12 09:40, Colin Guthrie wrote: > I pointed you at this mail in the archives when you were having > troubles, but I don't think you're replied to it to give the > necessary debug info. Hi Colin. No, I had next to no time to spend on it yeste

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/09/12 23:20, AL13N wrote: > Op woensdag 26 september 2012 20:57:43 schreef Anne Wilson: >> On 26/09/2012 16:24, Jani Välimaa wrote: >>> On 26.09.2012 18:00, Anne Wilson wrote: >>>> Colin, I sent this last evening,

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/09/12 16:12, Marja van Waes wrote: > Can you try doing "systemctl show prefdm.service | grep > ActiveEnter.*Mono" after a fresh boot. > > I don't need to know the results, just whether it's non-zero or > still at 0. > > Assuming it's still at

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/09/2012 17:05, Jani Välimaa wrote: > On 26.09.2012 18:29, Wolfgang Bornath wrote: >> 2012/9/26 Jani Välimaa : >>> On 26.09.2012 18:00, Anne Wilson wrote: >>>> Colin, I sent this last evening, but I haven't seen

Re: [Mageia-dev] Fwd: Re: M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/09/2012 16:24, Jani Välimaa wrote: > On 26.09.2012 18:00, Anne Wilson wrote: >> Colin, I sent this last evening, but I haven't seen it on-list. >> For some reason a fair number of my messages don't get through. >&g

Re: [Mageia-dev] M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/09/2012 16:44, Jani Välimaa wrote: > On 24.09.2012 22:21, Anne Wilson wrote: >> I finally got around to connecting my netbook, which has been >> running Cauldron for some time. This was fully up to date before >> my holiday

[Mageia-dev] Fwd: Re: M3 won't complete boot after update

ubject: Re: [Mageia-dev] M3 won't complete boot after update Date: Tue, 25 Sep 2012 16:37:20 +0100 From: Anne Wilson To: Mageia development mailing-list On 25/09/12 15:41, Colin Guthrie wrote: > 'Twas brillig, and Anne Wilson at 25/09/12 15:02 did gyre and > gimble: >> Sent yes

Re: [Mageia-dev] M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/09/12 15:41, Colin Guthrie wrote: > 'Twas brillig, and Anne Wilson at 25/09/12 15:02 did gyre and > gimble: >> Sent yesterday, but not seen on-list, so apologies if this is a >> duplicate. >> >> I finally

[Mageia-dev] M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sent yesterday, but not seen on-list, so apologies if this is a duplicate. I finally got around to connecting my netbook, which has been running Cauldron for some time. This was fully up to date before my holidays, and apart from the recent display p

[Mageia-dev] M3 won't complete boot after update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I finally got around to connecting my netbook, which has been running Cauldron for some time. This was fully up to date before my holidays, and apart from the recent display problem (which as Angelo Naselli suspected, is a KDE problem) it has behaved

Re: [Mageia-dev] Any progress on the NFS mount problem? - One step further

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/09/12 08:26, Thierry Vignaud wrote: > On 23 September 2012 11:18, Anne Wilson > wrote: >>>> Package nfs-utils blahblah is already installed >>> nfs-common service, sorry. >>> >> That may well poin

  1   2   >