RESEARCHUT

Lately, for my day job (to be more efficient for the time I spent), I am required to use Windows, back again. :-)

It is great to be back. By back, I mean using Windows for some of the workflows. All these years, I’ve been using Linux based tools (Debian, Kontact | IceDove, Konq | Chromium | IceWeasel etc) to get my job done. It is great to try back Windows for some of the workflows.

I just released Laptop Mode Tools @ version 1.64. And am pleased to introduce the new graphical utility to toggle individual power saving modules in the package.

The GUI is written using the PyQT Toolkit and the options in the GUI are generated at runtime, based on the list of available power saving modules.

Apart from the GUI configuration tool, this release also includes some bug fixes:

• Don’t touch USB Controller power settings. The individual devices, when plugged in, while on battery, inherit the power settings from the USB controller
• start-stop-programs: add support for systemd. Thanks to Alexander Mezin
• Replace hardcoded path to udevadm with “which udevadm”. Thanks to Alexander Mezin
• Honor .conf files only. Thanks to Sven Köhler
• Make ‘/usr/lib’ path configurable. This is especially useful for systems that use /usr/lib64, or /lib64 directly. Thanks to Nicolas Braud-Santoni
• Don’t call killall with the -g argument. Thanks to Murray Campbell
• Fix RPM Spec file build errors

The Debian package will follow soon. I don’t intend to introduce a new package for the GUI tool because the source is hardly 200 lines. So the dependencies (pyqt packages) will go as Recommeds or Suggests

The power consumption on the Linux kernel 3.10 is pretty bad.

On kernel 3.10, with the follwing config, the PowerTop results are:

#

# Timers subsystem

#

CONFIG_TICK_ONESHOT=y

CONFIG_NO_HZ_COMMON=y

# CONFIG_HZ_PERIODIC is not set

CONFIG_NO_HZ_IDLE=y

# CONFIG_NO_HZ_FULL is not set

CONFIG_NO_HZ=y

CONFIG_HIGH_RES_TIMERS=y

PowerTOP v2.0 Overview Idle stats Frequency stats Device stats Tunables

The battery reports a discharge rate of 28.0 W

The estimated remaining time is 23 minutes

Summary: 1785.5 wakeups/second, 0.0 GPU ops/second, 0.0 VFS ops/sec and 22.1% CPU use

As someone who learned computers on his own, I always acknowledged the value that the Free Software movement has brought. The accessibility of these topics, which are only supposed to be part of text books and schools, is available for anyone and everyone who has the resource and passion to do it.

But this past week, 2 things made me pretty impressed with the maturity and quality of work that we do.

[rrs@learner ~] tar -axvf researchut-1.2.0.tar.bz2 && ls

It is still 2012 in this part of the world and the world is still intact. Since nothing major happened, I thought of spending the new gifted time to add a long pending item to apt-offline. As shown in the screen shots, apt- offline’s GUI now has support to detect and display the downloaded offline bug reports.

This is part of the just released, version 1.3.

I recently switched to a ThinkPad W530 laptop. It is a fairly recent machine with the following hardware config:

• Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
• 8 GiB RAM
• nVIDIA Optimus
• Samsung SSD Drive

On the software front, I decided to take my chances. Hence:

Hello World. This is the follow-up to the last [2](http://blog/report-bugs- with-apport) updates on the state of apport in Debian.

A lot has changed since the last update on Apport. Currently, in Experimental, we have version 2.6.1-2. With this version, and going forward, there will be no hacks to make it work for Debian. Thanks to Martin Pitt, with his assistance, Apport now has a very basic crashdb in place for Debian. The Debian crashdb provides Apport the interface to interact with the Debian BTS.

This is a follow up to the previous post regarding Reporting bugs with Apport

Apport, version 2.2.3-2, has been pushed to experimental. There were some nice feedback that led to some more changes that I will talk here.

**Opt out: **As a developer, if you see the volume of reports to be annoying, you have the option to opt out of apport reports. To do this, you should specify the XBS-Apport: No field in your package ’s control file. When your application crashes, apport first checks for that field in your package’s description and acts based on what you chose.

So yet another bug reporting tool. :-)

When I prepared Apport for Debian, I wasn’t sure how it will look going forward. If you look at the current one lying in experimental, it just detects your crashes and pops up in your systray. It doesn’t have the mechanism to interact with BTS.

So, like the title of this post says, this is the first worthy feature for Apport in the context of Debian.