Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

2018-06-14 Thread Timo Aaltonen 
On 14.06.2018 10:00, Josh Triplett wrote:
> Package: libgl1-mesa-dri
> Version: 18.1.1-1
> Severity: important
> 
> Severity "important" because it hard-hangs the system, but not RC
> because presumably it doesn't happen on all configurations.
> 
> After upgrading all the mesa packages from 18.0.5-1 to 18.1.1-1, I can
> consistently and quickly hard-hang the system by visiting almost any
> non-trivial webpage in Firefox. The symptom is that the loading
> indicator and all other display updates will freeze, the system will
> stop responding to keystrokes (including alt-tab or ctrl-w), and the
> mouse cursor will temporarily keep functioning but stop working if I
> move it to the upper left corner to trigger the (gnome-shell) overview.
> 
> I reproduced this several times in a row (with reboots in between). I
> then downgraded the mesa packages back to 18.0.5-1, and the problem
> stopped occurring.
> 
> (Note that the information below comes from the system after downgrading
> to 18.0.5.)

that's odd, I've been running 18.1.0 on my KBL laptop (on Ubuntu though)
without any issues..

maybe file it upstream and see what happens


-- 
t

Bug#901498: FTBFS on stretch, needs newer libgpg-error

2018-06-14 Thread Daniel Baumann 
Package: gnupg2
Version: 2.2.8-1
Severity: minor

Hi,

when locally backporting gnupg2, I noticed that 2.2.8-1 now FTBFS on
stretch due to old libgpg-error. Would you mind bumping build-depends
accordingly to ease backporting?

Regards,
Daniel

Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

2018-06-14 Thread Josh Triplett 
Package: libgl1-mesa-dri
Version: 18.1.1-1
Severity: important

Severity "important" because it hard-hangs the system, but not RC
because presumably it doesn't happen on all configurations.

After upgrading all the mesa packages from 18.0.5-1 to 18.1.1-1, I can
consistently and quickly hard-hang the system by visiting almost any
non-trivial webpage in Firefox. The symptom is that the loading
indicator and all other display updates will freeze, the system will
stop responding to keystrokes (including alt-tab or ctrl-w), and the
mouse cursor will temporarily keep functioning but stop working if I
move it to the upper left corner to trigger the (gnome-shell) overview.

I reproduced this several times in a row (with reboots in between). I
then downgraded the mesa packages back to 18.0.5-1, and the problem
stopped occurring.

(Note that the information below comes from the system after downgrading
to 18.0.5.)

-- Package-specific info:
glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_SGI_make_current_read
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2)  (0x5916)
Version: 18.0.5
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, 
GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, 
GL_AMD_shader_stencil_export, GL_AMD_shader_trinary_minmax, 
GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, 
GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, 
GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, 
GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, 
GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, 
GL_ARB_blend_func_extended, GL_ARB_buffer_storage, 
GL_ARB_clear_buffer_object, GL_ARB_clear_texture,

Bug#901496: mirror listing update for mirror.aminidc.com

2018-06-14 Thread Amin IDC 
Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: mirror.aminidc.com
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Amin IDC 
Country: IR Iran, Islamic Republic of




Trace Url: http://mirror.aminidc.com/debian/project/trace/
Trace Url: http://mirror.aminidc.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.aminidc.com/debian/project/trace/mirror.aminidc.com

Bug#901136: can't remove if install fails

2018-06-14 Thread Wouter Verhelst 
On Thu, Jun 14, 2018 at 08:08:02AM +0300, kact...@gnu.org wrote:
> 
> [2018-06-14 00:32] Wouter Verhelst 
> > Hi,
> 
> Hi!
> 
> > On Wed, Jun 13, 2018 at 03:21:11AM +0300, kact...@gnu.org wrote:
> > > I never worked with NSS, but how did it happen, that useradd {in postinst}
> > > created user in a way, that userdel {in prerm} could not find?
> > 
> > That's not what happened.
> > 
> > The sreview user already existed before the sreview-common package was
> > installed, but it did not exist in /etc/passwd; instead, it existed in a
> > different location, configured through an NSS module.
> 
> Am I correct, some time ago it was created by previous version of maintainer 
> script,
> when I did not use dh-sysuser?

No.

It was created in Debian's LDAP directory.

> > The easiest way for you to test this is probably to install libnss-db,
> > change the value of ETC in /etc/default/libnss-db to some other
> > directory and cull the DBS value so it contains just passwd, then create
> > a file called "passwd" in the directory that you pointed ETC to, run
> > "make -C /var/lib/misc", and add "db" to /etc/nsswitch.conf on the
> > "passwd" line.
> > 
> > Meanwhile, I'm going to have to implement it properly and remove
> > dh_sysuser from my build-depends. Ah well.
> 
> So sad. Maybe you could suggest what should I use instead of 'useradd/userdel'
> in sysuser-helper to make dh-sysuser also work with NSS?

You generally cannot modify users from the command line (or from a
maintainer script) that are created through any NSS module that is not
libnss-compat (note: I said "unix" before, but that was obviously
wrong).

There's nothing wrong with useradd, but you should be prepared for the
possibility that the user already exists or cannot be modified.

Alternatively, you can just use adduser.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab

Bug#857679: system fails to shutdown if there is a mounted nfs share, due to it not being unmounted before network is brought down

2018-06-14 Thread Harald Dunkel 

I have the same problem. Here is the data of my host.

/proc/self/mountinfo :

20 25 0:19 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw
21 25 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:12 - proc proc rw
22 25 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs udev 
rw,size=16437880k,nr_inodes=4109470,mode=755
23 22 0:20 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
24 25 0:21 / /run rw,nosuid,noexec,relatime shared:5 - tmpfs tmpfs 
rw,size=3290532k,mode=755
25 0 259:2 / / rw,noatime shared:1 - ext4 /dev/md0p3 rw,data=ordered
26 20 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - 
securityfs securityfs rw
27 22 0:22 / /dev/shm rw,nosuid,nodev shared:4 - tmpfs tmpfs rw
28 24 0:23 / /run/lock rw,nosuid,nodev,noexec,relatime shared:6 - tmpfs tmpfs 
rw,size=5120k
29 20 0:24 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:9 - tmpfs tmpfs 
ro,mode=755
30 29 0:25 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:10 - 
cgroup cgroup 
rw,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
31 20 0:26 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:11 - pstore 
pstore rw
32 29 0:27 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:13 - cgroup cgroup rw,net_cls,net_prio
33 29 0:28 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:14 - 
cgroup cgroup rw,freezer
34 29 0:29 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:15 - 
cgroup cgroup rw,devices
35 29 0:30 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,perf_event
36 29 0:31 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:17 - cgroup cgroup rw,cpu,cpuacct
37 29 0:32 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:18 - 
cgroup cgroup rw,memory
38 29 0:33 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:19 - 
cgroup cgroup rw,blkio
39 29 0:34 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:20 - 
cgroup cgroup rw,cpuset,clone_children
40 29 0:35 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:21 - 
cgroup cgroup rw,pids
41 20 0:8 / /sys/kernel/debug rw,relatime shared:22 - debugfs debugfs rw
42 22 0:36 / /dev/hugepages rw,relatime shared:23 - hugetlbfs hugetlbfs 
rw,pagesize=2M
43 24 0:37 / /run/rpc_pipefs rw,relatime shared:24 - rpc_pipefs sunrpc rw
44 22 0:18 / /dev/mqueue rw,relatime shared:25 - mqueue mqueue rw
45 21 0:38 / /proc/sys/fs/binfmt_misc rw,relatime shared:26 - autofs systemd-1 
rw,fd=41,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=287
74 25 0:40 / /tmp rw,nosuid,nodev,relatime shared:27 - tmpfs tmpfs 
rw,size=2097152k
76 25 8:19 / /local rw,noatime shared:28 - ext4 /dev/sdb3 
rw,discard,data=ordered
78 25 259:3 / /export rw,noatime shared:29 - ext4 /dev/md0p4 rw,data=ordered
80 45 0:41 / /proc/sys/fs/binfmt_misc rw,relatime shared:30 - binfmt_misc 
binfmt_misc rw
209 25 0:44 / /data rw,noatime shared:153 - nfs4 nfs-data:/space/data 
rw,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.16.97.128,local_lock=none,addr=172.16.96.205
208 25 0:44 / /home rw,noatime shared:157 - nfs4 nfs-data:/space/home 
rw,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.16.97.128,local_lock=none,addr=172.16.96.205
210 24 0:43 / /run/user/123 rw,nosuid,nodev,relatime shared:162 - tmpfs tmpfs 
rw,size=3290528k,mode=700,uid=123,gid=133
156 24 0:42 / /run/user/6502 rw,nosuid,nodev,relatime shared:102 - tmpfs tmpfs 
rw,size=3290528k,mode=700,uid=6502,gid=100
250 20 0:47 / /sys/fs/fuse/connections rw,relatime shared:142 - fusectl fusectl 
rw


Please note the NFS mount of /home.

# host nfs-data
nfs-data.ac.example.de is an alias for nasl006.ac.example.de.
nasl006.ac.example.de has address 172.19.96.205



Here is /etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto br0
iface br0 inet static
address 172.16.97.128
netmask 255.255.240.0
gateway 172.16.96.1
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 172.16.96.124 172.16.96.123
dns-search ac.example.de. vs.example.de. public.example.de. 
dmz.example.de. example.de.

iface br0 inet6 static
address 2001:db8:30:60::180
netmask 64
gateway 2001:db8:30:60::1
privext 2


Please increase the priority of this bug report. Cutting off the
network connections can result in lost data, in case of pending NFS
writes.


Regards
Harri

Bug#901495: redis: multiple security issues in Lua scripting

2018-06-14 Thread Chris Lamb 
Package: redis
Version: 3:3.2.6-1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

>From https://github.com/antirez/redis/issues/5017:

> The Apple Security Team, together with Alibaba and myself,
> identified several security issues in the Lua script engine. The full
> report is here: 

No CVE has (yet) been assigned:

  https://github.com/antirez/redis/issues/5017#issuecomment-397038992

Version tagged >= 3:3.2.6-1 due to stretch having Lua support but
wheezy (2.8.17) does not.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

<    1   2   3