[Desktop-packages] [Bug 1682799] Re: mouse pointer disappears on tabs/navbar when screen scaled
Yes, that's still the case. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1682799 Title: mouse pointer disappears on tabs/navbar when screen scaled Status in chromium-browser package in Ubuntu: New Bug description: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1682799/+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 1682799] Re: mouse pointer disappears on tabs/navbar when screen scaled
lspci: ``` 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 02:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 02:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 02:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge] 3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter (rev 08) 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 (rev 01) ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1682799 Title: mouse pointer disappears on tabs/navbar when screen scaled Status in chromium-browser package in Ubuntu: New Bug description: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1682799/+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 1682799] Re: mouse pointer disappears on tabs/navbar when screen scaled
After setting scale to 1x1 and back to 0.75x0.75 just now, my music stopped playing[1] and the screen turned yellow ¯\_(ツ)_/¯: https://goo.gl/photos/HiVim712e2rpQdZy6 1) Might be unrelated though, using HDMI audio output and screen probably just got disconnected by xorg briefly. Didn't realize this before though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1682799 Title: mouse pointer disappears on tabs/navbar when screen scaled Status in chromium-browser package in Ubuntu: New Bug description: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1682799/+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 1682799] [NEW] mouse pointer disappears on tabs/navbar when screen scaled
Public bug reported: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1682799 Title: mouse pointer disappears on tabs/navbar when screen scaled Status in chromium-browser package in Ubuntu: New Bug description: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1682799/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
So yes this fixes the issue for me, although xorg already crashed on me once with that patch applied. Will report back with details if this happens again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
I'm willing to spend some time on this but really don't know how to proceed. Last comment on the upstream bug says 'Egbert', whoever that is, will discuss this on the dev mailing list. I don't know what that involves.. I mean I can also drop a mail to the list and say please, please include this patch but given how many people are involved in the issue who know more than me about this issue that seems silly.. Still, if you think that's the way to go I can just ping the mailing list. Fwiw, I was able to build new debs like this: - Download patch from https://bugs.freedesktop.org/attachment.cgi?id=94929 - apt-get source xserver-xorg-core - cd xorg-server-1.18.3 - quilt import that-downloaded.patch - quilt push - dch -n - debuild -b -uc -us Will see if it fixes the issue for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
Sorry but this is super confusing. Is this a known issue that is being worked on or did I miss something? I've opened this issue because 883319 didn't fix it. Now I tried panning and this also didn't fix it, but that's what was described in 883319. Willing to investigate time in debugging this but I'm really confused about the state of things right now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
Ha well.. No, it was working until I moved my mouse pointer to the other screen. Now my display actually pans around. So still have found no way to get decent sizes on both displays with different DPI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
I can confirm that --panning works for me. While I'm good now, I'd encourage the maintainers to consider this a severe UX issue. It's not at all intuitive that you need to change this option to make it work. Then again, it probably makes sense to add options to the control center for changing the scale factor where it could set the right panning option transparently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
** Changed in: xorg-server (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
I think there was a misunderstanding. The ppa works for me now, the segfault is gone. The Non-ppa package still has the issue described above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in xorg-server package in Ubuntu: Fix Released Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
@tjaalton: OH oops. Yes just realize this package is from your ppa. Hrm looks like it's work now. Maybe the segfault was caused by another package it depends on? At least right now things look stable. Will report back if that changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in xorg-server package in Ubuntu: Triaged Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
Just upgraded my system and the problem seems to be solved. But I'm a bit confused regarding the package versions. Is there a -1ubuntu2 and -1ubuntu2.0? Because later is what is installed now: $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2.0 And the log shows that it was upgraded: 2016-05-17 10:08:54 configure xserver-xorg-core:amd64 2:1.18.3-1ubuntu2.0 2016-05-17 10:08:54 status unpacked xserver-xorg-core:amd64 2:1.18.3-1ubuntu2.0 2016-05-17 10:08:54 status half-configured xserver-xorg-core:amd64 2:1.18.3-1ubuntu2.0 2016-05-17 10:08:54 status installed xserver-xorg-core:amd64 2:1.18.3-1ubuntu2.0 Either way, I'm not affected by this issue anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in xorg-server package in Ubuntu: Triaged Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution
I've tried tjaalton's build with the patch from https://bugs.freedesktop.org/attachment.cgi?id=94929 and while it fixes the problem, it causes a segfault after a few seconds: https://gist.github.com/discordianfish/e91a463ef66ba9dbb3a86f14fc43c129 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in xorg-server package in Ubuntu: Triaged Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123/+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 1580123] [NEW] xrandr --scale (again) confines mouse to native solution
Public bug reported: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Description changed: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: + xrandr --output DP1 --scale 1.25x1.25 - xrandr --output DP1 --scale 1.25x1.25 - - The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. - + The mouse will be still constrained to the native solution (aka you + can't move the mouse outside a box of whatever DP1 had as resolution + before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 + + $ apt-cache policy xserver-xorg-core + xserver-xorg-core: + Installed: 2:1.18.3-1ubuntu2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in xorg-server package in Ubuntu: New Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123/+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 883319] Re: xrandr --scale restricts area in which mouse moves
I have the same issue in up-to-date xenial (1:7.7+13ubuntu3). Is it suppose to be fixed there as well? I can't find anything in the changelog. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Fix Released Status in xorg-server source package in Quantal: Fix Released Status in xorg-server source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+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 1502075] Re: Firefox crash on speakdanish.dk website load
Still repro on 41.0.1. $ sudo apt-show-versions firefox firefox:amd64/vivid-security 41.0.1+build2-0ubuntu0.15.04.2 uptodate firefox:i386 not installed This seems to be something specific to this build/my configuration -- I have some other Linux machines with Firefox 41.0.1 that don't crash on this page. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1502075 Title: Firefox crash on speakdanish.dk website load Status in firefox package in Ubuntu: Incomplete Bug description: Loading www.speakdanish.dk/en/grammar/nouns-et-words-list.php results in Firefox crash ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: firefox 41.0+build3-0ubuntu0.15.04.1 Uname: Linux 3.19.8-031908ckt4-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nichfish 1799 F pulseaudio /dev/snd/controlC1: nichfish 1799 F pulseaudio /dev/snd/controlC0: nichfish 1799 F pulseaudio BuildID: 20150918100231 Channel: Unavailable CurrentDesktop: Unity Date: Fri Oct 2 11:55:41 2015 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-08-03 (59 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 65.53.128.1 dev eth0 proto static metric 100 10.221.22.9 via 65.53.128.1 dev eth0 proto dhcp metric 100 65.53.128.0/23 dev eth0 proto kernel scope link metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-9583564d-952a-4d8c-91fa-473a52150924 Plugins: Java(TM) Plug-in 11.60.2 - /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=41.0/20150918100231 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-9583564d-952a-4d8c-91fa-473a52150924 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2015 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.3 R1.15.0 for D3128-A1x dmi.board.name: D3128-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3128-A1 dmi.chassis.type: 7 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$M710 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.15.0forD3128-A1x:bd01/30/2015:svnFUJITSU:pnCELSIUSM720:pvr:rvnFUJITSU:rnD3128-A1:rvrS26361-D3128-A1:cvnFUJITSU:ct7:cvrC$M710: dmi.product.name: CELSIUS M720 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1502075/+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 1502075] [NEW] Firefox crash on speakdanish.dk website load
Public bug reported: Loading www.speakdanish.dk/en/grammar/nouns-et-words-list.php results in Firefox crash ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: firefox 41.0+build3-0ubuntu0.15.04.1 Uname: Linux 3.19.8-031908ckt4-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nichfish 1799 F pulseaudio /dev/snd/controlC1: nichfish 1799 F pulseaudio /dev/snd/controlC0: nichfish 1799 F pulseaudio BuildID: 20150918100231 Channel: Unavailable CurrentDesktop: Unity Date: Fri Oct 2 11:55:41 2015 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-08-03 (59 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 65.53.128.1 dev eth0 proto static metric 100 10.221.22.9 via 65.53.128.1 dev eth0 proto dhcp metric 100 65.53.128.0/23 dev eth0 proto kernel scope link metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-9583564d-952a-4d8c-91fa-473a52150924 Plugins: Java(TM) Plug-in 11.60.2 - /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=41.0/20150918100231 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-9583564d-952a-4d8c-91fa-473a52150924 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2015 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.3 R1.15.0 for D3128-A1x dmi.board.name: D3128-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3128-A1 dmi.chassis.type: 7 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$M710 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.15.0forD3128-A1x:bd01/30/2015:svnFUJITSU:pnCELSIUSM720:pvr:rvnFUJITSU:rnD3128-A1:rvrS26361-D3128-A1:cvnFUJITSU:ct7:cvrC$M710: dmi.product.name: CELSIUS M720 dmi.sys.vendor: FUJITSU ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1502075 Title: Firefox crash on speakdanish.dk website load Status in firefox package in Ubuntu: New Bug description: Loading www.speakdanish.dk/en/grammar/nouns-et-words-list.php results in Firefox crash ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: firefox 41.0+build3-0ubuntu0.15.04.1 Uname: Linux 3.19.8-031908ckt4-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nichfish 1799 F pulseaudio /dev/snd/controlC1: nichfish 1799 F pulseaudio /dev/snd/controlC0: nichfish 1799 F pulseaudio BuildID: 20150918100231 Channel: Unavailable CurrentDesktop: Unity Date: Fri Oct 2 11:55:41 2015 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-08-03 (59 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 65.53.128.1 dev eth0 proto static metric 100 10.221.22.9 via 65.53.128.1 dev eth0 proto dhcp metric 100 65.53.128.0/23 dev eth0 proto kernel scope link metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-9583564d-952a-4d8c-91fa-473a52150924 Plugins: Java(TM) Plug-in 11.60.2 - /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default)
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
#48 do you mean that you want to let pulseaudio to use analog and the another user/application to use hdmi audio ? No, I only want to use one audio output, and I'd like this to be my analog output by default. My default audio output is currently my HDMI port, and when I change it my settings are lost after I reboot. The only way I can make my analog audio output be the default is if I unplug my HDMI cable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in PulseAudio sound server: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
I've attached some pulseaudio logs based on the procedure from #32, but this time after setting my HDMI audio to: auto, on and off (using xrandr). The first log for each setting is from step 3, i.e. before using the pactl command (in step 4). The second log is from step 6. ** Attachment added: pulseaudio output for various HDMI audio settings https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+attachment/4031424/+files/pulseaudio_logs-auto-on-off.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in PulseAudio sound server: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
# 46: do mean HDMI still available when you run xrandr --output HDMI --set audio off No it's not available - I meant there were no changes from the point of view of my default output. The HDMI audio was present for the on and auto settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in PulseAudio sound server: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1256511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
#43: I ran alsa-info.sh for different xrandr settings: auto and on are identical, but off is slightly different. I didn't notice any difference in how pulseaudio was working. See attachment. ** Attachment added: alsa info logs for different xrandr settings https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+attachment/4025881/+files/alsa-info_logs.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in PulseAudio sound server: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1256511/+subscriptions
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
I've just submitted the same bug report on freedesktop.org. https://bugs.freedesktop.org/show_bug.cgi?id=73375 ** Bug watch added: freedesktop.org Bugzilla #73375 https://bugs.freedesktop.org/show_bug.cgi?id=73375 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
** Changed in: pulseaudio (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+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 1256511] Re: Sounds settings lost after reboot
#10: I didn't know about that file. I've just tried changing the paths- output lines within /usr/share/pulseaudio/alsa-mixer/profile- sets/default.conf to include the analog-output-lineout entry as shown in the diff output, but it didn't make any difference. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: New Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
#7: I tried adding those changes to /usr/share/pulseaudio/alsa- mixer/paths/analog-output.conf, but it didn't help. If my HDMI cable is attached when I boot my PC, then that's always chosen as the default output. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: New Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+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
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
#2: do you mean pulseaudio select hdmi automatically even speaker is plugged into Line Out jack ? - Yes, my Line-Out is always connected to my PC speakers, and my HDMI is always connected to my TV. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: New Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+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 1256511] Re: Sounds settings lost after reboot
#4: No, I don't have that file. $ ls /usr/share/pulseaudio/alsa-mixer/paths/analog-output* /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common /usr/share/pulseaudio/alsa-mixer/paths/analog-output-desktop-speaker.conf /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones-2.conf /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf /usr/share/pulseaudio/alsa-mixer/paths/analog-output-mono.conf /usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker-always.conf /usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: New Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3
[Desktop-packages] [Bug 1256511] Re: Sounds settings lost after reboot
#3: continued... If I unplug my HDMI cable and restart my PC, then the Analog Stereo (Line-Out) output is used as the default (it's the only output available). But when I plug-in my HDMI cable and reboot, the HDMI output becomes the default again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: New Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1256511] [NEW] Sounds settings lost after reboot
Public bug reported: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my fallback device (which I think means default device?), but my changes are not saved between reboots. After changing the output device to Analogue Stereo using the Configuration tab, I then have to change the output of the individual program using the Playback tab, since it uses the current default (HDMI). I've tried setting my default audio device using pacmd, but it hasn't helped: my Analogue device does show up as the active sink when I run pacmd list-sinks, but it's not the selected device within the Volume Control (in the Configuration tab) so I don't get any sound unless I manually change it using the GUI. Here's the output of some pactl commands after I start my PC - note that the Analog Stereo source is missing: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz SUSPENDED After I open the pulse-audio Volume Control and select the Analog Stereo item from the Configuration tab, running the same commands again gives: $ pactl list sources short 0 alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c s16le 1ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_output.pci-_00_1b.0.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE $ pactl list sinks short 0 alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c s16le 2ch 44100Hz IDLE 1 alsa_output.pci-_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz IDLE The Analogue Stereo source is present and I can hear sound through my PC's speakers. But when I reboot my PC these settings are lost, and I have to do this over again. I wouldn't mind so much if I could fix this from the command line, but I haven't found a way to do that. I'm not 100% certain this is a pulseaudio bug - that's just my best guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fish 3878 F pulseaudio /dev/snd/pcmC0D3p: fish 3878 F...m pulseaudio /dev/snd/controlC1: fish 3878 F pulseaudio /dev/snd/pcmC1D0c: fish 3878 F...m pulseaudio Date: Sat Nov 30 13:59:41 2013 InstallationDate: Installed on 2013-03-01 (273 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1256511 Title: Sounds settings lost after reboot Status in “pulseaudio” package in Ubuntu: New Bug description: I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since then I have no sound when I start my PC, because it's being sent to the HDMI output (my TV). I want it to go to the Analogue output (my PC) like it used to on 13.04. I can change it using the pulse-audio Volume Control program, but my settings are lost after I reboot. The pulse-audio Volume Control doesn't have my Analogue Output as a valid option in the Output Devices tab; it appears only after I select Analogue Stereo within the Configuration tab. I then choose it as my
[Desktop-packages] [Bug 855100] Re: python plugins not working
Any update when upnp-coherence plugin will be fixed or if it will be fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/855100 Title: python plugins not working Status in “totem” package in Ubuntu: Confirmed Status in “totem” source package in Oneiric: Fix Released Bug description: Hi, I upgraded to Oneiric and noticed that the upnp-coherence plugin is missing. After installing it manually, I noticed that some plugins aren't working on totem. Output from console: (totem:5249): libpeas-WARNING **: Could not find 'Module' in '/usr/lib/totem/plugins/upnp-coherence/upnp-coherence.plugin' (totem:5249): libpeas-WARNING **: Error loading '/usr/lib/totem/plugins/upnp-coherence/upnp-coherence.plugin' /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject Traceback (most recent call last): File /usr/lib/totem/plugins/pythonconsole/pythonconsole.py, line 69, in module class PythonConsolePlugin(gobject.GObject, Peas.Activatable): TypeError: Error when calling the metaclass bases metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases (totem:5249): libpeas-WARNING **: Error loading plugin 'pythonconsole' Traceback (most recent call last): File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 298, in module class OpenSubtitles(gobject.GObject, Peas.Activatable): TypeError: Error when calling the metaclass bases metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases (totem:5249): libpeas-WARNING **: Error loading plugin 'opensubtitles' Traceback (most recent call last): File /usr/lib/totem/plugins/jamendo/jamendo.py, line 66, in module class JamendoPlugin(gobject.GObject, Peas.Activatable, PeasGtk.Configurable): TypeError: Error when calling the metaclass bases metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases (totem:5249): libpeas-WARNING **: Error loading plugin 'jamendo' Traceback (most recent call last): File /usr/lib/totem/plugins/dbus/dbus-service.py, line 30, in module class dbusservice(gobject.GObject, Peas.Activatable): TypeError: Error when calling the metaclass bases metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases (totem:5249): libpeas-WARNING **: Error loading plugin 'dbus-service' Traceback (most recent call last): File /usr/lib/totem/plugins/iplayer/iplayer.py, line 16, in module class IplayerPlugin (gobject.GObject, Peas.Activatable): TypeError: Error when calling the metaclass bases metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases (totem:5249): libpeas-WARNING **: Error loading plugin 'iplayer' Totem-Message: socket created Segmentation fault (core dumped) ProblemType: BugDistroRelease: Ubuntu 11.10 Package: totem 3.0.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 NonfreeKernelModules: slamr ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Tue Sep 20 23:39:19 2011SourcePackage: totem UpgradeStatus: Upgraded to oneiric on 2011-09-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/855100/+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 827382] Re: Coherence uPNP plugin missing in totem in Oneiric
Updated dependencies of totem-coherence to match the new code using introspection but keep the package disabled as python-coherence is still PyGTK based and thus incompatible. https://launchpad.net/ubuntu/+source/totem/3.0.1-0ubuntu1 from change log per [ Raphaël Hertzog ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/827382 Title: Coherence uPNP plugin missing in totem in Oneiric Status in “totem” package in Ubuntu: Confirmed Bug description: I have installed totem-plugins-extra and can see the BBC iPlayer plugin in Totem but not the Coherence uPNP plugin when running Oneiric with all updates. Both are listed in Synaptic as being part of that package. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: totem-plugins-extra 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed Aug 17 00:00:32 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110319) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to oneiric on 2011-07-27 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/827382/+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 832533] Re: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
this is no longer affecting me. -- 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/832533 Title: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance() Status in GVFS: New Status in Unity Greeter: Fix Released Status in “gvfs” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: Fix Released Status in “gvfs” source package in Oneiric: New Status in “unity-greeter” source package in Oneiric: Fix Released Bug description: Oneiric i386 silent crash logged after a cold boot ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gvfs-fuse 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic-pae 3.0.3 Uname: Linux 3.0.0-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Aug 24 07:54:14 2011 ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon ProcCmdline: /usr/lib/gvfs//gvfs-fuse-daemon /var/lib/lightdm/.gvfs ProcEnviron: SHELL=/bin/false PATH=(custom, no user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0xb6114fa1:mov0xc(%eax),%eax PC (0xb6114fa1) ok source 0xc(%eax) (0x000c) not located in a known VMA region (needed readable region)! destination %eax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/gio/modules/libgvfsdbus.so ?? () from /usr/lib/gio/modules/libgvfsdbus.so g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/832533/+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 862161] Re: check_gl_texture_size crashed with SIGSEGV in __libc_start_main()
error appeared on desktop nothing else seems out of place -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/862161 Title: check_gl_texture_size crashed with SIGSEGV in __libc_start_main() Status in “gnome-desktop3” package in Ubuntu: Confirmed Bug description: Bug occurs in Unity2D session.. no more information . last update/upgrade 20110929 at 11.00 am ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: libgnome-desktop-3-2 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Sep 29 10:59:46 2011 ExecutablePath: /usr/lib/gnome-desktop3/check_gl_texture_size InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110808) ProcCmdline: /usr/lib/gnome-desktop3/check_gl_texture_size ProcEnviron: SegvAnalysis: Segfault happened at: 0x400872: mov0xe0(%rax),%esi PC (0x00400872) ok source 0xe0(%rax) (0x00e0) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-desktop3 StacktraceTop: ?? () __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () Title: check_gl_texture_size crashed with SIGSEGV in __libc_start_main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/862161/+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 835810] Re: telepathy-haze crashed with SIGSEGV in vfprintf()
Same issue. loaded empathy prior to starting skype. Error came up upon starting empathy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-haze in Ubuntu. https://bugs.launchpad.net/bugs/835810 Title: telepathy-haze crashed with SIGSEGV in vfprintf() Status in “telepathy-haze” package in Ubuntu: Confirmed Bug description: I tried to use pidgin-skype plugin in empathy when skype was not running and this bug came up ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: telepathy-haze 0.5.0-1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sat Aug 27 23:04:04 2011 ExecutablePath: /usr/lib/telepathy/telepathy-haze InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110716) ProcCmdline: /usr/lib/telepathy/telepathy-haze ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f17835a81a4 vfprintf+7348:repnz scas %es:(%rdi),%al PC (0x7f17835a81a4) ok source %es:(%rdi) (0x0002) not located in a known VMA region (needed readable region)! destination %al ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-haze StacktraceTop: vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 __vasprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 skype_debug_vargs () from /usr/lib/purple-2/libskype_dbus.so Title: telepathy-haze crashed with SIGSEGV in vfprintf() UpgradeStatus: Upgraded to oneiric on 2011-08-15 (13 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-haze/+bug/835810/+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 857348] Re: All python plugins are broken by a bad import
#15 fixes rhymthbox plugins on amd64 - same issue with plugins -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/857348 Title: All python plugins are broken by a bad import Status in Python bindings for GObject: Unknown Status in “pygobject” package in Ubuntu: Triaged Bug description: All python plugins in gedit are disabled because of a python import error. This affects all apps that use libpeas to to host python plugins. (gedit:3574): libpeas-WARNING **: Error initializing Python Plugin Loader:PyGObject initialization failed ImportError: could not import gobject (error was: '/usr/lib/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: _Py_ZeroStruct') Error in sys.excepthook: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport_python_hook.py, line 59, in apport_excepthook from apport.fileutils import likely_packaged File /usr/lib/python2.7/dist-packages/apport/__init__.py, line 1, in module from apport.report import Report File /usr/lib/python2.7/dist-packages/apport/report.py, line 16, in module from xml.parsers.expat import ExpatError File /usr/lib/python2.7/xml/parsers/expat.py, line 4, in module from pyexpat import * ImportError: /usr/lib/python2.7/lib-dynload/pyexpat.so: undefined symbol: _Py_ZeroStruct Original exception was: ImportError: could not import gobject (error was: '/usr/lib/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: _Py_ZeroStruct') (gedit:3574): libpeas-WARNING **: Please check the installation of all the Python related packages required by libpeas and try again (gedit:3574): libpeas-WARNING **: Loader 'python' is not a valid PeasPluginLoader instance (gedit:3574): libpeas-WARNING **: Could not find loader 'python' for plugin 'gdpbzr' ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gir1.2-peas-1.0 1.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 NonfreeKernelModules: nvidia wl ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Fri Sep 23 08:38:30 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libpeas UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/857348/+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 858204] Re: Rhythmbox plugins not working properly
same issue on multiarch amd64 upgrade i believe it worked a few days ago but is not working now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/858204 Title: Rhythmbox plugins not working properly Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: I can't able to enable the context menu ,IM status ,cover art , song lyrics etc... ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: rhythmbox 2.90.1~20110908-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 24 18:35:12 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: rhythmbox UpgradeStatus: Upgraded to oneiric on 2011-09-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/858204/+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 822253] Re: gdm's metacity stays running in the session that's started
Hi all. I've just reported the same bug in Mageia Linux Cauldron. It tripped me this morning after I restarted KDE: https://bugs.mageia.org/show_bug.cgi?id=2628 ** Bug watch added: bugs.mageia.org/ #2628 https://bugs.mageia.org/show_bug.cgi?id=2628 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/822253 Title: gdm's metacity stays running in the session that's started Status in “gdm” package in Ubuntu: New Bug description: I'm running a system with both KDE and Gnome installed. The login manager is gdm, but most of the time I then start from that a KDE plasma session. Occasionally the KDE session isn't started properly and I find that the 'metacity' window manager is running (but with most of the KDE processes). Worryingly this metacity seems to be owned by 'gdm' which makes me regard this as a security issue - I shouldn't have any X clients running by a priveliged user in my session. dg@major:~$ xlsclients major kded4 major kded4 major /usr/bin/kglobalaccel major /usr/bin/kglobalaccel major ksmserver major ksmserver major /usr/bin/knotify4 major /usr/bin/knotify4 major /usr/bin/plasma-desktop major /usr/bin/plasma-desktop major /usr/bin/kactivitymanagerd major /usr/bin/kactivitymanagerd major /usr/bin/plasma-desktop repeated major /usr/bin/plasma-desktop major /usr/bin/kuiserver major /usr/bin/kuiserver major /usr/bin/plasma-desktop repeated major /usr/bin/plasma-desktop major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_contacts_resource major /usr/bin/akonadi_vcard_resource major /usr/bin/akonadi_vcard_resource major /usr/bin/nepomukservicestub major /usr/bin/nepomukservicestub major /usr/bin/plasma-desktop major /usr/bin/krunner major /usr/bin/krunner major /usr/bin/krunner major /usr/bin/nepomukcontroller major /usr/bin/nepomukcontroller major kmix major kmix major /usr/bin/plasma-desktop major kmix major kmix major kmix major /usr/bin/printer-applet major /usr/bin/printer-applet major /usr/bin/klipper major /usr/bin/klipper major /usr/bin/klipper major /usr/bin/printer-applet major /usr/bin/plasma-desktop major /usr/bin/plasma-desktop major /usr/bin/plasma-desktop major /usr/bin/plasma-desktop major /usr/bin/plasma-desktop major /usr/bin/plasma-desktop major /usr/bin/krunner major /usr/bin/rekonq major /usr/bin/rekonq major /usr/lib/kde4/libexec/kpackagekitsmarticon major /usr/lib/kde4/libexec/kpackagekitsmarticon major metacity major /usr/bin/konsole major /usr/bin/konsole major /usr/bin/konsole major /usr/bin/konsole major /usr/bin/konsole major /usr/bin/konsole major /usr/bin/rekonq major /usr/bin/konsole major nautilus major wicd-client.py major chromium-browser major rekonq major npviewer.bin major /usr/bin/rekonq major kmix dg@major:~$ ps -eaf|grep metacity gdm 1815 1 0 12:41 ?00:00:00 metacity dg3840 3093 0 12:50 pts/12 00:00:00 grep metacity I'd seen this on Natty with the Gnome 3 ppa installed, but that's been purged now and I'm running OO without ppa. Dave ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gdm 3.0.4-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570 CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948 Date: Sun Aug 7 12:44:43 2011 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gdm UpgradeStatus: Upgraded to oneiric on 2011-07-31 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/822253/+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
