[Desktop-packages] [Bug 1512545] [NEW] Wifi Country Regulations not set automatically

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu does not set Wifi Regulations according to country automatically.
This means that my computer wouldn't detect a wifi network on channel 13 
(because it had the US regulations by default, where channels 12 and 13 are not 
allowed.)
I am from Portugal and using the portuguese language, and still had US 
regulation (or some other) as default.

This configuration should be done automatically. I did not have this
issue in Windows or Android.

The issues is further described here (as well as a real example).
http://ubuntuforums.org/showthread.php?t=2300985&p=13381849#post13381849

Sincerely,
Diogo Valada

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


** Tags: bot-comment country network regulations wifi
-- 
Wifi Country Regulations not set automatically
https://bugs.launchpad.net/bugs/1512545
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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

[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot

[Yesfan]

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

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

Title:
  No menu bar in gtk apps on fresh boot

Status in Release Notes for Ubuntu:
  Fix Released
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Released

Bug description:
  Seen here in fresh 16.04 install using 01/07/16 image.
  Around 35% of fresh boots or restarts results in no menus in unity panel for 
most apps, notable exceptions are firefox & thunderbird
  A log out/in restores functionality.
  When this occurs there is nothing in any of the ~/.cache/upstart logs of 
obvious note

  Test case:
  fresh install, no changes
  Do a number of restarts from system settings, using either restart > restart 
or shutdown > restart, here randomly picked one or the other
  What happens here: 
  around 35% of the time the login has no menus in the unity panel for most 
apps.

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

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

[Desktop-packages] [Bug 1512545] Re: Wifi Country Regulations not set automatically

[Paul White]

** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  Wifi Country Regulations not set automatically

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu does not set Wifi Regulations according to country automatically.
  This means that my computer wouldn't detect a wifi network on channel 13 
(because it had the US regulations by default, where channels 12 and 13 are not 
allowed.)
  I am from Portugal and using the portuguese language, and still had US 
regulation (or some other) as default.

  This configuration should be done automatically. I did not have this
  issue in Windows or Android.

  The issues is further described here (as well as a real example).
  http://ubuntuforums.org/showthread.php?t=2300985&p=13381849#post13381849

  Sincerely,
  Diogo Valada

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

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

[Desktop-packages] [Bug 1178272] Re: Without pulseaudio, banshee and rhythmbox report "jack server is not running or cannot be started" and do not play

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  Without pulseaudio, banshee and rhythmbox report "jack server is not
  running or cannot be started" and do not play

Status in banshee package in Ubuntu:
  Invalid
Status in gstreamer0.10 package in Ubuntu:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Lubuntu Raring (13.04).
  The Lubuntu standard installation comes without jack, and without pulse, just 
plain alsa. Gstreamer applications (rhythmbox, banshee) used to work fine after 
installing "ubuntu-restricted-extras", which pulls in the usual gstreamer 
plugins.
  On my system, gstreamer applications stopped working. They report:
  > Cannot connect to server socket err = No such file or directory
  > Cannot connect to server request channel
  > jack server is not running or cannot be started
  Since there is no jack on this system, never was, and is not intended to be 
there, I cannot understand this message. The applications do not produce sound.

  This looks like gstreamer tries to start up jackd, regardless whether
  it is installed or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May  9 15:38:20 2013
  InstallationDate: Installed on 2013-02-12 (85 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to raring on 2013-04-25 (13 days ago)

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

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

[Desktop-packages] [Bug 1582957] Re: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

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

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

Title:
  package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Linux i7-4790K-ubuntu-box 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15
  22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  This popped up as soon as the desktop appeared.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon Apr 25 20:26:26 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-09-29 (231 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (21 days ago)

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

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

[Desktop-packages] [Bug 446394] Re: Connect to Hidden...select Saved Secure Connection; Connect not possible

[Bug Watch Updater]

** Changed in: network-manager-applet
   Status: Confirmed => Fix Released

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

Title:
  Connect to Hidden...select Saved Secure Connection; Connect not
  possible

Status in Network Manager Applet:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: network-manager

  please check the attached screenshot 
  I have a wifi network configured with wep. 
  The left side windows in the screenshot show the wifi network configured with 
the wep key
  when the machine boots up, I click on the network manager icon and select 
"Connect to hidden wireless network". Select the network from the  connection 
drop down. The connect button stays disabled probably because the key shows up 
blank.  see the right side of the screenshot
  
  $ lsb_release -rd
  Description:  Ubuntu karmic (development branch)
  Release:  9.10
  
  $ apt-cache policy network-manager
  network-manager:
Installed: 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
Candidate: 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
Version table:
   *** 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2 0
  500 http://in.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status
  

  ProblemType: Bug
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory
  Date: Thu Oct  8 20:02:10 2009
  DistroRelease: Ubuntu 9.10
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.2  metric 
2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   default via 192.168.0.1 dev wlan0  proto static
  NonfreeKernelModules: nvidia
  Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.31-12-generic i686

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

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

[Desktop-packages] [Bug 1583849] Re: dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

[elvisplatini]

Hi,
On my powermac G5, running Lubuntu 16.04, I downgraded firefox to 45.02, and it 
worked again (I'm currently using it). I used:

sudo apt-get install firefox=45.0.2+build1-0ubuntu1
sudo apt-mark hold firefox

I know it's not really satisfactory, that it would be better to try to
fix the 46 version bug, but until I manage to succeed in this skill
(maybe in 150 years), it allows me to avoid going back to macOS 10.5.

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

Title:
  dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  OK, the reason I'm posting back here, running Lu 16.04 on an PPC
  iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
  so it now running the new "22" kernel and saw in the list of upgrades
  new updates to FF and T-bird . . . on both machines after reboot FF
  window frame loads . . . and then crashes . . . no data is ever filled
  into the browser window.

  The iBook error says it "doesn't have enough memory to report the
  problem" . . . and on the PM . . . apparently it says the error report
  was "corrupted" . . . no launchpad window opened in the browser when I
  clicked on the "report the problem."

  Tried to revert to the old kernel in the iBook several times,
  seemingly failed to boot the old one . . . shut it down.

  I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
  via console there, that upgrade was much larger than the Lu system,
  but subsequently FF also then failed to launch w/o crashing . . .
  installed Midori to make an apple user post, but when I tried to start
  a new thread there Midori crashed as well.

  I ran "apt-get -f install" in both the iBook & the PM . . . nothing
  showed up. No "comment" in the terminal during the upgrade asking any
  questions or reporting "problems" . . . but FF is kaput

  I'm back in OSX 10.5 side until things cool down for the browsers in
  16.04 PPC Lu & U-MATE/XFCE.

  e...

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[SerCe]

Same problem

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[SerCe]

serce@serce-linuxpc:~$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Juniper PRO [Radeon HD 5750]
serce@serce-linuxpc:~$ lspci -knn | grep -A2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
Kernel driver in use: i915
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper PRO [Radeon HD 5750] [1002:68be]
Subsystem: ASUSTeK Computer Inc. Juniper PRO [Radeon HD 5750] 
[1043:0338]
Kernel driver in use: radeon

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 682788] announcement

[Michael Rybinsky]

Hi,

I've got an announcement for you, you may be interested, you can find
more information here 

onecathar...@yandex.ru

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

Title:
  Improve Unity Global Menu

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Triaged
Status in Baltix:
  Confirmed

Bug description:
  ===+++ _ ! ALL USERS ! _ +++===
  ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++===

  IMPORTANT 1: Please don't post any "me too message"; use the "Does
  this bug affect you?" feature you can find a bit above this bug
  description on Launchpad.

  IMPORTANT 2: Do not post anything if you haven't read all comments to
  verify that your point hasn't been made. If you feel tempted to stop
  reading because there are too many messages, that is a strong
  indicator that you shouldn't add even more comments. Developers have a
  tough time to find anything if you post redundant stuff. So please
  abstain from doing that.

  =
  Global menu in general (not only in Unity) is very unergonomic on large 
screens (see the attached screenshot) because if you have a small window 
somewhere near the low right corner you have to move the cursor all the way up 
to to panel to reach the menu. I understand why the global menu was used for 
the netbook edition (it saves space and most windows are maximized), but since 
Unity is intended to be for the desktop edition there should be an option to 
switch to the traditional position of the app menu. It would be welcomed by 
many desktop users. Please try to find a solution for it that works.

  A commonly suggested solution is:
   [ ] Global Menu on
   [ ] Global Menu off
   [ ] Global Menu only for maximized windows
  The default is usually suggested as either the first (on) or last (on only 
for maximized windows).

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10.  This project will
  address the issue described in this bug and also issues described in
  the duplicates of this bus.  Note this is the 'official' bug that
  tracks the implementation of this project.

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location:Global/Local
  Visibility:  Hidden/Always displayed
  ---

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

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

[Desktop-packages] [Bug 1584962] Re: [aisleriot][Klondike] Missing card

[Bob]

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

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

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

Title:
  [aisleriot][Klondike] Missing card

Status in aisleriot package in Ubuntu:
  New

Bug description:
  I just played, and almost win, until I realized that the third of spade was 
completely missing : it is nor in the stack nor a hidden card.
  In attachment, you will find a screenshot of my game.

  Version : 1:3.18.2-1ubuntu1

  So frustrating ! ^^

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

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

[Desktop-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

[Launchpad Bug Tracker]

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

** Changed in: network-manager-openvpn (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/1576726

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Confirmed
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Confirmed
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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

[Desktop-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

[Launchpad Bug Tracker]

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

** Changed in: network-manager-openvpn (Ubuntu Xenial)
   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/1576726

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Confirmed
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Confirmed
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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

[Desktop-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

[Launchpad Bug Tracker]

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

** Changed in: network-manager-openconnect (Ubuntu Xenial)
   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/1576726

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Confirmed
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Confirmed
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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

[Desktop-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

[Launchpad Bug Tracker]

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

** Changed in: network-manager-vpnc (Ubuntu Xenial)
   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/1576726

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Confirmed
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Confirmed
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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

[Desktop-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

[Launchpad Bug Tracker]

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

** Changed in: network-manager-ssh (Ubuntu Xenial)
   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/1576726

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Confirmed
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Confirmed
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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

[Desktop-packages] [Bug 1513964] Re: dsextras.py : Shell Command Injection with a pkg name

[Bernd Dietzel]

** Information type changed from Private Security to Public Security

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

Title:
  dsextras.py :  Shell Command Injection with a pkg name

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  Expoit screenshot attached.

  The "dsextras.py" script  is vulnerable in multiple functions for code
  injections in the "name" of a pkg.

  The script uses old and depreached python functions wich are a
  security risk :

  commands.getstatusoutput()
  os.system()
  os.popen()

  Please use the subprocess module instead !

  
  Expoit Example wich runs a xmessage command
  ==

  theregrunner@1510:~$ cd /usr/lib/python2.7/dist-packages/gtk-2.0/
  theregrunner@1510:/usr/lib/python2.7/dist-packages/gtk-2.0$ python
  Python 2.7.10 (default, Oct 14 2015, 16:09:02) 
  [GCC 5.2.1 20151010] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import dsextras
  >>> dsextras.pkgc_get_version('fontutil;xmessage "hello bug"')
  '1.3.1'
   
  ===

  This Bug also effects the "so" files in the gtk-2.0 folder :
  atk.so
  gtkunixprint.so
  pangocairo.so
  pango.so

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Fri Nov  6 21:36:38 2015
  InstallationDate: Installed on 2015-10-22 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pygobject-2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1586628] [NEW] Thunderbird should switch to GTK3

[Nikita Yerenkov-Scott]

Public bug reported:

I think that it would be good if Thunderbird got up-to-date with its GTK
look so it would be good if it upgraded from GTK2 to GTK3.

** Affects: thunderbird (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

Title:
  Thunderbird should switch to GTK3

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  I think that it would be good if Thunderbird got up-to-date with its
  GTK look so it would be good if it upgraded from GTK2 to GTK3.

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

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

[Desktop-packages] [Bug 1586628] Re: Thunderbird should switch to GTK3

[Nikita Yerenkov-Scott]

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

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

Title:
  Thunderbird should switch to GTK3

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  I think that it would be good if Thunderbird got up-to-date with its
  GTK look so it would be good if it upgraded from GTK2 to GTK3.

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

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

[Desktop-packages] [Bug 1584962] Re: [aisleriot][Klondike] Missing card

[Jeremy Bicha]

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

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

Title:
  [aisleriot][Klondike] Missing card

Status in Aisleriot:
  Unknown
Status in aisleriot package in Ubuntu:
  New

Bug description:
  I just played, and almost win, until I realized that the third of spade was 
completely missing : it is nor in the stack nor a hidden card.
  In attachment, you will find a screenshot of my game.

  Version : 1:3.18.2-1ubuntu1

  So frustrating ! ^^

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

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

[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot

[Rui Neto]

It is still in proposed, not main. Should it be marked as released ?

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

Title:
  No menu bar in gtk apps on fresh boot

Status in Release Notes for Ubuntu:
  Fix Released
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Released

Bug description:
  Seen here in fresh 16.04 install using 01/07/16 image.
  Around 35% of fresh boots or restarts results in no menus in unity panel for 
most apps, notable exceptions are firefox & thunderbird
  A log out/in restores functionality.
  When this occurs there is nothing in any of the ~/.cache/upstart logs of 
obvious note

  Test case:
  fresh install, no changes
  Do a number of restarts from system settings, using either restart > restart 
or shutdown > restart, here randomly picked one or the other
  What happens here: 
  around 35% of the time the login has no menus in the unity panel for most 
apps.

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

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

[Desktop-packages] [Bug 1586641] [NEW] PCI/internal sound card not detected

[mart1oeil]

Public bug reported:

My sound card is not even detected and alsamixer do nothing.

I tried oem-audio-hda-daily-lts-xenial-dkms -
0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
dev/+archive/ubuntu/alsa-daily/+packages like it was described here
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

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
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May 28 15:20:10 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-27 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My sound card is not even detected and alsamixer do nothing.

  I tried oem-audio-hda-daily-lts-xenial-dkms -
  0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages like it was described here
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 28 15:20:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-27 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1577137] Re: saned.service masked and cannot be unmasked

[Hanky]

I checked the whole procedure on a fresh 16.04 install.

To start saned.socket first I needed to run

`sudo systemctl start saned.socket`

However, in /usr/share/doc/sane-utils/README.Debian I found the
solution: To use socket.saned from startup, you have to run

`sudo systemctl enable saned.socket`

once. The terminal tells me:

`Created symlink from
/etc/systemd/system/sockets.target.wants/saned.socket to
/lib/systemd/system/saned.socket.`

On the next reboot saned.socket starts right away. This explains why it
was started on my working machine; I definitely tried that command in my
attempts to start saned...

If you don't want that automatic start anymore, it has do be disabled
again:

`sudo systemctl disable saned.socket`


So I would conclude: This is not a bug, but a feature ;-)

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

Title:
  saned.service masked and cannot be unmasked

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04 (from 14.04) I noticed the sane daemon (sane-
  utils 1.0.25+git20150528-1ubuntu2) was no longer running. Attempting
  to manually start it results in systems complaining that the service
  is masked:

  kjetil at lucien in ~> sudo systemctl start saned
  Failed to start saned.service: Unit saned.service is masked.

  Unmasking it does not work:

  kjetil at lucien in ~> sudo systemctl unmask saned
  kjetil at lucien in ~> sudo systemctl start saned
  Failed to start saned.service: Unit saned.service is masked.

  kjetil at lucien in ~> ps u -C saned
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  kjetil at lucien in ~>

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sane-utils 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  1 13:10:31 2016
  InstallationDate: Installed on 2012-08-01 (1368 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (6 days ago)
  mtime.conffile..etc.default.saned: 2016-05-01T12:51:02.879807
  mtime.conffile..etc.sane.d.saned.conf: 2016-01-10T13:57:20.785810

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

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

[Desktop-packages] [Bug 210081] Re: evince will not launch external applications

[efa]

as the bug was opened in 2008, fix was available with upstream evince
2.24 but in ubuntu evince 3.10.3 still is present, here the solution
found out of launchpad:

sudo ln -s /etc/apparmor.d/usr.bin.evince /etc/apparmor.d/disable/usr.bin.evince
sudo service apparmor restart

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

Title:
  evince will not launch external applications

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  In gutsy, evince used to be able to launch external helper
  applications. In a fully updated hardy, it doesn't seem to do this, at
  least with the attached example.

  Steps to reproduce:
  1) Download test.tar.gz attachment, unpack in a directory, cd to it.
  2) Load test.pdf in gutsy's evince. A movie player will launch if you 
   click on the image on the last page, assuming your system can 
   play MOV files.
  3) Load test.pdf in hardy's evince. Even though the tooltip says that
  evince intends to launch the movie player, it doesn't. However, 
  the movie can be played just fine using a properly configure totem.

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

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

[Desktop-packages] [Bug 1586651] [NEW] loose theme and icons

[Amin]

Public bug reported:

Every time I log on ,I have a lot of problem with theme and icons .

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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
Date: Sat May 28 19:08:45 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
 nvidia-340, 340.96, 4.4.0-21-generic, x86_64: installed
 nvidia-340, 340.96, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GT215 [GeForce GT 240] [19da:2134]
InstallationDate: Installed on 2016-04-26 (32 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: MSI MS-7636
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=4bc22359-34b7-43fa-9783-1e28527cf3b6 ro 152535455565 quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.7
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: H55M-P31(MS-7636)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd04/27/2010:svnMSI:pnMS-7636:pvr1.0:rvnMSI:rnH55M-P31(MS-7636):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7636
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat May 28 18:54:28 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputA4 tech USB2.0 Camera KEYBOARD, 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.3-1ubuntu2

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


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

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

Title:
  loose theme and icons

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time I log on ,I have a lot of problem with theme and icons .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Abhishek Chaudhary]

Confirmed bug. Audio interface "focusrite solo" isn't found on startup.
Have to plug it out and then in again to make it work.

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1586657] [NEW] Touchpad gsettings being ignored

[Nikita Yerenkov-Scott]

Public bug reported:

I think this is just the touchpad, though I don't have a mouse to test
this with so it could also be affecting the mouse or a wider range of
settings. But I have found that after upgrading to GNOME 3.20 on Ubuntu
GNOME 16.04 that all my gsettings for things like natural scrolling and
tap to click are being ignored and it doesn't matter what I have them
set to, they are doing what they like. I have also seen others
experiencing the same issues.

This is what dconf-editor shows me the settings are set to:

dconf-editor_touchpad_settings.png

And yet even though the tap to click option is set to 'false', my
touchpad is acting as though it has been set to 'true' ever since the
upgrade, same for natural scrolling. As I have said, these are the only
settings that I have noticed this with, however I have not really tested
it with any of the others so I cannot say for sure how many settings
this issue affects.

** Affects: gsettings-desktop-schemas
 Importance: Unknown
 Status: Unknown

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

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: xenial

** Attachment added: "dconf-editor_touchpad_settings.png"
   
https://bugs.launchpad.net/bugs/1586657/+attachment/4671887/+files/dconf-editor_touchpad_settings.png

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

** Also affects: gsettings-desktop-schemas (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Confirmed

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

** Also affects: gsettings-desktop-schemas via
   https://bugzilla.gnome.org/show_bug.cgi?id=766964
   Importance: Unknown
   Status: Unknown

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1581569] Re: Thunderbird crashes randomly while busy or idle (Xubuntu Xenial)

[Richard Elkins]

I should have said earlier that the same is true for Firefox.
Version = 46.0.1+build1-0ubuntu0.16.04.2

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

Title:
  Thunderbird crashes randomly while busy or idle (Xubuntu Xenial)

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Since I have been using Thunderbird version
  1:38.7.2+build1-0ubuntu0.16.04.1 on Xenial, I can observe it crashing
  (seemingly) randomly while idle or while busy, resulting in the
  platform-independent Mozilla crash dialogue window.

  I don't know if this is related to Xenial or to internal changes at
  Mozilla.

  -

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy thunderbird
  thunderbird:
Installed: 1:38.7.2+build1-0ubuntu0.16.04.1
Candidate: 1:38.7.2+build1-0ubuntu0.16.04.1
Version table:
   *** 1:38.7.2+build1-0ubuntu0.16.04.1 500
  500 http://mirror.lstn.net/ubuntu xenial-updates/main amd64 Packages
  500 http://mirror.lstn.net/ubuntu xenial-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1:38.6.0+build1-0ubuntu1 500
  500 http://mirror.lstn.net/ubuntu xenial/main amd64 Packages
   1:24.4.0+build1-0ubuntu1 500
  500 http://cz.archive.ubuntu.com/ubuntu trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:38.7.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elkins 1436 F pulseaudio
  BuildID: 20160426220723
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri May 13 09:40:02 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-05-05 (8 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   192.168.1.0/24 dev enp2s0  proto kernel  scope link  src 192.168.1.219  
metric 100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-73d462c6-f824-4a34-819a-3c9d82160513
  Plugins:
   IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - 
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-8-plugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=38.7.2/20160426220723 (In use)
  RelatedPackageVersions: icedtea-8-plugin 1.6.2-3ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-73d462c6-f824-4a34-819a-3c9d82160513
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: NM70I-1037U
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/05/2013:svnBIOSTARGroup:pnNM70I-1037U:pvr6.0:rvnBIOSTARGroup:rnNM70I-1037U:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: NM70I-1037U
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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

[Desktop-packages] [Bug 1586659] [NEW] Notification don't appear when I'm in full screen mode

[Yvan Roy]

*** This bug is a security vulnerability ***

Private security bug reported:

When I use full screen in different app. the notification about battery
charge (especially when it's low) don't appear. When I don't use full
screen, the notification appear. It's problematic because when the
battery is low, I don't have notification before the laptop shut down.

The same problem occur with Firefox and VLC.

More info: The notification seem to be created but not showing on
screen. If I'm in full screen and I return to regular mode, the
notification appear. Also, if I'm in regular mode and the notification
appear, when I change for the full screen mode, the notification stay on
screen.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat May 28 11:36:06 2016
DistUpgraded: 2016-05-11 12:46:43,015 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 45) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:80cb]
InstallationDate: Installed on 2016-03-02 (87 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: HP HP Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=06f354f2-97a2-48a8-8ead-4bb66400bfa1 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-05-11 (16 days ago)
dmi.bios.date: 10/19/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.1C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 80CB
dmi.board.vendor: HP
dmi.board.version: 99.42
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/19/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80CB:rvr99.42:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat May 28 06:45:13 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug ubuntu xenial

** Information type changed from Public to Private Security

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

Title:
  Notification don't appear when I'm in full screen mode

Status in xorg package in Ubuntu:
  New

Bug description:
  When I use full screen in different app. the notification about
  battery charge (especially when it's low) don't appear. When I don't
  use full screen, the notification appear. It's problematic because
  when the battery is low, I don't have notification before the laptop
  shut down.

  The same problem occur with Firefox and VLC.

  More info: The notification seem to be created but not showing on
  screen. If I'm in full screen and I return to regular mode, the
  notification appear. Also, if I'm in regular mode and the notification
  appear, when I change for the full screen mode, the notification stay
  on screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 28 1

[Desktop-packages] [Bug 1581569] Re: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial)

[Richard Elkins]

** Summary changed:

- Thunderbird crashes randomly while busy or idle (Xubuntu Xenial)
+ Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial)

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

Title:
  Thunderbird & Firefox crash randomly while busy or idle (Xubuntu
  Xenial)

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Since I have been using Thunderbird version
  1:38.7.2+build1-0ubuntu0.16.04.1 on Xenial, I can observe it crashing
  (seemingly) randomly while idle or while busy, resulting in the
  platform-independent Mozilla crash dialogue window.

  I don't know if this is related to Xenial or to internal changes at
  Mozilla.

  -

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy thunderbird
  thunderbird:
Installed: 1:38.7.2+build1-0ubuntu0.16.04.1
Candidate: 1:38.7.2+build1-0ubuntu0.16.04.1
Version table:
   *** 1:38.7.2+build1-0ubuntu0.16.04.1 500
  500 http://mirror.lstn.net/ubuntu xenial-updates/main amd64 Packages
  500 http://mirror.lstn.net/ubuntu xenial-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1:38.6.0+build1-0ubuntu1 500
  500 http://mirror.lstn.net/ubuntu xenial/main amd64 Packages
   1:24.4.0+build1-0ubuntu1 500
  500 http://cz.archive.ubuntu.com/ubuntu trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:38.7.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elkins 1436 F pulseaudio
  BuildID: 20160426220723
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri May 13 09:40:02 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-05-05 (8 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   192.168.1.0/24 dev enp2s0  proto kernel  scope link  src 192.168.1.219  
metric 100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-73d462c6-f824-4a34-819a-3c9d82160513
  Plugins:
   IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - 
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-8-plugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=38.7.2/20160426220723 (In use)
  RelatedPackageVersions: icedtea-8-plugin 1.6.2-3ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-73d462c6-f824-4a34-819a-3c9d82160513
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: NM70I-1037U
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/05/2013:svnBIOSTARGroup:pnNM70I-1037U:pvr6.0:rvnBIOSTARGroup:rnNM70I-1037U:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: NM70I-1037U
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

-- 
Mailing list: https://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 1574079] Re: USB audio device is not recognized after startup in 16.04

[Mario Limonciello]

Abkishek,

Can you please try to reproduce it with fwupd running with debug flags as
listed above?

You might have to unplug it, run with debug flags and plug back in.

On Sat, May 28, 2016, 09:50 Abhishek Chaudhary 
wrote:

> Confirmed bug. Audio interface "focusrite solo" isn't found on startup.
> Have to plug it out and then in again to make it work.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1574079
>
> Title:
>   USB audio device is not recognized after startup in 16.04
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions
>

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1586661] Re: gnome-terminal transparent in wrong place when selected

[Nikita Yerenkov-Scott]

** Attachment added: "gnome-terminal_Normal_Clicked_Off.png"
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1586661/+attachment/4671913/+files/gnome-terminal_Normal_Clicked_Off.png

** Description changed:

  I have just noticed that on Ubuntu GNOME 16.04 with GNOME 3.20 that the
  gnome-terminal when transparency mode is on is transparent where the
  "File Edit" etc options are, but when the gnome-terminal window is not
- selected it does not have the faulty behaviour:
+ selected it does not have the faulty behaviour (I have blacked out
+ private-ish information so please just ignore the big black box in the
+ title bar and the lacking of the bit with the '$' in the second image):
  
- gnome-terminal_Strange_See-Through.png
- gnome-terminal_Normal_Clicked_Off.png
+ gnome-terminal_Strange_See-Through.png
+ gnome-terminal_Normal_Clicked_Off.png

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

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

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

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

Title:
  gnome-terminal transparent in wrong place when selected

Status in GNOME Terminal:
  Unknown
Status in Ubuntu GNOME:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I have just noticed that on Ubuntu GNOME 16.04 with GNOME 3.20 that
  the gnome-terminal when transparency mode is on is transparent where
  the "File Edit" etc options are, but when the gnome-terminal window is
  not selected it does not have the faulty behaviour (I have blacked out
  private-ish information so please just ignore the big black box in the
  title bar and the lacking of the bit with the '$' in the second
  image):

  gnome-terminal_Strange_See-Through.png
  gnome-terminal_Normal_Clicked_Off.png

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

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

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Abhishek Chaudhary]

This is what I got after running
1) sudo killall fwupd
2) sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v 2>&1 | tee fwupd_debug.log

21:57:58Verbose debugging enabled (on console 0)
21:57:58adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-1/libfu_plugin_steelseries.so
21:57:58adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-1/libfu_plugin_test.so
21:57:58performing init() on test
21:57:58Loading fallback values from /etc/fwupd.conf
21:57:58adding udev device: 
/sys/devices/pci:00/:00:02.0/:01:00.0
21:57:58fixing GUID 0x10de:0x1040->693025a1-4a7d-53b8-864e-c7f3e5866ec0
21:57:58emit added from Udev: 
ro__sys_devices_pci_00__00_02_0__01_00_0
Failed to coldplug: UEFI firmware updating not supported
***
21:57:58Failed to coldplug: UEFI firmware updating not supported
***
21:57:58emit added from USB: usb:00:04
21:57:58emit added from USB: usb:00:03
### 
   @0551ms AsStore:load 551ms
### 
   @0551ms AsStore:load{per-system} 551ms
#   
   @0005ms 
AsStore:app-info{/usr/share/app-info/xmls/org.freedesktop.fwupd.xml} 5ms
 #  
   @0022ms 
AsStore:app-info{/var/lib/app-info/yaml/in.archive.ubuntu.com_ubuntu_dists_xenial_multiverse_dep11_Components-amd64.yml.gz}
 11ms
 #  
   @0022ms AsStore:store-from-file 11ms
   ###  
   @0046ms 
AsStore:app-info{/var/lib/app-info/yaml/in.archive.ubuntu.com_ubuntu_dists_xenial-updates_main_dep11_Components-amd64.yml.gz}
 23ms
   ###  
   @0046ms AsStore:store-from-file 23ms
  ##
   @0452ms 
AsStore:app-info{/var/lib/app-info/yaml/in.archive.ubuntu.com_ubuntu_dists_xenial_universe_dep11_Components-amd64.yml.gz}
 406ms
  ##
   @0452ms AsStore:store-from-file 406ms
 #  
   @0547ms 
AsStore:app-info{/var/lib/app-info/yaml/in.archive.ubuntu.com_ubuntu_dists_xenial_main_dep11_Components-amd64.yml.gz}
 94ms
 #  
   @0547ms AsStore:store-from-file 94ms

  ###  @0593ms FuMain:coldplug 24ms

  ##   @0584ms FuMain:coldplug{Udev} 15ms

  #@0578ms FuProviderUdev:coldplug{usb} 9ms

   #   @0584ms FuProviderUdev:coldplug{pci} 5ms

#  @0593ms FuMain:coldplug{USB} 8ms

 # @0593ms FuProviderUsb:added{258a:0001} 5ms
21:57:58FuMain: acquired name: org.freedesktop.fwupd
21:57:59devices now in store:
21:57:591   com.steelseries.rival-legacy.firmware   Rival 
SteelSeries
21:57:592   UEFI-dummy-dev0 UEFI Updates
21:57:593   com.via.VL811.firmware  VL811 Firmware
21:57:594   com.via.VL811+.firmware VL811+ Firmware
21:57:595   com.via.VL812.firmware  VL812 Firmware
21:57:596   com.via.VL812_B2.firmware   VL812 B2 Firmware
21:57:597   com.dell.uefi124c207d.firmware  XPS 15 9550/Precision 
5510 System Update
21:57:598   com.dell.uefi33773727.firmware  XPS 13 9350 System 
Update
21:57:599   com.dell.uefi43ca3264.firmware  OptiPlex 7440 AIO 
System Update
21:57:5910  com.dell.uefia0a3aa54.firmware  Embedded Box PC 5000 
System Update
21:57:5911  com.dell.uefiaee2604a.firmware  Embedded Box PC 3000 
System Update
21:57:5912  com.dell.uefie0f614ed.firmware  Edge Gateway 5000/5100 
System Update
21:57:5913  com.hughski.ColorHug.firmware   ColorHug
21:57:5914  com.hughski.ColorHug2.firmware  ColorHug2
21:57:5915  com.hughski.ColorHugALS.firmwareColorHugALS

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

Title:
  USB audio device is

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Mario Limonciello]

Great thanks, can you please also share sudo lsusb -v output?

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[AroundWorker]

Best workaround:

* purge package `light-locker`

* install package `i3lock`

* execute command: `sudo ln -s /usr/bin/i3lock /usr/bin/slock`

cheers..

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

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

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

  After unlocking screen cursor is invisible.

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

  

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

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

  this is xubuntu using the xfce window manager.

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

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Jeremy Bicha]

Please try installing

xserver-xorg-input-libinput

and log out and log back in.

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1586628] Re: Thunderbird should switch to GTK3

[Nikita Yerenkov-Scott]

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

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

Title:
  Thunderbird should switch to GTK3

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I think that it would be good if Thunderbird got up-to-date with its
  GTK look so it would be good if it upgraded from GTK2 to GTK3.

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

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

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Abhishek Chaudhary]

Here is the output of sudo lsusb -v

** Attachment added: "sudo lsusb -v"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+attachment/4671919/+files/sudo%20lsusb%20-v

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[hyperboria]

#103 does not work for me. [xubuntu 16.04]

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

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

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

  After unlocking screen cursor is invisible.

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

  

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

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

  this is xubuntu using the xfce window manager.

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

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Severus Tux]

Same problem with me. My "Mouse & Touchpad" Settings is empty (see the
attachment). Changes made to touchpad schemas have no effect. I am using
SynPS/2 Synaptics TouchPad.

** Attachment added: "Screenshot from 2016-05-28 22-19-32.png"
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1586657/+attachment/4671926/+files/Screenshot%20from%202016-05-28%2022-19-32.png

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Nikita Yerenkov-Scott]

@Jeremy,

Yes, installing that and then logging out and in again solves the
problem and even adds a new section to the gnome-control-center's Mouse
& Touchpad settings. This package should really be installed by default
and as a dependency of something.

** No longer affects: gsettings-desktop-schemas

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

Title:
  Touchpad gsettings being ignored

Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Severus Tux]

installing xserver-xorg-input-libinput solves the problem

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

Title:
  Touchpad gsettings being ignored

Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

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

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

[Desktop-packages] [Bug 1586670] [NEW] car bluetooth SMS service functionality

[Andris Petrams]

Public bug reported:

The Meizu Pro 5 Ubuntu edition (OTA-10.2) does not support SMS writing-
reading and SMS text to speech playing via bluetooth in a car factory
handsfree system (Ford B-MAX). This functionality is fully supported
when I use phone with Android version 4 or higher.

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


** Tags: bluetooth car sms

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

Title:
  car bluetooth SMS service functionality

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Meizu Pro 5 Ubuntu edition (OTA-10.2) does not support SMS
  writing-reading and SMS text to speech playing via bluetooth in a car
  factory handsfree system (Ford B-MAX). This functionality is fully
  supported when I use phone with Android version 4 or higher.

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Nikita Yerenkov-Scott]

Wait, I understand that this issue is affecting all distros, so is this
a downstream issue or an upstream one?

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

Title:
  Touchpad gsettings being ignored

Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Nikita Yerenkov-Scott]

** Also affects: gsettings-desktop-schemas via
   https://bugzilla.gnome.org/show_bug.cgi?id=766964
   Importance: Unknown
   Status: Unknown

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1381415] Re: Can't create new folder in "List" view

[sergey]

yes. This is bag

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

Title:
  Can't create new folder in "List" view

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

Bug description:
  If i click right button in list view of nautilus, i don't see "create
  folder" menuitem. And for creating new folder i must change view to
  "grid", create folder, and then change view back to list.

  I can create folder in list view only if in folder few files, and
  lower part of window is free from files, then my right click of mouse
  will be recognized as click_on_free_space, but in windows with many
  files, if i click anywere in windows, i click on file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 15 20:58:37 2014
  GsettingsChanges: 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 2014-10-04 (11 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1586674] [NEW] nautilus list view - reset of the entered name of the folder when changing an layout

[sergey]

Public bug reported:

reset of the entered name of the folder when changing an layout

It is impossible to jobt with nautilus on two and more apportions in the list 
view mode.
At change of language the entered name is dumped. It is very critical bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 28 20:02:18 2016
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+565+281'"
 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-05-28 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  nautilus list view -  reset of the entered name of the folder when
  changing an layout

Status in nautilus package in Ubuntu:
  New

Bug description:
  reset of the entered name of the folder when changing an layout

  It is impossible to jobt with nautilus on two and more apportions in the list 
view mode.
  At change of language the entered name is dumped. It is very critical bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 28 20:02:18 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+565+281'"
   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-05-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Nikita Yerenkov-Scott]

Also, I have just noticed that when I install this package, although it
fixes the problem it does something crazy to the mouse sensitivity
(possibly) and speed, but no matter what I do with the speed settings I
can't stop it just jumping and shaking all the time even if I'm not even
trying to move it... It's either too fast or too slow, it's like an
overly exciting owl or something... I'm just mulling over whether I
should report this as a bug or not or keep trying with the settings...

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1583849] Re: dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

[Fritz Hudnut]

@elvisplatini:

Thanks for the post, I was hoping that since this issue is "significant"
. . . that it would have been patched by now . . . but apparently not.
I did try to look in synaptic to see if the history of FF versions would
be listed, but, nope . . . only the 46 . . . .  In 16.04 I have been
using Qupzilla, it's OK, but function is a bit "limited" and/or even
"slow" . . . like trying to log into LP here the cursor wouldn't load
into the email user box . . . for several minutes . . . then, I went
back to it, and it was there . . . .

I might get around to trying out your commands . . . but, if it is
marked as "hold" . . . if and when the patched version shows up (hard to
know when that might happen) . . . how would I "un-hold" it?

F

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

Title:
  dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  OK, the reason I'm posting back here, running Lu 16.04 on an PPC
  iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
  so it now running the new "22" kernel and saw in the list of upgrades
  new updates to FF and T-bird . . . on both machines after reboot FF
  window frame loads . . . and then crashes . . . no data is ever filled
  into the browser window.

  The iBook error says it "doesn't have enough memory to report the
  problem" . . . and on the PM . . . apparently it says the error report
  was "corrupted" . . . no launchpad window opened in the browser when I
  clicked on the "report the problem."

  Tried to revert to the old kernel in the iBook several times,
  seemingly failed to boot the old one . . . shut it down.

  I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
  via console there, that upgrade was much larger than the Lu system,
  but subsequently FF also then failed to launch w/o crashing . . .
  installed Midori to make an apple user post, but when I tried to start
  a new thread there Midori crashed as well.

  I ran "apt-get -f install" in both the iBook & the PM . . . nothing
  showed up. No "comment" in the terminal during the upgrade asking any
  questions or reporting "problems" . . . but FF is kaput

  I'm back in OSX 10.5 side until things cool down for the browsers in
  16.04 PPC Lu & U-MATE/XFCE.

  e...

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

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

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Taras]

Hi Mario,  I believe the
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1574079/comments/20
debug output is not complete. Please see the log:

...
21:26:1615  com.hughski.ColorHugALS.firmwareColorHugALS
21:26:30waiting a small time for other providers
21:26:30using b69159f2-3778-5728-80d0-01be18b2ea30 for 
USB\VID_1397&PID_0501
21:26:30emit added from DFU: usb:00:01:03
21:26:31no product string descriptor
21:26:33Called GetUpdates()
(END)

Here I've also tried to connect my USB sound-card BEHRINGER UMC204 at
21:26:30.

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1586628] Re: Thunderbird should switch to GTK3

[Nikita Yerenkov-Scott]

** Bug watch added: Mozilla Bugzilla #1043146
   https://bugzilla.mozilla.org/show_bug.cgi?id=1043146

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1043146
   Importance: Unknown
   Status: Unknown

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

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

Title:
  Thunderbird should switch to GTK3

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

Bug description:
  I think that it would be good if Thunderbird got up-to-date with its
  GTK look so it would be good if it upgraded from GTK2 to GTK3.

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Severus Tux]

@Nikita Yerenkov-Scott (yerenkov-scott)  Same happens with mine. After
installing this package, mo cursor has become Hyper Exited. I cant hold
it still for a seconds. Its shivering all the time and too fast.

In addition to this. My usable touchpad area is reduced very much. If I
start slowly from my right down corner towards top, it does not move.

My Conclusion : this is not a perfect solution.

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1586655] Re: Background grey even though set to image and image is displayed elsewhere

[Nikita Yerenkov-Scott]

@Jeremy,

Yes, after restarting all Nautilus instances (actually just killing it
did the trick) the problem is solved. Though seemingly only affected the
Adwaita GTK+ theme as changing it to the Numix one fixed the issue.

** No longer affects: gnome-shell (Ubuntu)

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

** Changed in: ubuntu-gnome
   Status: Incomplete => Fix Released

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

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

Title:
  Background grey even though set to image and image is displayed
  elsewhere

Status in gnome-shell:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 I have found that
  even if I set my background again through the gnome-control-center
  that my background looks like this:

  Background_Not_Showing.png

  Even though it shows correctly in both of these places:

  Background_Shown_In_Settings.png
  Background_Shown_In_AO.png

  I have also tried setting the button via the right-click option in
  Nautilus but still the same results.

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

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

[Desktop-packages] [Bug 1586655] Re: Background grey even though set to image and image is displayed elsewhere

[Nikita Yerenkov-Scott]

By the way, are you going to give the patch to upstream (the upstream
report is linked) or was this something only affecting the Ubuntu
nautilus for some reason?

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

Title:
  Background grey even though set to image and image is displayed
  elsewhere

Status in gnome-shell:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 I have found that
  even if I set my background again through the gnome-control-center
  that my background looks like this:

  Background_Not_Showing.png

  Even though it shows correctly in both of these places:

  Background_Shown_In_Settings.png
  Background_Shown_In_AO.png

  I have also tried setting the button via the right-click option in
  Nautilus but still the same results.

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

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

[Desktop-packages] [Bug 1586678] [NEW] Should have better support for GNOME Online Accounts

[Nikita Yerenkov-Scott]

Public bug reported:

I think that it would be really good if Thunderbird had proper support
for GNOME Online Accounts.

** Affects: thunderbird
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: Mozilla Bugzilla #847989
   https://bugzilla.mozilla.org/show_bug.cgi?id=847989

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=847989
   Importance: Unknown
   Status: Unknown

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

Title:
  Should have better support for GNOME Online Accounts

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I think that it would be really good if Thunderbird had proper support
  for GNOME Online Accounts.

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Nikita Yerenkov-Scott]

@Severus Tux, Yes, I am getting the same, I think it time I did file a
bug report against that package, this is getting a little bit too much.
Though maybe I will have a look at the dconf-editor and gnome-tweak-tool
options first because I was sure there was something about touchpad
usability area or something like that, but I could be mistaken.

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"

[Nonny Moose]

I was aware that the InitializeSandbox error was not related to the issue 
because I get that from like half of my applications. XD
The chromium-browser script that starts chromium-browser supports the 
flag --no-touch-pinch, which I find a little odd because it essentially turns 
it into --disable-pinch when it sends the flags to the binary itself.

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

Title:
  Chromium-browser armhf crashes with "InitializeSandbox() called with
  multiple threads in process gpu-process"

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  crashes on startup with

  [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() 
called with multiple threads in process gpu-process
  Segmentation fault

  System ODROID XU3 armhf

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

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

[Desktop-packages] [Bug 1586657] Re: Touchpad gsettings being ignored

[Jeremy Bicha]

The Settings app (gnome-control-center and gnome-settings-daemon)
included in GNOME 3.20 only support the new xserver-xorg-input-libinput
driver.

We would just make that a dependency of gnome-control-center then except
that unity-control-center doesn't yet support changing touchpad settings
with it. For Ubuntu GNOME 16.10 (still in development), the libinput
package is a recommends currently.

Yes, it is a different touchpad driver and works differently than the
old -synaptics driver. Maybe it will be more comfortable once you get
used to it. If not, you can report a new bug:

ubuntu-bug xserver-xorg-input-libinput

** Package changed: gsettings-desktop-schemas (Ubuntu) => gnome-control-
center (Ubuntu)

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

Title:
  Touchpad gsettings being ignored

Status in GSettings Desktop Schemas:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  I think this is just the touchpad, though I don't have a mouse to test
  this with so it could also be affecting the mouse or a wider range of
  settings. But I have found that after upgrading to GNOME 3.20 on
  Ubuntu GNOME 16.04 that all my gsettings for things like natural
  scrolling and tap to click are being ignored and it doesn't matter
  what I have them set to, they are doing what they like. I have also
  seen others experiencing the same issues.

  This is what dconf-editor shows me the settings are set to:

  dconf-editor_touchpad_settings.png

  And yet even though the tap to click option is set to 'false', my
  touchpad is acting as though it has been set to 'true' ever since the
  upgrade, same for natural scrolling. As I have said, these are the
  only settings that I have noticed this with, however I have not really
  tested it with any of the others so I cannot say for sure how many
  settings this issue affects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1586657/+subscriptions

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

[Desktop-packages] [Bug 1586655] Re: Background grey even though set to image and image is displayed elsewhere

[Jeremy Bicha]

I got the patch from upstream! :)

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

Title:
  Background grey even though set to image and image is displayed
  elsewhere

Status in gnome-shell:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 I have found that
  even if I set my background again through the gnome-control-center
  that my background looks like this:

  Background_Not_Showing.png

  Even though it shows correctly in both of these places:

  Background_Shown_In_Settings.png
  Background_Shown_In_AO.png

  I have also tried setting the button via the right-click option in
  Nautilus but still the same results.

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

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

[Desktop-packages] [Bug 1556714] Re: pitivi crashed with pitivi.undo.undo.UndoWrongStateError in _getTopmostStack()

[Launchpad Bug Tracker]

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

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

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

Title:
  pitivi crashed with pitivi.undo.undo.UndoWrongStateError in
  _getTopmostStack()

Status in pitivi package in Ubuntu:
  Confirmed

Bug description:
  Resumed working after that I believe. Screen turned black & white for
  a second. Haven't had problems afterwards.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pitivi 0.95-1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 01:59:29 2016
  ExecutablePath: /usr/bin/pitivi
  InstallationDate: Installed on 2016-03-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  InterpreterPath: /usr/bin/python3.5
  ProcCmdline: /usr/bin/python3 /usr/bin/pitivi
  PythonArgs: ['/usr/bin/pitivi']
  SourcePackage: pitivi
  Title: pitivi crashed with pitivi.undo.undo.UndoWrongStateError in 
_getTopmostStack()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1585867] Re: Support squashfs / .snap packages

[Launchpad Bug Tracker]

This bug was fixed in the package shared-mime-info - 1.6-1ubuntu1

---
shared-mime-info (1.6-1ubuntu1) yakkety; urgency=medium

  * debian/patches/squashfs.patch:
- Recognise squashfs files (LP: #1585867)

 -- Robert Ancell   Thu, 26 May 2016
16:13:40 +1200

** Changed in: shared-mime-info (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Support squashfs / .snap packages

Status in File Roller:
  Confirmed
Status in shared-mime-info:
  Unknown
Status in file-roller package in Ubuntu:
  Fix Released
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in file-roller source package in Xenial:
  Triaged
Status in shared-mime-info source package in Xenial:
  Triaged

Bug description:
  Support squashfs / .snap pacakges

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

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

[Desktop-packages] [Bug 1585691] Re: [regression] keyboard backlight is not exported in upower 0.99.4-2git1

[Martin Pitt]

** Changed in: upower (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [regression] keyboard backlight is not exported in upower 0.99.4-2git1

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Fix Committed

Bug description:
  This is in yakkety.

  With last upower:
 (upowerd:12806): UPower-WARNING **: failed to convert brightness: 2

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

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

[Martin Pitt]

Adjusted patch in
https://launchpad.net/ubuntu/+source/upower/0.99.4-2ubuntu0.2, please
re-test with this version.

** Tags removed: regression-proposed verification-failed
** Tags added: verification-needed

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  New
Status in unity-settings-daemon source package in Xenial:
  New
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Desktop-packages] [Bug 1586655] Re: Background grey even though set to image and image is displayed elsewhere

[Nikita Yerenkov-Scott]

Ah! Glad all that is settled then!

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

Title:
  Background grey even though set to image and image is displayed
  elsewhere

Status in gnome-shell:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 I have found that
  even if I set my background again through the gnome-control-center
  that my background looks like this:

  Background_Not_Showing.png

  Even though it shows correctly in both of these places:

  Background_Shown_In_Settings.png
  Background_Shown_In_AO.png

  I have also tried setting the button via the right-click option in
  Nautilus but still the same results.

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

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

[Desktop-packages] [Bug 1546317] Re: Accessibility indicator is missing from ubiquity-dm at the "Try Ubuntu" dialog

[Tuukka Ojala]

I'm still seeing this on both the 16.4 release as well as the 2016-05-28
Yakkety build. Either I am missing something or this is a separate bug.

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

Title:
  Accessibility indicator is missing from ubiquity-dm at the "Try
  Ubuntu" dialog

Status in gnome-orca:
  Invalid
Status in ubuntu-mate:
  Fix Released
Status in a11y-profile-manager package in Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Boot from a media containing the 15.10 32-bit image. Let it just boot, do 
not select anything.
  2. After the bongo drum sound, select your language and click "Try Ubuntu".
  3. After the desktop has been loaded, start Orca screen reader with the 
dedicated Alt+Super+s combination.
  Expected: the screen reader comes up talking
  Actual: the system remains silent.
  4. Try starting Orca from a terminal (Ctrl-Alt-t) and also from the Run 
dialog (Alt+F2).
  Results are the same as for point 3.

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

-- 
Mailing list: https://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 1574079] Re: USB audio device is not recognized after startup in 16.04

[Mario Limonciello]

Well that's interesting, it looks like your audio device might have a dfu
mode. I wonder if that's the case for the other reporters. Can you please
also share lsusb output? Everyone affected it would be great to share both
of these so that upstream can make sense of common denominations to figure
what's actually going on.

On Sat, May 28, 2016, 13:50 Taras  wrote:

> Hi Mario,  I believe the
> https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1574079/comments/20
> debug output is not complete. Please see the log:
>
> ...
> 21:26:1615  com.hughski.ColorHugALS.firmwareColorHugALS
> 21:26:30waiting a small time for other providers
> 21:26:30using b69159f2-3778-5728-80d0-01be18b2ea30 for
> USB\VID_1397&PID_0501
> 21:26:30emit added from DFU: usb:00:01:03
> 21:26:31no product string descriptor
> 21:26:33Called GetUpdates()
> (END)
>
> Here I've also tried to connect my USB sound-card BEHRINGER UMC204 at
> 21:26:30.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1574079
>
> Title:
>   USB audio device is not recognized after startup in 16.04
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions
>

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[TheBigW]

my lsusb output:

Bus 001 Device 003: ID 1235:8006 Focusrite-Novation Focusrite Scarlett 2i2
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 046d:c20d Logitech, Inc. WingMan Attack 2
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


addition: the focusrite 2i2 works great now after removing fwupd. However on my 
second system with RME Fireface UCX it still happens that it takes 1..2 reboots 
until the UCX gets recognized. I will post it's lsusb output later once I get 
to this system.

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[Afforess]

I can also confirm this for 16.04. I note a very similar error in the
syslog:

May 28 17:34:58 afforess-pc pulseaudio[2004]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
May 28 17:35:00 afforess-pc bluetoothd[1009]: 
/org/bluez/hci0/dev_20_9B_A5_5D_BB_30/fd2: fd(31) ready
May 28 17:35:00 afforess-pc pulseaudio[2004]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_20_9B_A5_5D_BB_30/fd2 (Operation Not Authorized)
May 28 17:35:00 afforess-pc kernel: [91164.555960] input: 20:9B:A5:5D:BB:30 as 
/devices/virtual/input/input27

I did some digging at one point, and the error from bluez5 seems to
originate from DBus, and may be a permissions issue with the bluetooth
DBus configuration or pulseaudio DBus configuration.

The workaround suggested by Con Kolivas works, but is very annoying.

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in Bluez Utilities:
  New
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Desktop-packages] [Bug 1116337] Re: libnl-route-3 produces segmentation fault in libvirt

[Mathew Hodson]

** Tags added: precise

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

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

Title:
  libnl-route-3 produces segmentation fault in libvirt

Status in libnl3 package in Ubuntu:
  New

Bug description:
  libvirtd is crashing with a segmentation fault when listing available domains 
and dumping an interface description at the same time.
  The segmentation fault is thrown in rtnl_link_get in the libnl-route-3 
library (libnl-route-3-200 3.2.7-4).

  How to reproduce:
  - Create a domain and start it
  - Call "while [ 1 ]; do virsh  list --all ; done" on one terminal
  - Call "virsh iface-dumpxml eth0" a few times on another terminal

  Ubuntu version: 12.04.2 LTS

  Using the latest version of libnl3 (commit
  506020ae99377ce45992d225e3b2917ee7b45b77) libvirt works without any
  problems.

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

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

[Desktop-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

[Mathew Hodson]

** Tags added: trusty

** Tags added: testcase

** Changed in: libnl3 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

Status in libnl3 package in Ubuntu:
  In Progress

Bug description:
  Retrieving information about configured neighbors fail 
  my application is running the following procedure:

  neigh = NULL;
  cache = rtnl_neigh_alloc_cache(sk);
  while(NULL == neigh){
  nl_cache_refill(sk, chache);
  neigh = rtnl_neigh_get(cache, ifindex, dst_addr);
  }

  with libnl3 3.2.21-1 this loop will never end, even when adding a static arp 
entry.
  However, with libnl-3.2.24 the neighbor lookup succeed.

  additional general info:
  $ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  $ uname -r
  3.13.0-24-generic
  $ apt-cache policy libnl-genl-3-200 libnl-route-3-200
  libnl-genl-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libnl-route-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1584740] Re: Libreoffice impress hanging and high cpu on slide operations

[Claudio Arseni]

the issue also affect Libreoffice Calc

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

Title:
  Libreoffice impress hanging and high cpu on slide operations

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - Create a presentation in libreoffice impress, 30-100 slides with or without 
images
  - Add, copy or delete slides
  - On those operations LO Impress hangs a lot; sometimes 5 mins or more
  - Opening and saving works quick

  Tested on 2 different laptops, both had the same issue. Both did have
  Intel Graphics, but different  ones.  It works fine on the same laptop
  with LO 5.1 on Ubuntu 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-impress 1:5.1.2-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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 23 12:55:08 2016
  InstallationDate: Installed on 2016-04-29 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1584740/+subscriptions

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

[Desktop-packages] [Bug 1585691] Re: [regression] keyboard backlight is not exported in upower 0.99.4-2git1

[Launchpad Bug Tracker]

This bug was fixed in the package upower - 0.99.4-2git2

---
upower (0.99.4-2git2) yakkety; urgency=medium

  * Update previous keyboard backlight patch with upstream commit 71e3bb0.
(LP: #1585691)

 -- Martin Pitt   Sat, 28 May 2016 21:31:06
+0200

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

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

Title:
  [regression] keyboard backlight is not exported in upower 0.99.4-2git1

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Fix Released

Bug description:
  This is in yakkety.

  With last upower:
 (upowerd:12806): UPower-WARNING **: failed to convert brightness: 2

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

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

[Desktop-packages] [Bug 1584740] Re: Libreoffice impress hanging and high cpu on slide operations

[Launchpad Bug Tracker]

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

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

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

Title:
  Libreoffice impress hanging and high cpu on slide operations

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - Create a presentation in libreoffice impress, 30-100 slides with or without 
images
  - Add, copy or delete slides
  - On those operations LO Impress hangs a lot; sometimes 5 mins or more
  - Opening and saving works quick

  Tested on 2 different laptops, both had the same issue. Both did have
  Intel Graphics, but different  ones.  It works fine on the same laptop
  with LO 5.1 on Ubuntu 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-impress 1:5.1.2-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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 23 12:55:08 2016
  InstallationDate: Installed on 2016-04-29 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1584740/+subscriptions

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

[Desktop-packages] [Bug 1097285] Re: A "prohibit default" route causes crash

[Mathew Hodson]

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

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

Title:
  A "prohibit default" route causes crash

Status in libnl3 package in Ubuntu:
  New

Bug description:
  This bug:
  https://bugs.kde.org/show_bug.cgi?id=312677
  is apparently the fault of /usr/lib64/libnl-route-3.so.200
  so I'm reporting it here.

  This is related to the route in a second ip2 routing table:
  $ ip route show table vpn
  0.0.0.0/1 via 10.10.10.65 dev tap0
  prohibit default
  128.0.0.0/1 via 10.10.10.65 dev tap0
  192.168.0.0/24 dev eth0 proto kernel scope link metric 1
  192.168.188.0/24 dev virbr1 proto kernel scope link src 192.168.188.1

  A "blackhole default" may well work, but I'm out of my depth a little
  here.

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

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

[Desktop-packages] [Bug 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

[Mathew Hodson]

** Tags removed: 14.04.4 libnl ubuntu vf
** Tags added: trusty

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

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

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

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

[Desktop-packages] [Bug 1540294] Re: Network manager stopped working after some update

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 1539634
   network-manager crashes when using libnl-3-200 3.2.21-1ubuntu1

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

Title:
  Network manager stopped working after some update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  'sudo NetworkManager' gives:
  (NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Key file does not have group 'connectivity'

  To get network interface to work I have to do like this:
  'sudo ip link set dev eth0 down'
  'sudo dhclient eth0'

  
  Ubuntu 14.04.3 LTS

  'apt-cache policy network-manager':
  network-manager:
Installed: 0.9.8.8-0ubuntu7.2
Candidate: 0.9.8.8-0ubuntu7.2
Version table:
   *** 0.9.8.8-0ubuntu7.2 0
  500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.9.8.8-0ubuntu7.1 0
  500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
   0.9.8.8-0ubuntu7 0
  500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 10:57:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-28 (1190 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.1.1 dev eth0 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to trusty on 2016-02-01 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-02-01T11:14:17.778018
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:6612): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.8) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

[Treviño]

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

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  New
Status in unity-settings-daemon source package in Xenial:
  New
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot

[Treviño]

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

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

Title:
  No menu bar in gtk apps on fresh boot

Status in Release Notes for Ubuntu:
  Fix Released
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Committed

Bug description:
  Seen here in fresh 16.04 install using 01/07/16 image.
  Around 35% of fresh boots or restarts results in no menus in unity panel for 
most apps, notable exceptions are firefox & thunderbird
  A log out/in restores functionality.
  When this occurs there is nothing in any of the ~/.cache/upstart logs of 
obvious note

  Test case:
  fresh install, no changes
  Do a number of restarts from system settings, using either restart > restart 
or shutdown > restart, here randomly picked one or the other
  What happens here: 
  around 35% of the time the login has no menus in the unity panel for most 
apps.

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

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

[Desktop-packages] [Bug 1578853] Re: Firefox blotchy graphics in Google Maps

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox blotchy graphics in Google Maps

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Google maps are displayed in Firefox with blotches.  It can take a few
  seconds for the blotches to stablize.  It occurs both with the
  symbolic maps and the satellite images, and typically gets worse with
  more zoomed-in views.  The blotches seem to be rather random.

  I don't have a problem with any other kind of graphics or video,
  Firefox or otherwise.

  I will attach or otherwise post three example screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 46.0+build5-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  circ   2432 F pulseaudio
   /dev/snd/controlC1:  circ   2432 F pulseaudio
   /dev/snd/controlC0:  circ   2432 F pulseaudio
  BuildID: 20160425115534
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu May  5 15:45:29 2016
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources:
   prefs.js
   
[Profile]/extensions/{6AC85730-7D0F-4de0-B3FA-21142DD85326}/defaults/preferences/colorzilla.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-30 (645 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.3.1 dev eth0  proto static 
   192.168.3.0/24 dev eth0  proto kernel  scope link  src 192.168.3.181  metric 
1
  MostRecentCrashID: bp-3e82e56c-e5b2-4cb6-9b4b-fbc4d2160505
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=46.0/20160425115534 (In use)
   Profile1 - LastVersion=46.0/20160425115534
  RelatedPackageVersions:
   totem-mozilla 3.10.1-1ubuntu4
   rhythmbox-mozilla 3.0.2-0ubuntu2
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-3e82e56c-e5b2-4cb6-9b4b-fbc4d2160505
   bp-175b14d6-3673-4fa7-a7ae-a98bd2140730
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd05/16/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8700
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping

[Paulkelly]

Installing this removes Gnome, should be in big letters in the
description

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

Title:
  [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt
  Looping

Status in Linux Mint:
  Fix Committed
Status in libimobiledevice package in Ubuntu:
  Fix Released
Status in libimobiledevice package in Debian:
  Fix Released

Bug description:
  The latest libimobiledevice release 1.1.5 is a year old and does not
  support iOS7 devices. Most iOS devices have been updated to iOS7 by
  now, so currently the library is broken in functionality for most
  users. The git snapshot has been tested to work, but there seems to be
  no new upstream release being prepared for the time being.

  The new git snapshot includes several fixes, including the security
  fix that was previously patched on top of 1.1.5 in Ubuntu.

  Packaging branch merge request attached to this bug report.

  --- Original report ---

  The iPhone reporting "Trust the currently connected computer?" Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1561795] Re: Fullscreen Crash Intel GPU since Ubuntu 15.10

[Launchpad Bug Tracker]

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

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

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

Title:
  Fullscreen Crash Intel GPU since Ubuntu 15.10

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ever since I upgraded to Ubuntu 15.10, I haven't been able to exit
  fullscreen without video crashing. There are rare cases when I've been
  able to safely exit, but more times than not, it doesn't. This is
  typically when I'm using Chrome to watch YouTube or Twitch video
  streams. The only way out is switch over and do a "killall -u myname".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:57:24 2016
  DistUpgraded: 2015-10-25 04:02:46,508 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-03 (446 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=a630eb7a-a0ab-49aa-bdb6-8221ae278346 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-25 (151 days ago)
  dmi.bios.date: 09/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA0WW(2.60):bd09/12/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Mar 24 19:14:03 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Desktop-packages] [Bug 1586716] Re: yelp crashed with SIGSEGV in g_str_equal()

[Tim]

I can reproduce this in yakkety with the following command:
yelp ghelp://usr/share/doc/pspp/pspp.xml#ONEWAY

seems to be an issue with the uri parsing

** Information type changed from Private to Public

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

** Tags added: yakkety

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

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

Title:
  yelp crashed with SIGSEGV in g_str_equal()

Status in Ubuntu GNOME:
  New
Status in yelp package in Ubuntu:
  New

Bug description:
  No idea, just saw the error.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: yelp 3.20.1-1ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  Uname: Linux 4.6.0-040600-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sun May 29 03:03:21 2016
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2014-02-04 (844 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203)
  ProcCmdline: yelp file:///usr/share/doc/pspp/pspp.xml#ONEWAY
  SegvAnalysis:
   Segfault happened at: 0x7f497638eb5a <__strcmp_sse2_unaligned+26>:   movdqu 
(%rdi),%xmm1
   PC (0x7f497638eb5a) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: yelp
  StacktraceTop:
   g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: yelp crashed with SIGSEGV in g_str_equal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo 
vboxusers
  XsessionErrors:
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to create 
device: failed to obtain org.freedesktop.color-manager.create-device auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain 
org.freedesktop.color-manager.create-profile auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain 
org.freedesktop.color-manager.create-profile auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: could not find 
device: property match 'XRANDR_name'='eDP1' does not exist

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

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

[Desktop-packages] [Bug 1579516] Re: Wrong icon: displaying wired when WiFi client connected

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Wrong icon: displaying wired when WiFi client connected

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

Bug description:
  16.04 amd64.

  The applet icon in the status area shows the opposing vertical arrows
  (Wired) symbol rather than the classic WiFi radiating symbol after
  adding a Wifi Access Point Hotspot, enabling it, having it fail to
  start (see bug #1579512 "Hotspot Access Point mode fails for 802.11a
  (5GHz) band"), and the system automatically reconnecting as a WiFi
  client to the local AP. The system doesn't even have a wired Ethernet
  interface.

  The applet menu also does not display the connected WiFi network at
  all although the Active Network Connections dialog displays the
  connection parameters correctly.

  $ nmcli gen
  STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
  connected full enabled enabled enabled enabled

  $nmcli con
  NAME UUID TYPE DEVICE
  wireless.lan.iam.tj 3779baf8-edd9-4960-bd72-813e6626fa52 802-11-wireless 
wlp2s0
  Access Point 05b2e2ee-0e93-4d00-b080-681b61d3e036 802-11-wireless --
  HTC One M8 Network b32ad6d1-d170-4bb3-9bf5-a77a54bc7773 bluetooth --

  $ ip link show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: wlp2s0:  mtu 1500 qdisc mq state UP mode 
DORMANT group default qlen 1000
  link/ether 34:02:86:fc:ad:55 brd ff:ff:ff:ff:ff:ff

  $ ip route show
  default via 10.254.1.254 dev wlp2s0 proto static metric 600
  10.254.1.0/24 dev wlp2s0 proto kernel scope link src 10.254.1.42 metric 600
  169.254.0.0/16 dev wlp2s0 scope link metric 1000

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

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

[Desktop-packages] [Bug 1579516] Re: Wrong icon: displaying wired when WiFi client connected

[nacenteno]

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

Upgraded to 16.04 and now I have the same problem

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

Title:
  Wrong icon: displaying wired when WiFi client connected

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

Bug description:
  16.04 amd64.

  The applet icon in the status area shows the opposing vertical arrows
  (Wired) symbol rather than the classic WiFi radiating symbol after
  adding a Wifi Access Point Hotspot, enabling it, having it fail to
  start (see bug #1579512 "Hotspot Access Point mode fails for 802.11a
  (5GHz) band"), and the system automatically reconnecting as a WiFi
  client to the local AP. The system doesn't even have a wired Ethernet
  interface.

  The applet menu also does not display the connected WiFi network at
  all although the Active Network Connections dialog displays the
  connection parameters correctly.

  $ nmcli gen
  STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
  connected full enabled enabled enabled enabled

  $nmcli con
  NAME UUID TYPE DEVICE
  wireless.lan.iam.tj 3779baf8-edd9-4960-bd72-813e6626fa52 802-11-wireless 
wlp2s0
  Access Point 05b2e2ee-0e93-4d00-b080-681b61d3e036 802-11-wireless --
  HTC One M8 Network b32ad6d1-d170-4bb3-9bf5-a77a54bc7773 bluetooth --

  $ ip link show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: wlp2s0:  mtu 1500 qdisc mq state UP mode 
DORMANT group default qlen 1000
  link/ether 34:02:86:fc:ad:55 brd ff:ff:ff:ff:ff:ff

  $ ip route show
  default via 10.254.1.254 dev wlp2s0 proto static metric 600
  10.254.1.0/24 dev wlp2s0 proto kernel scope link src 10.254.1.42 metric 600
  169.254.0.0/16 dev wlp2s0 scope link metric 1000

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

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

[Desktop-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Abhishek Chaudhary]

Here is the lsusb output after login (audio interface is plugged in) ; 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 004 Device 002: ID 258a:0001  
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Here is the lsusb output after removing and plugging the interface back again ;
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 1235:801c Focusrite-Novation 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 004 Device 002: ID 258a:0001  
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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