Bug#798494: Removing wicd doesn't solve the problem
As Mr. Lippers-Hollman suggested, I removed wicd and installed network-manager. I also installed the 4.1.0-2-686-pae kernel. I can't connect using network-manager using any of the three kernels (3.16.0-4-686-pae, 4.1.0-1-686-pae, or 4.1.0-2-686-pae). I can connect by configuring the interface in /etc/network/interfaces and giving the command, ifup, but only while running the 3.16.0-4-686-pae kernel. In all other cases, syslog reports a timeout while attempting to associate with the access point. The following syslog entries were produced while network-manager was attempting to connect running the 3.16 kernel, but the entries are the same for the other two kernels: Sep 11 20:53:11 kitchencomp wpa_supplicant[1149]: wlan0: SME: Trying to authenticate with 00:14:6c:20:29:3c (SSID='NETGEAR' freq=2462 MHz) Sep 11 20:53:11 kitchencomp kernel: [26589.281328] wlan0: authenticate with 00:14:6c:20:29:3c Sep 11 20:53:11 kitchencomp kernel: [26589.291026] wlan0: send auth to 00:14:6c:20:29:3c (try 1/3) Sep 11 20:53:11 kitchencomp kernel: [26589.294716] wlan0: authenticated Sep 11 20:53:11 kitchencomp NetworkManager[5073]: (wlan0): supplicant interface state: scanning -> authenticating Sep 11 20:53:11 kitchencomp wpa_supplicant[1149]: wlan0: Trying to associate with 00:14:6c:20:29:3c (SSID='NETGEAR' freq=2462 MHz) Sep 11 20:53:11 kitchencomp kernel: [26589.297292] ath5k :00:0d.0 wlan0: disabling HT as WMM/QoS is not supported by the AP Sep 11 20:53:11 kitchencomp kernel: [26589.297299] ath5k :00:0d.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP Sep 11 20:53:11 kitchencomp NetworkManager[5073]: (wlan0): supplicant interface state: authenticating -> associating Sep 11 20:53:11 kitchencomp kernel: [26589.404063] wlan0: associate with 00:14:6c:20:29:3c (try 2/3) Sep 11 20:53:11 kitchencomp kernel: [26589.508038] wlan0: associate with 00:14:6c:20:29:3c (try 3/3) Sep 11 20:53:11 kitchencomp kernel: [26589.612021] wlan0: association with 00:14:6c:20:29:3c timed out Sep 11 20:53:11 kitchencomp wpa_supplicant[1149]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="NETGEAR" auth_failures=1 duration=10 reason=CONN_FAILED Sep 11 20:53:11 kitchencomp NetworkManager[5073]: (wlan0): supplicant interface state: associating -> disconnected The following syslog entries were produced after stopping network-manager, configuring wlan0 in /etc/network/interfaces, and running ifup. These entries are the same while running on the 4.1.0-1 and the 4.1.0-2 kernels: Sep 13 13:39:55 kitchencomp kernel: [ 2398.024117] wlan0: authenticate with 00:14:6c:20:29:3c Sep 13 13:39:55 kitchencomp kernel: [ 2398.033534] wlan0: send auth to 00:14:6c:20:29:3c (try 1/3) Sep 13 13:39:55 kitchencomp kernel: [ 2398.034943] wlan0: authenticated Sep 13 13:39:55 kitchencomp kernel: [ 2398.035021] ath5k :00:0d.0 wlan0: disabling HT as WMM/QoS is not supported by the AP Sep 13 13:39:55 kitchencomp kernel: [ 2398.035028] ath5k :00:0d.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP Sep 13 13:39:55 kitchencomp kernel: [ 2398.037439] wlan0: associate with 00:14:6c:20:29:3c (try 1/3) Sep 13 13:39:55 kitchencomp kernel: [ 2398.140063] wlan0: associate with 00:14:6c:20:29:3c (try 2/3) Sep 13 13:39:55 kitchencomp kernel: [ 2398.244023] wlan0: associate with 00:14:6c:20:29:3c (try 3/3) Sep 13 13:39:55 kitchencomp kernel: [ 2398.348022] wlan0: association with 00:14:6c:20:29:3c timed out However, ifup consistently connects when running the 3.16 kernel: Sep 11 21:27:00 kitchencomp kernel: [28618.793843] wlan0: authenticate with 00:14:6c:20:29:3c Sep 11 21:27:00 kitchencomp dhclient: Listening on LPF/wlan0/00:11:95:92:61:bd Sep 11 21:27:00 kitchencomp dhclient: Sending on LPF/wlan0/00:11:95:92:61:bd Sep 11 21:27:00 kitchencomp dhclient: Sending on Socket/fallback Sep 11 21:27:00 kitchencomp dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 Sep 11 21:27:00 kitchencomp kernel: [28618.800559] wlan0: send auth to 00:14:6c:20:29:3c (try 1/3) Sep 11 21:27:00 kitchencomp kernel: [28618.801956] wlan0: authenticated Sep 11 21:27:00 kitchencomp kernel: [28618.802036] ath5k :00:0d.0 wlan0: disabling HT as WMM/QoS is not supported by the AP Sep 11 21:27:00 kitchencomp kernel: [28618.802040] ath5k :00:0d.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP Sep 11 21:27:00 kitchencomp kernel: [28618.805975] wlan0: associate with 00:14:6c:20:29:3c (try 1/3) Sep 11 21:27:00 kitchencomp kernel: [28618.808262] wlan0: RX AssocResp from 00:14:6c:20:29:3c (capab=0x421 status=0 aid=1) Sep 11 21:27:00 kitchencomp kernel: [28618.808363] wlan0: associated Given that wicd, iw, iwconfig, and ifup can all connect when running the 3.16 kernel, but none can connect when running the 4.1.0-1 or 4.1.0-2 kernels, I don't see how this can be a wicd bug. However, I don't have the knowledge to figure out which package this should be reported against. If someone with
Bug#698989: libgl1-mesa-dri: glxinfo segmentation fault in nouveau_vieux_dri.so
That seems to have worked. Thanks. I can wait for this to get into the testing repository. Below is the terminal output: # LIBGL_DRIVERS_PATH=/tmp/scratchdir/usr/lib/i386-linux-gnu/dri glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, 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_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: 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_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_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 OpenGL vendor string: Nouveau OpenGL renderer string: Mesa DRI nv18 x86/MMX+/3DNow!+/SSE2 OpenGL version string: 1.2 Mesa 10.6.5 OpenGL extensions: GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_clear_buffer_object, GL_ARB_compressed_texture_pixel_storage, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_draw_buffers, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_multi_bind, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_program_interface_query, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_separate_shader_objects, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_texture_compression, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle, GL_ARB_texture_storage, GL_ARB_transpose_matrix, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_s3tc, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_KHR_context_flush_control, GL_KHR_debug, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_fog_distance, GL_NV_light_max_exponent, GL_NV_packed_depth_stencil, GL_NV_texgen_reflection, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_OES_read_format, GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays 64 GLX Visuals visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms
Bug#798494: [pkg-wpa-devel] Bug#798494: iw: Can't connect to wireless router when running 4.1 kernel
Thanks for the prompt reply, but you're not correct when you state that I didn't reproduce the issue in any way other than using wicd. In the case of the Atheros card, I stopped wicd, put the wireless interface down and back up, and then connected using the iw and iwconfig commands from the terminal (or failed to connect, in the case of the 4.1 kernel). My wireless connection is unencrypted, which is why I didn't think I needed to use wpa_supplicant. I'll try network-manager tomorrow. Regards, John Harrington On 09/09/2015 06:36 PM, Stefan Lippers-Hollmann wrote: reassign 798494 wicd thanks On 2015-09-09, John Harrington wrote: Package: iw Version: 3.17-1 Severity: important Dear Maintainer, My network manager (wicd) lost the ability to connect to my unsecured wireless router when I upgraded from the 3.16-0-4-686-pae kernel to the 4.1.0-1-686-pae kernel. It still works normally when I boot into the 3.16 kernel. iw is a command line tool to query and modify the configuration of cfg80211 based wlan cards via nl80211. To the best of my knowledge wicd still has no concept of nl80211 and still depends on the obsolete wext compatibility layer in order to speak to the kernel. Accordingly this bug can't be in iw, as iw isn't even involved in the use case you describe. Therefore, from an initial 10'000 mile bird view, the packages involved in your problem could be: - src:linux - crda/ wireless-regdb - wpasupplicant - wicd but not iw. The prime suspect would usually be the kernel upgrade, but considering that you experience problems with vastly different kernel modules (ath5k and iwlagn) suggests a more generic issue (and wlan as a whole certainly isn't broken in linux 4.1 for everyone). crda and wireless-regdb are only responsible for setting and obeying the regulatory domain settings (allowed channels, ~transmit power, and ~features). Unless you're operating your device outside of its specifications, these two packages aren't really an active component in your problem. wpasupplicant would be the next contender, but here the version didn't really change between jessie (roughly corresponding to kernel 3.16) and unstable (the difference between wpasupplicant 2.3-1+deb8u1 and 2.3-2 is tiny and doesn't affect functionality). wicd hasn't seen an uploaded since 2013, so at least no /change/ in wicd could be made responsible for your issues either - except that no change at all and using an obsolete API to talk to the kernel (wext) can be a source of problems on its own. I'm still tentatively reassigning this bug to wicd, as you apparently have only tried wicd as configuration and connection management frontend and didn't reproduce the issue any other way so far.
Bug#791603: same problem with guvcview ver. 2.0.2+debian-1
I have the same problem with guvcview 2.0.2+debian-1. Here's my shell output: $ guvcview GUVCVIEW: version 2.0.2 V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory V4L2_CORE: (UVCIOC_CTRL_MAP) Error: File exists V4L2_CORE: (UVCIOC_CTRL_MAP) Error: File exists V4L2_CORE: (UVCIOC_CTRL_MAP) Error: File exists V4L2_CORE: (UVCIOC_CTRL_MAP) Error: File exists V4L2_CORE: (UVCIOC_CTRL_MAP) Error: File exists ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.VIA8237.pcm.surround71.0:CARD=0' ALSA lib conf.c:4260:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4739:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM surround71 ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Segmentation fault I'm running Debian Testing with the 3.16.0-4-686-pae kernel, but I've had the same problem when running the 4.1 kernel.
