On 01/18/2013 01:07 PM, Colin Watson wrote:
> On Fri, Jan 18, 2013 at 11:32:16AM -0600, Michael Spencer wrote:
>> Okay, that makes sense. What I'm trying to do is identify the package
>> and then access the Launchpad entry for the package. But for example,
>> Libreoffice seems to lump all the libre
On Fri, Jan 18, 2013 at 11:32:16AM -0600, Michael Spencer wrote:
> Okay, that makes sense. What I'm trying to do is identify the package
> and then access the Launchpad entry for the package. But for example,
> Libreoffice seems to lump all the libreoffice packages into one
> Launchpad entry, https
On 01/18/2013 10:54 AM, Martin Pitt wrote:
> Michael Spencer [2013-01-18 10:39 -0600]:
>> What is the best way to discover the package a program is in by clicking
>> on an open window?
>>
>> So far I've been using xprop to get the PID of the window, reading where
>> /proc//exe points too, and then
Michael Spencer [2013-01-18 10:39 -0600]:
> What is the best way to discover the package a program is in by clicking
> on an open window?
>
> So far I've been using xprop to get the PID of the window, reading where
> /proc//exe points too, and then running apt-file search on that.
That's by and l
On 18 January 2013 16:39, Michael Spencer wrote:
> What is the best way to discover the package a program is in by clicking
> on an open window?
>
> So far I've been using xprop to get the PID of the window, reading where
> /proc//exe points too, and then running apt-file search on that.
>
> Howev
What is the best way to discover the package a program is in by clicking
on an open window?
So far I've been using xprop to get the PID of the window, reading where
/proc//exe points too, and then running apt-file search on that.
However, for some programs, like LibreOffice Writer, I get
libreoff
