Mark your calendars for Jun 26 – 28 for FUDCon Pune. Start making travel arrangements. Think of topics to speak on, workshops and hackfests to organise, and have fun with friends.
FUDCon Pune is being hosted at MIT COE. They have excellent infrastructure and an amazing team of people who have been really helpful in addressing our needs to host a large conference.
Hop on to #fedora-india on freenode and the mailing list for information on volunteering. The etherpad has all the to-do items, feel free to jump in and help! The Twitter, Google+ and Facebook pages will have announcements and Planet Fedora will have blog posts from various people involved with the FUDCon.
It’s going to be a blast organising a FUDCon again!
When the call for bids for FUDCon APAC 2015 was put out, a few of us huddled together to discuss a bid from India. We had already organised a successful FUDCon in Pune in 2011, so our initial conversations were around which city to host it in. Pune won again, just because the number of volunteers available in Pune are more than any other place in India, and Pune has several technical colleges, which makes hosting the event at one of them easier.
This time around, we’re proposing to host the FUDCon at the MITCOE campus, more details in the bid page.
Last Saturday a few of us gathered to work on Fedora Security. This FAD (Fedora Activity Day) was the second in recent times held in Pune, after the testing FAD held in August.
The goal of the FAD was to get introduced to the newly-formed Fedora Security Team, pick up a few bug reports that were tagged as security-relevant bug reports, and triage them. Fixing the bugs wasn’t part of the agenda, as actually pushing package updates needs one to be a provenpackager or the maintainer of the package.
I participated in the Fedora Activity Day at the RH office in Pune yesterday. There was a decent turnout, 20+ people, and it was fun to test the in-progress version of the upcoming F21 release along with other folks.
I’ve been using the Fedora 18 pre-release for a couple of months now, and am generally happy with how it works. I filed quite a few bugs, some got resolved, some not. Here’s a list of things that don’t work as they used to in the past, with workarounds so they may help others:
If you have enabled git information in the shell prompt (like branch name, working tree status, etc.) , an upgrade to F18 breaks this functionality. What’s worse, __git_ps1 (a shell function) isn’t found, and a yum plugin goes looking for a matching package name to install, making running any command on the shell *very* slow.
The GNOME default of ‘hibernate’ or suspend-to-disk on very low battery power isn’t optimal for many laptops — hibernate is known to be broken on several hardware setups, it frequently results in file system corruption, and just causes pain. That, combined with the weird behaviour of the GNOME power manager to put the system in hibernate, even when the battery isn’t low, annoyed me enough to go hunting for a way to change the default.
The GUI doesn’t expose a ‘sleep’ setting; it just offers hibernate and shutdown, so here’s a tip to just put the system to sleep state (suspend to RAM), which is a much well-behaved default for me.
Updating a Fedora 16 guest to a Fedora 17 guest via preupgrade gave me the ‘Oh no, something has gone wrong!’ screen at the GDM login screen. It’s quite frustrating to see that screen because you can’t switch to a virtual terminal for troubleshooting, or even reboot or shutdown.
To send the key sequence Ctrl+Alt+F2 to the guest to switch to a virtual terminal, use the qemu monitor by pressing
and use sendkey to send the key sequence:
(qemu) sendkey ctrl-alt-f2
Then go back to the guest window by issuing
After logging in as root, I poked in the gdm log files in /var/log/gdm/ and saw the fprint daemon was causing some errors. Removing the fprintd package fixed this, but this is just a workaround, not a solution:
Apparently my initial submission was about 3x longer than the average article on opensource.com. I’ve covered events running up to the conference on this blog, and with the osdc article, I’ve covered the conf as well. There still might be a few things left which I’ll post about here in the coming days.