Re: [Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-10-13 Thread Scott Palmer
I can confirm that I am still having this issue on 3.34 as well
(Manjaro).

This is shocking to me that anyone using Gnome to develop doesn't
encounter this bug at minimum of 5x per day.  Or are Gnome developers
using MacOS and MBPs to develop like those in the lol "Linux"
Foundation.


+Scott


‐‐‐ Original Message ‐‐‐
On Sunday, October 13, 2019 7:42 AM, kohey  wrote:

> Yes, the issue still happens with 3.34.
> My work around is to trigger the following script through a keyboard shortcut.
> gsettings set org.gnome.desktop.peripherals.touchpad send-events disabled
> sleep 1
> gsettings set org.gnome.desktop.peripherals.touchpad send-events enabled
> gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click false
> sleep 1
> gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click true
>
> -
>
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1181666
>
> Title:
> gnome-shell randomly blocks mouse clicks from working in app windows
>
> Status in GNOME Shell:
> Confirmed
> Status in Ubuntu GNOME:
> Confirmed
> Status in gnome-shell package in Ubuntu:
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Under GNOME 3, the use of the mouse-click stops occasionally, though I
> can still move the mouse around and can still click on items in the
> Activities screen and the top-bar.
>
> I can use alt-tab to cycle windows and can still type into already-
> active textboxes in windows, but I cannot click within the windows,
> and the mouse is not picked up at all by the windows.
>
> I can open the alt-f2 "run command" dialogue, but cannot type into it.
>
> The workaround I'm using is to open terminal (ctrl-alt-T) and run
> "gnome-shell -r", and restarting that command every time I have the
> problem again.
>
> Please ask if there's anything I forgot to mention.
>
> ADDITIONAL: The error tends to happen randomly, but it seems to happen
> upon opening a new window, changing windows, closing windows, or
> opening the activities pane (whether a change of window is thus
> instigated or not)
>
> ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
> and to log in again, but that is also less than ideal
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: gnome-shell 3.6.3.1-0ubuntu6
> ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
> Uname: Linux 3.8.0-22-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> Date: Sun May 19 07:02:18 2013
> DisplayManager: gdm
> GsettingsChanges:
>  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
>  b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
>  b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
>  b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
>  b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
> InstallationDate: Installed on 2013-05-04 (14 days ago)
> InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
> (20130424)
> MarkForUpload: True
> ProcEnviron:
>  LANGUAGE=en_GB:en
>  PATH=(custom, no user)
>  XDG_RUNTIME_DIR=
> LANG=en_GB.UTF-8
>  SHELL=/bin/bash
> SourcePackage: gnome-shell
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, 

[Desktop-packages] [Bug 220263] Re: Bad Firefox integration with dark themes

2019-05-25 Thread Scott Palmer
For those that run linux and want to update their Firefox icon so it
automatically launches with GTK_THEME="Adwaita:light" firefox %u instead
(band-aid work around that shouldn't need to be).

$ cp /usr/share/applications/firefox.desktop ~/.local/share/applications
$ gedit ~/.local/share/applications/firefox.desktop

Change the "Exec=" line to read:

Exec=bash -c "GTK_THEME=\"Adwaita:light\" firefox %u &"

Save and Exit.  
Now your Firefox icon should start using the Adwaita:light theme without a 
lingering terminal window.

-- 
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/220263

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 220263] Re: Bad Firefox integration with dark themes

2019-05-25 Thread Scott Palmer
I am having this issue with Firefox 66.0.3 using Ubuntu 19.04 (Gnome
3.32 using Adwaita dark).

This release seems to ignore:

  widget.content.allow-gtk-dark-theme in about:config is set to default / false
  widget.chrome.allow-gtk-dark-theme in about:config is also default /false

I came back to Firefox after running Brave for a bit only to find this
Is this just another Mozilla blunder?  Time to install Brave again.

** Attachment added: "Screenshot from 2019-05-25 13-20-00.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/220263/+attachment/5266533/+files/Screenshot%20from%202019-05-25%2013-20-00.png

-- 
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/220263

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 1828649] Re: Wayland session freezes

2019-05-17 Thread Scott Palmer
I believe I made a mistake in the steps taken above.

I believe I rebooted my computer once after the `journalctl --vacuum-
time=1s`

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1828649

Title:
  Wayland session freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
  was to use a PASSIVE adaptor, I cannot drive two external displays and
  the laptop display.

  With my laptop screen closed, I was able to drive both displays in
  Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
  kernel has always (as far as I know) been lacking in smarts to drive
  all three displays.

  This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
  laptop).

  Main screen is 2560x1600 via DisplayPort to laptop.
  Secondary screen is 1920x1200 via DisplayPort to laptop dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 10 16:55:27 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2019-03-25 (46 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.sku: LENOVO_MT_3435
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+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 1828649] Re: Wayland session freezes

2019-05-17 Thread Scott Palmer
# journalctl rotate
# journalctl --vacuum-time=1s





journalctl -b-1 --no-pager > prevboot.txt

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+attachment/5264569/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1828649

Title:
  Wayland session freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
  was to use a PASSIVE adaptor, I cannot drive two external displays and
  the laptop display.

  With my laptop screen closed, I was able to drive both displays in
  Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
  kernel has always (as far as I know) been lacking in smarts to drive
  all three displays.

  This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
  laptop).

  Main screen is 2560x1600 via DisplayPort to laptop.
  Secondary screen is 1920x1200 via DisplayPort to laptop dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 10 16:55:27 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2019-03-25 (46 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.sku: LENOVO_MT_3435
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+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 1828649] [NEW] Wayland freeze

2019-05-10 Thread Scott Palmer
Public bug reported:

When I switch to wayland the gnome desktop locks up before I see my desktop.
It doesn't lock up when I have my laptop closed and only one display connected.
When I connect up the second display, it locks up every time.
I tried deleting my monitors.xml file..  that doesn't make any difference.

I was able to get it to work by connecting one display via DisplayPort.
When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

Additionally, when I lift my laptop screen, one of my monitors goes out
and re-enabling it causes another to go off.  Linux kernel is not smart
enough to drive the 3 displays.  I am able to drive two monitors and
have my laptop screen open in Windows just fine.

Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
was to use a PASSIVE adaptor, I cannot drive two external displays and
the laptop display.

With my laptop screen closed, I was able to drive both displays in
Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
kernel has always (as far as I know) been lacking in smarts to drive all
three displays.

This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
laptop).

Main screen is 2560x1600 via DisplayPort to laptop.
Secondary screen is 1920x1200 via DisplayPort to laptop dock.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 10 16:55:27 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2019-03-25 (46 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: GCETB2WW (2.72 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.sku: LENOVO_MT_3435
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco freeze ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1828649

Title:
  Wayland freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance 

Re: [Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-02-10 Thread Scott Palmer
The solution until this is solved is to use something other than gnome
shell as far as I know.  Mint Cinnamon and Elementary are both popular
alternatives.

On Sun, Feb 10, 2019, 1:29 PM Adrian <1181...@bugs.launchpad.net wrote:

> I am facing the same issue in Ubuntu 18.10. The super key randomly stops
> working and I loose control of all windows except for the active window,
> which in some cases also stops working and cannot even do clicks there.
> The workaround I found is to close all windows, lock the screen and the
> problem solves for 5-10 min or so. But this is clearly impractical and I
> can't really go on like this any further. I re-installed the OS but it
> didn't solve the issue. I have a Lenovo T430s if that helps. Does anyone
> found a solution to this yet? I'd appreciate it very much!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1181666
>
> Title:
>   gnome-shell randomly blocks mouse clicks from working in app windows
>
> Status in GNOME Shell:
>   Confirmed
> Status in Ubuntu GNOME:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Under GNOME 3, the use of the mouse-click stops occasionally, though I
>   can still move the mouse around and can still click on items in the
>   Activities screen and the top-bar.
>
>   I can use alt-tab to cycle windows and can still type into already-
>   active textboxes in windows, but I cannot click within the windows,
>   and the mouse is not picked up at all by the windows.
>
>   I can open the alt-f2 "run command" dialogue, but cannot type into it.
>
>   The workaround I'm using is to open terminal (ctrl-alt-T) and run
>   "gnome-shell -r", and restarting that command every time I have the
>   problem again.
>
>   Please ask if there's anything I forgot to mention.
>
>   ADDITIONAL: The error tends to happen randomly, but it seems to happen
>   upon opening a new window, changing windows, closing windows, or
>   opening the activities pane (whether a change of window is thus
>   instigated or not)
>
>   ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
>   and to log in again, but that is also less than ideal
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.04
>   Package: gnome-shell 3.6.3.1-0ubuntu6
>   ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
>   Uname: Linux 3.8.0-22-generic x86_64
>   ApportVersion: 2.9.2-0ubuntu8
>   Architecture: amd64
>   Date: Sun May 19 07:02:18 2013
>   DisplayManager: gdm
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'clock-show-date' b'true'
>b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
>b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
>b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
>b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono
> 12'"
>   InstallationDate: Installed on 2013-05-04 (14 days ago)
>   InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   MarkForUpload: True
>   ProcEnviron:
>LANGUAGE=en_GB:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_GB.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  

[Desktop-packages] [Bug 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2018-10-21 Thread Scott Palmer
Don't get too excited..
https://gitlab.gnome.org/GNOME/nautilus/issues/703

-- 
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/1706097

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Fedora:
  Unknown

Bug description:
  I get this every day when I have connected my Android phone for
  charging its battery.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:29:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (816 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
   PC (0x7fea768b6cc9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1706097/+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 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer
** Attachment added: "the horizontal band"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203629/+files/20181020_172736.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1799061

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+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 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer
** Attachment added: "the bright box"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203630/+files/20181020_172739.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1799061

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+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 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer
Also note that the screen jitters at the GDM login screen.

My video card does not exhibit have any of these issues when I boot into
Windows 10.

Sometimes logging in doesn't fix the jittering so I reboot into Windows
10.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1799061

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+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 1799061] [NEW] Corruption at GDM screen

2018-10-21 Thread Scott Palmer
Public bug reported:

Video does not appear to be getting set correctly for GDM but seems
"corrected" after I login.

I have attached some screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 21 08:01:42 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
InstallationDate: Installed on 2018-10-20 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption cosmic ubuntu wayland-session

** Attachment added: "20181020_172728.jpg"
   
https://bugs.launchpad.net/bugs/1799061/+attachment/5203613/+files/20181020_172728.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1799061

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 23001] Re: Copying using ctrl +c doesn't copy in file-roller

2018-09-13 Thread Scott Palmer
Copy and Paste is not working for me on a freshly installed copy of 18.04.1 
using Wayland.
Is this regression from 3 years ago still not resolved?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/23001

Title:
  Copying using ctrl +c doesn't copy in file-roller

Status in File Roller:
  Expired
Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  Reproduce: 
   Open an archive and copy one or more files using ctrl+c

  Expected result:
   The selected file(s) should be copied to clipboard

  Actual result:
   No files are copied to the clipboard

  http://bugzilla.gnome.org/show_bug.cgi?id=143195:
  http://bugzilla.gnome.org/show_bug.cgi?id=143195

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/23001/+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 1724921] Re: VLANs get incorrectly listed under Bluetooth

2018-07-05 Thread Scott Palmer
This also affects 18.04 (updated to July 5, 2018)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1724921

Title:
  VLANs get incorrectly listed under Bluetooth

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  I expected them to show up under Wired because the VLANs' associated
  adapter is wired.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:25:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724921/+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 1780360] [NEW] Wayland session doesnt work with Monitor in either Portrait mode

2018-07-05 Thread Scott Palmer
Public bug reported:

When I use a Wayland session I am unable to use either Portrait mode.

I have the same problem at work using my Intel Integrated Video on my
Lenovo X230 laptop.

Given that both AMD and Intel are broken, it looks to be a regression of
some sort.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Jul  5 17:29:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] 
[1462:8a91]
InstallationDate: Installed on 2018-05-27 (39 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=0c69e0ec-e162-4882-aa5d-337219c7f2c8 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1780360

Title:
  Wayland session doesnt work with Monitor in either Portrait mode

Status in xorg package in Ubuntu:
  New

Bug description:
  When I use a Wayland session I am unable to use either Portrait mode.

  I have the same problem at work using my Intel Integrated Video on my
  Lenovo X230 laptop.

  Given that both AMD and Intel are broken, it looks to be a regression
  of some sort.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Jul  5 17:29:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] 
[1462:8a91]
  InstallationDate: Installed on 2018-05-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Desktop-packages] [Bug 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2018-03-17 Thread Scott Palmer
Also note that this problem also affects Bionic 18.04 users with
4.15.0-12-generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2018-03-17 Thread Scott Palmer
** Attachment added: "Fresh boot -- after re-plug -- woking sound from rear 
green jack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082539/+files/alsa-info-after.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2018-03-17 Thread Scott Palmer
** Attachment added: "Fresh boot -- no sound from rear green jack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082538/+files/alsa-info-before.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1756484] Re: Screen flickers and small moving artifacts

2018-03-16 Thread Scott Palmer
I believe I have corrected this by changing my refresh rate from 59.99
Hz to 59.86 Hz.

Is this a requirement for 2560x1600 resolution on DL-DVI?  Should this
perhaps be communicated upstream to someone who knows better?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1756484

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756484/+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 1710752] Re: Intel HDA Audio doesn't work

2018-03-16 Thread Scott Palmer
I just installed the 18.04 daily and formatted a fresh partition (no
prior home directory or any existing data used) and this is still an
issue in 4.15.0-12-generic.

Can I run a command to manually turn on this jack at startup or force it
to recheck that input to see if something is plugged in?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710752

Title:
  Intel HDA Audio doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
   Built-in Audio and there is no option to select anything else.  If I unplug 
my line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710752/+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 1756484] [NEW] Screen flickers and small moving artifacts

2018-03-16 Thread Scott Palmer
Public bug reported:

This is likely a wayland issue.  I can't bear the tearing if I don't use
wayland.

I get screen flickering (approximately every 5 seconds) and some windows
seem to bring up some mis-colored moving artifacts that clear when the
window is closed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 20:07:47 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
InstallationDate: Installed on 2018-03-17 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic reproducible ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1756484

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1725532] Re: wired network ignores auto connect setting and does not auto connect

2017-10-29 Thread Scott Palmer
The other bug was closed.  Here is the correct one.

https://bugzilla.gnome.org/show_bug.cgi?id=789626

** Bug watch added: GNOME Bug Tracker #789626
   https://bugzilla.gnome.org/show_bug.cgi?id=789626

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1725532

Title:
  wired network ignores auto connect setting and does not auto connect

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532/+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 1723815] Re: Unable to show files on MTP connection

2017-10-29 Thread Scott Palmer
https://gitlab.gnome.org/GNOME/nautilus/issues/91

-- 
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/1723815

Title:
  Unable to show files on MTP connection

Status in gvfs package in Ubuntu:
  New

Bug description:
  Opening "Samsung_Android\Card\DCIM\Camera" folder with many images
  gets stuck at "Loading..." and never shows anything.  I have waited 10
  minutes.  There is no error and not a single icon shows.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 16:36:50 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1723815/+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 1725532] Re: wired network ignores auto connect setting and does not auto connect

2017-10-29 Thread Scott Palmer
I tried to file a bug report here:

https://gitlab.gnome.org/GNOME/Infrastructure/issues/50

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1725532

Title:
  wired network ignores auto connect setting and does not auto connect

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-28 Thread Scott Palmer
This was fixed for a while by an update that came in, but now this
problem has come back.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-22 Thread Scott Palmer
It could be related to this bug:

See Comment #62   https://bugzilla.gnome.org/show_bug.cgi?id=745079#c62

** Bug watch added: GNOME Bug Tracker #745079
   https://bugzilla.gnome.org/show_bug.cgi?id=745079

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724977

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1093129] Re: system settings -> printer is not able to delete not started print jobs

2017-10-22 Thread Scott Palmer
Also, The Active Jobs window does not seem to ever update / refresh
itself.

I accidentally printed the same document two times.  My printer wasn't
plugged in so I just went to the Active Jobs window and clicked the [X]
button to delete the "Pending" entry.  It did nothing.  I plugged in my
printer and both jobs printed.  Unexpectedly, both jobs are still listed
in Active Jobs.  The top entry still says "Processing" and the second
entry still says "Pending".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1093129

Title:
  system settings ->  printer is not able to delete not started print
  jobs

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  System settings -> Printer -> Jobs

  shows correct all print jobs, but it is not able to delete them.

  The pause and stop buttons are availabe and clickable, but do not take
  any action on the print jobs.

  
  Steps to reproduce(not tested):

  1.Send a print job from firefox(html)
  2.Send a second print job from evince(pdf)
  3.Call System Settings -> Printers -> Jobs
  4.Try to stop the second not started print job with the buttons for that
  5.See that failing
  6.Have a not wanted print.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sat Dec 22 17:03:57 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-07-22 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to raring on 2012-11-15 (36 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   indicator-datetime  12.10.3daily12.11.23-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1093129/+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 1093129] Re: system settings -> printer is not able to delete not started print jobs

2017-10-22 Thread Scott Palmer
Oh!  I should also note that I am running Ubuntu 17.10.
Printer is a Samsung C460.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1093129

Title:
  system settings ->  printer is not able to delete not started print
  jobs

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  System settings -> Printer -> Jobs

  shows correct all print jobs, but it is not able to delete them.

  The pause and stop buttons are availabe and clickable, but do not take
  any action on the print jobs.

  
  Steps to reproduce(not tested):

  1.Send a print job from firefox(html)
  2.Send a second print job from evince(pdf)
  3.Call System Settings -> Printers -> Jobs
  4.Try to stop the second not started print job with the buttons for that
  5.See that failing
  6.Have a not wanted print.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sat Dec 22 17:03:57 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-07-22 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to raring on 2012-11-15 (36 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   indicator-datetime  12.10.3daily12.11.23-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1093129/+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 1725532] [NEW] wired network ignores auto connect setting and does not auto connect

2017-10-20 Thread Scott Palmer
Public bug reported:

My onboard Intel network adapter has [X] Connect automatically but when
I start my Gnome session, I always have to tell it to Connect which it
does without error.

You can't see it in the Gnome dialog windows but this connection is set
to also connect to a VPN.  I setup this connection with nm-connection-
editor.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:26:18 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Tags removed: wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1725532

Title:
  wired network ignores auto connect setting and does not auto connect

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer
I have attached a photo of my screen showing this behavior.

Notice how the icon is shown with correct orientation but the mouse
cursor has landscape orientation.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724977

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer
Oops, I attached the wrong picture.  This one is correct.

** Attachment added: "20171019_140503.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+attachment/4976890/+files/20171019_140503.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724977

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer
I have attached a copy of a monitor.xml file I can use that will yield
this behavior.

** Attachment added: "monitors.xml"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+attachment/4976873/+files/monitors.xml-order_and_rotation_correct

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724977

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1724979] [NEW] system freeze when activating my 3rd display

2017-10-19 Thread Scott Palmer
Public bug reported:

On Windows I use all three displays without issue, but I can only seem
to activate any 2 of my 3 displays in Ubuntu.  The moment I activate the
3rd, the system freezes.

It may also be worth noting that due to this I have been disabling my
built-in laptop display and leaving my two larger desktop displays
active.  When I open my laptop the whole system freezes and has to be
power cycled.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:48:32 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724979

Title:
  system freeze when activating my 3rd display

Status in xorg package in Ubuntu:
  New

Bug description:
  On Windows I use all three displays without issue, but I can only seem
  to activate any 2 of my 3 displays in Ubuntu.  The moment I activate
  the 3rd, the system freezes.

  It may also be worth noting that due to this I have been disabling my
  built-in laptop display and leaving my two larger desktop displays
  active.  When I open my laptop the whole system freezes and has to be
  power cycled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:48:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 

[Desktop-packages] [Bug 1724977] [NEW] two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer
Public bug reported:

When my 2nd Asus (Ancor) display is in portrait mode and is set to be to
the left of my centered landscape display in extended mode, moving the
mouse to roughly the left 20% of my landscape display will show a mouse
cursor on my landcape display AND portrait display at the same time.
Oddly moving a window into this area only shows on the landscape
display.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:43:30 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724977

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: 

[Desktop-packages] [Bug 1724966] [NEW] Settings - Display - Primary Display selection does not allow selection of available entries

2017-10-19 Thread Scott Palmer
Public bug reported:

Settings - Display - Primary Displayoffers me a choice of 3 displays.
Clicking on any of the non checked displays does nothing.

NOTE: My other 2 displays are currently disabled and likely shouldn't be
showing up in this list.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:27:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724966

Title:
  Settings - Display - Primary Display selection does not allow
  selection of available entries

Status in xorg package in Ubuntu:
  New

Bug description:
  Settings - Display - Primary Displayoffers me a choice of 3 displays.
  Clicking on any of the non checked displays does nothing.

  NOTE: My other 2 displays are currently disabled and likely shouldn't
  be showing up in this list.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:27:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Desktop-packages] [Bug 1724955] [NEW] unable to drag monitors in Display Arrangement

2017-10-19 Thread Scott Palmer
Public bug reported:

I am unable to drag the displays in the Display Arrangement section.  I
have a dual monitor setup and they are in the reverse order.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:12:07 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724955

Title:
  unable to drag monitors in Display Arrangement

Status in xorg package in Ubuntu:
  New

Bug description:
  I am unable to drag the displays in the Display Arrangement section.
  I have a dual monitor setup and they are in the reverse order.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:12:07 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Desktop-packages] [Bug 1724926] [NEW] No button to launch nm-connection-editor for Advanced functionality like VLANs

2017-10-19 Thread Scott Palmer
Public bug reported:

Gnome removed the ability to add/remove VLANs.  When people ask /
complain about how this is to be accomplished, they are usually referred
to nm-connection-editor.

Can a Gnome developer please add an "Advanced Configuration" button that
launches nm-connection-editor?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 11:38:58 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.50.253 dev vlan757 proto static metric 400 
 169.254.0.0/16 dev vlan757 scope link metric 1000 
 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 
400
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
 VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508438283  Thu 19 Oct 2017 11:38:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
 Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Tags removed: wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1724926

Title:
  No button to launch nm-connection-editor for Advanced functionality
  like VLANs

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Gnome removed the ability to add/remove VLANs.  When people ask /
  complain about how this is to be accomplished, they are usually
  referred to nm-connection-editor.

  Can a Gnome developer please add an "Advanced Configuration" button
  that launches nm-connection-editor?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:38:58 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508438283  Thu 19 Oct 2017 11:38:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --

[Desktop-packages] [Bug 1724921] [NEW] VLANs get incorrectly listed under Bluetooth

2017-10-19 Thread Scott Palmer
Public bug reported:

I expected them to show up under Wired because the VLANs' associated
adapter is wired.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 11:25:17 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.50.253 dev vlan757 proto static metric 400 
 169.254.0.0/16 dev vlan757 scope link metric 1000 
 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 
400
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
 VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
 Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Attachment added: "Screenshot from 2017-10-19 11-18-44.png"
   
https://bugs.launchpad.net/bugs/1724921/+attachment/4976422/+files/Screenshot%20from%202017-10-19%2011-18-44.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1724921

Title:
  VLANs get incorrectly listed under Bluetooth

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I expected them to show up under Wired because the VLANs' associated
  adapter is wired.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:25:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled


[Desktop-packages] [Bug 1724923] [NEW] VLANs are not always listed in Settings - Network

2017-10-19 Thread Scott Palmer
Public bug reported:

Sometimes when I open Settings - Network I see my VLANs, sometimes I
don't.  I don't think changes made in nm-connection-editor are being
properly recognized by Gnome.

I use nm-connection-editor to add and configure VLANs.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 11:33:19 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.50.253 dev vlan757 proto static metric 400 
 169.254.0.0/16 dev vlan757 scope link metric 1000 
 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 
400
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
 VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437983  Thu 19 Oct 2017 11:33:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
 Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1724923

Title:
  VLANs are not always listed in Settings - Network

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Sometimes when I open Settings - Network I see my VLANs, sometimes I
  don't.  I don't think changes made in nm-connection-editor are being
  properly recognized by Gnome.

  I use nm-connection-editor to add and configure VLANs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:33:19 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437983  Thu 19 Oct 2017 11:33:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI 

[Desktop-packages] [Bug 1724442] [NEW] Search feature returns seemingly unrelated results

2017-10-17 Thread Scott Palmer
Public bug reported:

This bug should actually be linked to ubuntu software, not gnome
software.


Search for "libre"

1. yacas 
2. wormhole
.
.
.

I can't even find "libre" in the package name, nor the description of
the first few pages of results.

Way down on the list is "libreoffice" but even it isn't grouped with
"LibreOffice Writer", "LibreOffice Calc" which are several pages lower.

What is the order of results?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-software 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:10:29 2017
InstallationDate: Installed on 2017-10-03 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.1-0ubuntu1
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1724442

Title:
  Search feature returns seemingly unrelated results

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This bug should actually be linked to ubuntu software, not gnome
  software.

  
  Search for "libre"

  1. yacas 
  2. wormhole
  .
  .
  .

  I can't even find "libre" in the package name, nor the description of
  the first few pages of results.

  Way down on the list is "libreoffice" but even it isn't grouped with
  "LibreOffice Writer", "LibreOffice Calc" which are several pages
  lower.

  What is the order of results?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:10:29 2017
  InstallationDate: Installed on 2017-10-03 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724442/+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 1723824] [NEW] Unable to scroll down to all photos

2017-10-15 Thread Scott Palmer
Public bug reported:

Shotwell would not let my scroll down any further to select some photoss
on the bottom row.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: shotwell 0.26.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 17:54:26 2017
InstallationDate: Installed on 2017-10-03 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shotwell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

** Attachment added: "Notice the scrollbar is all the way down and there are 
still photos below"
   
https://bugs.launchpad.net/bugs/1723824/+attachment/4972338/+files/cannot_scroll_down.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1723824

Title:
  Unable to scroll down to all photos

Status in shotwell package in Ubuntu:
  New

Bug description:
  Shotwell would not let my scroll down any further to select some
  photoss on the bottom row.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:54:26 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723824/+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 1723815] [NEW] Unable to show files on MTP connection

2017-10-15 Thread Scott Palmer
Public bug reported:

Opening "Samsung_Android\Card\DCIM\Camera" folder with many images gets
stuck at "Loading..." and never shows anything.  I have waited 10
minutes.  There is no error and not a single icon shows.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 16:36:50 2017
InstallationDate: Installed on 2017-10-03 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1723815

Title:
  Unable to show files on MTP connection

Status in nautilus package in Ubuntu:
  New

Bug description:
  Opening "Samsung_Android\Card\DCIM\Camera" folder with many images
  gets stuck at "Loading..." and never shows anything.  I have waited 10
  minutes.  There is no error and not a single icon shows.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 16:36:50 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1723815/+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 1722987] [NEW] screen brightness control is backwards

2017-10-11 Thread Scott Palmer
Public bug reported:

Increase brightness key on my keyboard (func-f3) makes the screen more dim.
Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
The gnome-shell on-screen display of brightness is backwards also.

I see on google search results that this was a problem with older
kernels. I guess the problem is back / possible regression.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 20:52:44 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
InstallationDate: Installed on 2017-10-08 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=3db6d4f1-3d95-4b8c-93d1-ab9465947670 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.15
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.37
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd11/11/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr096F100800405F00010420180:rvnHewlett-Packard:rn2209:rvr57.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.version: 096F100800405F00010420180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1722987

Title:
  screen brightness control is backwards

Status in xorg package in Ubuntu:
  New

Bug description:
  Increase brightness key on my keyboard (func-f3) makes the screen more dim.
  Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
  The gnome-shell on-screen display of brightness is backwards also.

  I see on google search results that this was a problem with older
  kernels. I guess the problem is back / possible regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 20:52:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
  InstallationDate: Installed on 2017-10-08 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 

[Desktop-packages] [Bug 1711037] Re: Screen intermittently flickers

2017-10-08 Thread Scott Palmer
These seems to be related to what is in monitors.xml.
When I deleted that file the flickering was gone but my monitors were out of 
order and alignment.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1711037

Title:
  Screen intermittently flickers

Status in xorg package in Ubuntu:
  New

Bug description:
  Using both my nvidia and radeon cards my 2560x1600 display flickers.
  The screen is fine in Windows.  This only seems to happen when I run
  the open source driver.

  Additionally, if I drop that screen to a lower 16:10 resolution like
  1920x1200 it goes black.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Aug 15 22:32:41 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
   bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
  InstallationDate: Installed on 2017-08-07 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 14 07:40:51 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1711037/+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 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-08 Thread Scott Palmer
Some updates must have come in, in the last few days that fixed this.
Close the bug.

-- 
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/1721160

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+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 1721674] [NEW] Scan All Pages From Feeder action scans the first page and feeds the rest without scanning

2017-10-05 Thread Scott Palmer
Public bug reported:

"Scan All Pages From Feeder" action scans the first page and feeds the
rest without scanning them.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: simple-scan 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  5 18:31:19 2017
InstallationDate: Installed on 2017-10-03 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a393d6b9-0886-4a0a-b2be-5111bfcf9ada ro quiet splash
SimpleScanLog:
 
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1721674

Title:
  Scan All Pages From Feeder action scans the first page and feeds the
  rest without scanning

Status in simple-scan package in Ubuntu:
  New

Bug description:
  "Scan All Pages From Feeder" action scans the first page and feeds the
  rest without scanning them.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: simple-scan 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  5 18:31:19 2017
  InstallationDate: Installed on 2017-10-03 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a393d6b9-0886-4a0a-b2be-5111bfcf9ada ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1721674/+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 1721430] Re: connection missing in gui when created using nmcli

2017-10-04 Thread Scott Palmer
** Attachment added: "Screenshot from 2017-10-04 19-45-09.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+attachment/4962439/+files/Screenshot%20from%202017-10-04%2019-45-09.png

** Description changed:

- When I create a new connection using `sudo nmcli` the entry is missing
- in Network settings but exists in the popup.  Also the name used to
- create the connection is not displayed.  (see screenshots attached)
+ When I create a new connection using nmcli the entry is missing in
+ Network settings but exists in the popup.  Also the name used to create
+ the connection is not displayed.  (see screenshots attached)
  
  The commands used to create the connection are basically:
  
- VPN_NAME="Sample VPN"
- VPN_REMOTE="somewhere.inter.net"
- VPN_USERNAME="somebody"
- VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
- nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type 
openvpn 
- nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
- nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
- nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
- nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
- nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
- nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes
+ VPN_NAME="Sample VPN"
+ VPN_REMOTE="somewhere.inter.net"
+ VPN_USERNAME="somebody"
+ VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
+ nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
+ nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
+ nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
+ nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
+ nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
+ nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
+ nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 19:40:41 2017
  InstallationDate: Installed on 2017-10-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1721430

Title:
  connection missing in gui when created using nmcli

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  When I create a new connection using nmcli the entry is missing in
  Network settings but exists in the popup.  Also the name used to
  create the connection is not displayed.  (see screenshots attached)

  The commands used to create the connection are basically:

  VPN_NAME="Sample VPN"
  VPN_REMOTE="somewhere.inter.net"
  VPN_USERNAME="somebody"
  VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
  nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
  nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
  nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
  nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 19:40:41 2017
  InstallationDate: Installed on 2017-10-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1721430] [NEW] connection missing in gui when created using nmcli

2017-10-04 Thread Scott Palmer
Public bug reported:

When I create a new connection using nmcli the entry is missing in
Network settings but exists in the popup.  Also the name used to create
the connection is not displayed.  (see screenshots attached)

The commands used to create the connection are basically:

VPN_NAME="Sample VPN"
VPN_REMOTE="somewhere.inter.net"
VPN_USERNAME="somebody"
VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca = 
$VPN_CA, password-flags = 1, connection-type = password, remote = $VPN_REMOTE, 
username = $VPN_USERNAME"
nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  4 19:40:41 2017
InstallationDate: Installed on 2017-10-03 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

** Attachment added: "Screenshot from 2017-10-04 19-43-35.png"
   
https://bugs.launchpad.net/bugs/1721430/+attachment/4962434/+files/Screenshot%20from%202017-10-04%2019-43-35.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1721430

Title:
  connection missing in gui when created using nmcli

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  When I create a new connection using nmcli the entry is missing in
  Network settings but exists in the popup.  Also the name used to
  create the connection is not displayed.  (see screenshots attached)

  The commands used to create the connection are basically:

  VPN_NAME="Sample VPN"
  VPN_REMOTE="somewhere.inter.net"
  VPN_USERNAME="somebody"
  VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
  nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
  nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
  nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
  nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 19:40:41 2017
  InstallationDate: Installed on 2017-10-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+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 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-03 Thread Scott Palmer
** Attachment added: "Screenshot from 2017-10-03 17-18-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+attachment/4961790/+files/Screenshot%20from%202017-10-03%2017-18-29.png

-- 
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/1721160

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+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 1721160] [NEW] [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-03 Thread Scott Palmer
Public bug reported:

If I unplug the green plug to my speakers after my computer finishes
booting and then immediately plug it back in again, sound works
correctly.

Prior to the unplug / replug trick the Line-out is missing from Sound settings.
After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

I will attach screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1272 F pulseaudio
 /dev/snd/controlC1:  scott  1272 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  3 17:21:49 2017
InstallationDate: Installed on 2017-10-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 926 F pulseaudio
  scott  1272 F pulseaudio
 /dev/snd/controlC1:  gdm 926 F pulseaudio
  scott  1272 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
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/1721160

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-03 Thread Scott Palmer
** Attachment added: "Screenshot from 2017-10-03 17-18-43.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+attachment/4961791/+files/Screenshot%20from%202017-10-03%2017-18-43.png

-- 
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/1721160

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+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 1711037] [NEW] Screen intermittently flickers

2017-08-15 Thread Scott Palmer
Public bug reported:

Using both my nvidia and radeon cards my 2560x1600 display flickers.
The screen is fine in Windows.  This only seems to happen when I run the
open source driver.

Additionally, if I drop that screen to a lower 16:10 resolution like
1920x1200 it goes black.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Aug 15 22:32:41 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
 bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
 nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
 nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
InstallationDate: Installed on 2017-08-07 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 14 07:40:51 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful reproducible ubuntu wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1711037

Title:
  Screen intermittently flickers

Status in xorg package in Ubuntu:
  New

Bug description:
  Using both my nvidia and radeon cards my 2560x1600 display flickers.
  The screen is fine in Windows.  This only seems to happen when I run
  the open source driver.

  Additionally, if I drop that screen to a lower 16:10 resolution like
  1920x1200 it goes black.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Aug 15 22:32:41 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
   bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
  InstallationDate: Installed on 2017-08-07 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: 

[Desktop-packages] [Bug 1710754] [NEW] [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-08-14 Thread Scott Palmer
Public bug reported:

When I start my computer I have no sound.  If I unplug my line out and
plug it in again sound works fine. In Windows 10 this unplug and replug
is not required (the jack is fine).

Running:
 $ amixer -c0 contents
so I can compare the non working state with the working state, the following 
differences exist:

Non Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=off
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on

Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=on
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1154 F pulseaudio
 /dev/snd/controlC1:  scott  1154 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Aug 14 19:05:12 2017
InstallationDate: Installed on 2017-08-07 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1154 F pulseaudio
 /dev/snd/controlC1:  scott  1154 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test 

[Desktop-packages] [Bug 1710752] [NEW] Intel HDA Audio doesn't work

2017-08-14 Thread Scott Palmer
Public bug reported:

I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
 Built-in Audio and there is no option to select anything else.  If I unplug my 
line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

Running:
 $ amixer -c0 contents
so I can compare the non working state with the working state, the following 
differences exist:

Non Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=off
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on

Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=on
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710752

Title:
  Intel HDA Audio doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
   Built-in Audio and there is no option to select anything else.  If I unplug 
my line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710752/+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 1709159] Re: Mouse cursor stuck on primary monitor on dual monitor system

2017-08-14 Thread Scott Palmer
I just changed my video card to a Radeon RX 560 using the open source
driver and the same problem exists.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1709159

Title:
  Mouse cursor stuck on primary monitor on dual monitor system

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS 
450.
  I have a dual monitor setup with my primary on the right.
  My primary display is slightly higher than my secondary on the left as 
configured in Displays.

  When I play a video full screen on the left monitor and then bring my
  mouse cursor back to my primary on the right, the mouse cursor often
  refuses to go back onto the left monitor (as if I only had one
  monitor).  Once I switch to overview mode, it will let the mouse go
  back over to the left monitor again.  The mouse will continue working
  across both monitors now.

  I go back into the video and toggle out of full screen and then back
  to full screen and bring my mouse back over to the right monitor.  It
  is now stuck on the right monitor again.

  So..  activation of full screen on the left secondary monitor and then
  moving the mouse cursor onto the right primary is enough to reproduce
  the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  7 12:02:43 2017
  InstallationDate: Installed on 2017-08-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159/+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 1628153] Re: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts

2017-08-13 Thread Scott Palmer
I am getting similar behaviour on 17.10.  If I unplug my line out and
plug it in again it works fine.  In Windows 10 this unplug and replug is
not required (the jack is fine).


Running:
 $ amixer -c0 contents
so I can compare the non working state with the working state, the following 
differences exist:


Non Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=off
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on


Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=on
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1628153

Title:
  [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most
  restarts

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On the vast majority of restarts of Ubuntu 16.04 I get no internal
  sound at all.

  There are no reported issues in system settings on the only sound card
  I have. The volume is not muted.

  On an estimated 1 in 10 restart, the sound works, and both the test
  sounds get played and other applications work fine.

  There is no reported errors or messages on the restarts when the sound
  has failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 27 15:56:02 2016
  InstallationDate: Installed on 2015-10-29 (334 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1628153/+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 1709159] [NEW] Mouse cursor stuck on primary monitor on dual monitor system

2017-08-07 Thread Scott Palmer
Public bug reported:

I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS 
450.
I have a dual monitor setup with my primary on the right.
My primary display is slightly higher than my secondary on the left as 
configured in Displays.

When I play a video full screen on the left monitor and then bring my
mouse cursor back to my primary on the right, the mouse cursor often
refuses to go back onto the left monitor (as if I only had one monitor).
Once I switch to overview mode, it will let the mouse go back over to
the left monitor again.  The mouse will continue working across both
monitors now.

I go back into the video and toggle out of full screen and then back to
full screen and bring my mouse back over to the right monitor.  It is
now stuck on the right monitor again.

So..  activation of full screen on the left secondary monitor and then
moving the mouse cursor onto the right primary is enough to reproduce
the bug.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session-wayland (not installed)
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug  7 12:02:43 2017
InstallationDate: Installed on 2017-08-07 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1709159

Title:
  Mouse cursor stuck on primary monitor on dual monitor system

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS 
450.
  I have a dual monitor setup with my primary on the right.
  My primary display is slightly higher than my secondary on the left as 
configured in Displays.

  When I play a video full screen on the left monitor and then bring my
  mouse cursor back to my primary on the right, the mouse cursor often
  refuses to go back onto the left monitor (as if I only had one
  monitor).  Once I switch to overview mode, it will let the mouse go
  back over to the left monitor again.  The mouse will continue working
  across both monitors now.

  I go back into the video and toggle out of full screen and then back
  to full screen and bring my mouse back over to the right monitor.  It
  is now stuck on the right monitor again.

  So..  activation of full screen on the left secondary monitor and then
  moving the mouse cursor onto the right primary is enough to reproduce
  the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  7 12:02:43 2017
  InstallationDate: Installed on 2017-08-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159/+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