date:20180503

the log has those warnings

gsd-xsettings[1590]: Failed to get current display configuration state:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
"org.gnome.Mutter.DisplayConfig" does not exist

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

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

Title:
  External monitors--limited working permutations

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

Bug description:
  "Displays" in the Gnome Control Center doesn't seem to be working.
  When I connect an external monitor (Dell P2415Qb) to my laptop (XPS 13 touch 
screen), most of the "Join Displays" options do not work: when I click "Apply" 
after changing resolution or display arrangement, the external monitor goes to 
sleep. When I move the mouse into the region that the monitor should be, it 
seems to go into that region--it feels like although the laptop knows that the 
monitor is there, the monitor doesn't get a signal.
  The only permutation (besides setting display mode to "Mirror") that I have 
found to work (i.e. the external monitor doesn't go to sleep) involves setting 
the resolution to 1600x900 on both the laptop screen and the monitor. This only 
works when the monitor is to the left of the screen. When I try to put display 
2 (the monitor) above display 1, or of course change resolution, the monitor 
goes to sleep.

  I would expect that any permutation of screen positions and
  resolutions that is allowed by the GUI would work, i.e. the external
  monitor should not go to sleep after applying changes when "Join
  Displays" is selected. It's odd that only 1600x900 is allowed (both
  the laptop screen and external monitor can do much better), and that
  the relative positions of the screens makes a difference.

  Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 11:15:56 2018
  InstallationDate: Installed on 2018-04-27 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768261] Re: Videos are getting stuck randomly at frames

2018-05-03 Thread Rishabh Lohia

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

** This bug has been marked a duplicate of bug 1752938
   Upgrading Ubuntu 18.04 disables GPU hardware acceleration

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

Title:
  Videos are getting stuck randomly at frames

Status in xorg package in Ubuntu:
  New

Bug description:
  Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos,
  on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The
  video seek time also gets stuck at that frame, and then suddenly the
  video skips ahead. Audio has no issues. I am assuming it's a problem
  with the video drivers.

  I have dual graphics cards, one integrated and one dedicated(AMD
  Radeon HD 8670M). I guess my problem is similar to
  https://askubuntu.com/questions/1029205/video-playback-performance-
  issue-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May  1 19:40:21 2018
  DistUpgraded: 2018-04-26 21:50:03,842 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
  InstallationDate: Installed on 2016-01-21 (830 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 5537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d287f35b-0011-4adf-a2f4-3626718405ff ro quiet splash radeon.modeset=1 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 04NGGW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron5537:pvrA08:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805010730.6487e7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805010730.6487e7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1661590] Re: GNOME Software only supports running one application from a snap

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.10

---
gnome-software (3.20.5-0ubuntu0.16.04.10) xenial; urgency=medium

  * debian/patches/0020-Add-a-Snap-plugin.patch:
  * 
debian/patches/0015-Don-t-reject-unexpected-state-changes-external-event.patch:
- Correctly launch snaps with multiple apps (LP: #1661590)
- Fix snaps not being shown correctly after install from command line
  (LP: #1754655)

gnome-software (3.20.5-0ubuntu0.16.04.9) xenial; urgency=medium

  * debian/patches/0001-Make-app-name-sorting-case-insensitive.patch:
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Show snaps in categories (LP: #1665126)
  * 
debian/patches/0001-trivial-Include-the-fwupd-version-in-the-useragent.patch:
- Report fwupd version in user agent (LP: #1750030)
  * debian/patches/0050-snap-Support-channels.patch:
- Support channels (LP: #1750288)
  * debian/README.source:
- Update git repository to point to gitlab.gnome.org

 -- Robert Ancell   Wed, 28 Mar 2018
17:04:55 +1300

** Changed in: gnome-software (Ubuntu Xenial)
   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/1661590

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

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

[Desktop-packages] [Bug 1750288] Re: Support snap channels

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.10

---
gnome-software (3.20.5-0ubuntu0.16.04.10) xenial; urgency=medium

  * debian/patches/0020-Add-a-Snap-plugin.patch:
  * 
debian/patches/0015-Don-t-reject-unexpected-state-changes-external-event.patch:
- Correctly launch snaps with multiple apps (LP: #1661590)
- Fix snaps not being shown correctly after install from command line
  (LP: #1754655)

gnome-software (3.20.5-0ubuntu0.16.04.9) xenial; urgency=medium

  * debian/patches/0001-Make-app-name-sorting-case-insensitive.patch:
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Show snaps in categories (LP: #1665126)
  * 
debian/patches/0001-trivial-Include-the-fwupd-version-in-the-useragent.patch:
- Report fwupd version in user agent (LP: #1750030)
  * debian/patches/0050-snap-Support-channels.patch:
- Support channels (LP: #1750288)
  * debian/README.source:
- Update git repository to point to gitlab.gnome.org

 -- Robert Ancell   Wed, 28 Mar 2018
17:04:55 +1300

** Changed in: gnome-software (Ubuntu Xenial)
   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/1750288

Title:
  Support snap channels

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  [Test Case]
  1. Open GNOME Software
  2. Select the VLC snap

  Observed result:
  No channel information is shown.

  Expected result:
  The snap is shown with four (at the time of writing) channels available - 
stable/candidate/beta/edge. You are able to choose a channel at the time of 
install and this installs the appropriate version (can be confirmed with 'snap 
info vlc' on the command line). Once installed the channel can be changed and 
the snap updated (requires clicking install again).

  [Regression Potential]
  Patch is quite large and could cause new bugs.

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

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

[Desktop-packages] [Bug 1750030] Re: Report fwupd version in user agent

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.10

---
gnome-software (3.20.5-0ubuntu0.16.04.10) xenial; urgency=medium

  * debian/patches/0020-Add-a-Snap-plugin.patch:
  * 
debian/patches/0015-Don-t-reject-unexpected-state-changes-external-event.patch:
- Correctly launch snaps with multiple apps (LP: #1661590)
- Fix snaps not being shown correctly after install from command line
  (LP: #1754655)

gnome-software (3.20.5-0ubuntu0.16.04.9) xenial; urgency=medium

  * debian/patches/0001-Make-app-name-sorting-case-insensitive.patch:
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Show snaps in categories (LP: #1665126)
  * 
debian/patches/0001-trivial-Include-the-fwupd-version-in-the-useragent.patch:
- Report fwupd version in user agent (LP: #1750030)
  * debian/patches/0050-snap-Support-channels.patch:
- Support channels (LP: #1750288)
  * debian/README.source:
- Update git repository to point to gitlab.gnome.org

 -- Robert Ancell   Wed, 28 Mar 2018
17:04:55 +1300

** Changed in: gnome-software (Ubuntu Xenial)
   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/1750030

Title:
  Report fwupd version in user agent

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Some firmware updates fail require a recent version of fwupd to work. 
Upstream has requested we update the user agent sent in HTTP requests so that 
they can stop sending firmware to clients that may not work.

  [Test Case]
  Check with the fwupd server that the correct user agent is being sent.

  [Regression Potential]
  Low. The fix is simply to add to the user-agent string used in HTTP requests.

  There are some situations that LVFS shouldn't be offering firmware to certain 
machines.
  Upstream is going to use the user agent for filtering these firmware 
offerings and it would be good if gnome-software can report the user agent.

  The following has been added to the gnome 3.20 tree:
  
https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3

  Can this please be backported to xenial?

  Bionic can already report this as part of 3.26 gnome-software.

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

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

[Desktop-packages] [Bug 1750030] Update Released

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

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

Title:
  Report fwupd version in user agent

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Some firmware updates fail require a recent version of fwupd to work. 
Upstream has requested we update the user agent sent in HTTP requests so that 
they can stop sending firmware to clients that may not work.

  [Test Case]
  Check with the fwupd server that the correct user agent is being sent.

  [Regression Potential]
  Low. The fix is simply to add to the user-agent string used in HTTP requests.

  There are some situations that LVFS shouldn't be offering firmware to certain 
machines.
  Upstream is going to use the user agent for filtering these firmware 
offerings and it would be good if gnome-software can report the user agent.

  The following has been added to the gnome 3.20 tree:
  
https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3

  Can this please be backported to xenial?

  Bionic can already report this as part of 3.26 gnome-software.

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

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

[Desktop-packages] [Bug 1661590] Update Released

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

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

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

[Desktop-packages] [Bug 1750288] Update Released

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

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

Title:
  Support snap channels

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  [Test Case]
  1. Open GNOME Software
  2. Select the VLC snap

  Observed result:
  No channel information is shown.

  Expected result:
  The snap is shown with four (at the time of writing) channels available - 
stable/candidate/beta/edge. You are able to choose a channel at the time of 
install and this installs the appropriate version (can be confirmed with 'snap 
info vlc' on the command line). Once installed the channel can be changed and 
the snap updated (requires clicking install again).

  [Regression Potential]
  Patch is quite large and could cause new bugs.

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

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

[Desktop-packages] [Bug 1665126] Re: Snaps do not show in categories

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.10

---
gnome-software (3.20.5-0ubuntu0.16.04.10) xenial; urgency=medium

  * debian/patches/0020-Add-a-Snap-plugin.patch:
  * 
debian/patches/0015-Don-t-reject-unexpected-state-changes-external-event.patch:
- Correctly launch snaps with multiple apps (LP: #1661590)
- Fix snaps not being shown correctly after install from command line
  (LP: #1754655)

gnome-software (3.20.5-0ubuntu0.16.04.9) xenial; urgency=medium

  * debian/patches/0001-Make-app-name-sorting-case-insensitive.patch:
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Show snaps in categories (LP: #1665126)
  * 
debian/patches/0001-trivial-Include-the-fwupd-version-in-the-useragent.patch:
- Report fwupd version in user agent (LP: #1750030)
  * debian/patches/0050-snap-Support-channels.patch:
- Support channels (LP: #1750288)
  * debian/README.source:
- Update git repository to point to gitlab.gnome.org

 -- Robert Ancell   Wed, 28 Mar 2018
17:04:55 +1300

** Changed in: gnome-software (Ubuntu Xenial)
   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/1665126

Title:
  Snaps do not show in categories

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Snaps are not shown in categories.

  [Test Case]
  1. Open GNOME Software
  2. Select "Games" category at the bottom of the page.
  3. Select "All"
  4. Look for pin-town (a snap game)

  Expected result:
  Game is shown

  Observed result:
  Game is not shown.

  [Regression Potential]
  Loading snap information in category screens could trigger new bugs.

  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)

  Looks like only .deb are listed in categories within Ubuntu Software?

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

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

[Desktop-packages] [Bug 1665126] Update Released

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

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

Title:
  Snaps do not show in categories

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Snaps are not shown in categories.

  [Test Case]
  1. Open GNOME Software
  2. Select "Games" category at the bottom of the page.
  3. Select "All"
  4. Look for pin-town (a snap game)

  Expected result:
  Game is shown

  Observed result:
  Game is not shown.

  [Regression Potential]
  Loading snap information in category screens could trigger new bugs.

  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)

  Looks like only .deb are listed in categories within Ubuntu Software?

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread claudio@ubuntu

There are two setups where the solution is with my setup (NVIDIA Corporation 
GK107M [GeForce GT 750M], laptop with nvidia and intel):
- Use Wayland with nouveau drivers: performance OK.
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1" 
(see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when 
you install the binary drivers).

What doesn't work (black or too slow):
- nvidia drivers.
- nvidia drivers with intel selected by prime.
- nouveau drivers on Xorg.

Here are the more expanded instructions. Be sure to know what you do,
you won't loose files, but you may make your system unbootable if you
type an error.

1. Make sure nvidia is not blacklisted. E.g. remove bumblebee. Have a look in 
/etc/modules and /etc/modprobe.d/*:
$ sudo apt-get remove --purge bumblebee
$ grep nvidia /etc/modules /etc/modprobe.d/*

"blacklist nvidia" is what's mostly used.

2. Add "modeset=1" to grub:
$ sudo vi /etc/default/grub
(or sudo nano /etc/default/grub)

Add nvidia-drm.modeset=1 to the GRUB_CMDLINE line (with the quotes):
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"

Activate the changes:
$ sudo update-grub

4. Install Nvidia drivers:
$ sudo ubuntu-drivers autoinstall
$ sudo prime-select nvidia

5. Reboot

Be warned that modeset=1 disabled the virtual consoles (ctl+alt+f).

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1754655] Re: Installing snap from command line confuses GNOME Software

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.10

---
gnome-software (3.20.5-0ubuntu0.16.04.10) xenial; urgency=medium

  * debian/patches/0020-Add-a-Snap-plugin.patch:
  * 
debian/patches/0015-Don-t-reject-unexpected-state-changes-external-event.patch:
- Correctly launch snaps with multiple apps (LP: #1661590)
- Fix snaps not being shown correctly after install from command line
  (LP: #1754655)

gnome-software (3.20.5-0ubuntu0.16.04.9) xenial; urgency=medium

  * debian/patches/0001-Make-app-name-sorting-case-insensitive.patch:
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Show snaps in categories (LP: #1665126)
  * 
debian/patches/0001-trivial-Include-the-fwupd-version-in-the-useragent.patch:
- Report fwupd version in user agent (LP: #1750030)
  * debian/patches/0050-snap-Support-channels.patch:
- Support channels (LP: #1750288)
  * debian/README.source:
- Update git repository to point to gitlab.gnome.org

 -- Robert Ancell   Wed, 28 Mar 2018
17:04:55 +1300

** Changed in: gnome-software (Ubuntu Xenial)
   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/1754655

Title:
  Installing snap from command line confuses GNOME Software

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Installing snaps from the command line (or any other client) causes the state 
in GNOME Software to wrongly represented.

  [Test Case]
  1. Ensure you don't have moon-buggy installed
  $ sudo snap remove moon-buggy
  2. Start GNOME Software
  3. Install moon-buggy from the command line:
  $ sudo snap install moon-buggy
  4. Search for "moon" in GNOME Software

  Expected result:
  Moon Buggy shows in search results as installed

  Observed result:
  Moon Buggy not returned in search results.

  [Regression Potential]
  Low, we fix a bug where were reading invalid metadata and a check that makes 
stops unexpected (but valid) state notification from the snap plugin.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread claudio@ubuntu

Forgot to add:
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1" 
(see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when 
you install the binary drivers). Performance: very good.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1754655] Update Released

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

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

Title:
  Installing snap from command line confuses GNOME Software

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Installing snaps from the command line (or any other client) causes the state 
in GNOME Software to wrongly represented.

  [Test Case]
  1. Ensure you don't have moon-buggy installed
  $ sudo snap remove moon-buggy
  2. Start GNOME Software
  3. Install moon-buggy from the command line:
  $ sudo snap install moon-buggy
  4. Search for "moon" in GNOME Software

  Expected result:
  Moon Buggy shows in search results as installed

  Observed result:
  Moon Buggy not returned in search results.

  [Regression Potential]
  Low, we fix a bug where were reading invalid metadata and a check that makes 
stops unexpected (but valid) state notification from the snap plugin.

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

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

[Desktop-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)
  [gtkstyleproviderprivate.c:123]

Status in Apport:
  New
Status in GTK+:
  Expired
Status in apport package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 965953] Re: Indicator menus are too short and scroll when opened from screen bottom

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Indicator menus are too short and scroll when opened from screen
  bottom

Status in GTK+:
  Expired
Status in Indicator Applet:
  Invalid
Status in gnome-panel package in Ubuntu:
  Invalid

Bug description:
  The indicator applet, installed by default in classic session of
  Precise, appears with just some up and down scroll arrows, and I have
  to scroll down before it fills in and shows the 3 items, and then the
  scroll arrows disappear.

  Is it possible to fix this annoying behaviour?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-panel 1:3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 08:39:06 2012
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768653] Re: chromium 66 FTBFS on armhf

** Branch linked: lp:~chromium-team/chromium-browser/artful-stable

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

Title:
  chromium 66 FTBFS on armhf

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:21: 
error: unknown type name '_Unwind_Control_Block'
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
  ^
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:62: 
error: member reference base type 'void' is not a structure or union
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
   ^ ~
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:434:71: 
error: no member named 'barrier_cache' in '_Unwind_Exception'
  return 
reinterpret_cast(exception_header->unwindHeader.barrier_cache.bitpattern[0]);
 ~~ ^

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Jean-Sébastien Herbaux

I've upgraded from ubuntu 17.10 to 18.04 and I got the same issue.

When I boot on my laptop with a gtx 1070, I can see on my laptop screen
and my monitor connected through a USB-C adapter the startup console
starting all the modules. On the other hand I have the login screen
working well on my external monitor (through HDMI).

It is important to notice that I cannot detect any of the two others
display through the device manager or any command.

I believe that the monitor connected through HDMI only is using the
integrated Intel GPU while my two other screens uses the nvidia graphic
card.

This bug is definitively not fixed at all and it is astonishing to see
that it has been marked as 'resolved' while a lot of users are still
getting blocked from using their computer (personal or work...).

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1747717] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw

This particular upgrade was from Ubuntu 17.10 to Ubuntu 18.04. Bug
1768890 is also about triggers looping for gnome-menus but is about the
upgrade from Ubuntu 16.04 to Ubuntu 18.04.

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned - gnome-menus -> ufw

Status in dpkg package in Ubuntu:
  Invalid
Status in gnome-menus package in Ubuntu:
  Incomplete
Status in dpkg source package in Bionic:
  Invalid
Status in gnome-menus source package in Bionic:
  Incomplete

Bug description:
  using the bionic beaver version

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb  6 23:00:47 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768653] Re: chromium 66 FTBFS on armhf

** Branch linked: lp:~chromium-team/chromium-browser/bionic-stable

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

Title:
  chromium 66 FTBFS on armhf

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:21: 
error: unknown type name '_Unwind_Control_Block'
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
  ^
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:62: 
error: member reference base type 'void' is not a structure or union
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
   ^ ~
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:434:71: 
error: no member named 'barrier_cache' in '_Unwind_Exception'
  return 
reinterpret_cast(exception_header->unwindHeader.barrier_cache.bitpattern[0]);
 ~~ ^

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

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

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

2018-05-03 Thread Soham Dongargaonkar

Confirmed, entering an incorrect password and then trying to log in with
the correct one leads to a purple screen.

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

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

Status in gdm:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

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

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

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

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

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

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

[Desktop-packages] [Bug 1767096] Re: Random Xorg crashes

2018-05-03 Thread spodin

also, in `/var/log/Xorg.1.log.old`

I see such error:

[ 16706.342] (EE) 
Fatal server error:
[ 16706.342] (EE) Cannot run in framebuffer mode. Please specify busIDs
for all framebuffer devices
[ 16706.342] (EE) 
[ 16706.342] (EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
[ 16706.342] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
[ 16706.342] (EE) 
[ 16706.382] (EE) Server terminated with error (1). Closing log file.

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768653] Re: chromium 66 FTBFS on armhf

** Branch linked: lp:~chromium-team/chromium-browser/xenial-stable

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

Title:
  chromium 66 FTBFS on armhf

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:21: 
error: unknown type name '_Unwind_Control_Block'
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
  ^
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:62: 
error: member reference base type 'void' is not a structure or union
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
   ^ ~
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:434:71: 
error: no member named 'barrier_cache' in '_Unwind_Exception'
  return 
reinterpret_cast(exception_header->unwindHeader.barrier_cache.bitpattern[0]);
 ~~ ^

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Nicolae Righeriu

I'm running Ubuntu 18 (although I had exactly the same issue on 16 too)
and instalation of Nvidia drivers works fine, until I choose to change
to Intel graphics card. Then, after rebooting I can't open the Nvidia
GUI anymore. This means I can't use my Hdmi port. Seems like I'll have
to get back to Windows for a while because of this matter unfortunately

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Nicolae Righeriu

no fix is released, please change the status. Things are definetly not
fine yet

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Tim Richardson

This is not a new problem, and it affects every gdm3-based distro that I have 
used. Long story short; if you want to use modeset=1 with nvidia to get rid of 
tearing (which would be every linux Optimus user on the planet), gdm3 doesn't 
work. No one seems to know why. 
Change your display manager to lightdm and enjoy life again. I have two Optimus 
laptops. 

sudo dpkg-reconfigure lightdm

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1768613] Re: External monitors--limited working permutations

2018-05-03 Thread Michael Greenburg

Upon restarting, I was able to get the monitor above the laptop screen,
but only after a few attempts; the behavior doesn't seem to be
deterministic--sometimes one permutation will work, sometimes it won't.

Here is the output of xrandr:
Screen 0: minimum 320 x 200, current 1600 x 1800, maximum 8192 x 8192
eDP-1 connected primary 1600x900+0+900 (normal left inverted right x axis y 
axis) 294mm x 165mm
   3200x1800 59.98 +  59.9659.9447.99  
   2880x1620 59.9659.97  
   2560x1600 59.9959.97  
   2560x1440 59.9959.9959.9659.95  
   2048x1536 60.00  
   1920x1440 60.00  
   1856x1392 60.01  
   1792x1344 60.01  
   2048x1152 59.9959.9859.9059.91  
   1920x1200 59.8859.95  
   1920x1080 60.0159.9759.9659.93  
   1600x1200 60.00  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.95*   59.82  
   1280x1024 60.02  
   1440x900  59.89  
   1400x900  59.9659.88  
   1280x960  60.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 connected 1600x900+0+0 (normal left inverted right x axis y axis) 527mm 
x 296mm
   3840x2160 60.00 +  29.98  
   2560x1440 59.95  
   2048x1280 59.99  
   1920x1200 59.88  
   1920x1080 60.0060.0050.0059.9424.0023.98  
   1600x1200 60.00  
   1600x900  60.00* 
   1280x1024 75.0260.02  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
DP-1-3 disconnected (normal left inverted right x axis y axis)
DP-2-1 disconnected (normal left inverted right x axis y axis)
DP-2-2 disconnected (normal left inverted right x axis y axis)
DP-2-3 disconnected (normal left inverted right x axis y axis)

I've attached the output of journalctl; this warning was printed:
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
If you need more info let me know.

** Attachment added: "journalctl > journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768613/+attachment/5132993/+files/journalctl.log

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

Title:
  External monitors--limited working permutations

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

Bug description:
  "Displays" in the Gnome Control Center doesn't seem to be working.
  When I connect an external monitor (Dell P2415Qb) to my laptop (XPS 13 touch 
screen), most of the "Join Displays" options do not work: when I click "Apply" 
after changing resolution or display arrangement, the external monitor goes to 
sleep. When I move the mouse into the region that the monitor should be, it 
seems to go into that region--it feels like although the laptop knows that the 
monitor is there, the monitor doesn't get a signal.
  The only permutation (besides setting display mode to "Mirror") that I have 
found to work (i.e. the external monitor doesn't go to sleep) involves setting 
the resolution to

[Desktop-packages] [Bug 1768854] Re: ubuntu-session incompatible with extension "window list"

2018-05-03 Thread xavier

Sorry, It is an ubuntu-session bug, not gnome-session's.
I can't find the "delete" button.

I've opened a new bug here: https://bugs.launchpad.net/ubuntu/+source
/ubuntu-session/+bug/1768856

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

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

Title:
  ubuntu-session incompatible with extension "window list"

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04 (also tested in 17.10)

  ubuntu-session:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-shell-extensions:
Installed: 3.28.0-2
Candidate: 3.28.0-2
Version table:
   *** 3.28.0-2 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  gnome-session:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Gnome extension "Window List" 
(https://extensions.gnome.org/extension/602/window-list/) installed via apt 
(gnome-shell-extensions package) fails to load when logged using ubuntu-session.

  When using Ubuntu / Communitheme

  https://dl.sai.ma/s/X5CPKfnZspQx66W
  https://dl.sai.ma/s/yxtD3bgtBfpcoJR

  
  But when using Gnome / Gnome on Xorg

  https://dl.sai.ma/s/kmfyTffmXK8SNGj
  https://dl.sai.ma/s/77ZnBkaGoj6PX3f

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

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

[Desktop-packages] [Bug 1768854] [NEW] ubuntu-session incompatible with extension "window list"

2018-05-03 Thread xavier

Public bug reported:

Ubuntu 18.04 (also tested in 17.10)

ubuntu-session:
  Installed: 3.28.1-0ubuntu2
  Candidate: 3.28.1-0ubuntu2
  Version table:
 *** 3.28.1-0ubuntu2 500
500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

gnome-shell-extensions:
  Installed: 3.28.0-2
  Candidate: 3.28.0-2
  Version table:
 *** 3.28.0-2 500
500 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://es.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

gnome-session:
  Installed: 3.28.1-0ubuntu2
  Candidate: 3.28.1-0ubuntu2
  Version table:
 *** 3.28.1-0ubuntu2 500
500 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status


Gnome extension "Window List" 
(https://extensions.gnome.org/extension/602/window-list/) installed via apt 
(gnome-shell-extensions package) fails to load when logged using ubuntu-session.

When using Ubuntu / Communitheme

https://dl.sai.ma/s/X5CPKfnZspQx66W
https://dl.sai.ma/s/yxtD3bgtBfpcoJR


But when using Gnome / Gnome on Xorg

https://dl.sai.ma/s/kmfyTffmXK8SNGj
https://dl.sai.ma/s/77ZnBkaGoj6PX3f

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

Title:
  ubuntu-session incompatible with extension "window list"

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04 (also tested in 17.10)

  ubuntu-session:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-shell-extensions:
Installed: 3.28.0-2
Candidate: 3.28.0-2
Version table:
   *** 3.28.0-2 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  gnome-session:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Gnome extension "Window List" 
(https://extensions.gnome.org/extension/602/window-list/) installed via apt 
(gnome-shell-extensions package) fails to load when logged using ubuntu-session.

  When using Ubuntu / Communitheme

  https://dl.sai.ma/s/X5CPKfnZspQx66W
  https://dl.sai.ma/s/yxtD3bgtBfpcoJR

  
  But when using Gnome / Gnome on Xorg

  https://dl.sai.ma/s/kmfyTffmXK8SNGj
  https://dl.sai.ma/s/77ZnBkaGoj6PX3f

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

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

[Desktop-packages] [Bug 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2018-05-03 Thread srinivas

Hi Brain,

Can you please let me know the hplip version you installed.
when you got this error "error running python rtupdate hook hplip-data", what 
are the commands you tried.

Can you please provide me the following logs
1) syslog.
  It will be there in the path /var/log/syslog.


2) error_log for cups
path: /var/log/cups/error_log
How to enable cups log :
-> go to /etc/cups/cupsd.conf
-> Change the Loglevel from warn to debug2 and save the file.
-> restart the cups before adding the printer using hp-setup - /etc/init.d/cups 
restart

Please clear the logs before adding the printer using
1)cp /dev/null /var/log/syslog.
2)cp /dev/null /var/log/cups/error_log.

3)Output of hp-check -rt

Thanks
Srinivas

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

Title:
  package python3 3.6.5-3 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Hello, error came up while updating. Paketmanager has canceled the
  update completely. Not yet analyzed for errors with console ...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Sun Apr 22 00:01:23 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-04 (17 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago)

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2018-05-03 Thread Lonnie Lee Best

You should not only be able to have different fractal scaling for each
monitor, but you should also be able to have fractal scaling for each
separate window you launch.

Back around 2008, Mandriva released a desktop called Metisse that allowed 
(seemingly infinite) fractional scaling for each window! (much less is per 
monitor granularity) Here's a video of that in action:
https://www.youtube.com/watch?v=dxsUKX6xXyE=40s

To accomplish this, using Metisse, you'd simply hold down shift (or was
it ctrl) while resizing the window.

You could do almost anything to that window, and all your mouse actions
on that window would still work accurately no matter how you scaled it.
You could even do silly impractical things like turn the window up-side-
down, pivot it, push the left side of the window deeper into the
background than the right side, etc. And, all your interactions with
that window would still work accurately. It was amazing (and done on
Linux first -- 10 years ago).

When will the world catch up with what Metisse accomplished in 2008? It
was way ahead of its time.

Here's an academic paper on Metisse:
https://hal.inria.fr/inria-00533597/document

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

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

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  After restarting your computer, you should find additional scale
  options in Settings > Devices > Displays.

  If you change your mind and want to get back to supported status, run:

  gsettings reset org.gnome.mutter experimental-features

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

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

[Desktop-packages] [Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

** Changed in: gnome-keyring (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1768844] [NEW] Numlock key turns on constantly, must push twice to turn off

2018-05-03 Thread Tom White

Public bug reported:

Since the 18.04 xubuntu upgrade, the numlock key turns on when the login
screen appears (such as after locking the screen). I have this turned
off in the BIOS, and I do not ever want it turned on. This "automatic"
behavior is unwanted and unexpected. I see that I can disable this, but
I shouldn't have to.

Also, after numlock is turned on I have to press the numlock key twice
to get it to turn off. Since I lock my computer every time I stand up
from my desk this is a constant annoyance.

This is not a feature, this is a bug.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: numlockx 1.2-7ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May  3 08:24:20 2018
InstallationDate: Installed on 2016-04-21 (741 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: numlockx
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Numlock key turns on constantly, must push twice to turn off

Status in numlockx package in Ubuntu:
  New

Bug description:
  Since the 18.04 xubuntu upgrade, the numlock key turns on when the
  login screen appears (such as after locking the screen). I have this
  turned off in the BIOS, and I do not ever want it turned on. This
  "automatic" behavior is unwanted and unexpected. I see that I can
  disable this, but I shouldn't have to.

  Also, after numlock is turned on I have to press the numlock key twice
  to get it to turn off. Since I lock my computer every time I stand up
  from my desk this is a constant annoyance.

  This is not a feature, this is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: numlockx 1.2-7ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May  3 08:24:20 2018
  InstallationDate: Installed on 2016-04-21 (741 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: numlockx
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1768840] [NEW] Evince 3.18.2 claims excessive memeoy when opening a multipage file created with AbbyyFineReader14 (AFR14, runs on Windows10)

2018-05-03 Thread melolontha

Public bug reported:

If Evince 3.18.2 (running on Xubuntu 16.04.4) loads such a pdf file (e.g. after 
doubleclicking on the file name in Thunar), a few seconds later more than 3 GiB 
of RAM are in use. Then memory consumption stays almost stationary for some 
time to sharply rise again. 
Finally you may be caught in swapping memory and becoime almost unable to 
control the computer, because the cursor reacts on mouse movements only with 
much time delay.
In some cases, after many minutes of heavy CPU use, finally a result is shown. 
Memory consumption may be up to 6GiB for a two page grayscale pdf document and 
even for a two page BW-document! In such a case, after stopping Evince, all the 
memory is back again and the computer is operational as it was before.
The same documents load quickly in Firefox 59.0.2 (64-Bit) and without 
excessive memory consumption.
The syndrome does not show up, if Evince shall read a single page pdf document. 
But even if you add the same content into a single document (in AFR14) to make 
it a two page document, the result shows the syndrome.
The syndrome does not show up with files made by AFR9.
GIMP2.8 and LibreOffice (Draw) Build-ID: 1:5.1.6~rc2-0ubuntu1~xenial3 also 
suffer from the same illness for the same file. Do they all rely on the same 
libraries?
If someone needs sample files to look into it, I can provide some.
It even looks like Evince claims this excessive memory already when it is 
started from a command line and shows the “last opened“ view. The included 
example Test AFR14_2 Seiten, beruht auf Test-AFR14_00-00_SW.tif_SW.pdf was 
created with AFR14 (under Windows) by including the scanned image 
Test-AFR14_00-00_SW.tif twice into the PDF file sauch that it becomes a more 
than one page pdf file. After I opened Evince, it claimed 3.3GiB and just 
showed the names of the last opened files with some default icons. After 
waiting some minutes, the icons were filled with previews and then Evince‘s 
memory consumption dropped down to 48,9 MB! 
There were known errors which may or may not have the same root cause: in 
Evince 0.6x, see https://bugzilla.gnome.org/show_bug.cgi?id=431423 and in 
Evince 2.6x, see https://bugzilla.gnome.org/show_bug.cgi?id=577144.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4.3
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May  3 15:15:30 2018
InstallationDate: Installed on 2018-02-10 (81 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "PDF file created by AFR14 by including the tif file as 
two pages, i.e. including it twice to make a multipage document"
   
https://bugs.launchpad.net/bugs/1768840/+attachment/5132959/+files/Test%20AFR14_2%20Seiten%2C%20beruht%20auf%20Test-AFR14_00-00_SW.tif_SW.pdf

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

Title:
  Evince 3.18.2 claims excessive memeoy when opening a multipage file
  created with AbbyyFineReader14 (AFR14, runs on Windows10)

Status in evince package in Ubuntu:
  New

Bug description:
  If Evince 3.18.2 (running on Xubuntu 16.04.4) loads such a pdf file (e.g. 
after doubleclicking on the file name in Thunar), a few seconds later more than 
3 GiB of RAM are in use. Then memory consumption stays almost stationary for 
some time to sharply rise again. 
  Finally you may be caught in swapping memory and becoime almost unable to 
control the computer, because the cursor reacts on mouse movements only with 
much time delay.
  In some cases, after many minutes of heavy CPU use, finally a result is 
shown. Memory consumption may be up to 6GiB for a two page grayscale pdf 
document and even for a two page BW-document! In such a case, after stopping 
Evince, all the memory is back again and the computer is operational as it was 
before.
  The same documents load quickly in Firefox 59.0.2 (64-Bit) and without 
excessive memory consumption.
  The syndrome does not show up, if Evince shall read a single page pdf 
document. But even if you add the same content into a single document (in 
AFR14) to make it a two page document, the result shows the syndrome.
  The syndrome does not show up with files made by AFR9.
  GIMP2.8 and LibreOffice (Draw) Build-ID: 1:5.1.6~rc2-0ubuntu1~xenial3 also 
suffer from the same illness for the same file. Do they all rely on the same 
libraries?
  If someone needs sample files to look into it, I can provide some.
  It even

[Desktop-packages] [Bug 1768840] Re: Evince 3.18.2 claims excessive memeoy when opening a multipage file created with AbbyyFineReader14 (AFR14, runs on Windows10)

2018-05-03 Thread melolontha

** Attachment added: "TIF file which was included twice into the 2-pages pdf 
file by AFR14"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1768840/+attachment/5132964/+files/Test-AFR14_00-00_SW.tif

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

Title:
  Evince 3.18.2 claims excessive memeoy when opening a multipage file
  created with AbbyyFineReader14 (AFR14, runs on Windows10)

Status in evince package in Ubuntu:
  New

Bug description:
  If Evince 3.18.2 (running on Xubuntu 16.04.4) loads such a pdf file (e.g. 
after doubleclicking on the file name in Thunar), a few seconds later more than 
3 GiB of RAM are in use. Then memory consumption stays almost stationary for 
some time to sharply rise again. 
  Finally you may be caught in swapping memory and becoime almost unable to 
control the computer, because the cursor reacts on mouse movements only with 
much time delay.
  In some cases, after many minutes of heavy CPU use, finally a result is 
shown. Memory consumption may be up to 6GiB for a two page grayscale pdf 
document and even for a two page BW-document! In such a case, after stopping 
Evince, all the memory is back again and the computer is operational as it was 
before.
  The same documents load quickly in Firefox 59.0.2 (64-Bit) and without 
excessive memory consumption.
  The syndrome does not show up, if Evince shall read a single page pdf 
document. But even if you add the same content into a single document (in 
AFR14) to make it a two page document, the result shows the syndrome.
  The syndrome does not show up with files made by AFR9.
  GIMP2.8 and LibreOffice (Draw) Build-ID: 1:5.1.6~rc2-0ubuntu1~xenial3 also 
suffer from the same illness for the same file. Do they all rely on the same 
libraries?
  If someone needs sample files to look into it, I can provide some.
  It even looks like Evince claims this excessive memory already when it is 
started from a command line and shows the “last opened“ view. The included 
example Test AFR14_2 Seiten, beruht auf Test-AFR14_00-00_SW.tif_SW.pdf was 
created with AFR14 (under Windows) by including the scanned image 
Test-AFR14_00-00_SW.tif twice into the PDF file sauch that it becomes a more 
than one page pdf file. After I opened Evince, it claimed 3.3GiB and just 
showed the names of the last opened files with some default icons. After 
waiting some minutes, the icons were filled with previews and then Evince‘s 
memory consumption dropped down to 48,9 MB! 
  There were known errors which may or may not have the same root cause: in 
Evince 0.6x, see https://bugzilla.gnome.org/show_bug.cgi?id=431423 and in 
Evince 2.6x, see https://bugzilla.gnome.org/show_bug.cgi?id=577144.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4.3
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May  3 15:15:30 2018
  InstallationDate: Installed on 2018-02-10 (81 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 137606] Re: an icon view for the fileselectors would be useful

** Changed in: gtk
   Status: In Progress => Expired

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

Title:
  an icon view for the fileselectors would be useful

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  When using nautilus in lookup mode, i.e. browse for a file for opening
  or selecting, the list of files is always in list mode. It would be
  very handy when one can change to icon mode, because then there's
  automatically a preview.

  This has especially much value when browsing for an image, say for
  adding an attachmant in a gmail message within firefox.

  Note. special lookup screens for example eog already have a preview,
  but this is a special mode, this should be generic.

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

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

[Desktop-packages] [Bug 328444] Re: gnome-terminal shortcuts: Alt+Shift+1 shows as Alt+! etc.

** Changed in: gnome-terminal
   Status: Confirmed => Expired

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

Title:
  gnome-terminal shortcuts: Alt+Shift+1 shows as Alt+! etc.

Status in GNOME Terminal:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-terminal

  Using Jaunty alpha 4, updating packages daily.

  I use irssi a lot, using gnome-terminal. By default irssi uses Alt+num
  to change windows, gnome-terminal uses Alt+num to change tabs. When
  multiple tabs are open, Alt+num keypress is catched by gnome-terminal,
  so I decided to bind tab keys differently:

  Alt-Shift-1 -> Tab 1
  Alt-Shift-2 -> Tab 2
  etc.

  The keypresses function just fine, but they are displayed like this:

  Alt-Shift-1 -> Alt-!
  Alt-Shift-2 -> Alt-@
  etc. (depends on keymap used)

  This behavious is, in my opinion, wrong.

  See screenshot (Finnish keymap used).

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

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

[Desktop-packages] [Bug 1281617] Re: Missing padding above menu's first item and below last item

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Missing padding above menu's first item and below last item

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Problem occurs with: light-themes 13.04+13.10.20131014-0ubuntu1, Ubuntu 13.10
  Does not occur with: light-themes 0.1.8.11, Ubuntu 11.04

  1. Position the pointer on an empty area of the desktop, or of a Nautilus 
window's main pane.
  2. Without moving the pointer at all, either hold down the right mouse 
button, or click once.
  3. Release the button, or click again.

  What happens:
  2. A shortcut menu opens with "New Folder" highlighted.
  3. A new folder is created.

  What should happen:
  2. A shortcut menu opens with nothing highlighted.
  3. Nothing.

  This is a regression of bug 626462. I noticed the problem during a
  usability test in 2009 or 2010, when someone tapped absent-mindedly on
  the right mouse button and created a folder without realizing it.

  The fix is to add as much padding above every menu's first item, and
  below its last item, as there is above or below a menu separator (as
  illustrated in bug 659866).

  Fixing this would also help avoid accidentally closing a menu in the
  menu bar, when its first item is a submenu or other control that is
  dangerously close to other items in the menu bar.

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

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

[Desktop-packages] [Bug 1683359] Re: 17.04 rdesktop crash

2018-05-03 Thread sles

>The old (v1.8.3) version still works fine.

>no issues with rdesktop to
>Windows 2008 upwards with rdesktop 1.8.3.

which one?

>I don't see it getting fixed given
>that it's an end of life product.

well, such position will not bring ubuntu more users :-)

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

Title:
  17.04 rdesktop crash

Status in rdesktop package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  After upgrading to 17.04 rdesktop crashes while connecting to windows
  2003:

  
  dm@dm:~$ LANG=C rdesktop -g 1024x758 elk
  Failed to negotiate protocol, retrying with plain RDP.
  Ошибка сегментирования (стек памяти сброшен на диск)
  dm@dm:~$ 

  
  Previous version , i.e. from 16.10 works just fine though..

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

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

[Desktop-packages] [Bug 1752456] Re: package libp11-kit-gnome-keyring 3.27.4-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) is not co-installable wit

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

** This bug has been marked a duplicate of bug 1768541
   package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: 
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances

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

Title:
  package libp11-kit-gnome-keyring 3.27.4-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-
  Arch: no) is not co-installable with libp11-kit-gnome-keyring which
  has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  I think this occured during a large package update.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.27.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 28 23:40:38 2018
  Dependencies:
   gcc-8-base 8-20180218-1ubuntu1
   libc6 2.26-0ubuntu2.1
   libgcc1 1:8-20180218-1ubuntu1
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.27.4-1ubuntu1
   Unpacking glib-networking-common (2.55.90-1) over (2.54.1-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Ko9Wpj/040-libp11-kit-gnome-keyring_3.27.4-2ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  InstallationDate: Installed on 2011-10-14 (2329 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.27.4-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (37 days ago)

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

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

[Desktop-packages] [Bug 1768499] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.48-0ubuntu3

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

Bug description:
  nvidia driver not working after 18.04 upgrade from 16.04 LTS
  Had to reinstall an older version 340

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 21:05:09 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2015-10-17 (927 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1765504] Re: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

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

** This bug has been marked a duplicate of bug 1768541
   package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: 
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances

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

Title:
  package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  error while upgrade!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 14:58:45 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-0ubuntu3
   libgcc1 1:8-20180414-1ubuntu2
   multiarch-support 2.27-0ubuntu3
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  InstallationDate: Installed on 2014-05-28 (1422 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

2018-05-03 Thread sojusnik

Please change it to "confirmed". That's still a relevant issue.

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

Status in GTK+:
  Expired
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2018-05-03 Thread Reece

Lack of fractional scaling is a significant feature regression relative
to 17.10 with Unity for those of us with hidpi displays. What can users
do to show support for getting solved?

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

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

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  After restarting your computer, you should find additional scale
  options in Settings > Devices > Displays.

  If you change your mind and want to get back to supported status, run:

  gsettings reset org.gnome.mutter experimental-features

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

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

[Desktop-packages] [Bug 505765] Re: gedit problem with long lines

** Changed in: gedit
   Status: Confirmed => Expired

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

Title:
  gedit problem with long lines

Status in gedit:
  Expired
Status in One Hundred Papercuts:
  Triaged
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Hi,

  I was editing a text file when the cursor began to behave strangely.
  The file contained these lines:

  CREATE TABLE people(
   integer primary key,
   name varchar(50),
   age integer
  )

  When I put the cursor after the 'l' in 'people', the arrow key would
  not move the cursor to the right. Instead it jumped to the next line.
  Similarly, I could not add text at this position.

  Viewing the file in a hex editor revealed a lot of spaces (284 to be
  accurate) after the opening parenthesis. Probably I've added those
  spaces without knowing it (resting my book "beginning Ruby" on the
  space bar ^ ^). Still, I feel the editor should handle a few hundred
  chars on a line without misbehaviour.

  I attached a copy of the text file.

  Thanks for developing and maintaining this simple but useful editor!

  Tor

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  Tags:  ubuntu-unr
  Uname: Linux 2.6.28-17-generic i686

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

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

[Desktop-packages] [Bug 1756619] Re: nautilus-actions package missing in Ubuntu 18.04 beta

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

** Changed in: nautilus-actions (Ubuntu)
   Status: New => Confirmed

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

Title:
  nautilus-actions package missing in Ubuntu 18.04 beta

Status in gedit package in Ubuntu:
  Invalid
Status in nautilus-actions package in Ubuntu:
  Confirmed

Bug description:
  ***
  Please change this bug from gedit to the correct package.
  ***

  Synaptic no longer offers package nautilus-actions for installation.

  This package is required for right click custom actions in file
  manager and the desktop.

  Please reinstate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 19:39:57 2018
  InstallationDate: Installed on 2018-03-10 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768830] [NEW] the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

2018-05-03 Thread Hui Wang

Public bug reported:

Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.


So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

And we have several Lenovo machines like Lenovo P520 which have 2
analogue audio codecs on them, to make the audio work on those machines,
the kernel needs 3 patches for alsa driver, and those 3 patches are
already in the linux kernel from linux-4.12, kernel is not a blocking
issue under ubuntu 18.04:

7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
56798e6b ALSA: hda - Use a helper function for renaming kctl names
ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420


Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

2b9b3f01 ucm: Assure the user input card name not to exceed max size of
card long name (it is in the alsa-lib v1.1.4)

4b9297e6 ucm: Load device-specific configuration file based on the card
long name (it is in the alsa-lib v1.1.4)

b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
the alsa-lib v1.1.6)

181f8e25 ucm: adding the folder of card_long_name when finding verb conf
file (it is in the alsa-lib v1.1.6+)

81db276f conf/ucm: increase the input volume for LineIn (it is in the
alsa-lib v1.1.6+)

To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
minor change to resolve the patch conflict. And I attached 5 patches to
this bug, these patches can be successfully applied to v1.1.3-5 without
any change.

After applying this patches, the ucm searcher will look for folder
according to card_long_name first, if it fails, it will fallback to use
card_name as before, so these 5 patches are safe and will not introduce
any regression.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: alsa-lib (Ubuntu)
 Importance: Critical
 Status: New


** Tags: originate-from-1735041 sutton

** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)

** Summary changed:

- the audio can't work on Lenovo machines with dual analogue cocecs underubuntu 
18.04
+ the audio can't work on Lenovo machines with dual analogue codecs under 
ubuntu 18.04

** Tags added: originate-from-1735041 sutton

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  
  So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

  And we have several Lenovo machines like Lenovo P520 which have 2
  analogue audio codecs on them, to make the audio work on those
  machines, the kernel needs 3 patches for alsa driver, and those 3
  patches are already in the linux kernel from linux-4.12, kernel is not
  a blocking issue under ubuntu 18.04:

  7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
  56798e6b ALSA: hda - Use a helper function for renaming kctl names
  ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

  
  Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size
  of card long name (it is in the alsa-lib v1.1.4)

  4b9297e6 ucm: Load device-specific configuration file based on the
  card long name (it is in the alsa-lib v1.1.4)

  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
  in the alsa-lib v1.1.6)

  181f8e25 ucm: adding the folder of card_long_name when finding verb
  conf file (it is in the alsa-lib v1.1.6+)

  81db276f conf/ucm: increase the input volume for LineIn (it is in the
  alsa-lib

[Desktop-packages] [Bug 170049] Re: Inverted ruler co-ordinate system

2018-05-03 Thread Thomas Holder

@tweenk mind if I assign this to myself? I'd like to work on this.

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

Title:
  Inverted ruler co-ordinate system

Status in Inkscape:
  Confirmed
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  The y-axis of the rulers' co-ordinate system is
  inverted (increasing upwards), and places the origin on
  the bottom left of the viewport. The SVG spec places the
  default origin on the top left of the viewport, and has
  the co-ordinate system increasing to the right and
  downwards.

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

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

[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor

tweaked the version and fixed the email address and uploaded

** Changed in: libgtop2 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Snap mounts should be hidden from System Monitor

Status in gnome-system-monitor package in Ubuntu:
  In Progress
Status in libgtop2 package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  snaps mount at listed in the system monitor but they are an implementation 
detail and not interesting there. We already filter them out of the Disks UI, 
we should do the same in the system monitor

  * Test case
  - have a snap installed (wshich is true in the default installation of Ubuntu)
  - open gnome-system-monitor
  - check the filesystem tabs content, snaps mounts shouldn't be listed

  * Regression potential
  Check that the system mounted partitions are still correctly listed

  --

  As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the
  snap mounts in System Monitor should be hidden just as they're hidden
  from GNOME Disks. Perhaps they should be grouped under a dropdown of /
  (though this would require developing a new feature)?

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

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

[Desktop-packages] [Bug 1085976] Re: Documentation has "FIXME" items that are unfixed

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Documentation has "FIXME" items that are unfixed

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  The Ubuntu package libgtk-3-doc supplies the items of interest...
  In the directory /usr/share/doc/libgtk-3-doc/gtk3 there are 3 files that 
contain FIXME content

  In that directory:
  # grep FIXME *
  GtkApplication.html:FIXME: MISSING XINCLUDE CONTENT
  GtkBuilder.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:  FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  #

  I am just starting with GTK+ and Glade, so having this instead of the
  first code sample in the gtk-getting-started page is a show-stopper.
  I suggest it's as urgent as documentation bugs get.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgtk-3-doc 3.4.2-0ubuntu0.5
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  Date: Mon Dec  3 05:59:17 2012
  Dependencies:
   
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 543611] Re: emacsclient -c randomly crashes emacs about 1 in every 5 to 10 times

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  emacsclient -c randomly crashes emacs about 1 in every 5 to 10 times

Status in GNU Emacs:
  Fix Released
Status in GTK+:
  Expired
Status in emacs23 package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: emacs23

  I am trying to start using emacs --daemon and emacsclient, so that I
  can easily have multiple emacs windows sharing a single process.
  However, my attempts are frustrated by the fact that when I use
  "emacsclient -c" to create a new window in an exising emacs session,
  emacs crashes about 1 in 5 times. It seems completely random.

  Here's what I've been using to reproduce this:

  x=0; emacs23 -Q --daemon &>/dev/null; while emacsclient -c
  &>/dev/null; do x=$(( $x + 1 )); done; echo "Created $x windows before
  crash."

  
  That will start the daemon, and then keep spawning new emacs windows as long 
as the daemon is running. Just keep closing the windows, and new ones will pop 
up. Every time I do this command, I get a different number of windows before 
emacs crashes. On my last five tries, I have gotten 7, 17, 12, 18, and 24 
windows. Hence my claim of randomness.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Mar 21 10:34:10 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia wl
  Package: emacs23 23.1+1-4ubuntu3.1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-13bfsbfq1.43-generic
  SourcePackage: emacs23
  Uname: Linux 2.6.31-13bfsbfq1-generic x86_64

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

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

[Desktop-packages] [Bug 803824] Re: Can't change the gtkfilechooser view

** Changed in: gtk
   Status: In Progress => Expired

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

Title:
  Can't change the gtkfilechooser view

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When using File open in an application the Nautilus File Dialog shows up. It 
has severe shortcomings (see attached screenshot):
  (1) Hidden files show or don't show based on the selection made in Nautilus 
earlier. No UI (e.g. at (2)) is provided to toggle (Ctrl+H seems to work)
  (3) display is always in detail mode Ctrl1-3 or Ctlr+- to alter the display 
don't work.

  Show/Hide hidden files is available through keyboard shortcuts or rightclick, 
so a UI element is a nice-to-have.
  The lack of display settings (e.g. specify columns like in the main window) 
like icons/list/details is a usability issue.

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

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

[Desktop-packages] [Bug 241604] Re: Maximum zoom in Evince is 400%

2018-05-03 Thread Pander

** Tags added: bionic

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

Title:
  Maximum zoom in Evince is 400%

Status in Evince:
  Confirmed
Status in One Hundred Papercuts:
  Invalid
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  Evince zoom max is 400%, and in some pdf this is too small. I have to
  use xpdf to open some file in a usable way.. you should remove this
  limit

  ProblemType: Bug
  Architecture: i386
  Date: Fri Jun 20 13:26:32 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/evince
  NonfreeKernelModules: nvidia
  Package: evince 2.22.2-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  Uname: Linux 2.6.24-19-generic i686

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

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

[Desktop-packages] [Bug 1578129] Re: Can't drag symlink to folder to bookmarks

** Changed in: nautilus
   Status: Confirmed => Expired

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

Title:
  Can't drag symlink to folder to bookmarks

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Fresh clean installation of Ubuntu 16.04
  GNOME nautilus 3.14.3
  kernel 4.4.0-21-generic 

  Bug scenario:
  1) Create symlink to folder
  2) Try to drag and drop  symlink  to the custom bookmarks pad.
  3) While dragging and having mouse on the boomarks area, label "New 
bookmarks" is displayed, but  after dropping the bookmark to symlink is not 
added to bookmark area

  However, it is possible to add bookmark to symlink via menu bar or
  Ctrl+D.

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

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

[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor

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

** Description changed:

+ * Impact
+ snaps mount at listed in the system monitor but they are an implementation 
detail and not interesting there. We already filter them out of the Disks UI, 
we should do the same in the system monitor
+ 
+ * Test case
+ - have a snap installed (wshich is true in the default installation of Ubuntu)
+ - open gnome-system-monitor
+ - check the filesystem tabs content, snaps mounts shouldn't be listed
+ 
+ * Regression potential
+ Check that the system mounted partitions are still correctly listed
+ 
+ --
+ 
  As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the
  snap mounts in System Monitor should be hidden just as they're hidden
  from GNOME Disks. Perhaps they should be grouped under a dropdown of /
  (though this would require developing a new feature)?

** Changed in: libgtop2 (Ubuntu)
   Importance: Undecided => Low

** Changed in: libgtop2 (Ubuntu)
   Status: New => In Progress

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

Title:
  Snap mounts should be hidden from System Monitor

Status in gnome-system-monitor package in Ubuntu:
  In Progress
Status in libgtop2 package in Ubuntu:
  In Progress

Bug description:
  * Impact
  snaps mount at listed in the system monitor but they are an implementation 
detail and not interesting there. We already filter them out of the Disks UI, 
we should do the same in the system monitor

  * Test case
  - have a snap installed (wshich is true in the default installation of Ubuntu)
  - open gnome-system-monitor
  - check the filesystem tabs content, snaps mounts shouldn't be listed

  * Regression potential
  Check that the system mounted partitions are still correctly listed

  --

  As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the
  snap mounts in System Monitor should be hidden just as they're hidden
  from GNOME Disks. Perhaps they should be grouped under a dropdown of /
  (though this would require developing a new feature)?

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

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

[Desktop-packages] [Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.

2018-05-03 Thread Jan Niklas Hasse

New upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/322

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

Title:
  Right-click should not pre-light first option, too easy to
  accidentally select the first Context-menu option.

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When I right click in nautilus, the context menu appear. If I right
  click on a menu item, the function of that menu item is performed.
  This is very annoying, because when the context menu appears, the
  mouse is at the first menu item, so if you accidentally right click
  two times, you will surely perform the function of the first menu
  item! Everytime I right click in desktop, i probably create a new
  Folder!

  I think there maybe 2 solutions to this:
  - To perform the function of a menu item, only left click is allowed.
  - When the user right click, the context menu will appear at a bit lower 
position, so the mouse will not be at the first menu item.

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

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

[Desktop-packages] [Bug 1761844] Re: Thunderbird: emojis is displayed in the email list

2018-05-03 Thread Wal

I can confirm I too have this problem. Three pc's running ubuntu 18.04
and all have the same problem in thunderbird. This was not present
running thunderbird on Ubuntu 16.04. This problem does not replicate on
thunderbird in Windows. It would appear that it is Operating System
specific.

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

Title:
  Thunderbird: emojis is displayed in the email list

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

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

** Changed in: cairo
   Status: Unknown => Confirmed

** Changed in: cairo
   Importance: Unknown => Medium

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

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

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

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 Gnome Shell with Communitheme.

  Steps to reproduce:
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  Screenshot attached

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

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

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

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

A patch to fix the crash is here:
https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6

If we fail to get cairo fixed for any reason, it's probably possible to
do a workaround/fix in ubiquity. But I think there are now multiple
reasons to fix cairo as first preference.

** Bug watch added: freedesktop.org Bugzilla #98883
   https://bugs.freedesktop.org/show_bug.cgi?id=98883

** Also affects: cairo via
   https://bugs.freedesktop.org/show_bug.cgi?id=98883
   Importance: Unknown
   Status: Unknown

** Changed in: ubiquity (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Andrea Azzarone (azzar1)

** Changed in: ubiquity (Ubuntu Bionic)
 Assignee: Daniel van Vugt (vanvugt) => Andrea Azzarone (azzar1)

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

Robert, is the list we display coming directly from snapd? or a bug in
g-s/snapd-glib?

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics

2018-05-03 Thread Hadmut Danisch

Are you just here to keep me busy with useless conversation?


As I said: 

- that machine with that monitor connected over display port was working well 
for more than a year with 
  ubuntu 16.10, 17.04, 17.10, it just took the nomodeset

- and it works well under 18.04 just for the login screen, trouble
begins after login.


So don't tell me what the hardware is capable of. The hardware was doing the 
job until last friday when I put a fresh 18.04 on that machine. 



The question is: 

What happens between the login screen's X11-Session and the user
X11-Session. Why is the former working and the latter not.

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

Title:
  Lubuntu: X11 freezing/low resolution on N3150 intel graphics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just installed a fresh 18.04 on an ASRock beebox N3150 machine.

  The regular ubuntu desktop installer hanged after entering X11 mode,
  machine froze.

  I then used Lubuntu alternate installer with the console based
  installation, which worked without any problem.

  But after rebooting the system again hung after the graphical login
  prompt.

  I then changed the boot options in /etc/default/grub to give the
  kernel the options nosplash nomodeset and to leave the system in
  console mode (I had similar experiences with former ubuntu versions on
  that machine where X11 did not start when the mode had been set by
  console.)

  
  Now X11 works, but comes up in vesa mode (1024x768) only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 30 12:25:09 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

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

** Changed in: cairo (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: cairo (Ubuntu)
   Status: New => In Progress

** Changed in: cairo (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: cairo (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

https://bugs.launchpad.net/ubuntu/+source/gnome-
software/+bug/1768779/comments/3 has the snapd list of channels/versions

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 439239] Re: Selecting a folder to save to loses focus on file name

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Selecting a folder to save to loses focus on file name

Status in GTK+:
  Expired
Status in One Hundred Papercuts:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  This bug has occured multiple times before, however the fixes no
  longer seem to be working:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/130224,
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/22322, and
  their duplicates.

  In short: the task of saving a file is broken as soon as the user
  chooses a different folder.  Typing no longer renames the file but
  instead starts searching for folders in the list, however the text
  selecting the filename is still highlighted.

  I believe the task of naming a file to save is much more common than
  having to do a text search to find a folder to save to (they're
  already alphabetically ordered).  Accordingly, the filename should
  never lose focus, even when the user is active inside the other parts
  of the file save dialog (eg making/selecting a folder to save to).

  
  To reproduce: in Gedit, make a new file and File->Save as.  Click a folder 
and then start typing.  A similar thing happens if you save a picture in 
Firefox.

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Sep 30 01:55:52 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: libgtk2.0-0 2.18.0-1ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: gtk+2.0
  Uname: Linux 2.6.31-11-generic x86_64

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

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

[Desktop-packages] [Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Right-click should not pre-light first option, too easy to
  accidentally select the first Context-menu option.

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When I right click in nautilus, the context menu appear. If I right
  click on a menu item, the function of that menu item is performed.
  This is very annoying, because when the context menu appears, the
  mouse is at the first menu item, so if you accidentally right click
  two times, you will surely perform the function of the first menu
  item! Everytime I right click in desktop, i probably create a new
  Folder!

  I think there maybe 2 solutions to this:
  - To perform the function of a menu item, only left click is allowed.
  - When the user right click, the context menu will appear at a bit lower 
position, so the mouse will not be at the first menu item.

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

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

[Desktop-packages] [Bug 1164829] Re: Place an "Add Printer" button on print dialog

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Place an "Add Printer" button on print dialog

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When I print a document (by choosing File then Print) I am able to
  select any installed printer  But, sometimes I want to use a printer
  on the network and I have not installed it yet.  I really wish there
  was a button on the print dialog box (from File/Print) that would be
  labeled "Add Printer" that would take me to the printers/add a printer
  dialog box.  That way, I could add the printer I want and have it
  listed in the list of printers without me having to leave the
  application, go to the printers application, add a printer, return to
  the original application and choose File and Print then choose the new
  printer.

  This is like when you save a document and you realize the folder you
  want does not exist, you don't have to exit and go to Nautilus, create
  the folder, then return to the application to save the file in the new
  folder.  You just select the Create a New folder button when you save
  the file.  Same idea with the printer - when you print and the printer
  does not exist click on a button that allows you to add it right then.

  Note, I am not suggesting that network printers be automatically
  installed.  Just add a button on the File/Print dialog box that takes
  you to Printer/Add New Printer box.  No other OS makes it this easy to
  allow you to add a printer at the time when you print a document so
  this would be helpful.  Also helpful for the new person who wants to
  print something to a network printer and when they don't see it in the
  list of installed printers, they wouldn't have to ask "where do I go
  to add a printer" since the button would be right there.

  Thanks

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

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

[Desktop-packages] [Bug 1480387] Re: Clicking a date to go back or forward a month causes repeated jumps between two dates

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Clicking a date to go back or forward a month causes repeated jumps
  between two dates

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
  or trusty. It happened for me in the most recent wily iso.

  Open the indicator, click one of the greyed dates at the start or end
  of the month (sometimes requires more than one go). The active date
  starts to repeatedly jump between this date and another one. I ran
  with G_MESSAGES_DEBUG=all and when it's happening this is spammed (I
  clicked a date in 2015-05).

  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 31 17:09:43 2015
  InstallationDate: Installed on 2012-10-07 (1026 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2013-05-07 (815 days ago)

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

bug #1768779 has details

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

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

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1685878] Re: Gedit bottom scroll bar goes on top of final line

** Changed in: gtk
   Status: New => Expired

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

Title:
  Gedit bottom scroll bar goes on top of final line

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still
  Gedit 3.22, and I have found something slightly annoying with it, and
  that is that when mousing over the last line to try to copy and paste
  it for instance, the bottom scroll bar goes on top of it and obscures
  it. I have attached two screenshots of what I mean.

  This also affects me on Arch so I have filled an upstream report on
  this.

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

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

[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

2018-05-03 Thread Jacob Zimmermann

My WiFi is working perfectly but I'm still getting these messages

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

k, let's keep that one about the scrolling issue then

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

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

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 Gnome Shell with Communitheme.

  Steps to reproduce:
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  Screenshot attached

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

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

[Desktop-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-03 Thread Will Cooke

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

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

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

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

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

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

[Desktop-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

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

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

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

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

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

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

[Desktop-packages] [Bug 1768797] [NEW] LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-03 Thread Will Cooke

Public bug reported:

I enabled LivePatch via gnome-initial-setup and added my U1 account to
g-o-a.

My U1 account gets marked as expired quite often. When it's expired the
LP entry in Software & Updates is not ticked to show that LP is running.
When my u1 account is re-authenticated then everything shows correctly.

This could make it seem that LivePatch does not run if your account
expires, which is not the case.

** Affects: gnome-online-accounts (Ubuntu)
Importance: High
Assignee: Andrea Azzarone (azzar1)
Status: New

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

Title:
LivePatch in Software & Updates shows that LP is not enabled when the
U1 account has expired in g-o-a

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

Bug description:
I enabled LivePatch via gnome-initial-setup and added my U1 account to
g-o-a.

My U1 account gets marked as expired quite often. When it's expired
the LP entry in Software & Updates is not ticked to show that LP is
running. When my u1 account is re-authenticated then everything shows
correctly.

This could make it seem that LivePatch does not run if your account
expires, which is not the case.

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

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

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

2018-05-03 Thread Phillip Lord

Also here, with a Radeon R7.

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

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

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

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

  This problem is reproducible.

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

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

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

2018-05-03 Thread Michal Predotka

I've reported another bug about same entries: bug #1768794

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 Gnome Shell with Communitheme.

  Steps to reproduce:
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  Screenshot attached

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

Robert, is the list we display coming directly from snapd? or a bug in
g-s/snapd-glib?

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 Gnome Shell with Communitheme.

  Steps to reproduce:
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  Screenshot attached

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

2018-05-03 Thread Didier Roche

The list of real entries are (at that time, it's dynamic):

TrackArchChannel  VersionRevision   
 Expires at
latest   all stable   0.1124
 candidate^  ^
 beta ^  ^
 edge 0.1170
 edge/gnome-shell-communitheme-pr125  0.1112
 2018-05-26T13:54:16.742243
 edge/gnome-shell-communitheme-pr128  0.1144
 2018-05-29T22:59:41.400161
 edge/gnome-shell-communitheme-pr130  0.1108
 2018-05-26T09:21:19.157622
 edge/gnome-shell-communitheme-pr131  0.1125
 2018-05-27T12:05:18.882819
 edge/gnome-shell-communitheme-pr136  0.1132
 2018-05-27T21:09:57.216625
 edge/gtk-communitheme-pr371  0.1123
 2018-05-27T10:43:32.369778
 edge/gtk-communitheme-pr374  0.1128
 2018-05-27T16:17:18.898120
 edge/gnome-shell-communitheme-pr143  0.1136
 2018-05-28T08:51:24.786638
 edge/gtk-communitheme-pr384  0.1159
 2018-05-31T08:48:58.912739
 edge/gtk-communitheme-pr385  0.1164
 2018-05-31T22:17:13.052878
 edge/gtk-communitheme-pr387  0.1146
 2018-05-30T09:35:43.783124
 edge/gnome-shell-communitheme-pr149  0.1148
 2018-05-30T14:05:02.010329
 edge/gnome-shell-communitheme-pr150  0.1150
 2018-05-30T16:23:04.423498
 edge/gnome-shell-communitheme-pr151  0.1155
 2018-05-30T22:11:56.694347
 edge/communitheme-snap-helpers-pr9   0.1156
 2018-05-30T22:49:43.618408
 edge/gnome-shell-communitheme-pr158  0.1160
 2018-05-31T16:11:35.365221
 edge/gtk-communitheme-pr392  0.1167
 2018-06-01T14:24:25.782118
 edge/gtk-communitheme-pr393  0.1168
 2018-06-01T14:46:23.289516
 edge/gtk-communitheme-pr394  0.1169
 2018-06-01T14:46:53.708757
 amd64   stable   0.197
 candidate^  ^
 beta ^  ^
 edge 0.1104
 edge/ubuntu-communitheme-snap-helpers-1  0.14  
 2018-05-04T10:05:45.478718
 edge/communitheme-snap-helpers-pr1   0.129 
 2018-05-05T09:31:00.421780
 edge/blablab-branch-pr1  0.110 
 2018-05-04T14:44:43.359591
 edge/communitheme-snap-helpers-pr2   0.135 
 2018-05-09T15:05:08.609020
 edge/communitheme-sounds-pr5 0.138 
 2018-05-10T08:46:42.989211
 edge/cursor-communitheme-pr1 0.139 
 2018-05-10T08:50:04.794461
 edge/gtk-communitheme-pr321  0.140 
 2018-05-10T08:52:08.630168
 edge/test-gtk2   0.145 
 2018-05-11T08:52:14.866723
 edge/communitheme-snap-helpers-pr3   0.146 
 2018-05-11T09:02:37.264041
 edge/communitheme-snap-helpers-pr4   0.164 
 2018-05-13T13:25:53.288391
 edge/communitheme-snap-helpers-pr6   0.166 
 2018-05-16T09:40:08.990495
 edge/communitheme-snap-helpers-pr7   0.168 
 2018-05-20T07:42:54.143890
 edge/gnome-shell-communitheme-pr122  0.172 
 2018-05-21T20:17:17.099928
 edge/gnome-shell-communitheme-pr123  0.181 
 2018-05-23T19:43:13.058809
 edge/gnome-shell-communitheme-pr125  0.1105
 2018-05-26T13:54:16.742243
 edge/gnome-shell-communitheme-pr126  0.180 
 2018-05-23T18:30:45.643229
 edge/gtk-communitheme-pr360  0.186 
 2018-05-24T18:07:42.761720
 edge/gnome-shell-communitheme-pr127  0.188 
 2018-05-24T21:20:07.959559
 edge/gtk-communitheme-pr361  0.189 
 2018-05-24T21:21:29.565369
 edge/gnome-shell-communitheme-pr128  0.1103
 2018-05-29T22:59:41.400161

[Desktop-packages] [Bug 1768785] Re: Crashes on Ubuntu startup in 18.04

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Crashes on Ubuntu startup in 18.04

Status in remmina package in Ubuntu:
  Incomplete

Bug description:
  Just crashes.

  remmina --version
  StatusNotifier/Appindicator support: your desktop does support it and 
libappindicator is compiled in remmina. Good!
  Running under Gnome Shell version 3.28.1
  Remmina - 1.2.0-rcgit-29 (git rcgit-29)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   linux-image-extra-4.13.0-36-generic:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Apr 29 06:31:21 2018
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-10-16 (198 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: remmina
  Title: package remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1 failed 
to install/upgrade: проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (4 days ago)

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

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

[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend

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

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

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

Title:
  Screen is displayed when resuming from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

Thank you for your bug report. The list not being scrollable is an issue
but there is also a bug that its has more entries that it should.

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

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

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 Gnome Shell with Communitheme.

  Steps to reproduce:
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  Screenshot attached

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

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

[Desktop-packages] [Bug 1768794] [NEW] A lot of the same entries for Communitheme snap channels

2018-05-03 Thread Michal Predotka

Public bug reported:

Steps to reproduce:
1. Search for ”communitheme”
2. Select ”communitheme” result
3. Click on the channel selection button
4. You will see a popup with loong list of channels

Notice the names are all the same

Screenshot attached

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Thu May  3 10:38:37 2018
InstallationDate: Installed on 2018-04-30 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.28.1-0ubuntu4
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Zrzut ekranu z 2018-05-03 09-21-19.png"
   
https://bugs.launchpad.net/bugs/1768794/+attachment/5132887/+files/Zrzut%20ekranu%20z%202018-05-03%2009-21-19.png

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  gnome-terminal crashes when tab is dragged onto another tab's terminal
  area

Status in GNOME Terminal:
  Confirmed
Status in GTK+:
  Expired
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  This bug occurs when I drag an existing terminal tab out of the tab
  bar and drop it onto the text area of the open terminal. Usually
  occurs by accident, to be honest (when I don't mean to drag the tab at
  all, for instance) but it's 100% reproducible intentionally.

  I found several old bug reports on similar issues, but they were
  either not detailed enough to figure out if they were exactly the same
  or were closed as duplicates of a bug that no longer exists
  (https://bugs.launchpad.net/ubuntu/+source/gnome-
  terminal/+bug/1442826).

  Apport generated a report (title: gnome-terminal-server crashed with
  SIGABRT in g_assertion_message()) for me and then helpfully explained
  that the bug had already been filed. It redirected me to a bug that
  doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm
  refiling it here.

  1. Ubuntu release:
  spyro@julep:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. Package version:
  spyro@julep:~$ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu3~ubuntu16.04.1
Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1
Version table:
   *** 3.20.2-1ubuntu3~ubuntu16.04.1 500
  500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   3.18.3-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  spyro@julep:~$ 

  3. Expected behavior: Tab should split into a new window (as it does
  if you drop it onto someplace that's not a gnome-terminal window). At
  the worst, it should go back to where it was on the tab bar instead of
  crashing.

  4. Actual behavior: The whole gnome-terminal window crashes, losing
  any activity or work on other tabs. Other open gnome-terminal windows
  also crash and close.

  From /var/log/syslog:
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER 
(cont
  ainer)' failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER 
(cont
  ainer)' failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: **
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
Gtk:ERROR:/build/gtk+3.0-j0Vp0u/
  gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion 
fail
  ed: (window != NULL)
  Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service 
name
  ='org.gnome.Contacts.SearchProvider'
  Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service 
name
  ='org.gnome.Documents'
  Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service 
name
  ='org.gnome.Nautilus'

  I've also saved the apport-generated crash report if that would be
  helpful to upload.

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

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

[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

2018-05-03 Thread Gede Suartana

The WiFi is off, and I used the Ethernet connection "everything OK".
It's still  popup shows incessantly Activation of network connection
failed.

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

2018-05-03 Thread Andrew Hayzen

@Ads2, Yup I'm preparing an SRU for the next microrelease, you can
track in bug 1767215. I am able to use flatpakref's with 0.11.3-3, if
you are still having an issue please report upstream :-) (I have also
seen issues discussed as different browsers acting differently, or the
browser associating mime types itself - causing issues, wonder if that
is the case 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/1716409

Title:
  Unable to install flatpakref on Ubuntu artful

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

Bug description:
  I saw a news article with a link to install a flatpak.

  http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4

  I clicked the link expecting to be able to install the flatpak, but
  the experience appears broken. I'm on an up to date Artful install

  What I did was:-

  Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4
  Click the flathub link:- 
https://flathub.org/repo/appstream/io.github.Pithos.flatpakref
  This downloaded the flatpakref file.
  I clicked the file in my browser, nothing happened

  I then tried finding the file in nautilus and double clicked it.
  GNOME Software launched and presented an error "Don't know how to handle 
'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot).

  If I search for pithos in GNOME Software I am able to find the older
  version from the deb repo, but not the newer version from flathub.

  Do we not support flatpak/flathub out of the box? Or is my system
  uniquely hosed?

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

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

[Desktop-packages] [Bug 1768789] [NEW] connectivity results in limited when behind proxy

2018-05-03 Thread Markus Lindberg

Public bug reported:

The connectivity for a connection results in limited when behind a proxy
for NetworkManager.

$ sudo nmcli general 
STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
connected (site only)  limited   enabled  enabled  enabled  enabled

$ sudo nmcli networking connectivity check 
limited

I have configured my proxy in both '/etc/environment' and via the GUI
under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

After this is set I can do an HTTP GET against the URL/URI you have
configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
ubuntu.conf' file.

$ curl -I http://connectivity-check.ubuntu.com/
HTTP/1.1 204 No Content
Date: Thu, 03 May 2018 09:01:34 GMT
Server: Apache/2.4.18 (Ubuntu)
X-NetworkManager-Status: online
X-Cache: MISS from proxy.example.com
X-Cache-Lookup: MISS from proxy.example.com:3128
Via: 1.1 proxy.example.com (squid/3.3.8)
Connection: keep-alive

$ env|grep -i proxy
auto_proxy=http://proxy.example.com/auto
https_proxy=http://proxy.example.com:3128
http_proxy=http://proxy.example.com:3128

But network connectivity still fails to use the proxy.

I assume that the 'network-manager-config-connectivity-ubuntu' package
is used for this feature after reading the following output.

$ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
ubuntu.conf' file the connectivity check succeeds or I don't get limited
connectivity at least.

--
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

$ uname -a
Linux lnxhplap2 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l|grep network-manager
ii  network-manager1.10.6-2ubuntu1  
   amd64network management framework (daemon and userspace tools)
ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1  
   all  NetworkManager configuration to enable connectivity checking
ii  network-manager-gnome  1.8.10-2ubuntu1  
   amd64network management framework (GNOME frontend)
ii  network-manager-pptp   1.2.6-1  
   amd64network management framework (PPTP plugin core)
ii  network-manager-pptp-gnome 1.2.6-1  
   amd64network management framework (PPTP plugin GNOME GUI)
--

Note: I have used "proxy.example.com" as substitute for our proxy server
in this bug report for privacy reasons.

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

Title:
  connectivity results in limited when behind proxy

Status in network-manager package in Ubuntu:
  New

Bug description:
  The connectivity for a connection results in limited when behind a
  proxy for NetworkManager.

  $ sudo nmcli general 
  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected (site only)  limited   enabled  enabled  enabled  enabled

  $ sudo nmcli networking connectivity check 
  limited

  I have configured my proxy in both '/etc/environment' and via the GUI
  under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

  After this is set I can do an HTTP GET against the URL/URI you have
  configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file.

  $ curl -I http://connectivity-check.ubuntu.com/
  HTTP/1.1 204 No Content
  Date: Thu, 03 May 2018 09:01:34 GMT
  Server: Apache/2.4.18 (Ubuntu)
  X-NetworkManager-Status: online
  X-Cache: MISS from proxy.example.com
  X-Cache-Lookup: MISS from proxy.example.com:3128
  Via: 1.1 proxy.example.com (squid/3.3.8)
  Connection: keep-alive

  $ env|grep -i proxy
  auto_proxy=http://proxy.example.com/auto
  https_proxy=http://proxy.example.com:3128
  http_proxy=http://proxy.example.com:3128

  But network connectivity still fails to use the proxy.

  I assume that the 'network-manager-config-connectivity-ubuntu' package
  is used for this feature after reading the following output.

  $ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

  If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file the connectivity check succeeds or I don't get
  limited connectivity at least.

  --
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename:

[Desktop-packages] [Bug 945430] Re: Lists lack zebra-striping

2018-05-03 Thread TomasHnyk

The upstream bug moved to https://gitlab.gnome.org/GNOME/gtk/issues/581
(Launchpad does not seem to know about gitlab).

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

Title:
  Lists lack zebra-striping

Status in GTK+:
  Expired
Status in light-themes:
  Fix Released
Status in Ubuntu theme:
  Fix Released
Status in light-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  We had it before and was taken out in Precise. We need this back. It
  makes apps like Rhythmbox much easier to handle.

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

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

[Desktop-packages] [Bug 1768785] [NEW] Crashes on Ubuntu startup in 18.04

2018-05-03 Thread FractalizeR

Public bug reported:

Just crashes.

remmina --version
StatusNotifier/Appindicator support: your desktop does support it and 
libappindicator is compiled in remmina. Good!
Running under Gnome Shell version 3.28.1
Remmina - 1.2.0-rcgit-29 (git rcgit-29)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 linux-image-extra-4.13.0-36-generic:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Apr 29 06:31:21 2018
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2017-10-16 (198 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: remmina
Title: package remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1 failed to 
install/upgrade: проблемы зависимостей — оставляем не настроенным
UpgradeStatus: Upgraded to bionic on 2018-04-28 (4 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  Crashes on Ubuntu startup in 18.04

Status in remmina package in Ubuntu:
  New

Bug description:
  Just crashes.

  remmina --version
  StatusNotifier/Appindicator support: your desktop does support it and 
libappindicator is compiled in remmina. Good!
  Running under Gnome Shell version 3.28.1
  Remmina - 1.2.0-rcgit-29 (git rcgit-29)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   linux-image-extra-4.13.0-36-generic:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Apr 29 06:31:21 2018
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-10-16 (198 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: remmina
  Title: package remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1 failed 
to install/upgrade: проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (4 days ago)

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

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

[Desktop-packages] [Bug 1768786] [NEW] Screen is displayed when resuming from suspend

2018-05-03 Thread Will Cooke

Public bug reported:

Steps to reproduce and description:

First test case - where things work correctly:

1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
2.  Suspend your machine
3.  Resume your machine
4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

Second test case - where things are broken

1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
2.  Suspend your machine
3.  Resume your machine
4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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

Title:
  Screen is displayed when resuming from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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

[Desktop-packages] [Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

2018-05-03 Thread Ads20000

I'm using 0.11.3-3 from the repositories, does 0.11.6 need to be SRU'd?
Since this is a new upstream microrelease that should be acceptable, if
someone wants to follow the process for making that happen:
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

Title:
  Unable to install flatpakref on Ubuntu artful

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

Bug description:
  I saw a news article with a link to install a flatpak.

  http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4

  I clicked the link expecting to be able to install the flatpak, but
  the experience appears broken. I'm on an up to date Artful install

  What I did was:-

  Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4
  Click the flathub link:- 
https://flathub.org/repo/appstream/io.github.Pithos.flatpakref
  This downloaded the flatpakref file.
  I clicked the file in my browser, nothing happened

  I then tried finding the file in nautilus and double clicked it.
  GNOME Software launched and presented an error "Don't know how to handle 
'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot).

  If I search for pithos in GNOME Software I am able to find the older
  version from the deb repo, but not the newer version from flathub.

  Do we not support flatpak/flathub out of the box? Or is my system
  uniquely hosed?

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Ruslan

The issue is affecting me as well, GTX 1050, ASUS laptop.
None of the resolution tactics proposed so far helped in loading the drivers 
properly. 
The only way to load the system is to add nomodeset and acpi=off in the grub 
menu.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1768779] [NEW] Snap channel selection list not scrollable

2018-05-03 Thread Michal Predotka

Public bug reported:

Ubuntu 18.04 Gnome Shell with Communitheme.

Steps to reproduce:
1. Search for ”communitheme” in the store
2. Open ”communitheme” result
3. Click on the channel selection button
4. You will see a popup with loong list of channels
5. Try to scroll to see more entries

Expected result:
You can scroll the list

What happen instead:
You cannot scroll the list

Screenshot attached

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

** Attachment added: "Zrzut ekranu z 2018-05-03 09-21-19.png"

https://bugs.launchpad.net/bugs/1768779/+attachment/5132868/+files/Zrzut%20ekranu%20z%202018-05-03%2009-21-19.png

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

Title:
Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
New

Bug description:
Ubuntu 18.04 Gnome Shell with Communitheme.

Expected result:
You can scroll the list

What happen instead:
You cannot scroll the list

Screenshot attached

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

[Desktop-packages] [Bug 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

2018-05-03 Thread Ads20000

The bug is now at https://gitlab.gnome.org/GNOME/gtk/issues/624

** Changed in: gtk
   Importance: Medium => Undecided

** Changed in: gtk
   Status: Expired => New

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #766284 => None

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768764] Re: disable wayland by default - nvidia proprietary drivers backlight

Also, we do disable Wayland by default for login sessions. Ubuntu 18.04
uses Xorg by default.

Wayland is only enabled by default for gdm3. Do you have a problem with
the login screen?

Also, can you please run this command to tell us more information about
your system?;

  apport-collect 1768764

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

** No longer affects: mutter (Ubuntu)

** Tags added: nvidia

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

Title:
  disable wayland by default - nvidia proprietary drivers backlight

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  With wayland can't control screen brightness using nvidia proprietary
  drivers. The screen brightness is always at 100%.

  Please DON'T enable wayland by default on fresh installations or
  updates because it's not 100% compatible with nvidia proprietary
  drivers. Nouveau still doesn't support backlight control on Pascal
  cards.

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

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

[Desktop-packages] [Bug 1768764] Re: disable wayland by default - nvidia proprietary drivers backlight

"Wayland" is only a protocol and "wayland (Ubuntu)" is a series of
libraries for that protocol. So please don't log bugs against "wayland".

What you are describing sounds most likely like Gnome Shell, where the
mutter component chooses Wayland or X11.

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  disable wayland by default - nvidia proprietary drivers backlight

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  With wayland can't control screen brightness using nvidia proprietary
  drivers. The screen brightness is always at 100%.

  Please DON'T enable wayland by default on fresh installations or
  updates because it's not 100% compatible with nvidia proprietary
  drivers. Nouveau still doesn't support backlight control on Pascal
  cards.

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

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

[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-03 Thread Pham Hong Nhat

What's the point of testing or providing information if no one is
willing to fix? Stop posting here, it won't change anything.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions

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

[Desktop-packages] [Bug 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog

** Changed in: gnome-control-center
   Status: Confirmed => Expired

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

Title:
  GEdit is the only choice as Calendar application in Default
  Applications dialog

Status in gnome-control-center:
  Expired
Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in desktop-file-utils source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Triaged

Bug description:
  In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog 
(System Settings -> System Information), GEdit is selected (and only possible 
choice) for Calendar items.
  I think this is not expected, since it is not so useful to open calendar data 
as standard text).

  In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta 
is installed, and I noticed the Lightning extension for Calendar is not 
compatible with it yet.
  Will Thunderbird/Lightining be possible values for Calendar applications?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 00:56:27 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago)

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

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

[Desktop-packages] [Bug 1727518] Re: Presentation mode broken with HighDPI and 200% scale