Deepening the GNU/Linux community

2009-07-10 Thread shirish
Hi all,
Apart from the usual things that one needs to speak about
Free Software, I have also made some pointers as to the way I see
things in my community
http://flossexperiences.wordpress.com/2009/07/09/deepening-the-gnulinux-community/

This is just an attempt to let some of the developers, testers, users
and to be users to know what some of the problem areas and atleast
have awareness about them. Some of them have answers, for some answers
need to be found and so on and so forth.

Feel free to add or rip apart whatever you think is right. Also
perhaps some of these questions could be used if found fitting with
technical audiences (as they love challenges :) ) .

Comments, suggestions, brickbats all welcome :)
-- 
  Regards,
  Shirish Agarwal
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: gparted, ubiquity and other packages left behind by karmic a2 installer

2009-07-10 Thread Nathan Dorfman
On Tue, Jun 30, 2009 at 5:28 PM, Colin Watson wrote:
> On Tue, Jun 30, 2009 at 11:27:02AM -0400, Nathan Dorfman wrote:
>> On Mon, Jun 29, 2009 at 8:39 PM, Colin Watson wrote:
>> > (It's surprising that you apparently didn't see a dialog informing you
>> > that the installer had crashed. It must have gone down pretty hard.)
>>
>> Yup. I had no idea that it crashed until you just told me :)
>
> Interesting. That's a rather curious bug in itself.

Yeah. The crash itself turned out to be a dupe -- 395425. Following
your suggestion in the main bug, I updated ubiquity in the live
desktop env., and confirmed that it is fixed.

I was also taken aback, though, by how non-obvious it was that the
installler crashed. Am I the only one for whom the gnome crash
notification occurs long after the crash -- at least a minute, maybe
two, into the live desktop session? This is on relatively modern
hardware. If not, shouldn't the installer at least be wrapped in some
script? One that can at least say "We're sorry, but something went
wrong." After all, booting the (perhaps partially-) installed system
will produce undefined results at this point.

Of course, in my case everything worked pretty much flawlessly for
weeks, as evidenced by the progression in this thread. So, perhaps
it's best not to worry the user unnecessarily. ;-)

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss