[Desktop-packages] [Bug 2031252] Re: Playing video with audio freezes

[Gary Godfrey]

I've been having this issue since updating to mantic - the sound to HDMI
just freezes and any application that is writing to it also freezes.  If
I do (from a terminal):

systemctl restart --user wireplumber.service

It comes back for a while.

I'm also running on a Lenovo X1 Carbon 7th generation.

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

Title:
  Playing video with audio freezes

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm not sure when this started, but any video I play with audio is not
  working properly - it severely lags and/or freezes. This happens in
  Youtube on both Chrome and Firefox, and in the regular GNOME media
  player. Audio by itself works fine, and video with audio muted works
  fine. I tried restarting and downgrading the kernel, to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ari2679 F pipewire
ari2700 F wireplumber
   /dev/snd/seq:ari2679 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 13 17:22:56 2023
  InstallationDate: Installed on 2022-06-07 (432 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago)
  dmi.bios.date: 06/12/2023
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET85W (1.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031252/+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 2018264] [NEW] package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- There needs to be an opti

[gary knott]

Public bug reported:


There needs to be some way to override a bad config fiel, instead of
just complaining and complaining

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic i686
ApportVersion: 2.20.1-0ubuntu2.30
AptOrdering:
 ubuntu-advantage-tools: Install
 tex-common: Configure
 ubuntu-advantage-tools: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Mon May  1 18:54:06 2023
DpkgHistoryLog:
 Start-Date: 2023-05-01  18:52:59
 Commandline: aptdaemon role='role-commit-packages' sender=':1.78'
 Upgrade: ubuntu-advantage-tools:i386 (27.9~16.04.1, 27.14.4~16.04)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-03-18 (3696 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: tex-common
Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2019-02-09 (1542 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1  --
  There needs to be an option to override bad config files!

Status in tex-common package in Ubuntu:
  New

Bug description:

  There needs to be some way to override a bad config fiel, instead of
  just complaining and complaining

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
  Uname: Linux 4.4.0-210-generic i686
  ApportVersion: 2.20.1-0ubuntu2.30
  AptOrdering:
   ubuntu-advantage-tools: Install
   tex-common: Configure
   ubuntu-advantage-tools: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Mon May  1 18:54:06 2023
  DpkgHistoryLog:
   Start-Date: 2023-05-01  18:52:59
   Commandline: aptdaemon role='role-commit-packages' sender=':1.78'
   Upgrade: ubuntu-advantage-tools:i386 (27.9~16.04.1, 27.14.4~16.04)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-03-18 (3696 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: tex-common
  Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-02-09 (1542 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/2018264/+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 2016906] [NEW] Inactive zombie ghost icons left behind on desktop when copying files

[Gary W Sherwin]

Public bug reported:

When copying files between directory windows, occasionally zombie ghost
icons are left on the desktop.  These are like holes in the screen with
an icon that appears on top of everything in its covered location, is
not selectable and is not moveable.

Ubuntu 22.10
Release:22.10

gjs:
  Installed: 1.74.0-1
  Candidate: 1.74.0-1
  Version table:
 *** 1.74.0-1 500
500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gjs 1.74.0-1
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 18 11:24:52 2023
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2023-02-21 (56 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gjs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic

** Attachment added: "Example Zombie Ghost Icons On Desktop"
   
https://bugs.launchpad.net/bugs/2016906/+attachment/5665032/+files/Screenshot%20from%202023-04-08%2007-54-06.png

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

Title:
  Inactive zombie ghost icons left behind on desktop when copying files

Status in gjs package in Ubuntu:
  New

Bug description:
  When copying files between directory windows, occasionally zombie
  ghost icons are left on the desktop.  These are like holes in the
  screen with an icon that appears on top of everything in its covered
  location, is not selectable and is not moveable.

  Ubuntu 22.10
  Release:  22.10

  gjs:
Installed: 1.74.0-1
Candidate: 1.74.0-1
Version table:
   *** 1.74.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gjs 1.74.0-1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 18 11:24:52 2023
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2023-02-21 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gjs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2016906/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

All the same, perhaps vulkaninfo should issue a warning about vestigial
config if it can find a perfectly usable icd somewhere else! Presumably
it looks for the one supplied by Ubuntu.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

Got to the bottom of it and post here in case anyone else has this
problem.

In /etc/vulkan/icd.d there was a link: amd_icd64.json ->
/etc/alternatives/amd_icd64.json

Also a link: /etc/alternatives/amd_icd64.json -> 
/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json
(a non existant path)

In /opt/amdgpu-pro/lib/x86_64-linux-gnu there was a link:
libamd_comgr.so.1 -> libamd_comgr.so.1.7.0 (which does not exist).

Deleted all above and vulkaninfo no longer reports that error.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

That's not quite true, it was assumed and believed until a little while
ago that I had amdgpu-pro installed which I don't and because of that no
one even looked at the problem.  Mark it invalid if you like but the
real problem has not even been investigated.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

Thank you. I have that file:
/usr/share/vulkan/icd.d/radeon_icd.x86_64.json.  So now I'm back to
figuring out why vulkaninfo errors out:

vulkaninfo reports:
ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

There must be some config somewhere that tells vulkaninfo to use this,
no?

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

Thank you.  It does seem to point to that.  Even so, vulkan-mesa-drivers
has been installed and has not provided vulkan-icd.  Does it go under a
different name?  When I installed vulkan-mesa-drivers, has dpkg or apt
seen a remnant of amdgpu-pro and not installed the icd even though by
normal means like the commands above I see no trace of amdgpu-pro?  That
appears unlikely.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

→ apt list --installed|grep amdvlk
(just the interface warning otherwise nothing)

→ apt-cache show amdvlk
N: Unable to locate package amdvlk
E: No packages found

→ apropos amdvlk
amdvlk: nothing appropriate.

→ apt-cache search amdvlk
(nothing)
→ apt-cache search amd|grep vlk
(nothing)

So no, I don't think it's installed. Just to be clear, I have used
amdgpu-pro in the past to try gpu rendering with Blender but it was so
flaky I gave up and uninstalled it.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

I don't see amdgpu-pro when I do this:

→ apt list --installed |grep amdgpu

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

libdrm-amdgpu1/bionic-updates,now 2.4.101-2~18.04.1 amd64 [installed]
xserver-xorg-video-amdgpu-hwe-18.04/bionic-updates,now 19.1.0-1~18.04.1 amd64 
[installed,automatic]

lspci -v shows no amdgpu-pro

Curious, how can you tell I have amdgpu-pro installed?  There is no
mention of it in the reports above.  Maybe the problem is a mixed up
installation?

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Gary Taverner]

'if its vulkan driver does not install its icd file in the correct
place, there's nothing we can do about that'

Thank you for your help. I was not aware of that interaction, only of
what the installed package vulkan-mesa-drivers claimed as stated at the
beginning of this report.

'apt-cache show says that vulkan-mesa-drivers provides vulkan-icd'.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1956365] Re: Firefox snap package can not resolve .local dns names

[Gary Allan]

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

Not quite the same issue.

I have AVAHI/mdns disabled and was using vanilla DNS. It was working OK
and recently stopped working.

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

Title:
  Firefox snap package can not resolve .local dns names

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Firefox snap package does not resolve .local dns names after recent
  update.

  After a recent snap package update of Firefox I can no longer resolve
  .local DNS names for my local network. This ONLY impacts the Firefox
  snap package. Brave, Chrome and DNS resolution on the local terminal
  (ping) are working correctly.

  When opening https://docker.local developer tools displays the error
  NS_ERROR_UNKNOWN_HOST

  gary@orion:~$ ping docker.local
  PING docker.local (192.168.0.18) 56(84) bytes of data.
  64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

  Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
  No DNS requests for the docker.local A record are generated by the Firefox 
snap package.

  563.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
  573.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local

  
  I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] Re: Firefox snap package can not resolve .local dns names

[Gary Allan]

Hello,

I think it's something to do with AVAHI resolution within the Firefox
snap package.

I disabled the AVAHI services on my servers/PCs as it conflicts with
.local running on a local DNS server. For some reason .local requests
within the Firefox snap package stopped working and just generate the
odd SOA .local DNS request.

I've now migrated my internal network to .lan and DNS resolution is
working correctly.

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

Title:
  Firefox snap package can not resolve .local dns names

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Firefox snap package does not resolve .local dns names after recent
  update.

  After a recent snap package update of Firefox I can no longer resolve
  .local DNS names for my local network. This ONLY impacts the Firefox
  snap package. Brave, Chrome and DNS resolution on the local terminal
  (ping) are working correctly.

  When opening https://docker.local developer tools displays the error
  NS_ERROR_UNKNOWN_HOST

  gary@orion:~$ ping docker.local
  PING docker.local (192.168.0.18) 56(84) bytes of data.
  64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

  Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
  No DNS requests for the docker.local A record are generated by the Firefox 
snap package.

  563.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
  573.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local

  
  I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] Re: Firefox snap package can not resolve .local dns names

[Gary Allan]

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  Firefox snap package can not resolve .local dns names

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Firefox snap package does not resolve .local dns names after recent
  update.

  After a recent snap package update of Firefox I can no longer resolve
  .local DNS names for my local network. This ONLY impacts the Firefox
  snap package. Brave, Chrome and DNS resolution on the local terminal
  (ping) are working correctly.

  When opening https://docker.local developer tools displays the error
  NS_ERROR_UNKNOWN_HOST

  gary@orion:~$ ping docker.local
  PING docker.local (192.168.0.18) 56(84) bytes of data.
  64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

  Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
  No DNS requests for the docker.local A record are generated by the Firefox 
snap package.

  563.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
  573.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local

  
  I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] Re: Firefox snap package can not resolve .local dns names

[Gary Allan]

Firefox running on Windows 10 is working correctly (latest version).

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

Title:
  Firefox snap package can not resolve .local dns names

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap package does not resolve .local dns names after recent
  update.

  After a recent snap package update of Firefox I can no longer resolve
  .local DNS names for my local network. This ONLY impacts the Firefox
  snap package. Brave, Chrome and DNS resolution on the local terminal
  (ping) are working correctly.

  When opening https://docker.local developer tools displays the error
  NS_ERROR_UNKNOWN_HOST

  gary@orion:~$ ping docker.local
  PING docker.local (192.168.0.18) 56(84) bytes of data.
  64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

  Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
  No DNS requests for the docker.local A record are generated by the Firefox 
snap package.

  563.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
  573.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local

  
  I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] [NEW] Firefox snap package can not resolve .local dns names

[Gary Allan]

Public bug reported:

Firefox snap package does not resolve .local dns names after recent
update.

After a recent snap package update of Firefox I can no longer resolve
.local DNS names for my local network. This ONLY impacts the Firefox
snap package. Brave, Chrome and DNS resolution on the local terminal
(ping) are working correctly.

When opening https://docker.local developer tools displays the error
NS_ERROR_UNKNOWN_HOST

gary@orion:~$ ping docker.local
PING docker.local (192.168.0.18) 56(84) bytes of data.
64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
No DNS requests for the docker.local A record are generated by the Firefox snap 
package.

56  3.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
57  3.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local


I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

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

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

Title:
  Firefox snap package can not resolve .local dns names

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap package does not resolve .local dns names after recent
  update.

  After a recent snap package update of Firefox I can no longer resolve
  .local DNS names for my local network. This ONLY impacts the Firefox
  snap package. Brave, Chrome and DNS resolution on the local terminal
  (ping) are working correctly.

  When opening https://docker.local developer tools displays the error
  NS_ERROR_UNKNOWN_HOST

  gary@orion:~$ ping docker.local
  PING docker.local (192.168.0.18) 56(84) bytes of data.
  64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

  Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
  No DNS requests for the docker.local A record are generated by the Firefox 
snap package.

  563.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
  573.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local

  
  I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1888240] Re: Ubuntu Dock shows empty space for apps lacking a .desktop file

[Gary]

Replicated in our systems as well.

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

Title:
  Ubuntu Dock shows empty space for apps lacking a .desktop file

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  Problem:
  On Ubuntu Desktop 20.04, everything latest, I have run into the inconvenience 
that when I'm running a GUI program without a freedesktop .desktop launcher, 
the Ubuntu Dock shows it as an empty space (since it has no icon of its own).

  Expected behavior:
  I would expect a generic placeholder / fallback icon to be shown for such 
applications, as an empty space at the bottom of the Dock is hard to find, and 
makes navigating applications frustrating. (In older versions of Ubuntu, a 
generic application icon was shown in such cases.)

  Steps to reproduce:
  1. Open terminal
  2. Run "xclock" from the terminal
  3. Observe the blank space on Ubuntu Dock

  Some relevant package versions:
  gnome-shell: 3.36.3-1ubuntu1~20.04.2
  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1
  yaru-theme-icon: 20.04.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1888240/+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 195982] Re: Shift key (and caps lock) stop working when using VMWare

[Gary Clayburg]

Ok, so I went back and re-read some of the most recent comments here -
especially #226 and #229.

This is what works for me:
$ alias vmware="xmodmap -e 'remove control =  Caps_Lock ' && 
/usr/lib/vmware/bin/vmplayer"

If I start vmware with this alias, the keyboard on the host does not get 
corrupted when the mouse leaves the window.  Well, sorta.  I've used this for a 
few days and it was working until just now as i type this message.  So this fix 
is not perfect.  But this 2 step fix seems to get around the issue:
$ setxkbmap
$ alias vmware="xmodmap -e 'remove control =  Caps_Lock '

To me this really looks more like a vmware bug.  I plan on filing an
issue there.

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

Title:
  Shift key (and caps lock) stop working when using VMWare

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in xkeyboard-config package in Ubuntu:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  [Problem]
  VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys 
stopping functionality when running under VMWare, requiring the user to setup 
their configuration settings manually in VMWare.  For a detailed explanation 
see the following article:

  http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html

  [Original Report]
  After a day or so of running the shift key mysteriously stops working as does 
the cap lock. In other words I cannot enter shifted characters of any kind. The 
keyboard is connected to a KVM and all other systems respond to it properly. In 
additional any VMWare sessions I have open respond correctly. So I have the 
condition where all non-vmware applications in Ubuntu Hardy (all updates 
applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT 
applications within an active (a paused/restarted session also works) VMWare 
sessions running DO recognize the key.

  When this condition occurs ALL applications (except those within a
  VMWare session) are also unstable and will usually crash within a few
  keystrokes.If I continue to operate in this mode. I cannot pinpoint
  what, if any, application triggers this. It has always happened while
  working within terminal/browser/vmware sessions and NOT when opening a
  new application. It could be related to the KVM switch, but none of my
  other systems (2 Mandriva, 1 Windows) are affected by this.

  This bug has been present on my system for a number of days across
  daily updates and reboots (if the update requested it) and I think
  since I installed Hardy Alpha 1.

  A work around: log off and back on. A reboot/restart does not appear
  to be needed.

  Error logs show some unusual activity.

  --- MARK 
  ...
  ... kernel ... rtc lost 7 interrupts ...
  --- MARK ---
  

  Plus some segfaults indicating which application crashed as I tried to
  type into it (mouse works fine).

  System: HP dv9743cl (which otherwise works lovely)
  Ubuntu: Hardy 8.04 (from lsb-release)

  
  TEST CASE:
  1. Click inside the VM and
 
  2. Hold any of the Ctrl, Alt and/or shift keys while releasing the 
keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt 
to revert back to windowed mode, as the cursor is then released from the VM). 

  WORKAROUND:
  After this happens to recover your keyboard execute 'setxkbmap' in a terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/195982/+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 195982] Re: Shift key (and caps lock) stop working when using VMWare

[Gary Clayburg]

Ok I see this issue is closed as its quite old.  Is this particular
issue tracked somewhere else?

I just upgraded my Ubuntu 16.04 system to Ubuntu 18.04.5 and this issue
still exists for me.

what I'd like to be able to do is:
1. configure my keyboard on the host laptop to map "Caps Lock as an extra 
control key"
2. launch a vm in vmware player on the laptop
3. Use both the left and right shift keys inside any window on the host laptop.

The workaround of running "setxkbmap" does get around the issue
somewhat.  For me it does allow the right shift key to start working
again.  However, it doesn't fix everything.  For example, I notice that
I can no longer use a the Alt-F1 keyboard shortcut in IntelliJ IDEA.
The only workaround I have found for this is to restart the entire
laptop after using any vm in vmware player or just not use Alt-F1
keystroke.

I do recall having to do some keyboard mapping a long time ago so that
IntelliJ could process Alt-F1 and not Ubuntu itself.

Does anyone know if Ubuntu 20.04 magically makes this issue go away?


One other thing I remembered.  I had a similar but a little different issue 
some years ago with the "caps lock as extra control key" setting when using 
synergy.  More details here:

https://github.com/symless/synergy-core/issues/4658


AFAIK, that issue was never resolved either.


** Bug watch added: github.com/symless/synergy-core/issues #4658
   https://github.com/symless/synergy-core/issues/4658

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

Title:
  Shift key (and caps lock) stop working when using VMWare

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in xkeyboard-config package in Ubuntu:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  [Problem]
  VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys 
stopping functionality when running under VMWare, requiring the user to setup 
their configuration settings manually in VMWare.  For a detailed explanation 
see the following article:

  http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html

  [Original Report]
  After a day or so of running the shift key mysteriously stops working as does 
the cap lock. In other words I cannot enter shifted characters of any kind. The 
keyboard is connected to a KVM and all other systems respond to it properly. In 
additional any VMWare sessions I have open respond correctly. So I have the 
condition where all non-vmware applications in Ubuntu Hardy (all updates 
applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT 
applications within an active (a paused/restarted session also works) VMWare 
sessions running DO recognize the key.

  When this condition occurs ALL applications (except those within a
  VMWare session) are also unstable and will usually crash within a few
  keystrokes.If I continue to operate in this mode. I cannot pinpoint
  what, if any, application triggers this. It has always happened while
  working within terminal/browser/vmware sessions and NOT when opening a
  new application. It could be related to the KVM switch, but none of my
  other systems (2 Mandriva, 1 Windows) are affected by this.

  This bug has been present on my system for a number of days across
  daily updates and reboots (if the update requested it) and I think
  since I installed Hardy Alpha 1.

  A work around: log off and back on. A reboot/restart does not appear
  to be needed.

  Error logs show some unusual activity.

  --- MARK 
  ...
  ... kernel ... rtc lost 7 interrupts ...
  --- MARK ---
  

  Plus some segfaults indicating which application crashed as I tried to
  type into it (mouse works fine).

  System: HP dv9743cl (which otherwise works lovely)
  Ubuntu: Hardy 8.04 (from lsb-release)

  
  TEST CASE:
  1. Click inside the VM and
 
  2. Hold any of the Ctrl, Alt and/or shift keys while releasing the 
keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt 
to revert back to windowed mode, as the cursor is then released from the VM). 

  WORKAROUND:
  After this happens to recover your keyboard execute 'setxkbmap' in a terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/195982/+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 1901358] ProcCpuinfoMinimal.txt

[Gary Cameron]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1901358/+attachment/5427267/+files/ProcCpuinfoMinimal.txt

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2018-08-26 (792 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Tags:  ulyana
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1901358] PulseList.txt

[Gary Cameron]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1901358/+attachment/5427269/+files/PulseList.txt

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2018-08-26 (792 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Tags:  ulyana
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1901358] ProcEnviron.txt

[Gary Cameron]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1901358/+attachment/5427268/+files/ProcEnviron.txt

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2018-08-26 (792 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Tags:  ulyana
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1901358] Re: [System Settings] :Sound - 5.1 audio outputs are reported as Headphones

[Gary Cameron]

apport information

** Tags added: apport-collected ulyana

** Description changed:

  [System settings] Sound
  
  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard
  
  5.1 Audio outputs are only usable as stereo by selecting "Headphones USB
  Audio", which means only the front right and left speaker work.
  
  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.
  
  Ubuntu release 20.04
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.10
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20
+ InstallationDate: Installed on 2018-08-26 (792 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: alsa-driver (not installed)
+ ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
+ Tags:  ulyana
+ Uname: Linux 5.4.0-52-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 06/05/2020
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1101
+ dmi.board.asset.tag: Default string
+ dmi.board.name: ROG ZENITH II EXTREME ALPHA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1901358/+attachment/5427264/+files/AlsaInfo.txt

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2018-08-26 (792 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Tags:  ulyana
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1901358] CurrentDmesg.txt

[Gary Cameron]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1901358/+attachment/5427266/+files/CurrentDmesg.txt

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2018-08-26 (792 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Tags:  ulyana
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1901358] AudioDevicesInUse.txt

[Gary Cameron]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1901358/+attachment/5427265/+files/AudioDevicesInUse.txt

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2018-08-26 (792 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Tags:  ulyana
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1901358] [NEW] [System Settings] :Sound - 5.1 audio outputs are reported as Headphones

[Gary Cameron]

Public bug reported:

[System settings] Sound

ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

5.1 Audio outputs are only usable as stereo by selecting "Headphones USB
Audio", which means only the front right and left speaker work.

When I select "Speakers USB Audio" they do not work at all, neither as
stereo or 5.1 audio.

Ubuntu release 20.04

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

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901358/+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 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3

[Gary Potwin]

Doing the usual Ubuntu operating system updates, we are now up to
18.04.4. Epson came out with a new driver (3.63), as opposed to the 2
previous drivers mentioned above. 3.63 works just fine, so it looks as
though it just wouldn't work with the previous 2 drivers. So it looks as
though this problem is solved, but I don't know how to mark this
question as solved. I'm going to make this same entry in the question
(687949) that I started on this problem, and try to close it out also.

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

Title:
  New Epson V19 scanner problems under Ubuntu 18.04.3

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Bought new Epson V19 scanner, and it works fine on my wife's computer
  running Windows 7, and also on my computer running Windows XP.
  Rebooted my computer into Ubuntu 18.04.3, and installed the driver
  packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64
  bit, release date 12-26-2019) using their install.sh file with the
  without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650
  1.0.2, and imagescan-plugin-ocr-engine 1.0.2).  Looking at these
  packages using Aptitude, it appears that they are installed OK with no
  missing dependencies.  Imagescan (on the graphical desktop) appears to
  find the scanner, and when you click to scan, you can hear the scanner
  seeming to run normally, but no image is produced at the end.  Using
  the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to
  work fine for finding the scanner.  But when I try scanimage -T, no
  image file is produced, although you can hear the scanner appearing to
  do a normal scan.  So it appears that all the control functions are
  working fine, but the problem is getting the scan data.  I also tried
  the suggestions in this video
  (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04
  scanner problems how to fix them" concerning bug 1728012.  In the end,
  nothing appears to have changed, so it appears I didn't make it any
  better or any worse.  Any help would be greatly appreciated, including
  referring me to another place if I'm not posting in the right place
  yet.  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+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 1877784] [NEW] libreoffice help does not work

[Gary Johnson]

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

Public bug reported:

New installation of Ubuntu 20.04. LibreOffice Calc seems to work fine, but when 
I click on Help, I get the message: Object not accessible. The object cannot be 
accessed due to insufficient user rights.
Ubuntu 20.04 LTC Release 20.04

LibreOffice Version: 6.4.3.2
Build ID: 1:6.4.3-0ubuntu0.20.04.1
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

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

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

Title:
  libreoffice help does not work

Status in libreoffice package in Ubuntu:
  New

Bug description:
  New installation of Ubuntu 20.04. LibreOffice Calc seems to work fine, but 
when I click on Help, I get the message: Object not accessible. The object 
cannot be accessed due to insufficient user rights.
  Ubuntu 20.04 LTC Release 20.04

  LibreOffice Version: 6.4.3.2
  Build ID: 1:6.4.3-0ubuntu0.20.04.1
  CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); UI-Language: en-US
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877784/+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 1868140] [NEW] package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[gary knott]

Public bug reported:

I think some configuration file for TeX needs 
to be completely replaced; maybe the post-processing script could offer 
that option instead of just complaining and exiting.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211
Uname: Linux 4.4.0-174-generic i686
ApportVersion: 2.20.1-0ubuntu2.22
Architecture: i386
Date: Thu Mar 19 12:49:14 2020
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-03-18 (2557 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: tex-common
Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2019-02-09 (404 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I think some configuration file for TeX needs 
  to be completely replaced; maybe the post-processing script could offer 
  that option instead of just complaining and exiting.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211
  Uname: Linux 4.4.0-174-generic i686
  ApportVersion: 2.20.1-0ubuntu2.22
  Architecture: i386
  Date: Thu Mar 19 12:49:14 2020
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-03-18 (2557 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: tex-common
  Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-02-09 (404 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1868140/+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 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3

[Gary Potwin]

I followed the instructions in #2 above regarding FindRightPackage, and
it printed sane-utils on my terminal regarding the scanimage command.
Aptitude shows that the sane-utils package is indeed installed.  But
when I tried to follow the instructions in +editstatus, it refused the
sane-utils entry saying that Ubuntu has no such package.  It suggested
the sane-backends package, so I put that in only because it allowed
that.  Thank you in advance for any help.

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

Title:
  New Epson V19 scanner problems under Ubuntu 18.04.3

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Bought new Epson V19 scanner, and it works fine on my wife's computer
  running Windows 7, and also on my computer running Windows XP.
  Rebooted my computer into Ubuntu 18.04.3, and installed the driver
  packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64
  bit, release date 12-26-2019) using their install.sh file with the
  without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650
  1.0.2, and imagescan-plugin-ocr-engine 1.0.2).  Looking at these
  packages using Aptitude, it appears that they are installed OK with no
  missing dependencies.  Imagescan (on the graphical desktop) appears to
  find the scanner, and when you click to scan, you can hear the scanner
  seeming to run normally, but no image is produced at the end.  Using
  the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to
  work fine for finding the scanner.  But when I try scanimage -T, no
  image file is produced, although you can hear the scanner appearing to
  do a normal scan.  So it appears that all the control functions are
  working fine, but the problem is getting the scan data.  I also tried
  the suggestions in this video
  (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04
  scanner problems how to fix them" concerning bug 1728012.  In the end,
  nothing appears to have changed, so it appears I didn't make it any
  better or any worse.  Any help would be greatly appreciated, including
  referring me to another place if I'm not posting in the right place
  yet.  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+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 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3

[Gary Potwin]

** Package changed: ubuntu => sane-backends (Ubuntu)

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

Title:
  New Epson V19 scanner problems under Ubuntu 18.04.3

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Bought new Epson V19 scanner, and it works fine on my wife's computer
  running Windows 7, and also on my computer running Windows XP.
  Rebooted my computer into Ubuntu 18.04.3, and installed the driver
  packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64
  bit, release date 12-26-2019) using their install.sh file with the
  without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650
  1.0.2, and imagescan-plugin-ocr-engine 1.0.2).  Looking at these
  packages using Aptitude, it appears that they are installed OK with no
  missing dependencies.  Imagescan (on the graphical desktop) appears to
  find the scanner, and when you click to scan, you can hear the scanner
  seeming to run normally, but no image is produced at the end.  Using
  the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to
  work fine for finding the scanner.  But when I try scanimage -T, no
  image file is produced, although you can hear the scanner appearing to
  do a normal scan.  So it appears that all the control functions are
  working fine, but the problem is getting the scan data.  I also tried
  the suggestions in this video
  (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04
  scanner problems how to fix them" concerning bug 1728012.  In the end,
  nothing appears to have changed, so it appears I didn't make it any
  better or any worse.  Any help would be greatly appreciated, including
  referring me to another place if I'm not posting in the right place
  yet.  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+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 1689653] Re: Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

I haven't seen this problem for quite a while. I guess it did get fixed
by accident or by intention at some point.

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

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)

[Gary]

I fixed it by adding a few lines in my /etc/default/grub file! (not sure which 
exactly which one of the 3 fixed it)
In the line (GRUB_CMDLINE_LINUX_DEFAULT=) I added to the quotes: iommu=soft 
processor.max_cstate=5 idle=nomwait
If anyone can explain what they each do/which ones are necessary that would be 
great as well (if it also fixes it for other people)!

I found these commands from:
https://forum.manjaro.org/t/amd-ryzen-problems-and-fixes/55533
https://www.reddit.com/r/Amd/comments/apw8im/ryzen_freezes_in_linux_even_if_linux_is_in_vm/
https://askubuntu.com/questions/1181819/ubuntu-keeps-crashing-on-huawei-matebook-d-ryzen-5-2500u

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

Title:
  [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
  2500u (Raven Ridge)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous window 
appear in the newly opened window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-08 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+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 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

[Gary Wright II]

Seeing same problem on my xubuntu machine after upgrade to 19.10. I
tried different GDM's (xubuntu, gnome, xfce) and tried different themes
(default, Adwaita, Breeze, DMZ). I have basic Intel graphics card with
minimal capabilities, and machine is used in production so I'm unable to
experiment much further. Logitech trackball mouse. I don't see anything
obvious in logs. Everything was working properly prior to upgrade. I'm
able to use the mouse to select and click, just no cursor is being
display so it's hard to see where the pointer is located. I'm assuming
this problem is related to this bug.

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : 

[Desktop-packages] [Bug 1844775] Re: HDR support for Ubuntu

[Gary Wang]

** Changed in: weston (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu

[Gary Wang]

HDR i915 for Gfx-Gen9 in CFL/CML: Reviewing in upstream 
(https://patchwork.kernel.org/patch/11204583/)
[v2,0/6] Enable HDR on MCA LSPCON based Gen9 devices
[v2,1/6] drm/i915/display: Add HDR Capability detection for LSPCON
[v2,2/6] drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon
[v2,3/6] drm/i915/display: Attach HDR property for capable Gen9 devices
[v2,4/6] drm/i915/display: Set HDR Infoframe for HDR capable LSPCON devices
[v2,5/6] drm/i915/display: Enable BT2020 for HDR on LSPCON devices
[v2,6/6,NOT,FOR,MERGE] drm/i915/display: Reduce blanking to support 4k60@10bpp 
for LSPCON

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu

[Gary Wang]

For #15, 
Sorry for causing you confusion, just put related HDR patch of Gemini Lake for 
your reference. 

The patch for GLK were in i915 upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc4=44b42ebfccfd9d6ef377a25e99ae0085b071e868

Gary

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu

[Gary Wang]

For related commits of i915's HDR support with Gemini Lake,
https://github.com/freedesktop/drm-tip/c...85b071e868
https://patchwork.freedesktop.org/series/25091/#rev15

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

[Gary Wang]

Hi Timo and Daniel (@vanvugt),
Any plan for enabling HDR in part of X.org? Thanks!

Gary

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

Title:
  HDR support for Ubuntu 20.04

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

[Gary Wang]

I also put information for HDR feature in media's software stack
(ffmpeg/libva/iHD driver(media-driver)/

intel's video codec with HDR is enabled in Linux media stack for transcoding, I 
list the code commits of media libraries related to HDR for reference,
FFmpeg 
https://github.com/FFmpeg/FFmpeg/commit/38a413213216fc7add112f67e26326492c859c08
Libva
https://github.com/intel/libva/commit/cf11abe5e1b9c93ee75cf974076957162c1605b9
intel's iHD driver
https://github.com/intel/media-driver/commit/7e0ebbc794e83202808f6404f20f2a41c32a181d

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

Title:
  HDR support for Ubuntu 20.04

Status in intel-media-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1844775/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

[Gary Filipski]

Tested bionic-proposed with both original VM that exhibited the problem
on upgrade and a separate VM used to test the work-around (uncommenting
WaylandEnable=false in /etc/gdm3/custom.conf).

Both VMs upgraded and ran successfully using
https://wiki.ubuntu.com/Testing/EnableProposed.

-

# First test w/older VM that first exhibited the problem...

# [ No network card present ]
# Booted from old, saved VM where update first screwed up:

$ uname -a
Linux linuxTest 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

# Added bionic-proposed repository in update / developer options
# [ Enabled network card for VM ]
# Updated to current; restarted
# Booted & logged in normally

$ uname -a
Linux linuxTest 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

# Yea!

-

# Second test with VM used for later testing of the problem...

# [ No network card present ]
# Re-tested with more recent problem VM...
# Removed fix in /etc/gdm3/custom.conf (re-commented WaylandEnable=false)
# Booted to watch login hang
# {Shift} boot w/Grub in recovery mode to recovery mode menu; resumed startup.
# Logged in (desktop @800x600); re-set desktop width

$ uname -a
Linux Linux linuxTest 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

# Added bionic-proposed repository in update / developer options
# [ Enabled network card for VM ]
# Updated to current; restarted
# Booted & logged in normally

$ uname -a
Linux linuxTest 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

# Yea!

-

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a 

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

[Gary Filipski]

Additional confirmation...

Working under VMware Workstation v12.5.7 running kernel 4.15.0.52:

Having performed the workaround of uncommenting the
WaylandEnable=false...

   - Re-commented the line & rebooted to experience the hang with the
Ubuntu logo before the login screen

   - Using your ppa, installed the test kernel.

   - Rebooted.

Login proceeded normally: Linux linuxTest 4.15.0-53-generic
#57+hf231164v20190620b11-Ubuntu SMP Thu Jun 20 13:18:41 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux

Thank you!

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  

[Desktop-packages] [Bug 1815269] [NEW] package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[gary knott]

Public bug reported:

upgrade fron 14.04 to 16.04  and part of TeX fails to install!!  The complaint 
presented is script related to package tex-common 6.04unbuntu1 returns an error 
code of 1.

No idea what to do about it?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Fri Feb  8 20:06:31 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-03-18 (2153 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29ubuntu0.1
SourcePackage: tex-common
Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2019-02-09 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  upgrade fron 14.04 to 16.04  and part of TeX fails to install!!  The 
complaint 
  presented is script related to package tex-common 6.04unbuntu1 returns an 
error code of 1.

  No idea what to do about it?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Fri Feb  8 20:06:31 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-03-18 (2153 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: tex-common
  Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-02-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1815269/+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 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04

[Gary Caine]

I am getting the same error as Ricardo

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

Title:
  [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  nvidia-304 is not available in the Ubuntu 18.04. Newer versions are
  available but I have an old nVidia 7600 GT, so I need 304.137.

  I searched online and found that at
  https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2
  it has Status: Deleted :(

  Could you please pack this for the new release of Ubuntu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1763648/+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 1759096] [NEW] package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Gary Young]

Public bug reported:

upgrade 16.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: fontconfig 2.11.94-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Mar 26 17:38:43 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-06-08 (656 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to artful on 2018-03-27 (0 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  upgrade 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: fontconfig 2.11.94-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 26 17:38:43 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-06-08 (656 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to artful on 2018-03-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1759096/+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 1689653] Re: Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

Still occurring in latest Ubuntu. Using Xfce4 desktop with Xfwm4 window
manager. Previous reference to fvwm may be bogus.

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

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1729938] [NEW] package libx11-doc 2:1.6.4-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Gary Pinsky]

Public bug reported:

crashed

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libx11-doc 2:1.6.4-3
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Nov  3 17:06:23 2017
Dependencies:
 
DistUpgraded: 2017-10-25 21:46:58,559 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
DistroCodename: zesty
DistroVariant: ubuntu
DpkgHistoryLog:
 Start-Date: 2017-11-03  17:06:23
 Commandline: apt-get install apt-transport-https
 Requested-By: gary (1000)
DpkgTerminalLog:
 dpkg: error processing package libx11-doc (--configure):
  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
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family 
Integrated Graphics Controller [1179:fcd0]
InstallationDate: Installed on 2017-07-10 (116 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: TOSHIBA Satellite L745
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=d1d5ae7f-47b1-4f8a-867b-ff6e4b1b30f8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: libx11
Title: package libx11-doc 2:1.6.4-3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to zesty on 2017-10-26 (8 days ago)
dmi.bios.date: 05/17/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr1.60:bd05/17/2011:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-01V00E:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L745
dmi.product.version: PSK0YU-01V00E
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
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.14-0ubuntu1
xserver.bootTime: Fri Nov  3 16:38:19 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-package compiz-0.9 ubuntu zesty

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

Title:
  package libx11-doc 2:1.6.4-3 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libx11 package in Ubuntu:
  New

Bug description:
  crashed

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libx11-doc 2:1.6.4-3
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  3 17:06:23 2017
  Dependencies:
   
  DistUpgraded: 2017-10-25 21:46:58,559 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: zesty
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-11-03  17:06:23
   Commandline: apt-get install apt-transport-https
   Requested-By: gary (1000)
  DpkgTerminalLog:
   dpkg: error processing package libx11-doc (--configure):
package is in 

[Desktop-packages] [Bug 1689653] Re: Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

I guess nobody else has this bug, oddly enough, and if it ever gets
fixed, it will be by accident. Attached a screenshot.

** Attachment added: "Firefox at startup with a menu open."
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+attachment/4924400/+files/Screenshot%20from%202017-07-31%2009-42-12.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/1689653

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1689653] Re: Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

It still happens occasionally. The menus are still there, but invisible.
I wonder if it's a race condition involving loading of fonts.

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

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1689653] Re: Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

Now the problem has gone away. Or maybe it has become intermittent.

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

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1689653] Re: Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

I tried starting it as firefox --safe-mode mode instead. The problem
still exists, although it looks a little different, presumably because
the Menu Bar isn't enabled. It starts up without any space between the
title bar and the tabs. Right clicking above the tab gives the pop-up
menu but with Menu Bar, Bookmarks Toolbar and Customize greyed out.
Selecting Menu Bar produces some space where the Menu Bar would go, but
no menu bar. The option in the right-click menu then has a tick beside
it.

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

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1689653] [NEW] Firefox Menu Bar missing when starting up at fvwm login

[Gary Houston]

Public bug reported:

I'm using the Fvwm window manager. In the "Session and Startup" dialog,
I've added Firefox as an "Application Autostart", using the simple
command "firefox". This has previously worked fine, but since upgrading
to Ubuntu 17.04, Firefox starts up with the Menu Bar missing (below the
title bar). Non-active window tabs are also greyed out. It's 100%
reproducible. If I shut down Firefox and restart it, it works fine.

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

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

Title:
  Firefox Menu Bar missing when starting up at fvwm login

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm using the Fvwm window manager. In the "Session and Startup"
  dialog, I've added Firefox as an "Application Autostart", using the
  simple command "firefox". This has previously worked fine, but since
  upgrading to Ubuntu 17.04, Firefox starts up with the Menu Bar missing
  (below the title bar). Non-active window tabs are also greyed out.
  It's 100% reproducible. If I shut down Firefox and restart it, it
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1689653/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

I just installed 304.135 on 16.10 (not 16.04) and was able to log in

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1663737] Re: --execute changes following -h to --help

[Gary Filipski]

Egmont,

The man page for the version that I have does not mention '--' nor the fact
that the --execute
option is obsolete --- BUT!   ... the '--' option *does* work and functions
as desired with
the command-line you gave below...   the '-h' is echoed properly.

Thank you for taking the time to look into this.

The man page probably needs to be updated as even the 'Zesty' version still
shows the
--command and --execute options (and no '--') with the same description as
16.04 LTS.

Thanks,
Gary

PS: I've added this text as a comment to bug report.


On Sun, Feb 12, 2017 at 7:12 AM, Egmont Koblinger <egm...@gmail.com> wrote:

> Newest gnome-terminal declares the --execute/--command options obsolete,
> and states that a lone "--" followed by the arguments is the desired way
> to go. That one doesn't suffer for me in newest gnome-terminal (git
> snapshot). Could you please try this with your version, that is:
>
> gnome-terminal -- echoParams.sh -h
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1663737
>
> Title:
>   --execute changes following -h to --help
>
> Status in gnome-terminal package in Ubuntu:
>   New
>
> Bug description:
>   Description:  Ubuntu 16.04.1 LTS
>   Release:  16.04
>
>   gnome-terminal:
> Installed: 3.18.3-1ubuntu1
> Candidate: 3.18.3-1ubuntu1
> Version table:
>*** 3.18.3-1ubuntu1 500
>   500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64
> Packages
>   100 /var/lib/dpkg/status
>
>   Create a bash script called echoParams.sh somewhere in your current
>   path (attached):
>
>   #!/bin/bash
>   for param in "$@"
>   do echo "param '$param'"
>   done
>   echo -n "Enter to finish..."
>   read junk
>
>   Execute the following:
>
>   $ gnome-terminal --execute echoParams.sh -h
>
>   In a new terminal window the output is:
>
>   param '--help'
>   Enter to finish...
>
>   ... meanwhile, back at the command line:
>
>   $ which gnome-terminal
>   /usr/bin/gnome-terminal
>
>   $ gnome-terminal --version
>   GNOME Terminal 3.18.3
>
>
>   The '-h' is being translated and passed as '--help'
>
>   ... which is no help at all if the --execute command expects '-h'.
>
>   All puns intended.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bu
> g/1663737/+subscriptions
>


On Sun, Feb 12, 2017 at 7:12 AM, Egmont Koblinger <egm...@gmail.com> wrote:

> Newest gnome-terminal declares the --execute/--command options obsolete,
> and states that a lone "--" followed by the arguments is the desired way
> to go. That one doesn't suffer for me in newest gnome-terminal (git
> snapshot). Could you please try this with your version, that is:
>
> gnome-terminal -- echoParams.sh -h
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1663737
>
> Title:
>   --execute changes following -h to --help
>
> Status in gnome-terminal package in Ubuntu:
>   New
>
> Bug description:
>   Description:  Ubuntu 16.04.1 LTS
>   Release:  16.04
>
>   gnome-terminal:
> Installed: 3.18.3-1ubuntu1
> Candidate: 3.18.3-1ubuntu1
> Version table:
>*** 3.18.3-1ubuntu1 500
>   500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64
> Packages
>   100 /var/lib/dpkg/status
>
>   Create a bash script called echoParams.sh somewhere in your current
>   path (attached):
>
>   #!/bin/bash
>   for param in "$@"
>   do echo "param '$param'"
>   done
>   echo -n "Enter to finish..."
>   read junk
>
>   Execute the following:
>
>   $ gnome-terminal --execute echoParams.sh -h
>
>   In a new terminal window the output is:
>
>   param '--help'
>   Enter to finish...
>
>   ... meanwhile, back at the command line:
>
>   $ which gnome-terminal
>   /usr/bin/gnome-terminal
>
>   $ gnome-terminal --version
>   GNOME Terminal 3.18.3
>
>
>   The '-h' is being translated and passed as '--help'
>
>   ... which is no help at all if the --execute command expects '-h'.
>
>   All puns intended.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+
> bug/1663737/+subscriptions
>

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

[Desktop-packages] [Bug 1663737] Re: --execute changes following -h to --help

[Gary Filipski]

The man page for the version that I have does not mention '--' nor the fact 
that the --execute
option is obsolete --- BUT!   ... the '--' option *does* work and functions as 
desired with
the command-line you gave...   the '-h' is echoed properly.

Thank you for taking the time to look into this.

The man page probably needs to be updated as even the 'Zesty' version still 
shows the
--command and --execute options (and no '--') with the same description as 
16.04 LTS.

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

Title:
  --execute changes following -h to --help

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  gnome-terminal:
Installed: 3.18.3-1ubuntu1
Candidate: 3.18.3-1ubuntu1
Version table:
   *** 3.18.3-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Create a bash script called echoParams.sh somewhere in your current
  path (attached):

  #!/bin/bash
  for param in "$@"
  do echo "param '$param'"
  done
  echo -n "Enter to finish..."
  read junk

  Execute the following:

  $ gnome-terminal --execute echoParams.sh -h

  In a new terminal window the output is:

  param '--help'
  Enter to finish...

  ... meanwhile, back at the command line:

  $ which gnome-terminal
  /usr/bin/gnome-terminal

  $ gnome-terminal --version
  GNOME Terminal 3.18.3

  
  The '-h' is being translated and passed as '--help'

  ... which is no help at all if the --execute command expects '-h'.

  All puns intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1663737/+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 1663737] [NEW] --execute changes following -h to --help

[Gary Filipski]

Public bug reported:

Description:Ubuntu 16.04.1 LTS
Release:16.04

gnome-terminal:
  Installed: 3.18.3-1ubuntu1
  Candidate: 3.18.3-1ubuntu1
  Version table:
 *** 3.18.3-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

Create a bash script called echoParams.sh somewhere in your current path
(attached):

#!/bin/bash
for param in "$@"
do echo "param '$param'"
done
echo -n "Enter to finish..."
read junk

Execute the following:

$ gnome-terminal --execute echoParams.sh -h

In a new terminal window the output is:

param '--help'
Enter to finish...

... meanwhile, back at the command line:

$ which gnome-terminal
/usr/bin/gnome-terminal

$ gnome-terminal --version
GNOME Terminal 3.18.3


The '-h' is being translated and passed as '--help'

... which is no help at all if the --execute command expects '-h'.

All puns intended.

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

** Attachment added: "The echoParams.sh script listed in the bug description."
   
https://bugs.launchpad.net/bugs/1663737/+attachment/4816779/+files/echoParams.sh

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

Title:
  --execute changes following -h to --help

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  gnome-terminal:
Installed: 3.18.3-1ubuntu1
Candidate: 3.18.3-1ubuntu1
Version table:
   *** 3.18.3-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Create a bash script called echoParams.sh somewhere in your current
  path (attached):

  #!/bin/bash
  for param in "$@"
  do echo "param '$param'"
  done
  echo -n "Enter to finish..."
  read junk

  Execute the following:

  $ gnome-terminal --execute echoParams.sh -h

  In a new terminal window the output is:

  param '--help'
  Enter to finish...

  ... meanwhile, back at the command line:

  $ which gnome-terminal
  /usr/bin/gnome-terminal

  $ gnome-terminal --version
  GNOME Terminal 3.18.3

  
  The '-h' is being translated and passed as '--help'

  ... which is no help at all if the --execute command expects '-h'.

  All puns intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1663737/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Seems 0ubuntu1 is in Zesty see https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/+bug/1634802/comments/32

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

OK I thought I saw that it was 304.134-0ubuntu1 that fixed it in 16.04

Anyway 304.134-0ubuntu0.16.10.1 is causing the login loop on my system

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Already did, but just tried again. Still get login loop

According to what I've seen it's

304.134-0ubuntu1.16.10.1 not 304.134-0ubuntu0.16.10.1 that fixed the
problem in 16.04

Note the 0ubuntu1 not 0ubuntu0

If i try to load 304.134-0ubuntu1.16.10.1 I get this mesage  E: Version
'304.134-0ubuntu1.16.10.1' for 'nvidia-304' was not found

Note 0ubuntu1 not availaible just 0ubuntu0

Trying 0ubuntu1 gives this message E: Version '304.134-0ubuntu1.16.10.1'
for 'nvidia-304' was not found

Nouveau "sort of" works but I get a freeze up with diagonal lines
occasionally

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

yes the problem is in 16.10 Yakkety

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

I just tried installing Nvidia again and still same login loop problem.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Just reread your message it's version 304.134-unbuntu1 that fixed the
problem in 16.104 not 304.132

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

What is availble in 16.10 is -0ubuntu0 not -0ubuntu1

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

I have

NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)

with 16.10 nvidia-304 304.134-0ubuntu1 isn't available just nvidia-304
304.134-0ubuntu0 which still cause the login loop

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

I agree it's not solved on 16.10

I believe there is an open bug about it on 16.10 but I can't find it.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1631191] Re: Display backlight won't turn on after screen timeout

[Gary Herron]

As of today, Jan 5, 2017, 375.26 *is* now in the Ubuntu repositories,
and it does indeed solve this backlight problem.

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

Title:
  Display backlight won't turn on after screen timeout

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Using nVidia driver 367.44 on Skylake Intel Processors, with 1000
  series graphics, the backlight won't turn on after turned off by gnome
  session idle delay (org.gnome.desktop.session idle-delay). or by `xset
  dpms force off`

  Resume from suspend is unaffected.

  This is on a clean install of 16.10 with the 367.44 nVidia driver.
  This is a regression from the 367.35 driver.  367.48 and 370.28 also
  exhibit this behavior.

  This is confirmed on the following hardware:

  Oryx Pro 2 (oryp2) i7-6700HQ with 1070
  Serval 10 (serw10) i7-6700 with 1060
  Bonobo 11 (bonw11) i7-6700K with dual 1070

  Steps to reproduce:

  1. Install a fresh image of Yakkety and 367.44 from the graphics driver 
team's PPA.
  2. Log in to Unity shell
  3. Lock screen and wait for dimming.
  4. Move the mouse to 'resume'
  5. The screen will turn on, but the backlight is still off

  The current workaround:

  1. Hit tty1 (Ctrl+Alt+F1)
  2. Hit tty7 (Ctrl+Alt+F7)

  This will bring Unity back to life.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.44-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  6 16:17:11 2016
  SourcePackage: nvidia-graphics-drivers-367
  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-367/+bug/1631191/+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 1637652] Re: stucked in a login loop

[Gary Caine]

Sorry I mis read the report.

I am getting the login loop with nvidea 304 not 340

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

Title:
  stucked in a login loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after 16.10 upgrade I cannot login into the graphical interface

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Oct 28 23:40:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
  InstallationDate: Installed on 2012-03-13 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: Z68XP-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd02/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Oct 28 23:29:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 8
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637652/+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 1637652] Re: stucked in a login loop

[Gary Caine]

I am also getting the login loop with nvidia-304.134

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

Title:
  stucked in a login loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after 16.10 upgrade I cannot login into the graphical interface

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Oct 28 23:40:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
  InstallationDate: Installed on 2012-03-13 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: Z68XP-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd02/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Oct 28 23:29:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 8
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637652/+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 1634802] Re: Could not insert module

[Gary Caine]

I still have the login loop with 4.8.0-32-generic GNU/Linux after
installing 304.134

At https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304/+bug/1639180

it seems that the bug for 16.04 was fixed in the package nvidia-
graphics-drivers-304 - 304.134-0ubuntu1

However in 16.10 the latest version is nvidia-graphics-drivers-304 -
304.134-0ubuntu0

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

Title:
  Could not insert module

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged

Bug description:
  Ubuntu release: 16.10 Yakkety Yak
  Kernel version: 4.8.0-22-generic x86_64
  Package version: 304.132-0ubuntu1

  The nvidia module cannot be loaded. The following errors are reported:
  Could not insert module Unknown symbol in module

  and:

  nvidia: Unknown symbol mtrr_del (err 0)
  nvidia: Unknown symbol mtrr_add (err 0)

  It looks like the buildfix_kernel_4.3.patch, which is supposed to be
  dealing with those calls, is not applied in this release of the
  package.

  The package was working fine with the previous fully updated Ubuntu
  version 16.04 prior to the upgrade to 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Oleksandr

OK I tried both.

Actually I had already downloaded the 131 package from (I think it was)
launchpad.

So I tried both again.

I can use Nouveau for now. Problem is I never know if it's going to
freeze with horz lines.

Is there a way to know when nvidia get's fixed in 16.10 so I can install
it?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Thanks for suggestions - don't know if I will get a chance to try in
next few days.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

dino99

If you are referring to doing

sudo add-apt-repository ppa:graphics-drivers/ppa

then

sudo apt-get update

I did that a few times

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

I wonder if it's because I upgraded to 16.10 on Saturday?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

If I do sudo apt-get install nvidia-304=304.131-0ubuntu3
I get
Version '304.131-0ubuntu3' for 'nvidia-304' was not found

If I try sudo apt-get install nvidia-304=304.134-0ubuntu1

I get
Version '304.134-0ubuntu1' for 'nvidia-304' was not found

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Oleksandr

yes I put = after nvidia-304

Here's the outup

nvidia-304:
  Installed: (none)
  Candidate: 304.134-0ubuntu0.16.10.1
  Version table:
 304.134-0ubuntu0.16.10.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main 
amd64 Packages
100 /var/lib/dpkg/status
 304.132-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu yakkety/restricted amd64 Packages
N: Ignoring file 'local-nvidia-quirks.bk' in directory 
'/etc/apt/preferences.d/' as it has an invalid filename extension

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

OK I did
sudo add-apt-repository ppa:graphics-drivers/ppa 
sudo apt-get update.

Now I have nvidia-304 304.1343-0ubuntu0 showing up in Synaptic

I don't have
nvidia-304 304.1343-0ubuntu1

nor is version 131 showing up

In Software and Updates I selected Main Server and reloaded

Maybe I just have to wait until nvidia-304 304.1343-0ubuntu1 becomes
available here?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Correction

I have
I don't have
nvidia-304 304.134-0ubuntu0 available

I don't have
nvidia-304 304.134-0ubuntu1

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

No I just typed it wrong in the message.

As I said even synapthic can't find it.

It can't find 304.134 now either.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

Oleksandr

What I mean is I get a message saying it can't find 131-0ubuntu3 . I
tried a couple of different mirrors.

If i open Synapthic I see a few different versions of NVidea but not
that one.

I see it's supposed to be fixed now. Hopefully I will get a chance to
try it today.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

[Gary Caine]

nvidia-304.134 didn't work for me with gforce 7025/mForce 630A (rev a2)

Also I can't get apt-get to find 304.131 any suggestions on that?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 654323] Re: [VIA VT1708S] ALSA test tone not correctly played back. Cannot unmute. Get brief burst of sound then it remutes without my taking any action

[Gary Houston]

I haven't seen this bug for several years. It should probably just be
closed as stale.

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

Title:
  [VIA VT1708S] ALSA test tone not correctly played back. Cannot unmute.
  Get brief burst of sound then it remutes without my taking any action

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On unticking mute I get a brief burst of sound, then it remutes. I'm
  using 10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 1/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1671 F pulseaudio
   /dev/snd/pcmC0D0p:   john   1671 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xf7ff8000 irq 22'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11064397,18490397,0010'
 Controls  : 24
 Simple ctrls  : 15
  CurrentDmesg: [   22.736355] eth0: no IPv6 routers present
  Date: Mon Oct  4 01:11:41 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SelectedCard: 0 NVidia HDA-Intel - HDA NVidia
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [VIA VT1708S] ALSA test tone not correctly played back
  dmi.bios.date: 05/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: N68C-S UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/27/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/654323/+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 1635005] Re: xubuntu 16.10 freezes when trying to print

[Gary Houston]

It's probably bug #1630063. The system seems to lock up because the
keyboard and/or mouse are plugged into the same USB hub as the printer.
If you can plug them differently, only the printer will lock up. Running
"lsusb" in a terminal will show which hub the devices are connected to.
If you can still type after a lockup, then the typing "dmesg" in a
terminal may show ohci-pci errors.

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

Title:
  xubuntu 16.10 freezes when trying to print

Status in cups package in Ubuntu:
  New

Bug description:
  Premise: before the upgrade, the system was at version 16.04 and I had no 
problems with the printer.
  Some days ago I upgraded my os (xubuntu) through the upgrade screen.
  I haven' t found any bugs or problems, until I haven't tried to print a 
document. At first I tried from chromium, I started the printer and, just 
started the process, the printer has stopped. By controlling the computer, I 
realized I could no longer do anything, the pc was completely frozen (no access 
to the mouse, the keyboard seemed turned off and there was no change on the 
screen).
  Rebooting from the reset button, the pc is back fully operational, without 
giving any error message after login. I tried to print directly from local, 
downloading the document, and it happened the same. Searching around I cannot 
find anyone that suffer these problems after the upgrade.

  The printer is an hp 1110 psc installed and connected via usb.

  Tecnical information:

  Description:  Ubuntu 16.10
  Release:  16.10

  cups:
    Installed: 2.2.0-2
    Candidate:  2.2.0-2
    Version table:
   *** 2.2.0-2 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CupsErrorLog:

  CurrentDesktop: XFCE
  Date: Wed Oct 19 20:19:48 2016
  InstallationDate: Installed on 2016-04-24 (177 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for psc-1100-series: 
hp:/usb/psc_1100_series?serial=MY36E1614SB0
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/psc-1100-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/psc-1100-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=9b6816f1-3435-4096-a661-6dfdc791b7af ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (4 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.asset.tag: BC5FF4C28047
  dmi.board.name: 960GM-VGS3 FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1635005/+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 1514474] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gary Eitel]

This doesn't mean much to me---all I know is that when I clicked the 
"upgrade" button when I was notified of the newer 16.04 version that was 
available, it didn't finish installing and kept asking me for passwords 
before anything would boot as such.  I entered my user and root 
passwords and kept getting the message saying it was the wrong password.

Have finally bought a new hard drive and taken it to a Tech to hopefully 
get running again but likely have lost all my files. Previous years I 
had upgraded from version 11, 12, and to 14 with no problems---it needs 
to be made more foolproof somehow.  Been running Ubuntu for at least 5 
yrs and like it

Gary


On 08/11/2016 02:30 PM, Alberto Salvia Novella wrote:
> ** Changed in: tex-common (Ubuntu)
> Importance: Undecided => High
>

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  dist-upgrade from wily to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  Date: Mon Nov  9 09:56:09 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-12 (1580 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+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 1610621] [NEW] tried to upgrade to version 16.04 but something went wrong and having problems getting started back up---won't accept passwords and wasn't able to get into BIOS,

[Gary Eitel]

Public bug reported:

Is the 3rd party driver security option necessary to be turned on or off at my 
end for the best operation?
Am using the upgraded 16.04LT from 14.04LT on an AMD 64 bit system  The 14.04 
was working great until the upgrade tried to happen.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Aug  5 13:58:24 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-09-27 (1044 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tex-common (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 tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1610621

Title:
  tried to upgrade to version 16.04 but something went wrong and having
  problems getting started back up---won't accept passwords and wasn't
  able to get into BIOS, etc.  will keep trying at this end.  Was having
  trouble with the 3rd party driver on/off part and now asking for the
  ADM password before all starts up.  package tex-common 6.04 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Is the 3rd party driver security option necessary to be turned on or off at 
my end for the best operation?
  Am using the upgraded 16.04LT from 14.04LT on an AMD 64 bit system  The 14.04 
was working great until the upgrade tried to happen.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug  5 13:58:24 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-09-27 (1044 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1610621/+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 1409032] Re: gvfsd-smb: very high CPU utilisation

[Gary Turnbull]

Using Ubuntu 16.04. Issue effects me as well.

I implemented the suggestions in post #29 and #37.

When I open Files, gvfsd-smb-browse maxes out one core at 100% for about
10 minutes.

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

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in gvfs package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+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 1608954] Re: Performance degradation caused by libica2 library

[Gary Gaydos]

** Package changed: libical (Ubuntu) => libica (Ubuntu)

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

Title:
  Performance degradation caused by libica2 library

Status in libica package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Bastian Pfeifer  - 2016-07-29 
09:07:47 ==
  ---Problem Description---
  'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
   
  A patch is already upstream and can be found under this commit:
  
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

  It will fix the issue + we will get a great performance improvement
  for the RSA encryption via opencryptoki's ICA-TOKEN.

  Contact Information = bastian.pfei...@de.ibm.com 
   
  ---uname output---
  Linux s42lp26 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:14:29 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = 2964, 701 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   na
   
  Userspace tool common name: libica version 2.6.1 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: libica2:s390x

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for bastian.pfei...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #2 - Ingo Tuchscherer  -
  2016-08-01 06:53:45 ==

  
  == Comment: #3 - Heinz-Werner Seeck  - 
2016-08-02 08:19:23 ==
  'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
   
  A patch is already upstream and can be found under this commit:
  
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

  Also attached to this bugzilla !

  It will fix the issue + we will get a great performance improvement
  for the RSA encryption via opencryptoki's ICA-TOKEN.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1608954/+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 449910] Re: Certain notification area icons are invisible

[Gary Sawyer]

I see this intermittently (about every other boot) since updating Ubuntu
GNOME to Xenial, but only on the Autokey notification icon. I work-
around by re-booting as often as necessary.

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

Title:
  Certain notification area icons are invisible

Status in gnome-panel package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-panel

  Since more than a week some notification icons are not shown anymore - namely 
volume, display settings, network, empathy.
  Strange thing is - they area reacts normally to mouse actions - but it just 
doesn't show the icons.

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Oct 12 23:57:26 2009
  DistroRelease: Ubuntu 9.10
  Package: gnome-panel 1:2.28.0-0ubuntu4
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
  SourcePackage: gnome-panel
  Uname: Linux 2.6.31-13-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/449910/+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 1570921] Re: suspend not working

[Gary Holmlund]

I am having the same issue. I first tried with Ubuntu Gnome 16.04 and
then with Ubuntu 16.04. Both have the same issue.  Doing "sudo pm-
hibernate" can duplicate the issue. I am attaching a report from lshw.
My computer is a HP Pavilion dv7.


** Attachment added: "lshw output for HP Pavilon dv7"
   
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1570921/+attachment/4643129/+files/hw

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

Title:
  suspend not working

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  My computer cannot go to suspend state.  The monitor switch off but the 
cpu/cpu fan keeps running and the hard drive is active.
  It doesn't respond, I need to switch off manually to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 15 18:42:49 2016
  InstallationDate: Installed on 2016-04-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1570921/+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 196058] Re: Thunderbird starts in a full-screen mode and cannot be restored

[Gary B]

Marco's note was the key for me.  In my case some conflict between
Compiz and Mate caused my desktop to go completely crazy.  One of the
effects was to make every application go full screen.  After cleaning up
the mess, all the apps went back to more-or-less normal but Thunderbird.
I had already tried the localstore.rdf method without success.  But
Marco's note about using xulstore.json did the trick!

Until then, while I tried to get this working, the only way I could get
to my Panel was by hitting F12, which brought up the miniterminal and
coincidentally showed the Panel.  But then I could only minimize
Thunderbird. (And I ended up with a dozen or so miniterminal windows...)
The right-click options on the Thunderbird button in the task list did
not show Thunderbird as maximized.  So the easiest thing was to just use
File->exit in Thunderbird each time I tried things.

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

Title:
  Thunderbird starts in a full-screen mode and cannot be restored

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND:
  1. Edit ~/.thunderbird/*/xulstore.json
  2. Search for:   "sizemode":"fullscreen"
  3. Change it to: "sizemode":"normal"

  OLD WORKAROUND:
  1. Edit ~/.thunderbird/*/localstore.rdf
  2. Search for:   sizemode="fullscreen"
  3. Change it to: sizemode="normal"

  ORIGINAL DESCRIPTION:
  Binary package hint: thunderbird

  I've tried clicking F11 in various of places and even all the rest of
  F-buttons, with Alt/Shift/Ctrl, and still no result. I've scrolled
  throughout the whole advanced configuration and there was nothing
  about full-screen mode. I don't have any extensions yet installed on
  my Thunderbird and I don't know what to do next.

  The problem has it basics because the profile that I've switched to,
  comes from previous Windows installation.

  I'm begging for Your help. It is stupid but really frustrating.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Feb 27 10:05:55 2008
  Dependencies:

  DistroRelease: Ubuntu 8.04
  Package: mozilla-thunderbird None [modified: 
/var/lib/dpkg/info/mozilla-thunderbird.list]
  PackageArchitecture: allSourcePackage: thunderbird
  Uname: Linux 2.6.24-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/196058/+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 1131571] Re: Nautilus properties window "Content" number continuously counting

[Gary]

Has this been fixed, because I keep my machines up-to-date and it is
still happening.  It is really frustrating.

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

Title:
  Nautilus properties window "Content" number continuously counting

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  1. Press Ctrl H in your home directory
  2. Selected all files inclusing hidden files
  3. Right-click > Properties

  Result:
  Size keeps shifting (does not end counting). Can't find out the size of the 
selected files/folders.

  Expected:
  Ends counting with the size of the selected files/folders.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 22 00:59:57 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1290x831+1+52'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'219'
  InstallationDate: Installed on 2012-12-31 (53 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121230)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2013-01-01T18:32:27.165937

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1131571/+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 1503318] [NEW] PDF Not Rendering Properly

[Gary Helbig]

Public bug reported:

Display errors reading PDFs on the web

Oh, and this page (bug reporting page) no longer works properly in
FireFox - the scrolling is "wrong", bad wrong.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 41.0+build3-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-90.128-generic 3.2.69
Uname: Linux 3.2.0-90-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ghelbig2391 F pulseaudio
BuildID: 20150918100339
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21'
   Mixer name   : 'Nvidia MCP77/78 HDMI'
   Components   : 'HDA:10ec0888,10250153,00100202 
HDA:10de0002,10de0101,0010'
   Controls  : 42
   Simple ctrls  : 20
Channel: Unavailable
Date: Tue Oct  6 07:46:47 2015
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
IncompatibleExtensions:
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
IpRoute:
 default via 192.168.1.1 dev eth0  proto static 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.151  metric 1
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MarkForUpload: True
MostRecentCrashID: bp-46d3fe82-a101-4256-8fb0-8b75a2150413
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=41.0/20150918100339 (In use)
RelatedPackageVersions:
 gnome-shell   3.4.1-0ubuntu2
 totem-mozilla 3.0.1-0ubuntu21.1
 adobe-flashplugin 1:20150921.1-0precise1
RfKill:
 0: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-46d3fe82-a101-4256-8fb0-8b75a2150413
UpgradeStatus: Upgraded to precise on 2015-09-29 (6 days ago)
WifiSyslog:
 
dmi.bios.date: 08/28/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: P01-A0
dmi.board.name: WMCP78M
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrP01-A0:bd08/28/2009:svnAcer:pnAspireX1301:pvr:rvnAcer:rnWMCP78M:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire X1301
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug precise

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

Title:
  PDF Not Rendering Properly

Status in firefox package in Ubuntu:
  New

Bug description:
  Display errors reading PDFs on the web

  Oh, and this page (bug reporting page) no longer works properly in
  FireFox - the scrolling is "wrong", bad wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 41.0+build3-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-90.128-generic 3.2.69
  Uname: Linux 3.2.0-90-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ghelbig2391 F pulseaudio
  BuildID: 20150918100339
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21'
 Mixer name : 'Nvidia MCP77/78 HDMI'
 Components : 'HDA:10ec0888,10250153,00100202 
HDA:10de0002,10de0101,0010'
 Controls  : 42
 Simple ctrls  : 20
  Channel: Unavailable
  Date: Tue Oct  6 07:46:47 2015
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.151  metric 
1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MarkForUpload: True
  MostRecentCrashID: bp-46d3fe82-a101-4256-8fb0-8b75a2150413
  PrefSources: prefs.js
  ProcEnviron:
   

[Desktop-packages] [Bug 1492568] Re: Add new locale en_ID (Indonesian English)

[Gary Dean]

Thank you for your direction.

I have posted the request for the en_ID locale, which can be found at

https://sourceware.org/bugzilla/show_bug.cgi?id=19010




** Bug watch added: Sourceware.org Bugzilla #19010
   http://sourceware.org/bugzilla/show_bug.cgi?id=19010

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

Title:
  Add new locale en_ID (Indonesian English)

Status in langpack-locales package in Ubuntu:
  Incomplete

Bug description:
  Please see attached submission for a new locale for Indonesian English
  (en_ID).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1492568/+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 1492568] Re: Add new locale en_ID (Indonesian English)

[Gary Dean]

It is precisely this kind of combination that leads to all kinds of
inconsistency across systems within the country, or worse, users
defaulting to whatever English the machine was set up for and using
oddball date and time formats, and using inappropriate currency and
decimal setups, leading to confusion.

There is no satisfactory combination of existing locales (eg, en_US
language with id_ID region) that accommodate English language and region
settings.  In the case of decimals, for example, the convention in
Indonesian English is to use periods and not commas, as is the standard
for Indonesian language.

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

Title:
  Add new locale en_ID (Indonesian English)

Status in langpack-locales package in Ubuntu:
  Incomplete

Bug description:
  Please see attached submission for a new locale for Indonesian English
  (en_ID).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1492568/+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 1492568] [NEW] Add new locale en_ID (Indonesian English)

[Gary Dean]

Public bug reported:

Please see attached submission for a new locale for Indonesian English
(en_ID).

** Affects: langpack-locales (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch

** Attachment added: "Indonesian English locale file (en_ID)"
   https://bugs.launchpad.net/bugs/1492568/+attachment/4457807/+files/en_ID

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

Title:
  Add new locale en_ID (Indonesian English)

Status in langpack-locales package in Ubuntu:
  New

Bug description:
  Please see attached submission for a new locale for Indonesian English
  (en_ID).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1492568/+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 1492568] Re: Add new locale en_ID (Indonesian English)

[Gary Dean]

While English is not widely spoken in Indonesia as a proportion of it's
population, it is  the standard language of business and the
professions, and among Indonesia's urban middle class.

Probably 3-5% of Indonesia's 250 million people use English on a daily
basis, twice the population of Singapore.

The en_ID locale conforms to Indonesian standards relating to country
codes, currency, time and date formats.

The en_ID locale was developed by Yayasan Teknologi Terbuka Indonesia
(Indonesian Open Technology Foundation).

http://yatti.id/doku.php/en/en_id-indonesian-english-project

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

Title:
  Add new locale en_ID (Indonesian English)

Status in langpack-locales package in Ubuntu:
  Incomplete

Bug description:
  Please see attached submission for a new locale for Indonesian English
  (en_ID).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1492568/+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 1478230] [NEW] package flashplugin-installer 11.2.202.491ubuntu0.14.04.1 failed to install/upgrade: package flashplugin-installer is already installed and configured

[Gary]

Public bug reported:

I am unable to install flash

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: flashplugin-installer 11.2.202.491ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
Uname: Linux 3.13.0-58-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: amd64
CrashReports:
 640:0:116:2357862:2015-07-25 17:14:08.084537982 +0530:2015-07-25 
17:14:28.644537264 +0530:/var/crash/update-notifier-common.0.crash
 600:0:116:382119:2015-07-25 17:11:14.140545368 +0530:2015-07-25 
17:11:15.140545368 +0530:/var/crash/flashplugin-installer.0.crash
 644:0:116:0:2015-07-25 17:14:27.620537307 +0530:2015-07-25 17:14:27.620537307 
+0530:/var/crash/update-notifier-common.0.upload
Date: Sat Jul 25 17:11:15 2015
DuplicateSignature: 
package:flashplugin-installer:11.2.202.491ubuntu0.14.04.1:package 
flashplugin-installer is already installed and configured
ErrorMessage: package flashplugin-installer is already installed and configured
InstallationDate: Installed on 2015-07-18 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: flashplugin-nonfree
Title: package flashplugin-installer 11.2.202.491ubuntu0.14.04.1 failed to 
install/upgrade: package flashplugin-installer is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: flashplugin-nonfree (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package trusty

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

Title:
  package flashplugin-installer 11.2.202.491ubuntu0.14.04.1 failed to
  install/upgrade: package flashplugin-installer is already installed
  and configured

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  I am unable to install flash

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: flashplugin-installer 11.2.202.491ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-58-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  CrashReports:
   640:0:116:2357862:2015-07-25 17:14:08.084537982 +0530:2015-07-25 
17:14:28.644537264 +0530:/var/crash/update-notifier-common.0.crash
   600:0:116:382119:2015-07-25 17:11:14.140545368 +0530:2015-07-25 
17:11:15.140545368 +0530:/var/crash/flashplugin-installer.0.crash
   644:0:116:0:2015-07-25 17:14:27.620537307 +0530:2015-07-25 
17:14:27.620537307 +0530:/var/crash/update-notifier-common.0.upload
  Date: Sat Jul 25 17:11:15 2015
  DuplicateSignature: 
package:flashplugin-installer:11.2.202.491ubuntu0.14.04.1:package 
flashplugin-installer is already installed and configured
  ErrorMessage: package flashplugin-installer is already installed and 
configured
  InstallationDate: Installed on 2015-07-18 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-installer 11.2.202.491ubuntu0.14.04.1 failed to 
install/upgrade: package flashplugin-installer is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1478230/+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 1476385] Re: sni doesn't appear to work in this version of firefox

[Gary Lyons]

This seems to have been fixed in the latest beta update.

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

Title:
  sni doesn't appear to work in this version of firefox

Status in firefox package in Ubuntu:
  New

Bug description:
   If I connect to a server doing sni I get a certificate error. IT
  works fine in the non beta version and in chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 40.0~b5+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  BuildID: 20150717074332
  CurrentDesktop: XFCE
  Date: Mon Jul 20 15:24:58 2015
  InstallationDate: Installed on 2014-07-31 (353 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  Plugins:
   IcedTea-Web Plugin (using IcedTea-Web 1.5 (1.5-1ubuntu1)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to trusty on 2015-06-18 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476385/+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 1476385] [NEW] sni doesn't appear to work in this version of firefox

[Gary Lyons]

Public bug reported:

 If I connect to a server doing sni I get a certificate error. IT works
fine in the non beta version and in chrome.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 40.0~b5+build1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
BuildID: 20150717074332
CurrentDesktop: XFCE
Date: Mon Jul 20 15:24:58 2015
InstallationDate: Installed on 2014-07-31 (353 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
Plugins:
 IcedTea-Web Plugin (using IcedTea-Web 1.5 (1.5-1ubuntu1)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date)
SourcePackage: firefox
UpgradeStatus: Upgraded to trusty on 2015-06-18 (32 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  sni doesn't appear to work in this version of firefox

Status in firefox package in Ubuntu:
  New

Bug description:
   If I connect to a server doing sni I get a certificate error. IT
  works fine in the non beta version and in chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 40.0~b5+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  BuildID: 20150717074332
  CurrentDesktop: XFCE
  Date: Mon Jul 20 15:24:58 2015
  InstallationDate: Installed on 2014-07-31 (353 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  Plugins:
   IcedTea-Web Plugin (using IcedTea-Web 1.5 (1.5-1ubuntu1)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to trusty on 2015-06-18 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476385/+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 1459235] Re: Google Address book: Unable to open address book

[Gary Hooley]

Just like to add my name to list of people affected by this problem.
 I am using ubuntu 14.04 LTS 32bit with Evolution 3.10.4
An urgent fix would be appreciated as this is greatly affecting my daily 
business activities ('obviously').

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

Title:
  Google Address book: Unable to open address book

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Since today (2015-05-27) I've been getting this message when trying to
  open my Google address book:

  Unable to open address book

  This address book cannot be opened.  This either means that an
  incorrect URI was entered, or the server is unreachable.

  Detailed error message: Unable to connect to 'Google address book':
  The requested resource was not found:
  https://developers.google.com/accounts/docs/AuthForInstalledApps

  
  Running standard Evolution ( 3.10.4) on Ubuntu 14.04.2 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1459235/+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 1021375] Re: Nautilus says the USB stick is read only when it is not

[Gary]

I just had this problem occur again, I am using 12.04 (still).  I also
got it tp work correctly, here is what worked for me (YMMV).  I am not
sure all these step are required, but the combination fixed my problem.

1- sudo chmod 755 /media (this was recommended with -R option, but I did not 
want that as my raid is mounted under /media)
2- cd 
3- mv .config/nautilus   .config/nautilus.bak
(the net effect is a new nautilus desktop file is created, for me the delta was 
deletion of nautilus-icon-view-auto-layout=true and a change to the  
nautilus-icon-view-layout-timestamp value)
4- remove media if it happens to be in
5- logout
6- login
7- insert media and test

Good luck.

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

Title:
  Nautilus says the USB stick is read only when it is not

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

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