Re: [Desktop-packages] [Bug 1574324] [NEW] pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-25 Thread Luke Yelavich
Ok, as suggested by Simon, I've added some extra debugging to
PulseAudio, with the Ubuntu Touch patches re-enabled. At the time of
writing, this has just been pushed to my personal package archive for
Xenial.

If folks experiencing this problem could install the version of
PulseAudio from my PPA, and get a log as outlined at
https://wiki.ubuntu.com/PulseAudio/Log that would be great.I suggest
starting pulseaudio, then turning on your bluetooth device.

Attached is my own log, for reference.


** Attachment added: "pulse.log"
   https://bugs.launchpad.net/bugs/1574324/+attachment/4748670/+files/pulse.log

-- 
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 (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

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 578357] Re: MySql log file problem prevents Akonadi startup

2016-09-25 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=238217.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-05-19T19:37:50+00:00 Cubranic-w wrote:

Version:(using KDE 4.4.2)
OS:Linux
Installed from:Ubuntu Packages

I originally reported this bug in Ubuntu Launchpad:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357

I am opening it here as a wider issue: Akonadi is very fragile in the
face of mysql startup problems, and that has a knock-on effect of
preventing basic user applications (mail, PIM) from running.

The most visible symptom of the problem was that after starting up
KMail, I would get an error dialog stating that Akonadi is not running.
After closing the dialog, the app would close also.

I started investigating, and got voluminous, but not very helpful error
output when running 'akonadictl start' from the command line. (I'll
attach a copy.) Further poking and twiddling with apparmor and other
workarounds suggested in various bugs and forums was unsuccessful.
Eventually, I stumbled upon mysql.err in ~/.local/share/akonadi/db_data/
with the following contents:

100519 9:49:38 [Note] Plugin 'FEDERATED' is disabled.
 InnoDB: Error: log file ./ib_logfile1 is of different size 0 0 bytes
 InnoDB: than specified in the .cnf file 0 67108864 bytes!
 100519 9:49:38 [ERROR] Plugin 'InnoDB' init function returned error.
 100519 9:49:38 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
 100519 9:49:38 [ERROR] Unknown/unsupported table type: innodb
 100519 9:49:38 [ERROR] Aborting
100519 9:49:38 [Note] /usr/sbin/mysqld-akonadi: Shutdown complete

File 'ib_logfile1' was indeed of size zero. Deleting it and
'ib_logfile0', and then restarting 'akonadictl' seemed to fix the
problem and I now have a working mail reader.

I don't know how the log file got corrupted, but the system should be
more robust than that. I mean, having a zero-size or corrupted log file
does not need to be an unrecoverable error!

It's completely reasonable in such a situation to delete it and proceed
with startup. The database should still be in a consistent state, and
the worst that could happen is that the last few transactions are
missing. Or at the very least notify the user what the real problem is.
As it is, akonadi server's output is utterly unhelpful, and it took me
forever to find Akonadi's mysql.err, where the problem was actually
clearly identified.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/7


On 2010-05-19T19:40:53+00:00 Cubranic-w wrote:

Created attachment 43736
Output of 'akonadictl start' when MySql fails to start

This is the output of running 'akonadictl start' from the console before
I vixed the problem by deleting the corrupted logfiles. This output
actually repeats three times. (Why?)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/8


On 2010-09-14T22:52:52+00:00 reagle wrote:

I have the same problem too. Moving to akonadi has been a disaster for
me as a user. Beside this breakage, how does one even backup one's email
files even?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/13


On 2010-11-10T17:59:00+00:00 João Eiras wrote:

*** Bug 256527 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/15


On 2011-03-13T16:31:37+00:00 Ricardo Graça wrote:

*** This bug has been confirmed by popular vote. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/17


On 2016-09-24T20:38:55+00:00 Kdenis wrote:

This bug has only been reported for versions older than KDEPIM 4.14 (at
most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE
Applications 15.08 or later), it gets closed in about three months.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/24


** Changed in: akonadi
   Status: Unknown => Incomplete

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

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

Title:
  MySql log file problem prevents Akonadi startup

Status 

[Desktop-packages] [Bug 1622844] Re: [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the headphone jack, ever.

2016-09-25 Thread ScarySquirrel
// , Has anyone else run into this?

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

Title:
  [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the
  headphone jack, ever.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
// , Other sound works alright.

  This bug seems to affect my Dell XPS L521X Ubuntu laptop running
  Ubuntu Xenial 16.04:

  $ lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller (rev 04)
  01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller 
(rev ff)

  
  $ uname -a
  Linux nb-XPS-L521X 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 
18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  My headphone jack simply does not work with 16.04.

  It worked just fine with 14.04.

  I ran the following command to look at my audio packages:

  $ sudo apt list > apt_list_20160912.txt ; cat
  apt_list_20160912.txt | egrep 'audio|alsa|pulse'

  Results are at the following link:

  http://hastebin.com/kivayotucu.apache

  If you would like further details about this, or a gdb report, I'm at
  your service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   nb 3944 F...m pulseaudio
   /dev/snd/controlC0:  nb 3944 F pulseaudio
nb13118 F alsamixer
   /dev/snd/controlC1:  nb 3944 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:23:48 2016
  InstallationDate: Installed on 2016-09-11 (1 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_Jack: Black Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0880F2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/01/2013:svnDellInc.:pnXPSL521X:pvrA15:rvnDellInc.:rn0880F2:rvrA00:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: XPS L521X
  dmi.product.version: A15
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1582495] Re: cannot type password login

2016-09-25 Thread Launchpad Bug Tracker
[Expired for unity-greeter (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: unity-greeter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cannot type password login

Status in unity-greeter package in Ubuntu:
  Expired

Bug description:
  I cannot type my password on the login screen on Ubuntu 16.04. It
  shows `Log in >` where I should type it. I can login using `Ctrl + Alt
  + F2`, then `sudo service lightdm force-reload`, then just clicking on
  the `Log In >` box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 04:42:15 2016
  InstallationDate: Installed on 2016-04-08 (39 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LightdmConfig:
   [Seat:*]
   autologin-user=
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1574005] Re: HDMI connection not working on Ubuntu 16.04 and GeForce GTX 960M

2016-09-25 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HDMI connection not working on Ubuntu 16.04 and GeForce GTX 960M

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The bug is described in question #291879 . After upgrading to Ubuntu
  16.04 the HDMI monitor is no longer detected.

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

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


[Desktop-packages] [Bug 1607675] Re: Nautilus cann't access AirPort Time Capsule in Ubuntu 16.04

2016-09-25 Thread Chow Loong Jin
nautilus-share sets up your computer to host shares, not to access
shares. Reassigning to nautilus.

** Package changed: nautilus-share (Ubuntu) => nautilus (Ubuntu)

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

Title:
  Nautilus cann't access AirPort Time Capsule in Ubuntu 16.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When connecting to my Time Capsule, I'll get an error
  "kFPAuthContinue" from server.

  While I can mount server with `mount.cifs`:

  ```
  sudo mount.cifs \\10.0.1.1\${user_name} /mnt/ -o user=${user_name},sec=ntlm
  ```

  According to `mount.cifs`'s manual, **the default was sec=ntlm in
  mainline kernel version prior to v3.8, and has been changed to
  sec=ntlmssp in kernel v3.8+**.

  Maybe that's the reason why it works in Ubuntu 14.04 and fails in
  Ubuntu 16.04.

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

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


[Desktop-packages] [Bug 1575484] Re: "Set document metadata failed"

2016-09-25 Thread PHB
"If I recall correctly from a previous discussion about this sort of
thing, the problem is that when you su to root a lot of your environment
which is required for the correct running of Gnome GUI apps is not set
up appropriately. The consensus from the developers seemed to be that
running GUIs as root was generally a bad idea and should not be
encouraged."

Translation: We hate you all, you will learn vi, suck on it.

Not having a working editor is generally considered to be a problem in
an operating system. The problem has only been there for like 5 years.

Like Donald Trump, Linux succeeds only by setting expectations so low
they are easy to exceed.

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

Title:
  "Set document metadata failed"

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Whenever I edit a document via the Terminal, I get these error
  messages:

  ** (gedit:12864): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-spell-enabled not supported

  ** (gedit:12864): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-encoding not supported

  ** (gedit:12864): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-position not supported

  Info:
  OS: Ubuntu 16.04 (Xenial) x64
  App version: 3.18.3

  - Blossom

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

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


[Desktop-packages] [Bug 1506358] Re: unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

2016-09-25 Thread Daniel van Vugt
Still happening in Mir 0.24.0 using NBS. See: bug 1627311

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

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

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

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


[Desktop-packages] [Bug 1592717] Re: Can't select secret .pem key for TLS auth on wired and WiFi connection

2016-09-25 Thread Fedor
*** This bug is a duplicate of bug 1575614 ***
https://bugs.launchpad.net/bugs/1575614

As a workaround, you can drag and drop your private key directly from
Files (Nautilus)

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

Title:
  Can't select secret .pem key for TLS auth on wired and WiFi connection

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

Bug description:
  STR for wired conncetion:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where .pem key is located and try 
to select key file

  Actual result: only .p12 files are listed
  Expected result: .pem files listed as well

  STR for WiFi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file

  Actual result: only .p12 files are listed
  Expected result: .pem files listed as well

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

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


[Desktop-packages] [Bug 1627311] Re: Mir client crashes with SIGABRT in send_message() from release_buffer_stream

2016-09-25 Thread Daniel van Vugt
This appears to be a recurrence of bug 1506358, which we closed thinking
it was fixed by the introduction of NBS. Obviously not fixed, now the
same crash is happening in a slightly different way with NBS.

** Summary changed:

- Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
+ Mir client crashes with SIGABRT in send_message() from release_buffer_stream

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

** Summary changed:

- Mir client crashes with SIGABRT in send_message() from release_buffer_stream
+ Xmir crashes with SIGABRT in send_message() from release_buffer_stream (on a 
cursor)

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

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

** Tags added: cursor unity8-desktop

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

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

** Summary changed:

- Xmir crashes with SIGABRT in send_message() from release_buffer_stream (on a 
cursor)
+ Xmir crashes with SIGABRT in send_message() from release_buffer_stream() from 
FreeCursor()

** Summary changed:

- Xmir crashes with SIGABRT in send_message() from release_buffer_stream() from 
FreeCursor()
+ Xmir crashed with SIGABRT in send_message() from release_buffer_stream() from 
FreeCursor()

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

Title:
  Xmir crashed with SIGABRT in send_message() from
  release_buffer_stream() from FreeCursor()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  

[Desktop-packages] [Bug 1575614] Re: [SRU]Can't select secret key for TLS auth for 802.1X authentication

2016-09-25 Thread Fedor
As a workaround, you can drag and drop your private key directly from
Files (Nautilus)

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

Title:
  [SRU]Can't select secret key for TLS auth for 802.1X authentication

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

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

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


[Desktop-packages] [Bug 1627311] Re: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

2016-09-25 Thread Daniel van Vugt
** Information type changed from Private to Public

** Tags added: xmir

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

Title:
  Mir client crashes with SIGABRT in send_message() from
  release_buffer_stream

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1627576] [NEW] Properties fails to display Polaroid Cube video metadata

2016-09-25 Thread J. Matthew Catron
Public bug reported:

With all video files generated by the Polaroid Cube camera, Ubuntu
cannot load the videos in the Videos application or decipher the
metadata from the files. Running the files in VLC allows for metadata
reading.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 25 23:00:54 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+502'"
InstallationDate: Installed on 2016-09-12 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Properties fails to display Polaroid Cube video metadata

Status in nautilus package in Ubuntu:
  New

Bug description:
  With all video files generated by the Polaroid Cube camera, Ubuntu
  cannot load the videos in the Videos application or decipher the
  metadata from the files. Running the files in VLC allows for metadata
  reading.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 25 23:00:54 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+502'"
  InstallationDate: Installed on 2016-09-12 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


Re: [Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-25 Thread Luke Yelavich
affects ubuntu/pulseaudio
 assignee themuso


** Changed in: pulseaudio (Ubuntu)
 Assignee: Simon Fels (morphis) => Luke Yelavich (themuso)

-- 
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 (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

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 1627562] [NEW] PulseaudioSound[2537]: segfault at 0 ip 000000000143a244 sp 00007fafacff72e0 error 4 in spotify[400000+2134000]

2016-09-25 Thread Cristian Aravena Romero
Public bug reported:

[ 6081.211245] PulseaudioSound[2537]: segfault at 0 ip 0143a244
sp 7fafacff72e0 error 4 in spotify[40+2134000]

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-16.17-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-16-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   9271 F...m pulseaudio
 /dev/snd/controlC0:  caravena   9271 F pulseaudio
CurrentDesktop: GNOME
Date: Sun Sep 25 22:02:48 2016
InstallationDate: Installed on 2015-07-26 (427 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  PulseaudioSound[2537]: segfault at 0 ip 0143a244 sp
  7fafacff72e0 error 4 in spotify[40+2134000]

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [ 6081.211245] PulseaudioSound[2537]: segfault at 0 ip
  0143a244 sp 7fafacff72e0 error 4 in
  spotify[40+2134000]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-16.17-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-16-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   9271 F...m pulseaudio
   /dev/snd/controlC0:  caravena   9271 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 25 22:02:48 2016
  InstallationDate: Installed on 2015-07-26 (427 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


Re: [Desktop-packages] [Bug 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all

2016-09-25 Thread Luke Yelavich
So there is no 3.5mm connectinos at the rear?

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

Title:
  [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I am not getting any sound at all from my Dell Optiplex 7040 (running
  Ubuntu 16.04).

  The volume control icon is showing up next to the clock, and I am able
  to change the volume levels: but this has no effect. There is
  absolutely NO sound at all.

  In Settings -> Output, no devices are listed. Strangely enough, aplay
  -l results in:

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0

  which indicates that the sound card is getting detected. I tried

  sudo alsa force-reload

  following which I rebooted. That doesn't fix the problem. I opened
  alsamixer: it is detecting the sound card perfectly and nothing is
  muted. Still, there is no audio. I then tried the following:

  sudo apt-get remove --purge alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio
  sudo alsa force-reload

  And still there is no audio. I'd be really grateful if you could look
  into this. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  suvam  4522 F pulseaudio
suvam  5594 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Aug 24 15:59:21 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-02-12 (193 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  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:  suvam  4522 F pulseaudio
suvam  5594 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (13 days ago)
  dmi.bios.date: 12/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0HD5W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/04/2015:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-25 Thread Kathy Reid
@vooze: This worked PERFECTLY. The PLT_BBTGO2 is now paired and
connected successfully and I can adjust controls in the Sound settings
panel. I had to run

sudo pactl load-module module-bluetooth-discover

after I'd added the PPA, updated pulseaudio and rebooted.

A huge thank you for all your help.

Do you need specifics on the hardware I'm using?

Kind regards,
Kathy

-- 
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 (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

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 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group

2016-09-25 Thread Dongdong88
To xin (pursue) :

  you also can download procps-3.3.10 source code and compile it in
ubuntu16.04, then you could replace /bin/kill with the binary you
compile . in this way you dont need copy the libprocps.so.3 .

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

Title:
  /bin/kill in ubuntu16.04 has bug in killing process group

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

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

-- 
Mailing list: https://launchpad.net/~desktop-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-09-25 Thread Abel
I found another solution, seems to be better because, kernel version
4.4.0.21 has a bug within the suspend mode(sometimes works and sometimes
not) at least, happened to me in a Dell latitude e6420 and also this bug
of the backlight, so to fix it I updated the kernel version to 4.7.5 --
The only problem was that wireless stopped working, so to fix it I
connected through wired connection and I changed the driver,  after that
all works well!

check this: http://askubuntu.com/questions/574920/upgrading-to-3-18
-kernel-causes-wireless-not-to-work

**may be help:)
Sorry for my bad english.

-- 
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 1625595] Re: Libre Office Icons unreadability on YY with Intel Drivers

2016-09-25 Thread Christopher M. Penalver
Marco Parillo, regarding apport not working as expected, please file a
new report via https://launchpad.net/apport/+filebug , and feel free to
subscribe me to it.

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

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

Title:
  Libre Office Icons unreadability on YY with Intel Drivers

Status in libreoffice package in Ubuntu:
  New

Bug description:
  glxinfo | grep -i vendor
  server glx vendor string: SGI
  client glx vendor string: Mesa Project and SGI
  Vendor: Intel Open Source Technology Center (0x8086)
  OpenGL vendor string: Intel Open Source Technology Center

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

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


[Desktop-packages] [Bug 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

2016-09-25 Thread Christopher M. Penalver
jap1968, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  dmesg output :

  [ 8815.416923] [drm] stuck on render ring
  [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8815.419462] drm/i915: Resetting chip after gpu hang
  [ 8821.417592] [drm] stuck on render ring
  [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8821.420108] drm/i915: Resetting chip after gpu hang
  [ 8827.430254] [drm] stuck on render ring
  [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8827.432786] drm/i915: Resetting chip after gpu hang
  [ 8833.418862] [drm] stuck on render ring
  [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8833.421551] drm/i915: Resetting chip after gpu hang
  [ 8839.419503] [drm] stuck on render ring
  [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8839.422060] drm/i915: Resetting chip after gpu hang
  [ 8845.432118] [drm] stuck on render ring
  [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8845.434799] drm/i915: Resetting chip after gpu hang
  [ 8851.432751] [drm] stuck on render ring
  [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8851.435224] drm/i915: Resetting chip after gpu hang
  [ 8857.457381] [drm] stuck on render ring
  [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8857.459883] drm/i915: Resetting chip after gpu hang
  [ 8863.458003] [drm] stuck on render ring
  [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8863.460640] drm/i915: Resetting chip after gpu hang
  [ 8869.458654] [drm] stuck on render ring
  [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [ 8869.461116] drm/i915: Resetting chip after gpu hang
  [ 8875.435238] [drm] stuck on render ring
  [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8875.437697] drm/i915: Resetting chip after gpu hang
  [ 8881.447863] [drm] stuck on render ring
  [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8881.450331] drm/i915: Resetting chip after gpu hang
  [ 8887.436497] [drm] stuck on render ring
  [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8887.438961] drm/i915: Resetting chip after gpu hang
  [ 8893.437078] [drm] stuck on render ring
  [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8893.439562] drm/i915: Resetting chip after gpu hang

  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: Sun Apr 24 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2002]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1625595] Re: Libre Office Icons unreadability on YY with Intel Drivers

2016-09-25 Thread Marco Parillo
Same response from the Live ISO (Beta2 Release Candidate):

To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

kubuntu@kubuntu:~$ apport-collect 1625595
You need to run 'sudo apt-get install python-apport' for apport-collect to work.
kubuntu@kubuntu:~$ sudo apt install python-apport -y
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  python-apt python-cffi-backend python-cryptography python-enum34 
python-httplib2
  python-idna python-ipaddress python-keyring python-keyrings.alt 
python-launchpadlib
  python-lazr.restfulclient python-lazr.uri python-oauth python-pkg-resources
  python-problem-report python-pyasn1 python-secretstorage python-setuptools
  python-simplejson python-six python-wadllib python-zope.interface
Suggested packages:
  python-apt-dbg python-apt-doc python-cryptography-doc 
python-cryptography-vectors
  python-enum34-doc gnome-keyring gir1.2-gnomekeyring-1.0 python-fs python-gdata
  python-kde4 python-keyczar python-testresources doc-base 
python-secretstorage-doc
  python-setuptools-doc
The following NEW packages will be installed:
  python-apport python-apt python-cffi-backend python-cryptography python-enum34
  python-httplib2 python-idna python-ipaddress python-keyring 
python-keyrings.alt
  python-launchpadlib python-lazr.restfulclient python-lazr.uri python-oauth
  python-pkg-resources python-problem-report python-pyasn1 python-secretstorage
  python-setuptools python-simplejson python-six python-wadllib 
python-zope.interface
0 upgraded, 23 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,302 kB of archives.
After this operation, 7,095 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-apt amd64 
1.1.0~beta5 [142 kB]
Get:2 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-problem-report 
all 2.20.3-0ubuntu7 [9,638 B]
Get:3 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-httplib2 all 
0.9.1+dfsg-1 [34.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-keyring all 
9.1-1 [28.9 kB]
Get:5 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-pkg-resources 
all 25.2.0-1ubuntu1 [109 kB]
Get:6 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-lazr.uri all 
1.0.3-2build1 [13.6 kB]
Get:7 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-simplejson 
amd64 3.8.2-2 [60.1 kB]
Get:8 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-wadllib all 
1.3.2-3 [28.2 kB]
Get:9 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-zope.interface 
amd64 4.2.0-2 [80.6 kB]
Get:10 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-oauth all 
1.0.1-5 [12.9 kB]
Get:11 http://archive.ubuntu.com/ubuntu yakkety/main amd64 
python-lazr.restfulclient all 0.13.4-6 [50.8 kB]
Get:12 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-launchpadlib 
all 1.10.4-1 [45.7 kB]
Get:13 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-apport all 
2.20.3-0ubuntu7 [79.2 kB]
Get:14 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-cffi-backend 
amd64 1.7.0-1 [60.2 kB]
Get:15 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-enum34 all 
1.1.6-1 [34.6 kB]
Get:16 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-idna all 
2.1-1 [30.4 kB]
Get:17 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-ipaddress all 
1.0.16-1 [18.0 kB]
Get:18 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-pyasn1 all 
0.1.9-2 [45.4 kB]
Get:19 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-setuptools 
all 25.2.0-1ubuntu1 [176 kB]
Get:20 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-six all 
1.10.0-3 [10.9 kB]
Get:21 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-cryptography 
amd64 1.5-2 [205 kB]
Get:22 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-keyrings.alt 
all 1.1.1-1 [15.4 kB]
Get:23 http://archive.ubuntu.com/ubuntu yakkety/main amd64 python-secretstorage 
all 2.3.1-2 [11.8 kB]
Fetched 1,302 kB in 4s (314 kB/s) 
Selecting previously unselected package python-apt.
(Reading database ... 163246 files and directories currently installed.)
Preparing to unpack .../00-python-apt_1.1.0~beta5_amd64.deb ...
Unpacking python-apt (1.1.0~beta5) ...
Selecting previously unselected package python-problem-report.
Preparing to unpack .../01-python-problem-report_2.20.3-0ubuntu7_all.deb ...
Unpacking python-problem-report (2.20.3-0ubuntu7) ...
Selecting previously unselected package python-httplib2.
Preparing to unpack .../02-python-httplib2_0.9.1+dfsg-1_all.deb ...
Unpacking python-httplib2 (0.9.1+dfsg-1) ...
Selecting previously unselected package python-keyring.
Preparing to unpack .../03-python-keyring_9.1-1_all.deb ...
Unpacking python-keyring (9.1-1) ...
Selecting previously unselected package python-pkg-resources.
Preparing to unpack 

[Desktop-packages] [Bug 1627543] [NEW] Sync avatar is massive and breaks hamburguer menu

2016-09-25 Thread Jorge García
Public bug reported:

At Firefox 50, the sync avatar is massive and breaks the layout of the
menu (and makes it unusable).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 50.0~b1+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   jorge  2358 F...m pulseaudio
 /dev/snd/controlC0:  jorge  2358 F pulseaudio
BuildID: 20160921100542
Channel: beta
CurrentDesktop: Unity
Date: Sun Sep 25 22:32:07 2016
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins:
 VLC Web Plugin - /usr/lib/mozilla/plugins/libvlcplugin.so (browser-plugin-vlc)
 Java(TM) Plug-in 11.101.2 - 
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
 [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js
 [Profile]/extensions/foxma...@kei.com/defaults/preferences/prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
EcryptfsInUse: Yes
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-26 (60 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.1.1 dev wlp8s0  proto static  metric 600 
 169.254.0.0/16 dev wlp8s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.2  metric 
600
MostRecentCrashID: bp-faca4cd3-41c2-453b-a424-4a5dc2160918
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1Plugins:
 VLC Web Plugin - /usr/lib/mozilla/plugins/libvlcplugin.so (browser-plugin-vlc)
 Java(TM) Plug-in 11.101.2 - 
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Profile1PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
 [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js
 [Profile]/extensions/foxma...@kei.com/defaults/preferences/prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile0 (Default) - LastVersion=50.0/20160921100542 (In use)
 Profile1 - LastVersion=50.0a2/20160919004008 (Out of date)
RelatedPackageVersions: browser-plugin-vlc 2.0.6-4
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs: bp-faca4cd3-41c2-453b-a424-4a5dc2160918
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0CM76H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A14
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/22/2013:svnDellInc.:pnXPSL421X:pvrA14:rvnDellInc.:rn0CM76H:rvrA00:cvnDellInc.:ct8:cvrA14:
dmi.product.name: XPS L421X
dmi.product.version: A14
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug beta-channel third-party-packages xenial

** Attachment added: "firefoxBug.png"
   
https://bugs.launchpad.net/bugs/1627543/+attachment/4748508/+files/firefoxBug.png

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

Title:
  Sync avatar is massive and breaks hamburguer menu

Status in firefox package in Ubuntu:
  New

Bug description:
  At Firefox 50, the sync avatar is massive and breaks the layout of the
  menu (and makes it unusable).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 50.0~b1+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jorge  2358 F...m pulseaudio
   

[Desktop-packages] [Bug 1627541] [NEW] Sync ptouch-driver 1.4.2-2 (main) from Debian unstable (main)

2016-09-25 Thread Jeremy Bicha
Public bug reported:

Please sync ptouch-driver 1.4.2-2 (main) from Debian unstable (main)

Failed to build in recent archive rebuild:
http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html

Changelog entries since current yakkety version 1.4.2-1:

ptouch-driver (1.4.2-2) unstable; urgency=medium

  * Initialize git-dpm
  * Add patch to add 'include ' as CUPS 2.2 moved some definitions
to ppd.h, to fix FTBFS

 -- Didier Raboud   Sat, 24 Sep 2016 19:05:20 +0200

** Affects: ptouch-driver (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: ptouch-driver (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync ptouch-driver 1.4.2-2 (main) from Debian unstable (main)

Status in ptouch-driver package in Ubuntu:
  New

Bug description:
  Please sync ptouch-driver 1.4.2-2 (main) from Debian unstable (main)

  Failed to build in recent archive rebuild:
  http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html

  Changelog entries since current yakkety version 1.4.2-1:

  ptouch-driver (1.4.2-2) unstable; urgency=medium

* Initialize git-dpm
* Add patch to add 'include ' as CUPS 2.2 moved some definitions
  to ppd.h, to fix FTBFS

   -- Didier Raboud   Sat, 24 Sep 2016 19:05:20 +0200

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

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


[Desktop-packages] [Bug 1614050] Re: Window depth order messed up

2016-09-25 Thread Alberts Muktupāvels
Ok, finally I am able to reproduce this bug. It looks like steps are very 
simple:
- kill kupfer and nautilus if running
- start kupfer
- start nautilus

So in my case nautilus must be started after kupfer to trigger this bug.

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

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Using the gome-flashback session with metacity is totally messed up
  since I updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  
  I guess all those effects originate from a similiar reason. None of these 
problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

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

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


[Desktop-packages] [Bug 1614050] Re: Window depth order messed up

2016-09-25 Thread Alberts Muktupāvels
** Patch removed: "0001-compositor-log-debug-info.patch"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/+attachment/4741953/+files/0001-compositor-log-debug-info.patch

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

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Using the gome-flashback session with metacity is totally messed up
  since I updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  
  I guess all those effects originate from a similiar reason. None of these 
problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

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

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


[Desktop-packages] [Bug 1627365] Re: Screen frezes, only mouse pointer can move

2016-09-25 Thread Jose Barakat
Hi Christopher.

I'll remove
  http://ppa.launchpad.net/canonical-x/vulkan/ubuntu
  http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu
  http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu

and report back.

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

Title:
  Screen frezes, only mouse pointer can move

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This issue only occurs when I use certain gaming software like
  Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode.

  As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my
  symptoms are:

  - X stops responding to input (sometimes mouse cursor can still move, but 
clicking has no effect)
  - The screen displays but does not update. Sometimes there is screen 
corruption too, sometimes the screen goes black.
  - Often, X cannot be killed from the console or if it can, it won't restart 
properly; only a reboot clears the state 

  I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to
  frozen desktop/application with Ctrl+Alt+F7.

  I would like to reproduce this issue and collect the necessary data
  over ethernet, but I don't how to do it.

  - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony
  PlayStation Portable Emulator), Emulation Station (Frontend for
  Emulators) and a couple of minutes pass, so I can't go back to
  Windowed mode. I've tried with VLC fullscreen mode without issues.
  I'll make a more detailed report of apps later on comments.

  - I first noticed it aprox. after installing this repos:
http://ppa.launchpad.net/canonical-x/vulkan/ubuntu
http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu

  - I'm using Unity, so I can't be sure if this is happening in other
  DE's

  - Like I said before, this happens when switching from fullscreen mode
  to windowed mode, in some applications. I haven't had problems with
  streaming video (youtube player, jwplayer, vimeo player, etc...) in
  fullscreen mode.

  
  Thanks!

  
  Technical Info.
  
  Machine: Lenovo G400s (Laptop)

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


  ~$ apt-cache policy xorg
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status


  Phoronix Test Suite v6.4.0
  Interactive Benchmarking

  System Software / Hardware Information

  Hardware:
  Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, 
Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate 
ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, 
Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless

  Software:
  OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 
7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 
3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen 
Resolution: 1366x768

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.2-040702-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: Sat Sep 24 10:11:14 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2015-07-08 (444 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20244
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic 
root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash 
pciehp.pciehp_force=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BCN36WW(V2.02)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G400s
  dmi.modalias: 

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

2016-09-25 Thread miked
miked@free-yak:~$ lsb_release -rd
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10

miked@free-yak:~$ apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installed: 2:1.18.4-1ubuntu6
  Candidate: 2:1.18.4-1ubuntu6
  Version table:
 *** 2:1.18.4-1ubuntu6 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status
miked@free-yak:~$

-- 
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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Peter S
Thanks for the input about 16.10, Christian. I was considering an
upgrade to get rid of the problem, but now I will think twice before
doing so.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Desktop-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

2016-09-25 Thread Launchpad Bug Tracker
This bug was fixed in the package qtmir - 0.4.8+16.10.20160909-0ubuntu1

---
qtmir (0.4.8+16.10.20160909-0ubuntu1) yakkety; urgency=medium

  [ Daniel d'Andrada ]
  * Send relative pointer movement to Mir clients (LP: #1597205)
  * Implement cursor confinement (LP: #1590099)

  [ Gerry Boland ]
  * Deliver mouse event manually if no cursor exists to deliver it
  * [tests] refactor ScreensModel test to use mocks from mirtest-dev

 -- Michał Sawicz   Fri, 09 Sep 2016
14:40:56 +

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

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

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

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


[Desktop-packages] [Bug 1627534] [NEW] Keeps resetting homepage to start.ubuntu-mate.org

2016-09-25 Thread Egmont Koblinger
Public bug reported:

Since the Xenial -> Yakkety beta upgrade, firefox resets its homepage to
https://start.ubuntu-mate.org/ upon each start.

I use the default Unity 7 desktop, no Mate whatsoever. (I might have
started up Mate once or twice for a very short period, way before even
upgrading to Xenial.)

Happened both with firefox-49 package as shipped by Xenial, as well as
firefox-48 that's currently in Yakkety beta (I purged and then
reinstalled the package to get the one matching the distro, rather than
the latest).

No startup wrapper script or something like that should mess with my
preferred homepage, let alone set it to something that is about a
different desktop than the one I'm using.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 48.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.8.0-16-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  egmont 2339 F pulseaudio
BuildID: 20160728202151
Channel: Unavailable
CurrentDesktop: Unity
Date: Sun Sep 25 21:34:07 2016
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-05-30 (1579 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.11  metric 
600
MostRecentCrashID: bp-02582fc4-8633-4d4a-86cb-814af2140429
PrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntumate.js
 prefs.js
Profiles: Profile0 (Default) - LastVersion=48.0/20160728202151 (In use)
RelatedPackageVersions:
 google-talkplugin 5.41.0.0-1
 icedtea-8-plugin  1.6.2-3ubuntu1
 gnome-shell   3.20.3-1ubuntu2
 rhythmbox-mozilla 3.4.1-1ubuntu1
 browser-plugin-evince 3.22.0-0ubuntu1
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-02582fc4-8633-4d4a-86cb-814af2140429
UpgradeStatus: Upgraded to yakkety on 2016-09-23 (2 days ago)
dmi.bios.date: 12/14/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03QB
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 300E4Z/300E5Z/300E7Z
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr03QB:bd12/14/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4Z/300E5Z/300E7Z:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4Z/300E5Z/300E7Z:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300E4Z/300E5Z/300E7Z
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Keeps resetting homepage to start.ubuntu-mate.org

Status in firefox package in Ubuntu:
  New

Bug description:
  Since the Xenial -> Yakkety beta upgrade, firefox resets its homepage
  to https://start.ubuntu-mate.org/ upon each start.

  I use the default Unity 7 desktop, no Mate whatsoever. (I might have
  started up Mate once or twice for a very short period, way before even
  upgrading to Xenial.)

  Happened both with firefox-49 package as shipped by Xenial, as well as
  firefox-48 that's currently in Yakkety beta (I purged and then
  reinstalled the package to get the one matching the distro, rather
  than the latest).

  No startup wrapper script or something like that should mess with my
  preferred homepage, let alone set it to something that is about a
  different desktop than the one I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 48.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egmont 2339 F pulseaudio
  BuildID: 20160728202151
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Sep 25 21:34:07 2016
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-05-30 (1579 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.11  metric 
600
  MostRecentCrashID: 

[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Joakim Koed
Christian: Sounds like maybe it could be a problem with network-manager
+ lightdm, as gnome use GDM it makes sense there is no issue there.

In the meantime, you could always use this script:
http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-upgrade/761220#761220

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Christian Dysthe
I am having the same problem in Ubuntu 16.10 Beta 1. The main reason I
went for it so early was hoping these issues were resolved. They are
not. There's always problems when I come home after work and resume my
laptop. I'm either stuck on the now non existing work network or I do
not have any networks at all. I have tried "everything". I have two of
these Yoga Pro laptops, one with vanilla Ubuntu 16.10 beta and one with
UbuntuGNOME. On UbuntuGNOME no such problems.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Joakim Koed
Peter S: Just tried, same result.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Peter S
Have any of you tried using static IP adressess for your system?

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Desktop-packages] [Bug 1486450] Re: Error in loading other_hosts file

2016-09-25 Thread WinEunuchs2Unix
Same here:

Sep 25 12:06:13 dell com.ubuntu.OneConf[1161]:
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No
such file or directory:
'/home/rick/.cache/oneconf/60404938df669372cddaa05a56db23ae/other_hosts'

I checked and the file does exist. Note the system had been suspended
and resumed 3 minutes earlier. Ubuntu 16.04 LTD, Kernel 4.7.3. Only
other anomaly (ok the major one!) is syslog shows systemd initiates
suspend and upon resume kernel starts sleep process and wakes up right
away.

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

Title:
  Error in loading other_hosts file

Status in oneconf package in Ubuntu:
  Confirmed

Bug description:
  I am seeing this error in the syslog

  Aug 19 20:38:31 M1 com.ubuntu.OneConf[25838]:
  WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No
  such file or directory: '/home/michael-
  heuberger/.cache/oneconf/813e56ef1c4f171bda95b46b5448007c/other_hosts'

  Any ideas what it could be and how to fix?

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

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


[Desktop-packages] [Bug 1565516] Re: Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in fail

2016-09-25 Thread Pranav Sharma
I am willing to be a lab rat if a dev could work with me

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

Title:
  Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in
  fail

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  Fresh updated install of 16.04, installed nvidia-361 package. Upon reboot get 
to greeter can go no further.
  gpu-manager.log reports this, will attach full log - 
  Is prime available? yes
  Is prime egl available? no
  Single card detected
  Selecting mesa
  Error: no alternative found for mesa
  Warning: no EGL alternative found for mesa
  Error: no alternative found for unblacklist
  Removing xorg.conf. Path: /etc/X11/xorg.conf
  Moved /etc/X11/xorg.conf to /etc/X11/xorg.conf.04032016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.16
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  3 13:39:23 2016
  InstallationDate: Installed on 2016-04-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1565516] Re: Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in fail

2016-09-25 Thread Pranav Sharma
I have a similar issue on my Inspiron 7559

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

Title:
  Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in
  fail

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  Fresh updated install of 16.04, installed nvidia-361 package. Upon reboot get 
to greeter can go no further.
  gpu-manager.log reports this, will attach full log - 
  Is prime available? yes
  Is prime egl available? no
  Single card detected
  Selecting mesa
  Error: no alternative found for mesa
  Warning: no EGL alternative found for mesa
  Error: no alternative found for unblacklist
  Removing xorg.conf. Path: /etc/X11/xorg.conf
  Moved /etc/X11/xorg.conf to /etc/X11/xorg.conf.04032016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.16
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  3 13:39:23 2016
  InstallationDate: Installed on 2016-04-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-25 Thread Joakim Koed
Kathy: sounds like you have the exact same problem as the rest of us. I
would recommend just using the PPA, until Luke and Simon have an chance
to take a further look at it.. Hope it works for your hardware.

-- 
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 (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

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 1619922] Re: gnome-software crashed with SIGSEGV in look_at_pkg()

2016-09-25 Thread Christopher
The initial display of the bug is Photos, which aren't loading when
Gnome-Software is launched.

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

Title:
  gnome-software crashed with SIGSEGV in look_at_pkg()

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  It may be a variant of related bugs or just my 2005 laptop crashing as
  it frequently does when overloaded or too hot.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Sep  3 11:07:26 2016
  ExecutablePath: /usr/bin/gnome-software
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0xb2183249:pushl  0xc(%eax)
   PC (0xb2183249) ok
   source "0xc(%eax)" (0xbf4a3a4c) not located in a known VMA region (needed 
readable region)!
   destination "(%esp)" (0xb0c451f0) ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /usr/lib/gs-plugins-9/libgs_plugin_apt.so
   ?? () from /usr/lib/gs-plugins-9/libgs_plugin_apt.so
   gs_plugin_refine () from /usr/lib/gs-plugins-9/libgs_plugin_apt.so
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV in gs_plugin_refine()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video

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

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


[Desktop-packages] [Bug 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

2016-09-25 Thread David DIDIER
** Changed in: xorg (Ubuntu)
   Status: Invalid => 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/1623173

Title:
  [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 13 21:49:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (104 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 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 13 21:14:29 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Desktop-packages] [Bug 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

2016-09-25 Thread jap1968
Same problem here. I rarely had this problem previously with Ubuntu
14.04, but since updated to Ubuntu 16.04 I am suffering this issue very
often.

The problem mainly appears when trying to resume the laptop from
suspend. Mine has already installed xserver-xorg-video-intel. The laptop
has an intel HD Graphics 4400 video adapter, the one integrated within
the Core i7-4510U CPU

$ lspci
...
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)

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

Title:
  Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  dmesg output :

  [ 8815.416923] [drm] stuck on render ring
  [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8815.419462] drm/i915: Resetting chip after gpu hang
  [ 8821.417592] [drm] stuck on render ring
  [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8821.420108] drm/i915: Resetting chip after gpu hang
  [ 8827.430254] [drm] stuck on render ring
  [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8827.432786] drm/i915: Resetting chip after gpu hang
  [ 8833.418862] [drm] stuck on render ring
  [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8833.421551] drm/i915: Resetting chip after gpu hang
  [ 8839.419503] [drm] stuck on render ring
  [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8839.422060] drm/i915: Resetting chip after gpu hang
  [ 8845.432118] [drm] stuck on render ring
  [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8845.434799] drm/i915: Resetting chip after gpu hang
  [ 8851.432751] [drm] stuck on render ring
  [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8851.435224] drm/i915: Resetting chip after gpu hang
  [ 8857.457381] [drm] stuck on render ring
  [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8857.459883] drm/i915: Resetting chip after gpu hang
  [ 8863.458003] [drm] stuck on render ring
  [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8863.460640] drm/i915: Resetting chip after gpu hang
  [ 8869.458654] [drm] stuck on render ring
  [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [ 8869.461116] drm/i915: Resetting chip after gpu hang
  [ 8875.435238] [drm] stuck on render ring
  [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8875.437697] drm/i915: Resetting chip after gpu hang
  [ 8881.447863] [drm] stuck on render ring
  [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8881.450331] drm/i915: Resetting chip after gpu hang
  [ 8887.436497] [drm] stuck on render ring
  [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8887.438961] drm/i915: Resetting chip after gpu hang
  [ 8893.437078] [drm] stuck on render ring
  [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8893.439562] drm/i915: Resetting chip after gpu hang

  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: Sun Apr 24 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2002]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   

[Desktop-packages] [Bug 1627502] Re: Black screen, cursor shown, wifi connection popup shown

2016-09-25 Thread Timo Jyrinki
** Description changed:

  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.
+ 
+ After some while this disappears and the system goes to some sort of tty
+ switching loop where sometimes text cursor is shown and sometimes just
+ blank screen. If I want to recover text console control of machine I
+ need to quickly after booting switch to tty1 and stop lightdm.
+ 
+ This started happening last week after some upgrades and a reboot.
  
  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't
  start at all.
  
  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

** Attachment added: "lightdm logs"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627502/+attachment/4748365/+files/lightdm.tar

** Description changed:

  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.
  
  After some while this disappears and the system goes to some sort of tty
  switching loop where sometimes text cursor is shown and sometimes just
  blank screen. If I want to recover text console control of machine I
  need to quickly after booting switch to tty1 and stop lightdm.
  
  This started happening last week after some upgrades and a reboot.
  
  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't
- start at all.
+ start at all. So I'm using sddm + Plasma now but would like to be also
+ be able to run Unity 7 and Unity 8.
  
  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

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

Title:
  Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
  New

Bug description:
  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  After some while this disappears and the system goes to some sort of
  tty switching loop where sometimes text cursor is shown and sometimes
  just blank screen. If I want to recover text console control of
  machine I need to quickly after booting switch to tty1 and stop
  lightdm.

  This started happening last week after some upgrades and a reboot.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all. So I'm using sddm + Plasma now but would like to
  be also be able to run Unity 7 and Unity 8.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

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

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


[Desktop-packages] [Bug 1627504] [NEW] [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or crackling sound. Test tones work but sound immediatly returns to poor quality after comp

2016-09-25 Thread Nyall
Public bug reported:

Using digital audio output on Intel driver.
Sound from games is barely decipherable over the distortion/crackle. Playing 
test tones (left/right test and on bug report) work fine but the noise returns 
when the clips are completed.

Tried tsched=0, hda fix 1 and hda fix 2. no luck yet
When first added tsched command, it blurs the screen and no audio devices are 
available. remove, restart, re-add and screen and audio back but problem still 
present (maybe just spelt wrong first time?).

Help appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nytonial   1759 F pulseaudio
 /dev/snd/controlC0:  nytonial   1759 F pulseaudio
CurrentDesktop: Unity
Date: Sun Sep 25 15:28:53 2016
InstallationDate: Installed on 2016-09-07 (17 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black SPDIF Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or 
crackling sound
UpgradeStatus: Upgraded to xenial on 2016-09-08 (16 days ago)
dmi.bios.date: 02/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.60
dmi.board.asset.tag: Default string
dmi.board.name: Z170A XPOWER GAMING TITANIUM EDITION(MS-7968)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 3.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd02/23/2016:svnMSI:pnMS-7968:pvr3.0:rvnMSI:rnZ170AXPOWERGAMINGTITANIUMEDITION(MS-7968):rvr3.0:cvnMSI:ct3:cvr3.0:
dmi.product.name: MS-7968
dmi.product.version: 3.0
dmi.sys.vendor: MSI
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-25T14:21:58.691691

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


** Tags: amd64 apport-bug xenial

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

Title:
  [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts
  or crackling sound. Test tones work but sound immediatly returns to
  poor quality after completion.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Using digital audio output on Intel driver.
  Sound from games is barely decipherable over the distortion/crackle. Playing 
test tones (left/right test and on bug report) work fine but the noise returns 
when the clips are completed.

  Tried tsched=0, hda fix 1 and hda fix 2. no luck yet
  When first added tsched command, it blurs the screen and no audio devices are 
available. remove, restart, re-add and screen and audio back but problem still 
present (maybe just spelt wrong first time?).

  Help appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nytonial   1759 F pulseaudio
   /dev/snd/controlC0:  nytonial   1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 25 15:28:53 2016
  InstallationDate: Installed on 2016-09-07 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts 
or crackling sound
  UpgradeStatus: Upgraded to xenial on 2016-09-08 (16 days ago)
  dmi.bios.date: 02/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A XPOWER GAMING TITANIUM EDITION(MS-7968)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  

[Desktop-packages] [Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes

2016-09-25 Thread Jan Claeys
** Summary changed:

- nautilus trash doesn't include btrfs subvolumes
+ nautilus trash doesn't include btrfs and zfs subvolumes

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

Title:
  nautilus trash doesn't include btrfs and zfs subvolumes

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global
  trash.

  Comment by bug triage team: comment 4 has a spot-on analysis of where
  this issue is coming from, an inconsistency between trash handling in
  gvfs and glib/gio.  The problem has been around for quite a while.

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

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


[Desktop-packages] [Bug 1627502] [NEW] Black screen, cursor shown, wifi connection popup shown

2016-09-25 Thread Timo Jyrinki
Public bug reported:

My yakkety installation is now for some reason in shape that lightdm
only starts with a black screen, although mouse cursor is shown and
movable and "wifi networks available" popup is shown at the top right
corner.

I've tried reinstalling and everything I can think of, but I can't fix
it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't
start at all.

I couldn't also use ubuntu-bug since I can't use the browser interface
from command line (otherwise it works fine until that point) and it
segfaults under Plasma environment while collecting information.

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

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

Title:
  Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
  New

Bug description:
  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

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

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


[Desktop-packages] [Bug 883138] Re: Dim file extensions

2016-09-25 Thread Fred
@ginggs, modify the Open File and Save File dialogs in Wine to dim the
file extension. See screenshot.

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

Title:
  Dim file extensions

Status in GTK+:
  Confirmed
Status in Nautilus:
  Confirmed
Status in Wine:
  New
Status in enlightenment package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in lesstif2 package in Ubuntu:
  New
Status in mono package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged
Status in qt4-x11 package in Ubuntu:
  Opinion
Status in tcltk-defaults package in Ubuntu:
  New
Status in wine package in Ubuntu:
  Incomplete

Bug description:
  Many web browsers have now began dimming less relevant parts of the URL, such 
as the protocol, subdomain, path, and query string.
  I propose we have an option/setting/feature that does the same Nautilus and 
Gtk file dialogs. Dim the the file extension.

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

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


[Desktop-packages] [Bug 1627496] [NEW] AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.

2016-09-25 Thread Valentin Quequet
Public bug reported:

Hello Guys,

I'm currently running an up-to-date Xenial system on amd64 (PC)
platform.

Whenever I launch the OS with stock kernel (4.4.X) all seems good.

Whenever I launch the OS with let's say a mainline-PPA kernel whose
version is above 3.6.0 inclusive (3.5.X are functional), or stock
yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card,
whose description is appended in a few text files I joined to this
message.

In hope this helps,

Sincelely,
Vécu


P.S. : I very suspect this is a mainstream bug ; for any complimentary info. 
please don't hesitate to post and ask for more.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.8.0-16-generic x86_64
.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: Sun Sep 25 15:23:08 2016
DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41]
InstallationDate: Installed on 2015-05-01 (512 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: TOSHIBA SATELLITE L875-10G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic 
root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago)
dmi.bios.date: 3/25/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.50
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE L875-10G
dmi.product.version: PSKBLE-003006FR
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs 1.0
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Sep 25 15:10:31 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

** Attachment added: "Logs_Attachment.tar.gz"
   
https://bugs.launchpad.net/bugs/1627496/+attachment/4748335/+files/Logs_Attachment.tar.gz

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

Title:
  AMD Radeon hardware features or firmware looked over by Linux 3.6.0+
  kernel.

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello Guys,

  I'm currently running an up-to-date Xenial system on amd64 (PC)
  platform.

  Whenever I launch the OS with stock kernel (4.4.X) all seems good.

  Whenever I launch the OS with let's say a mainline-PPA kernel whose
  version is above 3.6.0 inclusive (3.5.X are functional), or stock
  yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics
  card, whose description is appended in a few text files I joined to
  this message.

  In hope this helps,

  Sincelely,
  Vécu

  
  P.S. : I very suspect this is a mainstream bug ; for any complimentary info. 
please don't hesitate to post and ask for more.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  

[Desktop-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04

2016-09-25 Thread javier algilaga
Same issue in lg p1 express dual, using Ubuntu 16.04. This bug is repeated 
previously with Ubuntu 8.04
Luke Yelavich, I tried installing this package 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+files/oem-audio-hda-daily-dkms_0.201609250548~ubuntu16.04.1_all.deb
but doesn't work.
It works correctly changing files in /etc/modprobe.d 
It's the same solution that it worked in Ubuntu 8,04
Thaks

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

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

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


[Desktop-packages] [Bug 1614050] Re: Window depth order messed up

2016-09-25 Thread Cui Wei
I recommend Alberts to use nemo 3.18 on ubuntu 16.04 and keep using for
several days because I think nemo background is more possible to cover
all windows than nautilus background under the management of metacity.

Nemo 3.18 is only integrated with ubuntu 14.04. If it's hard to find a
nemo repo for gnome desktop and compiled with ubuntu 16.04 libraries,
here is one:

http://ppa.launchpad.net/ghostplant/flashback/ubuntu/pool/main/n/nemo/

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

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Using the gome-flashback session with metacity is totally messed up
  since I updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  
  I guess all those effects originate from a similiar reason. None of these 
problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

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

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


[Desktop-packages] [Bug 1614050] Re: Window depth order messed up

2016-09-25 Thread Cui Wei
I have to say that I have given up using metacity for nearly two months
because I encountered this issue all the time since using it and cannot
find a way to reproduce it intentionally. Instead, I am using
macro:yakkety which is also based on GTK3 and it works well and
stablely.

I can confirm that metacity:trusty doesn't has this issue but
metacity:xenial has this issue.

And I can also confirm that metacity:xenial has this issue on virtualbox
as well.

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

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Using the gome-flashback session with metacity is totally messed up
  since I updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  
  I guess all those effects originate from a similiar reason. None of these 
problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

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

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


[Desktop-packages] [Bug 1622955] Re: VLC automatic video output malfunctions on Intel HD Graphics 520 (Skylake)

2016-09-25 Thread Alexey
I have just encountered the same problem with Skype video, and there i
do not see a way to fix it through preferences.

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

Title:
  VLC automatic video output malfunctions on Intel HD Graphics 520
  (Skylake)

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This problem is likely similar or same as #1537053.

  When selecting "Automatic" video output in VLC player, the playback
  malfunctions in several ways.

  1. The video floats on top, covering drop-down menus and other windows
  in front. I tried to take a screenshot, but the video does not appear
  on the screenshot.

  2. The aspect ratio is wrong: the image is squeezed from the sides.
  Trying to change the aspect ratio cuts a different rectangle from the
  image without changing the aspect ratio.  (Note: I have a Full HD
  screen 1920x1080.)

  3. The image cannot be stretched beyond its maximal resolution (as
  understood by VLC after miscalculating the aspect ratio).

  4. When resizing the window, a blue background appears and blinks.
  Sometimes it stays, especially in fullscreen mode.

  These problems are fixed by selecting GLX video output instead of
  Automatic.

  I do not know if this might be relevant, but i suspect that for some
  reason i do not have accelerated graphics in my desktop environment:
  dragging windows around clearly is not accelerated enough.

  WORKAROUND: Uncheck Accelerated video output (Overlay)" in Preference
  > Video > Display.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Sep 13 11:04:05 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c1d]
  InstallationDate: Installed on 2016-08-24 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: ASUSTeK COMPUTER INC. BU403UA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=4844f5ce-60b0-4b8b-a266-74c1faecf470 ro acpi_osi= 
acpi_backlight=native
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: BU403UA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: BU403UA
  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:bvnASUSTeKCOMPUTERINC.:bvrBU403UA.303:bd06/27/2016:svnASUSTeKCOMPUTERINC.:pnBU403UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnBU403UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: BU403UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  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/xserver-xorg-video-intel/+bug/1622955/+subscriptions

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


[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2016-09-25 Thread Vincas Dargis
** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1612367/+attachment/4748324/+files/unity8.log

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

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

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


[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2016-09-25 Thread Vincas Dargis
I've noticed same issue on BQ E5 on OTA-12 and OTA-13. Sometimes
incomming call gets silent after a split second (I can hear a blip of
sound).

Attaching syslog and unity8.log of that exact minute it happened. There
are no lines in media-hub log.


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1612367/+attachment/4748323/+files/syslog

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

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

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


[Desktop-packages] [Bug 1614050] Re: Window depth order messed up

2016-09-25 Thread Alberts Muktupāvels
Can someone please apply patch, reproduce bug and post log file? Or
should I create PPA for this?

I can not reproduce this bug... I hope that attached patch will help
understand what is going on, if not - will try to create other patch
until I will find what is causing this problem.

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

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Using the gome-flashback session with metacity is totally messed up
  since I updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  
  I guess all those effects originate from a similiar reason. None of these 
problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

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

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


[Desktop-packages] [Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

2016-09-25 Thread André Brait Carneiro Fabotti
Hello Henryque,

The scenario you describe (manually installing the NVIDIA drivers from
their website) is not within the scope of this request/bug, as far as I
know and having to install the 370 series is unrelated to this
request/bug.

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

Title:
  SRU request: Include the 367 driver in Ubuntu 16.04

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  The nvidia packages in Ubuntu 16.04 do not support recent NVIDIA GPUs.

  The new driver also requires changes in ubuntu-drivers-common, as gpu-
  manager needs to be able to unload the nvidia-drm module in order to
  power down the dGPU in hybrid systems.

  
  [Test Case]
  1) Enable the xenial-proposed repository, and install the nvidia-367 package

  2) Restart and see if the system boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the packages are already in Yakkety.

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

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


[Desktop-packages] [Bug 1581713] Re: Ubuntu Software asks for an Ubuntu Single Sign-On account to install/remove a snap

2016-09-25 Thread Bruce Pieterse
Unfortunately trying to login with Ubuntu One credentials with sudo snap
login em...@address.com returns error: cannot authenticate to snap
store: Provided email/password is not correct. (see "snap login --help")

I know these credentials are correct and also reflects the same
authentication failure currently present in gnome-software when trying
to install a snap as well.

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-gnome
   Importance: Undecided => High

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

Title:
  Ubuntu Software asks for an Ubuntu Single Sign-On account to
  install/remove a snap

Status in Ubuntu GNOME:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  If I try to uninstall a snap using Ubuntu Software, it asks for an Ubuntu 
Single Sign-On account. It seems strange since if I use a terminal and do:
  $ sudo snap remove john-the-ripper

  Everything works as expected.

  BTW: Ubuntu Software takes ages to find out the size of the snap
  package.

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

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


[Desktop-packages] [Bug 1581713] Re: Ubuntu Software asks for an Ubuntu Single Sign-On account to install/remove a snap

2016-09-25 Thread Bruce Pieterse
** Summary changed:

- Ubuntu Software asks for an Ubuntu Single Sign-On account to remove a snap
+ Ubuntu Software asks for an Ubuntu Single Sign-On account to install/remove a 
snap

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

Title:
  Ubuntu Software asks for an Ubuntu Single Sign-On account to
  install/remove a snap

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  If I try to uninstall a snap using Ubuntu Software, it asks for an Ubuntu 
Single Sign-On account. It seems strange since if I use a terminal and do:
  $ sudo snap remove john-the-ripper

  Everything works as expected.

  BTW: Ubuntu Software takes ages to find out the size of the snap
  package.

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

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


[Desktop-packages] [Bug 1625877] Re: VLC screen always on top

2016-09-25 Thread Leo Lee
I test this on Yakkety Yak in VirtualBox, works normally.
Maybe it's resolved.

Last version of Ubuntu I used is 14.04.
I remembered vlc works normally, but not the same computer.

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

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC

  the interface disappeared while minimum VLC (video playing)
  video screen remains only

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  Reference:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-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: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 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 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1191
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Desktop-packages] [Bug 899878] Re: Software center have hardcoded colors and shows white font on white bg

2016-09-25 Thread Bruce Pieterse
** Description changed:

+ [Impact]
+ 
+  * A user is unable to view the text within the software center
+ application which makes the application almost unusable.
+ 
+  * Ubuntu GNOME users that are currently using a dark theme with an LTS
+ release requested that the fix be backported to trusty from wily.
+ 
+  * This fix applies a custom style sheet for the dark variant of Ubuntu
+ GNOME Adwaita theme.
+ 
+ [Test Case]
+ 
+  * In Ubuntu GNOME open Gnome Tweak Tool
+  * Enable the Global Dark Theme option under Appearances
+  * Launch Software Center
+  * You will find that text is translucent which is hard to read on the home 
page.
+  * Click on any package. The package text is the same color as the background.
+  * Apply the fix
+  * Open software center and all text is now legible.
+ 
+ [Regression Potential]
+ 
+  * None. This fix was applied in Wily.
+  * Fix for trusty was tested with both dark and light themes for both Ubuntu 
Gnome and Ubuntu Unity. 
+ 
+ 
  When using dark theme
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: software-center 5.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sun Dec  4 15:28:41 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: software-center
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (48 days ago)

** Tags added: patch

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

Title:
  Software center have hardcoded colors and shows white font on white bg

Status in Ubuntu GNOME:
  Fix Released
Status in software-center package in Ubuntu:
  Fix Released
Status in software-center source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * A user is unable to view the text within the software center
  application which makes the application almost unusable.

   * Ubuntu GNOME users that are currently using a dark theme with an
  LTS release requested that the fix be backported to trusty from wily.

   * This fix applies a custom style sheet for the dark variant of
  Ubuntu GNOME Adwaita theme.

  [Test Case]

   * In Ubuntu GNOME open Gnome Tweak Tool
   * Enable the Global Dark Theme option under Appearances
   * Launch Software Center
   * You will find that text is translucent which is hard to read on the home 
page.
   * Click on any package. The package text is the same color as the background.
   * Apply the fix
   * Open software center and all text is now legible.

  [Regression Potential]

   * None. This fix was applied in Wily.
   * Fix for trusty was tested with both dark and light themes for both Ubuntu 
Gnome and Ubuntu Unity. 
  

  When using dark theme

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: software-center 5.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sun Dec  4 15:28:41 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: software-center
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (48 days ago)

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

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


[Desktop-packages] [Bug 1627365] Re: Screen frezes, only mouse pointer can move

2016-09-25 Thread Christopher M. Penalver
Jose Barakat, thank you for reporting this and helping make Ubuntu
better.

To clarify, if you remove all the unsupported PPAs is this still
reproducible?

** Tags added: bios-outdated-2.04

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

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

Title:
  Screen frezes, only mouse pointer can move

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This issue only occurs when I use certain gaming software like
  Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode.

  As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my
  symptoms are:

  - X stops responding to input (sometimes mouse cursor can still move, but 
clicking has no effect)
  - The screen displays but does not update. Sometimes there is screen 
corruption too, sometimes the screen goes black.
  - Often, X cannot be killed from the console or if it can, it won't restart 
properly; only a reboot clears the state 

  I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to
  frozen desktop/application with Ctrl+Alt+F7.

  I would like to reproduce this issue and collect the necessary data
  over ethernet, but I don't how to do it.

  - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony
  PlayStation Portable Emulator), Emulation Station (Frontend for
  Emulators) and a couple of minutes pass, so I can't go back to
  Windowed mode. I've tried with VLC fullscreen mode without issues.
  I'll make a more detailed report of apps later on comments.

  - I first noticed it aprox. after installing this repos:
http://ppa.launchpad.net/canonical-x/vulkan/ubuntu
http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu

  - I'm using Unity, so I can't be sure if this is happening in other
  DE's

  - Like I said before, this happens when switching from fullscreen mode
  to windowed mode, in some applications. I haven't had problems with
  streaming video (youtube player, jwplayer, vimeo player, etc...) in
  fullscreen mode.

  
  Thanks!

  
  Technical Info.
  
  Machine: Lenovo G400s (Laptop)

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


  ~$ apt-cache policy xorg
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status


  Phoronix Test Suite v6.4.0
  Interactive Benchmarking

  System Software / Hardware Information

  Hardware:
  Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, 
Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate 
ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, 
Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless

  Software:
  OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 
7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 
3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen 
Resolution: 1366x768

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.2-040702-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: Sat Sep 24 10:11:14 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2015-07-08 (444 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20244
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic 
root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash 
pciehp.pciehp_force=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BCN36WW(V2.02)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G400s
  dmi.modalias: 

[Desktop-packages] [Bug 1615204] Re: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1

2016-09-25 Thread Christopher M. Penalver
Aaron Marcuse-Kubitza, the justification you provided doesn't indicate
one way or the other the root cause is xorg.

Could you please provide a full technical discussion (not a couple
sentence opinion)?

** Package changed: xorg (Ubuntu) => linux (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/1615204

Title:
  select-by-word/double-click drag-select only works sporadically on
  Toshiba Chromebook 1

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (also on Linux kernel bug tracker at
  https://bugzilla.kernel.org/show_bug.cgi?id=153871)

  Detailed bug description:
  In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text 
by word, by double-clicking/triple-touchpad-tapping and then dragging the 
mouse, this only works occasionally. However, selecting text by line with a 
triple-click/4-tap drag works fine. This bug does not appear when Ubuntu 
16.04.1 is run in a VM in VirtualBox.
  [1] and now Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 
4.4.0-34-generic (the same as for 16.04)

  Steps to reproduce:
  1) On a 1st-generation Toshiba Chromebook (and possibly other machines, too), 
run Ubuntu 16.04.1 from a boot disk 
(http://releases.ubuntu.com/16.04/ubuntu-16.04.1-desktop-i386.iso).
  2) Open a terminal window and type several words.
  3) Double-click/triple-touchpad-tap and then drag the mouse to attempt to 
select multiple words.
  4) Compare this to the same boot disk run in VirtualBox, where it works 
properly.
  5) Compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux 
kernel 4.4.0-34-generic (see comment #23 & 
http://wiki.ubuntu.com/1404_HWE_EOL), where it doesn't work.
  6) Compare this to the hardware-specific update but with Linux kernel 
4.4.0-34-generic removed (downgraded to 3.16.0-77-generic), where it also 
doesn't work (and is therefore not a kernel problem, but rather relates to 
other files in the hardware-specific update).

  Expected results:
  Multiple words are selected.

  Actual result:
  Only the first word is selected.

  Reproducibility:
  Double-click drag-select will work occasionally, but most of the time it 
doesn't.

  Workaround:
  In applications other than Terminal, can use Ctrl+Shift+Right-Arrow to select 
by word (significantly slower for large text blocks). No known workaround for 
Terminal.

  Impact:
  Recommend not upgrading to 16.04 if you have a computer where double-click 
drag-select doesn't work in it.

  Description of the environment:
   Operation system: Ubuntu 16.04.1
   Versions of components: Linux kernel 4.4.0-34-generic (also on Ubuntu 
14.04.5)
   Reference architecture: 1st-generation Toshiba Chromebook (model name 
"Toshiba Leon")
   Network model: N/A
   Related projects installed: none (boot disk)

  Additional information:
  N/A
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   1882 F pulseaudio
   /dev/snd/controlC1:  administrator   1882 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-04-05 (506 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Toshiba Leon
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=127e42a1-2015-0521--28e347c5f54d ro tpm_tis.force=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.127.22
  Tags:  trusty
  Uname: Linux 4.4.0-34-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: Toshiba
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr:
  dmi.product.name: Leon
  dmi.product.version: 1.0
  dmi.sys.vendor: Toshiba

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

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


[Desktop-packages] [Bug 1578698] Re: Crash on waking from suspend after upgrading to 16.04

2016-09-25 Thread Christopher M. Penalver
Csaba Miklos, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Crash on waking from suspend after upgrading to 16.04

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Since upgrading to Ubuntu 16.04 and compiz
  1:0.9.12.2+16.04.20160415-0ubuntu1 I have started to see frequent,
  apparently random crashes when resuming from suspend.  I don't have
  any definitive proof that it is compiz vs e.g. the Unity plugin, as I
  don't even get one of the usual crash dialogues when this happens.  I
  just see the screen freeze up, aside from the cursor, and then after
  10-15 seconds it seems to reload compiz and I am able to actually
  enter my password to login.  I'm sorry this report isn't of more help,
  I will continue investigating to see if I can narrow it down at all.

  Edit: I'm using the Intel graphics driver, and spotted the following
  in dmesg:

  [drm] stuck on render ring
  [drm] GPU HANG: ecode 7:0:0x85d8, in compiz [16077], reason: Ring hung, 
action: reset
  drm/i915: Resetting chip after gpu hang
  [drm] stuck on render ring
  [drm] GPU HANG: ecode 7:0:0x85d8, in compiz [16077], reason: Ring hung, 
action: reset
  [ cut here ]
  WARNING: CPU: 6 PID: 804 at 
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, 
false, NULL, _flip->i915->rps.mmioflips))
  Modules linked in:
   vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) hidp cmac drbg 
ansi_cprng ctr ccm pci_stub rfcomm bnep zram lz4_compress arc4 intel_rapl 
x86_pkg_temp_thermal uvcvideo intel_powerclamp iwlmvm snd_hda_codec_conexant 
snd_hda_codec_hdmi videobuf2_vmalloc crct10dif_pclmul snd_hda_codec_generic 
videobuf2_memops crc32_pclmul videobuf2_v4l2 mac80211 snd_hda_intel 
videobuf2_core aesni_intel snd_hda_codec v4l2_common snd_hda_core btusb 
videodev aes_x86_64 snd_hwdep btrtl lrw btbcm media gf128mul snd_pcm btintel 
glue_helper bluetooth ablk_helper cryptd snd_seq_midi snd_seq_midi_event 
iwlwifi snd_rawmidi joydev snd_seq input_leds rtsx_pci_ms serio_raw cfg80211 
memstick snd_seq_device snd_timer lpc_ich snd soundcore ie31200_edac mei_me 
toshiba_acpi mei toshiba_bluetooth toshiba_haps sparse_keymap
   edac_core shpchp mac_hid soc_button_array kvm_intel kvm irqbypass nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc coretemp autofs4 hid_generic usbhid hid 
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt psmouse fb_sys_fops ahci drm alx libahci rtsx_pci mdio wmi video fjes 
[last unloaded: vboxdrv]
  CPU: 6 PID: 804 Comm: kworker/6:0 Tainted: GW  OE   4.4.0-21-generic 
#37-Ubuntu
  Hardware name: TOSHIBA Satellite P75-A/Type2 - Board Product Name1, BIOS 1.50 
04/18/2014
  Workqueue: events intel_mmio_flip_work_func [i915]
   0286 c262292d 88007aa2bd20 813e93c3
   88007aa2bd68 c0270a50 88007aa2bd58 81080f62
   88027609f780 88045f396500 88045f39ae00 0180
  Call Trace:
   [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? __switch_to+0x420/0x5a0
   [] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
   [] process_one_work+0x162/0x480
   [] worker_thread+0x4b/0x4c0
   [] ? process_one_work+0x480/0x480
   [] ? process_one_work+0x480/0x480
   [] kthread+0xd8/0xf0
   [] ? kthread_create_on_node+0x1e0/0x1e0
   [] ret_from_fork+0x3f/0x70
   [] ? kthread_create_on_node+0x1e0/0x1e0
  ---[ end trace d6a9268873c90b8e ]---
  [ cut here ]
  WARNING: CPU: 6 PID: 23478 at 
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, 
false, NULL, _flip->i915->rps.mmioflips))
  Modules linked in:
   vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) hidp cmac drbg 
ansi_cprng ctr ccm pci_stub rfcomm bnep zram lz4_compress arc4 intel_rapl 
x86_pkg_temp_thermal uvcvideo intel_powerclamp iwlmvm snd_hda_codec_conexant 
snd_hda_codec_hdmi videobuf2_vmalloc crct10dif_pclmul snd_hda_codec_generic 
videobuf2_memops crc32_pclmul videobuf2_v4l2 mac80211 snd_hda_intel 
videobuf2_core aesni_intel snd_hda_codec v4l2_common snd_hda_core btusb 
videodev aes_x86_64 snd_hwdep btrtl lrw btbcm media gf128mul snd_pcm btintel 
glue_helper bluetooth ablk_helper cryptd snd_seq_midi snd_seq_midi_event 
iwlwifi snd_rawmidi joydev snd_seq input_leds rtsx_pci_ms 

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

2016-09-25 Thread Christopher M. Penalver
** Changed in: xorg (Ubuntu)
   Status: Confirmed => 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/1434351

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

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

  The lines underlining menu hotkeys do NOT disappear.

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

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

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

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


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

2016-09-25 Thread Christopher M. Penalver
Samuel Ballé, thank you for reporting this and helping make Ubuntu
better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** This bug is no longer a duplicate of bug 1434351
   X fonts and widgets disappear after suspend/resume cycle

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

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

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  not all the time, but at some suspend/resume operations fonts disapear from 
gnome terminal, nm-applet and soffice which then show spaces and underscore 
placeholders instead of characters.
  google chrome, thunderbird, firefox, virtualbox are not affected.
  As it happens not at each suspend resume I find it hard to diagnose what is 
going wrong.
  next time I will launch more apps to see wich ones are affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks
   [FAILED] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any 
system changes.
Starting Light Display Manager...
  CompizPlugins:
   (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Wed Sep 21 23:41:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  InstallationDate: Installed on 2016-07-27 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook W65_67SZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05SB.02
  dmi.board.asset.tag: Tag 12345
  

[Desktop-packages] [Bug 1625877] Re: VLC screen always on top

2016-09-25 Thread Christopher M. Penalver
Leo Lee, thank you for reporting this and helping make Ubuntu better.

To clarify, did this issue not occur in a Ubuntu release prior to 16.04?

To see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

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

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

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC

  the interface disappeared while minimum VLC (video playing)
  video screen remains only

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  Reference:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-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: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 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 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1191
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Desktop-packages] [Bug 1625595] Re: Libre Office Icons unreadability on YY with Intel Drivers

2016-09-25 Thread Christopher M. Penalver
Marco Parillo, please boot into http://cdimage.ubuntu.com/daily-
live/current/ and then run the command.

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

Title:
  Libre Office Icons unreadability on YY with Intel Drivers

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  glxinfo | grep -i vendor
  server glx vendor string: SGI
  client glx vendor string: Mesa Project and SGI
  Vendor: Intel Open Source Technology Center (0x8086)
  OpenGL vendor string: Intel Open Source Technology Center

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

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


[Desktop-packages] [Bug 1614050] Re: Window depth order messed up

2016-09-25 Thread crc32
This bug effects me too. I'm on an Intel on board card. this is a show
stopper for me too. Guess I'll have to use compiz now. :(

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)

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

Title:
  Window depth order messed up

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Using the gome-flashback session with metacity is totally messed up
  since I updated from Ubuntu 14.04.3 to 16.04.1.

  All the effects mentioned here do not appear when using compiz, so I
  guess Metacity is broken.

  -Windows that should open in front (like Kupfer) appear behind the
  windows already open.

  -Before nemo is run, the Ubuntu default desktop background image
  appear, it can't be changed by settings. I just guess this is due
  wrong ordering of the true background and some window used by Gnome
  for showing the selected background.

  -If nemo is run to take over the desktop, the destkop icons appear in
  front of all windows.

  
  I guess all those effects originate from a similiar reason. None of these 
problems where appearant at Ubuntu 14.04.

  This is a total show stopper for using metacity on 16.04 as everyday
  applications like nemo and Kupfer can't be used.

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

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