[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing

[Boris Dalstein]

Just adding my voice here. This bug makes PDF+LaTeX pretty unusable as
of now. Rolling back to previous behaviour seems advisable, at least
until an actual fix is made.

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

Title:
  PDF+Latex export creates multipage pdf, pages missing

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

Bug description:
  In 0.91 the z-order information in svg is used to create multipage
  PDF+LaTeX documents as per bug 771957. However, for the SVGs I have
  been converting to PDF+LaTeX in this way, the TeX-file instructs to
  load more pages than the PDF has, for example the PDF has only three
  pages and the TeX file also includes page=4. This basically breaks the
  PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf
  package.

  The bug occurs on OpenSuse 13.1 and Windows 8.1.

  Attached a zip file with two svg files and their broken PDF+LaTeX
  counterparts.

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

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

[Desktop-packages] [Bug 1662227] Re: Error with command "apt-get update" when using versioned "Provides:" (apt is too old to support that case)

[Vitaliy Yeresko]

All libreoffice conponents have successfully updated to 5.3.2~rc2 from
ppa:libreoffice/ppa. All components except libreoffice-l10n-xx... A log
is in an attachment. I have to notice that libreoffice-core 5.3.2~rc2
and libreoffice-common 5.3.2~rc2 are installed.

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1662227/+attachment/4853980/+files/log

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

Title:
  Error with command "apt-get update" when using versioned "Provides:"
  (apt is too old to support that case)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I'm getting this error every time I do "apt-get update"

  Ign http://ni.archive.ubuntu.com trusty/multiverse Translation-en_US  
 
  Ign http://ni.archive.ubuntu.com trusty/restricted Translation-en_US  
 
  Ign http://ni.archive.ubuntu.com trusty/universe Translation-en_US
 
  Reading package lists... Done 
 
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  ...
  ...
  ...
  ...
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: You may want to run apt-get update to correct these problems

  This error started to show after I upgraded LibreOffice form 5.2 to
  5.3 with the LibreOffice PPA: ppa:libreoffice/ppa.

  The thing is that everything is working fine. I can update/upgrade the
  system, I can install packages, delete packages, etc. The problem is
  just with the error.

  I tried: "apt-get autoclean". "apt-get clean", "apt-get autoremove",
  apt-get install -f", and a lot of other things and nothing removes
  that ugly error.

  If I remove all PPA packages and remove the PPA itself the error goes
  away.

  This has been reported in askubuntu.com:

  
  
http://askubuntu.com/questions/880447/ubuntu-14-04-error-with-apt-get-update-w-ignoring-provides-line-with-depcom

  http://askubuntu.com/questions/879497/apt-spewing-warnings-after-
  libreoffice-update

  
  Help please. Thank you.

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

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

[Desktop-packages] [Bug 1679451] Re: Xorg crashed with SIGABRT

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1611839

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  this happens after every boot and log-in, within a minute or so.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.18.4-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-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
  CrashCounter: 1
  Date: Fri Mar 31 15:36:27 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-14-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7a66]
  InstallationDate: Installed on 2017-01-21 (72 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170120)
  MachineType: MSI MS-7A66
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt8 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=/dev/sda5 
ro quiet
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   ()
   ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270I GAMING PRO CARBON AC (MS-7A66)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/06/2016:svnMSI:pnMS-7A66:pvr1.0:rvnMSI:rnZ270IGAMINGPROCARBONAC(MS-7A66):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7A66
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  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 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Apr  4 05:20:47 2017
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

[Desktop-packages] [Bug 1667903] Re: choqok crashed with SIGSEGV in QCA::init()

[clickwir]

Yup, it's broke.

$ choqok 
org.kde.choqok: Choqok  1.6.0
org.kde.choqok: 
org.kde.choqok: 
org.kde.choqok: 
org.kde.choqok: 
org.kde.choqok.lib: 
org.kde.choqok.lib: 
org.kde.choqok.lib: 
org.kde.choqok.lib: ("Account_Twitter")
org.kde.choqok.lib: "Account_Twitter"
org.kde.choqok.lib: Loading Plugin: "choqok_twitter"
org.kde.choqok.lib: 
org.kde.choqok.twitterapi: 
org.kde.choqok.twitter: 
org.kde.choqok.lib: Successfully loaded plugin ' "choqok_twitter" '
org.kde.choqok.lib: Finding: "Twitter"
org.kde.choqok.lib: 
org.kde.choqok.lib: 
org.kde.choqok.lib: Wallet successfully opened.
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.lib: 
org.kde.choqok.twitterapi: 
org.kde.choqok.lib: 
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.lib: 
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.twitterapi: UsingOAuth: true
org.kde.choqok.twitterapi: 
Segmentation fault (core dumped)

syslog:
Apr  3 20:59:09 host kernel: [157712.663466] show_signal_msg: 66 callbacks 
suppressed
Apr  3 20:59:09 host kernel: [157712.663469] choqok[27206]: segfault at 4 ip 
7efe103deb37 sp 7fff206de370 error 4 in 
libqca.so.2.1.1[7efe1038b000+f]
Apr  3 20:59:45 host whoopsie[1237]: [20:59:45] Not online; processing later 
(/var/crash/_usr_bin_choqok.1000.crash).
Apr  3 20:59:45 host kernel: [157748.986394] choqok[28306]: segfault at 4 ip 
7f8bae2aeb37 sp 7ffd3613af50 error 4 in 
libqca.so.2.1.1[7f8bae25b000+f]
Apr  3 21:00:00 host kernel: [157764.254790] choqok[28324]: segfault at 4 ip 
7f0e99ad6b37 sp 7ffc0a844b30 error 4 in 
libqca.so.2.1.1[7f0e99a83000+f]


Kubuntu 17.04

$ sudo apt show choqok
Package: choqok
Version: 1.6-1ubuntu1
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Kubuntu Developers 
Original-Maintainer: Lisandro Damián Nicanor Pérez Meyer 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 7,637 kB
Depends: libqca2-plugin-ossl, kio, libc6 (>= 2.14), libkf5attica5 (>= 4.98.0), 
libkf5configcore5 (>= 4.98.0), libkf5configgui5 (>= 4.97.0), 
libkf5configwidgets5 (>= 4.96.0), libkf5coreaddons5 (>= 5.2.0), 
libkf5emoticons-bin, libkf5emoticons5 (>= 4.96.0), libkf5globalaccel5 (>= 
5.0.0), libkf5guiaddons5 (>= 4.96.0), libkf5i18n5 (>= 4.97.0), 
libkf5jobwidgets5 (>= 4.96.0), libkf5kcmutils5 (>= 4.96.0), libkf5kiocore5 (>= 
4.96.0), libkf5kiofilewidgets5 (>= 4.96.0), libkf5kiowidgets5 (>= 4.96.0), 
libkf5notifications5 (>= 4.96.0), libkf5notifyconfig5 (>= 4.96.0), libkf5parts5 
(>= 4.96.0), libkf5service-bin, libkf5service5 (>= 4.99.0), libkf5sonnetcore5 
(>= 4.96.0), libkf5textwidgets5 (>= 4.96.0), libkf5wallet-bin, libkf5wallet5 
(>= 4.96.0), libkf5webkit5 (>= 4.96.0), libkf5widgetsaddons5 (>= 4.96.0), 
libkf5xmlgui5 (>= 4.98.0), libqca-qt5-2 (>= 2.0.2), libqoauth1, libqt5core5a 
(>= 5.6.1), libqt5dbus5 (>= 5.0.2), libqt5gui5 (>= 5.2.0) | libqt5gui5-gles (>= 
5.2.0), libqt5webkit5 (>= 5.6.0~rc), libqt5widgets5 (>= 5.2.0), libqt5xml5 (>= 
5.0.2), libstdc++6 (>= 4.1.1), libtelepathy-qt5-0 (>= 0.0.9.5)
Homepage: http://choqok.gnufolks.org
Download-Size: 1,727 kB
APT-Manual-Installed: yes
APT-Sources: http://mirrors.us.kernel.org/ubuntu zesty/universe amd64 Packages
Description: KDE micro-blogging client
 Choqok is a fast, efficient and simple to use micro-blogging client for KDE.
 It currently supports the twitter.com and identi.ca microblogging services.
 .
 Other notable features include:
* Support for user + friends time-lines.
* Support for @Reply time-lines.
* Support for sending and receiving direct messages.
* Twitpic.com integration.
* The ability to use multiple accounts simultaneously.
* Support for search APIs for all services.
* KWallet integration.
* Support for automatic shortening urls with more than 30 characters.
* Support for configuring status lists appearance.

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

Title:
  choqok crashed with SIGSEGV in QCA::init()

Status in choqok package in Ubuntu:
  Confirmed

Bug description:
  Choqok segfaults upon startup on Kubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: choqok 1.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Fri Feb 24 23:54:47 2017
  ExecutablePath: /usr/bin/choqok
  InstallationDate: Installed on 2016-12-17 (70 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcCmdline: /usr/bin/choqok -qwindowtitle Choqok
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened 

[Desktop-packages] [Bug 1667903] Re: choqok crashed with SIGSEGV in QCA::init()

[Launchpad Bug Tracker]

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

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

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

Title:
  choqok crashed with SIGSEGV in QCA::init()

Status in choqok package in Ubuntu:
  Confirmed

Bug description:
  Choqok segfaults upon startup on Kubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: choqok 1.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Fri Feb 24 23:54:47 2017
  ExecutablePath: /usr/bin/choqok
  InstallationDate: Installed on 2016-12-17 (70 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcCmdline: /usr/bin/choqok -qwindowtitle Choqok
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb55fb4b37 <_ZN3QCA4initENS_10MemoryModeEi+39>:
testb  $0x1,0x4(%rdx)
   PC (0x7feb55fb4b37) ok
   source "$0x1" ok
   destination "0x4(%rdx)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: choqok
  StacktraceTop:
   QCA::init(QCA::MemoryMode, int) () from /usr/lib/x86_64-linux-gnu/libqca.so.2
   QOAuth::InterfacePrivate::InterfacePrivate() () from /usr/lib/libqoauth.so.1
   QOAuth::Interface::Interface(QNetworkAccessManager*, QObject*) () from 
/usr/lib/libqoauth.so.1
   TwitterApiAccount::initQOAuthInterface() () from 
/usr/lib/x86_64-linux-gnu/libtwitterapihelper.so.1
   TwitterApiAccount::TwitterApiAccount(TwitterApiMicroBlog*, QString const&) 
() from /usr/lib/x86_64-linux-gnu/libtwitterapihelper.so.1
  Title: choqok crashed with SIGSEGV in QCA::init()
  UpgradeStatus: Upgraded to zesty on 2017-02-25 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (opera:10496): Gtk-WARNING **: Unable to locate theme engine in module_path: 
"adwaita",
   (opera:10496): Gtk-WARNING **: Unable to locate theme engine in module_path: 
"adwaita",

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

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

[Desktop-packages] [Bug 1661556] Re: epiphany does not accept uppercase letter or shortcuts on HTML form on first button press

[Jeremy Bicha]

Alan, please specify the exact version of the web browser you are using.

I cannot duplicate this issue on Ubuntu 16.04 LTS with epiphany-browser
3.18.11-0ubuntu1.

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

Title:
  epiphany does not accept uppercase letter or shortcuts on HTML form on
  first button press

Status in elementary OS:
  Confirmed
Status in Epiphany Browser:
  Unknown
Status in epiphany-browser package in Ubuntu:
  Incomplete

Bug description:
  When writing inside a page HTML form (i.e. google search input field, this 
textarea etc...) you have to press twice the letter to capitalize (holding the 
"shift") to write one.
  Same behavior with CTRL or ALT-GR

  For example to select all I need to press this keyboard sequence to
  get the shorcut working.

  CTRL+A+A 
  (seems like missing the first input key, in the example the first "A") 

  I am using Elementary OS Loki
  Italian keyboard.
  Verified even with Guest user
  Verified w onscreen keyboard

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

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

[Desktop-packages] [Bug 1393578] Re: Subpixel order not included in Mir display information

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

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

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

[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683

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

Title:
  [enhancement] Missing client API for relative surface movement (e.g.
  dragging client-decorated windows)

Status in Mir:
  Fix Committed
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Mir needs a client API to allow surfaces to move themselves
  relatively. This is required to support full client-side decorations
  (bug 1398849), and also other apps like Google Chrome and Gnome
  Nautilus which can be dragged using part of their client areas.

  Later additions that are so similar I think they are part of the same
  bug: there need to be client APIs for "always on top" and "client
  initiate resize".

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

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

[Desktop-packages] [Bug 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683

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

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

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

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

[Desktop-packages] [Bug 1675481] Re: Xmir crashes when using the '-fd' option

[Daniel van Vugt]

https://git.launchpad.net/~xmir-team/xorg-
server/+git/xmir/commit/?id=e8435ece23017fb4153487f6157eb11cac985697

** Changed in: xorg-server (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Xmir crashes when using the '-fd' option

Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  I'm trying to use the '-fd' option in Xmir and get a crash when Xmir
  starts up.

  This is what I'm doing:

  I'm using socket()/bind()/listen()/accept() on a AF_UNIX socket at
  /tmp/.X11-unix/X0 (or whatever available display number).  DISPLAY is
  then set based on this.  Then, when an X app accesses that socket, the
  code then starts Xmir and passes the fd returned in the accept() call
  to Xmir in the '-fd' option.

  This is what I get in journalctl when this crash occurs:
  http://pastebin.ubuntu.com/24235520/

  I installed the Xmir debug symbols and also passed in '-core' when
  starting Xmir and here is the bt: http://pastebin.ubuntu.com/24236088/

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

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

[Desktop-packages] [Bug 1661556] Re: epiphany does not accept uppercase letter or shortcuts on HTML form on first button press

[Alan Diggs]

Using: Elementary OS (0.4 Loki)
Dated: April 03, 2017
I'm also having this issue. System and applications are up to date.

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

Title:
  epiphany does not accept uppercase letter or shortcuts on HTML form on
  first button press

Status in elementary OS:
  Confirmed
Status in Epiphany Browser:
  Unknown
Status in epiphany-browser package in Ubuntu:
  Incomplete

Bug description:
  When writing inside a page HTML form (i.e. google search input field, this 
textarea etc...) you have to press twice the letter to capitalize (holding the 
"shift") to write one.
  Same behavior with CTRL or ALT-GR

  For example to select all I need to press this keyboard sequence to
  get the shorcut working.

  CTRL+A+A 
  (seems like missing the first input key, in the example the first "A") 

  I am using Elementary OS Loki
  Italian keyboard.
  Verified even with Guest user
  Verified w onscreen keyboard

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

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

[Desktop-packages] [Bug 1618712] Re: Xmir -rootless: Fullscreen apps never go full screen

[Daniel van Vugt]

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => In Progress

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1618712

Title:
  Xmir -rootless: Fullscreen apps never go full screen

Status in Canonical System Image:
  In Progress
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Xmir -rootless: Fullscreen apps never go full screen.

  E.g. Press F11 in Gnome Terminal or in Chrome.

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

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

[Desktop-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Thibauld]

Also affected. Here is a screenshot of gnome-terminal when the bugs
happens. It is *really* annoying.

** Attachment added: "gnome-terminal when the bug happens"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4853854/+files/gnome-terminal.png.png

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

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

[Robert Ancell]

** Changed in: sane-backends (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: sane-backends (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Changed in: sane-backends (Ubuntu Zesty)
   Status: Triaged => Fix Committed

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

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

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

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

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

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

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

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

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

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

[Robert Ancell]

** Description changed:

- Upgraded from 14.04 to 14.10 alpha.
+ [Impact]
+ A bug in the SANE Kodak driver can cause a SANE device scan to crash the 
client that is using it (e.g. colord, simple-scan).
  
- ProblemType: Crash
- DistroRelease: Ubuntu 14.10
- Package: colord 1.2.1-1ubuntu1
- ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
- Uname: Linux 3.16.0-6-generic x86_64
- ApportVersion: 2.14.5-0ubuntu2
- Architecture: amd64
- AssertionMessage: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: 
Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state 
== STATE_FAILURE' failed.
- Date: Fri Aug  1 14:00:57 2014
- ExecutablePath: /usr/lib/colord/colord-sane
- InstallationDate: Installed on 2013-12-26 (217 days ago)
- InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
- ProcCmdline: /usr/lib/colord/colord-sane
- ProcEnviron:
-  
- Signal: 6
- SourcePackage: colord
- StacktraceTop:
-  __assert_fail_base (fmt=0x7fcda3d688b0 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fcd926f9fb0 "s->state == STATE_INIT 
|| s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", 
file=file@entry=0x7fcd926f9ee8 "simple-watch.c", line=line@entry=454, 
function=function@entry=0x7fcd926fa140 "avahi_simple_poll_prepare") at 
assert.c:92
-  __GI___assert_fail (assertion=0x7fcd926f9fb0 "s->state == STATE_INIT || 
s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=0x7fcd926f9ee8 
"simple-watch.c", line=454, function=0x7fcd926fa140 
"avahi_simple_poll_prepare") at assert.c:101
-  avahi_simple_poll_prepare () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
-  avahi_simple_poll_iterate () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
-  ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-kodakaio.so.1
- Title: colord-sane assert failure: colord-sane: simple-watch.c:454: 
avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == 
STATE_DISPATCHED || s->state == STATE_FAILURE' failed.
- UpgradeStatus: Upgraded to utopic on 2014-07-31 (0 days ago)
- UserGroups:
+ [Test Case]
+ 1. Run a SANE client on a system that is failing Avahi scans (exact cause not 
determined).
+ 
+ Expected result:
+ Client works without crashing.
+ 
+ Observed result:
+ Client crashes.
+ 
+ [Regression Potential]
+ Code fix could cause a change in behaviour of successful Avahi scans for 
Kodak devices, though the fix matches the Avahi documentation for correct usage.

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

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

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

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

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

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

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

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

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

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

[Robert Ancell]

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: sane-backends (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: sane-backends (Ubuntu Zesty)
   Importance: Medium
   Status: Triaged

** Also affects: sane-backends (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: sane-backends (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: sane-backends (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: sane-backends (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: sane-backends (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: sane-backends (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: sane-backends (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: sane-backends (Ubuntu Yakkety)
   Importance: Undecided => Medium

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

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

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

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

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

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

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

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

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

[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.3

[Tim Richardson]

I've been testing 1.19.x in 17.04 pre-release for a few weeks, hoping to
take advantage of the Nvidia PRIME synchronisation fix for laptops with
Optimus hybrid graphics. As of 1.19.3, PRIME sync works (with a modprobe
fix related to the nvidia driver). This is a huge improvement for nvidia
Optimus users (i.e. most high-end laptops I suspect), since it means no
more screen tearing on the laptop's LCD panel when hybrid graphics mode
is activated. My testing has been on a Thinkpad P50.  Really hope 1.19
gets into 17.04, and then into 16.04.3

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
  - qemu (QXL)

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

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

[Desktop-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x

[Tim Richardson]

I have a ThinkPad P50 and Prime sync is now working for me. I don't know
what change happened, sorry; it was two weeks since I did an update, and
it could be an updated kernel or updated xserver packages from Timo's
PPA.  I have the 375 driver. And it works really well, it's marvellous
to behold no tearing on the laptop panel.

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

Title:
  PRIME synchronization not working with xserver-1.19.x

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

  Shows this in kern.log so support is enabled

  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1551599] Re: Remove button missing after package installation

[Jeremy Bicha]

** Description changed:

  [What Happens]
  ==
  Installing
  --
  1. Open the Software app (GNOME Software). Search for clocks.
  2. Click Install next to Clocks.
  3. The Install button becomes insensitive and changes to Installing...
  4. The Install button becomes sensitive again and changes back to Install (it 
should have changed to Remove)
  5. If you click the Clocks row (still in the All page), the Clocks info page 
opens with an Install button (it should have a Launch button and a Remove 
button).
  6. If you switch to the Installed page, Clocks correctly shows up with a 
Remove button.
  7. If you click the Clocks row in the Installed page, the Clocks info page 
correctly opens with a Launch button and a Remove button.
  8. Close the Software app then reopen it. Same results as #4-7 above.
  9. $ pkill gnome-software
  10. Open the Software app. Now Clocks shows up correctly in the All page with 
a Remove button and the Clocks info page correctly includes the Launch and 
Remove buttons but not the Install button.
  
  Removing
  
  11. Click the Remove button to uninstall Clocks.
  12. The Remove button becomes insensitive again and changes to Removing...
  12. We basically get the same broken results as before. In the All page, the 
Clocks row shows Remove still. Clicking the Clocks row shows the Info page with 
Launch and Remove.
  One change is that in the Installed page, Clocks shows up twice, once with an 
Install button, once with a Remove button.
  Completely stopping the gnome-software process (via logging out or the pkill 
trick mentioned in #9) is necessary for the Software app to correctly register 
Clocks as being removed.
  
  I was unable to reproduce this bug with Fedora 24.
  
+ Other Info
+ ==
  See also bug 1582959 which is similar but a bit different.
+ 
+ In bug 1679417, a user reported that the package disappears from the
+ Installed list if Remove is selected but password authentication is
+ cancelled or failed.
  
  [Original bug report]
  =
  Used gnome-software to install a package.
  
  Once it was installed I expected to see an option to remove it.
  
  As can be seen all I see is the option to Install the package.
  
  If you click Install you are then given the option to remove the
  package.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar  1 08:05:06 2016
  InstallationDate: Installed on 2015-10-29 (123 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Remove button missing after package installation

Status in One Hundred Papercuts:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  [What Happens]
  ==
  Installing
  --
  1. Open the Software app (GNOME Software). Search for clocks.
  2. Click Install next to Clocks.
  3. The Install button becomes insensitive and changes to Installing...
  4. The Install button becomes sensitive again and changes back to Install (it 
should have changed to Remove)
  5. If you click the Clocks row (still in the All page), the Clocks info page 
opens with an Install button (it should have a Launch button and a Remove 
button).
  6. If you switch to the Installed page, Clocks correctly shows up with a 
Remove button.
  7. If you click the Clocks row in the Installed page, the Clocks info page 
correctly opens with a Launch button and a Remove button.
  8. Close the Software app then reopen it. Same results as #4-7 above.
  9. $ pkill gnome-software
  10. Open the Software app. Now Clocks shows up correctly in the All page with 
a Remove button and the Clocks info page correctly includes the Launch and 
Remove buttons but not the Install button.

  Removing
  
  11. Click the Remove button to uninstall Clocks.
  12. The Remove button becomes insensitive again and changes to Removing...
  12. We basically get the same broken results as before. In the All page, the 
Clocks row shows Remove still. Clicking the Clocks row shows the Info page with 
Launch and Remove.
  One change is that in the Installed page, Clocks shows up twice, once with an 
Install button, once with a Remove button.
  Completely stopping the gnome-software process (via logging out or the pkill 
trick mentioned in #9) is necessary for the Software app to correctly register 
Clocks as being removed.

  I was unable to reproduce this bug 

[Desktop-packages] [Bug 1679417] Re: removes package from installed list even when you don't remoe

[Jeremy Bicha]

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

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

** This bug has been marked a duplicate of bug 1551599
   Remove button missing after package installation

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

Title:
  removes package from installed list even when you don't remoe

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This is not a major bug, but it is a bug anyway. my gnome-software
  version is: 3.20.1.

  Problem is when you try to remove a software from installed list. You
  hit the remove and then when it prompts to ask you to remove you hit
  the remove again, but when it ask you to enter the password you hit
  cancel. In this condition seems the hitting remove is enough to remove
  the software from installed list eventhough you have not actually
  uninstalled the software. This list becomes sync again when you logout
  or restart, but not before that.

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

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

[Desktop-packages] [Bug 1678622] Re: Libreoffice copy paste doesn't copy calculations

[Cliff Carson]

Simplified failure description...
Mark a single cell that has data and formula.  Hit ctl-c once, move to an open 
cell and hit ctl-v.  When this is failing the data in the marked cell is copied 
to the new cell but not the formula.
Unmark the cell by marking any other cell and then mark the formula cell again. 
 Hit ctl-c twice, move to an open cell and hit ctl-v.  The formula is copied, 
adjusted and cell content recalculated.
While this was failing tried to copy formula to multiple cells...
Marked the formula cell, ctl-c once, marked 3 cells one column over, ctl-v.  
The data in the formula cell was copied to the first target cell and the other 
cells left blank.  Formula not copied.
Mark the formula cell, ctl-c twice, mark 3 cells one column over, ctl-v.  
Operation worked as expected.  Formulas copied, adjusted, and cells 
recalculated.

Had to reboot this laptop and the failure is gone again.  I was failing
every time and on all the spreadsheets I tried.

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

Title:
  Libreoffice copy paste doesn't copy calculations

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When doing a copy/paste of rows only the text information is copied (a
  "Text Import" dialog box is displayed which normally wasn't before).
  If the copy/paste operation is repeated than the text and calculations
  are copied.  In fact if the copy (ctl-c) is hit twice and then the
  paste (ctl-v) the operation works correctly.  Using the Copy/Paste
  icons shows the same incorrect behavior.

  ii  libreoffice-calc1:5.3.1-0ubunt amd64  office
  productivity suite -- spreadsheet

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-calc 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr  2 10:05:34 2017
  InstallationDate: Installed on 2017-02-13 (47 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1679417] [NEW] removes package from installed list even when you don't remoe

[farhad haqiqat]

Public bug reported:

This is not a major bug, but it is a bug anyway. my gnome-software
version is: 3.20.1.

Problem is when you try to remove a software from installed list. You
hit the remove and then when it prompts to ask you to remove you hit the
remove again, but when it ask you to enter the password you hit cancel.
In this condition seems the hitting remove is enough to remove the
software from installed list eventhough you have not actually
uninstalled the software. This list becomes sync again when you logout
or restart, but not before that.

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

** Description changed:

- This is not a major bug, but it is bug anyway. my gnome-software version
- is: 3.20.1.
+ This is not a major bug, but it is a bug anyway. my gnome-software
+ version is: 3.20.1.
  
  Problem is when you try to remove a software from installed list. You
  hit the remove and then when it prompts to ask you to remove you hit the
  remove again, but when it ask you to enter the password you hit cancel.
  In this condition seems the hitting remove is enough to remove the
  software from installed list eventhough you have not actually
  uninstalled. This list becomes sync again when you logout or restart,
  but not before that.

** Description changed:

  This is not a major bug, but it is a bug anyway. my gnome-software
  version is: 3.20.1.
  
  Problem is when you try to remove a software from installed list. You
  hit the remove and then when it prompts to ask you to remove you hit the
  remove again, but when it ask you to enter the password you hit cancel.
  In this condition seems the hitting remove is enough to remove the
  software from installed list eventhough you have not actually
- uninstalled. This list becomes sync again when you logout or restart,
- but not before that.
+ uninstalled the software. This list becomes sync again when you logout
+ or restart, but not before that.

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

Title:
  removes package from installed list even when you don't remoe

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This is not a major bug, but it is a bug anyway. my gnome-software
  version is: 3.20.1.

  Problem is when you try to remove a software from installed list. You
  hit the remove and then when it prompts to ask you to remove you hit
  the remove again, but when it ask you to enter the password you hit
  cancel. In this condition seems the hitting remove is enough to remove
  the software from installed list eventhough you have not actually
  uninstalled the software. This list becomes sync again when you logout
  or restart, but not before that.

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

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

[Desktop-packages] [Bug 1679359] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of April 3, 2017, this source package did not contain package tests
in the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source pm-utils zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'. The package was also checked for 1) a test suite
declaration in the debian/control file, 2) any 'test', 'tests',
'testsuite', or 'test-suite' directories, 3) go tests (if applicable),
and 4) a test suite declared in a setup.py (if applicable).

If you feel this report is incorrect (e.g. this is a library or a source
only package) or the check above missed some other package level test
please reply explaining why and mark this bug as 'invalid'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

Thanks!

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/pm-utils
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY4smeAAoJEIP8BxPaZgwlfuMP/3KA2S1IDXH2OBD5GFusUTBs
/AJv0a56NFpBin5GGwU6yuDeWz/Z4jRANNicNEjEqWYyH0fXt2tPZMt3EeQ72b/s
JvmqbqpMYPv+5XYt8T3YPQXPFPA0kdoQRRF+S3qokAveCyqHeOxeDFbMCCoa/PUV
7rMIJ0hdHldTGI/5ovNeGGwfdq1QshcJRsdfusAFBfIyph5fWBtrkLLZSEkJbIRF
tZod0RyvZxlNv/pIJ+C83uOdRW/qSCBCDRiOPIB6mfpT+1EqgP9EVH4d5OxrS0Pa
A3TtHn7eOGIBqeLfOeStVt3lTDjwlmpjFiWXVrSLJj25Q7A+4RP7BrD+5p/KrT/c
qiw1dV8DCHz9QVoOTd8L+maUh04RB+pVogPMiWo/XyPbPgf8f/sVixIqHWFfkKMG
Rwbor5yL603EpVOjDy+yGsgbUozbYfOsrPaIo7qKVcsSx4CMAP8A9CxqyO1X4dwk
Ru1d0M53MTY/rWrtDNLq3lFX67K6LfqrsEcw2e3S9xuIhpLWAeMThRF89a3lm3t9
ut5AfA2YArXzX2njYRe425nOcc52qffSS3ew/qHygtZ6w58dpt6xL3tvgKBAicyv
IqhEfK9DjAUhsgATU5/5zKScRzhSYKffxG+DZtP85Y3WIJqkc4pya7QUIGJ0aWZZ
qhtO7AokoWV8adGpzUQc
=o5cI
-END PGP SIGNATURE-

** Affects: pm-utils (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in pm-utils package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of April 3, 2017, this source package did not contain package tests
  in the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source pm-utils zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'. The package was also checked for 1) a test suite
  declaration in the debian/control file, 2) any 'test', 'tests',
  'testsuite', or 'test-suite' directories, 3) go tests (if applicable),
  and 4) a test suite declared in a setup.py (if applicable).

  If you feel this report is incorrect (e.g. this is a library or a source
  only package) or the check above missed some other package level test
  please reply explaining why and mark this bug as 'invalid'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  Thanks!

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/pm-utils
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY4smeAAoJEIP8BxPaZgwlfuMP/3KA2S1IDXH2OBD5GFusUTBs
  /AJv0a56NFpBin5GGwU6yuDeWz/Z4jRANNicNEjEqWYyH0fXt2tPZMt3EeQ72b/s
  JvmqbqpMYPv+5XYt8T3YPQXPFPA0kdoQRRF+S3qokAveCyqHeOxeDFbMCCoa/PUV
  7rMIJ0hdHldTGI/5ovNeGGwfdq1QshcJRsdfusAFBfIyph5fWBtrkLLZSEkJbIRF
  tZod0RyvZxlNv/pIJ+C83uOdRW/qSCBCDRiOPIB6mfpT+1EqgP9EVH4d5OxrS0Pa
  A3TtHn7eOGIBqeLfOeStVt3lTDjwlmpjFiWXVrSLJj25Q7A+4RP7BrD+5p/KrT/c
  qiw1dV8DCHz9QVoOTd8L+maUh04RB+pVogPMiWo/XyPbPgf8f/sVixIqHWFfkKMG
  Rwbor5yL603EpVOjDy+yGsgbUozbYfOsrPaIo7qKVcsSx4CMAP8A9CxqyO1X4dwk
  Ru1d0M53MTY/rWrtDNLq3lFX67K6LfqrsEcw2e3S9xuIhpLWAeMThRF89a3lm3t9
  ut5AfA2YArXzX2njYRe425nOcc52qffSS3ew/qHygtZ6w58dpt6xL3tvgKBAicyv
  IqhEfK9DjAUhsgATU5/5zKScRzhSYKffxG+DZtP85Y3WIJqkc4pya7QUIGJ0aWZZ
  qhtO7AokoWV8adGpzUQc
  =o5cI
  -END PGP SIGNATURE-

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

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

[Desktop-packages] [Bug 1663918] Re: Network Manager fails to reconnect to wifi after resuming from suspend

[gutschke]

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

** This bug has been marked a duplicate of bug 1676810
   Network Manager needs restarting from sleep

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

Title:
  Network Manager fails to reconnect to wifi after resuming from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resuming from suspend on my laptop, I have wifi enabled, but
  Network Manager does not automatically reconnect, and it's list of
  available wifi networks is blank.

  If I run `sudo service network-manager restart`, then this fixes
  everything and it automatically detects and connects to my wifi
  hotspot, but this shouldn't be necessary.

  This problem seems specific to 16.04. Under 14.04, NM worked
  perfectly. After I upgraded my 14.04 install to 16.04 it started
  happening, however, I assumed this was likely due to some broken
  config file leftover from the upgrade. However, I recently did a fresh
  install to the same laptop on a blank hard drive, and the problem
  still exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 11 13:25:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-21 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.122  
metric 600 
   192.168.121.0/24 dev virbr1  proto kernel  scope link  src 192.168.121.1 
linkdown 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1676810] Re: Network Manager needs restarting from sleep

[Creak]

And the bug #1676081 also has relevant information toward VPN
connections:

> Side effect of the workaround: it closes the VPN connection if there
was one before.

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

Title:
  Network Manager needs restarting from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Each time my laptop is suspended and resumed, Network Manager seems
  unable to bring up Wifi.

  Calling...

  sudo service network-manager restart

  ...resolves the problem.

  I therefore placed the attached file at...

  /lib/systemd/system-sleep/network-manager

  ...which provides a workaround for the problem. However, there must be
  some kind of underlying bug in network-manager which requires it to be
  restarted after every suspend/resume cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Mar 28 10:21:35 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp1s0  proto static  metric 600 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.1.203  
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
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 ac7e4d66-b979-41de-b4b2-6f7c5dffc232  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp1s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Kitchen 2   937ae07a-fb47-46ac-91a4-0fe200203a95  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1676810] Re: Network Manager needs restarting from sleep

[gutschke]

Please note that bug 1666318 has relevant information. It appears that
editing

/etc/NetworkManager/NetworkManager.conf

and removing "dns=dnsmasq" makes the problem go away.

So, this could be a bug in either network manager or in dnsmasq

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

Title:
  Network Manager needs restarting from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Each time my laptop is suspended and resumed, Network Manager seems
  unable to bring up Wifi.

  Calling...

  sudo service network-manager restart

  ...resolves the problem.

  I therefore placed the attached file at...

  /lib/systemd/system-sleep/network-manager

  ...which provides a workaround for the problem. However, there must be
  some kind of underlying bug in network-manager which requires it to be
  restarted after every suspend/resume cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Mar 28 10:21:35 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp1s0  proto static  metric 600 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.1.203  
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
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 ac7e4d66-b979-41de-b4b2-6f7c5dffc232  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp1s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Kitchen 2   937ae07a-fb47-46ac-91a4-0fe200203a95  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1666318] Re: Disconnecting and reconnecting docking station breaks DNS

[gutschke]

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

** This bug has been marked a duplicate of bug 1676810
   Network Manager needs restarting from sleep

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

Title:
  Disconnecting and reconnecting docking station breaks DNS

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm not sure which package this bug should be submitted to as service
  troubleshooting in the latest few Ubuntu releases is a jumbled mess.

  Anyway, here's how to repro the problem:
  - Lenovo Carbon X1 2016 (4th gen), OneLink+ docking station
  - Ethernet connected to docking station
  - Disconnect docking station
  - Reconnect docking station

  From this point on all DNS requests fail. Workarounds I found so far:
  - reboot the machine (not really a solution)
  - sudo system network-manager restart (requires sudo access)
  - usually in older releases I'd just poke around with the resolver config 
files, but anything I do seems to be ignored now so I gave up and posted a bug 
instead.

  Here's the journalctl log for NetworkManager, followed by an example
  of the problem:

  nico@nico-lenovo-ubuntu:~$ journalctl -u NetworkManager -f
  -- Logs begin at Sun 2017-02-19 00:10:56 GMT. --
  Feb 20 20:22:41 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622161.9976] dns-mgr: Writing DNS information to /sbin/resolvconf
  Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: setting upstream servers 
from DBus
  Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 
194.168.4.100#53(via lan1)
  Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 
194.168.8.100#53(via lan1)
  Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 
194.168.4.100#53(via wifi0)
  Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 
194.168.8.100#53(via wifi0)
  Feb 20 20:22:42 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622162.0156] device (wifi0): Activation: successful, device activated.
  Feb 20 20:22:42 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622162.0169] manager: startup complete
  Feb 20 20:22:43 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622163.1408] manager: WiFi hardware radio set enabled
  Feb 20 20:22:43 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622163.1409] manager: WWAN hardware radio set disabled
  Feb 20 20:27:40 nico-lenovo-ubuntu dhclient[6736]: receive_packet failed on 
lan1: Network is down
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1588] manager: NetworkManager state is now CONNECTED_LOCAL
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1589] manager: NetworkManager state is now CONNECTED_GLOBAL
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1590] policy: set 'Auto ITADINANTA' (wifi0) as default for IPv4 
routing and DNS
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1590] device (lan1): state change: activated -> unmanaged (reason 
'removed') [100 10 36]
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1594] dhcp4 (lan1): canceled DHCP transaction, DHCP client pid 6736
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1595] dhcp4 (lan1): state changed bound -> done
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1618] dns-mgr: Writing DNS information to /sbin/resolvconf
  Feb 20 20:27:40 nico-lenovo-ubuntu dnsmasq[6728]: setting upstream servers 
from DBus
  Feb 20 20:27:40 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 
194.168.4.100#53(via wifi0)
  Feb 20 20:27:40 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 
194.168.8.100#53(via wifi0)
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:  
[1487622460.1799] platform-linux: do-change-link[5]: failure changing link: 
failure 19 (No such device)
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1800] device (lan1): failed to disable userspace IPv6LL address 
handling
  Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622460.1803] devices removed (path: 
/sys/devices/pci:00/:00:14.0/usb2/2-4/2-4.1/2-4.1.3/2-4.1.3:2.0/net/lan1,
 iface: lan1)
  Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622476.6972] device (eth0): failed to find device 6 'eth0' with udev
  Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622476.6990] manager: (eth0): new Ethernet device 
(/org/freedesktop/NetworkManager/Devices/4)
  Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622476.7679] device (eth0): interface index 6 renamed iface from 'eth0' to 
'lan1'
  Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]:   
[1487622476.7742] devices added (path: 

[Desktop-packages] [Bug 1667247] Re: NetworkManager stops working until re-run

[gutschke]

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

** This bug has been marked a duplicate of bug 1676810
   Network Manager needs restarting from sleep

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

Title:
  NetworkManager stops working until re-run

Status in network-manager package in Ubuntu:
  New

Bug description:
  after awake from sleep(open my lenovo laptop lid) network manager
  shows - it is connected to one of wi-fi's networks (not mine) -
  switching on\off wifi, networking service doesn't help.

  Here is workaround: 
  ps -Af | grep -i networkmanager (write down the pid)
  sudo kill pid
  sudo /usr/sbin/NetworkManager --no-daemon

  It happens time to time when awake after sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  Uname: Linux 4.4.23-040423-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 23 11:57:58 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
600
  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: Upgraded to xenial on 2016-08-17 (189 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
beeline-198  242d5038-e875-4c07-b0ec-ba6fc4470e24  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1676081] Re: No wifi connection after suspend with a MacBook Pro

[gutschke]

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

** This bug has been marked a duplicate of bug 1676810
   Network Manager needs restarting from sleep

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

Title:
   No wifi connection after suspend with a MacBook Pro

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

Bug description:
  I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug
  should have been fixed in Xenial (see bug 1422143), I lose my wifi
  connection each time I get back from suspend (when opening the lid).

  # Expected behavior:

  Not losing the wifi connection.

  # Actual behavior:

  Wifi connection is lost all the time.

  # Workaround:

  The workaround explained in the comment 50 of the previous bug worked for me:
  https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50

  Side effect: it closes the VPN connection if there was one.

  # Note:

  I've been advised to create a new bug for this (see
  https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63)

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

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

[Desktop-packages] [Bug 1679323] Re: Drop xserver-xorg-video-freedreno from the archive

[Timo Aaltonen]

** Summary changed:

- Drop freedreno from the archive
+ Drop xserver-xorg-video-freedreno from the archive

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

Title:
  Drop xserver-xorg-video-freedreno from the archive

Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-freedreno package in Ubuntu:
  New

Bug description:
  Freedreno driver should be removed, with xserver 1.19 the builtin
  modesetting driver should be used instead.

  http://bloggingthemonkey.blogspot.co.uk/2016/11/a-quick-note-for-
  usersdistros.html

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

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

[Desktop-packages] [Bug 1676810] Re: Network Manager needs restarting from sleep

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network Manager needs restarting from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Each time my laptop is suspended and resumed, Network Manager seems
  unable to bring up Wifi.

  Calling...

  sudo service network-manager restart

  ...resolves the problem.

  I therefore placed the attached file at...

  /lib/systemd/system-sleep/network-manager

  ...which provides a workaround for the problem. However, there must be
  some kind of underlying bug in network-manager which requires it to be
  restarted after every suspend/resume cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Mar 28 10:21:35 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp1s0  proto static  metric 600 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.1.203  
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
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 ac7e4d66-b979-41de-b4b2-6f7c5dffc232  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp1s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Kitchen 2   937ae07a-fb47-46ac-91a4-0fe200203a95  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1679323] [NEW] Drop xserver-xorg-video-freedreno from the archive

[Timo Aaltonen]

Public bug reported:

Freedreno driver should be removed, with xserver 1.19 the builtin
modesetting driver should be used instead.

http://bloggingthemonkey.blogspot.co.uk/2016/11/a-quick-note-for-
usersdistros.html

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

** Affects: xserver-xorg-video-freedreno (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  Drop xserver-xorg-video-freedreno from the archive

Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-freedreno package in Ubuntu:
  New

Bug description:
  Freedreno driver should be removed, with xserver 1.19 the builtin
  modesetting driver should be used instead.

  http://bloggingthemonkey.blogspot.co.uk/2016/11/a-quick-note-for-
  usersdistros.html

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

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

[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.3

[Joseph Yasi]

Any reason libx11 wasn't bumped for zesty this? 1.6.4 has some security
fixes.

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
  - qemu (QXL)

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

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

[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[utklasad]

Fixed the no sound headphone issue for my Dell XPS 9560 by running this
in the terminal:

alsactl restore

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1296966] Re: Displays: Can't modify UI scale slide with keyboard

[Anton Keks]

Maybe it would be better to apply the change together with display
resolution instead of applying on the fly. I personally have trouble
moving the slider correctly to the right position each time after I
change resolution.

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

Title:
  Displays: Can't modify UI scale slide with keyboard

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

Bug description:
  It should be possible to modify the UI Scale slider using the
  keyboard.

  To reproduce:
  1) Launch the Displays control panel
  2) Click the thumb/handle in the UI scale slider once, to select it. Notice 
that the handle gets an orange border, to indicate that it's selected
  3) Press the left/right arrow keys to modify the UI scale

  Expected results:
  The UI scale slider responds to the arrow keys

  Actual results:
  Nothing happens when you use the keyboard to manipulate the UI scale slider

  This is an accessibility issue. It's also a problem if you set the UI
  scale so big that the UI scale widget is no longer drawn onscreen -
  you can't use keyboard navigation to reset it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 24 17:40:33 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (111 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2
   gnome-control-center 1:3.6.3-0ubuntu54

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

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

[Desktop-packages] [Bug 1679307] Re: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all

[utklasad]

Possible duplicate:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801

I've been trying to fix this issue for hours. Now I got the sound
working by running this in the terminal:

sactl restore

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

Title:
  [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My speakers are working on my Dell XPS 15 9560. But when I connect
  headphones to the computer there is no sound at all. Tried different
  headphones that should work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  klas   2471 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr  3 22:44:05 2017
  InstallationDate: Installed on 2017-03-22 (12 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/controlC0:  klas   2471 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1679307] Re: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all

[utklasad]

typo last comment...

alsactl restore

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

Title:
  [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My speakers are working on my Dell XPS 15 9560. But when I connect
  headphones to the computer there is no sound at all. Tried different
  headphones that should work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  klas   2471 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr  3 22:44:05 2017
  InstallationDate: Installed on 2017-03-22 (12 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/controlC0:  klas   2471 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1679313] [NEW] There should be a downscale mirror mode in Displays for HiDPI laptops

[Anton Keks]

Public bug reported:

Both OSX and Windows 10 with HiDPI laptops default to downscaled mirror
for LoDPI external monitors/projectors.

Xrandrs is also able to do that, but you cannot do this with Displays
preferences GUI in Ubuntu.


Currently Displays offers only the lowest common resolutions in mirror mode, 
but it should also offer the scaled mode for the external screen or maybe even 
both options: 'Scale external' and 'Scale built-in'.

This does the trick for my laptop:
xrandr --output eDP-1 --auto --output DP-1 --auto --same-as eDP-1 --scale-from 
3200x1800

(assuming eDP-1 is built-in display and DP-1 is external lower-dpi
screen, which is almost always the case for HiDPI laptops nowadays)

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

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

Title:
  There should be a downscale mirror mode in Displays for HiDPI laptops

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

Bug description:
  Both OSX and Windows 10 with HiDPI laptops default to downscaled
  mirror for LoDPI external monitors/projectors.

  Xrandrs is also able to do that, but you cannot do this with Displays
  preferences GUI in Ubuntu.

  
  Currently Displays offers only the lowest common resolutions in mirror mode, 
but it should also offer the scaled mode for the external screen or maybe even 
both options: 'Scale external' and 'Scale built-in'.

  This does the trick for my laptop:
  xrandr --output eDP-1 --auto --output DP-1 --auto --same-as eDP-1 
--scale-from 3200x1800

  (assuming eDP-1 is built-in display and DP-1 is external lower-dpi
  screen, which is almost always the case for HiDPI laptops nowadays)

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

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

[Desktop-packages] [Bug 1528297] Re: libvpx FTBFS with gcc 5.3 on armhf

[Mattia Rizzolo]

libvpx just builds now, so this is fixed.

** Changed in: libvpx (Ubuntu)
   Status: New => Fix Released

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

Title:
  libvpx FTBFS with gcc 5.3 on armhf

Status in firefox package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Invalid
Status in libvpx package in Ubuntu:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Fix Released

Bug description:
  (originally reported as bug #1527741)

  Trying to build libvpx from source in an up-to-date xenial arhmf
  environment, with gcc 5.3.1, fails with the following error:

  gcc  -marm -Wall -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -march=armv6 -DNDEBUG -O2 -fPIC -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=0 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall 
-Wdeclaration-after-statement -Wdisabled-optimization -Wpointer-arith 
-Wtype-limits -Wcast-qual -Wvla -Wimplicit-function-declaration -Wuninitialized 
-Wunused-variable -Wunused-but-set-variable -Wno-unused-function -I. 
-I"/tmp/libvpx-1.4.0" -c -o vp8/common/treecoder.c.o 
/tmp/libvpx-1.4.0/vp8/common/treecoder.c
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'tree2tok':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:9: error: invalid use of array 
with unspecified bounds
   const vp8_tree_index j = t[i++];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:34: warning: initialization makes 
integer from pointer without a cast [-Wint-conversion]
   const vp8_tree_index j = t[i++];
^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'branch_counts':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:13: error: invalid use of array 
with unspecified bounds
   i = tree[ i + b];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:15: warning: assignment makes 
integer from pointer without a cast [-Wint-conversion]
   i = tree[ i + b];
 ^
  Makefile:148: recipe for target 'vp8/common/treecoder.c.o' failed

  
  I’m attaching a full build log. This is reproducible both on a porter box and 
in a armhf chroot.

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

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

[Desktop-packages] [Bug 1679310] [NEW] Default scale factor for common resolutions needed

[Anton Keks]

Public bug reported:

Currently you are always in trouble when trying to connect a LoDPI
projector to a HiDPI laptop.

If e.g. scale of 2 was chosen for laptop and then you connect an
external LoDPI screen and select mirror, all the controls stay huge, but
the scale should go down to 1 by default to avoid dealing with huge
windows, which don't even fit on the screen.

Moreover, when external mirrored screen is disconnected, scale should be
restored to 2 automatically to avoid user trying to find the tiny scale
slider on a HiDPI screen.

There should be reasonable default scales for common screens also out of the 
box.
Right now, starting Ubuntu on 3200x1800 13" laptop has the initial scale of 1, 
forcing the user to find the scaling slider and operate it while it is 2mm big.

$ xrandr
Screen 0: minimum 320 x 200, current 3200 x 1800, maximum 8192 x 8192
eDP-1 connected primary 3200x1800+0+0 (normal left inverted right x axis y 
axis) 294mm x 165mm

This info should be enough to set scale=2 by default, and reset scale to
1 when resolution is 1920x1080 and below.

The problem is there with both 16.10 and 17.04

unity-control-center:
  Installed: 15.04.0+17.04.20170402.6-0ubuntu1

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

** Summary changed:

- Default scale factor should for common resolutions needed
+ Default scale factor for common resolutions needed

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

Title:
  Default scale factor for common resolutions needed

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

Bug description:
  Currently you are always in trouble when trying to connect a LoDPI
  projector to a HiDPI laptop.

  If e.g. scale of 2 was chosen for laptop and then you connect an
  external LoDPI screen and select mirror, all the controls stay huge,
  but the scale should go down to 1 by default to avoid dealing with
  huge windows, which don't even fit on the screen.

  Moreover, when external mirrored screen is disconnected, scale should
  be restored to 2 automatically to avoid user trying to find the tiny
  scale slider on a HiDPI screen.

  There should be reasonable default scales for common screens also out of the 
box.
  Right now, starting Ubuntu on 3200x1800 13" laptop has the initial scale of 
1, forcing the user to find the scaling slider and operate it while it is 2mm 
big.

  $ xrandr
  Screen 0: minimum 320 x 200, current 3200 x 1800, maximum 8192 x 8192
  eDP-1 connected primary 3200x1800+0+0 (normal left inverted right x axis y 
axis) 294mm x 165mm

  This info should be enough to set scale=2 by default, and reset scale
  to 1 when resolution is 1920x1080 and below.

  The problem is there with both 16.10 and 17.04

  unity-control-center:
Installed: 15.04.0+17.04.20170402.6-0ubuntu1

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

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

[Desktop-packages] [Bug 1679307] [NEW] [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all

[utklasad]

Public bug reported:

My speakers are working on my Dell XPS 15 9560. But when I connect
headphones to the computer there is no sound at all. Tried different
headphones that should work.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  klas   2471 F pulseaudio
CurrentDesktop: Unity
Date: Mon Apr  3 22:44:05 2017
InstallationDate: Installed on 2017-03-22 (12 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
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/controlC0:  klas   2471 F pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My speakers are working on my Dell XPS 15 9560. But when I connect
  headphones to the computer there is no sound at all. Tried different
  headphones that should work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  klas   2471 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr  3 22:44:05 2017
  InstallationDate: Installed on 2017-03-22 (12 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/controlC0:  klas   2471 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1678622] Re: Libreoffice copy paste doesn't copy calculations

[Cliff Carson]

Tried many times to reproduce this problem since my last append and it
did come back.  There are three methods to copy/paste.  Using
ctl-c/ctl-v, the copy/paste icons, and the edit pull-down.  Each method
results in the same failure.  I mark a number of cells to be copied, do
the copy, move to a target cell, and then paste.  Every time when this
is failing I get an "Import Text" menu box.  Entering OK to this box
copies only the text information not any calculations.  This box should
not come up.  If I mark cells, copy, copy (using any of the three
methods), then paste the operation works correctly (no "Import Text" box
displayed).

I don't know what to try next to document this failure.  Any
suggestions?

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

Title:
  Libreoffice copy paste doesn't copy calculations

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When doing a copy/paste of rows only the text information is copied (a
  "Text Import" dialog box is displayed which normally wasn't before).
  If the copy/paste operation is repeated than the text and calculations
  are copied.  In fact if the copy (ctl-c) is hit twice and then the
  paste (ctl-v) the operation works correctly.  Using the Copy/Paste
  icons shows the same incorrect behavior.

  ii  libreoffice-calc1:5.3.1-0ubunt amd64  office
  productivity suite -- spreadsheet

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-calc 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr  2 10:05:34 2017
  InstallationDate: Installed on 2017-02-13 (47 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1679305] [NEW] /usr/lib/libreoffice/program/soffice.bin:11:Menu::Deactivate:MenuFloatingWindow::KillActivePopup:ImplSchedulerData::Invoke:ImplSchedulerData::Invoke:Scheduler::P

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
libreoffice.  This problem was most recently seen with package version 
1:5.1.6~rc2-0ubuntu1~xenial1, the problem page at 
https://errors.ubuntu.com/problem/6539b8da718c505ada4b8968a984aed1022eb572 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: wily xenial

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:Menu::Deactivate:MenuFloatingWindow::KillActivePopup:ImplSchedulerData::Invoke:ImplSchedulerData::Invoke:Scheduler::ProcessTaskScheduling

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
libreoffice.  This problem was most recently seen with package version 
1:5.1.6~rc2-0ubuntu1~xenial1, the problem page at 
https://errors.ubuntu.com/problem/6539b8da718c505ada4b8968a984aed1022eb572 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1678397] Re: "privacy > screen lock > disable" does not work

[Brian Murray]

** Tags added: yakkety

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

Title:
  "privacy > screen lock > disable" does not work

Status in lightdm package in Ubuntu:
  New

Bug description:
  System:
  ubuntu 16.10 (also occurred at 14.10, 15.04, 15.10 and 16.04)
  GNOME desktop
  nvidia-370 (also occurred with all recend nvidia drivers during last two 
years)
  2 monitors

  condition:
  "settings > privacy > screen lock -- set to "disable"

  expected behaviour:
  after resume from suspend, my applications immediately are available

  behaviour as it is:
  monitors power up
  my applications are available for a second 
  monitors power off 
  monitors power up again
  password prompt

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

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

[Desktop-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)

[Christopher Townsend]

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: xmir

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of
  native GTK/Qt (and so menus don't appear in the titlebar)

Status in Canonical System Image:
  Confirmed
Status in Libertine:
  In Progress
Status in Libertine devel series:
  In Progress
Status in Libertine trunk series:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in libertine package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Qt & GTK apps on Unity8 are defaulting to Xmir instead of native
  GTK/Qt on Mir.

  I noticed a slight change in appearance and performance, but also:

  dan  25410  0.1  0.2 423316 38996 ?Sl   11:14   0:00 Xmir 
-rootless -displayfd 3 -mir org.gnome.Calculator
  dan  25456  1.8  0.5 606084 91736 ?Sl   11:14   0:03 Xmir 
-rootless -displayfd 3 -mir org.gnome.Nautilus
  dan  25611  1.7  0.2 345312 35520 ?Sl   11:18   0:00 Xmir 
-rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10

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

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

[Desktop-packages] [Bug 1636666] Re: [MIR] pcre2

[Mathieu Trudel-Lapierre]

** Changed in: pcre2 (Ubuntu)
Milestone: ubuntu-17.03 => ubuntu-17.05

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

Title:
  [MIR] pcre2

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in pcre2 package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Availability
  
  Synced with Debian. Built for all supported architectures.

  Rationale
  =
  Required by gnome-terminal 3.22+ and vte2.91 0.46+

  Security
  
  At least one open security issue, affecting Ubuntu 16.04 LTS
  https://people.canonical.com/~ubuntu-security/cve/pkg/pcre2.html
  https://security-tracker.debian.org/tracker/source-package/pcre2
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop Bugs or Ubuntu Foundation Bugs (like pcre3) 
to this package.
  https://bugs.launchpad.net/ubuntu/+source/pcre2
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pcre2

  Upstream tests are run during the build but there is no autopkgtest

  Does not have 3.0 (quilt) set

  Dependencies
  
  Only build-dependencies are dpkg and debhelper. No other added dependencies.

  Standards compliance
  
  3.9.6

  Maintenance
  ===
  - Actively developed upstream
  http://pcre.org/

  Background information
  ==
  As the package description states, the older version of this library is 
confusingly named pcre3 in Debian/Ubuntu. pcre3 is already in Ubuntu main.

  Other Info
  ==
  In the original release of pcre2 in Jan 2015, the author says this is not 
just a drastic update to the original pcre but a "new project". He felt free to 
change names and options.
  https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html

  pcre3 has gotten some bugfix releases since then (from 8.36 to 8.40
  released Jan 2017)

  Some discussion of how it's different:
  http://www.regular-expressions.info/pcre2.html

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

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

[Desktop-packages] [Bug 1679255] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

[Daniel Holbach]

Public bug reported:

No idea what happened.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: cracklib-runtime 2.9.2-3
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Mon Apr  3 18:57:12 2017
ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
InstallationDate: Installed on 2015-04-30 (703 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: cracklib2
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
UpgradeStatus: Upgraded to zesty on 2017-04-03 (0 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade:
  Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  No idea what happened.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Apr  3 18:57:12 2017
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2015-04-30 (703 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: cracklib2
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to zesty on 2017-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Khairul Aizat Kamarudzzaman]

yeah, we are more than happy to test the fixes. Can't wait for the PPA,
hope it will land in Zesty as well ..

Kind Regards,
ejat @ fenris

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1021375] Re: Nautilus says the USB stick is read only when it is not

[Jan Pischel]

I observe a variant of this bug in Ubuntu 16.04 LTS 64-bit
(4.4.0-71-generic #92-Ubuntu): In Nautilus 3.14.3, an auto-mounted
partition on a local drive is read-only (no issues before, nothing
changed with the system (hardware) configuration). In addition, if I
open files with apps (gedit, ...) from Nautilus by double click, I
cannot save changes.

The variant is this: Even if I use now the terminal, the drive is read-
only (I cannot create files -- touch: cannot touch 'test.txt': Read-only
file system -- or save changes when editing files).

Workaround: I can still change content using the terminal or Krusader by
remounting the partition, i.e.

sudo mount -o remount,rw '/media//

However, as soon as I go to the mount directory in Nautilus, it seems to
be read-only again, so no chance to change contents. It looks to me like
Nautilus really changes actively the information of the mounted drive.

Please let me know if you need further information to debug. I agree to
previous users that this bug is really annoying, especially since
nothing seems to happen for now almost FIVE YEARS!

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

Title:
  Nautilus says the USB stick is read only when it is not

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is 

[Desktop-packages] [Bug 1679209] Re: SDL video init unreliable with xvfb 1.19 on qemu

[Launchpad Bug Tracker]

This bug was fixed in the package onscripter - 20161102-1ubuntu1

---
onscripter (20161102-1ubuntu1) zesty; urgency=medium

  * tests: Don't use xvfb, instead force the dummy SDL videodriver so
that racy SDL init won't fail the tests on qemu. (LP: #1679209)

 -- Timo Aaltonen   Mon, 03 Apr 2017 17:43:15 +0300

** Changed in: onscripter (Ubuntu)
   Status: New => Fix Released

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

Title:
  SDL video init unreliable with xvfb 1.19 on qemu

Status in onscripter package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New

Bug description:
  forked from 1671799

  Onscripter autopkgtests use xvfb to run some scripted tests.
  Onscripter itself initializes SDL, and this is somewhat unreliable on
  a qemu instance where the X11 connection can fail, especially if Xvfb
  is started via xvfb-run. The tests don't need X11, instead it can use
  the dummy driver which is enough for running the tests.

  
  The actual bug remains, 1.19 is for some reason unreliable for SDL where 1.18 
wasn't. This will be reported upstream, as it can be reproduced on Debian as 
well. Real hw is less likely to hit this, much easier to reproduce with qemu.

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

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

[Desktop-packages] [Bug 1217585] Re: System hangs after some time with nouveau and GT240

[Bob H]

This has been affecting my installation routines for a number of versions of 
Kubuntu now.
I found a workaround that involves temporarily disabling nouveau until nvidia 
drivers can be installed:

Boot from the Ubuntu installation media.
When the boot menu appears : Highlight Try Ubuntu without installing and press 
the E key.
Add the nouveau.modeset=0 parameter to the end of the linux line ... Then press 
F10 to boot.
Having entered the desktop start the installation process, once completed 
restart the PC.
Again.
When the GRUB boot menu appears : Highlight the Ubuntu menu entry and press the 
E key.
Add the nouveau.modeset=0 parameter to the end of the linux line ... Then press 
F10 to boot.
Now install the latest official NVIDIA drivers.

This is a bug that needs to be addressed. Anyone new to *ubuntu who
encounters this would assume that installation is impossible, even using
the Live Disk has become a problem.

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

Title:
  System hangs after some time with nouveau and GT240

Status in Nouveau Xorg driver:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1569970] Re: Nautilus does not start

[Alberto Salvia Novella]

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

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Nautilus does not start

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  when opening nautilus i get the following errors:

  
  lotuspsychje@R00TBOOK:~$ nautilus

  (nautilus:9475): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  (nautilus:9475): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: 
assertion 'interface_->priv->connections != NULL' failed
  Kon de toepassing niet registreren: Tijd is verlopen

  (nautilus:9475): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:9475): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:9475): GLib-GObject-CRITICAL **: g_signal_connect_object:
  assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

  
  gksu nautilus opens nautilus, but also with an error:

  
  lotuspsychje@R00TBOOK:~$ gksu nautilus

  (nautilus:10257): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 13 17:22:53 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'confirm-trash' b'false'
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.preferences' b'enable-delete' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+0+24'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2016-04-04 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2016-04-05T06:03:34.591882

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

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

[Desktop-packages] [Bug 1679226] [NEW] gedit consumes 100% of cpu when left minimised

[Kevin Selva Prasanna]

Public bug reported:

When left minimised, gedit on ubuntu takes up 30 to 50% of CPU. When I
maximise it to use it again, the CPU usage drops to zero. I tried
purging and reinstalling gedit many times. But it doesn't help. The
issue starts a few seconds after opening gedit. But the issue is so
serious, that I cannot use it more than a few seconds without heating up
my computer.

OS
==
Description:Ubuntu 16.04.2 LTS

INSTALLED VERSION
=
gedit:
  Installed: 3.18.3-0ubuntu4

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

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

Title:
  gedit consumes 100% of cpu when left minimised

Status in gedit package in Ubuntu:
  New

Bug description:
  When left minimised, gedit on ubuntu takes up 30 to 50% of CPU. When I
  maximise it to use it again, the CPU usage drops to zero. I tried
  purging and reinstalling gedit many times. But it doesn't help. The
  issue starts a few seconds after opening gedit. But the issue is so
  serious, that I cannot use it more than a few seconds without heating
  up my computer.

  OS
  ==
  Description:  Ubuntu 16.04.2 LTS

  INSTALLED VERSION
  =
  gedit:
Installed: 3.18.3-0ubuntu4

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

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

[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[rooijan]

Maybe if helpful to someone else quickest way for me to work around it
is kill the dnsmasq process.  When it restarts itself DNS over VPN is
working.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

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

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1648534] Re: /usr/bin/gnome-software:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_cal

[Will Cooke]

Still the biggest cause of problems on errors.u.c.

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

Title:
  /usr/bin/gnome-
  
software:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_sync

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at 
https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1677327] Re: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]

[Alberto Milone]

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided => High

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  dkms build fails with zesty hwe kernel [error: too few arguments to
  function ‘NV_GET_USER_PAGES’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  In Progress

Bug description:
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

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

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

[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

something in 1.19 makes SDL video init unreliable, causing onscripter
autopkgtest to fail when run on qemu.. this issue is now monitored on
bug 1679209

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
  - qemu (QXL)

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

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

[Desktop-packages] [Bug 1666912] Re: Invoking openvpn removed option --tls-remote

[Mathieu Trudel-Lapierre]

This patch should not be applied as-is; as Chris mentions, the correct
thing to do is to modify the settings in the VPN connection.

A valid workaround for n-m-openvpn would require also modifying either
the value entered in the dialog to strip out part of the value (anything
up and including "CN=") and keeping 'name' as the piece to validate via
verify-x509-name; or using "subject" instead, and requiring the use of a
fully-formed DN in the dialog.

I think this should be "Won't Fix". It's unfortunate that we are stuck
dealing with this fallout in the release, but there doesn't appear to be
a foolproof way to transition configs (what is used for "tls-remote"
currently is arbitrary, and can vary between installations).

** Tags added: patch-needswork

** Changed in: network-manager-openvpn (Ubuntu Zesty)
   Status: In Progress => Incomplete

** Changed in: network-manager-openvpn (Ubuntu Zesty)
   Status: Incomplete => Triaged

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

Title:
  Invoking openvpn removed option --tls-remote

Status in network-manager-openvpn package in Ubuntu:
  Triaged
Status in network-manager-openvpn source package in Zesty:
  Triaged
Status in network-manager-openvpn package in Debian:
  Fix Released

Bug description:
  Upgrading to the latest openvpn breakes already configured VPN
  connections.

  Steps to reproduce:
  1. Import an OpenVPN connection via NetworkManager with the tls-remote option 
used.
  2. Try to connect to VPN.

  Expected result:
  VPN connection is established.

  Actual result:
  (from syslog)
  Feb 22 14:54:48 hostname NetworkManager[8593]: Options error: Unrecognized 
option or missing or extra parameter(s) in [CMD-LINE]:1: tls-remote (2.4.0)
  Feb 22 14:54:48 hostname NetworkManager[8593]: Use --help for more 
information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 15:06:53 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-30 (329 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2016-10-30 (115 days ago)

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

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

[Desktop-packages] [Bug 1679209] [NEW] SDL video init unreliable with xvfb 1.19 on qemu

[Timo Aaltonen]

Public bug reported:

forked from 1671799

Onscripter autopkgtests use xvfb to run some scripted tests. Onscripter
itself initializes SDL, and this is somewhat unreliable on a qemu
instance where the X11 connection can fail, especially if Xvfb is
started via xvfb-run. The tests don't need X11, instead it can use the
dummy driver which is enough for running the tests.


The actual bug remains, 1.19 is for some reason unreliable for SDL where 1.18 
wasn't. This will be reported upstream, as it can be reproduced on Debian as 
well. Real hw is less likely to hit this, much easier to reproduce with qemu.

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

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

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

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

Title:
  SDL video init unreliable with xvfb 1.19 on qemu

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

Bug description:
  forked from 1671799

  Onscripter autopkgtests use xvfb to run some scripted tests.
  Onscripter itself initializes SDL, and this is somewhat unreliable on
  a qemu instance where the X11 connection can fail, especially if Xvfb
  is started via xvfb-run. The tests don't need X11, instead it can use
  the dummy driver which is enough for running the tests.

  
  The actual bug remains, 1.19 is for some reason unreliable for SDL where 1.18 
wasn't. This will be reported upstream, as it can be reproduced on Debian as 
well. Real hw is less likely to hit this, much easier to reproduce with qemu.

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

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

[Desktop-packages] [Bug 1557346] Re: Xorg crashed with SIGABRT in OsAbort()

[Timo Aaltonen]

** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I think this crash was after a resume (suspended just after removing a
  DisplayLink device)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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
  Date: Mon Mar 14 23:45:43 2016
  DistUpgraded: 2016-02-26 13:01:01,567 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:15a7]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2012-12-20 (1180 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUSTeK COMPUTER INC. UX51VZA
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=/dev/mapper/ubuntu-root ro pcie_aspm=force drm.vblankoffdelay=1 
i915.semaphores=1 nmi_watchdog=0 "acpi_osi=!Windows 2012"
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (17 days ago)
  UserGroups:
   
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX51VZA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX51VZA
  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.:bvrUX51VZA.204:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnUX51VZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX51VZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Mar 14 23:46:00 2016
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 803 
   vendor LGD
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Desktop-packages] [Bug 1675705] Re: unknown file system type zfs_member

[Phillip Susi]

** Package changed: util-linux (Ubuntu) => udisks2 (Ubuntu)

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

Title:
  unknown file system type zfs_member

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Hi,

  I'm happy to see that there is some progress about automounting
  removable devices with zfs, but when I plug in a pendrive with zfs, I
  still get the error message

  Error mounting /dev/dm-2 at /media/danisch/sync2: Command-line `mount
  -t "zfs_member" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-2"
  "/media/danisch/sync2"' exited with non-zero exit status 32: mount:
  unknown filesystem type 'zfs_member'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 10:20:03 2017
  InstallationDate: Installed on 2016-04-22 (335 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (158 days ago)

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

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

[Desktop-packages] [Bug 1675705] [NEW] unknown file system type zfs_member

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi,

I'm happy to see that there is some progress about automounting
removable devices with zfs, but when I plug in a pendrive with zfs, I
still get the error message

Error mounting /dev/dm-2 at /media/danisch/sync2: Command-line `mount -t
"zfs_member" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-2"
"/media/danisch/sync2"' exited with non-zero exit status 32: mount:
unknown filesystem type 'zfs_member'

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: mount 2.28.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 24 10:20:03 2017
InstallationDate: Installed on 2016-04-22 (335 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: util-linux
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (158 days ago)

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


** Tags: amd64 apport-bug yakkety
-- 
unknown file system type zfs_member
https://bugs.launchpad.net/bugs/1675705
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to udisks2 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 1627290] Re: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox

[John Dennis]

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

it affects me too.

ubuntu 16.04.2 LTS,ubufox  3.2 with firefox 52.0.2

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

Title:
  Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox

Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Firefox 49+ enables e10s by default:

  https://wiki.mozilla.org/Electrolysis

  
  But Ubuntu's "Ubuntu Modifications 3.2" extension disables it. In 
about:support output it says:

  "Multiprocess Windows 0/1 (Disabled by add-ons)"

  
  If we manually disable "Ubuntu Modifications" extension, it works:

  "Multiprocess Windows 1/1 (Enabled by default)"

  
  I am using Xubuntu 16.04, firefox 49.0+build4-0ubuntu0.16.04.1, 
xul-ext-ubufox 3.2-0ubuntu1.

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

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

[Desktop-packages] [Bug 1676973] Re: systemd-resolved fails to use non-dnssec caches

[Bruce Duncan]

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

** No longer affects: libreoffice (Ubuntu)

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

Title:
  systemd-resolved fails to use non-dnssec caches

Status in systemd:
  New

Bug description:
  Upgraded to Kubuntu 17.10 beta 2 today.

  On logging in I was unable to connect to any network services. I
  discovered that any DNS lookups returned SERVFAIL. It seems the caches
  being used in my university don't support DNSSEC yet and, despite the
  systemd-resolved man page saying that DNSSEC=allow-downgrade (the
  default) will allow me to use caches which don't support DNSSEC, I had
  to explicitly specify DNSSEC=off and restart systemd-resolved.

  I can reproduce the bug trivially by changing the
  /etc/systemd/resolved.conf DNSSEC= setting back to the default and
  trying a DNS lookup.

  :) bduncan@fry:~$ apt-cache policy systemd
  systemd:
Installed: 232-19
Candidate: 232-19
Version table:
   *** 232-19 500
  500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  :) bduncan@fry:~$ lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  Hope this helps,
  Bruce

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

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

[Desktop-packages] [Bug 1679184] Re: LVM configuration cannot be removed when volume groups with the same name are found during installation

[Frank Heimes]

** Package changed: llvm-toolchain-3.5 (Ubuntu) => lvm2 (Ubuntu)

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

Title:
  LVM configuration cannot be removed when volume groups with the same
  name are found during installation

Status in Ubuntu on IBM z Systems:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Installer version: 20101020ubuntu500

  Kernel: 4.10.0-14

  Description/Reproduction:

  During installation, the installer finds LVM volume groups from a
  previous installation.

  Current LVM configuration:
   Unallocated physical volumes:
 * /dev/mapper/mpatha2  (21218MB)
  
   Volume groups:   
 * rootVG   (21218MB)
   - Uses physical volume: /dev/dasda2  (21315MB)
   - Uses physical volume: /dev/mapper/mpathc1  (21470MB)
   - Uses physical volume: [unknown](21470MB)
   - Uses physical volume: [unknown](21470MB)
 * rootVG   (21470MB)
   - Uses physical volume: /dev/dasda2  (21315MB)
   - Uses physical volume: /dev/mapper/mpathc1  (21470MB)
   - Uses physical volume: [unknown](21470MB)
   - Uses physical volume: [unknown](21470MB)
 * rootvg   (42685MB)
   - Uses physical volume: /dev/mapper/mpathb1  (21470MB)
   - Uses physical volume: [unknown](214

  When trying to remove that LVM using "Configure the Logical Volume
  Manager", it is not possible to remove logical volumes. The error "The
  logical volume swapLV on rootVG could not be deleted." is displayed.
  In syslog, you see the following messages:

  Apr  3 12:55:56 partman-lvm:   Multiple VGs found with the same name: 
skipping rootVG
  Apr  3 12:55:56 partman-lvm:   Use --select vg_uuid= in place of the VG 
name.

  As you cannot use the suggested parameter in the installer, the system
  cannot be installed without manually removing the LVM setup with
  another shell.

  Debug logs are attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679184/+subscriptions

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

[Desktop-packages] [Bug 1677327] Re: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]

[Alberto Milone]

I've just found out that the patch for Linux 4.9 in xenial is not the
same as the one in zesty. I'll have to refresh that.

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

Title:
  dkms build fails with zesty hwe kernel [error: too few arguments to
  function ‘NV_GET_USER_PAGES’]

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

Bug description:
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

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

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

[Desktop-packages] [Bug 1639656] Re: Ubuntu version in Details (in System Settings) says 16.10 not 17.04

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+17.04.20170402.6-0ubuntu1

---
unity-control-center (15.04.0+17.04.20170402.6-0ubuntu1) zesty; urgency=medium

  [ Robert Ancell ]
  * Update system information logo for Zesty Zapus (LP: #1639656)

 -- Jeremy Bicha   Sun, 02 Apr 2017 19:07:55 +

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

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

Title:
  Ubuntu version in Details (in System Settings) says 16.10 not 17.04

Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu version in the Details section of System Settings reads
  16.10 when it should read 17.04.

  I reported this for Ubuntu 16.10 too, was fixed promptly!
  https://bugs.launchpad.net/ubuntu/+source/unity-control-
  center/+bug/1581192

  Computer info:
  VirtualBox Graphical User Interface Version 5.1.6_Ubuntu r110634
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.10 64-bit
  Lenovo ThinkPad X201

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+16.10.20161003.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  7 00:03:12 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-10-10 (27 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2016-11-06 (0 days ago)

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

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

[Desktop-packages] [Bug 1679184] syslog, partman log, hardware-summary

[bugproxy]

Default Comment by Bridge

** Attachment added: "syslog, partman log, hardware-summary"
   https://bugs.launchpad.net/bugs/1679184/+attachment/4853576/+files/logs.tar

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => llvm-toolchain-3.5 (Ubuntu)

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

Title:
  LVM configuration cannot be removed when volume groups with the same
  name are found during installation

Status in llvm-toolchain-3.5 package in Ubuntu:
  New

Bug description:
  Installer version: 20101020ubuntu500

  Kernel: 4.10.0-14

  Description/Reproduction:

  During installation, the installer finds LVM volume groups from a
  previous installation.

  Current LVM configuration:
   Unallocated physical volumes:
 * /dev/mapper/mpatha2  (21218MB)
  
   Volume groups:   
 * rootVG   (21218MB)
   - Uses physical volume: /dev/dasda2  (21315MB)
   - Uses physical volume: /dev/mapper/mpathc1  (21470MB)
   - Uses physical volume: [unknown](21470MB)
   - Uses physical volume: [unknown](21470MB)
 * rootVG   (21470MB)
   - Uses physical volume: /dev/dasda2  (21315MB)
   - Uses physical volume: /dev/mapper/mpathc1  (21470MB)
   - Uses physical volume: [unknown](21470MB)
   - Uses physical volume: [unknown](21470MB)
 * rootvg   (42685MB)
   - Uses physical volume: /dev/mapper/mpathb1  (21470MB)
   - Uses physical volume: [unknown](214

  When trying to remove that LVM using "Configure the Logical Volume
  Manager", it is not possible to remove logical volumes. The error "The
  logical volume swapLV on rootVG could not be deleted." is displayed.
  In syslog, you see the following messages:

  Apr  3 12:55:56 partman-lvm:   Multiple VGs found with the same name: 
skipping rootVG
  Apr  3 12:55:56 partman-lvm:   Use --select vg_uuid= in place of the VG 
name.

  As you cannot use the suggested parameter in the installer, the system
  cannot be installed without manually removing the LVM setup with
  another shell.

  Debug logs are attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1679184/+subscriptions

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

[Desktop-packages] [Bug 1679184] [NEW] LVM configuration cannot be removed when volume groups with the same name are found during installation

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Installer version: 20101020ubuntu500

Kernel: 4.10.0-14

Description/Reproduction:

During installation, the installer finds LVM volume groups from a
previous installation.

Current LVM configuration:
 Unallocated physical volumes:
   * /dev/mapper/mpatha2  (21218MB)

 Volume groups:   
   * rootVG   (21218MB)
 - Uses physical volume: /dev/dasda2  (21315MB)
 - Uses physical volume: /dev/mapper/mpathc1  (21470MB)
 - Uses physical volume: [unknown](21470MB)
 - Uses physical volume: [unknown](21470MB)
   * rootVG   (21470MB)
 - Uses physical volume: /dev/dasda2  (21315MB)
 - Uses physical volume: /dev/mapper/mpathc1  (21470MB)
 - Uses physical volume: [unknown](21470MB)
 - Uses physical volume: [unknown](21470MB)
   * rootvg   (42685MB)
 - Uses physical volume: /dev/mapper/mpathb1  (21470MB)
 - Uses physical volume: [unknown](214

When trying to remove that LVM using "Configure the Logical Volume
Manager", it is not possible to remove logical volumes. The error "The
logical volume swapLV on rootVG could not be deleted." is displayed. In
syslog, you see the following messages:

Apr  3 12:55:56 partman-lvm:   Multiple VGs found with the same name: skipping 
rootVG
Apr  3 12:55:56 partman-lvm:   Use --select vg_uuid= in place of the VG 
name.

As you cannot use the suggested parameter in the installer, the system
cannot be installed without manually removing the LVM setup with another
shell.

Debug logs are attached

** Affects: llvm-toolchain-3.5 (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-153121 severity-medium 
targetmilestone-inin---
-- 
LVM configuration cannot be removed when volume groups with the same name are 
found during installation
https://bugs.launchpad.net/bugs/1679184
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to llvm-toolchain-3.5 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 1631095] Re: pushed dns servers not being used

[Matthew Gregg]

FWIW this seems fixed in 17.04, but a few new issues have been
introduced :-)

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

Title:
  pushed dns servers not being used

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

Bug description:
  After the upgrade from yenial to yakkety, the internal DNS servers
  (pushed by the openvpn server) are not being used by dnsmasq.

  Symptom:

  I connect via openvpn (called from network manager), the connection is
  established successfully but INTERNAL hostnames cannot be resolved.

  The system itself is using dnsmasq.

  I then have to kill the running dnsmasq instance. After it's been
  (automagically) restarted, internal DNS names can be resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager-openvpn 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Oct  6 20:06:33 2016
  InstallationDate: Installed on 2014-02-07 (972 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to yakkety on 2016-10-01 (5 days ago)

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

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

[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.3

[Sampo Savola]

Any news on this, will it make it to the release? IMHO this is very important 
to be included.
Is there somewhere a test image or instructions how to test?

Thanks

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
  - qemu (QXL)

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

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

[Desktop-packages] [Bug 1678687] Re: screen crashes after restore from suspend

[Launchpad Bug Tracker]

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

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

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

Title:
  screen crashes after restore from suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dual screen. after the system being waken from the suspend, a mess
  rectangle appears surrounding any normal window or any pop-up menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Mon Apr  3 10:14:40 2017
  DistUpgraded: 2016-09-08 00:19:31,601 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 745] [10de:1382] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GM107 [GeForce GTX 745] [10de:1065]
  InstallationDate: Installed on 2016-01-10 (448 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. XPS 8700
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=ab94cc99-dabb-4a49-be5e-04ecd7d8954c ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-09-07 (207 days ago)
  dmi.bios.date: 11/22/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/22/2014:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8700
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr  2 19:54:00 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech M705MOUSE, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1678436] Re: Gnome-Software does not install local .deb-files

[Will Cooke]

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

Possible dupe of bug #1672424?

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

Title:
  Gnome-Software does not install local .deb-files

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When trying to install a downloaded .deb-file through double clicking
  in Nautilus Gnome Software is started and offers an "Install"-Button,
  but when it is pressed nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu2
  Uname: Linux 4.8.17-040817-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  1 11:39:49 2017
  InstallationDate: Installed on 2017-03-24 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 269343] Re: "Paste Into Folder" blinked in context menu

[tagelicht]

PS: reinstalling nautilus fixed that bug for me... however, I got it
without doing anything on a fresh installation in the first place...

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

Title:
  "Paste Into Folder" blinked in context menu

Status in gvfs:
  Fix Released
Status in Nautilus:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  If I connect to a ftp account shortcut appear on the desktop. If I
  make a right click with mouse the Paste Into Folder is going to blink
  fast (activated/deactivated) . This happens on Intrepid Ibex Alpha 5.

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

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

[Desktop-packages] [Bug 269343] Re: "Paste Into Folder" blinked in context menu

[tagelicht]

Hi,

im also having this bug (blinking "paste" menu item, when I have copied
certain things (or not copied anyrthing?).

My system is a fully updated Ubuntu 16.04

Well, however I noticed that when the paste button is blinking (Which is
nearly ALL of the time), Nautilus's CPU usage goes up to values as high
as 60% constantly when nautilus is active, so I would recommend
fixing this quickly :((

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

Title:
  "Paste Into Folder" blinked in context menu

Status in gvfs:
  Fix Released
Status in Nautilus:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  If I connect to a ftp account shortcut appear on the desktop. If I
  make a right click with mouse the Paste Into Folder is going to blink
  fast (activated/deactivated) . This happens on Intrepid Ibex Alpha 5.

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

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

[Desktop-packages] [Bug 1678436] Re: Gnome-Software does not install local .deb-files

[Amr Ibrahim]

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

** This bug has been marked a duplicate of bug 1672424
   Cannot install Debian files outside of the repositories

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

Title:
  Gnome-Software does not install local .deb-files

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When trying to install a downloaded .deb-file through double clicking
  in Nautilus Gnome Software is started and offers an "Install"-Button,
  but when it is pressed nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu2
  Uname: Linux 4.8.17-040817-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  1 11:39:49 2017
  InstallationDate: Installed on 2017-03-24 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Louis Bouchard]

Hello,

Le 03/04/2017 à 12:02, Konrad Zapałowicz a écrit :
> Hey, to everyone interested we are currently testing and reviewing an
> improvement to PA that fixes problems with selecting A2DP mode for BT
> headsets.
> 
> Right now it is being tested internally with good results for Sony
> headsets, QC35 from Bose and BT speakers. Once it is in a silo/ppa I
> will share this information for much wider testing. Then it will be
> submitted as a SRU and will land in xenial.
> 

I've been subscribed to this bug for ages & I'm still seeing this issue with my
BT headset so I'd be more than happy to help you tests.

Kind regards,

...Louis

-- 
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer   Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack

[Mohd Imran Jamadar]

** Attachment added: "alsa_mixer_after.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516025/+attachment/4853476/+files/alsa_mixer_after.png

** Tags removed: latest-bios-a09

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

Title:
  Realtek ALC3661 Alienware14 / Soundoutput / Jack

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Unknown

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

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

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

[Desktop-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack

[Mohd Imran Jamadar]

Alsamixer setting before setting the 8. Click on 'Overwrite' on Pin ID
'0x1a'.

9. Click on the Context Menu and select 'Line out (Center/LFE)'.


** Attachment added: "alsamixer_before.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516025/+attachment/4853475/+files/alsamixer_before.png

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

Title:
  Realtek ALC3661 Alienware14 / Soundoutput / Jack

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Unknown

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

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

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

[Desktop-packages] [Bug 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design

[Khurshid Alam]

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

** This bug has been marked a duplicate of bug 1677626
   Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard 
is enabled (Zesty)

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

Title:
  Enabling the onscreen keyboard in the accessibility menu changes
  lockscreen design

Status in Onboard:
  Invalid
Status in Unity:
  Invalid
Status in onboard package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After enabling the onscreen keyboard in the accessibility menu the
  design of the lockscreen is changed to the old design of Ubuntu 13.10
  and earlier.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu4 [modified: 
usr/share/onboard/onboard-defaults.conf]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 21 00:16:10 2014
  InstallationDate: Installed on 2014-04-14 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-14 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413)
  Package: unity
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1677626] Re: Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard is enabled (Zesty)

[Launchpad Bug Tracker]

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

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

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

Title:
  Lock-Screen: Unity falls-back to old screensaver lock if onscreen
  keyboard is enabled (Zesty)

Status in lightdm package in Ubuntu:
  Confirmed
Status in onboard package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Unity falls-back to old lock from gnome-screensaver if accessibility
  is enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen

  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
  3. Restart lightdm or reboot
  4. Press CTRL+ALT+L

  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.

  Expected Behavior:
  
  It should be using new lock-screen

  Severity: High
  ---
  This bug is pretty well hidden. Sometimes when app which depends on-screen 
keyboard (ex: orca) gets updated, it automatically turns on screensaver. It can 
also get turned on if user accidentally press CTRL+ALT+S. User will have no 
clue whats hit him.

  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.

  ⇛ Please fix accessibility for new lock-screen. Thanks

  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)

  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1

  gnome-screensaver: 3.6.1-7ubuntu5

  unity: 7.5.0+17.04.20170301-0ubuntu1

  lightdm: 1.22.0-0ubuntu1

  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1677626] Re: Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard is enabled (Zesty)

[Launchpad Bug Tracker]

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

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

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

Title:
  Lock-Screen: Unity falls-back to old screensaver lock if onscreen
  keyboard is enabled (Zesty)

Status in lightdm package in Ubuntu:
  Confirmed
Status in onboard package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Unity falls-back to old lock from gnome-screensaver if accessibility
  is enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen

  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
  3. Restart lightdm or reboot
  4. Press CTRL+ALT+L

  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.

  Expected Behavior:
  
  It should be using new lock-screen

  Severity: High
  ---
  This bug is pretty well hidden. Sometimes when app which depends on-screen 
keyboard (ex: orca) gets updated, it automatically turns on screensaver. It can 
also get turned on if user accidentally press CTRL+ALT+S. User will have no 
clue whats hit him.

  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.

  ⇛ Please fix accessibility for new lock-screen. Thanks

  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)

  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1

  gnome-screensaver: 3.6.1-7ubuntu5

  unity: 7.5.0+17.04.20170301-0ubuntu1

  lightdm: 1.22.0-0ubuntu1

  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1677626] Re: Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard is enabled (Zesty)

[Khurshid Alam]

** Description changed:

  Unity falls-back to old lock from gnome-screensaver if accessibility is
  enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen
  
  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
- 3. Press CTRL+ALT+L
+ 3. Restart lightdm or reboot
+ 4. Press CTRL+ALT+L
  
  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.
  
  Expected Behavior:
  
  It should be using new lock-screen
  
- 
  Severity: High
  ---
  This bug is pretty well hidden. Sometimes when app which depends on-screen 
keyboard (ex: orca) gets updated, it automatically turns on screensaver. It can 
also get turned on if user accidentally press CTRL+ALT+S. User will have no 
clue whats hit him.
- 
  
  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.
  
  ⇛ Please fix accessibility for new lock-screen. Thanks
  
  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)
  
  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1
  
  gnome-screensaver: 3.6.1-7ubuntu5
  
  unity: 7.5.0+17.04.20170301-0ubuntu1
  
  lightdm: 1.22.0-0ubuntu1
  
  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

Title:
  Lock-Screen: Unity falls-back to old screensaver lock if onscreen
  keyboard is enabled (Zesty)

Status in lightdm package in Ubuntu:
  Confirmed
Status in onboard package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Unity falls-back to old lock from gnome-screensaver if accessibility
  is enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen

  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
  3. Restart lightdm or reboot
  4. Press CTRL+ALT+L

  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.

  Expected Behavior:
  
  It should be using new lock-screen

  Severity: High
  ---
  This bug is pretty well hidden. Sometimes when app which depends on-screen 
keyboard (ex: orca) gets updated, it automatically turns on screensaver. It can 
also get turned on if user accidentally press CTRL+ALT+S. User will have no 
clue whats hit him.

  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.

  ⇛ Please fix accessibility for new lock-screen. Thanks

  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)

  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1

  gnome-screensaver: 3.6.1-7ubuntu5

  unity: 7.5.0+17.04.20170301-0ubuntu1

  lightdm: 1.22.0-0ubuntu1

  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1677626] Re: Lock-Screen: Unity fallsback to old screensave lock if onscreen keyboard is enabled (Zesty)

[Khurshid Alam]

** Description changed:

- After today's update screen-locking suddenly started using gtk-greeter
- instead of unity-greeter. It looks similar to the old greeter of gdm
- /gnome-screensaver. I don't even have lightdm-gtk-greeter installed.
+ Unity falls-back to old lock from gnome-screensaver if accessibility is
+ enabled because accessibility in the new lock-screen is partially
+ broken. Please fix accessibility for new lock-screen
  
  How to reproduce:
  -
- 1. Reboot. It uses unity-greeter for login.
- 
- 2. Login to unity and press CTRL + ALT + L
+ 1. Go to system-settings ⟶ Universal Access ⟶ Seeing
+ 2. Turn on Screen-Reader
+ 3. Press CTRL+ALT+L
  
  Current Behavior:
  -
- It uses gtk-greeter instead of unity-greeter.
+ It uses old screensaver lock instead of unity-greeter.
  
  Expected Behavior:
  
- It should use unity-greeter
+ It should use new lockscreen
  
- Using dm-tool lock:
- -
- Locks screen with unity greeter, but then after unlocking, it presents 
gtk-greeter again, I had to unlock it again to see desktop. And the lock is not 
smooth. It first blank the screen then load the unity-greeter and then lock it.
+ 
+ Reason:
+ 
+ Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.
+ 
+ 
+ ⇛ Please fix accessibility for new lock-screen. Thanks
+ 
  
  Info:
  --
- OS: Ubuntu 17.04 (32 bit)
+ OS: Ubuntu 17.04 (32 bit/64bit)
  
  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1
  
  gnome-screensaver: 3.6.1-7ubuntu5
  
  unity: 7.5.0+17.04.20170301-0ubuntu1
  
  lightdm: 1.22.0-0ubuntu1
  
  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

** Package changed: lightdm-gtk-greeter (Ubuntu) => onboard (Ubuntu)

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

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

** Summary changed:

- Lock-Screen: Unity fallsback to old screensave lock if onscreen keyboard is 
enabled (Zesty)
+ Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard is 
enabled (Zesty)

** Description changed:

  Unity falls-back to old lock from gnome-screensaver if accessibility is
  enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen
  
  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
  3. Press CTRL+ALT+L
  
  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.
  
  Expected Behavior:
  
- It should use new lockscreen
- 
+ It should be using new lockscreen
  
  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.
  
- 
  ⇛ Please fix accessibility for new lock-screen. Thanks
- 
  
  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)
  
  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1
  
  gnome-screensaver: 3.6.1-7ubuntu5
  
  unity: 7.5.0+17.04.20170301-0ubuntu1
  
  lightdm: 1.22.0-0ubuntu1
  
  lignome-desktop-3-12: 3.24.0-0ubuntu1

** Description changed:

  Unity falls-back to old lock from gnome-screensaver if accessibility is
  enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen
  
  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
  3. Press CTRL+ALT+L
  
  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.
  
  Expected Behavior:
  
- It should be using new lockscreen
+ It should be using new lock-screen
+ 
+ 
+ Severity: High
+ ---
+ This bug is pretty well hidden. Sometimes when app which depends on-screen 
keyboard (ex: orca) gets updated, it automatically turns on screensaver. It can 
also get turned on if user accidentally press CTRL+ALT+S. User will have no 
clue whats hit him.
+ 
  
  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.
  
  ⇛ Please fix accessibility for new lock-screen. Thanks
  
  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)
  
  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1
  
  gnome-screensaver: 3.6.1-7ubuntu5
  
  unity: 7.5.0+17.04.20170301-0ubuntu1
  
  lightdm: 1.22.0-0ubuntu1
  
  lignome-desktop-3-12: 3.24.0-0ubuntu1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in 

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Hui Wang]

@Luke,

0502-bluetooth-bluez5-bring-back-SCO-over-PCM-support.patch

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1677626] Re: Unity started using gtk-greeter for screen-lock after update (Zesty)

[Khurshid Alam]

Apparently, It's this issue- LP: #1310404

Few!

** Summary changed:

- Unity started using gtk-greeter for screen-lock after update (Zesty)
+ Lock-Screen: Unity fallsback to old screensave lock if onscreen keyboard is 
enabled (Zesty)

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

Title:
  Lock-Screen: Unity fallsback to old screensave lock if onscreen
  keyboard is enabled (Zesty)

Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  After today's update screen-locking suddenly started using gtk-greeter
  instead of unity-greeter. It looks similar to the old greeter of gdm
  /gnome-screensaver. I don't even have lightdm-gtk-greeter installed.

  How to reproduce:
  -
  1. Reboot. It uses unity-greeter for login.

  2. Login to unity and press CTRL + ALT + L

  Current Behavior:
  -
  It uses gtk-greeter instead of unity-greeter.

  Expected Behavior:
  
  It should use unity-greeter

  Using dm-tool lock:
  -
  Locks screen with unity greeter, but then after unlocking, it presents 
gtk-greeter again, I had to unlock it again to see desktop. And the lock is not 
smooth. It first blank the screen then load the unity-greeter and then lock it.

  Info:
  --
  OS: Ubuntu 17.04 (32 bit)

  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1

  gnome-screensaver: 3.6.1-7ubuntu5

  unity: 7.5.0+17.04.20170301-0ubuntu1

  lightdm: 1.22.0-0ubuntu1

  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design

[Khurshid Alam]

Still reproducible in zesty.

** Tags added: zesty

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

Title:
  Enabling the onscreen keyboard in the accessibility menu changes
  lockscreen design

Status in Onboard:
  Invalid
Status in Unity:
  Invalid
Status in onboard package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After enabling the onscreen keyboard in the accessibility menu the
  design of the lockscreen is changed to the old design of Ubuntu 13.10
  and earlier.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu4 [modified: 
usr/share/onboard/onboard-defaults.conf]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 21 00:16:10 2014
  InstallationDate: Installed on 2014-04-14 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-14 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413)
  Package: unity
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin sambashare sudo
  _MarkForUpload: True

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

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

Re: [Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Luke Yelavich]

Hui, do you know which patch in the pulseaudio package is responsible
for this revert? A quick glance and I cannot find it.

Luke

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1665402] Re: Own keyboard shortcuts don't work

[Gunnar Hjalmarsson]

I agree that there is room for improvement of the design. More intuitive
(IMO) would be that it was just highlighted when you click it, as for
the predefined shortcuts, and that the window for editing is opened when
you double click or right click.

** Summary changed:

- Own keyboard shortcuts don't work
+ Custom shortcuts - unintuitive behavior

** Changed in: unity-control-center (Ubuntu)
   Importance: Medium => Wishlist

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

Title:
  Custom shortcuts - unintuitive behavior

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

Bug description:
  I do not know why the own-shortcuts not working. The only what i had
  done in the system is removing the unity-webapps-common and a
  autoremove after that.

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Konrad Zapałowicz]

Hey, to everyone interested we are currently testing and reviewing an
improvement to PA that fixes problems with selecting A2DP mode for BT
headsets.

Right now it is being tested internally with good results for Sony
headsets, QC35 from Bose and BT speakers. Once it is in a silo/ppa I
will share this information for much wider testing. Then it will be
submitted as a SRU and will land in xenial.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1590970] Re: package lightdm 1.18.1-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10

[Launchpad Bug Tracker]

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

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

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

Title:
  package lightdm 1.18.1-0ubuntu1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 10

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  removed and reinstalled due to graphical error with Radeon video card.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  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
  AptOrdering:
   ubuntu-desktop: Purge
   lightdm: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jun  8 20:50:25 2016
  DpkgTerminalLog:
   Removing ubuntu-desktop (1.361) ...
   Removing lightdm (1.18.1-0ubuntu1) ...
   dpkg: error processing package lightdm (--purge):
subprocess installed pre-removal script returned error exit status 10
  DuplicateSignature:
   package:lightdm:1.18.1-0ubuntu1
   Removing lightdm (1.18.1-0ubuntu1) ...
   dpkg: error processing package lightdm (--purge):
subprocess installed pre-removal script returned error exit status 10
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 10
  InstallationDate: Installed on 2016-05-31 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: lightdm
  Title: package lightdm 1.18.1-0ubuntu1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1569970] Re: Nautilus does not start

[Narcissus]

Still happening randomly on an up-to-date Ubuntu 16.04.

Now killing the nautilus process solves the issue temporarily, but it
takes some time for nautilus to start again even after killing the
process.

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

Title:
  Nautilus does not start

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  when opening nautilus i get the following errors:

  
  lotuspsychje@R00TBOOK:~$ nautilus

  (nautilus:9475): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  (nautilus:9475): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: 
assertion 'interface_->priv->connections != NULL' failed
  Kon de toepassing niet registreren: Tijd is verlopen

  (nautilus:9475): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:9475): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:9475): GLib-GObject-CRITICAL **: g_signal_connect_object:
  assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

  
  gksu nautilus opens nautilus, but also with an error:

  
  lotuspsychje@R00TBOOK:~$ gksu nautilus

  (nautilus:10257): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 13 17:22:53 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'confirm-trash' b'false'
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.preferences' b'enable-delete' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+0+24'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2016-04-04 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2016-04-05T06:03:34.591882

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

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

[Desktop-packages] [Bug 1677327] Re: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]

[Alberto Milone]

Hi Seth, please attach the full log:
/var/lib/dkms/nvidia-340/340.102/build/make.log

Also, I backported the patches for 4.9 and 4.10 in
340.102-0ubuntu0.16.04.1. There must be something else going on.

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

Title:
  dkms build fails with zesty hwe kernel [error: too few arguments to
  function ‘NV_GET_USER_PAGES’]

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

Bug description:
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

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

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

[Desktop-packages] [Bug 1677327] Re: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]

[Seth Forshee]

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1677327/+attachment/4853369/+files/make.log

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

Title:
  dkms build fails with zesty hwe kernel [error: too few arguments to
  function ‘NV_GET_USER_PAGES’]

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

Bug description:
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Hui Wang]

I have tested #59 on several laptops which have different bluetooth
modules (intel, atheros and realtek), and all of them are installed
ubuntu 16.04, after restoring the commit of #59 in the pulseaudio, the
problem disappears.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Hui Wang]

I found a very import commit was reverted in the canonical's pulseaudio,
if we restore that commit, this problem will be fixed.

commit de1e78a47cd13496c38f627d56944045a629053e
Author: David Henningsson 
Date:   Fri Dec 19 10:24:47 2014 +0100

bluez5: Do not suspend on no -> unknown profile transitions

In case a transport is currently disconnected and transitions to
idle, that should not count as a "remote hang up" event.

Signed-off-by: David Henningsson 

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 429869] Re: obsolete option '--print-installation-architecture'

[Mattia Rizzolo]

Removed in version 1:1.0.1 (in 2010).

** Changed in: xfonts-base (Ubuntu)
   Status: New => Fix Released

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

Title:
  obsolete option '--print-installation-architecture'

Status in xfonts-100dpi package in Ubuntu:
  New
Status in xfonts-75dpi package in Ubuntu:
  New
Status in xfonts-base package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xfonts-base

  Upgrade 9.04->9.10 alpha 5:

  Setting up xfonts-base (1:1.0.0-6) ...
  dpkg: warning: obsolete option '--print-installation-architecture', please 
use '--print-architecture' instead.

  Setting up xfonts-100dpi (1:1.0.0-4build1) ...
  dpkg: warning: obsolete option '--print-installation-architecture', please 
use '--print-architecture' instead.

  Setting up xfonts-75dpi (1:1.0.0-4build1) ...
  dpkg: warning: obsolete option '--print-installation-architecture', please 
use '--print-architecture' instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfonts-100dpi/+bug/429869/+subscriptions

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

[Desktop-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

[pgramond]

Hi, i've the same problem when i disconnect-reconnect a PPP connection (mobile 
broadband actually).
I 've found a workaround killing dnsmasq in pre-up script of Network-Manager 
(then, dnsmasq gets automatically restarted).
The problem appeared passing from network-manager 1.2.2 to 1.2.6 (while dnsmasq 
remained unchanged).

Will Network-Manager be patched, or should we wait for dnsmasq upagrade
in Yakkety ?

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

Title:
  Name resolution stops working after resume from suspend

Status in dnsmasq:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

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

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

[Desktop-packages] [Bug 1426596] Re: I get an "error report" popup on log-in

[Andreas Fritiofson]

This still happens from time to time on a fresh install of 16.10 on a
Dell Precision 5520. So x86_64. Apport says it's unreportable because
the core file is truncated.

** Changed in: xorg (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  I get an "error report" popup on log-in

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This doesn't occurr on every login, but it does occurr on the
  majority.

  From the crash report it seems to be Xorg, rather than Nautilus
  desktop.

  There are no obvious symptoms of this crash - i.e. everything seems to
  carry on regardless.

  I am reporting this against xorg, due to the existance of
  _usr_bin_Xorg.0.crash in /var/crash - I assume that all the
  information you need has been extracted below ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.75~precise1-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.113  Mon Dec  1 20:14:01 
PST 2014
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,resize,vpswitch,snap,imgpng,grid,regex,place,gnomecompat,compiztoolbox,unitymtgrabhandles,move,mousepoll,animation,wall,session,workarounds,expo,fade,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Feb 28 00:05:49 2015
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  JockeyStatus: xorg:nvidia_331_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Enabled, In use)
  MachineType: Notebook W65_67SF
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic 
root=UUID=9b573783-9dac-471b-ba7f-755099846d9e ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.libdrm2: libdrm2 2.4.52-1~precise2
  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.nvidia-graphics-drivers: nvidia-graphics-drivers 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

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

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

[Desktop-packages] [Bug 1678911] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Zusicherung »mixer« nicht erfüllt.

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1663528
   pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Zusicherung »mixer« nicht
  erfüllt.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup and login, changed from nvidia proprietary to nouveau

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Zusicherung »mixer« nicht erfüllt.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erik   3387 F pulseaudio
   /dev/snd/controlC0:  erik   3387 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr  3 09:17:08 2017
  ExecutablePath: /usr/bin/pulseaudio
  ExecutableTimestamp: 1490811859
  InstallationDate: Installed on 2016-04-08 (359 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcCwd: /
  ProcEnviron:
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fccb9037188 "mixer", 
file=file@entry=0x7fccb9037419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7fccb90376a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7fccb9037188 "mixer", file=0x7fccb9037419 
"mixer.c", line=929, function=0x7fccb90376a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Zusicherung »mixer« nicht erfüllt.
  UpgradeStatus: Upgraded to zesty on 2017-04-03 (0 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A186P105
  dmi.board.asset.tag: N/A
  dmi.board.name: Z68ITX-B-E
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 3
  dmi.chassis.vendor: N/A
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA186P105:bd08/06/2013:svnMotherboardbyZOTAC:pnZ68ITX-B-E:pvrRev.00:rvnZOTAC:rnZ68ITX-B-E:rvrRev.00:cvnN/A:ct3:cvrN/A:
  dmi.product.name: Z68ITX-B-E
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

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

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