Bug#1086866: gnome: Brightness key combinations do not work
Package: gnome Version: 1:47+3 Severity: normal X-Debbugs-Cc: deb...@tutamail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I don't know for sure, but it looks like I've changed from stable to unstable (sid). * What exactly did you do (or not do) that was effective (or ineffective)? Press the Fn + BRIGHT_UP or the Fn + BRIGHT_DOWN key combinations * What was the outcome of this action? A brightness indicator (slider) is drawn at the bottom of the center, but the brightness of the display itself does not change. The brightness slider behaves in the Quick Access panel (where sound, network, performance mode) behaves in the same way. * What outcome did you expect instead? Changed brigtness of the display. Btw, the brigtnessctl programm does work fine. *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.11.6-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome depends on: ii avahi-daemon 0.8-13+b3 ii cups-pk-helper 0.2.6-2.1 ii desktop-base 13.0.0~pre1 ii evolution3.54.1-1 ii evolution-plugins3.54.1-1 ii file-roller 44.3-1 ii gnome-core 1:47+3 ii gnome-music 47.0-1 ii gnome-sound-recorder 43~beta-1 ii gnome-tweaks 46.1-1 ii gstreamer1.0-libav 1.24.9-1 ii gstreamer1.0-plugins-ugly1.24.9-1 ii libgsf-bin 1.14.52-1.1 ii libreoffice-calc 4:24.8.2-2 ii libreoffice-gnome4:24.8.2-2 ii libreoffice-gtk3 4:24.8.2-2 ii libreoffice-impress 4:24.8.2-2 ii libreoffice-writer 4:24.8.2-2 ii network-manager 1.50.0-1 ii rhythmbox3.4.7-2+b2 ii rhythmbox-plugin-cdrecorder 3.4.7-2+b2 ii rhythmbox-plugins3.4.7-2+b2 ii seahorse 47.0.1-1 ii shotwell 0.32.7-1 ii totem-plugins43.1-1 ii xdg-user-dirs-gtk0.11-1+b1 Versions of packages gnome recommends: ii hunspell-en-us 1:2020.12.07-3 ii hyphen-en-us2.8.8-7 ii libreoffice-help-en-us 4:24.8.2-2 ii mythes-en-us1:24.8.2-1 Versions of packages gnome suggests: pn alacarte pn firefox-esr-l10n-all | firefox-l10n-all ii gnome-games 1:47+3 pn goobox | sound-juicer ii nm-connection-editor 1.36.0-3+b1 pn polari pn webext-ublock-origin-firefox | webext-ublock-origin-chromium Versions of packages gnome-core depends on: ii adwaita-icon-theme47.0-2 ii baobab47.0-1 ii cups 2.4.10-2 ii evince46.3.1-1+b1 ii evolution-data-server 3.54.1-1 ii fonts-cantarell 0.303.1-2 ii gdm3 47.0-3 ii glib-networking 2.80.0-1 ii gnome-backgrounds 47.0-1 ii gnome-bluetooth-sendto47.1-1 ii gnome-calculator 1:47.0-2 ii gnome-calendar47.0-1 ii gnome-characters 47.0-1 ii gnome-clocks 47.0-1 ii gnome-connections 47.0-1 ii gnome-contacts47.0-1 ii gnome-control-center 1:47.1.1-2 ii gnome-disk-utility46.1-1 ii gnome-font-viewer 47.0-1 ii gnome-keyring 46.2-1 ii gnome-logs45.0-1 ii gnome-maps47.1-1 ii gnome-menus 3.36.0-1.1+b3 ii gnome-session 47.0.1-1 ii gnome-settings-daemon 47.1-2 ii gnome-shell 47.0-3 ii gnome-snapshot47.1-2 ii gnome-software47.1-1 ii gnome-sushi 46.0-2 ii gnome-system-monitor 47.0-1 ii gnome-terminal3.54.0-1 ii gnome-text-editor 47.1-1 ii gnome-user-docs 47.0-1 ii gnome-weather 47.0-1 ii gsettings-desktop-schemas 47.1-1 ii gstreamer1.0-packagekit 1.3.0-1+b1 ii gstreamer1.0-plugins-base 1.24.9-1 ii gstreamer1.0-plugins-good 1.24.9-1 ii gvfs-backends 1.56.1-1 ii gvfs-fuse 1.56.1-1 ii libatk-adaptor
Bug#1070972: epiphany-browser fails to render webpages - blank pages
Some addtional information :
Rendered page output from browser with older libraries:
+
{
"Version Information": {
"WebKit version": "WebKitGTK 2.42.5 (tarball)",
"Operating system": "Linux 6.7.12-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.7.12-1 (2024-04-24) x86_64",
"Desktop": "XFCE",
"Cairo version": "1.18.0 (build) 1.18.0 (runtime)",
"GStreamer version": "1.22.9 (build) GStreamer 1.24.4 (runtime)",
"GTK version": "4.12.5 (build) 4.12.5 (runtime)"
},
"Display Information": {
"Type": "X11",
"Screen geometry": "0,0 2560x1440",
"Screen work area": "0,31 2560x1378",
"Depth": "24",
"Bits per color component": "8",
"DPI": "96",
"DRM Device": "/dev/dri/card0",
"DRM Render Node": "/dev/dri/renderD128"
},
"API": "OpenGL (libepoxy)",
"Hardware Acceleration Information": {
"Policy": "always",
"WebGL enabled": "Yes",
"Renderer": "DMABuf (Supported buffers: Hardware, Shared Memory)",
"Native interface": "None"
},
"Hardware Acceleration Information (Render process)": {
"Platform": "GBM",
"GL_RENDERER": "NV167",
"GL_VENDOR": "Mesa",
"GL_VERSION": "OpenGL ES 3.2 Mesa 24.0.8-1",
"GL_SHADING_LANGUAGE_VERSION": "OpenGL ES GLSL ES 3.20",
"GL_EXTENSIONS": "GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_s3tc
GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc
GL_EXT_texture_format_BGRA GL_OES_compressed_ETC1_RGB8_texture
GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap
GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8
GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear
GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot
GL_OES_vertex_half_float GL_EXT_draw_instanced GL_EXT_texture_sRGB_decode
GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil
GL_EXT_texture_type_2_10_10_10_REV GL_NV_conditional_render
GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer
GL_EXT_read_format_bgra GL_NV_pack_subimage GL_NV_texture_barrier
GL_EXT_frag_depth GL_NV_fbo_color_attachments GL_OES_EGL_image_external
GL_OES_EGL_sync GL_OES_vertex_array_object GL_OES_viewport_array
GL_ANGLE_pack_reverse_row_order GL_ANGLE_texture_compression_dxt3
GL_ANGLE_texture_compression_dxt5 GL_EXT_occlusion_query_boolean
GL_EXT_robustness GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers
GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil
GL_APPLE_sync GL_EXT_draw_buffers GL_EXT_instanced_arrays
GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness
GL_KHR_texture_compression_astc_ldr GL_NV_generate_mipmap_sRGB
GL_NV_pixel_buffer_object GL_OES_depth_texture_cube_map
GL_OES_required_internalformat GL_OES_surfaceless_context
GL_EXT_color_buffer_float GL_EXT_debug_label GL_EXT_sRGB_write_control
GL_EXT_separate_shader_objects GL_EXT_shader_group_vote
GL_EXT_shader_implicit_conversions GL_EXT_shader_integer_mix
GL_EXT_tessellation_point_size GL_EXT_tessellation_shader
GL_ANDROID_extension_pack_es31a GL_EXT_base_instance
GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_copy_image
GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_gpu_shader5
GL_EXT_polygon_offset_clamp GL_EXT_primitive_bounding_box GL_EXT_render_snorm
GL_EXT_shader_io_blocks GL_EXT_texture_border_clamp GL_EXT_texture_buffer
GL_EXT_texture_cube_map_array GL_EXT_texture_norm16 GL_EXT_texture_view
GL_KHR_blend_equation_advanced GL_KHR_context_flush_control
GL_KHR_robust_buffer_access_behavior GL_NV_image_formats
GL_NV_shader_noperspective_interpolation GL_OES_copy_image
GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_gpu_shader5
GL_OES_primitive_bounding_box GL_OES_sample_shading GL_OES_sample_variables
GL_OES_shader_io_blocks GL_OES_shader_multisample_interpolation
GL_OES_tessellation_point_size GL_OES_tessellation_shader
GL_OES_texture_border_clamp GL_OES_texture_buffer GL_OES_texture_cube_map_array
GL_OES_texture_stencil8 GL_OES_texture_storage_multisample_2d_array
GL_OES_texture_view GL_EXT_blend_func_extended GL_EXT_buffer_storage
GL_EXT_float_blend GL_EXT_geometry_point_size GL_EXT_geometry_shader
GL_EXT_texture_filter_minmax GL_EXT_texture_sRGB_R8 GL_KHR_no_error
GL_KHR_texture_compression_astc_sliced_3d GL_NV_conservative_raster
GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap_triangles
GL_NV_sample_locations GL_NV_viewport_array2 GL_NV_viewport_swizzle
GL_OES_EGL_image_external_essl3 GL_OES_geometry_point_size
GL_OES_geometry_shader GL_OES_shader_image_atomic GL_EXT_clear_texture
GL_EXT_clip_cull_distance GL_EXT_disjoint_timer_query
GL_EXT_texture_compression_s3tc_srgb GL
Bug#1057843: (no subject)
Would an fsck even be able to recognize corruption, if metadata were unaffected? Without file checksumming, can it discern?
Bug#1055200: g++-multilib: bullseye & bookworm currently has amd64 support for this package, add support for aarch64 (64-bit ARM)
Subject: g++-multilib: bullseye & bookworm currently has amd64 support for this package, add support for aarch64 (64-bit ARM) Package: g++-multilib X-Debbugs-Cc: jahway-bug-repo...@proton.me Severity: wishlist Dear Maintainer, * What led up to the situation? Requiring the ability to compile particular * software requiring the g++-multilib library to have support for the * aarch64 architecture. This package currently does have amd64 support in * Bullsye & Bookworm, as seen here: * https://packages.debian.org/bookworm/g++-multilib * What exactly did you do (or not do) that was effective (or ineffective)? Tried to install g++-multilib on aarch64, * but support does not exist for that architecture. * What was the outcome of this action? Compilation of software on the * aarch64 architecture requiring this package failed. * What outcome did you expect instead? Compilation of software on the * aarch64 architecture to be successful as there would be support for the * aarch64 (64-bit ARM) architecture. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-21-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1055199: gcc-multilib: bullseye & bookworm currently has amd64 support for this package, add support for aarch64 (64-bit ARM)
Subject: gcc-multilib: bullseye & bookworm currently has amd64 support for this package, add support for aarch64 (64-bit ARM) Package: gcc-multilib X-Debbugs-Cc: jahway-bug-repo...@proton.me Severity: wishlist Dear Maintainer, * What led up to the situation? Requiring the ability to compile particular * software requiring the gcc-multilib library to have support for the * aarch64 architecture. This package currently does have amd64 support in * Bullsye & Bookworm, as seen here: * https://packages.debian.org/bookworm/gcc-multilib * What exactly did you do (or not do) that was effective (or ineffective)? Tried to install gcc-multilib on aarch64, * but support does not exist for that architecture. * What was the outcome of this action? Compilation of software on the * aarch64 architecture requiring this package failed. * What outcome did you expect instead? Compilation of software on the * aarch64 architecture to be successful as there would be support for the * aarch64 (64-bit ARM) architecture. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-21-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1033146: gcc-multilib: make it available on arm64 architecture (known as aarch64)
Subject: gcc-multilib: make it available on arm64 architecture (known as aarch64) Package: gcc-multilib X-Debbugs-Cc: jahway-bug-repo...@proton.me Severity: wishlist Dear Maintainer, * What led up to the situation? Unable to compile certain * software without gcc-multilib library * What exactly did you do (or not do) that was effective (or ineffective)? Attempted to install gcc-multilib on arm64 * and it was not available * What was the outcome of this action? Complation of software * requiring this package failed * What outcome did you expect instead? Able to install this * package on arm64 architecture and then complation of software * requiring this package would be successful -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-21-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1033145: g++-multilib: make it available on arm64 architecture (known as aarch64)
Subject: g++-multilib: make it available on arm64 architecture (known as aarch64) Package: g++-multilib X-Debbugs-Cc: jahway-bug-repo...@proton.me Severity: wishlist Dear Maintainer, * What led up to the situation? Unable to compile certain * software without g++-multilib library * What exactly did you do (or not do) that was effective (or ineffective)? Attempted to install g++-multilib on arm64 * and it was not available * What was the outcome of this action? Complation of software * requiring this package failed * What outcome did you expect instead? Able to install this * package on arm64 architecture and then complation of software * requiring this package would be successful -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-21-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1028439: Unable to run X server since 22.3.1-1 upgrade
22.3.3-1 works here! But the upstream bug is unanswered still: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007. And there's another guy who did the same to no avail. It's not fixed for everyone. If we want to fix it for all, why not just revert it globally now, until the cause has been found? Who knows how long that'll take. The laptop I can personally test on is rather average. (intel UHD630, some unused nv card, nouveau is blacklisted for energy savings, and the busses removed via udev) If someone has an idea how to debug this that does not eat all day, I'd help possibly diff to find out why it works here, and not for him. Side note: I received 2 mails, one triggered directly by you, another from being subscribed to the bug. The latter fails DKIM. If this is unintended, we might want to tell the postmaster. January 18, 2023 10:25 AM, "Fabio Pedretti" wrote: > Can you check with 22.3.3-1 (now in testing) or 23.0.0~rc1-1 (in > experimental) if the issue is fixed or still not?
Bug#1028439:
As this is still open and breaking many computers: Here is one more hand to confirm. Would you mind explaining what an 's.d.o downgrade' entails? I used the snapshot archive and pinned the offender, then used aptitude and skipped through solutions until I found an acceptable one. (apt wants to kill all of X!). That is a pretty convoluted and unreliable process. 'dontbreakdebian' also says to never mess around like that. There is no official SOP as far as I'm aware. The process on Fedora given here https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007 seems a lot more straightforward. I understand this is 'testing' - but Debian testing > Arch regular and many people even consider sid to be usable everyday (see 'siduction'). Can we please revert this package instantly while we wait for an upstream fix? Testing is so darn stable usually, many 'normal' people use it in prod. This is a very severe bug in my book, right next to that kernel one a few months ago killing screens. Unless you're rather deep into Debian, you're never going to find the workaround, and likely just move on.
Bug#1023279: Segfault on startup; stack overflow involving libwx
On Sat, Nov 05, 2022 at 01:47:25PM +0100, Andreas Metzler wrote: > It is WX related, problably missing EGL support in glew. > > It worked my in own tests. I realize now that was because I have this > setting in ~/.config/hugin.conf: > [GLPreviewFrame] > [...] > isShown=0 > > (i.e. The OpenGL Preview window does not autoopen). I then need two > klicks to actually open it (the first try fails) but apart from that > hugin works. > > Does this workaround also work at your system? Afraid not! It was already set to zero in my ~/.hugin, and changing it to zero in ~/.config/hugin.conf had no effect, other than it getting changed back to 1 again... o_O Thanks, -MD -- - Michael Deegan Hugaholic https://www.deegan.id.au/ Jung, zr jbeel? --
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
Is there an easy way to unbrick a system affected by the issue? such as a kernel-line option or a configuration file in /etc? I don't see how I can set a GLIBC_TUNABLES environment variable for the whole system. I was trying during my testing to set such option globally somehow, but failed, though maybe some method for this exists. As it stands I only see two possibilities of unbricking a system, both assuming you can access the partition externally from some bootable system: 1. Downgrade the affected libc6 package to a version before the one causing issues (either chroot and dpkg, or just extract and physically replace the files), after booting apt-mark hold libc6 to prevent faulty update from being installed until the issue is fixed 2. Or install intel-microcode package, assuming the microcode update adds the missing instructions in particular case, basically coincidentally fixing this issue (the updated CPU microcode is loaded on every bootup)
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
Now that we understood the bug, I actually find strange that the microcode update is fixing this, it looks like that the BMI2 instructions support has been added in a microcode update. Would it be possible to give the output of /proc/cpuinfo with and without the microcode update applied? The /proc/cpuinfo without microcode update is already attached somewhere above in the bug report, the new one after update is as follows: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz stepping: 3 microcode : 0x28 cpu MHz : 2400.000 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 smep bmi2 erms invpcid xsaveopt dtherm arat pln pts md_clear flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips: 4788.76 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: Please note that "avx2" is once again missing due to the kernel masking flag from before that I once again forgot to remove before rebooting, and sorry for confusion it might cause -- that flag would normally be there. Running a quick diff against old procinfo reveals that "flags" has the following new entries now: tsc_deadline_timer ssbd ibrs ibpb stibp bmi1 bmi2 md_clear flush_l1d > it looks like that the BMI2 > instructions support has been added in a microcode update As such it does appear that indeed this is the case.
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
I can confirm updating the microcode by installing the intel-microcode package and rebooting does indeed mitigate this issue. An LXC container that was previously bricked due to update now starts and seems to behave fully normally. [0.00] microcode: microcode updated early to revision 0x28, date = 2019-11-12 But as microcode update needs to be loaded every time on boot (unless I presumably updated the UEFI), while it technically solves my problem on this installation, the concern of people with the same family of processors and outdated microcode running into this issue and having no idea why any Linux does not want to boot anymore still probably remains... (is there even any easy way to load updated microcode while installing Debian? I can most certainly bet its ISO does not include those due to non-free constraints)
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
Hello, sorry for delayed response, I've managed to collect and analyze a few coredump files with valid symbols (I installed libc6-dbg and dpkg-dev, and pointed gdb at Debian's debuginfod server, also used apt-get source to get the sources for libc6). It seems there are at least 3-4 distinct places it crashes at, two places at memchr-avx2.S, one at strlen-avx2.S, and potentially one at syscall-template.S, although that last one may be just some kind of kill signal redirect. Pasting all below: Core was generated by `apt'. Program terminated with signal SIGILL, Illegal instruction. #0 __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:400 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/memchr-avx2.S. 400 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or directory. (gdb) ### Core was generated by `dpkg'. Program terminated with signal SIGILL, Illegal instruction. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:514 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/strlen-avx2.S. 514 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) ### Core was generated by `/usr/bin/perl /usr/sbin/adduser'. Program terminated with signal SIGILL, Illegal instruction. #0 __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:135 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/memchr-avx2.S. 135 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or directory. (gdb) ### Core was generated by `useradd'. Program terminated with signal SIGILL, Illegal instruction. #0 __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:135 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/memchr-avx2.S. 135 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or directory. (gdb) ### Core was generated by `passwd'. Program terminated with signal SIGILL, Illegal instruction. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:514 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/strlen-avx2.S. 514 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) ### Core was generated by `bash'. Program terminated with signal SIGILL, Illegal instruction. #0 0x7f2006faf087 in kill () at ../sysdeps/unix/syscall-template.S:120 Download failed: Invalid argument. Continuing without source file ./signal/../sysdeps/unix/syscall-template.S. 120 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) ### Core was generated by `su'. Program terminated with signal SIGILL, Illegal instruction. #0 __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:135 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/memchr-avx2.S. 135 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or directory. (gdb) ### It does seem in case of this SIGILL there's no additional stack trace, also the path containing ".." seems to cause the source code resolution to fail, but still the debug symbols seem to show the file source and line, so it should hopefully help see what exactly fails. I'm yet to try rebooting with microcode package installed though (I'll soon check it and update on whether it helps, but even if it does, one without bootable system first won't get a chance to install it; I'm a bit curious how these changes did trigger this, given all these years it didn't happen to occur before)
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
81b7f918 error:0 in libc.so.6[7fc5f7234000+16e000] kernel: [67322.502174] traps: bash[435709] trap invalid opcode ip:7f24abbad422 sp:7ffe428004f8 error:0 in libc.so.6[7f24aba7d000+16e000] kernel: [67339.606742] traps: passwd[436152] trap invalid opcode ip:7f4f047ce422 sp:7fff59b0f618 error:0 in libc.so.6[7f4f0469e000+16e000] kernel: [67433.720656] traps: adduser[437285] trap invalid opcode ip:7f0e09f602b7 sp:7fff697e8f98 error:0 in libc-2.31.so[7f0e09e28000+15a000] kernel: [67714.117441] traps: bash[439504] trap invalid opcode ip:7f96d3a5c0c4 sp:7ffd554b71a8 error:0 in libc.so.6[7f96d392c000+154000] Note that this time around they come from different libc compilations: - +15a000 one is from Debian Stable (debian:bullseye-20220912-slim docker image) - +16e000 one is from Debian Sid (debian:sid-slim docker image) - +2ce2000 is bun.js, unrelated program that seems to have libc6 statically compiled - +154000 is from Fedora for a good measure (fedora:rawhide docker image) So this "+" number being the same in case of same distinct libc builds does suggest heavily that it is simply relative instruction offset in the .so itself. I might be wrong though, I also had no idea where to get debug symbols from, and gdb didn't seem to be willing to print any useful information either... Do you think I should setup another LXC container and upgrade the libc6 using this env var workaround and then try running some program under gdb itself with this variable cleared? I've never actually used gdb debugger, but surely a simple debugging up to a crash couldn't be that hard... > The changes that are in this stable release have been (or at least were > supposed to, given the bug you reported) in testing/sid for a few > months. Are you able to do a test with debian sid, for instance in > docker? Yes, same story apparently. Btw, I tested similar way in latest Fedora, with exact same outcome, so in the end the issue seems not isolated to Debian, but libc6 and this particular set of patches that eventually has found its way to Debian Stable. # docker run -it --rm debian:sid-slim bash # echo $? 132 ^ Interestingly, apt is one program that does work on sid, while not working on stable. Looking at this changelog...: https://tracker.debian.org/news/1358014/accepted-glibc-231-13deb11u4-source-into-proposed-updates-stable-new-proposed-updates/ ... is there perhaps some way these changes could be applied one by one to pinpoint which one is causing issues that way? This machine, in case it matters, is a Lenovo G510 laptop. There is some update available for the BIOS, but it requires booting up Windows to perform it. Should I attempt that? I found some ancient thread on some forum that mentioned BIOS update fixes some issues with "freezes" on
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
Package: libc6 Version: 2.31-13+deb11u4 Severity: critical Dear Maintainer, After an upgrade to version +deb11u4 on my system running Haswell (4th gen Intel Core) CPU, most of the programs including bash or dpkg are immediately crashing with SIGILL. The problem seems to be caused/ related to AVX2 and changes made to some functions utilizing this instruction set. I don't know much about Debian bug reporting, so forgive me any mistakes I've made. The issue is on both host, LXC and Docker. I have described more on this link: https://github.com/debuerreotype/docker-debian-artifacts/issues/175 where I also linked my coredump from example program and described stuff more thoroughly. Coredump link directly just in case: https://github.com/debuerreotype/docker-debian-artifacts/files/9569748/core.bash.10.2663c40e671041e6b40c882a70b83c3f.1480736.166318582400.zip Also log lines from kernel: kernel: [834669.721253] traps: dpkg[1455373] trap invalid opcode ip:7fa39701951d sp:7ffc4ad26e58 error:0 in libc-2.31.so[7fa396edd000+15a000] kernel: [834669.732958] traps: dpkg[1455374] trap invalid opcode ip:7f529ca9551d sp:7fffb6f0a238 error:0 in libc-2.31.so[7f529c959000+15a000] kernel: [834669.840128] traps: dpkg[1455375] trap invalid opcode ip:7f1874cc951d sp:7fffc2c2f5d8 error:0 in libc-2.31.so[7f1874b8d000+15a000] kernel: [834669.907918] traps: dpkg[1455378] trap invalid opcode ip:7f3b4f8d851d sp:7fff3ec970f8 error:0 in libc-2.31.so[7f3b4f79c000+15a000] kernel: [834712.152139] traps: passwd[1455693] trap invalid opcode ip:7fefee4b52b7 sp:7cb506b8 error:0 in libc-2.31.so[7fefee37d000+15a000] Not sure what exactly might be causing the issue, but if these changes aren't pulled, potentially anyone with this or similar CPU as me will upgrade and end up with bricked system. I will proceed to try using `clearcpuid=293` kernel flag myself, but consider how many distros depend on Debian, live CDs etc, with people unable to figure out why their system became useless, unable to trace the source, and blaming it just on Linux... I'm filling this bug report from my downgraded host system to the previous libc6 version. * What led up to the situation? apt upgrade... * What exactly did you do (or not do) that was effective (or ineffective)? downgrade to +deb11u3 * What was the outcome of this action? everything works on the older version * What outcome did you expect instead? -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.39-1-pve (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6 depends on: ii libcrypt1 1:4.4.18-4 ii libgcc-s1 10.2.1-6 Versions of packages libc6 recommends: ii libidn2-0 2.3.0-5 pn libnss-nis pn libnss-nisplus Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.77 pn glibc-doc ii libc-l10n 2.31-13+deb11u3 ii locales2.31-13+deb11u3 -- debconf information: glibc/disable-screensaver: glibc/restart-services: glibc/kernel-not-supported: glibc/kernel-too-old: libraries/restart-without-asking: false glibc/restart-failed: glibc/upgrade: true
Bug#1006700: squidguard crashes with an error 4, segfault at libc-2.31.so
Package: squidguard Version: 1.6.0-2 Severity: normal X-Debbugs-Cc: fernando.alves.ra...@gmail.com 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: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/8 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages squidguard depends on: ii debconf [debconf-2.0] 1.5.77 ii libc6 2.31-13+deb11u2 ii libdb5.3 5.3.28+dfsg1-0.8 ii libldap-2.4-2 2.4.57+dfsg-3 Versions of packages squidguard recommends: ii liburi-perl 5.08-1 ii libwww-perl 6.52-1 ii squid4.13-10 Versions of packages squidguard suggests: pn ldap-utils pn squidguard-doc -- debconf information: squidguard/dbreload: true Best regards,
Bug#1001875: closed by Andrei POPESCU (Re: Bug#1001875: gammy: Adapt Gammy so that a user can control color temperature, control brightness, and avoid eye damage.)
Hello Andrei: True, the package is not from Debian, but the purpose of me filing a bug report is to generate an RFP so that the package can be adapted by Debian. Adapting the package by Debian is the first step in moving things forward. So far I haven't found any issues, and the package is hosted on Github. Its relatively knew so bugs will inevitably be discovered. The package is available for both Arch, and Fedora users. It should be added to Debian as well. Its the best package I have seen for adjusting color temperature. Previously folks in the Debian channel said this should be submitted as a bug so that someone can pick it up for consideration, and adaption. Randal South On 12/18/21 12:54 AM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the gammy package: #1001875: gammy: Adapt Gammy so that a user can control color temperature, control brightness, and avoid eye damage. It has been closed by Andrei POPESCU . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Andrei POPESCU by replying to this email.
Bug#995976: atari800: No sound or intermittent sound on HDMI
Package: atari800 Version: 4.2.0-4 Severity: important X-Debbugs-Cc: mcluo...@grr.la Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Switching pulse audio output to hdmi instead of sound card audio out * What exactly did you do (or not do) that was effective (or ineffective)? I'm using nvidia quadro K4000 with DP to HDMI cable * What was the outcome of this action? No sound or intermittent sound on HDMI/DisplayPort * What outcome did you expect instead? Sound working on HDMI/DP *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/3 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages atari800 depends on: ii libc62.32-4 ii libedit2 3.1-20210910-1 ii libpng16-16 1.6.37-3 ii libsdl1.2debian 1.2.15+dfsg2-6 ii zlib1g 1:1.2.11.dfsg-2 atari800 recommends no packages. atari800 suggests no packages. -- no debconf information
Bug#991930: ifenslave: ifstate command does not exists
Package: ifenslave
Version: 2.12
Problem while trying to bring up bond0 or any bonding interface.
ifup[933]: No iface stanza found for master bond0
The root cause is ifenslave shipped with a script, referring to ifstate command
which is not present.
Script:/etc/network/if-pre-up.d/ifenslave
...
setup_slave_device() {
# Require the bond master to have an iface stanza
if ! ifstate -l "$IF_BOND_MASTER" 2>/dev/null ; then
echo "No iface stanza found for master $IF_BOND_MASTER" >&2
exit 1
fi
...
To fix switched to ip command that achieve the same goal
...
setup_slave_device() {
# Require the bond master to have an iface stanza
if ! ip link show dev "$IF_BOND_MASTER" 2>/dev/null; then
echo "No iface stanza found for master $IF_BOND_MASTER" >&2
exit 1
fi
...
Debian 11.0 (5.10.0-8-amd64 #1 SMP Debian 5.10.46-3 (2021-07-28) x86_64
GNU/Linux)
Reference:
https://blog.rtsp.us/debian-11-bullseye-bonding-problem-9d8d8866117e
Bug#984907: Debian Installer 10.8.0 will not Write to Disk with 2021 HP Notebook 17"
Package: Debian stable installer Version: 10.8.0 Severity: Critical Report submitted on behalf of from #xfce Freenode Network. Svartoyg reports that Debian installer 10.8.0 would not write file systems to disk if an EFI partition was installed first. His report consists of -notebook with 17''-display and Ryzen5-CPU. had problems with EFI and IOMMU https://forums.linuxmint.com/viewtopic.php?t=302902 This problems with the installer not writing file system to disk have been observed also with the Dell XPS 15 7590, and other newer systems.
Bug#984905: Partitions/File System Will Not Write to Disk with EFI Disk Installed First
Package: Debian stable installer Version: 10.7.0, and 10.8.0 Severity: Critical Hard drive was formated as GPT. Installer will not write to disk after setting up file system/partitions if an EFI partition is created first. Error message indicates "Can't write to disk". Once the EFI partition is removed then the installer will write to disk. This presents a problem to people wishing to dual boot with EFI partitions on a GPT formatted drive. Hardware that this occurred on is a Dell XPS 15 7590. This laptop came out in late 2019. One of the key benefits of a GPT formatted partition is being able to install windows in any order -- first or last. But that won't be possible on this laptop because Linux has problems with EFI if installed first. No test was done to see if a problem would occur if the EFI was installed last.
Bug#982919: mate-panel: Memory leak. Memory use steadily grows until OOM trips
Package: mate-panel Version: 1.20.5-1 Severity: important Dear Maintainer, Memory leak in mate-panel_1.20.5-1_i386 * What led up to the situation? Normal desktop usage leading to hanging desktop processes and a crash * What exactly did you do (or not do) that was effective (or ineffective)? HUPing the process causes a reload of the process, clearing its excessive memory usage. Attempting to update mate-panel from the Buster back-ports and proposed-updates repositories resulted in a 'mate-panel is already the newest version (1.20.5-1).' message. * What was the outcome of this action? After HUPing, resetting memory usage, the process resumes gobbling memory. HUPing the process also resets the placement of all Task Bar icons to their chronological order, not the order they have been manually rearranged or moved to. * What outcome did you expect instead? Normal mate-panel memory usage. An earlier bug report on this issue #966292 was closed six months ago on 12 Aug 2020 with the note: "fixed in the latest version of mate-panel, which is due to be installed in the Debian FTP archive" But this fix does not yet appear to be available to the Buster release as it is not in proposed-updates or back-ports repositories. -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-11-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-panel depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo-gobject21.16.0-4+deb10u1 ii libcairo21.16.0-4+deb10u1 ii libdbus-1-3 1.12.20-0+deb10u1 ii libdbus-glib-1-2 0.110-4 ii libdconf10.30.1-2 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libice6 2:1.0.9-2 ii libmate-desktop-2-17 1.20.4-2 ii libmate-menu21.20.2-1 ii libmate-panel-applet-4-1 1.20.5-1 ii libmateweather1 1.20.2-1 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii librda0 0.0.5-1 ii librsvg2-2 2.44.10-2.1 ii libsm6 2:1.2.3-1 ii libstartup-notification0 0.12-6 ii libwnck-3-0 3.30.0-2 ii libx11-6 2:1.6.7-1+deb10u1 ii libxau6 1:1.0.8-1+b2 ii libxrandr2 2:1.5.1-1 ii mate-desktop 1.20.4-2 ii mate-menus 1.20.2-1 ii mate-panel-common1.20.5-1 ii mate-polkit 1.20.2-1 ii menu-xdg 0.6 mate-panel recommends no packages. mate-panel suggests no packages. -- no debconf information
Bug#887035: cron: Logging to STDOUT when in foreground mode
For the use case of containerized environments BusyBox already provides a cron applet with custom logging capabilities: busybox crond -f -L /dev/stdout
Bug#922214: bug #922214 regarding libpng12-0_1.2.50 - grave
Dear Maintainer I have two machines, one with this bug, and one without. #922214 I've tried a few things including dpkg-repack and a rebuild from source. The only thing that works is an install of the version 1.2.49-3 and manual linking to the newer code. The difference in the two machines may be that my /usr directory is on a separate partition. Hence this: lrwxrwxrwx 1 root root 7 Oct 14 15:40 lib -> usr/lib drwxr-xr-x 12 root root 4096 Jan 29 2020 usr Regards Richard
Bug#902413: Breaks systemd-analyze verify
This raises a warning in `systemd-analyze verify` too. Please consider backporting https://github.com/fail2ban/fail2ban/commit/d5a5efcd5af272372153e86436d7c8cde2ddf66d. This should fix the issues all together.
Bug#910362: duplicate of #902413
This is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902413
Bug#946826: duplicate of #910362
This is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910362
Bug#949729: Gimp: cannot find libgegl files and fails to open
Package: gimp2.0 Version: gimp_2.10.12-1_amd64.deb I am running Debian|testing one or more recent upgrades caused gimp to fail to open. The cause seems to be an incompatibility in the installation of libgegl-common /quote libgegl-common : Conflicts: libgegl-0.4-0 (<= 1:0.4.0-dmo1) but 0.4.16-2 is to be installed /unquote this seems to have fixed it apt-get remove --purge gimp libgegl-0.4-0 libgegl-common apt-get install gimp xsane HTH Richard A Lough
Bug#935881: Additional information on pgadmin3 usability
Dear Maintainer, re: pgadmin3 I am running Debian Testing and postgresql ver 12.1 on an amd machine I forward this as an update to bug #935881 because there is no real fix for this bug. The pgadmin site says that pgadmin3 is no longer supported. It would appear that migration to pgAdmin4 is their preferred solution. The situation is now somewhat critial for Debian|Testing because of the current upgrade of postgresql to version 12.1 This causes an error message : column ad.adsrc does not exist Much of the functionality of pgadmin3 is lost. It is no longer possible to access tables in pgadmin3 because of this bug. Presently two solutions are available, to either build the package (pgadmin4) from source code, or revert to version 11 pf postgresql. May I suggest that this bug be elevated to grave. HTH Richard A Lough apt list --installed | grep postgresql WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libreoffice-sdbc-postgresql/testing,now 1:6.3.4-2 amd64 [installed,automatic] postgresql-11/testing,now 11.6-2~sid1 amd64 [installed] postgresql-12/testing,now 12.1-2 amd64 [installed,automatic] postgresql-client-11/testing,now 11.6-2~sid1 amd64 [installed] postgresql-client-12/testing,now 12.1-2 amd64 [installed,automatic] postgresql-client-common/testing,now 210 all [installed,automatic] postgresql-common/testing,now 210 all [installed,automatic] postgresql/testing,now 12+210 all [installed]
Bug#946620: bug#38574: closed (Re: diff called 'GNU')
Your bug report #38574: Bug#946620: diff called 'GNU' which was filed against the diffutils package, has been closed. The explanation is attached below, along with your original report. If you require more details, please reply to 38...@debbugs.gnu.org. -- 38574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38574 GNU Bug Tracking System Contact help-debb...@gnu.org with problems --- Begin Message --- Re https://bugs.gnu.org/38574. Thank you for the report. I've fixed it with the attached: diff-nroff.diff Description: Binary data --- End Message --- --- Begin Message --- X-Debbugs-Cc: bug-diffut...@gnu.org Package: diffutils Version: 1:3.7-3 File: /usr/share/man/man1/diff.1.gz Severity: important $ COLUMNS=50 man diff | head GNU(1)User Commands GNU(1) << Say DIFF(1) NAME GNU diff - compare files line by line SYNOPSIS diff [OPTION]... FILES DESCRIPTION Compare FILES line by line. $ COLUMNS=50 man diff | tail -n 11 The full documentation for GNU is main‐ << Say diff tained as a Texinfo manual. If the info and GNU programs are properly installed at your site, the command info GNU << Say diff should give you access to the complete manual. diffutils 3.7 December 2018 GNU(1) << Say DIFF(1) In fact this bug affects the diff3 etc. man pages too. --- End Message ---
Bug#946870: nemo: default application is hidden for executables
Package: nemo Version: 3.8.5-1+b1 Severity: normal Dear Maintainer, [Problem description] The default application associated with a file is hidden, if the file is set with the execute permission. As a result, the user cannot open an executable file in the default associated application from a context menu (also including "Open with" submenu). [Steps to reproduce] 1. Go to Nemo preferences. 2. Go to the "Behavior" tab. 3. Select "Run executable text files when they are opened" radio button in the "Executable Text Files" group. 4. Close the preferences window. 5. Create an empty file, named "test.txt". 6. Right click on the file to open the context menu. 7. The default application associated with the file is shown on the top of the context menu 8. Select "Open with" item in the menu. 9. The submenu lists alternative applications associated with the file. 10. Make the file executable. 11. Right click on the file to open the context menu. 12. The context menu doesn't contain the option to open the file in the preferred application (which is right, because the file is executed by default). 13. Click "Open with" item in the menu to open list of associated applications. 14. The "Open with" submenu contains list of alternative associations, but doesn't contain the preferred application. [Observed behavior] Usually, files are opened in the default associated application on double-click. The default application is also shown as the topmost item in the context menu at right mouse click. Alternative applications are shown in the "Open with" submenu in the context menu. When the file is set with the execute permission, instead of being opened in the default application, the file gets executed. The topmost item in the context menu corresponds the default action, executing the file too. That's all right. Though, the "Open with" submenu still contains alternative associated applications, but doesn't contain the prefferred one. As a result, the user cannot easily open an executable file in the preferred application. [Expected behavior] "Open with" submenu shall cotain the preferred associated application at the top of the list either for absolutely all files or at minimum only for executable files. [Workaround] To open an executable file in the preferred associated application follow these steps: 1. Right click on the file to open the context menu. 2. Click "Open with" in the context menu. 3. Select "other application..." item. 4. The "Open with" window opens with the preferred application being already selected. 5. Press enter or "OK" button. This cannot be considered as a solution, because openning file in the preferred application requires more steps, then openning the file in an alternative associated application. Cheers. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU:ru (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nemo depends on: ii cinnamon-desktop-data 3.8.1-2 ii desktop-file-utils 0.23-4 ii gsettings-desktop-schemas 3.28.1-1 ii gvfs 1.38.1-5 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libcinnamon-desktop4 3.8.1-2 ii libexempi8 2.5.0-2 ii libexif12 0.6.21-5.1 ii libgail-3-0 3.24.5-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libglib2.0-data 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libnemo-extension1 3.8.5-1+b1 ii libnotify4 0.7.7-4 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libselinux1 2.8-1+b1 ii libx11-6 2:1.6.7-1 ii libxapp1 1.2.2-1 ii libxml2 2.9.4+dfsg1-7+b3 ii nemo-data 3.8.5-1 ii shared-mime-info 1.10-1 Versions of packages nemo recommends: ii cinnamon-l10n 3.8.2-1 ii gvfs-backends 1.38.1-5 ii gvfs-fuse 1.38.1-5 ii librsvg2-common 2.44.10-2.1 ii nemo-fileroller 3.8.0-2 Versions of packages nemo suggests: ii eog 3.28.4-2+b1 ii evince [pdf-viewer] 3.30.2-3 ii totem 3.30.0-4 ii xdg-user-dirs 0.17-2
Bug#946620: bug#38574: Acknowledgement (Bug#946620: diff called 'GNU')
Thank you for filing a new bug report with debbugs.gnu.org. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to bug-diffut...@gnu.org (after having been given a bug report number, if it did not have one). Your message has been sent to the package maintainer(s): bug-diffut...@gnu.org If you wish to submit further information on this problem, please send it to 38...@debbugs.gnu.org. Please do not send mail to help-debb...@gnu.org unless you wish to report a problem with the Bug-tracking system. -- 38574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38574 GNU Bug Tracking System Contact help-debb...@gnu.org with problems
Bug#945069: thunderbird: when I open thunderbird a giant screen appears with code that does not leave visibility to use it.
Package: thunderbird Version: 1:68.2.2-1~deb10u1 Severity: important 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: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thunderbird depends on: ii debianutils 4.8.6.1 ii fontconfig2.13.1-2 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libevent-2.1-62.1.8-stable-4 ii libffi6 3.2.1-9 ii libfontconfig12.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-02.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-03.24.5-1 ii libgtk2.0-0 2.24.32-3 ii libjsoncpp1 1.7.4-3 ii libpango-1.0-01.42.4-7~deb10u1 ii libstartup-notification0 0.12-6 ii libstdc++68.3.0-6 ii libvpx5 1.7.0-3 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb-shm0 1.13.1-2 ii libxcb1 1.13.1-2 ii libxext6 2:1.3.3-1+b2 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii psmisc23.2-1 ii x11-utils 7.7+4 ii zlib1g1:1.2.11.dfsg-1 Versions of packages thunderbird recommends: ii hunspell-ar [hunspell-dictionary]3.2-1.1 ii hunspell-be [hunspell-dictionary]0.53-3 ii hunspell-bg [hunspell-dictionary]1:6.2.0-1 ii hunspell-bn [hunspell-dictionary]1:6.2.0-1 ii hunspell-bs [hunspell-dictionary]1:6.2.0-1 ii hunspell-ca [hunspell-dictionary]3.0.3+repack1-1 ii hunspell-cs [hunspell-dictionary]1:6.2.0-1 ii hunspell-de-at [hunspell-dictionary] 20161207-7 ii hunspell-de-ch [hunspell-dictionary] 20161207-7 ii hunspell-de-de [hunspell-dictionary] 20161207-7 ii hunspell-en-gb [hunspell-dictionary] 1:6.2.0-1 ii hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1 ii hunspell-eu [hunspell-dictionary]0.5.20151110-4 ii hunspell-fr-classical [hunspell-dictionary] 1:6.3-2 ii hunspell-gl [hunspell-dictionary]1:6.2.0-1 ii hunspell-gu [hunspell-dictionary]1:6.2.0-1 ii hunspell-hi [hunspell-dictionary]1:6.2.0-1 ii hunspell-hr [hunspell-dictionary]1:6.2.0-1 ii hunspell-hu [hunspell-dictionary]1:6.2.0-1 ii hunspell-is [hunspell-dictionary]1:6.2.0-1 ii hunspell-it [hunspell-dictionary]1:6.2.0-1 ii hunspell-kk [myspell-dictionary] 1.1-2 ii hunspell-kmr [hunspell-dictionary] 1:6.2.0-1 ii hunspell-ko [hunspell-dictionary]0.7.1-1 ii hunspell-lt [hunspell-dictionary]1:6.2.0-1 ii hunspell-lv [hunspell-dictionary]1.3.0-5 ii hunspell-ne [hunspell-dictionary]1:6.2.0-1 ii hunspell-pl [hunspell-dictionary]1:6.2.0-1 ii hunspell-pt-br [hunspell-dictionary] 1:6.2.0-1 ii hunspell-pt-pt [hunspell-dictionary] 1:6.2.0-1 ii hunspell-ro [hunspell-dictionary]1:6.2.0-1 ii hunspell-ru [hunspell-dictionary]1:6.2.0-1 ii hunspell-se [hunspell-dictionary]1.0~beta6.20081222-1.2 ii hunspell-si [hunspell-dictionary]1:6.2.0-1 ii hunspell-sl [hunspell-dictionary]1:6.2.0-1 ii hunspell-sr [hunspell-dictionary]1:6.2.0-1 ii hunspell-sv [hunspell-dictionary]1:6.2.0-1 ii hunspell-te [hunspell-dictionary]1:6.2.0-1 ii hunspell-th [hunspell-dictionary]1:6.2.0-1 ii hunspell-vi [hunspell-dictionary]1:6.2.0-1 ii lightning1:68.2.2-1~deb10u1 ii myspell-da [myspell-dictionary] 1.6.36-11 ii myspell-eo [myspell-dictionary] 2.1.2000.02.25-57 ii myspell-es [myspell-dictionary] 1.11-15 ii myspell-et [myspell-dictionary] 1:20030606-30 ii myspell-fa [myspell-dictionary] 0.20070816-3.1 ii myspell-ga
Bug#933908: bitcoind: symbol lookup error: bitcoind: undefined symbol: _ZN7leveldb4port5Mutex4LockEv
Package: bitcoind Version: 0.18.0~dfsg-1 Severity: important Dear Maintainer, after apt upgrade this week, bitcoin-qt does not start anymore. It fails with both of this errors message: bitcoind: symbol lookup error: bitcoind: undefined symbol: _ZN7leveldb4port5Mutex4LockEv bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: _ZN7leveldb4port5Mutex6UnlockEv Also reported by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933311 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.5 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bitcoin-qt depends on: ii libboost-chrono1.67.0 1.67.0-13 ii libboost-filesystem1.67.0 1.67.0-13 ii libboost-system1.67.0 1.67.0-13 ii libboost-thread1.67.0 1.67.0-13 ii libc6 2.28-10 ii libdb5.3++ 5.3.28+dfsg1-0.6 ii libevent-2.1-6 2.1.8-stable-4 ii libevent-pthreads-2.1-62.1.8-stable-4 ii libgcc11:9.1.0-10 ii libleveldb1d 1.22-3 ii libminiupnpc17 2.1-1+b1 ii libprotobuf17 3.6.1.3-2 ii libqrencode4 4.0.2-1 ii libqt5core5a 5.11.3+dfsg1-2 ii libqt5dbus55.11.3+dfsg1-2 ii libqt5gui5 5.11.3+dfsg1-2 ii libqt5network5 5.11.3+dfsg1-2 ii libqt5widgets5 5.11.3+dfsg1-2 ii libsecp256k1-0 0.1~20170810-2 ii libssl1.1 1.1.1c-1 ii libstdc++6 9.1.0-10 ii libunivalue0 1.0.4-2 ii libzmq54.3.2-1 bitcoin-qt recommends no packages. bitcoin-qt suggests no packages. -- no debconf information
Bug#933543: (no subject)
Sorry, used reportbug for the first time... Misprint the email.
Bug#910343: Please restore sodomized-sheep.cow
I also noticed that at least sodomized-sheep.cow had been removed in the latest update, breaking a login script on my system. Please restore the previous cows. Thanks!
Bug#906261: less version 520 has a regression with -F, impacts e.g. git
Package: less Version: 487-0.1+b1 Severity: important Tags: upstream This is not a bug in any current Debian package, but an FYI about an upstream regression. As of version 520 the following test-case will wait a full 5 seconds before printing "hello": (echo "hello"; sleep 5; echo "bye bye") | less -F Before that it would print "hello" immediately, and then "bye bye" 5 seconds later. See this report & discussion on the git mailing list: https://public-inbox.org/git/87k1orqpxj@evledraar.gmail.com/ Linus posted a patch that works for me to solve this, but the upstream maintainer hasn't commented: https://public-inbox.org/git/ca+55afxjusvhhwqgthgilr537bghkd-lecxvv8kzbtmmco1...@mail.gmail.com/
Bug#887667: socnetv - commas cause crashes
Package: socnetv Version: 2.1-1.1 Severity: important Dear Maintainer, I had written a perl application to produce a database table of linked organisations by extracting details from a book. My preferred way of producing the network graph id to produce a pajek.net file from the postgresql table of linked names. There are roughly 278 tuples in the table and slightly fewer nodes. I opened socnetv and selected pajek for import. When I clicked on 'OK', socnetv segfaulted. This is a consistent behaviour caued by one particular data field: 'Bureau of Alcohol, Tobacco, & Firearms' Altering the field to: 'Bureau of Alcohol and Tobacco and Firearms' allows the loading to proceed as it should. Initially I thought it was the & (ampersand) but it still crashed. The commas cause crashes. -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages socnetv depends on: pn libc6 pn libgcc1 pn libgl1-mesa-glx | libgl1 pn libqt5core5a pn libqt5gui5 pn libqt5network5 pn libqt5printsupport5 pn libqt5widgets5 pn libqt5xml5 pn libstdc++6 socnetv recommends no packages. socnetv suggests no packages. -- no debconf information
Bug#881976: [php-memcached] Must be split into php7.0-memcached and php7.1-memcached
Package: php-memcached Version: 3.0.1+2.2.0-1 Severity: normal --- Please enter the report below this line. --- Unusable in testing with php7.1 so must be split or add files for both version. --- System information. --- Architecture: Kernel: Linux 4.9.0-4-amd64 Debian Release: 9.1 999 stable deb.debian.org 950 stretch-backports deb.debian.org 900 testing deb.debian.org 800 unstable deb.debian.org 700 experimental deb.debian.org 500 stretch packagecloud.io --- Package information. --- Depends (Version) | Installed -+-=== php-igbinary | 2.0.5-1 php-msgpack | 2.0.2+0.5.7-2 ucf | 3.0036 php-common (>= 1:7.0+33~) | 1:49 phpapi-20151012 | libc6 (>= 2.14) | libmemcached11 | libmemcachedutil2 | libsasl2-2 | zlib1g (>= 1:1.1.4) | Package's Recommends field is empty. Package's Suggests field is empty.
Bug#881975: [php-xdebug] xdebug 2.5.5.-3 in testing is for php7.0 but in testing php7.1 already
Package: php-xdebug Version: 2.5.5-3 Severity: normal --- Please enter the report below this line. --- Must be split to php7.0-xdebug and php7.1-xdebug as many other php packages or as some packages include files in both dir /usr/lib/php/20151012 and /usr/lib/php/20160303 --- System information. --- Architecture: Kernel: Linux 4.9.0-4-amd64 Debian Release: 9.1 999 stable deb.debian.org 950 stretch-backports deb.debian.org 900 testing deb.debian.org 800 unstable deb.debian.org 700 experimental deb.debian.org 500 stretch packagecloud.io --- Package information. --- Depends (Version) | Installed ==-+-=== ucf | 3.0036 php-common (>= 1:7.0+33~) | 1:49 phpapi-20151012 | libc6 (>= 2.14) | Package's Recommends field is empty. Package's Suggests field is empty.
Bug#256588: anacron: Error opening /etc/anacrontab: no such file or directory
Followup-For: Bug #256588 Package: anacron Dear Maintainer, It looked like my machine hadn't run anacron for many months, and for some undetermined reason, it wasn't reported. After some checks, I found in syslog : anacron: Error opening /etc/anacrontab: no such file or directory When I checked, the message was accurate. My first attempt was to ask apt-get to reinstall, in fact, I tried that before I found the cause in syslog. But the reinstall didn't paste a copy of anacrontab into /etc. I see that as a bug, which is why I'm filing this. I don't know why anacrontab got deleted. I had several attempts at recovering this machine from a bungled shutdown and restart, so many reasons are possible. While verifying cause and effect for this, I find that systemctl is now recognising the problem, systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● anacron.service loaded failed failed Run anacron jobs ... more messages I think that on a reinstall of anacron, it should at least check whether /etc/anacrontab is there on the system, and report an error, or warning, if not. I've just noticed that a bunch of other anacron-related files are missing (see below) and I will hold off on fixing those until after I do some backups. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages anacron depends on: pn debianutils pn init-system-helpers pn libc6 pn lsb-base Versions of packages anacron recommends: pn cron | cron-daemon pn rsyslog | system-log-daemon Versions of packages anacron suggests: pn default-mta | mail-transport-agent pn powermgmt-base -- Configuration Files: /etc/anacrontab [Errno 2] No such file or directory: '/etc/anacrontab' /etc/apm/event.d/anacron [Errno 2] No such file or directory: '/etc/apm/event.d/anacron' /etc/cron.daily/0anacron [Errno 2] No such file or directory: '/etc/cron.daily/0anacron' /etc/cron.monthly/0anacron [Errno 2] No such file or directory: '/etc/cron.monthly/0anacron' /etc/cron.weekly/0anacron [Errno 2] No such file or directory: '/etc/cron.weekly/0anacron' /etc/default/anacron [Errno 2] No such file or directory: '/etc/default/anacron' /etc/init.d/anacron [Errno 2] No such file or directory: '/etc/init.d/anacron' /etc/init/anacron.conf [Errno 2] No such file or directory: '/etc/init/anacron.conf' -- no debconf information
Bug#877289: pulseaudio: core-util.c failed to acquire high-priority scheduling
Package: pulseaudio Version: 10.0-1+deb9u1 Severity: normal Dear Maintainer, I upgraded from jessie to stretch and find that the "stable" system is a lot less stable than before, I'll get to systemd eventually, but I had to deal with minor issues like pulseaudio taking about 20 minutes to start, and other problems reported in the logs. Systemctl reports other failures I have to resolve, but pulseaudio is the start. After searching for solutions on the internet, I ran $ pulseaudio - with this line in the output (among others) core-util.c failed to acquire high-priority scheduling The full message is this : $ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us. I: [pulseaudio] core-util.c: Failed to acquire high-priority scheduling: Input/output error I: [pulseaudio] main.c: This is PulseAudio 10.0 D: [pulseaudio] main.c: Compilation host: x86_64-pc-linux-gnu D: [pulseaudio] main.c: Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/pulseaudio-ZMrhzG/pulseaudio-10.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -fdiagnostics-color=auto D: [pulseaudio] main.c: Running on host: Linux x86_64 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) D: [pulseaudio] main.c: Found 4 CPUs. I: [pulseaudio] main.c: Page size is 4096 bytes D: [pulseaudio] main.c: Compiled with Valgrind support: no D: [pulseaudio] main.c: Running in valgrind mode: no D: [pulseaudio] main.c: Running in VM: no D: [pulseaudio] main.c: Optimized build: yes D: [pulseaudio] main.c: FASTPATH defined, only fast path asserts disabled. I: [pulseaudio] main.c: Machine ID is . I: [pulseaudio] main.c: Using runtime directory . I: [pulseaudio] main.c: Using state directory . I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-10.0/modules. I: [pulseaudio] main.c: Running in system mode: no E: [pulseaudio] pid.c: Daemon already running. E: [pulseaudio] main.c: pa_pid_file_create() failed. Taking advice, I added the following to /etc/security/limits.conf @audio - rtprio 99 @audio - nice-20 @audio - memlock 400 @pulse-rt - rtprio 99 @pulse-rt - nice-15 I now get this after a reboot: $ pulseaudio - D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us. D: [pulseaudio] core-util.c: setpriority() worked. I: [pulseaudio] core-util.c: Successfully gained nice level -11. I: [pulseaudio] main.c: This is PulseAudio 10.0 D: [pulseaudio] main.c: Compilation host: x86_64-pc-linux-gnu D: [pulseaudio] main.c: Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/pulseaudio-ZMrhzG/pulseaudio-10.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -fdiagnostics-color=auto D: [pulseaudio] main.c: Running on host: Linux x86_64 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) D: [pulseaudio] main.c: Found 4 CPUs. I: [pulseaudio] main.c: Page size is 4096 bytes D: [pulseaudio] main.c: Compiled with Valgrind support: no D: [pulseaudio] main.c: Running in valgrind mode: no D: [pulseaudio] main.c: Running in VM: no D: [pulseaudio] main.c: Optimized build: yes D: [pulseaudio] main.c: FASTPATH defined, only fast path asserts disabled. I: [pulseaudio] main.c: Machine ID is . I: [pulseaudio] main.c: Session ID is 1. I: [pulseaudio] main.c: Using runtime . I: [pulseaudio] main.c: Using state directory . I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-10.0/modules. I: [pulseaudio] main.c: Running in system mode: no E: [pulseaudio] pid.c: Daemon already running. E: [pulseaudio] main.c: pa_pid_file_create() failed. It looks like a bug in the source code in this line: I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I haven't checked to see if this
Bug#867115: more information on the #867115 bug
Hi maintainer, I'm running debian stable (Stretch) and have had problems with SMPlayer ever since I upgraded to Stretch. I'm running the older versions of xorg and xserver, in case that makes any difference. I'm seeing the bug reported as #867115, and I'm forwarding this copy of the mplayer log as this doesn't seem to be reported thus far. I note there may be differences in how the option is reported "noquiet", "-noquiet" and "--noquiet" == /usr/bin/mplayer -noquiet -slave -identify -nofs -sub-fuzziness 1 -vo xv, -ao pulse, -nodr -double -nomouseinput -input nodefault-bindings:conf=/dev/null -nokeepaspect -wid 46137378 -monitorpixelaspect 1 -subfont-osd-scale 3 -ass -embeddedfonts -ass-line-spacing 0 -ass-font-scale 1 -noflip-hebrew -ass-styles /home/richard/.config/smplayer/styles.ass -subcp ISO-8859-1 -subpos 100 -volume 47 -osdlevel 0 -prefer-ipv4 -vf-add screenshot=/home/richard/Pictures/smplayer_screenshots/shot -noslices -channels 2 -af-add scaletempo -af-add equalizer=0:0:0:0:0:0:0:0:0:0 -softvol -softvol-max 110 /home/Library/Media/Video/George.Webb/Day 2021 HillaryHillarys Awan Brothers Saga Deepens Part 1. Error parsing option noquiet (option not found) Setting command line option '--noquiet=' failed. Exiting... (Fatal error) = I'd be happy to test modifications to this command line, but as I'm unfamiliar with the application, I thought I should seek advice first. regards Richard
Bug#867034: [Pkg-zfsonlinux-devel] Bug#867034: zfsutils-linux: ls -l gives an input/output error
Hi, Freshly made pool with noting in it: # zpool scrub stor04 # zpool status stor04 pool: stor04 state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Mon Jul 3 23:32:30 2017 config: NAME STATE READ WRITE CKSUM stor04 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ata-SAMSUNG_MZ7KM960HMJP-5_S3F3NY0J400802 ONLINE 0 0 0 ata-SAMSUNG_MZ7KM960HMJP-5_S3F3NY0J401053 ONLINE 0 0 0 ata-SAMSUNG_MZ7KM960HMJP-5_S3F3NY0J401191 ONLINE 0 0 0 ata-SAMSUNG_MZ7KM960HMJP-5_S3F3NY0J401196 ONLINE 0 0 0 logs mirror-1 ONLINE 0 0 0 nvme-INTEL_SSDPEDMD400G4_PHFT641000MY400BGN-part2 ONLINE 0 0 0 nvme-INTEL_SSDPEDMD400G4_PHFT641000NL400BGN-part2 ONLINE 0 0 0 cache nvme-INTEL_SSDPEDMD400G4_PHFT641000MY400BGN-part3ONLINE 0 0 0 errors: No known data errors On Mon, 3 Jul 2017, Petter Reinholdtsen wrote: [G] ls -l gives an input/output error when running on a directory containing an .zfs directory (all run as root): Are you sure you do not have corrupted disks? 'zpool status' should get you going if that is the case. -- Happy hacking Petter Reinholdtsen
Bug#863888: openjdk-8-jdk: cannot install package
I solved this by updating the ca-certificates-java package in backports. I could then install the jdk and jre. apt-get install -t jessie-backports ca-certificates-java --bs
Bug#842801: cowsay: The cowsay-off split should be noted more prominently
Package: cowsay Version: 3.03+dfsg1-16 Severity: wishlist In 3.03+dfsg1-13 the cowsay-off package was created in response to #769194. I used one of those cows in a login script and on upgrade had an error about a nonexisting cow. It took me longer than it otherwise would have to figure out what was going on because the changelog entry: * Add cowsay-off package (closes: #769194) Isn't clear. Since this is carving out a feature that's been in upstream forever doesn't this at least warrant some mention in NEWS, or at the very least: * Cows deemed offensive have been split off into a separate cowsay-off package. Affected cows are: head-in, mutilated, sodomized-sheep (closes: #769194) Which would make this easier to find for people who searched through the changelog for the missing file. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages cowsay depends on: ii libtext-charwidth-perl 0.04-7+b4 ii perl5.22.2-5 Versions of packages cowsay recommends: ii cowsay-off 3.03+dfsg1-16 Versions of packages cowsay suggests: pn filters -- no debconf information
Bug#808358: vmdebootstrap: no-kernel option is being ignored
Package: vmdebootstrap Version: 1.2-1 Severity: important -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable'), (50, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 4.1.6-249 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vmdebootstrap depends on: ii debootstrap 1.0.75 ii kpartx 0.5.0+git1.656f8865-1 ii libjs-sphinxdoc 1.3.2-1 ii mbr 1.1.11-5 ii parted 3.2-10 ii python-cliapp 1.20150829-1 ii python-distro-info 0.14 ii python2.7 2.7.9-2 pn python:any ii qemu-utils 1:2.1+dfsg-12+deb8u4 Versions of packages vmdebootstrap recommends: ii grub2-common 2.02~beta2-32 ii python-guestfs1:1.28.12-1+b3 ii qemu-system 1:2.4+dfsg-5 ii qemu-user-static 1:2.4+dfsg-5 ii squashfs-tools1:4.3-3 Versions of packages vmdebootstrap suggests: pn cmdtest pn pandoc pn u-boot:armhf -- no debconf information INFO EEEK! Something bad happened... INFO command failed: ['debootstrap', '--arch=armel', '--include=kmod,linux-image-armel,less,openssh-server,ntp,screen,sudo,tcpdump,ca-certificates,netbase,lsb-release,wget,curl,haveged,git-core,acpid,binutils', 'jessie', '/tmp/tmpho78Ue', 'http://httpredir.debian.org/debian'] I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Found additional required dependencies: acl adduser dmsetup insserv libaudit1 libaudit-common libbz2-1.0 libcap2 libcap2-bin libcryptsetup4 libdb5.3 libdebconfclient0 libdevmapper1.02.1 libgcrypt20 libgpg-error0 libkmod2 libncursesw5 libprocps3 libsemanage1 libsemanage-common libslang2 libsystemd0 libudev1 libustr-1.0-1 procps systemd systemd-sysv udev I: Found additional base dependencies: git git-man libbsd0 libcurl3 libcurl3-gnutls libdns-export100 libedit2 liberror-perl libexpat1 libffi6 libgmp10 libgnutls-deb0-28 libgnutls-openssl27 libgssapi-krb5-2 libhavege1 libhogweed2 libicu52 libidn11 libirs-export91 libisccfg-export90 libisc-export95 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 libmnl0 libnetfilter-acct1 libnettle4 libnfnetlink0 libopts25 libp11-kit0 libpcap0.8 libpsl0 libpython2.7-minimal libpython2.7-stdlib libpython-stdlib librtmp1 libsasl2-2 libsasl2-modules-db libsqlite3-0 libssh2-1 libtasn1-6 libwrap0 mime-support openssh-client openssh-sftp-server openssl perl perl-modules python python2.7 python2.7-minimal python-minimal I: Checking component main on http://httpredir.debian.org/debian... E: Couldn't find these debs: linux-image-armel It seems that the parameter 'no-kernel' is being ignored.
Bug#798225: ERROR: Only amd64 supports UEFI in Wheezy
Package: vmdebootstrap Version: 0.10-1 Severity: important DEBUG Config: [config] output = log = log-level = debug log-max = 0 log-keep = 10 log-mode = 0600 dump-memory-profile = simple memory-dump-interval = 300 verbose = True image = image.img size = 39 bootsize = 12800 boottype = vfat bootoffset = 0 use-uefi = False esp-size = 5242880 part-type = msdos roottype = ext4 swap = 0 foreign = variant = extlinux = False tarball = apt-mirror = http://httpredir.debian.org/debian mirror = http://localhost:3142/debian arch = armel distribution = wheezy package = netbase, ntp, less, openssh-server, screen, git-core, binutils, ca-certificates, wget, kmod, curl, haveged, lsb-release custom-package = no-kernel = True kernel-package = enable-dhcp = True root-password = lock-root-password = True serial-console = False serial-console-command = /sbin/getty -L ttyS0 115200 vt100 sudo = True owner = squash = False configure-apt = True mbr = False grub = False sparse = False pkglist = False no-acpid = False DEBUG Python version: 2.7.10 (default, Jul 1 2015, 10:54:53) [GCC 4.9.2] CRITICAL Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 189, in _run self.process_args(args) File "/usr/sbin/vmdebootstrap", line 268, in process_args 'Only amd64 supports UEFI in Wheezy') AppException: Only amd64 supports UEFI in Wheezy ERROR: Only amd64 supports UEFI in Wheezy AppException: command failed: ['qemu-img', 'create', '-f', 'raw', 'image.img', '59'] I can reproduce this only with wheezy distribution. This should not happen since UEFI support was not set in config.
Bug#797445: KeyError: 'armel'
Package: vmdebootstrap Version: 0.8-1 Severity: important Tags: upstream Hi, I get the following error using the latest Debian package version 0.9-1 in sid: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 189, in _run self.process_args(args) File "/usr/sbin/vmdebootstrap", line 246, in process_args if self.efi_arch_table[self.settings['arch']]['exclusive'] and\ KeyError: 'armel'
Bug#791467: plowshare: javascript usage puts user at risk of remote code execution
> I am in the process of packaging the new upstream version of plowshare. > There has been a significant change so that the core framework (of shell > scripts) is kept entirely separate to the scripts which use this API to > implement support for specific external sites. While separating the core from the scripts that support the individual sites is definitely a step in the right direction, I think that relying entirely on audits of those scripts is a bad idea. There are many such scripts, new scripts for new cyberlocker sites are frequently added, and existing scripts updated to take account of changes to the sites they support. Therefore, performing such audits would be like playing a game of whack-a-mole. Moreover there is a trade-off: the stricter the scripts are about what javascript they accept, the more likely they will be broken by small changes so the websites. Lastly, you've got to wonder how effective malicious code detection can be if it's implemented entirely using unix shell tools (and presumably operates purely on the syntactic level). For these reasons, you really do need a sandboxed javascript interpreter if you want to avoid the possibility of malicious code execution. Maybe other js interpreters (v8, spidermonkey) are easier to sandbox? Until you find a way of sandboxing the JS interpreter, I'd recommend disabling the javascript support.
Bug#792612: frama-c: please provide package w/o gui & gui dependencies
Source: frama-c Version: 20140301+neon+dfsg-3 Severity: wishlist According to the INSTALL document in the frama-c source distribution, the GTK GUI and the associated dependencies are optional. However, in Debian both the frama-c and the frama-c-base package depend on the liblablgtk* packages. Please provide a version of the frama-c package without the GTK GUI, and without its associated dependencies.
Bug#792296: gcc-msp430: scary warning in package discription no longer relevant
Package: gcc-msp430 Version: 4.6.3~mspgcc-20120406-7 The long description for gcc-msp430 contains the following scary warning: BEWARE: due to a bug in the memory layout reference of FRAM-based chips, this package DOES NOT WORK with MSP430FR5xxx chips (eg. FraunchPad devkit). DO NOT use gcc-msp430 on that chip series, as you will lose access to JTAG and BSL, and permanently BRICK your chip! I suspect this is a reference to bug #706482 https://bugs.debian.org/706482 However, bug #706482 was marked as fixed in version 4.6.3~mspgcc-20120406-7. If the warning message is no longer applicable it should be removed.
Bug#792293: gcc-msp430: please provide msp430 cross-compiler based on mainline gcc
Package: gcc-msp430 Version: 4.6.3~mspgcc-20120406-7 Severity: important The gcc-msp430 package in Debian is based on the obsolete mspgcc project. Now that upstream gcc officially supports the msp430 architecture, there should be a new gcc-msp430 package providing an msp430 cross-compiler based on the msp430 support in mainline gcc.
Bug#792182: vmdebootstrap does not create /etc/network/interfaces.d/ if missing
Package: vmdebootstrap
Version: 0.8-1
Severity: important
Tags: patch
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages vmdebootstrap depends on:
ii debootstrap 1.0.70
ii extlinux3:6.03+dfsg-7
ii kpartx 0.5.0-7
ii mbr 1.1.11-5+b1
ii parted 3.2-7
ii python 2.7.9-1
ii python-cliapp 1.20140719-1
ii python-distro-info 0.14
ii python2.7 2.7.10-2
pn python:any
ii qemu-utils 1:2.3+dfsg-5
Versions of packages vmdebootstrap recommends:
ii grub2-common 2.02~beta2-23
ii python-guestfs1:1.28.10-2+b1
ii qemu-system 1:2.3+dfsg-5
ii qemu-user-static 1:2.3+dfsg-5
ii squashfs-tools1:4.2+20130409-2
Versions of packages vmdebootstrap suggests:
pn u-boot:armhf
-- debconf information excluded
Hi,
While trying to build a wheezy Debian image in armel arch vmdebootstrap
doesn't create the folder '/etc/network/interfaces.d/'.
Relevant error:
#[Errno 2] No such file or directory:
'/tmp/tmpX/etc/network/interfaces.d/setup'
Cleaning up
ERROR: [Errno 2] No such file or directory:
'/tmp/tmpX/etc/network/interfaces.d/setup'
#
This is the patch that I have used to build the image:
--- /tmp/vmdebootstrap.orig 2015-07-12 15:17:25.0 +0200
+++ /usr/sbin/vmdebootstrap 2015-07-09 18:05:18.12800 +0200
@@ -624,17 +624,8 @@
def setup_networking(self, rootdir):
self.message('Setting up networking')
-# unconditionally write for wheezy (which became oldstable on
04/25/2015)
-if self.was_oldstable(datetime.date(2015, 4, 26)):
-with open(os.path.join(
-rootdir, 'etc', 'network', 'interfaces'), 'w') as netfile:
-netfile.write('source /etc/network/interfaces.d/*\n')
-os.mkdir(os.path.join(rootdir, 'etc', 'network', 'interfaces.d'))
-
-elif not os.path.exists(os.path.join(rootdir, 'etc', 'network',
'interfaces')):
-with open(os.path.join(
-rootdir, 'etc', 'network', 'interfaces'), 'w') as netfile:
-netfile.write('source-directory /etc/network/interfaces.d\n')
+if not os.path.exists(os.path.join(rootdir, 'etc', 'network',
'interfaces.d')):
+os.makedirs(os.path.join(rootdir, 'etc', 'network',
'interfaces.d'))
with open(os.path.join(
rootdir, 'etc', 'network', 'interfaces.d', 'setup'), 'w') as eth:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#791467: plowshare: javascript usage puts user at risk of remote code execution
Package: plowshare4 Version: 1.0.5-1 Severity: grave Tags: security (Rationale for severity grave: introduces a security hole allowing access to the accounts of users who use the package. plowshare4 is a command-line tool for downloading files from cyberlocker-type sites. For some sites, this requires evaluating snippets of javascript code, to this end the plowshare4 package depends on rhino, a JVM-based javascript implementation. According to the rhino documentation, the rhino command-line tool is capable of loading arbitrary java classes, accessing the filesystem and executing shell commands (see https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino/Shell ). This has obvious security implications: If the individual plowshare4 download modules are not carefully implemented, a malicious download site could emit javascript code which causes arbitrary commands to be run on the user's system. Where the javascript is downloaded via http rather than https, a malicious 3rd party (man-in-the-middle) could do the same. In order to prevent this, the javascript interpreter should be invoked in such a way that the code is evaluated in a sandbox, i.e. loading arbitrary java classes, accessing the filesystem and executing shell commands are not possible. There does seem to be some support for this in rhino, judging by the documentation https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino/Overview#Security Moreover, the javascript code snippets should be filtered to check for malicious code before being passed to the javascript interpreter; ideally, any code that doesn't match a specific, known-good pattern should be rejected. Until these things have been implemented, I suggest disabling javascript support in plowshare4 completely to prevent putting users at risk.
Bug#779370:
With udev rules that call a script to applies the apm_on_ac or apm_on_battery settings accordingly, the systemd resume could be handled with a unit file like this: [Unit] Description=Trigger all block device udev rules on resume to re-apply non-permanent device settings (e.g. smartctl and hdparm rules). After=suspend.target After=hibernate.target After=hybrid-sleep.target [Service] Type=oneshot ExecStart=/sbin/udevadm trigger --action=change --subsystem-match=block [Install] WantedBy=suspend.target WantedBy=hibernate.target WantedBy=hybrid-sleep.target -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779370: hdparm + systemd: old apm/pm-utils hooks not working/migrated
Package: hdparm
Severity: serious
The apm/pm-utils suspend/resume functionalities, provided by shipping the
files 20hdparm and 95hdparm-apm scripts, do not work with systemd.
(missing systemd unit files)
To allow setting defaults I would suggest to support wildcards in hdparm.conf.
And ship with visible defaults like this:
# avoid excessive hard disk load-cycling
ata-* {
apm = 254
}
Maybe apm_on_battery and apm_on_ac settings?
And have those defaults switched on state changes.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744753: Fix for anacron (running on resume under systemd)
Control: reopen 744753 Please ship a working systemd unit file as given in the last comments. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725284:
Control: reopen 725284 Udev rules are only trigged when devices appear/disapper, but not when the kernel suspends (with the device staying present and only entering a low power state) A systemd unit file is required to recover all hdparm settings that devices wrongly initialize back to factory defaults after suspend. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772663: apt-listchanges stores temporary files in /tmp, vulnerably to a tmpcleaner
Package: apt-listchanges Version: 2.85.13+nmu1 Severity: minor I discovered this bug after leaving the message buffer of apt-listchanges around for days in a screen session while the pager was set to read the changelog: Fetched 186 MB in 10s (17.8 MB/s) Reading changelogs... Done Exception OSError: (2, 'No such file or directory', '/tmp/apt-listchanges-tmp6Mpfdy') in ', mode 'w+b' at 0x7fc1bcf23930>> ignored apt-listchanges: Do you want to continue? [Y/n] It's probably a better idea to store this in /var/run/apt-listchanges/tmp or something, so something cleaning up old entries in /tmp won't cause an error if this runs over a period of time greater than the thing automatically cleaning up /tmp. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-listchanges depends on: ii apt1.0.9.3 ii debconf [debconf-2.0] 1.5.53 ii debianutils4.4+b1 ii python 2.7.8-2 ii python-apt 0.9.3.11 ii python-support 1.0.15 ii ucf3.0030 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii elinks [www-browser]0.12~pre6-5+b2 ii links [www-browser] 2.8-2+b3 ii lynx-cur [www-browser] 2.8.9dev1-2+b1 ii postfix [mail-transport-agent] 2.11.3-1 pn python-glade2 pn python-gtk2 ii w3m [www-browser] 0.5.3-19 ii xterm [x-terminal-emulator] 312-1 -- debconf information: apt-listchanges/email-address: root apt-listchanges/confirm: false apt-listchanges/frontend: pager apt-listchanges/save-seen: true apt-listchanges/which: news -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772033: oops my bad, missing description
I'm sorry, somehow I missed to post the bug description. I'm using LXDE with openbox and have it configured to always put windows/dialogs onto the monitor where the mouse pointer currently is. Gimp instead *always* opens the save-file dialog and some other dialogs on the other monitor. This is confusing behavior and in my case pretty annoying, since I have pen input on one monitor and have to switch to the mouse to drag over the window everytime this happens. I think this might a Gimp bug, because the WM setting works for every other application I use, except for Gimp. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770065: I think the NEWS file for 3.4.0 should mention allow-axfr-ips
Package: pdns-server Version: 3.4.1-3 Severity: important I upgraded to 3.4.0 and my authoritative nameserver stopped working, nothing major was noted in the Changelog or NEWS file, I think it's worth a mention that the value for allow-axfr-ips changed from 0.0.0.0/0,::/0 to 127.0.0.0/8,::1, this means that by default AXFR won't be allowed unless you're on localhost, which is a pretty big behavior change for the default configuration of a DNS server. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdns-server depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii init-system-helpers 1.21 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-serialization1.55.01.55.0+dfsg-3 ii libbotan-1.10-0 1.10.8-2 ii libc6 2.19-13 ii libcrypto++95.6.1-6 ii libgcc1 1:4.9.1-19 ii libgmp102:6.0.0+dfsg-6 ii liblua5.1-0 5.1.5-7.1 ii libpolarssl71.3.8-1 ii libsqlite3-03.8.7.1-1 ii libstdc++6 4.9.1-19 ii lsb-base4.1+Debian13+nmu1 ii ucf 3.0030 pdns-server recommends no packages. Versions of packages pdns-server suggests: pn pdns-backend ii pdns-recursor 3.6.2-2 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769944: The server can't load /usr/lib/powerdns/libbindbackend.so, it's actually located at /usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so
Package: pdns-server Version: 3.4.1-3 Severity: grave When I upgraded from 3.3.* I started getting this in error log: Nov 17 19:28:30 u pdns[14671]: Loading '/usr/lib/powerdns/libbindbackend.so' Nov 17 19:28:30 u pdns[14671]: Unable to load module '/usr/lib/powerdns/libbindbackend.so': /usr/lib/powerdns/libbindbackend.so: cannot open shared object file: No such file or directory Nov 17 19:28:30 u pdns[14671]: dnsbackend unable to load module in bind Nov 17 19:28:31 u pdns[14500]: Our pdns instance exited with code 1 Nov 17 19:28:31 u pdns[14500]: Respawning There's no such *.so file. To hack around this I've done this: $ sudo mkdir /usr/lib/powerdns/ $ sudo ln -s $(dpkg -L pdns-server|grep libbindbackend.so) /usr/lib/powerdns/libbindbackend.so $ file /usr/lib/powerdns/libbindbackend.so /usr/lib/powerdns/libbindbackend.so: symbolic link to `/usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so' Which makes pdns-server work again. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdns-server depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii init-system-helpers 1.21 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-serialization1.55.01.55.0+dfsg-3 ii libbotan-1.10-0 1.10.8-2 ii libc6 2.19-13 ii libcrypto++95.6.1-6 ii libgcc1 1:4.9.1-19 ii libgmp102:6.0.0+dfsg-6 ii liblua5.1-0 5.1.5-7.1 ii libpolarssl71.3.8-1 ii libsqlite3-03.8.7.1-1 ii libstdc++6 4.9.1-19 ii lsb-base4.1+Debian13+nmu1 ii ucf 3.0030 pdns-server recommends no packages. Versions of packages pdns-server suggests: pn pdns-backend ii pdns-recursor 3.6.2-2 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752263: The exact same issue that was previously resolved in #612723 is happening again
Package: iodine Version: 0.6.0~rc1-19 Severity: serious I couldn't find out how to re-open an existing bug but this issue that I reported & was resolved a while ago is now happening again: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612723 Upgrading from 0.6.0~rc1-12 to 0.6.0~rc1-19 yields a munged config file as noted in 612723, since that bug was solved back in 2011 I've upgraded iodine several times, so this must be some regression in the control scripts for it. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iodine depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii libc6 2.19-1 ii udev 204-8 ii zlib1g 1:1.2.8.dfsg-1 iodine recommends no packages. Versions of packages iodine suggests: ii dnsutils 1:9.9.5.dfsg-4 pn fping | oping ii gawk 1:4.1.1+dfsg-1 ii ipcalc 0.41-4 ii iproute2 3.14.0-2 -- debconf information: iodine/daemon_options: -c -p 5252 172.31.255.1/27 gg.nix.is iodine/start_daemon: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743200: The cronolog manpage should document its exit codes
Package: cronolog
Version: 1.6.2+rpk-1
Severity: wishlist
Tags: upstream
When you run cronolog successfully it exits with a non-zero exit code
due to this bit of code in main():
n_bytes_read = read(0, read_buf, sizeof read_buf);
if (n_bytes_read == 0)
{
exit(3);
}
I.e. if it has no more bytes to read it exits with non-zero, this is
most unusual for programs check the successful exit status of spawned
programs.
Since this looks intentional this should be documented prominently in
the manpage, along with the other exit codes, from the source via
Emacs's "M-x occur RET exit( RET":
11 matches for "exit(" in buffer: cronolog.c
213:exit(1);
233:exit(1);
254:exit(0);
259:exit(1);
266:exit(1);
277:exit(1);
301:exit(1);
319:exit(3);
327:exit(4);
362:exit(5);
417:exit(2);
Documenting when and why it exits with 0..5 would be really useful.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cronolog depends on:
ii dpkg 1.17.6
ii install-info 5.2.0.dfsg.1-2
ii libc6 2.18-4
ii perl 5.18.2-2+b1
cronolog recommends no packages.
cronolog suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743186: cronolog segfaults on [sic] cronolog --vesion
Package: cronolog
Version: 1.6.2+rpk-1
Severity: normal
On my system:
$ cronolog --version
cronolog version 1.6.2
$ cronolog --vesion
Segmentation fault
A backtrace for this is:
Program received signal SIGSEGV, Segmentation fault.
0x77ab5f4c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x77ab5f4c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x77af3b46 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x77af48cb in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x77af4953 in getopt_long () from /lib/x86_64-linux-gnu/libc.so.6
#4 0x0040130d in main (argc=2, argv=0x7fffdf58) at cronolog.c:172
(gdb)
Which reveals that the "struct option long_options" just needs to have
this at the end:
{ NULL, 0, NULL, 0 }
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cronolog depends on:
ii dpkg 1.17.6
ii install-info 5.2.0.dfsg.1-2
ii libc6 2.18-4
ii perl 5.18.2-2+b1
cronolog recommends no packages.
cronolog suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730580: 1.6.0 released
Hi, in fact, 1.6.0 was released 2014-01-04, so upgrading to 1.5.11 got pointless ;) Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731845: handlersocket-mysql-5.5: API version for DAEMON plugin is too different
Package: handlersocket-mysql-5.5 Version: 1.1.0-7-g1044a28-1 Severity: important Dear Maintainer, when install the plugin handlersocket for mysql-server-5.5 as below, mysql>install plugin handlersocket soname 'handlersocket.so'; ERROR 1126 (HY000): Can't open shared library 'handlersocket.so' (errno: 0 API version for DAEMON plugin is too different) it seems that this problem has occured in previous version which is reported in bug 649214 * What led up to the situation? -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages handlersocket-mysql-5.5 depends on: ii libc6 2.13-38 ii libgcc11:4.7.2-5 ii libstdc++6 4.7.2-5 ii mysql-server-core-5.5 5.5.31+dfsg-0+wheezy1 Versions of packages handlersocket-mysql-5.5 recommends: pn handlersocket-doc handlersocket-mysql-5.5 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728183: plasma-desktop: Plasma desktop crashes on boot since update
Package: plasma-desktop Version: 4:4.10.5-3 Severity: grave Justification: renders package unusable Since an update to the packages on Debian testing last night, the KDE desktop crashes on boot, giving a message that prompts to create a backtrace. Here is that backtrace. As you can see, running Debian Jessie, versions of KDE packages are 4.10.5-1 or 4.10.5-2. kernel 3.10-3-amd64. I have a wallpaper slideshow which appears to be one of the things crashing. What is the source of this problem? This is the first time my desktop has failed in 3 years of KDE atop debian. Will be happy for a solution as have had to fall back to another desktop. Reproducible: Always Steps to Reproduce: 1. Boot with user configuration into KDE desktop. (guest account with default configuration boots normally.) 2. Error message appears indicating that the plasma desktop has crashed. Ctrl- Alt-Del will still bring up a restart/shutdown/logout menu with the correct appearance settings. 3. Actual Results: KDE desktop does not appear at boot. Expected Results: KDE desktop renders computer available for use when started up. Application: plasma-desktop (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.6 Operating System: Linux 3.10-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (jessie) -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: plasma-desktop (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.6 Operating System: Linux 3.10-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (jessie) -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd0f8287780 (LWP 7946))] Thread 3 (Thread 0x7fd0d9719700 (LWP 7957)): #0 0x7fd0ebff8e35 in __GI___pthread_mutex_lock (mutex=0x239eb10) at pthread_mutex_lock.c:95 #1 0x7fd0eb724291 in g_mutex_lock () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #2 0x7fd0eb6e4a2b in g_main_context_query () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #3 0x7fd0eb6e5102 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd0eb6e55fa in g_main_loop_run () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #5 0x7fd0e05abd26 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fd0eb7091d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fd0ebff6e0e in start_thread (arg=0x7fd0d9719700) at pthread_create.c:311 #8 0x7fd0f7b889ed in clone () at .../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7fd0ce491700 (LWP 7959)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at .../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd0f174ba4b in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7fd0f174ba89 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fd0ebff6e0e in start_thread (arg=0x7fd0ce491700) at pthread_create.c:311 #4 0x7fd0f7b889ed in clone () at .../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7fd0f8287780 (LWP 7946)): [KCrash Handler] #6 0x7fd0f46d7b80 in QMetaObject::cast (this=this@entry=0x7fd0f7a8e560 , obj=obj@entry=0x2a73bb0) at kernel/qmetaobject.cpp:275 #7 0x7fd0f77371cf in qobject_cast (object=0x2a73bb0) at /usr/include/qt4/QtCore/qobject.h:380 #8 create (args=..., keyword=..., parent=, parentWidget=, this=) at .../../kdecore/util/kpluginfactory.h:533 #9 createInstance (error=, args=..., parent=, parentWidget=, this=) at .../../kdecore/services/kservice.h:559 #10 createInstance (error=, args=..., parent=, this=) at .../../kdecore/services/kservice.h:536 #11 Plasma::loadEngine (language=..., type=type@entry=Plasma::AppletComponent, parent=parent@entry=0x2a74140) at ../../plasma/scripting/scriptengine.cpp:185 #12 0x7fd0f7737796 in Plasma::loadScriptEngine (language=..., applet=0x2a74140) at ../../plasma/scripting/scriptengine.cpp:209 #13 0x7fd0f768b9ad in Plasma::AppletPrivate::init (this=0x290aa70, packagePath=...) at ../../plasma/applet.cpp:2799 #14 0x7fd0f7690a53 in Plasma::Applet::Applet (this=0x2a74140, parentObject=0x0, args=...) at ../../plasma/applet.cpp:193 #15 0x7fd0f76cdf62 in Plasma::PluginLoader::loadApplet (this=, name=..., appletId=, appletId@entry=172, args=...) at .../../plasma/pluginloader.cpp:134 #16 0x7fd0f76832a5 in Plasma::Applet::load (appletName=..., appletId=appletId@entry=172, args=...) at ../../plasma/applet.cpp:2451 #17 0x7fd0f76a04e4 in Plasma::ContainmentPrivate::addApplet (this=0x291caf0, name=..., args=..., appletGeometry=..., id=id@entry=172, delayInit=delayInit@entry=true) at ../../plasma/containment.cpp:2221 #18 0x7fd0f76a4be5 in Plasma::Containment::restoreContents (this=0x28f0990, group=...) at ../../plasma/containment.cpp:497 #19 0x7fd0f76a1734 in Plasma::Containment::restore (this=0x28f0990,
Bug#726390: switch to upstream udev rules
Thank you for the kind response and information. Looking forward to it. With "auto-assembly support" you have a much better description then my "using udev rules". Basicly, I think it is about moving the assembly functionality from the startup scripts to event driven rules, and leaving only some watchdog functionality in the initramfs and regular startup scripts that degrades the arrays if they are not getting assembled. I found a related page that lists some points and pseudo code: https://wiki.ubuntu.com/ReliableRaid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726390: switch to upstream udev rules
Package: mdadm Wondering about why nothing happened when hot-plugging a raid member drive, I found the following answer in the changelog: * disabled the incremental assembly upstream turned on in 3.1.3 for now, this will have to wait until after the squeeze release. And saw the Maintainer changed. Many thanks to all for maintaining the package in the past and ongoing! Maybe it is possible to shed some light about the current state and the intentions of enabling upsteam's incremental/hotplug code (udev rules) in Debian? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718217: lmt fails to run on resume from sleep, suspend, standby
Package: gdm I noticed lmt was again not properly setting the hdparm values on resume. Turning on the verbose output revealed many "Couldn't acquire prelim lock on descriptor" errors. I have no idea about the real cause for this. But stopping lmt before suspend in a /etc/pm/sleep.d/99laptop_mode file with something like this ... hibernate|suspend) if [ -e /etc/init.d/laptop-mode ] ; then invoke-rc.d laptop-mode stop fi ... works around the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#713022: bug#14686: closed (Re: bug#14686: Bug#713022: truncate man and info pages must mention -s / -r mandatory)
Your bug report #14686: Bug#713022: truncate man and info pages must mention -s / -r mandatory which was filed against the coreutils package, has been closed. The explanation is attached below, along with your original report. If you require more details, please reply to 14...@debbugs.gnu.org. -- 14686: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14686 GNU Bug Tracking System Contact help-debb...@gnu.org with problems --- Begin Message --- On 06/21/2013 09:05 PM, jida...@jidanni.org wrote: > Package: coreutils > Version: 8.13-3.3 > File: /usr/share/man/man1/truncate.1.gz > X-debbugs-CC: bug-coreut...@gnu.org > > $ truncate /tmp/erere > truncate: you must specify either `--size' or `--reference' > > What a shock. Not mentioned on man or info pages! Well it was immediately obvious what to do given the above output. Some might consider a pointed message like this, preferable to having to read the manual initially. > > And >truncate OPTION... FILE... > should be >truncate <--size|--ref...> [OPTION...] FILE... Or more accurately: truncate <--size|--reference> [OPTION...] FILE... Now some may find the above more confusing to parse. Also worth noting is the next line in the man page and info manual, i.e. the first line of the description, should make it quite obvious a size is required: "Shrink or extend the size of each FILE to the specified size" Also we follow this pattern for other utils like cut(1). So I'm slightly inclined to leave as is. > Also mention size is in bytes. Don't just hope the reader will examine > every options' wording to ferret that out. Fair enough. I'll adjust to: -s, --size=SIZE set or adjust the file size by SIZE bytes. See also --io-blocks thanks, Pádraig. --- End Message --- --- Begin Message --- Package: coreutils Version: 8.13-3.3 File: /usr/share/man/man1/truncate.1.gz X-debbugs-CC: bug-coreut...@gnu.org $ truncate /tmp/erere truncate: you must specify either `--size' or `--reference' What a shock. Not mentioned on man or info pages! And truncate OPTION... FILE... should be truncate <--size|--ref...> [OPTION...] FILE... Also mention size is in bytes. Don't just hope the reader will examine every options' wording to ferret that out. --- End Message ---
Bug#713022: bug#14686: Acknowledgement (Bug#713022: truncate man and info pages must mention -s / -r mandatory)
Thank you for filing a new bug report with debbugs.gnu.org. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to bug-coreut...@gnu.org (after having been given a bug report number, if it did not have one). Your message has been sent to the package maintainer(s): bug-coreut...@gnu.org If you wish to submit further information on this problem, please send it to 14...@debbugs.gnu.org. Please do not send mail to help-debb...@gnu.org unless you wish to report a problem with the Bug-tracking system. -- 14686: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14686 GNU Bug Tracking System Contact help-debb...@gnu.org with problems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712700: xscreensaver-screensaver-bsod: Windows 3.1 bsod screensaver is sometimes displayed when it is not selected
Package: xscreensaver-screensaver-bsod Version: 5.15-3 Severity: minor Dear Maintainer, Select the BSOD screensaver and configure it to use only one type of bsod. I tried it several times with linux(fsck) option, then the linux(sparc) option and then bsd option. Then lock the system to start the screensaver. The screensaver starts initially as it should and repeats but after time the windows 3.1 bsod screensaver is shown. Since I had not selected the windows 3.1 option this should not be displayed. It does not always show up but I can frequently produce it with the options I tried. When testing this setting the duration to 5 seconds will make the windows screen show up quicker. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xscreensaver-screensaver-bsod depends on: ii libc62.13-38 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libice6 2:1.0.8-2 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.5.0-1+deb7u1 ii libxext6 2:1.3.1-2+deb7u1 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxt6 1:1.1.3-1+deb7u1 ii xscreensaver-data-extra 5.15-3 xscreensaver-screensaver-bsod recommends no packages. xscreensaver-screensaver-bsod suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: [pkg-wine-party] package wine does not install wine on amd64
Michael, somehow I misread your response, as if you wanted me to patch other packages, but reconsidering I think you have rather expressed you'd consider a patch from me. Thanks for being willing to accept an improvement. I would certainly send a patch if I were able to. So please leave the bug open, to reflect the status and point other admins and users to the solution. Have a nice weekend. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: [pkg-wine-party] package wine does not install wine on amd64
> If you believe in that solution, please feel free to provide a patch.
> Complaints without action tend to be counter-productive time wasters.
Exactly. That would surely be the answer if filing this for packages that
depend on wine.
Exept, wine-party is resposible for a package that currently suffers from not
being able to fulfill the dependency and simply hasn't put the workaround's
("hello world" message) in the right place yet.
Sorry, I won't bother other packages' devs that are not in the position to
throw in
a debconf question in the right place, to make sure all *admins* are
getting informed properly.
Nevermind, as an admin I reported the issue after having gone through troubles,
and it
is the pkg-wine-party decision to appreciate it or not.
The thing is as simple as "package wine does not install wine on amd64".
Install time informations would surely be appreciated if only an incomplete
installation happened.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: [pkg-wine-party] package wine does not install wine on amd64
> > Thus, the idea of letting the packet managment script provide the > message. > > Or having the front end fix their assumptions. Please consider filing > a bug against q4wine. Please sleep over this. This sounds funny to me. The debian wine package maintainers want upstream software to adapt to a debian wine package that does not install the files that the package claims to fulfill the dependency for? Pushing patches upstream instead of providing a package with a fixed workaround until the cross-arch dependecy can be properly resolved? With humor it can give a good laugh. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: [pkg-wine-party] package wine does not install wine on amd64
> Which front end are you using? It was q4wine > message should pop up via > xmessage, and if not it will be dumped to stdout. So if your front > end is preventing that, the issue should be fixed there. Unfortunately, missing files already cause errors during the frontend configuration process, before any actual attempt to execute the wine "binary". Thus, the idea of letting the packet managment script provide the message. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: package wine does not insall wine on amd64)
> Are you saying that the following message was never displayed to you? Correct, the message was never displayed. As reported, I installed a frontend that depends on wine, and strange error messages popped up instead, caused by all kinds of missing files. Thus my suggestion you use a high priority debconf question/action/message, if the cross-arch dependecy can not yet be defined and fulfilled properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: package wine does not insall wine on amd64)
Hello, thanks for your answer. > It is impossible for a package to install another from its postinst; > dpkg has a lock to prevent multiple simultaneous invocations, and > postinst scripts are run under the dpkg lock. Perhaps the postinst > could enable i386 multiarch, If selecting a package for later install would be possible (maybe through PackageKit), purposely triggering a failure and retry may be enough. > but that is an intrusive change and it > would be hard to ensure it would work (e.g. if the user has configured > architecture-specific mirrors for apt); it seems better to me to just > tell the user what to do, until i386 multiarch becomes the default for > amd64... It isn't? Will this resolve the deps correctly instead of installing a fake wine64-bin? Since wine64-bin does not ensure wine will work at all, I would at least suggest to use a high priority debconf question to draw attention to it, if no automated solution is possible. (My reopen attempt did not work out. I think it wold be good to let the report open. When trying to figure out what the problem was I came accross a closed bug that mentioned this, but I was lead on, because it suggested wine64-bin fixed it.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: package wine does not insall wine on amd64)
reopen: 707226 > If you install the wine package instead of wine-bin, you will get the > wine64-bin package, Yes, that is also what the bug title says and exaclty what happened by installing a package that depends on wine. > which will present the above helpful info to the > user. Unfortunately not, and it was't helpfull. It seems rather misleading have a package that seems to be installed correctly but executing it will not produce its functionality. The dependecy is actually only fullfilled by providing the true wine functionality. Thus the suggestion to let the wine64-bin package execute a post-inst script or similar, to install the 32bit version, instead of pretending to be wine and delivering only a string. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707226: package wine does not insall wine on amd64
Package: wine Severity: grave On a freshly installed Debian stable (wheezy) on amd64, installing a frontend like q4wine and wine seems to succeed, but running it produces strange errors. The reason: Actually, no wine binaries or libs were installed. Please add some debconf script to the wine-bin:amd64 package that does actually pull in wine-bin:i386 package. If i386 is not enabled, these are the steps such a script needs to perform: dpkg --add-architecture i386 apt-get update apt-get install wine-bin:i386 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702996: please mention/provide upgrade path from gnome to xfce
Package: release-notes Hello, after seaching a lot, it finaly turned up not only questions but also a solution on how to upgrade a squeeze gnome system to a wheezy xfce system. Found at the end of this thread: debianforum.de/forum/viewtopic.php?f=12&t=140311 This request seems quite justified especially for people in the world where only older hardware is available. The method: * removing gnome aptitude purge `dpkg --get-selections | grep gnome | cut -f 1` aptitude -f install aptitude purge `dpkg --get-selections | grep deinstall | cut -f 1` aptitude -f install * dist-upgrade * installing xfce4 aptitude install xfce4 (or xfce4-desktop) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700573: (no subject)
Thank you It looked like a bug to me -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700573: (no subject)
I forgot to tell that my wheezy install is about 3 weeks old. I use a local mirror that is not updated -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678834: permissions of shared directory
For the sake of completeness for users that are bitten by this bug and search for instructions: The filesystem permissions of a fully publicly shared directory (i.e. ~/public) has to be drwxrwsrwx. chmod a+rwx ~/public chmod g+s ~/public And /etc/samba/smb.conf has to contain the line inherit permissions = yes in the [global] section. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678834: permission fix for public shares
The experience after a couple of months showed that the solution that sets "inherit permissions = yes" as default works very well. I'd suggest to implement that change as a fix. (Either in the default config file shipped, or better, by adjusting the fallback value that samba uses if the option is not defined in the configuraiton.) Adjusting a default in this way also seems to be the easiest of the options. I did not experience interference with manually defined shares, but if there is a possibility to define it as a default that applies only to usershares (maybe a template file?) that might be an option as well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693533: krossruby no longer exists in testing (Wheezy)
Package: krossruby Source: kross-interpreters Severity: wishlist krossruby no longer exists in testing. It would be nice for it to come back, if possible. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661230: use nopasswdlogin group (empty passwords break things)
Tools like gnome-system-tools or accountservice allow to add the user to the nopasswdlogin group. You might adopt that, to avoid the sudo breakage with empty passwords. A description of the method: https://wiki.archlinux.org/index.php/GDM#Passwordless_login -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683058: closed by Ansgar Burchardt (Re: ftp.debian.org: please create an empty wheezy-updates repository)
Am Wed, 10 Oct 2012 21:09:05 + schrieb ow...@bugs.debian.org (Debian Bug Tracking System): > wheezy-updates does now exist. Thanks! Is the creation of the dir now included in the script/procedure for post wheezy releases? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685422: iscsitarget-dkms: ata smart commands denial of service
Package: iscsitarget-dkms Version: 1.4.20.2-10 Severity: important Dear Maintainer, ata smart commands generates kernel call trace and kernel process istd1 hangs running at 100% cpu. iscsi target becomes unuseable unless reboot for example, I ran smartctl -i sdl on my windows xp initiator. this is how kernel has responded: [21974.560657] iscsi_trgt: BUG at /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.c:392 assert(req->tio) [21974.560667] Pid: 3288, comm: istiod1 Tainted: G O 3.2.0-3-amd64 #1 [21974.560671] Call Trace: [21974.560683] [] ? send_data_rsp+0x45/0x1f4 [iscsi_trgt] [21974.560691] [] ? ua_pending+0x19/0xa5 [iscsi_trgt] [21974.560698] [] ? disk_execute_cmnd+0x1cf/0x22d [iscsi_trgt] [21974.560705] [] ? worker_thread+0xfd/0x255 [iscsi_trgt] [21974.560711] [] ? try_to_wake_up+0x197/0x197 [21974.560717] [] ? nthread_stop+0x35/0x35 [iscsi_trgt] [21974.560724] [] ? kthread+0x76/0x7e [21974.560730] [] ? kernel_thread_helper+0x4/0x10 [21974.560735] [] ? kthread_worker_fn+0x139/0x139 [21974.560740] [] ? gs_change+0x13/0x13 [21974.560767] [ cut here ] [21974.560770] kernel BUG at /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.c:392! [21974.560775] invalid opcode: [#1] SMP [21974.560779] CPU 1 [21974.560781] Modules linked in: pppoe pppox ppp_generic slhc bluetooth drbd lru_cache cn tun ip6table_filter ip6_tables ebtable_nat ebtables iscsi_trgt(O) crc32c ipt_LOG ipt_REJECT xt_multiport xt_conntrack iptable_filter xt_TCPMSS xt_tcpmss iptable_mangle ipt_MASQUERADE xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables x_tables kvm_intel kvm ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse bridge stp loop tpm_infineon snd_hda_codec_analog i915 asix snd_hda_intel snd_hda_codec drm_kms_helper snd_hwdep coretemp psmouse drm i2c_algo_bit mcs7830 snd_pcm i2c_core snd_page_alloc snd_timer usbnet snd evdev hp_wmi sparse_keymap serio_raw pcspkr soundcore rfkill iTCO_wdt iTCO_vendor_support acpi_cpufreq mperf processor video button tpm_tis tpm tpm_bios wmi thermal_sys ext4 crc16 jbd2 mbcache raid1 md_mod dm_mirror dm_region_hash dm_log dm_mod usb_storage uas sd_mod crc_t10dif ata_ge neric floppy uhci_hcd ata_piix e100 mii ehci_hcd libata scsi_mod e1000e usbcore usb_common [last unloaded: scsi_wait_scan] [21974.560891] [21974.560895] Pid: 3288, comm: istiod1 Tainted: G O 3.2.0-3-amd64 #1 Hewlett-Packard HP Compaq dc5800 Microtower/2820h [21974.560902] RIP: 0010:[] [] send_data_rsp+0x45/0x1f4 [iscsi_trgt] [21974.560911] RSP: 0018:880112d55e10 EFLAGS: 00010286 [21974.560915] RAX: RBX: 880115445060 RCX: b182 [21974.560920] RDX: b182 RSI: 880112d55f58 RDI: 880112d55f58 [21974.560924] RBP: R08: R09: 0720072007200720 [21974.560928] R10: 0001 R11: 0720072007200720 R12: 880113be8280 [21974.560932] R13: 880115d76000 R14: 880112c5a4d8 R15: 880112c5a4e8 [21974.560937] FS: () GS:88011bc8() knlGS: [21974.560942] CS: 0010 DS: ES: CR0: 8005003b [21974.560946] CR2: 7f9a69f95600 CR3: 00011350e000 CR4: 06e0 [21974.560950] DR0: DR1: DR2: [21974.560954] DR3: DR6: 0ff0 DR7: 0400 [21974.560959] Process istiod1 (pid: 3288, threadinfo 880112d54000, task 880113be8280) [21974.560963] Stack: [21974.560966] 13f1 8801136c9650 00013740 a04ce093 [21974.560973] 880112d55fd8 880115445060 880113be8280 880113be8280 [21974.560979] 880115d76000 880112c5a4d8 880112c5a4e8 a04ccda8 [21974.560986] Call Trace: [21974.560992] [] ? ua_pending+0x19/0xa5 [iscsi_trgt] [21974.560999] [] ? disk_execute_cmnd+0x1cf/0x22d [iscsi_trgt] [21974.561006] [] ? worker_thread+0xfd/0x255 [iscsi_trgt] [21974.561011] [] ? try_to_wake_up+0x197/0x197 [21974.561018] [] ? nthread_stop+0x35/0x35 [iscsi_trgt] [21974.561023] [] ? kthread+0x76/0x7e [21974.561028] [] ? kernel_thread_helper+0x4/0x10 [21974.561033] [] ? kthread_worker_fn+0x139/0x139 [21974.561039] [] ? gs_change+0x13/0x13 [21974.561041] Code: 48 85 ed 75 28 48 c7 c1 38 fd 4c a0 ba 88 01 00 00 48 c7 c6 a7 f9 4c a0 48 c7 c7 df f9 4c a0 31 c0 e8 de f2 e7 e0 e8 19 d8 e7 e0 <0f> 0b 48 89 df e8 d0 fa ff ff 8b 55 14 39 d0 0f 46 d0 85 d2 0f [21974.561083] RIP [] send_data_rsp+0x45/0x1f4 [iscsi_trgt] [21974.561090] RSP [21974.561094] ---[ end trace 6fe56b5bd067bee4 ]--- root@homerouter:~# /etc/init.d/iscsitarget stop Removing iSCSI enterprise target devices: : the rest of the system is running ok, but since I cannot kill the kernel process I must reboot the system in order to keep using iscsi target. PID USER PR NI VIRT RES SH
Bug#520901: Status?
In the meanwhile in 2012... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683815: gdm overrides system's default umask
Package: gdm Hello, in contrast to slim, kdm, or startx, gdm breaks the central umask configuration. This is in debian stable (squeeze). GDM sets the default umask to an explicit value (0022), however, it should leave it as set by the system's default settings. (The default umask is set with pam_umask according to http://wiki.debian.org/DebianDesktopHowTo) Executed in an xterm called directly from ~/.xsession ~$ umask 0022 while a text console gives a correct: ~$ umask 0002 (as set by pam_umask.so usergroups) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683765: [Pkg-xfce-devel] Bug#683765: default umask gets overidden
Hello, thank you very much for your help. The umask returned in the .xsession xterm is 0022. Does this mean gdm is wrongly setting the umask? Could you then please reassign this bug to gdm? > > Package: xfce4 > > > > Hello, > > this is in debian stable (squeeze). > > > > Something in the desktop environment sets the default umask > > to an explicit value (0022), instead of leaving it as set according > > to the system's default settings. > > > > (The default umask is set with pam_umask according to > http://wiki.debian.org/DebianDesktopHowTo) > > > > Executed in an xfce-terminal or xterm: > > ~$ umask > > 0022 > > > > while a text console gives a correct: > > ~$ umask > > 0002 > > (as set by pam_umask.so usergroups) > > How do you start Xfce? Can you try to put an xterm in .xsession and see > what umask you get there? > > Regards, > -- > Yves-Alexis > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683765: default umask gets overidden
Package: xfce4 Hello, this is in debian stable (squeeze). Something in the desktop environment sets the default umask to an explicit value (0022), instead of leaving it as set according to the system's default settings. (The default umask is set with pam_umask according to http://wiki.debian.org/DebianDesktopHowTo) Executed in an xfce-terminal or xterm: ~$ umask 0022 while a text console gives a correct: ~$ umask 0002 (as set by pam_umask.so usergroups) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683058: codename urls that enable proper next-stable sources.list
Package: ftp.debian.org Currently it does not seem possible to set up a sources.list for the next-stable release (i.e. now wheezy) such that it will remain fully appropriate after the release. >From what I gathered, wheezy-updates is missing. Could you please add symlinks, empty dirs (whatever may be appropriate) for the next-stable codename (wheezy), and include this step into the release cycling procedure? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682378: bug#12024: Acknowledgement (Bug#682378: Error in post-command-hook (flyspell-post-command-hook))
Thank you for filing a new bug report with debbugs.gnu.org. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to bug-gnu-em...@gnu.org (after having been given a bug report number, if it did not have one). Your message has been sent to the package maintainer(s): help-debb...@gnu.org If you wish to submit further information on this problem, please send it to 12...@debbugs.gnu.org. Please do not send mail to help-debb...@gnu.org unless you wish to report a problem with the Bug-tracking system. -- 12024: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12024 GNU Bug Tracking System Contact help-debb...@gnu.org with problems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678834: usable configurations for guest-writable public samba shares
The three alternatives I found: (also a workaround without samba adjustments) chmod publicly writable shares to be setguid dirs and add the samba option "inherit permissions = yes" (x bits are still mapped to archive,hidden,system) (should works in all cases) let samba guests create files as "sambaguest" and belonging to the "users" group (rw for all users if they have local access to the path) (should work for usershares) let samba guests create files in the name of the user who created the user share (and belonging to the "sambaguest" group) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
