date:20190401

Please:

1. Try logging into "Ubuntu on Wayland" as a workaround.

2. Run this command to send us more system information:

   apport-collect 1822513

** Tags added: regression-update

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

** No longer affects: gnome-shell (Ubuntu)

** Summary changed:

- Part of the screen is black in landscape orientation
+ [regression] gnome-shell aspect ratio doesn't rotate with the rest of the 
screen

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

Title:
  [regression] gnome-shell aspect ratio doesn't rotate with the rest of
  the screen

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I'm testing 19.04 on an Acer-One S1003. An interesting quirk of that
  tablet is that the default screen orientation is portrait (as can be
  seen in BIOS setup, grub etc.)

  Ubuntu 19.04 support screen rotation out of the box. But after a
  recent update, the landscape mode is broken.

  In landscape, only the left hand portion the screen displays an image.
  The right hand part is black.

  The part that's shown is about as wide as the screen would be in
  portrait orientation.

  Another quirk is that landscape screenshots (taken with printscreen)
  have a portrait size, with some garbage at the bottom.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1822513/+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 1822716] Re: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all if headphones are plugged in before boot

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1583801, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1583801
   No sound via headphones (headset) when Ubuntu boots with them plugged in

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

Title:
  [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at
  all if headphones are plugged in before boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is only an issue if the headphones are plugged in before boot. If
  I unplug/plug the headphone jack the audio works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  strassek   1732 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 21:53:00 2019
  InstallationDate: Installed on 2018-05-12 (324 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1309 F pulseaudio
strassek   1732 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0YT4WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822716/+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 1805561] Re: [nvidia] "Ubuntu on Wayland" login option is missing in 19.04 even though nvidia-drm.modeset=1 is set.

The only possible cause of this I can think of has now been fixed by the
introduction of:

  https://launchpad.net/ubuntu/+source/egl-wayland

and rebuilds of mutter which enabled use of it.

Does anyone still see this bug in 19.04?

** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

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

Title:
  [nvidia] "Ubuntu on Wayland" login option is missing in 19.04 even
  though nvidia-drm.modeset=1 is set.

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  No wayland in Beta of 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.78  Sat Nov 10 22:09:04 
CST 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-9ubuntu1)
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 22:33:12 2018
  DistUpgraded: 2018-11-07 22:10:40,058 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 410.78, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2018-08-01 (119 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=b0227ec8-a2f0-4e84-921d-290520742391 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to disco on 2018-11-08 (20 days ago)
  XorgLog:
   
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: MACH-WX9
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd06/05/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: HUAWEI MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1805561/+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 1822716] [NEW] [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all if headphones are plugged in before boot

2019-04-01 Thread Kevin Strasser

Public bug reported:

This is only an issue if the headphones are plugged in before boot. If I
unplug/plug the headphone jack the audio works just fine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  strassek   1732 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 21:53:00 2019
InstallationDate: Installed on 2018-05-12 (324 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1309 F pulseaudio
  strassek   1732 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/01/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.3
dmi.board.name: 0YT4WT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at
  all if headphones are plugged in before boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is only an issue if the headphones are plugged in before boot. If
  I unplug/plug the headphone jack the audio works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  strassek   1732 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 21:53:00 2019
  InstallationDate: Installed on 2018-05-12 (324 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1309 F pulseaudio
strassek   1732 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0YT4WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822716/+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 1822513] Re: Part of the screen is black in landscape orientation

2019-04-01 Thread Alexandre Jasmin

The problem disappears after downgrading mutter.

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

Title:
  Part of the screen is black in landscape orientation

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I'm testing 19.04 on an Acer-One S1003. An interesting quirk of that
  tablet is that the default screen orientation is portrait (as can be
  seen in BIOS setup, grub etc.)

  Ubuntu 19.04 support screen rotation out of the box. But after a
  recent update, the landscape mode is broken.

  In landscape, only the left hand portion the screen displays an image.
  The right hand part is black.

  The part that's shown is about as wide as the screen would be in
  portrait orientation.

  Another quirk is that landscape screenshots (taken with printscreen)
  have a portrait size, with some garbage at the bottom.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822513/+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 982503] Re: Zooming keys hardcoded inconsistently

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Zooming keys hardcoded inconsistently

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Ctrl + 0, Ctrl + Plus Sign and Ctrl + Minus Sign are the designated
  keyboard shortcuts for controlling the zoom. This works on my setup.

  Ctrl + Shift + Minus Sign seems to work identically to Ctrl + Minus
  Sign, but on my setup, Ctrl + Shift + Plus Sign does nothing, whereas
  Ctrl + Shift + 0 does what, given Minus Sign's behaviour, I'd expect
  Ctrl + Shift + Plus Sign to do: it zooms in.

  I'm guessing this is keyboard layout dependent.  I'm using the
  Finnish/Swedish keyboard layout, in which the '0' key with Shift is
  the = character. In US keyboard it seems the Plus Sign has its own
  key, and that key with the Shift pressed becomes =. This is why
  Chromium thinks that I'm doing the 'zoom in' combination when in fact
  I'm doing the 'reset zoom' combination with shift.

  I came across this while looking for a way to reset the zoom back to
  my custom default via keyboard. I figured if Ctrl+0 is 'reset to
  normal', Ctrl+Shift+0 could be 'reset to default'. (I have yet to find
  such a keyboard shortcut. That's a separate issue from the one I'm
  filing here. I'll have to file a wishlist bug if said shortcut doesn't
  exist.)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
  Uname: Linux 3.3.0-030300rc4-generic x86_64
  NonfreeKernelModules: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs reiserfs ext2 nls_iso8859_1 nls_cp437 vfat fat pci_stub 
vboxpci vboxnetadp vboxnetflt vboxdrv rfcomm bnep dm_crypt binfmt_misc 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer 
snd_seq_device snd btusb bluetooth joydev dm_multipath soundcore snd_page_alloc 
edac_core ppdev sp5100_tco i2c_piix4 mac_hid k10temp edac_mce_amd parport_pc 
shpchp asus_atk0110 lp parport uas usb_storage dm_mirror dm_region_hash dm_log 
hid_microsoft usbhid hid radeon pata_atiixp wmi ttm drm_kms_helper drm 
i2c_algo_bit r8169
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  ChromiumPrefs: can't open profile 
/home/jani/.config/chromium/Default/Preferences
  Date: Sun Apr 15 21:17:56 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to precise on 2011-11-21 (146 days ago)
  chromium-default: CHROMIUM_FLAGS=""

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/982503/+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 1062549] Re: popup windows in chromium don't have exit button in the spread

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  popup windows in chromium don't have exit button in the spread

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  When you have popup windows in chromium and you click on the chromium
  icon in the launcher, the spread appears with exit button for the main
  window but not for the popup windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  5 22:52:32 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1062549/+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 1074127] Re: Opening a web page causes a binary file to be immediately and automatically downloaded

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Opening a web page causes a binary file to be immediately and
  automatically downloaded

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Opening the link below causes a file "x32cxf" to be immediately and
  automatically downloaded:

  http://techrights.org/2010/02/17/choice-versus-condition/

  No action is needed by the user to cause the download other than
  opening the web page.  It happens every time the page is opened,
  though sometimes the page closes itself.

  This should not happen under any circumstances.  Firefox can open the
  page without downloading the file.   I have no idea if or how this can
  be exploited but automatic download seems like a very major security
  risk.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Nov  1 22:24:22 2012
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = /etc/xdg/lubuntu/:/etc/xdg/xdg-Lubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/etc/xdg/lubuntu:/usr/share/Lubuntu:/usr/local/share/:/usr/share/:/usr/share:/usr/share/gdm:/var/lib/menu-xdg
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda2  
ext4   73G  5.2G   64G   8% /\nudev   devtmpfs  474M  4.0K  474M   
1% /dev\ntmpfs  tmpfs 193M  908K  192M   1% /run\nnone   
tmpfs 5.0M 0  5.0M   0% /run/lock\nnone   tmpfs 483M  416K  
482M   1% /run/shm\nnone   tmpfs 100M   20K  100M   1% /run/user\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda24.7M  
193K  4.5M5% /\nudev 119K   544  118K1% /dev\ntmpfs 
   121K   454  121K1% /run\nnone 121K 4  121K1% 
/run/lock\nnone 121K10  121K1% /run/shm\nnone 
121K19  121K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-10-16 (16 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64+mac 
(20121015)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1074127/+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 1407108] Re: Chrome html5test.com score incorrent object store blob and array buffer support disabled

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Chrome html5test.com score incorrent object store blob and array
  buffer support disabled

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  When checking the html5test.com score of my own browser, Chrome
  39.0.2171.95 (64-bit) (fully up to date) I compare it to same browser
  and mine is scored four points lower... object store blob support and
  object store array buffer support are not enabled in my version
  running on Ubuntu 14.04 x64... fully updated 1/2/15 For some reason
  these storage options are not enabled and they should be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1407108/+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 1717388] Re: Duplicate lines created when copying csv file from a windows shared folder through Virtualbox

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Duplicate lines created when copying csv file from a windows shared
  folder through Virtualbox

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Running: Ubuntu 16.04.3 LTS
  System: Virtualbox VM

  When copying a large csv file (30-40 columns with strange characters, null 
bytes, etc.) from a shared folder with windows through vbox to Ubuntu, the data 
is corrupted in a strange way.
  Some of the lines are repeated further down. The original csv still in the 
shared folder opens fine, so this doesn't appear to be a problem with 
LibreOffice or Ubuntu's ability to view shared files, it looks like a copying 
error with nautilus.

  Copying using 'cp' through the terminal works without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 15 00:53:01 2017
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'814x581+999+107'"
  InstallationDate: Installed on 2017-08-24 (21 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1717388/+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 1687478] Re: "properties" -> "open with" - defective statemachine

[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  "properties" -> "open with" - defective statemachine

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  On Ubuntu 16.04.2: The statemachine of the "Open With" dialogue in is
  defective. To open this dialogue reightclick a file, click
  "properties" and select "Open With" tab.

  The behaviour of the button "Set as default" is correct. After
  clicking that button, the behaviour of the "Add" button is also
  correct.

  But clicking only the button "Add" after opening the dialogue without
  click "Set as default", it shows the wrong behavior. Clicking "add"
  does always the same like clicking "Set as Default". Clicking "Set as
  default" one time repairs that behavior.

  Why that? There are two problems.

  Clicking "Add" does have the behaviour like clicking "Set as default"
  to have one "Default Application" set, if no "Default Application" is
  set. That is correct.

  1st problem: This dialogue starts in state believing no default
  application is set. But the already set default application is listed
  as "Default Application". That means, clicking "Add" does the same
  like "Set as default", when it should not.

  2nd related problem: Clicking "Add" to set the "Default Application"
  the first time, does not set the state that the "Default Application"
  is set like clicking "Set as default" does. So the 1st problem is
  repeated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 23:09:06 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'253'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'"
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1687478/+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 1726355] Re: Files cannot be moved from the desktop.

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Files cannot be moved from the desktop.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  PROBLEM 1
  I'm selecting a file on the desktop.
  I'm moving it to an open nautilus window.
  The cursor takes the form of a hand.
  The file is not moved.
  The cursor retains its hand shape.
  Nautilus remains usable. 
  Firefox is no longer usable (the cursor is no longer present).

  PROBLEM 2
  Similar actions, alternative results.
  The file move behind the Nautilus windows, staying on desktop, but at a 
different location.

  Solution for unlocking problem 1:
  use gnome-tweak, desktop parameters
  deactivate icon on desktop.
  reactivate icon on desktop.
  Problem solved
  Behavioral solution:
  Use the Nautilus tree structure to move files from the desktop to other 
folders.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726355/+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 1738413] Re: speedlink LUCIDS keyboards ctrl alt keys recognised as shift key

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  speedlink LUCIDS keyboards ctrl alt keys recognised as shift key

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Each keys in space row - except for space - recognised as shift key.
  In GRUB it works perfectly fine, dual booted windows recognises them
  well. The correct type of the keyboard is Speedlink SL-6432-BK-HU,
  hungarian layout. Please, provide proper driver. Thank you.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Package - Default provided

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 15 14:17:28 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+2297+202'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2017-08-16 (120 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1738413/+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 1734205] Re: Copying file does not show speed, just (...

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Copying file does not show speed, just (...

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When file size is big the speed is cut off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1734205/+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 1697292] Re: Ubuntu-Gnome 14.04.5 Nautilus occasionally remove desktop icon's

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu-Gnome 14.04.5 Nautilus occasionally remove desktop icon's

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  In error code launched to screen so no report. The desktop just goes
  away. Have to launch Places to get the desktop back. seems to be Bug
  #17367, but this is very old (2005)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1697292/+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 1813843] Re: [nouveau] Xorg crash

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nouveau] Xorg crash

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  With the newest updates to 18 & with the HP VGA monitor attached I can
  enter the pswd but will NOT get to the home screen. It hangs at a
  black screen.

  If I detach the VGA cable I can power down and boot up to the internal
  Laptop screen then attach the VGA after logging into Ubuntu. All is
  fine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 14:28:59 2019
  DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/NetworkManager/NetworkManager.conf'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221e]
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK106GLM [Quadro K2100M] [17aa:221e]
  InstallationDate: Installed on 2014-12-13 (1508 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20BG0016US
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=6f412d93-ba4b-4a3a-a067-9d615e154680 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago)
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET70WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BG0016US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BG0016US
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jan 29 14:14:34 2019
  xserver.configfile: default
  xserver.errors: NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1813843/+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 1814025] Re: Screen flickering on many programm

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Screen flickering on many programm

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  While using VSCode, Firefox Developer Edition, Google Chrome. Watching
  youtube videos or coding the screen flickering really bad

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Thu Jan 31 10:55:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20]
  InstallationDate: Installed on 2019-01-11 (19 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. UX430UAR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier  "Card0"
   Driver  "intel"
   Option  "Backlight"  "intel_backlight"
   EndSection
  dmi.bios.date: 10/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.300:bd10/06/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901260730.8e9ad5~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1901260730.8e9ad5~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.99+git1901101932.b1c016~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1901211932.33ee0c~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1901240732.ca1391~oibaf~b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814025/+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 1814098] Re: Favorites cant be added or removed

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Favorites cant be added or removed

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Apps randomly stay on the sidebar even tho they are not added to
  favorites, also favorites cant be removed.

  Video:

  https://www.youtube.com/watch?v=5LUx3ljV83I

  Recreation:

  i cant, but restarting the system allways fixes it.

  Also the sidebar appears on the lockscreen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 11:43:49 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:39fa]
  InstallationDate: Installed on 2018-12-01 (60 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81BL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4QCN41WW(V2.05)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 520S-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN41WW(V2.05):bd12/12/2017:svnLENOVO:pn81BL:pvrLenovoideapad520S-14IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad520S-14IKB:
  dmi.product.family: ideapad 520S-14IKB
  dmi.product.name: 81BL
  dmi.product.sku: LENOVO_MT_81BL_BU_idea_FM_ideapad 520S-14IKB
  dmi.product.version: Lenovo ideapad 520S-14IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814098/+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 1706753] Re: multi dir properties unable to calculate total size

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  multi dir properties unable to calculate total size

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  when I select android-{ndk,sdk} folders, right-click & select
  properties, total size calculation goes into infinite loop. see
  attached video..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 26 22:33:33 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 4294967295'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'249'
   b'org.gnome.nautilus.window-state' b'geometry' b"'683x716+0+24'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2016-11-06 (262 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1706753/+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 1711438] Re: nautilus crashed with SIGABRT in g_assertion_message() (filename != NULL)

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message() (filename !=
  NULL)

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  During the display of a rather large SMB share directory

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 17 20:33:10 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-04-01 (138 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to artful on 2017-06-08 (70 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711438/+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 1720500] Re: data transfer status broken for usb drives

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  data transfer status broken for usb drives

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  While copying large files (i.e. >500MB) the window displaying the data
  transfer status, or progress, is totally wrong.

  Using Ubuntu 16.04 LTS 64-bit.

  When I copy a 592MB file to a USB 2.0 flash drive formatted to NTFS
  the transfer status climbs very fast then finishes and closes, all
  within a couple seconds which is too fast. Then I use udisksctrl
  command to unmount the USB drive, and although the window displaying
  the USB shows it change to unmounted, the terminal cursor just hangs
  for a couple minutes then finally outputs the "Unmounted" message once
  the file finishes copying.

  When copying the same file to a different USB 2.0 flash, formatted to
  FAT32, the status jumps immediately to i.e. 586 MB of 592 MB and hangs
  there for a couple minutes then closes when the transfer is done. At
  least this shows the file operation is still in progress, even if it
  appears frozen.

  I've tried this several times on two different machines (desktop &
  laptop) running Ubuntu 16.04 LTS 64-bit, and the problem is always the
  same as described above. On another machine running Ubuntu 14.04 LTS
  32-bit the transfer progress is displayed correctly, gradually
  climbing then closing the window when finished.

  Also, when transferring from the USB drives to the host machine the
  progress works fine in all cases. The problems only occur when
  transferring to the external USB drives.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  File Operations Copying File

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720500/+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 1754809] Re: single click not working for "move/copy file context functions" of nautilus

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  single click not working for "move/copy file context functions" of
  nautilus

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  
  "Single click" not working for "move/copy file context functions" of nautilus.

  Recentely I switched to the "Single click" mode of nautilus and this
  was the right decision. Works like a charme, BUT not if you right
  click a file an select "copy to" or "move to" functionalety.

  That's less of a bug than an inconsistence of the concept of the
  "Single click mode".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 [modified: 
usr/share/applications/nautilus-folder-handler.desktop]
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 10 07:17:22 2018
  ExecutablePath: /usr/bin/nautilus
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754809/+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 1814107] Re: Crash after fade to black (lock screen or screensaver)

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Crash after fade to black (lock screen or screensaver)

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  When leaving my laptop inactive for over 15min (screensaver settings),
  gnome-shell crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 31 14:56:34 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-06-15 (229 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814107/+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 1799614] Re: Use new media API

The pending SRU page (http://people.canonical.com/~ubuntu-archive
/pending-sru.html) still shows this bug as blocking the SRU.

Temporarily marking as verified in cosmic, though no change has
occurred. Will re-use this bug once that SRU is complete and we are
ready for the media API update.

** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  In Progress
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1796251] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/issues #113
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/113

** Also affects: gdk-pixbuf via
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/113
   Importance: Unknown
   Status: Unknown

** Also affects: gdk-pixbuf (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome-shell crashed with SIGSEGV in __strlen_avx2() from
  real_save_png() from gdk_pixbuf__png_image_save_to_callback() from
  gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv()

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.0-3ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1796251/+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 1818595] Re: Update to 1.46

Tested snapd-glib 1.47-0ubuntu0.18.10.0 in Ubuntu 18.10 (cosmic). GNOME
software able to install/remove/launch snaps (moon-buggy tested), pulse
audio still working, gnome-initial-setup showing promoted snaps.

** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Update to 1.46

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Fix Released

Bug description:
  https://wiki.ubuntu.com/SnapdGlibUpdates

  Overview of changes in snapd-glib 1.46

  * New API:
    - snapd_channel_get_released_at
    - SNAPD_ERROR_DNS_FAILURE
  * Fix tests breaking due to undefined order of results

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+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 1818766] Re: Update to 1.47

Tested snapd-glib 1.47-0ubuntu0.18.04.0 in Ubuntu 18.04 LTS (bionic).
GNOME software able to install/remove/launch snaps (moon-buggy tested),
pulse audio still working, gnome-initial-setup showing promoted snaps.

Tested snapd-glib 1.47-0ubuntu0.16.04.0 in Ubuntu 16.04 LTS (xenial).
GNOME software able to install/remove/launch snaps (moon-buggy tested),
pulse audio still working, gnome-initial-setup not in the archive.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial

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

Title:
  Update to 1.47

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Any new release has a risk of introducing bugs, this is mitigated by 
automatic regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+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 1815708] Re: Use ODRS for reviews

Tested gnome-software 3.30.2-0ubuntu10 in Ubuntu 18.10. Able to see
reviews for snaps and debs and write reviews.

** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Use ODRS for reviews

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The Ubuntu review server is being retired which will cause all Ubuntu package 
reviews to stop working. We are switching to using the Open Desktop Review 
Service (https://odrs.gnome.org/). This plugin has existed for sometime in the 
GNOME Software source, so it is well tested. This change will allow Snap 
packages to be reviewed (new feature).

  [Test Case]
  1. Open GNOME Software
  2. Select a popular app (e.g. Firefox)

  [Expected Result]
  Reviews are shown for this package. They will be different to the previous 
reviews. You are able to create reviews for both .deb and snap apps.

  [Regression Potential]
  There is a risk of new bugs encountered in the ODRS plugin. This has been 
enabled in Disco without major issue and has been used in other distributions 
for many releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815708/+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 1822699] Re: System appears to use wayland despite my having Wayland Enable set to false in the .conf file in the gdm3 folder.

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1822527, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1822527
   System appears to use wayland despite my having Wayland Enable set to false.

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

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false in the .conf file in the gdm3 folder.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
  Expected Results:
  Machine runs with the behavior of Xorg.
  Actual Results:
  Machine appears to run Wayland.
  Workaround: Edit the conf file again, and then reboot.
  In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon Apr  1 22:00:43 2019
  DistUpgraded: 2018-11-20 23:52:16,217 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: cosmic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  InstallationDate: Installed on 2018-10-07 (176 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-21 (131 days ago)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822699/+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 1822639] Re: Login screen doesn't react to key pressings prior to entering the password

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1822072, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** This bug has been marked a duplicate of bug 1822072
   User selector doesn't have focus from login screen after screen turned off

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

Title:
  Login screen doesn't react to key pressings prior to entering the
  password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Before the screen when you enter the password, where the clock is
  shown, if a key is pressed, it does not retract the screen upwards, as
  it used to. Now I have to manually use my mouse to drag the screen up.
  Not sure if it is the way it was intended to be used, but I am
  submitting a bug report to be sure.

  I apologise if this is a bug with GNOME, but please do tell me so I
  can send a bug report to them.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 18:23:16 2019
  DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2018-12-31 (91 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 5986:0670 Acer, Inc 
   Bus 001 Device 002: ID 17ef:60b2 Lenovo 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-03-29 (2 days ago)
  XorgConf:
   Section "Extensions"
   Option "XVideo" "Disable"
   EndSection
  dmi.bios.date: 02/15/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN58WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel:

[Desktop-packages] [Bug 1822665] Re: Brightness can't be changed from keyboard

Brightness keys (if not implemented in hardware directly) need to be
known and mapped by the kernel.

Please:

1. Tell us the exact laptop model.

2. Run: sudo apt install evtest

3. Run: sudo evtest

4. Select your keyboard and then tap the Fn+brightness keys.

5. Copy and paste what you see in the evtest output.

** Tags added: nvidia

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Brightness can't be changed from keyboard

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness level can't be changed from keyboard with the Fn key and
  the corresponding designated key. Other functions like changing
  volumes involving the Fn key work perfectly. The only way I can change
  brightness is from the status bar.

  Current OS: Ubuntu 19.04 Disco Dingo (development branch)
  Package version: gnome-shell 3.32.0-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:46:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-31 (91 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822665/+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 1822634] Re: grub boot fail

Could you please explain in more detail what problem you are
experiencing?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  grub boot fail

Status in Ubuntu:
  Incomplete

Bug description:
  no linux file found  16.04 GMT

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 17:04:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] 
[103c:30ea]
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316]
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.sku: KW336EA#ABU
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1822634/+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 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus

2019-04-01 Thread Bug Watch Updater

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  (In Xorg sessions only) apps launched from gnome shell do not get
  input focus

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Disco:
  In Progress

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1817924/+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 1822478] Re: [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

Oh, you could also try using these for driver detection:

extern const char *glXQueryExtensionsString( Display *dpy, int screen );

extern const char *glXQueryServerString( Display *dpy, int screen, int
name );

extern const char *glXGetClientString( Display *dpy, int name );

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

Title:
  [nvidia] All on screen text is tiny. Icons are normal size but text is
  nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822478] Re: [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

Marco,

If you are in a GL context then you could glGetString(GL_VENDOR) or
glGetString(GL_RENDERER). But actually I think both of those are a bad
idea here. Because this isn't a GL bug -- it's a basic Xorg driver bug
that would occur even without anyone using GL.

If anything, I think you would have to look at what's available from:

  /usr/include/X11/extensions/Xrandr.h

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

Title:
  [nvidia] All on screen text is tiny. Icons are normal size but text is
  nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822699] Re: System appears to use wayland despite my having Wayland Enable set to false in the .conf file in the gdm3 folder.

2019-04-01 Thread Seija Kijin

Correction: This issue occurred at around 9:55 PM, EDT on April 1, 2019,
not March 31, 2019.

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

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false in the .conf file in the gdm3 folder.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
  Expected Results:
  Machine runs with the behavior of Xorg.
  Actual Results:
  Machine appears to run Wayland.
  Workaround: Edit the conf file again, and then reboot.
  In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon Apr  1 22:00:43 2019
  DistUpgraded: 2018-11-20 23:52:16,217 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: cosmic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  InstallationDate: Installed on 2018-10-07 (176 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-21 (131 days ago)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822699/+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 1822699] [NEW] System appears to use wayland despite my having Wayland Enable set to false in the .conf file in the gdm3 folder.

2019-04-01 Thread Seija Kijin

Public bug reported:

1. Ubuntu 18.10
2. xorg:
  Installed: 1:7.7+19ubuntu8
Version table:
 *** 1:7.7+19ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
Steps to Reproduce:
1. Edit the .conf file to uncomment "WaylandEnabled"
2. Reboot the machine
3. Wait 2 days before booting it back up
4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
Expected Results:
Machine runs with the behavior of Xorg.
Actual Results:
Machine appears to run Wayland.
Workaround: Edit the conf file again, and then reboot.
In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Mon Apr  1 22:00:43 2019
DistUpgraded: 2018-11-20 23:52:16,217 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: cosmic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
InstallationDate: Installed on 2018-10-07 (176 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Gateway DX4860
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-11-21 (131 days ago)
dmi.bios.date: 08/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02-A1
dmi.board.name: IPISB-VR
dmi.board.vendor: Gateway
dmi.board.version: 1.01
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
dmi.product.family: Gateway Desktop
dmi.product.name: DX4860
dmi.sys.vendor: Gateway
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic 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/1822699

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false in the .conf file in the gdm3 folder.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
  Expected Results:
  Machine runs with the behavior of Xorg.
  Actual Results:
  Machine appears to run Wayland.
  Workaround: Edit the conf file again, and then reboot.
  In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname:

[Desktop-packages] [Bug 1822394] Re: laptop keyboard & touchpad not working at gdm screen after boot

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- laptop keyboard & touchpad not working at gdm screen after boot
+ [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after 
boot

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

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

Title:
  [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm
  screen after boot

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in lightdm package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+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 1236749] Re: Gnome shell extensions disabled at every startup

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

This bug is closed as a duplicate of bug 1385572 which is also closed.

If you have any problems in 19.04 then please open a new bug.

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

Title:
  Gnome shell extensions disabled at every startup

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Since gnome-shell 3.10, my extensions are disabled by default at every boot.
  I need to launch Tweak Tool to enable theme by hand every time.

  Both pre-installed extensions ( AlternateTab) and user-installed ones
  (top-icons)

  Step to reproduce :
  Enable an extension in Tweak Tool ( Alternate Tab for example)
  reboot computer,
  open Tweak Tool : Alternate tab is disabled.

  Running on Ubuntu 13.10
  GNOME Shell 3.10.0.1
  gnome-tweak-tool 3.10..0-0ubuntu1-saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+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 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus

** Tags added: fixed-in-3.32.1 fixed-upstream

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

Title:
  (In Xorg sessions only) apps launched from gnome shell do not get
  input focus

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Disco:
  In Progress

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1817924/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer

** Tags added: fixed-upstream

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

Title:
  [regression] Desktop zoom is missing the mouse pointer

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Disco:
  Fix Committed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020
  Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454

  ---

  Desktop zoom is missing the mouse pointer.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Wed Mar  6 15:12:04 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-04 (92 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 
(20181203)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1818790/+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 1760447] Re: Indicator of Goldendict (Qt5 software) functions only after returning from screen lock

2019-04-01 Thread Vladymir

the same is on Ubuntu 18.04 + Unity

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

Title:
  Indicator of Goldendict (Qt5 software) functions only after returning
  from screen lock

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  1. Install then run goldendict
  3. Its indicator appears, but you cannot drop its menu down
  4. Double-clicking on the indicator icon makes the app disappear and appear 
(that should not happen in an appindicator as it is similar to the old tray 
icon behaviour)
  5. Lock the screen then unlock it
  6. The indicator works fine after that

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-appindicator 18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 17:09:14 2018
  Dependencies:
   
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1760447/+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 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

2019-04-01 Thread Drew Walton

The issue is somewhere in the dynamic power management code. Here's a
workaround that has completely resolved the flickering (for me):

As root:
echo "high" > /sys/class/drm/card0/device/power_dpm_force_performance_level

Found here:
https://wiki.archlinux.org/index.php/AMDGPU#Screen_artifacts_and_frequency_problem

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

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

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1821900] Re: Ubuntu 19.04 Community Wallpapers

This bug was fixed in the package ubuntu-wallpapers - 19.04.2-0ubuntu1

---
ubuntu-wallpapers (19.04.2-0ubuntu1) disco; urgency=medium

  [ Olivier Tilloy ]
  * Add Free Culture Showcase winners for 19.04 (LP: #1821900).
  * Move the greyscale dingo to ubuntu-wallpapers-disco (add B to
ubuntu-wallpapers for this file move).
  * Update scripts used to generate XML files, to include PNG as well as JPG
files (two of the Free Culture Showcase winners are PNG files this time).

  [ Iain Lane ]
  * Update with new and smaller images, and
80s_Disco_Dingo_Simulation_by_Abubakar_NK is now a jpg.

 -- Olivier Tilloy   Mon, 01 Apr 2019
17:09:29 +0100

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 19.04 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.04.

  These have been resized to n x 2160 pixels at 72x72 dpi and then
  cropped to 16:9 where needed.

  They are all named Image_Title_by_Author_Name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821900/+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 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

2019-04-01 Thread Lucas Partridge

Also, shouldn't the user at least see an error message if you click on
the Settings icon but nothing appears to happen?

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

Title:
gnome-control-center won't install: Depends: colord (>= 0.1.30)

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

Bug description:
This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1762256.

I noticed Settings has gone missing from my ubuntu 18.04. When I click
on the spanner icon under the power icon in the top right nothing
appears to happen. Attempting to install it fails with:

$ sudo apt install gnome-control-center
[sudo] password for lucas:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

This may have come about as a side-effect of trying to install simple-
scan. I raised a question about that at
https://askubuntu.com/q/1108407/103266 but it never got fixed. I
couldn't resolve the error "Unable to correct problems, you have held
broken packages". Any suggestions welcome, please.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 21:15:46 2019
InstallationDate: Installed on 2017-09-03 (569 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
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/1821809/+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 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

2019-04-01 Thread Lucas Partridge

Thanks. Yes, I had installed a ppa for simple-scan a long time ago to
fix a scanner issue but I thought I'd gotten rid of it. I have also just
deleted all the ppas to do with that under /etc/apt/sources.list.d. But
I still can't get gnome-control-center to run or be installed:

The following packages have unmet dependencies.
gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

Do you have any idea how I can fix this please? I'm at a loss here.

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

Title:
gnome-control-center won't install: Depends: colord (>= 0.1.30)

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

Bug description:
This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1762256.

I noticed Settings has gone missing from my ubuntu 18.04. When I click
on the spanner icon under the power icon in the top right nothing
appears to happen. Attempting to install it fails with:

The following packages have unmet dependencies.
gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions

[Desktop-packages] [Bug 291827]

2019-04-01 Thread ALinuxUser

I have this problem too. Since the notification knows that there are
'zero' new mails, I do not see why the code for the notification cannot
check that number and, if the number is indeed zero, abort.

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

Title:
  New mail icon doesn't always hide

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  Thunderbird conveniently displays a notification icon when new mail
  arrives. Consider the following situation. You receive mail, however
  you check it through a web client (not thunderbird) in result of which
  there is no more unread mail. However, the notification icon is still
  present until new mail arrives. This is really not a big problem
  though I thought it is worth reporting so it could be fixed in future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/291827/+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 1822480] Re: Scrollbar Missing in Font Selection for Insert Character Form

2019-04-01 Thread Olivier Tilloy

I am not seeing that in a 18.10 VM with the latest libreoffice snap from
the stable channel. The list of fonts has arrows at its top and bottom,
scrolling with the mouse wheel and arrow keys works.

Is this something that can be consistently reproduced?

What GTK theme are you using?

** Changed in: libreoffice (Ubuntu)
   Status: New => Incomplete

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

Title:
  Scrollbar Missing in Font Selection for Insert Character Form

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  On an Ubuntu 18.10 system, using LibreOffice 6.2.2-2 Snap package, a
  scroll-bar is not displayed in the font listing within the ‘Special
  Characters’ dialogue; the field of displayed fonts cannot be moved
  through with the arrow keys or the scroll-wheel on the mouse, but the
  selected font can be changed with the arrow keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 09:13:57 2019
  InstallationDate: Installed on 2018-12-30 (91 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1822480/+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 1822674] [NEW] aspell-de: replace instantiieren with instanziieren

2019-04-01 Thread Md Ayquassar

Public bug reported:

Package: aspell-de
Version: 20161207-5

I'm using Ubuntu cosmic.

How to reproduce:

1) Run any of 
aspell -d de_DE-neu -a
aspell -d de-neu -a

2) Type in

instantiieren
instanziieren

3) Observe that aspell knows the version with "t", but not with "z".
However, www.duden.de says it's the other way round: it clearly mentions
"instanziieren" and doesn't know "instantiieren" at all. The proper verb
is "instanziieren", and that's what aspell should recognize (and ignore
the other spelling) nowadays.

Please update your dictionaries (and/or ask for an update upstream if it
exists and if it is necessary).

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  aspell-de: replace instantiieren with instanziieren

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  Package: aspell-de
  Version: 20161207-5

  I'm using Ubuntu cosmic.

  How to reproduce:

  1) Run any of 
  aspell -d de_DE-neu -a
  aspell -d de-neu -a

  2) Type in

  instantiieren
  instanziieren

  3) Observe that aspell knows the version with "t", but not with "z".
  However, www.duden.de says it's the other way round: it clearly
  mentions "instanziieren" and doesn't know "instantiieren" at all. The
  proper verb is "instanziieren", and that's what aspell should
  recognize (and ignore the other spelling) nowadays.

  Please update your dictionaries (and/or ask for an update upstream if
  it exists and if it is necessary).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1822674/+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 1822528] Re: Can't access plasma-browser integration from snap

2019-04-01 Thread Olivier Tilloy

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

This has already been reported at https://forum.snapcraft.io/t/call-for-
testing-chromium-62-0-3202-62/2569/65.

This is basically bug #1741074, marking it as a duplicate.

** This bug has been marked a duplicate of bug 1741074
   [snap] chrome-gnome-shell extension fails to detect native host connector

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

Title:
  Can't access plasma-browser integration from snap

Status in firefox package in Ubuntu:
  New

Bug description:
  Plasma Integration plugin can't access plasma-browser-integration,
  after installing Firefox from Snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  1 06:19:02 2019
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1822528/+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 1821415] Re: pkexec fails in a non-graphical environment

2019-04-01 Thread Brian Murray

** Description changed:

  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not in
  a non-graphical one.
+ 
+ N.B. you first need to create a /var/log/plymouth-debug.log file for the
+ plymouth apport package hook to actually trigger this.
  
  ubuntu@disco:~$ ubuntu-bug plymouth
  
  *** Collecting problem information
  
  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized
  
  This incident has been reported.
  
  Subsequently, bug reports from servers will contain less information.

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

2019-04-01 Thread bat21sl

Please ignore it is wrong.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1819013/+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 1822665] [NEW] Brightness can't be changed from keyboard

2019-04-01 Thread Adrian

Public bug reported:

Brightness level can't be changed from keyboard with the Fn key and the
corresponding designated key. Other functions like changing volumes
involving the Fn key work perfectly. The only way I can change
brightness is from the status bar.

Current OS: Ubuntu 19.04 Disco Dingo (development branch)
Package version: gnome-shell 3.32.0-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 20:46:39 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-31 (91 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Brightness can't be changed from keyboard

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Brightness level can't be changed from keyboard with the Fn key and
  the corresponding designated key. Other functions like changing
  volumes involving the Fn key work perfectly. The only way I can change
  brightness is from the status bar.

  Current OS: Ubuntu 19.04 Disco Dingo (development branch)
  Package version: gnome-shell 3.32.0-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:46:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-31 (91 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822665/+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 1817285] Re: SRU xdg-desktop-portal 1.0.3

2019-04-01 Thread Ken VanDine

@sil2100:  jamesh has looked at that and wasn't able to see why it would
be arch specific failure there.  However, this is probably not
interesting on ppc64el anyway.  Perhaps best to just skip this test for
that arch?

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285/+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 1816547] Re: SRU 2.56.4 to bionic

As per GNOME MRE, package hit properly proposed.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1236749] Re: Gnome shell extensions disabled at every startup

2019-04-01 Thread Xosé

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

Confirming this on 19.04-development, not only after every new boot but
also after suspend.

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

Title:
  Gnome shell extensions disabled at every startup

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Since gnome-shell 3.10, my extensions are disabled by default at every boot.
  I need to launch Tweak Tool to enable theme by hand every time.

  Both pre-installed extensions ( AlternateTab) and user-installed ones
  (top-icons)

  Step to reproduce :
  Enable an extension in Tweak Tool ( Alternate Tab for example)
  reboot computer,
  open Tweak Tool : Alternate tab is disabled.

  Running on Ubuntu 13.10
  GNOME Shell 3.10.0.1
  gnome-tweak-tool 3.10..0-0ubuntu1-saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+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 1819368] Re: unity-control-center crashed with SIGSEGV in free()

This bug was fixed in the package unity-control-center -
15.04.0+19.04.20190209-0ubuntu3

---
unity-control-center (15.04.0+19.04.20190209-0ubuntu3) disco; urgency=medium

  [ Khurshid Alam ]
  * panels/info/cc-info-panel.c:
info: Fix crashes when retrieving disk size (lp: #1819368)

 -- Sebastien Bacher   Mon, 01 Apr 2019 18:03:01
+0200

** Changed in: unity-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  unity-control-center crashed with SIGSEGV in free()

Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  Happens when trying to open the info (details) panel

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: unity-control-center 15.04.0+19.04.20190209-0ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Mar 10 15:09:20 2019
  ExecutablePath: /usr/bin/unity-control-center
  ExecutableTimestamp: 1551456572
  InstallationDate: Installed on 2019-03-09 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  ProcCmdline: unity-control-center info --verbose
  ProcCwd: /home/doug
  SegvAnalysis:
   Segfault happened at: 0x7f17f1c1f25d <__GI___libc_free+29>:  mov
-0x8(%rdi),%rax
   PC (0x7f17f1c1f25d) ok
   source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   __GI___libc_free (mem=0x1) at malloc.c:3109
   g_unix_mount_free () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
   () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1819368/+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 1306849] Re: Printing error

2019-04-01 Thread Till Kamppeter

hailfinger, this would mean that Brother's PostScript printers only work
with PostScript level 2 instead of level 3, this is at least what cups-
filters will do different after your change.

I have modified cups-filters (the pdftops filter) now to emit PostScript
level 2 on Brother printers, regardless whether the PPD filetells level
2 or level 3.

See

https://github.com/OpenPrinting/cups-
filters/commit/84657859490f302bb6d146517f656d5fe933363d

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

Title:
  Printing error

Status in foomatic-db package in Ubuntu:
  Confirmed

Bug description:
  I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND
  STACK; when I try to print from Firefox or anything that has a picture
  as part of the file.  I am running saucy on an AMD64 system. so far I
  have tried deleting the printer and setting it up again. No change.
  Ubuntu 13.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+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 1819368] Re: unity-control-center crashed with SIGSEGV in free()

2019-04-01 Thread Sebastien Bacher

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  unity-control-center crashed with SIGSEGV in free()

Status in unity-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Happens when trying to open the info (details) panel

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: unity-control-center 15.04.0+19.04.20190209-0ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Mar 10 15:09:20 2019
  ExecutablePath: /usr/bin/unity-control-center
  ExecutableTimestamp: 1551456572
  InstallationDate: Installed on 2019-03-09 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  ProcCmdline: unity-control-center info --verbose
  ProcCwd: /home/doug
  SegvAnalysis:
   Segfault happened at: 0x7f17f1c1f25d <__GI___libc_free+29>:  mov
-0x8(%rdi),%rax
   PC (0x7f17f1c1f25d) ok
   source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   __GI___libc_free (mem=0x1) at malloc.c:3109
   g_unix_mount_free () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
   () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1819368/+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 1822642] [NEW] Suspend with pm-suspend (or any other way) stops working after a few cycles

2019-04-01 Thread debasish ray chawdhuri

Public bug reported:

I had a fresh installation of Ubuntu-18.04. From the beginning suspend
was failing spuriously. When I looked up in Google, I was suggested to
upgrade my kernel as the provided kernel 4.15 was buggy. So I compiled
the kernel from source and upgraded to 5.04. The problem still
persisted. Having GRUB_CMDLINE_LINUX_DEFAULT="acpi_sleep=nonvs" in the
file /etc/default/grub and running sudo update-grub does not change
anything. Finally I have narrowed down the problem to calling sudo pm-
suspend directly. The command works perfectly fine until a few suspend-
wakeup cycles have passed. After a few cycle, the screen blanks out and
the system does not go to sleep. Nothing responds and I have to do a
hard reboot after which everything works the same.

Release: Description:   Ubuntu 18.04.2 LTS
Release:18.04

pm-utils:
  Installed: 1.4.1-17
  Candidate: 1.4.1-17
  Version table:
 *** 1.4.1-17 500
500 http://in.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://in.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

Expected pm-suspend to work every time. Instead, pm-suspend fails to put
the system to sleep after a few cycles.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pm-utils 1.4.1-17
Uname: Linux 5.0.4 x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 21:20:39 2019
InstallationDate: Installed on 2019-02-13 (47 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Suspend with pm-suspend (or any other way) stops working after a few
  cycles

Status in pm-utils package in Ubuntu:
  New

Bug description:
  I had a fresh installation of Ubuntu-18.04. From the beginning suspend
  was failing spuriously. When I looked up in Google, I was suggested to
  upgrade my kernel as the provided kernel 4.15 was buggy. So I compiled
  the kernel from source and upgraded to 5.04. The problem still
  persisted. Having GRUB_CMDLINE_LINUX_DEFAULT="acpi_sleep=nonvs" in the
  file /etc/default/grub and running sudo update-grub does not change
  anything. Finally I have narrowed down the problem to calling sudo pm-
  suspend directly. The command works perfectly fine until a few
  suspend-wakeup cycles have passed. After a few cycle, the screen
  blanks out and the system does not go to sleep. Nothing responds and I
  have to do a hard reboot after which everything works the same.

  Release: Description: Ubuntu 18.04.2 LTS
  Release:  18.04

  pm-utils:
Installed: 1.4.1-17
Candidate: 1.4.1-17
Version table:
   *** 1.4.1-17 500
  500 http://in.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://in.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  Expected pm-suspend to work every time. Instead, pm-suspend fails to
  put the system to sleep after a few cycles.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pm-utils 1.4.1-17
  Uname: Linux 5.0.4 x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 21:20:39 2019
  InstallationDate: Installed on 2019-02-13 (47 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   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/1822642/+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 701856] Re: Brother's printer/scanner drivers awkward to find and install

2019-04-01 Thread Colan Schwartz

I gave up on Brother after having to fiddle with the config on every OS
upgrade, and I recommend that everyone else do the same.  I tried
opening a support ticket the last time, and they said Linux support is
only available in the forums, which tells me they don't actively support
it any more (if they ever did).

So as suggested in comment #26, I ran out and bought an HP, and never
looked back.  I got everything working fairly quickly, and it hasn't
broken since.

They actually work with the open-source community so I'll keep
supporting them.  I'm never buying a Brother again.

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

Title:
  Brother's printer/scanner drivers awkward to find and install

Status in cups package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: cupsys

  Hello,

  I have the multifonction laser printer and scan Brother DCP-7030.

  It works very well in Ubuntu, but with some hard configuration.
  Printer is automatically detected when connected in USB, but Ubuntu
  does not propose DCP-7030 drivers, only DCP-7025, and it doesn't work
  well.

  To get DCP-7030 fully recognized and well printing / scanning, I have to do 
this (it's a short summary) :
  http://solutions.brother.com/linux/en_us/before.html

  - Printer BROTHER DCP-7030 :

  cd ~/desktop
  sudo aa-complain cupsd
  sudo mkdir /usr/share/cups/model
  http://solutions.brother.com/linux/en_us/download_prn.html#DCP-7030
  sudo dpkg -i --force-all --force-architecture brdcp7030lpr-2.0.2-1.i386.deb
  sudo dpkg -i --force-all --force-architecture 
cupswrapperDCP7030-2.0.2-1.i386.deb
  http://127.0.0.1:631/printers/DCP7030 : OK

  After that printer works

  
  - SCANNING :

  Install scan-key-tools  /  Brscan3
  http://solutions.brother.com/linux/en_us/download_scn.html#brscan3
  http://solutions.brother.com/linux/en_us/instruction_scn1a.html

  sudo gedit /lib/udev/rules.d/50-udev-default.rules : in section
  "libusb device nodes", replacer 0664 by 0666

  sudo lsusb
  Bus 001 Device 004: ID 04f9:01a Brother Industries, Ltd
  Go to dev/bus/usb : bus 1 and device 4 is root owned
  Open it in Nautilus as root, change it to my user name and take ownership

  Now Simple Scan works, Brother-DCP is seen.

  But... big problem !

  At each restart of Ubuntu or DCP Brother, permission resets and comes
  back to root, I have to change ownership and re-log each time, this is
  not nice...

  Is it a way to "protect" the file against erasing or permission change
  ?

  It's also true for other models than DCP-7030 (like DCP-7040...). I do
  not know if it is a Cups / Ubuntu "bug" or Openprinting missing for
  new drivers, but as Brother gives functional drivers for Linux, this
  should be easily implemented I hope, as more and more materials are
  natively identified in Ubuntu.

  Thanks in advance for your help. Best regards,

  Xavier

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/701856/+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 1822515] Re: Touchscreen input doesn't rotate with the screen

2019-04-01 Thread Alexandre Jasmin

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

I don't know whether this touch input issue should be marked as a
duplicate of Bug #1822513 as I was experiencing before the "part of the
screen is black" problem appeared.

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I'm testing 19.04 on an Acer-One S1003. An interesting quirk of that
  tablet is that the default screen orientation is portrait (as can be
  seen in BIOS setup, grub etc.)

  Ubuntu 19.04 support automatic screen rotation out of the box. But
  that touch input doesn't seem to follow the screen orientation.

  When the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1822515/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all

Performing 
sudo apt-get -y --reinstall install linux-sound-base alsa-base alsa-utils 
lightdm ubuntu-desktop linux-image-`uname -r` libasound2
On fresh install 18.04 partition on a different partition did not dolce the 
problem. Is there any step by step

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

Title:
  [ASRock FM2A75M-DGS] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  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.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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.
  modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+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 1822478] Re: [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

One reason so far I didn't do this kind of blacklist though is related
to the fact there's I don't have a proper way to get the actual driver
from xorg. Indeed I could get from the renderer, but I don't see it that
clean.

Any tip?

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

Title:
  [nvidia] All on screen text is tiny. Icons are normal size but text is
  nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822639] [NEW] Login screen doesn't react to key pressings prior to entering the password

2019-04-01 Thread Adrian

Public bug reported:

Before the screen when you enter the password, where the clock is shown,
if a key is pressed, it does not retract the screen upwards, as it used
to. Now I have to manually use my mouse to drag the screen up. Not sure
if it is the way it was intended to be used, but I am submitting a bug
report to be sure.

I apologise if this is a bug with GNOME, but please do tell me so I can
send a bug report to them.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 18:23:16 2019
DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:380a]
   Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
InstallationDate: Installed on 2018-12-31 (91 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:0670 Acer, Inc 
 Bus 001 Device 002: ID 17ef:60b2 Lenovo 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80RU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-03-29 (2 days ago)
XorgConf:
 Section "Extensions"
 Option "XVideo" "Disable"
 EndSection
dmi.bios.date: 02/15/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: E5CN58WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo ideapad 700-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 700-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80RU
dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
dmi.product.version: Lenovo ideapad 700-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco possible-manual-nvidia-install 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/1822639

Title:
  Login screen doesn't react to key pressings prior to entering the
  password

Status in xorg package in Ubuntu:
  New

Bug description:
  Before the screen when you enter the password, where the clock is
  shown, if a key is pressed, it does not retract the screen upwards, as
  it used to. Now I have to manually use my mouse to drag the screen up.
  Not sure if it is the way it was intended to be used, but I am
  submitting a bug report to be sure.

  I apologise if this is a bug with GNOME, but please do tell me so I
  can send a bug report to them.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia

[Desktop-packages] [Bug 1821900] Re: Ubuntu 19.04 Community Wallpapers

2019-04-01 Thread Will Cooke

It looks like when I exported them from Gimp I didn't have the correct
defaults set, so they had the wrong compression and lots of extra meta
data set.  This archive should be about 1/3rd the size.


** Attachment added: "fcs_1904_smaller.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821900/+attachment/5251716/+files/fcs_1904_smaller.tar.xz

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

Title:
  Ubuntu 19.04 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Committed

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.04.

  These have been resized to n x 2160 pixels at 72x72 dpi and then
  cropped to 16:9 where needed.

  They are all named Image_Title_by_Author_Name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821900/+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 1821900] Re: Ubuntu 19.04 Community Wallpapers

2019-04-01 Thread Will Cooke

It looks like when I exported them from Gimp I didn't have the correct
defaults set, so they had the wrong compression and lots of extra meta
data set.  This archive should be about 1/3rd the size.


** Attachment added: "fcs_1904_smaller.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821900/+attachment/5251717/+files/fcs_1904_smaller.tar.xz

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

Title:
  Ubuntu 19.04 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Committed

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.04.

  These have been resized to n x 2160 pixels at 72x72 dpi and then
  cropped to 16:9 where needed.

  They are all named Image_Title_by_Author_Name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821900/+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 1745666] Re: gsd-housekeeping leaks file descriptors

2019-04-01 Thread Anders Hall

This bug came back again in latest ubuntu, this time a new symptom
occurred. Gnome extensions are also regularly disabled for some reason.
Removing gsd-housekeepin still works.

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

Title:
  gsd-housekeeping leaks file descriptors

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Apparently a process called gsd-housekeeping is periodically invoked
  on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason.
  Looks like it is leaking file descriptors while doing so.

  My syslogs are full of error messages like the following:

  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error 
opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+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 1822635] [NEW] Graphical configurator wrongly requires IPv4 Gateway in routes list

2019-04-01 Thread Josef Mašek

Public bug reported:

Valid IPv4 route configuration (in openvpn text configuration) is without 
gateway (route is going to the tunnel, so next hop is not required), eg:
route 192.168.32.0 255.255.240.0

This valid configuration works when is imported by nmcli (open VPN tunnel by 
nmcli or GUI).
But configuration cannot be saved by GUI (and thus not saved after import), 
because GUI require filled Gateway.
Use unfilled Gateway is very useful during openvpn readressing or changing 
pools etc. When Gateway is filled, then any changes is often required also all 
on clients.
Ps. Sending routes from OVPN server is not implemented on Mikrotik (my case).

Gateway fields.

My versions:
network-manager-openvpn/bionic,now 1.8.2-1 amd64 [installed]
network-manager-openvpn-gnome/bionic,now 1.8.2-1 amd64 [installed]
openvpn/bionic-updates,now 2.4.4-2ubuntu1.1 amd64 [installed]
openvpn-auth-ldap/bionic 2.0.3-6.1ubuntu2 amd64
openvpn-auth-radius/bionic 2.1-6build1 amd64
openvpn-auth-radius-dbg/bionic 2.1-6build1 amd64
openvpn-systemd-resolved/bionic,now 1.2.7-1 amd64 [installed]

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

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

Title:
  Graphical configurator wrongly requires IPv4 Gateway in routes list

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

Bug description:
  Valid IPv4 route configuration (in openvpn text configuration) is without 
gateway (route is going to the tunnel, so next hop is not required), eg:
  route 192.168.32.0 255.255.240.0

  This valid configuration works when is imported by nmcli (open VPN tunnel by 
nmcli or GUI).
  But configuration cannot be saved by GUI (and thus not saved after import), 
because GUI require filled Gateway.
  Use unfilled Gateway is very useful during openvpn readressing or changing 
pools etc. When Gateway is filled, then any changes is often required also all 
on clients.
  Ps. Sending routes from OVPN server is not implemented on Mikrotik (my case).

  Gateway fields.

  My versions:
  network-manager-openvpn/bionic,now 1.8.2-1 amd64 [installed]
  network-manager-openvpn-gnome/bionic,now 1.8.2-1 amd64 [installed]
  openvpn/bionic-updates,now 2.4.4-2ubuntu1.1 amd64 [installed]
  openvpn-auth-ldap/bionic 2.0.3-6.1ubuntu2 amd64
  openvpn-auth-radius/bionic 2.1-6build1 amd64
  openvpn-auth-radius-dbg/bionic 2.1-6build1 amd64
  openvpn-systemd-resolved/bionic,now 1.2.7-1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1822635/+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 1822634] [NEW] grub boot fail

2019-04-01 Thread Ray Newton

Public bug reported:

no linux file found  16.04 GMT

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 17:04:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] 
[103c:30ea]
InstallationDate: Installed on 2019-04-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316]
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.0A
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.sku: KW336EA#ABU
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic corruption 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/1822634

Title:
  grub boot fail

Status in xorg package in Ubuntu:
  New

Bug description:
  no linux file found  16.04 GMT

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 17:04:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] 
[103c:30ea]
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316]
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV

[Desktop-packages] [Bug 1822466] Re: [FM2A75M-DGS., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

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

In this bug report I include case specs and alsamixer image with front
panel with audio jack

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

Title:
  [FM2A75M-DGS., Realtek ALC662 rev1, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Alsamixer with my http://it.thermaltake.com/products-model.aspx?id=C_2559 
front panel audio extension, usb powered 
https://www.trust.com/it/product/20943-polo-compact-2-0-speaker-set connected 
to rear green port
  https://imgur.com/nM1gzEC

  pavucontrol option all analog device seems unplugged even if they are plugged 
in
  https://streamable.com/ix2ob

  Need a fix

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1776 F pulseaudio
   /dev/snd/controlC0:  hp 1776 F pulseaudio
hp16340 F alsamixer
  CurrentDesktop: XFCE
  Date: Sun Mar 31 13:29:12 2019
  InstallationDate: Installed on 2016-09-07 (934 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1776 F pulseaudio
   /dev/snd/controlC0:  hp 1776 F pulseaudio
hp16340 F alsamixer
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  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.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: 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.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-30T08:08:19.492099

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822466/+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 1755007] Re: tracker-miner-fs crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1713629
   tracker-miner-fs crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1822629
   
/usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

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

Title:
  tracker-miner-fs crashed with SIGSEGV

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  Dont know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: tracker-miner-fs 2.0.4-1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 11 19:00:48 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f1b5ed6056a:mov0x40(%rbp),%ebx
   PC (0x7f1b5ed6056a) ok
   source "0x40(%rbp)" (0x0040) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-miner-fs crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1755007/+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 1723645] Re: tracker-miner-fs crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1713629
   tracker-miner-fs crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1822629
   
/usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

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

Title:
  tracker-miner-fs crashed with SIGSEGV

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  Mah!!!

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-miner-fs 2.0.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 21:07:38 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  SegvAnalysis:
   Segfault happened at: 0x7f919a0ee04a:mov0x40(%rbp),%ebx
   PC (0x7f919a0ee04a) ok
   source "0x40(%rbp)" (0x0040) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-miner-fs crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1723645/+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 1724801] Re: tracker-miner-fs crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1713629
   tracker-miner-fs crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1822629
   
/usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

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

Title:
  tracker-miner-fs crashed with SIGSEGV

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  ...some litle instabilities since last upgrade. Crash eventualy few
  minutes after login. No known cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-miner-fs 2.0.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 08:20:19 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2017-09-29 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe990b74046:mov0x18(%rdi),%rbp
   PC (0x7fe990b74046) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-miner-fs crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bluetooth cdrom clamav dip firebird input lpadmin plugdev 
pulse sambashare sudo utmp uucp uuidd vboxusers video voice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1724801/+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 1724475] Re: tracker-miner-fs crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1713629
   tracker-miner-fs crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1822629
   
/usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

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

Title:
  tracker-miner-fs crashed with SIGSEGV

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  Tracker processes using up >90% of the processor too often. Unplugging
  laptop from power causes processes to crash. Something needs to be
  done to keep tracker from running my machine hot all the time, else I
  will be forced to remove it.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-miner-fs 2.0.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 08:39:44 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2016-12-03 (318 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd7fa91a046:mov0x18(%rdi),%rbp
   PC (0x7fd7fa91a046) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-miner-fs crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-09-28 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1724475/+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 1762974] Re: tracker-miner-fs crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1713629
   tracker-miner-fs crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1822629
   
/usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

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

Title:
  tracker-miner-fs crashed with SIGSEGV

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  It crashed while I was adding and removing folders in Search Locations
  in Settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: tracker-miner-fs 2.0.4-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 11:07:37 2018
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2017-10-02 (190 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  SegvAnalysis:
   Segfault happened at: 0x7f723f68a566:mov0x18(%rdi),%rbp
   PC (0x7f723f68a566) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-miner-fs crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1762974/+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 1822629] [NEW] /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

2019-04-01 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
tracker-miners.  This problem was most recently seen with package version 
2.1.6-1, the problem page at 
https://errors.ubuntu.com/problem/d74b7e2c225d68f36ba3587ca110e0f0923aae8a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: tracker-miners (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: artful bionic cosmic disco kylin-18.04

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

Title:
  /usr/lib/tracker/tracker-miner-
  
fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb

Status in tracker-miners package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
tracker-miners.  This problem was most recently seen with package version 
2.1.6-1, the problem page at 
https://errors.ubuntu.com/problem/d74b7e2c225d68f36ba3587ca110e0f0923aae8a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1822629/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Run test for test_move_item inside glib 2.56.4-0ubuntu0.18.04.2 and it
works as expected.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2

This bug was fixed in the package xdg-desktop-portal-gtk -
1.0.2-0ubuntu0.0

---
xdg-desktop-portal-gtk (1.0.2-0ubuntu0.0) xenial-proposed; urgency=medium

  * New upstream release 1.0.2 (LP: #1817287)

 -- Ken VanDine   Mon, 10 Dec 2018 16:23:19
-0500

** Changed in: xdg-desktop-portal-gtk (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  SRU xdg-desktop-portal-gtk 1.0.2

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal-gtk upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in 
xdg-desktop-portal-gtk 1.0.  We're SRU'ing 1.0.2 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and 
xenial, so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
   
   Also requires xdg-desktop-portal 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal also from proposed.  Verify the file
  selection lets you select a file and open local opens test.txt in a
  text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however the version in bionic had limited 
functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic 
and disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+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 1817287] Update Released

2019-04-01 Thread Łukasz Zemczak

The verification of the Stable Release Update for xdg-desktop-portal-gtk
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU xdg-desktop-portal-gtk 1.0.2

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal-gtk upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in 
xdg-desktop-portal-gtk 1.0.  We're SRU'ing 1.0.2 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and 
xenial, so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
   
   Also requires xdg-desktop-portal 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal also from proposed.  Verify the file
  selection lets you select a file and open local opens test.txt in a
  text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however the version in bionic had limited 
functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic 
and disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+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 1817285] Re: SRU xdg-desktop-portal 1.0.3

2019-04-01 Thread Łukasz Zemczak

Hey Ken! Do you know why the xdg-desktop-portal ppc64el tests are
failing? Looks like it's reproducible. Is it something we should be
worrying about?

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285/+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 1822610] [NEW] Scaling not persisted across reboots on Disco

2019-04-01 Thread Joseph Borg

Public bug reported:

Using Xorg with Nvidia-412 drivers on 19.04.  When running and apt
upgrade (inc the Nvidia driver), something seems to have updated that's
overwriting the Gnome settings scale option.  I want this to be at 100%,
but it keeps going back to around 200% everytime I reboot.  When I check
back in Gnome Setting to see the resolution, 100% is selected, so I have
to click 200% and then 100%, at which point it looks normal again.

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

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

Title:
  Scaling not persisted across reboots on Disco

Status in mutter package in Ubuntu:
  New

Bug description:
  Using Xorg with Nvidia-412 drivers on 19.04.  When running and apt
  upgrade (inc the Nvidia driver), something seems to have updated
  that's overwriting the Gnome settings scale option.  I want this to be
  at 100%, but it keeps going back to around 200% everytime I reboot.
  When I check back in Gnome Setting to see the resolution, 100% is
  selected, so I have to click 200% and then 100%, at which point it
  looks normal again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1822610/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2019-04-01 Thread Carl-Daniel Hailfinger

See https://bugs.launchpad.net/ubuntu/+source/foomatic-
db/+bug/1306849/comments/42 for a workaround for the broken Firefox

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1306849] Re: Printing error

2019-04-01 Thread Carl-Daniel Hailfinger

Same issue with printing files from Firefox (and sometimes other applications) 
in Bionic with a Brother HL5250DN.
The used driver does not matter (BR-Script3, PCL, PS).
Related: https://bugzilla.redhat.com/show_bug.cgi?id=855009#c6

Solution:
Use the BR-Script3 driver, then edit (as root) the PPD for your printer (for me 
it's /etc/cups/ppd/Brother_HL-5250DN_Brotherscript3.ppd ).
The PPD starts with some comments, then the following content:

[...]
*%
*%  Copyright(C) 2005 Brother Industries, Ltd.
*%  "Brother HL-5250DN BR-Script3"
*%
*% General Information Keywords 
*FormatVersion: "4.3"
*FileVersion: "1.03"
*LanguageEncoding: ISOLatin1
*LanguageVersion: English
*Manufacturer: "Brother"
*PCFileName: "BR5250_2.PPD"
*Product: "(Brother HL-5250DN series)"
*PSVersion: "(3010.106) 5"
*ShortNickName: "Brother HL-5250DN BR-Script3"
*ModelName: "Brother HL-5250DN BR-Script3"
*NickName: "Brother HL-5250DN BR-Script3"
*1284DeviceID: "MFG:Brother;MDL:HL-5250DN series;CMD:PJL,PCL,PCLXL,POSTSCRIPT;"
*% Basic Device Capabilities =
*LanguageLevel: "3"
[...]

Edit the line with "LanguageLevel" and change the "3" to "2". It should now 
look like this:
*LanguageLevel: "2"

Restart cups with "systemctl restart cups". Enjoy.

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

Title:
  Printing error

Status in foomatic-db package in Ubuntu:
  Confirmed

Bug description:
  I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND
  STACK; when I try to print from Firefox or anything that has a picture
  as part of the file.  I am running saucy on an AMD64 system. so far I
  have tried deleting the printer and setting it up again. No change.
  Ubuntu 13.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+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 1822478] Re: [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [nvidia] All on screen text is tiny. Icons are normal size but text is
  nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822593] [NEW] No option to disable devices low battery notifications

2019-04-01 Thread Efthimios Chaskaris

Public bug reported:

You can find the battery levels of devices in Settings->Power.

It would be nice if the notifications about the batteries could be
disabled. I keep getting them, but my devices keep working for a long
time (even when they themselves flash red due to low battery).

Ubuntu 18.10
Gnome 3.30.1

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

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

Title:
  No option to disable devices low battery notifications

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

Bug description:
  You can find the battery levels of devices in Settings->Power.

  It would be nice if the notifications about the batteries could be
  disabled. I keep getting them, but my devices keep working for a long
  time (even when they themselves flash red due to low battery).

  Ubuntu 18.10
  Gnome 3.30.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822593/+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 1822478] Re: [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

Yeah, this is a known issue, ideally the driver should advertize weather
the randr transformations are supported or not, and nvidia driver says
so, while isn't true actually.

So, we'd need to probably filter out nvidia from this, or wait nvidia to
fix this.

Something like this https://askubuntu.com/questions/704503/scale-2x2-in-
xrandr-causes-the-monitor-to-not-display-anything has some solutions,
but I had nothing like that working in my system.

If you can get that working, then probably we can figure out another
solution.

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

Title:
  [nvidia] All on screen text is tiny. Icons are normal size but text is
  nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1821863] Re: Need to add Intel CML related pci-id's

2019-04-01 Thread Thadeu Lima de Souza Cascardo

** Also affects: mesa (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: libdrm (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

** Also affects: xorg-server (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Fix Committed

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Incomplete
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  New
Status in xorg-server source package in Disco:
  New

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1822587] [NEW] wifi service stops occasionally.

2019-04-01 Thread Justin Hall

Public bug reported:

wifi service stops occasionally: ('?' in the top right icon). an old bug
that disappeared a few updates back, back now after yesterday's update.
'service network-manager restart' gets it working again. annoying as i
thought it gone.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager 1.12.4-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 14:50:50 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-30 (975 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTIONCON-UUID  CON-PATH 
  
 wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
 enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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


** Tags: amd64 apport-bug cosmic

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  New

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   --

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

2019-04-01 Thread Derk Willem te Bokkel

xubuntu iso for daily april 1, 2019 .. no change

installed iso reboots into the install partition everything works as normal..
reboot into sda1 .. grub-install /dev/sda then update-grub then reboot .. back
into the fresh install partition ..

same behaviours as before .. red flash no visible plymouth .. brief
lightdm login screen appearance .. then brief cursor .. then blank
screen .. all after changing grub back to sda1 as master after
installing iso to freshly blanked test partition sda7 or sda6

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

Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
New

Bug description:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..

back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively

on the test installs as long as the iso is using the grub boot loader
installed from that install the system will boot normally .. the display manger
tends to flicker on and off but does final start and login can proceed.

but if another install re-installs grub as master the display manager
fails to stay active or even come-up for sda6 or sda7 only if their
own grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work
by running dpkg fix which does nothing .. and then resuming the boot .. then
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power
down and reboot gives access. (sometime requiring radical depowering ..
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias:
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
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/1821609/+subscriptions

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

[Desktop-packages] [Bug 1819729] Re: Add support for installing gpgpu drivers

This bug was fixed in the package ubuntu-drivers-common - 1:0.5.2.3

---
ubuntu-drivers-common (1:0.5.2.3) bionic; urgency=medium

  * tests/ubuntu_drivers.py,
UbuntuDrivers/detect.py,
ubuntu-drivers:
- Deprecate the "autoinstall" parameter in favour of
  "install". While "autoinstall" will still work,
  we recommend the latter.
- Add support to for the --gpgpu parameter (LP: #1819729).

 -- Alberto Milone   Tue, 12 Mar 2019
16:31:04 +0100

** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Add support for installing gpgpu drivers

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  We need the ubuntu-drivers tool to be able to install gpgpu driver 
meta-packages (without pulling in the kernel modules).

  An additional "--gpgpu" parameter, paired with the "install" parameter
  will provide this feature.

  Note: in this first implementation - already available in Ubuntu 19.04
  - only the NVIDIA driver packages are supported.

  [Test Case]
  1) Enable the -proposed repository, and install the new ubuntu-drivers-common 
(1:0.5.2.3).

  2) Make sure to have compatible NVIDIA hardware

  3) Install the gpgpu driver:
  ubuntu-drivers install --gpgpu

  4) Make sure that the new driver is installed.

  [Test Case - desktop regression test]
  1) On a machine which has nvidia GPU hardware and has not had the gpgpu 
enabled as above, enable the -proposed repository and install the new 
ubuntu-drivers-common (1:0.5.2.3).
  2) Run "Software & Updates" (software-properties-gtk)
  3) Switch to the Additional Drivers tab
  4) Confirm that information is display detailing the nvidia graphics drivers 
being available
  5) Install the drivers from the UI by selecting the correct radio button and 
clicking Apply
  6) After install has finished, reboot the system and check the drivers are 
loaded by opening Software & Updates again.

  [Regression Potential]
  Low. The changes do not affect the currently supported features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1819729/+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 1819729] Update Released

2019-04-01 Thread Łukasz Zemczak

The verification of the Stable Release Update for ubuntu-drivers-common
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for installing gpgpu drivers

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  We need the ubuntu-drivers tool to be able to install gpgpu driver 
meta-packages (without pulling in the kernel modules).

  An additional "--gpgpu" parameter, paired with the "install" parameter
  will provide this feature.

  Note: in this first implementation - already available in Ubuntu 19.04
  - only the NVIDIA driver packages are supported.

  [Test Case]
  1) Enable the -proposed repository, and install the new ubuntu-drivers-common 
(1:0.5.2.3).

  2) Make sure to have compatible NVIDIA hardware

  3) Install the gpgpu driver:
  ubuntu-drivers install --gpgpu

  4) Make sure that the new driver is installed.

  [Test Case - desktop regression test]
  1) On a machine which has nvidia GPU hardware and has not had the gpgpu 
enabled as above, enable the -proposed repository and install the new 
ubuntu-drivers-common (1:0.5.2.3).
  2) Run "Software & Updates" (software-properties-gtk)
  3) Switch to the Additional Drivers tab
  4) Confirm that information is display detailing the nvidia graphics drivers 
being available
  5) Install the drivers from the UI by selecting the correct radio button and 
clicking Apply
  6) After install has finished, reboot the system and check the drivers are 
loaded by opening Software & Updates again.

  [Regression Potential]
  Low. The changes do not affect the currently supported features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1819729/+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 1821415] Re: pkexec fails in a non-graphical environment

I proposed a fix upstream [1]. A workaround can be added to apport to
workaroud this while polkit is fixed upstream: we could for example
spawn pkttyagent manually (a similar approach is used by systemd).

[1] https://gitlab.freedesktop.org/polkit/polkit/merge_requests/28

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all

asrock-mobo from live 19.04 live, sudo alsa force-reloading, pulseaudio
-k. Did not work

** Attachment added: "alsa-info.txt.1BjH77KqBS"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+attachment/5251562/+files/alsa-info.txt.1BjH77KqBS

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

Title:
  [ASRock FM2A75M-DGS] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  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.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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.
  modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all