Bug#845450: Found the cause

2016-12-29 Thread LRN
After once again trying to make it work i finally found out why this is
happening (i kind of knew *what* was happening, but not why).

Turns out, Kodi does indeed have separate stereoscopic modes - input mode (i.e.
what kind of content the file has) and output mode (i.e. how Kodi UI, and
subtitles, should be rendered).

One is changed in the 3d-glass-options-button, and its default value can be
changed in Player/Videos section of Kodi global settings.
The other is changed separately in video settings when playing a file, and it
is absent from global settings. Instead, current file settings can be saved as
defaults for all media.

What happened to me was that, apparently, i've switched media file settings
from Auto to Side-by-Side at some point, and saved it as default for all
further files, without understanding what i was doing. This might have been
necessary due to Kodi misdetecting media stereoscopic layout, i don't know.

Anyway, this bug can be either closed as not-a-bug, or fixed with some kind of
doc-fix. One could argue that it's not good to be able to have mismatching
input/output stereoscopic settings, as this can easily degrade the picture
quality, but this feature does have legitimate uses (quality degradation
notwithstanding), and it's not up to Debian package maintainers to change that
anyway.

-- 
O< ascii ribbon - stop html email! - www.asciiribbon.org


0x6759BA74.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#845450: kodi-bin: kodi is stuck in left_right stereoscopic mode

2016-11-23 Thread LRN
Package: kodi-bin
Version: 2:17.0~beta5+dfsg1-4
Severity: normal

Dear Maintainer,

When playing stereoscopic over/under (top-bottom) videos in Kodi i've noticed
that for the last few months Kodi does not display the video contents correctly
when instructed to switch to over/under stereoscopic mode. The UI changes
correctly, the video contents does not.

How to reproduce:
* Open any video file (does not need to have stereoscopic contents) in Kodi
* Ensure that stereoscopic mode is not enabled
* Verify that UI and video look fine
* Enable Side-By-Side (left_right) stereoscopic (3D) mode
* Verify that UI is mirrored horizontally, and the video is unchanged
* Verify that stereoscopic mode menu item (a-pair-of-glasses icon->Change Mode;
available in Kodi v17.x) says "left_right"
* Enable Over/Under (top_bottom) stereoscopic (3D) mode

Actual result:
* UI is mirrored vertically, and the video is distorted (video is split
horizontally, as if in left_right mode, then both halves are positioned as
needed by top_bottom mode)
* The stereoscopic mode menu item says "left_right"

Expected result:
* UI is mirrored vertically, and the video is unchanged
* The stereoscopic mode menu item says "top_bottom"

This affects Kodi v16.x from sid and Kodi v17.x from experimental.
I've tried upstream Windows version of Kodi, it does not seem to be affected.
Can't test the upstream *nix version of Kodi, because it only comes in form of
Ubuntu packages.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (950, 'unstable'), (900, 'testing'), (800, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-rc5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kodi-bin depends on:
ii  libasound2  1.1.2-1
ii  libatomic1  6.2.1-4
ii  libavahi-client30.6.32-1
ii  libavahi-common30.6.32-1
ii  libavcodec577:3.2-2
ii  libavfilter67:3.2-2
ii  libavformat57   7:3.2-2
ii  libavutil55 7:3.2-2
ii  libbluetooth3   5.43-1
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.24-6
ii  libcap2 1:2.25-1
ii  libcdio13   0.83-4.2+b1
ii  libcrossguid0   0.0+git200150803-2
ii  libcurl3-gnutls 7.51.0-1
ii  libdbus-1-3 1.10.12-1
ii  libdrm2 2.4.73-1
ii  libegl1-mesa [libegl1-x11]  12.0.4-2
ii  libexpat1   2.2.0-1
ii  libfreetype62.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:6.2.1-4
ii  libgcrypt20 1.7.3-2
ii  libgif7 5.1.4-0.4
ii  libgl1-mesa-glx [libgl1]12.0.4-2
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  libgpg-error0   1.25-1
ii  libjpeg62-turbo 1:1.5.1-2
ii  liblcms2-2  2.7-1
ii  liblzo2-2   2.08-1.2
ii  libmariadbclient18  10.0.28-2
ii  libmicrohttpd12 0.9.51-1
ii  libpcre32:8.39-2
ii  libpcrecpp0v5   2:8.39-2
ii  libpng16-16 1.6.26-2
ii  libpostproc54   7:3.2-2
ii  libpulse0   9.0-5
ii  libpython2.72.7.12-7
ii  libsmbclient2:4.4.7+dfsg-1
ii  libsqlite3-03.15.1-1
ii  libssh-gcrypt-4 0.7.3-1
ii  libstdc++6  6.2.1-4
ii  libswresample2  7:3.2-2
ii  libswscale4 7:3.2-2
ii  libtag1v5   1.11.1-0.1
ii  libtinyxml2.6.2v5   2.6.2-4
ii  libudev1232-6
ii  libuuid12.29-1
ii  libva-x11-1 1.7.3-2
ii  libva1  1.7.3-2
ii  libx11-62:1.6.3-1
ii  libxext62:1.3.3-1
ii  libxml2 2.9.4+dfsg1-2.1
ii  libxrandr2  2:1.5.0-1
ii  libxslt1.1  1.1.29-2
ii  libyajl22.1.0-2
ii  zlib1g  1:1.2.8.dfsg-2+b3

Versions of packages kodi-bin recommends:
ii  libass5  0.13.4-1
ii  libbluray1   1:0.9.3-3
ii  libcec3  3.1.0+dfsg1-4
ii  libmodplug1  1:0.8.8.5-3
ii  libnfs8  1.11.0-2
ii  libplist31.12-3.1
ii  libvdpau11.1.1-5
ii  udisks2  2.1.7-3

kodi-bin suggests no packages.

-- no debconf information



Bug#730437: network-manager: fails to start

2013-11-28 Thread LRN
The problem is in nm_manager_new().

It calls:
singleton = (NMManager *) g_object_new (NM_TYPE_MANAGER, NULL);
to create the nmm object, which results in a call to nm_manager_init()
down the chain, which eventually leads to a nm_manager_update_state()
call, which calls:
nm_connectivity_set_online (priv-connectivity, new_state =
NM_STATE_CONNECTED_LOCAL);
However, priv-connectivity is initialized only back in
nm_manager_new() AFTER it creates the nmm object.

Possible solution:
somehow move this line:
priv-connectivity = nm_connectivity_new (connectivity_uri,
connectivity_interval, connectivity_response);
into nm_manager_init() or one of its subroutines


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



Bug#688190: ssvnc: vncviewer fails to nudge gnome screensaver in fullscreen mode

2012-09-20 Thread LRN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: ssvnc
Version: 1.0.29-2
Severity: normal

Dear Maintainer,

I use ssvnc to access my desktop, and often work in fullscreen mode for
extended periods of time (more than 10 minutes).

After pressing F9 to disable fullscreen mode (to access my laptop's Gnome
desktop again), i am presented with a locked desktop, which i have to
unlock.

My understanding is that vncviewer does not report my activity to
Gnome, Gnome
thinks that i'm AFK, fires up gnome-screensaver, which then locks my
screen -
all the while i'm working in a fullscreen VNC session, and when i
interrupt
this session, i find my screen locked.



- -- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.6.0-rc3-custom+ (SMP w/2 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 ssvnc depends on:
ii  bind9-host [host]  1:9.8.1.dfsg.P1-4.2
ii  host   1:9.8.1.dfsg.P1-4.2
ii  libc6  2.13-35
ii  libice62:1.0.8-2
ii  libjpeg8   8d-1
ii  libsm6 2:1.2.1-2
ii  libssl1.0.01.0.1c-4
ii  libx11-6   2:1.5.0-1
ii  libxaw72:1.0.10-2
ii  libxext6   2:1.3.1-2
ii  libxmu62:1.1.1-1
ii  libxpm41:3.5.10-1
ii  libxt6 1:1.1.3-1
ii  openssh-client 1:6.0p1-3
ii  openssl1.0.1c-4
ii  procps 1:3.3.3-2
ii  psmisc 22.19-1
ii  stunnel4   3:4.53-1
ii  tk 8.5.0-2
ii  xterm  278-2
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages ssvnc recommends:
ii  default-jre [java5-runtime]1:1.6-47
ii  gcj-4.4-jre [java5-runtime]4.4.5-2
ii  gcj-4.7-jre [java5-runtime]4.7.1-3
ii  gcj-jre [java5-runtime]4:4.7.1-1
ii  openjdk-6-jre [java5-runtime]  6b24-1.11.4-3

ssvnc suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQWsR+AAoJEOs4Jb6SI2CwYU8IAMxCYcEDy+94mro4IxOj3y9t
vty42T9cLqzLy7o2f6bgYT3VVclWr+ddRW/JhLXcCbKzUsXOPNI3C8ratxOZnNuY
g6UDQXgoG43AR8JW9cGyd9b7jUhq0EOSKhtxo7J2oGOKYlN9wITbT4sjJ2Juf6oL
iHctYCJDTqx6TQHfqqzIF39zEpqjWeq4iCW3vjRk31Dys2iuWT4+rrZWWeARjzcL
GYj7n3KckMiJiU8kfJLqR5UBxIG0pf794AkZF2xQBkzAtWNh6NGDgLszhtnK2D7m
E7O+fHcejywTgSVBtmEAbKU1e6koAB0pMM6FHPiygLV0rljT7wcyEzSMqZHMm0E=
=ebSr
-END PGP SIGNATURE-


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



Bug#637989: indent: apply -pls to function prototype declarations

2011-08-16 Thread LRN
Package: indent
Version: 2.2.11
Severity: normal
Tags: upstream patch

At the moment indent -pls formats a code like this:

int foo ();
int foo () { bar; }

to be roughly like this:

int foo ();
int
foo ()
{
  bar;
}

That is, function prototypes are NOT affected by -pls.
I think i have a hack that will allow this to be changed (patch is attached).
I've tested it on GNUnet source tree and haven't found any anomalies (although
it might produce ones when used on other sources that follow different
conventions, or when combined with some other settings that i didn't use).

This bug should be submitted upstream.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (1100, 'testing'), (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u indent-2.2.11/src/args.c indent-2.2.11.my/src/args.c
--- indent-2.2.11/src/args.c	2008-07-23 23:27:17 +0400
+++ indent-2.2.11.my/src/args.c	2011-08-16 14:07:30 +0400
@@ -151,6 +151,7 @@
 static int exp_cpp  = 0;
 static int exp_cs   = 0;
 static int exp_d= 0;
+static int exp_ddd  = 0;
 static int exp_bfda = 0;
 static int exp_bfde = 0;
 static int exp_di   = 0;
@@ -317,6 +318,8 @@
 {fca, PRO_BOOL,true,   ON, settings.format_comments,  exp_fca},
 {fc1, PRO_BOOL,true,   ON, settings.format_col1_comments, exp_fc1},
 {eei, PRO_BOOL,   false,   ON, settings.extra_expression_indent,  exp_eei},
+{ddd, PRO_BOOL,true,   ON, settings.diff_decls_and_defs,  exp_ddd},
+{nddd,PRO_BOOL,true,  OFF, settings.diff_decls_and_defs,  exp_ddd},
 {dj,  PRO_BOOL,   false,   ON, settings.ljust_decl,   exp_dj},
 {di,  PRO_INT,   16, ONOFF_NA, settings.decl_indent,  exp_di},
 {d,   PRO_INT,0, ONOFF_NA, settings.unindent_displace,exp_d},
@@ -436,6 +439,8 @@
 {fca, PRO_BOOL,   false,   ON, settings.format_comments,  exp_fca},
 {fc1, PRO_BOOL,   false,   ON, settings.format_col1_comments, exp_fc1},
 {eei, PRO_BOOL,   false,   ON, settings.extra_expression_indent,  exp_eei},
+{ddd, PRO_BOOL,true,   ON, settings.diff_decls_and_defs,  exp_ddd},
+{nddd,PRO_BOOL,true,  OFF, settings.diff_decls_and_defs,  exp_ddd},
 {dj,  PRO_BOOL,   false,   ON, settings.ljust_decl,   exp_dj},
 {di,  PRO_INT,2, ONOFF_NA, settings.decl_indent,  exp_di},
 {d,   PRO_INT,0, ONOFF_NA, settings.unindent_displace,exp_d},
diff -u indent-2.2.11/src/handletoken.c indent-2.2.11.my/src/handletoken.c
--- indent-2.2.11/src/handletoken.c	2009-02-15 14:20:42 +0300
+++ indent-2.2.11.my/src/handletoken.c	2011-08-16 14:18:28 +0400
@@ -1642,6 +1642,11 @@
 {
   /* what ? */
 }
+if (parser_state_tos-in_parameter_declaration_prototype)
+{
+  parser_state_tos-in_parameter_declaration_prototype = 0;
+  parser_state_tos-in_parameter_declaration = 0;
+}
 }
 
 /**
diff -u indent-2.2.11/src/indent.h indent-2.2.11.my/src/indent.h
--- indent-2.2.11/src/indent.h	2009-10-11 23:15:34 +0400
+++ indent-2.2.11.my/src/indent.h	2011-08-16 14:19:37 +0400
@@ -318,6 +318,11 @@
 int brace_indent; /*! number of spaces to indent braces from the suround if, while, etc. in -bl
* (bype_2 == 0) code */
 int expect_output_file;  /*! Means -o was specified. */
+int diff_decls_and_defs; /*! Makes indent think that function prototypes are terminated by ';',
+  * without this option indent will not be able to tell a difference between
+  * int foo (); and int foo () {}
+  * This is the default.
+  */
 } user_options_ty;
 
 extern user_options_ty settings;
@@ -430,6 +435,7 @@
* slightly different */
 int in_stmt;  /*!  set to 1 while in a stmt */
 int in_parameter_declaration;
+int in_parameter_declaration_prototype;
 int ind_level;/*!  the current indentation level in spaces */
 int ind_stmt; /*!  set to 1 if next line should have an extra