[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device

[Martina]

Having the same issue on Elementary os 0.4 Loki

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

Title:
  Unable to mount Android MTP device

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem on 3 computers with 14.04:

  So I tried,
   mtp-detect 
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
 Found 1 device(s):
 Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): Resource temporarily unavailable
  outep: usb_get_endpoint_status(): Device or resource busy
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs-backends 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 30 11:18:12 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor
  InstallationDate: Installed on 2013-02-12 (441 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Martina]

Happening on a HP- Pavilion 1540us (with Intel integrated graphics)

Using Elementary 0.4 Loki beta

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Cursor is visible at unlock screen either after returning from suspend
  or just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers

[Launchpad Bug Tracker]

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

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

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

Title:
  Duplex printing does not work properly for HP printers

Status in hplip package in Ubuntu:
  Expired

Bug description:
  I am reporting this as a new bug because I want to avoid adding
  further to the mish mash of half fixed bugs that is duplex printing on
  hp printers via cups.

  I will warn readers that this will sound like a bit of a rant. But
  these issues have been outstanding for years

  1. Take the hpcups.drv driver information from the upstream part of
  the current source package and run it throught the cups ppd compiler
  in test mode, anbd filter the output for failures.

  roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL
  roger@dragon:~/ppd-testing$

  Result a nice clean file.

  2. Take this file and run it through the script debian/local/make-
  duplex-page-sizes-default.sh that is run when this file is installed
  on a system. Then repeat the above test.

  roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL

  --- Other FAILS removed

  hp-photosmart_6510_series.ppd: FAIL
    **FAIL**  Multiple occurrences of option PageRegion choice name Card4x6.
    **FAIL**  Multiple occurrences of option PageRegion choice name Hagaki.
    **FAIL**  Multiple occurrences of option PageRegion choice name Card5x8.
    **FAIL**  Multiple occurrences of option PageRegion choice name Oufuku.
    **FAIL**  Multiple occurrences of option PageRegion choice name 
Executive.
    **FAIL**  Multiple occurrences of option PageRegion choice name A4.
    **FAIL**  Multiple occurrences of option PageSize choice name Card4x6.
    **FAIL**  Multiple occurrences of option PageSize choice name Hagaki.
    **FAIL**  Multiple occurrences of option PageSize choice name Card5x8.
    **FAIL**  Multiple occurrences of option PageSize choice name Oufuku.
    **FAIL**  Multiple occurrences of option PageSize choice name Executive.
    **FAIL**  Multiple occurrences of option PageSize choice name A4.

  --Other FAILS removed

  I have removed the many other printer types that fail for clarity. It
  is a feature of the cups ppdc compiler that if you do not specify the
  -t option it will blithely go on and produce the compiled ppds errors
  and all. I personally think that this is a bug and the compiler should
  refuse to produce erroneous ppds, but putting that to one side. Taking
  A4 as an exmaple the hp6510 ppd file now has two definitions for
  PageSize A4.

  *PageSize A4/A4 210x297mm: "<>setpagedevice"
  and
  *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice"

  Same name but different page dimensions. Only the first one will ever
  be seen by the cups system.

  3. This above often does not matter when printing from the command
  line. Because PageSize options are not often specified. However,
  taking as an example a gnome desktop application such as  Evince
  printing a pdf using the gtk+ print options with duplex printing
  selected. In this case a PageSize option will be passed to Cups and it
  will look like this.

  D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper
  number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal
  ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed-
  e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date-
  time-at-creation= date-time-at-processing= time-at-creation=1460393994
  time-at-processing=1460393994"

  So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so
  what is passed down for matching is "A4" which matches the first
  occurrence of A4. Depending on what other defaults are set in the pdd
  it might print something, but it will most likely be clipped. In the
  case of the 6510 it results in this.

  D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error:
  rangecheck in setpagedevice

  Of course the above line only appears in the error_log if you have
  debugging turned on. So the job just appears to stuck in the print
  queue for no reason at all. This is probably another bug.

  The work around. This has been mentioned many times in various bug
  reports. You need page sizes, page regions, imageable areas, and paper
  dimensions  with names ending in .Duplex in your ppd. Rename the
  duplicate which has the biggest bottom margin, hopefully this is the
  one with AutoDuplex in the descriptive text. It is probably best to
  make these entries default as well. You might make the corresponding
  changes in the drv file if you wish. That will save you having to
  reapply them every time the ppd file is regenerated.

  I realise that I have broken just about every rule in the "bug laws".
  I offer no 

[Desktop-packages] [Bug 1589550] Re: Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but doesn't switch to that VT

[Robert Ancell]

Can you try lightdm 1.19.1 / 1.18.2 and see if that solves this?

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

Title:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT

Status in Light Display Manager:
  New
Status in Mir:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT.

  The result is a black screen, as Unity8 is running but the system
  defaults to the wrong VT so it's not visible.

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

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

[Desktop-packages] [Bug 1571640] Re: lightdm changing resolution

[Robert Ancell]

And update the description here suitable for an SRU -
https://wiki.ubuntu.com/StableReleaseUpdates

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

Title:
  lightdm changing resolution

Status in unity-greeter package in Ubuntu:
  Fix Committed
Status in unity-greeter source package in Xenial:
  New
Status in unity-greeter source package in Yakkety:
  Fix Committed

Bug description:
  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1571640] Re: lightdm changing resolution

[Robert Ancell]

Kai-Heng - do you plan to SRU this to Xenial? Can you make a merge
proposal to lp:unity-greeter/16.04 if so.

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

** Also affects: unity-greeter (Ubuntu Yakkety)
   Importance: High
   Status: Fix Committed

** Also affects: unity-greeter (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  lightdm changing resolution

Status in unity-greeter package in Ubuntu:
  Fix Committed
Status in unity-greeter source package in Xenial:
  New
Status in unity-greeter source package in Yakkety:
  Fix Committed

Bug description:
  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1591980] Re: unity-greeter FTBFS on yakkety: undefined reference to `gtk_widget_set_focus_on_click'

[Robert Ancell]

** Changed in: unity-greeter (Ubuntu)
   Status: New => Fix Committed

** Changed in: unity-greeter (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity-greeter (Ubuntu)
   Importance: Critical => High

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

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

Title:
  unity-greeter FTBFS on yakkety: undefined reference to
  `gtk_widget_set_focus_on_click'

Status in unity-greeter package in Ubuntu:
  Fix Committed
Status in vala package in Ubuntu:
  New
Status in vala package in Debian:
  New

Bug description:
  This is apparently caused by vala 0.32

  https://bugs.debian.org/820641

  and will be fixed once we get GTK+ 3.20, probably later in the yakkety
  cycle. I'm filing this bug so hopefully others won't waste as much
  time trying to figure out what broke.

  unity_greeter-main-window.o: In function `main_window_constructor':
  /«PKGBUILDDIR»/src/main-window.c:1644: undefined reference to 
`gtk_widget_set_focus_on_click'
  unity_greeter-prompt-box.o: In function `prompt_box_real_create_name_grid':
  /«PKGBUILDDIR»/src/prompt-box.c:590: undefined reference to 
`gtk_widget_set_focus_on_click'
  unity_greeter-shutdown-dialog.o: In function `dialog_button_construct':
  /«PKGBUILDDIR»/src/shutdown-dialog.c:2087: undefined reference to 
`gtk_widget_set_focus_on_click'
  collect2: error: ld returned 1 exit status
  Makefile:482: recipe for target 'unity-greeter' failed
  make[4]: *** [unity-greeter] Error 1
  make[4]: Leaving directory '/«PKGBUILDDIR»/src'

  Full build log at https://launchpad.net/ubuntu/+source/unity-
  greeter/16.10.0-0ubuntu2/+build/9679540

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

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

[Desktop-packages] [Bug 648539] Re: Trash Bin icon still shows full despite trash empty of files

[Bug Watch Updater]

** Changed in: gnome-applets
   Status: New => Confirmed

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

Title:
  Trash Bin icon still shows full despite trash empty of files

Status in gnome-applets:
  Confirmed
Status in gnome-applets package in Ubuntu:
  Invalid

Bug description:
  TEST CASE: Plug in a Western Digital My Book ( Model# WDBAAF0010HBK-
  NESN ) then delete something on the HDD, empty the Trash, then right
  click the My Book Desktop icon and clicks "Safely Remove".

  WORKAROUND: Restart the computer, the full Trash Bin icon becomes an
  empty one.

  Binary package hint: gnome-applets

  1) lsb_release -rd
  Description:  Ubuntu 10.10
  Release:  10.10

  2) apt-cache policy gnome-applets
  gnome-applets:
    Installed: 2.30.0-3ubuntu3
    Candidate: 2.30.0-3ubuntu3
    Version table:
   *** 2.30.0-3ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
  100 /var/lib/dpkg/status

  3) Thank you for reading this. What is expected to happen is when one
  empties the Trash Bin file via secondary clicking Trash Bin icon,
  primary clicking Empty Trash, then primary clicking Empty Trash
  button, the icon would show it is empty.

  4) What happens instead is that the Trash Bin still shows it is full
  (please see screenshot.png). If any questions exist please ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xserver-xorg-video-radeon 1:6.13.1-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
   edid-base64: 
AP///wAGr3SBAAEQAQOAIRV4Chz1l1hQjicnUFQBAQEBAQEBAQEBAQEBAQEBxxsAoFAgFzAwIDYAS88QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU0RVcwOCBWMSAKAEM=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes:
   edid-base64:
  Date: Mon Sep 27 00:36:21 2010
  DkmsStatus: virtualbox-ose, 3.2.8, 2.6.35-22-generic, i686: installed
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  MachineType: TOSHIBA Satellite L305D
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=071b6692-65a6-47fd-8f58-d33216d1cf0e ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-ati
  dmi.bios.date: 09/01/2009
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd09/01/2009:svnTOSHIBA:pnSatelliteL305D:pvrPSLC8U-03701QB:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite L305D
  dmi.product.version: PSLC8U-03701QB
  dmi.sys.vendor: TOSHIBA
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   i686
   kernel: 2.6.35-22-generic

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

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

[Desktop-packages] [Bug 1580482] Re: Virtualbox guest additions isn't working properly in Ubuntu 16.04

[Ron Tackaberry]

"About the virtualbox-guest-dkms package, I'm not sure it is really
needed in 16.04 as xenial kernel already packs virtualbox's guest
modules(you can lsmod it even without installing the package)"

Actually, I had the same problem. Installing this package solved it.
Error gone and pasting and screen resize is now working fine.

Thanks for the help.

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

Title:
  Virtualbox guest additions isn't working properly in Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Incomplete

Bug description:
  ## Symptoms ##
  * OpenGL processing offloading is not supported(3D hardware acceleration is 
enabled in VM settings and is available on Intel Graphics host)
  * VBoxClient warns about "Failed to connect to the ViratualBox kernel 
service, rc=VERR_ACCESS_DENIED"(refer attached screenshot)

  You may checkout the screen record for what exactly this issue is about:
  https://www.youtube.com/watch?v=aB1sb3D4Q9g

  ## Workarounds ##
  Install VirtualBox provided guest additions iso from the menu works

  ## Additional Information ##
  * I uses the VirtualBox from upstream on the host side, the version is 5.0.20
  * Note that the Ubuntu Kernel bundled with 16.04 has integrated VirtualBox 
guest modules(vboxguest, vboxsf, and vboxvideo specifically) for unknown 
reason, this bug is reproduced *without* the virtualbox-guest-dkms 
package(since the Additional Drivers interface doesn't provide me the option to 
do so(the option is greyed-out, refer attached screenshot))
  * I have another 14.04 VM and it's OpenGL offloading works, so it's not 
likely that the host isn't providing proper OpenGL functionallity

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.0.18-dfsg-2build1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 11 12:08:31 2016
  InstallationDate: Installed on 2016-01-07 (124 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (33 days ago)

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

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

[Desktop-packages] [Bug 1595023] Re: Need to determine if snap apps require terminal or not

[Robert Ancell]

I was also considering if it made sense to report the graphical
backend(s) that the app would use, i.e.

"apps": [{"name": "moon-buggy", "backend"s: ["mir", "x11"]}]

But I think that most apps actually don't care / know - they use a
toolkit and have no idea what backend it uses.

** Tags added: gnome-software

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

Title:
  Need to determine if snap apps require terminal or not

Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  snapd returns a list of apps a snap contains, i.e:

  "apps": [{"name": "moon-buggy"}]

  However, we can't tell if this is a terminal app (like moon buggy) or
  a graphical app (like Ubuntu calculator).

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

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

[Desktop-packages] [Bug 1595023] Re: Need to determine if snap apps require terminal or not

[Robert Ancell]

Reading the .desktop spec [1] the key they use is "Terminal". So perhaps
this is worth matching:

"apps": [{"name": "moon-buggy", "terminal": true}]

[1] https://specifications.freedesktop.org/desktop-entry-spec/latest/

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

Title:
  Need to determine if snap apps require terminal or not

Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  snapd returns a list of apps a snap contains, i.e:

  "apps": [{"name": "moon-buggy"}]

  However, we can't tell if this is a terminal app (like moon buggy) or
  a graphical app (like Ubuntu calculator).

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

** Description changed:

  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.
  
  This SRU will restore the bare minimum of LSB compatibility necessary to
  support known third-party LSB printer driver packages on Ubuntu 16.04.
  
  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.
  
  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land before
  the first 16.04 point release.
  
  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
- 5. Verify that any executables within the package can be run without errors 
about missing lsb ld.so.
+ 5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.
  
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):
  
  lsb (9.20150826) unstable; urgency=low
  
    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's
  
   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200
  
  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:
  
  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable
  
  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.
  
  I see two possible solutions:
  
  - Add a proper replaces field to one of the remaining lsb-* packages, to
  hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).
  
  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  In Progress
Status in system-config-printer package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  In Progress
Status in system-config-printer source package in Xenial:
  Invalid

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using 

[Desktop-packages] [Bug 1593357] Re: Software app should not show command-line only snaps

[Robert Ancell]

Re-reading the desktop spec, you are correct in that we should show
launchable apps (currently determined by having .desktop files). The
desktop spec allows terminal apps with the key Terminal=true.

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

Title:
  Software app should not show command-line only snaps

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  By design, the Software app only shows "apps". I'm not sure precisely
  what standard is used but at a minimum, an "app" includes a .desktop
  file.

  This is a common complaint by users who prefer the way the Ubuntu
  Software Center worked (default before 16.04 LTS) where everything in
  the archive was installable or uninstallable via the gui. See bug
  1553211 as one example where this kind of request is more or less
  closed as WONTFIX.

  On the other hand, all snaps are currently being shown in the Software
  app, even if they are command-line apps and don't bundle a .desktop.
  For consistency, the same standard needs to be used to show snaps as
  to show classic .deb's.

  Two specific test cases I saw are Cassandra and Jenkins (which were
  "Editor's Picks" in the development snapshot I tested from
  https://launchpad.net/~attente/+archive/ubuntu/gnome-software this
  week).

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

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

[Desktop-packages] [Bug 1564076] Re: Can't launch snaps

[Robert Ancell]

I've opened bug 1595023 for the next step - determining which apps a
graphical and which are terminal.

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

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

Title:
  Can't launch snaps

Status in Snappy:
  Triaged
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Clicking the "launch" button from GNOME Software has no effect for
  snaps. This is because snapd doesn't provide any mechanism to
  determine what binaries / .desktop files a snap contains.

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

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

[Desktop-packages] [Bug 1595023] [NEW] Need to determine if snap apps require terminal or not

[Robert Ancell]

Public bug reported:

snapd returns a list of apps a snap contains, i.e:

"apps": [{"name": "moon-buggy"}]

However, we can't tell if this is a terminal app (like moon buggy) or a
graphical app (like Ubuntu calculator).

** Affects: gnome-software (Ubuntu)
 Importance: High
 Status: Triaged

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

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

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

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

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

Title:
  Need to determine if snap apps require terminal or not

Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  snapd returns a list of apps a snap contains, i.e:

  "apps": [{"name": "moon-buggy"}]

  However, we can't tell if this is a terminal app (like moon buggy) or
  a graphical app (like Ubuntu calculator).

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

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

[Desktop-packages] [Bug 1595023] Re: Need to determine if snap apps require terminal or not

[Robert Ancell]

A potential solution:

"apps": [{"name": "moon-buggy", "graphical": false}]

Not sure if this can be easily determined from the snapd metadata.

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

Title:
  Need to determine if snap apps require terminal or not

Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  snapd returns a list of apps a snap contains, i.e:

  "apps": [{"name": "moon-buggy"}]

  However, we can't tell if this is a terminal app (like moon buggy) or
  a graphical app (like Ubuntu calculator).

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

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

[Desktop-packages] [Bug 379895] Re: Trash applet sometimes shows wrong icon when is not empty in Jaunty

[Bug Watch Updater]

** Changed in: gnome-applets
   Status: New => Confirmed

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

Title:
  Trash applet sometimes shows wrong icon when is not empty in Jaunty

Status in gnome-applets:
  Confirmed
Status in Nautilus:
  Invalid
Status in gnome-applets package in Ubuntu:
  Triaged
Status in Guadalinex:
  Confirmed

Bug description:
  Binary package hint: nautilus

  Sometimes when I delete files, the trash applet continues showing a "empty 
icon" (the icon isn't modified). I don't know what causes this problem.
  The icon is shown correctly when I restart the system.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.26.2-0ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 1595020] [NEW] Unity/Launcher Z Order errors.

[Biatu]

Public bug reported:

I have been noticing issues with windows being hidden when switching
between windows. For example, When performing a File operation, the File
Operations Dialog will disappear, and will not be accessible again
through the launcher, or the window that called the dialog. The only way
to get back to the dialog is to minimize all blocking windows.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Jun 21 22:09:11 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: vboxhost, 5.0.22, 4.4.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated 
Graphics Controller [10cf:15f5]
InstallationDate: Installed on 2016-06-14 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: FUJITSU LIFEBOOK T901
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=270675e2-6b43-4607-95e4-a9036be2e5b4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.16
dmi.board.name: FJNB228
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: AOL433E312BB2002
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd06/19/2012:svnFUJITSU:pnLIFEBOOKT901:pvr:rvnFUJITSU:rnFJNB228:rvr:cvnAOL433E312BB2002:ct10:cvr:
dmi.product.name: LIFEBOOK T901
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jun 21 15:22:51 2016
xserver.configfile: default
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id2600 
 vendor BOE
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Unity/Launcher Z Order errors.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have been noticing issues with windows being hidden when switching
  between windows. For example, When performing a File operation, the
  File Operations Dialog will disappear, and will not be accessible
  again through the launcher, or the window that called the dialog. The
  only way to get back to the dialog is to minimize all blocking
  windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jun 21 22:09:11 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.22, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  

[Desktop-packages] [Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

[Andrew Skalski]

I tested by applying the patch against the current Ubuntu Xenial release
version of the metacity package (metacity_3.18.4-0ubuntu0.3).  I can
confirm the patch fixes the regression (it allows me to drag my Firefox
and Thunderbird windows above the top of the screen.)  So far, I have
encountered no new regressions.

I also tried building metacity git master, but ran into several unmet
dependencies (newer versions of gtk+/glib than what I have installed),
so I was unable to complete that test.

Thanks for looking into this!

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

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  New

Bug description:
  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect
 
  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

[Jason Pell]

Manthis, there are two workarounds available.  The nmcli definately
works, but you need to know your SSID, for instance I have a SSID for my
phone access point which I can manually connect to when I encounter this
issue:

nmcli c up id ThomasAp

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

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1587853] Re: Canon Lide 110 scanner does not work with xsane, simple scan, gscan2pdf but works with vuescan

[Satyapriyananda]

I suggest get rid off xsane, simple-scan and gscan2pdf using sudo apt
purge xsane etc.

Scanimage does a good job.

Use sane-find-scanner to find the scanner.

Use scanimage -L to find what make the scanner is.

Use scanimage -A to find which parameters go with the scanner you have.

Use SANE_DEBUG_DLL=5 scanimage -L to do a bit of debugging, if needed.

Somehow simple-scan works on some other machines with Ubuntu 16.04.


** Attachment added: "This attachment gives the output for the commands given 
above."
   
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1587853/+attachment/4688227/+files/scanner.txt

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

Title:
  Canon Lide 110 scanner does not work with xsane, simple scan,
  gscan2pdf but works with vuescan

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I have a Canon Lide 110 scanner which is detected in scanimage -L and
  sane-find-scanner. It gets stuck at the finishing end and does not
  return to the starting end with xsane, simple scan and gscan2pdf.
  However it works admirably well with vuescan. Even though the light is
  stuck at the finishing end, on starting vuescan the light returns to
  the starting end and the scanning is smooth with vuescan. The problem
  continues with xsane, simple scan and gscan2pdf, however. It seems to
  me to be a sane backend problem. I had stated this problem before and
  thought that the problem was solved. But it has not been solved.
  Please help

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

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

[Desktop-packages] [Bug 1595017] [NEW] u-wallpapers include Creative Commons v2 licenses which are controversial

[Jeremy Bicha]

Public bug reported:

The Ubuntu Wallpapers for 15.10 include Creative Commons version 2
licensed photos.

https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
wallpapers/ubuntu/revision/166

This is in contrast to what was in debian/copyright up until that point
and what I believe the guidelines say:

https://wiki.ubuntu.com/Artwork/Documentation/Backgrounds

There's good reason to have version 3 of Creative Commons by the minimum
standard.

It is widely believe in Debian that version 2 isn't good enough.
(Version 1 is definitively believed to have not been DFSG-compatible).

See

https://wiki.debian.org/DFSGLicenses#Creative_Commons_Attribution_Share-
Alike_.28CC-BY-SA.29_v4.0

And see bug 1588938 as just one example, where Debian developers
reported the issue with CC version 2 files to the GNOME developers who
replaced the images in the new release.

To summarize, Creative Commons version 2 licenses should be avoided in
Ubuntu because they are mostly avoided in Debian.

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily xenial

** Summary changed:

- u-wallpapers includes Creative Commons v2 licenses which are controversial
+ u-wallpapers include Creative Commons v2 licenses which are controversial

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

Title:
  u-wallpapers include Creative Commons v2 licenses which are
  controversial

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  The Ubuntu Wallpapers for 15.10 include Creative Commons version 2
  licensed photos.

  https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  wallpapers/ubuntu/revision/166

  This is in contrast to what was in debian/copyright up until that
  point and what I believe the guidelines say:

  https://wiki.ubuntu.com/Artwork/Documentation/Backgrounds

  There's good reason to have version 3 of Creative Commons by the
  minimum standard.

  It is widely believe in Debian that version 2 isn't good enough.
  (Version 1 is definitively believed to have not been DFSG-compatible).

  See

  https://wiki.debian.org/DFSGLicenses
  #Creative_Commons_Attribution_Share-Alike_.28CC-BY-SA.29_v4.0

  And see bug 1588938 as just one example, where Debian developers
  reported the issue with CC version 2 files to the GNOME developers who
  replaced the images in the new release.

  To summarize, Creative Commons version 2 licenses should be avoided in
  Ubuntu because they are mostly avoided in Debian.

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Arup]

Does this mean we no longer need to do the hack of using Trusty repos
for lsb? The printer driver from Epson will install without any need for
a lsb package now?

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  In Progress
Status in system-config-printer package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  In Progress
Status in system-config-printer source package in Xenial:
  Invalid

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that any executables within the package can be run without errors 
about missing lsb ld.so.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+subscriptions

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

[Desktop-packages] [Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://

[Ubuntu Foundations Team Bug Bot]

The attachment "wikipedia_applet.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-
  change for https://

Status in amarok package in Ubuntu:
  New

Bug description:
  Amaroks wikipedia applet stopped showing any information. According to
  the upstream bug report (https://bugs.kde.org/show_bug.cgi?id=349313)
  this is caused by a change in wikipedias api, which requires now a ssl
  connection. This means, that all amarok versions currently available
  on ubuntu are affected.

  The same bug report mentions a commit
  http://commits.kde.org/amarok/284342b48dc32341c3553fd2b0ee5069d75b58f9
  which (partially) fixes the issue by making it possible to enable ssl
  for the applet. It might be worth backporting if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: amarok 2:2.8.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan  8 13:25:04 2016
  InstallationDate: Installed on 2015-09-22 (107 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: amarok
  UpgradeStatus: Upgraded to xenial on 2015-10-30 (70 days ago)

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

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

[Desktop-packages] [Bug 1595006] [NEW] Error creating partition: ... You requested a partition from X to Y

[themusicgod1]

Public bug reported:

Brand new hard drive, newly formatted by gnome-disks, went to add a new
filesystem to it

> ext4+LUKS
partition size (default at 4001 GB) free space following (default at 0 GB)
erase: don't erase
name: hedy1
password: *
confirm password: *
[create]

result:
Error creating partition on /dev/sdb: Command-line `parted --align optimal 
--script "/dev/sdb" "mkpart \" \" ext2 1MiB 4000752582143b"' exited with 
non-zero exit status 1: Error: You requested a partition from 1049kB to 4001GB 
(sectors 256..976746235).
The closest location we can manage is 1049kB to 4001GB (sectors 256..976746234).
 (udisks-error-quark, 0)

Ubuntu : 15.10
gnome-disk-utility: 3.16.2-0ubuntu2

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gnome-disk-utility 3.16.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun 21 20:07:12 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-09 (713 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
SourcePackage: gnome-disk-utility
UpgradeStatus: Upgraded to wily on 2016-04-21 (61 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  Error creating partition: ... You requested a partition from X to Y

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

Bug description:
  Brand new hard drive, newly formatted by gnome-disks, went to add a
  new filesystem to it

  > ext4+LUKS
  partition size (default at 4001 GB) free space following (default at 0 GB)
  erase: don't erase
  name: hedy1
  password: *
  confirm password: *
  [create]

  result:
  Error creating partition on /dev/sdb: Command-line `parted --align optimal 
--script "/dev/sdb" "mkpart \" \" ext2 1MiB 4000752582143b"' exited with 
non-zero exit status 1: Error: You requested a partition from 1049kB to 4001GB 
(sectors 256..976746235).
  The closest location we can manage is 1049kB to 4001GB (sectors 
256..976746234).
   (udisks-error-quark, 0)

  Ubuntu : 15.10
  gnome-disk-utility: 3.16.2-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-disk-utility 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun 21 20:07:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (713 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to wily on 2016-04-21 (61 days ago)

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

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

[Desktop-packages] [Bug 220080] Re: lynx fails to start if ubuntu-docs is not installed

[Jeremy Bicha]

>From what I can see, no supported Ubuntu release ships a lynx modified
to show a Ubuntu home page by default. Therefore, this bug is fixed.

** Changed in: lynx (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  lynx fails to start if ubuntu-docs is not installed

Status in lynx package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lynx

  The text-based web browser 'lynx', in its default configuration, will
  fail to start if the ubuntu-docs package is not installed.   Often a
  server installed as a command line system will not have this package
  installed.  Attempts to start the application will produce the
  following error message after a short delay:

  Can't Access `file://localhost/usr/share/ubuntu-artwork/home/index.html'
  Alert!: Unable to access document.

  Note: The file /usr/share/ubuntu-artwork/home/index.html is a symlink
  to /etc/alternatives/firefox-homepage, which is managed by the
  alternatives system, but usually points to /usr/share/ubuntu-
  artwork/home/firefox-index.html.  This makes it difficult to debug
  this problem, since the original file is not actually supplied by any
  package, and thus is not returned by any searches on
  packages.ubuntu.com or with 'auto-apt search'.

  I suggest either making ubuntu-docs a dependency for lynx, or if
  possible, patching or reconfiguring lynx to not exit upon failing to
  load its configured homepage.

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

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

[Desktop-packages] [Bug 1595000] [NEW] /usr/bin/rhythmbox:11:emit_updated_in_idle:prop_model_row_changed_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding rhythmbox.  This problem was most recently seen with version
3.3-1ubuntu7, the problem page at
https://errors.ubuntu.com/problem/fa21dcf29605ca4feed24fa67377f1177a5314e5
contains more details.

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


** Tags: kylin-15.04 precise quantal raring saucy trusty utopic vivid wily 
xenial yakkety

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

Title:
  
/usr/bin/rhythmbox:11:emit_updated_in_idle:prop_model_row_changed_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding rhythmbox.  This problem was most recently seen with version
  3.3-1ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/fa21dcf29605ca4feed24fa67377f1177a5314e5
  contains more details.

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

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

[Desktop-packages] [Bug 1594999] [NEW] /usr/lib/gvfs/gvfsd-dav:11:certificate_to_string:gvfs_accept_certificate:do_mount:run:g_vfs_job_run

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding gvfs.  This problem was most recently seen with version
1.28.2-1ubuntu1~16.04.1, the problem page at
https://errors.ubuntu.com/problem/13e67168b6f3917caf57b9793f70d32e3b4717bc
contains more details.

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


** Tags: xenial

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

Title:
  /usr/lib/gvfs/gvfsd-
  
dav:11:certificate_to_string:gvfs_accept_certificate:do_mount:run:g_vfs_job_run

Status in gvfs package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gvfs.  This problem was most recently seen with version
  1.28.2-1ubuntu1~16.04.1, the problem page at
  https://errors.ubuntu.com/problem/13e67168b6f3917caf57b9793f70d32e3b4717bc
  contains more details.

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

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

[Desktop-packages] [Bug 1564076] Re: Can't launch snaps

[Robert Ancell]

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

Title:
  Can't launch snaps

Status in Snappy:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Clicking the "launch" button from GNOME Software has no effect for
  snaps. This is because snapd doesn't provide any mechanism to
  determine what binaries / .desktop files a snap contains.

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

** Description changed:

+ [SRU justification]
+ Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.
+ 
+ This SRU will restore the bare minimum of LSB compatibility necessary to
+ support known third-party LSB printer driver packages on Ubuntu 16.04.
+ 
+ [Regression potential]
+ The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.
+ 
+ As there are very few lsb packages in use in the wild, this is
+ considered an acceptable regression, especially as this will land before
+ the first 16.04 point release.
+ 
+ [Test case]
+ 
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):
  
  lsb (9.20150826) unstable; urgency=low
  
    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's
  
   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200
  
  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:
  
  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable
  
  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.
  
  I see two possible solutions:
  
  - Add a proper replaces field to one of the remaining lsb-* packages, to
  hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).
  
  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

** Description changed:

  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.
  
  This SRU will restore the bare minimum of LSB compatibility necessary to
  support known third-party LSB printer driver packages on Ubuntu 16.04.
  
  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.
  
  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land before
  the first 16.04 point release.
  
  [Test case]
+ 1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
+ 2. Install the package and confirm that its dependencies are not satisfiable.
+ 3. Enable xenial-proposed.
+ 4. Install the package again and confirm that the dependencies are satisfied.
+ 5. Verify that any executables within the package can be run without errors 
about missing lsb ld.so.
  
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):
  
  lsb (9.20150826) unstable; urgency=low
  
    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's
  
   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200
  
  The problem is that 

[Desktop-packages] [Bug 1594791] Re: light dm screen resolution

[Robert Ancell]

I don't know what you mean - could you attach a photo?

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

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

Title:
  light dm screen resolution

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Part of the screen is not accessible, and the upper part is huge on
  the screen. Is lightdm activated?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 21 14:25:45 2016
  InstallationDate: Installed on 2015-04-30 (418 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1589005] Re: After update DNS work unstable

[TyhDyh]

echo "network-manager hold" | sudo dpkg --set-selections

"apt update" going to show network-manager as upgradable but "apt
upgrage" going to ignore it

** Description changed:

  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.
  
  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'
  
  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal update.
  
- workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using 
+ workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
- and lock version in synaptic
+ and lock version 
+ echo "network-manager hold" | sudo dpkg --set-selections
  
+ "apt update" going to show network-manager as upgradable but "apt
+ upgrage" going to ignore it
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 

[Desktop-packages] [Bug 1594551] Re: keyfile plugin: Read /run/NetworkManager/system-connections/

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.2.2-0ubuntu5

---
network-manager (1.2.2-0ubuntu5) yakkety; urgency=medium

  * debian/tests/{network_test_base.py,nm}: Unblacklist the client test veth 
device
from NetworkManager and re-enable the three tests to auto-connect to
Ethernet interfaces.
  * Add Read-connections-from-run.patch: Read system-connections from /run.
Like with the corresponding conf.d/, files in /etc/ trump files in /run.
(LP: #1594551)

 -- Martin Pitt   Tue, 21 Jun 2016 21:49:04
+0200

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  keyfile plugin: Read /run/NetworkManager/system-connections/

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Apparently new connections cannot be added in NetworkManager.conf or
  /{etc,run}/NetworkManager/conf.d/* snippets, the [connection-*]
  sections can only modify existing connections. Thus for
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-network-
  yaml we need to write /run/NetworkManager/system-connections/ and NM's
  keyfile plugin needs to read these in addition to /etc/NetworkManager
  /system-connections/. Like with conf.d/, files in /etc/ should
  override files in /run/.

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

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

[Desktop-packages] [Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

[Alberts Muktupāvels]

https://git.gnome.org/browse/metacity/commit/?id=967eebdd5bdf378e220f3856756745ea39f7415b
Can you verify that this commit fixes regression and does not introduce new 
regressions?

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

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  New

Bug description:
  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect
 
  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1581187] Re: AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session at line 14: Could not open 'abstractions/fcitx'

[Tyler Hicks]

Thanks, Martin. I have verified that this bug is fixed in
1.19.1-0ubuntu1.

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

Title:
  AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in
  /etc/apparmor.d/lightdm-guest-session at line 14: Could not open
  'abstractions/fcitx'

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  The current yakkety lightdm version has a regression in its AppArmor
  profile:

  $ sudo systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2016-05-12 18:03:37 CEST; 3h 
17min ago
   Docs: man:systemd-sysv-generator(8)

  May 12 18:03:37 autopkgtest apparmor[493]:  * Starting AppArmor profiles
  May 12 18:03:37 autopkgtest apparmor[493]: AppArmor parser error for 
/etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session 
at line 14: Could not open 'abstractions/fcitx'
  May 12 18:03:37 autopkgtest apparmor[493]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 12 18:03:37 autopkgtest apparmor[493]: AppArmor parser error for 
/etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session 
at line 14: Could not open 'abstractions/fcitx'
  May 12 18:03:37 autopkgtest apparmor[493]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 12 18:03:37 autopkgtest apparmor[493]:...fail!
  May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Control process 
exited, code=exited status=123
  May 12 18:03:37 autopkgtest systemd[1]: Failed to start LSB: AppArmor 
initialization.
  May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Unit entered failed 
state.
  May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Failed with result 
'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 21:20:13 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://

[b3nmore]

The attached patch fixes the issue for trusty. Since there were only
minimal updates to amarok for xenial, it probably works for it too.

Its basically a backport of the following upstream commits:
http://commits.kde.org/amarok/8c15258b28870b6d9990b24f87ce913e2049bac8
http://commits.kde.org/amarok/15d68755dc5dcf549386a4d50d8a15ebfbea

** Patch added: "wikipedia_applet.patch"
   
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+attachment/4688193/+files/wikipedia_applet.patch

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

Title:
  Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-
  change for https://

Status in amarok package in Ubuntu:
  New

Bug description:
  Amaroks wikipedia applet stopped showing any information. According to
  the upstream bug report (https://bugs.kde.org/show_bug.cgi?id=349313)
  this is caused by a change in wikipedias api, which requires now a ssl
  connection. This means, that all amarok versions currently available
  on ubuntu are affected.

  The same bug report mentions a commit
  http://commits.kde.org/amarok/284342b48dc32341c3553fd2b0ee5069d75b58f9
  which (partially) fixes the issue by making it possible to enable ssl
  for the applet. It might be worth backporting if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: amarok 2:2.8.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan  8 13:25:04 2016
  InstallationDate: Installed on 2015-09-22 (107 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: amarok
  UpgradeStatus: Upgraded to xenial on 2015-10-30 (70 days ago)

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

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

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  In Progress
Status in system-config-printer package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  In Progress
Status in system-config-printer source package in Xenial:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+subscriptions

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

[Desktop-packages] [Bug 1333158] Re: scaling doesn't affect firefox and thunderbird

[Anmar Oueja]

Isn't there a firefox extension to do that automatically

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

Title:
  scaling doesn't affect firefox and thunderbird

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in ubufox package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  If you use "Scale for menu and title bars" in the Displays Tab, this
  doesn't affect Firefox.

  please add this to the Unity Desktop Integration:

  about:config in Firefox and search for 
  layout.css.devPixelsPerPx
  set this value to the same scale factor as in unity-control-center

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

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

[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume

[Henry J. Douglas]

One more thing I forgot to mention. Ubuntu (Unity) works perfectly. Any
other official flavour or distribution launched before 2016 (as this is
a new laptop) will have this issue. I couldn't find what makes Ubuntu's
network-manager work as it should yet.

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

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Desktop-packages] [Bug 1594551] Re: keyfile plugin: Read /run/NetworkManager/system-connections/

[Martin Pitt]

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  keyfile plugin: Read /run/NetworkManager/system-connections/

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Apparently new connections cannot be added in NetworkManager.conf or
  /{etc,run}/NetworkManager/conf.d/* snippets, the [connection-*]
  sections can only modify existing connections. Thus for
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-network-
  yaml we need to write /run/NetworkManager/system-connections/ and NM's
  keyfile plugin needs to read these in addition to /etc/NetworkManager
  /system-connections/. Like with conf.d/, files in /etc/ should
  override files in /run/.

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

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

[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume

[Henry J. Douglas]

Intel Wireless 3160 (iwlwifi driver), Ubuntu MATE 16.04 is still being
affected. The connection is reestablished but no wireless Access Points
are displayed (up/down arrow ethernet icon instead of wireless). It
seems that this same bug has been reported several times here and
upstream, with no relevant updates :(

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

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

** Changed in: cups-filters (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: epson-inkjet-printer-escpr (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: system-config-printer (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  In Progress
Status in system-config-printer package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  New
Status in system-config-printer source package in Xenial:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+subscriptions

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

** Also affects: lsb (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: system-config-printer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: epson-inkjet-printer-escpr (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cups-filters (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  In Progress
Status in system-config-printer package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  New
Status in epson-inkjet-printer-escpr source package in Xenial:
  New
Status in lsb source package in Xenial:
  New
Status in system-config-printer source package in Xenial:
  New

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+subscriptions

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Steve Langasek]

** Changed in: lsb (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  In Progress
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+subscriptions

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[Launchpad Bug Tracker]

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

** Changed in: trust-store (Ubuntu)
   Status: New => Confirmed

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

Title:
  audio record works for call audio

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591935/+subscriptions

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

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[Launchpad Bug Tracker]

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

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

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

Title:
  audio record works for call audio

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591935/+subscriptions

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

[Desktop-packages] [Bug 1591274] Re: cups-browsed hangs on shutdown

[Martin Pitt]

** Summary changed:

- xenial shutdown takes a looong time
+ cups-browsed hangs on shutdown

** Package changed: systemd (Ubuntu) => cups (Ubuntu)

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

Title:
  cups-browsed hangs on shutdown

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have a new XPS13, running an up-to-date 16.04.  The shutdown process
  takes ages - something is clearly getting stuck.  It eventually
  completes, but is (or seems like) several minutes.  Happy to help
  debug if you can give instructions on how to see what's stuck.

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[vernario]

** Changed in: lsb (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+subscriptions

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

[Desktop-packages] [Bug 1594953] [NEW] 47.0+build3-0ubuntu0.14.04.1 crashes on remote X11 display

[randomtasks]

Public bug reported:

Much of the time, firefox 47.0 will crash when displayed remotely. Both
local and remote PCs are Ubuntu 14.04 with all patches applied as of
today.

To reproduce, log into pc1 console then "ssh -X pc2.domain.dom" then:

>firefox -P --no-remote
[7663] ###!!! ABORT: X_ShmPutImage: BadShmSeg (invalid shared segment 
parameter); 2 requests ago: file 
/build/firefox-sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157
[7663] ###!!! ABORT: X_ShmPutImage: BadShmSeg (invalid shared segment 
parameter); 2 requests ago: file 
/build/firefox-sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157
ExceptionHandler::GenerateDump cloned child 7815
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Segmentation fault (core dumped)

This did not happen with 46.0.1+build1-0ubuntu0.14.04.3. It is stable,
confirmed with downgrade on pc2.

Tested on 3 different systems with identical results.

1) >lsb_release -rd
Description:Ubuntu 14.04.4 LTS
Release:14.04

2) >apt-cache policy firefox
firefox:
  Installed: 47.0+build3-0ubuntu0.14.04.1
  Candidate: 47.0+build3-0ubuntu0.14.04.1
  Version table:
 *** 47.0+build3-0ubuntu0.14.04.1 0

3) Firefox should launch and be relatively stable

4) Firefox crashes with one of the following errors:
[7663] ###!!! ABORT: X_ShmPutImage: BadShmSeg (invalid shared segment 
parameter); 2 requests ago: file 
/build/firefox-sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157

[15679] ###!!! ABORT: X_ShmDetach: BadShmSeg (invalid shared segment
parameter); 2 requests ago: file /build/firefox-
sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157

[15920] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private
resource denied); 3 requests ago: file /build/firefox-
sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157

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

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

Title:
  47.0+build3-0ubuntu0.14.04.1 crashes on remote X11 display

Status in firefox package in Ubuntu:
  New

Bug description:
  Much of the time, firefox 47.0 will crash when displayed remotely.
  Both local and remote PCs are Ubuntu 14.04 with all patches applied as
  of today.

  To reproduce, log into pc1 console then "ssh -X pc2.domain.dom" then:

  >firefox -P --no-remote
  [7663] ###!!! ABORT: X_ShmPutImage: BadShmSeg (invalid shared segment 
parameter); 2 requests ago: file 
/build/firefox-sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157
  [7663] ###!!! ABORT: X_ShmPutImage: BadShmSeg (invalid shared segment 
parameter); 2 requests ago: file 
/build/firefox-sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157
  ExceptionHandler::GenerateDump cloned child 7815
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Segmentation fault (core dumped)

  This did not happen with 46.0.1+build1-0ubuntu0.14.04.3. It is stable,
  confirmed with downgrade on pc2.

  Tested on 3 different systems with identical results.

  1) >lsb_release -rd
  Description:Ubuntu 14.04.4 LTS
  Release:14.04

  2) >apt-cache policy firefox
  firefox:
Installed: 47.0+build3-0ubuntu0.14.04.1
Candidate: 47.0+build3-0ubuntu0.14.04.1
Version table:
   *** 47.0+build3-0ubuntu0.14.04.1 0

  3) Firefox should launch and be relatively stable

  4) Firefox crashes with one of the following errors:
  [7663] ###!!! ABORT: X_ShmPutImage: BadShmSeg (invalid shared segment 
parameter); 2 requests ago: file 
/build/firefox-sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157

  [15679] ###!!! ABORT: X_ShmDetach: BadShmSeg (invalid shared segment
  parameter); 2 requests ago: file /build/firefox-
  sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157

  [15920] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access
  private resource denied); 3 requests ago: file /build/firefox-
  sKY334/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157

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

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

[Desktop-packages] [Bug 1573171] Re: package libreoffice-style-tango (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Felipe]

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

** Attachment removed: "AptOrdering.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1573171/+attachment/4641679/+files/AptOrdering.txt

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

Title:
  package libreoffice-style-tango (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  package libreoffice-style-tango (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-style-tango (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 21 11:06:52 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2012-03-19 (1494 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libreoffice
  Title: package libreoffice-style-tango (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1573171] Re: package libreoffice-style-tango (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

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

Title:
  package libreoffice-style-tango (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  package libreoffice-style-tango (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-style-tango (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 21 11:06:52 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2012-03-19 (1494 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libreoffice
  Title: package libreoffice-style-tango (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1591274] [NEW] cups-browsed hangs on shutdown

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have a new XPS13, running an up-to-date 16.04.  The shutdown process
takes ages - something is clearly getting stuck.  It eventually
completes, but is (or seems like) several minutes.  Happy to help debug
if you can give instructions on how to see what's stuck.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
cups-browsed hangs on shutdown
https://bugs.launchpad.net/bugs/1591274
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cups in Ubuntu.

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

[Desktop-packages] [Bug 1582359] Re: [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1582357
   [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

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

Title:
  [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem keeps recurring. Not sure if I installed some update in
  between. The headphones output goes out.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ramanathan   1582 F...m pulseaudio
   /dev/snd/controlC0:  ramanathan   1582 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 16 13:20:17 2016
  InstallationDate: Installed on 2015-03-19 (423 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ramanathan   1582 F...m pulseaudio
   /dev/snd/controlC0:  ramanathan   1582 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CA.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551CA.207:bd10/23/2013:svnASUSTeKCOMPUTERINC.:pnX551CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-26T22:21:13.321665

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1582359/+subscriptions

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

[Desktop-packages] [Bug 1582358] Re: [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1582357
   [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

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

Title:
  [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem keeps recurring. Not sure if I installed some update in
  between. The headphones output goes out.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ramanathan   1582 F...m pulseaudio
   /dev/snd/controlC0:  ramanathan   1582 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 16 13:20:17 2016
  InstallationDate: Installed on 2015-03-19 (423 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ramanathan   1582 F...m pulseaudio
   /dev/snd/controlC0:  ramanathan   1582 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [X551CA, Realtek ALC270, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CA.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551CA.207:bd10/23/2013:svnASUSTeKCOMPUTERINC.:pnX551CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-26T22:21:13.321665

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1582358/+subscriptions

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

[Desktop-packages] [Bug 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window

[Jorge Iván Rosales Méndez]

Well the tablet works with gnome 3.20, but in ubuntu the problem persist.
I didn't have the xf86-input-wacom installed in antergos :p so i thinked that 
gnome 3.20 wasn't detecting the tablet. I installed and it works!!! in Gnome 
3.20.
So the problem is only in the unity-control-center.
Sorry for the confusion.
xP

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

Title:
  Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties
  window

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

Bug description:
  The section in system configuration called "Wacom Tablet" isn't
  detecting my Wacom Intuos Art Small 2015, i'm using Ubuntu 16.04 with
  4.4 kernel, i installed the drivers of linux wacom but the issue
  continue.I expected that ubuntu will detect the tablet and the wacom
  properties setting will work.

  INFO:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

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

[Desktop-packages] [Bug 1594938] Re: [arale] Hotspot activation doesn't always work

[Tony Espy]

** Attachment added: "Screenshot of Hotspot setup dialog"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688157/+files/hotspot-spinning.png

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

Title:
  [arale] Hotspot activation doesn't always work

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Although the hotspot logic was vastly improved in OTA11, there are
  still intermittent issues with enabling hotspot on arale.

  On a freshly flashed phone running rc-proposed / 356, when I first
  attempt to setup a hotspot, when I click the "Start" button, the
  spinner shows up and the hotspot never actually starts ( see attached
  screenshot ).

  I was then able to cancel the dialog and enable hotspot via the toggle
  switch.  The correct icon was shown on the panel, and the hotspot was
  visible from other devices.

  Note, the only change I made to the configuration was to change the
  default password to "12345678" ( the minimum length WPA-PSK passphrase
  ).

  Here's my image details:

  current build number: 356
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-06-21 14:39:34
  version version: 356
  version ubuntu: 20160621
  version device: 20160526-af18709
  version custom: 20160504-975-19-6

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions

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

[Desktop-packages] [Bug 1594938] Re: [arale] Hotspot activation doesn't always work

[Tony Espy]

** Attachment added: "indicator-network log file from arale after start failed"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688158/+files/indicator-network.log

** Also affects: canonical-devices-system-image
   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/1594938

Title:
  [arale] Hotspot activation doesn't always work

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Although the hotspot logic was vastly improved in OTA11, there are
  still intermittent issues with enabling hotspot on arale.

  On a freshly flashed phone running rc-proposed / 356, when I first
  attempt to setup a hotspot, when I click the "Start" button, the
  spinner shows up and the hotspot never actually starts ( see attached
  screenshot ).

  I was then able to cancel the dialog and enable hotspot via the toggle
  switch.  The correct icon was shown on the panel, and the hotspot was
  visible from other devices.

  Note, the only change I made to the configuration was to change the
  default password to "12345678" ( the minimum length WPA-PSK passphrase
  ).

  Here's my image details:

  current build number: 356
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-06-21 14:39:34
  version version: 356
  version ubuntu: 20160621
  version device: 20160526-af18709
  version custom: 20160504-975-19-6

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions

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

[Desktop-packages] [Bug 1594938] [NEW] [arale] Hotspot activation doesn't always work

[Tony Espy]

Public bug reported:

Although the hotspot logic was vastly improved in OTA11, there are still
intermittent issues with enabling hotspot on arale.

On a freshly flashed phone running rc-proposed / 356, when I first
attempt to setup a hotspot, when I click the "Start" button, the spinner
shows up and the hotspot never actually starts ( see attached screenshot
).

I was then able to cancel the dialog and enable hotspot via the toggle
switch.  The correct icon was shown on the panel, and the hotspot was
visible from other devices.

Note, the only change I made to the configuration was to change the
default password to "12345678" ( the minimum length WPA-PSK passphrase
).

Here's my image details:

current build number: 356
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2016-06-21 14:39:34
version version: 356
version ubuntu: 20160621
version device: 20160526-af18709
version custom: 20160504-975-19-6

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

Title:
  [arale] Hotspot activation doesn't always work

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Although the hotspot logic was vastly improved in OTA11, there are
  still intermittent issues with enabling hotspot on arale.

  On a freshly flashed phone running rc-proposed / 356, when I first
  attempt to setup a hotspot, when I click the "Start" button, the
  spinner shows up and the hotspot never actually starts ( see attached
  screenshot ).

  I was then able to cancel the dialog and enable hotspot via the toggle
  switch.  The correct icon was shown on the panel, and the hotspot was
  visible from other devices.

  Note, the only change I made to the configuration was to change the
  default password to "12345678" ( the minimum length WPA-PSK passphrase
  ).

  Here's my image details:

  current build number: 356
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-06-21 14:39:34
  version version: 356
  version ubuntu: 20160621
  version device: 20160526-af18709
  version custom: 20160504-975-19-6

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions

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

[Desktop-packages] [Bug 1594934] [NEW] lost my logout and shoutdown icons

[Benjamin]

Public bug reported:

I lost the showdown button and the logout is not working.

what can I do to fix it.

Is there a way to reset the system without reinstalling?

Thanks.

Benjamin

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jun 21 11:36:46 2016
DistUpgraded: 2016-05-25 07:19:08,650 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:1444]
InstallationDate: Installed on 2016-03-17 (95 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Hewlett-Packard Presario CQ62 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5c07a458-8b31-4f33-8e50-b7ba8608802b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-05-25 (27 days ago)
dmi.bios.date: 05/20/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1444
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 69.16
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd05/20/2010:svnHewlett-Packard:pnPresarioCQ62NotebookPC:pvr0496122428102:rvnHewlett-Packard:rn1444:rvr69.16:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario CQ62 Notebook PC
dmi.product.version: 0496122428102
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jun 21 09:16:56 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  lost my logout and shoutdown icons

Status in xorg package in Ubuntu:
  New

Bug description:
  I lost the showdown button and the logout is not working.

  what can I do to fix it.

  Is there a way to reset the system without reinstalling?

  Thanks.

  Benjamin

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jun 21 11:36:46 2016
  DistUpgraded: 2016-05-25 07:19:08,650 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:1444]
  InstallationDate: Installed on 2016-03-17 (95 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard Presario CQ62 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, 

[Desktop-packages] [Bug 838543] Re: False battery warning +suspend

[Launchpad Bug Tracker]

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

** Changed in: gnome-settings-daemon (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  False battery warning +suspend

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Trusty:
  Confirmed
Status in linux source package in Trusty:
  Fix Released

Bug description:
  I pulled the plug on my laptop with it's battery full:

  ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state
  present: yes
  capacity state:  ok
  charging state:  charged
  present rate:0 mA
  remaining capacity:  7200 mAh
  present voltage: 11100 mV
  ubuntu@ubuntu:~$ ubuntu-bug -w
  ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info
  present: yes
  design capacity: 7200 mAh
  [...]

  And suddenly got a dialog saying that it was critically low (while the
  icon top-left appears, properly, as full) and the laptop did suspend
  shortly after that.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.5-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CasperVersion: 1.280
  Date: Thu Sep  1 02:26:17 2011
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831)
  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-settings-daemon/+bug/838543/+subscriptions

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

[Desktop-packages] [Bug 838543] Re: False battery warning +suspend

[RockTeam]

Linux 3.13.0-88-generic #135-Ubuntu SMP Wed Jun 8 21:10:42 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

With the shown above kernel version this bug is still seen. It doesn't
looks to be solved. Could you comment please?

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

Title:
  False battery warning +suspend

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Trusty:
  Confirmed
Status in linux source package in Trusty:
  Fix Released

Bug description:
  I pulled the plug on my laptop with it's battery full:

  ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state
  present: yes
  capacity state:  ok
  charging state:  charged
  present rate:0 mA
  remaining capacity:  7200 mAh
  present voltage: 11100 mV
  ubuntu@ubuntu:~$ ubuntu-bug -w
  ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info
  present: yes
  design capacity: 7200 mAh
  [...]

  And suddenly got a dialog saying that it was critically low (while the
  icon top-left appears, properly, as full) and the laptop did suspend
  shortly after that.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.5-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CasperVersion: 1.280
  Date: Thu Sep  1 02:26:17 2011
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831)
  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-settings-daemon/+bug/838543/+subscriptions

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

[Desktop-packages] [Bug 1565975] Re: scanning sometimes impossible with LIDE 210

[Dmitry]

Lide 220 doesn't work too. https://bugs.launchpad.net/ubuntu/+source
/sane-backends/+bug/1588878

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

Title:
  scanning sometimes impossible with LIDE 210

Status in sane-backends package in Ubuntu:
  New

Bug description:
  If I try to scan with xsane or skanlite there is often an error
  message like "Error during device I/O". If that error message appears,
  I have to replug the scanner to make it working again. There are
  several symptom which are not always the same: Sometimes only preview
  doesn't work, sometimes scanning doesn't work. Sometimes scanning with
  75 dpi / color results in a corrupted image with vertical coloured
  lines while scanning the same text printout with 600 dpi results in a
  normal output. Often the scanner is very noisy compared to the sound I
  am used to from scanning with the trusty release.

  Using the amd64 version on the same machine works, but the scanner is
  quite noisy compared to the sound I am used to from the trusty
  release.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libsane 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: KDE
  Date: Mon Apr  4 21:43:22 2016
  InstallationDate: Installed on 2016-04-04 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160404)
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1587853] Re: Canon Lide 110 scanner does not work with xsane, simple scan, gscan2pdf but works with vuescan

[Dmitry]

Lide 220 doesn't work too. https://bugs.launchpad.net/ubuntu/+source
/sane-backends/+bug/1588878 . It used to work in 14.04.

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

Title:
  Canon Lide 110 scanner does not work with xsane, simple scan,
  gscan2pdf but works with vuescan

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I have a Canon Lide 110 scanner which is detected in scanimage -L and
  sane-find-scanner. It gets stuck at the finishing end and does not
  return to the starting end with xsane, simple scan and gscan2pdf.
  However it works admirably well with vuescan. Even though the light is
  stuck at the finishing end, on starting vuescan the light returns to
  the starting end and the scanning is smooth with vuescan. The problem
  continues with xsane, simple scan and gscan2pdf, however. It seems to
  me to be a sane backend problem. I had stated this problem before and
  thought that the problem was solved. But it has not been solved.
  Please help

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

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

[Desktop-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

[Benjamin Gemmill]

The xorg folks are aware of this too:
https://bugs.freedesktop.org/show_bug.cgi?id=94987


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

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=94987
   Importance: Unknown
   Status: Unknown

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 269441] Re: Trash always full

[Alberts Muktupāvels]

** Package changed: gnome-applets (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  Trash always full

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/269441/+subscriptions

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

[Desktop-packages] [Bug 1594907] Re: /usr/bin/file-roller:11:strlen:move_files_in_chunks:_fr_command_extract:_fr_command_extract_to_local:_fr_window_archive_extract_from_edata

[Sebastien Bacher]

Yeah, it's likely the same but trusty has been out for longer and has
more users, in any case it's a rather low number of report compared to
other issues

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Low

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

Title:
  /usr/bin/file-
  
roller:11:strlen:move_files_in_chunks:_fr_command_extract:_fr_command_extract_to_local:_fr_window_archive_extract_from_edata

Status in file-roller package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding file-roller.  This problem was most recently seen with
  version 3.16.5-0ubuntu1.1, the problem page at
  https://errors.ubuntu.com/problem/a595b32f105a3f7cb708c518855658d3e48eea2c
  contains more details.

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

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

[Desktop-packages] [Bug 1594907] Re: /usr/bin/file-roller:11:strlen:move_files_in_chunks:_fr_command_extract:_fr_command_extract_to_local:_fr_window_archive_extract_from_edata

[Brian Murray]

This seems to be much more common in Trusty, than in Xenial but might
still be worth having a look at.

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

Title:
  /usr/bin/file-
  
roller:11:strlen:move_files_in_chunks:_fr_command_extract:_fr_command_extract_to_local:_fr_window_archive_extract_from_edata

Status in file-roller package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding file-roller.  This problem was most recently seen with
  version 3.16.5-0ubuntu1.1, the problem page at
  https://errors.ubuntu.com/problem/a595b32f105a3f7cb708c518855658d3e48eea2c
  contains more details.

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

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

[Desktop-packages] [Bug 1594907] [NEW] /usr/bin/file-roller:11:strlen:move_files_in_chunks:_fr_command_extract:_fr_command_extract_to_local:_fr_window_archive_extract_from_edata

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding file-roller.  This problem was most recently seen with version
3.16.5-0ubuntu1.1, the problem page at
https://errors.ubuntu.com/problem/a595b32f105a3f7cb708c518855658d3e48eea2c
contains more details.

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


** Tags: trusty utopic vivid wily xenial

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

Title:
  /usr/bin/file-
  
roller:11:strlen:move_files_in_chunks:_fr_command_extract:_fr_command_extract_to_local:_fr_window_archive_extract_from_edata

Status in file-roller package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding file-roller.  This problem was most recently seen with
  version 3.16.5-0ubuntu1.1, the problem page at
  https://errors.ubuntu.com/problem/a595b32f105a3f7cb708c518855658d3e48eea2c
  contains more details.

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

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

[Desktop-packages] [Bug 1519120] Re: Xenial: VLAN interfaces don't work until after a reboot

[Wesley Wiedenmeier]

Since it looks like network-manager needs to pull in 'vlan' by default,
here is a debdiff that adds it to recommends.

It may make sense to write a patch that grays out menu entries for
network types which do not have the required deps installed, but this
may have to wait until later.

** Patch added: "add_vlan.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1519120/+attachment/4688034/+files/add_vlan.debdiff

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

Title:
  Xenial: VLAN interfaces don't work until after a reboot

Status in network-manager package in Ubuntu:
  Confirmed
Status in vlan package in Ubuntu:
  Invalid

Bug description:
  I tried to use the network manager UI to define a VLAN interface, and
  nothing happened. There are a few bugs here:

  (1) When creating a VLAN interface through the UI, the "vlan interface
  name" must be filled in. This should just default to ., rather than being a required field. (I typed in "vlan100"
  to get the "Save" button to activate.)

  (2) After creating my VLAN interface, nothing happened. No new
  interface appeared. I then realized that I had not installed the
  "vlan" package, and assumed that NetworkManager therefore could not
  complete configuration of the interface.

  (3) After installing the 'vlan' package (and then telling
  NetworkManager to disconnect and reconnect my Ethernet interface from
  the UI, just for good measure), still no VLAN interfaces were present
  on my system.

  I also tried editing the VLAN interface in the UI, and specifying
  "enp4s0f1.100", but still no VLAN interface came online.

  # apt-cache policy network-manager
  network-manager:
Installed: 1.0.4-0ubuntu6
Candidate: 1.0.4-0ubuntu6
Version table:
   *** 1.0.4-0ubuntu6 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy vlan
  vlan:
Installed: 1.9-3.2ubuntu1
Candidate: 1.9-3.2ubuntu1
Version table:
   *** 1.9-3.2ubuntu1 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1554895] Re: Erratic mouse behaviour

[Theo]

Another observation: When the laptop goes to sleep mode this happens
100% after you open the lid.

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

Title:
  Erratic mouse behaviour

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 14.04 on a Lenovo Yoga 2 13 and, after a few
  minutes of working, the mouse pointer goes crazy. It goes to the
  bottom right corner of the screen and flickers, clicking stuff
  randomly.

  * Adding a USB mouse and deactivating the trackpad makes no difference.
  * Tried Kubuntu 15.10, problem still there.
  * Tried suggestions in 

  http://ubuntuforums.org/showthread.php?t=2235704
  
http://ubuntuforums.org/showthread.php?t=2229831=2=13451930#post13451930

  without success also.

  As mentioned by other users, my laptop is currently unusable. I do not
  want to switch to Windows but, given the current hardware I have, I do
  not see how I can resolve this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  9 01:44:53 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-03-07 (2 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2016-05-19 (24 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 20344
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jun 12 23:26:25 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1069 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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

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

[Desktop-packages] [Bug 1554895] Re: Erratic mouse behaviour

[Theo]

Another observation: When the laptop goes to sleep mode this happens
100% after the laptop wakes up.

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

Title:
  Erratic mouse behaviour

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 14.04 on a Lenovo Yoga 2 13 and, after a few
  minutes of working, the mouse pointer goes crazy. It goes to the
  bottom right corner of the screen and flickers, clicking stuff
  randomly.

  * Adding a USB mouse and deactivating the trackpad makes no difference.
  * Tried Kubuntu 15.10, problem still there.
  * Tried suggestions in 

  http://ubuntuforums.org/showthread.php?t=2235704
  
http://ubuntuforums.org/showthread.php?t=2229831=2=13451930#post13451930

  without success also.

  As mentioned by other users, my laptop is currently unusable. I do not
  want to switch to Windows but, given the current hardware I have, I do
  not see how I can resolve this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  9 01:44:53 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-03-07 (2 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2016-05-19 (24 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 20344
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jun 12 23:26:25 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1069 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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

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

[Desktop-packages] [Bug 1592382] Re: Updates are notified even when they are installed automatically

[Alberto Salvia Novella]

I will test this for a week, and if the message doesn't show up then I
will make a comment here.

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Alberto Salvia Novella (es20490446e)

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Alberto Salvia Novella (es20490446e)

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

** Changed in: gnome-software (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: hundredpapercuts
   Status: Fix Released => In Progress

** Changed in: hundredpapercuts
 Assignee: (unassigned) => Alberto Salvia Novella (es20490446e)

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

Title:
  Updates are notified even when they are installed automatically

Status in One Hundred Papercuts:
  In Progress
Status in gnome-software package in Ubuntu:
  In Progress
Status in gnome-software source package in Xenial:
  In Progress

Bug description:
  HOW TO REPRODUCE:
  1. Go to the "Software & Updates" application.
  2. Go to the "Updates" tab.
  3. Set the "automatically check for updates" option to "daily".
  4. Set the "when there are security updates" option to "download and install 
automatically".
  5. Set the "when there are other updates" option to "display weekly".

  RESULT:
  In a day there will be a bubble notification telling you there are important 
updates ready to be installed, but those are set to be installed automatically 
and the Update Manager won't show up.

  RELEVANT DETAILS:
  - The bubble can show up multiple times during the same user session.
  - The bubble seems to belong to gnome-software, where the Software Updater 
should be the only application asking the user to upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: update-notifier 3.168
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 14 13:40:02 2016
  InstallationDate: Installed on 2016-05-02 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: update-notifier
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1593387] Re: Overlapping unicode characters with Cantarell font in Firefox 47

[Aldo Nogueira]

Probably related to this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=643364

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

** Also affects: fonts-cantarell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Overlapping unicode characters with Cantarell font in Firefox 47

Status in firefox package in Ubuntu:
  New
Status in fonts-cantarell package in Ubuntu:
  New

Bug description:
  Certain Portuguese words like "Atualizações" or "Preferências" (meaning 
Updates and Preferences) are shown with the characters "õe" and "ên" 
overlapping, as they were only one character.
  To reproduce this bug we need Firefox 47 and Cantarell regular as UI font.
  My system is a Ubuntu 16.04 which was "converted" to Ubuntu Gnome installing 
ubuntu-gnome-desktop package.
  I remember everything was fine with Firefox 46.
  Switching the UI font to Ubuntu regular fixes the problem as well.
  Other applications work fine: gtk2, gtk3, qt...

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

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

[Desktop-packages] [Bug 235128] Re: apt:// should be supported in Epiphany

[Goyo]

This was fixed a long time ago.

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

Title:
  apt:// should be supported in Epiphany

Status in apturl:
  Invalid
Status in apturl package in Ubuntu:
  Triaged
Status in epiphany-browser package in Ubuntu:
  In Progress

Bug description:
  apt:// links do not seem to work in epiphany-browser

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

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

[Desktop-packages] [Bug 1581560] Re: system crash when attaching external display

[Rob Latham]

I tried an upstream kernel ( 4.4.12-040412-generic #201606011712 ).
Attaching after suspend/resume no longer results in a crash.

The screen frequently fails to restore on the first try.  dmesg has
these lines in that case:

[drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
[drm] GPU HANG: ecode 8:-1:0x, reason: Kicking stuck wait on blitter 
ring, action: continue
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun

But, in an improvement from the Ubuntu kernel, I can unplug and try
again with success.

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

Title:
  system crash when attaching external display

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
  and reboots when I attach an external display.

  Process: 
  -  put laptop to sleep.
  - come into work the next day
  - open up laptop
  - plug in external display
  - observe bug

  Expected behavior: I can attach the external display
  Observed behavior: system shows black screen on both laptop and display and 
after a minute or two reboots.  Laptop drives external display fine after 
reboot.

  I ssh to the laptop from another machine and monitored
  /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors.  All I
  see in those files before the lockup is this, from Xorg.0.log:

  [ 34289.447] (II) intel(0): Enabled output DP1-8
  [ 34289.448] (II) intel(0): Enabled output DP1-1
  [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440
  [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 
0,
  (0, 0), rotation normal, reflection none

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 09:24:07 2016
  DistUpgraded: 2016-04-21 20:51:13,846 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: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2015-09-10 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BS0031US
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BS0031US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BS0031US
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  drirc:
   
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
 

[Desktop-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

[Vasya Pupkin]

joakimk...@gmail.com posted a real workaround on chromium bug tracker:

===
sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf 

Paste this:

Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "AccelMethod" "uxa"
EndSection

Save and reboot.
===

This works for me.

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1591426] Re: LCD remains off once it is turned off for power saving

[Alex Mayorga]

** Summary changed:

- LCD remains off once it is turned of fo power saving
+ LCD remains off once it is turned off for power saving

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

Title:
  LCD remains off once it is turned off for power saving

Status in xorg package in Ubuntu:
  New

Bug description:
  ¡Hola!

  LCD stays off on Dell Inspiron 1501.

  See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/596269

  ¡Gracias!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun 10 20:58:06 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
 Subsystem: Dell RS482M [Mobility Radeon Xpress 200] [1028:01f5]
  InstallationDate: Installed on 2013-01-01 (1256 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Dell Inc. Inspiron 1501
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b42f093d-7eba-4e2b-9df4-7e0a29917796 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 1501
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1593805] Re: libsignon-glib fail to authenticate account

[David Barth]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

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

Title:
  libsignon-glib fail to authenticate account

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in webapps-sprint:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress

Bug description:
  While using syncevolution to sync multiple calendars, we noticed that
  some accounts are failing to authenticate.

  The error returned by 'libsignon-glib' shows the dbus process as
  service name, what is different from the app requested.

  Check syslog attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593805/+subscriptions

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

[Desktop-packages] [Bug 1594857] [NEW] LO Base ORB Report crashes on conditional formatting

[Fred Saunier]

Public bug reported:

After updating to LO 5.1.3.2 on Ubuntu Trusty and Xenial, Base Reports
(built with ORB) crash when trying to apply conditional formatting to a
field. LO Base is connected to MySQL in MySQL native mode. To reproduce:

1. open/create a report
2. select a field
3. Format - Conditional formatting
4. Create a condition, select a format (bold, color, italics, whatever)
5. Apply

A message box pops-up with "std::bad_cast" and the whole of LO Base
crashes.

Existing reports containing conditional formatting created before the
update to LO 5.1.3.2 do run properly, with fields being conditionally
applied. However, when trying to edit these and modify their conditional
formatting, the same bug happens and LO Base crashes.

I originally reported the bug to the Document Foundation
(https://bugs.documentfoundation.org/show_bug.cgi?id=100303), they
cannot reproduce the bug. Hence my thinking this could be specific to
our distro.

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

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

Title:
  LO Base ORB Report crashes on conditional formatting

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After updating to LO 5.1.3.2 on Ubuntu Trusty and Xenial, Base Reports
  (built with ORB) crash when trying to apply conditional formatting to
  a field. LO Base is connected to MySQL in MySQL native mode. To
  reproduce:

  1. open/create a report
  2. select a field
  3. Format - Conditional formatting
  4. Create a condition, select a format (bold, color, italics, whatever)
  5. Apply

  A message box pops-up with "std::bad_cast" and the whole of LO Base
  crashes.

  Existing reports containing conditional formatting created before the
  update to LO 5.1.3.2 do run properly, with fields being conditionally
  applied. However, when trying to edit these and modify their
  conditional formatting, the same bug happens and LO Base crashes.

  I originally reported the bug to the Document Foundation
  (https://bugs.documentfoundation.org/show_bug.cgi?id=100303), they
  cannot reproduce the bug. Hence my thinking this could be specific to
  our distro.

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

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

[Desktop-packages] [Bug 1594854] Re: Touchscreen not responding to touch - only mouse input

[TenLeftFingers]

Works with stylus pen - not finger. Marking as invalid.

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

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

Title:
  Touchscreen not responding to touch - only mouse input

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I thought this report (comment #8 specifically, which describes the
  fix) would fix the issue but in my case the udev rule is not
  misplaced.

  Expected: Touching the screen should be interpreted like a mouse and affect 
the pointer
  Actual:   Touching has no effect, as if the screen is not touch screen.

  HP EliteBook 2760p

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jun 21 15:57:18 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:162a]
  InstallationDate: Installed on 2016-06-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 2760p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=1813374c-c2eb-4bc3-b409-527ac14e9f41 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SOU Ver. F.40
  dmi.board.name: 162A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 05.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SOUVer.F.40:bd03/13/2013:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005E02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.39:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2760p
  dmi.product.version: A0005E02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jun 21 15:44:30 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2208 
   vendor BOE
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Desktop-packages] [Bug 1594854] [NEW] Touchscreen not responding to touch - only mouse input

[TenLeftFingers]

Public bug reported:

I thought this report (comment #8 specifically, which describes the fix)
would fix the issue but in my case the udev rule is not misplaced.

Expected: Touching the screen should be interpreted like a mouse and affect the 
pointer
Actual:   Touching has no effect, as if the screen is not touch screen.

HP EliteBook 2760p

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Jun 21 15:57:18 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:162a]
InstallationDate: Installed on 2016-06-21 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 2760p
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=1813374c-c2eb-4bc3-b409-527ac14e9f41 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SOU Ver. F.40
dmi.board.name: 162A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 05.39
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SOUVer.F.40:bd03/13/2013:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005E02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.39:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 2760p
dmi.product.version: A0005E02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jun 21 15:44:30 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id2208 
 vendor BOE
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Touchscreen not responding to touch - only mouse input

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I thought this report (comment #8 specifically, which describes the
  fix) would fix the issue but in my case the udev rule is not
  misplaced.

  Expected: Touching the screen should be interpreted like a mouse and affect 
the pointer
  Actual:   Touching has no effect, as if the screen is not touch screen.

  HP EliteBook 2760p

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jun 21 15:57:18 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:162a]
  InstallationDate: Installed on 2016-06-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP 

[Desktop-packages] [Bug 1594846] [NEW] libxp not part of 16.04 xenial

[Martyn Brake]

Public bug reported:

A number of packages (in this case IDL -
http://www.exelisvis.co.uk/ProductsServices/IDL.aspx) need to have
libxp6 and libxp-dev to run. I believe that there are a load of other
programs that will depend upon it. Add it to apt and all will be happy.

Thanks,
Martyn

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

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

Title:
  libxp not part of 16.04 xenial

Status in libxp package in Ubuntu:
  New

Bug description:
  A number of packages (in this case IDL -
  http://www.exelisvis.co.uk/ProductsServices/IDL.aspx) need to have
  libxp6 and libxp-dev to run. I believe that there are a load of other
  programs that will depend upon it. Add it to apt and all will be
  happy.

  Thanks,
  Martyn

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

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

[Desktop-packages] [Bug 1592382] Re: Updates are notified even when they are installed automatically

[Alberto Salvia Novella]

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

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

Title:
  Updates are notified even when they are installed automatically

Status in One Hundred Papercuts:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed

Bug description:
  HOW TO REPRODUCE:
  1. Go to the "Software & Updates" application.
  2. Go to the "Updates" tab.
  3. Set the "automatically check for updates" option to "daily".
  4. Set the "when there are security updates" option to "download and install 
automatically".
  5. Set the "when there are other updates" option to "display weekly".

  RESULT:
  In a day there will be a bubble notification telling you there are important 
updates ready to be installed, but those are set to be installed automatically 
and the Update Manager won't show up.

  RELEVANT DETAILS:
  - The bubble can show up multiple times during the same user session.
  - The bubble seems to belong to gnome-software, where the Software Updater 
should be the only application asking the user to upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: update-notifier 3.168
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 14 13:40:02 2016
  InstallationDate: Installed on 2016-05-02 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: update-notifier
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Bob Dooby]

Thanks aroundworker for the i3lock tip in #103. This fixed the mouse
issue in Xubuntu 16.04. It also resolved an issue with RDP breaking in
VirtualBox when the screen was locked.

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Cursor is visible at unlock screen either after returning from suspend
  or just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1594551] Re: keyfile plugin: Read /run/NetworkManager/system-connections/

[Martin Pitt]

** Changed in: network-manager (Ubuntu)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-16.06

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

Title:
  keyfile plugin: Read /run/NetworkManager/system-connections/

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Apparently new connections cannot be added in NetworkManager.conf or
  /{etc,run}/NetworkManager/conf.d/* snippets, the [connection-*]
  sections can only modify existing connections. Thus for
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-network-
  yaml we need to write /run/NetworkManager/system-connections/ and NM's
  keyfile plugin needs to read these in addition to /etc/NetworkManager
  /system-connections/. Like with conf.d/, files in /etc/ should
  override files in /run/.

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

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

[Desktop-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Willy Schott]

I can confirm that this issue still exists in Ubuntu 16.04 LTS.

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1594681] Re: Don't set ibus variables from gnome-session

[Gunnar Hjalmarsson]

Well, I tested the attached patch, but it didn't make a difference -
those two variables are still set to "ibus". What else can it be?

OTOH I could successfully type Mozc in gedit using fcitx. Can it be
because the GTK_IM_MODULE variable was set to fcitx (by im-config)
without being overridden by something else?

In any case, there seems to be more into it to make Ubuntu GNOME safely
ready for users who prefer other IM frameworks but ibus.

** Patch added: "gnome-session_no-ibus-vars.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1594681/+attachment/4687934/+files/gnome-session_no-ibus-vars.patch

** Tags added: patch

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

Title:
  Don't set ibus variables from gnome-session

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

Bug description:
  Currently these variable settings are hardcoded in gnome-session:

  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  That way the use of alternative IM frameworks, for instance fcitx, is
  prevented. gnome-session should drop those variable assignments, and
  rely on im-config instead.

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

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

[Desktop-packages] [Bug 1594814] [NEW] NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34"

[Set Hallstrom]

Public bug reported:

I get this error in my log a lot:
"Jun 21 15:04:00 basspistol NetworkManager[834]:   [1466514240.9769] 
(wlan0): error getting signal strength: No such device"

My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is
getting a very funky name: "wlxc46e1f1abe34". It's not too much of a
problem since the connection is established and working, but it renders
the wifi-strength icon as if it was receiving maximum signal strength.

Restarting the network-manager with: "sudo systemctl restart network-
manager.service" solves the problem.

Not sure if it is related, but i am also affected by this bug:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 
1.2.0-0ubuntu0.16.04.3) on 2016-06-19

Let me know if there is any complementary information i can provide.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10
Uname: Linux 4.4.0-24-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jun 21 15:04:46 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-21 (60 days ago)
InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
IpRoute:
 default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600
 10.42.0.0/24 dev wlxc46e1f1abe34  proto kernel  scope link  src 10.42.0.22  
metric 600
 169.254.0.0/16 dev wlxc46e1f1abe34  scope link  metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:

SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
 wlxc46e1f1abe34  wifi  connected
/org/freedesktop/NetworkManager/Devices/0  sakrecoer 1  
7bfae379-b282-4335-8bfe-f1f55229ad51  
/org/freedesktop/NetworkManager/ActiveConnection/0
 enp3s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
 lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug xenial

** Description changed:

- I get this error in my log a lot: 
+ I get this error in my log a lot:
  "Jun 21 15:04:00 basspistol NetworkManager[834]:   [1466514240.9769] 
(wlan0): error getting signal strength: No such device"
  
- My wireless device (TP-Link 150Mnps Wireless N Nano USB Adapter) is
+ My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is
  getting a very funky name: "wlxc46e1f1abe34". It's not too much of a
  problem since the connection is established and working, but it renders
- the wife-strength icon as if it was receiving maximum signal strength.
+ the wifi-strength icon as if it was receiving maximum signal strength.
  
  Restarting the network-manager with: "sudo systemctl restart network-
  manager.service" solves the problem.
  
- Not sure if it is related, but i am also affected by this bug: 
+ Not sure if it is related, but i am also affected by this bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
  Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 
1.2.0-0ubuntu0.16.04.3) on 2016-06-19
  
  Let me know if there is any complementary information i can provide.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10
  Uname: Linux 4.4.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 21 15:04:46 2016
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2016-04-21 (60 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
-  default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600 
-  10.42.0.0/24 dev wlxc46e1f1abe34  proto kernel  scope link  src 10.42.0.22  
metric 600 
-  169.254.0.0/16 dev wlxc46e1f1abe34  scope link  metric 1000
+  default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600

[Desktop-packages] [Bug 817326] Re: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync

[Angel Garcia]

However I also have to discard hardware problems or even viruses, no
matter how improbable be.

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

Title:
  [Upstream] Previously-saved LibreOffice document lost by power outage
  (became 0 bytes long) - LibreOffice should call fsync

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  I was working on a document in LibreOffice today while my battery was
  low and so I was frequently saving, which I thought would help me if I
  lost power. However, when I eventually did lose power and later
  rebooted, the document had become 0 bytes long. LibreOffice was not
  able to restore the auto-saved copy either. As a result, I have lost a
  whole week of notes for one of my courses.

  After researching online, it seems that this is caused by the
  application not calling fsync() (or fdatasync()) when saving files.
  Due to delayed allocation in modern filesystems, there is no guarantee
  that the new file's data has actually been written to disk unless the
  application calls fsync. So if an app writes a new file and replaces
  the old one with it without fsync'ing the new one first then there is
  a window of opportunity during which a power failure will result in
  the loss of BOTH versions of the file. In ext4 this window is also
  much larger than in ext3.

  Theodore Tso blogged about this at http://ldn.linuxfoundation.org
  /blog-entry/delayed-allocation-and-zero-length-file-problem and
  http://www.linuxfoundation.org/news-
  media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly
  recommends to call fsync in this situation.

  Please update LibreOffice to fsync() saved files so that other users
  do not lose their data like I did.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Wed Jul 27 21:37:02 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/817326/+subscriptions

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

[Desktop-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

[Manthis]

Unable to connect to any hidden network on Ubuntu 16.04. Workaround does
not work either.

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

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1594407] Re: [SRU] New stable release 1.8.2

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-base1.0 - 1.8.2-1ubuntu1

---
gst-plugins-base1.0 (1.8.2-1ubuntu1) yakkety; urgency=medium

  * Merge from Debian unstable (LP: #1594407). Remaining changes:
+ 0001-riff-Add-input-buffer-size-to-GstCaps.patch: Take patch from
  Alfonso Sanchez-Beato on upstream bug #737599 to add a field in the
  GstCaps containing the suggested buffer size for this stream.
+ Update Vcs-* for Ubuntu

gst-plugins-base1.0 (1.8.2-1) unstable; urgency=medium

  * debian/control.in:
+ Remove duplicated field name.
  * New upstream bugfix release.

 -- Iain Lane   Mon, 20 Jun 2016 15:24:43 +0100

** Changed in: gst-plugins-base1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  New
Status in gst-plugins-bad1.0 source package in Xenial:
  New
Status in gst-plugins-base1.0 source package in Xenial:
  New
Status in gst-plugins-good1.0 source package in Xenial:
  New
Status in gst-plugins-ugly1.0 source package in Xenial:
  New
Status in gstreamer-vaapi source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+subscriptions

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

[Desktop-packages] [Bug 1594791] [NEW] light dm screen resolution

[Thomas]

Public bug reported:

Part of the screen is not accessible, and the upper part is huge on the
screen. Is lightdm activated?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jun 21 14:25:45 2016
InstallationDate: Installed on 2015-04-30 (418 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  light dm screen resolution

Status in lightdm package in Ubuntu:
  New

Bug description:
  Part of the screen is not accessible, and the upper part is huge on
  the screen. Is lightdm activated?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 21 14:25:45 2016
  InstallationDate: Installed on 2015-04-30 (418 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 817326] Re: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync

[Angel Garcia]

This bug has returned to live. LibreOffice 4.2.8.2   Compilation Id.
420m0 (build:2), with autobackup active each 15 min. Running on Ubuntu
14.04 LTS. ext4 hard disk.

I opened a .doc, (previously created by LOW), made modifications (6 hour 
session) while continuously saving (each 5 minutes or so). Then I saved and 
closed the document and turned off the computer. When I came back, the file 
.doc was untouched as if any changes were made.
I looked for similar files in all the hard disk (grep), I looked in the 
libreoffice backup directory (empty) and also I ran scalpel, at no avail.

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

Title:
  [Upstream] Previously-saved LibreOffice document lost by power outage
  (became 0 bytes long) - LibreOffice should call fsync

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  I was working on a document in LibreOffice today while my battery was
  low and so I was frequently saving, which I thought would help me if I
  lost power. However, when I eventually did lose power and later
  rebooted, the document had become 0 bytes long. LibreOffice was not
  able to restore the auto-saved copy either. As a result, I have lost a
  whole week of notes for one of my courses.

  After researching online, it seems that this is caused by the
  application not calling fsync() (or fdatasync()) when saving files.
  Due to delayed allocation in modern filesystems, there is no guarantee
  that the new file's data has actually been written to disk unless the
  application calls fsync. So if an app writes a new file and replaces
  the old one with it without fsync'ing the new one first then there is
  a window of opportunity during which a power failure will result in
  the loss of BOTH versions of the file. In ext4 this window is also
  much larger than in ext3.

  Theodore Tso blogged about this at http://ldn.linuxfoundation.org
  /blog-entry/delayed-allocation-and-zero-length-file-problem and
  http://www.linuxfoundation.org/news-
  media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly
  recommends to call fsync in this situation.

  Please update LibreOffice to fsync() saved files so that other users
  do not lose their data like I did.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Wed Jul 27 21:37:02 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/817326/+subscriptions

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

[Desktop-packages] [Bug 1575422] Re: /usr/bin/nm-applet:6:g_assertion_message:g_assertion_message_expr:applet_get_first_active_vpn_connection:applet_update_icon:g_main_dispatch

[Sebastien Bacher]

Could you have a look Aron?

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

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

Title:
  /usr/bin/nm-
  
applet:6:g_assertion_message:g_assertion_message_expr:applet_get_first_active_vpn_connection:applet_update_icon:g_main_dispatch

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 1.1.93-1ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4f70964382796f71970a9d200d180ee5d1b0180f
  contains more details.

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

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

[Desktop-packages] [Bug 1583573] Re: /usr/bin/nm-applet:11:stuff_changed_cb:stuff_changed:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

[Sebastien Bacher]

That doesn't seem new nor Ubuntu specific (there are similar reports in
the fedora bugzilla for example) ... Aron could you forward that one to
GNOME?

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

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

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

Title:
  /usr/bin/nm-
  
applet:11:stuff_changed_cb:stuff_changed:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in network-manager-applet package in Ubuntu:
  New
Status in network-manager-applet package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 1.2.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/d3a44e26e1ce9f60c75516733fdfc44bf0c8405b
  contains more details.

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

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

[Desktop-packages] [Bug 1583573] Re: /usr/bin/nm-applet:11:stuff_changed_cb:stuff_changed:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

[Sebastien Bacher]

https://bugzilla.redhat.com/show_bug.cgi?id=1287267 is one

** Also affects: network-manager-applet (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1287267
   Importance: Unknown
   Status: Unknown

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

Title:
  /usr/bin/nm-
  
applet:11:stuff_changed_cb:stuff_changed:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in network-manager-applet package in Ubuntu:
  New
Status in network-manager-applet package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 1.2.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/d3a44e26e1ce9f60c75516733fdfc44bf0c8405b
  contains more details.

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

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

[Desktop-packages] [Bug 1575878] Re: Xorg freeze when see videos or animation 16.04

[Christopher M. Penalver]

** Tags added: wily

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

Title:
  Xorg freeze when see videos or animation 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When videos are played the system randomly freezes to start playing
  the video, or when it takes a few minutes. It also happens with
  animations webs. This happened with the previous kernel of 15.10 and
  with the current kernel of 16.04. The bios is the latest version and
  use public graphics drivers.

  If I do not watch videos or animations I can work full days without
  freezing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 27 21:01:26 2016
  DistUpgraded: 2016-04-21 20:00:24,411 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:2224]
  InstallationDate: Installed on 2016-01-14 (104 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20D9S00D00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3e293fa3-ec43-4f0a-a925-562901db8088 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (6 days ago)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0G00622 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn20D9S00D00:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0G00622WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20D9S00D00
  dmi.product.version: ThinkPad 11e
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 21:00:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1161 
   vendor IVO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1594407] Re: [SRU] New stable release 1.8.2

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-good1.0 - 1.8.2-1ubuntu1

---
gst-plugins-good1.0 (1.8.2-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian unstable (LP: #1594407); remaining changes:
+ Import plugins from -bad that are needed for main applications.
  - jpegformat
  - camerabin2 (+ basecamerabinsrc + photography)
+ Break and Replace -bad versions which contained these plugins.
+ Add a library package containing the shared library and a -dev package for
  compiling against it. Add Breaks and Replaces against the plugins packages
  which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
  some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu

gst-plugins-good1.0 (1.8.2-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Iain Lane   Mon, 20 Jun 2016 15:53:46 +0100

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  New
Status in gst-plugins-bad1.0 source package in Xenial:
  New
Status in gst-plugins-base1.0 source package in Xenial:
  New
Status in gst-plugins-good1.0 source package in Xenial:
  New
Status in gst-plugins-ugly1.0 source package in Xenial:
  New
Status in gstreamer-vaapi source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+subscriptions

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

[Desktop-packages] [Bug 1594743] Re: Yahoo account access blocked because of “less secure sign-in”

[Matthew Paul Thomas]

** Description changed:

  Ubuntu 15.04 (r349)
  
  1. Launch Dekko.
  2. Choose to set up a new account.
  3. Choose Yahoo.
  4. Enter your Yahoo account details.
  
  What happens:
  * An error appears: “Authentication failed. This often happens due to bad 
password or wrong user name. (#MBR1212) Incorrect username or password.”
- * If you sign in to Yahoo mail on another device, you see a new message: 
“Someone attempted to sign in to your Yahoo account (mpt_nz) from an app that 
doesn't meet Yahoo's security standards. We blocked this sign-in attempt … 
Using apps that don't meet Yahoo's recommended security standards may leave 
your account more vulnerable or less secure.”
+ * If you sign in to Yahoo mail on another device, you see a new message: 
“Someone attempted to sign in to your Yahoo account from an app that doesn't 
meet Yahoo's security standards. We blocked this sign-in attempt … Using apps 
that don't meet Yahoo's recommended security standards may leave your account 
more vulnerable or less secure.”
  
  What should happen: Signing in should work.
- 
- [Sorry I don’t know the appropriate component: it’s not listed under
-  or
- .]

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

Title:
  Yahoo account access blocked because of “less secure sign-in”

Status in Canonical System Image:
  New
Status in account-plugins package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 (r349)

  1. Launch Dekko.
  2. Choose to set up a new account.
  3. Choose Yahoo.
  4. Enter your Yahoo account details.

  What happens:
  * An error appears: “Authentication failed. This often happens due to bad 
password or wrong user name. (#MBR1212) Incorrect username or password.”
  * If you sign in to Yahoo mail on another device, you see a new message: 
“Someone attempted to sign in to your Yahoo account from an app that doesn't 
meet Yahoo's security standards. We blocked this sign-in attempt … Using apps 
that don't meet Yahoo's recommended security standards may leave your account 
more vulnerable or less secure.”

  What should happen: Signing in should work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594743/+subscriptions

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

[Desktop-packages] [Bug 1594743] Re: Yahoo account access blocked because of “less secure sign-in”

[Matthew Paul Thomas]

** Project changed: dekko => account-plugins (Ubuntu)

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

Title:
  Yahoo account access blocked because of “less secure sign-in”

Status in Canonical System Image:
  New
Status in account-plugins package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 (r349)

  1. Launch Dekko.
  2. Choose to set up a new account.
  3. Choose Yahoo.
  4. Enter your Yahoo account details.

  What happens:
  * An error appears: “Authentication failed. This often happens due to bad 
password or wrong user name. (#MBR1212) Incorrect username or password.”
  * If you sign in to Yahoo mail on another device, you see a new message: 
“Someone attempted to sign in to your Yahoo account from an app that doesn't 
meet Yahoo's security standards. We blocked this sign-in attempt … Using apps 
that don't meet Yahoo's recommended security standards may leave your account 
more vulnerable or less secure.”

  What should happen: Signing in should work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594743/+subscriptions

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