bwm-ng: Changing input method causes program to quit

Bug #1502593 reported by AZ
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bwm-ng (Ubuntu)
Fix Released
Undecided
Samuel Henrique

Bug Description

When changing input method the program exists with a non-zero exit
status (1) with the message:

libstatgrab error!

I'm running
ii bwm-ng 0.6-3.1ubuntu2 amd64 small and simple console-based bandwidth monitor
on ubuntu trusty.

This is the same as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746014

Upstream fixed this with
https://github.com/vgropp/bwm-ng/commit/20c51f46720dbf329e0ec46654d55b2e4d696a8a

which would also apply to the ubuntu package.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bwm-ng (Ubuntu):
status: New → Confirmed
Revision history for this message
Thiago Martins (martinx) wrote :

Happening on Xenial...

AZ (m-dev)
tags: added: patch patch-accepted-upstream
Revision history for this message
AZ (m-dev) wrote :

What is needed to get this fix into xenial?

Revision history for this message
Samuel Henrique (samueloph) wrote :

Hi, I'm the new bwm-ng Debian maintainer and i'm preparing the packaging of 0.6.1 right now, which contains this fix.

Could this new release 0.6.1 enter Xenial? If not, what can i do to fix this on Xenial? As Yaketty will sync from Debian Unstable and fix the bug.

Revision history for this message
Samuel Henrique (samueloph) wrote :

s/Yaketty/Zesty/g

Changed in bwm-ng (Ubuntu):
assignee: nobody → Samuel Henrique (samueloph)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bwm-ng - 0.6.1-2

---------------
bwm-ng (0.6.1-2) unstable; urgency=medium

  * debian/control: Build-Depends: Remove libstatgrab-dev, no longer default
    upstream, we can now build on hurd and kfreebsd.

 -- Samuel Henrique <email address hidden> Tue, 25 Oct 2016 18:04:47 -0200

Changed in bwm-ng (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
AZ (m-dev) wrote :

That fix has not yet shown up in xenial, so that bug is still present.

Revision history for this message
Samuel Henrique (samueloph) wrote :

Yeah, this release needs to be ported to Xenial, i'm not an Ubuntu developer so i'm not sure what is the workflow for this, i can help with anything needed though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.