Bug#1035900: signond uses 100% cpu when used with Google account/drive
Package: signond Version: 8.61-1 Severity: normal X-Debbugs-Cc: s...@gmx.de Dear Maintainer, I've set up my Google account in Plasma systemsettings/online accounts, to be able to access my files in Google Drive from Dolphin. It seems that after a while Dolphin doesn't display those files anymore and signond goes to 100% cpu use. My current workaround is to kill signond, which is restarted automatically and files are displayed again, until the issue occurs again. I would expect files to be displayed continously without having to kill signond and without it using 100% cpu. Not sure at the moment how much of an effect sending the computer to sleep has. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory 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 signond depends on: ii libc6 2.36-9 ii libdbus-1-31.14.6-1 ii libproxy1v50.4.18-1.2 ii libqt5core5a 5.15.8+dfsg-3 ii libqt5dbus55.15.8+dfsg-3 ii libqt5network5 5.15.8+dfsg-3 ii libqt5sql5 5.15.8+dfsg-3 ii libqt5sql5-sqlite 5.15.8+dfsg-3 ii libsignon-extension1 8.61-1 ii libsignon-plugins-common1 8.61-1 ii libstdc++6 12.2.0-14 Versions of packages signond recommends: pn signon-ui signond suggests no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = "", LC_ALL = (unset), LC_TIME = "en_DE.UTF-8", LC_MEASUREMENT = "en_DE.UTF-8", LANG = "en_US.UTF-8" are supported and installed on your system. perl: warning: Falling back to a fallback locale ("en_US.UTF-8"). locale: Cannot set LC_ALL to default locale: No such file or directory
Bug#1019866: linux-image-5.18.0-0.deb11.4-amd64: Noise first before actual sound whenever any sound is played
Package: src:linux Version: 5.18.16-1~bpo11+1 Severity: normal X-Debbugs-Cc: sten.hei...@gmx.de Dear Maintainer, Since upgrading to this kernel, a noise is played first before any sound anytime a sound is starting. After the noise, the actual sounds play just fine. The problem immediately does away if I switch back to the previous kernel, linux-image-5.18.0-0.bpo.1-amd64 (5.18.2 instead of the current 5.18.16). The problem also goes away when using the workaround of disabling the pulseaudio suspend-on-idle module described here [1]. Now I can temporalily use the workaround or the previous kernel, however I'd prefer a fix that still allows for the suspend on idle. Thanks! [1] https://forum.manjaro.org/t/noise-starting-sound-on-amd-ellesmere-hdmi-audio-radeon-rx-590/117101/6 -- Package-specific info: ** Version: Linux version 5.18.0-0.deb11.4-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC Debian 5.18.16-1~bpo11+1 (2022-08-12) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.18.0-0.deb11.4-amd64 root=UUID=0a37c2d3-0cfa-4a80-b172-406cc4b54977 ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: To Be Filled By O.E.M. product_name: To Be Filled By O.E.M. product_version: To Be Filled By O.E.M. chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: P4.50 board_vendor: ASRock board_name: B450 Gaming-ITX/ac board_version: ** Loaded modules: ccm rfcomm cmac algif_hash algif_skcipher af_alg intel_rapl_msr intel_rapl_common bnep edac_mce_amd btusb iwlmvm btrtl kvm_amd btbcm btintel btmtk kvm mac80211 binfmt_misc bluetooth irqbypass snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic ledtrig_audio libarc4 uvcvideo snd_hda_codec_hdmi videobuf2_vmalloc iwlwifi videobuf2_memops nls_ascii aesni_intel snd_usb_audio videobuf2_v4l2 snd_hda_intel nls_cp437 jitterentropy_rng videobuf2_common snd_intel_dspcfg vfat snd_intel_sdw_acpi crypto_simd fat snd_hda_codec snd_usbmidi_lib videodev cryptd sha512_ssse3 snd_rawmidi sha512_generic cfg80211 snd_hda_core snd_seq_device joydev mc ctr snd_hwdep snd_pcm rapl drbg wmi_bmof snd_timer ansi_cprng ccp snd efi_pstore pcspkr sp5100_tco ecdh_generic ecc watchdog k10temp soundcore rng_core crc16 rfkill evdev acpi_cpufreq nct6775 hwmon_vid fuse configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq zstd_compress libcrc32c crc32c_generic hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid amdgpu gpu_sched drm_dp_helper cec rc_core drm_ttm_helper ttm drm_kms_helper ahci libahci xhci_pci libata igb xhci_hcd nvme drm nvme_core scsi_mod usbcore dca t10_pi crc32_pclmul ptp crc32c_intel pps_core i2c_piix4 crc64_rocksoft i2c_algo_bit crc64 crc_t10dif crct10dif_generic crct10dif_pclmul usb_common scsi_common crct10dif_common wmi gpio_amdpt gpio_generic button ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr-
Bug#905321: linux-image-4.17.0-1-amd64: Screen flicker
Here's a link to a video of the flickering; https://drive.google.com/file/d/1nZ4Z_Y1pDtylS11FqZ0PSU5a5G2QxAxM/ Sten
Bug#905321: linux-image-4.17.0-1-amd64: Screen flicker
Package: src:linux Version: 4.17.8-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? apt upgrade installed linux 4.17 and booting the new kernel. * What exactly did you do (or not do) that was effective (or ineffective)? Neither previous kernel versions (mostly 4.15 and before; I have not used 4.16 as much because it causes the X start to be delayed) nor Windows has this problem. I was trying to see if anything is in the logs and some flickers seems to coincide with the following kernel log message: Aug 03 01:27:46 box kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun However, most of the flickers do not (not with this or any other message that I can see in journalctl.) * What was the outcome of this action? Screen flickering in X. Every few seconds (seems to depend how active I use the system) for a fraction of a second. * What outcome did you expect instead? No flickering as before. Please let me know if I can provide any other information, logs, video recording, etc. -- Package-specific info: ** Version: Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-amd64 root=UUID=822f5786-fcce-4563-ada9-f9c9d684742e ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: HP product_name: HP EliteBook Folio G1 product_version: chassis_vendor: HP chassis_version: bios_vendor: HP bios_version: N91 Ver. 01.24 board_vendor: HP board_name: 8170 board_version: KBC Version 29.70 ** Loaded modules: ctr ccm cmac rfcomm bnep nls_ascii nls_cp437 vfat fat arc4 btusb btrtl btbcm btintel snd_hda_codec_hdmi intel_rapl snd_hda_codec_conexant bluetooth x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_generic kvm_intel hp_wmi wmi_bmof jitterentropy_rng snd_soc_skl snd_soc_skl_ipc efi_pstore snd_hda_ext_core snd_soc_sst_dsp kvm snd_soc_sst_ipc snd_soc_acpi irqbypass snd_soc_core snd_compress crct10dif_pclmul crc32_pclmul iwlmvm ghash_clmulni_intel intel_cstate snd_hda_intel intel_uncore snd_hda_codec intel_rapl_perf mac80211 serio_raw snd_hda_core pcspkr efivars snd_hwdep drbg iwlwifi i915 snd_pcm ansi_cprng snd_timer uvcvideo videobuf2_vmalloc videobuf2_memops iTCO_wdt iTCO_vendor_support videobuf2_v4l2 drm_kms_helper snd soundcore videobuf2_common cfg80211 videodev evdev media ecdh_generic joydev rfkill mei_me crc16 mei idma64 shpchp intel_pch_thermal drm i2c_algo_bit processor_thermal_device battery wmi intel_soc_dts_iosf tpm_crb int3403_thermal int340x_thermal_zone soc_button_array tpm_tis video tpm_tis_core tpm int3400_thermal rng_core acpi_thermal_rel intel_hid sparse_keymap button acpi_pad hp_wireless ac efivarfs ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c crc32c_generic crc32c_intel hid_alps hid_generic aesni_intel aes_x86_64 crypto_simd cryptd glue_helper psmouse xhci_pci nvme xhci_hcd i2c_i801 nvme_core intel_lpss_pci usbcore intel_lpss usb_common i2c_hid thermal hid ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # shz, added 01.01.2018, commented 02.01.2018 #iface wlp109s0 inet dhcp # wpa-ssid WooAlum # wpa-psk 2743acc9675072f716d232a3721c0e8d5fdaf71de11b3a85767dac1601a42210 # ** Network status: *** IP interfaces and addresses: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp109s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:c5:89:21:5e:b2 brd ff:ff:ff:ff:ff:ff inet 192.168.0.103/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp109s0 valid_lft 85937sec preferred_lft 85937sec inet6 fe80::ec5c:f6ba:937a:f66b/64 scope link noprefixroute valid_lft forever preferred_lft forever *** Device statistics: Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 15416 196000 0 0 015416 196000 0 0 0 wlp109s0: 12250992529000 0 0 0 339285 1443000 0 0 0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Skylake
Bug#898021: (no subject)
I can confirm libbsd0 0.9.1-1/bug #898088 does not fix my problems, and neither does upgrading to linux-image-4.16.0-2-amd64. (Btw. this is on a Skylake CPU.) Sten
Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail
Hi Stuart, I definitely experience a much shorter delay if I press keys on the keyboard vs. doing nothing; the delay decreases from >5 minutes to 10-20 seconds before sddm appears. Sten
Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail
Package: src:linux Version: 4.16.5-1 Followup-For: Bug #898021 Dear Maintainer, I also seem to have this issue. After upgrading my kernel to linux-image-4.16.0-1-amd64, the graphical login screen (sddm) either is not shown or only shown after a delay (>10s after I complete the text mode login). Before the upgrade X would start instantly. Clicking the mouse does not seem to have an effect with my setup. Booting the previous kernel, linux-image-4.15.0-3-amd64, does not exhibit this problem. After booting linux-image-4.16.0-1-amd64, starting X from the tty (startkde in my case), works too. I can provide additional details if helpful. Sten -- Package-specific info: ** Version: Linux version 4.16.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-1-amd64 root=UUID=822f5786-fcce-4563-ada9-f9c9d684742e ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: HP product_name: HP EliteBook Folio G1 product_version: chassis_vendor: HP chassis_version: bios_vendor: HP bios_version: N91 Ver. 01.16 board_vendor: HP board_name: 8170 board_version: KBC Version 29.70 ** Loaded modules: ctr ccm cmac rfcomm bnep arc4 intel_rapl nls_ascii x86_pkg_temp_thermal intel_powerclamp nls_cp437 coretemp vfat kvm_intel hid_alps fat kvm irqbypass hid_generic snd_hda_codec_hdmi crct10dif_pclmul crc32_pclmul snd_hda_codec_conexant snd_hda_codec_generic ghash_clmulni_intel intel_cstate wmi_bmof hp_wmi btusb btrtl btbcm btintel iwlmvm bluetooth mac80211 snd_soc_skl jitterentropy_rng snd_soc_skl_ipc snd_hda_ext_core iwlwifi snd_soc_sst_dsp intel_uncore snd_soc_sst_ipc snd_soc_acpi intel_rapl_perf drbg snd_soc_core efi_pstore ansi_cprng joydev uvcvideo snd_compress cfg80211 pcspkr snd_hda_intel snd_hda_codec videobuf2_vmalloc snd_hda_core videobuf2_memops evdev i915 videobuf2_v4l2 snd_hwdep ecdh_generic serio_raw videobuf2_common efivars videodev snd_pcm rfkill media crc16 idma64 snd_timer drm_kms_helper snd iTCO_wdt soundcore iTCO_vendor_support drm mei_me tpm_crb shpchp mei intel_lpss_pci intel_lpss i2c_algo_bit intel_pch_thermal wmi battery tpm_tis tpm_tis_core intel_hid tpm sparse_keymap video rng_core ac hp_wireless button acpi_pad efivarfs ip_tables x_tables autofs4 btrfs crc32c_generic xor zstd_decompress zstd_compress xxhash raid6_pq crc32c_intel nvme aesni_intel aes_x86_64 crypto_simd xhci_pci cryptd glue_helper xhci_hcd i2c_i801 psmouse nvme_core usbcore usb_common i2c_hid thermal hid ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback ** Network status: *** IP interfaces and addresses: 1: lo:mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp109s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:c5:89:21:5e:b2 brd ff:ff:ff:ff:ff:ff inet 192.168.0.101/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp109s0 valid_lft 85617sec preferred_lft 85617sec inet6 fe80::ec5c:f6ba:937a:f66b/64 scope link noprefixroute valid_lft forever preferred_lft forever *** Device statistics: Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 48172 592000 0 0 048172 592000 0 0 0 wlp109s0: 29612796 21537000 0 0 0 721865 6479000 0 0 0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:190c] (rev 08) Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [103c:8170] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
Bug#837597: Aw: Bug#837597: Acknowledgement (network-manager: NetworkManager start times out during boot)
The upgrade to linux-image-4.8.0-rc8-amd64 seems to fix the problem and causes no delay on boot anymore. Sten
Bug#839558: Aw: Re: Bug#839558: plasma-nm: Shows incorrect status and want to have password entered again
Hi, Yes, version 1.4.2-1 fixed this problem indeed. Thanks for your idea! Sten > Gesendet: Samstag, 01. Oktober 2016 um 21:42 Uhr > Von: "Diederik de Haas" <didi.deb...@cknow.org> > An: "Sten Heinze" <s...@gmx.de>, 839...@bugs.debian.org > Betreff: Re: Bug#839558: plasma-nm: Shows incorrect status and want to have > password entered again > > On zaterdag 1 oktober 2016 20:42:04 CEST Sten Heinze wrote: > > Upgrade: libnm0:amd64 (1.2.4-2, 1.4.0-4), network-manager:amd64 (1.2.4-2, > > 1.4.0-4) > > Unstable has version 1.4.2-1 and I think there's a good chance that fixes it. > Seems at least worth a try as it resolved an issue I had and also someone > else's issue.
Bug#839558: plasma-nm: Shows incorrect status and want to have password entered again
Package: plasma-nm Version: 4:5.7.4-1 Severity: normal Dear Maintainer, * What led up to the situation? Upgrade: libnm0:amd64 (1.2.4-2, 1.4.0-4), network-manager:amd64 (1.2.4-2, 1.4.0-4) * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? After the upgrade, when waking up the laptop from sleep, plasma-nm shows an incorrect state (not connected, the grayed out wifi-symbol with a red questionmark in the lower right corner). Running nmcli on the command line shows the correct state (connect to my access point). When attempting to connect to my access point (which plasma-nm lists in the available networks), plasma-nm asks for the network password, even though the plasma-nm connection editor shows the password as saved. * What outcome did you expect instead? The correct network state displayed by plasma-nm. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-nm depends on: ii libc6 2.24-3 ii libkf5completion5 5.25.0-1 ii libkf5configcore5 5.25.0-1 ii libkf5configwidgets55.25.0-1 ii libkf5coreaddons5 5.25.0-1 ii libkf5dbusaddons5 5.25.0-1 ii libkf5i18n5 5.25.0-1 ii libkf5iconthemes5 5.25.0-1 ii libkf5itemviews55.25.0-1 ii libkf5kdelibs4support5 5.25.0-1 ii libkf5kiowidgets5 5.25.0-1 ii libkf5modemmanagerqt6 5.25.0-1 ii libkf5networkmanagerqt6 5.25.0-1 ii libkf5notifications55.25.0-1 ii libkf5service-bin 5.25.0-1 ii libkf5service5 5.25.0-1 ii libkf5solid55.25.0-1 ii libkf5wallet-bin5.25.0-1 ii libkf5wallet5 5.25.0-1 ii libkf5widgetsaddons55.25.0-1 ii libkf5windowsystem5 5.25.0-1 ii libkf5xmlgui5 5.25.0-1 ii libopenconnect5 7.06-2+b2 ii libqca-qt5-22.1.1-2 ii libqt5core5a5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui5 5.6.1+dfsg-3+b1 ii libqt5network5 5.6.1+dfsg-3+b1 ii libqt5qml5 5.6.1-8 ii libqt5widgets5 5.6.1+dfsg-3+b1 ii libqt5xml5 5.6.1+dfsg-3+b1 ii libstdc++6 6.1.1-11 ii mobile-broadband-provider-info 20151214-0.1 ii network-manager 1.4.0-4 ii plasma-framework5.25.0-1 ii qml-module-org-kde-kcoreaddons 5.25.0-1 plasma-nm recommends no packages. Versions of packages plasma-nm suggests: ii network-manager-openconnect 1.2.2-1 ii network-manager-openvpn 1.2.4-1 ii network-manager-pptp 1.2.2-1 ii network-manager-vpnc 1.2.2-1 -- no debconf information
Bug#837597: network-manager: NetworkManager start times out during boot
Package: network-manager Version: 1.2.4-2 Severity: normal Dear Maintainer, * What led up to the situation? * Since my upgrade last Friday this happens on every boot. * Before the login manager is displayed, I can see the following message, waiting the full 90s: [ *** ] A start job is running for Network Manager (30s/1min 30s) * Sometimes I could see the following output on the console just before the login manager takes over, but I have not seen those since installing systemd from sid 231-5 and -6 instead of -4 from testing: [FAILED] Failed to start Network Manager. [DEPEND] Dependency failed for Network Manager Wait Online. * The output of "journalctl -u NetworkManager" contains a first failed start during boot, followed by a successful start (I have seen two failed starts followed by a successful start, too): Sep 12 12:28:31 pc systemd[1]: Starting Network Manager... Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Sep 12 12:30:01 pc systemd[1]: Failed to start Network Manager. Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Unit entered failed state. Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Failed with result 'timeout'. Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart. Sep 12 12:30:01 pc systemd[1]: Stopped Network Manager. Sep 12 12:30:01 pc systemd[1]: Starting Network Manager... Sep 12 12:31:23 pc NetworkManager[921]: [1473697883.1057] NetworkManager (version 1.2.4) is starting... Sep 12 12:31:23 pc NetworkManager[921]: [1473697883.1064] Read config: /etc/NetworkManager/NetworkManager.conf * What exactly did you do (or not do) that was effective (or ineffective)? * I tried many things, none of which helped * Plugging in the wired network cable to see if earlier network access helps. (Usually the wireless network connection is established after I log in.) * Using "systemd-analyze critical-chain" I saw virtualbox at the top of the chain, but purging it did not help. * I tried to set logging level to DEBUG in /etc/NetworkManager/NetworkManager.conf, but only the successful second start of NetworkManager logged with DEBUG level, the output for the first start was unchanged (same as above). * I tried commenting out CapabilityBoundingSet, ProtectSystem, and ProtectHome as described in #820174, nothing changed. * Downgrading network-manager to the pre-upgrade version 1.2.2-2 did not help. * Upgrading network-manager to 1.4.0-3 from sid, nothing changed (well, actually the plasma desktop client to network-manager failed to pick up that a network connection was established). * What outcome did you expect instead? * I expect my system to boot in 30s not 3min. And I don't expect NetworkManager to fail to start for no obvious reason. So please help me figure out why this happens and how it can be fixed. * I am adding some system information below that was asked for in #820174 and I hope is useful: # systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2016-09-12 12:51:13 EDT; 27min ago Docs: man:NetworkManager(8) Main PID: 1012 (NetworkManager) Tasks: 5 (limit: 4915) CGroup: /system.slice/NetworkManager.service ├─1012 /usr/sbin/NetworkManager --no-daemon └─1301 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclien Sep 12 12:51:20 pc NetworkManager[1012]: [1473699080.2381] policy: set 'GuestWiFi' (wlp3s0) as default for IPv4 routing and DN Sep 12 12:51:20 pc NetworkManager[1012]: [1473699080.2397] device (wlp3s0): Activation: successful, device activated. Sep 12 12:51:20 pc NetworkManager[1012]: [1473699080.2403] manager: startup complete Sep 12 12:51:20 pc dhclient[1301]: bound to 192.168.65.26 -- renewal in 5900 seconds. Sep 12 13:07:08 pc NetworkManager[1012]: [1473700028.0004] sup-iface[0x179fb80,wlp3s0]: connection disconnected (reason -4) Sep 12 13:07:08 pc NetworkManager[1012]: [1473700028.0050] device (wlp3s0): supplicant interface state: completed -> disconnected Sep 12 13:07:08 pc NetworkManager[1012]: [1473700028.1048] device (wlp3s0): supplicant interface state: disconnected -> scanning Sep 12 13:07:08 pc NetworkManager[1012]: [1473700028.3096] device (wlp3s0): supplicant interface state: scanning -> authenticating Sep 12 13:07:08 pc NetworkManager[1012]: [1473700028.3162] device (wlp3s0): supplicant interface state: authenticating -> associating Sep 12 13:07:08 pc NetworkManager[1012]: [1473700028.4372] device (wlp3s0): supplicant interface state: associating -> completed $ systemctl --version systemd 231 +PAM +AUDIT
Bug#816354: okular: No file association for pdf files and no menu entry
Package: okular Version: 4:15.08.3-1 Severity: minor Dear Maintainer, * What led up to the situation? I installed okular on an uptodate Debian/testing to view a pdf file. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? Trying to open a pdf file from dolphin only leads to an 'open with..' dialog where I can select the application to do so. But no entry for okular can be found is the list of known application nor in the applications list in the Plasma launcher. However, okular can be run from the command line and can open the pdf file, so just the file associations and menu entry is missing. * What outcome did you expect instead? Open okular displaying the selected pdf file from dolpin; or when starting from the launcher, okular to open without any files to display. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-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 Init: systemd (via /run/systemd/system) Versions of packages okular depends on: ii kde-runtime 4:15.08.3-1+b1 ii libc6 2.21-9 ii libfreetype62.6.1-0.1 ii libjpeg62-turbo 1:1.4.2-2 ii libkactivities6 4:4.13.3-1 ii libkdecore5 4:4.14.14-1+b1 ii libkdeui5 4:4.14.14-1+b1 ii libkexiv2-114:15.04.3-1 ii libkio5 4:4.14.14-1+b1 ii libkparts4 4:4.14.14-1+b1 ii libkprintutils4 4:4.14.14-1+b1 ii libkpty44:4.14.14-1+b1 ii libokularcore6 4:15.08.3-1 ii libphonon4 4:4.8.3-2 ii libpoppler-qt4-40.38.0-2 ii libqca2 2.1.1-2 ii libqimageblitz4 1:0.0.6-4 ii libqmobipocket1 4:14.12.2-2 ii libqt4-dbus 4:4.8.7+dfsg-6 ii libqt4-declarative 4:4.8.7+dfsg-6 ii libqt4-svg 4:4.8.7+dfsg-6 ii libqt4-xml 4:4.8.7+dfsg-6 ii libqtcore4 4:4.8.7+dfsg-6 ii libqtgui4 4:4.8.7+dfsg-6 ii libsolid4 4:4.14.14-1+b1 ii libspectre1 0.2.7-3 ii libstdc++6 5.3.1-8 ii phonon 4:4.8.3-2 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages okular recommends: ii cups-bsd 2.1.3-1 Versions of packages okular suggests: pn ghostscript pn jovie ii okular-extra-backends 4:15.08.3-1 ii poppler-data 0.4.7-7 pn texlive-binaries pn unrar -- no debconf information
Bug#815630: Aw: Bug#815630: Acknowledgement (2.4.67-1 causes black screen after login on plasma desktop)
Updating libdrm-intel1 with other packages today lead to a working system with version 2.4.67-1. The following packages were updated: libc-bin:amd64 2.21-8 2.21-9 libc6:amd64 2.21-8 2.21-9 libvlccore8:amd64 2.2.2-3+b1 2.2.2-4 vlc-data:all 2.2.2-3 2.2.2-4 libvlc5:amd64 2.2.2-3+b1 2.2.2-4 libavresample-ffmpeg2:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libswresample-ffmpeg1:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libpostproc-ffmpeg53:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libswscale-ffmpeg3:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libavformat-ffmpeg56:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libavcodec-ffmpeg56:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libavutil-ffmpeg54:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1 libkate1:amd64 0.4.1-5 0.4.1-7 libpng12-0:amd64 1.2.54-1 1.2.54-3 vlc:amd64 2.2.2-3+b1 2.2.2-4 vlc-nox:amd64 2.2.2-3+b1 2.2.2-4 multiarch-support:amd64 2.21-8 2.21-9 iproute2:amd64 4.3.0-1 4.3.0-1+b1 libc-l10n:all 2.21-8 2.21-9 locales:all 2.21-8 2.21-9 libdrm-intel1:amd64 2.4.66-2 2.4.67-1 libutempter0:amd64 1.1.6-1 1.1.6-3 xserver-xorg-video-intel:amd64 2:2.99.917+git20160127-1+b1 2:2.99.917+git20160218-1 Hope that helps someone. Sten > Gesendet: Montag, 22. Februar 2016 um 22:15 Uhr > Von: "Debian Bug Tracking System" <ow...@bugs.debian.org> > An: "Sten Heinze" <s...@gmx.de> > Betreff: Bug#815630: Acknowledgement (2.4.67-1 causes black screen after > login on plasma desktop) > > Thank you for filing a new Bug report with Debian. > > 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 > s...@gmx.de > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian X Strike Force <debia...@lists.debian.org> > > If you wish to submit further information on this problem, please > send it to 815...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 815630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815630 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#815630: 2.4.67-1 causes black screen after login on plasma desktop
Package: libdrm-intel1 Version: 2.4.67-1 Severity: important Dear Maintainer, Updating libdrm-intel1 from 2.4.66-2 to 2.4.67-1 causes a black screen after logging into the plasma desktop. Only the mouse is still visible and the blue glow around the start menu whenever the mouse moves over it. The function of the login screen (SDDM) is unchanged. Downgrading libdrm-intel1 to 2.4.66-2 fixes this problem and results in a normally working desktop. Please let me know if I can provide additional information or can test different hypotheses. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-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 Init: systemd (via /run/systemd/system) Versions of packages libdrm-intel1 depends on: ii libc6 2.21-8 ii libdrm22.4.67-1 ii libpciaccess0 0.13.4-1 libdrm-intel1 recommends no packages. libdrm-intel1 suggests no packages. -- no debconf information
Bug#784406: kdevelop does not call selected source formatter
Package: kdevelop Version: 4:4.7.0-1 Severity: normal Dear Maintainer, I try to use KDevelop with a custom source formatter. So in the Configure KDevelop... dialog in the section Source Formatter I created a new style clang-formatter with the following command line: clang-format-3.5 -style=file I have a .clang-format file in the base folder of the project (to test -style=LLVM should work). Using this command on the command line works: clang-format-3.5 -style=file input.c output.c If I run KDevelop from the terminal I can see the following output when calling Reformat Source: /bin/sh: 1: indent: not found kdevelop(6849) CustomScriptPlugin::formatSourceWithStyle: indent returned empty text for style GNU_indent_GNU indent indent is another custom formatter (that comes with KDevelop) that still seems to be called even though I selected my formatter and saving this. It would be great if KDevelop would actually call the formatter that I selected. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdevelop depends on: ii kde-runtime4:4.14.2-2 ii kdevelop-data 4:4.7.0-1 ii kdevplatform8-libs 1.7.0-2 ii libc6 2.19-18 ii libgcc11:4.9.2-10 ii libkasten2controllers2 4:4.14.2-1 ii libkasten2core24:4.14.2-1 ii libkasten2okteta1controllers1abi1 4:4.14.2-1 ii libkasten2okteta1core1 4:4.14.2-1 ii libkasten2okteta1gui1 4:4.14.2-1 ii libkcmutils4 4:4.14.2-5 ii libkdeclarative5 4:4.14.2-5 ii libkdecore54:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkio54:4.14.2-5 ii libknewstuff3-44:4.14.2-5 ii libkparts4 4:4.14.2-5 ii libktexteditor44:4.14.2-5 ii libplasma3 4:4.14.2-5 ii libprocessui4a 4:4.11.13-2 ii libqjson0 0.8.1-3 ii libqt4-dbus4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqt4-help4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtwebkit4 2.3.4.dfsg-3 ii libstdc++6 4.9.2-10 ii libsublime81.7.0-2 ii libthreadweaver4 4:4.14.2-5 Versions of packages kdevelop recommends: ii g++ 4:4.9.2-2 ii gcc 4:4.9.2-2 ii gdb 7.7.1+dfsg-5 ii make 4.0-8.1 Versions of packages kdevelop suggests: ii cmake 3.0.2-1 pn kapptemplate none pn kdevelop-l10n none pn ninja-buildnone -- 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#760351: error message and test case
Hi, I attached two files, test.cpp, which is an example copied from the cpp-netlib site, and CMakeLists.txt to build it to allow reproducing the issue. If I install libcppnetlib-dev and libcppnetlib0, cmake fails: CMake Error at CMakeLists.txt:6 (find_package): By not providing Findcppnetlib.cmake in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by cppnetlib, but CMake did not find one. Could not find a package configuration file provided by cppnetlib (requested version 0.11.0) with any of the following names: cppnetlibConfig.cmake cppnetlib-config.cmake Add the installation prefix of cppnetlib to CMAKE_PREFIX_PATH or set cppnetlib_DIR to a directory containing one of the above files. If cppnetlib provides a separate development package or SDK, be sure it has been installed. If I download and compile the upstream source code, it will generate (and install) four files, cppnetlibConfig.cmake, cppnetlibConfigVersion.cmake, cppnetlibTargets.cmake, and cppnetlibTargets-noconfig.cmake; This makes the above cmake command run. If I remove this local build of cpp-netlib, the cmake cache, and ~/.cmake/packages/cppnetlib/*, the cmake command returns the same error as at the beginning. Hope that helps reproduce the problem. Let me know if I can help further. Stencmake_minimum_required( VERSION 2.6) project( test) find_package( Boost REQUIRED COMPONENTS thread system) find_package( cppnetlib 0.11.0 REQUIRED) set( SOURCES_TEST_NETLIB test.cpp ) add_executable( test ${SOURCES_TEST_NETLIB}) target_link_libraries( test ${Boost_LIBRARIES} ${CPPNETLIB_LIBRARIES}) #include boost/network/protocol/http/client.hpp #include iostream int main(int argc, char *argv[]) { using namespace boost::network; if (argc != 2) { std::cout Usage: argv[0] [url] std::endl; return 1; } http::client client; http::client::request request(argv[1]); request header(Connection, close); http::client::response response = client.get(request); std::cout body(response) std::endl; return 0; }
Bug#760351: cpp-netlib: cppnetlibConfig.cmake missing in deb pkg?
Source: cpp-netlib Severity: normal Dear Ximin Luo, I'm trying yo use the cpp-netlib package and link to it when building my program. However, my cmake build setup cannot find cpp-netlib because there are no cmake config files in the deb pkgs. I can find a cppnetlibConfig.cmake.in in the 0.11-devel branch on GitHub and Alioth, which as I understand helps cmake to find cpp-netlib. Was the cppnetlibConfig.cmake.in intentionally not added to the deb pkgs? If so, how to I link to cpp-netlib? If not, can it be added? Thanks a lot, Sten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756326: xserver-xorg-video-intel: Upgrade removes xserver-xorg-video-intel
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: normal Dear Maintainer, on my last update/upgrade of my Debian/testing desktop, xserver-xorg-video-intel was removed. This does not lead to an unusable desktop, because it falls back using llvmpipe, however, some programs like pymol segfault with llvmpipe. Reinstalling xserver-xorg-video-intel will fix this. It would be great, if xserver-xorg-video-intel could be kept as a dependency, so that such segfaults can be avoided. Note this might be caused by disabling the automatic install of recommended packages. Please let me know if I can provide more information. Thanks! Sten -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Dec 25 2013 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2356320 Jul 17 17:25 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller [8086:041a] (rev 06) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.16-rc6-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-5) ) #1 SMP Debian 3.16~rc6-1~exp1 (2014-07-21) Xorg X server log files on system: -- -rw-r--r-- 1 root root 30850 Jul 28 14:57 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 2.776] X.Org X Server 1.16.0 Release Date: 2014-07-16 [ 2.776] X Protocol Version 11, Revision 0 [ 2.776] Build Operating System: Linux 3.14-1-amd64 x86_64 Debian [ 2.776] Current Operating System: Linux boston 3.16-rc6-amd64 #1 SMP Debian 3.16~rc6-1~exp1 (2014-07-21) x86_64 [ 2.776] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16-rc6-amd64 root=UUID=6efb5efc-e813-42b0-b19a-f52c8818c7e6 ro quiet [ 2.776] Build Date: 17 July 2014 10:22:36PM [ 2.776] xorg-server 2:1.16.0-1 (http://www.debian.org/support) [ 2.776] Current version of pixman: 0.32.6 [ 2.776]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2.776] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2.776] (==) Log file: /var/log/Xorg.0.log, Time: Mon Jul 28 14:56:58 2014 [ 2.776] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 2.778] (==) No Layout section. Using the first Screen section. [ 2.778] (==) No screen section available. Using defaults. [ 2.778] (**) |--Screen Default Screen Section (0) [ 2.778] (**) | |--Monitor default monitor [ 2.778] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 2.778] (==) Automatically adding devices [ 2.778] (==) Automatically enabling devices [ 2.778] (==) Automatically adding GPU devices [ 2.779] (WW) The directory /usr/share/fonts/X11/misc does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (WW) The directory /usr/share/fonts/X11/Type1 does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (WW) The directory /usr/share/fonts/X11/75dpi does not exist. [ 2.779]Entry deleted from font path. [ 2.779] (==) FontPath set to: built-ins [ 2.779] (==) ModulePath set to /usr/lib/xorg/modules [ 2.779] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 2.779] (II) Loader magic: 0x7f6a20797d80 [ 2.779] (II) Module ABI versions: [ 2.779]X.Org ANSI C Emulation: 0.4 [ 2.779]X.Org Video Driver: 18.0 [ 2.779]X.Org XInput driver : 21.0 [ 2.779]X.Org Server Extension : 8.0 [ 2.780] (II) xfree86: Adding drm device (/dev/dri/card0) [ 2.780] (--) PCI:*(0:0:2:0) 8086:041a:1849:041a rev 6, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0xf000/64 [ 2.780] (II) LoadModule: glx [ 2.781] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 2.787] (II) Module glx:
Bug#734005: error: git-svn died of signal 11 (at least doing git svn fetch/rebase)
Package: git-svn Version: 1:1.8.5.2-1 Severity: normal Dear Maintainer, (This might be a duplicate of #703524, but I don't have a backtrace, so I'm not sure.) Running 'git svn fetch' or 'git svn rebase' results in the git-svn crashing with the following: error: git-svn died of signal 11. These commands were run on a checked out svn repository, which didn't exhibit this error in the past. It seems that the changesets are completely downloaded and applied to the git working copy, b/c compiling succeeds; I have not compared every file to the original source however. To obtain more details, I ran: GIT_TRACE=1 git svn rebase and: PERLDB_OPTS=NonStop frame=5 perl -d $(git --exec-path)/git-svn svn rebase and attached the output. I'm unsure about what to take from these, so any information on how to interpret them is welcome. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) (The only packages not from testing are the kernel, mesa, and iceweasel.) Kernel: Linux 3.12-1-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 git-svn depends on: ii git 1:1.8.5.2-1 ii libsvn-perl 1.7.14-1 ii libterm-readkey-perl 2.31-1 ii libyaml-perl 0.84-1 git-svn recommends no packages. Versions of packages git-svn suggests: pn git-doc none pn subversion none -- 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#689564: backtrace
Once it a while one of those left-over konqueror processes crashes. Below is a backtrace from one of those crashes: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f63afe36760 (LWP 23710))] Thread 3 (Thread 0x7f6399e8e700 (LWP 23711)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f639c4afc0d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f639ce70280) at wtf/FastMalloc.cpp:2499 #2 0x7f639c4afd19 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1622 #3 0x7f63a8d89b50 in start_thread (arg=optimized out) at pthread_create.c:304 #4 0x7f63af6b870d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7f639958d700 (LWP 23712)): #0 0x7f63af6adac3 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=5769) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f63a84c14d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63a84c15f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63ad192296 in QEventDispatcherGlib::processEvents (this=0x20b22c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f63ad1628af in QEventLoop::processEvents (this=this@entry=0x7f639958ce40, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f63ad162b38 in QEventLoop::exec (this=0x7f639958ce40, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f63ad065d70 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f63ad068d0b in QThreadPrivate::start (arg=0x20b1fb0) at thread/qthread_unix.cpp:307 #8 0x7f63a8d89b50 in start_thread (arg=optimized out) at pthread_create.c:304 #9 0x7f63af6b870d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 1 (Thread 0x7f63afe36760 (LWP 23710)): [KCrash Handler] #6 0x7f63ad17bccf in QObject::disconnect (sender=0x2642800, signal=0x0, receiver=0x2277e60, method=0x20e9619 receiveMetaData()) at kernel/qobject.cpp:2891 #7 0x7f639c1a57fe in disconnect (member=0x7f639c77f74f 1receiveMetaData(), receiver=0x2277e60, this=optimized out) at /usr/include/qt4/QtCore/qobject.h:252 #8 WebCore::QNetworkReplyWrapper::resetConnections (this=0x2277e60) at platform/network/qt/QNetworkReplyHandler.cpp:254 #9 0x7f639c1a585d in WebCore::QNetworkReplyWrapper::release (this=0x2277e60) at platform/network/qt/QNetworkReplyHandler.cpp:235 #10 0x7f639c1a59d6 in WebCore::QNetworkReplyHandler::release (this=this@entry=0x2a39280) at platform/network/qt/QNetworkReplyHandler.cpp:419 #11 0x7f639c1a5a2e in WebCore::QNetworkReplyHandler::abort (this=0x2a39280) at platform/network/qt/QNetworkReplyHandler.cpp:407 #12 0x7f639c1a2e29 in WebCore::ResourceHandle::cancel (this=0x7f634fca9d98) at platform/network/qt/ResourceHandleQt.cpp:107 #13 0x7f639bfa66dd in WebCore::PingLoader::~PingLoader (this=0x7f634f72bbe0, __in_chrg=optimized out) at loader/PingLoader.cpp:130 #14 0x7f639bfa6769 in WebCore::PingLoader::~PingLoader (this=0x7f634f72bbe0, __in_chrg=optimized out) at loader/PingLoader.cpp:131 #15 0x7f639c07c3a2 in WebCore::ThreadTimers::sharedTimerFiredInternal (this=0x7f63995c77a8) at platform/ThreadTimers.cpp:112 #16 0x7f63ad17885c in QObject::event (this=0x20ca920, e=optimized out) at kernel/qobject.cpp:1157 #17 0x7f63ac29070c in QApplicationPrivate::notify_helper (this=this@entry=0x1b6f160, receiver=receiver@entry=0x20ca920, e=e@entry=0x7fff91f33280) at kernel/qapplication.cpp:4556 #18 0x7f63ac294b8a in QApplication::notify (this=0x7fff91f33800, receiver=0x20ca920, e=0x7fff91f33280) at kernel/qapplication.cpp:4417 #19 0x7f63adbef8a6 in KApplication::notify (this=0x7fff91f33800, receiver=0x20ca920, event=0x7fff91f33280) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x7f63ad163b5e in QCoreApplication::notifyInternal (this=0x7fff91f33800, receiver=0x20ca920, event=0x7fff91f33280) at kernel/qcoreapplication.cpp:915 #21 0x7f63ad194a52 in sendEvent (event=0x7fff91f33280, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QTimerInfoList::activateTimers (this=0x1b70c90) at kernel/qeventdispatcher_unix.cpp:611 #23 0x7f63ad191c04 in timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:186 #24 timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:180 #25 0x7f63ad191c21 in idleTimerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:233 #26 0x7f63a84c1205 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f63a84c1538 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f63a84c15f4 in g_main_context_iteration () from
Bug#689564: konqueror consumes huges amount of memory and does not quit
Package: konqueror Version: 4:4.8.4-1 Severity: normal Konqueror (with webkit) consumes huge amounts of memory and does not quit even when the windows is closed. My system runs for 3 days now, and I have no Konqueror window open at this moment, yet the first lines in top look like this: top - 22:23:39 up 3 days, 5:28, 5 users, load average: 0.76, 0.79, 0.77 Tasks: 200 total, 1 running, 190 sleeping, 0 stopped, 9 zombie %Cpu(s): 4.1 us, 1.9 sy, 0.0 ni, 94.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3854560 total, 3122544 used, 732016 free,24124 buffers KiB Swap: 8191996 total, 133164 used, 8058832 free, 900956 cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 13899 user 20 0 2301m 534m 44m S 0.0 14.2 42:38.63 konqueror 14443 user 20 0 2076m 363m 47m S 0.0 9.7 32:13.13 konqueror 32635 user 20 0 1764m 188m 38m S 0.3 5.0 14:28.58 konqueror 9816 user 20 0 1758m 175m 42m S 0.0 4.7 2:28.12 konqueror 20711 user 20 0 1588m 110m 39m S 0.3 2.9 2:11.74 konqueror Expected outcome: Konqueror process ends and frees memory when the window is closed. The system is a fresh install of Wheezy/testing and uptodate as of 3 days ago. The hardware is a Thinkpad X201. Any ideas and approaches to get more insight in this are very welcome. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 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 konqueror depends on: ii install-info4.13a.dfsg.1-10 ii kde-baseapps-bin4:4.8.4-1 ii kde-baseapps-data 4:4.8.4-1 ii kde-runtime 4:4.8.4-1 ii libc6 2.13-35 ii libkcmutils44:4.8.4-3 ii libkde3support4 4:4.8.4-3 ii libkdecore5 4:4.8.4-3 ii libkdesu5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkfile4 4:4.8.4-3 ii libkhtml5 4:4.8.4-3 ii libkio5 4:4.8.4-3 ii libkonq5abi14:4.8.4-1 ii libkonqsidebarplugin4a 4:4.8.4-1 ii libkparts4 4:4.8.4-3 ii libqt4-dbus 4:4.8.2+dfsg-2 ii libqt4-qt3support 4:4.8.2+dfsg-2 ii libqt4-xml 4:4.8.2+dfsg-2 ii libqtcore4 4:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libstdc++6 4.7.1-7 ii libx11-62:1.5.0-1 Versions of packages konqueror recommends: ii dolphin 4:4.8.4-1 ii kfind4:4.8.4-1 pn konqueror-nsplugins none Versions of packages konqueror suggests: pn konq-plugins none -- 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#627163: installation-reports: installer hangs on searching drives for installer iso
Package: installation-reports Followup-For: Bug #627163 -- Package-specific info: Boot method: usb-memory Image version: Debian Wheezy DI-b2 and weekly build from 20120926 Date: 20120926 Machine: Thinkpad X201 Partitions: Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000e75fc Device Boot Start End Blocks Id System /dev/sda1 *204812290047 6144000 83 Linux /dev/sda212292094 234441647 1110747775 Extended /dev/sda51229209628676095 8192000 82 Linux swap / Solaris /dev/sda62867814430726143 1024000 83 Linux /dev/sda73072819247112191 8192000 83 Linux /dev/sda847114240 23444164793663704 83 Linux All partitions were created with Debian's fdisk. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: When the installer is searching the harddrive for installer ISO images, it hangs when trying to access sda2. This happens on the automatic install, and in the expert install if the automatic drive detection is chosen. Selecting specifically the usb memory with the ISO image makes the installer successfully find the image. Deleting all partitions except sda1 makes the installer find the ISO image. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655152: [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times
Hi Jonathan, Finally I got around to test this patch. While the system if fine for office work, cloning linux.git or compiling kernels takes hours. Please test the attached patch against a 3.2.y kernel, for example using the following instructions: Done with testing, results below. These instructions were really good and easy to use, thanks for that! 3. configure, build, test: git checkout stable/linux-3.2.y cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot ...test test test ... I compiled 3.2.28, and it reproduces the bug within the first minute after boot and the logs are full of the error message. 4. try the patch: cd linux git am -3sc /path/to/the/patch make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot ... test test test ... The patch fixes the problem. I've run more than 30 minutes without a single occurrence of the error message in the logs. Everything I tested seems to be still working, Graphics, Suspend, etc. Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655152: patch for [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times
Hi, Please backport the patch merged in Linux to the Debian kernel. The patch is in the upstream 3.5 kernel and references the bug freedesktop.org bug report: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=c2798b19bac2538393fc932bfbe59807a4734b3e https://bugs.freedesktop.org/show_bug.cgi?id=41793#c5 With the current Debian kernel (I'm using 3.2.21-3) without the patch, I still get lots of messages of drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times which increased the size of the log files to gigabytes within a few days: -rw-r- 1 root adm 489M Aug 18 11:26 syslog -rw-r- 1 root adm 487M Aug 18 11:26 kern.log Thanks, Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684634: xserver-xorg-video-intel: viewing pic in browser reboots laptop
- Ursprüngliche Nachricht - Von: Julien Cristau Gesendet: 18.08.12 11:33 Uhr An: Sten Heinze, 684...@bugs.debian.org Betreff: Re: Bug#684634: xserver-xorg-video-intel: viewing pic in browser reboots laptop On Sun, Aug 12, 2012 at 02:20:58 -0500, Sten Heinze wrote: Package: xserver-xorg-video-intel Version: 2:2.19.0-5 Severity: normal Dear Maintainer, * What led up to the situation? Boot laptop. Log into KDE. Activate external monitor (1280x1024) in addition to internal screen (1280x800). External monitor is right of internal screen, internal screen is primary output. Open Konqueror browser, load picture from link below. Default view is picture zoomed out to show it completely. Laptop is a Thinkpad X201 with Core i5 520M with integrated graphics (Arrandale). Debian/Wheezy is installed and uptodate as of a couple days ago. The picture used is: http://photojournal.jpl.nasa.gov/jpeg/PIA16051.jpg (resolution 29481x4144, size 8.6MB) * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? Trying to zoom to show picture at 100% leads to reproducible immediate reboot. That doesn't sound like a userspace bug. Have you tried different (older/newer) kernel versions? Cheers, Julien Not yet, but I will test and report back. Let me know if you are interested in me testing a particular kernel version, otherwise I will try debian snapshots and experimental kernels. Thanks, Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684953: cantor: Crash when trying to get latex rendered output in Cantor
Package: cantor Version: 4:4.8.4-2 Severity: normal I did a fresh install of cantor and cantor-backend-[maxima,kalgebra] today. In trying to display a LaTeX rendered formula in Cantor I did the following steps: 1. Type 'expand((x+y)^2);' and evaluate it. This will return the latex code that need to be rendered: \begin{eqnarray*}y^2+2\,x\,y+x^2\end{eqnarray*} 2. Insert a new text entry, write $$ (latex from above) $$ and evaluate it. This makes this text (in the text entry) disappear, just the empty box frame is left. 3. Trying to click into it leads to a crash (and Dr. Konqi). The packages recommended by cantor, texlive-latex-base and texlive-binaries, are installed. (In fact, Lyx is installed with a pretty complete set of Texlive packages.) After installing the debug packages (for cantor and qt) I got a couple (not so good) backtraces: Application: Cantor (cantor), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [KCrash Handler] #6 QTextFrame::firstPosition (this=this@entry=0xa3ed6a0) at text/qtextobject.cpp:489 #7 0xb68b8b6d in QTextFrame::firstCursorPosition (this=0xa3ed6a0) at text/qtextobject.cpp:467 #8 0xb2626f35 in WorksheetEntry::firstPosition (this=0xa3142a0) at ../../src/worksheetentry.cpp:86 #9 0xbfbc014c in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Application: Cantor (cantor), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [KCrash Handler] #6 0xb6865afa in fragment (index=16777488, this=0xa4) at ../../include/QtGui/private/../../../src/gui/text/qfragmentmap_p.h:107 #7 position (this=0xa4, field=0, node=16777488) at ../../include/QtGui/private/../../../src/gui/text/qfragmentmap_p.h:120 #8 position (field=0, node=16777488, this=0xa4) at ../../include/QtGui/private/../../../src/gui/text/qfragmentmap_p.h:860 #9 QTextFrame::firstPosition (this=this@entry=0x89e7dc0) at text/qtextobject.cpp:491 #10 0xb6865b6d in QTextFrame::firstCursorPosition (this=0x89e7dc0) at text/qtextobject.cpp:467 #11 0xb25d3f35 in WorksheetEntry::firstPosition (this=0x8b8e5a8) at ../../src/worksheetentry.cpp:86 #12 0xbf9b3adc in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-486 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 cantor depends on: ii kde-runtime 4:4.8.4-1 ii libc6 2.13-33 ii libkdecore5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkio5 4:4.8.4-3 ii libknewstuff3-4 4:4.8.4-3 ii libkparts4 4:4.8.4-3 ii libktexteditor4 4:4.8.4-3 ii libqt4-xml 4:4.8.2-2+b1 ii libqt4-xmlpatterns 4:4.8.2-2+b1 ii libqtcore4 4:4.8.2-2+b1 ii libqtgui4 4:4.8.2-2+b1 ii libspectre1 0.2.6-2 ii libstdc++6 4.7.1-2 Versions of packages cantor recommends: ii cantor-backend-kalgebra 4:4.8.4-2 ii texlive-binaries 2012.20120628-2 ii texlive-latex-base 2012.20120611-3 Versions of packages cantor suggests: ii cantor-backend-maxima 4:4.8.4-2 pn cantor-backend-octave none pn cantor-backend-qalculate none pn cantor-backend-r none pn cantor-backend-sage none pn cantor-backend-scilab none -- 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#684634: xserver-xorg-video-intel: viewing pic in browser reboots laptop
Hi, Some more information: --The external monitor is not necessary. The crash occurs just with the internal screen. --Zooming the picture is not enough, it seems. I only get reliable crashes (and reboots) if I move the mouse while clicking i.e. start dragging the image in the browser. --The image only shows the reported resolution (29481x4144) if loaded from http://photojournal.jpl.nasa.gov/catalog/PIA16051 by using the Full-Res JPEG link. If wget is used to download the image, it's resolution is shown as 7296x1036. --The intel driver in Debian/Experimental (2:2.20.2-1) crashes as well. (However, so far I've only managed to crash this version with the external monitor attached.) Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683477: phonon-backend-vlc: No sound in KDE or Amarok
Do you have pulseaudio installed by chance? Yes, and pulseaudio itself works. Running e.g. 'paplay /usr/share/sounds/KDE-Sys-Log-In.ogg' plays correctly. I also tried vlc directly, and while running 'vlc /usr/share/sounds/KDE-Sys-Log-In.ogg' produces sound, only the first few seconds are correct, then it speeds up and plays too fast until the end. Not sure if that is related or different. If possible, ask on IRC on #debian-kde in oftc.net mentioning this bug (and please be patient, we may take some time to reply :-) ) I'm there and I did ask, but I can do it again. Thanks for your reply! Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683477: phonon-backend-vlc: No sound in KDE or Amarok
Package: phonon-backend-vlc Version: 0.5.0+14.g382da0d-2 Severity: normal Dear Maintainer, * What led up to the situation? I assume some update, but I am not sure. Sound in KDE is not working for a few weeks now. It was working about a month ago. I tried to find which updated deb caused the problem, but could not pinpoint a single one (both vlc and the phonon backend had minor updates since it worked last). * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? Boot laptop, log in. No sound at login or at any other time. No sound in System Settings or Amarok. However, sound works when paplay (play command of pulseaudio) is used. Sound sort of works when vlc is used on the command line (some problems with the speed of which the sound is played though with dropped buffers). Sound in KDE works with the gstreamer backend, sound in Amarok does not work with gstreamer. Another, newly created account did not show any different behavior, no sound in KDE or Amarok with VLC. * What outcome did you expect instead? Sound. Any pointers on where to look or what to test are highly appreciated. The system is a up-to-date Debian/Wheezy; only boost packages (1.50.0) are from unstable, no packages from experimental. Hardware is a Thinkpad X201 laptop: $ lspci |grep Audio 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 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 phonon-backend-vlc depends on: ii libc6 2.13-33 ii libphonon4 4:4.6.0.0-2 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libstdc++6 4.7.1-2 ii libvlc5 2.0.2-2 ii vlc-nox 2.0.2-2 Versions of packages phonon-backend-vlc recommends: pn vlc none phonon-backend-vlc 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#681169: owncloud: unable to create additional users from the owncloud webinterface admin settings
Package: owncloud Version: 4.0.4debian-1 Severity: normal Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? Install owncloud from the deb package, set it up, log in as admin, go to settings, users, and try to create additional users. * What was the outcome of this action? No users are created. This is owncloud upstream bug oc-1164. Commenting out the line described in the upstream bug report fixes the problem. (However this line was a fix for another bug, oc-1098, which may reappear, but is less important in my opinion.) -- System Information: Debian Release: wheezy APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679997: coreutils: 'cp infile outfile' fill up all mem with 180gb sparse infile on xfs
Package: coreutils Version: 8.13-3.2 Severity: normal Dear Maintainer, * What led up to the situation? I created a sparse file for a virtual disk using 'virsh create-vol-as'. The file was 180gb with ~4gb used after installing the vm. The setup is a Debian Wheezy (uptodate yesterday when I tried this) with an XFS filesystem. The XFS filesystem itself is 387gb, so it would have enough space should the sparse file fill up. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? I wanted to copy this file using 'cp infile outfile'. This lead to the system filling up all memory and even killing half the running processes (gettys, sshd, etc.). Calling 'cp --sparse=always infile outfile' to ensure only 4gb would be copied made no difference. In both cases outfile used more blocks than 4gb even before the copy process could finish (it got killed too). * What outcome did you expect instead? I expected a sparse copy outfile of infile that is 180gb in size using only ~4gb in actual data. I did not expect this huge memory consumption at all. PS. I am not sure if coreutils is the right package to file the bug against. I chose is because cp is part of this package, but additional tests of copying sparse files on a RHEL5 with ext3 filesystem worked fine. So the problem could be in XFS intead. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 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 coreutils depends on: ii dpkg 1.16.3 ii install-info 4.13a.dfsg.1-10 ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libc6 2.13-33 ii libselinux1 2.1.9-5 coreutils recommends no packages. coreutils 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#677822: nut: Old /etc/init.d/nut is not removed, /etc/init.d/nut-{server, client} fail to start
Package: nut Version: 2.6.4-1 Severity: minor Dear Maintainer, * What led up to the situation? Upgrate of nut: 2012-06-16 14:50:02 upgrade nut:all 2.6.3-1 2.6.4-1 * What exactly did you do (or not do) that was effective (or ineffective)? Reboot. * What was the outcome of this action? nut init scripts failed. /etc/init.d/nut completed successfully and started everything (drv, upsd, upsmon), but subsequently started /etc/init.d/nut-{server,client} failed because of upsd and upsmon. Checking the status after logging in shows that all parts are running. * What outcome did you expect instead? Successful start of all init scripts as before the upgrade. * Fix? I removed the /etc/init.d/nut init script (update-rc.d nut remove) as it seemed from an earlier time and possibly left over: $ ls -l /etc/init.d/nut* -rwxr-xr-x 1 root root 5345 Jan 24 06:17 /etc/init.d/nut -rwxr-xr-x 1 root root 5273 Jun 6 14:06 /etc/init.d/nut-client -rwxr-xr-x 1 root root 5271 Jun 6 14:06 /etc/init.d/nut-server This fixed the problem, subsequent reboots completed without failure. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589778: linux-image-2.6.32-5-686: prism2.5: hostap loads 90s
Hi Ben, Thanks for your reply. The laptop with this wireless network card was replaced in the meantime, so this issue is solved for me. Sten Original-Nachricht Datum: Fri, 13 Jan 2012 03:26:33 + Von: Ben Hutchings b...@decadent.org.uk An: Sten Heinze sten.hei...@gmx.de CC: 589...@bugs.debian.org Betreff: Re: Bug#589778: linux-image-2.6.32-5-686: prism2.5: hostap loads 90s On Wed, 2010-07-21 at 10:10 +0200, Sten Heinze wrote: On Wednesday 21 July 2010 01:32:38 Ben Hutchings wrote: On Wed, 2010-07-21 at 01:04 +0200, Sten Heinze wrote: Package: linux-2.6 Version: 2.6.32-15 and 2.6.32-17 Severity: minor After upgrading from Lenny to Squeeze loading the hostap* modules for the built-in prism2.5 wireless network card need ~90s to load (I think loading is done by udev) and thus extend the boot process by this time. It is quite annoying to have to wait twice as long as the boot process usually takes, e.g. if the orinoco module for this card is loaded (but no connection is possible with the orinoco module). [...] Please send the file /etc/udev/rules.d/70-persistent-net.rules from this system. Attached. Sten I'm sorry about this ridiculously belated reply. I think the problem is this entry: # PCI device 0x1260:0x3873 (orinoco_pci) SUBSYSTEM==net, DRIVERS==?*, ATTR{address}==00:20:e0:8d:ea:db, NAME=eth2 which now matches two different network devices, initally created as 'wifi0' and 'wlan0': [7.831480] hostap_pci :02:02.0: PCI INT A - Link[LNKC] - GSI 11 (level, low) - IRQ 11 [7.833476] hostap_pci: Registered netdevice wifi0 [7.833487] wifi0: Original COR value: 0x21 [8.038478] prism2_hw_init: initialized in 200 ms [8.039317] wifi0: NIC: id=0x8013 v1.0.0 [8.039530] wifi0: PRI: id=0x15 v1.1.1 [8.039735] wifi0: STA: id=0x1f v1.5.6 [8.044622] wifi0: Intersil Prism2.5 PCI: mem=0xec00, irq=11 [8.053279] wifi0: registered netdevice wlan0 [8.094549] udev: renamed network interface wifi0 to eth2 udev's net device naming script is a bit dumb: when it deals with 'wlan0' it assumes that the device already named 'eth2' (originally 'wifi0') is being dealt with in parallel and is going to get renamed to something else. Eventually it gives up waiting. The simple thing to do is just to delete that entry; the current version of udev should automatically generate new entries with the appropriate qualifying attributes in addition to the MAC address. Unfortunately I don't think there's any good way to make this happen automatically on upgrade. Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584905: plasma-netbook not auto-starting on a fresh install
Hi, I experienced this bug on a fresh squeeze install (2 days ago). Removing the Hidden=true from plasma-netbook.desktop (as introduced by the kubuntu-patch?) seems to help and the netbook shell comes up on every start after this change. I am not sure that this is the correct way to solve this, as I haven't tested what happens with plasma-desktop and -netbook installed. Are both started if none is hidden? It might be better to try fixing the kcm module, as aseigo pointed out that an unselected plasma-shell should have Hidden=true. (The drop-down list for the workspace form-factor is systemsettings is disabled for me though.) Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589778: linux-image-2.6.32-5-686: prism2.5: hostap loads 90s
On Wednesday 21 July 2010 01:32:38 Ben Hutchings wrote: On Wed, 2010-07-21 at 01:04 +0200, Sten Heinze wrote: Package: linux-2.6 Version: 2.6.32-15 and 2.6.32-17 Severity: minor After upgrading from Lenny to Squeeze loading the hostap* modules for the built-in prism2.5 wireless network card need ~90s to load (I think loading is done by udev) and thus extend the boot process by this time. It is quite annoying to have to wait twice as long as the boot process usually takes, e.g. if the orinoco module for this card is loaded (but no connection is possible with the orinoco module). [...] Please send the file /etc/udev/rules.d/70-persistent-net.rules from this system. Attached. Sten # This file was automatically generated by the /lib/udev/write_net_rules # program, probably run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # MAC addresses must be written in lowercase. # PCI device 0x8086:0x1031 (e100) SUBSYSTEM==net, DRIVERS==?*, ATTR{address}==00:d0:59:c1:49:b3, NAME=eth1 # PCI device 0x1260:0x3873 (orinoco_pci) SUBSYSTEM==net, DRIVERS==?*, ATTR{address}==00:20:e0:8c:d5:6a, NAME=eth0 # PCI device 0x1260:0x3873 (orinoco_pci) SUBSYSTEM==net, DRIVERS==?*, ATTR{address}==00:20:e0:8d:ea:db, NAME=eth2 # PCI device 0x168c:0x0013 (ath5k_pci) SUBSYSTEM==net, DRIVERS==?*, ATTR{address}==00:15:6d:10:33:bd, ATTR{type}==1, NAME=wlan0 # PCI device 0x1260:0x3890 (p54pci) SUBSYSTEM==net, ACTION==add, DRIVERS==?*, ATTR{address}==00:09:5b:c9:5c:d3, ATTR{dev_id}==0x0, ATTR{type}==1, KERNEL==wlan*, NAME=wlan1
Bug#589778: linux-image-2.6.32-5-686: prism2.5: hostap loads 90s
Package: linux-2.6 Version: 2.6.32-15 and 2.6.32-17 Severity: minor After upgrading from Lenny to Squeeze loading the hostap* modules for the built-in prism2.5 wireless network card need ~90s to load (I think loading is done by udev) and thus extend the boot process by this time. It is quite annoying to have to wait twice as long as the boot process usually takes, e.g. if the orinoco module for this card is loaded (but no connection is possible with the orinoco module). This problem occurs with the kernel versions in testing (2.6.32-15) and unstable (2.6.32-17). With a vanilla 2.6.34.1 the boot process does not finish because the kernel get stuck in soft lockups: BUG: soft lockup - CPU#0 stuck for 61s! Updating the prism2.5 firmware from 1.4.3 to 1.4.9 or 1.5.6 does not help. (1.7.4 does not help either and prevents the card from connecting.) Blacklisting the hostap* modules (the orinoco modules are already blacklisted by the hostap-utils package) prevents all modules from loading which dramatically decreases the boot time. Manually loading the modules shows a bunch of messages in dmesg (which do not help me finding a solution), it still nearly completely block the whole system (but top does not show any number significantly above 0% except idle) and a connection is not possible. 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Actiontec Electronics Inc Device 0406 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at ec00 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: hostap_pci hostap_pci 34480 2 hostap 76764 1 hostap_pci lib802112870 3 lib80211_crypt_wep,hostap_pci,hostap -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux linux-image-2.6.32-5-686 2.6.32-17 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-5-686 depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii initramfs-tools [linux-initra 0.97.2 tools for generating an initramfs ii linux-base2.6.32-17 Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-686 recommends: ii firmware-linux-free 2.6.32-15 Binary firmware for various driver ii libc6-i6862.11.2-2 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.32-5-686 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.32 none (no description available) -- 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#488283: libgl1-mesa-glx: drmMap of framebuffer failed, reverting to software rendering
On Tuesday 29 June 2010 16:41:29 Julien Cristau wrote: On Fri, Jun 27, 2008 at 17:10:07 +0200, Sten Heinze wrote: Package: libgl1-mesa-glx Version: 7.0.3-1 Severity: important Since my last update I noticed a immense slowdown in the graphics performance. Even switching desktops needs up to several seconds. Looking into Xorg.0.log I found: (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE) AIGLX: reverting to software rendering Is this still reproducible with a more recent stack? Hi Julien, No, it's not reproducable anymore. The versions currently in testing/squeeze work fine: mesa-common-dev/testing uptodate 7.8.1-1 xserver-xorg-video-intel/testing uptodate 2:2.9.1-4 Thanks, Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574072: apt-get upgrade re-upgrades same packages over and over (to same already installed version)
Am Mittwoch 17 März 2010 15:04:56 schrieb David Kalnischkies: 2010/3/17 Sten Heinze sten.hei...@gmx.de: Back to the problem itself: The version merger in apt is a bit broken if multiply versions with different hashes are available. In your case two versions are available: the official and your rebuilt - now apt tries to merge the status file and doesn't find the right version and therefore creates a new one: This triggers the local and online package with the same version but different hash - reinstall it feature -- in an endless loop as it will reinstall version 2, but compares in the next run only against version 1 leading again to a version 3… This bug should be fixed by applying the patch from #351056 [0]. I have therefore optimistically merged your bug to this group and the changelog will close them all together as most (if not all) are caused by this bug or no longer reproducible with newer APT… … or caused by the reinstall feature which if it runs only one time is really a feature as it is a simple matter of pinning in action. I compiled my own apt version 0.7.25.3+patch r1962 (and I had to add the build-deps of r1959 to make it build, both from the mentioned bazaar repo), and it fixes it: # apt-cache policy libqt4-designer libqt4-designer: Installiert: 4:4.6.2-1 Kandidat: 4:4.6.2-1 Versions-Tabelle: 4:4.6.2-1 0 1 http://ftp.de.debian.org experimental/main Packages *** 4:4.6.2-1 0 500 file: ./ Packages 100 /var/lib/dpkg/status 4:4.5.3-4 0 500 http://ftp.de.debian.org testing/main Packages 50 http://ftp.de.debian.org unstable/main Packages 4.4.3-1+lenny1 0 500 http://security.debian.org stable/updates/main Packages 4.4.3-1 0 500 http://ftp.de.debian.org stable/main Packages On apt-get upgrade, no upgrade of qt to the already installed version is happening anymore. Thanks a lot! Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574072: apt-get upgrade re-upgrades same packages over and over (to same already installed version)
Am Mittwoch 17 März 2010 18:53:34 schrieb Sten Heinze: I compiled my own apt version 0.7.25.3+patch r1962 (and I had to add the build-deps of r1959 to make it build, both from the mentioned bazaar repo), and it fixes it: # apt-cache policy libqt4-designer libqt4-designer: Installiert: 4:4.6.2-1 Kandidat: 4:4.6.2-1 Versions-Tabelle: However, after having the system up for some time (hours), I ran into: # apt-get update [..] OK http://ftp.de.debian.org experimental/contrib Packages Speicherzugriffsfehleresen... 27% This continues after it started, independent which program or parameter I try, apt-get update, apt-get upgrade, apt-cache. Dpkg helped to get apt working again, a restart did not fix it. # dpkg -i /var/cache/apt/archives/apt-utils_0.7.25.3_i386.deb # dpkg -i /var/cache/apt/archives/apt_0.7.25.3_i386.deb # apt-get update [..] OK http://ftp.de.debian.org experimental/contrib Packages Paketlisten werden gelesen... Fertig Obviously I'm now back at my original problem: # apt-cache policy libqt4-designer libqt4-designer: Installiert: 4:4.6.2-1 Kandidat: 4:4.6.2-1 Versions-Tabelle: 4:4.6.2-1 0 1 http://ftp.de.debian.org experimental/main Packages 4:4.6.2-1 0 500 file: ./ Packages *** 4:4.6.2-1 0 100 /var/lib/dpkg/status 4:4.5.3-4 0 500 http://ftp.de.debian.org testing/main Packages 50 http://ftp.de.debian.org unstable/main Packages 4.4.3-1+lenny1 0 500 http://security.debian.org stable/updates/main Packages 4.4.3-1 0 500 http://ftp.de.debian.org stable/main Packages Upgrading to my patched version of apt keeps apt working and fixes my problem again: # apt-get install apt apt-utils # apt-get update [..] OK http://ftp.de.debian.org experimental/contrib Packages Paketlisten werden gelesen... Fertig I am unsure by what this is triggered, since I had it twice since starting to use my patched apt-version. How can I find the cause? The apt-version in experimental does not have the patch [0] yet, correct? Sten [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351056#87 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574072: apt-get upgrade re-upgrades same packages over and over (to same already installed version)
Am Dienstag 16 März 2010 15:33:49 schrieb Julian Andres Klode: On Tue, Mar 16, 2010 at 05:27:48AM +0100, Sten Heinze wrote: Qt packages of the same version are in my local repository (where I test) and in experimental, but I expect this not to be a problem, since same versions can also occur e.g. in testing and unstable. If they are different, then it is a problem (see below) Qt package currently in my local repository are compiled from the same source as the experimental ones. No modifications are made to the source, so there should be no difference. # apt-cache policy libqt4-designer libqt4-designer: Installiert: 4:4.6.2-1 Kandidat: 4:4.6.2-1 Versions-Tabelle: 4:4.6.2-1 0 1 http://ftp.de.debian.org experimental/main Packages 4:4.6.2-1 0 500 file: ./ Packages *** 4:4.6.2-1 0 100 /var/lib/dpkg/status 4:4.5.3-4 0 500 http://ftp.de.debian.org testing/main Packages 50 http://ftp.de.debian.org unstable/main Packages 4.4.3-1+lenny1 0 500 http://security.debian.org stable/updates/main Packages 4.4.3-1 0 500 http://ftp.de.debian.org stable/main Packages If I remove either my local or the experimental deb-line (or both), it works fine. This looks very similar to reports of old apt versions, like #351056, except I use the current testing/squeeze version. 4:4.6.2-1 entries should be a single entry normally. If you have modified and rebuild the local package, change the version number to e.g. 4:4.6.2-1shze1 and it may work. If two packages have the same version number, they should be completely equal; having two different packages with the same version number is not really supported. If your local packages are completely the same as the remote ones, I don't know. How do I find out if apt sees them really as the same? I've seen some checksums in the apt-cache output attached, but I can't figure out how to get them from the Debian repositories, maybe grep-dctrl or something else? I've attached the output of apt-cache show -a libqt4-designer. Unfortunately I don't know where to find status/Packages file. Do you mean the Packages.gz of my local repository? For creating the repository I just have small script to run (with some helper commands): dpkg-scanpackages binary/ /dev/null | gzip Packages.gz dpkg-scansources source/ | gzip Sources.gz Sorry for the large number of questions. Thanks, Sten Package: libqt4-designer Priority: optional Section: libs Installed-Size: 10256 Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Architecture: i386 Source: qt4-x11 Version: 4:4.6.2-1 Replaces: libqt4-gui ( 4.4.0~beta1-1) Depends: libc6 (= 2.1.3), libgcc1 (= 1:4.1.1), libqt4-script (= 4:4.6.2-1), libqt4-xml (= 4:4.6.2-1), libqtcore4 (= 4:4.6.2-1), libqtgui4 (= 4:4.6.2-1), libstdc++6 (= 4.1.1) Conflicts: libqt4-gui ( 4.4.0~beta1-1) Filename: pool/main/q/qt4-x11/libqt4-designer_4.6.2-1_i386.deb Size: 5635914 MD5sum: b495e06426bbba654faf46bab04dbe9e SHA1: a4d13920ec7b9ecf91ce5d27845c5f986db4192b SHA256: 7ebd4f3bbf19ea585fb749f291eb42ad53411da13ee482a8864e2dea7fd621c7 Description: Qt 4 designer module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. . The QtDesigner module provides classes that allow you to create your own custom widget plugins for Qt Designer, and classes that enable you to access Qt Designer's components. Homepage: http://www.qtsoftware.com Package: libqt4-designer Source: qt4-x11 Version: 4:4.6.2-1 Architecture: i386 Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Installed-Size: 10276 Depends: libc6 (= 2.1.3), libgcc1 (= 1:4.1.1), libqt4-script (= 4:4.6.2-1), libqt4-xml (= 4:4.6.2-1), libqtcore4 (= 4:4.6.2-1), libqtgui4 (= 4:4.6.2-1), libstdc++6 (= 4.1.1) Conflicts: libqt4-gui ( 4.4.0~beta1-1) Replaces: libqt4-gui ( 4.4.0~beta1-1) Filename: binary//libqt4-designer_4.6.2-1_i386.deb Size: 5648940 MD5sum: ac8c7b1908e258618fdfa4ddb29f07be SHA1: dc1783675f86e8f28c38ac07e98fb7024aadb759 SHA256: 99dbba42aeb389e0f26d857121352bc9bcbe7570c52d7c211d4efd1ae5422695 Section: libs Priority: optional Homepage: http://www.qtsoftware.com Description: Qt 4 designer module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. . The QtDesigner module provides classes that allow you to create your own custom widget plugins for Qt Designer, and classes that enable you to access Qt Designer's components. Package: libqt4-designer Status: install ok installed Priority: optional Section: libs Installed-Size: 10276 Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Architecture: i386 Source: qt4-x11 Version: 4:4.6.2-1 Replaces: libqt4-gui ( 4.4.0~beta1-1) Depends: libc6 (= 2.1.3), libgcc1 (= 1:4.1.1), libqt4
Bug#574072: apt-get upgrade re-upgrades same packages over and over (to same already installed version)
Package: apt Version: 0.7.25.3 Severity: normal apt-get upgrade does upgrade already installed packages to the same version again and again even without running apt-get update in between and without new versions becoming available. # LANG=C apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: libgettext-ruby1.8 libgl1-mesa-dri libsoprano4 soprano-daemon The following packages will be upgraded: libphonon4 libqt4-designer libqt4-qt3support libqt4-script libqt4-webkit libqt4-xmlpatterns libqtcore4 libqtgui4 phonon-backend-xine 9 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0B/23.9MB of archives. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? WARNING: The following packages cannot be authenticated! libqtcore4 libqtgui4 libphonon4 libqt4-script libqt4-designer libqt4-qt3support libqt4-xmlpatterns libqt4-webkit phonon-backend-xine Install these packages without verification [y/N]? y locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Parsing Found/Fixed information... Done (Reading database ... 69318 files and directories currently installed.) Preparing to replace libqtcore4 4:4.6.2-1 (using ...//libqtcore4_4.6.2-1_i386.deb) ... Unpacking replacement libqtcore4 ... Preparing to replace libqtgui4 4:4.6.2-1 (using ...//libqtgui4_4.6.2-1_i386.deb) ... Unpacking replacement libqtgui4 ... Preparing to replace libphonon4 4:4.6.0really4.3.80-1 (using .../libphonon4_4.6.0really4.3.80-1_i386.deb) ... Unpacking replacement libphonon4 ... Preparing to replace libqt4-script 4:4.6.2-1 (using .../libqt4-script_4.6.2-1_i386.deb) ... Unpacking replacement libqt4-script ... Preparing to replace libqt4-designer 4:4.6.2-1 (using .../libqt4-designer_4.6.2-1_i386.deb) ... Unpacking replacement libqt4-designer ... Preparing to replace libqt4-qt3support 4:4.6.2-1 (using .../libqt4-qt3support_4.6.2-1_i386.deb) ... Unpacking replacement libqt4-qt3support ... Preparing to replace libqt4-xmlpatterns 4:4.6.2-1 (using .../libqt4-xmlpatterns_4.6.2-1_i386.deb) ... Unpacking replacement libqt4-xmlpatterns ... Preparing to replace libqt4-webkit 4:4.6.2-1 (using .../libqt4-webkit_4.6.2-1_i386.deb) ... Unpacking replacement libqt4-webkit ... Preparing to replace phonon-backend-xine 4:4.6.0really4.3.80-1 (using .../phonon-backend-xine_4.6.0really4.3.80-1_i386.deb) ... Unpacking replacement phonon-backend-xine ... Setting up libqtcore4 (4:4.6.2-1) ...
Bug#567681: Patch: Allow options to be passed to btrfsck
This patch makes btrfsck ignore (for now) options passed to it. This makes btrfsck runs on startup not failing. I was asked to post my patch here by the Debian Maintainer of btrfs-tools. Background: On Startup all filesystem (on a Debian system) are fsck'ed. A option to allow non-interactive filesystem checks on startup is passed to fsck, usually -a or -y. Currently btrfsck expects the device as the only parameter and fails if run with any option e.g. btrfsck -a /dev/hda1 (returns error code 1). My patch fixes this by allowing options to be passed, although all options are ignored at the moment. (The attached patch is slightly improved from the one I sent to the Debian bug report [1] before.) Please comment if this is acceptable for inclusion in btrfsck. If not, I would be happy to improve the patch. Thanks, Sten [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567681: Patch: Allow options to be passed to btrfsck
[This time with the patch attached.] [Please CC: me, as I am not subscribed to the linux-btrfs mailing list.] This patch makes btrfsck ignore (for now) options passed to it. This makes btrfsck runs on startup not failing. I was asked to post my patch here by the Debian Maintainer of btrfs-tools. Background: On Startup all filesystem (on a Debian system) are fsck'ed. A option to allow non-interactive filesystem checks on startup is passed to fsck, usually -a or -y. Currently btrfsck expects the device as the only parameter and fails if run with any option e.g. btrfsck -a /dev/hda1 (returns error code 1). My patch fixes this by allowing options to be passed, although all options are ignored at the moment. (The attached patch is slightly improved from the one I sent to the Debian bug report [1] before.) Please comment if this is acceptable for inclusion in btrfsck. If not, I would be happy to improve the patch. Thanks, Sten [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681 Index: btrfs-tools/btrfsck.c === --- btrfs-tools.orig/btrfsck.c 2010-02-08 05:44:01.037134357 +0100 +++ btrfs-tools/btrfsck.c 2010-02-11 05:02:15.469358404 +0100 @@ -2807,7 +2807,7 @@ static void print_usage(void) { - fprintf(stderr, usage: btrfsck dev\n); + fprintf(stderr, usage: btrfsck [option] dev\n); fprintf(stderr, %s\n, BTRFS_BUILD_VERSION); exit(1); } @@ -2821,9 +2821,24 @@ if (ac 2) print_usage(); + char *file = av[ac - 1]; + int pos; + for( pos = 1; pos ac; ++pos) + { + /* ignore all options for now, stop at first device found */ + if (av[pos][0] != '-') + { + file = av[pos]; + break; + } + } + + /* print device fsck'ed */ + printf(%s: , file); + radix_tree_init(); cache_tree_init(root_cache); - root = open_ctree(av[1], 0, 0); + root = open_ctree(file, 0, 0); if (root == NULL) return 1;
Bug#567681: btrfs-tools: please add -a to fsck.btrfs
Hi, I have attached a patch (which goes on top of 0.19-10) that makes btrfsck ignore all options (all parameters that are not a device to scan). While it might not be perfect it makes btrfsck run on boot without errors for me. Let me know if it needs changes or improvements. Thanks, Sten Index: btrfs-tools/btrfsck.c === --- btrfs-tools.orig/btrfsck.c 2010-02-08 05:37:15.097132451 +0100 +++ btrfs-tools/btrfsck.c 2010-02-08 05:38:11.585242066 +0100 @@ -2821,9 +2821,21 @@ if (ac 2) print_usage(); + char *file = av[ac - 1]; + int pos; + for( pos = 1; pos ac; ++pos) + { + /* ignore all options for now, stop at first device found */ + if (av[pos][0] != '-') + { + file = av[pos]; + break; + } + } + radix_tree_init(); cache_tree_init(root_cache); - root = open_ctree(av[1], 0, 0); + root = open_ctree(file, 0, 0); if (root == NULL) return 1;
Bug#567681: btrfs-tools: fsck.btrfs dies on startup with could not open -a
Package: btrfs-tools Version: 0.19-8 Severity: normal After conversion of a partition (with btrfs-convert) to btrfs and changes to fstab, my system boots fine with only one error message: Could not open -a fsck did with exit status 1. This is caused by a call to fsck.btrfs, which does not support -a. Please add the -a option to fsck.btrfs. Thanks, Sten -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551769: glibc: /usr/bin/perl: double free or corruption
I tried a couple things today. On a different system (also Debian testing, but not recently updated) I had git-svn (always using the same command git svn clone https://repository) working w/ following versions: $ apt-show-versions |egrep ^perl-base\|subversion\|git-core git-core/testing uptodate 1:1.6.3.3-2 perl-base/testing uptodate 5.10.0-25 subversion/testing uptodate 1.6.3dfsg-1 So I upgraded subversion to: subversion/testing uptodate 1.6.5dfsg-1 This caused git-svn to crash. Downgrading subversion made it work again. Then I went back to my main system, where it crashed using versions: $ apt-show-versions |egrep ^perl-base\|subversion\|git-core git-core/testing uptodate 1:1.6.3.3-2 perl-base/testing uptodate 5.10.1-5 subversion/testing uptodate 1.6.5dfsg-1 I downgraded subversion: subversion/testing upgradeable from 1.6.3dfsg-1 to 1.6.5dfsg-1 And git-svn works! Just a note: I have seen Ubuntu 9.10 Beta using subversion 1.6.5dfsg-1ubuntu1 with which git-svn works too, but I did not look into the differences. Maybe that helps finding the cause. Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551769: glibc: /usr/bin/perl: double free or corruption
Package: perl-base Version: 5.10.1-5 Severity: normal When running git svn clone for an repository otherwise working with svn, I get after a few files are downloaded from the repository: Temp file with moniker 'svn_delta' already in use at /usr/share/perl5/Git.pm line 1022. *** glibc detected *** /usr/bin/perl: double free or corruption (!prev): 0x097598d0 *** === Backtrace: = /lib/i686/cmov/libc.so.6[0xb7ea48f4] /lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7ea6896] /usr/lib/libapr-1.so.0(apr_allocator_destroy+0x44)[0xb7b1b11e] /usr/lib/libapr-1.so.0(apr_pool_destroy+0x139)[0xb7b1bcaf] /usr/lib/libapr-1.so.0(apr_pool_terminate+0x46)[0xb7b1b80b] /usr/lib/libapr-1.so.0(apr_terminate+0x30)[0xb7b1e760] /usr/lib/perl5/auto/SVN/_Core/_Core.so(_wrap_apr_terminate+0x8f)[0xb7be9faf] /usr/bin/perl(Perl_pp_entersub+0x541)[0x80d9491] /usr/bin/perl(Perl_runops_standard+0x19)[0x80d7a59] /usr/bin/perl(Perl_call_sv+0x450)[0x8078e60] /usr/bin/perl(Perl_call_list+0x2c7)[0x80792b7] /usr/bin/perl(perl_destruct+0x125d)[0x807] /usr/bin/perl(main+0xc2)[0x8064172] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7e4c7a5] /usr/bin/perl[0x8064011] === Memory map: 08048000-0817a000 r-xp 03:01 82416 /usr/bin/perl 0817a000-0817c000 rw-p 00132000 03:01 82416 /usr/bin/perl 08ef3000-099da000 rw-p 00:00 0 [heap] b700-b7021000 rw-p 00:00 0 b7021000-b710 ---p 00:00 0 b7198000-b71c2000 r-xp 03:01 40564 /lib/libgcc_s.so.1 b71c2000-b71c3000 rw-p 00029000 03:01 40564 /lib/libgcc_s.so.1 b71cf000-b71d9000 r-xp 03:01 49794 /lib/i686/cmov/libnss_files-2.9.so b71d9000-b71da000 r--p 9000 03:01 49794 /lib/i686/cmov/libnss_files-2.9.so b71da000-b71db000 rw-p a000 03:01 49794 /lib/i686/cmov/libnss_files-2.9.so b71de000-b71e6000 r-xp 03:01 219318 /usr/lib/perl5/auto/Term/ReadKey/ReadKey.so b71e6000-b71e7000 rw-p 8000 03:01 219318 /usr/lib/perl5/auto/Term/ReadKey/ReadKey.so b71e7000-b7234000 r--p 03:01 244015 /usr/share/locale/de/LC_MESSAGES/subversion.mo b7234000-b725b000 r-xp 03:01 219171 /usr/lib/perl5/auto/SVN/_Delta/_Delta.so b725b000-b725d000 rw-p 00027000 03:01 219171 /usr/lib/perl5/auto/SVN/_Delta/_Delta.so b725d000-b729d000 r-xp 03:01 88857 /usr/lib/libsvn_client-1.so.1.0.0 b729d000-b729e000 rw-p 0004 03:01 88857 /usr/lib/libsvn_client-1.so.1.0.0 b729e000-b7347000 r-xp 03:01 219154 /usr/lib/perl5/auto/SVN/_Client/_Client.so b7347000-b734b000 rw-p 000a8000 03:01 219154 /usr/lib/perl5/auto/SVN/_Client/_Client.so b734b000-b738d000 r-xp 03:01 88858 /usr/lib/libsvn_wc-1.so.1.0.0 b738d000-b738e000 rw-p 00042000 03:01 88858 /usr/lib/libsvn_wc-1.so.1.0.0 b738e000-b7452000 r-xp 03:01 219157 /usr/lib/perl5/auto/SVN/_Wc/_Wc.so b7452000-b7456000 rw-p 000c3000 03:01 219157 /usr/lib/perl5/auto/SVN/_Wc/_Wc.so b7456000-b7594000 r-xp 03:01 97825 /usr/lib/i686/cmov/libcrypto.so.0.9.8 b7594000-b75ab000 rw-p 0013e000 03:01 97825 /usr/lib/i686/cmov/libcrypto.so.0.9.8 b75ab000-b75ae000 rw-p 00:00 0 b75ae000-b75f1000 r-xp 03:01 97824 /usr/lib/i686/cmov/libssl.so.0.9.8 b75f1000-b75f5000 rw-p 00043000 03:01 97824 /usr/lib/i686/cmov/libssl.so.0.9.8 b75f5000-b7749000 r-xp 03:01 83675 /usr/lib/libdb-4.7.so b7749000-b774c000 rw-p 00153000 03:01 83675 /usr/lib/libdb-4.7.so b774c000-b7759000 r-xp 03:01 88812 /usr/lib/libserf-0.so.0.0.0 b7759000-b775a000 rw-p c000 03:01 88812 /usr/lib/libserf-0.so.0.0.0 b775a000-b7783000 r-xp 03:01 88854 /usr/lib/libsvn_fs_base-1.so.1.0.0
Bug#551769: glibc: /usr/bin/perl: double free or corruption
Am Dienstag 20 Oktober 2009 20:03:48 schrieben Sie: package perl-base libsvn-perl reassign 551769 libsvn-perl thanks Hello Sten, thanks for your report. Since libsvn-perl contains binary Perl module in the middle of the stack strae, it is a possible culprit of this bug. Reassigned. In this case, let me add the information about libsvn-perl: Package: libsvn-perl Version: 1.6.5dfsg-1 Versions of packages libsvn-perl depends on: ii libapr1 1.3.8-1 The Apache Portable Runtime Libra ii libc62.9-25 GNU C Library: Shared libraries ii libsvn1 1.6.5dfsg-1 Shared libraries used by Subversi ii perl 5.10.1-5Larry Wall's Practical Extraction ii perl-base [perlapi-5.10.1] 5.10.1-5minimal Perl system Let me know if and which additional information is needed. Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#497358: hal-info: wrong quirks for pm-suspend on thinkpad x40
Since my last upgrade (for upgraded packages see attached part of dpkg.log) the backlight is off after resume from suspend to ram. As descibed in the original bug report, pm-suspend shows this behaviour (as does suspending from KDE for me), while pm-suspend --quirk-s3-bios does not. I went back to the old version of hal-info I used before the upgrade (20081219-1), but I did not get back normal behaviour with backlight on after resume. I also attached a patch that comments out the disabling of quirks, which make resuming working again with the current version (20090202-1). Please add the patch to the next version. My laptop seems to be identical to the bug reporter's. It is a Thinkpad X40, to be more precise: $ lshal |grep system.hardware.product system.hardware.product = '23711CU' (string) $ lshal |grep system.hardware.version system.hardware.version = 'ThinkPad X40' (string) $ lshal |grep system.firmware.version system.firmware.version = '1UETD2WW (2.07 )' (string) I am happy to provide more information or test other possible solutions. Regards, Sten 2009-02-27 15:50:16 upgrade grep 2.5.3~dfsg-6 2.5.4-2 2009-02-27 15:50:22 upgrade gzip 1.3.12-6 1.3.12-7 2009-02-27 15:50:26 upgrade libxau-dev 1:1.0.3-3 1:1.0.4-2 2009-02-27 15:50:27 upgrade libxau6 1:1.0.3-3 1:1.0.4-2 2009-02-27 15:50:27 upgrade x11proto-core-dev 7.0.12-1 7.0.14-2 2009-02-27 15:50:27 upgrade libsm6 2:1.0.3-2 2:1.1.0-2 2009-02-27 15:50:28 upgrade libxaw7 2:1.0.4-2 2:1.0.5-2 2009-02-27 15:50:28 upgrade libxft2 2.1.12-3 2.1.13-3 2009-02-27 15:50:28 upgrade x11-utils 7.3+2+nmu1 7.4+1 2009-02-27 15:50:29 upgrade x11-xkb-utils 7.4+1 7.4+2 2009-02-27 15:50:29 upgrade x11proto-input-dev 1.5.0-1 1.5.0-2 2009-02-27 15:50:30 upgrade xtrans-dev 1.2-2 1.2.3-3 2009-02-27 15:50:30 upgrade libsepol1 2.0.30-2 2.0.32-1 2009-02-27 15:50:36 upgrade tzdata 2008i-3 2009b-1 2009-02-27 15:50:42 upgrade libgnutls26 2.4.2-6 2.6.4-2 2009-02-27 15:50:43 upgrade dictionaries-common 0.98.16 1.0.0 2009-02-27 15:50:44 upgrade pciutils 1:3.0.0-6 1:3.0.3-2 2009-02-27 15:50:45 upgrade libpci3 1:3.0.0-6 1:3.0.3-2 2009-02-27 15:50:45 upgrade apt-file 2.2.1 2.2.2 2009-02-27 15:50:45 upgrade binutils 2.18.1~cvs20080103-7 2.19.1-1 2009-02-27 15:50:47 upgrade ca-certificates 20080809 20081127 2009-02-27 15:50:47 upgrade cmake-data 2.6.2-4 2.6.2-4 2009-02-27 15:50:49 upgrade cmake 2.6.2-4 2.6.2-4 2009-02-27 15:50:50 upgrade libdbus-1-3 1.2.1-5 1.2.12-1 2009-02-27 15:50:50 upgrade dbus 1.2.1-5 1.2.12-1 2009-02-27 15:50:51 upgrade dbus-x11 1.2.1-5 1.2.12-1 2009-02-27 15:50:51 upgrade hal-info 20081219-1 20090202-1 2009-02-27 15:50:52 upgrade klibc-utils 1.5.12-2 1.5.15-1 2009-02-27 15:50:52 upgrade libklibc 1.5.12-2 1.5.15-1 2009-02-27 15:50:53 upgrade libdbus-glib-1-2 0.76-1 0.80-3 2009-02-27 15:50:53 upgrade libfaac0 1.26-0.2 1.28-0.1 2009-02-27 15:50:53 upgrade libpciaccess0 0.10.3-1 0.10.5-3 2009-02-27 15:50:54 upgrade libpcsclite1 1.4.102-1 1.5.2-1 2009-02-27 15:50:54 upgrade libtheora0 1.0~beta3-1 1.0-1 2009-02-27 15:50:54 upgrade libvoikko1 1.7-2 2.0-2 2009-02-27 15:50:55 upgrade libxfont1 1:1.3.3-1 1:1.3.4-2 2009-02-27 15:50:55 upgrade pm-utils 1.1.2.4-1 1.2.4-2 2009-02-27 15:50:55 upgrade xinit 1.0.9-2 1.1.1-1 2009-02-27 15:50:56 upgrade libdirac0 1.0.0-0.0 1.0.2-0.0 2009-02-27 15:50:56 upgrade libxcb-render-util0 0.2.1+git1-1 0.3.3-2 diff -ur hal-info-20090202.orig/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi hal-info-20090202/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi --- hal-info-20090202.orig/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi 2009-02-28 21:18:16.0 +0100 +++ hal-info-20090202/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi 2009-02-28 21:20:07.0 +0100 @@ -104,9 +104,12 @@ /match !-- need no quirks: a X40, T40 -- match key=system.hardware.version string=ThinkPad X40 - match key=system.firmware.version prefix=1UETD2WW - merge key=power_management.quirk.none type=booltrue/merge -/match + !-- + X40 need s3 bios quirk to bring backlight back on resume b.d.o #497358 + match key=system.firmware.version prefix=1UETD2WW +merge key=power_management.quirk.none type=booltrue/merge + /match + -- /match match key=system.hardware.version string=ThinkPad T40 match key=system.firmware.version prefix=1RETDRWW
Bug#513758: [Pkg-utopia-maintainers] Bug#513758: network-manager: upgrading to 0.7 install/recommends gnome on kde desktop
reopen 513758 severity 513758 normal reassign 513758 policykit thanks Reopening and reassigning to policykit after talking to mbiebl. Also lowering severity, since there's no policy violation. Please change the recommends of policykit-gnome into a suggests. Thanks, Sten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513758: network-manager: upgrading to 0.7 install/recommends gnome on kde desktop
Package: network-manager Version: 0.6.6-2 Severity: serious Justification: Policy 7.2 I am not sure against which package this bug should be reported, network-manager or policykit. Please reassign if necessary. Upgrading network-manager from 0.6.6-2 to 0.7.0-1 causes most of Gnome to be installed: $ apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: network-manager 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. $ apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: consolekit defoma esound-clients esound-common fam fontconfig fontconfig-config gconf2 gconf2-common gnome-keyring gnome-mime-data gnome-mount hicolor-icon-theme libart-2.0-2 libaudiofile0 libavahi-client3 libavahi-common-data libavahi-common3 libavahi-glib1 libbonobo2-0 libbonobo2-common libbonoboui2-0 libbonoboui2-common libcairo2 libck-connector0 libcups2 libdatrie0 libdirectfb-1.0-0 libeel2-2.20 libeel2-data libenchant1c2a libesd0 libfam0 libfontconfig1 libgail-common libgail18 libgconf2-4 libglade2-0 libgnome-keyring0 libgnome-menu2 libgnome2-0 libgnome2-common libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-extra libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libhunspell-1.2-0 libidl0 libjpeg62 libmalaga7 libnautilus-extension1 libnm-glib0 libnm-util1 libnotify1 liborbit2 libpam-ck-connector libpam-gnome-keyring libpango1.0-0 libpango1.0-common libpcap0.8 libpolkit-dbus2 libpolkit-gnome0 libpolkit-grant2 libpolkit2 libsexy2 libsmbclient libstartup-notification0 libtalloc1 libthai-data libthai0 libtiff4 libts-0.0-0 libttf2 libvoikko1 libwbclient0 libwnck-common libwnck22 libxcb-render-util0 libxcb-render0 libxcomposite1 libxcursor1 libxft2 libxinerama1 libxrandr2 libxrender1 libxres1 myspell-en-us notification-daemon policykit policykit-gnome portmap ppp shared-mime-info ttf-dejavu ttf-dejavu-core ttf-dejavu-extra x-ttcidfont-conf The following packages will be upgraded: network-manager 1 upgraded, 103 newly installed, 0 to remove and 0 not upgraded. Need to get 15.0MB/32.7MB of archives. After this operation, 99.7MB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. This happens because of recommends: $ aptitude why network-manager libgnomevfs2-0 p network-manager Recommends policykit p policykit Recommends policykit-gnome p policykit-gnome Dependslibgnomevfs2-0 (= 1:2.17.90) $ apt-get --no-install-recommends dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libnm-glib0 libnm-util1 libpolkit-dbus2 libpolkit2 The following packages will be upgraded: network-manager 1 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 191kB/1330kB of archives. After this operation, 1876kB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. This happens even without having a Gnome desktop (since I am using KDE). I see in this a serious violation of the policy, since The Recommends field should list packages that would be found together with this one, which in turn means recommends must not contain packages that are not found together. And Gnome is usually not found on KDE desktops. Thanks, Sten -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.27.10-sh-pentiumm (PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser 3.110 add and remove users and groups ii dbus 1.2.1-5simple interprocess messaging syst ii dhcdbd3.0-5 D-Bus interface to the ISC DHCP cl ii hal 0.5.11-8 Hardware Abstraction Layer ii ifupdown 0.6.8+nmu1 high level tools to configure netw ii iproute 20080725-2 networking and traffic control too ii libc6 2.7-18 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-5simple interprocess messaging syst ii libdbus-glib-1-2 0.76-1 simple interprocess messaging syst ii libgcrypt11 1.4.1-1LGPL Crypto library - runtime libr ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libgpg-error0 1.4-2 library for common error values an ii libhal1 0.5.11-8 Hardware Abstraction Layer - share ii libiw29
Bug#510181: xserver-xorg-core: crash on startx when dri enabled after upgrade to xserver 1.5.3
Reading through the commit log for the mesa_7_2_branch I found that freedesktop.org bug #17766 [1] is exactly my bug and the patch at [2] fixes it. I attached the patch. Thanks and regards, Sten [1] http://bugs.freedesktop.org/show_bug.cgi?id=17766 [2] http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_2_branchid=48c29b60a899877c76d643b9cd06d5277cd97b9c From 48c29b60a899877c76d643b9cd06d5277cd97b9c Mon Sep 17 00:00:00 2001 From: Xiang, Haihaohaihao.xi...@intel.com Date: Tue, 21 Oct 2008 02:30:39 + Subject: i915: fix carsh in i830_emit_state. (bug #17766) --- diff --git a/src/mesa/drivers/dri/i915/i830_vtbl.c b/src/mesa/drivers/dri/i915/i830_vtbl.c index c5a85fe..38f35dd 100644 --- a/src/mesa/drivers/dri/i915/i830_vtbl.c +++ b/src/mesa/drivers/dri/i915/i830_vtbl.c @@ -444,7 +444,8 @@ i830_emit_state(struct intel_context *intel) ret = 0; if (dirty I830_UPLOAD_BUFFERS) { ret |= dri_bufmgr_check_aperture_space(state-draw_region-buffer); - ret |= dri_bufmgr_check_aperture_space(state-depth_region-buffer); + if (state-depth_region) + ret |= dri_bufmgr_check_aperture_space(state-depth_region-buffer); } for (i = 0; i I830_TEX_UNITS; i++) -- cgit v0.8.1-24-ge5fb
Bug#510181: xserver-xorg-core: crash on startx when dri enabled after upgrade to xserver 1.5.3
With the help of jcristau I got the attached gdb log by doing the following: --on terminal tty1 $ X --ssh session 1 $ pidof X 3872 $ gdb -p 3872 --ssh session 2 $ export DISPLAY=:0; startkde Thanks and regards, Sten # gdb -p 3871 GNU gdb 6.8-debian Copyright (C) 2008 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 i486-linux-gnu. Attaching to process 3871 Reading symbols from /usr/bin/Xorg...Reading symbols from /usr/lib/debug/usr/bin/Xorg...done. done. Reading symbols from /usr/lib/libpciaccess.so.0...done. Loaded symbols for /usr/lib/libpciaccess.so.0 Reading symbols from /lib/i686/cmov/libdl.so.2...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread 0xb7b956b0 (LWP 3871)] Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from /usr/lib/libXfont.so.1...done. Loaded symbols for /usr/lib/libXfont.so.1 Reading symbols from /usr/lib/libXau.so.6...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libfontenc.so.1...done. Loaded symbols for /usr/lib/libfontenc.so.1 Reading symbols from /usr/lib/libpixman-1.so.0...done. Loaded symbols for /usr/lib/libpixman-1.so.0 Reading symbols from /usr/lib/libhal.so.1...done. Loaded symbols for /usr/lib/libhal.so.1 Reading symbols from /usr/lib/libdbus-1.so.3...done. Loaded symbols for /usr/lib/libdbus-1.so.3 Reading symbols from /usr/lib/libXdmcp.so.6...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /usr/lib/i686/cmov/libcrypto.so.0.9.8...done. Loaded symbols for /usr/lib/i686/cmov/libcrypto.so.0.9.8 Reading symbols from /lib/i686/cmov/libm.so.6...done. Loaded symbols for /lib/i686/cmov/libm.so.6 Reading symbols from /lib/i686/cmov/librt.so.1...done. Loaded symbols for /lib/i686/cmov/librt.so.1 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/i686/cmov/libc.so.6...done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libfreetype.so.6...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /usr/lib/xorg/modules/extensions/libextmod.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libextmod.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libextmod.so Reading symbols from /usr/lib/xorg/modules/extensions/libdbe.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdbe.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libdbe.so Reading symbols from /usr/lib/xorg/modules/extensions/libglx.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libglx.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libglx.so Reading symbols from /usr/lib/xorg/modules/fonts/libfreetype.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/fonts/libfreetype.so...done. done. Loaded symbols for /usr/lib/xorg/modules//fonts/libfreetype.so Reading symbols from /usr/lib/xorg/modules/extensions/librecord.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/librecord.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//librecord.so Reading symbols from /usr/lib/xorg/modules/extensions/libdri.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdri.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libdri.so Reading symbols from /usr/lib/libdrm.so.2...done. Loaded symbols for /usr/lib/libdrm.so.2 Reading symbols from /usr/lib/xorg/modules/drivers/intel_drv.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/drivers/intel_drv.so...done. done. Loaded symbols for /usr/lib/xorg/modules/drivers//intel_drv.so Reading symbols from /usr/lib/libdrm_intel.so.1...done. Loaded symbols for /usr/lib/libdrm_intel.so.1 Reading symbols from /usr/lib/xorg/modules/libvgahw.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/libvgahw.so...done. done. Loaded symbols for /usr/lib/xorg/modules//libvgahw.so Reading symbols from /usr/lib/xorg/modules/drivers/sil164.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/drivers/sil164.so...done. done. Loaded symbols for /usr/lib/xorg/modules/drivers//sil164.so Reading symbols from /usr/lib/xorg/modules/drivers/ch7xxx.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/drivers/ch7xxx.so...done. done. Loaded symbols for /usr/lib/xorg/modules/drivers//ch7xxx.so Reading symbols from /usr/lib/xorg/modules/drivers/ivch.so...Reading
Bug#510181: xserver-xorg-core: crash on startx when dri enabled after upgrade to xserver 1.5.3
Package: xserver-xorg-core Version: 2:1.5.3-1 Severity: important After upgrade to xorg 7.4/xserver 1.5.3, the xserver crashes on startx if DRI is enabled. Disabling it in xorg.conf (and disabling compositing in kwin) make the xserver start again. This was working with xserver 1.4/testing. The attached xorg.0.log is after disabling DRI. I will send a log containing the crash. I am not sure if the severity is correct. Because it breaks unrelated software (that depends on compositing) it would qualify even for a higher severity. Please modify if necessary. Regards, Sten -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 28. Dez 05:46 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1623452 25. Dez 03:38 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1370 29. Dez 21:38 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard # Driver kbd Driver evdev Option XkbRules xorg # Option XkbModel pc104 Option XkbModel evdev Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device # Driver vesa # Option ModeDebug true Option NoDRI EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor # SubSection Display # Depth 24 # Modes 1024x768 800x600 # Virtual 2048 2048 # EndSubSection EndSection #Section ServerFlags # Option NoTrapSignals #EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 21515 30. Dez 04:57 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.27.10-sh-pentiumm i686 Debian Current Operating System: Linux brasilia 2.6.27.10-sh-pentiumm #1 PREEMPT Tue Dec 23 16:31:50 CET 2008 i686 Build Date: 25 December 2008 02:18:19AM xorg-server 2:1.5.3-1 (pbuil...@brasilia.heinze.lan) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Dec 30 04:55:37 2008 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) ModulePath set to /usr/lib/xorg/modules
Bug#510181: xserver-xorg-core: crash on startx when dri enabled after upgrade to xserver 1.5.3
I attached the xorg.0.log containing the crash. Regards, Sten X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.27.10-sh-pentiumm i686 Debian Current Operating System: Linux brasilia 2.6.27.10-sh-pentiumm #1 PREEMPT Tue Dec 23 16:31:50 CET 2008 i686 Build Date: 25 December 2008 02:18:19AM xorg-server 2:1.5.3-1 (pbuil...@brasilia.heinze.lan) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Dec 28 05:58:50 2008 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81d1280 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (--) using VT number 7 (--) PCI:*(0...@0:2:0) Intel Corporation 82852/855GM Integrated Graphics Device rev 2, Mem @ 0xe000/0, 0xd000/0, I/O @ 0x1800/0 (--) PCI: (0...@0:2:1) Intel Corporation 82852/855GM Integrated Graphics Device rev 2, Mem @ 0xe800/0, 0xd008/0 (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x (0x1) IX[B] (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.5.3, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.1 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.5.3, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.1 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.5.3, module version = 1.0.0 ABI class: X.Org Server Extension, version 1.1 (==) AIGLX enabled (==) Exporting typical set of GLX visuals (II) Loading extension GLX (II) LoadModule: freetype (II) Loading /usr/lib/xorg/modules//fonts/libfreetype.so (II) Module freetype: vendor=X.Org Foundation the After X-TT Project compiled for 1.5.3, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.6 (II)
Bug#488283: software rendering
Am Tuesday 28 October 2008 06:54:05 schrieben Sie: Handle yes, allocate no. Allocating room for a 2048x2048 virtual screen requires a lot of available memory. I cannot imagine that it needs more memory that I have. According to [1] on system with more than 256MB of ram (i have more) 64MB should be allocated to the graphics card. For 3d acceleration I need 4*height*width*colordepth, again according to [1], which is 4*2048*2048*4byte=64MB. Do I miss something? And if DRI doesn't work, I don't think you can expect 3d effects in KDE to work. That probably explains the white screen. I don't expect KDE to work with 3d effects, but I expect it to fallback to normal operation without 3d effects. And it does this correctly if I e.g. switch to driver from intel to vesa. Therefore I would also expect it in this case. Thanks for helping me, Sten [1] ftp://download.intel.com/support/graphics/intel852gm/dvmt.pdf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488283: software rendering
Am Mittwoch 22 Oktober 2008 17:41:35 schrieb Julien Cristau: The 2048 log shows that the driver isn't able to allocate enough memory for direct rendering from the GART. This explains why indirect rendering is used instead. I think we should close this as not a bug. Hi Julien, But shouldn't the driver be able to allocate and handle memory up to 2048x2048? Another thing I've experienced is that if I add the line Virtual 2048 2048 again, I just get a white screen with mouse pointer, but I cannot do anything with it. Switching to a tty works though. This behaviour cannot be observed when I am switching off 3d effects in KDE. But that's probably something I should file a bug against KDE? Thanks, Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497116: xorg: random crashes on shutdown
Hi, I am using the vesa driver since yesterday, and it is stable so far. But it only has limited number of colors and no 3d acceleration. After searching again I found very similar bug reports: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/244817 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/229043 https://bugs.freedesktop.org/show_bug.cgi?id=15168 Does xserver-xorg-video-intel/testing 2:2.3.2-2+lenny4 contain the fix from https://bugs.freedesktop.org/show_bug.cgi?id=15168#c41 As soon as I have time I'll try to set the equivalent ForceEnablePipeA setting and test if it helps. Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497116: xorg: random crashes on shutdown
Hi, I got a little further in investigating the problem. What I did: --boot, stop kdm, login on tty1, 'startx'; --ssh into the system, attach gdb to the x process; --from this session you can only logout and return to tty1. On logging out I got hit by the bug again (blank screen, no reaction to keys nor mouse), see attached gdb-output.log. Even though I added NoTrapSignals to the xorg.conf, Ctrl+C did not help at this point (it worked when I tested it before). So far this are very similar. The difference is that I was able to ssh into the system a second time, and I found x using about 100% cpu, see attached top-output.log. In addition I found that another x process (pid 3043) was using my cpu than the one I attached gdb to earlier (pid 2653): $ ps -A |grep X 2653 tty7 00:00:06 Xorg 3043 tty7 06:37:35 Xorg Trying to attach gdb again resulted in error messages, as well as everything using strace (regardless of process or user): $ strace -p 3043 attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted $ strace -p 2653 attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted # gdb -p 3043 GNU gdb 6.8-debian Copyright (C) 2008 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 i486-linux-gnu. Attaching to process 3043 ptrace: Operation not permitted. (gdb) quit # gdb -p 2653 GNU gdb 6.8-debian Copyright (C) 2008 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 i486-linux-gnu. Attaching to process 2653 ptrace: Operation not permitted. (gdb) quit Even trying to kill the x processes was not really possible: # ps -A |grep X 2653 tty7 00:00:06 Xorg 3043 tty7 08:45:12 Xorg # kill 2653 # ps -A |grep X 2653 tty7 00:00:06 Xorg 3043 tty7 08:45:18 Xorg # kill -9 2653 # ps -A |grep X 2653 ?00:00:06 Xorg defunct 3043 ?08:45:22 Xorg # kill 3043 # ps -A |grep X 2653 ?00:00:06 Xorg defunct 3043 ?08:45:22 Xorg # kill -9 3043 # ps -A |grep X 2653 ?00:00:06 Xorg defunct 3043 ?08:45:22 Xorg defunct Rebooting was successful, though. What is the best to do in case I get my system in this bug-situation again? How do I figure out in which loop or function it spins? What is my problem with those strace error messages (after the reboot the used strace command worked)? Thanks in advance, Sten brasilia:/home/mheinzes# ps -A |grep X 2653 tty7 00:00:02 Xorg brasilia:/home/mheinzes# gdb /usr/bin/Xorg 2653 GNU gdb 6.8-debian Copyright (C) 2008 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 i486-linux-gnu... Attaching to program: /usr/bin/Xorg, process 2653 Reading symbols from /lib/i686/cmov/libdl.so.2...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /usr/lib/libXfont.so.1...done. Loaded symbols for /usr/lib/libXfont.so.1 Reading symbols from /usr/lib/libXau.so.6...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libfontenc.so.1...done. Loaded symbols for /usr/lib/libfontenc.so.1 Reading symbols from /usr/lib/libpixman-1.so.0...done. Loaded symbols for /usr/lib/libpixman-1.so.0 Reading symbols from /usr/lib/libhal.so.1...done. Loaded symbols for /usr/lib/libhal.so.1 Reading symbols from /usr/lib/libdbus-1.so.3...done. Loaded symbols for /usr/lib/libdbus-1.so.3 Reading symbols from /usr/lib/libXdmcp.so.6...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /lib/i686/cmov/libm.so.6...done. Loaded symbols for /lib/i686/cmov/libm.so.6 Reading symbols from /lib/i686/cmov/librt.so.1...done. Loaded symbols for /lib/i686/cmov/librt.so.1 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/i686/cmov/libc.so.6...done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libfreetype.so.6...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/i686/cmov/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread 0xb7dc5a30 (LWP 2653)] Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from
Bug#497116: xorg: random crashes on shutdown
Hi, I was not able to attach gdb successfully in case of a crash. Trying to attach after a crash is not possible (ssh: connect to host 160.129.138.82 port 22: No route to host). Everytime I attached gdb before shutting down, it did not crash. So I tried to change kernel version (vanilla 2.6.25.10 to 2.6.26.5), but crashs still occur. I also tried to test the new xorg (xorg 7.4~3, xserver 1.5.0-1, xserver-xorg-video-intel 2.4.2-1), but I was stopped by bug #497267 (underrun on pipe B!). Let me know, if I can help further than trying to get a backtrace. Thanks, Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497116: xorg: random crashes on shutdown
Am Saturday 30 August 2008 08:51:50 schrieben Sie: Is the machine pingable after the crash? Can you restart X without any problem? No ping after a crash. trying to ssh into the system (it works before a crash) results in: $ ssh [EMAIL PROTECTED] ssh: connect to host 160.129.138.82 port 22: No route to host * catch a backtrace with gdb after installing xserver-xorg-core-dbg and xserver-xorg-video-intel-dbg. The easiest way is to connect through ssh from another machine, attach gdb with gdb -p $(pidof X), wait for the crash to occurs, and then ru bt full in gdb. I installed those packages and opened a ssh connection after booting, attached gdb and continued. When shutting down KDE detects the running ssh session, and asks about closing them. If I confirm that, I get the gdb messages about receiving SIGTERM, SIGHUP, and SIGCONT, which I continue on. In case of a crash the system stopps working after one of those messages, see attached crash.txt. If everything works Xorg exits normally and I get no- crash.txt, attached as well. This information does not seem very useful to me, but I am glad if I can help more. So, please tell me. Sten # ps -A |grep Xorg 2654 tty7 00:00:02 Xorg # gdb -p 2654 GNU gdb 6.8-debian Copyright (C) 2008 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 i486-linux-gnu. Attaching to process 2654 Reading symbols from /usr/bin/Xorg...Reading symbols from /usr/lib/debug/usr/bin/Xorg...done. done. Reading symbols from /lib/i686/cmov/libdl.so.2...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /usr/lib/libXfont.so.1...done. Loaded symbols for /usr/lib/libXfont.so.1 Reading symbols from /usr/lib/libXau.so.6...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libfontenc.so.1...done. Loaded symbols for /usr/lib/libfontenc.so.1 Reading symbols from /usr/lib/libpixman-1.so.0...done. Loaded symbols for /usr/lib/libpixman-1.so.0 Reading symbols from /usr/lib/libhal.so.1...done. Loaded symbols for /usr/lib/libhal.so.1 Reading symbols from /usr/lib/libdbus-1.so.3...done. Loaded symbols for /usr/lib/libdbus-1.so.3 Reading symbols from /usr/lib/libXdmcp.so.6...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /lib/i686/cmov/libm.so.6...done. Loaded symbols for /lib/i686/cmov/libm.so.6 Reading symbols from /lib/i686/cmov/librt.so.1...done. Loaded symbols for /lib/i686/cmov/librt.so.1 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/i686/cmov/libc.so.6...done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libfreetype.so.6...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/i686/cmov/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread 0xb7c5ca30 (LWP 2654)] Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from /usr/lib/xorg/modules/libpcidata.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/libpcidata.so...done. done. Loaded symbols for /usr/lib/xorg/modules//libpcidata.so Reading symbols from /usr/lib/xorg/modules/extensions/libextmod.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libextmod.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libextmod.so Reading symbols from /usr/lib/xorg/modules/extensions/libdbe.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdbe.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libdbe.so Reading symbols from /usr/lib/xorg/modules/extensions/libglx.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libglx.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libglx.so Reading symbols from /usr/lib/xorg/modules/fonts/libfreetype.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/fonts/libfreetype.so...done. done. Loaded symbols for /usr/lib/xorg/modules//fonts/libfreetype.so Reading symbols from /usr/lib/xorg/modules/extensions/librecord.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/librecord.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//librecord.so Reading symbols from /usr/lib/xorg/modules/extensions/libdri.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdri.so...done. done. Loaded symbols for /usr/lib/xorg/modules/extensions//libdri.so Reading symbols from /usr/lib/libdrm.so.2...done. Loaded symbols for /usr/lib/libdrm.so.2 Reading symbols from
Bug#497116: xorg: random crashes on shutdown
Package: xorg Version: 1:7.3+15 Severity: grave Justification: causes data loss xorg crashes randomly on shutdown, i.e. after the desktop environment shut down (closing programs and playing shutdown sound). The screen does not return to the normal console (tty1) but stays black instead and freezes the system (only switching off helps). This happened for me both with KDE 3 and 4 (each using the latest versions available in Debian). Unfortunately no information about the crash is recorded in the log files, and I did not find a clearly reproducable pattern. It usually happens once a day, although I start/shutdown the system only about 2-4 times a day. This is extremely annoying, in particular when losing data after working on it all day. I am using Thinkpad X40 with an integrated Intel 855GM graphics controller. Please tell me if and how I can provide further help. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25.10-sh-pentiumm (SMP w/1 CPU core; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488283: software rendering
Found http://bugs.freedesktop.org/show_bug.cgi?id=16151 today and removed the following line which I added in order to use external monitors: Virtual 2048 2048 Afterwards the error message was not displayed anymore, and also 'glxinfo | grep rendering' returns now 'direct rendering: Yes'. To be able to expand (cloning works with the default maximum of 1024x1024) my desktop I tried several values, and while 2048x1900 did not work I found Virtual 2048 1820 is working and gives me the possibility to use a [1400|1680]x1050 display together with my internal 1024x768 laptop screen. I have no idea, why 2048x2048 does not work, although this value can be found as the maximum value direct rendering works with in most places, but the slightly lower resolution for the virtual screen works for me. But don't hesitate to ask, I'm happy to help or test. Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488283: software rendering
I tried to find more information. It looks like the bugs has a similar reason as #393266 for xserver-xorg-video-savage, see also http://bugzilla.kernel.org/show_bug.cgi?id=7767. I installed debian's linux-image-2.6.25-2-686 from testing, and compiled vanilla 2.6.25.10 (+patches for tp-smapi, hdaps, linux-phc), but the error message still remains the same. Please let me know, if I can help. Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488283: libgl1-mesa-glx: drmMap of framebuffer failed, reverting to software rendering
Package: libgl1-mesa-glx Version: 7.0.3-1 Severity: important Since my last update I noticed a immense slowdown in the graphics performance. Even switching desktops needs up to several seconds. Looking into Xorg.0.log I found: (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE) AIGLX: reverting to software rendering Same result when starting glxgears: libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering Trying to find more information I looked into BTS, but solutions from bug-reports describing a similar slowdown (e.g. #480689) do not work. It is slow whatever I use, EXA, XAA, or other options. This is using a Thinkpad X40 with Intel 855GM graphics card: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) I am not sure if this is correct package, so reassign to the appropriate one, please. Also I set the severity to important, but a higher is probably more suitable since it makes other packages almost unusable. If you have further questions, please send me an email. Regards, Sten -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25.7-sh-pentiumm (SMP w/1 CPU core; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libgl1-mesa-glx depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libdrm2 2.3.0-4Userspace interface to kernel DRM ii libx11-6 2:1.1.4-2 X11 client-side library ii libxdamage1 1:1.1.1-4 X11 damaged region extension libra ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfixes31:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxxf86vm1 1:1.0.1-3 X11 XFree86 video mode extension l libgl1-mesa-glx recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488283: libgl1-mesa-glx: drmMap of framebuffer failed, reverting to software rendering
Am Freitag, 27. Juni 2008 19:19:06 schrieb Brice Goglin: Sten Heinze wrote: Package: libgl1-mesa-glx Version: 7.0.3-1 Severity: important Since my last update I noticed a immense slowdown in the graphics performance. Even switching desktops needs up to several seconds. Looking into Xorg.0.log I found: (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE) AIGLX: reverting to software rendering Did you change your kernel recently? Brice I changed my kernel ~1 week ago, but only from 2.6.25.4 to .7, the last change before that is ~5 weeks ago. I didn't have this problem with .4, and I don't see anything in the kernel changelogs causing that. So I think it's not my kernel causing the error. Let me know if there's anythings else I can help with. Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481180: [laptop-mode-tools] wireless-ipw-power not working on ac
Package: laptop-mode-tools Version: 1.41-1 Severity: normal --- Please enter the report below this line. --- When switching from battery to AC two command are executed in /usr/share/laptop-mode-tools/modules/wireless-ipw-power, which are for my ipw2100 card: /sbin/iwconfig eth1 power off /sbin/iwpriv eth1 set_power 5 According to man iwconfig the first command disabled power management, so that the second has no effect. This results on a significant higher temperature in my laptop (Thinkpad X40) of: CPU=41 GPU=42 MB=46 MiniPCI=39 BAT=35 N/A=-128 BAT=33 N/A=-128 with power management off than having it on: CPU=41 GPU=42 MB=46 MiniPCI=37 BAT=35 N/A=-128 BAT=33 N/A=-128 (consistent temperatures in a few runs, temperatures after 10~15 min idle, fan off) So it should be changed to keep powermanagement switched on, and to use the power level for AC instead of the battery one (just a typo). Thanks, Sten --- System information. --- Architecture: i386 Kernel: Linux 2.6.20.15-sh-pentiumm Debian Release: lenny/sid 500 testing security.debian.org 500 testing mirrors.ecology.uni-kiel.de 500 testing ftp.de.debian.org 500 stable security.debian.org 500 stable ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+- lsb-base (= 3.0-10) | 3.1-24 util-linux (= 2.13) | 2.13.1-1 *** /root/Desktop/wireless-ipw-power 2008-05-13 21:28:24.0 +0200 --- /root/Desktop/wireless-ipw-power.new 2008-05-14 13:37:59.0 +0200 *** *** 50,56 SET_I2200_AC_PARMS=power off SET_I2200_BAT_PARMS=power on ! SET_I2100_AC_PARMS_1=power off SET_I2100_BAT_PARMS_1=power on SET_I2100_AC_PARMS_2=set_power $IPW2100_AC_POWER SET_I2100_BAT_PARMS_2=set_power $IPW2100_BATT_POWER --- 50,56 SET_I2200_AC_PARMS=power off SET_I2200_BAT_PARMS=power on ! SET_I2100_AC_PARMS_1=power on SET_I2100_BAT_PARMS_1=power on SET_I2100_AC_PARMS_2=set_power $IPW2100_AC_POWER SET_I2100_BAT_PARMS_2=set_power $IPW2100_BATT_POWER *** *** 124,130 intel2100_AcPwrSave () { setWifiPwrSave $I2100_DRIVERNAME $IWCONFIG $SET_I2100_AC_PARMS_1 ! setWifiPwrSave $I2100_DRIVERNAME $IWPRIV $SET_I2100_BAT_PARMS_2 } --- 124,130 intel2100_AcPwrSave () { setWifiPwrSave $I2100_DRIVERNAME $IWCONFIG $SET_I2100_AC_PARMS_1 ! setWifiPwrSave $I2100_DRIVERNAME $IWPRIV $SET_I2100_AC_PARMS_2 }
Bug#465580: gcc-4.2: FTBFS: ../../src/gcc/config/i386/crtfastmath.c:96: error: size of array 'st_space' is too large
I found this bug when I tried to upgrade to lenny, so I tried to reproduce it on the single core to exclude multi-core effects if there are any. still not able to reproduce, how is make called (-j ?) debian/rules is not called with -j, but parallel=8 is set in DEB_BUILD_OPTIONS. I used pbuilder (from testing, because of #419807) and clean sid environments as of today (pbuilder create) to build the package. It worked both with pbuilder build gcc-4.2_4.2.3-2.dsc and with additional DEB_BUILD_OPTIONS=parallel=2. It also worked using an lenny environment (tried 2 days ago w/o DEB_BUILD_OPTIONS). So the reason for the FTBFS might be somewhere else? Sten Heinze -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452218: installation-reports
Package: installation-reports Boot method: cd Image version: d-i testing i386 cd daily build 17.11.2007 http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ Date: 18.11.2007 Machine: Toshiba Satellite Pro 4220 Processor: Intel Pentium 3 with 450 MHz Memory: 64MB onboard faulty + 128MB in slot Partitions: didnt get to that point Output of lspci -nn and lspci -vnn: n/a Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The laptop has bad ram in the onboard ram, first at 2.1MB, some more following in 2.1MB to 3MB, a second group of bad ram is from 22MB to 23MB (results by memtest86). Caused by the bad ram the d-i stops while uncompressing the kernel (probably while using the 2MB area). I'm looking for a possibility to circumvent the usage of bad ram. I've found the badram-kernel-patch and the idea of relocatable kernels so far. Can I use one of these to solve my problem? Are there other possibities? Thanks in advance, Sten Heinze -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390881: kernel-package: Enable -source and -headers packages for Xen kernels
Package: kernel-package Version: 10.065 The same problem, even with a newer version. Although Tore's patch is a possible workaround to get headers and source packages, there will be no initrd build in spite of using the --initrd switch. At least it would be nice to have some information about the actual behaviour of the kernel-package in its documentation. Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401832: installation-reports
Package: installation-reports Boot method: usb, since i have no external floppy or cd-drive at the moment Image version: http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso Date: Mi 6. Dez 09:44:57 CET 2006 Machine: IBM Thinkpad X40 Processor: Intel Pentium M 1GHz ULV Memory: 768 MB Partitions: no no Output of lspci -nn and lspci -vnn, because no successful boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ E] Comments/Problems: Unable to boot from usb pen drive. Two approaches: 1. $ wget http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/rc1/images/hd-media/boot.img.gz $ gunzip boot.img.gz $ wget http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso $ wget http://freshmeat.net/redir/syslinux/10177/url_bz2/syslinux-3.31.tar.bz2 $ tar xjvf syslinux-3.11.tar.bz2 syslinux-3.11/mbr.bin $ fdisk /dev/sda delete all partitions, create a new primary partition anlegen, activate partition, save and exit $ cat syslinux-3.11/mbr.bin /dev/sda $ mount -o loop boot.img /mnt $ cp /mnt/* /media/disk/ $ cp debian-testing-i386-netinst.iso /media/disk boot show following error message: Disk error Press any key to restart 2. $ wget http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/rc1/images/hd-media/boot.img.gz $ wget http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso $ wget http://freshmeat.net/redir/syslinux/10177/url_bz2/syslinux-3.31.tar.bz2 $ tar xjvf syslinux-3.11.tar.bz2 syslinux-3.11/mbr.bin $ fdisk /dev/sda delete all partitions, create a new primary partition anlegen, activate partition, save and exit $ zcat boot.img.gz /dev/sda $ cp debian-testing-i386-netinst.iso /media/Debian\ Inst/ (name of usb pen drive changed to Debian Inst after 'zcat') boot show following error message: Boot error In general, if I try to choose the boot media (F12) it gives me two possibilities: Hard disk or usb hard drive (but it is an usb pen drive), although all options in the bios are enabled (boot from usb hard drive as well as boot from usb floppy and usb cd). Regards, Sten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401832: installation-reports
Frans, Using 'the flexible way' resulted in successful boot! At the moment I haven't enough time to do the full installation, but I'll try in the next days. Thank you for your help! Sten Am Mittwoch, 6. Dezember 2006 10:21 schrieb Frans Pop: On Wednesday 06 December 2006 09:57, Sten Heinze wrote: Two approaches: Could you also try a third method as described on http://d-i.alioth.debian.org/manual/en.i386/ch04s04.html under 4.4.2. Copying the files — the flexible way. If that does not work, I'm not sure that we can help you. Apparently your BIOS does not support booting using syslinux from USB stick. Cheers, FJP