[Bug 721896] Re: kswapd0 100% cpu usage
A comment on the fedora bug (https://bugzilla.redhat.com/show_bug.cgi?id=712019) mentions that this occurs when a large file (2G) is in cache. I just started experiencing this bug while working with large files, so this may be something to look into. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721896 Title: kswapd0 100% cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484045] Re: kswapd0 at 100% cpu
*** This bug is a duplicate of bug 721896 *** https://bugs.launchpad.net/bugs/721896 A comment on the fedora bug (https://bugzilla.redhat.com/show_bug.cgi?id=712019) mentions that this occurs when a large file (2G) is in cache. I just started experiencing this bug while working with large files, so this may be something to look into. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484045 Title: kswapd0 at 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/484045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659025] Re: Jack crashes and consumes 100% CPU after resume from suspend
I can't confirm the error messages, but I'm seeing this or similar behaviour on two different machines. One is running 10.10 amd64; the other, 11.10 i386. Both are using the default `jackd2` package. This bug really reduces the practicality of using jack on a laptop, since it's much more convenient to leave things running when moving than it is to shut everything down. It's also inconvenient for people who like to conserve electricity by suspending their machines when they are not in use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659025 Title: Jack crashes and consumes 100% CPU after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/659025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659025] Re: Jack crashes and consumes 100% CPU after resume from suspend
Confirmed that removing the package `jackd2-firewire` does not help with this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659025 Title: Jack crashes and consumes 100% CPU after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/659025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659025] Re: Jack crashes and consumes 100% CPU after resume from suspend
Using jackd1 instead of jackd2 seems to be a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659025 Title: Jack crashes and consumes 100% CPU after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/659025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921401] [NEW] No audio connections for qsynth with jackd1
Public bug reported: When using the package `jackd1` instead of `jackd2`, audio connections for qsynth do not appear. They appear neither in qjackctl's Audio tab nor in patchage. This is somewhat similar to https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/666824 except that that bug report reports that input audio connections do appear; I am not seeing any at all (neither input nor output). I do see qsynth appear (as FLUID Synth) in the ALSA midi tab. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921401 Title: No audio connections for qsynth with jackd1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/921401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921401] Re: No audio connections for fluidsynth with jackd1
System/package details: Ubuntu 11.10 jackd1 version 1:0.121.0+svn4469-2ubuntu2 qsynth version 0.3.6-1ubuntu2 Note that I've only tried doing this using qsynth rather than fluidsynth itself. qsynth is represented as FLUID Synth in qjackctl's ALSA midi tab. ** Summary changed: - No audio connections for fluidsynth with jackd1 + No audio connections for qsynth with jackd1 ** Description changed: When using the package `jackd1` instead of `jackd2`, audio connections - for fluidsynth do not appear. They appear neither in qjackctl's Audio - tab nor in patchage. + for qsynth do not appear. They appear neither in qjackctl's Audio tab + nor in patchage. This is somewhat similar to https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/666824 except that that bug report reports that input audio connections do appear; I am not seeing any at all (neither input nor output). - I do see fluidsynth appear in the ALSA midi tab. + I do see qsynth appear (as FLUID Synth) in the ALSA midi tab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921401 Title: No audio connections for qsynth with jackd1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/921401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921401] Re: No audio connections for qsynth with jackd1
I've since installed the fluidsynth package and discovered that fluidsynth does work. I ran it with the following command line: $ fluidsynth -a jack -m alsa_seq /usr/share/sounds/sf2/FluidR3_GM.sf2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921401 Title: No audio connections for qsynth with jackd1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/921401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921401] Re: No audio connections for qsynth with jackd1
I've now discovered that qsynth actually does appear in the qjackctl Audio tab briefly, then vanishes. This event seems to be concurrent with an xrun. It seems that the xrun causes qsynth to get booted from the audio connections list. I've also discovered that with frames/period set to 1024 in the qjackctl Setup box, this problem does not occur and qsynth starts up normally. I'm still confused as to a) why qsynth's startup triggers an xrun (fluidsynth's does not) and b) why this results in qsynth being removed from the audio connections list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921401 Title: No audio connections for qsynth with jackd1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/921401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921401] Re: No audio connections for qsynth with jackd1
PS I had frames/period set to a lower number (should that not be obvious from the above comment) because 1024 results in noticeable latency and so is not really ideal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921401 Title: No audio connections for qsynth with jackd1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/921401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296922] Re: Unknown encoder mp3 error in ffmpeg (ibex)
Having this problem under 10.10 -- getting the message Unknown encoder
'mp3' when trying to convert passing `-acodec mp3`. I get the same
message if I pass `libmp3lame` or even `ogg`.
Attempting to install libavcodec-unstripped-52 gives
v
The following NEW packages will be installed:
libavcodec-extra-52{ab} libavcodec-unstripped-52 libavutil-extra-50{ab}
libdirac-encoder0{a} libopencore-amrnb0{a} libopencore-amrwb0{a} libopenjpeg2{a}
0 packages upgraded, 7 newly installed, 0 to remove and 4 not upgraded.
Need to get 3,278kB of archives. After unpacking 7,500kB will be used.
The following packages have unmet dependencies:
libavutil-extra-50: Conflicts: libavutil50 but 4:0.6-2ubuntu6.1 is installed.
libavcodec-extra-52: Conflicts: libavcodec52 but 4:0.6-2ubuntu6.1 is
installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) libavcodec52
2) libavutil50
Accept this solution? [Y/n/q/?] q
^
What's going on here? Why are there two different pairs of packages
that seem to do the same thing?
Also: if I run `ffmpeg -codecs` it lists mp3 as one of the available
codecs. Is that a different bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/296922
Title:
Unknown encoder mp3 error in ffmpeg (ibex)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/296922/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 747811] [NEW] USB subsystem seems to shut down occasionally
Public bug reported: When reconnecting a USB keyboard to my system, I got this stream of messages in `/var/log/syslog`: Mar 31 22:35:01 gatsby kernel: [442633.491562] usb 2-1.2: new low speed USB device using ehci_hcd and address 79 Mar 31 22:35:01 gatsby kernel: [442633.579057] ehci_hcd :00:1d.0: fatal error Mar 31 22:35:01 gatsby kernel: [442633.585381] ehci_hcd :00:1d.0: force halt; handshake c9674824 4000 4000 - -110 Mar 31 22:35:01 gatsby kernel: [442633.585389] ehci_hcd :00:1d.0: HC died; cleaning up Mar 31 22:35:01 gatsby kernel: [442633.598955] usb 2-1.2: device descriptor read/all, error -108 Mar 31 22:35:01 gatsby kernel: [442633.598961] hub 2-1:1.0: cannot disable port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598974] hub 2-1:1.0: cannot reset port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598977] hub 2-1:1.0: cannot disable port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598983] hub 2-1:1.0: cannot reset port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598987] hub 2-1:1.0: cannot disable port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598992] hub 2-1:1.0: cannot reset port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598995] hub 2-1:1.0: cannot disable port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.598998] hub 2-1:1.0: unable to enumerate USB device on port 2 Mar 31 22:35:01 gatsby kernel: [442633.599002] hub 2-1:1.0: cannot disable port 2 (err = -19) Mar 31 22:35:01 gatsby kernel: [442633.599015] usb 2-1: USB disconnect, address 2 A normal set of log messages for the same event looks like this: Mar 31 16:36:44 gatsby kernel: [421175.156518] usb 2-1.2: new low speed USB device using ehci_hcd and address 74 Mar 31 16:36:44 gatsby kernel: [421175.278006] input: Dell Dell USB Keyboard as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input63 Mar 31 16:36:44 gatsby kernel: [421175.278256] generic-usb 0003:413C:2003.0038: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-:00:1d.0-1.2/input0 Since that error was logged, the system will no longer respond to the connection of USB devices. There is no record of such events in either `/var/log/syslog` or via `dmesg`. I'm running 10.10 on an Acer Aspire 5742 laptop. It may be relevant that both my HECI controller and SMBus show up as `UNCLAIMED` in the output from `lshw`. They are both listed as being `/^\s*product: 5 Series/3400 Series Chipset (HECI|SMBus) Controller/`. I'm booting with the `acpi_osi=` kernel argument. This, or a different problem resulting in USB devices not being detected, has happened once before, on 2011-03-12. I rebooted in order to be able to use newly connected USB devices. When the previous event occurred, I was not using the acpi_osi= kernel parameter. I was using the kernel package `linux-image-generic 2.6.35.27.35` (or possibly an earlier one, depending on when/if I rebooted) at that point; I have since upgraded to `linux-image-2.6.35-28-generic 2.6.35-28.49`. Since my last reboot I have plugged and unplugged numerous USB devices multiple times without any issues. Note the address `79` on the above syslog messages. I tried $ sudo modprobe -r usbhid ; sudo modprobe usbhid This logged the following to `/var/log/syslog` Apr 1 00:41:10 gatsby kernel: [450189.768916] usbcore: deregistering interface driver usbhid Apr 1 00:41:10 gatsby kernel: [450189.768960] usbcore: deregistering interface driver hiddev Apr 1 00:41:10 gatsby kernel: [450189.823210] usbcore: registered new interface driver hiddev Apr 1 00:41:10 gatsby kernel: [450189.823246] usbcore: registered new interface driver usbhid Apr 1 00:41:10 gatsby kernel: [450189.823250] usbhid: USB HID core driver but otherwise had no effect: newly-connected USB devices still do not work, nor are any syslog messages generated in response to their connection. I tried connecting devices to two different USB ports on different sides of the machine, both to the same non-effect. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-28-generic 2.6.35-28.49 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sixty 2548 F pulseaudio sixty 4769 F alsamixer sixty 20641 F alsamixer CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at
[Bug 747811] Re: USB subsystem seems to shut down occasionally
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747811 Title: USB subsystem seems to shut down occasionally -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636045] Re: intel ips 0000:00:1f.6: MCP power or thermal limit exceeded
Updating to the new kernel seems a bit sketchy. People should probably at least use the PPA given by Ramoonus in the comments, so as to allow security updates to be picked up by APT — assuming that updated kernel images are indeed posted to the PPA. Based on the lxml thread posted in comment #21, and based on the fact that my machine is running cool, it looks like this is just noise that can safely be muted until the kernel patch is deployed in the mainline ubuntu release. I've done this by adding a syslog filter: $ cat /etc/rsyslog/10-mcp-power.conf :msg,contains,intel ips :00:1f.6: MCP power or thermal limit exceeded ~ I'm not sure if the the `...1f:6` will always be the same or not. Skeptics can get more info at these locations: http://serverfault.com/questions/15106/is-there-a-way-to-filter-syslog- entries http://www.rsyslog.com/doc/rsyslog_conf_filter.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636045 Title: intel ips :00:1f.6: MCP power or thermal limit exceeded -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705328] [NEW] Failure to bring up Java applet during System Testing
Public bug reported: While running through the System Testing, there is a test to be run on a Java applet. The applet didn't display. I waited at least 30 seconds for it; cpu and disk were idle during this period. Honestly I'm not really sure why the test system thought I should report this bug and not the other failed tests, I'm mostly just following its suggestion. I guess the fact that it asked for this one and not the others implies that other people have not had, or not reported, this issue. It also thinks the bug is in Firefox, but I'm guessing it's as likely to be with the JRM package, so I left that field blank. I'm also assuming that the hardware info scraped by the test system will be made available in this bug report; if not, I guess I will follow up with it. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 CheckboxCommand: firefox $CHECKBOX_SHARE/data/websites/javatest.html CheckboxData: I didn't even see the Applet, let alone the Test Message. CheckboxDescription: Click the Test button to open Firefox with the Java test page, and follow the instructions there. Did the applet display? CheckboxTest: applications-firefox-java Date: Thu Jan 20 05:20:17 2011 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: firefox ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug checkbox-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705328 Title: Failure to bring up Java applet during System Testing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705328] Re: Failure to bring up Java applet during System Testing
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705328 Title: Failure to bring up Java applet during System Testing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464101] Re: Untrusted packages not installable
Also experiencing this issue. Was able to resolve by editing `/etc/apt/sources.list` to use the [Cc]anonical repository, as per https://help.ubuntu.com/10.10/serverguide/C/configuration.html, then running `sudo aptitude update; sudo aptitude dist-upgrade`. I had been getting this warning message before the upgrade began any downloads; after changing the repo it goes right into downloading. I had been using the same mirror (http://mirror.its.dal.ca/ubuntu/) without issues for some months now, and have not had a problem until now. I have done numerous updates since upgrading to Maverick and before experiencing this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/464101 Title: Untrusted packages not installable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464101] Re: Untrusted packages not installable
P.S. The warning message first began to be issued by `aptitude dist- upgrade` earlier today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/464101 Title: Untrusted packages not installable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 524774] Re: xmodmap failure BadValue error, 118 (X_SetModifierMapping)
I've started using a different machine recently, and was initially not experiencing this bug. I'm running xfce under 10.10. IIRC I originally installed xubuntu on this box but have also installed the ubuntustudio package as well as kubuntu-desktop and possibly ubuntu-desktop. Anyway this erroneous behaviour with xmodmap, specifically $ xmodmap -e 'clear Lock' X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 118 (X_SetModifierMapping) Value in failed request: 0x17 Serial number of failed request: 8 Current serial number in output stream: 8 started when I added the Keyboard Layouts applet to a panel. I added the Canadian Multilingual keyboard to the initial default of US. The switcher combo was set to Alt+CapsLock. At this point I had already run this xmodmap script !Remap Caps_Lock as Escape remove Lock = Caps_Lock keysym Caps_Lock = Escape which switches CapsLock and Escape. This had been working normally up until this point, but IIRC the keyboard setup reverted to the default after I accepted the Keyboard Layouts preferences. When I tried to re- run my script, I got the above-quoted error message. I've filed an `upstream bug report`_ which, it would appear, is not a duplicate. .. _upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=31436 ** Bug watch added: freedesktop.org Bugzilla #31436 http://bugs.freedesktop.org/show_bug.cgi?id=31436 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524774 Title: xmodmap failure BadValue error, 118 (X_SetModifierMapping) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 524774] Re: xmodmap failure BadValue error, 118 (X_SetModifierMapping)
I've discovered that the addition of the Canadian Multilingual keyboard (ca-multix) specifically triggers the bug behaviour. I.E. If I add it in the properties dialog for xfce's Keyboard Settings applet, I will subsequently be unable to do ``xmodmap -e 'clear Lock'`. Removing the Canadian Multilingual keyboard as one of the keyboard options will cause that xmodmap command to work again. The problem does not occur (i.e. xmodmap works correctly) if I instead add the keyboard Canada - Multilingual (first part) (ca-multi). So this may prove to be a good workaround for myself and perhaps others, and may provide a useful clue to people who can track down this bug. Also: this issue is `rumoured`_ to be related or identical to `https://bugs.freedesktop.org/show_bug.cgi?id=20145`_ .. _rumoured: http://unix.stackexchange.com/questions/4541/diagnosing-xmodmap-errors#comment-5291 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524774 Title: xmodmap failure BadValue error, 118 (X_SetModifierMapping) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508545] Re: Aptitude ignores /etc/apt/preferences.d/*
Is this supposed to be fixed in updated versions of Maverick? Sorry if that's a silly question — is there a better way to find out which version of aptitude has this fix? I've got my system updated but it looks like aptitude is still not finding files like ``/etc/apt/preferences.d/identifier.pref``. -- Aptitude ignores /etc/apt/preferences.d/* https://bugs.launchpad.net/bugs/508545 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41301] Re: Mouse clicks stop working sporadically
Another user of a Logitech USB mouse (MediaPlay) here. I've found that running `modprobe -r usbhid modprobe usbhid` works as a temporary fix. I've also noticed that the mouse focus is, at least in some cases, stuck on a particular window. For example, if I double-click on the focused window (when this bug is active) there will be no perceivable effect on that window. However, sometimes the response to that mouse action (e.g. text selection) will be apparent on another window when I switch back to it with ALT-TAB. Like DJ I'm running a (mostly) regularly updated 10.04 and have started experiencing this problem within the past month or so. After restarting X it will often take a long time for this to start happening (days, weeks) but once it starts it will keep happening quite often. I'm finding that using the `modprobe` workaround will only be effective for about an hour or so. -- Mouse clicks stop working sporadically https://bugs.launchpad.net/bugs/41301 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576102] [NEW] Unable to unmap Lock modifier using xmodmap
Public bug reported: Binary package hint: x11-xserver-utils This problem is happening under GNOME, KDE, and Openbox window manager sessions. I've deleted any ~/.Xmodmap files, so these sessions are not modifying the xmodmap prior to my execution of the described commands. Steps to reproduce: 1. Start a new X login session. It doesn't seem to matter which desktop environment is selected, as this bug is reproducible under KDE, GNOME, and Openbox. 2. Open a terminal. 3. Type one of the following commands: $ xmodmap -e 'clear Lock' OR $ xmodmap -e 'remove Lock = Caps_Lock' Result: An error message similar to the following is displayed: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 118 (X_SetModifierMapping) Value in failed request: 0x17 Serial number of failed request: 11 Current serial number in output stream: 11 The serial number values vary but the other information is consistent. Requested information: 1) Release info: $ lsb_release -rd Description:Ubuntu 10.04 LTS Release:10.04 2) Package version: $ apt-cache policy x11-xserver-utils x11-xserver-utils: Installed: 7.5+1ubuntu2 Candidate: 7.5+1ubuntu2 Version table: *** 7.5+1ubuntu2 0 500 http://ubuntu.mirror.rafal.ca/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 3) Expected result Prior to my recent upgrade to Lucid (Ubuntu release 10.04), I was able to unmap the Lock modifier without problems. As a vim user I find it quite useful to map the [CapsLock] key to Escape, and prefer to disable the Lock modifier entirely: as I rarely write anything in all caps, I seldom have any use for it, and an accidental activation of it can cause minor confusion when editing files in Vim. My previous ~/.xmodmap file used the clear Lock directive to disable the Lock modifier. Upon rebooting after upgrading to Lucid I discovered that this functionality was no longer activated, ie that the Caps Lock key continues to control the Lock modifier's state. I expected it to be activated and for the Caps Lock key to not affect the Lock modifier state. 4) What happened instead: The Caps Lock key continued to control the Lock modifier's state. The error message given above was output in response to an xmodmap command to clear or remove that functionality. Also: please note that my exclusion of gdm debugging information was not so much due to privacy concerns as because I haven't run it in months. Although this install is an Ubuntu install, I installed the kubuntu-desktop metapackage some time ago, and so am using kdm rather than gdm. In any case this seems unlikely to be affecting xmodmap functionality. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: x11-xserver-utils 7.5+1ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed May 5 19:03:06 2010 MachineType: Hewlett-Packard HP Pavilion tx2000 Notebook PC ProcCmdLine: root=UUID=5212e362-bd7e-4b90-9b1b-50d67ab7563a ro quiet splash crashkernel=384M-2G:64M,2G-:128M ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: x11-xserver-utils dmi.bios.date: 02/22/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.06 dmi.board.name: 30E5 dmi.board.vendor: Quanta dmi.board.version: 88.08 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd02/22/2008:svnHewlett-Packard:pnHPPaviliontx2000NotebookPC:pvrRev1:rvnQuanta:rn30E5:rvr88.08:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion tx2000 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic ** Affects: x11-xserver-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Unable to unmap Lock modifier using xmodmap https://bugs.launchpad.net/bugs/576102 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576102] Re: Unable to unmap Lock modifier using xmodmap
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/47897490/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/47897491/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47897492/Dependencies.txt ** Attachment added: DkmsStatus.txt http://launchpadlibrarian.net/47897493/DkmsStatus.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/47897494/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/47897495/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/47897496/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/47897497/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/47897498/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/47897499/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/47897500/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/47897501/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/47897502/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/47897503/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/47897504/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/47897505/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/47897506/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/47897507/glxinfo.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/47897508/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/47897509/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/47897510/xkbcomp.txt -- Unable to unmap Lock modifier using xmodmap https://bugs.launchpad.net/bugs/576102 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508545] Re: Aptitude ignores preferences.d/*
In response to @mariodebian's comment (#6): Using the karmic version of aptitude (0.4.11.11-1ubuntu6), files in /etc/preferences.d are ignored even if they have the .pref extension. -- Aptitude ignores preferences.d/* https://bugs.launchpad.net/bugs/508545 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480037] Re: Closing laptop lid crashes Ubuntu
Hi all, I'm running a D400 that has not had any hardware problems. Until a couple of days ago it was working perfectly under hardy using the i810 driver. I've tried using nomodeset but there seem to be problems with this as well. Before using nomodeset: I've also noticed that the bug is at least triggered by lid _opening_. I think it's triggered by closing as well, but it will definitely happen when the lid is opened. To test this I closed the lid when rebooting, before reaching the boot screen. I was able to ssh in to the machine without issues, but when I opened the lid it crashed. This was _without_ the nomodeset parameter. Side effects of using nomodeset: • Consoles (eg CTRL-ALT-F2) didn't work the first time I booted with nomodeset. They have worked on other boots. • When opening the lid: The display comes up immediately (unless it crashes). After about a second, the display blanks out for maybe a second. Then it will start displaying again, and stay lit this time. If I move the mouse during the initial display period, ie before it blanks out, the cursor will cease to be visible, and I'll have to close the lid and open it again, and refrain from moving the mouse during that period. I noticed that if the mouse cursor isn't displayed during the initial display period, it will start being displayed about 3/4 of the way through that period; then the screen blanks, then it comes back. • Sometimes it crashes anyway. See below. Report of crash which occurred while running with the nomodeset parameter: I initially (for a few lid opening/closings) had success with the nomodeset fix. However I just had a crash that seems related: 1) closed the lid 2) opened the lid. Everything was fine except that the mouse cursor wasn't displayed. I guess I moved the cursor too soon.I noticed that on opening the lid, the screen would display right away, but then blank out for maybe a second, then come back up. Before the blank-out, the mouse cursor was being displayed. 3) closed opened the lid in an attempt to make the mouse cursor work. 4) crash. the box is unpingable, the display is blanked. Repeated lid openings/closings, as well as console switches, don't have any effect. I don't remember if it displayed for a moment before crashing or if the crash happened after the initial display period. Questions: Is it possible to install the i810 driver under karmic? It was great under hardy. -- Closing laptop lid crashes Ubuntu https://bugs.launchpad.net/bugs/480037 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480037] Re: Closing laptop lid crashes Ubuntu
I've found a bug report for the mouse cursor issue: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/482715 (#482715) -- Closing laptop lid crashes Ubuntu https://bugs.launchpad.net/bugs/480037 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480037] Re: Closing laptop lid crashes Ubuntu
Err.. whoops, that's a different issue, it's Compiz-related. -- Closing laptop lid crashes Ubuntu https://bugs.launchpad.net/bugs/480037 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 192735] Re: mpd no access to soundcard using pulseaudio
Hi Andreas, I've since upgraded to 13.2 and it still working okay. I am pretty busy but I will try to find time in the next week to check with 14.2. I assume you mean to check if it can be made to authenticate through the pulse-cookie? Cheers -Ted On Wed, Apr 22, 2009 at 9:51 AM, Andreas Moog andreas-launch...@warperbbs.de wrote: Thanks for reporting, does this work with version 0.14.2 from the official repositories? If not, could you please also try the version available in my ppa (https://edge.launchpad.net/~amoog/+archive/ppahttps://edge.launchpad.net/%7Eamoog/+archive/ppa )? Thanks. ** Changed in: mpd (Ubuntu) Importance: Undecided = Medium ** Changed in: mpd (Ubuntu) Status: Confirmed = Incomplete -- mpd no access to soundcard using pulseaudio https://bugs.launchpad.net/bugs/192735 You received this bug notification because you are a direct subscriber of the bug. Status in “mpd” source package in Ubuntu: Incomplete Status in “pulseaudio” source package in Ubuntu: Invalid Bug description: Binary package hint: pulseaudio Version info: uname -r: 2.6.24-8-generic pulseaudio Version: 0.9.9-1ubuntu2 mpd : Version: 0.13.1-3ubuntu1 After changing from esound to pulseaudio, MPD is not able to access the sound card. MPD logs the following errors in /var/log/mpd/errors.log: No protocol specified E: client-conf-x11.c: XOpenDisplay() failed *** PULSEAUDIO: Unable to connect: Access denied By giving xhost + and restarting mpd the XOpenDisplay() error disappears, but the error regarding PULSEAUDIO still persists. This happend using the latest ubuntu gutsy as of 16.02.2008, as well as the current Hardy. Pulseaudio was installed using https://wiki.ubuntu.com/PulseAudio on gutsy, and the system was upgraded to hardy using update-manager. I have added mpd and root to all pulseaudio groups (pulse, pulse-access, pulse-rt), but this did not solve the problem. Xine works using native pulse output and mythtv works using ALSA:default output device. Regards, Rune -- mpd no access to soundcard using pulseaudio https://bugs.launchpad.net/bugs/192735 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192735] Re: mpd no access to soundcard using pulseaudio
I initially got this working by using the paprefs applet. pulse-related changes to my mpd.conf file are the same as the de facto solution. this solution is noted as an alternate solution in http://mpd.wikia.com/wiki/PulseAudio#For_Distros_where_PulseAudio_output_is_broken This solution works is necessary (unless you use the loadmodule fix) because a) the mpd daemon is run by the user mpd and is unable to connect to that user's instance of pulseaudio because it doesn't exist b) I have told the instance of pulseaudio that's running under my username to allow connections via tcp from unauthenticated users c) mpd is able to make connections via tcp, and will do so to the localhost by default. the problem, as I understand it, with this workaround, is that it leaves my instance of pulseaudio open to other users on either my local machine or anywhere on the LAN. so there's the possibility of unexpected bursts of sound emitting from the machine when I'm at, say, the library. yeah yeah hosts.allow. with help from the section http://mpd.wikia.com/wiki/PulseAudio#On_Windows i gathered that copying ~/.pulse-cookie to the mpd user's home directory (and chowning it to that user) will let mpd get authorization to the pulseaudio server for that user, even if the paprefs option to allow unauthenticated users is unchecked and the loadmodule command is not specified. this is working fine under hardy. i also did # usermod -d /home/mpd mpd; not sure if that was necessary. again you do have to check the box in paprefs to enable network access to local sound devices. but since this will only let mpd connect to one user's instance of pulseaudio, it's not a very good solution for a music server. more appropriate for, for example, a system that supplies audio to a stereo system and has various users logging into it, is to invoke a system-wide instance of pulse as per http://pulseaudio.org/wiki/SystemWideInstance, and copy /var/run/pulse/.pulse-cookie to /home/mpd instead of the user's cookie. there are some security other issues associated with using a system-wide pulse instance; read all about it at the pulseaudio wiki link. -- mpd no access to soundcard using pulseaudio https://bugs.launchpad.net/bugs/192735 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
