[Desktop-packages] [Bug 1904525] [NEW] Audio balance settings is reset when the volume is turned down to the end.
Public bug reported: Audio balance settings is reset when the volume is turned down to the end. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alikosen 1560 F pulseaudio /dev/snd/pcmC0D0p: alikosen 1560 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 17 10:47:56 2020 InstallationDate: Installed on 2020-11-11 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dahili Ses - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Kas 17 09:05:03 LIPG500 dbus-daemon[770]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Kas 17 09:05:44 LIPG500 systemd[952]: pulseaudio.service: Succeeded. Kas 17 09:05:54 LIPG500 systemd[952]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [VIWGP, Conexant CX20757, Black Headphone Out, Left] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN25WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pnVIWGP:pvrINVALID:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: VIWGP dmi.product.sku: LENOVO_BI_IDEAPAD78 dmi.product.version: INVALID dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904525 Title: Audio balance settings is reset when the volume is turned down to the end. Status in alsa-driver package in Ubuntu: New Bug description: Audio balance settings is reset when the volume is turned down to the end. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alikosen 1560 F pulseaudio /dev/snd/pcmC0D0p: alikosen 1560 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 17 10:47:56 2020 InstallationDate: Installed on 2020-11-11 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dahili Ses - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Kas 17 09:05:03 LIPG500 dbus-daemon[770]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Kas 17 09:05:44 LIPG500 systemd[952]: pulseaudio.service: Succeeded. Kas 17 09:05:54 LIPG500 systemd[952]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [VIWGP, Conexant CX20757, Black Headphone Out, Left] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN25WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pnVIWGP:pvrINVALID:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: VIWGP dmi.product.sku: LENOVO_BI_IDEAPAD78 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
I can also confirm that this bug is still present. I'm on Ubuntu 19.04 with the latest drivers & updates installed. Also, I want to add something here: It's not that it specifically limits the framerate to 60 Hz. Rather, it limits it to the monitor with the lowest refresh rate. Try setting one monitor's refresh rate to 30 Hz, and you should instantly notice how laggy the whole desktop environment becomes. I understand that this issue might be looked at as "not that important", but I believe a lot of people that would love to switch from Windows to something like Ubuntu really wouldn't appreciate the fact that their 144 Hz monitor doesn't work as intended. If you own one yourself, you probably would never want to set it to 60 Hz out of free will. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837330] [NEW] Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations
Public bug reported: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily repeatable if you have two monitors with two refresh rates, I suppose. After you set up your monitors, make sure to enable 144 Hz, then "test" it by moving your mouse around. It should feel smooth, just like it should on 144 Hz. Now move a window (such as a browser, or your file manager) around. You should notice that it still feels like it runs at 60 Hz. To sum up: What should happen: - The windows that are currently on the 144 Hz Monitor should be rendered at the specified refresh rate What actually happens - The refresh rate of rendered windows (excluding games) appears to be capped to the lowest refresh rate monitor I did test this further and it seemed to confirm my hypothesis. When I set my second, 60 Hz monitor, to run at 30 Hz, everything excluding my cursor was now being rendered at 30 Hz on both screens. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 19:47:07 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed nvidia, 418.56, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2019-07-16 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco refresh-rate ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837330 Title: Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations Status in xorg package in Ubuntu: New Bug description: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily repeatable if
[Desktop-packages] [Bug 1296275] Re: PTP Cameras not working on 14.04, works flawlessly on 12.04
I have same issue with my FinePix T350 I can browse it this way: $ gphoto2 --auto-detect Model Port -- USB PTP Class Camera usb:002,006 $ nautilus gphoto2://[usb:002,006]/ also it works with gphotofs (https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1296275/comments/7) But it is not opens automatically $ gvfs-mount -lo ... Mount(0): mtp - mtp://[usb:002,002]/ Type: GDaemonMount $ gphoto2 --summary Camera summary: Manufacturer: FUJIFILM Model: FinePix T350 Version: Digital Camera FinePix T350 Ver1.00 Serial Number: 592D313339323112122711A52WN46319 Vendor Extension ID: 0x6 (1.0) Vendor Extension Description: fujifilm.co.jp: 1.0; Capture Formats: Display Formats: JPEG, JFIF Supported MTP Object Properties: JPEG/3801: dc01/StorageID dc02/ObjectFormat dc03/ProtectionStatus dc04/ObjectSize dc07/ObjectFileName dc0b/ParentObject dc41/PersistantUniqueObjectIdentifier dc44/Name dc08/DateCreated dc87/Width dc88/Height dcd3/ImageBitDepth JFIF/3808: dc01/StorageID dc02/ObjectFormat dc03/ProtectionStatus dc04/ObjectSize dc07/ObjectFileName dc0b/ParentObject dc41/PersistantUniqueObjectIdentifier dc44/Name Device Capabilities: File Download, File Deletion, File Upload No Image Capture, No Open Capture, No vendor specific capture Storage Devices Summary: store_00010001: StorageDescription: External Memory VolumeLabel: Storage Type: Removable RAM (memory card) Filesystemtype: Digital Camera Layout (DCIM) Access Capability: Read Only with Object deletion Maximum Capability: 8060403712 (7687 MB) Free Space (Bytes): 8056569856 (7683 MB) Free Space (Images): 2270 Device Property Summary: Battery Level(0x5001):(read only) (type=0x2) Range [0 - 3, step 1] value: 3% (3) Property 0xd303:(read only) (type=0x2) 1 Perceived Device Type(0xd407):(read only) (type=0x6) 1 Session Initiator Info(0xd406):(readwrite) (type=0x) '' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1296275 Title: PTP Cameras not working on 14.04, works flawlessly on 12.04 Status in GVFS: Confirmed Status in Shotwell: New Status in “gvfs” package in Ubuntu: Triaged Bug description: I have a Canon Powershot A3200 camera. It works perfectly on 12.04, pops right up when I plug it in. However on 14.04 nothing happens. lsusb outputs shows that the camera is detected, with the right model. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1296275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
