Fedora
I love my Fedora desktop wallpapers
This is the easiest way to identify which distro I am using. Please don’t take them away.
FAD PUNE 2010
So this weekend we had FAD Pune 2010. Being organizer the main issue was to get inside the office before everyone else :)
- Packaged accessx ( with help from Sayamindu to patch it for Fedora)
- Updated code in Pony so that it works with new flickrapi API (committed but not pushed yet)
- Now we have cover images in Pathagar , the digital library system.
- Helped people with packaging
Problem with arduino in Fedora 12
Binary sketch size: 892 bytes (of a 30720 byte maximum)
/home/kdas/code/arduino/arduino-0018/hardware/tools/avrdude -C/home/kdas/code/arduino/arduino-0018/hardware/tools/avrdude.conf -v -v -v -v -patmega328p -cstk500v1 -P/dev/ttyUSB0 -b57600 -D -Uflash:w:/tmp/build6600949432041572401.tmp/Blink.cpp.hex:i
avrdude: Version 5.10, compiled on Feb 19 2010 at 10:03:26
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is “/home/kdas/code/arduino/arduino-0018/hardware/tools/avrdude.conf”
User configuration file is “/home/kdas/.avrduderc”
User configuration file does not exist or is not a regular file, skipping
Using Port : /dev/ttyUSB0
Using Programmer : stk500v1
Overriding Baud Rate : 57600
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude done. Thank you.
Any clue how to fix this ?
Fedora Project day in foss.in started
Kital is giving the first talk on Fedora Security Spin. The room is not full yet, people are still coming in slowly. Kital just a very nice example of robbing bank and how one should go ahead to plan and execute that :)
The post is brought to you by lekhonee v0.8
Boog, the desktop bugzilla client for Fedora
Few nights back I was looking for way to explain my dad how to file a bug and this starts from there. Me and mether had the initial discussion in the middle of night about the basic design and workflow.
From the project page “Boog is a desktop and command line bugzilla client that aims to provide a very easy and simple interface for end users to file bug reports. We aim to built some intelligence into the client. We will collect the Fedora version and component version information, hardware details, log output, SELinux status and other details depending on the component the user chooses to file a bug report against.”
To get automated information , I wrote some code based on this wiki page.If your package requires any other information which can be collected automatically please drop a mail to me.
I started writing a console based client for the same. For now we thought that user will know against which package he wants to file the bug.
The first screen
In the next screen, user needs to put the username and password or it will pick them up from a config file.
Next is the package name
Then a single line summary
Next it will open up your favorite editor based on $EDITOR environment variable or it will fallback to vi.
Finally it will show the report to the user , user may want to submit that to go back or cancel the whole operation.
While submitting the bug it will automatically upload the files to be attached.
After submitting the report the user will get an URL of the bug just filed.
You can see the process in this screencast.
We need help on the mockup of the Gtk based GUI. Please contact me or mether in case you want.
Any new ideas or suggestions are welcome :)
The post is brought to you by lekhonee v0.7
Fedora in light painting
Also I was endowed with some super power tonight.
The post is brought to you by lekhonee v0.6