Bug#1038004: not fixed yet

[Vladimir Stavrinov]

The problem still exists. The reason is missing asm/orc_h ash.h and
orc_header.h files. Fortunately workaround exists:

cp -a 
/usr/src/linux-headers-6.3.0-{2,1}-common/arch/x86/include/asm/orc_header.h
cp -a /usr/src/linux-headers-6.3.0-{2,1}-common/arch/x86/include/asm/orc_hash.h

dpkg --list nvidia-tesla-470-kernel-dkms linux-{image,headers}-6.3.0-?-amd64
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----===
ii  linux-headers-6.3.0-1-amd64  6.3.7-1  amd64Header
files for Linux 6.3.0-1-amd64
ii  linux-headers-6.3.0-2-amd64  6.3.11-1 amd64Header
files for Linux 6.3.0-2-amd64
ii  linux-image-6.3.0-1-amd646.3.7-1  amd64Linux 6.3
for 64-bit PCs (signed)
ii  linux-image-6.3.0-2-amd646.3.11-1 amd64Linux 6.3
for 64-bit PCs (signed)
ii  nvidia-tesla-470-kernel-dkms 470.199.02-1 amd64NVIDIA
binary kernel module DKMS source (Tesla 470 version)

Though the regular solution should be provided.

--

Bug#845023: efibootmgr: Could not prepare Boot variable: No space left on device

[Vladimir Stavrinov]

On Sat, Nov 19, 2016 at 03:55:43PM +, Steve McIntyre wrote:

> It's quite likely not a problem with the ESP on /boot/efi, but maybe a
> problem with the variable storage space on your computer. What make

No, nothing changed there since it was working: the same hardware in
the same configuration. The problem appeared in some point of Debian
upgrade a mounth ago. This EFI setup was working without problem for
more then 2 years under continuous upgrading of Debian sid

> and model are you using?

It is Lenovo H530:

http://shop.lenovo.com/gb/en/desktops/lenovo/h-series/h530/

>   efibootmgr -c -L debian -l \EFI\debian\grubx64.efi

No difference - the same result. Moreover the very short command
emits the same error:

efibootmgr -c
Could not prepare Boot variable: No space left on device

So again: it is not about space. This is some sort of bug of
interaction with hardware.

> grub-install -v will show you exactly what commands grub is trying to
> use.

grub-install: info: executing efibootmgr -c -d /dev/sda -p 2 -w -L debian -l 
\EFI\debian\grubx64.efi.
Could not prepare Boot variable: No space left on device
Installation finished. No error reported.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Tue, Oct 20, 2015 at 11:31:05PM +0100, Luca Boccassi wrote:
 
> Could you please make sure that both your user and your DM user (sddm I
> believe?) are in the video group and try again and report the result?

Yes, this solves the problem, but it is ridiculous. 

First of all it is security issue. The "video" group is system group
that provide write access to video device. It is using not only for
nvidia. For example I am using special system user "webcam" for
streaming from my web camera to RTMP server. To do this I've added it
to video group. So normal non-system user should not be included
into this group.

Second, tell us please how do You make sure the normal user being
included into video group? For example, if You add new user with
useradd utility? Yes, You can do this with something like hook or
trigger, but this is not only way to create new user - there are
unlimited number of ways to do this. Or may be You are going notify
all sysadmins about this?

No. This is really crazy idea to provide non-system ordinary user
with write access to video device in order to provide access to glx
library. And Andreas Beckmann's post:

http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2015-October/011948.html

explains nothing about this. There are no answer to the question:
what for glx requires write access to video device for normal live
user?  This is something new in world fashion. Why only glx require
this? How do other video works without such requirements?

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Wed, Oct 21, 2015 at 05:50:22PM +0200, Andreas Beckmann wrote:

> The driver is a non-free blob. I have no clue how it works :-)

Kicks nvidia ass. Non-free blob is always headache. Will it be
sensitive for nvida if all Linux user will boycott them not buying
their hardware?

OK, but what happened recently with 0.6.x version? Do You want to
say, that ordinary user always had had write access to nvidia device?

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Wed, Oct 21, 2015 at 05:34:32PM +0100, Luca Boccassi wrote:

> default by upstream (and by udev) with 666 permissions, so world

I hate such gys. They want more: 777. They say: "give me 777 and
everything will work. They don't need any other user than root. This
is microsoft heritage in mind. No users, no task no network - this is
the best OS where everything work.

> With the upload Andreas just did (340.93-6) the video group workaround
> won't be needed, but device nodes go back to 666.

May be this is even worse solution. I have recently joked, but may be
this is true: it is better to notify about need to include user in
video group. You can do this with banner while installation or via
email after that.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Mon, Oct 19, 2015 at 10:11:45PM +0100, Luca Boccassi wrote:

> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the Nvidia driver packages or glx-alternatives?

Absolutely. This is Nvidia driver problem. Few days ago I conducted
specific experiment. After upgrading to latest version of all nvidia
and glx packages, I've downgraded only kernel module and after
reloading module the glx got working. But after rebooting system the
problem returned again. So not only kernel module is problem, but it
is main.

> Andreas, you use KDE if I'm not mistaken. Are you seeing any issues? Do

How many times again: this is not problem of KDE, plasma, kodi or any
other software using glx. This is problem of glx in nvidia driver. 

I am using xlock from very old package xlockmore-gl not included in
any of today's debian distributions. But it has two options
"-modelist allgl" and "-modelist all-allgl". First is for include glx
modes, second - to exclude ones. This is very good for testing glx,
because it explicitly points to glx as the source of problem when it
works with second option and doesn't work with the first one.

So it is certainly clear, that the source of our problems is glx
feature of nvdia driver. But the fact that You can't reproduce the
problem (if You can't, because You never mentioned this) may mean,
that problem is somehow hardware specific. In this case there are no
way to debug it as to ask us to do for You some experiments of Your
choice.

Here is my hardware:

lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 635] 
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)

If this guess is not true and the problem is not hardware specific, then You
should try number of different software using glx to reproduce the
problem.

And finally it is possible, that at some point of investigation You
will understand necessity to escalate the problem to upstream.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Mon, Oct 19, 2015 at 10:05:12PM +0100, Luca Boccassi wrote:

> In your case it looks like it certainly is. Your glx alternative is

No, it is not. I never touched setup. As I wrote before more then
once, the problem arises after upgrade, not as result of setup changing.


> configured to Mesa instead of Nvidia:
> 
> diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
> glx-diversions
> diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
> glx-diversions
> diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
> glx-diversions
> diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
> by glx-diversions

You are wrong: it is about divert and not about alternative.
 
> Please run:
>
> sudo update-alternatives --set glx /usr/lib/nvidia
> sudo dpkg-reconfigure glx-alternative-nvidia

This does not helps and can't help, because again and again: it is
not setup problem, it is upgrade result. Downgrade helps. That is
what I am doing to get it working:

dpkg -P nvidia-kernel-support
dpkg -i glx-alternative-mesa_0.5.1_amd64.deb 
glx-alternative-nvidia_0.5.1_amd64.deb glx-diversions_0.5.1_amd64.deb 
libegl1-nvidia_340.93-1_amd64.deb libgl1-nvidia-glx-i386_340.93-1_i386.deb 
libgl1-nvidia-glx_340.93-1_amd64.deb libgl1-nvidia-glx_340.93-1_i386.deb 
libgles1-nvidia_340.93-1_amd64.deb libgles2-nvidia_340.93-1_amd64.deb 
libnvidia-eglcore_340.93-1_amd64.deb libnvidia-ml1_340.93-1_amd64.deb 
nvidia-alternative_340.93-1_amd64.deb nvidia-driver-bin_340.93-1_amd64.deb 
nvidia-driver_340.93-1_amd64.deb nvidia-kernel-dkms_340.93-1_amd64.deb 
nvidia-vdpau-driver_340.93-1_amd64.deb 
xserver-xorg-video-nvidia_340.93-1_amd64.deb

And nothing else.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Tue, Oct 20, 2015 at 09:25:16AM +0300, Vladimir Stavrinov wrote:

> what I am doing to get it working:
> 
> dpkg -P nvidia-kernel-support
> dpkg -i glx-alternative-mesa_0.5.1_amd64.deb 
> glx-alternative-nvidia_0.5.1_amd64.deb glx-diversions_0.5.1_amd64.deb 
> libegl1-nvidia_340.93-1_amd64.deb libgl1-nvidia-glx-i386_340.93-1_i386.deb 
> libgl1-nvidia-glx_340.93-1_amd64.deb libgl1-nvidia-glx_340.93-1_i386.deb 
> libgles1-nvidia_340.93-1_amd64.deb libgles2-nvidia_340.93-1_amd64.deb 
> libnvidia-eglcore_340.93-1_amd64.deb libnvidia-ml1_340.93-1_amd64.deb 
> nvidia-alternative_340.93-1_amd64.deb nvidia-driver-bin_340.93-1_amd64.deb 
> nvidia-driver_340.93-1_amd64.deb nvidia-kernel-dkms_340.93-1_amd64.deb 
> nvidia-vdpau-driver_340.93-1_amd64.deb 
> xserver-xorg-video-nvidia_340.93-1_amd64.deb
> 

In reverse order or do it twice to resolve dependency issue.

> And nothing else.

Then reboot.

P.S. 0.6.92 doesn't help again.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Sun, Oct 18, 2015 at 08:43:50PM +0100, Luca Boccassi wrote:

 
> Could you please attach the output of:
> 
> reportbug --template glx-alternative-nvidia
> reportbug --template nvidia-driver

*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Vladmimir Stavrinov ' as your from address.
Getting status for glx-alternative-nvidia...
Will send report to Debian (per lsb_release).
Maintainer for glx-alternative-nvidia is 'Debian NVIDIA Maintainers 
'.
Looking up dependencies of glx-alternative-nvidia...
Getting status for related package glx-diversions...
Looking up 'depends' of related package glx-diversions...
Looking up 'recommends' of related package glx-diversions...
Getting status for related package nvidia-glx...
Getting status for related package fglrx-driver...
Looking up status of additional packages...

Rewriting subject to 'glx-alternative-nvidia: none'
Gathering additional data, this may take a while...
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Vladmimir Stavrinov 
To: Debian Bug Tracking System 
Subject: glx-alternative-nvidia: none

Package: glx-alternative-nvidia
Version: 0.6.91
Severity: wishlist

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of 

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Sun, Oct 18, 2015 at 11:03:35PM +0100, Luca Boccassi wrote:

> Nothing seems wrong in the setup.

The problem is not about setup.

> What is the exact error you get with plasma?

The problem is not about "exact error".

The problem is about GLX, that doesn't works with any software.
Errors may be differ. But segfault is common.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Sun, Oct 18, 2015 at 08:16:39PM +0200, Miguel Angel Rojas wrote:

>Vladimir is right, same issue here. Indeed, It is weird to me not so
>many people is currently reporting on it, but it is affecting a lot of

And even more weird is practice to close an issue without
confirmation from users who reported the problem, that it has been
solved.

###  Vladimir Stavrinov  ###

Bug#799948: 0.6.1 doesn't solves the problem

[Vladimir Stavrinov]

On Tue, Oct 06, 2015 at 07:38:23PM +0300, Vladimir Stavrinov wrote:

> The problem still exists. See

Again, with new version the problem don't solved as You reported.
With 0.6.91 and 340.93-5 GLX still doesn't works. See attached log.
It is not about kodi only. The problem exists for other software too:
GLX doesn't works. And as before to make it working all related
packages should be downgraded to 0.5.1 and 340.93-1 versions.

### Vladimir Stavrinov ###
## Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Sun Oct 18 12:27:57 MSK 2015
 Kodi Options: 
 Arch: x86_64
 Kernel: Linux 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14)
 Release: Debian GNU/Linux
## END SYSTEM INFO ##

### STACK TRACE #
=>  Core file: /home/vs/core (2015-10-18 12:27:57.398449307 +0300)
=
[New LWP 2592]
[New LWP 2600]
[New LWP 2602]
[New LWP 2601]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/kodi/kodi.bin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x in ?? ()
[Current thread is 1 (Thread 0x7ff3bdc2b980 (LWP 2592))]

Thread 4 (Thread 0x7ff3941db700 (LWP 2601)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:143
#1  0x7ff3b71a2e18 in pa_threaded_mainloop_wait () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x00999dac in CAESinkPULSE::AddPackets(unsigned char**, unsigned 
int, unsigned int) ()
#3  0x0097cf56 in 
ActiveAE::CActiveAESink::OutputSamples(ActiveAE::CSampleBuffer*) ()
#4  0x0097e122 in ActiveAE::CActiveAESink::StateMachine(int, 
Actor::Protocol*, Actor::Message*) ()
#5  0x0097eb57 in ActiveAE::CActiveAESink::Process() ()
#6  0x01146aff in CThread::Action() ()
#7  0x01146dc2 in CThread::staticThread(void*) ()
#8  0x7ff3bb5210a4 in start_thread (arg=0x7ff3941db700) at 
pthread_create.c:309
#9  0x7ff3b2e2306d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7ff3939da700 (LWP 2602)):
#0  0x7ff3b2e1a52d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff3b71a2831 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7ff3b7193e51 in pa_mainloop_poll () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7ff3b71944ee in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7ff3b71945a0 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7ff3b71a27c6 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7ff3ab331ff8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-7.0.so
#7  0x7ff3bb5210a4 in start_thread (arg=0x7ff3939da700) at 
pthread_create.c:309
#8  0x7ff3b2e2306d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7ff3901da700 (LWP 2600)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x0097afc7 in ActiveAE::CActiveAE::Process() ()
#2  0x01146aff in CThread::Action() ()
#3  0x01146dc2 in CThread::staticThread(void*) ()
#4  0x7ff3bb5210a4 in start_thread (arg=0x7ff3901da700) at 
pthread_create.c:309
#5  0x7ff3b2e2306d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ff3bdc2b980 (LWP 2592)):
#0  0x in ?? ()
#1  0x00746995 in CMediaSourceSettings::Clear() ()
#2  0x00c9dbb1 in CSettingsManager::OnSettingsUnloaded() ()
#3  0x00c9e843 in CSettingsManager::Unload() ()
#4  0x00ca1d9e in CSettingsManager::Clear() ()
#5  0x007312fd in CSettings::Uninitialize() ()
#6  0x0073175f in CSettings::~CSettings() ()
#7  0x7ff3b2d74bc9 in __run_exit_handlers (status=-1, listp=0x7ff3b30e05a8 
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#8  0x7ff3b2d74c15 in __GI_exit (status=) at exit.c:104
#9  0x7ff3b2d5eb4c in __libc_start_main (main=0x6ccd00 , argc=1, 
argv=0x7fffc9ed7e18, init=, fini=, 
rtld_fini=, stack_end=0x7fffc9ed7e08) at libc-start.c:321
#10 0x00716fc9 in _start ()
# END STACK TRACE ###

# LOG FILE ##

12:27:56 T:140684837435776  NOTICE: special://profile/ is mapped to: 
special://masterprofile/
12:27:56 T:140684837435776  NOTICE: 
---
12:27:56 T:140684837435776  NOTICE: Starting Kodi from Debian (15.2-RC3 Debian 
package version:15.2~rc3+dfsg1-1 Git: (unknown)). Platform: Linux x86 64-bit
12:27:56 T:140684837435776  NOTICE: Using Debug Kodi from Debian x64 build
12:27:56 T:140684837435776  NOTICE: Kodi from Debian compiled from 
15.2~rc

Bug#799948: 0.6.1 doesn't solves the problem

[Vladimir Stavrinov]

The problem still exists. See

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800938

###  Vladimir Stavrinov  ###

Bug#679714: postgres-xc: fails to install: missing dependency on postgresql server?

[Vladimir Stavrinov]

On Sun, Jul 01, 2012 at 11:57:15AM +0200, Andreas Beckmann wrote:

 One step further. So installation fails if policy-rc.d is configured to 
 forbid starting of services ...

It should be discussed what default setting should be. But in any case
it should be taken in account by postinst script.

 + sudo su - postgres-xc -c 'psql postgres -c CREATE NODE dn1 WITH
 (TYPE=datanode, PORT=15432); CREATE NODE dn2 WITH (TYPE=datanode,
 PORT=15433); select pgxc_pool_reload();'
 /var/lib/dpkg/info/postgres-xc.postinst: line 144: sudo: command not
 found

This certainly should be fixed either with dependency or by replacing sudo
with su.

I think postinst script should be rewritten in some other aspects too. So do
not hurry up to take it production and be ready to reinstall it from
scratch.

Thanks You for Your testing.


***
###  Vladimir Stavrinov
###  vstavri...@gmail.com
***




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

Bug#679714: postgres-xc: fails to install: missing dependency on postgresql server?

[Vladimir Stavrinov]

On Sun, Jul 01, 2012 at 01:39:30AM +0200, Andreas Beckmann wrote:

 + '[' '!' -S /var/run/postgresql/.s.PGSQL.5432 ']'
 + i=11
 + sleep 1
 + '[' 11 -gt 10 ']'
 + exit 1
 dpkg: error processing postgres-xc (--configure):
  subprocess installed post-installation script returned error exit status 1
 Errors were encountered while processing:
  postgres-xc
 
 Where should the socket come from?


It created when coordinator starts. Try to start/stop it with init
script and see what prevents to do so.


***
###  Vladimir Stavrinov
###  vstavri...@gmail.com
***




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

Bug#520082: openswan: reincarnation

[Vladimir Stavrinov]

Package: openswan
Version: 1:2.6.20+dfsg-4
Severity: normal



You have reproduced the same bug in the new version with new feature. Here is
patch:


--- /etc/init.d/ipsec.orig  2009-03-22 12:41:56.0 +0300
+++ /etc/init.d/ipsec   2009-03-26 20:10:16.0 +0300
@@ -123,7 +123,7 @@
 start_stop() {
# remove for: @cygwin_START@ 
# portable way for checking for root
-   if test `id -u` !=  0
+   if test  `id -u` !=  0
then
echo permission denied (must be superuser) |
logger -s -p $IPSECsyslog -t ipsec_setup 21


This is minimal changes against original version, but it is better to use $(id 
-u).


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

Versions of packages openswan depends on:
ii  bsdmainutils  6.1.10 collection of more utilities from 
ii  debconf [debconf-2.0] 1.5.26 Debian configuration management sy
ii  debianutils   2.32.2 Miscellaneous utilities specific t
ii  host  2331-9 utility for querying DNS servers
ii  iproute   20090115-1 networking and traffic control too
ii  ipsec-tools   1:0.7.1-1.3IPsec tools for Linux
ii  libc6 2.9-6  GNU C Library: Shared libraries
ii  libcurl3  7.18.2-8.1 Multi-protocol file transfer libra
ii  libgmp3c2 2:4.2.4+dfsg-2 Multiprecision arithmetic library
ii  libldap-2.4-2 2.4.15-1   OpenLDAP libraries
ii  libpam0g  1.0.1-9Pluggable Authentication Modules l
ii  openssl   0.9.8g-15  Secure Socket Layer (SSL) binary a

openswan recommends no packages.

Versions of packages openswan suggests:
ii  curl  7.18.2-8.1 Get a file from an HTTP, HTTPS or 
pn  openswan-modules-source | lin none (no description available)

-- debconf information:
  openswan/existing_x509_key_filename:
  openswan/x509_state_name:
  openswan/rsa_key_length: 2048
  openswan/restart: true
  openswan/start_level: earliest
  openswan/enable-oe: false
  openswan/existing_x509_certificate: false
  openswan/existing_x509_certificate_filename:
  openswan/create_rsa_key: true
  openswan/x509_email_address:
  openswan/x509_country_code: AT
  openswan/x509_self_signed: true
  openswan/x509_organizational_unit:
  openswan/x509_locality_name:
  openswan/x509_common_name:
  openswan/rsa_key_type: x509
  openswan/x509_organization_name:



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

Bug#439984: Acknowledgement (libpam0g: Bad item passed to pam_*_item())

[Vladimir Stavrinov]

Hi!

I didn't receive Your replies to my report for unknown reason,
but I read it on the site. So, here is my summary comments for
your and numerous related messages about last upgrade of pam
system

I am serve a lot of debian servers, but only one machine (which is
my home computer) has the problem I am reported. But at this
moment it is not accessible for me, and thus I can't give You
more info right now, but some time later. The reason caused
problem and pointed out by Soeren look like fantastic, but it
rather likely it is my case too, because I am never touch pam
configuration anywhere, but as usual edit environment.

There is some number of reports about many services needed to
restart after upgrading pam. I should add one more to this list:
it is samba too, that should be restarted. And reasonable question
is: is this list closed, or there are other daemons to restart?

And finally, rhetorical question: is it possible to catch bugs,
like this, that cause the earthquake, before upload?

-- 

*
   Vladimir Stavrinov  **
***   [EMAIL PROTECTED]   **
*



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#435663: debmirror: how many broken mirrors?

[Vladimir Stavrinov]

Package: debmirror
Followup-For: Bug #435663


This is my case too: whole mirror deleted. How many victims are there
yet? It is time to think about some kind of protection against such
incidents in the future. The traffic at least 25 Gb worth an efforts in
this directions.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#435227: linux-image-2.6.22-1-686: yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal)

[Vladimir Stavrinov]

On Mon, Jul 30, 2007 at 10:20:39AM +0200, maximilian attems wrote:

 reassign 435227 yaird
 severity 435227 critical
 stop

Thanks and sorry: I should look at yaird bug report, before
posting there. 

And I have found the source of error:

/usr/lib/yaird/perl/InputTab.pm

where this tag is not defined among others.

 
 don't use yaird, it's plain and simple like that.

The reason, I prefer yaird is that in opposite to others it
don't include into image a lot of never needed at boot time
modules.  Usually the disk controller and file system drivers
are included only. This is best politic result the small image
generated.
 

-- 

*
   Vladimir Stavrinov  **
***   [EMAIL PROTECTED]   **
*



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#435227: linux-image-2.6.22-1-686: yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal)

[Vladimir Stavrinov]

On Mon, Jul 30, 2007 at 02:57:20PM +0200, maximilian attems wrote:

 
 i have trouble to parse/understand your sentences,

Sorry

 and get MODULES=dep and send patches for even more minimal images.
 MODULES=dep is highly enhanced in lenny already.

I know about this. But.. with this setting it generate image 1.9
Mb in size, while yaird make 1.2 Mb and this is by default, no
configuration needed, and finally it is in sid. As for
initrd-tools by default with  MODULES=most it produce 5.5 Mb
image with extra modules most of which never will be used. I
don't understand what for this is doing. May be for case of
nuclear war.

-- 

*
   Vladimir Stavrinov  **
***   [EMAIL PROTECTED]   **
*


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#435227: linux-image-2.6.22-1-686: yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal)

[Vladimir Stavrinov]

On Mon, Jul 30, 2007 at 04:02:54PM +0200, maximilian attems wrote:

 
 you seem to be confused, initrd-tools is gone!

Yes, sorry, I meant initramfs-tools of course.

 initramfs-tools produces by _default_ an generic image that boots
 any box! yes this is an important commitment to our users,

What for? If initrd image generated every time the kernel
package installed or upgraded? 


-- 

*
   Vladimir Stavrinov  **
***   [EMAIL PROTECTED]   **
*


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#419843: bacula-director-mysql: wrong dependency

[Vladimir Stavrinov]

Package: bacula-director-mysql
Version: 2.0.3-3+b1
Severity: grave
Justification: renders package unusable


apt-get install bacula-director-mysql
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  bacula-director-mysql: Depends: bacula-director-common (= 2.0.3-3) but 
2.0.3-3+b1 is to be installed
E: Broken packages

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

Versions of packages bacula-director-mysql depends on:
ii  bacula-director-common2.0.3-3+b1 Network backup, recovery and verif
ii  dbconfig-common   1.8.31 common framework for packaging dat
ii  debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii  libc6 2.5-2  GNU C Library: Shared libraries
ii  libgcc1   1:4.1.1-21 GCC support library
ii  libmysqlclient15off   5.0.38-2   mysql database client library
ii  libssl0.9.8   0.9.8e-4   SSL shared libraries
ii  libstdc++64.1.1-21   The GNU Standard C++ Library v3
ii  libwrap0  7.6.dbs-13 Wietse Venema's TCP wrappers libra
ii  mysql-client  5.0.38-2   mysql database client (meta packag
ii  mysql-client-5.0 [mysql-clien 5.0.38-2   mysql database client binaries
ii  python2.4 2.4.4-3An interactive high-level object-o
ii  zlib1g1:1.2.3-13 compression library - runtime

Versions of packages bacula-director-mysql recommends:
ii  mysql-server  5.0.38-2   mysql database server (meta packag
ii  mysql-server-5.0 [mysql-serve 5.0.38-2   mysql database server binaries


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#418813: locales: dependencies are broken again

[Vladimir Stavrinov]

Package: locales
Version: 2.5-2
Followup-For: Bug #418813


Upgrade libc6 from 2.3.6.ds1-13 to 2.5-1 cause removing locales bacause
libc6 Proviedes: glibc-2.5.0-0exp1, glibc-2.5.0-0exp2, while locales
Depends: glibc-2.5-1


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages locales depends on:
ii  debconf [debconf-2.0] 1.5.13 Debian configuration management sy
pn  glibc-2.3.6.ds1-1 none (no description available)

locales recommends no packages.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#397625: libapache2-mod-php5: apache segfault

[Vladimir Stavrinov]

Package: libapache2-mod-php5
Version: 5.2.0-1
Severity: grave
Justification: renders package unusable


After upgrade child apache process segfault on every request.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-k7
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages libapache2-mod-php5 depends on:
ii  apache2- 2.2.3-3 Traditional model for Apache HTTPD
ii  apache2. 2.2.3-3 Next generation, scalable, extenda
ii  libbz2-1 1.0.3-6 high-quality block-sorting file co
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libcomer 1.39+1.40-WIP-2006.10.02+dfsg-2 common error description library
ii  libdb4.4 4.4.20-8Berkeley v4.4 Database Libraries [
ii  libkrb53 1.4.4-3 MIT Kerberos runtime libraries
ii  libmagic 4.17-4  File type determination library us
ii  libpcre3 6.7-1   Perl 5 Compatible Regular Expressi
ii  libssl0. 0.9.8c-3SSL shared libraries
ii  libxml2  2.6.27.dfsg-1   GNOME XML library
ii  mime-sup 3.37-1  MIME files 'mime.types'  'mailcap
ii  php5-com 5.2.0-1 Common files for packages built fr
ii  ucf  2.0016  Update Configuration File: preserv
ii  zlib1g   1:1.2.3-13  compression library - runtime

libapache2-mod-php5 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#384433: bacula-director-mysql: can not be started due to mysql version mismatch

[Vladimir Stavrinov]

Package: bacula-director-mysql
Version: 1.38.11-3
Severity: grave
Justification: renders package unusable


Try start after upgrade:

Starting Bacula Director: /usr/sbin/bacula-dir: relocation error:
/usr/sbin/bacula-dir: symbol SSL_load_error_strings, version
libmysqlclient_15 not defined in file libmysqlclient.so.15 with link
time reference
failed.

Two days ago I have solved this problem downgrading mysql. But now, only
one version exist. And so, all productions servers are leaving without
backup.

This is common case: time by time some of main services were removed or
can not be started due to versions mismatch after upgrade.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages bacula-director-mysql depends on:
ii  bacula-director-common   1.38.11-3   Network backup, recovery and verif
ii  dbconfig-common  1.8.20  common framework for packaging dat
ii  debconf [debconf-2.0]1.5.3   Debian configuration management sy
ii  libc62.3.6.ds1-2 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-11  GCC support library
ii  libmysqlclient15off  5.0.24-1mysql database client library
ii  libssl0.9.8  0.9.8b-2SSL shared libraries
ii  libstdc++6   4.1.1-11The GNU Standard C++ Library v3
ii  libwrap0 7.6.dbs-10  Wietse Venema's TCP wrappers libra
ii  mysql-client-5.0 [mysql-clie 5.0.24-1mysql database client binaries
ii  python2.32.3.5-15An interactive high-level object-o
ii  zlib1g   1:1.2.3-13  compression library - runtime

Versions of packages bacula-director-mysql recommends:
ii  mysql-server-5.0 [mysql-serve 5.0.24-1   mysql database server binaries

-- debconf information:
  bacula-director-mysql/mysql/admin-pass: (password omitted)
* bacula-director-mysql/db_password: (password omitted)
  bacula-director-mysql/mysql_root_password: (password omitted)
  bacula-director-mysql/mysql/app-pass: (password omitted)
  bacula-director-mysql/app-password-confirm: (password omitted)
  bacula-director-mysql/password-confirm: (password omitted)
  bacula-director-mysql/mysql/admin-user: root
  bacula-director-mysql/purge: false
  bacula-director-mysql/remove-error: abort
  bacula-director-mysql/import-oldsettings:
* bacula-director-mysql/remove_catalog_on_purge: false
* bacula-director-mysql/dbconfig-install: false
  bacula-director-mysql/db/app-user:
  bacula-director-mysql/upgrade-backup: true
  bacula-director-mysql/install-error: abort
  bacula-director-mysql/db/dbname:
  bacula-director-mysql/remote/host:
  bacula-director-mysql/upgrade-error: abort
  bacula-director-mysql/remote/port:
  bacula-director-mysql/passwords-do-not-match:
* bacula-director-mysql/db_host: localhost
  bacula-director-mysql/dbconfig-upgrade: true
  bacula-director-mysql/remote/newhost:
  bacula-director-mysql/performing_upgrade: true
  bacula-director-mysql/database-type: mysql
* bacula-director-mysql/create_tables: true
  bacula-director-mysql/mysql/method: unix socket
  bacula-director-mysql/internal/reconfiguring: false
* bacula-director-mysql/mysql_root_username: root
  bacula-director-mysql/dbconfig-reinstall: false
  bacula-director-mysql/dbconfig-remove: true
* bacula-director-mysql/db_user: bacula


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#294395: apache2-mpm-prefork: upgrade to 2.0.53-3 break down php sites

[Vladimir Stavrinov]

On Mon, Feb 14, 2005 at 05:41:16PM +0300, Vladimir Stavrinov wrote:

 broken. Downgrade to 2.0.52-3 solve this problem. With 2.0.53-2 php
 halted with error:
 
 Warning: preg_match_all: internal pcre_fullinfo() error -3 in ...

Sorry, this is mistype. The php error above come with apache
2.0.53-3 and not with 2.0.53-2 or 2.0.52-3
 

-- 

*
  Vladimir Stavrinov  ***
***  [EMAIL PROTECTED]  ***
*


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]