[Desktop-packages] [Bug 1877074] Re: Support configuring multiple Bluetooth adapters separately

[3DRaven]

I have same problem. It is very uncomfortable.

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

Title:
  Support configuring multiple Bluetooth adapters separately

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

Bug description:
  In gnome desktop under settings/bluetoth be able to turn on/off
  bluetoth on per-devoce level in case when machine have > 1 BT devices
  attached. For example, one laptop internal and second - BT USB dongle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 12:39:50 2020
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877074/+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 1958019] [NEW] [82N6, Realtek ALC287, Speaker, Internal] No sound at all

[3DRaven]

Public bug reported:

On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal
speakers, but it work by headphones connected to standard jack aux.

uname -r
5.11.0-44-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  i3draven   1266 F pulseaudio
 /dev/snd/controlC0:  i3draven   1266 F pulseaudio
 /dev/snd/controlC1:  i3draven   1266 F pulseaudio
 /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 15 15:10:53 2022
InstallationDate: Installed on 2021-10-11 (96 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  i3draven   1266 F pulseaudio
 /dev/snd/controlC0:  i3draven   1266 F pulseaudio
 /dev/snd/controlC1:  i3draven   1266 F pulseaudio
 /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN49WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.49
dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  [82N6, Realtek ALC287, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 

[Desktop-packages] [Bug 1958017] [NEW] Screen scaling reset every reboot

[3DRaven]

Public bug reported:

I set in settings scaling for my 2560x1600 laptop screen. After reboot
this settings reset every time. And I can't set custom scale factor. I
used for this functionality simple script:


# Enable rotation lock  to avoid issues with xrandr.
gsettings set org.gnome.settings-daemon.peripherals.touchscreen 
orientation-lock true

# Xrandr scaling hack, --panning is used in order to let
# the mouse navigate in all of the 'generated'
# screen space.
xrandr --output DP-4 --mode 2560x1600 --scale 1.333x1.333 --panning 3413x2133

# Change scaling factor (GNOME)
gsettings set org.gnome.desktop.interface scaling-factor 2

# Confirm script execution
echo "Script finished execution"


It working fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 15 15:02:36 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation Device [10de:24dc] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3a58]
InstallationDate: Installed on 2021-10-11 (96 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: LENOVO 82N6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-44-generic 
root=UUID=698b053d-caef-42da-a499-418d0a991d5e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN49WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.49
dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution ubuntu

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

Title:
  Screen scaling reset every reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  I set in settings scaling for my 2560x1600 laptop screen. After reboot
  this settings reset every time. And I can't set custom scale factor. I
  used for this functionality simple script:

  
  # Enable rotation lock  to avoid issues with xrandr.
  gsettings set org.gnome.settings-daemon.peripherals.touchscreen 
orientation-lock true

  # Xrandr scaling hack, --panning is used in order to let
  # the mouse navigate in all of the 'generated'
  # screen space.
  xrandr --output DP-4 --mode 2560x1600 --scale 1.333x1.333 --panning 3413x2133

  # Change scaling factor (GNOME)
  gsettings set org.gnome.desktop.interface scaling-factor 2

  # Confirm script execution
  echo "Script finished execution"


  It working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: 

[Desktop-packages] [Bug 1945760] [NEW] gnome-shell errors

[3DRaven]

Public bug reported:

I have two type of errors

 gnome-shell[2070]: Window manager warning: Overwriting existing binding
of keysym 31 with keysym 31 (keycode>


gnome-shell[2070]: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 
for 0x572b45a window override-r>

Ubuntu 20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
Uname: Linux 5.13.0-9.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  1 10:48:53 2021
DisplayManager: gdm3
InstallationDate: Installed on 2018-06-28 (1190 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-12-05 (299 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  gnome-shell errors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have two type of errors

   gnome-shell[2070]: Window manager warning: Overwriting existing
  binding of keysym 31 with keysym 31 (keycode>

  
  gnome-shell[2070]: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 
for 0x572b45a window override-r>

  Ubuntu 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  Uname: Linux 5.13.0-9.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  1 10:48:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-28 (1190 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-12-05 (299 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945760/+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 1928556] [NEW] When opened modal password input window power off button don't work

[3DRaven]

Public bug reported:

I opened wifi connect dialog. When I need to write password for network
conneciton, I wish to power off notebook, but modal window don't allowed
it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
Uname: Linux 5.11.0-18.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 15 21:36:47 2021
DisplayManager: gdm3
InstallationDate: Installed on 2018-06-28 (1051 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-12-05 (160 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

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


** Tags: amd64 apport-bug focal third-party-packages

** Summary changed:

- When opened modal password input window power off button not work
+ When opened modal password input window power off button don't work

** Description changed:

  I opened wifi connect dialog. When I need to write password for network
- conneciton, I wish to power off notebook, but modal window do not allow
+ conneciton, I wish to power off notebook, but modal window don't allowed
  it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  Uname: Linux 5.11.0-18.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 15 21:36:47 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-28 (1051 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-12-05 (160 days ago)
  modified.conffile..etc.default.apport:
-  # set this to 0 to disable apport, or to 1 to enable it
-  # you can temporarily override this with
-  # sudo service apport start force_start=1
-  enabled=0
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
  mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

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

Title:
  When opened modal password input window power off button don't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I opened wifi connect dialog. When I need to write password for
  network conneciton, I wish to power off notebook, but modal window
  don't allowed it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  Uname: Linux 5.11.0-18.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 15 21:36:47 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-28 (1051 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-12-05 (160 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928556/+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 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[3DRaven]

I confirm this bug. Ubuntu 16.04.

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

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  In Progress
Status in Debian:
  Invalid

Bug description:
  [Impact]

   * The recent update of the Ubuntu asgen instance yielded it to
  generate modern metadata. While we could tell asgen to generate old-
  style metadata, fixing appstream is the better idea, since we already
  applied similar patches to appstream-glib (and having this package
  hold back updates is a bad idea). Currently, the unknown metadata is
  considered to be broken by appstream and it displays a warning about
  that issue during an `apt update`

   * The attached patch includes a second change to make AppStream more
  robust against broken YAML data, ensuring LP #1579712 can not be
  triggered on purpose or due to broken disks creating damaged YAML
  structure.

  [Test Case 1]

   * apt update
   * Check for errors about metadata being ignored

  [Test Case 2]

   * appstreamcli refresh --force
   * Check for errors about metadata being ignored
   * Check if we ignored data that should be present
 (search for it via `appstreamcli search `)
   * Run `appstreamcli status` and see if we still have information on the same 
amount of components as prior to the update.

  [Regression Potential]

   * Medium; The works case would be KDE Discover and GNOME Software
  loosing information on available software, but this risk is very low
  and the patch to fix this bug is very simple and has almost no
  regression potential. The YAML parser fix patch is a bit more complex,
  but should have no sideeffects.

  [Original report]

  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  I have a machine monitored by Munin.  One of the plugins used on that
  machine is /etc/munin/plugins/apt which periodically counts the number
  of packets that can be upgraded.  This is achieved by a crontab entry
  installed from the package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  For many months everything has been running smoothly.  On the 23rd
  November 2016 I started getting the "AppStream cache update completed,
  but some metadata was ignored due to errors." messages at a rate of
  about ten a day.

  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+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 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

[3DRaven]

Try reinstall bbswitch-dkms before update kernel or driver
Steps.
1. Purge all nvidia driver packages
2. Install nvidia nvidia-prime bbswitch-dkms

all works for me.

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Trusty:
  Fix Released

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+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 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

[3DRaven]

Sorry! Try reinstall bbswitch-dkms AFTER update kernel or driver

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Trusty:
  Fix Released

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+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 1236084] [NEW] xserver segfault

[3DRaven]

Public bug reported:

When i write proggram in java 7 se (javafx+swing application in eclipse)
X.server many segfaults. Segfault log in attachment (apport give not
real log files).

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
Uname: Linux 3.11-3.dmz.1-liquorix-amd64 x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct  7 04:18:12 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.10-12.dmz.1-liquorix-amd64, x86_64: installed
 nvidia-304, 304.108: added
 vboxhost, 4.2.16, 3.10-12.dmz.1-liquorix-amd64, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:2701]
 NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:2701]
InstallationDate: Installed on 2013-08-15 (52 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MachineType: CLEVO CO. W250ENQ / W270ENQ
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11-3.dmz.1-liquorix-amd64 
root=UUID=16121439-0ceb-40d9-9fd6-aff0c73dd6b6 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/03/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W250ENQ / W270ENQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/03/2012:svnCLEVOCO.:pnW250ENQ/W270ENQ:pvrNotApplicable:rvnCLEVOCO.:rnW250ENQ/W270ENQ:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A:
dmi.product.name: W250ENQ / W270ENQ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.
version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.46+git20130910.58d00888-0ubuntu0sarvatt~raring
version.libgl1-mesa-dri: libgl1-mesa-dri 
9.2.0~git20131002+9.2.2eb55601-0ubuntu0sarvatt~raring
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
9.2.0~git20131002+9.2.2eb55601-0ubuntu0sarvatt~raring
version.xserver-xorg-core: xserver-xorg-core 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.1.99+git20130730.6a278369-0ubuntu0sarvatt~raring
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.903+git20131001.c724098f-0ubuntu0sarvatt~raring
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt~raring
xserver.bootTime: Mon Oct  7 04:11:48 2013
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 732 
 vendor LGD
xserver.version: 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring

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


** Tags: amd64 apport-bug compiz-0.9 raring third-party-packages ubuntu

** Attachment added: real X.org server segfault log!
   
https://bugs.launchpad.net/bugs/1236084/+attachment/3863227/+files/Xorg.0.log.old

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

Title:
  xserver segfault

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When i write proggram in java 7 se (javafx+swing application in
  eclipse) X.server many segfaults. Segfault log in attachment (apport
  give not real log files).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  Uname: Linux 3.11-3.dmz.1-liquorix-amd64 x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct  7 04:18:12 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7,