Bug#942823: linux-image-5.3.0-1-amd64: Dell XPS 13 gets stuck on sddm login screen at boot
Package: src:linux Version: 5.3.7-1 Severity: important Dear Maintainer, When booting this kernel image on my Dell XPS 13 laptop, the sddm login screen comes up, and I can enter my password, but nothing happens when I hit return. I switched to a virtual terminal, where I saw error messages like this: Oct 21 21:10:26 vortex kernel: [8.810386] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270503 Oct 21 21:10:27 vortex kernel: [9.814405] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370503 Oct 21 21:10:28 vortex kernel: [ 10.818466] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Oct 21 21:10:29 vortex kernel: [ 11.822460] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270d00 Oct 21 21:10:30 vortex kernel: [ 12.830446] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270d00 Oct 21 21:10:32 vortex kernel: [ 14.846233] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270503 Oct 21 21:10:33 vortex kernel: [ 15.850222] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370503 Oct 21 21:10:34 vortex kernel: [ 16.862221] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Oct 21 21:10:36 vortex kernel: [ 18.902451] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270503 Oct 21 21:10:37 vortex kernel: [ 19.910446] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370503 Oct 21 21:10:38 vortex kernel: [ 20.914420] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Oct 21 21:10:41 vortex kernel: [ 22.954258] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270503 Oct 21 21:10:42 vortex kernel: [ 23.962414] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370503 Oct 21 21:10:43 vortex kernel: [ 24.970253] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Oct 21 21:10:45 vortex kernel: [ 27.010253] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270503 Oct 21 21:10:46 vortex kernel: [ 28.022444] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370503 Oct 21 21:10:47 vortex kernel: [ 29.034417] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Oct 21 21:10:49 vortex kernel: [ 31.078240] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20270503 Oct 21 21:10:50 vortex kernel: [ 32.086235] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370503 These messages continue as long as I care to wait. I had to reboot using the previous kernel to use my computer again. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: XPS 13 9360 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 2.3.1 board_vendor: Dell Inc. board_name: 0PF86Y board_version: A00 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 03) Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1028:075b] 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 Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell Iris Plus Graphics 640 [1028:075b] 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: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 03) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:075b] 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: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
Bug#920650: fluidsynth: New major version released upstream: please upgrade to 2.x
Package: fluidsynth Version: 1.1.11-1 Severity: wishlist The fluidsynth project has released a new major version; they are currently on 2.0.3 as of this bug report. I hope the whole fluidsynth package ecosystem (e.g. libfluidsynth, libfluidsynth-dev) will soon be upgraded to this version. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fluidsynth depends on: ii libc6 2.28-5 ii libfluidsynth1 1.1.11-1 Versions of packages fluidsynth recommends: ii qsynth 0.5.0-2 fluidsynth suggests no packages. -- no debconf information
Bug#910345: Actually, it may not be fixed.
I went to grab the patch that supposedly fixed the problem from https://github.com/mate-desktop/mate-panel/pull/845/commits/a130fb0379a270f6ed80fa21ba2a69e184b4cc2a and I find that has already been applied to the debian source. That fix adds conditional compilation for versions of GTK < 3.23, and sid is already on 3.24, so that fix would be irrelevant anyway. Is this a regression?
Bug#910345: Should be fixed by upgrading to upstream version 1.21.x
I misread version numbers; you haven't packaged the version which has the fix for this critical issue. All that needs to be done is to package the next version of MATE. I hope this happens soon. Forrest
Bug#910345: Severity is actually 'important'
I should have classified this bug as 'important', because there's significant functionality I can't access and for which the workarounds are difficult or nonexistent. In particular, the truncation of the notification area keeps me from using all but the leftmost two widgets. I have to close the bluetooth and iBus widgets for the wifi widget to be available, and then I can only see the two lowest strength bar. I haven't seen the battery widget in months, since this bug first appeared. I believe there's some right-click functionality to that widget as well but I'll never be able to see or much less use it until this bug is fixed (or I switch desktop environments, which sadly may be necessary if this can't be fixed). I've confirmed that if I set /org/mate/desktop-interface/window-scaling-factor to 1 using dconf-editor, the notification area and other truncated applets are fully displayed. Of course they are too tiny to be useful at this resolution. It would appear that the width calculation for these applets is ignoring the window-scaling-factor, as they appear to be exactly half as wide as expected. Is there anything I can do to help resolve this issue? I've started looking at the source code but MATE is a large project and hard to get a handle on. I indicated an upstream bug in my initial report which sounds _exactly_ like the issue I'm experiencing, however looking at the version numbers of MATE and GTK3 seem to indicate that the fix for that should already be in this Debian package. I think that, somehow, it must not be. Forrest
Bug#910345: mate-panel: Some panel applets are narrow and truncated on HiDPI screen
Package: mate-panel Version: 1.20.3-1 Severity: normal Tags: patch Some MATE panel applets are narrow and only the left part is visible. This may have to do with the fact I have a HiDPI screen. The notification area only shows me bluetooth & ibus statuses; sound, network, and battery indicators do not appear in the allocated width. The clock applet shows a weather icon and the day of the week; anything to the right of that is truncated. The window list and show desktop button applets are half-width, but usable (with difficulty). The workspace switcher applet is narrow, but appears to be scaled rather than truncated so it is usable. Menu and launcher applets are not affected. This issue seems very much like the one reported upstream at https://github.com/mate-desktop/mate-panel/issues/843 , but that is reported to have been fixed. Attached is a screenshot showing the truncated clock applet. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-panel depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.0-1 ii libatk1.0-0 2.30.0-1 ii libc62.27-6 ii libcairo-gobject21.15.12-1 ii libcairo21.15.12-1 ii libdbus-1-3 1.12.10-1 ii libdbus-glib-1-2 0.110-3 ii libdconf10.30.0-1 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6 ii libglib2.0-0 2.58.1-2 ii libgtk-3-0 3.24.1-2 ii libice6 2:1.0.9-2 ii libmate-desktop-2-17 1.20.3-2 ii libmate-menu21.20.1-1 ii libmate-panel-applet-4-1 1.20.3-1 ii libmateweather1 1.20.1-1 ii libpango-1.0-0 1.42.4-3 ii libpangocairo-1.0-0 1.42.4-3 ii librsvg2-2 2.40.20-3 ii libsm6 2:1.2.2-1+b3 ii libstartup-notification0 0.12-5 ii libwnck-3-0 3.30.0-1 ii libx11-6 2:1.6.6-1 ii libxau6 1:1.0.8-1+b2 ii libxrandr2 2:1.5.1-1 ii mate-desktop 1.20.3-2 ii mate-menus 1.20.1-1 ii mate-panel-common1.20.3-1 ii mate-polkit 1.20.1-1 ii menu-xdg 0.5 mate-panel recommends no packages. mate-panel suggests no packages. -- no debconf information
Bug#823160: musescore: Playback volume inside of MuseScore is low
Package: musescore Version: 2.0.2+dfsg-2 Severity: normal Dear Maintainer, When playing back music inside of MuseScore, the volume is really low. Exporting to wav and playing back has a decent volume; I think that playing from inside MuseScore should match that. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.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 musescore depends on: ii desktop-file-utils 0.22-1 ii libasound2 1.1.0-1 ii libc62.22-7 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:5.3.1-15 ii libogg0 1.3.2-1 ii libportaudio219+svn20140130-1 ii libpulse08.0-2+b2 ii libqt5concurrent55.5.1+dfsg-16+b1 ii libqt5core5a [qtbase-abi-5-5-1] 5.5.1+dfsg-16+b1 ii libqt5designer5 5.5.1-3 ii libqt5gui5 5.5.1+dfsg-16+b1 ii libqt5help5 5.5.1-3 ii libqt5network5 5.5.1+dfsg-16+b1 ii libqt5printsupport5 5.5.1+dfsg-16+b1 ii libqt5qml5 5.5.1-3 ii libqt5quick5 5.5.1-3 ii libqt5quickwidgets5 5.5.1-3 ii libqt5sql5 5.5.1+dfsg-16+b1 ii libqt5sql5-sqlite5.5.1+dfsg-16+b1 ii libqt5svg5 5.5.1-2 ii libqt5test5 5.5.1+dfsg-16+b1 ii libqt5webkit55.5.1+dfsg-2+b1 ii libqt5widgets5 5.5.1+dfsg-16+b1 ii libqt5xml5 5.5.1+dfsg-16+b1 ii libqt5xmlpatterns5 5.5.1-2 ii libsndfile1 1.0.25-10 ii libstdc++6 5.3.1-15 ii libvorbis0a 1.3.5-3 ii libvorbisfile3 1.3.5-3 ii musescore-common 2.0.2+dfsg-2 ii qml-module-qtquick-controls 5.5.1-2 ii qml-module-qtquick-layouts 5.5.1-2 ii qml-module-qtquick2 5.5.1-3 ii shared-mime-info 1.5-2 ii xdg-utils1.1.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages musescore recommends: ii pulseaudio-utils 8.0-2+b2 Versions of packages musescore suggests: ii fluid-soundfont-gm 3.1-5 pn timgm6mb-soundfont -- no debconf information
Bug#768524: I'm also waiting for Musescore 2.x to be packaged
I'm also waiting for Musescore 2.x to be packaged, and am willing to help, if there's something I can do. Forrest
Bug#787788: [Pkg-alsa-devel] Bug#787788: alsa-utils: snd_seq and snd_seq_midi modules no longer loaded
I discovered that on plugging in a USB MIDI device, the module snd_seq_device is loaded, bringing with it the dependency snd_rawmidi. This would suffice for apps which use the raw MIDI interface, but not the sequencer MIDI interface. I have always used the latter, and until recently this has worked. I think that if the snd_seq_midi module could be loaded at the same time, using the same mechanism as the snd_seq_device module gets loaded, that would be the optimal solution. On Fri, Jun 5, 2015 at 2:16 PM, Elimar Riesebieter riese...@lxtec.de wrote: * Forrest Cahoon forrest.cah...@gmail.com [2015-06-04 21:55 -0500]: Package: alsa-utils Version: 1.0.28-1 Severity: normal Kernel modules snd_seq and snd_seq_midi are no longer loaded at boot in Debian unstable. I apologize if this is the wrong package; this functionality was formerly implemented in alsa-base, but that is a dummy package now. I believe this continued to work for some time after the alsa-base implementation went away though, so I think this functionality was maintained in the switch but recently became broken. The mentioned drivers (modules) should be loaded dynamically by kmod if required from a midi device. Please test it. Elimar -- Experience is something you don't get until just after you need it!
Bug#787788: alsa-utils: snd_seq and snd_seq_midi modules no longer loaded
Package: alsa-utils Version: 1.0.28-1 Severity: normal Kernel modules snd_seq and snd_seq_midi are no longer loaded at boot in Debian unstable. I apologize if this is the wrong package; this functionality was formerly implemented in alsa-base, but that is a dummy package now. I believe this continued to work for some time after the alsa-base implementation went away though, so I think this functionality was maintained in the switch but recently became broken. I fixed this on my own system by creating the file /etc/modules-load.d/alsa- seq.conf with the contents snd_seq_midi Since snd_seq_midi depends on snd_seq, this one line loads all the required modules. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.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 alsa-utils depends on: ii kmod20-1 ii libasound2 1.0.28-1 ii libc6 2.19-18 ii libncursesw55.9+20150516-2 ii libsamplerate0 0.1.8-8 ii libtinfo5 5.9+20150516-2 ii lsb-base4.1+Debian13+nmu1 ii whiptail0.52.17-1+b1 alsa-utils recommends no packages. alsa-utils 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#787393: base: snd_seq_midi module no longer loaded on boot
Package: base Severity: normal I know I was able to use MIDI input devices on my computer on Monday 2015-05-25, but something happened after an aptitude full-upgrade so that they stopped working by Thursday 2015-05-28. I tracked the issue down to the fact that the kernel module snd_seq_midi is no longer getting loaded; modprobe snd_seq_midi restores the functionality. How did this module get loaded before? What is the best way to ensure it is always loaded? -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768918: pulseaudio: Streams do not switch to correct sink when USB speakers are removed
Package: pulseaudio Version: 5.0-13 Severity: normal I have added these lines to my /etc/pulse/default.pa: # fc-added set-default-sink alsa_output.pci-_00_1b.0.analog-stereo set-default-source alsa_input.pci-_00_1b.0.analog-stereo load-module module-switch-on-connect These define a default sink (and source), and loads module-switch-on-connect, which correctly causes pulseaudio to switch any playing streams to my external USB speakers when I plug them in. I expect that when i unplug the USB speakers, playing streams will return to the default sink which I have defined in my config. This does not happen. What happens is that pulseaudio switches the stream to its sink #0, which is an HDMI audio device that is not connected to any output. When I check the default sink again after having unplugged the USB device by checking the output of pacmd list-sinks and looking for the asterisk, it is correctly set back to the default I've defined in my config. My suspicion is that the module module-rescue-streams, which is responsible for switching streams once a sink becomes unavailable, is being called _before_ the default sink is set back from the USB device to the config-defined default device, and it is choosing the first available sink it finds, which is #0. (The function find_evacuation_source in module-rescue-streams.c looks like it would do that, although I haven't been able run it in the debugger and set a breakpoint to check.) -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-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 pulseaudio depends on: ii adduser 3.113+nmu3 ii libasound21.0.28-1 ii libasound2-plugins1.0.28-1+b1 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libdbus-1-3 1.8.8-2 ii libfftw3-single3 3.3.4-1.1 ii libgcc1 1:4.9.2-1 ii libice6 2:1.0.9-1 ii libltdl7 2.4.2-1.11 ii liborc-0.4-0 1:0.4.22-1 ii libpulse0 5.0-13 ii libsamplerate00.1.8-8 ii libsm62:1.2.2-1 ii libsndfile1 1.0.25-9+b1 ii libspeexdsp1 1.2~rc1.2-1 ii libstdc++64.9.2-1 ii libsystemd0 215-5+b1 ii libtdb1 1.3.1-1 ii libudev1 215-5+b1 ii libwebrtc-audio-processing-0 0.1-3 ii libx11-6 2:1.6.2-3 ii libx11-xcb1 2:1.6.2-3 ii libxcb1 1.10-3+b1 ii libxtst6 2:1.2.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii pulseaudio-utils 5.0-13 ii udev 215-5+b1 Versions of packages pulseaudio recommends: ii pulseaudio-module-x11 5.0-13 ii rtkit 0.11-1 Versions of packages pulseaudio suggests: pn pamannone pn paprefs none ii pavucontrol 2.0-3 pn pavumeternone -- Configuration Files: /etc/pulse/default.pa changed: ..nofail ..fail load-module module-device-restore load-module module-stream-restore load-module module-card-restore load-module module-augment-properties load-module module-switch-on-port-available ..ifexists module-udev-detect.so load-module module-udev-detect ..else load-module module-detect ..endif ..ifexists module-jackdbus-detect.so ..nofail load-module module-jackdbus-detect channels=2 ..fail ..endif ..ifexists module-bluetooth-policy.so load-module module-bluetooth-policy ..endif ..ifexists module-bluetooth-discover.so load-module module-bluetooth-discover ..endif ..ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix ..endif load-module module-native-protocol-unix ..ifexists module-gconf.so ..nofail load-module module-gconf ..fail ..endif load-module module-default-device-restore load-module module-rescue-streams load-module module-always-sink load-module module-intended-roles load-module module-suspend-on-idle ..ifexists module-console-kit.so load-module module-console-kit ..endif ..ifexists module-systemd-login.so load-module module-systemd-login ..endif load-module module-position-event-sounds load-module module-role-cork load-module module-filter-heuristics load-module module-filter-apply set-default-sink alsa_output.pci-_00_1b.0.analog-stereo set-default-source alsa_input.pci-_00_1b.0.analog-stereo load-module module-switch-on-connect -- no debconf information # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify #
Bug#760340: [Pkg-xfce-devel] Bug#760340: xfce4-battery-plugin: Only updates when I log in to xfce
On Thu, Sep 4, 2014 at 1:16 AM, Yves-Alexis Perez cor...@debian.org wrote: Please keep the bug on CC:, this is not a support channel Sorry, I thought there would be a Reply-To header to take care of that. On jeu., 2014-09-04 at 00:55 -0500, Forrest Cahoon wrote: It may be xfce4-power-manager. I'm referring to the icon that looks like a battery which has a picture of a power plug next to it when the computer is plugged in. I just added a panel applet I hadn't noticed before called Battery Monitor which shows a bar for the battery level which is blue when the AC is plugged in, but green when running on battery power. That one appears to work OK. So no, not the power manager (the plugin is called “Power Manager Plugin”). When I right-click on the panel and choose Panel - Add New Items, I do not see anything with Power in the name in the item list. Is there where you meant to look? I do have these debian packages installed: forrest@makemake:~$ dpkg -l | grep xfce4 | grep power ii xfce4-power-manager1.2.0-5amd64 power manager for Xfce desktop ii xfce4-power-manager-data 1.2.0-5allpower manager for Xfce desktop, arch-indep files ii xfce4-power-manager-plugin 1.2.0-5amd64 power manager plugins for Xfce panel As far as I know the battery plugin directly uses sysfs so if it's broken that somehow means the kernel gives it bad information. I'll try to check the plugin here. I've attached a picture: the battery picture on the left is the broken one; the bar with a percent on the right is the correctly working Battery Monitor. The left one seems to be the previous power manager, so I think you're not up to date in Jessie. I'm actually running sid, and I did an aptitude full-upgrade yesterday (after I had originally submitted this bug), and the problem remains. -- Yves-Alexis
Bug#760340: [Pkg-xfce-devel] Bug#760340: Bug#760340: xfce4-battery-plugin: Only updates when I log in to xfce
On Thu, Sep 4, 2014 at 1:58 PM, Yves-Alexis Perez cor...@debian.org wrote: Nevermind, it's not yet transitioned to the panel plugin in jessie/sid, sorry for the confusion. So, xfpm is running in the system tray (in your initial screenshot, that's the battery+plug on the left part). The battery plugin is the green one with the 98%. Which one works and which one doesn't That means xfpm is broken, as I had unplugged my laptop for several minutes at that point and the icon still shows the plug. The battery plugin (which I didn't know about until after I submitted this bug) is working correctly. Sorry if I got the wrong package. Regards, -- Yves-Alexis
Bug#755234: Workaround is to install which packages from experimental?
I have the same issue, and having read through this bug it sounds like installing some packages out of experimental fixes it, but I didn't catch exactly which packages. I understand the risks of installing stuff out of experimental, and I still want to give it a try. Can someone please tell me exactly which packages I need to install? Forrest
Bug#760340: xfce4-battery-plugin: Only updates when I log in to xfce
Package: xfce4-battery-plugin Version: 1.0.5-2 Severity: normal Dear Maintainer, xfce4-battery-plugin is only updating for me when I log out and log back in. This is especially a problem when I don't notice my laptop charger has been unplugged until the battery runs out :-( -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-battery-plugin depends on: ii libatk1.0-0 2.12.0-1 ii libc62.19-10 ii libcairo21.12.16-3 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-1.1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-5 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-0 1.36.6-1 ii libpangocairo-1.0-0 1.36.6-1 ii libpangoft2-1.0-01.36.6-1 ii libxfce4ui-1-0 4.10.0-5 ii libxfce4util64.10.1-1 ii xfce4-panel 4.10.1-1 xfce4-battery-plugin recommends no packages. xfce4-battery-plugin 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#707781: What is the status of this ITP? Can I try to package it?
I would like to have this package, and I see this ITP is over a year old. I am relatively new to the packaging process, but I'm working on trying to make this package for my own edification right now. I hope to be able to submit my package if it's not being actively worked on otherwise. Forrest Cahoon
Bug#759190: csound: The STKSitar opcode can create a buildup of clipped samples as illustrated by the attached csd file
Package: csound Version: 1:6.03.2~dfsg-1 Severity: normal The following CSD produces unexpected output: this may be a problem with Csound, or STK, or both -- I'm filing this as a Csound bug because that's the application I'm using when I experience the problem. The CSD has two descending tone sequences played with the STKSitar opcode. The duration of each note is 0.4 seconds and they are played 0.1 seconds apart, so there should be no more than 4 notes playing simultaneously. Towards the end of the first descending sequence, the volume shoots up dramatically, creating a great deal of distortion. There is a pause of 1.0 seconds before the second descending sequence, which should be adequate for all notes from the first sequence to complete. Yet when the second sequence plays, the distortion occurs almost immediately, on notes which played without issue during the first tone sequence. It appears that some sort of buffer is building up and not being flushed adequately, but that's just speculation. CsoundSynthesizer CsInstruments sr=48000 ksmps=1 nchnls=2 0dbfs=1 instr 1 ;STKSitar iAmpl = 0.2 iFreq = p4 aOut STKSitar iFreq, iAmpl outs aOut, aOut endin /CsInstruments CsScore i1 0.0 0.4 1024.0 i1 ^+0.1 . 960.0 i1 ^+0.1 . 896.0 i1 ^+0.1 . 853. i1 ^+0.1 . 768.0 i1 ^+0.1 . 731.4286 i1 ^+0.1 . 716.8 i1 ^+0.1 . 682.6667 i1 ^+0.1 . 640.0 i1 ^+0.1 . 597. i1 ^+0.1 . 512.0 i1 ^+0.1 . 480.0 i1 ^+0.1 . 448.0 i1 ^+0.1 . 426.6 i1 ^+0.1 . 384.0 i1 ^+0.1 . 365.7143 i1 ^+0.1 . 358.4 i1 ^+0.1 . 341.4 i1 ^+0.1 . 320.0 i1 ^+0.1 . 298.6 i1 ^+0.1 . 256.0 i1 ^+0.1 . 240.0 i1 ^+0.1 . 224.0 i1 ^+0.1 . 213.3 i1 ^+0.1 . 192.0 i1 ^+0.1 . 182.85715 i1 ^+0.1 . 179.2 i1 ^+0.1 . 170.7 i1 ^+0.1 . 160.0 i1 ^+0.1 . 149.3 i1 ^+0.1 . 128.0 i1 ^+0.1 . 120.0 i1 ^+0.1 . 112.0 i1 ^+0.1 . 106.64 i1 ^+0.1 . 96.0 i1 ^+0.1 . 91.42857 i1 ^+0.1 . 89.6 i1 ^+0.1 . 85.36 i1 ^+0.1 . 80.0 i1 ^+0.1 . 74.64 i1 ^+0.1 . 64.0 i1 ^+1.0 . 1024.0 i1 ^+0.1 . 960.0 i1 ^+0.1 . 896.0 i1 ^+0.1 . 853. i1 ^+0.1 . 768.0 i1 ^+0.1 . 731.4286 i1 ^+0.1 . 716.8 i1 ^+0.1 . 682.6667 i1 ^+0.1 . 640.0 i1 ^+0.1 . 597. i1 ^+0.1 . 512.0 i1 ^+0.1 . 480.0 i1 ^+0.1 . 448.0 i1 ^+0.1 . 426.6 i1 ^+0.1 . 384.0 i1 ^+0.1 . 365.7143 i1 ^+0.1 . 358.4 i1 ^+0.1 . 341.4 i1 ^+0.1 . 320.0 i1 ^+0.1 . 298.6 i1 ^+0.1 . 256.0 i1 ^+0.1 . 240.0 i1 ^+0.1 . 224.0 i1 ^+0.1 . 213.3 i1 ^+0.1 . 192.0 i1 ^+0.1 . 182.85715 i1 ^+0.1 . 179.2 i1 ^+0.1 . 170.7 i1 ^+0.1 . 160.0 i1 ^+0.1 . 149.3 i1 ^+0.1 . 128.0 i1 ^+0.1 . 120.0 i1 ^+0.1 . 112.0 i1 ^+0.1 . 106.64 i1 ^+0.1 . 96.0 i1 ^+0.1 . 91.42857 i1 ^+0.1 . 89.6 i1 ^+0.1 . 85.36 i1 ^+0.1 . 80.0 i1 ^+0.1 . 74.64 i1 ^+0.1 . 64.0 i1 ^+1.0 . 1024.0 i1 ^+0.1 . 960.0 i1 ^+0.1 . 896.0 i1 ^+0.1 . 853. i1 ^+0.1 . 768.0 i1 ^+0.1 . 731.4286 i1 ^+0.1 . 716.8 i1 ^+0.1 . 682.6667 i1 ^+0.1 . 640.0 i1 ^+0.1 . 597. i1 ^+0.1 . 512.0 i1 ^+0.1 . 480.0 i1 ^+0.1 . 448.0 i1 ^+0.1 . 426.6 i1 ^+0.1 . 384.0 i1 ^+0.1 . 365.7143 i1 ^+0.1 . 358.4 i1 ^+0.1 . 341.4 i1 ^+0.1 . 320.0 i1 ^+0.1 . 298.6 i1 ^+0.1 . 256.0 i1 ^+0.1 . 240.0 i1 ^+0.1 . 224.0 i1 ^+0.1 . 213.3 i1 ^+0.1 . 192.0 i1 ^+0.1 . 182.85715 i1 ^+0.1 . 179.2 i1 ^+0.1 . 170.7 i1 ^+0.1 . 160.0 i1 ^+0.1 . 149.3 i1 ^+0.1 . 128.0 i1 ^+0.1 . 120.0 i1 ^+0.1 . 112.0 i1 ^+0.1 . 106.64 i1 ^+0.1 . 96.0 i1 ^+0.1 . 91.42857 i1 ^+0.1 . 89.6 i1 ^+0.1 . 85.36 i1 ^+0.1 . 80.0 i1
Bug#751069: csound: Does not recognize STK opcodes even though libstk is installed
Package: csound Version: 1:6.03.2~dfsg-1 Severity: normal Dear Maintainer, Every time I render a csd file, the following warning appears near the top of csound's output: WARNING: could not open library '/usr/lib/csound/plugins64-6.0/libstk.so' (/usr/lib/x86_64-linux-gnu/libstk.so.0: undefined symbol: _ZN7RtAudio10openStreamEPNS_16StreamParametersES1_mjPjPFiPvS3_jdjS3_ES3_PNS_13StreamOptionsEPFvN7RtError4TypeERKSsE) If I don't try to use STK opcodes, it's just a harmless warning. But if I try to use an STK opcode, I get an error like this: error: syntax error, unexpected T_IDENT (token STKTubeBell) from file helloSTKTubeBell.csd (1) line 20: aOut STKTubeBell Unexpected untyped word aOut when expecting a variable Parsing failed due to invalid input! This looks to me like csound failed to recognize STKTubeBell as an opcode, which is consistent with the warning which appears to say the STK opcodes weren't loaded. Here are the STK packages I have installed: root@makemake:~# dpkg -l | grep stk ii libstk0-dev:amd644.4.4-4 amd64 Sound Synthesis Toolkit (development files) ii libstk0c2a:amd64 4.4.4-4 amd64 Sound Synthesis Toolkit ii stk 4.4.4-4 amd64 Sound Synthesis Toolkit (example applications) ii stk-doc 4.4.4-4 all Sound Synthesis Toolkit (documentation) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-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 csound depends on: ii libc62.19-1 ii libcsound64-6.0 1:6.03.2~dfsg-1 ii libgcc1 1:4.9.0-5 ii libgomp1 4.9.0-5 ii libstdc++6 4.9.0-5 Versions of packages csound recommends: ii csound-utils 1:6.03.2~dfsg-1 csound 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#729547: Works now
I'm not sure what caused this -- there are so many interrelated packages -- but since a recent upgrade, it's been working for me again. This bug can be closed. Forrest
Bug#729547: xfce4-power-manager: XFCE user not authorized to suspend, hibernate, restart, or shut down
Package: xfce4-power-manager Version: 1.2.0-2 Severity: normal Dear Maintainer, After a recent upgrade, my computer no longer suspends after being idle. When my computer has been idle long enough, I now get a notification which reads Power Manager not authorized. Under the action buttons, Suspend, Hibernate, Restart, and Shut Down are all grayed out. I can suspend manually by typing pm-suspend in a root terminal window. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-power-manager depends on: ii libc6 2.17-95 ii libdbus-1-3 1.6.18-1 ii libdbus-glib-1-2 0.100.2-1 ii libgdk-pixbuf2.0-02.28.2-1 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-0 2.24.22-1 ii libnotify40.7.6-1 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxfce4ui-1-04.10.0-5 ii libxfce4util6 4.10.1-1 ii libxfconf-0-2 4.10.0-2 ii libxrandr22:1.4.1-1 ii upower0.9.23-2+b1 ii xfce4-power-manager-data 1.2.0-2 Versions of packages xfce4-power-manager recommends: ii consolekit 0.4.6-3+b1 Versions of packages xfce4-power-manager suggests: ii udisks 1.0.4-8+b1 pn xfce4-power-manager-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#673606: Please package! I have an actual need.
This is more than a nice to have for me -- I'm trying to work with a project that uses Netbeans API 7.1+ (possibly later by now). Do you need help getting this packaged? If there's something I can do, let me know.
Bug#656034: csound: Files required by STK opcodes not installed
Package: csound Version: 1:5.14.2~dfsg-2 Severity: normal When attempting to use the STKTubeBell opcode by running the sample csd from http://www.csounds.com/manual/html/STKTubeBell.html, I get this error FileRead::open: could not open or find file (/usr/share/stk/rawwaves/sinewave.raw)! terminate called after throwing an instance of 'stk::StkError' I created an stk directory under /usr/share and copied the rawwaves directory from the STK source tarball (downloadable from https://ccrma.stanford.edu/software/stk/download.html) into it, and this solved the problem. That dir should be installed by the csound or csound-data package. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-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 Versions of packages csound depends on: ii libc62.13-24 ii libcsound64-5.2 1:5.14.2~dfsg-2 Versions of packages csound recommends: ii csound-gui 1:5.14.2~dfsg-2 ii csound-manpages 1:5.13~dfsg-1 ii csound-utils 1:5.14.2~dfsg-2 csound 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#649824: recordmydesktop: Specifying --use-jack makes recordmydesktop exit with a bad screen geometry
Package: recordmydesktop Version: 0.3.8.1+svn602-1+b1 Severity: normal When I have jackd running and I attempt to use recordmydesktop using the --use- jack switch, I get this: forrest@supercool:~$ recordmydesktop --channels 2 --use-jack system:capture_1 system:capture_2 Window size specification out of bounds!(current resolution:1280x800) forrest@supercool:~$ and it exist immediately. If I attempt the same without jack running, I receive a more informative error message: forrest@supercool:~$ recordmydesktop --channels 2 --use-jack system:capture_1 system:capture_2 Initial recording window is set to: X:-31456 Y:0Width:32736Height:800 Adjusted recording window is set to: X:-31456 Y:0Width:32736Height:800 Your window manager appears to be Xfwm4 Initializing... Could not create new client! Make sure that Jack server is running! forrest@supercool:~$ Again, it exists immediately. Note that the numbers are not always the same; another run gave me this: forrest@supercool:~$ recordmydesktop --channels 2 --use-jack system:capture_1 system:capture_2 Initial recording window is set to: X:-6880 Y:0Width:8160Height:800 Adjusted recording window is set to: X:-6880 Y:0Width:8160Height:800 Your window manager appears to be Xfwm4 Initializing... Could not create new client! Make sure that Jack server is running! forrest@supercool:~$ My screen is 1280x800 and I would expect the values X:0 Y:0 Width:1280 Height: 800. Specifying the correct geometry on the command line doesn't help: It gives the same, less-informative error as when jack is running: forrest@supercool:~$ recordmydesktop -x 0 -y 0 --width 1280 --height 800 --channels 2 --use-jack system:capture_1 system:capture_2 Window size specification out of bounds!(current resolution:1280x800) forrest@supercool:~$ If I don't specify --use-jack, recordmydesktop works fine, and will record sound from alsa. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-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 Versions of packages recordmydesktop depends on: ii libasound21.0.24.1-4 ii libc6 2.13-21 ii libice6 2:1.0.7-2 ii libjack0 [libjack-0.116] 1:0.121.0+svn4538-3 ii libogg0 1.2.2~dfsg-1 ii libpopt0 1.16-1 ii libsm62:1.2.0-2 ii libtheora01.1.1+dfsg.1-3 ii libvorbis0a 1.3.2-1 ii libvorbisenc2 1.3.2-1 ii libvorbisfile31.3.2-1 ii libx11-6 2:1.4.4-4 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.0-3 ii libxfixes31:5.0-4 ii zlib1g1:1.2.3.4.dfsg-3 recordmydesktop recommends no packages. recordmydesktop 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
