Bug#912721: libasound2-plugins: Sound no longer works after latest update
I installed the corresponding .conf files from the source package to /usr/share/alsa/alsa.conf.d and sound started working again after a restart. So all that needs to be done is to add the files to the package. Best regards, Matthias On 03/11/2018 09:56, Matthias Liertzer wrote: > Package: libasound2-plugins > Severity: grave > Justification: renders package unusable > > After updating to the latest version of libasound2-plugins, sound on > my system stopped working. Trying to start `alsamixer' failed as well > with the following error message: > > ALSA lib conf.c:3639:(config_file_open) cannot access file > /etc/alsa/conf.d/10-rate-lav.conf > > It turns out that libasound2-plugins installs broken symlinks in > /etc/alsa/conf.d. All symlinks installed by libasound2-plugins in > /etc/alsa/conf.d are broken, because the corresponding files in > /usr/share/alsa/alsa.conf.d do not exist. > > Best regards, > Matthias > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled >
Bug#912721: libasound2-plugins: Sound no longer works after latest update
Package: libasound2-plugins Severity: grave Justification: renders package unusable After updating to the latest version of libasound2-plugins, sound on my system stopped working. Trying to start `alsamixer' failed as well with the following error message: ALSA lib conf.c:3639:(config_file_open) cannot access file /etc/alsa/conf.d/10-rate-lav.conf It turns out that libasound2-plugins installs broken symlinks in /etc/alsa/conf.d. All symlinks installed by libasound2-plugins in /etc/alsa/conf.d are broken, because the corresponding files in /usr/share/alsa/alsa.conf.d do not exist. Best regards, Matthias -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Hello, find the log attached to this mail. Best, Matthias On 03/07/18 09:25, Gianfranco Costamagna wrote: > Hello, > >> After upgrading from 5.2.12 to the latest version in debian unstable, >> virtualbox fails to start my windows vm with the error message: >> Failed to open a session for the virtual machine Win7. >> Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed >> (VERR_LDRELF_RELOCATION_NOT_SUPPORTED). >> Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED). >> Result Code: NS_ERROR_FAILURE (0x80004005) >> Component: ConsoleWrap >> Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} >> Let me know if you have any further questions. > > > can you please send VBoxLogs? (Ctrl+L should show them from graphic interface) > > G. > VirtualBox VM 5.2.14_Debian r122571 linux.amd64 (Jul 2 2018 17:50:29) release log 00:00:00.703416 Log opened 2018-07-03T17:21:43.400436000Z 00:00:00.703417 Build Type: release 00:00:00.703421 OS Product: Linux 00:00:00.703422 OS Release: 4.16.0-2-amd64 00:00:00.703423 OS Version: #1 SMP Debian 4.16.16-2 (2018-06-22) 00:00:00.703449 DMI Product Name: 20AQS00600 00:00:00.703458 DMI Product Version: ThinkPad T440s 00:00:00.703505 Host RAM: 11912MB (11.6GB) total, 8438MB (8.2GB) available 00:00:00.703510 Executable: /usr/lib/virtualbox/VirtualBox 00:00:00.703511 Process ID: 6426 00:00:00.703511 Package type: LINUX_64BITS_GENERIC (OSE) 00:00:00.712344 Installed Extension Packs: 00:00:00.712366 VNC (Version: 5.2.14 r122571; VRDE Module: VBoxVNC) 00:00:00.712371 Oracle VM VirtualBox Extension Pack (Version: 5.2.14 r123301; VRDE Module: VBoxVRDP) 00:00:00.713827 Console: Machine state changed to 'Starting' 00:00:00.714319 Qt version: 5.10.1 00:00:00.714331 X11 Window Manager code: 2 00:00:00.722828 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:00:00.726850 SUP: RTLdrGetBits failed for VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0). rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED 00:00:00.726982 PDMLdr: pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED szErr="RTLdrGetBits failed" 00:00:00.727023 VMSetError: /build/virtualbox-5ojW2E/virtualbox-5.2.14-dfsg/src/VBox/VMM/VMMR3/PDMLdr.cpp(731) int pdmR3LoadR0U(PUVM, const char*, const char*, const char*); rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED 00:00:00.727027 VMSetError: Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed 00:00:00.727040 VMSetError: /build/virtualbox-5ojW2E/virtualbox-5.2.14-dfsg/src/VBox/VMM/VMMR3/VM.cpp(598) int vmR3CreateU(PUVM, uint32_t, PFNCFGMCONSTRUCTOR, void*); rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED 00:00:00.727043 VMSetError: Failed to load VMMR0.r0 00:00:00.727233 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed (VERR_LDRELF_RELOCATION_NOT_SUPPORTED). 00:00:00.727288 Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)}, preserve=false aResultDetail=0 00:00:00.727869 Console: Machine state changed to 'PoweredOff' 00:00:00.731566 Your keyboard layout does not appear to be fully supported by 00:00:00.731568 VirtualBox. If you are experiencing keyboard problems this. 00:00:00.731569 information may help us to resolve them. 00:00:00.731569 (Note: please tell us if you are using a custom layout.) 00:00:00.731572 00:00:00.731573 The correct table for your layout is: 00:00:00.731613 "\x0\x0","1!","2@","3#","4$","5%","6^","7&","8*","9(","0)","-_","=+", 00:00:00.731737 "qQ","wW","eE","rR","tT","yY","uU","iI","oO","pP","[{","]}", 00:00:00.731839 "aA","sS","dD","fF","gG","hH","jJ","kK","lL",";:","'\"","\\|", 00:00:00.731935 "zZ","xX","cC","vV","bB","nN","mM",",<",".>","/?","\\|","\x0\x0","\x0\x0" 00:00:00.732061 00:00:00.732065 X Server details: vendor: The X.Org Foundation, release: 1200, protocol version: 11.0, display string: :0 00:00:00.732070 Using known keycode mapping for keycode to scan code conversion 00:00:00.748003 Power up failed (vrc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED, rc=NS_ERROR_FAILURE (0X80004005)) 00:00:00.749336 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x27 x 1920x1053 00:00:01.248798 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1916x999 00:00:01.248867 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0 00:00:01.248939 GUI: Aborting startup due to power up progress issue detected...
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Package: virtualbox Version: 5.2.14-dfsg-1 Severity: important After upgrading from 5.2.12 to the latest version in debian unstable, virtualbox fails to start my windows vm with the error message: Failed to open a session for the virtual machine Win7. Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed (VERR_LDRELF_RELOCATION_NOT_SUPPORTED). Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} Let me know if you have any further questions. Best regards, Matthias Liertzer -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox depends on: ii adduser 3.117 ii iproute2 4.16.0-4 ii libc6 2.27-3 ii libcurl3-gnutls 7.60.0-2 ii libdevmapper1.02.12:1.02.145-4.1 ii libgcc1 1:8.1.0-9 ii libgsoap-2.8.60 2.8.60-2 ii libopus0 1.3~beta+20180518-1 ii libpng16-16 1.6.34-1 ii libpython3.6 3.6.6-1 ii libsdl1.2debian 1.2.15+dfsg2-1 ii libssl1.1 1.1.0h-4 ii libstdc++68.1.0-9 ii libvncserver1 0.9.11+dfsg-1.1 ii libvpx5 1.7.0-3 ii libx11-6 2:1.6.5-1 ii libxcursor1 1:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-7+b1 ii libxmu6 2:1.1.2-2 ii libxt61:1.1.5-1 ii procps2:3.3.15-2 ii python3 3.6.6-1 ii python3.6 3.6.6-1 ii virtualbox-dkms [virtualbox-modules] 5.2.14-dfsg-1 ii zlib1g1:1.2.11.dfsg-1 Versions of packages virtualbox recommends: ii libgl1 1.0.0+git20180308-3 ii libqt5core5a5.10.1+dfsg-7 ii libqt5opengl5 5.10.1+dfsg-7 ii libqt5widgets5 5.10.1+dfsg-7 ii virtualbox-qt 5.2.14-dfsg-1 Versions of packages virtualbox suggests: pn vde2 ii virtualbox-guest-additions-iso 5.2.14-1 -- no debconf information
Bug#884035: libqt5webkit5-dev: qt5webkit's pkgconfig file does not provide a description
Package: libqt5webkit5-dev Version: 5.212.0~alpha2-5 Severity: normal qt5webkit's pkgconfig file does not provide a description and this breaks the command `pkg-config --list-all --print-errors` (it stops in the middle when processing the qt5webkit file and exits). This in turn breaks jhbuild, which uses the above pkg-config command to determine if all necessary system dependencies are installed. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt5webkit5-dev depends on: ii dpkg1.19.0.4 ii libqt5webkit5 5.212.0~alpha2-5 ii qtbase5-dev 5.9.2+dfsg-6 ii qtdeclarative5-dev 5.9.2-3 libqt5webkit5-dev recommends no packages. libqt5webkit5-dev suggests no packages. -- no debconf information
Bug#856626: solr-tomcat: fails to start
Package: solr-tomcat Version: 3.6.2+dfsg-9 Severity: grave Justification: renders package unusable solr doesn't start with the following error message(s) in the log 03-Mar-2017 00:04:42.268 SEVERE [localhost-startStop-1] org.apache.tomcat.util.digester.Digester.startElement Begin event threw exception java.lang.ClassNotFoundException: org.apache.naming.resources.FileDirContext at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:116) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1190) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1458) at org.apache.catalina.startup.ContextConfig.processContextConfig(ContextConfig.java:537) at org.apache.catalina.startup.ContextConfig.contextConfig(ContextConfig.java:494) at org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:738) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:310) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:395) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:108) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:140) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:596) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1805) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Best regards -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-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 Init: systemd (via /run/systemd/system) Versions of packages solr-tomcat depends on: ii solr-common 3.6.2+dfsg-9 ii tomcat8 8.5.11-1 solr-tomcat recommends no packages. solr-tomcat suggests no packages. -- no debconf information
Bug#853207: bluez: bluetooth.service doesn't start with systemd
Most likely the bluetooth support for your laptop is broken under linux. The bluetooth.service file contains ConditionPathIsDirectory=/sys/class/bluetooth which means that systemd only tries to start the bluetooth daemon when the bluetooth module from the kernel is loaded which creates the above directory in sysfs. The bluetooth module is in turn only loaded by the kernel/udev when bluetooth hardware is detected. So the .service file behaves correctly as to only start the daemon when there is actual bluetooth hardware available. Could you check if the above reasoning is correct by first directly loading the bluetooth kernel module (modprobe bluetooth), which should create /sys/class/bluetooth and then trying to start the bluetooth daemon (systemctl restart bluetooth.service)? If that is the case the bug should be reassigned as a wishlist bug to systemd. If a condition for starting a service is not satisfied when a user explicitly tries to explicitly start it on the command line, it would be useful to report the reason for the startup failure to the user. This would significantly help a user to debug such an issue.
Bug#833753: ledger: FTBFS on buildds after gcc6/icu57/boost1.61
This is most likely a gcc6 bug. When compiling ledger with clang via DEB_BUILD_MAINT_OPTIONS=reproducible=-fixdebugpath CC=clang-3.8 CXX=clang++-3.8 dpkg-buildpackage the package compiles successfully. Note, that clang-3.8 is needed otherwise linking fails due to bug #797917.
Bug#836151: sysprof: .desktop file and icon duplicated in package
Package: sysprof Version: 3.20.0-3 Severity: minor Upstream provides a .desktop file and icons and these files are already installed by the sysprof package. The debian package, in addition, provides debian/sysprof.desktop and debian/sysprof.xpm, both of which are no longer necessary and can be safely removed. Note, that gnome shell shows the sysprof application twice in the app launcher due to the duplicated .desktop file. Best regards -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.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 sysprof depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1 ii libatk1.0-0 2.20.0-1 ii libc62.23-5 ii libcairo-gobject21.14.6-1+b1 ii libcairo21.14.6-1+b1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.48.1-3 ii libgtk-3-0 3.20.9-1 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libpolkit-gobject-1-00.105-16 ii libstdc++6 6.2.0-1 ii libsystemd0 231-5 sysprof recommends no packages. sysprof suggests no packages. -- no debconf information
Bug#833827: sysprof: version 3.20 has been released upstream
Package: sysprof Severity: wishlist Dear Maintainer, sysprof is now maintained within the gnome project. The new location for the release tarball is https://download.gnome.org/sources/sysprof/. Version 3.20 has been released upstream and it would be nice to see the latest version in Debian as well. Best regards, Matthias
Bug#829584: linux-image-4.6.0-1-amd64: fails to boot on Lenovo Thinkpad T460
Package: src:linux Version: 4.7~rc4-1~exp1 Severity: important Dear Maintainer, Booting a Lenovo T460 laptop with linux-image-4.6.0-1-amd64 fails after the output "Loading initial ramdisk...". Unfortunately, no additional debug information is shown even when booting with debug=1. The same behavior also occurs for linux-image-4.7.0-rc4-amd64. linux-image-4.5.0-2-amd64 instead boots normally and is currently in use while writing this bug report. Best regards, Matthias Liertzer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20FMS03600 product_version: ThinkPad T460 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: R06ET33W (1.07 ) board_vendor: LENOVO board_name: 20FMS03600 board_version: Not Defined ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1904] (rev 08) Subsystem: Lenovo Skylake Host Bridge/DRAM Registers [17aa:5053] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:5053] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:5053] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) Subsystem: Lenovo Sunrise Point-LP Thermal subsystem [17aa:5053] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:5053] 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: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo Sunrise Point-LP SATA Controller [AHCI mode] [17aa:5053] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) (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 Kernel modules: shpchp 00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:9d12] (rev f1) (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 Kernel modules: shpchp 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d48] (rev 21) Subsystem: Lenovo Sunrise Point-LP LPC Controller [17aa:5053] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl 00:1f.4 SMBus [0c05]: Intel Corporation Sunris
Bug#827848: snapd: Purging snapd doesn't properly delete snapd from the system
Source: snapd Severity: normal After purging snapd and restarting the system, ubuntu core is still mounted automatically at boot: $ mount | grep ubuntu /var/lib/snapd/snaps/ubuntu-core_122.snap on /snap/ubuntu-core/122 type squashfs (ro,relatime) After purging snapd I would expect this to no longer be the case. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.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)
Bug#827824: libopenmpi1.10: libmca_common_verbs.so.7 missing in installation
Package: libopenmpi1.10 Version: 1.10.3-2 Severity: important Dear Maintainer, when trying to run the standard mpi petsc test case after compilation, mpiexec gives the following warning: mca: base: component_find: unable to open /usr/lib/openmpi/lib/openmpi/mca_btl_openib: libmca_common_verbs.so.7: cannot open shared object file: No such file or directory According to `dpkg -L', libmca_common_verbs.so.7 should be installed in /usr/lib, however, it bizarrely does not seem to be installed there as verified by a reinstall: $ sudo apt-get install --reinstall libopenmpi1.10 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/2,110 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 420483 files and directories currently installed.) Preparing to unpack .../libopenmpi1.10_1.10.3-2_amd64.deb ... Unpacking libopenmpi1.10 (1.10.3-2) over (1.10.3-2) ... Processing triggers for libc-bin (2.22-12) ... Setting up libopenmpi1.10 (1.10.3-2) ... Processing triggers for libc-bin (2.22-12) ... $ dpkg -L libopenmpi1.10 | grep common_verbs.so.7 /usr/lib/libmca_common_verbs.so.7 /usr/lib/libmca_common_verbs.so.7.0.0 $ ls /usr/lib | grep common_verbs.so.7 $ Best regards, Matthias Liertzer -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.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 libopenmpi1.10 depends on: ii libc6 2.22-12 ii libfabric11.3.0-2 ii libgcc1 1:6.1.1-7 ii libgfortran3 6.1.1-7 ii libhwloc-plugins 1.11.3-2 ii libhwloc5 1.11.3-2 ii libibverbs1 1.2.0-1 ii libquadmath0 6.1.1-7 ii libstdc++66.1.1-7 Versions of packages libopenmpi1.10 recommends: ii openmpi-bin 1.10.3-2 libopenmpi1.10 suggests no packages. -- no debconf information
Bug#794092: gnome-maps misses dependency on gir1.2-goa-1.0
Package: gnome-maps Version: 3.16.2-1 Severity: important Dear Maintainer, gnome-maps doesn't start on my system with the following error message: Unsatisfied dependency: Requiring Goa, version 1.0: Typelib file for namespace 'Goa', version '1.0' not found After manually installing package `gir1.2-goa-1.0', the application starts up correctly. Note, that I only have gnome-core installed + gnome-maps. Normal users which have the full `gnome' suite installed are not affected since (at least) gnome-documents depends on gir1.2-goa-1.0. Best regards, Matthias -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-maps depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii geoclue-2.0 2.1.10-2 ii gir1.2-champlain-0.120.12.10-1 ii gir1.2-clutter-1.0 1.22.4-1 ii gir1.2-cogl-1.0 1.20.0-2 ii gir1.2-gdkpixbuf-2.0 2.31.5-1 ii gir1.2-geocodeglib-1.0 3.16.2-1 ii gir1.2-gfbgraph-0.2 0.2.3-1 ii gir1.2-glib-2.0 1.44.0-1+b2 ii gir1.2-gtk-3.0 3.16.6-1 ii gir1.2-gtkchamplain-0.12 0.12.10-1 ii gir1.2-gtkclutter-1.01.6.2-1 ii gjs 1.43.3-2 ii libatk1.0-0 2.16.0-2 ii libc62.19-19 ii libcairo-gobject21.14.2-2 ii libcairo21.14.2-2 ii libchamplain-0.12-0 0.12.10-1 ii libclutter-1.0-0 1.22.4-1 ii libcogl-pango20 1.20.0-2 ii libcogl-path20 1.20.0-2 ii libcogl201.20.0-2 ii libdrm2 2.4.62-1 ii libegl1-mesa [libegl1-x11] 10.6.3-1 ii libfolks25 0.11.1-2 ii libgbm1 10.6.3-1 ii libgdk-pixbuf2.0-0 2.31.5-1 ii libgee-0.8-2 0.18.0-1 ii libgeocode-glib0 3.16.2-1 ii libglib2.0-0 2.44.1-1.1 ii libgtk-3-0 3.16.6-1 ii libjson-glib-1.0-0 1.0.4-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libwayland-client0 1.8.1-1 ii libwayland-cursor0 1.8.1-1 ii libwayland-egl1-mesa [libwayland-egl1] 10.6.3-1 ii libwayland-server0 1.8.1-1 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.4-1+b2 ii libxkbcommon00.5.0-1 ii libxrandr2 2:1.5.0-1 gnome-maps recommends no packages. gnome-maps 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#766761: sub...@bugs.debian.org
Package: transmission-daemon Version: 2.84-0.1+b1 Severity: important Dear Maintainer, The systemd .service file for transmission-daemon is broken, since it doesn't include the configuration option --config-dir as it does in the case of the standard init.d startup script. Hence the configuration can't be found when transmission-daemon is started via systemd, which is now the default init system with jessie. Locally I fixed the service file by placing the following snippet in /etc/systemd/service/transmission-daemon.service.d/fix_ExecStart.conf [Service] ExecStart= ExecStart=/usr/bin/transmission-daemon -f --log-error --config-dir=/var/lib/transmission-daemon/info The proper fix is of course to add the option in the installed service file /lib/systemd/system/transmission-daemon.service . Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750630: Acknowledgement (python-matplotlib: Default backend 'tkagg' broken)
The bug is caused by the new multiarch version of tk, which has the effect that matplotlib's setup file no longer finds the include header tk.h . There are two possible routes to resolve the bug: 1) Depend on tk-dev (matplotlib should build fine with tk8.6-dev), which contains /usr/lib/tkConfig.sh, and not on tk8.5-dev 2) Use the patch contained in the ubuntu package, which I have also attached to this mail. Best, Matthias On 06/05/2014 04:09 AM, Debian Bug Tracking System wrote: 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 matth...@liertzer.at (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 Python Modules Team python-modules-t...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 750...@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. Description: adapt setup to find multiarched tk/tcl Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/752647 Forwarded: no, only if we upstream multiarchification Author: Julian Taylor jtay...@ubuntu.com Index: matplotlib-1.3.1/setupext.py === --- matplotlib-1.3.1.orig/setupext.py 2013-10-29 07:19:22.483793802 +0100 +++ matplotlib-1.3.1/setupext.py 2013-10-29 07:20:01.504272247 +0100 @@ -1235,13 +1235,16 @@ except ImportError: return None +from distutils import sysconfig tcl_poss = [tcl_lib_dir, os.path.normpath(os.path.join(tcl_lib_dir, '..')), /usr/lib/tcl + str(Tkinter.TclVersion), +/usr/lib/%s/tcl%s % (sysconfig.get_config_var('MULTIARCH'), Tkinter.TclVersion), /usr/lib] tk_poss = [tk_lib_dir, os.path.normpath(os.path.join(tk_lib_dir, '..')), /usr/lib/tk + str(Tkinter.TkVersion), + /usr/lib/%s/tk%s % (sysconfig.get_config_var('MULTIARCH'), Tkinter.TkVersion), /usr/lib] for ptcl, ptk in zip(tcl_poss, tk_poss): tcl_config = os.path.join(ptcl, tclConfig.sh)
Bug#750630: Acknowledgement (python-matplotlib: Default backend 'tkagg' broken)
I just noticed that python itself nowadays depends on the default installation of tcl/tk. Hence, matplotlib should do the same as it is using the python tk interface. Best, Matthias On 06/08/2014 12:30 PM, Matthias Liertzer wrote: The bug is caused by the new multiarch version of tk, which has the effect that matplotlib's setup file no longer finds the include header tk.h . There are two possible routes to resolve the bug: 1) Depend on tk-dev (matplotlib should build fine with tk8.6-dev), which contains /usr/lib/tkConfig.sh, and not on tk8.5-dev 2) Use the patch contained in the ubuntu package, which I have also attached to this mail. Best, Matthias On 06/05/2014 04:09 AM, Debian Bug Tracking System wrote: 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 matth...@liertzer.at (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 Python Modules Team python-modules-t...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 750...@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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750630: python-matplotlib: Default backend 'tkagg' broken
Package: python-matplotlib Version: 1.3.1-1+b1 Severity: grave Justification: renders package unusable A simple script like #!/usr/bin/env python import numpy as np import matplotlib.pyplot as plt plt.figure() x = np.linspace(0, 1, 100) y = np.sin(x) plt.plot(x, y) plt.show() fails to show a plot and leads to the following error: Exception in Tkinter callback Traceback (most recent call last): File /usr/lib/python2.7/lib-tk/Tkinter.py, line 1489, in __call__ return self.func(*args) File /usr/lib/pymodules/python2.7/matplotlib/backends/backend_tkagg.py, line 276, in resize self.show() File /usr/lib/pymodules/python2.7/matplotlib/backends/backend_tkagg.py, line 349, in draw tkagg.blit(self._tkphoto, self.renderer._renderer, colormode=2) File /usr/lib/pymodules/python2.7/matplotlib/backends/tkagg.py, line 20, in blit tk.call(PyAggImagePhoto, photoimage, id(aggimage), colormode, id(bbox_array)) TclError In fact, I wasn't able to produce any plot using the default backend 'tkagg'. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-matplotlib depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.18-7 ii libcairo2 1.12.16-2 ii libfontconfig12.11.0-5 ii libfreetype6 2.5.2-1 ii libgcc1 1:4.9.0-5 ii libgdk-pixbuf2.0-02.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.23-1 ii libpango-1.0-01.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-0 1.36.3-1 ii libpng12-01.2.50-1 ii libstdc++64.9.0-5 ii python2.7.6-2 ii python-dateutil 1.5+dfsg-1 ii python-matplotlib-data1.3.1-1 ii python-numpy [python-numpy-abi9] 1:1.8.1-1 ii python-pyparsing 2.0.1+dfsg1-1 ii python-support1.0.15 ii python-tz 2012c-1 ii tcl8.58.5.15-4 ii tk8.5 8.5.15-4 Versions of packages python-matplotlib recommends: ii python-glade2 2.24.0-3+b1 ii python-imaging 2.3.0-2 ii python-tk 2.7.7-1 Versions of packages python-matplotlib suggests: ii dvipng 1.14-2 ii ghostscript9.05~dfsg-8.1 ii gir1.2-gtk-3.0 3.12.2-1 ii inkscape 0.48.4-4 ii ipython2.1.0-1 ii librsvg2-common2.40.2-1 ii python-cairo 1.8.8-1+b2 ii python-configobj 4.7.2+ds-5 pn python-excelerator none ii python-gobject 3.12.1-1 ii python-gtk22.24.0-3+b1 pn python-matplotlib-doc none ii python-nose1.3.3-1 pn python-qt4 none ii python-scipy 0.13.3-2 pn python-sip none ii python-tornado 3.2.0-1 pn python-traits none pn python-wxgtk2.8none ii texlive-extra-utils2014.20140528-2 ii texlive-latex-extra2014.20140528-2 pn ttf-staypuft 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#737727: Possible duplicate of #726483
Dear Matthias, Are you referring to the problem that when /etc/init.d/foobar.sh was called by invoke-rc.d foobar.sh ... the command failed? If so, this bug report is a duplicate of #726483, which has already been fixed in initscripts=2.88dsf-46. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732341: initscripts: invoke-rc.d should strip .sh suffix from name when invoking systemctl
reassign 732341 initscripts retitle 732341 initscripts: invoke-rc.d should strip .sh suffix from name when invoking systemctl tag 732341 patch thanks Hi, I stumbled upon the same bug as the original bug reporter. Systemd drops the .sh suffix from init scripts in /etc/init.d when translating sysv script filenames in /etc/init.d to a corresponding systemd .service name (see: http://sources.debian.net/src/systemd/204-5/src/core/service.c?hl=337#L337) Hence, invoke-rc.d should strip the .sh suffix as well, if present, before invoking systemctl. A patch for invoke-rc.d is attached. Best, Matthias diff -Nru sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d --- sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d 2013-07-14 22:57:26.0 +0200 +++ sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d 2013-12-19 22:20:51.0 +0100 @@ -390,7 +390,10 @@ if [ -n $is_upstart ]; then _executable=1 elif [ -n $is_systemd ]; then -_state=$(systemctl -p LoadState show ${INITSCRIPTID}.service 2/dev/null) +# For SysV services systemd strips the *.sh suffix +SYSTEMDSERVICE=${INITSCRIPTID%.sh}.service + +_state=$(systemctl -p LoadState show ${SYSTEMDSERVICE} 2/dev/null) if [ $_state != LoadState=masked ]; then _executable=1 fi @@ -517,27 +520,30 @@ # pick up any changes. systemctl daemon-reload fi + # For SysV services systemd strips the *.sh suffix +SYSTEMDSERVICE=${INITSCRIPTID%.sh}.service + case $saction in start|stop|restart|status) -systemctl ${saction} ${INITSCRIPTID}.service exit 0 +systemctl ${saction} ${SYSTEMDSERVICE} exit 0 ;; reload) -_canreload=$(systemctl -p CanReload show ${INITSCRIPTID}.service 2/dev/null) +_canreload=$(systemctl -p CanReload show ${SYSTEMDSERVICE} 2/dev/null) if [ $_canreload = CanReload=no ]; then ${INITDPREFIX}${INITSCRIPTID} ${saction} $@ exit 0 else -systemctl reload ${INITSCRIPTID}.service exit 0 +systemctl reload ${SYSTEMDSERVICE} exit 0 fi ;; force-stop) -systemctl --signal=KILL kill ${INITSCRIPTID}.service exit 0 +systemctl --signal=KILL kill ${SYSTEMDSERVICE} exit 0 ;; force-reload) -_canreload=$(systemctl -p CanReload show ${INITSCRIPTID}.service 2/dev/null) +_canreload=$(systemctl -p CanReload show ${SYSTEMDSERVICE} 2/dev/null) if [ $_canreload = CanReload=no ]; then - systemctl restart ${INITSCRIPTID}.service exit 0 + systemctl restart ${SYSTEMDSERVICE} exit 0 else - systemctl reload ${INITSCRIPTID}.service exit 0 + systemctl reload ${SYSTEMDSERVICE} exit 0 fi ;; *)
Bug#717661: New suspend functionality causes double-suspend for environments not supporting the inhibit API
Hi, I think I experience this bug as well. In my case I'm using GNOME from unstable and suspending the laptop by closing the lid results in the laptop not waking up when I open the lid again. However, if I suspend manually via the gnome menu, the PC wakes up as expected. Furthermore the bug doesn't appear when switching back to sysv. Regarding gnome-power-manager, isn't most of the logic regarding suspending and shutdown located in upower? I just had a quick look at the package and it seems to enable deprecated behavior in debian by default for enabling/disabling resume/suspend. From the debian changelog: * Add no_deprecation_define.patch: Do not require applications to define UPOWER_ENABLE_DEPRECATED to access suspend/resume functionality. We are not ready to do that yet in Debian. It would be clever to ask Martin Pitt about this, as he committed the last version of upower including this patch. Best, Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711065: gdm3 stuck in infinite loop
I can confirm the breakage of gdm3 as well after upgrading to the latest version of d-conf in unstable. The user session, however, doesn't seem to be affected. After installing lightdm, I can log into a gnome session and everything works so far (I'm using gnome+xmonad). Best, Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707008: dkms: should depend on python-apport
Package: dkms Version: 2.2.0.3-1.2 Severity: normal Dear Maintainer, while updating the system to the newest version of linux-headers in unstable (linux-headers-3.8-1-amd64), dkms failed to run the package hooks for dkms. The script in /usr/share/apport/package-hooks/dkms_packages.py failed because it imports the python module apport, which is, however, not installed on the machine. Installing python-apport and applying the following patch --- dkms_packages.py2013-05-06 20:02:05.102478775 + +++ /usr/share/apport/package-hooks/dkms_packages.py2013-05-06 20:00:26.940936271 + @@ -92,4 +92,4 @@ if options.kernel: report['DKMSKernelVersion'] = options.kernel -report.write(open(apport.fileutils.make_report_path(report), 'w')) +report.write(open(apport.fileutils.make_report_path(report), 'wb')) fixes the problem. Best, Matthias *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action?linux-headers-3.8-1-amd64 * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-1-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 Versions of packages dkms depends on: ii build-essential11.6 ii coreutils 8.20-3 ii dpkg-dev 1.16.10 ii gcc4:4.7.2-1 ii make 3.81-8.2 ii module-init-tools 9-3 ii patch 2.6.1-3 Versions of packages dkms recommends: ii fakeroot 1.18.4-2 ii linux-headers-3.2.0-4-amd64 [linux-headers] 3.2.41-2 ii linux-headers-3.8-1-amd64 [linux-headers]3.8.11-1 ii linux-headers-amd64 [linux-headers] 3.8+47 ii linux-image-3.2.0-4-amd64 [linux-image] 3.2.41-2 ii linux-image-3.8-1-amd64 [linux-image]3.8.11-1 ii menu 2.1.46 ii sudo 1.8.5p2-1+nmu1 dkms 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#663470: [Pkg-haskell-maintainers] Bug#663470: xmonad: Recommended packages of xmonad not installable on i386
Hi, I just checked today. The installation of xmonad is working as it should! This bug can be closed. Best regards, Matthias On 03/12/2012 09:32 AM, Matthias Liertzer wrote: Thanks for the quick reply, I'll try again in a few days! Best regards, Matthias On 03/11/2012 04:30 PM, Joachim Breitner wrote: Dear Matthias, Am Sonntag, den 11.03.2012, 16:03 +0100 schrieb Matthias Liertzer: Package: xmonad Version: 0.10-3+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to install the latest version of xmonad on one of my older (i386) computers failed to install all development-related packages for xmonad. As configuration is done by recompiling xmonad the package itself is rendered unusable for everyone who doesn't use the default config. In particular libghc-xmonad-contrib-dev, libghc-mtl-dev, libghc-x11-xft-dev, libghc-xmonad-dev, libghc-x11-dev, and libghc-transformers-dev can not be installed due to dependencies on virtual packages, which can't be resolved. thanks for the report. This is probably due to the upload of GHC that happend yesterday. I scheduled rebuild for all i386 packages today, so you should be good to go by later today or tomorrow. Please check again by then, and if you can install all that you need, please close the bug. Greetings, Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663470: [Pkg-haskell-maintainers] Bug#663470: xmonad: Recommended packages of xmonad not installable on i386
Thanks for the quick reply, I'll try again in a few days! Best regards, Matthias On 03/11/2012 04:30 PM, Joachim Breitner wrote: Dear Matthias, Am Sonntag, den 11.03.2012, 16:03 +0100 schrieb Matthias Liertzer: Package: xmonad Version: 0.10-3+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to install the latest version of xmonad on one of my older (i386) computers failed to install all development-related packages for xmonad. As configuration is done by recompiling xmonad the package itself is rendered unusable for everyone who doesn't use the default config. In particular libghc-xmonad-contrib-dev, libghc-mtl-dev, libghc-x11-xft-dev, libghc-xmonad-dev, libghc-x11-dev, and libghc-transformers-dev can not be installed due to dependencies on virtual packages, which can't be resolved. thanks for the report. This is probably due to the upload of GHC that happend yesterday. I scheduled rebuild for all i386 packages today, so you should be good to go by later today or tomorrow. Please check again by then, and if you can install all that you need, please close the bug. Greetings, Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663470: xmonad: Recommended packages of xmonad not installable on i386
Package: xmonad Version: 0.10-3+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to install the latest version of xmonad on one of my older (i386) computers failed to install all development-related packages for xmonad. As configuration is done by recompiling xmonad the package itself is rendered unusable for everyone who doesn't use the default config. In particular libghc-xmonad-contrib-dev, libghc-mtl-dev, libghc-x11-xft-dev, libghc-xmonad-dev, libghc-x11-dev, and libghc-transformers-dev can not be installed due to dependencies on virtual packages, which can't be resolved. The same bug was present for amd64 a few months ago, but was quickly fixed back then. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xmonad depends on: ii libc6 2.13-27 ii libffi5 3.0.10-3 ii libgmp10 2:5.0.4+dfsg-1 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxinerama1 2:1.1.1-3 ii x11-utils 7.6+4 Versions of packages xmonad recommends: ii libghc-xmonad-dev none ii libghc-xmonad-doc none ii xfonts-base1:1.0.3 Versions of packages xmonad suggests: ii suckless-tools [dmenu] 38-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648015: chromium: fails to render any web page
Package: chromium Version: 15.0.874.106~r107270-1 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading to the latest version of chromium in unstable, the browser can no longer be used easily as I get an Aw, Snap! on each website I try to load. This occurs even for the start page of the browser (i.e. favorites). Deleting .config/chromium doesn't help either, so the problem seems to be directly related to the latest version of chromium in unstable. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 15.0.874.106~r107270-1 ii libasound2 1.0.24.1-4 ii libavcodec535:0.8.6-0.1 ii libavformat53 5:0.8.6-0.1 ii libavutil51 5:0.8.6-0.1 ii libbz2-1.0 1.0.5-7 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libcups21.5.0-10 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-20.98-1 ii libevent-1.4-2 1.4.14b-stable-1 ii libexpat1 2.0.1-7.2 ii libflac81.2.1-6 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.7-2 ii libgcc1 1:4.6.2-4 ii libgconf2-4 2.32.4-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.28.8-1 ii libgtk2.0-0 2.24.7-1 ii libjpeg88c-2 ii libnspr4-0d 4.8.9-1 ii libnss3-1d 3.13.1.with.ckbi.1.88-1 ii libpango1.0-0 1.29.4-2 ii libpng12-0 1.2.46-3 ii libspeex1 1.2~rc1-1 ii libstdc++6 4.6.2-4 ii libvpx0 0.9.7.p1-2 ii libwebp20.1.3-1 ii libx11-62:1.4.4-2 ii libxext62:1.3.0-3 ii libxml2 2.7.8.dfsg-5 ii libxrender1 1:0.9.6-2 ii libxslt1.1 1.1.26-8 ii libxss1 1:1.2.1-2 ii xdg-utils 1.1.0~rc1-2 ii zlib1g 1:1.2.3.4.dfsg-3 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n 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#645046: git-annex stops working with git v1.7.7
Package: git-annex Version: 3.20110928 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading git to version 1.7.7, git-annex is no longer able to retrieve data from remotes. Test case: $ $ cd /tmp/ $ mkdir annex1 $ cd annex1 $ git init Initialized empty Git repository in /tmp/annex1/.git/ $ git annex init test annex init test annex ok $ echo 123 blubb $ git annex add . add blubb ok (Recording state in git...) $ git commit -m add blubb [master (root-commit) 401da9d] add blubb 1 files changed, 1 insertions(+), 0 deletions(-) create mode 12 blubb $ cd /tmp $ git clone annex1 annex2 Cloning into annex2... done. $ cd annex2 $ git annex init test annex2 init test annex2 (merging origin/git-annex into git-annex...) ok $ git annex get . fatal: Could not switch to '.git/annex/objects/6f/v3/WORM-s4-m1318381546--blubb': No such file or directory Switching back to git v1.7.6.3 solves the issue. Best regards, Matthias -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-annex depends on: ii curl7.21.7-3 ii git [git-core] 1:1.7.7-1 ii libc6 2.13-21 ii libffi5 3.0.10-2 ii libgmp102:5.0.2+dfsg-1 ii libpcre38.12-4 ii openssh-client 1:5.9p1-1 ii rsync 3.0.8-1 ii uuid1.6.2-1.1 ii wget1.13-1 git-annex recommends no packages. Versions of packages git-annex suggests: ii bup none ii gnupg 1.4.11-3 ii graphviz 2.26.3-7 -- 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#628965: virtualbox-guest-additions-iso: recommends transitional package virtualbox-ose
Package: virtualbox-guest-additions-iso Version: 4.0.8-1 Severity: minor virtualbox-guest-additions-iso should instead recommend the virtualbox package -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash virtualbox-guest-additions-iso depends on no packages. Versions of packages virtualbox-guest-additions-iso recommends: ii virtualbox-ose 4.0.8-dfsg-1 transitional package for virtualbo virtualbox-guest-additions-iso 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#571414: xmobar crashes when receiving unicode characters from standard input
Package: xmobar Version: 0.9.2-2 Severity: important xmobar crashes when receiving utf8 characters from standard input this bug only occurs when being built wiht ghc 6.12 an upstream fix is available from http://code.google.com/p/xmobar/issues/detail?id=17#c8 Another possiblity would be to compile xmonad without utf support. (UTF8 support is now in ghc 6.12, so this actually doesn't disable utf support, it just disables the usage of the now outdated utf library) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-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/bash Versions of packages xmobar depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libffi5 3.0.9-1Foreign Function Interface library ii libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library ii libx11-6 2:1.3.3-1 X11 client-side library ii libxext6 2:1.1.1-2 X11 miscellaneous extension librar ii libxft2 2.1.14-1 FreeType-based font drawing librar ii libxinerama1 2:1.1-2X11 Xinerama extension library Versions of packages xmobar recommends: ii curl 7.19.7-1 Get a file from an HTTP, HTTPS or Versions of packages xmobar suggests: ii xmonad0.9.1-2+b1 A lightweight X11 window manager -- 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#538637: defect in binary xserver-xorg-core package disables compositing with kwin in KDE 4.2
Could you send the list of version of packages that you have installed for each build-depends of the server? ii debhelper7.3.8 ii quilt0.46-7 ii lsb-release 3.2-23 ii pkg-config 0.22-1 ii bison1:2.4.1.dfsg-2 ii flex 2.5.35-7 ii automake 1:1.10.2-1 ii libtool 2.2.6a-4 ii xutils-dev 1:7.4+4 ii x11proto-bigreqs-dev 1:1.0.2-5 ii x11proto-composite-dev 1:0.4-2 ii x11proto-core-dev7.0.15-1 ii x11proto-damage-dev 1.1.0-2 ii x11proto-fixes-dev 1:4.0-3 ii x11proto-kb-dev 1.0.3-3 ii x11proto-xinerama-dev1.1.2-5 ii x11proto-randr-dev 1.3.0-1 ii x11proto-record-dev 1.13.2-5 ii x11proto-render-dev 2:0.9.3-2 ii x11proto-resource-dev1.0.2-5 ii x11proto-scrnsaver-dev 1.1.0.0-2 ii x11proto-video-dev 2.2.2-5 ii x11proto-xcmisc-dev 1.1.2-5 ii x11proto-xext-dev7.0.4-2 ii x11proto-xf86bigfont-dev 1.1.2-5 ii x11proto-xf86dga-dev 2.0.3-1 ii x11proto-xf86vidmode-dev 2.2.2-5 ii xtrans-dev 1.2.3-3 ii libxau-dev 1:1.0.4-2 ii x11proto-input-dev 1.5.0-2 ii x11proto-dri2-dev2.1-1 ii libxdmcp-dev 1:1.0.2-3 ii libxfont-dev 1:1.4.0-1 ii libfontenc-dev 1:1.0.4-3 ii libxkbfile-dev 1:1.0.5-1 ii libpixman-1-dev 0.14.0-1 ii libpciaccess-dev 0.10.6-1 ii libdbus-1-dev1.2.16-2 ii libhal-dev 0.5.12~git20090406.46dc48-2 ii libselinux1-dev 2.0.82-1 ii libaudit-dev 1.7.13-1 ii x11proto-xf86dri-dev 2.0.4-1 ii libdrm-dev 2.4.12-1 ii x11proto-gl-dev 1.4.10-1 ii mesa-common-dev 7.5-3 ii libgl1-mesa-dev 7.5-3 ii libxmuu-dev 2:1.0.4-1 ii libxext-dev 2:1.0.4-1 ii libx11-dev 2:1.2.2-1 ii libxrender-dev 1:0.9.4-2 ii libxi-dev2:1.2.1-2 ii x11proto-dmx-dev 1:2.2.2-5 ii libdmx-dev 1:1.0.2-3 ii libxpm-dev 1:3.5.7-2 ii libxaw7-dev 2:1.0.5-2 ii libxt-dev1:1.0.5-3 ii libxmu-dev 2:1.0.4-1 ii libxtst-dev 2:1.0.3-1 ii libxres-dev 2:1.0.3-1 ii libxfixes-dev1:4.0.3-2 ii libxv-dev2:1.0.4-1 ii libxinerama-dev 2:1.0.3-2 Was your unstable totally uptodate when you rebuilt the package? my unstable was totally uptodate ( I executed aptitude -PV full-upgrade right before I build the package to be sure ) Also it would be nice to know if this problem only occurs on amd64 (I uploaded the package for i386) UnfortunateIy I can only confirm that the bug appears on the amd64 platform. I don't have debian ia32 installed on my laptop. /Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538637: defect in binary xserver-xorg-core package disables compositing with kwin in KDE 4.2
Could you send the list of version of packages that you have installed for each build-depends of the server? ii debhelper7.3.8 ii quilt0.46-7 ii lsb-release 3.2-23 ii pkg-config 0.22-1 ii bison1:2.4.1.dfsg-2 ii flex 2.5.35-7 ii automake 1:1.10.2-1 ii libtool 2.2.6a-4 ii xutils-dev 1:7.4+4 ii x11proto-bigreqs-dev 1:1.0.2-5 ii x11proto-composite-dev 1:0.4-2 ii x11proto-core-dev7.0.15-1 ii x11proto-damage-dev 1.1.0-2 ii x11proto-fixes-dev 1:4.0-3 ii x11proto-kb-dev 1.0.3-3 ii x11proto-xinerama-dev1.1.2-5 ii x11proto-randr-dev 1.3.0-1 ii x11proto-record-dev 1.13.2-5 ii x11proto-render-dev 2:0.9.3-2 ii x11proto-resource-dev1.0.2-5 ii x11proto-scrnsaver-dev 1.1.0.0-2 ii x11proto-video-dev 2.2.2-5 ii x11proto-xcmisc-dev 1.1.2-5 ii x11proto-xext-dev7.0.4-2 ii x11proto-xf86bigfont-dev 1.1.2-5 ii x11proto-xf86dga-dev 2.0.3-1 ii x11proto-xf86vidmode-dev 2.2.2-5 ii xtrans-dev 1.2.3-3 ii libxau-dev 1:1.0.4-2 ii x11proto-input-dev 1.5.0-2 ii x11proto-dri2-dev2.1-1 ii libxdmcp-dev 1:1.0.2-3 ii libxfont-dev 1:1.4.0-1 ii libfontenc-dev 1:1.0.4-3 ii libxkbfile-dev 1:1.0.5-1 ii libpixman-1-dev 0.14.0-1 ii libpciaccess-dev 0.10.6-1 ii libdbus-1-dev1.2.16-2 ii libhal-dev 0.5.12~git20090406.46dc48-2 ii libselinux1-dev 2.0.82-1 ii libaudit-dev 1.7.13-1 ii x11proto-xf86dri-dev 2.0.4-1 ii libdrm-dev 2.4.12-1 ii x11proto-gl-dev 1.4.10-1 ii mesa-common-dev 7.5-3 ii libgl1-mesa-dev 7.5-3 ii libxmuu-dev 2:1.0.4-1 ii libxext-dev 2:1.0.4-1 ii libx11-dev 2:1.2.2-1 ii libxrender-dev 1:0.9.4-2 ii libxi-dev2:1.2.1-2 ii x11proto-dmx-dev 1:2.2.2-5 ii libdmx-dev 1:1.0.2-3 ii libxpm-dev 1:3.5.7-2 ii libxaw7-dev 2:1.0.5-2 ii libxt-dev1:1.0.5-3 ii libxmu-dev 2:1.0.4-1 ii libxtst-dev 2:1.0.3-1 ii libxres-dev 2:1.0.3-1 ii libxfixes-dev1:4.0.3-2 ii libxv-dev2:1.0.4-1 ii libxinerama-dev 2:1.0.3-2 Was your unstable totally uptodate when you rebuilt the package? my unstable was totally uptodate ( I executed aptitude -PV full-upgrade right before I build the package to be sure ) Also it would be nice to know if this problem only occurs on amd64 (I uploaded the package for i386) UnfortunateIy I can only confirm that the bug appears on the amd64 platform. I don't have debian ia32 installed on my laptop. /Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org