[Touch-packages] [Bug 2051694] [NEW] Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor layout
Public bug reported:
When I built a new PC with Kubuntu 22.04 LTS, I carried over my recently
purchased GeForce RTX 3060 and copied over the Xorg.conf that was doing
perfectly well for me in 20.04 LTS, containing the following line:
Option "metamodes" "HDMI-0: 1280x1024 +3200+0, DP-3:
1280x1024 +0+0, DP-1: 1920x1080 +1280+0"
(Bear in mind that, due to a history of bugginess in KScreen2 and how it
interacts with Plasma panel layouts, I disable it in the Background
Services control panel and do my best to lock down the allowed layouts
and resolutions in Xorg.conf.)
This technique has been working for me for close to a decade, with my
previous video card being a GeForce GTX750 and, if I remember correctly,
I was also using it with the GeForce GT430 I was using before that, and
with Kubuntu and Lubuntu versions going back to at least Kubuntu 16.04
LTS and likely to Lubuntu 14.04 and possibly even Lubuntu 12.04.
However, much to my dismay, it appeared to have no effect, and the
system was still assigning a virtual layout that didn't match the
physical arrangement of the monitors.
Eventually, I realized from /var/log/Xorg.0.log that my metamodes line
WAS getting set, but, for reasons I still have no idea how to diagnose,
something else was overriding it and resetting the metamodes line back
to the undesired default, with unlocked resolutions and an incorrect
monitor layout.
[21.689] (II) NVIDIA(0): Setting mode "HDMI-0: 1280x1024 @1280x1024 +3200+0
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 1280x1024 @1280x1024
+0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1:
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[21.747] (II) NVIDIA(0): Setting mode "DP-3: 1280x1024 @1280x1024 +0+0
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[21.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3:
1280x1024 @1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0},
DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[21.922] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3:
nvidia-auto-select @1280x1024 +3200+0 {ViewPortIn=1280x1024,
ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
As a workaround which may or may not show up in the ubuntu-bug report,
I've created a /etc/X11/Xsession.d/01-fix-the-damn-ignored-metamodes
file containing the line `xrandr --output DP-3 --left-of DP-1`.
...though that doesn't fix the monitor layout at the login screen and
it's not possible to work around the forced changeability of the
resolution without a working metamodes according to
https://gitlab.freedesktop.org/xorg/xserver/-/issues/353#note_91110
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.146.02 Sun Dec 3
14:06:14 UTC 2023
GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Jan 30 06:25:44 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA106 [GeForce RTX 3060 Lite Hash Rate]
[1043:8810]
Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c6) (prog-if 00
[VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e]
InstallationDate: Installed on 2024-01-05 (24 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.1)
MachineType: ASRock B650 PG Lightning
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=7aefb7ca-223b-4111-81e4-0d2a1003dbce ro
zfs.zfs_dmu_offset_next_sync=0 quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
[Touch-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
Still affecting KDE users on 14.04 LTS. Here's a workaround I found on the KDE bug tracker: cat ~/.kde/env/fix_gtk3.sh EOF #!/bin/sh export GDK_CORE_DEVICE_EVENTS=1 EOF chmod +x ~/.kde/env/fix_gtk3.sh Source: https://bugs.kde.org/show_bug.cgi?id=348270#c26 ** Bug watch added: KDE Bug Tracking System #348270 https://bugs.kde.org/show_bug.cgi?id=348270 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Confirmed Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452204] [NEW] evdev device for retro-bit NES controller adapter isn't set up as a joystick
Public bug reported:
Games which rely on SDL2 (and tools like antimicro) can't see the retro-
bit NES controller adapter by default because SDL2 has dropped support
for the old /dev/input/jsX API and udev lacks a rule to permission the
/dev/input/eventX node appropriately and set the ID_INPUT_JOYSTICK flag.
The following rule (or equivalent) needs to be added to the system-
provided udev rules.
SUBSYSTEM==input, ATTRS{name}==INNEX NES Controller USB,
MODE=0666, ENV{ID_INPUT_JOYSTICK}=1
I come to this conclusion because:
1. Until the mode is changed, feeding evtest with an explicit input device
number results in a permissions error.
2. Globally allowing users to read joystick input poses no security risk and
the data is already mirrored via /dev/input/jsX which is 0666 already.
3. Once the mode is changed, sdl2-jstest and antimicro still cannot see it.
4. Once ID_INPUT_JOYSTICK=1 is set, sdl2-jstest and antimicro work just as well
as sdl-jstest and jstest-gtk, which use the old API.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.11
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: LXDE
CustomUdevRuleFiles: 99-escpos.rules 49-teensy.rules 99-nes-controller.rules
99-TrueRNG.rules
Date: Wed May 6 05:39:13 2015
InstallationDate: Installed on 2014-08-01 (278 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic
root=UUID=d8313afd-996d-4d2c-9764-02e9336e03fd ro verbose
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-880GMA-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GMA-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1452204
Title:
evdev device for retro-bit NES controller adapter isn't set up as a
joystick
Status in systemd package in Ubuntu:
New
Bug description:
Games which rely on SDL2 (and tools like antimicro) can't see the
retro-bit NES controller adapter by default because SDL2 has dropped
support for the old /dev/input/jsX API and udev lacks a rule to
permission the /dev/input/eventX node appropriately and set the
ID_INPUT_JOYSTICK flag.
The following rule (or equivalent) needs to be added to the system-
provided udev rules.
SUBSYSTEM==input, ATTRS{name}==INNEX NES Controller USB,
MODE=0666, ENV{ID_INPUT_JOYSTICK}=1
I come to this conclusion because:
1. Until the mode is changed, feeding evtest with an explicit input device
number results in a permissions error.
2. Globally allowing users to read joystick input poses no security risk and
the data is already mirrored via /dev/input/jsX which is 0666 already.
3. Once the mode is changed, sdl2-jstest and antimicro still cannot see it.
4. Once ID_INPUT_JOYSTICK=1 is set, sdl2-jstest and antimicro work just as
well as sdl-jstest and jstest-gtk, which use the old API.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.11
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: LXDE
CustomUdevRuleFiles: 99-escpos.rules 49-teensy.rules 99-nes-controller.rules
99-TrueRNG.rules
Date: Wed May 6 05:39:13 2015
InstallationDate: Installed on 2014-08-01 (278 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64
(20140416.2)
MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic
root=UUID=d8313afd-996d-4d2c-9764-02e9336e03fd ro verbose
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-880GMA-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
[Touch-packages] [Bug 1378752] [NEW] Crackling in PulseAudio when using src-linear or src-sinc-fastest resamplers with 22050Hz audio
Public bug reported: On my system, I had problems with both excess CPU usage and tried to resolve them by using a simpler resampling algorithm. However, that resulted in crackling audio from DOSBox and Windows 3.1 games running under Wine 1.2.x. (Both are configured to output audio at 22050Hz, with which ALSA dmix has no problem, and, in the case of the Windows 3.1 games, that's not something that can be reconfigured as far as I know.) Nothing I changed seemed to help and I was forced to return to speex- float-1. (As such, the pulseaudio config files in the debug dump don't represent PA in a broken configuration... just one that consumes more CPU than I'd like it to.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Oct 8 06:28:19 2014 InstallationDate: Installed on 2014-08-01 (68 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763 mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1378752 Title: Crackling in PulseAudio when using src-linear or src-sinc-fastest resamplers with 22050Hz audio Status in “pulseaudio” package in Ubuntu: New Bug description: On my system, I had problems with both excess CPU usage and tried to resolve them by using a simpler resampling algorithm. However, that resulted in crackling audio from DOSBox and Windows 3.1 games running under Wine 1.2.x. (Both are configured to output audio at 22050Hz, with which ALSA dmix has no problem, and, in the case of the Windows 3.1 games, that's not something that can be reconfigured as far as I know.) Nothing I changed seemed to help and I was forced to return to speex- float-1. (As such, the pulseaudio config files in the debug dump don't represent PA in a broken configuration... just one that consumes more CPU than I'd like it to.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Oct 8 06:28:19 2014 InstallationDate: Installed on 2014-08-01 (68 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763 mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1378752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378752] Re: Crackling in PulseAudio when using src-linear or src-sinc-fastest resamplers with 22050Hz audio
** Description changed: - On my system, I had problems with both excess CPU usage and tried to - resolve them by using a simpler resampling algorithm. However, that - resulted in crackling audio from DOSBox and Windows 3.1 games running - under Wine 1.2.x. + On my system, I had problems with excess CPU usage and tried to resolve + them by using a simpler resampling algorithm. However, that resulted in + crackling audio from DOSBox and Windows 3.1 games running under Wine + 1.2.x. (Both are configured to output audio at 22050Hz, with which ALSA dmix has no problem, and, in the case of the Windows 3.1 games, that's not something that can be reconfigured as far as I know.) Nothing I changed seemed to help and I was forced to return to speex- float-1. (As such, the pulseaudio config files in the debug dump don't represent PA in a broken configuration... just one that consumes more CPU than I'd like it to.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Oct 8 06:28:19 2014 InstallationDate: Installed on 2014-08-01 (68 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763 mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127 ** Description changed: On my system, I had problems with excess CPU usage and tried to resolve them by using a simpler resampling algorithm. However, that resulted in crackling audio from DOSBox and Windows 3.1 games running under Wine 1.2.x. (Both are configured to output audio at 22050Hz, with which ALSA dmix has no problem, and, in the case of the Windows 3.1 games, that's not - something that can be reconfigured as far as I know.) + something that can be changed as far as I know.) Nothing I changed seemed to help and I was forced to return to speex- float-1. (As such, the pulseaudio config files in the debug dump don't represent PA in a broken configuration... just one that consumes more CPU than I'd like it to.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Oct 8 06:28:19 2014 InstallationDate: Installed on 2014-08-01 (68 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763 mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127 ** Description changed: On my system, I had problems with excess CPU usage and tried to resolve them by using a simpler resampling algorithm. However, that resulted in crackling audio from DOSBox and Windows 3.1 games running under Wine 1.2.x. (Both are configured to output audio at 22050Hz, with which ALSA dmix has no problem, and, in the case of the Windows 3.1 games, that's not something that can be changed as far as I know.) - Nothing I changed seemed to help and
[Touch-packages] [Bug 207135] Re: pulseaudio uses too much CPU
Lubuntu 14.04. Despite using src-linear, it consumes 6% when mixing Audacious and Wine but shoots up to 10-12% CPU when padevchooser is open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/207135 Title: pulseaudio uses too much CPU Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64 Processor 3500+) when I'm just listening music using Rhythmbox. Seems too much IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
