from:"Craig"

Don't forget to 'sudo apt update' after making those changes.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Just uncomment the deb-src lines in /etc/apt/sources.list.

For example, replace:

# deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main
restricted

With:

deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

The above worked for (k)ubuntu 18.10.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

For those following https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel, I
had to do some extra things to get kernel compilation working.

The workaround steps are described here:
https://askubuntu.com/questions/1085411/unable-to-follow-kernel-
buildyourownkernel/1099988. Substitute the kernel version relevant to
you wherever you see "4.18.0"...

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2018-11-29 Thread Craig Gilding

Also having the same problem. Compiling from git as per instructions
didn't solve for me either. Not sure what I've done wrong

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-11-23 Thread craig jackson

Re above comment, the UX533 also has the ALC294. I should have made this
clear in that comment.

Thanks,
Craig

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Hi Pawel,

You may be right, but I think the common thread in all the laptops
exhibiting this problem is the ALC294. Does the power save trick
mentioned in my comment work for you at all?

Cheers,
Craig

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1742852

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485, as I'm seeing the same symptoms, with the same
temporary improvement enabling the power save as described above.

Asus UX533 Kubuntu 18.10 (4.18.0-11-generic) fresh install (dual boot
with Windows 10).

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Interestingly, if I put the sound device into power save mode and wait a
few seconds before playing a sound, I can actually hear it perffectly
clearly, but after repeating the playing of the sound a few times, it
distorts then disappears:

  sudo -i
  echo 10 >/sys/module/snd_hda_intel/parameters/power_save
  sleep 10
  aplay /usr/share/sounds/alsa/Front_Center.wav

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-21 Thread craig jackson

Same on Asus Zenbook UX533 with Realtek ALC294. No sound on Kubuntu
18.10 (4.18.0-11-generic) -  speakers or headphones. Dual boot with
Windows 10. Windows 10 sounds work fine.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1316648] Re: gedit hangs on start

2018-11-20 Thread Craig Blake

Sorry I am no longer using Ubuntu so I cannot say if the bug still
exists.

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

Title:
  gedit hangs on start

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  When trying to start gedit on Ubuntu 14.04 it hangs for a long time
  (longer than 5 minutes) without opening a window.  Sometimes when I
  come back to the laptop 30 minutes or more later it has finally opened
  a gedit window.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  6 11:13:44 2014
  InstallationDate: Installed on 2014-03-09 (57 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140309)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1401599] Re: Aw Snap Pinterest Chromium 39 on Trusty 14.10 when I sign into Pinterest

2018-07-18 Thread Craig Keefner

thanks. Yes, that was a blast from the past.  I use 16.04 LTS now and
haven't used Chromium in awhile.


Craig Allen Keefner
720.324.1837 m
www.linkedin.com/in/kiosk
http://kioskindustry.org

On Wed, Jul 18, 2018 at 1:41 PM, Paul White <1401...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. We are sorry that we do not always have the capacity to
> look at all reported bugs in a timely manner. You reported this bug some
> time ago and there have been many changes in Ubuntu since that time.
> Your problem may have been fixed with some of the updates.
>
> It would help us a lot if you could test on a currently supported Ubuntu
> version. When you test it and it is still an issue, kindly upload the
> updated logs by running only once in a terminal:
>
> apport-collect 1401599
>
> and add any additional information that you think relevant.
> Alternatively, please confirm that this is no longer a problem and that
> we can close the report. If we do not hear from you the bug report will
> close itself in approximately two months time.
>
> Thank you again for helping make Ubuntu better.
>
> Paul White
> [Ubuntu Bug Squad]
>
>
> ** Changed in: chromium-browser (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1401599
>
> Title:
>   Aw Snap Pinterest Chromium 39 on Trusty 14.10 when I sign into
>   Pinterest
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I was having issues with Chromium and Chrome on Trusty beginning a few
>   weeks ago especially with can't load profile, users, and other
>   specific site issues like Pinterest.  I tried disabling all extensions
>   but no change.
>
>   Today I renamed my profiles for both Chromium and Chrome and set up
>   new profiles.  I was able to call up and then sign into Pinterest with
>   Chrome. When I tried it with Chromium I was able to get to Pinterest
>   but as soon as I tried to login as the specific user on Pinterest, I
>   got the Aw Snap again.
>
>   For whatever reason Chrome and for that matter Google in general has
>   seemed to have more glitches than usual the last few weeks. Even on my
>   Nexus 7 tablet that got upgraded to latest Android suddenly now can go
>   bonkers.
>
>   I have many of same issues on my Win7 Pro machine to that runs side by
>   side.
>
>   Craig
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1401599/+
> subscriptions
>

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

Title:
  Aw Snap Pinterest Chromium 39 on Trusty 14.10 when I sign into
  Pinterest

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I was having issues with Chromium and Chrome on Trusty beginning a few
  weeks ago especially with can't load profile, users, and other
  specific site issues like Pinterest.  I tried disabling all extensions
  but no change.

  Today I renamed my profiles for both Chromium and Chrome and set up
  new profiles.  I was able to call up and then sign into Pinterest with
  Chrome. When I tried it with Chromium I was able to get to Pinterest
  but as soon as I tried to login as the specific user on Pinterest, I
  got the Aw Snap again.

  For whatever reason Chrome and for that matter Google in general has
  seemed to have more glitches than usual the last few weeks. Even on my
  Nexus 7 tablet that got upgraded to latest Android suddenly now can go
  bonkers.

  I have many of same issues on my Win7 Pro machine to that runs side by
  side.

  Craig

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1401599/+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 1613117] Re: Download-complete animated image stays on screen after showing

2018-06-29 Thread Craig

I am not seeing this issue anymore.  This bug can be closed.

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

Title:
  Download-complete animated image stays on screen after showing

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I download something in Firefox and it completes, the blue arrow
  animated image shows and stays over the toolbar indefinitely.  As
  other things change (causing parts to rerender) in the affected area,
  that portion of the image goes away.

  This occurred in FF 47 and now 48 too.

  Image attached showing what I'm talking about.  Color is funny in
  screenshot due to misconfigured screenshot tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 48.0+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clandry3969 F pulseaudio
   /dev/snd/controlC1:  clandry3969 F pulseaudio
  BuildID: 20160728203720
  Channel: Unavailable
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Aug 14 14:57:36 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-08-02 (378 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 10.10.10.254 dev wlan0  proto static  metric 600 
   10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.10.10.219  metric 
600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Profiles: Profile0 (Default) - LastVersion=48.0/20160728203720 (In use)
  RelatedPackageVersions: rhythmbox-mozilla 3.3-1ubuntu7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2016-06-12 (63 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1613117/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-04-11 Thread Craig Carnell

@RevAngel do you have a link to this please?

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-02-22 Thread Craig Carnell

It's set to private at request

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-02-21 Thread Craig Carnell

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1750773

However, the uploading of attachments appears to be broken.

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1750773] [NEW] Session terminates after logging back in when screen saver was on

2018-02-21 Thread Craig Carnell

Private bug reported:

Using wayland on Ubuntu 17.10. When I leave my machine to idle, the
screen saver activates as you would expect and my session is locked.

When I unlock the computer as normal, all my windows will have closed
and running applications stopped.

My System is a Dell 9560 with Nvidia 1050 and Intel Graphics. Using
nouveau

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


** Tags: xwayland

** Information type changed from Public to Private

** Summary changed:

- Session terminates when screen saver is on
+ Session terminates after logging back when screen saver was on

** Summary changed:

- Session terminates after logging back when screen saver was on
+ Session terminates after logging back in when screen saver was on

** Description changed:

  Using wayland on Ubuntu 17.10. When I leave my machine to idle, the
  screen saver activates as you would expect and my session is locked.
  
  When I unlock the computer as normal, all my windows will have closed
  and running applications stopped.
+ 
+ My System is a Dell 9560 with Nvidia 1050 and Intel Graphics. Using
+ nouveau

** Tags added: xwayland

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

Title:
  Session terminates after logging back in when screen saver was on

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using wayland on Ubuntu 17.10. When I leave my machine to idle, the
  screen saver activates as you would expect and my session is locked.

  When I unlock the computer as normal, all my windows will have closed
  and running applications stopped.

  My System is a Dell 9560 with Nvidia 1050 and Intel Graphics. Using
  nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1750773/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-02-08 Thread Craig Carnell

Whenever I try to log an issue with ubuntu-bug
/var/crash/_usr_bin_Xwayland.1000.crash for this issue my machine locks
up

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-02-06 Thread Craig Carnell

Are there any updates on this issue? This issue is causing some major
problems for me - as soon as I go away from my computer for more than a
few minutes and re login to the computer all my windows have closed and
I have to re-open everything.

My system is a Dell 9560 with Intel & Nvidia 1050 Graphics - Ubuntu
17.10, Wayland Gnome.

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1731094] [NEW] Trouble Switching between GPUs on a Carrizo laptop with an integrated and discrete graphics card.

2017-11-08 Thread Craig Stein

Public bug reported:


Yesterday I decided to learn how to switch between my low power usage
GPU and my discrete GPU in my laptop using Prime. I started by running
this command: xrandr --listproviders.

I got the following result:

Providers: number : 2 Provider 0: id: 0x75 cap: 0x9, Source Output,
Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:AMD Radeon
R6 Graphics @ pci::00:01.0 Provider 1: id: 0x3f cap: 0x4, Source
Offload crtcs: 0 outputs: 0 associated providers: 1 name:AMD Radeon (TM)
R7 M360 @ pci::03:00.0

I then ran this command to switch to my discrete GPU: xrandr
--setprovideroffloadsink 1 0.

This resulted in the following result to my GPU with this command:
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

OpenGL renderer string: AMD Radeon (TM) R7 M360 (AMD ICELAND / DRM
3.18.0 / 4.13.8-041308-generic, LLVM 5.0.0)

Now however when i attempt to switch back to using my low powered Radeon
R6 with this command I get: xrandr --setprovideroffloadsink 0 1

X Error of failed request: BadValue (integer parameter out of range
for operation) Major opcode of failed request: 140 (RANDR) Minor opcode
of failed request: 34 (RRSetProviderOffloadSink) Value in failed
request: 0x75 Serial number of failed request: 16 Current serial number
in output stream: 17

I should mention I am logging into the Gnome session using Xorg on
Ubuntu 17.10. I would love to be able to switch back to my R6 so any
help is much appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
Uname: Linux 4.13.8-041308-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Nov  8 19:53:41 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.1.30, 4.13.8-041308-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Carrizo [1025:095e]
InstallationDate: Installed on 2017-10-20 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.8-041308-generic 
root=UUID=17c9ce89-7e9f-4910-965e-cbd862c45839 ro modprobe.blacklist=radeon 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Nami_CZ
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd09/15/2015:svnAcer:pn:pvrV1.10:rvnAcer:rnNami_CZ:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: CZ
dmi.product.version: V1.10
dmi.sys.vendor: Acer
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 xrandr

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

Title:
  Trouble Switching between GPUs on a Carrizo laptop with an integrated
  and discrete graphics card.

Status in xorg package in Ubuntu:
  New

Bug description:

  Yesterday I decided to learn how to switch between my low power usage
  GPU and my discrete GPU in my laptop using Prime. I started by running
  this command: xrandr --listproviders.

  I got the following result:

  Providers: number : 2 Provider 0: id: 0x75 cap: 0x9, Source
  Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 1
  name:AMD Radeon R6 Graphics @ pci::00:01.0 Provider 1: id: 0x3f
  cap: 0x4, Source Offload crtcs: 0 outputs: 0 associated providers: 1
  name:AMD Radeon (TM) R7 M360 @ pci::03:00.0

  I then ran this command to switch to my discrete GPU: xrandr
  --setprovideroffloadsink 1 0.

  This resulted in the following result to my GPU with this command:
  DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

  OpenGL renderer string: AMD Radeon (TM) R7 M360 (AMD ICELAND / DRM
  3.18.0 / 4.13.8-041308-generic, LLVM 5.0.0)

  Now however when i attempt to switch

[Desktop-packages] [Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subpr

2017-10-21 Thread Craig Stein

yes

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

Title:
  gnome-shell crashed with SIGTRAP in object_instance_finalize from
  js::Class::doFinalize ["Finalizing proxy for an object that's
  scheduled to be unrooted: Gio.Subprocess\n"]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/bcc0785597c2485f446db82f8dfa08eb7dd972a5

  ---

  Logged in with one new user, switched to login under another account.
  Was logged in for a few moments then got kicked out - session crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-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: GNOME-Greeter:GNOME
  Date: Mon Oct  2 10:39:27 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-08-02 (60 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720768/+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 1281250] Re: VNC accessible from non-linux machines only with encryption disabled

2017-07-17 Thread Craig Hansen

I've been trying to turn off encryption on vino-server in order to use
one of many of the VNC clients that don't deal with TLS encryption. In
the past, I've been able to start the vino-server by running by using
"DISPLAY=:0 /usr/lib/vino/vino-server --sm-disable >& ~/.vino.log &"
from a shell invoked with "ssh -X remotehostname".

The usual advice to turn off encryption and restart vino has reached yet
another wrinkle: Upon attempting to restart vino-server (because the
gsettings changes don't get re-read by vino-server except upon restart,
already a problem), we now get the following messages (1) "(vino-
server:21493): EggSMClient-CRITICAL **: egg_sm_client_set_mode:
assertion 'global_client == NULL || global_client_mode ==
EGG_SM_CLIENT_MODE_DISABLED' failed" and (2) "** Message: The desktop
sharing service is already running, exiting.", even after a "pkill
vino".

Message (1) I haven't tracked down, though another bug report:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1082182  mentions
essentially the same problem, but there's no resolution.

For message (2), looking at the source code, this message comes from 
name_lost(), which is called from:
g_bus_own_name (G_BUS_TYPE_SESSION, "org.gnome.Vino",
  G_BUS_NAME_OWNER_FLAGS_NONE,
  bus_acquired, name_acquired, name_lost,
  , NULL);

Now, looking at the doc for g_bus_own_name(), from
https://developer.gnome.org/gio/stable/gio-Owning-Bus-Names.html

There are two ways the name_lost handler might be invoked: "You are guaranteed 
that one of the name_acquired_handler and name_lost_handler callbacks will be 
invoked after calling this function - there are three possible cases:
name_lost_handler with a NULL connection (if a connection to the bus can't be 
made).
bus_acquired_handler then name_lost_handler (if the name can't be obtained)
bus_acquired_handler then name_acquired_handler (if the name was obtained)."

Unfortunately the writer of this name_lost code assumed that it must be
because of the second case, and completely ignored the first case (if a
connection to the bus can't be made), making it hard to distinguish
what's going wrong here. I know that when, for example, starting emacs
from the command line over an "ssh -X" connection, I get a bunch of
error messages about having trouble connecting to dbus, but it
eventually starts up. Is this something similar, except that gives up
immediately?

I've been unable to figure out how to restart the vino-server in these
cases, other than to reboot the machine. Is there a any better way to
restart the vino-server?

A final thought - is there any possibility of (a) turning off require
encryption by default or (b) having vino-preferences set up to click off
the option of requiring TLS encryption or (c) having some normal way to
restart the vino-server (such as "sudo service vino restart" or
something) or (d) having vino-server re-read the settings before opening
a new connection or even (e) having a man page for vino-server? It's my
understanding that this "require encryption" option only protects the
initial handling of the password, and that all the rest of the session
keystrokes and display data aren't encrypted anyway, so all these
problems are the result of insisting on a change that doesn't really
protect users. It's more effective to form the connection within an ssh
session that would protect all the contents, password, keystroke, and
display data.

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

Title:
  VNC accessible from non-linux machines only with encryption disabled

Status in TigerVNC:
  New
Status in vino:
  Confirmed
Status in vino package in Ubuntu:
  Triaged
Status in vino source package in Trusty:
  Triaged
Status in vino package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the

[Desktop-packages] [Bug 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause

2017-06-12 Thread Craig

I too needed to re-enable graphical login after having disabled it.

I can confirm adding:

[Install]
Alias=display-manager.service

to my /lib/systemd/system/lightdm.service file.

Allowed me to re-enable lightdm to start on boot (by running "sudo
systemctl enable lightdm"), previous to this I would end up booting to a
black screen with a flashing cursor in the top left.  Ctrl+Alt+F1 (for
VT1) etc... would lead me to the login prompts, Ctrl+Alt+F7 leads me
back to the screen with the flashing cursor (VT7).

So for me Ubuntu was expecting a graphical interface to be running and
had me on VT7 at boot.  Logging in from one of the other terminals
showed lightdm to be stopped ("systemctl status lightdm").  Prior to the
fix above I would have to manually start lightdm by logging in and
running "sudo systemctl start lightdm"

I hope the above helps anyone googling the issue as it took me a couple
of hours to track down why it wasn't starting when I thought it was re-
enabled.

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

Title:
  /lib/systemd/system/lightdm.service file has no [Install] clause

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This concerns lightdm 1.18.1-0ubuntu1 in Xenial.

  The /lib/systemd/system/lightdm.service file lacks an [Install]
  clause. Meaning, that if you do

  # systemctl disable display-manager

  to prevent LightDM from starting, running

  # systemctl enable lightdm

  does not restore the /etc/systemd/system/display-manager.service
  symlink, and thus does not re-enable LightDM to run at the next boot
  as intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1584575/+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 1688739] [NEW] package libxml++2.6-2v5:amd64 2.40.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2017-05-06 Thread Craig Westwood

Public bug reported:

Will not install. Crashes half way through.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxml++2.6-2v5:amd64 2.40.1-1
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat May  6 15:24:42 2017
DuplicateSignature:
 package:libxml++2.6-2v5:amd64:2.40.1-1
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package libxml++2.6-2v5:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-01 (5 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libxml++2.6
Title: package libxml++2.6-2v5:amd64 2.40.1-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libxml++2.6 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
   package libxml++2.6-2v5:amd64 2.40.1-1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libxml++2.6 package in Ubuntu:
  New

Bug description:
  Will not install. Crashes half way through.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxml++2.6-2v5:amd64 2.40.1-1
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat May  6 15:24:42 2017
  DuplicateSignature:
   package:libxml++2.6-2v5:amd64:2.40.1-1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libxml++2.6-2v5:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-01 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libxml++2.6
  Title: package libxml++2.6-2v5:amd64 2.40.1-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml++2.6/+bug/1688739/+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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-05-03 Thread Craig Carnell

I have the same issue:

Dell XPS 15 9560
Ubuntu 17.04
4.10.0-20-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/1575078

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1661891] [NEW] Access to IPv4-only subdomain via IPv6

2017-02-04 Thread Craig McQueen

Public bug reported:

I access the following URL, which is done via IPv6 and returns my IPv6
address:

https://craig.mcqueen.id.au/ip.php

Then I access:

https://ipv4.craig.mcqueen.id.au/ip.php

That sub-domain has only a DNS A record, which should force it to be an
IPv4 access. But, somehow Firefox manages to access it via IPv6 and
return my IPv6 address again.

I think Firefox should access the second URL via IPv4.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 51.0.1+build2-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  craig  1936 F pulseaudio
BuildID: 20170125172221
Channel: Unavailable
CurrentDesktop: Unity
Date: Sun Feb  5 09:42:30 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2015-10-08 (485 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 192.168.178.1 dev eth0  proto static  metric 100 
 192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.33  
metric 100
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-a5d28002-f6a2-4e09-9e15-4cc312161226
Plugins:
 Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
 Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
 iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
 prefs.js
 [Profile]/extensions/easyc...@smokyink.com/defaults/preferences/defaultPrefs.js
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=51.0.1/20170125172221 (In use)
RelatedPackageVersions:
 google-talkplugin 5.41.3.0-1
 rhythmbox-mozilla 3.3-1ubuntu7
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-a5d28002-f6a2-4e09-9e15-4cc312161226
 bp-c84c5629-e2eb-4027-8054-bb86b2160724
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-06-23 (226 days ago)
dmi.bios.date: 11/27/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.90
dmi.board.asset.tag: 00
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.90:bd11/27/2008:svnTOSHIBA:pnTECRAP10:pvrPTSB3A-05R001:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA P10
dmi.product.version: PTSB3A-05R001
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug xenial

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

Title:
  Access to IPv4-only subdomain via IPv6

Status in firefox package in Ubuntu:
  New

Bug description:
  I access the following URL, which is done via IPv6 and returns my IPv6
  address:

  https://craig.mcqueen.id.au/ip.php

  Then I access:

  https://ipv4.craig.mcqueen.id.au/ip.php

  That sub-domain has only a DNS A record, which should force it to be
  an IPv4 access. But, somehow Firefox manages to access it via IPv6 and
  return my IPv6 address again.

  I think Firefox should access the second URL via IPv4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 51.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  craig  1936 F pulseaudio
  BuildID: 20170125172221
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Feb  5 09:42:30 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-10-08 (485 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.178.1 dev eth0  proto static  metric 100 
   192.168.178.

[Desktop-packages] [Bug 1661870] [NEW] package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-02-04 Thread Wendell Craig

Public bug reported:

Ubuntu 16.04.

Attempting install of Epson printer driver;

which seems to require lsb.

tracking down the problems.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: install-info 6.1.0.dfsg.1-5
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sat Feb  4 12:49:13 2017
DpkgHistoryLog:
 Start-Date: 2017-02-04  12:49:13
 Commandline: apt-get -f install
 Requested-By: win (1000)
 Install: gstreamer1.0-plugins-base-apps:amd64 (1.8.3-1ubuntu0.1, automatic), 
gstreamer1.0-tools:amd64 (1.8.3-1~ubuntu0.1, automatic), alien:amd64 (8.95, 
automatic), dh-strip-nondeterminism:amd64 (0.015-1, automatic), lsb:amd64 
(9.20160110ubuntu0.2, automatic), build-essential:amd64 (12.1ubuntu2, 
automatic), pkg-config:amd64 (0.29.1-0ubuntu1, automatic), debhelper:amd64 
(9.20160115ubuntu3, automatic), lsb-printing:amd64 (9.20160110ubuntu0.2, 
automatic), lsb-core:amd64 (9.20160110ubuntu0.2, automatic), dpkg-dev:amd64 
(1.18.4ubuntu1.1, automatic)
 Upgrade: libgstreamer1.0-0:amd64 (1.8.2-1~ubuntu1, 1.8.3-1~ubuntu0.1)
DpkgTerminalLog:
 Setting up install-info (6.1.0.dfsg.1-5) ...
 Not a directory: PRINTER=EPSON_WF-3620_Series.
 dpkg: error processing package install-info (--configure):
  subprocess installed post-installation script returned error exit status 1
DuplicateSignature:
 package:install-info:6.1.0.dfsg.1-5
 Setting up install-info (6.1.0.dfsg.1-5) ...
 Not a directory: PRINTER=EPSON_WF-3620_Series.
 dpkg: error processing package install-info (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-08 (58 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: texinfo
Title: package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package install-info 6.1.0.dfsg.1-5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in texinfo package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.

  Attempting install of Epson printer driver;

  which seems to require lsb.

  tracking down the problems.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: install-info 6.1.0.dfsg.1-5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Feb  4 12:49:13 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-04  12:49:13
   Commandline: apt-get -f install
   Requested-By: win (1000)
   Install: gstreamer1.0-plugins-base-apps:amd64 (1.8.3-1ubuntu0.1, automatic), 
gstreamer1.0-tools:amd64 (1.8.3-1~ubuntu0.1, automatic), alien:amd64 (8.95, 
automatic), dh-strip-nondeterminism:amd64 (0.015-1, automatic), lsb:amd64 
(9.20160110ubuntu0.2, automatic), build-essential:amd64 (12.1ubuntu2, 
automatic), pkg-config:amd64 (0.29.1-0ubuntu1, automatic), debhelper:amd64 
(9.20160115ubuntu3, automatic), lsb-printing:amd64 (9.20160110ubuntu0.2, 
automatic), lsb-core:amd64 (9.20160110ubuntu0.2, automatic), dpkg-dev:amd64 
(1.18.4ubuntu1.1, automatic)
   Upgrade: libgstreamer1.0-0:amd64 (1.8.2-1~ubuntu1, 1.8.3-1~ubuntu0.1)
  DpkgTerminalLog:
   Setting up install-info (6.1.0.dfsg.1-5) ...
   Not a directory: PRINTER=EPSON_WF-3620_Series.
   dpkg: error processing package install-info (--configure):
subprocess installed post-installation script returned error exit status 1
  DuplicateSignature:
   package:install-info:6.1.0.dfsg.1-5
   Setting up install-info (6.1.0.dfsg.1-5) ...
   Not a directory: PRINTER=EPSON_WF-3620_Series.
   dpkg: error processing package install-info (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-08 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: texinfo
  Title: package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this

[Desktop-packages] [Bug 1594814] Re: NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34"

2016-11-19 Thread Craig Furman

It seems like a fix was released for NetworkManager a few months ago,
when can we expect it to be released into the Ubuntu repositories?

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

Title:
  NetworkManager looking for signal strength in 'wlan0' instead of the
  apropriate 'wlxc46e1f1abe34"

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I get this error in my log a lot:
  "Jun 21 15:04:00 basspistol NetworkManager[834]:   [1466514240.9769] 
(wlan0): error getting signal strength: No such device"

  My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is
  getting a very funky name: "wlxc46e1f1abe34". It's not too much of a
  problem since the connection is established and working, but it
  renders the wifi-strength icon as if it was receiving maximum signal
  strength.

  Restarting the network-manager with: "sudo systemctl restart network-
  manager.service" solves the problem.

  Not sure if it is related, but i am also affected by this bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
  Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 
1.2.0-0ubuntu0.16.04.3) on 2016-06-19

  Let me know if there is any complementary information i can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10
  Uname: Linux 4.4.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 21 15:04:46 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-21 (60 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600
   10.42.0.0/24 dev wlxc46e1f1abe34  proto kernel  scope link  src 10.42.0.22  
metric 600
   169.254.0.0/16 dev wlxc46e1f1abe34  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH
   wlxc46e1f1abe34  wifi  connected
/org/freedesktop/NetworkManager/Devices/0  sakrecoer 1  
7bfae379-b282-4335-8bfe-f1f55229ad51  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp3s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1594814/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-11-13 Thread Craig Howard

The Chromium bug that was linked in the description of this bug now
contains a patch to reduce impact.  It's not clear to me if the bug is a
complete solution or not.

I don't know if upgrading to a new Chromium or applying that patch is a
faster mitigation for affected users.

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit

2016-09-10 Thread Craig Olofson

I have a JABRA Evolve 40 - MS Skype Edition attached to my Ubuntu
16.04.01 LTS and had experienced the same issues as kringalf.
kringalf's solution solved this for me as well.

Distribution:
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial
Kernel: 4.4.0-36-generic

usb-devices:
T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0b0e ProdID=0305 Rev=02.02
S:  Manufacturer=GN Netcom A/S
S:  Product=Jabra EVOLVE LINK MS
S:  SerialNumber=898EF4E007
C:  #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I:  If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
I:  If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
I:  If#= 3 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering
  Edit

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA
  Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my
  computer, the mouse pointer is somehow "captured" by the last active
  window. I can switch windows via alt-tab but left clicks in the new
  window still won't work, they will only work in the "old" window.

  WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the 
following:
  Section "InputClass"
   Identifier "Jabra"
  MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
   Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  and restart xorg-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Sep  1 14:47:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  1 11:27:32 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619307/+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 1447345] Re: Support the unprivileged namespace sandbox

2016-09-06 Thread Craig

I can confirm that chromium-browser does not start, syslog shows:

apparmor="DENIED" operation="capable" profile="/usr/lib/chromium-browser
/chromium-browser" pid=27954 comm="chromium-browse" capability=21
capname="sys_admin"

Apparmor profile enforce mode.
Trusty 14.04.5
chromium-browser 51.0.2704.79
apparmor-profiles 2.8.95-2430

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

Title:
  Support the unprivileged namespace sandbox

Status in Oxide:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium has a new layer 1 sandbox which replaces the suid sandbox on
  systems with CLONE_NEWUSER. However, it's currently incompatible with
  application confinement.

  To summarize, the sandbox mechanism does something like this:

  1) Browser launches zygote process:
- clones with CLONE_NEWUSER | CLONE_NEWPID | CLONE_NEWNET and then exec()

  2) Zygote initializes sandbox:
- unshare(CLONE_NEWUSER)
- clones a new process with CLONE_FS and then does waitpid(). The child 
chroots to /proc/self/fdinfo
- Enables CAP_SYS_ADMIN (see below)

  3) Zygote forks
- Parent becomes init
- Child continues as zygote

  4) Zygote waits for requests from the browser to create render
  processes

  5) On each request:
- Zygote clones a new process with CLONE_NEWPID (this is why it needs 
CAP_SYS_ADMIN)
- New process drops all privileges and becomes a renderer

  This produces the following denial on the device:

  type=1400 audit(1429733985.487:153): apparmor="DENIED"
  operation="capable"
  profile="com.zeptolab.cuttherope.full_cuttherope_0.5.2" pid=7195
  comm="qmlscene" capability=21 capname="sys_admin"

  The oxide_helper profile already allows sys_admin, but this is coming
  from the browser process, just here:

  7229  clone(child_stack=0, flags=CLONE_NEWUSER|SIGCHLD) = 7246 <-- Test that 
the new sandbox can be used
  7246  exit_group(0) = ?
  7229  wait4(7246,  
  7246  +++ exited with 0 +++
  7229  <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 
7246
  7229  --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=7246, 
si_status=0, si_utime=0, si_stime=0} ---
  7229  write(13, "\0", 1)= 1
  7229  rt_sigreturn()= 7246
  7229  access("/proc/self/ns/user", F_OK) = 0
  7229  access("/proc/self/ns/user", F_OK) = 0
  7229  access("/proc/self/ns/pid", F_OK) = 0
  7229  access("/proc/self/ns/user", F_OK) = 0
  7229  access("/proc/self/ns/net", F_OK) = 0
  7229  getuid32()= 32011
  7229  getgid32()= 32011
  7229  access("/proc/self/setgroups", F_OK) = -1 ENOENT (No such file or 
directory)
  7229  rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 8) = 0
  7229  clone(child_stack=0xbe8518d4, 
flags=CLONE_NEWUSER|CLONE_NEWPID|CLONE_NEWNET|SIGCHLD) = -1 EPERM (Operation 
not permitted)

  It fails in step 1) above, because it needs CAP_SYS_ADMIN before it's
  able to transition to the oxide_helper profile (which allows it)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1447345/+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 753520] Re: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

2016-08-17 Thread Craig

This issue persists in a fresh install of 16.04.1, Junaids' solution
with adding to the Remmina preferences does indeed solve the issue and
Remmina will start up.

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

Title:
  remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

Status in freerdp:
  New
Status in remmina:
  New
Status in remmina package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: remmina

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy remmina
  remmina:
    Installed: 1.1.1-1ubuntu1
    Candidate: 1.1.1-1ubuntu1
    Version table:
   *** 1.1.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one has their default keyboard
  setting set to en_US > System Settings... > Text Entry > change to
  Input sources to use: Maori > close window > secondary click the Text
  Input tray icon and change from English to Maori > restart > open
  Remmina and it works.

  4) What happens instead is it crashes consistently:
  remmina
  Remmina plugin VNC (type=Protocol) registered.
  Remmina plugin VNCI (type=Protocol) registered.
  Remmina plugin RDP (type=Protocol) registered.
  Remmina plugin RDPF (type=File) registered.
  Remmina plugin RDPS (type=Preference) registered.
  Segmentation fault

  First reported against Ubuntu 11.04, remmina 0.9.3-2

  WORKAROUND: Use en_US.

  WORKAROUND: Remove remmina-plugin-rdp.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: remmina 0.9.3-2
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Apr  7 15:17:34 2011
  ExecutablePath: /usr/bin/remmina
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: remmina
  ProcEnviron:
   LANGUAGE=en_ZA:en
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc61738202b 
:   mov(%r12),%rdi
   PC (0x7fc61738202b) ok
   source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   find_keyboard_layout_in_xorg_rules () from /usr/lib/libfreerdpkbd.so.0
   detect_keyboard_layout_from_xkb () from /usr/lib/libfreerdpkbd.so.0
   detect_and_load_keyboard () from /usr/lib/libfreerdpkbd.so.0
   freerdp_kbd_init () from /usr/lib/libfreerdpkbd.so.0
   remmina_plugin_rdpset_init () from 
/usr/lib/remmina/plugins/remmina-plugin-rdp.so
  Title: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/freerdp/+bug/753520/+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 1613117] [NEW] Download-complete animated image stays on screen after showing

2016-08-14 Thread Craig

Public bug reported:

When I download something in Firefox and it completes, the blue arrow
animated image shows and stays over the toolbar indefinitely.  As other
things change (causing parts to rerender) in the affected area, that
portion of the image goes away.

This occurred in FF 47 and now 48 too.

Image attached showing what I'm talking about.  Color is funny in
screenshot due to misconfigured screenshot tool.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 48.0+build2-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  clandry3969 F pulseaudio
 /dev/snd/controlC1:  clandry3969 F pulseaudio
BuildID: 20160728203720
Channel: Unavailable
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Aug 14 14:57:36 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2015-08-02 (378 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 10.10.10.254 dev wlan0  proto static  metric 600 
 10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.10.10.219  metric 
600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000
Locales: extensions.sqlite corrupt or missing
Plugins:
 iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
 prefs.js
 [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
Profiles: Profile0 (Default) - LastVersion=48.0/20160728203720 (In use)
RelatedPackageVersions: rhythmbox-mozilla 3.3-1ubuntu7
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-06-12 (63 days ago)
dmi.bios.date: 12/11/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0GFTRT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: XPS13 9333
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

** Attachment added: "download-complete.png"
   
https://bugs.launchpad.net/bugs/1613117/+attachment/4720895/+files/download-complete.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/1613117

Title:
  Download-complete animated image stays on screen after showing

Status in firefox package in Ubuntu:
  New

Bug description:
  When I download something in Firefox and it completes, the blue arrow
  animated image shows and stays over the toolbar indefinitely.  As
  other things change (causing parts to rerender) in the affected area,
  that portion of the image goes away.

  This occurred in FF 47 and now 48 too.

  Image attached showing what I'm talking about.  Color is funny in
  screenshot due to misconfigured screenshot tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 48.0+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clandry3969 F pulseaudio
   /dev/snd/controlC1:  clandry3969 F pulseaudio
  BuildID: 20160728203720
  Channel: Unavailable
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Aug 14 14:57:36 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-08-02 (378 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 10.10.10.254 dev wlan0  proto static  metric 600 
   10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.10.10.219  metric 
600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   iTunes Application

[Desktop-packages] [Bug 1336663] Re: lightdm uses wrong ccache name on pam_krb5 credentials refresh

2016-06-27 Thread Craig G

FWIW, this issue is also present using gdm3 in Ubuntu 16.04.  With
pam_krb5's debug option set, I see the following during initial login
(with successful credential cache construction):

gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: entry
gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) attempting 
authentication as cgal...@.com
gdm-password]: pam_krb5(gdm-password:auth): user cgallek authenticated as 
cgal...@.com
gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) temporarily storing 
credentials in /tmp/krb5cc_pam_LB8CeL
gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: exit (success)
gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: entry (establish)
gdm-password]: pam_krb5(gdm-password:setcred): (user cgallek) initializing 
ticket cache FILE:/tmp/krb5cc_1000_3BiTY0
gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: exit (success)


When unlocking the screen, I see the following successful credential refresh, 
but to the wrong cache filename (/tmp/krb5cc_0):

gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: entry
gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) attempting 
authentication as cgal...@angrydoughnuts.com
gdm-password]: pam_krb5(gdm-password:auth): user cgallek authenticated as 
cgal...@.com
gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) temporarily storing 
credentials in /tmp/krb5cc_pam_Dkg5Ip
gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: exit (success)
gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: entry (reinit)
gdm-password]: pam_krb5(gdm-password:setcred): (user cgallek) refreshing ticket 
cache /tmp/krb5cc_0
gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: exit (success)

The _0 cache that is created has the correct new credential in it, but
is obviously not known by any other process as it does not match the
earlier version of $KRB5CCNAME.  I imagine this is the same issue
described above where the $KRB5CCNAME environment variable is not
available in the gdm context which unlocks the screen.

It's worth noting that in the GDM case, there appears to be a per-
session helper process (gdm-session-worker) used to communicate with the
GDM service.  This process _does not_ have the $KRB5CCNAME variable set
in its environment.  Would storing the value in this processes
environment fix the problem?

~: ps -ef | grep gdm-session-worker
root 11364 11203  0 Jun25 ?00:00:00 gdm-session-worker 
[pam/gdm-password]

~: cat /proc/11364/environ 
LANG=en_US.UTF-8PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binGDM_SESSION_DBUS_ADDRESS=unix:abstract=/tmp/dbus-oTnmcExV


** Also affects: gdm
   Importance: Undecided
   Status: New

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

Title:
  lightdm uses wrong ccache name on pam_krb5 credentials refresh

Status in gdm:
  New
Status in Light Display Manager:
  Triaged
Status in libpam-krb5 package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  As already noted by Brian Knoll in 
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/24
  lightdm 1.10.1-0ubuntu1 uses an inappropriate credentials cache, 
/tmp/krb5cc_0, when refreshing Kerberos credentials on screen unlock.

  I couldn't find the new bug Robert Ancell called for in
  https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/27
  so I'm opening one now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1336663/+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 1584464] Re: attempt to copy dot.mp3 to thumb drive (dot way takes precedence)

2016-05-22 Thread craig P

I can't figure out how to edit the title of this SDR -- I meant to say
dot.wav, but my fat-fingers types "dot way"... If someone can correct.

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

Title:
  attempt to copy dot.mp3 to thumb drive (dot way takes precedence)

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 (fresh clean install -- format/wipe of 12.04)

  Nautilus

  I tried this a couple times, at first thinking operator error, but I
  then figured out how to work around the Nautilus bug.

  I have two files in a directory -- one is a dot.wav music file and the
  other is a dot.mp3 conversion of that music file, properly tagged
  (using sound converter and easy tag).

  Here is the problem:

  If you copy the dot.mp3 to a thumb drive (fresh, clean, formatted,
  emptry), Nautilus does not copy the dot.mp3 to the thumb drive.

  Instead, unbeknownst to the user, nautilus copies the dot.wav file to
  the thumb drive instead.

  ---

  I made a few trips to the car before I realized the situation. Again,
  I conservatively decided to make the presumption it was operator
  error. Then, I decided to work around the bug, as follows:

  I opened up a MATE terminal and worked through bash, created an empty
  directory (i.e., mkdir) and copied JUST the dot.mp3 file to the empty
  directory (i.e., cp).

  I probably should have just used bash to copy the dot.mp3 to the thumb
  drive, but I used nautilus instead. This time it worked. I went out to
  the car and plopped the thumb drive in and all was good.

  ---

  I may have had the dot.wav already in the thumb drive at one point.
  The second time, I know I emptied the thumb drive. By the third time,
  I worked around the bug as above.

  So, if I had to take a guess, I would say that nautilus is making the
  dot.wav file take precedence over the dot.mp3 file. Yes, other than
  the file extension, the base names (i.e., bash basename) are the same.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1584464/+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 1584464] [NEW] attempt to copy dot.mp3 to thumb drive (dot way takes precedence)

2016-05-22 Thread craig P

Public bug reported:

Ubuntu 16.04 (fresh clean install -- format/wipe of 12.04)

Nautilus

I tried this a couple times, at first thinking operator error, but I
then figured out how to work around the Nautilus bug.

I have two files in a directory -- one is a dot.wav music file and the
other is a dot.mp3 conversion of that music file, properly tagged (using
sound converter and easy tag).

Here is the problem:

If you copy the dot.mp3 to a thumb drive (fresh, clean, formatted,
emptry), Nautilus does not copy the dot.mp3 to the thumb drive.

Instead, unbeknownst to the user, nautilus copies the dot.wav file to
the thumb drive instead.

---

I made a few trips to the car before I realized the situation. Again, I
conservatively decided to make the presumption it was operator error.
Then, I decided to work around the bug, as follows:

I opened up a MATE terminal and worked through bash, created an empty
directory (i.e., mkdir) and copied JUST the dot.mp3 file to the empty
directory (i.e., cp).

I probably should have just used bash to copy the dot.mp3 to the thumb
drive, but I used nautilus instead. This time it worked. I went out to
the car and plopped the thumb drive in and all was good.

---

I may have had the dot.wav already in the thumb drive at one point. The
second time, I know I emptied the thumb drive. By the third time, I
worked around the bug as above.

So, if I had to take a guess, I would say that nautilus is making the
dot.wav file take precedence over the dot.mp3 file. Yes, other than the
file extension, the base names (i.e., bash basename) are the same.

Regards.

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

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

Title:
  attempt to copy dot.mp3 to thumb drive (dot way takes precedence)

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 (fresh clean install -- format/wipe of 12.04)

  Nautilus

  I tried this a couple times, at first thinking operator error, but I
  then figured out how to work around the Nautilus bug.

  I have two files in a directory -- one is a dot.wav music file and the
  other is a dot.mp3 conversion of that music file, properly tagged
  (using sound converter and easy tag).

  Here is the problem:

  If you copy the dot.mp3 to a thumb drive (fresh, clean, formatted,
  emptry), Nautilus does not copy the dot.mp3 to the thumb drive.

  Instead, unbeknownst to the user, nautilus copies the dot.wav file to
  the thumb drive instead.

  ---

  I made a few trips to the car before I realized the situation. Again,
  I conservatively decided to make the presumption it was operator
  error. Then, I decided to work around the bug, as follows:

  I opened up a MATE terminal and worked through bash, created an empty
  directory (i.e., mkdir) and copied JUST the dot.mp3 file to the empty
  directory (i.e., cp).

  I probably should have just used bash to copy the dot.mp3 to the thumb
  drive, but I used nautilus instead. This time it worked. I went out to
  the car and plopped the thumb drive in and all was good.

  ---

  I may have had the dot.wav already in the thumb drive at one point.
  The second time, I know I emptied the thumb drive. By the third time,
  I worked around the bug as above.

  So, if I had to take a guess, I would say that nautilus is making the
  dot.wav file take precedence over the dot.mp3 file. Yes, other than
  the file extension, the base names (i.e., bash basename) are the same.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1584464/+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 1516304] [NEW] package unity-settings-daemon 14.04.0+14.04.20151012-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it be

2015-11-14 Thread Craig Olofson

Public bug reported:

A "system program problem detected" box pops up, gives an error.  I
click through to "show details" and to report it.  While doing this,
another "system program problem detected" box pops up... this seems to
go on ad nauseum.  Below is one of these reports.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: unity-settings-daemon 14.04.0+14.04.20151012-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
Uname: Linux 3.13.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
Date: Sat Nov 14 10:54:45 2015
DuplicateSignature: 
package:unity-settings-daemon:14.04.0+14.04.20151012-0ubuntu1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-07-28 (474 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: unity-settings-daemon
Title: package unity-settings-daemon 14.04.0+14.04.20151012-0ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check third-party-packages trusty

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

Title:
  package unity-settings-daemon 14.04.0+14.04.20151012-0ubuntu1 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  A "system program problem detected" box pops up, gives an error.  I
  click through to "show details" and to report it.  While doing this,
  another "system program problem detected" box pops up... this seems to
  go on ad nauseum.  Below is one of these reports.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20151012-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  Date: Sat Nov 14 10:54:45 2015
  DuplicateSignature: 
package:unity-settings-daemon:14.04.0+14.04.20151012-0ubuntu1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-07-28 (474 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: unity-settings-daemon
  Title: package unity-settings-daemon 14.04.0+14.04.20151012-0ubuntu1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1516304/+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 794415] Re: Seg fault on launch

2015-10-19 Thread Craig

*** This bug is a duplicate of bug 753520 ***
https://bugs.launchpad.net/bugs/753520

Confirmed as occurring in 15.10 with a ZA keyboard layout, switching to
US keyboard layout allows it to launch.

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

Title:
  Seg fault on launch

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: remmina

  Getting a seg fault when launching. Seems to be related to the keyboard 
layout. Some have reported success when changing the layout but this is 
obviously not a permanent solution.
  http://ubuntuforums.org/showthread.php?t=1664620

  Steps to reproduce error:
  Install Natty with South Africa localization, US keyboard is automatically 
chosen but keyboard layout appears as ZA once install is complete. Install 
remmina from default Ubuntu repos, launch from terminal.

  Remmina plugin RDP (type=Protocol) registered.
  Remmina plugin RDPF (type=File) registered.
  Remmina plugin RDPS (type=Tool) registered.
  xkbLayout: za xkbVariant:
  Segmentation fault

  For me its only happening on Natty, but as noted in the forum post
  above, spietkop is having the same problem on Maverick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/794415/+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 753520] Re: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

2015-10-19 Thread Craig

This issue persists, confirmed as occurring in 15.10 with a ZA keyboard
layout, switching to US keyboard layout allows it to launch.

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

Title:
  remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

Status in freerdp:
  New
Status in remmina:
  New
Status in remmina package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: remmina

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy remmina
  remmina:
    Installed: 1.1.1-1ubuntu1
    Candidate: 1.1.1-1ubuntu1
    Version table:
   *** 1.1.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one has their default keyboard
  setting set to en_US > System Settings... > Text Entry > change to
  Input sources to use: Maori > close window > secondary click the Text
  Input tray icon and change from English to Maori > restart > open
  Remmina and it works.

  4) What happens instead is it crashes consistently:
  remmina
  Remmina plugin VNC (type=Protocol) registered.
  Remmina plugin VNCI (type=Protocol) registered.
  Remmina plugin RDP (type=Protocol) registered.
  Remmina plugin RDPF (type=File) registered.
  Remmina plugin RDPS (type=Preference) registered.
  Segmentation fault

  First reported against Ubuntu 11.04, remmina 0.9.3-2

  WORKAROUND: Use en_US.

  WORKAROUND: Remove remmina-plugin-rdp.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: remmina 0.9.3-2
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Apr  7 15:17:34 2011
  ExecutablePath: /usr/bin/remmina
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: remmina
  ProcEnviron:
   LANGUAGE=en_ZA:en
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc61738202b 
:   mov(%r12),%rdi
   PC (0x7fc61738202b) ok
   source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   find_keyboard_layout_in_xorg_rules () from /usr/lib/libfreerdpkbd.so.0
   detect_keyboard_layout_from_xkb () from /usr/lib/libfreerdpkbd.so.0
   detect_and_load_keyboard () from /usr/lib/libfreerdpkbd.so.0
   freerdp_kbd_init () from /usr/lib/libfreerdpkbd.so.0
   remmina_plugin_rdpset_init () from 
/usr/lib/remmina/plugins/remmina-plugin-rdp.so
  Title: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/freerdp/+bug/753520/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

2015-10-12 Thread Craig Hansen

** Also affects: gparted via
   https://bugzilla.gnome.org/show_bug.cgi?id=729800
   Importance: Unknown
   Status: Unknown

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 1408149] Re: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 14.04 LTS  64bit release.

  When I logged in today I got an apport bug notification about the
  nvidia driver. nvidia-331 kernel module failed to build

  Everything appears to be working fine though.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Mon Jan  5 18:16:05 2015
  InstallationDate: Installed on 2015-01-05 (1 days ago)
  InstallationMedia: Ubuntu MATE 14.04.1 Trusty Tahr - final amd64 (2014)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1408149/+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 1408260] Re: nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  This is Ubuntu Gnome Vivid testing platform.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-8-generic
  Date: Wed Jan  7 15:27:44 2015
  InstallationDate: Installed on 2014-12-16 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141214)
  PackageVersion: 331.113-0ubuntu2
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1408260/+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 1408599] Re: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1408599

Title:
  nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  I decided to update my system and this bug occured.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.113-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-28-generic
  Date: Thu Jan  8 10:29:04 2015
  InstallationDate: Installed on 2009-11-16 (1878 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  PackageVersion: 331.113-0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1408599/+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 1408175] Re: nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-8-generic
  Date: Wed Jan  7 04:50:59 2015
  InstallationDate: Installed on 2014-07-10 (180 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  PackageVersion: 331.113-0ubuntu2
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1408175/+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 1408066] Re: nvidia-331-updates 331.113-0ubuntu2: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1408066

Title:
  nvidia-331-updates 331.113-0ubuntu2: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  apt-cache policy nvidia-331-updates
  nvidia-331-updates:
Installed: 331.113-0ubuntu2
Candidate: 331.113-0ubuntu2
Version table:
   *** 331.113-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages
  100 /var/lib/dpkg/status
   331.89-0ubuntu5 0
  500 http://archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331-updates 331.113-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-8-generic
  Date: Wed Jan  7 02:12:07 2015
  InstallationDate: Installed on 2014-05-29 (222 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.113-0ubuntu2
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.113-0ubuntu2: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1408066/+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 1408018] Re: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1408018

Title:
  nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  Was once again greeted with this on boot.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Mon Jan  5 11:15:04 2015
  InstallationDate: Installed on 2014-10-07 (90 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1408018/+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 1408929] Re: error while routine system update : nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  error while routine system update : nvidia-331-uvm
  331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Got this error while performing a system update. This was  a fresh
  install of ubuntu 2 days ago. Minimal changes since then

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Fri Jan  9 14:17:42 2015
  InstallationDate: Installed on 2015-01-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1408929/+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 1407894] Re: Crashed after a system update, and after bootup. nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  Crashed after a system update, and after bootup. nvidia-331
  331.113-0ubuntu0.1: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Crashed after a system update, and after bootup.
  Freshly installed xubuntu on a brand new ssd disk.

  Im using a Lenovo Z510.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.113-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-28-generic
  Date: Tue Jan  6 10:06:36 2015
  InstallationDate: Installed on 2015-01-05 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageVersion: 331.113-0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1407894/+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 1407728] Re: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Launchpad crashed!!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Mon Jan  5 21:42:26 2015
  InstallationDate: Installed on 2015-01-02 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1407728/+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 1407706] Re: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1407706

Title:
  nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm
  kernel module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  Upgrade to kernel 3.16.0-29

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.113-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-29-generic
  Date: Mon Jan  5 16:16:49 2015
  InstallationDate: Installed on 2013-05-17 (597 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac 
(20130424)
  PackageVersion: 331.113-0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm 
kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1407706/+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 1407631] Re: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file
** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
  failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  This bug was reported after running a system update. It has had no
  immediately visible effect.

  Some hardware specs: Dell XPS 15Z with Nvidia Optimus card. Had quite
  a struggle installing and getting 14.04 up and running with native
  resolution.

  Modifications I have made:
  GRUB: I have tried some different settings to avoid a black screen after the 
GRUB boot page. Currently it looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT=
  GRUB_CMDLINE_LINUX=acpi_osi=linux noapic nolapic i915.i915_enable_rc6=1 
i915.lvds_downclock=1 i915.i915_enable_fbc=1 pcie_aspm=force

  Bumblebee installed and things seem to be running relatively stable
  (mouse lagging after suspend some times though). Using the NVIDIA
  binary 331.113 nvidia -331 driver (proprietary, tested).

  $ lspci -vnn | grep '\''[030[02]\]'
  00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation 
Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) 
(prog-if 00 [VGA controller])

  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M
  [GeForce GT 525M] [10de:0df5] (rev ff) (prog-if ff)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Mon Jan  5 11:31:40 2015
  InstallationDate: Installed on 2014-12-31 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1407631/+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 1397679] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397679

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  occurred during installation of package updates
  similar to bug #1397677 but for AMD64 architecture

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Sun Nov 30 08:50:34 2014
  InstallationDate: Installed on 2014-09-25 (65 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-11-22 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397679/+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 1397619] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  happened during a system update

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Sat Nov 29 21:10:39 2014
  InstallationDate: Installed on 2014-07-31 (121 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397619/+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 1398719] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1398719

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  n/a

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Wed Dec  3 01:37:29 2014
  InstallationDate: Installed on 2014-12-03 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1398719/+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 1397878] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397878

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  Got crash when restarted laptop - as soon as I logged into Ubuntu,
  unity started and the crash dialog appeared.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Tue Nov 25 08:40:57 2014
  InstallationDate: Installed on 2014-03-25 (250 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397878/+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 1397791] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  This is automatically reported. I did not notice a problem.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-26-generic
  Date: Sun Nov 30 21:56:03 2014
  InstallationDate: Installed on 2014-09-06 (85 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397791/+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 1399042] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1399042

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  I ran the software update application and this bug report popped. Not
  sure why. There didn't seem to be any problems with installing the
  updates...although I have not restarted yet :)

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Wed Dec  3 18:40:36 2014
  InstallationDate: Installed on 2014-04-01 (246 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to utopic on 2014-11-02 (31 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1399042/+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 1398485] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1398485

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  this error appears after logging into Ubuntu 14.10.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Tue Nov 25 08:49:04 2014
  InstallationDate: Installed on 2014-09-30 (63 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to utopic on 2014-11-10 (22 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1398485/+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 1397677] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397677

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  download updating packages

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Sun Nov 30 14:40:51 2014
  InstallationDate: Installed on 2014-11-11 (19 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397677/+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 1399019] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build [sudo apt-get upgrade reports error]

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  [sudo apt-get upgrade reports error]

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  I was upgrading my newly configured Utopic Unicorn installation by
  running sudo apt-get upgrade. I had recently opted on using a
  proprietary driver that was indicated as tested under the Additional
  Drivers tab of the Softwares  Updates app. I would like to hear
  more from you regarding this and hope that this bug will not happen in
  Vivid Velvet since I am looking forward to upgrading to it by April.
  Good day. Thank you very much! More powers to all!

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Thu Dec  4 07:33:53 2014
  InstallationDate: Installed on 2014-12-03 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1399019/+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 1397986] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397986

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  The system reported and error during booting

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Wed Nov 26 11:56:49 2014
  InstallationDate: Installed on 2014-06-11 (173 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-29 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397986/+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 1397638] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 14.10
  Release:  14.10

  nvidia-331-uvm:
Installed: 331.89-0ubuntu5
Candidate: 331.89-0ubuntu5
Version table:
   *** 331.89-0ubuntu5 0
  500 http://archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages
  100 /var/lib/dpkg/status

  I don't know what should happen. Only my update failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Sun Nov 30 11:30:25 2014
  InstallationDate: Installed on 2014-05-08 (205 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-11-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397638/+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 1397982] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397982

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  After kernel update NVIDIA driver displayed the system error

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Mon Dec  1 18:25:43 2014
  InstallationDate: Installed on 2014-11-29 (2 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397982/+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 1397673] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397673

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  The system reports this when I log in. No symptoms that I can find.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Wed Nov 26 10:48:16 2014
  InstallationDate: Installed on 2012-07-14 (868 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397673/+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 1397757] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  after update then reboot

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-26-generic
  Date: Sun Nov 30 20:03:34 2014
  InstallationDate: Installed on 2014-10-27 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397757/+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 1396984] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1396984

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  An error occurred while updating.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  DKMSKernelVersion: 3.16.0-26-generic
  Date: Thu Nov 27 17:48:02 2014
  InstallationDate: Installed on 2012-11-29 (728 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-26 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1396984/+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 1397710] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Just keeps poping up failure window

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-lowlatency
  Date: Sun Nov 30 12:23:02 2014
  InstallationDate: Installed on 2014-11-30 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397710/+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 1399966] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1399966

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  Error occurred during normal system updates using the Ubuntu software
  update tool.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Fri Dec  5 20:08:27 2014
  InstallationDate: Installed on 2014-10-24 (42 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1399966/+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 1397596] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

*** This bug is a duplicate of bug 1431753 ***
https://bugs.launchpad.net/bugs/1431753

** This bug is no longer a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

** This bug has been marked a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1397596

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  update

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-26-generic
  Date: Sat Nov 29 21:52:16 2014
  InstallationDate: Installed on 2014-07-13 (138 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to utopic on 2014-11-15 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397596/+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 1397115] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build