Main Inclusion Report for mousetweaks

Bug #190208 reported by Francesco Fumanti
12
Affects Status Importance Assigned to Milestone
mousetweaks (Ubuntu)
Undecided
Unassigned

Bug Description

Package hint: mousetweaks

The corresponding main inclusion report can be found here:
https://wiki.ubuntu.com/MainInclusionReportMousetweaks

A debdiff against gnome-control-center will be submitted to ubuntu-main-sponsors with a mousetweaks dependency.

Changed in mousetweaks:
assignee: nobody → ubuntu-mir
Changed in mousetweaks:
assignee: ubuntu-mir → nobody
Revision history for this message
Francesco Fumanti (frafu) wrote :

Here is the bug filed against the gnome-control-center with the debdiff that adds mousetweaks to the dependency list:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/190554

Revision history for this message
Matthias Klose (doko) wrote :

Luke, Henrik,
package looks ok, but seems to start an additional process if it is installed. do we want this behaviour?

Changed in mousetweaks:
status: New → Incomplete
Revision history for this message
Francesco Fumanti (frafu) wrote :

@Matthias

There is probably something weird going on: mousetweaks has no code to start an additional process. Could you please tell us what additional process it started on your machine?

Revision history for this message
Matthias Klose (doko) wrote :

the MIR reads:
> The mousetweaks package installs a daemon and two gnome-panel applets.

Revision history for this message
Francesco Fumanti (frafu) wrote :

@Matthias

ok, I suppose now that your problem is the daemon:

Maybe that I should have clarified in the Main Inclusion Report that the daemon only runs when the user activates one of the features it implements. In other words, when the user activates for example dwelling in the Mouse control panel, the mousetweaks process gets started. And deactivating the dwelling feature kills the process. (The same also happens with the Simulated Secondary Click.)

So there is no additional process running on the machine if the user does not use the features it implements.

To be complete, there is a way to start mousetweaks at the command line without activating any feature; but even if the user would not kill the mousetweaks process before logout, it would not automatically restart at the next login. But what sense would it make to start mousetweaks by command line without activating one of its features? Finally, this situation is not possible when mousetweaks is controlled by the corresponding gui (the Accessibility tab of the Mouse control panel).

Revision history for this message
Francesco Fumanti (frafu) wrote :

I have now added to the MIR-report that the mousetweaks daemon only runs if the user activates one of the features it offers.

Revision history for this message
Luke Yelavich (themuso) wrote :

Yes, I can confirm that the mousetweaks daemon only runs if the mousetweaks options are enabled. The applets are also there for these options, so this is ok by me.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

I agree that this is an important feature and should be included in the default install (and thus promoted to main). I don't have the technical view to comment on how intrusive the deamon might be, but from other people's comments it sounds harmless. I would suggest we include it now and let it have some testing. We can then possibly pull out the more intrusive elements later.

Revision history for this message
Martin Pitt (pitti) wrote :

This looks good to me, I approved and promoted mousetweaks.

Now the following needs to happen:

 - Add the dependency somewhere or seed it
 - Please make sure that mousetweaks gets at least one more upload in Hardy, so that the language-pack magic and LP translation import can kick in.

Changed in mousetweaks:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers