im-config should not use ".xsession-errors" file for informational messages

STDOUT is output for piping data and im-config uses it for that purpose.

Errors and informational context messages should go to STDERR.

.xsession-errors just record everything on STDERR. (im-config does not set file name.)

If you have reference which supports your view of this being bug, please file bug in Debian.

By the way, I do not see .xsession-errors in my home directory anymore on my jessie(Debian).

Osamu

Osamu,

when I run

$ more .xsession-errors

On Ubuntu 14.04 or Ubuntu 14.10 I get the following messages:
----------------------------------------------------------
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
-----------------------------------------------------------

I am not sure which package creates these messages but they clearly don't belong in .xsession-errors file.

Do you know which package is responsible?

On Sun, Oct 12, 2014 at 08:47:29PM -0000, Սահակ wrote:
> Osamu,
>
> when I run
>
> $ more .xsession-errors
>
> On Ubuntu 14.04 or Ubuntu 14.10 I get the following messages:
> ----------------------------------------------------------
> Script for ibus started at run_im.
> Script for auto started at run_im.
> Script for default started at run_im.
> -----------------------------------------------------------
>
> I am not sure which package creates these messages but they clearly
> don't belong in .xsession-errors file.

??? why? It record any STDERR out put from programs started in
xsession.

> Do you know which package is responsible?

im-config

This way, we can track down what program was executed in user's system
when I get bug report.

Please re-read what I wrote, too.

Regards,

Osamu

> On Oct 13, 2014, at 08:56, osamu <email address hidden> wrote:
>
>> On Sun, Oct 12, 2014 at 08:47:29PM -0000, Սահակ wrote:
>> Osamu,
>>
>> when I run
>>
>> $ more .xsession-errors
>>
>> On Ubuntu 14.04 or Ubuntu 14.10 I get the following messages:
>> ----------------------------------------------------------
>> Script for ibus started at run_im.
>> Script for auto started at run_im.
>> Script for default started at run_im.
>> -----------------------------------------------------------
>>
>> I am not sure which package creates these messages but they clearly
>> don't belong in .xsession-errors file.
>
> ??? why? It record any STDERR out put from programs started in
> xsession.
>
>> Do you know which package is responsible?
>
> im-config
>
> This way, we can track down what program was executed in user's system
> when I get bug report.
>
> Please re-read what I wrote, too.
>

I think it's better to avoid such informative messages by default but
add the possibility of enabling it. In my understanding
.session-errors should record stuff that's at least Warning priority
level and the output from im-config doesn't fit into the category
well..

Just 2 cents.

HI

On Tue, Oct 14, 2014 at 03:22:47AM -0000, Aron Xu wrote:
> I think it's better to avoid such informative messages by default but
> add the possibility of enabling it.
          ^^^^^^^^^^^^^^^^^^^^^^^^^^

Patch welcome

On Tue, Oct 14, 2014 at 03:22:47AM -0000, Aron Xu wrote:
> I think it's better to avoid such informative messages by default but
> add the possibility of enabling it.

OK, I fixed this.

Maybe, we should also discuss desktop file for Ubuntu.

Osamu

On 2014-10-15 15:32, osamu wrote:
> On Tue, Oct 14, 2014 at 03:22:47AM -0000, Aron Xu wrote:
>> I think it's better to avoid such informative messages by default but
>> add the possibility of enabling it.
>
> OK, I fixed this.

Thanks, Osamu!

> Maybe, we should also discuss desktop file for Ubuntu.

Are you referring to bug #1342677?

On Wed, Oct 15, 2014 at 01:46:59PM -0000, Gunnar Hjalmarsson wrote:
> On 2014-10-15 15:32, osamu wrote:
> > On Tue, Oct 14, 2014 at 03:22:47AM -0000, Aron Xu wrote:
> >> I think it's better to avoid such informative messages by default but
> >> add the possibility of enabling it.
> >
> > OK, I fixed this.
>
> Thanks, Osamu!
>
> > Maybe, we should also discuss desktop file for Ubuntu.
>
> Are you referring to bug #1342677?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1375089

Yes.

This bug was fixed in the package im-config - 0.27-1ubuntu1

---------------
im-config (0.27-1ubuntu1) vivid; urgency=low

  * Merge with Debian unstable, remaining Ubuntu changes:
    - debian/im-config.user-session.upstart
    - debian/rules:
      - Additional "cd $(CURDIR) ; \" in the Ubuntu specific code
      - Install upstart job script
    - debian/postinst: Additional condition to be met to edit
      80im-switch.

im-config (0.27-1) unstable; urgency=medium

  * Make STDERR output less verbose as default. LP: #1375089
  * Customize desktop file for Ubuntu. LP: #1342677
 -- Gunnar Hjalmarsson <email address hidden> Tue, 28 Oct 2014 14:11:00 +0100

Re-opening this bug, since the fix does not work as intended.

An empty shell variable returns true in a boolean context - please see patch.

This bug was fixed in the package im-config - 0.29-1ubuntu2

---------------
im-config (0.29-1ubuntu2) vivid; urgency=medium

  * Fix installation directory in rules.
 -- Aron Xu <email address hidden> Mon, 23 Mar 2015 15:01:16 +0800