[Desktop-packages] [Bug 1551020] Re: IpUtils Ping can be in wait forever

2016-07-01 Thread Launchpad Bug Tracker
[Expired for iputils (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  IpUtils Ping can be in wait forever

Status in iputils package in Ubuntu:
  Expired

Bug description:
  Ping is using round trip time from previous incoming echo response
  packet to determine max waittime for next packet, but the validation
  of the value read from incoming echo response packet is poor. It only
  checks for non-negative values.

  To reproduce the Bug: 
  Step 1: Apply the following diff to the Ping command- (this simulates the 
condition that triptime value read from incoming echo response was some 
arbitrary large value)-
  diff -r iputils/ping_common.c iputils_ping_hang_repro/ping_common.c
  709c709,711
  <   triptime = tv->tv_sec * 100 + tv->tv_usec;
  ---
  >   /*SNAP: To repro Ping hang, set this value to some large long 
value. Since this is read from */
  >   /*  incoming echo reply and not validated for 0 or too 
large, this will cause hang/long wait.
  >   /* triptime = tv->tv_sec * 100 + tv->tv_usec; */
  >   triptime = 1000123456789;
  /tmp/diff.out (END)

  Step 2: Run the following ping command targeted at a host that is at
  first successfully replying to the Ping echo requests, but at some
  point during the execution (before the last ping echo request) take
  the target offline(to trigger the waittime).  This will cause Ping to
  set the waittime to tmax which is 2 X the max RTT which we just set to
  a very large value.

  sudo ./ping -c 10 -i 0.5 $TARGET_IP > /tmp/out.log

  
  AS A RESULT,

  1. The Ping will keep running for a few hundred years, no big deal. In
  strace there will be a periodic recvmsg to check for response every
  few ms, something like this-

  Process 11373 attached - interrupt to quit
  ...
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  ...

  2. In the /proc/timer_list file I see a large value for the process' timer-
  ...
   #14: <>, it_real_fn, S:01, hrtimer_start, ping/11373
   # expires at 611433835413-611433835413 nsecs [in 2000179546163581 to 
2000179546163581 nsecs]
  ...

  So we can see that when a large timeval is read from the echo
  response, it is not validated.

  Possible causes for invalid timeval values could be:
  Malicious destination, buggy OS, Malformed packets, interference with echo 
response belonging to "traceroute" command but had the same ID and Seq No.

  Impact-
  Ping runs forever.

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

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


[Desktop-packages] [Bug 1577223] Re: Crash when opening specific file

2016-07-01 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Crash when opening specific file

Status in gedit package in Ubuntu:
  Expired

Bug description:
  Gedit crashes when opening a certain file (both from command line and
  GUI):

  $ gedit NOTES.txt 
  **
  ERROR:../../gi/pygi-argument.c:1586:_pygi_argument_to_object: code should not 
be reached
  Aborted (core dumped)

  Other files (also from the same directory) work fine. Copying the file
  to a file with same content, but different file name will trigger the
  bug also for the new file.

  Ubuntu 15.10, gedit 3.10.4-0ubuntu13

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

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


[Desktop-packages] [Bug 1598344] [NEW] /usr/bin/vinagre:11:__GI_strstr:g_strsplit:vinagre_connection_split_string:vinagre_connection_new_from_string:vinagre_options_process_command_line

2016-07-01 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: trusty vivid wily xenial

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

Title:
  
/usr/bin/vinagre:11:__GI_strstr:g_strsplit:vinagre_connection_split_string:vinagre_connection_new_from_string:vinagre_options_process_command_line

Status in vinagre package in Ubuntu:
  New

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

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

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


[Desktop-packages] [Bug 1598342] [NEW] package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: end of file on stdin at conffile prompt

2016-07-01 Thread Mazahua
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common 1:5.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul  1 21:55:52 2016
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-06-21 (10 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libreoffice
Title: package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: 
end of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.bash_completion.d.libreoffice.sh: 2016-05-19T13:43:30
mtime.conffile..etc.libreoffice.psprint.conf: 2016-03-29T09:41:04
mtime.conffile..etc.libreoffice.soffice.sh: 2016-04-07T19:22:29
mtime.conffile..etc.libreoffice.sofficerc: 2016-04-07T19:22:29

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


** Tags: amd64 apport-package xenial

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

Title:
  package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade:
  end of file on stdin at conffile prompt

Status in libreoffice package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul  1 21:55:52 2016
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-06-21 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.bash_completion.d.libreoffice.sh: 2016-05-19T13:43:30
  mtime.conffile..etc.libreoffice.psprint.conf: 2016-03-29T09:41:04
  mtime.conffile..etc.libreoffice.soffice.sh: 2016-04-07T19:22:29
  mtime.conffile..etc.libreoffice.sofficerc: 2016-04-07T19:22:29

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

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


[Desktop-packages] [Bug 1598341] [NEW] package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: end of file on stdin at conffile prompt

2016-07-01 Thread Mazahua
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common 1:5.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul  1 21:55:52 2016
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-06-21 (10 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libreoffice
Title: package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: 
end of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.bash_completion.d.libreoffice.sh: 2016-05-19T13:43:30
mtime.conffile..etc.libreoffice.psprint.conf: 2016-03-29T09:41:04
mtime.conffile..etc.libreoffice.soffice.sh: 2016-04-07T19:22:29
mtime.conffile..etc.libreoffice.sofficerc: 2016-04-07T19:22:29

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


** Tags: amd64 apport-package xenial

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

Title:
  package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade:
  end of file on stdin at conffile prompt

Status in libreoffice package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul  1 21:55:52 2016
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-06-21 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.bash_completion.d.libreoffice.sh: 2016-05-19T13:43:30
  mtime.conffile..etc.libreoffice.psprint.conf: 2016-03-29T09:41:04
  mtime.conffile..etc.libreoffice.soffice.sh: 2016-04-07T19:22:29
  mtime.conffile..etc.libreoffice.sofficerc: 2016-04-07T19:22:29

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

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


[Desktop-packages] [Bug 1598343] [NEW] package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: end of file on stdin at conffile prompt

2016-07-01 Thread Mazahua
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common 1:5.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul  1 21:55:52 2016
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-06-21 (10 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libreoffice
Title: package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: 
end of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.bash_completion.d.libreoffice.sh: 2016-05-19T13:43:30
mtime.conffile..etc.libreoffice.psprint.conf: 2016-03-29T09:41:04
mtime.conffile..etc.libreoffice.soffice.sh: 2016-04-07T19:22:29
mtime.conffile..etc.libreoffice.sofficerc: 2016-04-07T19:22:29

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


** Tags: amd64 apport-package xenial

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

Title:
  package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade:
  end of file on stdin at conffile prompt

Status in libreoffice package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul  1 21:55:52 2016
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-06-21 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.4-0ubuntu1 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.bash_completion.d.libreoffice.sh: 2016-05-19T13:43:30
  mtime.conffile..etc.libreoffice.psprint.conf: 2016-03-29T09:41:04
  mtime.conffile..etc.libreoffice.soffice.sh: 2016-04-07T19:22:29
  mtime.conffile..etc.libreoffice.sofficerc: 2016-04-07T19:22:29

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

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


[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Confirmed => Invalid

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

2016-07-01 Thread Aiman
Hi everybody,
The OSK work with Xapps. However I found that in Firefox the keyboard appears 
in user name fields but not in the password one.
It happened in gmail login and online banking site.

I have M10 FHD and use RC proposed channel.

I thougt to let you know.

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

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Libertine:
  Fix Released
Status in Libertine devel series:
  Fix Released
Status in Libertine trunk series:
  Fix Released
Status in Ubuntu UX:
  New
Status in libertine package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

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

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


[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-07-01 Thread Cruz Fernandez
Regarding @shinyblue , on my configuration (lightdm/unity), sounds seems
to work in all cases (new kernel 4.4.0-28-generic).

Only caveat I want to mention is that System Settings->Sound->Output
shows two options with headphone connected, and selecting "Speakers.
Built-in Audio" just mutes and produces no sound.

I'm tempted to report that last caveat in a new bug, but I'm not sure if
it was one of the original problems reported by @ivan.koptiev and he
didn't realize about this current limitation.

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  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 x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys

2016-07-01 Thread Christian
By the way, as Bruno says this work well in High Contrast Theme.

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

Title:
  Nautilus invisible focused item when selecting files with Ctrl and
  arrow keys

Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 beta2 I noticed that selecting files with
  Ctrl and the arrow keys in Nautilus became more difficult since the
  active item had no decorations. I'm sure before there was some sort of
  dashed line around the active item's name, so this may be a
  regression.

  I have searched for any other bug report on this, or any other person
  complaining about it, without success. I tried using the guest account
  to confirm it wasn't a previous configuration on my regular account,
  and the issue is also present. Maybe it is uncommon for people to
  select items in nautilus with the keyboard arrows?

  I fixed it on my system for Ambiance by adding a dashed line
  decoration to

  /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css

  NautilusWindow * {
  -GtkPaned-handle-size: 1;
  outline-color: @selected_bg_color;
  outline-style: dashed;
  outline-width: 1px;
  outline-radius: 4px;
  outline-offset: -1px;
  }

  This may need to go in other selector properties, but it worked like
  this and I couldn't make it to work on any other selector.

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

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


[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

2016-07-01 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Confirmed => Unknown

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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


[Desktop-packages] [Bug 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys

2016-07-01 Thread Christian
Hello. 
*I want only use the keyboard. 
*In nautilus.
*list view.
*ubuntu 16.04 LTS Xenial Xerus.
My problem is that i can't see the focus  selected file or folder in nautilus. 
For example if I am in download folder i can select a file with ctrl+space then 
it file will have the selected item color (orange), then when i move down or up 
i can't see  what files has the focus.

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

Title:
  Nautilus invisible focused item when selecting files with Ctrl and
  arrow keys

Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 beta2 I noticed that selecting files with
  Ctrl and the arrow keys in Nautilus became more difficult since the
  active item had no decorations. I'm sure before there was some sort of
  dashed line around the active item's name, so this may be a
  regression.

  I have searched for any other bug report on this, or any other person
  complaining about it, without success. I tried using the guest account
  to confirm it wasn't a previous configuration on my regular account,
  and the issue is also present. Maybe it is uncommon for people to
  select items in nautilus with the keyboard arrows?

  I fixed it on my system for Ambiance by adding a dashed line
  decoration to

  /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css

  NautilusWindow * {
  -GtkPaned-handle-size: 1;
  outline-color: @selected_bg_color;
  outline-style: dashed;
  outline-width: 1px;
  outline-radius: 4px;
  outline-offset: -1px;
  }

  This may need to go in other selector properties, but it worked like
  this and I couldn't make it to work on any other selector.

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

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


[Desktop-packages] [Bug 1576565] Re: HDMI Sound drops out after screen blank/suspend (must use pacmd to reset0

2016-07-01 Thread Alberto Salvia Novella
** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  HDMI Sound drops out after screen blank/suspend (must use pacmd to
  reset0

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound is outputted through HDMI. Upon suspend/resume or resume from
  screen blank, output switches to analog and HDMI is not an available
  option from the GUI although still listed using "aplay-l". Sound
  returns after resetting HDMI as default using the following command:
  pacmd set-card-profile 1 output:hdmi-stereo-extra1+input:analog-stereo

  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 x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 29 09:52:09 2016
  InstallationDate: Installed on 2015-12-15 (135 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Sound works for a while, then breaks
  Title: [, Intel CougarPoint HDMI, Digital Out, HDMI] fails after a while
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (6 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-210:cvn:ct3:cvr:

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

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


[Desktop-packages] [Bug 1441331] Re: the menubar is showing fullscreen on !unity

2016-07-01 Thread Amr Ibrahim
*** This bug is a duplicate of bug 1502476 ***
https://bugs.launchpad.net/bugs/1502476

** This bug has been marked a duplicate of bug 1502476
   Totem menubar is displayed in fullscreen mode during gnome-flaskback session

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

Title:
  the menubar is showing fullscreen on !unity

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  The toolbar does not hide in fullscreen for wm . Work only Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  7 23:09:15 2015
  InstallationDate: Installed on 2015-02-16 (50 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

2016-07-01 Thread Alberto Salvia Novella
** Changed in: nvidia-graphics-drivers-361 (Ubuntu)
   Importance: Undecided => High

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in One Hundred Papercuts:
  Confirmed
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

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

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


[Desktop-packages] [Bug 1575899] Re: Text disappears after suspend

2016-07-01 Thread Christopher M. Penalver
Henrik Blidh, to further root cause, if you boot into a 4.2.x kernel
(the one from Ubuntu 15.10) does the issue go away?

** Tags added: regression-release

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

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

Title:
  Text disappears after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After waking my laptop running Xenial after it having been suspended,
  a lot of applications (e.g. Terminal and all settings) does not render
  most of the text that should be there. Some of it shows up on
  mouseover, but most is just permanently invisible until reboot of
  system.

  Detected a very similar bug after I created this issue:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 27 21:44:36 2016
  DistUpgraded: 2016-04-25 10:36:20,651 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2015-09-05 (234 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp.
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
   Bus 001 Device 005: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=6cc41411-46cb-4a14-a79a-038ee820f1aa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (2 days ago)
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 16:42:36 2016
  xserver.configfile: default
  xserver.errors:

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

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

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


[Desktop-packages] [Bug 1471621] Re: Untranslated strings shown [Spanish]

2016-07-01 Thread Amr Ibrahim
** Changed in: totem (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Untranslated strings shown [Spanish]

Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Some strings in Totem appear untranslated (Movie, Edit, View, Go,
  Ayuda > Contents,...). However, there are no untranslated strings in
  Launchpad, so it seems like a bug.

  OS Version: Ubuntu 15.04
  Package version: 3.14.2-0ubuntu2

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

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


[Desktop-packages] [Bug 1578848] Re: Current cell text illegible

2016-07-01 Thread Alberto Salvia Novella
** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Current cell text illegible

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The current cell text is illegible.  The two text parts seem to occupy
  the same space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May  5 15:24:44 2016
  InstallationDate: Installed on 2016-04-01 (34 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.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/1578848/+subscriptions

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


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

2016-07-01 Thread Alberto Salvia Novella
** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in [XPS 15 9550]

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

  In all cases, microphone works.

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

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

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


[Desktop-packages] [Bug 1574320] Re: package xserver-xorg-core 2:1.18.3-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/xorg/modules/libglamoregl.so', which is also in package xserve

2016-07-01 Thread Alberto Salvia Novella
** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

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

Title:
  package xserver-xorg-core 2:1.18.3-1ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/lib/xorg/modules/libglamoregl.so', which is
  also in package xserver-xorg-video-glamoregl 0.6.0-0ubuntu4

Status in One Hundred Papercuts:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  package xserver-xorg-core 2:1.18.3-1ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/lib/xorg/modules/libglamoregl.so', which is
  also in package xserver-xorg-video-glamoregl 0.6.0-0ubuntu4. The error
  occurred after upgrading to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   /dev/sda8: clean, 442377/1160992 files, 3820414/4638183 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 24 15:32:02 2016
  DistUpgraded: 2016-04-22 21:43:04,293 DEBUG disabling apt cron job (0o755)
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.131, 3.13.0-85-generic, x86_64: installed
   nvidia-304, 304.131, 4.4.0-21-generic, x86_64: installed
  ErrorMessage: trying to overwrite '/usr/lib/xorg/modules/libglamoregl.so', 
which is also in package xserver-xorg-video-glamoregl 0.6.0-0ubuntu4
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q33 Express Integrated Graphics Controller [8086:29d2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 82Q33 Express 
Integrated Graphics Controller [1462:7352]
  InstallationDate: Installed on 2014-05-14 (711 days ago)
  InstallationMedia: Custom 14.04 - Release amd64
  MachineType: Hewlett-Packard HP Compaq dx7400 Small Form Factor.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=d34389e0-e11f-4e62-8ca9-331d24db62ce ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: xorg-server
  Title: package xserver-xorg-core 2:1.18.3-1ubuntu2 failed to install/upgrade: 
trying to overwrite '/usr/lib/xorg/modules/libglamoregl.so', which is also in 
package xserver-xorg-video-glamoregl 0.6.0-0ubuntu4
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 09/03/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: MS7352 1.14
  dmi.board.name: 0AB8
  dmi.board.vendor: MSI
  dmi.chassis.asset.tag: INA90904TR
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrMS73521.14:bd09/03/2008:svnHewlett-Packard:pnHPCompaqdx7400SmallFormFactor.:pvr:rvnMSI:rn0AB8:rvr:cvnMSI:ct3:cvr:
  dmi.product.name: HP Compaq dx7400 Small Form Factor.
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 24 19:36:43 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB OPTICAL MOUSEMOUSE, id 8
   inputUSB2.0 PC CAMERA KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9963 
   vendor HWP
  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1598153] Re: ubuntu 16.04 thinkpad t560 死机

2016-07-01 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  ubuntu 16.04  thinkpad t560 死机

Status in xorg package in Ubuntu:
  New

Bug description:
  刚完全重新安装完成的系统用一段时间都有可能死机。查日志无明显错误信息!
  系统硬件如下:
  00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)
  00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-LM 
(rev 21)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
  04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.14-040414-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jul  1 20:18:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: tp-smapi, 0.41, 4.4.14-040414-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-07-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 004: ID 04f2:b52c Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 17ef:6050 Lenovo 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.14-040414-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET19W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET19W(1.06):bd03/10/2016:svnLENOVO:pn20FHCTO1WW:pvrThinkPadT560:rvnLENOVO:rn20FHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FHCTO1WW
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jul  1 19:06:20 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38562 
   vendor MEI
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1598316] [NEW] gtk2-engines-murrine desktop text shadow problem

2016-07-01 Thread makitso
Public bug reported:

Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
included an upgrade to gtk2-engines-murrine.  However, after the upgrade
and boot, the any desktop text, folder, launcher, etc. had a problem
with the text and shadow being quite far apart.

** Affects: gtk2-engines-murrine (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in gtk2-engines-murrine package in Ubuntu:
  New

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-murrine/+bug/1598316/+subscriptions

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


[Desktop-packages] [Bug 1294699] Re: Xubuntu desktop crashes in call to cairo after setting fixed-width bitmap (pcf) GTK font

2016-07-01 Thread Mathew Hodson
** Changed in: gtk2-engines-murrine (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  Xubuntu desktop crashes in call to cairo after setting fixed-width
  bitmap (pcf) GTK font

Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in gtk2-engines-murrine source package in Xenial:
  Fix Committed
Status in gtk2-engines-murrine package in Debian:
  Fix Released
Status in gtk2-engines-murrine package in Fedora:
  Unknown

Bug description:
  Reproduce: In Xubuntu (xfce), go to Settings Manager -> Appearance ->
  Fonts -> Default Font, select an installed fixed-width, bitmapped .pcf
  font (e.g. ProFont).  Desktop crashes; the new font does appear in the
  apport dialogs, but attempting to log back into the session, xfdesktop
  crashes with an assert in cairo, with gtk up the stacktrace:

  cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion
  `!scaled_font->cache_frozen' failed.

  To undo the change and be able to log in, I had to remove the GTK Font
  property in xfce4's xsettings.xml config file.  It would be a fair
  limitation if certain bitmap fonts failed over gracefully or were
  disallowed for selection, however, allowing an the interface to select
  the font without error, and then crashing and hanging the session on
  every login, leaving the config in a bad state should be fixed.

  uname:
  3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

  lsb_release:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  Similar report seen in archlinux/xfce4:
  https://bbs.archlinux.org/viewtopic.php?id=169433

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed Mar 19 10:41:54 2014
  InstallationDate: Installed on 2013-11-01 (138 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-murrine/+bug/1294699/+subscriptions

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


[Desktop-packages] [Bug 980660] Re: dvdauthor & mplex plugins missing

2016-07-01 Thread David VANTYGHEM
cdrdao and dvdauthor are needed by Brasero but they are not installed.
See https://bugs.launchpad.net/linuxmint/+bug/1598307

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

Title:
  dvdauthor & mplex plugins missing

Status in brasero package in Ubuntu:
  Confirmed

Bug description:
  after adding files as I click burn it shows mplex & dvd author plugins 
missing pls download it manually.
  But when I search it in ubuntu store it is not found

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: brasero 3.2.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Fri Apr 13 15:04:27 2012
  ExecutablePath: /usr/bin/brasero
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys

2016-07-01 Thread Christian
Hello. 
*I want only use the keyboard. 
*In nautilus.
*list view.
*ubuntu 16.04 LTS Xenial Xerus.
My problem is that i can't see the focus  selected file or folder in nautilus. 
For example if I am in download folder i can select a file with ctrl+space then 
it file will have the selected item color (orange), then when i move down or up 
i can't see  what files has the focus.

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

Title:
  Nautilus invisible focused item when selecting files with Ctrl and
  arrow keys

Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 beta2 I noticed that selecting files with
  Ctrl and the arrow keys in Nautilus became more difficult since the
  active item had no decorations. I'm sure before there was some sort of
  dashed line around the active item's name, so this may be a
  regression.

  I have searched for any other bug report on this, or any other person
  complaining about it, without success. I tried using the guest account
  to confirm it wasn't a previous configuration on my regular account,
  and the issue is also present. Maybe it is uncommon for people to
  select items in nautilus with the keyboard arrows?

  I fixed it on my system for Ambiance by adding a dashed line
  decoration to

  /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css

  NautilusWindow * {
  -GtkPaned-handle-size: 1;
  outline-color: @selected_bg_color;
  outline-style: dashed;
  outline-width: 1px;
  outline-radius: 4px;
  outline-offset: -1px;
  }

  This may need to go in other selector properties, but it worked like
  this and I couldn't make it to work on any other selector.

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

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


[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Vincent Cheng
A use case is that I would like to be able to ssh into my Ubuntu 16.04
laptop when I'm logged out, which is of course only possible if it's
connected to a network.

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1598303] [NEW] No HDMI sound with ATI Radeon HD 8570D & Asus VS238H-P Monitor

2016-07-01 Thread Mopar1973Man
Public bug reported:

As stated I've got a ATI Radeon HD 8570D video card with HDMI port. The
video part works fine but the audio does not function. The monitor
volume is turned up to 100%. Alsamixer shows 00 and unadjustable for the
volume control for this port. This is a Asus A78M-A motherboard with a
AMD A8-6600K APU with Radeon(tm) HD Graphics.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  michael2148 F pulseaudio
 /dev/snd/pcmC1D0p:   michael2148 F...m pulseaudio
 /dev/snd/controlC1:  michael2148 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jul  1 15:03:53 2016
InstallationDate: Installed on 2016-06-12 (19 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1204
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A78M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd12/05/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA78M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug trusty

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

Title:
  No HDMI sound with ATI Radeon HD 8570D & Asus VS238H-P Monitor

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As stated I've got a ATI Radeon HD 8570D video card with HDMI port.
  The video part works fine but the audio does not function. The monitor
  volume is turned up to 100%. Alsamixer shows 00 and unadjustable for
  the volume control for this port. This is a Asus A78M-A motherboard
  with a AMD A8-6600K APU with Radeon(tm) HD Graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2148 F pulseaudio
   /dev/snd/pcmC1D0p:   michael2148 F...m pulseaudio
   /dev/snd/controlC1:  michael2148 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul  1 15:03:53 2016
  InstallationDate: Installed on 2016-06-12 (19 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd12/05/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA78M-A:rvrRevX.0x: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/1598303/+subscriptions

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


[Desktop-packages] [Bug 1488254]

2016-07-01 Thread Dmitry-polukhin
abi_tag implementation was committed to Clang
http://reviews.llvm.org/D18035 Please start testing on your apps and
report issues.

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

Title:
  clang++ no longer ABI-compatible with g++

Status in LLVM:
  Confirmed
Status in llvm-toolchain-3.6 package in Ubuntu:
  Confirmed

Bug description:
  $ cat foo.cc
  #include 
  std::string hello = "Hello, world!\n";
  $ cat bar.cc
  #include 
  #include 
  extern std::string hello;
  int main() {
  std::cout << hello;
  return 0;
  }
  $ g++ -c foo.cc && g++ foo.o bar.cc && ./a.out
  Hello, world!
  $ clang++ -c foo.cc && clang++ foo.o bar.cc && ./a.out
  Hello, world!
  $ g++ -c foo.cc && clang++ foo.o bar.cc && ./a.out
  /tmp/bar-34fb23.o: In function `main':
  bar.cc:(.text+0x14): undefined reference to `hello'
  clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
  $ clang++ -c foo.cc && g++ foo.o bar.cc && ./a.out
  /tmp/ccqU38Mh.o: In function `main':
  bar.cc:(.text+0x5): undefined reference to `hello[abi:cxx11]'
  collect2: error: ld returned 1 exit status

  In practice, this means that many programs using C++ libraries other
  than libstdc++ fail to compile with clang++. For example, mosh fails
  with undefined references to
  google::protobuf::internal::empty_string_,
  google::protobuf::MessageLite::InitializationErrorString() const, and
  google::protobuf::MessageLite::SerializeAsString() const.

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

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


[Desktop-packages] [Bug 1575899] Re: Text disappears after suspend

2016-07-01 Thread Henrik Blidh
I had Ubuntu Desktop 15.10 installed on the laptop prior to 16.04, and
upgraded using the update-manager. I did not have this problem before.

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

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

Title:
  Text disappears after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  After waking my laptop running Xenial after it having been suspended,
  a lot of applications (e.g. Terminal and all settings) does not render
  most of the text that should be there. Some of it shows up on
  mouseover, but most is just permanently invisible until reboot of
  system.

  Detected a very similar bug after I created this issue:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 27 21:44:36 2016
  DistUpgraded: 2016-04-25 10:36:20,651 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2015-09-05 (234 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp.
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
   Bus 001 Device 005: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=6cc41411-46cb-4a14-a79a-038ee820f1aa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (2 days ago)
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 16:42:36 2016
  xserver.configfile: default
  xserver.errors:

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

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

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


[Desktop-packages] [Bug 1598300] [NEW] cups hang after a while

2016-07-01 Thread dominix
Public bug reported:

after 6 minutes or so, cups is not responding.
it do not produce error on the log, just stop working, worse, it exit with 0

⌌—⌍
|root@cupsmachine :~# systemctl status cups 
  |
|● cups.service - CUPS Scheduler
  |
|   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
|   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago   
  |
| Docs: man:cupsd(8)
  |
|  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)  
  |
| Main PID: 28686 (code=exited, status=0/SUCCESS)   
  |
|   
  |
|juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. 
  |
⌎—⌏

I got to launch it again, so I have finish with a cron job like
*/10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

but it is a dirty solution. I have no idea of what make it stop.
NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

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

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

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  New

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

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

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


[Desktop-packages] [Bug 914507] Re: Feature Request: special Browser window for logging in to WiFi Hotspots

2016-07-01 Thread Pat McGowan
Gaining a lot of heat with dupes

** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
Milestone: None => backlog

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

Title:
  Feature Request: special Browser window for logging in to WiFi
  Hotspots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Problem occurs with: Ubuntu, all versions
  Does not occur with: Fedora 21 and later, elementary OS 0.3 and later, OS X 
10.7 and later

  WiFi Hotspots normally redirect all traffic to a special IP address which 
provides a Welcome page with a login form. Accessing this server with another 
protocol does not work, which is not a problem for POP3, IMAP or SSH, but it is 
a problem if you connect by https, because your browser will recognise the 
wrong security certificate or the port is not even used (which is even better 
in my opinion).
  1) So if I open a browser it automatically tries to open its Start page which 
is https in my case (I use the HTTPS Everywhere plugin in my firefox). Because 
it uses https, I will not be redirected to the login page and am waiting in 
front of an empty page. Then I manually have to open a link which does not use 
https and get redirected to the login page.
  2) Another annoying thing are other users who open a saved browser session. 
All saved (http-)tabs will be redirected to the welcome page so that it does 
not make any sense anymore to save the browser session.
  3) Firefox also sometimes does compatibility checks and plugin updates at 
start time. These also fail when trying to login to a Hotspot network.

  How can we solve this problem?

  First, network manager should check if the connected wireless network is a 
Hotspot network. This chan be done by a simple http request to a stable and 
well-known page, for example http://gnome.org/netcheck which returns a known 
token (something like "Yes, you are connected to the Internet").
  - If the token is returned, everything is fine and the user has connection
  - If it does not receive this token but a redirect, it should open a special 
browser-window (not the default browser because of the reasons above) which 
allows to log-in to the network before other internet applications are started.
  - In any other case, network manager could try another server (backup) or 
stop probing.

  For known wireless networks, network manager could also provide a
  setting to disable/autodetect/force hotspot login.

  : "Whenever Ubuntu
  makes a new network connection, if 'Prompt whenever a new connection
  requires Web login' is checked, it should perform HTTP and DNS checks
  that the connection is valid. If it is not..."

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

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


[Desktop-packages] [Bug 1586800] Re: Captive portal experience is bad

2016-07-01 Thread Pat McGowan
*** This bug is a duplicate of bug 914507 ***
https://bugs.launchpad.net/bugs/914507

** This bug has been marked a duplicate of bug 914507
   Feature Request: special Browser window for logging in to WiFi Hotspots

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

Title:
  Captive portal experience is bad

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

Bug description:
  If you connect to a wifi AP that uses a captive portal (a login screen
  before granting full internet access, often seen in cafes and hotels)
  with your phone, the experience is quite lacking right now.

  - Webapps won't work. They try to connect to their site, are smart
  enough to know something is wrong when it doesn't get the right site
  back, and never finishes loading anything.

  - Apps in general fail to gracefully handle the case of getting back
  an unexpected result to their connections.

  - You may very reasonably auto connect to a wifi AP and not receive
  notifications for internet services like Telegram until you log in to
  the portal or turn off wifi.

  - If Browser is closed or OOM, when you open it, the last page you
  were at is overridden with the captive portal page. That's lost
  information! I hope you remember what it was.

  - If whatever page you try to go to first on the captive portal
  happens to be an https site, you will get an error instead of the
  portal.

  - If you know what to expect with the captive portal, you basically
  have to open a new browser tab and navigate to a site you have no
  intention of actually using just to get the log in page. It's a bit of
  a farce and not a great UX.

  - If you are *trying* to trigger the captive portal but the site you
  try happens to be cached (in some way? DNS or content caching or
  something), you will see that cached page instead of the portal. Which
  is unexpected for you. (I *think* this happens, maybe I am
  misremembering though.)

  And there are probably more pain points involved. This is just off the
  top of my head. Can we please guide the user through this experience
  instead of leaving them with a system that acts busted?

  Maybe prompt the user and open a page for them? Maybe keep using
  mobile data until the portal is past? Maybe don't tell apps that they
  are connected to the internet when they really aren't? Maybe have the
  Browser not overwrite the last open tab with a portal?

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

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


[Desktop-packages] [Bug 1598295] [NEW] $GTK_IM_MODULE ignored after upgrade

2016-07-01 Thread Constantine
Public bug reported:

After upgrade trusty → xenial, Compose key stopped producing configured
through ~/.XCompose characters for GTK3 only apps. To be sure that its
the GTK problem, I created a simple GTK3 window with textbox, launched
it like:

$ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a

and the textbox produces wrong characters for Compose key. (the
variables are actually set globally, I wrote them here just for
clarity).

XCompose works fine for all other toolkit's apps, including GTK2 and Qt
ones.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
$ apt-cache policy libgtk-3-0
libgtk-3-0:
  Installed: 3.18.9-1ubuntu3
  Candidate: 3.18.9-1ubuntu3
  Version table:
 *** 3.18.9-1ubuntu3 500
500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen

«Compose + - + space» would produce «— » in GTK3 apps.

4) What happened instead

«Compose + - + space» producing «~» in GTK3 apps.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  $GTK_IM_MODULE ignored after upgrade

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  After upgrade trusty → xenial, Compose key stopped producing
  configured through ~/.XCompose characters for GTK3 only apps. To be
  sure that its the GTK problem, I created a simple GTK3 window with
  textbox, launched it like:

  $ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a

  and the textbox produces wrong characters for Compose key. (the
  variables are actually set globally, I wrote them here just for
  clarity).

  XCompose works fine for all other toolkit's apps, including GTK2 and
  Qt ones.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy libgtk-3-0
  libgtk-3-0:
Installed: 3.18.9-1ubuntu3
Candidate: 3.18.9-1ubuntu3
Version table:
   *** 3.18.9-1ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  «Compose + - + space» would produce «— » in GTK3 apps.

  4) What happened instead

  «Compose + - + space» producing «~» in GTK3 apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1598295/+subscriptions

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


[Desktop-packages] [Bug 1528965] Re: "systemctl restart cups.service" hangs

2016-07-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  "systemctl restart cups.service" hangs

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Being stuck at a print job `sudo systemctl restart cups.service`
  doesn't show any progress for 30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  Uname: Linux 4.3.3-040303-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Wed Dec 23 23:09:06 2015
  InstallationDate: Installed on 2015-12-12 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat:
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(Netzwerk): 
hp:/net/HP_Color_LaserJet_MFP_M476dn?ip=192.168.179.42
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(USB): 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
  MachineType: LENOVO 20221
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(Netzwerk).ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(USB).ppd'] failed 
with exit code 2: grep: 
/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(Netzwerk).ppd: 
Keine Berechtigung
   grep: /etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(USB).ppd: 
Keine Berechtigung
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.3-040303-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: cups
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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


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

2016-07-01 Thread Douglas Santos
I was using LSB from Trusty's repo, and right now I've received the
update for this packages:   libappstream-glib8 lsb lsb-base lsb-core
lsb-invalid-mta lsb-printing lsb-release lsb-security

Also this packages was deleted with "autoremove":   libpod-plainer-perl
libqt4-opengl libqt4-svg lsb-cxx lsb-desktop  lsb-graphics lsb-languages
lsb-multimedia

The printer is still working perfectly. Thanks!

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

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

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

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

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

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

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

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

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

  lsb (9.20150826) unstable; urgency=low

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

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

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

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

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

  I see two possible solutions:

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

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

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

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


[Desktop-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

2016-07-01 Thread Jim Hodapp
@marcustomlinson: thanks for the reply. I wanted to make sure that was
intentional in the UX design. I could also think of situations where you
have your headphones on and you wouldn't want the ringtone to come
through the main speaker so as to not disturb the public around you
(assuming you would not answer the call and start talking because then
that would be a moot point).

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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


[Desktop-packages] [Bug 1591528] Re: Merge poppler 0.44.0-3 (main) from Debian unstable (main)

2016-07-01 Thread Launchpad Bug Tracker
This bug was fixed in the package poppler - 0.44.0-3ubuntu1

---
poppler (0.44.0-3ubuntu1) yakkety; urgency=medium

  * Merge with Debian. (LP: #1591528) Remaining changes:
- debian/control:
  + Don't build-depend on libopenjp2-7-dev since it's in universe
- debian/rules:
  + Use --disable-libopenjpeg
  * Dropped changes:
- Only suggest poppler-data since it's too big for CDs and
  language-selector automatically installs it after install
- debian/patches/revert_api_change.patch:
  + revert upstream commit that removed an enum, they claim it's
not an abi change because it's unused, but other packages (bindings)
rely on it to build still, we can drop the patch later once the
rdepends have been updated

poppler (0.44.0-3) unstable; urgency=medium

  * Switch from OpenJPEG 1.x to 2.x: (Closes: #826825)
- replace the libopenjpeg-dev build dependency with libopenjp2-7-dev
- pass --enable-libopenjpeg=openjpeg2 to configure, to be sure OpenJPEG 2.x
  is used

 -- Jeremy Bicha   Sat, 11 Jun 2016 18:16:34 -0400

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

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

Title:
  Merge poppler 0.44.0-3 (main) from Debian unstable (main)

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Please merge poppler 0.44.0-3 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
  ===
    * Updated for soname change libpoppler58 -> 61
    * New upstream version (soname update 57->58)
    * debian/patchres/revert_api_change.patch:
  - revert upstream commit that removed an enum, they claim it's
    not an abi change because it's unused, but other packages (bindings)
    rely on it to build still, we can drop the patch later once the
    redpends have been updated
    * Updated for soname change libpoppler56 -> 57
    * Updated for soname change libpoppler52 -> 56
    * Set hardening flags to "+all,-pie" to build with all hardening flags
  except -fPIE.
    * New upstream release (LP: #1449991)
    * Rename packages according to the new SONAMEs:
  - libpoppler49 -> libpoppler52
    * debian/libpoppler-glib8.symbols.in:
    * debian/libpoppler-qt4-4.symbols.in:
    * debian/libpoppler-qt5-1.symbols.in:
  - Updated
    * Explicitly pass --disable-libopenjpeg now - this support was auto-disabled
  before but now configure fails without this flag.
    * Rename packages according to the new SONAMEs:
  - libpoppler47 -> libpoppler49
    * Resynchronise with Debian, remaining changes:
  - Drop libopenjpeg-dev build depends, it is in universe.
  - Lower poppler-data to Suggests, it is too big for CD images,
    handled by language-selector.

  All of that is in the Debian package except for these:
  
  1. Drop libopenjpeg-dev build-depends, it is in universe
  - We still need this dropped, except it is now libopenjp2-7-dev
  2. Use --disable-libopenjpeg
  - Still needed
  3. debian/patches/revert_api_change.patch:
  - Not needed, see test build results below
  4. Lower poppler-data to Suggests since it's too big for CD images
  - Since we aren't as concerned about 1 or 2 MBs since we do DVDs instead
  of CDs, this seems like an obsolete change. See bug 893920 where we have
  language-selector install this for everyone after install anyway.

  $ apt show poppler-data
  Installed-Size: 12.4 MB
  Download-Size: 1,495 kB

  Changelog entries since current yakkety version 0.44.0-0ubuntu1:
  =

  poppler (0.44.0-3) unstable; urgency=medium

    * Switch from OpenJPEG 1.x to 2.x: (Closes: #826825)
  - replace the libopenjpeg-dev build dependency with libopenjp2-7-dev
  - pass --enable-libopenjpeg=openjpeg2 to configure, to be sure OpenJPEG 
2.x
    is used

   -- Pino Toscano   Thu, 09 Jun 2016 23:14:49 +0200

  poppler (0.44.0-2) unstable; urgency=medium

    * Upload to unstable. (See #823667)

   -- Pino Toscano   Fri, 27 May 2016 22:13:46 +0200

  poppler (0.44.0-1) experimental; urgency=medium

    * New upstream release.
    * Rename packages according to the new SONAMEs:
  - libpoppler60 -> libpoppler61
    * Update copyright.

   -- Pino Toscano   Sun, 22 May 2016 08:46:59 +0200

  poppler (0.43.0-1) experimental; urgency=medium

    * New upstream release: (Closes: #822644)
  - fixes pdfinfo man page (Closes: #813500)
  - fixes build with GCC 6 (Closes: #811901)
    * Rename packages according to the new SONAMEs:
  - libpoppler57 -> libpoppler60
    * Update copyright.
    * Update symbols files:
  - adapt to the different internal symbols with GCC 6
    * Update build dependencies:

[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

2016-07-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libunity (Ubuntu Xenial)
   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/1506744

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Committed
Status in libunity source package in Xenial:
  Confirmed

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2016-07-01 Thread Bruno Nova
Thank you people! My printer now works perfectly!

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

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

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

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

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

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

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

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

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

  lsb (9.20150826) unstable; urgency=low

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

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

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

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

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

  I see two possible solutions:

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

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

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

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


[Desktop-packages] [Bug 1589443] Re: I don't know what is the problem

2016-07-01 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  I don't know what is the problem

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I don't know what is the problem. Simply, I have just turned on
  xdiagnose and showed me some bag about nvidia m840.

  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_modeset nvidia wl
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun  6 11:58:53 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:16cd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:16cd]
  InstallationDate: Installed on 2016-06-03 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555LN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=7d0453c9-ea92-4810-b9f0-751c43c5d78f ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LN.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LN.309:bd08/14/2014:svnASUSTeKCOMPUTERINC.:pnX555LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jun  6 07:34:28 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones

2016-07-01 Thread Joakim Koed
I just downgraded to 6.0 from wily in xenial, now bluetooth is perfect.
Will hold those packages until this is resolved.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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


[Desktop-packages] [Bug 1589778] Re: I really don't know why a debug report was sent in

2016-07-01 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  I really don't know why a debug report was sent in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I dOn't know what is wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun  6 22:55:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-06-05 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Gigabyte Technology Co., Ltd. G1.Sniper H6
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=bd73f3ee-4d43-48cd-bdb5-5bcc9328e1a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper H6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperH6:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperH6:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper H6
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Desktop-packages] [Bug 1597389] Re: Resolution does not get set to 1024x900

2016-07-01 Thread Paul White
** Summary changed:

- Please fix probleam
+ Resolution does not get set to 1024x900

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

Title:
  Resolution does not get set to 1024x900

Status in xorg package in Ubuntu:
  New

Bug description:
  Resolution do not set 1024x900.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jun 29 20:52:15 2016
  InstallationDate: Installed on 2016-06-10 (19 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1578962] Re: [SRU] nm-applet crash with assertion failed for some users

2016-07-01 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager-applet -
1.2.2-0ubuntu1

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

  * Rebase to upstream stable point release (LP: #1578962)
  * Use git-pq to manage patches.
  * Patches updated:
- Make-sure-the-behavior-for-policykit-restricted-acti.patch
- Implement-support-for-hiding-rather-than-desensitizi.patch
  * cherry-pick from upstream post release
- wireless-security-fix-failed-assertion-in-default_fi.patch
- wireless-security-return-error-on-eap_method_validat.patch
- applet-remove-assert-s_con-from-applet_get_active_vp.patch
- apple-set-out_icon_name-for-WWAN-connections-for-ind.patch
  * Patches dropped:
- tests-run-tests-on-make-check.patch: merged upstream

 -- Aron Xu   Fri, 20 May 2016 18:09:18 +0800

** Changed in: network-manager-applet (Ubuntu Yakkety)
   Status: Triaged => 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/1578962

Title:
  [SRU] nm-applet crash with assertion failed for some users

Status in Network Manager Applet:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Yakkety:
  Fix Released
Status in network-manager-applet package in Debian:
  New

Bug description:
  [Impact]

  nm-applet crashes for some users with assertion failed

  [Test case]

  After installing the update, errors.ubuntu.com should receive a much
  smaller number of assertion failed crash reports.

  [Regression Potential]

  The assert is removed by upstream and thus backported to archive
  package because it was believed most of the assertion triggered are
  false positives, hence the potential of regression is having mis-
  functionality but the chance is fair low.

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

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


[Desktop-packages] [Bug 1546354] Re: rhythmbox crashed with SIGABRT in g_assertion_message()

2016-07-01 Thread Stefan Reine
*bump*
pls fix is very annoying

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

Title:
  rhythmbox crashed with SIGABRT in g_assertion_message()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  The program unexpectedly exited. Besides this event, to work properly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: rhythmbox 3.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
  Uname: Linux 4.4.0-5-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Feb 17 01:38:20 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2016-02-16 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160215)
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: rhythmbox
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: rhythmbox crashed with SIGABRT in raise()
  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/rhythmbox/+bug/1546354/+subscriptions

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


[Desktop-packages] [Bug 1598258] [NEW] /usr/bin/shotwell:11:gee_linked_list_iterator_real_next:photo_run_source_pixbuf_cache:photo_get_prefetched_copy:photo_get_pixbuf_with_options:photo_real_get_pixb

2016-07-01 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding shotwell.  This problem was most recently seen with version
0.22.0+git20160108.r1.f2fb1f7-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/206ef851d6a4e05f692eabad7d46367deb129228
contains more details.

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


** Tags: kylin-15.04 utopic vivid wily xenial

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

Title:
  
/usr/bin/shotwell:11:gee_linked_list_iterator_real_next:photo_run_source_pixbuf_cache:photo_get_prefetched_copy:photo_get_pixbuf_with_options:photo_real_get_pixbuf

Status in shotwell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding shotwell.  This problem was most recently seen with version
  0.22.0+git20160108.r1.f2fb1f7-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/206ef851d6a4e05f692eabad7d46367deb129228
  contains more details.

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

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


[Desktop-packages] [Bug 1575000] Re: font glyph corruption on dialog box

2016-07-01 Thread Bryan Quigley
Here is a debdiff for yakkety.

I've tested the binary produced for xenial (previous and pretty much
identical debdiff) and it fixes the issue on my hardware.  I don't have
hardware to test this on yakkety though (live sessions don't work well
on the hardware).

** Patch added: "xorg-server_1.18.3-1ubuntu2.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1575000/+attachment/4693737/+files/xorg-server_1.18.3-1ubuntu2.3.debdiff

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

Title:
   font glyph corruption on dialog box

Status in LibreOffice:
  Invalid
Status in xserver-xorg-driver-ati:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * This makes it impossible to read some text (usually yes/no questions) in 
Libreoffice.  This makes it more difficult to use LibreOffice on AMD graphics.

  [Test Case]

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  [Regression Potential]

   This modifies glamor to be used less.  There might be a potential for
  a performance hit in other cases?

  [Original Report]
  I get a font glyph corruption in various dialog boxes in libreoffice. This 
happens using the following graphic configuration:
    *-display
     description: VGA compatible controller
     product: Bonaire [FirePro W5100]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:03:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0

  I don't see this in other graphics (NVIDIA, INTEL).

  Steps to reproduce:

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  I attach a screenshot of the corrupted font.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 09:23:41 2016
  DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (191 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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: Mon Apr 25 08:20:34 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1575000/+subscriptions


[Desktop-packages] [Bug 1598246] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il sottoprocesso installato script di post-installation è stato terminato dal segnale (Ucciso)

2016-07-01 Thread Gabriele De Luca
Public bug reported:

I faced it while starting the Unity Desktop environment

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul  1 18:51:54 2016
ErrorMessage: il sottoprocesso installato script di post-installation è stato 
terminato dal segnale (Ucciso)
InstallationDate: Installed on 2016-05-15 (47 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il 
sottoprocesso installato script di post-installation è stato terminato dal 
segnale (Ucciso)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il
  sottoprocesso installato script di post-installation è stato terminato
  dal segnale (Ucciso)

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  I faced it while starting the Unity Desktop environment

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul  1 18:51:54 2016
  ErrorMessage: il sottoprocesso installato script di post-installation è stato 
terminato dal segnale (Ucciso)
  InstallationDate: Installed on 2016-05-15 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il 
sottoprocesso installato script di post-installation è stato terminato dal 
segnale (Ucciso)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1598246/+subscriptions

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


[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support

2016-07-01 Thread Alejandro J. Cura
** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

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

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

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

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


[Desktop-packages] [Bug 1575000] Re: font glyph corruption on dialog box

2016-07-01 Thread Ubuntu Foundations Team Bug Bot
The attachment "xorg-server_1.18.3-1ubuntu2.3.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
   font glyph corruption on dialog box

Status in LibreOffice:
  Invalid
Status in xserver-xorg-driver-ati:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * This makes it impossible to read some text (usually yes/no questions) in 
Libreoffice.  This makes it more difficult to use LibreOffice on AMD graphics.

  [Test Case]

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  [Regression Potential]

   This modifies glamor to be used less.  There might be a potential for
  a performance hit in other cases?

  [Original Report]
  I get a font glyph corruption in various dialog boxes in libreoffice. This 
happens using the following graphic configuration:
    *-display
     description: VGA compatible controller
     product: Bonaire [FirePro W5100]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:03:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0

  I don't see this in other graphics (NVIDIA, INTEL).

  Steps to reproduce:

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  I attach a screenshot of the corrupted font.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 09:23:41 2016
  DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (191 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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: Mon Apr 25 08:20:34 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1575000] Re: font glyph corruption on dialog box

2016-07-01 Thread Bryan Quigley
I don't think this is fixed in yakkety yet though (above debdiff is for
xenial).

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

Title:
   font glyph corruption on dialog box

Status in LibreOffice:
  Invalid
Status in xserver-xorg-driver-ati:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * This makes it impossible to read some text (usually yes/no questions) in 
Libreoffice.  This makes it more difficult to use LibreOffice on AMD graphics.

  [Test Case]

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  [Regression Potential]

   This modifies glamor to be used less.  There might be a potential for
  a performance hit in other cases?

  [Original Report]
  I get a font glyph corruption in various dialog boxes in libreoffice. This 
happens using the following graphic configuration:
    *-display
     description: VGA compatible controller
     product: Bonaire [FirePro W5100]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:03:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0

  I don't see this in other graphics (NVIDIA, INTEL).

  Steps to reproduce:

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  I attach a screenshot of the corrupted font.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 09:23:41 2016
  DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (191 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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: Mon Apr 25 08:20:34 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1575000/+subscriptions

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


[Desktop-packages] [Bug 1575000] Re: font glyph corruption on dialog box

2016-07-01 Thread Bryan Quigley
** Package changed: xserver-xorg-video-ati (Ubuntu) => xorg-server
(Ubuntu)

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

Title:
   font glyph corruption on dialog box

Status in LibreOffice:
  Invalid
Status in xserver-xorg-driver-ati:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * This makes it impossible to read some text (usually yes/no questions) in 
Libreoffice.  This makes it more difficult to use LibreOffice on AMD graphics.

  [Test Case]

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  [Regression Potential]

   This modifies glamor to be used less.  There might be a potential for
  a performance hit in other cases?

  [Original Report]
  I get a font glyph corruption in various dialog boxes in libreoffice. This 
happens using the following graphic configuration:
    *-display
     description: VGA compatible controller
     product: Bonaire [FirePro W5100]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:03:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0

  I don't see this in other graphics (NVIDIA, INTEL).

  Steps to reproduce:

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V

  I attach a screenshot of the corrupted font.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 09:23:41 2016
  DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (191 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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: Mon Apr 25 08:20:34 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1575000/+subscriptions

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


[Desktop-packages] [Bug 1556406] Re: Unable to perform disk Benchmark - Error seeking to offset 5121101824 (g-io-error-quark, 0)

2016-07-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1081019 ***
https://bugs.launchpad.net/bugs/1081019

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

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

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

Title:
  Unable to perform disk Benchmark - Error seeking to offset 5121101824
  (g-io-error-quark, 0)

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

Bug description:
  Steps to reproduce:
  1. Launch Gnome Disks (gnome-disks)
  2. Select "Drive" for benchmark
  3. Press "Gear" button, select "Benchmark" option
  4. Click "Start benchmark" button, click "Start benchmarking ..." button in 
"Benchmark Settings" windows.
  5. Get error message
Error seeking to offset 5121101824 (g-io-error-quark, 0)

  Expected results:
   get plot of speeds and access time, average speeds, average access time

  Actual results:
   error message - Error seeking to offset 5121101824 (g-io-error-quark, 0)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Mar 12 13:30:03 2016
  InstallationDate: Installed on 2015-12-12 (90 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

2016-07-01 Thread Marcus Tomlinson
@jhodapp: I'd say yes, makes sense to me that the ringtone should come
through both the speaker and the headphones.

E.g.
- when you're listening to music on headphones, you may not hear the phone 
speaker.
- you've got headphones plugged in but temporarily not using them, you'd still 
want to hear your phone ring.

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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


[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

2016-07-01 Thread Alberto Aguirre
So actually, fontconfig does not cache conf files at all... it caches
fonts but not conf files...

fontconfg needs support to also cache the result of the parsing of the
xml config file parsing. It seems a low priority effort for less than a
35ms improvement in startup.

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

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

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


[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

2016-07-01 Thread Alberto Aguirre
Also FcInitReinitialize and FcInitBringUptoDate both will do the same
thing the first time is called in the process, so wouldn't help for
startup either.


** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

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


[Desktop-packages] [Bug 1575000] Re: font glyph corruption on dialog box

2016-07-01 Thread Bryan Quigley
Yup, that patch worked for me.  Here's a debdiff of it.

** Patch added: "xorg-server_1.18.3-1ubuntu2.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1575000/+attachment/4693641/+files/xorg-server_1.18.3-1ubuntu2.3.debdiff

** Description changed:

+ [Impact] 
+  * This makes it impossible to read some text (usually yes/no questions) in 
Libreoffice.  This makes it more difficult to use LibreOffice on AMD graphics.
+ 
+ [Test Case]
+ 
+ 1. Open for instance LibreOffice Writer
+ 2. Copy some text to the clipboard
+ 3. Open the Paste Special dialog with CTRL-SHIFT-V
+ 
+ [Regression Potential]
+ 
+  This modifies glamor to be used less.  There might be a potential for a
+ performance hit in other cases?
+ 
+ [Original Report]
  I get a font glyph corruption in various dialog boxes in libreoffice. This 
happens using the following graphic configuration:
-   *-display   
-description: VGA compatible controller
-product: Bonaire [FirePro W5100]
-vendor: Advanced Micro Devices, Inc. [AMD/ATI]
-physical id: 0
-bus info: pci@:03:00.0
-version: 00
-width: 64 bits
-clock: 33MHz
-capabilities: vga_controller bus_master cap_list rom
-configuration: driver=radeon latency=0
+   *-display
+    description: VGA compatible controller
+    product: Bonaire [FirePro W5100]
+    vendor: Advanced Micro Devices, Inc. [AMD/ATI]
+    physical id: 0
+    bus info: pci@:03:00.0
+    version: 00
+    width: 64 bits
+    clock: 33MHz
+    capabilities: vga_controller bus_master cap_list rom
+    configuration: driver=radeon latency=0
  
  I don't see this in other graphics (NVIDIA, INTEL).
  
  Steps to reproduce:
  
  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
- 3. Open the Paste Special dialog with CTRL-SHIFT-V 
+ 3. Open the Paste Special dialog with CTRL-SHIFT-V
  
  I attach a screenshot of the corrupted font.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 09:23:41 2016
  DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
-  virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
+  virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
+  virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
-Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
+  Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
+    Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (191 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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: Mon Apr 25 08:20:34 2016
  xserver.configfile: default
  

[Desktop-packages] [Bug 1587305] Re: Add support for USB-LAN adapter

2016-07-01 Thread Pat McGowan
another ip6 related issue?

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

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Tony Espy (awe)

** Changed in: canonical-devices-system-image
   Status: Incomplete => 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/1587305

Title:
  Add support for USB-LAN adapter

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

Bug description:
  Some users contacted BQ because the USB-LAN adapters they own are not
  recognized by Frieza. They expect the device to automatically
  config/connect to their LAN network. They want the tablet to behave
  the same way as a Ubuntu PC does when LAN/Wi-Fi network is
  connected/disconnected. (I think they should be able to set the
  network through nmcli)

  Product: bq Aquaris E4.5, E5 & M10
  FW version: OTA-10.1
  HW version: MP

  STEPS TO REPRO:
  1. Connect DUT>USB-OTG>USB-LAN adapter>Rj45(picture attached)

  Actual Result:
  USB-LAN adapter is not recognized or it does not auto-connect to home LAN

  Expected Result:
  Whether Wifi is on or off, once LAN adapter is connected, it should 
auto-connect to home LAN

  Additional info: here is the link provided by one of the users
  http://de.anker.com/product/A7522012

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

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


[Desktop-packages] [Bug 1598183] Re: Operation not permitted while writing to symlinked fuse locations

2016-07-01 Thread Bug Watch Updater
** Changed in: gvfs
   Status: Unknown => Confirmed

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

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

Title:
  Operation not permitted while writing to symlinked fuse locations

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Affected releases:
  Ubuntu from 14.10+ (14.04 was working fine) 

  Steps to reproduce:
  1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
  2. Create a symlink to the fuse-mounted location e.g.
  cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
  3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.

  Expected result:
  File is saved.

  Actual result:
  An enigmatic error message is displayed
  (Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).

  The problems started with commit
  548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
  unless O_APPEND is given. Reverting it makes the issue disappear.

  I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
  # accessing via symlink
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=52
  vfs_open: -> Operation not supported
  # accessing via /run/user/(...)
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=110
  setup_input_stream: have stream
  setup_input_stream: doing read
  vfs_open: -> Success

  For reasons beyond my understanding the flags are different while
  accessing the file via the default gvfs-mountpoint causing the
  execusion to skip the modified section of client/gvfsdfusedaemon.c
  (returning -ENOTSUP).

  I am attaching the full vfs.debug created.
  Collapse All Comments
  Expand All Comments
  Add Comment

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

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


[Desktop-packages] [Bug 1598183] Re: Operation not permitted while writing to symlinked fuse locations

2016-07-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Operation not permitted while writing to symlinked fuse locations

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Affected releases:
  Ubuntu from 14.10+ (14.04 was working fine) 

  Steps to reproduce:
  1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
  2. Create a symlink to the fuse-mounted location e.g.
  cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
  3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.

  Expected result:
  File is saved.

  Actual result:
  An enigmatic error message is displayed
  (Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).

  The problems started with commit
  548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
  unless O_APPEND is given. Reverting it makes the issue disappear.

  I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
  # accessing via symlink
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=52
  vfs_open: -> Operation not supported
  # accessing via /run/user/(...)
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=110
  setup_input_stream: have stream
  setup_input_stream: doing read
  vfs_open: -> Success

  For reasons beyond my understanding the flags are different while
  accessing the file via the default gvfs-mountpoint causing the
  execusion to skip the modified section of client/gvfsdfusedaemon.c
  (returning -ENOTSUP).

  I am attaching the full vfs.debug created.
  Collapse All Comments
  Expand All Comments
  Add Comment

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

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


[Desktop-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

2016-07-01 Thread Jim Hodapp
Confirmed this, I am also seeing this issue. Is it normal to have the
ringtone go through the main speaker and the headphones as well when not
on silent mode?

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

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

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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


[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support

2016-07-01 Thread John McAleely
** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Tony Espy (awe)

** Changed in: canonical-devices-system-image
 Assignee: Tony Espy (awe) => John McAleely (john.mcaleely)

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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  [CTA] Enable WAPI support

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

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

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

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


[Desktop-packages] [Bug 1380364] Re: lightdm writes XDISPLAY instead of tty device name to utmp record

2016-07-01 Thread Sebastien Bacher
That change made the unity-control-center user's panel history dialog
stop working since it's filtering graphical session by they ":" entries
and now those are writted as "tty"

See https://code.launchpad.net/~seb128/unity-control-center/user-
graphical-sessions/+merge/210510 for some context

We either need to revert that change or to update u-c-c, note that the
issue should be sorted out before an eventual SRU of the lightdm change

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

Title:
  lightdm writes XDISPLAY instead of tty device name to utmp record

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.14 series:
  New
Status in Light Display Manager 1.16 series:
  New
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Until now, I've been using good old gdm-2.20.11 and wanted to switch
  to lightdm-1.12.1. If you list users logged in via the 'w' or 'who'
  command, it shows you who is logged in and what they are doing.
  Especially, on which tty. Example:

  USER TTYLOGIN@   IDLE   JCPU   PCPU WHAT
  usertty9  03Oct14 16days  1:52m  0.01s /bin/sh /etc/xdg/xfce4/xinitrc 
-- /etc/X11/xinit/xserverrc

  Also, 'who' gives this information:
  usertty9 Oct  3 22:34 (:20)

  However, lightdm does not follow that tradition. Instead, it prints :0
  instead of the actual tty, and something weird for other values (like
  ?xdm? instead of the idle value etc.)

  'w':
  USER TTYLOGIN@   IDLE   JCPU   PCPU WHAT
  user:019:50   ?xdm?  23.82s  0.01s /bin/sh /etc/xdg/xfce4/xinitrc 
-- /etc/X11/xinit/xserverrc

  Note: :0 is not tty, it is DISPLAY env.

  'who':
  user:0   2014-10-12 19:50 (:0)

  The same for this one. I wonder, is this a bug (to me it seems so,
  because for every other program the correct values are reported)?

  It is a problem for me, because I have written scripts for automation
  etc. that parse w and who output to determine which tty is in use by
  which DISPLAY.

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

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


[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

2016-07-01 Thread Sebastien Bacher
Note that currently the history dialog is empty under unity-control-
center, I've started discussing it with Robert who maintains lightdm in
context of bug #1380364

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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


[Desktop-packages] [Bug 1482636] Re: Ubuntu Touch on MX4 doesn't connect to WLAN with WEP

2016-07-01 Thread Pat McGowan
@paul did you add this task because you cannot currently connect to WEP?
We have no other such reports, so please add more info about your device
and Wifi configuration.

** Changed in: canonical-devices-system-image
   Status: New => Incomplete

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

Title:
  Ubuntu Touch on MX4 doesn't connect to WLAN with WEP

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

Bug description:
  Hi,

  while it is no problme to connect to a WLAN with WPA2 it is impossible
  to connect with a WLAN with WEP. Given that I'm the admin of the WLAN
  I changed to WPA temporarily and then it was no problem to connect.
  Thus it is not a hardware problem.

  Regards

  Ubuntu Touch Ver.  15.04 (r3)

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

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


[Desktop-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

2016-07-01 Thread Jim Hodapp
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: media-hub (Ubuntu)

** Also affects: pulseaudio (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu RTM:
  New

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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


[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Xavier Charpentier
A notification comes up the greeter advertising that wireless networks
are available. The greeter should at least not invite you to connect if
you can't...

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1598183] Re: Operation not permitted while writing to symlinked fuse locations

2016-07-01 Thread Dariusz Gadomski
** Bug watch added: GNOME Bug Tracker #768281
   https://bugzilla.gnome.org/show_bug.cgi?id=768281

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

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

Title:
  Operation not permitted while writing to symlinked fuse locations

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  Affected releases:
  Ubuntu from 14.10+ (14.04 was working fine) 

  Steps to reproduce:
  1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
  2. Create a symlink to the fuse-mounted location e.g.
  cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
  3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.

  Expected result:
  File is saved.

  Actual result:
  An enigmatic error message is displayed
  (Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).

  The problems started with commit
  548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
  unless O_APPEND is given. Reverting it makes the issue disappear.

  I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
  # accessing via symlink
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=52
  vfs_open: -> Operation not supported
  # accessing via /run/user/(...)
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=110
  setup_input_stream: have stream
  setup_input_stream: doing read
  vfs_open: -> Success

  For reasons beyond my understanding the flags are different while
  accessing the file via the default gvfs-mountpoint causing the
  execusion to skip the modified section of client/gvfsdfusedaemon.c
  (returning -ENOTSUP).

  I am attaching the full vfs.debug created.
  Collapse All Comments
  Expand All Comments
  Add Comment

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

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


[Desktop-packages] [Bug 1598183] [NEW] Operation not permitted while writing to symlinked fuse locations

2016-07-01 Thread Dariusz Gadomski
Public bug reported:

Affected releases:
Ubuntu from 14.10+ (14.04 was working fine) 

Steps to reproduce:
1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
2. Create a symlink to the fuse-mounted location e.g.
cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.

Expected result:
File is saved.

Actual result:
An enigmatic error message is displayed
(Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).

The problems started with commit
548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
unless O_APPEND is given. Reverting it makes the issue disappear.

I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
# accessing via symlink
vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
open_common: flags=52
vfs_open: -> Operation not supported
# accessing via /run/user/(...)
vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
open_common: flags=110
setup_input_stream: have stream
setup_input_stream: doing read
vfs_open: -> Success

For reasons beyond my understanding the flags are different while
accessing the file via the default gvfs-mountpoint causing the execusion
to skip the modified section of client/gvfsdfusedaemon.c (returning
-ENOTSUP).

I am attaching the full vfs.debug created.
Collapse All Comments
Expand All Comments
Add Comment

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


** Tags: regression-release sts

** Tags added: sts

** Tags added: regression-release

** Description changed:

- Platform:
- Ubuntu from 14.10+
+ Affected releases:
+ Ubuntu from 14.10+ (14.04 was working fine) 
  
  Steps to reproduce:
  1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
  2. Create a symlink to the fuse-mounted location e.g.
  cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
  3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.
  
  Expected result:
  File is saved.
  
  Actual result:
  An enigmatic error message is displayed
  (Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).
  
  The problems started with commit
  548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
  unless O_APPEND is given. Reverting it makes the issue disappear.
  
  I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
  # accessing via symlink
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=52
  vfs_open: -> Operation not supported
  # accessing via /run/user/(...)
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=110
  setup_input_stream: have stream
  setup_input_stream: doing read
  vfs_open: -> Success
  
  For reasons beyond my understanding the flags are different while
  accessing the file via the default gvfs-mountpoint causing the execusion
  to skip the modified section of client/gvfsdfusedaemon.c (returning
  -ENOTSUP).
  
  I am attaching the full vfs.debug created.
  Collapse All Comments
  Expand All Comments
  Add Comment

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

Title:
  Operation not permitted while writing to symlinked fuse locations

Status in gvfs package in Ubuntu:
  New

Bug description:
  Affected releases:
  Ubuntu from 14.10+ (14.04 was working fine) 

  Steps to reproduce:
  1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
  2. Create a symlink to the fuse-mounted location e.g.
  cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
  3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.

  Expected result:
  File is saved.

  Actual result:
  An enigmatic error message is displayed
  (Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).

  The problems started with commit
  548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
  unless O_APPEND is given. Reverting it makes the issue disappear.

  I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
  # accessing via symlink
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: 

[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

2016-07-01 Thread Pat McGowan
fwiw I am connecting with a 27 character passphrase on WPA

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Status: Confirmed => Incomplete

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

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

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


[Desktop-packages] [Bug 1588126] Re: [OTA-11] Wifi never connects since installing OTA-11

2016-07-01 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

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

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Tony Espy (awe)

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

Title:
  [OTA-11] Wifi never connects since installing OTA-11

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

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

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

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


[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

2016-07-01 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
Milestone: backlog => 13

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Alberto Aguirre (albaguirre)

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

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

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


[Desktop-packages] [Bug 1598162] Re: nautilus crashed with SIGABRT in g_assertion_message()

2016-07-01 Thread Apport retracing service
*** This bug is a duplicate of bug 1554884 ***
https://bugs.launchpad.net/bugs/1554884

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  New

Bug description:
  I was trying to Move a folder with sub-folders up a level.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.11
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul  1 14:21:01 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'smallest'"
   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-09-17 (653 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev postgres sambashare sudo www-data

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

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


[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Joakim Koed
I agree the idea is good, it's just hard to figure out what is wrong when you 
are "greeted" with permissions in that nasty "pop op".
I personally don't care anymore, because now I know how to fix it, but for 
future users, it seems stupid.

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1547900] Re: marlett.ttf crashes gnome-font-viewer, is unviewable in character map

2016-07-01 Thread Sebastien Bacher
** Also affects: gnome-font-viewer via
   https://bugzilla.gnome.org/show_bug.cgi?id=764238
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-font-viewer (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  marlett.ttf crashes gnome-font-viewer, is unviewable in character map

Status in Gnome Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 current as of 20 February 2016.
  gnome-font-viewer:  Installed: 3.16.2-1build1
  gucharmap:  Installed: 1:3.18.2-1ubuntu1

  Opening any version of marlett.ttf (the Windows interface font) will cause 
gnome-font-viewer to crash.
  Selecting Marlett in gnome-character-map does not change the font used in the 
grid.

  appears several times in dmesg:
  [128342.436711] gnome-font-view[30917]: segfault at 0 ip 7f31f05297aa sp 
7ffc23f7d7d8 error 4 in libc-2.21.so[7f31f049e000+1c]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1547900/+subscriptions

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


[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Sebastien Bacher
ok, so it's a security choice from upstream, unsure if we should change
the default ... what's the usecase to connect from the greeter? it's not
a session you can do anything with so that seems a bit pointless. In any
case the applet could probably deal better with the situation by not
listing those a selectable or telling you in the error dialog what to do
to make them work

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

2016-07-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-004

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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


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

2016-07-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-004

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

Title:
  lightdm changing resolution

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

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

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

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

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

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


[Desktop-packages] [Bug 1503758] Re: /usr/lib/unity-settings-daemon/unity-settings-daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapp

2016-07-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-004

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

Title:
  /usr/lib/unity-settings-daemon/unity-settings-
  
daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapping

Status in OEM Priority Project:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-settings-daemon.  This problem was most recently seen
  with version 15.04.1+15.10.20150818-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6e9dcc008057a747fb5c2e65cd47f07e5b672724
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1503758/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

2016-07-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-004

-- 
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:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Confirmed
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 1596397] Re: When restarting from sleep, the Wi-Fi widget doesn't display the correct access point

2016-07-01 Thread Andrea Azzarone
** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: unity (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/1596397

Title:
  When restarting from sleep, the Wi-Fi widget doesn't display the
  correct access point

Status in network-manager package in Ubuntu:
  New

Bug description:
  Normally, the access point I usually connect to shows up in the Wi-Fi
  menu. However, when rebooting from sleep, this Wi-Fi network isn't
  shown on the menu, even after disabling and re-enabling Wi-Fi or
  disabling and re-enabling networking. When I restart the computer, the
  Wi-Fi network I want shows up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160526.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jun 26 22:38:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2016-06-18 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0445 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 5986:055e Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20404
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0CN21WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Flex 2-14
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Flex 2-14
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN21WW:bd03/21/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14:
  dmi.product.name: 20404
  dmi.product.version: Lenovo Flex 2-14
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jun 26 22:35:29 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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


[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-07-01 Thread monte
Here is my syslog after resume. Sorry for so long time without reply. 
And there are errors in log related to bluez service, as it don't work properly 
after suspend either, so I need to use script to restart it automatically on 
resume.

** Attachment added: "syslog debug"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576747/+attachment/4693456/+files/syslog_debug

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   

[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Joakim Koed
This is apparently by choice in the newer versions of network-manager.
Strange that it does not affect GDM though. But like I said you can
change it in network-mananger applet/GUI.

https://git.gnome.org/browse/network-manager-
applet/commit/?id=0c92debe95f62a7f677e28eb8dee92728d702a0a

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1547900] Re: marlett.ttf crashes gnome-font-viewer, is unviewable in character map

2016-07-01 Thread John Tejada
** Also affects: gnome-font-viewer
   Importance: Undecided
   Status: New

** No longer affects: gnome-font-viewer

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

Title:
  marlett.ttf crashes gnome-font-viewer, is unviewable in character map

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 current as of 20 February 2016.
  gnome-font-viewer:  Installed: 3.16.2-1build1
  gucharmap:  Installed: 1:3.18.2-1ubuntu1

  Opening any version of marlett.ttf (the Windows interface font) will cause 
gnome-font-viewer to crash.
  Selecting Marlett in gnome-character-map does not change the font used in the 
grid.

  appears several times in dmesg:
  [128342.436711] gnome-font-view[30917]: segfault at 0 ip 7f31f05297aa sp 
7ffc23f7d7d8 error 4 in libc-2.21.so[7f31f049e000+1c]

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2016-07-01 Thread Kevin Brubeck Unhammer
Argh, missed a “”→"" (I stupidly copy-pasted my script from another
place I'd posted it instead of from the actual file …). Trying again:


sudo mkdir -p /usr/local/bin

echo '#!/bin/sh
n="$(fgconsole)" || exit 1
case "$n" in
[0-9]) /bin/chvt 1; /bin/chvt "$n";sleep 1;;
*) echo "error from $0; fgconsole gave $n" >/tmp/VTswitch.log
esac
' | sudo tee /usr/local/bin/VTswitch

sudo chmod +x /usr/local/bin/VTswitch

sudo mkdir -p /etc/lightdm/lightdm.conf.d

echo '[Seat:*]
session-cleanup-script=/usr/local/bin/VTswitch
' | sudo tee /etc/lightdm/lightdm.conf.d/50-vtswitch.conf

sudo systemctl restart lightdm

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

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

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

  After unlocking screen cursor is invisible.

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

  

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

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

  this is xubuntu using the xfce window manager.

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

  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1598125] [NEW] black borders

2016-07-01 Thread yhkldq
Public bug reported:

there are black borders surrounding my menus and my terminal is black

ProblemType: Bug
DistroRelease: Kali 2016.1
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jul  1 12:56:27 2016
DistUpgraded: Fresh install
DistroCodename: kali-rolling
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146d]
InstallationDate: Installed on 2016-06-28 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 003: ID 054c:0439 Sony Corp. 
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP ProBook 6450b
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
hostname=UUID=8a2fd2c2-cc0d-4d79-9ce4-e8fc607c651a ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CDE Ver. F.01
dmi.board.name: 146D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 73.11
dmi.chassis.asset.tag: CNU03203BG
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CDEVer.F.01:bd06/25/2010:svnHewlett-Packard:pnHPProBook6450b:pvr:rvnHewlett-Packard:rn146D:rvrKBCVersion73.11:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6450b
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.68-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.2-1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jul  1 12:08:27 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug compiz-0.9 kali-rolling third-party-packages ubuntu

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

Title:
  black borders

Status in xorg package in Ubuntu:
  New

Bug description:
  there are black borders surrounding my menus and my terminal is black

  ProblemType: Bug
  DistroRelease: Kali 2016.1
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jul  1 12:56:27 2016
  DistUpgraded: Fresh install
  DistroCodename: kali-rolling
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146d]
  InstallationDate: Installed on 2016-06-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 054c:0439 Sony Corp. 
   Bus 002 Device 002: ID 

[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Joakim Koed
It is NOW* disabled

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

2016-07-01 Thread Joakim Koed
Hi again.

After talking to Thomas Haller from redhat, it seems that we can make it
work just by enabling "all users may connect to this network" in network
manager GUI.

Now the questions is, why did that change from 15.10 to 16.04? It is not
disabled by default, instead of being enabled like it should!

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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


[Desktop-packages] [Bug 1590244] Re: Upgrading upower package caused forced reboot

2016-07-01 Thread Sebastien Bacher
Could you get a "upower -m > log" and reinstall the package and install
the log after reboot?

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

Title:
  Upgrading upower package caused forced reboot

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When upower was updated, the system claimed that my UPS was empty.
  The system then proceeded to shut down.  On reboot, the UPS was fully
  charged as expected.

  This is a major data loss concern.  The system shut down while
  upgrading packages.  Perhaps the bug is in the handling of my specific
  UPS but it's still important.

  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  jlquinn@cerberus:~$ apt-cache policy upower
  upower:
Installed: 0.99.4-2ubuntu0.2
Candidate: 0.99.4-2ubuntu0.2
Version table:
   *** 0.99.4-2ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.99.4-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  output of lsusb -v for my UPS

  Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x0764 Cyber Power System, Inc.
idProduct  0x0501 CP1500 AVR UPS
bcdDevice0.01
iManufacturer   3 CPS
iProduct1 CP625HGa
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   34
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass  0 No Subclass
bInterfaceProtocol  0 None
iInterface  0 
  HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID   1.10
bCountryCode   33 US
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 410
   Report Descriptors: 
 ** UNAVAILABLE **
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0008  1x 8 bytes
  bInterval  10
  Device Status: 0x
(Bus Powered)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 00:27:23 2016
  InstallationDate: Installed on 2016-05-30 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: upower
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (7 days ago)

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

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


[Desktop-packages] [Bug 1590244] Re: Upgrading upower package caused forced reboot

2016-07-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Upgrading upower package caused forced reboot

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When upower was updated, the system claimed that my UPS was empty.
  The system then proceeded to shut down.  On reboot, the UPS was fully
  charged as expected.

  This is a major data loss concern.  The system shut down while
  upgrading packages.  Perhaps the bug is in the handling of my specific
  UPS but it's still important.

  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  jlquinn@cerberus:~$ apt-cache policy upower
  upower:
Installed: 0.99.4-2ubuntu0.2
Candidate: 0.99.4-2ubuntu0.2
Version table:
   *** 0.99.4-2ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.99.4-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  output of lsusb -v for my UPS

  Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x0764 Cyber Power System, Inc.
idProduct  0x0501 CP1500 AVR UPS
bcdDevice0.01
iManufacturer   3 CPS
iProduct1 CP625HGa
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   34
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass  0 No Subclass
bInterfaceProtocol  0 None
iInterface  0 
  HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID   1.10
bCountryCode   33 US
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 410
   Report Descriptors: 
 ** UNAVAILABLE **
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0008  1x 8 bytes
  bInterval  10
  Device Status: 0x
(Bus Powered)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 00:27:23 2016
  InstallationDate: Installed on 2016-05-30 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: upower
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (7 days ago)

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

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


[Desktop-packages] [Bug 1598105] Re: updating package does a hard shutdown

2016-07-01 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1590244 ***
https://bugs.launchpad.net/bugs/1590244

** This bug has been marked a duplicate of bug 1590244
   Upgrading upower package caused forced reboot

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

Title:
  updating package does a hard shutdown

Status in upower package in Ubuntu:
  New

Bug description:
  I have a Eaton 3S 550 UPS connected via USB to my Linux machine. On a
  default install of Ubuntu 16.04 the UPS is not properly recognized and
  shows as empty in the power menu. The system does not shut down as the
  action to "When power is critically empty" in the power configuration
  panel is by default set to nothing.

  Upgrading the package causes a notification to pop up, stating that the power 
is critically low and the system will shut down shortly. The system then shuts 
down despite the upgrade of other packages still being in progress.
  Upon restart the forced shutdown does not reoccur.

  I wish to stress that this bug is not filed against this specific
  model of UPS not being properly recognized on a clean install, but
  instead that during upgrade the default action for critically low
  power seems to change for a short period, causing the shutdown of the
  computer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Jul  1 12:20:03 2016
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2016-07-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2016-07-01 Thread Apport retracing service
** Tags added: yakkety

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.17.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Feb  8 17:07:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2015-04-30 (283 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 
panic=-1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffc9e34fc8) at libc-start.c:289
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  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.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Mon Feb  8 17:08:14 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 9847 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.3-2ubuntu2

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

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


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

2016-07-01 Thread Apport retracing service
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  from update and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.6.0-7.8-generic 4.6.0
  Uname: Linux 4.6.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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  367.27  Thu Jun  9 18:53:27 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-4ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  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: Tue Jun 28 14:59:16 2016
  DistUpgraded: 2016-06-13 21:19:44,198 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.6.0-7-generic, x86_64: installed
   nvidia-367, 367.27, 4.6.0-7-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] 
[19da:1375]
  InstallationDate: Installed on 2016-06-06 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-7-generic 
root=UUID=17c413ea-eca0-4425-9b8f-8b77561bd0fa ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x561b36c411c0, argc=11, argv=0x7fffa27e4948, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffa27e4938) at ../csu/libc-start.c:291
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to yakkety on 2016-06-14 (17 days ago)
  UserGroups:
   
  dmi.bios.date: 05/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: 

[Desktop-packages] [Bug 1589097] Re: gnome-menus and bamfdaemon failed to install/upgrade: triggers looping, abandoned

2016-07-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/bamf/bamf-ubuntu-xenial-landing-063

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

Title:
  gnome-menus and bamfdaemon failed to install/upgrade: triggers
  looping, abandoned

Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Occurred during upgrade from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jun  4 07:35:11 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-04 (0 days ago)

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

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


[Desktop-packages] [Bug 1598105] [NEW] updating package does a hard shutdown

2016-07-01 Thread Alex
Public bug reported:

I have a Eaton 3S 550 UPS connected via USB to my Linux machine. On a
default install of Ubuntu 16.04 the UPS is not properly recognized and
shows as empty in the power menu. The system does not shut down as the
action to "When power is critically empty" in the power configuration
panel is by default set to nothing.

Upgrading the package causes a notification to pop up, stating that the power 
is critically low and the system will shut down shortly. The system then shuts 
down despite the upgrade of other packages still being in progress.
Upon restart the forced shutdown does not reoccur.

I wish to stress that this bug is not filed against this specific model
of UPS not being properly recognized on a clean install, but instead
that during upgrade the default action for critically low power seems to
change for a short period, causing the shutdown of the computer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: upower 0.99.4-2ubuntu0.2
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri Jul  1 12:20:03 2016
ExecutablePath: /usr/lib/upower/upowerd
InstallationDate: Installed on 2016-07-01 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: upower (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 upower in Ubuntu.
https://bugs.launchpad.net/bugs/1598105

Title:
  updating package does a hard shutdown

Status in upower package in Ubuntu:
  New

Bug description:
  I have a Eaton 3S 550 UPS connected via USB to my Linux machine. On a
  default install of Ubuntu 16.04 the UPS is not properly recognized and
  shows as empty in the power menu. The system does not shut down as the
  action to "When power is critically empty" in the power configuration
  panel is by default set to nothing.

  Upgrading the package causes a notification to pop up, stating that the power 
is critically low and the system will shut down shortly. The system then shuts 
down despite the upgrade of other packages still being in progress.
  Upon restart the forced shutdown does not reoccur.

  I wish to stress that this bug is not filed against this specific
  model of UPS not being properly recognized on a clean install, but
  instead that during upgrade the default action for critically low
  power seems to change for a short period, causing the shutdown of the
  computer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Jul  1 12:20:03 2016
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2016-07-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1294699] Re: Xubuntu desktop crashes in call to cairo after setting fixed-width bitmap (pcf) GTK font

2016-07-01 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk2-engines-murrine - 0.98.2-0ubuntu3

---
gtk2-engines-murrine (0.98.2-0ubuntu3) yakkety; urgency=medium

  * pango_cairo_update_layout.patch: new patch. Fixes crashes of
various apps when bitmap font like Terminus is used as default
system font. (LP: #1294699)

 -- Vlad Orlov   Sat, 20 Feb 2016 10:41:39 +0300

** Changed in: gtk2-engines-murrine (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Xubuntu desktop crashes in call to cairo after setting fixed-width
  bitmap (pcf) GTK font

Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in gtk2-engines-murrine source package in Xenial:
  Fix Committed
Status in gtk2-engines-murrine package in Debian:
  Fix Released
Status in gtk2-engines-murrine package in Fedora:
  Unknown

Bug description:
  Reproduce: In Xubuntu (xfce), go to Settings Manager -> Appearance ->
  Fonts -> Default Font, select an installed fixed-width, bitmapped .pcf
  font (e.g. ProFont).  Desktop crashes; the new font does appear in the
  apport dialogs, but attempting to log back into the session, xfdesktop
  crashes with an assert in cairo, with gtk up the stacktrace:

  cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion
  `!scaled_font->cache_frozen' failed.

  To undo the change and be able to log in, I had to remove the GTK Font
  property in xfce4's xsettings.xml config file.  It would be a fair
  limitation if certain bitmap fonts failed over gracefully or were
  disallowed for selection, however, allowing an the interface to select
  the font without error, and then crashing and hanging the session on
  every login, leaving the config in a bad state should be fixed.

  uname:
  3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

  lsb_release:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  Similar report seen in archlinux/xfce4:
  https://bbs.archlinux.org/viewtopic.php?id=169433

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed Mar 19 10:41:54 2014
  InstallationDate: Installed on 2013-11-01 (138 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-murrine/+bug/1294699/+subscriptions

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


[Desktop-packages] [Bug 1598097] [NEW] frozen screen and system

2016-07-01 Thread m3asmi
Public bug reported:

some times the screen is frozen 
and when I log out of the session the system froze and cannot go into ttyS 
the message is like the driver of the graphic is not good

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jul  1 10:27:45 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:3804]
InstallationDate: Installed on 2016-06-24 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 002: ID 8086:0a66 Intel Corp. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80NT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=009e3c20-6d0e-4f82-a892-f0750d5de684 ro quiet splash radeon.runpm=0 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: CFCN21WW(V1.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo ideapad 5
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 500-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrCFCN21WW(V1.03):bd08/10/2015:svnLENOVO:pn80NT:pvrLenovoideapad500-15ISK:rvnLENOVO:rnLenovoideapad5:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad500-15ISK:
dmi.product.name: 80NT
dmi.product.version: Lenovo ideapad 500-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jul  1 09:18:59 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14829 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug third-party-packages 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/1598097

Title:
  frozen screen and system

Status in xorg package in Ubuntu:
  New

Bug description:
  some times the screen is frozen 
  and when I log out of the session the system froze and cannot go into ttyS 
  the message is like the driver of the graphic is not good

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jul  1 10:27:45 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3804]
  InstallationDate: Installed on 2016-06-24 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8086:0a66 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80NT
  

[Desktop-packages] [Bug 1598060] Re: /usr/bin/nm-applet:6:g_assertion_message:g_assertion_message_expr:create_info_label_security:info_dialog_add_page:info_dialog_update

2016-07-01 Thread Bug Watch Updater
** Changed in: network-manager-applet
   Status: Unknown => Confirmed

** Changed in: network-manager-applet
   Importance: Unknown => Medium

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

Title:
  /usr/bin/nm-
  
applet:6:g_assertion_message:g_assertion_message_expr:create_info_label_security:info_dialog_add_page:info_dialog_update

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 1.2.0-0ubuntu0.16.04.3, the problem page at
  https://errors.ubuntu.com/problem/ec38a9bbc2a1641599eec2625cff8f1ca5697621
  contains more details.

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

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


[Desktop-packages] [Bug 1598060] Re: /usr/bin/nm-applet:6:g_assertion_message:g_assertion_message_expr:create_info_label_security:info_dialog_add_page:info_dialog_update

2016-07-01 Thread Sebastien Bacher
sent upstream to https://bugzilla.gnome.org/show_bug.cgi?id=768270

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

Title:
  /usr/bin/nm-
  
applet:6:g_assertion_message:g_assertion_message_expr:create_info_label_security:info_dialog_add_page:info_dialog_update

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 1.2.0-0ubuntu0.16.04.3, the problem page at
  https://errors.ubuntu.com/problem/ec38a9bbc2a1641599eec2625cff8f1ca5697621
  contains more details.

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

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


[Desktop-packages] [Bug 1294699] Re: Xubuntu desktop crashes in call to cairo after setting fixed-width bitmap (pcf) GTK font

2016-07-01 Thread Vlad Orlov
Thanks - but please don't forget about Trusty users as well.

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

Title:
  Xubuntu desktop crashes in call to cairo after setting fixed-width
  bitmap (pcf) GTK font

Status in gtk2-engines-murrine package in Ubuntu:
  Fix Committed
Status in gtk2-engines-murrine source package in Xenial:
  Fix Committed
Status in gtk2-engines-murrine package in Debian:
  Fix Released
Status in gtk2-engines-murrine package in Fedora:
  Unknown

Bug description:
  Reproduce: In Xubuntu (xfce), go to Settings Manager -> Appearance ->
  Fonts -> Default Font, select an installed fixed-width, bitmapped .pcf
  font (e.g. ProFont).  Desktop crashes; the new font does appear in the
  apport dialogs, but attempting to log back into the session, xfdesktop
  crashes with an assert in cairo, with gtk up the stacktrace:

  cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion
  `!scaled_font->cache_frozen' failed.

  To undo the change and be able to log in, I had to remove the GTK Font
  property in xfce4's xsettings.xml config file.  It would be a fair
  limitation if certain bitmap fonts failed over gracefully or were
  disallowed for selection, however, allowing an the interface to select
  the font without error, and then crashing and hanging the session on
  every login, leaving the config in a bad state should be fixed.

  uname:
  3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

  lsb_release:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  Similar report seen in archlinux/xfce4:
  https://bbs.archlinux.org/viewtopic.php?id=169433

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed Mar 19 10:41:54 2014
  InstallationDate: Installed on 2013-11-01 (138 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-murrine/+bug/1294699/+subscriptions

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


  1   2   >