--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xbmc: Working ...
- From: Vladmimir Stavrinov <vstavrinov@gmail.com>
- Date: Mon, 07 Jul 2014 18:23:41 +0400
- Message-id: <20140707142341.5596.55191.reportbug@terra.oz>
Package: xbmc
Version: 2:13.1~rc1+dfsg1-1
Severity: normal
Dear Maintainer,
The subject is what I see in the right bottom corner. And sometimes it is forever - there are no way to interrupt this "great work". Yes, I can type "x" and it stops "Working ...". But first there are no similar option for remote control, and second, it stops everything: not only xbmc hangs, but there are no way to do something else than switch to other console and kill entire session. This remind me microsoft windows in earlier times, when we should reboot if something hang.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xbmc depends on:
ii fonts-dejavu-core 2.34-1
ii fonts-roboto 1:4.3-3
ii libjs-iscroll 5.1.1+dfsg1-2
ii libjs-jquery 1.7.2+dfsg-3
ii mesa-utils 8.1.0-2+b1
ii python-imaging 2.4.0-2
pn python:any <none>
ii ttf-dejavu-core 2.34-1
ii x11-utils 7.7+1
ii xbmc-bin 2:13.1~rc1+dfsg1-1
xbmc recommends no packages.
xbmc suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- Subject: close bugs
- From: vasek.gello@gmail.com
- Date: Tue, 22 Dec 2020 12:50:10 -0800 (PST)
- Message-id: <5fe25c02.1c69fb81.c1b46.9fb3@mx.google.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Version: 2:19.0~beta2+dfsg1-2
Dear colleagues,
Preparing the release I have additionally checked this bug report.
I could reproduce it on neither sid nor buster-backports, so I am closing this bug.
Please feel free to open it again if you experience the same issue in the future releases of Kodi.
Sincerely,
Vasyl
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEoz6zRXbuWZdv2EJgilK8bCkfsoAFAl/iWSwACgkQilK8bCkf
soAFABAAhejPwAf64ZRVnR9ZaBQ3e/0A1+hl+MfNWj6IznbnTJNugAaOPfXjUUnl
gx68y1YcB6rOipX7eLyFApCoI/oQPUguzooyDcpzCRRwNf9p/e3fvEs0O+bI6j/E
JXgE9dc7kEAKZWtoU0up1wqbXRzhiT+Fg46zrOP+rYD53JO6d8raMnZ3d0TM5zEj
HQw4sGCSKA3JZCu8BbQSQoAi/VW3wGIbynD4NYHsAI6oojMWctJJP1TrcEPTf0ug
h+/+vnhUh6W87kJrWKHaIiG9p/n6XsFZPPrALHU/xxlzzt1Yky9TRYBXIbE1RLQz
vTnaHJSCVNOP4uU18iPiPvKC5OlI6C+SVX3HGVhXalDr+wYl0VaD23KyzJOfwM46
sDLu/t2q8NaGaDWEzEF3r+O7DfgJiDBsB/TLKyZbPAFDJTnr6q8+g05rS8LKirpp
lN6xU8gUz00ic9NqusolzR0WM5zrCiCoe/2pRqYFF6ZM13xWUPkq8mUzcrbJpCDS
r5t5+EQDOZ8EIpfc0ofykViACND1ICj/UvdRbGt9SaeV/Xyq6vpM4KHsJ2LYYyYU
pQ3Rdv3NX5ZeTnoDoQt5mGaGrzBvwN8p7strsALUjnx6eC9k9AMcB9IrhU+dvTyO
iVIqM7U15l0kISR5mS2NzsZPTqsfSGhy6oab6sbkzgsrYAWh3J0=
=nKzU
-----END PGP SIGNATURE-----
--- End Message ---