[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-05-04 Thread Tobias
Confirm that as well with clean install of Ubuntu gnome 17.04  yesterday, but 
maybe can give little support...
Before I decided to install I tried via Live-USB Stick and also connected to my 
google account.
Worked like a charm! Login-Screen that opened from Google was the old one!
After I installed ubuntu and wanted to creat again it didnt work again and 
ubuntu offered me new login screen.
I did a quick web search and found an interesting information here:
https://support.google.com/accounts/answer/7338427?co=GENIE.Platform%3DDesktop&hl=en

See the following:

You might still see the old sign-in page in these cases:
You use an older version of a browser
You've turned off JavaScript

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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


[Desktop-packages] [Bug 1671612] Re: Software app only shows explicitly compatible GNOME Shell extensions

2017-05-04 Thread Bug Watch Updater
** Changed in: gnome-software
   Status: In Progress => Fix Released

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

Title:
  Software app only shows explicitly compatible GNOME Shell extensions

Status in GNOME Software:
  Fix Released
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  Only gnome-shell extensions explicitly marked as compatible with the
  running gnome-shell version are shown in the Addons category in gnome-
  software.

  This is a problem when a beta version of gnome- shell is packaged.

  It's a problem when a new gnome-shell version is first released
  because it takes time for developers to test the extension and mark it
  as compatible. It's also a problem because gnome-software only checks
  for extension updates every 7 days.

  Some extensions still work but haven't been updated in a very long
  time.

  More discussion on the attached GNOME bug, particularly comment 7 and
  at GNOME bug 776460

  
  Original Bug Report
  ---
  Update: This behavior was because gnome-shell was a 3.23 development snapshot 
and no extensions at extensions.gnome.org were marked as being explicitly 
compatible with that version.

  GNOME Software 3.22 includes a plugin to show GNOME Shell extensions
  when GNOME Shell is running.

  On the home page, click Add-Ons.

  Except that the Add-Ons button is not showing up here.

  gnome-software 3.22.6-0ubuntu1
  Ubuntu GNOME 17.04 Beta

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

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


[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-05-04 Thread Jesse
Confirm on my Ubuntu GNOME 17.04 machines, too. Seems to be stemming
from Google's new sign-on page. GOA, Ephiphany, and Thunderbird 45.8.0
all get similar errors, now, when trying to access a user's Google
account. Tsk tsk, Google.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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


[Desktop-packages] [Bug 1687245] Re: Improper lock screen scaling on 4k monitor

2017-05-04 Thread Justin
** Also affects: gnome-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Improper lock screen scaling on 4k monitor

Status in Ubuntu GNOME:
  New
Status in gnome-desktop package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu Gnome 17.04, fully up to date. On the lock screen,
  the features are much smaller than the normal ones on a 4k monitor,
  even with no scaling enabled. I'll give you any other information
  you'd like upon request, I just don't know what else you'd need to
  replicate this. Please tell me if I should submit this to gnome
  instead.

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

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


[Desktop-packages] [Bug 1687253] Re: Can't Dock to Higher Resolution Monitor Without Reboot

2017-05-04 Thread Justin
** Also affects: gnome-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't Dock to Higher Resolution Monitor Without Reboot

Status in Ubuntu GNOME:
  New
Status in gnome-desktop package in Ubuntu:
  New

Bug description:
  The title is fairly self explanatory: I have an ASUS UX305C laptop
  with a UHD screen, and when I plug it into a 27 inch monitor via an
  HDMI cable to dock it, there's no way to achieve the standard DPI
  scaling that the system UI does without rebooting. With the major
  increases in 4k monitor popularity, docking a laptop to a higher
  resolution monitor is going to become a very common use case in the
  future, and attempts to accommodate it should be made. I know that
  this is difficult to do as not all programs draw things the same way,
  but you should at least be able to make this work for system apps.

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

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


[Desktop-packages] [Bug 1688453] Re: Installer Freezes When Installing .Deb Package

2017-05-04 Thread Justin
** Summary changed:

- Installer Freezes When Installing Debian App
+ Installer Freezes When Installing .Deb Package

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

Title:
  Installer Freezes When Installing .Deb Package

Status in Ubuntu GNOME:
  New
Status in software-center package in Ubuntu:
  New

Bug description:
  In Ubuntu Gnome 17.04, as of the most recent update, when I open a
  downloaded .deb file, it goes to the package manager, but when I click
  install, the install button goes white and nothing happens. Replicated
  across two systems.

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

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


[Desktop-packages] [Bug 1688453] [NEW] Installer Freezes When Installing Debian App

2017-05-04 Thread Justin
Public bug reported:

In Ubuntu Gnome 17.04, as of the most recent update, when I open a
downloaded .deb file, it goes to the package manager, but when I click
install, the install button goes white and nothing happens. Replicated
across two systems.

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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

** Also affects: software-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Installer Freezes When Installing Debian App

Status in Ubuntu GNOME:
  New
Status in software-center package in Ubuntu:
  New

Bug description:
  In Ubuntu Gnome 17.04, as of the most recent update, when I open a
  downloaded .deb file, it goes to the package manager, but when I click
  install, the install button goes white and nothing happens. Replicated
  across two systems.

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

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


[Desktop-packages] [Bug 1687252] Re: Gnome Software Center Showing Duplicate Installed Apps

2017-05-04 Thread Justin
And photos.

** Tags added: software-center

** Also affects: software-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Gnome Software Center Showing Duplicate Installed Apps

Status in Ubuntu GNOME:
  New
Status in software-center package in Ubuntu:
  New

Bug description:
  In the software store on Ubuntu Gnome 17.04, fully updated, some apps show up 
as installed twice without be doing anything command line installs, updates, 
etc. This currently effects the Software & Updates app and Chromium app 
(installed from the most popular software store options, I'm also confused why 
3 show there). I installed re-downloaded images on a second computer to verify 
this 
  issue further. Print screen showing the duplicates attached. Several other 
apps showed duplicated on installation (including ImageMagick), but went away 
after rebooting.

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Description changed:

  [Impact]
  
- hwe-16.04 refresh for 16.04.3
+ *** hwe-16.04 refresh for 16.04.3 ***
  
- Many packages need debhelper10 or would have to revert various packaging
- changes to work with dh9.
+ Revert changes to use debhelper10.
  
- xorg-server 1.19 needs updates
+ xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)
  
- x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
- the unity mouse config doesn't work with -libinput.
+ x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
+ x-x-i-libinput needs newer libinput, which in turn needs libwacom update.
+ 
+ Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.
  
  [Test case]
  
  upgrade from/to stock & old hwe stack, test desktop usage
  
  [Regression potential]
  
  zesty hasn't blown up
  
  [Other information]
  
  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
- 2. libclc
- 3. mesa, xorg-server
+ 2. libclc, xorg-server (build-dep libxfont1-dev)
+ 3. mesa, xorg-server-hwe-16.04
  4. drivers
- 5. xorg
+ 5. xorg-hwe-16.04

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
  2. libclc, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
  2. libclc, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Bug Watch Updater
** Changed in: gnome-user-docs
   Status: Unknown => Confirmed

** Changed in: gnome-user-docs
   Importance: Unknown => Medium

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

Title:
  Missing keyboard-key-*.svg icons

Status in Gnome Documentation:
  Confirmed
Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  New

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Bug Watch Updater
** Changed in: gnome-user-docs (Debian)
   Status: Unknown => New

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

Title:
  Missing keyboard-key-*.svg icons

Status in Gnome Documentation:
  Unknown
Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  New

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1571540] Re: Moving files nautilus extremely slow

2017-05-04 Thread pchaivaro
My laptop transfer file within ssd drive the transfers rate is 23.6 kB/sec.
Painfully slow...

** Attachment added: "slow.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1571540/+attachment/4872117/+files/slow.png

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

Title:
  Moving files nautilus extremely slow

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When I move a lot of files from  (ex.  two hundred images)  from one
  folder to another on the same harddrive, I get a message "Preparing to
  move x files"and it takes a long time to move them. The filesystem is
  btrfs (raid 1). The folder is linked to another folder because my main
  system hdd is a ssd drive. (Ex. /home/data/Pictures
  ~/username/Pictures/ ) All the userdata subfolders are stored on btrfs
  hdd (ex. /home/username/Downloads etc..)  Moving files via commandline
  is instant.

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  ii  libnautilus-extension1a:amd64   
1:3.18.4.is.3.14.3-0ubuntu4 amd64libraries for 
nautilus components - runtime version
  ii  nautilus
1:3.18.4.is.3.14.3-0ubuntu4 amd64file manager 
and graphical shell for GNOME
  ii  nautilus-data   
1:3.18.4.is.3.14.3-0ubuntu4 all  data files for 
nautilus
  ii  nautilus-sendto 
3.8.2-1ubuntu1  amd64integrates 
Evolution and Pidgin into the Nautilus file manager
  ii  nautilus-share  
0.7.3-2ubuntu1  amd64Nautilus 
extension to share folder using Samba

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Gunnar Hjalmarsson
** Bug watch added: GNOME Bug Tracker #782198
   https://bugzilla.gnome.org/show_bug.cgi?id=782198

** Also affects: gnome-user-docs via
   https://bugzilla.gnome.org/show_bug.cgi?id=782198
   Importance: Unknown
   Status: Unknown

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

Title:
  Missing keyboard-key-*.svg icons

Status in Gnome Documentation:
  Unknown
Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Gunnar Hjalmarsson
Or wait, I realize now that the problem is in gnome-help/Makefile.am.

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Gunnar Hjalmarsson
They also exist here:

https://git.gnome.org/browse/gnome-user-docs/snapshot/gnome-user-
docs-3.24.0.tar.xz

>From where did you get the tarball for Ubuntu? ;)

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Jeremy Bicha
Yes, it's a Debian issue too.

Yes, the files exist in git, but…

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Gunnar Hjalmarsson
Well, the web site issue may be, but since the files exist in git, isn't
it a Debian issue as well?

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-05-04 Thread Rifester
Can confirm this on new 17.04 and 17.10 installs.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Jeremy Bicha
It's upstream in GNOME.

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Gunnar Hjalmarsson
** Bug watch added: Debian Bug tracker #861869
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861869

** Also affects: gnome-user-docs (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861869
   Importance: Unknown
   Status: Unknown

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New
Status in gnome-user-docs package in Debian:
  Unknown

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1547870] Re: libsane-dev lacks sanei.h header required by some scanner drivers

2017-05-04 Thread Olaf Meeuwissen
Please note that all `sanei*` files are for internal use by the sane-
backends package only.  These files are *not* intended to be shared in
any way outside of the scope of sane-backends.

If third party backends want to reuse some of these files that is their
decision and that's fine buty they should include (and maintain) their
own copies.  The SANE project does not and will not guarantee any kind
of API/ABI compatibility for what's in the `sanei*` files.

None of the `sanei*.h` header files belong in a `libsane-dev` package
and I suggest to close this bug report as a "Won't fix".

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

Title:
  libsane-dev lacks sanei.h header required by some scanner drivers

Status in sane-backends package in Ubuntu:
  New

Bug description:
  After installing libsane-dev in /usr/include/sane/ there are sane.h
  and saneopts.h files but not sanei.h file which is required by some
  packages. Eg. Canon DR_2020U driver here http://software.canon-
  europe.com/software/0045134.asp .

  The problems covers more header files, at least: sanei_net.h,
  sanei_wire.h, sanei_usb.h, config.h, sanei_codec_bin.h,
  sanei_backend.h, sanei_debug.h, sanei_config.h.

  
  All those are present in include/sane directory of sane-backends git source 
but not in /usr/include/sane after installing libsane-dev or libsane-extras-dev

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libsane-dev 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 14:51:31 2016
  InstallationDate: Installed on 2015-05-08 (288 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to wily on 2015-11-15 (96 days ago)

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

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


[Desktop-packages] [Bug 1688423] [NEW] profile updates

2017-05-04 Thread Seth Arnold
Public bug reported:

daniel curtis reports some AppArmor profile changes that we probably
need; the discussion is at
https://lists.ubuntu.com/archives/apparmor/2017-May/010731.html

I added to my own profile:

@{PROC}/[0-9]*/net/arp r,
/sys/devices/system/node/node*/meminfo r,

and in the lsb_release child profile:

/usr/local/lib/python3.[0-5]/dist-packages/ r,
/usr/bin/python3.[0-5] rm,
/usr/share/distro-info/debian.csv r,

/etc/default/apport r,
/etc/apt/apt.conf r,
/etc/apt/apt.conf.d/ r,

Daniel reported other denials but I'm less clear if they're custom to
his installation or not.

Thanks

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

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

Title:
  profile updates

Status in firefox package in Ubuntu:
  New

Bug description:
  daniel curtis reports some AppArmor profile changes that we probably
  need; the discussion is at
  https://lists.ubuntu.com/archives/apparmor/2017-May/010731.html

  I added to my own profile:

  @{PROC}/[0-9]*/net/arp r,
  /sys/devices/system/node/node*/meminfo r,

  and in the lsb_release child profile:

  /usr/local/lib/python3.[0-5]/dist-packages/ r,
  /usr/bin/python3.[0-5] rm,
  /usr/share/distro-info/debian.csv r,

  /etc/default/apport r,
  /etc/apt/apt.conf r,
  /etc/apt/apt.conf.d/ r,

  Daniel reported other denials but I'm less clear if they're custom to
  his installation or not.

  Thanks

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

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


[Desktop-packages] [Bug 1688407] Re: Snap title field reverted to summary

2017-05-04 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-software - 3.24.1-0ubuntu3

---
gnome-software (3.24.1-0ubuntu3) artful; urgency=medium

  * debian/control:
- Bump build-depends on flatpak
  * debian/patches/flatpak-version.patch:
- Don't require updated version of flatpak for tests - we don't run them
  anyway.

 -- Robert Ancell   Fri, 05 May 2017
13:02:52 +1200

** Changed in: gnome-software (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Snap title field reverted to summary

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.

  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"

  Expected result:
  A snap is shown with the name "ghex-udt"

  Observed result:
  A snap is shown with the name "Hex Editor"

  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

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

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


[Desktop-packages] [Bug 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-04 Thread Jeremy Bicha
Yes, it's an upstream issue. Let me know if you need help fixing it. :)

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688418] [NEW] Missing keyboard-key-*.svg icons

2017-05-04 Thread Gunnar Hjalmarsson
Public bug reported:

This page:

https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
set.html

links to a bunch of keyboard-key-*.svg icons which don't exist. The
icons are not present in the gnome-user-guide package either.

(Noticed it when running the "yelp-build html" command. Apparently an
upstream issue.)

** Affects: gnome-user-docs (Ubuntu)
 Importance: Medium
 Status: New

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

Title:
  Missing keyboard-key-*.svg icons

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

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

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


[Desktop-packages] [Bug 1688414] Re: /usr/bin/gnome-calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

2017-05-04 Thread Bug Watch Updater
** Changed in: gnome-calendar
   Status: Unknown => Confirmed

** Changed in: gnome-calendar
   Importance: Unknown => High

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

Status in GNOME Calendar:
  Confirmed
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6d4cc768a146ab0f6ae401d9cb62adf1efb89b2c 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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


Re: [Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-05-04 Thread Will Cooke
Oxide can be removed. It's no longer supported.


On Thu, 4 May 2017 at 18:25, Steve Langasek 
wrote:

> I believe I heard this from Will Cooke who is on Cc:, so hopefully he
> can clarify.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1688395
>
> Title:
>   Remove Oxide, webbrowser-app and the Unity webapps
>
> Status in libunity-webapps package in Ubuntu:
>   Incomplete
> Status in oxide-qt package in Ubuntu:
>   Incomplete
> Status in webbrowser-app package in Ubuntu:
>   Incomplete
>
> Bug description:
>   These projects are discontinued, unsupported and should be removed.
>
>   I haven't done any analysis of the deps or rdeps to find out if there
>   is more to cull, or if there is some untangling to do.
>
>   I know of two tasks other than removing packages -
>
>Unity ships an Amazon launcher in its preset favourites which
>   launches a binary from unity-webapps-service. That should be removed.
>
>We need to keep providing the Amazon launcher by default (in GNOME
>   Shell) - it should be reimplemented and added to Shell by default.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions
>

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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


[Desktop-packages] [Bug 1663060] Re: Add a title field to snap metadata

2017-05-04 Thread Robert Ancell
*** This bug is a duplicate of bug 169 ***
https://bugs.launchpad.net/bugs/169

See bug 1688407 for the reversion in 17.04. (Also not this bug is a
duplicate and comment on bug 169 if you have more information to
add).

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

Title:
  Add a title field to snap metadata

Status in Developer registration portal:
  New
Status in Rocket.Chat:
  New
Status in Snappy:
  New
Status in gnome-software package in Ubuntu:
  Confirmed
Status in snapcraft package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Triaged
Status in snapd-glib package in Ubuntu:
  Confirmed

Bug description:
  There are currently three naming fields in the snap metadata:
  name: a codename for the snap (can't contain spaces)
  summary: a one-line description of the snap
  description: A multi-line description of the snap

  For example for the Ubuntu calculator app we have:
  name: ubuntu-calculator-app
  summary: Ubuntu Calculator app
  description: The calculator app for all Ubuntu devices.

  What is missing is the 'title' field from the store - this is more
  appropriate to use in a graphical system to display this. For example,
  this should be "Calculator" for ubuntu-calculator-app.

  I think the following needs to be done:
  1. A title field needs to be specified in the .snap metadata.
  2. snapd needs to return this field for local snaps from the metadata, and 
return the store field for searches.
  3. The store should take the title field from the metadata when uploading and 
automatically set it in the store.
  4. Snapcraft needs to have updated documentation / prompt the user to enter 
this field.
  5. snapd-glib needs support for this field.
  6. GNOME Software should use this field where appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-portal/+bug/1663060/+subscriptions

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


[Desktop-packages] [Bug 1688414] Re: /usr/bin/gnome-calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

2017-05-04 Thread Jeremy Bicha
** Changed in: gnome-calendar (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Medium

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

** Also affects: gnome-calendar via
   https://bugzilla.gnome.org/show_bug.cgi?id=782192
   Importance: Unknown
   Status: Unknown

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

Status in GNOME Calendar:
  Unknown
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6d4cc768a146ab0f6ae401d9cb62adf1efb89b2c 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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


[Desktop-packages] [Bug 1688414] [NEW] /usr/bin/gnome-calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

2017-05-04 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6d4cc768a146ab0f6ae401d9cb62adf1efb89b2c 
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 you can request it at 
http://forms.canonical.com/reports/.

** Affects: gnome-calendar
 Importance: Unknown
 Status: Unknown

** Affects: gnome-calendar (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: artful zesty

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

Status in GNOME Calendar:
  Unknown
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6d4cc768a146ab0f6ae401d9cb62adf1efb89b2c 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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


[Desktop-packages] [Bug 1688407] Re: Snap title field reverted to summary

2017-05-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  Snap title field reverted to summary

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.

  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"

  Expected result:
  A snap is shown with the name "ghex-udt"

  Observed result:
  A snap is shown with the name "Hex Editor"

  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

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

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


[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-05-04 Thread Steve Langasek
I believe I heard this from Will Cooke who is on Cc:, so hopefully he
can clarify.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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


[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-05-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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


[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts

2017-05-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  GNOME Software fails to install .deb packages that trigger debconf
  prompts

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software doesn't provide debconf support when using aptd. This means 
any package installation / upgrade that triggers a debconf prompt can fail. The 
requested package might not do a prompt, but some dependency can.

  [Test Case]
  1. Install a .deb file that causes a debconf prompt 
(https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test 
package).
  $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb

  Expected result:
  Package is installed after a debconf prompt is shown.

  Observed result:
  Package fails to install, no prompt is shown.

  [Regression Potential]
  The solution was to provide a pipe when using aptd to allow the debconf 
prompt to be handled in the session. This could introduce new bugs and/or 
security issues.

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

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


[Desktop-packages] [Bug 1688407] Re: Snap title field reverted to summary

2017-05-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Snap title field reverted to summary

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.

  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"

  Expected result:
  A snap is shown with the name "ghex-udt"

  Observed result:
  A snap is shown with the name "Hex Editor"

  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

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

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


[Desktop-packages] [Bug 1688407] Re: Snap title field reverted to summary

2017-05-04 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Artful)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

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

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

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

** Description changed:

  [Impact]
  The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
be dropped when we switched from git branches to using Debian patches.
  
  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"
  
  Expected result:
- A snap is show with the name "ghex-udt"
+ A snap is shown with the name "ghex-udt"
  
  Observed result:
  A snap is shown with the name "Hex Editor"
  
  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

** Description changed:

  [Impact]
- The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
be dropped when we switched from git branches to using Debian patches.
+ The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.
  
  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"
  
  Expected result:
  A snap is shown with the name "ghex-udt"
  
  Observed result:
  A snap is shown with the name "Hex Editor"
  
  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

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

Title:
  Snap title field reverted to summary

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.

  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"

  Expected result:
  A snap is shown with the name "ghex-udt"

  Observed result:
  A snap is shown with the name "Hex Editor"

  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

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

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


[Desktop-packages] [Bug 1688407] [NEW] Snap title field reverted to summary

2017-05-04 Thread Robert Ancell
Public bug reported:

[Impact]
The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.

[Test Case]
1. Open GNOME Software
2. Search for "ghex"

Expected result:
A snap is shown with the name "ghex-udt"

Observed result:
A snap is shown with the name "Hex Editor"

[Regression Potential]
Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

** Affects: gnome-software (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-software (Ubuntu Zesty)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-software (Ubuntu Artful)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

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

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

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

Title:
  Snap title field reverted to summary

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  The snap title field shows the summary in Ubuntu 17.04. This patch appears to 
have been dropped when we switched from git branches to using Debian patches.

  [Test Case]
  1. Open GNOME Software
  2. Search for "ghex"

  Expected result:
  A snap is shown with the name "ghex-udt"

  Observed result:
  A snap is shown with the name "Hex Editor"

  [Regression Potential]
  Low, we just change the snap field from "summary" to "name" to match the 
behaviour in previous Ubuntu releases.

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

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


[Desktop-packages] [Bug 1262068] Re: nvidia-prime should support gdm also

2017-05-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  nvidia-prime should support gdm also

Status in Ubuntu GNOME:
  Triaged
Status in gdm package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Precise:
  Fix Released
Status in gdm source package in Trusty:
  Confirmed
Status in gdm3 source package in Trusty:
  Confirmed
Status in nvidia-prime source package in Trusty:
  Confirmed
Status in ubuntu-drivers-common source package in Trusty:
  Confirmed

Bug description:
  On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends
  on lightdm. This means that

  1. Anyone installing nvidia binary drivers will pull in nvidia-prime and 
subsequently lightdm. As a consequence of this they are also going to get the 
potentially confusing dconf pop-up asking them to choose a DM.
  2. nvidia-prime probably won't work when using gdm

  I haven't looked to closely at how deeply integrated this is with
  lightdm, however we particularly don't want #1 happening, and it would
  be nice if #2 worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 18 16:56:19 2013
  InstallationDate: Installed on 2012-09-23 (451 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts

2017-05-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  GNOME Software fails to install .deb packages that trigger debconf
  prompts

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software doesn't provide debconf support when using aptd. This means 
any package installation / upgrade that triggers a debconf prompt can fail. The 
requested package might not do a prompt, but some dependency can.

  [Test Case]
  1. Install a .deb file that causes a debconf prompt 
(https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test 
package).
  $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb

  Expected result:
  Package is installed after a debconf prompt is shown.

  Observed result:
  Package fails to install, no prompt is shown.

  [Regression Potential]
  The solution was to provide a pipe when using aptd to allow the debconf 
prompt to be handled in the session. This could introduce new bugs and/or 
security issues.

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

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


[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-05-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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


[Desktop-packages] [Bug 1684778] Re: /usr/bin/gnome-calendar:11:g_time_zone_get_offset:g_date_time_to_instant:g_date_time_difference:g_date_time_compare:gcal_event_compare

2017-05-04 Thread Jeremy Bicha
I checked errrors.ubuntu.com and verified that this error has not been
reported for 3.24.1.

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

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

Title:
  /usr/bin/gnome-
  
calendar:11:g_time_zone_get_offset:g_date_time_to_instant:g_date_time_difference:g_date_time_compare:gcal_event_compare

Status in GNOME Calendar:
  Incomplete
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3aced12d125479866c7ffd1274e63558456da9b1 
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 you can request it at 
http://forms.canonical.com/reports/.

  Test Case
  -
  Make sure this error is not reported with version 3.24.1 on errors.ubuntu.com.

  Regression Potential
  
  This is part of the 3.24.1 SRU (LP: #1685803).

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

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


[Desktop-packages] [Bug 1685803] Re: Update gnome-calendar to 3.24.1

2017-05-04 Thread Jeremy Bicha
I've been using gnome-calendar 3.24.1-0ubuntu0.1 for the past week on
Ubuntu GNOME 17.04 without a problem.

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

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

Title:
  Update gnome-calendar to 3.24.1

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  This is a new bugfix release in the stable 3.24 series.

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

  This should fix crash bugs LP: #1683840 and LP: #1684778

  gnome-calendar is in the default Ubuntu, Ubuntu Budgie, and Ubuntu
  GNOME installs.

  Test Case
  -
  Install the update.

  Run the app and make sure it works without crashing.

  Regression Potential
  
  There was a lot of code changes in this release, but the Developer says they 
were necessarily to fix a lot of issues with 3.24's new Week View.

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

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


[Desktop-packages] [Bug 1683840] Re: /usr/bin/gnome-calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscrib

2017-05-04 Thread Jeremy Bicha
I checked errors.ubuntu.com and verified that this error has not been
reported for 3.24.1 (but there are 1500+ reports from 3.24.0).

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

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscribe

Status in GNOME Calendar:
  Incomplete
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0e9b28c8f82887d3c43f2034c47eb57b25df8d3b 
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 you can request it at 
http://forms.canonical.com/reports/.

  This error is being reported a very large number of times. I see 625
  reports on errors.ubuntu.com for this in the past week. This error is
  new with Ubuntu 17.04.

  Test Case
  -
  Make sure this error is not reported with version 3.24.1 on errors.ubuntu.com.

  Regression Potential
  
  This is part of the 3.24.1 SRU (LP: #1685803).

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

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


[Desktop-packages] [Bug 1351286] Please test proposed package

2017-05-04 Thread Brian Murray
Hello Fred, or anyone else affected,

Accepted sane-backends into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/sane-
backends/1.0.25+git20150528-1ubuntu2.16.04.2 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Trusty:
  Triaged
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  A bug in the SANE Kodak driver can cause a SANE device scan to crash the 
client that is using it (e.g. colord, simple-scan).

  [Test Case]
  1. Run a SANE client on a system that is failing Avahi scans (exact cause not 
determined).

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

  [Regression Potential]
  Code fix could cause a change in behaviour of successful Avahi scans for 
Kodak devices, though the fix matches the Avahi documentation for correct usage.

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

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


[Desktop-packages] [Bug 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta

2017-05-04 Thread Brian Murray
There's a whole bunch of these in the Error Tracker so that'll be a
useful data point when verifying the fix. Although, you'd need to dig
into the Dependencies to find the sane-backends version.

https://errors.ubuntu.com/bucket/?id=/usr/lib/colord/colord-sane
%3Acolord-sane%3A%20simple-
watch.c%3A454%3A%20avahi_simple_poll_prepare%3A%20Assertion%20%60s-%3Estate%20%3D%3D%20STATE_INIT%20%7C%7C%20s-%3Estate%20%3D%3D%20STATE_DISPATCHED%20%7C%7C%20s-%3Estate%20%3D%3D%20STATE_FAILURE%27%20failed.

** Tags added: verification-needed

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Trusty:
  Triaged
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  A bug in the SANE Kodak driver can cause a SANE device scan to crash the 
client that is using it (e.g. colord, simple-scan).

  [Test Case]
  1. Run a SANE client on a system that is failing Avahi scans (exact cause not 
determined).

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

  [Regression Potential]
  Code fix could cause a change in behaviour of successful Avahi scans for 
Kodak devices, though the fix matches the Avahi documentation for correct usage.

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

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


[Desktop-packages] [Bug 1351286] Please test proposed package

2017-05-04 Thread Brian Murray
Hello Fred, or anyone else affected,

Accepted sane-backends into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/sane-
backends/1.0.25+git20150528-1ubuntu2.16.10.2 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Trusty:
  Triaged
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  A bug in the SANE Kodak driver can cause a SANE device scan to crash the 
client that is using it (e.g. colord, simple-scan).

  [Test Case]
  1. Run a SANE client on a system that is failing Avahi scans (exact cause not 
determined).

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

  [Regression Potential]
  Code fix could cause a change in behaviour of successful Avahi scans for 
Kodak devices, though the fix matches the Avahi documentation for correct usage.

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

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


[Desktop-packages] [Bug 1663060] Re: Add a title field to snap metadata

2017-05-04 Thread Aaron Ogle
*** This bug is a duplicate of bug 169 ***
https://bugs.launchpad.net/bugs/169

** Also affects: rocket.chat
   Importance: Undecided
   Status: New

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

Title:
  Add a title field to snap metadata

Status in Developer registration portal:
  New
Status in Rocket.Chat:
  New
Status in Snappy:
  New
Status in gnome-software package in Ubuntu:
  Confirmed
Status in snapcraft package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Triaged
Status in snapd-glib package in Ubuntu:
  Confirmed

Bug description:
  There are currently three naming fields in the snap metadata:
  name: a codename for the snap (can't contain spaces)
  summary: a one-line description of the snap
  description: A multi-line description of the snap

  For example for the Ubuntu calculator app we have:
  name: ubuntu-calculator-app
  summary: Ubuntu Calculator app
  description: The calculator app for all Ubuntu devices.

  What is missing is the 'title' field from the store - this is more
  appropriate to use in a graphical system to display this. For example,
  this should be "Calculator" for ubuntu-calculator-app.

  I think the following needs to be done:
  1. A title field needs to be specified in the .snap metadata.
  2. snapd needs to return this field for local snaps from the metadata, and 
return the store field for searches.
  3. The store should take the title field from the metadata when uploading and 
automatically set it in the store.
  4. Snapcraft needs to have updated documentation / prompt the user to enter 
this field.
  5. snapd-glib needs support for this field.
  6. GNOME Software should use this field where appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-portal/+bug/1663060/+subscriptions

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


[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-05-04 Thread Jamie Strandboge
Are all of these unsupported? I know that the signage effort was
initially using webapp-container (part of webbrowser-app) with mir. Even
if webbrowser-app were removed, oxide-qt might still be interesting for
signage/etc since it can be used with upstream Qt.

I've not heard an official statement on these as they relate to signage
(et al), so I thought I'd ask.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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


[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-05-04 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => Confirmed

** Changed in: gnome-online-accounts
   Importance: Unknown => Critical

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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


[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-05-04 Thread Brian Murray
Hello Vague, or anyone else affected,

Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170427.0.3d09239-0ubuntu1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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


[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts

2017-05-04 Thread Brian Murray
Hello Bobby, or anyone else affected,

Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170427.0.3d09239-0ubuntu1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  GNOME Software fails to install .deb packages that trigger debconf
  prompts

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software doesn't provide debconf support when using aptd. This means 
any package installation / upgrade that triggers a debconf prompt can fail. The 
requested package might not do a prompt, but some dependency can.

  [Test Case]
  1. Install a .deb file that causes a debconf prompt 
(https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test 
package).
  $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb

  Expected result:
  Package is installed after a debconf prompt is shown.

  Observed result:
  Package fails to install, no prompt is shown.

  [Regression Potential]
  The solution was to provide a pipe when using aptd to allow the debconf 
prompt to be handled in the session. This could introduce new bugs and/or 
security issues.

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

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


[Desktop-packages] [Bug 1672424] Please test proposed package

2017-05-04 Thread Brian Murray
Hello Vague, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170427.0.3d09239-0ubuntu1~xenial1 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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


[Desktop-packages] [Bug 1679435] Please test proposed package

2017-05-04 Thread Brian Murray
Hello Bobby, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170427.0.3d09239-0ubuntu1~xenial1 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  GNOME Software fails to install .deb packages that trigger debconf
  prompts

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software doesn't provide debconf support when using aptd. This means 
any package installation / upgrade that triggers a debconf prompt can fail. The 
requested package might not do a prompt, but some dependency can.

  [Test Case]
  1. Install a .deb file that causes a debconf prompt 
(https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test 
package).
  $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb

  Expected result:
  Package is installed after a debconf prompt is shown.

  Observed result:
  Package fails to install, no prompt is shown.

  [Regression Potential]
  The solution was to provide a pipe when using aptd to allow the debconf 
prompt to be handled in the session. This could introduce new bugs and/or 
security issues.

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

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


[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-05-04 Thread Bryan Quigley
(old bug about part of this - https://bugs.launchpad.net/ubuntu/+source
/webapps-applications/+bug/1517509 feel free to mark dup)

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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


[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-05-04 Thread Iain Lane
Initially assigning xnox, but feel free to move that.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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


[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-05-04 Thread Iain Lane
Moving from bug #1649310

On Thu, May 04, 2017 at 08:02:57PM -, Steve Langasek wrote:
> On Thu, May 04, 2017 at 03:20:01PM -, Dimitri John Ledkov wrote:
> > Notable things not listed:
> >  * oxide/webbrowser app, still in use for amazon "app"
>·
> What pulls in the amazon app?  I have heard that oxide is definitively not
> on the supported list for 17.10+.

It's /usr/share/applications/ubuntu-amazon-default.desktop, so...

  application://ubuntu-amazon-default.desktop is in Unity's favourites 
  by default

and the chain is

 unity-webapps-service -> webapp-container -> webbrowser-app

I heard that we need to keep this, so if it is confirmed that Oxide, the
web browser and the Unity webapps are to be removed, then we will need
to provide this in another way. The desktop team will do that. (An
initial implementation might just be opening a new tab in Firefox.)

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libunity-webapps (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

** Changed in: libunity-webapps (Ubuntu)
   Status: New => Incomplete

** Changed in: oxide-qt (Ubuntu)
   Status: New => Incomplete

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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


[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-05-04 Thread Jeremy Bicha
** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Triaged

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

** Package changed: gnome-online-accounts (Arch Linux) => gnome-online-
accounts

** Changed in: gnome-online-accounts
   Importance: Undecided => Unknown

** Changed in: gnome-online-accounts
   Status: New => Unknown

** Changed in: gnome-online-accounts
 Remote watch: None => GNOME Bug Tracker #781990

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
   Importance: Undecided => High

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Changed in: ubuntu-gnome
Milestone: None => artful

** Tags added: gnome-1710

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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


[Desktop-packages] [Bug 1470663] Re: Owncloud is not present in the list of available services

2017-05-04 Thread Jeremy Bicha
Owncloud only works if you are using gnome-control-center not unity-
control-center.

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

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

Title:
  Owncloud is not present in the list of available services

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Hi, according to gnome changelog, there should be support for owncloud
  starting from version 3.8, but owncloud doesn't appear in the list of
  available services.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-online-accounts 3.14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-lowlatency 3.19.8-ckt1
  Uname: Linux 3.19.0-22-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME-Notion:Unity
  Date: Thu Jul  2 00:48:09 2015
  InstallationDate: Installed on 2012-04-26 (1161 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to vivid on 2015-05-30 (32 days ago)

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

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


[Desktop-packages] [Bug 1674529] Re: Credentials expired on all accounts.

2017-05-04 Thread Jeremy Bicha
Please try turning your computer off then try again.

If that fixes your issues, this is a duplicate of
https://launchpad.net/bugs/1610944

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

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

Title:
   Credentials expired on all accounts.

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Hello!
  I can not synchronize any account, I already tried eliminating each one, 
removed the key from the "Passwords" app, restarting and nothing.
  Any solution?
  Pd: Some have two-step verification enabled, some do not.
  GNOME Shell 3.20.4
  Ubuntu GNOME 16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 20 22:10:02 2017
  InstallationDate: Installed on 2017-03-18 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1688391] [NEW] Highlight of links in terminal is retarded

2017-05-04 Thread teo1978
Public bug reported:

Steps to reproduce:
- In a terminal, type this command:
ls /srv/www/example.com/htdocs
- hit Enter
- move the mouse cursor over "www" or over "example.com"

Expected:
- nothing should happen
Observed:
- The substring "www/example.com/htdocs" is underlined and right-clickable as 
if it was an URL, which it obviously isn't.

It is questionable in the first place that you try to parse urls that
don't start with a schema.

But in any case, you need to fix your regular expression I guess.

I see now that even wwwXexampleYcom gets recognized as an URL. Looks
like somebody forgot to escape a "." in a regular expression.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May  4 21:40:58 2017
InstallationDate: Installed on 2013-10-11 (1301 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to xenial on 2016-12-11 (143 days ago)

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


** Tags: amd64 apport-bug xenial

** Description changed:

  Steps to reproduce:
  - In a terminal, type this command:
- ls /srv/www/example.com/htdocs
+ ls /srv/www/example.com/htdocs
  - hit Enter
  - move the mouse cursor over "www" or over "example.com"
  
  Expected:
- - nothing should happen 
+ - nothing should happen
  Observed:
  - The substring "www/example.com/htdocs" is underlined and right-clickable as 
if it was an URL, which it obviously isn't.
  
- 
- It is questionable in the first place that you try to parse urls that don't 
start with a schema. 
+ It is questionable in the first place that you try to parse urls that
+ don't start with a schema.
  
  But in any case, you need to fix your regular expression I guess.
  
- I see now that even wwwXexampleYcom gets recognized as a domain. Looks
+ I see now that even wwwXexampleYcom gets recognized as an URL. Looks
  like somebody forgot to escape a "." in a regular expression.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  4 21:40:58 2017
  InstallationDate: Installed on 2013-10-11 (1301 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (143 days ago)

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

Title:
  Highlight of links in terminal is retarded

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - In a terminal, type this command:
  ls /srv/www/example.com/htdocs
  - hit Enter
  - move the mouse cursor over "www" or over "example.com"

  Expected:
  - nothing should happen
  Observed:
  - The substring "www/example.com/htdocs" is underlined and right-clickable as 
if it was an URL, which it obviously isn't.

  It is questionable in the first place that you try to parse urls that
  don't start with a schema.

  But in any case, you need to fix your regular expression I guess.

  I see now that even wwwXexampleYcom gets recognized as an URL. Looks
  like somebody forgot to escape a "." in a regular expression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  4 21:40:58 2017
  InstallationDate: Installed on 2013-10-11 (1301 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (143 days ago)

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

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


[Desktop-packages] [Bug 1663060] Re: Add a title field to snap metadata

2017-05-04 Thread Gustavo Niemeyer
*** This bug is a duplicate of bug 169 ***
https://bugs.launchpad.net/bugs/169

We just got a bug report saying gnome-software is actually showing
summaries as a title:

https://forum.snapcraft.io/t/title-summary-pulled-from/469

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

Title:
  Add a title field to snap metadata

Status in Developer registration portal:
  New
Status in Snappy:
  New
Status in gnome-software package in Ubuntu:
  Confirmed
Status in snapcraft package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Triaged
Status in snapd-glib package in Ubuntu:
  Confirmed

Bug description:
  There are currently three naming fields in the snap metadata:
  name: a codename for the snap (can't contain spaces)
  summary: a one-line description of the snap
  description: A multi-line description of the snap

  For example for the Ubuntu calculator app we have:
  name: ubuntu-calculator-app
  summary: Ubuntu Calculator app
  description: The calculator app for all Ubuntu devices.

  What is missing is the 'title' field from the store - this is more
  appropriate to use in a graphical system to display this. For example,
  this should be "Calculator" for ubuntu-calculator-app.

  I think the following needs to be done:
  1. A title field needs to be specified in the .snap metadata.
  2. snapd needs to return this field for local snaps from the metadata, and 
return the store field for searches.
  3. The store should take the title field from the metadata when uploading and 
automatically set it in the store.
  4. Snapcraft needs to have updated documentation / prompt the user to enter 
this field.
  5. snapd-glib needs support for this field.
  6. GNOME Software should use this field where appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-portal/+bug/1663060/+subscriptions

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


[Desktop-packages] [Bug 1687501] Re: Wifi can't connect on Ubuntu Gnome live usb 17.04

2017-05-04 Thread Phillip Susi
** Package changed: ubiquity (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Wifi can't connect on Ubuntu Gnome live usb 17.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  When using Ubuntu Gnome 17.04 live usb my wifi network shows as
  available, but when I enter the password it can't connect. I attempted
  several times and ensured the password was correct.

  Tried using Ubuntu Gnome 16.04 live usb as a comparison and it
  connects without issue.

  I know my wifi adapter is supported by linux. I have Xubuntu 16.04
  installed on my hard drive and have never had an issue with wifi
  connection.

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

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


[Desktop-packages] [Bug 1687501] [NEW] Wifi can't connect on Ubuntu Gnome live usb 17.04

2017-05-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When using Ubuntu Gnome 17.04 live usb my wifi network shows as
available, but when I enter the password it can't connect. I attempted
several times and ensured the password was correct.

Tried using Ubuntu Gnome 16.04 live usb as a comparison and it connects
without issue.

I know my wifi adapter is supported by linux. I have Xubuntu 16.04
installed on my hard drive and have never had an issue with wifi
connection.

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

-- 
Wifi can't connect on Ubuntu Gnome live usb 17.04
https://bugs.launchpad.net/bugs/1687501
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Description changed:

  [Impact]
  
  hwe-16.04 refresh for 16.04.3
  
  Many packages need debhelper10 or would have to revert various packaging
  changes to work with dh9.
  
  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)
  
  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.
  
  [Test case]
  
  upgrade from/to stock & old hwe stack, test desktop usage
  
  [Regression potential]
  
  zesty hasn't blown up
+ 
+ [Other information]
+ 
+ build order:
+ 1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
+ 2. libclc
+ 3. mesa, xorg-server
+ 4. drivers
+ 5. xorg

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
  2. libclc
  3. mesa, xorg-server
  4. drivers
  5. xorg

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: llvm-toolchain-4.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: llvm-toolchain-4.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: libclc (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 1686344] Re: Mesa 17.0.x stable release

2017-05-04 Thread Timo Aaltonen
** No longer affects: libdrm (Ubuntu)

** No longer affects: libdrm (Ubuntu Xenial)

** No longer affects: libdrm (Ubuntu Zesty)

** No longer affects: mesa (Ubuntu Xenial)

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Zesty:
  New

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

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

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


[Desktop-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

2017-05-04 Thread Magnus Hoff
FWIW, I did not experience this as fixed in 16.10, but now that I have
updated to 17.04 it works well :)

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable "connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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


[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-05-04 Thread Jeremy Bicha
Aere, yes, unless you have gnome-software 3.22.7-0ubuntu3.17.04.1 or
higher installed, you will experience this bug. If there aren't any
problems found with this version, it will be pushed as an update soon,
probably next week.

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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


[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-05-04 Thread Aere Greenway
Will not install keymusician-keyboard Debian package.  gdebi installs it
with no problems.

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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


[Desktop-packages] [Bug 1573408] Re: GNOME Software does not install third-party .deb packages

2017-05-04 Thread Aere Greenway
This bug has re-appeared in 17.04

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

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  installing local debs from nautilus doesn't work

  Test case
  download a deb and double click on it nautilus

  Regression potential
  the changes are restoring a feature that was working, should regression other 
parts of the code

  -

  Unlike previous versions of Ubuntu Unity, I'm unable to install the 
google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here:
  https://www.google.com/tools/dlpage/hangoutplugin

  After downloading, I open the deb file from Firefox and it launches
  the gnome-software package (used in Unity now).

  The first time I click the install button in gnome-software, I notice
  a strange repositioning of the layout, but nothing else happens.

  Clicking the install button a second time puts a 
question-mark-progress-launcher onto the launcher (task) bar, but it never 
progresses:
  http://neartalk.com/ss/2016-04-22_001_1262x740.png

  So far, no one has offered a workaround:
  
http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:02:45 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1688317] [NEW] PCI/internal sound card not detected

2017-05-04 Thread K Y
Public bug reported:

No sound card detected at all, no sound for laptop/bluetooth headphones

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Thu May  4 10:41:20 2017
InstallationDate: Installed on 2017-01-25 (98 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound card detected at all, no sound for laptop/bluetooth
  headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu May  4 10:41:20 2017
  InstallationDate: Installed on 2017-01-25 (98 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1688317/+subscriptions

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
I'll modify the hwe-pkg scripts so that packages will still use
debhelper9, so dropping the requirement of backporting dh-
autoreconf/debhelper.

** Changed in: debhelper (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: dh-autoreconf (Ubuntu)
   Status: New => Invalid

** Changed in: dh-autoreconf (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 106995] Re: gnome-terminal unconditionally interprets mouse wheel events

2017-05-04 Thread Guram Savinov
It seems that this commit in vte is related somehow:

commit 9f8c1b88dcd880c2d9e78c93521ee755560a9275
Author: Christian Persch 
Date:   Mon Sep 30 23:00:09 2013 +0200

emulation: Add support for DEC 1007 to set the alternate scroll mode

By default, the mouse wheel sends cursor up/down keycodes in the
alternate screen. This adds an escape sequence (DEC 1007) that allows
turning this off (and on again).

For compatibility with ubuntu's  patched vte, also add a
(deprecated, skip) public API that has the expected name but does nothing.

Based on patches from ubuntu, and Egmont Koblinger.

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

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

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

Title:
  gnome-terminal unconditionally interprets mouse wheel events

Status in Gnome Virtual Terminal Emulator:
  Invalid
Status in xfce4-terminal:
  Confirmed
Status in screen package in Ubuntu:
  Invalid
Status in vte package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-terminal

  gnome-terminal started to translate mouse-wheel events into history
  scrolling, which doesn't work well when there's not a command prompt
  (another command running). this behaviour should at least be a
  configuration option; commands other than the shell may be confused by
  the escape codes sent as input.

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

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


[Desktop-packages] [Bug 1688265] [NEW] Wifi disconnects when screen is locked

2017-05-04 Thread Mark Haase
Public bug reported:

Ubuntu: 17.04
Wifi Chipset: Intel 7260 rev bb
Driver: iwlwifi 4.10.0-19-generic

If I lock my screen overnight, the following morning my Wifi will be
disconnected and is slow to reconnect and often requires multiple
connection attempts. Locking my screen for a short period of time
(minutes or hours) doesn't trigger the behavior.

Dmesg:


```
[1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256404.230281] wlp5s0: authenticated
[1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
[1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
[1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256413.048999] wlp5s0: authenticated
[1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
[1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
[1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256422.365122] wlp5s0: authenticated
[1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
[1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
[1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256426.582424] wlp5s0: authenticated
[1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
[1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
[1256426.584763] wlp5s0: associated
[1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
[1256426.630815] bridge-wlp5s0: device is wireless, enabling SMAC
[1256426.630817] bridge-wlp5s0: up
[1256426.630823] bridge-wlp5s0: attached
```

There are hundreds of lines like this. It looks like it gets into a loop
where it disconnects every 5 seconds. Once I log in and reconnect using
the applet in the menu bar, the connection is pretty reliable for hours
-- I generally work a full day without wifi dropping.

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

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

Title:
  Wifi disconnects when screen is locked

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu: 17.04
  Wifi Chipset: Intel 7260 rev bb
  Driver: iwlwifi 4.10.0-19-generic

  If I lock my screen overnight, the following morning my Wifi will be
  disconnected and is slow to reconnect and often requires multiple
  connection attempts. Locking my screen for a short period of time
  (minutes or hours) doesn't trigger the behavior.

  Dmesg:

  
  ```
  [1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256404.230281] wlp5s0: authenticated
  [1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256413.048999] wlp5s0: authenticated
  [1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256422.365122] wlp5s0: authenticated
  [1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.582424] wlp5s0: authenticated
  [1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
  [1256426.584763] wlp5s0: associated
  [1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
  [1256426.630815] bridge-wlp5s0: device is wi

[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2017-05-04 Thread UBUNTU user
confirm issue on UBUNTU 16.04 with pulseaudio 8.0
Vahid Mardani's script is a valid temporary workaround by running it every time 
the bug appear

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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


[Desktop-packages] [Bug 106995] Re: gnome-terminal unconditionally interprets mouse wheel events

2017-05-04 Thread Guram Savinov
93_add_alt_screen_scroll_toggle.patch
Why this patch isn't included in Ubuntu's 14.04 vte package?
http://packages.ubuntu.com/trusty/libvte-2.90-9

gnome-terminal calls vte_terminal_set_alternate_screen_scroll which is 
deprecated and do nothing in vte 0.34.9
http://packages.ubuntu.com/trusty/gnome-terminal
http://packages.ubuntu.com/trusty/libvte-2.90-9

/**
 * vte_terminal_set_alternate_screen_scroll:
 * @terminal: a #VteTerminal
 * @scroll:
 *
 * Since: 0.34.9
 * Deprecated: 0.34.9: This function does nothing.
 */
void
vte_terminal_set_alternate_screen_scroll(VteTerminal *terminal, gboolean scroll)
{
/* We just want to export this symbol for compatibility */
}

It causes problems like this: mouse wheel sends key-up/key-down instead
of scroll when GNU screen is run in gnome-terminal.

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

Title:
  gnome-terminal unconditionally interprets mouse wheel events

Status in Gnome Virtual Terminal Emulator:
  Invalid
Status in xfce4-terminal:
  Confirmed
Status in screen package in Ubuntu:
  Invalid
Status in vte package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-terminal

  gnome-terminal started to translate mouse-wheel events into history
  scrolling, which doesn't work well when there's not a command prompt
  (another command running). this behaviour should at least be a
  configuration option; commands other than the shell may be confused by
  the escape codes sent as input.

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

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


[Desktop-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

2017-05-04 Thread LGB [Gábor Lénárt]
Another interesting finding with grep'ing around in /var/log for VGA-1:

root@vega:/var/log# grep VGA-1 syslog
May  4 14:27:10 vega unity-settings-[1644]: unable to get EDID for 
xrandr-VGA-1: unable to get EDID for output

And maybe the even more interesing part in /var/log/gpu-manager.log

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.10.0-21-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.10.0-21-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 8086:152
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-VGA-1
Number of connected outputs for /dev/dri/card0: 1
Does it require offloading? yes
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
Single card detected
Nothing to do
No change - nothing to do

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I've never had a problem like this before. Now, after upgraded to
  Ubuntu 17.04 it was already strange to see the boot logo in a kind of
  low and fuzzy resolution. And it remained for the LightDM login
  screen, also for the desktop after logged on. System setting ->
  Display reports "Unknown Display". System settings -> Software &
  updates  -> Additional drivers shows title "Unknown: Unknown" though
  after that "Using Processor microcode firmware for Intel CPUs from
  intel-microcode" is active. I could "work the problem around" (see the
  end of this writing) but it's really ugly that I need to run a script
  every time, when it always worked well on the same machine before this
  Ubuntu release.

  According to xrandr:

  lgb@vega:~$ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
  VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00* 
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  

  My GPU:
  lgb@vega:~$ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

  Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
  (this monitor hasn't got any other connector like HDMI or DVI).

  My workaround was to create this script and run:

  DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
  xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 
1120 -hsync +vsync
  xrandr --addmode $DEV 1920x1080
  xrandr --output $DEV --mode 1920x1080

  After this, the resolution is fine, but still everything reports
  "Unknown display" and such. The output of xrandr after running my
  script (I played with adding some modes, that is the _60.00 stuff):

  root@vega:~# xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00  
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  
 1920x1080 59.96* 
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
  h: width  1920 start 2048 end 2248 total 2576 skew0 clock  
67.16KHz
  v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
 

[Desktop-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

2017-05-04 Thread LGB [Gábor Lénárt]
I'm really not an xrandr / etc wizard, but what looks strange for me,
that it seems something reports "VGA-1" when all the examples on the Net
(and in xrandr man page) mentions "VGA". Even in Xorg.log:

root@vega:~# fgrep VGA /var/log/Xorg.0.log
[25.034] (II) modeset(0): Output VGA-1 has no monitor section
[25.037] (II) modeset(0): EDID for output VGA-1
[25.037] (II) modeset(0): Printing probed modes for output VGA-1
[25.037] (II) modeset(0): Output VGA-1 connected
[25.037] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I've never had a problem like this before. Now, after upgraded to
  Ubuntu 17.04 it was already strange to see the boot logo in a kind of
  low and fuzzy resolution. And it remained for the LightDM login
  screen, also for the desktop after logged on. System setting ->
  Display reports "Unknown Display". System settings -> Software &
  updates  -> Additional drivers shows title "Unknown: Unknown" though
  after that "Using Processor microcode firmware for Intel CPUs from
  intel-microcode" is active. I could "work the problem around" (see the
  end of this writing) but it's really ugly that I need to run a script
  every time, when it always worked well on the same machine before this
  Ubuntu release.

  According to xrandr:

  lgb@vega:~$ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
  VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00* 
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  

  My GPU:
  lgb@vega:~$ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

  Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
  (this monitor hasn't got any other connector like HDMI or DVI).

  My workaround was to create this script and run:

  DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
  xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 
1120 -hsync +vsync
  xrandr --addmode $DEV 1920x1080
  xrandr --output $DEV --mode 1920x1080

  After this, the resolution is fine, but still everything reports
  "Unknown display" and such. The output of xrandr after running my
  script (I played with adding some modes, that is the _60.00 stuff):

  root@vega:~# xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00  
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  
 1920x1080 59.96* 
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
  h: width  1920 start 2048 end 2248 total 2576 skew0 clock  
67.16KHz
  v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  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:Unity7
  Date: Thu May  4 15:03:53 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-06-10 (328 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dm

[Desktop-packages] [Bug 1688253] [NEW] Wrong resolution, and "unknown monitor" since upgraded to 17.04

2017-05-04 Thread LGB [Gábor Lénárt]
Public bug reported:

I've never had a problem like this before. Now, after upgraded to Ubuntu
17.04 it was already strange to see the boot logo in a kind of low and
fuzzy resolution. And it remained for the LightDM login screen, also for
the desktop after logged on. System setting -> Display reports "Unknown
Display". System settings -> Software & updates  -> Additional drivers
shows title "Unknown: Unknown" though after that "Using Processor
microcode firmware for Intel CPUs from intel-microcode" is active. I
could "work the problem around" (see the end of this writing) but it's
really ugly that I need to run a script every time, when it always
worked well on the same machine before this Ubuntu release.

According to xrandr:

lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm
   1024x768  60.00* 
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  

My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

Monitor is Samsung SyncMaster E2220, standard VGA-cable connection (this
monitor hasn't got any other connector like HDMI or DVI).

My workaround was to create this script and run:

DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 
-hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080

After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my script
(I played with adding some modes, that is the _60.00 stuff):

root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
   1024x768  60.00  
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  
   1920x1080 59.96* 
  1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width  1920 start 2048 end 2248 total 2576 skew0 clock  67.16KHz
v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
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:Unity7
Date: Thu May  4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
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.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917

[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

2017-05-04 Thread Michael Stockenhuber
Hi,
The content of my lircd.conf:
include "lircd.conf.d/*.conf"
that explains why it works, however, I got this after the --purge and did not 
modify
Happy for this to be a support request, not a bug. 
Cheers
Michael

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

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  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: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

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


[Desktop-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

2017-05-04 Thread Stefan
On my Lenovo B590, I was watching an mp4 movie using VLC and the computer 
became completely unresponsive, even the command line would not log me in.
Mint 17.03 (Ubuntu 14.04)
ALSA 1.0.25+dfsg-0ubuntu4
VLC Plugin Pulse 2.1.6-0ubuntu14.04.2
Pulse Audio: 1:4.0-0ubuntu11.1

My relevant syslog is attached.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+attachment/4871889/+files/pulseaudio_syslog

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

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

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


[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-05-04 Thread Duan Jiawei
I have encountered the same issue, I'm sure there is nothing related to the 
network-manager. This package is working properly and I can connect to any wifi 
as I with. 
However i thing it's related with the wifi indicator:)
Generally this issue recovers after I relaunch the Xorg.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: libwacom (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  New
Status in dh-autoreconf source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: libdrm (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  New
Status in dh-autoreconf source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 1573408] Re: GNOME Software does not install third-party .deb packages

2017-05-04 Thread Jeremy Bicha
Anyone who posted to this bug this year, the bug you are experiencing is
probably https://launchpad.net/bugs/1672424

This bug is closed and fixed. Please do not make any more comments here.

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

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  installing local debs from nautilus doesn't work

  Test case
  download a deb and double click on it nautilus

  Regression potential
  the changes are restoring a feature that was working, should regression other 
parts of the code

  -

  Unlike previous versions of Ubuntu Unity, I'm unable to install the 
google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here:
  https://www.google.com/tools/dlpage/hangoutplugin

  After downloading, I open the deb file from Firefox and it launches
  the gnome-software package (used in Unity now).

  The first time I click the install button in gnome-software, I notice
  a strange repositioning of the layout, but nothing else happens.

  Clicking the install button a second time puts a 
question-mark-progress-launcher onto the launcher (task) bar, but it never 
progresses:
  http://neartalk.com/ss/2016-04-22_001_1262x740.png

  So far, no one has offered a workaround:
  
http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:02:45 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

2017-05-04 Thread Alec Leamas
Glad that it works for you. The question is just how...

As noted in the README, from 0.9.4 all lircd.conf files needs names like
mce.lircd.conf i. e., with a lircd.conf suffix. The default lircd.conf
files only includes files with this suffix. That said, a custom
lircd.conf could of course include anything.

Given the overall situation, this is more like a support request than a
bug, right?

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

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  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: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

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


[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

2017-05-04 Thread Alec Leamas
Oops... seems that the default lircd.conf only requires .conf suffix,
not lircd.conf. All solved, my bad.


** Changed in: lirc (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  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: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

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


[Desktop-packages] [Bug 510059] Re: Gvfs keeps asking for password when trying to mount Samba share

2017-05-04 Thread Marc Pignat
Dear all,

Using ubuntu 16.04, and adding

security = user
client use spnego = no

to /etc/samba/smb.conf has fixed gvfs-mount for me

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

Title:
  Gvfs keeps asking for password when trying to mount Samba share

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  My Ubuntu Desktop (9.10, 64-bit) VM can't connect to my Windows 7
  (64-bit, Ultimate) File Share using Nautilus. I enter
  "smb://" in the address bar and then it comes up with a
  password dialog (see screenshot) and then after entering the correct
  login info, the dialog disappears for a second or two but then
  reappears again. The dialog always comes back up and the share is
  never mounted.

  * Connecting from an XP box on the network to the windows 7 share works 
just fine.
  * Connecting from the Ubuntu machine to the windows 7 share using the 
appropriate 'smbmount' command works just fine.
  * Connecting from the Ubuntu machine (using the nautilus GUI) to the XP 
box (password protected) works just fine.
  * Then I turned off password protection in Win7, rebooted the win7 
machine, and still all of the above tests turned out the same. And the Ubuntu 
machine still doesn't connect to the windows share using the nautilus GUI, and 
still displays the password dialog even though no password is required anymore.
  * I tried using smbclient to view the shares, here is the output (not 
sure if I should be trying something else using the smbclient program):
o eddie@eddie-ubuntu:~$ smbclient -L eddie-win7
  Enter eddie's password:
  session setup failed: SUCCESS - 0

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 17 15:41:28 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Package: nautilus 1:2.28.1-0ubuntu3
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-server
  SourcePackage: nautilus
  Uname: Linux 2.6.31-17-server x86_64

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

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


[Desktop-packages] [Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2017-05-04 Thread Ruben van Nieuwpoort
This bug is also present in Mint x64 18.1. Eagerly awaiting a solution
or workaround!

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed

Bug description:
  Unity always considers the left monitor as the default/primary one when in a 
dual-monitor configuration. By this I mean that:
  - Desktop icons appear only on the left monitor
  - An opened app (eg libreoffice writer) is opened on the left screen, even if 
I launch it via the launcher on the right monitor

  The current configuration can be seen at
  
http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

  The .config/monitors.xml file is shown below. Notice that the HDMI
  display (green in the photo) is set asyes.
  Nevertheless, this seems to be ignored - the behaviour is the one
  mentioned above (desktop icons on the left and writer opening on the
  left) .

  

no

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no




GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes




  

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

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


[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-04 Thread Timo Aaltonen
** Also affects: libinput (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  New
Status in libinput package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  New
Status in dh-autoreconf source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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

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


[Desktop-packages] [Bug 1547135] Re: Support purchasing software

2017-05-04 Thread Will Cooke
** Changed in: gnome-software (Ubuntu)
   Importance: High => Low

** Changed in: gnome-software (Ubuntu)
   Importance: Low => Medium

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

Title:
  Support purchasing software

Status in GNOME Software:
  In Progress
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Eventually people will be able to buy software with money.  This means
  that the prices will need to be displayed in the UI.

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

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


[Desktop-packages] [Bug 1573408] Re: GNOME Software does not install third-party .deb packages

2017-05-04 Thread Flavio Tordini
I'm experiencing this bug in Ubuntu 17.04. You should reopen it.

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

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  installing local debs from nautilus doesn't work

  Test case
  download a deb and double click on it nautilus

  Regression potential
  the changes are restoring a feature that was working, should regression other 
parts of the code

  -

  Unlike previous versions of Ubuntu Unity, I'm unable to install the 
google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here:
  https://www.google.com/tools/dlpage/hangoutplugin

  After downloading, I open the deb file from Firefox and it launches
  the gnome-software package (used in Unity now).

  The first time I click the install button in gnome-software, I notice
  a strange repositioning of the layout, but nothing else happens.

  Clicking the install button a second time puts a 
question-mark-progress-launcher onto the launcher (task) bar, but it never 
progresses:
  http://neartalk.com/ss/2016-04-22_001_1262x740.png

  So far, no one has offered a workaround:
  
http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:02:45 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

2017-05-04 Thread Michael Stockenhuber
Hi,

I have now reinstalled lirc and followed the upgrade steps to no avail. No 
response from irw. However purge helped:
apt-get remove --purge lirc
Had to copy mce.conf:
cp /usr/share/lirc/configs/mce.conf /etc/lirc/lircd.conf.d
Now everything is back to normal, irw gives a response and so does kodi.
Thank you for the help, I am not sure this is a bug, I have done upgrades using 
default keeping of the config files.
For me it is solved, maybe this helps someone else.
Cheers
Michael

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

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  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: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

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


[Desktop-packages] [Bug 1575434] Re: Shutdown/Restart prompt may stop working

2017-05-04 Thread Bug Watch Updater
** Changed in: gnome-session
   Status: Unknown => Fix Released

** Changed in: gnome-session
   Importance: Unknown => High

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

Title:
  Shutdown/Restart prompt may stop working

Status in gnome-session:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  Triaged

Bug description:
  Impact
  ==
  The Log Out/Power Off (software) buttons stop working in Ubuntu 16.04 LTS.

  Test Case
  =
  1. From Ubuntu GNOME, open the gedit Text Editor.
  2. Type a few characters but do not save the file.
  3. In the top right corner, click the system status menu. Click your name and 
then Log Out.
  4. Click the gedit icon in the Log Out dialog, then click Cancel in the Log 
Out dialog.
  5. Repeat step 3.

  If the bug happens, the Log Out dialog does not appear after Step 5.

  I was not able to trigger this bug every time but I think this test
  case makes it more likely to trigger the bug

  Original Bug Report
  ===
  The shutdown/restart prompt(60 seconds or the system will shutdown 
automatically) may stop working. Can be triggered by simply clicking on the 
button to open the prompt and not selecting an option or by opening the prompt 
multiple times.

  Description:   Ubuntu 16.04 LTS
  Release:  16.04

  gnome-shell:
    Installed: 3.18.4-0ubuntu3
    Candidate: 3.18.4-0ubuntu3
    Version table:
   *** 3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:18:31 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-23 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1325899] Re: evince is excruciatingly slow on some documents

2017-05-04 Thread shankao
It'd be better to open a new bug to increase visibility. This one was
dealing with a different / older problem that was already fixed.

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

Title:
  evince is excruciatingly slow on some documents

Status in Poppler:
  Invalid
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Evince is excruciatingly slow when displaying the book available for download 
at http://www.safetty.net/publications/pttes
  Scrolling can take several seconds and will often just display empty pages. 
(And it is even worse with the 2009 version of the book you can still find on 
several places on the internet), while xpdf has no problems at all with 
instantly switching to the next page.

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

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


[Desktop-packages] [Bug 1622883] Re: xdvi renders ps images incorrectly

2017-05-04 Thread Robert Nurnberg
The bug has been confirmed on the xdvik project page, see
https://sourceforge.net/p/xdvi/bugs/400/

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

Title:
  xdvi renders ps images incorrectly

Status in texlive-bin package in Ubuntu:
  New

Bug description:
  Since upgrading to kubuntu 16.04, xdvi shows the following problem when 
displaying eps or ps images. In .dvi files with more than one such image, that 
cover the same part of the screen (although on different pages), the renderer 
overlays several images into one, rather than showing the single image 
belonging to that page. But his happens only when going back and forth between
  the affected pages. On the first encounter of the first image, it will be 
displayed correctly.
  I believe the 'clear box' procedure for that part of the screen is broken.

  Steps to reproduce:
   * create LaTeX .tex file with at least two ps images
   * view .dvi output with xdvi
   * when cycling through the pages of the document, the two images will get 
overlayed in
 each of the two separate figures

  Version numbers: Ubuntu 16.04.1 LTS
  xdvik version 22.87 (Xaw toolkit)
  Libraries: kpathsea version 6.2.1, freetype version 2.5.5
  KDE Plasma Version: 5.5.5
  QT Version: 5.5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1622883/+subscriptions

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


[Desktop-packages] [Bug 1685805] Re: Gtk-CRITICAL **: gtk_widget_get_realized: assertion 'GTK_IS_WIDGET (widget)' failed

2017-05-04 Thread Matthew Paul Thomas
I can’t tell what this bug report is about, but it doesn’t seem to have
anything to do with Ubuntu Software Center. Please see
 for advice on how to
report bugs that get fixed. Thanks.

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

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

Title:
  Gtk-CRITICAL **: gtk_widget_get_realized: assertion 'GTK_IS_WIDGET
  (widget)' failed

Status in software-center package in Ubuntu:
  Incomplete

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  2.
  Gnome

  4.
  root@ubuntu:~# gnome-calendar 
  (gnome-calendar:31250): Gtk-CRITICAL **: gtk_widget_get_realized: assertion 
'GTK_IS_WIDGET (widget)' failed

  
  root@ubuntu:~# gnome-screenshot 
  ** Message: Unable to use GNOME Shell's builtin screenshot interface, 
resorting to fallback X11.

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

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


  1   2   >