Bug#746358: Boot hangs if fstab contains NFS entries
On 14/06/14 06:32, Michael Biebl wrote: Am 08.06.2014 00:37, schrieb Jason Alavaliant: I've just tested the latest initscripts package (2.88dsf-53.1) Jason, could you please test again with 2.88dsf-53.2? 53.1 had an embarrasing formatting error. I've retested with 2.88dsf-53.2 and confirmed that the /etc/network/if-up.d/mountnfs script in that version of the package successfully boots my machine without it hanging.So from my perspective that version of the package fixes this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
I've just tested the latest initscripts package (2.88dsf-53.1) Unfortunately the lines in adds to /etc/network/if-up.d/mountnfs ; -- # Skip the mountnfs hook when being triggered by the networking SysV init # script and instead use the systemd built-in mechanisms to mount remote # file systems. # This avoids a deadlock caused by the rpcbind SysV init script depending # on $network and the $network LSB facility being provided by the networking # SysV init script. if [ -d /run/systemd/system ]; then systemctl list-jobs | grep -q network.target exit 0 fi - Do not fix the problem for me and my boot started sitting on configuring network interfaces again (I only waited 5minutes before giving up, so I'm unsure if it was just being very slow or if it would never have completed) I ended up swapping out the above lines for --- if [ -d /run/systemd/system ] ; then systemctl status network.target /dev/null || exit 0 fi --- the same as I'd been using after a previous suggestion in this bug, they continues to work and my system now finishes configuring network interfaces and boots successfully again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750792: rpcbind: rpcinfo segfaults
On 07/06/14 12:21, Aníbal Monsalve Salazar wrote: On Sat, 2014-06-07 11:03:28 +1200, Jason Alavaliant wrote: Package: rpcbind Version: 0.2.1-3 Severity: important Dear Maintainer, In the last few days the rpcinfo command has started to segfault for me. (I'm not 100% sure but it may have started directly after I updated my libc6 package to 2.19-1) I'm seeing in /var/log/syslog entries like Jun 7 10:52:02 grigorig kernel: [ 1085.923616] traps: rpcinfo[3160] general protection ip:7f940ff37218 sp:783d1e38 error:0 in libpthread-2.19.so[7f940ff26000+18000] (which come from nfs-common trying to call it when it's init script runs). Running it directly from a shell results in a segfault; $ /usr/sbin/rpcinfo Segmentation fault Here is what I get running it through gdb $ gdb /usr/sbin/rpcinfo GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/rpcinfo...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/rpcinfo warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. __lll_unlock_elision (lock=0x77ddafe0 authnone_lock, private=0) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 29 ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or directory. (gdb) bt #0 __lll_unlock_elision (lock=0x77ddafe0 authnone_lock, private=0) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 #1 0x77bbc9b1 in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1 #2 0x77bc17f0 in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1 #3 0x00403f8d in ?? () #4 0x00401b22 in ?? () #5 0x77404b45 in __libc_start_main (main=0x401760, argc=1, argv=0x7fffe228, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe218) at libc-start.c:287 #6 0x00402591 in ?? () (gdb) Thanks -J -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages rpcbind depends on: ii initscripts 2.88dsf-53 ii insserv 1.14.0-5 ii libc-bin 2.19-1 ii libc62.19-1 ii libtirpc10.2.2-7 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian12 rpcbind recommends no packages. rpcbind suggests no packages. -- no debconf information Comments, Please. Did more testing my end and can confirm that libc6 version does seem be the trigger.The segfault went away when I downgraded my libc6 package from 2.19-1 to 2.18-7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750792: rpcbind: rpcinfo segfaults
Package: rpcbind Version: 0.2.1-3 Severity: important Dear Maintainer, In the last few days the rpcinfo command has started to segfault for me. (I'm not 100% sure but it may have started directly after I updated my libc6 package to 2.19-1) I'm seeing in /var/log/syslog entries like Jun 7 10:52:02 grigorig kernel: [ 1085.923616] traps: rpcinfo[3160] general protection ip:7f940ff37218 sp:783d1e38 error:0 in libpthread-2.19.so[7f940ff26000+18000] (which come from nfs-common trying to call it when it's init script runs). Running it directly from a shell results in a segfault; $ /usr/sbin/rpcinfo Segmentation fault Here is what I get running it through gdb $ gdb /usr/sbin/rpcinfo GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/rpcinfo...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/rpcinfo warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. __lll_unlock_elision (lock=0x77ddafe0 authnone_lock, private=0) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 29 ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or directory. (gdb) bt #0 __lll_unlock_elision (lock=0x77ddafe0 authnone_lock, private=0) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 #1 0x77bbc9b1 in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1 #2 0x77bc17f0 in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1 #3 0x00403f8d in ?? () #4 0x00401b22 in ?? () #5 0x77404b45 in __libc_start_main (main=0x401760, argc=1, argv=0x7fffe228, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe218) at libc-start.c:287 #6 0x00402591 in ?? () (gdb) Thanks -J -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages rpcbind depends on: ii initscripts 2.88dsf-53 ii insserv 1.14.0-5 ii libc-bin 2.19-1 ii libc62.19-1 ii libtirpc10.2.2-7 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian12 rpcbind recommends no packages. rpcbind 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#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
On 30/04/14 01:10, Michael Biebl wrote: Am 29.04.2014 13:10, schrieb Jason Alavaliant: On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 I suspect the hang to be caused by the NFS fstab entry. Can you comment out the entry and reboot so we have confirmation? If so, can you please try the following patch for /etc/network/if-up.d/mountnfs with the NFS mount re-enabled. --- a/network/if-up.d/mountnfs +++ b/network/if-up.d/mountnfs @@ -7,6 +7,10 @@ #Also mounts SMB filesystems now, so the name of #this script is getting increasingly inaccurate. +if [ -d /run/systemd/system ] ; then + systemctl status network.target /dev/null || exit 0 +fi + PATH=/sbin:/bin . /lib/init/vars.sh I've tested as requested and can confirm that if I restored the bridge interface lines in my /etc/network/interfaces but comment out the nfs mount in my fstab then the system boots without hanging. (Interestingly nfs mount in fstab doesn't cause a hang without the bridge network setup being there as well so in my case it seems to require both factors together to trigger the hang). Booting with mountnfs patched while the nfs mount and bridged network interface are in place also is successful so it looks like that patch does indeed fix the problem. Thank you for the quick fix. -J -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Package: systemd Version: 204-10 Severity: important Dear Maintainer, I just updated my system which installed systemd-sysv after I rebooted I found that the system was now hanging on bootup (even in rescue mode) with the stopping point being configuring network interfaces. Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741406: (linux-image-3.13-1-amd64: tcp traffic fails after approx 1/2hour boot time 'TCP: out of memory -- consider tuning tcp_mem')
I believe that linux-image-3.13-1-amd64 3.13.10-1 fixes this problem. I've been testing all package updates since 3.13.5-1 and this is the first version of 3.13 where I've been able to run it for 12 hours+ without tcp dropping out.I only have the computer effected by this bug on during the day so can't test longer than 12hours, but given in the past the longest it stayed up was sub 2hours I'm fairly confident the problem is gone. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741406: linux-image-3.13-1-amd64: tcp traffic fails after approx 1/2hour boot time 'TCP: out of memory -- consider tuning tcp_mem'
Package: src:linux Version: 3.13.5-1 Severity: important Dear Maintainer, When I boot up my computer using the 3.13 kernel it works for approximately 1/2 hour (I think the real factor is how much network traffic gets sent/recieved, it just takes me 1/2 hour to hit enough to trigger the problem). Suddenly my ability to send tcp traffic over the network stops working (icmp pings are fine), which given my home directory is mounted over nfs4 rather breaks the computer. The problem does not occur if I boot the machine using the kernel from linux-image-3.12-1-amd64 instead. Information from dmesg/syslog that occurs after tcp traffic stops working below; I've not done anything to alter my tcp_mem params so this failure is occuring with the kernel/debian default values. Mar 10 07:45:33 grigorig kernel: [ 2684.863224] TCP: out of memory -- consider tuning tcp_mem Mar 10 07:45:34 grigorig kernel: [ 2685.126472] [ cut here ] Mar 10 07:45:34 grigorig kernel: [ 2685.126479] WARNING: CPU: 1 PID: 4510 at /build/linux-UvfduQ/linux-3.13.5/net/core/stream.c:201 inet_csk_destroy_sock+0x4d/0x 130() Mar 10 07:45:34 grigorig kernel: [ 2685.126480] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables bnep rfcomm binfmt_misc rpcsec_gss_krb5 nfsv4 dns_resolver nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge stp llc nls_utf8 nls_cp437 vfat fat fuse loo p parport_pc ppdev lp parport joydev hid_generic snd_usb_audio snd_usbmidi_lib uvcvideo snd_seq_midi snd_seq_midi_event videobuf2_vmalloc videobuf2_memops videob uf2_core snd_rawmidi videodev usbhid media hid btusb bluetooth snd_hda_codec_realtek iTCO_wdt snd_hda_codec_hdmi iTCO_vendor_support eeepc_wmi asus_wmi sparse_ke ymap rfkill evdev x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86 _64 lrw gf128mul glue_helper ablk_helper cryptd efi_pstore efivars snd_seq snd_hda_intel psmouse snd_hda_codec pcspkr snd_hwdep lpc_ich serio_raw snd_pcm snd_seq _device mfd_core snd_page_alloc snd_timer i2c_i801 snd i915 drm_kms_helper drm i2c_algo_bit soundcore i2c_core wmi mei_me mei video processor button ext4 crc16 m bcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_common ahci libahci libata r8169 mii ehci_pci xhci_hcd ehci_hcd scsi_mod usbcore usb_common thermal fan thermal _sys Mar 10 07:45:34 grigorig kernel: [ 2685.126525] CPU: 1 PID: 4510 Comm: Socket Thread Not tainted 3.13-1-amd64 #1 Debian 3.13.5-1 Mar 10 07:45:34 grigorig kernel: [ 2685.126525] Hardware name: ASUS All Series/H87M-PRO, BIOS 1305 01/06/2014 Mar 10 07:45:34 grigorig kernel: [ 2685.126526] 0009 814a0927 8105ba72 Mar 10 07:45:34 grigorig kernel: [ 2685.126528] 8803dce0f840 8803dce0f9d8 0004 8803dce0f8d0 Mar 10 07:45:34 grigorig kernel: [ 2685.126529] 88040f0867e0 813fc97d 8803dce0f840 8140166e Mar 10 07:45:34 grigorig kernel: [ 2685.126531] Call Trace: Mar 10 07:45:34 grigorig kernel: [ 2685.126533] [814a0927] ? dump_stack+0x41/0x51 Mar 10 07:45:34 grigorig kernel: [ 2685.126535] [8105ba72] ? warn_slowpath_common+0x72/0x90 Mar 10 07:45:34 grigorig kernel: [ 2685.126537] [813fc97d] ? inet_csk_destroy_sock+0x4d/0x130 Mar 10 07:45:34 grigorig kernel: [ 2685.126538] [8140166e] ? tcp_close+0x16e/0x3f0 Mar 10 07:45:34 grigorig kernel: [ 2685.126541] [8142508c] ? inet_release+0x6c/0x80 Mar 10 07:45:34 grigorig kernel: [ 2685.126543] [813a6ad5] ? sock_release+0x15/0x80 Mar 10 07:45:34 grigorig kernel: [ 2685.126544] [813a6b49] ? sock_close+0x9/0x10 Mar 10 07:45:34 grigorig kernel: [ 2685.126546] [8117aec5] ? __fput+0xc5/0x210 Mar 10 07:45:34 grigorig kernel: [ 2685.126549] [81078e87] ? task_work_run+0x97/0xd0 Mar 10 07:45:34 grigorig kernel: [ 2685.126552] [81012969] ? do_notify_resume+0x59/0x90 Mar 10 07:45:34 grigorig kernel: [ 2685.126554] [814addf2] ? int_signal+0x12/0x17 Mar 10 07:45:34 grigorig kernel: [ 2685.126555] ---[ end trace 2ef75a6d35467fcd ]--- -- Package-specific info: ** Version: Linux version 3.13-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-14) ) #1 SMP Debian 3.13.5-1 (2014-03-04) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.13-1-amd64 root=UUID=e5b9e710-f4b3-4e7e-ab54-65f03bfcbc23 ro quiet ** Not tainted ** Kernel log: [1.989962] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860) [1.990082] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [2.003402] usbcore: registered new interface driver usbhid [2.003404] usbhid: USB HID core driver [2.007822] input: Kworld Webcam V5000AF as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input18 [2.007864] usbcore: registered new interface driver uvcvideo [
Bug#735870: linux-image-3.12-1-amd64: stk1160 module no longer enabled/configured on 3.12 kernels
Package: src:linux Version: 3.12.6-2 Severity: normal Dear Maintainer, It appears to me that that stk1160 kernel module has been disabled in the debian 3.12 kernel config. (I can see the stk1160.ko module in the 3.11 amd64 packages but not in the 3.12 ones and looking at the contents of linux-source-3.12: /usr/src/linux-config-3.12/config.amd64_none_amd64.xz I see '# CONFIG_VIDEO_STK1160_COMMON is not set'). I can't find mention of this is the changelog though so I'm presuming that this was not an intentional change? Can we please have CONFIG_VIDEO_STK1160_COMMON=m CONFIG_VIDEO_STK1160_AC97=y CONFIG_VIDEO_STK1160=m reinstated for the next kernel build so those of us with hardware supported by this module can use it again. :) -- Package-specific info: ** Version: Linux version 3.12-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-10) ) #1 SMP Debian 3.12.6-2 (2013-12-29) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.12-1-amd64 root=UUID=e5b9e710-f4b3-4e7e-ab54-65f03bfcbc23 ro quiet ** Not tainted ** Kernel log: [2.587846] hid-generic 0003:093A:2510.0004: input,hidraw3: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-:00:14.0-14.4/input0 [2.797258] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [5.100531] r8169 :03:00.0 eth0: link up [5.100536] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [5.100713] br0: port 1(eth0) entered forwarding state [5.100715] br0: port 1(eth0) entered forwarding state [5.100722] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready [ 12.662576] RPC: Registered named UNIX socket transport module. [ 12.662578] RPC: Registered udp transport module. [ 12.662578] RPC: Registered tcp transport module. [ 12.662579] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 12.664292] FS-Cache: Loaded [ 12.668010] FS-Cache: Netfs 'nfs' registered for caching [ 12.671947] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 37.936121] Key type dns_resolver registered [ 37.939372] NFS: Registering the id_resolver key type [ 37.939377] Key type id_resolver registered [ 37.939378] Key type id_legacy registered [ 50.327981] usb 1-14.4: USB disconnect, device number 8 [ 51.806457] usb 1-14.4: new low-speed USB device number 9 using xhci_hcd [ 51.806952] usb 1-14.4: Device not responding to set address. [ 52.029383] usb 1-14.4: New USB device found, idVendor=093a, idProduct=2510 [ 52.029385] usb 1-14.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 52.029386] usb 1-14.4: Product: USB OPTICAL MOUSE [ 52.029387] usb 1-14.4: Manufacturer: PIXART [ 52.029498] usb 1-14.4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 52.032526] input: PIXART USB OPTICAL MOUSE as /devices/pci:00/:00:14.0/usb1/1-14/1-14.4/1-14.4:1.0/input/input15 [ 52.032747] hid-generic 0003:093A:2510.0005: input,hidraw3: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-:00:14.0-14.4/input0 [ 52.946107] RPC: AUTH_GSS upcall timed out. [ 52.946107] Please check user daemon is running. [ 54.226916] lp: driver loaded but no devices found [ 54.230545] ppdev: user-space parallel port driver [ 54.295501] Bluetooth: RFCOMM TTY layer initialized [ 54.295509] Bluetooth: RFCOMM socket layer initialized [ 54.295510] Bluetooth: RFCOMM ver 1.11 [ 54.296421] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 54.296423] Bluetooth: BNEP filters: protocol multicast [ 54.296428] Bluetooth: BNEP socket layer initialized [ 54.406099] Ebtables v2.0 registered [ 54.414388] ip_tables: (C) 2000-2006 Netfilter Core Team [ 54.418499] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 3632.372182] systemd-logind[4824]: New seat seat0. [ 3632.372337] systemd-logind[4824]: Watching system buttons on /dev/input/event1 (Power Button) [ 3632.372366] systemd-logind[4824]: Watching system buttons on /dev/input/event4 (Video Bus) [ 3632.372392] systemd-logind[4824]: Watching system buttons on /dev/input/event0 (Power Button) [ 3632.372693] systemd-logind[4824]: New session 1 of user alasola. [ 3632.372737] systemd-logind[4824]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 3634.040341] NFS: v4 server thetower.ra09.com does not accept raw uid/gids. Reenabling the idmapper. [ 3684.718896] cdrom: Invalid DVD key ioctl (63) [ 3684.755062] cdrom: Invalid DVD key ioctl (63) [ 3684.921755] cdrom: Invalid DVD key ioctl (63) [ 3685.052601] cdrom: Invalid DVD key ioctl (63) [ 3685.381232] cdrom: Invalid DVD key ioctl (63) [ 3685.424108] cdrom: Invalid DVD key ioctl (63) [ 3685.533382] cdrom: Invalid DVD key ioctl (63) [17177.065598] perf samples too long (2501 2500), lowering kernel.perf_event_max_sample_rate to 5 [22215.724344] cdrom: Invalid DVD key ioctl (63) [22215.850481] cdrom: Invalid DVD key ioctl (63) [22216.059701] cdrom: Invalid DVD key ioctl (63) [22216.196383] cdrom: Invalid DVD key ioctl (63) [22216.505264]
Bug#732804: yabause-qt crashes when File Settings accessed (if no optical drive in system)
Package: yabause-qt Version: 0.9.13-1 Severity: normal Dear Maintainer, Yabause-qt mostly works for me but if from the main menu I select File Settings... to access the settings windows yabause instantly crashes printing in the shell ASSERT: f in file /tmp/buildd/yabause-0.9.13/src/qt/ui/UISettings.cpp, line 171 Aborted I did an strace an yabause and found that prior to the ASSERT yabause was trying to access /proc/sys/dev/cdrom/info (open(/proc/sys/dev/cdrom/info, O_RDONLY) = -1 ENOENT (No such file or directory)) so I dug up a usb dvd drive and connected it to my machine (it normally doesn't have an optical drive attached since I so rarely need optical media), as soon as the drive was attached (which made /proc/sys/dev/cdrom/info come into existance) I was able to access the settings window without crashing. Thanks Jason -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages yabause-qt depends on: ii freeglut3 2.8.1-1 ii libc6 2.17-97 ii libgcc1 1:4.8.2-10 ii libgl1-mesa-glx [libgl1] 10.0.1-1 ii libmini18n1 0.2.1-1 ii libopenal11:1.14-4 ii libqt4-opengl 4:4.8.5+git192-g085f851+dfsg-2 ii libqtcore44:4.8.5+git192-g085f851+dfsg-2 ii libqtgui4 4:4.8.5+git192-g085f851+dfsg-2 ii libsdl1.2debian 1.2.15-8 ii libstdc++64.8.2-10 ii libx11-6 2:1.6.2-1 ii libxrandr22:1.4.1-1 ii yabause-common0.9.13-1 yabause-qt recommends no packages. yabause-qt 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#729215: kate: Please include pate/python-plugins files with kate/kate-data packages
Package: kate Version: 4:4.11.3-1 Severity: wishlist Dear Maintainer, Please consider enabling/adding the pate/python-plugins files to the kate/kate-data packages so the python plugins in the upstream kate source are made available to debian users. Ubuntu has them enabled in their version of the kate packages (which I'd imaging will provide any needed reference on the matter). I've been making use of them in my own custom rebuilds of the kate packages and I believe having them available to debian users in general would be of benefit to other debian users. Briefly from my own testing it looks like to enable them in the debian packages the following changes are required; add to debian/control the following extra build-deps for the package libpython2.7-dev, python-sip-dev, python-qt4-dev, python-kde4-dev (= 4:4.9.80), libqt4-opengl-dev, libqtwebkit-dev update debian/kate-data.install to add +usr/lib/python2.7/dist-packages/PyKate4/__init__.py +usr/share/kde4/apps/kate/pate/block.py +usr/share/kde4/apps/kate/pate/cmake_utils/__init__.py +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_help_parser.py +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_utils.py +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_utils_settings.py +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_utils_settings.ui +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_utils_toolview_cacheview_page.ui +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_utils_toolview_help_page.ui +usr/share/kde4/apps/kate/pate/cmake_utils/cmake_utils_toolview_settings_page.ui +usr/share/kde4/apps/kate/pate/cmake_utils/command_completers/__init__.py +usr/share/kde4/apps/kate/pate/cmake_utils/command_completers/cmake_policy_cc.py +usr/share/kde4/apps/kate/pate/cmake_utils/command_completers/cond_cc.py +usr/share/kde4/apps/kate/pate/cmake_utils/command_completers/param_types.py +usr/share/kde4/apps/kate/pate/cmake_utils/command_completers/syntax_cc.py +usr/share/kde4/apps/kate/pate/color_tools.py +usr/share/kde4/apps/kate/pate/color_tools_toolview.ui +usr/share/kde4/apps/kate/pate/commentar.py +usr/share/kde4/apps/kate/pate/commentar_config.ui +usr/share/kde4/apps/kate/pate/django_utils/django_settings.py +usr/share/kde4/apps/kate/pate/django_utils/django_snippets.py +usr/share/kde4/apps/kate/pate/django_utils/django_template.py +usr/share/kde4/apps/kate/pate/django_utils/django_utils.py +usr/share/kde4/apps/kate/pate/django_utils/django_utils.ui +usr/share/kde4/apps/kate/pate/expand.py +usr/share/kde4/apps/kate/pate/expand/all.expand +usr/share/kde4/apps/kate/pate/expand/text_css.expand +usr/share/kde4/apps/kate/pate/expand/text_html.expand +usr/share/kde4/apps/kate/pate/expand/text_x-c++hdr.expand +usr/share/kde4/apps/kate/pate/expand/text_x-c++src.expand +usr/share/kde4/apps/kate/pate/expand/text_x-chdr.expand +usr/share/kde4/apps/kate/pate/expand/text_x-chdr.expand +usr/share/kde4/apps/kate/pate/expand/text_x-python.expand +usr/share/kde4/apps/kate/pate/format.py +usr/share/kde4/apps/kate/pate/gid/config.ui +usr/share/kde4/apps/kate/pate/gid/gid.py +usr/share/kde4/apps/kate/pate/gid/idutils.py +usr/share/kde4/apps/kate/pate/gid/tool.ui +usr/share/kde4/apps/kate/pate/js_utils/jquery_autocomplete.json +usr/share/kde4/apps/kate/pate/js_utils/js_autocomplete.json +usr/share/kde4/apps/kate/pate/js_utils/js_autocomplete.py +usr/share/kde4/apps/kate/pate/js_utils/js_settings.py +usr/share/kde4/apps/kate/pate/js_utils/js_snippets.py +usr/share/kde4/apps/kate/pate/js_utils/js_utils.py +usr/share/kde4/apps/kate/pate/js_utils/js_utils.ui +usr/share/kde4/apps/kate/pate/js_utils/jslint.py +usr/share/kde4/apps/kate/pate/js_utils/json_pretty.py +usr/share/kde4/apps/kate/pate/libkatepate/__init__.py +usr/share/kde4/apps/kate/pate/libkatepate/autocomplete.py +usr/share/kde4/apps/kate/pate/libkatepate/common.py +usr/share/kde4/apps/kate/pate/libkatepate/compat.py +usr/share/kde4/apps/kate/pate/libkatepate/debug.py +usr/share/kde4/apps/kate/pate/libkatepate/decorators.py +usr/share/kde4/apps/kate/pate/libkatepate/errors.py +usr/share/kde4/apps/kate/pate/libkatepate/menu.py +usr/share/kde4/apps/kate/pate/libkatepate/pred.py +usr/share/kde4/apps/kate/pate/libkatepate/project_utils.py +usr/share/kde4/apps/kate/pate/libkatepate/selection.py +usr/share/kde4/apps/kate/pate/libkatepate/text.py +usr/share/kde4/apps/kate/pate/libkatepate/ui.py +usr/share/kde4/apps/kate/pate/python_autocomplete/python_autocomplete.py +usr/share/kde4/apps/kate/pate/python_autocomplete/python_autocomplete_parse.py +usr/share/kde4/apps/kate/pate/python_console_classic/config.ui +usr/share/kde4/apps/kate/pate/python_console_classic/python_console_classic.py +usr/share/kde4/apps/kate/pate/python_console_ipython/python_console_ipython.css +usr/share/kde4/apps/kate/pate/python_console_ipython/python_console_ipython.py +usr/share/kde4/apps/kate/pate/python_console_ipython/python_console_ipython.ui +usr/share/kde4/apps/kate/pate/python_utils/python_checkers/__init__.py
Bug#668151: mesa: please consider uploading 8.0.2 to experimental
On Mon, Apr 9, 2012 at 10:30 PM, Cyril Brulebois k...@debian.org wrote: Jason Alasola alavali...@gmail.com (09/04/2012): Thank you for making the 8.0 experimental version of mesa available, due to all the new features in 8.0 it's made quite a few programs that never used to work under the mesa drivers work for me. However there are several bugs I'm running into which may be fixed by one of the two bug fix releases since 8.0, can you please package 8.0.2 into experimental if you get time. :) See: http://lists.debian.org/debian-x/2012/03/msg00364.html Where can we fetch your patches from? Mraw, KiBi. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk+CujoACgkQeGfVPHR5Nd0ragCfQnizvO2YSN0SRR/4qBdEipxi yTEAni1AKo07mF6rVcWC1AWXZRQNUE6Y =CKth -END PGP SIGNATURE- Not quite sure how to provide a patch directly but I did update the available 8.0-2 package sources to 8.0.2 and put the upload onto google docs (don't have a better web server available right now) https://docs.google.com/open?id=0BzeiL3tCXJYRbG1GZEVJZWhNeUE https://docs.google.com/open?id=0BzeiL3tCXJYRVzVLOTdXbWVaMUU https://docs.google.com/open?id=0BzeiL3tCXJYRUGJDVzF5R2ZZcm8 https://docs.google.com/open?id=0BzeiL3tCXJYRNGN5TWEwNncxUG8 They seem to compile fine with all the existing patches and settings and I've been using a amd64 package build from those sources on my machine without issue for two days now. -J -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#458765:
I believe I'm seeing the same bug on my system (I've also got 0.7-2) except in my case http: .ics files open with konqueror. (I'm using kde.)
