Bug#777041: xbmc: unable to disable extensive debug logging

2015-12-26 Thread Balint Reczey 
Control: tags -1 + pending - wontfix

Hi Jonathan,

On Sun, 29 Nov 2015 22:48:48 + Jonathan McDowell  wrote:
> On Sun, Nov 29, 2015 at 07:48:42PM +0100, Bálint Réczey wrote:
> > 2015-11-29 19:24 GMT+01:00 Jonathan McDowell :
> > > On Fri, Nov 06, 2015 at 10:14:55AM +0400, Bálint Réczey wrote:
> > >> > Looking at my XBMC which was started less than 2 days ago and breaking
> > >> > down the log entry types I see:
> > >> >
> > >> >   9 WARNING:
> > >> >  78 ERROR:
> > >> > 320 INFO:
> > >> > 390 NOTICE:
> > >> >7366 DEBUG:
> > >> >
> > >> > This debug output is considerable compared to the normal output. I
> > >> > understand the desire to have the debugging enabled by default to ease
> > >> > support, but the GUI configuration should be showing this is the case
> > >> > and it should be possible to turn it off.
> > >
> > >> I think the situation improved a lot with latest kodi packages. Could
> > >> you please test them?
> > >>
> > >> Debugging is not enabled in debian/rules anymore by default.
> > >
> > > I'm running XBMC on a jessie box so I'm a bit wary about updating it
> > > all; are there any plans to update the backport.debian.org packages to
> > > 15.2 final rather than 15.2-rc3?
> 
> > They are practically the same[1] thus I did not find it important, but
> > I'll update it because probably there are numerous users waiting for
> > that.  I was also waiting for feedback on bugs like this one to see if
> > I have to make additional changes before I create the backport.
> 
> > It sould be nice if you could upgrade and test the current version to
> > see if this bug is still open.
> 
> I have upgraded to 15.2~rc3+dfsg1-1~bpo8+1 and I'm still seeing loads of
> debug output, including every keypress:
> 
> 22:34:52 T:140404543895616   DEBUG: OnKey: backspace (0xf008) pressed, action 
> is Back
> 
> All visible debug options in the GUI (System -> Debugging) are disabled.
Debugging was set on by default by upstream, but I have now disabled it by 
default[1].
The next upload will contain the fix.

Thanks for reporting the issue and testing it again!

Cheers,
Balint

[1] 
http://anonscm.debian.org/cgit/pkg-multimedia/kodi.git/commit/?id=fe87a47be53c6bd9cf55b26ff4c2d073156faa6a

Bug#777041: xbmc: unable to disable extensive debug logging

2015-11-29 Thread Jonathan McDowell 
On Sun, Nov 29, 2015 at 07:48:42PM +0100, Bálint Réczey wrote:
> 2015-11-29 19:24 GMT+01:00 Jonathan McDowell :
> > On Fri, Nov 06, 2015 at 10:14:55AM +0400, Bálint Réczey wrote:
> >> > Looking at my XBMC which was started less than 2 days ago and breaking
> >> > down the log entry types I see:
> >> >
> >> >   9 WARNING:
> >> >  78 ERROR:
> >> > 320 INFO:
> >> > 390 NOTICE:
> >> >7366 DEBUG:
> >> >
> >> > This debug output is considerable compared to the normal output. I
> >> > understand the desire to have the debugging enabled by default to ease
> >> > support, but the GUI configuration should be showing this is the case
> >> > and it should be possible to turn it off.
> >
> >> I think the situation improved a lot with latest kodi packages. Could
> >> you please test them?
> >>
> >> Debugging is not enabled in debian/rules anymore by default.
> >
> > I'm running XBMC on a jessie box so I'm a bit wary about updating it
> > all; are there any plans to update the backport.debian.org packages to
> > 15.2 final rather than 15.2-rc3?

> They are practically the same[1] thus I did not find it important, but
> I'll update it because probably there are numerous users waiting for
> that.  I was also waiting for feedback on bugs like this one to see if
> I have to make additional changes before I create the backport.

> It sould be nice if you could upgrade and test the current version to
> see if this bug is still open.

I have upgraded to 15.2~rc3+dfsg1-1~bpo8+1 and I'm still seeing loads of
debug output, including every keypress:

22:34:52 T:140404543895616   DEBUG: OnKey: backspace (0xf008) pressed, action 
is Back

All visible debug options in the GUI (System -> Debugging) are disabled.

J.

-- 
101 things you can't have too much of : 44 - Fame.

Bug#777041: xbmc: unable to disable extensive debug logging

2015-11-29 Thread Bálint Réczey 
Hi Jonathan,

2015-11-29 19:24 GMT+01:00 Jonathan McDowell :
> On Fri, Nov 06, 2015 at 10:14:55AM +0400, Bálint Réczey wrote:
>> > Looking at my XBMC which was started less than 2 days ago and breaking
>> > down the log entry types I see:
>> >
>> >   9 WARNING:
>> >  78 ERROR:
>> > 320 INFO:
>> > 390 NOTICE:
>> >7366 DEBUG:
>> >
>> > This debug output is considerable compared to the normal output. I
>> > understand the desire to have the debugging enabled by default to ease
>> > support, but the GUI configuration should be showing this is the case
>> > and it should be possible to turn it off.
>
>> I think the situation improved a lot with latest kodi packages. Could
>> you please test them?
>>
>> Debugging is not enabled in debian/rules anymore by default.
>
> I'm running XBMC on a jessie box so I'm a bit wary about updating it
> all; are there any plans to update the backport.debian.org packages to
> 15.2 final rather than 15.2-rc3?
They are practically the same[1] thus I did not find it important, but
I'll update
it because probably there are numerous users waiting for that.
I was also waiting for feedback on bugs like this one to see if I have to make
additional changes before I create the backport.
It sould be nice if you could upgrade and test the current version to
see if this
bug is still open.

Cheers,
Balint

[1] 
https://anonscm.debian.org/cgit/pkg-multimedia/kodi.git/diff/?h=upstream/15.2%2bdfsg1

Bug#777041: xbmc: unable to disable extensive debug logging

2015-11-29 Thread Jonathan McDowell 
On Fri, Nov 06, 2015 at 10:14:55AM +0400, Bálint Réczey wrote:
> > Looking at my XBMC which was started less than 2 days ago and breaking
> > down the log entry types I see:
> >
> >   9 WARNING:
> >  78 ERROR:
> > 320 INFO:
> > 390 NOTICE:
> >7366 DEBUG:
> >
> > This debug output is considerable compared to the normal output. I
> > understand the desire to have the debugging enabled by default to ease
> > support, but the GUI configuration should be showing this is the case
> > and it should be possible to turn it off.

> I think the situation improved a lot with latest kodi packages. Could
> you please test them?
>
> Debugging is not enabled in debian/rules anymore by default.

I'm running XBMC on a jessie box so I'm a bit wary about updating it
all; are there any plans to update the backport.debian.org packages to
15.2 final rather than 15.2-rc3?

J.

-- 
If a program is useless, it must be documented.

Bug#777041: xbmc: unable to disable extensive debug logging

2015-11-05 Thread Bálint Réczey 
Hi Jonathan,

2015-03-02 23:10 GMT+04:00 Jonathan McDowell :
> On Mon, Mar 02, 2015 at 07:27:21PM +0100, Bálint Réczey wrote:
>> 2015-02-04 11:00 GMT+01:00 Jonathan McDowell :
>> > I'm hoping I'm just missing something here, but the Debian XBMC packages
>> > do extensive debug logging out of the box, including logging every
>> > directory scanned for updates, even when there is no change, and logging
>> > several lines each time a key is pressed on the remote e.g:
>> >
>> > 09:52:25 T:140192028579744   DEBUG: Keyboard: scancode: 0x71, sym: 0x0114, 
>> > unicode: 0x, modifier: 0x0
>> > 09:52:25 T:140192028579744   DEBUG: CAnnouncementManager - Announcement: 
>> > OnScreensaverDeactivated from xbmc
>> > 09:52:25 T:140192028579744   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, 
>> > message OnScreensaverDeactivated
>> > 09:52:25 T:140192028579744   DEBUG: OnKey: left (0xf082) pressed, screen 
>> > saver/dpms woken up
>> > 09:52:26 T:140192028579744   DEBUG: -- Window Deinit () --
>> >
>> > I have set:
>> >
>> > 
>> > 
>> > false
>> > 
>> >
>> > in ~xbmc/.xbmc/userdata/guisettings.xml and tried:
>> >
>> > -1
>> >
>> > in ~xbmc/.xbmc/userdata/advancedsettings.xml as well, but I still see
>> > this debug output. Given that my XBMC box is on all the time and this
>> > logging serves little purpose I'd like to be able to tone it down to
>> > avoid the debug output (and I don't expect it to do this out of the bug
>> > even when the GUI is saying there's no debug enabled).
>>
>> The extensive logging is enabled during the build intentionally to
>> help users in debugging issues without recompiling the package.
>> IMO there is little harm done since if you don't have problems you
>> don't have to look at the logs.
>> If you are really worried about the logs accumulating you can even set
>> up a cron job to remove it periodically.
>>
>> Please check's Kodi's wiki for hints on changing logging, but if you
>> can't find a better solution there I probably can't help either:
>> http://kodi.wiki/view/Log_file/Advanced
>
> Here are my problems with this approach:
>
>  * There is no indication in the GUI that debug is enabled. The option
>is greyed out. If debug was enabled by default but the GUI showed it
>as enabled (and it could be disabled there) that would be much more
>acceptable.
>
>  * A responsible package should be dealing with its log files in a
>better fashion. Policy 10.8 says they should be in /var/log (probably
>/var/log/xbmc/ for XBMC) and be rotated occasionally, ideally with
>logrotate.
>
>  * The logging of each and every remote keypress is a security concern
>as it means that password entry is recorded.
>
>  * It is not unreasonable to want to limit unnecessary logging output,
>especially that which "can pretty much only be deciphered by a
>developer or long time XBMC/Kodi power user"[0]
>
> Looking at my XBMC which was started less than 2 days ago and breaking
> down the log entry types I see:
>
>   9 WARNING:
>  78 ERROR:
> 320 INFO:
> 390 NOTICE:
>7366 DEBUG:
>
> This debug output is considerable compared to the normal output. I
> understand the desire to have the debugging enabled by default to ease
> support, but the GUI configuration should be showing this is the case
> and it should be possible to turn it off.
I think the situation improved a lot with latest kodi packages. Could
you please test them?
Debugging is not enabled in debian/rules anymore by default.

Cheers,
Balint

Bug#777041: xbmc: unable to disable extensive debug logging

2015-03-02 Thread Bálint Réczey 
Hi Jonathan,

Control: severity -1 wishlist
Control: tags -1 confirmed wontfix

2015-02-04 11:00 GMT+01:00 Jonathan McDowell nood...@earth.li:
 Package: xbmc
 Version: 2:13.2+dfsg1-3~bpo70+1
 Severity: normal

 I'm hoping I'm just missing something here, but the Debian XBMC packages
 do extensive debug logging out of the box, including logging every
 directory scanned for updates, even when there is no change, and logging
 several lines each time a key is pressed on the remote e.g:

 09:52:25 T:140192028579744   DEBUG: Keyboard: scancode: 0x71, sym: 0x0114, 
 unicode: 0x, modifier: 0x0
 09:52:25 T:140192028579744   DEBUG: CAnnouncementManager - Announcement: 
 OnScreensaverDeactivated from xbmc
 09:52:25 T:140192028579744   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, 
 message OnScreensaverDeactivated
 09:52:25 T:140192028579744   DEBUG: OnKey: left (0xf082) pressed, screen 
 saver/dpms woken up
 09:52:26 T:140192028579744   DEBUG: -- Window Deinit () --

 I have set:

 debug
 screenshotpath default=true/screenshotpath
 showloginfo default=truefalse/showloginfo
 /debug

 in ~xbmc/.xbmc/userdata/guisettings.xml and tried:

 loglevel hide=false-1/loglevel

 in ~xbmc/.xbmc/userdata/advancedsettings.xml as well, but I still see
 this debug output. Given that my XBMC box is on all the time and this
 logging serves little purpose I'd like to be able to tone it down to
 avoid the debug output (and I don't expect it to do this out of the bug
 even when the GUI is saying there's no debug enabled).

The extensive logging is enabled during the build intentionally to
help users in debugging issues without recompiling the package.
IMO there is little harm done since if you don't have problems you
don't have to look at the logs.
If you are really worried about the logs accumulating you can even set
up a cron job to remove it periodically.

Please check's Kodi's wiki for hints on changing logging, but if you
can't find a better solution there I probably can't help either:
http://kodi.wiki/view/Log_file/Advanced

Cheers,
Balint


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#777041: xbmc: unable to disable extensive debug logging

2015-03-02 Thread Jonathan McDowell 
On Mon, Mar 02, 2015 at 07:27:21PM +0100, Bálint Réczey wrote:
 2015-02-04 11:00 GMT+01:00 Jonathan McDowell nood...@earth.li:
  I'm hoping I'm just missing something here, but the Debian XBMC packages
  do extensive debug logging out of the box, including logging every
  directory scanned for updates, even when there is no change, and logging
  several lines each time a key is pressed on the remote e.g:
 
  09:52:25 T:140192028579744   DEBUG: Keyboard: scancode: 0x71, sym: 0x0114, 
  unicode: 0x, modifier: 0x0
  09:52:25 T:140192028579744   DEBUG: CAnnouncementManager - Announcement: 
  OnScreensaverDeactivated from xbmc
  09:52:25 T:140192028579744   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, 
  message OnScreensaverDeactivated
  09:52:25 T:140192028579744   DEBUG: OnKey: left (0xf082) pressed, screen 
  saver/dpms woken up
  09:52:26 T:140192028579744   DEBUG: -- Window Deinit () --
 
  I have set:
 
  debug
  screenshotpath default=true/screenshotpath
  showloginfo default=truefalse/showloginfo
  /debug
 
  in ~xbmc/.xbmc/userdata/guisettings.xml and tried:
 
  loglevel hide=false-1/loglevel
 
  in ~xbmc/.xbmc/userdata/advancedsettings.xml as well, but I still see
  this debug output. Given that my XBMC box is on all the time and this
  logging serves little purpose I'd like to be able to tone it down to
  avoid the debug output (and I don't expect it to do this out of the bug
  even when the GUI is saying there's no debug enabled).
 
 The extensive logging is enabled during the build intentionally to
 help users in debugging issues without recompiling the package.
 IMO there is little harm done since if you don't have problems you
 don't have to look at the logs.
 If you are really worried about the logs accumulating you can even set
 up a cron job to remove it periodically.
 
 Please check's Kodi's wiki for hints on changing logging, but if you
 can't find a better solution there I probably can't help either:
 http://kodi.wiki/view/Log_file/Advanced

Here are my problems with this approach:

 * There is no indication in the GUI that debug is enabled. The option
   is greyed out. If debug was enabled by default but the GUI showed it
   as enabled (and it could be disabled there) that would be much more
   acceptable.

 * A responsible package should be dealing with its log files in a
   better fashion. Policy 10.8 says they should be in /var/log (probably
   /var/log/xbmc/ for XBMC) and be rotated occasionally, ideally with
   logrotate.

 * The logging of each and every remote keypress is a security concern
   as it means that password entry is recorded.

 * It is not unreasonable to want to limit unnecessary logging output,
   especially that which can pretty much only be deciphered by a
   developer or long time XBMC/Kodi power user[0]

Looking at my XBMC which was started less than 2 days ago and breaking
down the log entry types I see:

  9 WARNING:
 78 ERROR:
320 INFO:
390 NOTICE:
   7366 DEBUG:

This debug output is considerable compared to the normal output. I
understand the desire to have the debugging enabled by default to ease
support, but the GUI configuration should be showing this is the case
and it should be possible to turn it off.

J.

[0] http://kodi.wiki/view/Log_file/Advanced section 5.2, DEBUG.

-- 
   Why did Kamikaze pilots wear|  .''`.  Debian GNU/Linux Developer
 helmets?  | : :' :  Happy to accept PGP signed
   | `. `'   or encrypted mail - RSA
   |   `-key on the keyservers.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#777041: xbmc: unable to disable extensive debug logging

2015-02-04 Thread Jonathan McDowell 
Package: xbmc
Version: 2:13.2+dfsg1-3~bpo70+1
Severity: normal

I'm hoping I'm just missing something here, but the Debian XBMC packages
do extensive debug logging out of the box, including logging every
directory scanned for updates, even when there is no change, and logging
several lines each time a key is pressed on the remote e.g:

09:52:25 T:140192028579744   DEBUG: Keyboard: scancode: 0x71, sym: 0x0114, 
unicode: 0x, modifier: 0x0
09:52:25 T:140192028579744   DEBUG: CAnnouncementManager - Announcement: 
OnScreensaverDeactivated from xbmc
09:52:25 T:140192028579744   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, 
message OnScreensaverDeactivated
09:52:25 T:140192028579744   DEBUG: OnKey: left (0xf082) pressed, screen 
saver/dpms woken up
09:52:26 T:140192028579744   DEBUG: -- Window Deinit () --

I have set:

debug
screenshotpath default=true/screenshotpath
showloginfo default=truefalse/showloginfo
/debug

in ~xbmc/.xbmc/userdata/guisettings.xml and tried:

loglevel hide=false-1/loglevel

in ~xbmc/.xbmc/userdata/advancedsettings.xml as well, but I still see
this debug output. Given that my XBMC box is on all the time and this
logging serves little purpose I'd like to be able to tone it down to
avoid the debug output (and I don't expect it to do this out of the bug
even when the GUI is saying there's no debug enabled).

-- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.5+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xbmc depends on:
ii  fonts-roboto 1:4.3-3~bpo70+1
ii  libjs-iscroll5.1.1+dfsg1-1~bpo70+1
ii  libjs-jquery 1.7.2+dfsg-1
ii  mesa-utils   8.0.1-2+b3
ii  python   2.7.3-4+deb7u1
ii  python-imaging   1.1.7-4+deb7u1
ii  ttf-dejavu-core  2.33-3
ii  x11-utils7.7~1
ii  xbmc-bin 2:13.2+dfsg1-3~bpo70+1

xbmc recommends no packages.

xbmc suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org