date:20171108

Didn't see your last post no worries I'm not really too concerned about i386 
was just trying to be as complete as possible. I just ran The Talos Princible 
in moddable version non x64 and it completed just fine despite the elf class 
warning no loss of fps or any visible graphical errors so really not a big 
issue. Thank you can't wait for 17.2.4 to hit the official update repo's.
As far as I'm comcerned issues fixed.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

2017-11-08 Thread Nathanel Titane

Also, while you guys are in the process of figuring out when and how to
fix this [stupid] regression, add a fix for keeping caribou onto the
display that is actually the touch screen if possible?

When a secondary monitor is plugged in, and regardless of the displays
positioning, caribou jumps to wherever it desires...

See attached image.

** Attachment added: "caribou-being-a-dick"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723857/+attachment/5006307/+files/Screenshot%20from%202017-11-09%2001-45-13.png

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is 
disabled in System Preferences > Universal Access.  This didn't happen in any 
previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based.

  Test Case
  =
  0. Find a laptop with a touch screen that works.
  1. Settings > Universal Access > Typing > Screen Keyboard = OFF
  2. Touch the screen.

  Regression Potential
  

  Workaround
  ==
  https://extensions.gnome.org/extension/1326/block-caribou/

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

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

[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock

2017-11-08 Thread Rocko

Ok, I'll try that when it happens and I can get ssh access (I can't
always trigger the freeze).

One thing that might be helpful is that every single time I unlock the
screen (whether after resume or not), the UI _always_ freezes for a
second or two, including the mouse pointer. It's as if gnome-shell is
waiting for some event to occur or a condition to become true before it
continues, and in some cases it ends up waiting forever.

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

Title:
  gnome-shell freezes after resume then unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Often after resuming and then entering my password to unlock gnome-
  shell, when I press the enter key gnome-shell immediately freezes. The
  lock screen is still displayed, the mouse no longer responds, and the
  keys no longer respond (I can't even get a tty console with CTRL-ALT-
  Fn key). I have to perform a hard reset at this point because gnome-
  shell remains frozen even after leaving the PC alone for 15 minutes.

  I haven't been able to find any crash files or error logs.

  It seems that this freeze is much more likely to occur if I have
  changed location between suspending and resuming and am therefore
  connecting to a different wifi router. Once, however, it happened at
  home on the same router and I was able to log in via ssh from another
  machine (so only gnome-shell was frozen, not the kernel). However, I
  couldn't see any messages or reason that gnome-shell had crashed, so
  all I could do was reboot (any hints as to what I should try at this
  stage are welcome).

  Bug #1709994 looks similar but in that case a) the user is using Xorg,
  not Wayland, b) he also gets past the lock screen, and c) gnome-shell
  eventually restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:46:43 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago)

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

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

[Desktop-packages] [Bug 1728222] Re: display updates are erroneous during scrolling after starting search

2017-11-08 Thread Michael Rowland Hunter

** Summary changed:

- display updates are errornous during scrolling after starting search
+ display updates are erroneous during scrolling after starting search

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

Title:
  display updates are erroneous during scrolling after starting search

Status in gedit package in Ubuntu:
  New

Bug description:
  Display updates are errornous during scrolling after starting search
  when using LXDE desktop, see attached screenshot for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Oct 28 13:01:06 2017
  InstallationDate: Installed on 2015-12-12 (685 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to artful on 2017-10-19 (8 days ago)

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

to be specific the libvulkan_intel.so and libvulkan_radeon.so i386
provided by mesa-vulkan-drivers:i386

also works great with $ uname -a
Linux 4.14.0-041400rc8-generic #201711052313 SMP Sun Nov 5 23:14:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

thanks for testing!

32bit drivers need 32bit vulkaninfo, and I don't know how to provide
that for 64bit.. so it's a non-issue right now

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-11-08 Thread Nicholas Stommel

@bagl0312 I agree, there really should be some kind of GUI default way
to set negative DNS priority when setting up certain VPN connections.
The average user shouldn't experience a nasty surprise when DNS leaks
happen by default.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions

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

[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2017-11-08 Thread Kai-Heng Feng

Linux kernel v4.4.0-100 in xenial-proposed contains the fix. Please give
it a try.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1731128] Re: script using continously 100% cpu core

2017-11-08 Thread Olivier Tilloy

Is your previous browsing session restored when you launch chromium?
If so, it would be useful to identify which tab is consuming so much CPU. You 
can invoke the chromium task manager with Shift+Esc to find that out.

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

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

Title:
  script using continously 100%  cpu core

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Each time chromium-browser is loaded, i'm seeing a full cpu core usage.
  System-monitor show me that it is "chromium-browser -type=renderer 
-enable-pinch -field-trial-handle=..." that needs to be killed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 62.0.3202.62-0ubuntu0.17.10.1380
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov  9 06:23:52 2017
  DetectedPlugins:
   
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1731128/+subscriptions

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

[Desktop-packages] [Bug 1731125] Re: Help links are broken in 17.10+

2017-11-08 Thread Gunnar Hjalmarsson

My thought: Simply change it to help:gnome-help. I don't think we should
count on a Unity docs team.

One temporary solution for 17.10 and 18.04 might be to upload the 17.04
docs (which is the best we have) to a version neutral Unity folder at
help.ubuntu.com, and provide a link to that index page.

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

Title:
  Help links are broken in 17.10+

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  The Help menu item in unity-control-center doesn't work in Ubuntu
  17.10.

  Note that the system help provided by ubuntu-docs now uses help:gnome-
  help instead of help:ubuntu-help URIs. The help now corresponds with
  the default Ubuntu session help instead of Unity.

  While a team could resurrect the old Unity documentation, it is a big
  job to support it.

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

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

[Desktop-packages] [Bug 158389] Re: Rhythmbox won't recognize a blank CD in my drive

2017-11-08 Thread lee jih shyang

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

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

Title:
  Rhythmbox won't recognize a blank CD in my drive

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: rhythmbox

  I get this error message, even though there is a valid, blank CD in
  the burner drive:

  Please replace the disc in the drive with a rewritable or blank CD.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Oct 29 12:25:25 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: video
  Package: rhythmbox 0.11.2-0ubuntu4
  PackageArchitecture: i386
  ProcCmdline: rhythmbox
  ProcCwd: /home/dhamma
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  Uname: Linux white-tara 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 
i686 GNU/Linux

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

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

[Desktop-packages] [Bug 566437] my trip was amazing

2017-11-08 Thread sailing

Hi friend!

I'd like  to tell you about my last trip, it was packed with adventures,
please learning  much more  here
http://www.perspectivetx.com/tender.php?UE81NjY0MzdAYnVncy5sYXVuY2hwYWQubmV0

Take care, Gianni Massaro


From: Bug 566437 [mailto:566...@bugs.launchpad.net]
Sent: Wednesday, November 08, 2017 11:43 PM
To: giannimass...@inwind.it
Subject: Thank you so much!

I could imagine  a two-person scene with the same punchline:

"Ricky was awfully rude yesterday, turning his back on the pastor like
that."


"Rude? Nah, Ricky's  dumber than a sack  of bricks. I  figure he  was just  
facing the wrong  way and  didn't notice."

The problem, I suppose, is turning it  into  a  standup joke.


Sent from Mail for Windows 10

** Attachment added: "2928BD5A4805EE05.jpg"
   
https://bugs.launchpad.net/bugs/566437/+attachment/5006295/+files/2928BD5A4805EE05.jpg

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

Title:
  package fglrx 2:8.723.1-0ubuntu2 failed to REMOVE: error exit status 2
  - dpkg-divert: mismatch on package - while removing the package

Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Lucid:
  Fix Released
Status in fglrx-installer source package in Natty:
  Fix Released

Bug description:
  I got this error when trying to remove the ATI/AMD proprietary FGLRX
  graphics driver. Despite the error the driver appears to be "not
  activated" after removal.

  == Workaround ==

  Open a terminal and run the following commands:
  $ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

  You can then remove the driver with:
  $ sudo apt-get --purge remove fglrx-kernel-source fglrx-modaliases 
xorg-driver-fglrx fglrx-amdcccle libamdxvba1

  
  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: fglrx 2:8.723.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: fglrx
  AptOrdering:
   fglrx-amdcccle: Remove
   fglrx: Remove
  Architecture: amd64
  Date: Mon Apr 19 08:27:03 2010
  DkmsStatus:

  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUSTeK Computer Inc. F3Sa
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic 
root=UUID=1642ac51-cbdf-4627-86e7-e3715e326a66 ro quiet splash
  SourcePackage: fglrx-installer
  Title: package fglrx 2:8.723.1-0ubuntu2 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 2
  dmi.bios.date: 02/12/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F3Sa
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd02/12/2008:svnASUSTeKComputerInc.:pnF3Sa:pvr1.0:rvnASUSTeKComputerInc.:rnF3Sa:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: F3Sa
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  glxinfo:
   Error: couldn't find RGB GLX visual or fbconfig
   name of display: :0.0
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   x86_64
   kernel: 2.6.32-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/566437/+subscriptions

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

[Desktop-packages] [Bug 1730900] Re: "Login Screen" button not present in Region & Language

2017-11-08 Thread Gunnar Hjalmarsson

On 2017-11-09 06:12, Jeremy Bicha wrote:
>> I may file an upstream bug.
> 
> It's probably worth mentioning in the user help that button and when
> it shows up.

Right. I'll consider that too. Adding a gnome-user-docs task to remember
it.

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

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

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Triaged

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

Title:
  "Login Screen" button not present in Region & Language

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-user-docs package in Ubuntu:
  Triaged

Bug description:
  On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
  Region & Language window includes a "Login Screen" button at the top
  right, which allows me to set language, format and input sources also
  system wide, i.e. affecting the login screen. The Ask Ubuntu answer
   shows its location.

  However, on an (almost) fresh install of Ubuntu 17.10, that button is
  not present.

  I don't know what the intended design is in this respect.

  * If the button is supposed to be there, some dependency necessary for
  it to function might be missing.

  * If the button is not supposed to be there, is there some other GUI
  way to control those settings system wide?

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

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

[Desktop-packages] [Bug 1730281] Re: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen

2017-11-08 Thread PJSingh5000

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

** This bug has been marked a duplicate of bug 1725384
   On touch screens, the apps icon in the dock does not open when touched

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

Title:
  Application icons appear and suddenly disappear when Applications
  Button is activated via a touchscreen

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

Bug description:
  Clicking on the application button (with a mouse) in the Ubuntu Dock
  causes the applications icons to be displayed.

  ISSUE

  On a Touch Screen...

  The issue is, if you touch the application button in the Ubuntu Dock,
  the applications icons appear (expand out from the button using
  animation) but then they suddenly disappear (contract back into the
  button using animation).

  If you touch the button and do not remove your finger, all of the
  icons are displayed on the screen.  As soon as you remove your finger,
  the icons recede back into the button.

  EXPECTED

  Touching the application button (with a finger) in the Ubuntu Dock should 
cause the applications icons to be displayed.  They should continue to be 
displayed until the user selects an application, 
   presses the ESC key, or clicks an icon on the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 00:24:05 2017
  InstallationDate: Installed on 2017-11-03 (2 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1730281/+subscriptions

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

[Desktop-packages] [Bug 1731128] [NEW] script using continously 100% cpu core

2017-11-08 Thread dino99

Public bug reported:

Each time chromium-browser is loaded, i'm seeing a full cpu core usage.
System-monitor show me that it is "chromium-browser -type=renderer 
-enable-pinch -field-trial-handle=..." that needs to be killed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 62.0.3202.62-0ubuntu0.17.10.1380
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Nov  9 06:23:52 2017
DetectedPlugins:
 
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  script using continously 100%  cpu core

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Each time chromium-browser is loaded, i'm seeing a full cpu core usage.
  System-monitor show me that it is "chromium-browser -type=renderer 
-enable-pinch -field-trial-handle=..." that needs to be killed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 62.0.3202.62-0ubuntu0.17.10.1380
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov  9 06:23:52 2017
  DetectedPlugins:
   
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1731128/+subscriptions

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

[Desktop-packages] [Bug 1730900] Re: "Login Screen" button not present in Region & Language

> I may file an upstream bug.

It's probably worth mentioning in the user help that button and when it
shows up.

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

Title:
  "Login Screen" button not present in Region & Language

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

Bug description:
  On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
  Region & Language window includes a "Login Screen" button at the top
  right, which allows me to set language, format and input sources also
  system wide, i.e. affecting the login screen. The Ask Ubuntu answer
   shows its location.

  However, on an (almost) fresh install of Ubuntu 17.10, that button is
  not present.

  I don't know what the intended design is in this respect.

  * If the button is supposed to be there, some dependency necessary for
  it to function might be missing.

  * If the button is not supposed to be there, is there some other GUI
  way to control those settings system wide?

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

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

[Desktop-packages] [Bug 1731125] [NEW] Help links are broken in 17.10+

Public bug reported:

The Help menu item in unity-control-center doesn't work in Ubuntu 17.10.

Note that the system help provided by ubuntu-docs now uses help:gnome-
help instead of help:ubuntu-help URIs. The help now corresponds with the
default Ubuntu session help instead of Unity.

While a team could resurrect the old Unity documentation, it is a big
job to support it.

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Help links are broken in 17.10+

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  The Help menu item in unity-control-center doesn't work in Ubuntu
  17.10.

  Note that the system help provided by ubuntu-docs now uses help:gnome-
  help instead of help:ubuntu-help URIs. The help now corresponds with
  the default Ubuntu session help instead of Unity.

  While a team could resurrect the old Unity documentation, it is a big
  job to support it.

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

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

[Desktop-packages] [Bug 1730900] Re: "Login Screen" button not present in Region & Language

2017-11-08 Thread Gunnar Hjalmarsson

Well, I think I have figured it out.

The behavior is easy to reproduce if there is only one user account on
the system. Then the Login Screen button is not shown, but OTOH changes
of language/format/input sources are written to /etc/default/locale
respective /etc/default/keyboard without asking for it explicitly.

If you add another user, the button shows up.

So this seems to be about the GNOME thinking in this respect which I'm
not used to, and right now I don't like it either. Look at the Ask
Ubuntu answer I linked to. I tried to help the OP based on what I saw on
my own machine (with more than one user account), but the OP didn't
understand what I was talking about.

The GNOME folks seem to be too smart for their own good. Things like
this cause confusion!! :(

Closing. (Some day, when I'm in a better mood, I may file an upstream
bug.)

** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Invalid

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

Title:
"Login Screen" button not present in Region & Language

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

Bug description:
On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
Region & Language window includes a "Login Screen" button at the top
right, which allows me to set language, format and input sources also
system wide, i.e. affecting the login screen. The Ask Ubuntu answer
shows its location.

However, on an (almost) fresh install of Ubuntu 17.10, that button is
not present.

I don't know what the intended design is in this respect.

* If the button is supposed to be there, some dependency necessary for
it to function might be missing.

* If the button is not supposed to be there, is there some other GUI
way to control those settings system wide?

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

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

[Desktop-packages] [Bug 1727015] Re: nvidia-graphics-drivers-304 304.137-0ubuntu1 ADT test failure with linux 4.14.0-3.4

2017-11-08 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu1 ADT test failure with
  linux 4.14.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/n/nvidia-graphics-drivers-304/20171024_133147_bfe9f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/n/nvidia-graphics-drivers-304/20171024_135722_bfe9f@/log.gz

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

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

[Desktop-packages] [Bug 1727016] Re: nvidia-graphics-drivers-340 340.104-0ubuntu2 ADT test failure with linux 4.14.0-3.4

2017-11-08 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  nvidia-graphics-drivers-340 340.104-0ubuntu2 ADT test failure with
  linux 4.14.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/n/nvidia-graphics-drivers-340/20171024_132953_9e651@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/n/nvidia-graphics-drivers-340/20171024_134321_9e651@/log.gz

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

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

[Desktop-packages] [Bug 1731111] Re: libreoffice crashes immediately

2017-11-08 Thread Kyle Bentley

This seems related to AMD's amdgpu pro:

Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging 
symbols found)...done.
(gdb) run
Starting program: /usr/lib/libreoffice/program/soffice.bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe149d700 (LWP 20986)]
[New Thread 0x7fffdf25c700 (LWP 20988)]
[New Thread 0x7fffdea5b700 (LWP 20989)]
[New Thread 0x7fffddf43700 (LWP 20990)]
[New Thread 0x7fffdc1c5700 (LWP 20994)]
[Thread 0x7fffdc1c5700 (LWP 20994) exited]
[Thread 0x7fffdf25c700 (LWP 20988) exited]
[New Thread 0x7fffdc1c5700 (LWP 20995)]

Thread 7 "soffice.bin" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdc1c5700 (LWP 20995)]
0x7fffc85d19ee in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
(gdb) bt
#0  0x7fffc85d19ee in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#1  0x7fffc85d1c79 in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#2  0x7fffc85a7c02 in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#3  0x7fffc85806b9 in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#4  0x7fffc8513fbf in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#5  0x7fffc85916ac in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#6  0x732396ba in start_thread (arg=0x7fffdc1c5700) at 
pthread_create.c:333
#7  0x73ef13dd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

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

Title:
  libreoffice crashes immediately

Status in libreoffice package in Ubuntu:
  New

Bug description:
  kyle@SOONG:~/src/testing$ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
  libreoffice:
Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
Version table:
   *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  This is a relatively new install.  I can't open libreoffice at all
  without it instantly crashing.  Nothing unusual from the terminal,
  just some GTK warnings.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov  8 21:18:44 2017
  InstallationDate: Installed on 2017-10-30 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

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

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

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

** Bug watch added: GNOME Bug Tracker #789984
   https://bugzilla.gnome.org/show_bug.cgi?id=789984

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

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL,

[Desktop-packages] [Bug 1730728] Re: gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

Uploading crash files as attachments is unfortunately not useful to us,
and is also a security risk to you.

Please try running 'apport-cli' on the crash file in place of 'ubuntu-
bug'. It should do the same job and might avoid some problems with
ubuntu-bug.

** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => 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/1730728

Title:
  gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It happens daily, 2 or 3 times. But I don't know what triggers it, and
  I can't reproduce it. Last time it happened I wasn't even in front of
  the computer, and only firefox, thunderbird and skypeforlinux were
  opened (if I'm not mistaken). clamd was running as well. But each time
  it happened, the following has been logged in syslog:

  kernel: [22818.213847] traps: gnome-shell[3063] general protection
  ip:7f58ba1eacdf sp:7fff1dad5578 error:0 in
  libgobject-2.0.so.0.5400.1[7f58ba1b5000+52000]

  Opening a virtual console (like ctrl+shift+f3) was still possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 16:36:22 2017
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['pomod...@arun.codito.in']"
   b'org.gnome.shell' b'command-history' b"['firefox', 'thunderbird', 
'dropboxd', 'firefox', 'skypeforlinux', 'thunderbird', 'darktable', 'dropboxd']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'gnome-control-center.desktop', 'gnome-system-monitor.desktop', 
'org.gnome.Software.desktop', 'firefox.desktop', 'keepass2.desktop', 
'evince.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 
'skype.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-03-01 (616 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-26 (11 days ago)

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

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

[Desktop-packages] [Bug 1731111] [NEW] libreoffice crashes immediately

2017-11-08 Thread Kyle Bentley

Public bug reported:

kyle@SOONG:~/src/testing$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
libreoffice:
  Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
  Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
  Version table:
 *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:5.1.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

This is a relatively new install.  I can't open libreoffice at all
without it instantly crashing.  Nothing unusual from the terminal, just
some GTK warnings.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Nov  8 21:18:44 2017
InstallationDate: Installed on 2017-10-30 (10 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  libreoffice crashes immediately

Status in libreoffice package in Ubuntu:
  New

Bug description:
  kyle@SOONG:~/src/testing$ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
  libreoffice:
Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
Version table:
   *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  This is a relatively new install.  I can't open libreoffice at all
  without it instantly crashing.  Nothing unusual from the terminal,
  just some GTK warnings.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov  8 21:18:44 2017
  InstallationDate: Installed on 2017-10-30 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721927] Re: Empty Trash in Settings doesn't work.

** Description changed:

- In Settings--privacy, there is a entry named "Empty trash and temporary
- files". but it doesn't work. when I clicked the red button EMPTY TRASH,
- the Trash still filled with something.
+ Impact
+ ==
+ In Settings--privacy, there is a entry named "Empty trash and temporary 
files". but it doesn't work. when I clicked the red button EMPTY TRASH, the 
Trash still filled with something.
+ 
+ Test Case
+ =
+ Note that this is a two-part fix. You will need the 3.26.2 versions of both 
gnome-settings-daemon and gnome-control-center.
+ 
+ 1. Create a sample document with Text Editor and save it to your home folder.
+ 2. Open the Files app. Select the sample file and press Delete to send it to 
the Trash.
+ 3. In the Files sidebar, click Trash to verify that the file is there.
+ 4. Open the Settings app.
+ 5. Open the Privacy panel. Click "Purge Trash & Temporary Files". Click 
"Empty Trash" then confirm "Empty Trash".
+ 6. The Trash folder in the Files app should be empty now.
+ 
+ Regression Potential
+ 
+ This fix is part of the GNOME 3.26.2 bug fix release.
+ 
+ The D-Bus method to empty the trash shouldn't be used by anything
+ besides gnome-control-center. If another app does use that, it will need
+ to be updated for the new D-Bus address.
+ 
+ There is a micro-release exception for GNOME:
+ https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

Title:
  Empty Trash in Settings doesn't work.

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Artful:
  Triaged
Status in gnome-settings-daemon source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  In Settings--privacy, there is a entry named "Empty trash and temporary 
files". but it doesn't work. when I clicked the red button EMPTY TRASH, the 
Trash still filled with something.

  Test Case
  =
  Note that this is a two-part fix. You will need the 3.26.2 versions of both 
gnome-settings-daemon and gnome-control-center.

  1. Create a sample document with Text Editor and save it to your home folder.
  2. Open the Files app. Select the sample file and press Delete to send it to 
the Trash.
  3. In the Files sidebar, click Trash to verify that the file is there.
  4. Open the Settings app.
  5. Open the Privacy panel. Click "Purge Trash & Temporary Files". Click 
"Empty Trash" then confirm "Empty Trash".
  6. The Trash folder in the Files app should be empty now.

  Regression Potential
  
  This fix is part of the GNOME 3.26.2 bug fix release.

  The D-Bus method to empty the trash shouldn't be used by anything
  besides gnome-control-center. If another app does use that, it will
  need to be updated for the new D-Bus address.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1729103] Re: Update gnome-desktop3 to 3.26.2

** Changed in: gnome-desktop3 (Ubuntu Artful)
   Status: Triaged => In Progress

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Update gnome-desktop3 to 3.26.2

Status in gnome-desktop3 package in Ubuntu:
  Fix Committed
Status in gnome-desktop3 source package in Artful:
  In Progress

Bug description:
  Impact
  --
  This updates the GNOME version number reported in Settings > Details > About 
to 3.26.2

  We do our own translations so the translation updates should have
  nearly no impact.

  Since we're updating most of the other GNOME packages to 3.26.2, it's
  appropriate to do this update too.

  https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-26
  https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-26

  Test Case
  =
  From Ubuntu 17.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.26.2

  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1731099] Re: Update gnome-settings-daemon to 3.26.2

** Description changed:

  Impact
- =
+ ==
+ This is a new bugfix release from the stable 3.26 branch.
+ 
+ https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS?h=gnome-3-26
+ https://git.gnome.org/browse/gnome-settings-daemon/log?h=gnome-3-26
+ 
+ It also fixes LP: #1721927
+ 
+ Test Case
+ =
+ After installing the update, restart your computer.
+ 
+ Open the Settings app and verify that things appear to work fine.
+ 
+ Regression Potential
+ 
+ gnome-settings-daemon is required for the login screen so a severe bug could 
make it unable to log in normally, but this is a fairly minimal update so that 
risk doesn't seem likely.
+ 
+ There is a micro-release exception for GNOME:
+ https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

** Also affects: gnome-settings-daemon (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Artful)
   Status: New => In Progress

** Changed in: gnome-settings-daemon (Ubuntu Artful)
   Importance: Undecided => Low

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

Title:
  Update gnome-settings-daemon to 3.26.2

Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  This is a new bugfix release from the stable 3.26 branch.

  https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS?h=gnome-3-26
  https://git.gnome.org/browse/gnome-settings-daemon/log?h=gnome-3-26

  It also fixes LP: #1721927

  Test Case
  =
  After installing the update, restart your computer.

  Open the Settings app and verify that things appear to work fine.

  Regression Potential
  
  gnome-settings-daemon is required for the login screen so a severe bug could 
make it unable to log in normally, but this is a fairly minimal update so that 
risk doesn't seem likely.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1731103] Re: Update gnome-control-center to 3.26.2

** Description changed:

Impact
==
+ This is a new bugfix release from the stable 3.26 branch.
+
+ https://git.gnome.org/browse/gnome-control-center/tree/NEWS?h=gnome-3-26
+ https://git.gnome.org/browse/gnome-control-center/log?h=gnome-3-26
+
+ It also fixes LP: #1721927
+
+ Test Case
+ =
+ Open the Settings app and verify that things appear to work fine.
+
+ One easy fix to verify is to open the Wi-Fi panel and press F1. The Help
+ app should load to the Wireless Networking page.
+
+ Close the Help app. Click the Notifications panel and press F1. The Help
+ app should open to the Notifications page.
+
+ Regression Potential
+
+ There is a micro-release exception for GNOME:
+ https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

Title:
Update gnome-control-center to 3.26.2

Status in gnome-control-center package in Ubuntu:
Fix Committed
Status in gnome-control-center source package in Artful:
In Progress

Bug description:
Impact
==
This is a new bugfix release from the stable 3.26 branch.

https://git.gnome.org/browse/gnome-control-center/tree/NEWS?h=gnome-3-26
https://git.gnome.org/browse/gnome-control-center/log?h=gnome-3-26

It also fixes LP: #1721927

Test Case
=
Open the Settings app and verify that things appear to work fine.

One easy fix to verify is to open the Wi-Fi panel and press F1. The
Help app should load to the Wireless Networking page.

Close the Help app. Click the Notifications panel and press F1. The
Help app should open to the Notifications page.

Regression Potential

There is a micro-release exception for GNOME:
https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

This bug is a catch-all bug. If Xwayland crashes for any reason it will
trigger gnome-shell death either in this bug or as bug 1556601.

While we appreciate everyone's efforts in diagnosing problems, in this
particular case the issue is already understood and doesn't need much
more comment.

We can and will try to reduce the number of Xwayland crashes triggering
this, which should be dealt as separate bugs. And separately, ideally,
mutter/gnome-shell should not commit suicide when Xwayland crashes. The
Gnome guys are already aware of this problem and say they would like to
break this dependency in a future version of mutter/gnome-shell. That
way even if Xwayland does crash it won't bring gnome-shell down with it.

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

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 source package in Artful:
  Confirmed
Status in gnome-shell source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed

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

  ---

  Occurred during start-up, before I did anything special...

  1 Ubuntu Wily Werewolf (development branch) 15.10
  2 3.16.3-1ubuntu6
  3&4 not applicable

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gnome-shell 3.16.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 12 19:22:07 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-10-08 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 498933] Re: Crash when restoring data KeyError

2017-11-08 Thread Jonathan

This seems to have helped me (clearing the cache):

mv ~/.cache/duplicity ~/.cache/duplicity.old

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Incomplete
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions

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

[Desktop-packages] [Bug 1731105] Re: /usr/bin/gnome-shell:11:st_widget_style_changed:st_scroll_view_style_changed:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit

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

** This bug has been marked a duplicate of bug 1725312
   gnome-shell crashed with SIGSEGV in st_widget_style_changed()

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

Title:
  /usr/bin/gnome-
  
shell:11:st_widget_style_changed:st_scroll_view_style_changed:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a 
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-shell/+bug/1731105/+subscriptions

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

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

Also tracking in:
https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a

** Description changed:

+ https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a
+ 
+ ---
+ 
  I was restoring a backup when this occurred.  I was not interacting with
  the system at the time.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 06:58:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
-  PC (0x7f840ef624f1) ok
-  source "$0x1" ok
-  destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
+  Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
+  PC (0x7f840ef624f1) ok
+  source "$0x1" ok
+  destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
-  ?? () from /usr/lib/gnome-shell/libst-1.0.so
-  ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
+  ?? () from /usr/lib/gnome-shell/libst-1.0.so
+  ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  I was restoring a backup when this occurred.  I was not interacting
  with the system at the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 06:58:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
   PC (0x7f840ef624f1) ok
   source "$0x1" ok
   destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_widget_style_changed () from

[Desktop-packages] [Bug 1731105] [NEW] /usr/bin/gnome-shell:11:st_widget_style_changed:st_scroll_view_style_changed:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit

2017-11-08 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: artful kylin-17.10 xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
shell:11:st_widget_style_changed:st_scroll_view_style_changed:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a 
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-shell/+bug/1731105/+subscriptions

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

[Desktop-packages] [Bug 498933] Re: Crash when restoring data KeyError

2017-11-08 Thread Jonathan

It  may or may not be related, but before seeing this bug, I had run
restore in a loop on different times, asynchronously, that is to say I
used:

for x in `seq 10 15`
duplicity --time {$x}D ... &

Note the ampersand, I forked them to a background process.
THEN on top of that I hit CTRL-C to force a cancel. This may have corrupted a 
cache.

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Incomplete
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions

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

[Desktop-packages] [Bug 498933] Re: Crash when restoring data KeyError

2017-11-08 Thread Jonathan

I just had this bug on Ubuntu 17.10, duplicity 0.7.12

```
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1546, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
  File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 767, in get_fileobj_iter
backup_set.volume_name_dict[vol_num],
KeyError: 1

```

** Changed in: duplicity
   Status: Expired => Incomplete

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Incomplete
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions

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

[Desktop-packages] [Bug 1731071] Re: Gnome shell huge memory usage

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

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


** This bug has been marked a duplicate of bug 1672297
   gnome-shell uses lots of memory, and grows over time

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

Title:
  Gnome shell huge memory usage

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have no idea why, but after half a day or so of usage, gnome-shell
  uses 1.4 GB of memory. I have never seen an OS where the shell is so
  "hungry", there seem to be lots of memory leaks. Good the system has
  12 GB of RAM, otherwise I would have lots of swap. Unity never did not
  do things like this, I really hope there will be a fix soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 01:32:07 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'weather-extens...@xeked.com', 
'astroweat...@dan-gnome.berrange.com', 'arc-m...@linxgem33.com', 
'gnomeGlobalAppMenu@lestcape']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'chromium-browser.desktop', 'firefox.desktop', 'google-chrome.desktop', 
'org.gnome.Terminal.desktop', 'update-manager.desktop', 'filezilla.desktop', 
'org.gnome.Screenshot.desktop', 'org.kde.ksysguard.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-21 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  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/1731071/+subscriptions

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

[Desktop-packages] [Bug 1731102] [NEW] Poor performance with Wayland

2017-11-08 Thread David Beswick

Public bug reported:

When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
env var) I see the following issues on this hardware:

* Jerky animations (glxgears stutters noticably)
* Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
* High CPU usage when mousing over icons in left-hand side Unity dock (20-30%), 
also causing mouse cursor to stutter
* 15fps in Kodi and poor video playback framerate
* 30-40% CPU usage in Kodi when program idle
* Gnome shell frequently using 25% of CPU or more

All issues disappear when using x11 mode (again confirmed with
XDG_SESSION_TYPE env var). Performance in that case seems as good as
17.04

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
BootLog:
 * Setting up X socket directories...   [240G 
[234G[ OK ]
  * Restoring resolver state...   [240G 
[234G[ OK ]
 Starting jabber server: ejabberd
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 13:03:08 2017
DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] 
[19da:a191]
InstallationDate: Installed on 2011-12-05 (2165 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago)
dmi.bios.date: 10/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.name: AMD HUDSON-M1
dmi.board.vendor: ZOTAC
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 18 20:39:16 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputRiitek Micro Keyboard KEYBOARD, id 8
 inputRiitek Micro Keyboard MOUSE, id 9
 inputRiitek Micro Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug artful performance ubuntu wayland-session

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

Title:
  Poor performance with Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
  env var) I see the following issues on this hardware:

  * Jerky animations (glxgears stutters noticably)
  * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
  * High CPU usage when mousing over icons in left-hand side Unity dock 
(20-30%), also causing mouse cursor to stutter
  * 15fps in Kodi and poor video playback framerate
  * 30-40% CPU usage in Kodi when program idle
  * Gnome shell frequently using 25% of CPU or more

  All issues disappear when using x11 mode (again confirmed with
  XDG_SESSION_TYPE env var). Performance in that case seems as good as
  17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64

[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

2017-11-08 Thread PJSingh5000

Please see gnome bug #790104.

https://bugzilla.gnome.org/show_bug.cgi?id=790104


** Bug watch added: GNOME Bug Tracker #790104
   https://bugzilla.gnome.org/show_bug.cgi?id=790104

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in caribou package in Ubuntu:
  New

Bug description:
  Unable to type capital letters using onscreen keyboard:

  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731103] [NEW] Update gnome-control-center to 3.26.2

Public bug reported:

Impact
==

** Affects: gnome-control-center (Ubuntu)
 Importance: Low
 Status: Fix Committed

** Affects: gnome-control-center (Ubuntu Artful)
 Importance: Low
 Status: In Progress


** Tags: artful upgrade-software-version

** Also affects: gnome-control-center (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: New => In Progress

** Changed in: gnome-control-center (Ubuntu Artful)
   Importance: Undecided => Low

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

Title:
  Update gnome-control-center to 3.26.2

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Artful:
  In Progress

Bug description:
  Impact
  ==

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

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

[Desktop-packages] [Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages

** Project changed: gnome-user-share => gnome-tweak-tool

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

Title:
  Personal file sharing preferences dialog does not offer to install
  needed packages

Status in Ayatana Design:
  Fix Committed
Status in gnome-user-share package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  What happens -> I open the Personal file sharing preferences dialog via 
system-preferences or via nautilus, and Im told that the network sharing 
feature can not be enabled because the required packages are not on your pc.
  I, as a tech user, went to synaptic, found the package, looked for its 
recommends and got the functionality.
  A normal user wont be able to do so, and so a button to install those 
packages is needed for usabilty's sake.

  --

  Desired resolution:

  - Change the "Sharing Options" text in them Nautilus right click folder menu 
to "Local network share"
  - Change the 'Share' tab title text in the Nautilus 'Properties' window to 
"Local network share"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions

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

[Desktop-packages] [Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages

** Project changed: gnome-tweak-tool => gnome-tweak-tool (Ubuntu)

** No longer affects: gnome-tweak-tool (Ubuntu)

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

Title:
  Personal file sharing preferences dialog does not offer to install
  needed packages

Status in Ayatana Design:
  Fix Committed
Status in gnome-user-share package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  What happens -> I open the Personal file sharing preferences dialog via 
system-preferences or via nautilus, and Im told that the network sharing 
feature can not be enabled because the required packages are not on your pc.
  I, as a tech user, went to synaptic, found the package, looked for its 
recommends and got the functionality.
  A normal user wont be able to do so, and so a button to install those 
packages is needed for usabilty's sake.

  --

  Desired resolution:

  - Change the "Sharing Options" text in them Nautilus right click folder menu 
to "Local network share"
  - Change the 'Share' tab title text in the Nautilus 'Properties' window to 
"Local network share"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions

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

[Desktop-packages] [Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages

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

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

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

Title:
  Personal file sharing preferences dialog does not offer to install
  needed packages

Status in Ayatana Design:
  Fix Committed
Status in gnome-user-share package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  What happens -> I open the Personal file sharing preferences dialog via 
system-preferences or via nautilus, and Im told that the network sharing 
feature can not be enabled because the required packages are not on your pc.
  I, as a tech user, went to synaptic, found the package, looked for its 
recommends and got the functionality.
  A normal user wont be able to do so, and so a button to install those 
packages is needed for usabilty's sake.

  --

  Desired resolution:

  - Change the "Sharing Options" text in them Nautilus right click folder menu 
to "Local network share"
  - Change the 'Share' tab title text in the Nautilus 'Properties' window to 
"Local network share"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions

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

[Desktop-packages] [Bug 1731099] Re: Update gnome-settings-daemon to 3.26.2

** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu

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

Title:
  Update gnome-settings-daemon to 3.26.2

Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed

Bug description:
  Impact
  =

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

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

[Desktop-packages] [Bug 1721927] Re: Empty Trash in Settings doesn't work.

** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu

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

Title:
  Empty Trash in Settings doesn't work.

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Artful:
  Triaged
Status in gnome-settings-daemon source package in Artful:
  In Progress

Bug description:
  In Settings--privacy, there is a entry named "Empty trash and
  temporary files". but it doesn't work. when I clicked the red button
  EMPTY TRASH, the Trash still filled with something.

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

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

[Desktop-packages] [Bug 1721927] Re: Empty Trash in Settings doesn't work.

** Also affects: gnome-control-center (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-control-center (Ubuntu Artful)
   Importance: Undecided => Low

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

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Fix Committed

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-settings-daemon (Ubuntu Artful)
   Status: New => In Progress

** Changed in: gnome-settings-daemon (Ubuntu Artful)
   Importance: Undecided => Low

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

Title:
  Empty Trash in Settings doesn't work.

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Artful:
  Triaged
Status in gnome-settings-daemon source package in Artful:
  In Progress

Bug description:
  In Settings--privacy, there is a entry named "Empty trash and
  temporary files". but it doesn't work. when I clicked the red button
  EMPTY TRASH, the Trash still filled with something.

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

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

[Desktop-packages] [Bug 1731098] [NEW] Drag and drop to nautilus does not trigger file extraction

2017-11-08 Thread jeremy-list

Public bug reported:

To replicate: open a .tar.gz archive containing a folder, and drag and
drop the folder to a nautilus window.

Expected results: The folder should be decompressed to the destination
open in the nautilus window.

Actual results: The mouse cursor changes to indicate nautilus is
prepared to accept the dropped folder; but nothing happens when the
mouse button is released.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: file-roller 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 15:01:32 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2017-08-15 (85 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: file-roller
UpgradeStatus: Upgraded to artful on 2017-09-14 (55 days ago)

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Drag and drop to nautilus does not trigger file extraction

Status in file-roller package in Ubuntu:
  New

Bug description:
  To replicate: open a .tar.gz archive containing a folder, and drag and
  drop the folder to a nautilus window.

  Expected results: The folder should be decompressed to the destination
  open in the nautilus window.

  Actual results: The mouse cursor changes to indicate nautilus is
  prepared to accept the dropped folder; but nothing happens when the
  mouse button is released.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: file-roller 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 15:01:32 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2017-08-15 (85 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: file-roller
  UpgradeStatus: Upgraded to artful on 2017-09-14 (55 days ago)

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

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

[Desktop-packages] [Bug 1731099] [NEW] Update gnome-settings-daemon to 3.26.2

Public bug reported:

Impact
=

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Low
 Status: Fix Committed


** Tags: artful upgrade-software-version

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

Title:
  Update gnome-settings-daemon to 3.26.2

Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed

Bug description:
  Impact
  =

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

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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

2017-11-08 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

** Changed in: oem-priority/xenial
   Status: Fix Committed => Fix Released

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions

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

[Desktop-packages] [Bug 1731094] [NEW] Trouble Switching between GPUs on a Carrizo laptop with an integrated and discrete graphics card.

2017-11-08 Thread Craig Stein

Public bug reported:


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

I got the following result:

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

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

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

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

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

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

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

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

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


** Tags: amd64 apport-bug artful ubuntu xrandr

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

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

Status in xorg package in Ubuntu:
  New

Bug description:

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

  I got the following result:

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

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

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

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

  Now however when i attempt to switch

[Desktop-packages] [Bug 1431837] Re: yay! useful info

2017-11-08 Thread Randy Valencia

Hi!


I've just  lately read some useful  information, I assume it might be great for 
you too, please read  at 
http://www.nairutravel.com/hazard.php?UE8xNDMxODM3QGJ1Z3MubGF1bmNocGFkLm5ldA--


Cheers, Sherman Dewitt


From: Bug 1431837 [mailto:1431...@bugs.launchpad.net]
Sent: Wednesday, November 08, 2017 7:27 PM
To: valenciara...@yahoo.com
Subject: Mama I love you!

RNA  seq is  essentially the same as  DNA seq.  There is just an extra
step in which a reverse transcriptase enzyme turns RNA into DNA.


The issue  at hand is that  you have to sample frequently as RNA is  
short-lived. You also have to keep the  samples in the  cold  or treat  them 
with an inhibitor for the enzyme that degrades RNA.

My  guess is that the limit here is how fast you can sample without
hurting the octopus.


Sent from Mail for Windows 10

** Attachment added: "8B36D920140DC132.jpg"
   
https://bugs.launchpad.net/bugs/1431837/+attachment/5006142/+files/8B36D920140DC132.jpg

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

Title:
  package nvidia-331 (not installed) failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 6

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

Bug description:
  input output error , core dumped

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Fri Mar 13 11:43:40 2015
  DuplicateSignature: package:nvidia-331:(not installed):subprocess installed 
post-installation script returned error exit status 6
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  InstallationDate: Installed on 2014-07-21 (235 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: nvidia-graphics-drivers-331
  Title: package nvidia-331 (not installed) failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 6
  UpgradeStatus: Upgraded to utopic on 2015-03-13 (0 days ago)

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

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

[Desktop-packages] [Bug 1729377] Re: AMD r7 250 wrong detection

2017-11-08 Thread brad

** Attachment added: "outpout of glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+attachment/5006143/+files/outpout%20of%20glxinfo.txt

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

Title:
  AMD r7 250 wrong detection

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

Bug description:
  My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD
  8830M. This results in the wrong detection of drivers. The result is a
  wrongly installed driver and very poor performance. This bug has been
  affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10.

  brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller'
  02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Venus LE [Radeon HD 8830M] (rev 87)
  brad@brad-ubuntu:~$ lsmod | grep -i 'radeon'
  radeon   1470464  9
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper
  brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu'
  amdgpu   2007040  0
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper

  Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper
  driver is, xserver-xorg-video-radeon.

  However even after proper installation of the new driver. Ubuntu still
  reports that I am using a mobile graphics card, instead of a desktop
  graphics card.

  Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And 
CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-23 (71 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7721
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A68HM-E33 V2 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 9.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 9.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.version: 9.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1729377] Re: AMD r7 250 wrong detection

2017-11-08 Thread brad

** Attachment added: "Xorg.1.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+attachment/5006144/+files/Xorg.1.log

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

Title:
  AMD r7 250 wrong detection

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

Bug description:
  My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD
  8830M. This results in the wrong detection of drivers. The result is a
  wrongly installed driver and very poor performance. This bug has been
  affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10.

  brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller'
  02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Venus LE [Radeon HD 8830M] (rev 87)
  brad@brad-ubuntu:~$ lsmod | grep -i 'radeon'
  radeon   1470464  9
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper
  brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu'
  amdgpu   2007040  0
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper

  Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper
  driver is, xserver-xorg-video-radeon.

  However even after proper installation of the new driver. Ubuntu still
  reports that I am using a mobile graphics card, instead of a desktop
  graphics card.

  Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And 
CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-23 (71 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7721
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A68HM-E33 V2 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 9.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 9.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.version: 9.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1731071] [NEW] Gnome shell huge memory usage

2017-11-08 Thread florin

Public bug reported:

I have no idea why, but after half a day or so of usage, gnome-shell
uses 1.4 GB of memory. I have never seen an OS where the shell is so
"hungry", there seem to be lots of memory leaks. Good the system has 12
GB of RAM, otherwise I would have lots of swap. Unity never did not do
things like this, I really hope there will be a fix soon.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 01:32:07 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-appindicat...@ubuntu.com', 
'weather-extens...@xeked.com', 'astroweat...@dan-gnome.berrange.com', 
'arc-m...@linxgem33.com', 'gnomeGlobalAppMenu@lestcape']"
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'chromium-browser.desktop', 'firefox.desktop', 'google-chrome.desktop', 
'org.gnome.Terminal.desktop', 'update-manager.desktop', 'filezilla.desktop', 
'org.gnome.Screenshot.desktop', 'org.kde.ksysguard.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2017-10-21 (18 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "gnome shell memory leaks consumption"
   
https://bugs.launchpad.net/bugs/1731071/+attachment/5006128/+files/System%20Monitor_010.jpg

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

Title:
  Gnome shell huge memory usage

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have no idea why, but after half a day or so of usage, gnome-shell
  uses 1.4 GB of memory. I have never seen an OS where the shell is so
  "hungry", there seem to be lots of memory leaks. Good the system has
  12 GB of RAM, otherwise I would have lots of swap. Unity never did not
  do things like this, I really hope there will be a fix soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 01:32:07 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'weather-extens...@xeked.com', 
'astroweat...@dan-gnome.berrange.com', 'arc-m...@linxgem33.com', 
'gnomeGlobalAppMenu@lestcape']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'chromium-browser.desktop', 'firefox.desktop', 'google-chrome.desktop', 
'org.gnome.Terminal.desktop', 'update-manager.desktop', 'filezilla.desktop', 
'org.gnome.Screenshot.desktop', 'org.kde.ksysguard.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-21 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  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/1731071/+subscriptions

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

[Desktop-packages] [Bug 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS

2017-11-08 Thread Caleb

Yes, please bring to 16.04

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

Title:
  Don't write search domains to resolv.conf in the case of split DNS

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  All VPN users meaning to use split-tunnelling in a situation where leaking 
DNS data to the internet about what might be behind their VPN is undesirable.

  [Test case]
  1) connect to VPN
  2) Use dig to request a name that should be on the VPN
  3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only 
gone through the VPN nameservers (only its request number should have increased 
by one)
  4) Use dig to request a name off-VPN, such as google.com.
  5) Verify (kill -USR1 again) that the request has caused the non-VPN 
nameserver request number to increase, and that the VPN number has not 
increased.

  It is easier to verify this when there is as little traffic as
  possible on the system, to avoid spurious DNS requests which would
  make it harder to validate the counters.

  [Regression potential]
  This change modifies the way in which DNS nameservers and search domains are 
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and 
intended to be used to resolve all network requests (which is typically not the 
case for split-tunnelling) or if the public network is intended to always 
resolve all requests while the VPN still provides search domains, one might 
observe incorrect behavior.

  Possible failure cases would include failure to resolve names
  correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving
  to the incorrect values (if the wrong nameserver is used).

  ---

  Currently, NM will write all search domains to both any DNS-handling
  plugins running, and also to resolv.conf / resolvconf; in all cases.

  The issue is that doing so means that in the split-DNS case on VPNs,
  you might get a negative response from all nameservers, then a new
  request by glibc with the search tacked on, to nameservers again,
  which might cause DNS requests for "private" resources (say, on the
  VPN) to be sent to external, untrusted resolvers, or for DNS queries
  not meant for VPN nameservers to be sent through the VPN anyway.

  This is fixable in the case where we have a caching plugin running
  (such as dnsmasq). dnsmasq will already know about the search domains
  and use that to limit queries to the right nameservers when a VPN is
  running. Writing search domains to resolv.conf is unnecessary in this
  case.

  We should still write search domains if no caching gets done, as we
  then need to expect glibc to send requests as it otherwise would.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+subscriptions

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

[Desktop-packages] [Bug 1731068] [NEW] With NVIDIA proprietary drivers, initial login screan appears only on mouse movement

2017-11-08 Thread Michal Bultrowicz

Public bug reported:

After installing the proprietary NVIDIA driver (384) I've been faced
with a black screen after reboot. It turned out, that when I moved the
mouse, the login screen appeared. The screen goes black immediately when
I stop moving the mouse. I can normally put the password in on the black
screen and go on with my life, but, you know, it doesn't look stable :)

After I get the system up from sleeping (which didn't work earlier but
suddenly started working) the log in screen in displayed normally.

My system (Alienware 15 R3) has Intel's i7-7820HK and NVIDIA's GeForce
GTX 1070 Mobile 8GB

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
BootLog: /dev/sda2: clean, 200420/61046784 files, 6117516/244157440 blocks
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Nov  8 23:43:20 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: kubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Subsystem: Dell Device [1028:0774]
 NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:07c0]
InstallationDate: Installed on 2017-11-04 (4 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:58c2 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 187c:0530 Alienware Corporation 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Alienware Alienware 15 R3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=32edfbb9-d0bb-495a-9313-48b5ee124d2b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2017
dmi.bios.vendor: Alienware
dmi.bios.version: 1.1.8
dmi.board.name: Alienware 15 R3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.1.8:bd06/09/2017:svnAlienware:pnAlienware15R3:pvr1.1.8:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.family: Alienware
dmi.product.name: Alienware 15 R3
dmi.product.version: 1.1.8
dmi.sys.vendor: Alienware
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful kubuntu

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

Title:
  With NVIDIA proprietary drivers, initial login screan appears only on
  mouse movement

Status in xorg package in Ubuntu:
  New

Bug description:
  After installing the proprietary NVIDIA driver (384) I've been faced
  with a black screen after reboot. It turned out, that when I moved the
  mouse, the login screen appeared. The screen goes black immediately
  when I stop moving the mouse. I can normally put the password in on
  the black screen and go on with my life, but, you know, it doesn't
  look stable :)

  After I get the system up from sleeping (which didn't work earlier but
  suddenly started working) the log in screen in displayed normally.

  My system (Alienware 15

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

I added the ppa vulkan-smoketest now runs correctly as well as The Talos
Principle. Just one issue left vulkaninfo shows an elf class error on
both of the mesa-vulkan-drivers:i386 packages

** Attachment added: "apt-cache policy and full vulkaninfo"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+attachment/5006110/+files/Updated%20Vulkan%20Info%2017.2.4%20testing

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1731061] [NEW] scanner non funziona

2017-11-08 Thread criceto45

Public bug reported:

 Xsane non riesce a trovare scanner Brother Mfc 5490cn

** 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/1731061

Title:
  scanner non funziona

Status in sane-backends package in Ubuntu:
  New

Bug description:
   Xsane non riesce a trovare scanner Brother Mfc 5490cn

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

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

[Desktop-packages] [Bug 1730900] Re: "Login Screen" button not present in Region & Language

I see the Login Screen button here, so I think we need more information
about how to reproduce this bug.

Are you able to duplicate this issue from a new Ubuntu 17.10 install?

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

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

Title:
  "Login Screen" button not present in Region & Language

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

Bug description:
  On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
  Region & Language window includes a "Login Screen" button at the top
  right, which allows me to set language, format and input sources also
  system wide, i.e. affecting the login screen. The Ask Ubuntu answer
   shows its location.

  However, on an (almost) fresh install of Ubuntu 17.10, that button is
  not present.

  I don't know what the intended design is in this respect.

  * If the button is supposed to be there, some dependency necessary for
  it to function might be missing.

  * If the button is not supposed to be there, is there some other GUI
  way to control those settings system wide?

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

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

[Desktop-packages] [Bug 1726224] Re: wacom invisible mouse pointer in wayland

2017-11-08 Thread Alessandro

I confirm the same behaviour reported by Kostas, the system freezes if I
press the buttons of the tablet.

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

Title:
  wacom invisible mouse pointer in wayland

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet,
  which has touch and pen functionality.

  Controlling the mouse pointer through the touch functionality seems to
  work fine, but using the stylus produced very strange behaviour,
  depending the program.

  - With Firefox there there are two pointers - one that is moving in
  accordance with the stylus movements, and one stays put at the
  position, when the stylus movement was detected.

  - With Darktable the mouse pointer becomes invisible, once it's moved
  inside of the application window (it registers clicks though). Once
  the pointer is moved outside of the application window, it appears
  again.

  I'm running Ubuntu inside of a wayland session.

  libwacom2: 0.24-1

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

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

[Desktop-packages] [Bug 728525] Re: benchmark window is not descriptive enough

2017-11-08 Thread John Parejko

This seems to be very orphaned, but I'm going to ping it again as well:
There is the note to "Please back up important data before using the
write benchmark.", but it's not clear if that's a "we *will* delete your
data" warning, or a "we *might* delete your data, but we'll try not to."

Some clarity on this, and even better an ability to do non-destructive
write testing on mounted partitions, would be very good. As it is, I'm
certainly not going to run the write benchmark...

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

Title:
  benchmark window is not descriptive enough

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-disk-utility

  This is a bug about Benchmark utility in gnome-disk-utility.

  There is no warning / info if read / write tests are destructive or
  safe to be used on a live system.

  Green lines and dots at the bottom are confusing to the user and don't
  tell the user what they mean.

  Also , It would be awesome if there was some way that this info could
  be sent back to some database at ubuntu and users can see and compare
  what other users are getting..

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-disk-utility 2.30.1-2
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
  Uname: Linux 2.6.35-27-generic x86_64
  Architecture: amd64
  Date: Thu Mar  3 21:43:45 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility

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

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

[Desktop-packages] [Bug 1712798] Re: gnome-shell errors out when gsettings-ubuntu-schemas is uninstalled

** Branch linked: lp:~ubuntu-desktop/gnome-shell/ubuntu-artful

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

Title:
  gnome-shell errors out when gsettings-ubuntu-schemas is uninstalled

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Artful:
  In Progress

Bug description:
  [Impact]

  People installing ubuntu-desktop without recommends have a segfault
  when selecting the ubuntu session (not the GNOME vanilla one) on start

  [Test Case]
  * update from the version in proposed
  * ensure you don't have gsettings-ubuntu-schemas installed
  * boot into the ubuntu session
  -> you should have the Shell drawn, you won't have the option to set the 
sound above 100% though.

  [Regression Potential]

  The new code (listener callback) is now all protected by the same
  schema installed condition as when we first listened to it.

  

  Step to reproduce :

  - Install from 
http://archive.ubuntu.com/ubuntu/dists/artful/main/installer-amd64/current/images/netboot/mini.iso
 2017-08-16 07:48
  - Select Command-line install
  - Choose default option (wipe disk)
  - sudo apt update
  - sudo apt install ubuntu-desktop --no-install-recommends
  - reboot
  - upon login, the screen return immediately to the login screen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.25.90.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 24 13:08:38 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  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/1712798/+subscriptions

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

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-08 Thread Ray Link

Correction/Addendum to the SRU justification above:

Fixed in current Ubuntu.  Bionic uses NM 1.8.x.  This bug was fixed in
1.4.

[Impact]

* This LP bug's original submitter backported the upstream 1.4 fix to
1.2, not Upstream.

[Regression Potential]

* The patch changes both nm-dhcp-helper and NetworkManager itself.  As
soon as the new packages are unpacked, the new nm-dhcp-helper will be
used on DHCP lease renewals, with the new Notify mechanism.  Since the
running, old NetworkManager is still expecting Event notifications, the
patched nm-dhcp-helper has fallback capability to Event.

* Once NetworkManager is restarted and is running the patched version,
it will have the new Notify support.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

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

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)

[Desktop-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

2017-11-08 Thread Stratos Goudelis

I switched to KDE Plasma..

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

Title:
  two mouse cursors visible at the same time on rotated screen

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1731053] Re: Update gnome-shell to 3.26.2

** Branch linked: lp:~ubuntu-desktop/gnome-shell/ubuntu-artful

** Branch linked: lp:~ubuntu-desktop/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/1731053

Title:
  Update gnome-shell to 3.26.2

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  gnome-shell has released a new stable bugfix release.

  https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26

  We had already cherry-picked two fixes:
  - fix_reset_initial_focus.patch
  - git_layout-unset-when-headless.patch

  We are also adding a fix for LP: #1712798

  Test Case
  =
  After installing this update, please restart your computer.

  Verify that the default Ubuntu 17.10 desktop still works as well as it
  did before.

  Also log in to the "vanilla" GNOME session to verify that it works
  (you may need to install gnome-session and restart first).

  Optionally, you can go through some of the fixed bugs to verify the
  bug and the fix.

  Regression Potential
  
  GNOME Shell is also used for the login screen so it is really important that

  This is a much smaller update than 3.26.1 (in terms of commits and
  lines of code changed).

  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1712798] Re: gnome-shell errors out when gsettings-ubuntu-schemas is uninstalled

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

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

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

** Changed in: gnome-shell (Ubuntu Artful)
   Status: New => In Progress

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

Title:
  gnome-shell errors out when gsettings-ubuntu-schemas is uninstalled

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Artful:
  In Progress

Bug description:
  [Impact]

  People installing ubuntu-desktop without recommends have a segfault
  when selecting the ubuntu session (not the GNOME vanilla one) on start

  [Test Case]
  * update from the version in proposed
  * ensure you don't have gsettings-ubuntu-schemas installed
  * boot into the ubuntu session
  -> you should have the Shell drawn, you won't have the option to set the 
sound above 100% though.

  [Regression Potential]

  The new code (listener callback) is now all protected by the same
  schema installed condition as when we first listened to it.

  

  Step to reproduce :

  - Install from 
http://archive.ubuntu.com/ubuntu/dists/artful/main/installer-amd64/current/images/netboot/mini.iso
 2017-08-16 07:48
  - Select Command-line install
  - Choose default option (wipe disk)
  - sudo apt update
  - sudo apt install ubuntu-desktop --no-install-recommends
  - reboot
  - upon login, the screen return immediately to the login screen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.25.90.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 24 13:08:38 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  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/1712798/+subscriptions

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

[Desktop-packages] [Bug 1731053] [NEW] Update gnome-shell to 3.26.2

Public bug reported:

Impact
==
gnome-shell has released a new stable bugfix release.

https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26

We had already cherry-picked two fixes:
- fix_reset_initial_focus.patch
- git_layout-unset-when-headless.patch

We are also adding a fix for LP: #1712798

Test Case
=
After installing this update, please restart your computer.

Verify that the default Ubuntu 17.10 desktop still works as well as it
did before.

Also log in to the "vanilla" GNOME session to verify that it works (you
may need to install gnome-session and restart first).

Optionally, you can go through some of the fixed bugs to verify the bug
and the fix.

Regression Potential

GNOME Shell is also used for the login screen so it is really important that

This is a much smaller update than 3.26.1 (in terms of commits and lines
of code changed).

GNOME 3.26 distros will be shipping this update.

There is a micro-release exception for GNOME:
https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

** Affects: gnome-shell (Ubuntu)
 Importance: Low
 Status: Fix Committed

** Affects: gnome-shell (Ubuntu Artful)
 Importance: Low
 Status: In Progress

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

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

** Changed in: gnome-shell (Ubuntu Artful)
   Status: New => In Progress

** Description changed:

  Impact
  ==
  gnome-shell has released a new stable bugfix release.
  
  https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26
  
  We had already cherry-picked two fixes:
  - fix_reset_initial_focus.patch
  - git_layout-unset-when-headless.patch
+ 
+ We are also adding a fix for LP: #1712798
  
  Test Case
  =
  After installing this update, please restart your computer.
  
  Verify that the default Ubuntu 17.10 desktop still works as well as it
  did before.
  
  Also log in to the "vanilla" GNOME session to verify that it works (you
  may need to install gnome-session and restart first).
  
  Optionally, you can go through some of the fixed bugs to verify the bug
  and the fix.
  
  Regression Potential
  
- GNOME Shell is also used for the login screen so it is really important that 
+ GNOME Shell is also used for the login screen so it is really important that
  
  This is a much smaller update than 3.26.1 (in terms of commits and lines
  of code changed).
  
  GNOME 3.26 distros will be shipping this update.
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

Title:
  Update gnome-shell to 3.26.2

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  gnome-shell has released a new stable bugfix release.

  https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26

  We had already cherry-picked two fixes:
  - fix_reset_initial_focus.patch
  - git_layout-unset-when-headless.patch

  We are also adding a fix for LP: #1712798

  Test Case
  =
  After installing this update, please restart your computer.

  Verify that the default Ubuntu 17.10 desktop still works as well as it
  did before.

  Also log in to the "vanilla" GNOME session to verify that it works
  (you may need to install gnome-session and restart first).

  Optionally, you can go through some of the fixed bugs to verify the
  bug and the fix.

  Regression Potential
  
  GNOME Shell is also used for the login screen so it is really important that

  This is a much smaller update than 3.26.1 (in terms of commits and
  lines of code changed).

  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-08 Thread Ray Link

[Impact]

 * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
   lease renewal due to a DBus race condition.

 * Upstream NetworkManager 1.4 fixes the race condition by changing
   nm-dhcp-helper's DBus notification from signal "Event" to method
   "Notify".

 * Upstream backported NM 1.4's nm-dhcp-helper notification fix to
   NM 1.2.  This SRU request applies that backported patch to Xenial's
   NM 1.2.x.

[Test Case]

 * Not reliably reproducible.  Out of hudreds of machines, only a
   dozen or so fail to notify NetworkManager of a DHCP lease
   renewal about 30-50% of the time.  (i.e. It's always the same
   handful of machines that fail.)

 * All such machines with the patched packages have been fine for weeks,
   over many dozens of lease renewals.

[Regression Potential]

 * Minimal.  Upstream's patch falls back to the former behavior if the
   new behavior is not supported or times out.

[Other Info]

 * Upstream bug w/ patch:
https://bugzilla.gnome.org/show_bug.cgi?id=784636

 * RHEL bug with links to the 1.4 commits from which the patch was
   derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

** Bug watch added: Red Hat Bugzilla #1373276
   https://bugzilla.redhat.com/show_bug.cgi?id=1373276

** Patch added: "nm-dhcp-helper.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1696415/+attachment/5006066/+files/nm-dhcp-helper.debdiff

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

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

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819

[Desktop-packages] [Bug 1727016] Re: nvidia-graphics-drivers-340 340.104-0ubuntu2 ADT test failure with linux 4.14.0-3.4

2017-11-08 Thread Seth Forshee

Attaching fix.

** Patch added: "nvidia-graphics-drivers-340_340.104-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1727016/+attachment/5006067/+files/nvidia-graphics-drivers-340_340.104-0ubuntu3.debdiff

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  nvidia-graphics-drivers-340 340.104-0ubuntu2 ADT test failure with
  linux 4.14.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/n/nvidia-graphics-drivers-340/20171024_132953_9e651@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/n/nvidia-graphics-drivers-340/20171024_134321_9e651@/log.gz

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

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

[Desktop-packages] [Bug 1730149] Re: No option to set a 2nd display as mirrored in Ubuntu 17.10

2017-11-08 Thread Lucas Cofresi

This turns out not to be a bug, but simply a different (and, it turns
out, a much improved) interface for the same purposes. I apologize for
the haste (also, I could not find a way to simply rescind it).

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

** Converted to question:
   
https://answers.launchpad.net/ubuntu/+source/gnome-control-center/+question/660501

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

Title:
  No option to set a 2nd display as mirrored in Ubuntu 17.10

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

Bug description:
  Up to rel 17.04, we were able to choose the mode for a second display
  as either "mirrored" or "extended". With rel 17.10, it always defaults
  to "extended".

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

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

[Desktop-packages] [Bug 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-11-08 Thread Łukasz Zemczak

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

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  New

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

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

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

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-08 Thread Ray Link

Upstream GNOME bug fixed.  I've applied the fix to Xenial's NM and
tested.  SRU incoming.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

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

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu0.16.04.4

---
network-manager-applet (1.2.6-0ubuntu0.16.04.4) xenial; urgency=medium

  * debian/patches/git_fix_wrong_status_for_wireless_toggle.patch:
* Fix failing to load / use nma gir bindings. LP: #1107935

 -- Dimitri John Ledkov   Tue, 31 Oct 2017 15:04:49
+

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions

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

[Desktop-packages] [Bug 1107935] Update Released

2017-11-08 Thread Łukasz Zemczak

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

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions

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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

This bug was fixed in the package ubiquity - 2.21.63.5

---
ubiquity (2.21.63.5) xenial; urgency=medium

  * Cherry-pick support for WPA2 Enterprise. LP: #1107935
  * Automatic update of included source packages: console-setup
1.108ubuntu15.4.

 -- Dimitri John Ledkov   Tue, 31 Oct 2017 17:45:29
+

** Changed in: ubiquity (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions

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

[Desktop-packages] [Bug 1727015] Re: nvidia-graphics-drivers-304 304.137-0ubuntu1 ADT test failure with linux 4.14.0-3.4

2017-11-08 Thread Seth Forshee

Attaching fix.

** Patch added: "nvidia-graphics-drivers-304_304.137-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1727015/+attachment/5006030/+files/nvidia-graphics-drivers-304_304.137-0ubuntu2.debdiff

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu1 ADT test failure with
  linux 4.14.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/n/nvidia-graphics-drivers-304/20171024_133147_bfe9f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/n/nvidia-graphics-drivers-304/20171024_135722_bfe9f@/log.gz

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

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

[Desktop-packages] [Bug 1731036] [NEW] package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que es distinto de otras i

2017-11-08 Thread Miqueas Josue Martinez Marcano

Public bug reported:

the specified package is not updated and says that it looks like it is
broken

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libglib2.0-0 2.52.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Wed Nov  8 15:53:23 2017
ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libglib2.0-0/NEWS.gz', que es distinto de otras instancias del 
paquetes libglib2.0-0:amd64
InstallationDate: Installed on 2017-11-08 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: glib2.0
Title: package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que es 
distinto de otras instancias del paquetes libglib2.0-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando
  sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que
  es distinto de otras instancias del paquetes libglib2.0-0:amd64

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  the specified package is not updated and says that it looks like it is
  broken

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.52.0-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Wed Nov  8 15:53:23 2017
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libglib2.0-0/NEWS.gz', que es distinto de otras instancias del 
paquetes libglib2.0-0:amd64
  InstallationDate: Installed on 2017-11-08 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que es 
distinto de otras instancias del paquetes libglib2.0-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731036/+subscriptions

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

[Desktop-packages] [Bug 1731031] Re: Kernel Oops with 17.10

2017-11-08 Thread Henning Meyer

xorg was auto selected when I used apport and said "freeze"

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

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

Title:
  Kernel Oops with 17.10

Status in linux package in Ubuntu:
  New

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1731031] [NEW] Kernel Oops with 17.10

2017-11-08 Thread Henning Meyer

Public bug reported:

have captured dmesg just before oops

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Nov  8 20:41:14 2017
DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: kubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011a]
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to load 
user image: Failed to open file '/home/hmeyer/.face': No such file or directory
MachineType: Apple Inc. MacBookPro11,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
dmi.bios.date: 02/22/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B17.1602221718
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Nov  8 20:39:06 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful fonts kubuntu

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

Title:
  Kernel Oops with 17.10

Status in linux package in Ubuntu:
  New

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias:

[Desktop-packages] [Bug 1731030] Re: PS3 Controller causes screen to rotate

2017-11-08 Thread fcole90

This happens both with Xorg and Wayland sessions.

The controller is an original Dualshock 3 Contoller. If I just plug the
controller in it doesn't cause any screen rotation, but pressing the
"home button" triggers the issue.

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

Title:
  PS3 Controller causes screen to rotate

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I attach and turn on my PS3 controller to my laptop, the screen
  get's rotated of 180 degrees.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 21:31:47 2017
  InstallationDate: Installed on 2017-08-21 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731030] [NEW] PS3 Controller causes screen to rotate

2017-11-08 Thread fcole90

Public bug reported:

When I attach and turn on my PS3 controller to my laptop, the screen
get's rotated of 180 degrees.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-session 3.26.1-0ubuntu7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 21:31:47 2017
InstallationDate: Installed on 2017-08-21 (79 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "VID_20171108_212004.mp4"
   
https://bugs.launchpad.net/bugs/1731030/+attachment/5005983/+files/VID_20171108_212004.mp4

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

Title:
  PS3 Controller causes screen to rotate

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I attach and turn on my PS3 controller to my laptop, the screen
  get's rotated of 180 degrees.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 21:31:47 2017
  InstallationDate: Installed on 2017-08-21 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

Awesome Thank you. I'll revert from Oibaf's ppa later today looking
forward to checking them out

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-11-08 Thread Schoof

sorry, #80 was designated for (similar) Bug 1724639...

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-11-08 Thread Schoof

today xubuntu deployed kernel 4.0.13-17. Looking into grub editor at
starton, gfxpayload option isn't shown any more. Does kernel update edit
grub boot options? If yes, how is etc/default/grub updated? Otherwise
latter update-grub would restore options of historic version?

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

a new version has been uploaded to xenial/artful/bionic, and for X/A you
can find it also on the updates ppa:

https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates

(artful still building ATM)

** Changed in: mesa (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1730993] Re: Bluetooth stops working shortly after connecting to WiFi

2017-11-08 Thread John W. Galvin

** Summary changed:

- Bluetooth stops shortly working after connecting to WiFI
+ Bluetooth stops working shortly after connecting to WiFi

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

Title:
  Bluetooth stops working shortly after connecting to WiFi

Status in network-manager package in Ubuntu:
  New

Bug description:
  On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-
  Fi, 2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10,
  when using WiFi, bluetooth will stop working within a minute or two of
  connecting to WiFI.  Specifically a bluetooth mouse (Logitech
  MXAnywhere2) will stop working under these circumstances and will not
  work again until the laptop is restarted.  This does not happen when
  WiFi is not in use (no network or wired network).  This did not happen
  at all in Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:16:05 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
   192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 
metric 100 
   192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1730993/+subscriptions

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

[Desktop-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

2017-11-08 Thread Eric Desrochers

Sponsored for Artful.

* Manual run of autopkgtest has been successful :
--
adt-run [09:26:47]:  summary
cups-core-drivers PASS
cups PASS

- Eric

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

Thanks for the update. I'm glad to see I wasn't imagining things or a 
user/hardware issue on my end.
When Ubuntu updated the mesa packages to 17.2.2 I made sure apport had the 
extra packages installed it needed. I also manually installed the 4 vulkan 
ddbug packages before running the vulkan-smoketest. Apport kicked in and 
auto-reported it. Hopefully that generated report helped since it does a far 
better job that my first attempt.

After I rebuilt the Ubuntu vulkan-utils package and used quilt to
restore the amd mesa source but was unable to rebuilt mesa for the mesa
vulkan drivers so was unable to test them. I had observed what the patch
was doing and came to the decision that radv was being disabled by
design. Thats why I didn't report upstream I didn't want to waste dev
time for what appeared to be a packaging choice. My apologies for that.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Triaged
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1731008] [NEW] Multi-monitor display arrangement doesn't work in Ubuntu 17.10

2017-11-08 Thread John W. Galvin

Public bug reported:

When using a fresh install of Ubuntu 17.10 desktop on a Lenovo T570
laptop in a Lenovo ThinkPad Ultra Dock (40A20090XX), with the buitin
monitor off (laptop closed) and 3 external 1920 x 1080 monitors (1 x
Acer V246HL VGA, 2 x Dell P2417H DisplayPort) display arrangement in
Settings | Devices | Displays does not work.  The Dell monitors show up
as 4 and 3, the Acer as 2.  1, the builtin monitor, is not displayed in
the arrangement area.  The monitor icons show up, left to right, in the
order 4, 3, 2.  It is almost impossible to change that order.  I have
managed, in 1 out of 20 attempts, to get the display icons into a 4, 2,
3 order, but in no case have I been able to apply any arrangement
changes.  The Apply button is never displayed.  I want to get them into
a 2, 4, 3 order.  This was not an issue in Ubuntu Gnome 17.04, in that
version everything worked fine.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 10:51:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:2247]
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20H9000NUS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1VET32W (1.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20H9000NUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET32W(1.22):bd06/02/2017:svnLENOVO:pn20H9000NUS:pvrThinkPadT570:rvnLENOVO:rn20H9000NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T570
dmi.product.name: 20H9000NUS
dmi.product.version: ThinkPad T570
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Multi-monitor display arrangement doesn't work in Ubuntu 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  When using a fresh install of Ubuntu 17.10 desktop on a Lenovo T570
  laptop in a Lenovo ThinkPad Ultra Dock (40A20090XX), with the buitin
  monitor off (laptop closed) and 3 external 1920 x 1080 monitors (1 x
  Acer V246HL VGA, 2 x Dell P2417H DisplayPort) display arrangement in
  Settings | Devices | Displays does not work.  The Dell monitors show
  up as 4 and 3, the Acer as 2.  1, the builtin monitor, is not
  displayed in the arrangement area.  The monitor icons show up, left to
  right, in the order 4, 3, 2.  It is almost impossible to change that
  order.  I have managed, in 1 out of 20 attempts, to get the display
  icons into a 4, 2, 3 order, but in no case have I been able to apply
  any arrangement changes.  The Apply button is never displayed.  I want
  to get them into a 2, 4, 3 order.  This was not an issue in Ubuntu
  Gnome 17.04, in that version everything worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:51:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620

[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login

2017-11-08 Thread Phil Hanson

been testing out some things with this - starting with both montitors
correct, left monitor is primary, mouse moves across to right monitor
ok. Then reboot/logoff and back on, monitors reversed and I have to
manually change in settings / displays etc.

before the reboot, after manually making the correct display settings -
I see in:  stat -c  %y .config/monitors.xml a timestamp of 2017-11-08
17:11:55.624995543 +0100

after the reboot the displays are back in the wrong setting and
timestamp in stat -c  %y .config/monitors.xml = 11-08 17:41:21.223296912
+0100

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

Title:
  Dual monitor configuration not saved across logout / login

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  System76 Galaga UltraPro laptop.

  Two monitors, one plugged into the DisplayPort and one plugged into
  HDMI.

  I use the Displays settings page to tell the system which monitor is
  on the right and which is on the left, and tell it to make the left
  monitor the primary one. All is well.

  Then I log out and log back in.

  Now the two monitors are reversed -- i.e., it thinks that the monitor
  on the right is on the left and vice versa -- and the right monitor
  (which, remember, it thinks is on the left) is the primary one.

  In short, it forgets the configuration I told it to use immediately
  before logging out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:55:09 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (157 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)

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

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

[Desktop-packages] [Bug 702452]

2017-11-08 Thread Hein

I've tested this now and I can confirm it works nicely. Thanks, this
improves the experience for our users quite a bit.

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

Title:
  [launcher] Wine applications are wrongly matched

Status in BAMF:
  Confirmed
Status in libwnck:
  Fix Released
Status in Unity:
  Confirmed
Status in Wine:
  Unknown
Status in bamf package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  After launching a Wine app from terminal or via gnome-do, it appears in the 
launcher with the Wine icon, instead of its own icon. The title is "Wine Window 
Program Loader" instead of the proper application name.
  It can't be favorited since it will favorite the wine executable itself.
  And obviously different wine apps are all grouped under the same launcher 
icon.

  See also bug #635223 about Wine applications not showing up in the
  dash.

  
-

  A way to fix this is to make all the Wine generated .desktop file to
  include a StartupWMClass value that matches the instance name of the
  related program (generally the .exe file name to be executed).

  So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding 
this parameter:
   StartupWMClass=firefox.exe

  Wine should try to add this information at file generation time.

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

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

[Desktop-packages] [Bug 1730993] [NEW] Bluetooth stops shortly working after connecting to WiFI

2017-11-08 Thread John W. Galvin

Public bug reported:

On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-Fi,
2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10, when
using WiFi, bluetooth will stop working within a minute or two of
connecting to WiFI.  Specifically a bluetooth mouse (Logitech
MXAnywhere2) will stop working under these circumstances and will not
work again until the laptop is restarted.  This does not happen when
WiFi is not in use (no network or wired network).  This did not happen
at all in Ubuntu 17.04.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 10:16:05 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
 172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
 192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 metric 
100 
 192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

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

Title:
  Bluetooth stops shortly working after connecting to WiFI

Status in network-manager package in Ubuntu:
  New

Bug description:
  On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-
  Fi, 2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10,
  when using WiFi, bluetooth will stop working within a minute or two of
  connecting to WiFI.  Specifically a bluetooth mouse (Logitech
  MXAnywhere2) will stop working under these circumstances and will not
  work again until the laptop is restarted.  This does not happen when
  WiFi is not in use (no network or wired network).  This did not happen
  at all in Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:16:05 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
   192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 
metric 100 
   192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1730993/+subscriptions

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

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

2017-11-08 Thread Bug Watch Updater

** Changed in: mesa
   Status: Unknown => In Progress

** Changed in: mesa
   Importance: Unknown => Medium

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I was restoring a backup when this occurred.  I was not interacting
  with the system at the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 06:58:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
   PC (0x7f840ef624f1) ok
   source "$0x1" ok
   destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

** Bug watch added: freedesktop.org Bugzilla #101691
   https://bugs.freedesktop.org/show_bug.cgi?id=101691

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=101691
   Importance: Unknown
   Status: Unknown

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

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

[Desktop-packages] [Bug 1727390] Re: New bugfix release 17.2.4