Bug#915488: initramfs-tools-core: after dist-upgrade to testing my system can't boot, need to go to recovery then init 5

2018-12-03 Thread gregory bahde
Package: initramfs-tools-core
Version: 0.132
Severity: critical
Tags: patch
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
upgrading from stretch to testing
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
edited /usr/share/initramfs-tools/hooks/lvm2
on line 29

to add 60-persistent-storage-lvm.rules

so that it goes like
"for rules in 56-lvm.rules 60-persistent-storage-lvm.rules 69-lvm-metad.rules;
do"

instead of
"
for rules in 56-lvm.rules 69-lvm-metad.rules; do
"
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (901, 'testing'), (500, 'stable-updates'), (500, 'stable'), (500, 
'oldstable'), (10, 'experimental'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools-core depends on:
ii  coreutils8.30-1
ii  cpio 2.12+dfsg-6
ii  e2fsprogs1.44.4-2
ii  klibc-utils  2.0.4-14
ii  kmod 25-2
ii  udev 239-13

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.27.2-3

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.8-4

-- debconf-show failed



Bug#915063: xen-hypervisor-4.8-amd64: xen 4.8 fails to boot

2018-11-29 Thread gregory bahde
Package: src:xen
Version: 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
I installed xen hypervisor 4.8 and rebooted to Xen, I am used to xen and run it
on servers
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
try grub kernel xen parameters (iommu )
   * What was the outcome of this action?
blackscreen at gdm3 login session
   * What outcome did you expect instead?

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



-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), 
(11, 'testing'), (10, 'experimental'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/16 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

xen-hypervisor-4.8-amd64 depends on no packages.

Versions of packages xen-hypervisor-4.8-amd64 recommends:
ii  xen-utils-4.8  4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10

xen-hypervisor-4.8-amd64 suggests no packages.

-- debconf-show failed



Bug#863652: system-config-lvm: crash on stretch, python gtk bug?

2017-05-29 Thread gregory bahde
Package: system-config-lvm
Version: 1.1.18-3
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

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


Dear sir, just discovered that sysmtem-config-lvm was crashing on my system:
It didn't occur during an operation as it crashes pretty quickly


Ready to help and provide more info.


Here is the output, running as root:


  scaled_pixbuf = self.pixbuf.scale_simple(pixmap_width, height,
gtk.gdk.INTERP_BILINEAR)
Traceback (most recent call last):
  File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 486, in
on_tree_selection_changed
self.on_best_fit(None)
  File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 555, in
on_best_fit
self.display_view.draw()
  File "/usr/share/system-config-lvm/renderer.py", line 604, in draw
self.display.draw(self.da, self.gc, (10, y_offset))
  File "/usr/share/system-config-lvm/cylinder_items.py", line 513, in draw
self.cyl.draw(pixmap, gc, (x, y))
  File "/usr/share/system-config-lvm/cylinder_items.py", line 305, in draw
CylinderItem.draw(self, dc, gc, (x, y))
  File "/usr/share/system-config-lvm/cylinder_items.py", line 120, in draw
child.draw(dc, gc, (x, y))
  File "/usr/share/system-config-lvm/cylinder_items.py", line 311, in draw
cyl_pix = self.cyl_gen.get_cyl(dc, self.get_width(), self.height)
  File "/usr/share/system-config-lvm/cylinder_items.py", line 1039, in get_cyl
pixmap.draw_pixbuf(gc, scaled_pixbuf, 0, 0, 0, 0, -1, -1)
TypeError: Gdk.Drawable.draw_pixbuf() argument 2 must be gtk.gdk.Pixbuf, not
None
The program 'system-config-lvm.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 9424 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)








-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (502, 'testing'), (500, 'testing-proposed-updates'), (500, 
'stable'), (10, 'experimental'), (10, 'unstable')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

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

Versions of packages system-config-lvm depends on:
ii  gettext0.19.8.1-2
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.3
ii  lvm2   2.02.168-2
ii  menu   2.1.47+b1
ii  python-glade2  2.24.0-5.1
ii  python-gnome2  2.28.1+dfsg-1.2
ii  python-gtk22.24.0-5.1
pn  python:any 

system-config-lvm recommends no packages.

system-config-lvm suggests no packages.

-- debconf-show failed



Bug#857450: libxcb1: many segfaults -gnome and such- related to libxcb

2017-03-11 Thread gregory bahde
Package: libxcb1
Version: libxcb.so.1.1.0
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
I don't know, it pops up randomly:
It goes like
[  826.014264] gnome-shell[3060]: segfault at ffb9 ip
7ffb33523ba3 sp 7ffc4416c5b0 error 7 in
libxcb.so.1.1.0[7ffb33516000+27000]
[  826.028665] solaar[3215]: segfault at ffb9 ip 7f54adaa1ba3
sp 7ffde885caa0 error 7 in libxcb.so.1.1.0[7f54ada94000+27000]
[  826.028994] arandr[3841]: segfault at ffb9 ip 7f4cc6861ba3
sp 7fff0663e630 error 7 in libxcb.so.1.1.0[7f4cc6854000+27000]
[  826.029578] smart-notifier[3205]: segfault at ffb9 ip
7fad6795aba3 sp 7ffe787b5c70 error 7 in
libxcb.so.1.1.0[7fad6794d000+27000]
[  826.030002] gnome-settings-[3185]: segfault at ffb9 ip
7f54e4bd9ba3 sp 7ffc46860410 error 7 in
libxcb.so.1.1.0[7f54e4bcc000+27000]
[  826.030908] nautilus-deskto[3216]: segfault at ffb9 ip
7f6e67830ba3 sp 7ffc1d48f5a0 error 7 in
libxcb.so.1.1.0[7f6e67823000+27000]
[  826.031081] python2[3212]: segfault at ffb9 ip 7f1a0cd3bba3
sp 7ffd982f3610 error 7 in libxcb.so.1.1.0[7f1a0cd2e000+27000]
[  826.031161] evolution-alarm[3202]: segfault at ffb9 ip
7eff93510ba3 sp 7fff22040a10 error 7 in
libxcb.so.1.1.0[7eff93503000+27000]
[  826.031209] qjackctl[3208]: segfault at ffb9 ip 7f951851fba3
sp 7fff453c51b0 error 7 in libxcb.so.1.1.0[7f9518512000+27000]
[  826.033558] gnome-software[3203]: segfault at ffb9 ip
7f5889e67ba3 sp 7fff023832c0 error 7 in
libxcb.so.1.1.0[7f5889e5a000+27000]
[  849.862335] show_signal_msg: 4 callbacks suppressed
[  849.862339] gnome-settings-[1748]: segfault at ffb9 ip
7f886ed92ba3 sp 7ffca61cd370 error 7 in
libxcb.so.1.1.0[7f886ed85000+27000]
[  849.876014] gnome-settings-[4164]: segfault at ffba ip
7fae3fedeba3 sp 7ffec51bc490 error 7 in
libxcb.so.1.1.0[7fae3fed1000+27000]
[  849.889686] gnome-shell[1554]: segfault at ffb9 ip
7f3369638ba3 sp 7ffc6c161510 error 7 in
libxcb.so.1.1.0[7f336962b000+27000]
[  916.162758] at-spi-bus-laun[3038]: segfault at ffba ip
7efc2f16fba3 sp 7ffe16cbd370 error 7 in
libxcb.so.1.1.0[7efc2f162000+27000]



Then if I try to restart gdm:

[ 1049.291499] gnome-shell[4356]: segfault at ffba ip
7fdf7b9a6ba3 sp 7ffc20e8b9f0 error 7 in
libxcb.so.1.1.0[7fdf7b999000+27000]
[ 1050.216066] gnome-session-c[4400]: segfault at ffba ip
7f649bacbba3 sp 7fff17039230 error 7 in
libxcb.so.1.1.0[7f649babe000+27000]
[ 1050.221303] gnome-session-c[4401]: segfault at ffba ip
7f268a0f3ba3 sp 7f071480 error 7 in
libxcb.so.1.1.0[7f268a0e6000+27000]
[ 1050.226985] gnome-session-f[4402]: segfault at ffba ip
7f1926b09ba3 sp 7ffcf9dc11d0 error 7 in
libxcb.so.1.1.0[7f1926afc000+27000]
[ 1051.588970] gnome-session-c[4434]: segfault at ffba ip
7fa80d070ba3 sp 7fff57a63870 error 7 in
libxcb.so.1.1.0[7fa80d063000+27000]
[ 1051.594360] gnome-session-c[4435]: segfault at ffba ip
7f8c1ffdfba3 sp 7ffdd56d9490 error 7 in
libxcb.so.1.1.0[7f8c1ffd2000+27000]
[ 1051.600283] gnome-session-f[4436]: segfault at ffba ip
7fecd15b9ba3 sp 7ffc9d0fd320 error 7 in
libxcb.so.1.1.0[7fecd15ac000+27000]
[ 1052.961614] gnome-session-c[4468]: segfault at ffba ip
7eff08e30ba3 sp 7ffca5e61100 error 7 in
libxcb.so.1.1.0[7eff08e23000+27000]
[ 1052.967012] gnome-session-c[4469]: segfault at ffba ip
7f71a0ffdba3 sp 7ffd3c620be0 error 7 in
libxcb.so.1.1.0[7f71a0ff+27000]
[ 1052.972834] gnome-session-f[4470]: segfault at ffba ip
7fd7e0c23ba3 sp 7ffc62acbb60 error 7 in
libxcb.so.1.1.0[7fd7e0c16000+27000]
[ 1054.318303] gnome-session-c[4501]: segfault at ffba ip
7fbfb518eba3 sp 7ffcccf92120 error 7 in
libxcb.so.1.1.0[7fbfb5181000+27000]
[ 1054.323252] gnome-session-c[4502]: segfault at ffba ip
7fa77c9cfba3 sp 7ffe566c6c90 error 7 in
libxcb.so.1.1.0[7fa77c9c2000+27000]
[ 1054.329006] gnome-session-f[4503]: segfault at ffba ip
7f6a9cd0cba3 sp 7ffdff3aa910 error 7 in
libxcb.so.1.1.0[7f6a9ccff000+27000]
[ 1055.708343] gnome-session-c[4534]: segfault at ffba ip
7ff874bc6ba3 sp 7ffe5d0e7800 error 7 in
libxcb.so.1.1.0[7ff874bb9000+27000]
[ 1055.713639] gnome-session-c[4535]: segfault at ffba ip
7eff39f78ba3 sp 7ffe98d508f0 error 7 in
libxcb.so.1.1.0[7eff39f6b000+27000]
[ 1055.719478] gnome-session-f[4536]: segfault at ffba ip
7f52214cbba3 sp 7fff2bc0ce50 error 7 in
libxcb.so.1.1.0[7f52214be000+27000]


   * What exactly did you do (or not 

Bug#854866: solaar: Solaar did not have permissions to open my receiver

2017-02-11 Thread gregory bahde
Package: solaar
Version: 0.9.2+dfsg-7
Severity: grave
Tags: ipv6
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
installing it
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
none yet though it i a matter a group permissions, i'll investigate soon

   * What was the outcome of this action?
   * What outcome did you expect instead?

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



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (101, 'testing'), (10, 'experimental'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages solaar depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  gir1.2-gtk-3.0 3.22.7-2
ii  passwd 1:4.4-3
ii  python-gi  3.22.0-2
ii  python-pyudev  0.21.0-1
pn  python:any 
ii  udev   232-15

Versions of packages solaar recommends:
ii  gir1.2-notify-0.7  0.7.7-1
ii  python-dbus1.2.4-1
ii  systemd232-15
ii  upower 0.99.4-4

Versions of packages solaar suggests:
ii  gir1.2-appindicator3-0.1  0.4.92-4
ii  solaar-gnome3 0.9.2+dfsg-7

-- debconf information:
  solaar/use_plugdev_group: false



Bug#854596: fontmatrix: uninstallable -at least under stretch, fontmatrix : Dépend: libicu52 (>= 52~m1-1~) which is a virtual package and is not provided by any available package

2017-02-08 Thread gregory . bahde
Package: fontmatrix 
Version: 0.6.0+svn20110930-1.1+b1 
Severity: grave 
Tags: upstream 
Justification: renders package unusable 

Dear Maintainer, 

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

* What led up to the situation? 
trying to install the soft 
* What exactly did you do (or not do) that was effective (or 
ineffective)? 
installed it from source -github, following the regular procedure- 
* What was the outcome of this action? 
successful but not using the package 
* What outcome did you expect instead? 
install from a package rightaway i suppose ;) 

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



-- System Information: 
Debian Release: 9.0 
APT prefers testing 
APT policy: (101, 'testing'), (10, 'experimental'), (10, 'unstable') 
Architecture: amd64 (x86_64) 
Foreign Architectures: i386 

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



Bug#854596: fontmatrix: uninstallable -at least under stretch, fontmatrix : Dépend: libicu52 (>= 52~m1-1~) which is a virtual package and is not provided by any available package

2017-02-08 Thread gregory bahde
Package: fontmatrix
Version: 0.6.0+svn20110930-1.1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

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 ***



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (101, 'testing'), (10, 'experimental'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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



Bug#819550: linux-image-4.4.0-0.bpo.1-rt-amd64: boot stall while trying 4.4 rt amd64 kernel

2016-03-30 Thread gregory bahde
Package: linux-image-4.4.0-0.bpo.1-rt-amd64
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
installing rt 4.4
   * 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?
locked at startup

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



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

Kernel: Linux 4.4.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)