date:20160915

tjaalton: Yes please revert the Mesa commit if it solves the problem.

Either way, we don't yet know what/where to fix in Mir/Unity8/Qt*

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

Title:
  [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any
  more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Desktop-packages] [Bug 1579501] Re: graphics distorted, lightdm restarting

2016-09-15 Thread Christian Brandt

I think I can now reliably produce this bug:

Install Ubuntu on a System with official NVidia-Drivers whith the
graphics older than G80 and system becomes unstable as written above.

Tested on:

1. Core2 with Geforce 7600
2. Pentium M with Geforce 6400M
3. Pentium 4 with Geforce 6800 AGP
4. Athlon X2 with Geforce 6600

A short test on the Core2 and Pentium4 with a Geforce 640 showed the
problem is related to the old graphic board.

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

Title:
  graphics distorted, lightdm restarting

Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Confirmed

Bug description:
  The system was running ubuntu 12.04 without any problems, quite fast
  and definitly worth keeping, I was able to play 3D games at decent
  quality while using official nvidia drivers. Overall a pretty stable
  system based on an Intel 965 Chipset and a Geforce 7600.

  I did a clean install of 16.04 and added nvidia-graphics-
  drivers-304-updates. At first the system was horribly unstable,
  displayed garbage at the slighted GPU load, even starting frozen
  bubble in full screen made lightdm restart.

  After using "dconf write
  /org/compiz/profiles/unity/plugins/opengl/enable-x11-sync false" the
  system became stable but display is still often distorted, missing
  picture elements, doesn't draw all elements in firefox, scrolling of
  firefox and terminal output is missing parts. This happens around once
  every minute so it is still workable but unprofessional. Happens a lot
  more often in Firefox than any other application.

  Also I have the feeling lots of stuff is working a lot slower than it
  did in 12.04, e.g. starting frozen bubble in full screen takes a lot
  longer than earlier.

  I think this error is somewhere between nvidia drivers, compiz and
  firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-304-updates 304.131-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  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 May  8 12:36:09 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304-updates, 304.131, 4.4.0-22-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GS] [10de:0392] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G73 [GeForce 7600 GS] [1acc:8132]
  InstallationDate: Installed on 2016-05-05 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=79fb27e9-d5d1-48c8-9210-7045256917c0 ro quiet splash nomodeset
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: 965P-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd05/28/2007:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 965P-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May  8 12:27:11 2016

[Desktop-packages] [Bug 1554166] Re: Downloads changelogs for non desktop components

2016-09-15 Thread Robert Ancell

Fixed by solution in bug 1574666 which now downloads on demand

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

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

Title:
  Downloads changelogs for non desktop components

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Using the current xenial version, seeing the warning on the command
  line it seems the code tries to download the changelogs for all the
  packages that have an update, but then it filters things out to
  display only desktop components ... there is no need to download
  content for things that are not displayed in the interface

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

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

[Desktop-packages] [Bug 1574666] Re: Updates tab slow to load due to downloading changelog information

2016-09-15 Thread Robert Ancell

Solved by making the changelogs download on demand.

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

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

Title:
  Updates tab slow to load due to downloading changelog information

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Changelog information is downloaded from changelogs.ubuntu.com. These
  must all be loaded before the updates tab is populated.

  This is slow because:
  - Changelogs are downloaded for non-GUI packages (bug 1554166)
  - Changelogs are downloaded sequentially.

  Downloading in parallel would speed this up significantly.

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

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

[Desktop-packages] [Bug 1624211] [NEW] Network-manager randomly won't recognize wireless card after resuming from sleep or hibernation or when disabling/reenabling the card

Public bug reported:

When resuming from sleep or coming out of hibernation and sometimes when
disabing and reenabling the wireless card (using Fn + the corresponding
key), network-manager will stop recognizing that there's a wireless card
in my laptop. The bluetooth applet and the card themselves still work. I
can still connect to the same network it was connected before putting it
to sleep/hibernate (because it's a known network and it does so
automatically) but network-manager won't display anything regarding me
having a wireless card, displaying the icon and information I would
expect if I were connected using an ethernet cable.

A workaround consists in restarting the network-manager service using
systemctl

sudo service network-manager restart

or

sudo systemctl restart network-manager.service


The system is a Dell Vostro 5470 running a fresh installation of Ubuntu 
16.04.1. If I recall correctly, this also happened with Ubuntu 14.04.4 too. 
BIOS version is A12 (the latest).

I've seen several people with problems like this one that were solved by
restarting network-manager (a quick Googling shows a handful of such
cases). This can be a huge turn off for a newcomer.

Some people also suggested creating a systemd service to restart the
network-manager service when resuming, etc. but since this bug also
occurs when disabling/reenabling the card, it might have another cause
that's unrelated to resuming from sleep.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.3
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
CurrentDesktop: Unity
Date: Fri Sep 16 01:26:01 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-09-10 (6 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.248  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
That's no moon! 1  2a59043a-02a4-4da0-ab5c-3c89c52bd15f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
  ----  
   
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug network-manager wireless xenial

** Attachment added: "This is what happens."
   
https://bugs.launchpad.net/bugs/1624211/+attachment/4741747/+files/Espa%C3%A7o%20de%20Trabalho%201_005.png

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

Title:
  Network-manager randomly won't recognize wireless card after resuming
  from sleep or hibernation or when disabling/reenabling the card

Status in network-manager package in Ubuntu:
  New

Bug description:
  When resuming from sleep or coming out of hibernation and sometimes
  when disabing and reenabling the wireless card (using Fn + the
  corresponding key), network-manager will stop recognizing that there's
  a wireless card in my laptop. The bluetooth applet and the card
  themselves still work. I can still connect to the same network it was
  connected before putting it to sleep/hibernate (because it's a known
  network and it does so automatically) but network-manager won't
  display anything regarding me having a wireless card, displaying the
  icon and information I would expect if I were connected using an
  ethernet cable.

  A workaround consists in restarting the network-manager service using
  systemctl

  sudo service network-manager restart

  or

  sudo systemctl restart network-manager.service

  
  The system is a Dell Vostro 5470 running a fresh installation of Ubuntu

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

2016-09-15 Thread triode

No love here, with either the top listed Xenial package, nor the 'LTS'
at the bottom. Even without either package installed, I am able to get
sound via USB to a stand alone DAC and headphone amplifier via Spotify
and DeadBeef, but no sound from internet/youtube, through speakers or my
DAC/amp.

-- 
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 1620994] Re: [regression] Starting in Mesa 12.0.2, EGL clients crash with SIGSEGV in dri2_destroy_context() (from eglDestroyContext or eglTerminate)

** Tags added: egl-platform-mir

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

Title:
  [regression] Starting in Mesa 12.0.2, EGL clients crash with SIGSEGV
  in dri2_destroy_context() (from eglDestroyContext or eglTerminate)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed x86, nvidia 8600gt nouveau

  unity8-dash crashed with SIGSEGV in eglDestroyContext()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep  7 13:04:53 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-06-05 (93 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  SegvAnalysis:
   Segfault happened at: 0x7fcab45aea3e:mov0x30(%rbp),%rax
   PC (0x7fcab45aea3e) ok
   source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGSEGV in eglDestroyContext()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log: [2016-09-07:13:04:52.767] QEGLPlatformContext: 
eglMakeCurrent failed: 3001

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

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

[Desktop-packages] [Bug 1620934] Re: [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

** Tags added: egl-platform-mir

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

Title:
  [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any
  more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Desktop-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-09-15 Thread Alan Robertson

Hi Christopher M. Penalver (@penalvch),

I have tons of old kernels to choose from. What one would you like for me to 
try?
Here are the choices:
vmlinuz-3.19.0-28-generic  vmlinuz-3.19.0-41-generic  vmlinuz-4.2.0-36-generic
vmlinuz-3.19.0-30-generic  vmlinuz-3.19.0-42-generic  vmlinuz-4.4.0-22-generic
vmlinuz-3.19.0-31-generic  vmlinuz-3.19.0-43-generic  vmlinuz-4.4.0-24-generic
vmlinuz-3.19.0-32-generic  vmlinuz-3.19.0-47-generic  vmlinuz-4.4.0-28-generic
vmlinuz-3.19.0-33-generic  vmlinuz-3.19.0-49-generic  vmlinuz-4.4.0-31-generic
vmlinuz-3.19.0-37-generic  vmlinuz-3.19.0-51-generic  vmlinuz-4.4.0-34-generic
vmlinuz-3.19.0-39-generic  vmlinuz-3.19.0-56-generic  vmlinuz-4.4.0-36-generic

By the way, I did try this before, and I think it worked, but I had
trouble with USB devices afterwards (or so I remember). Since my mice
are USB, that was a problem.

So it would be helpful to me for you to suggest which kernel you would
like for me to try...

Something I forgot to say...
When I remove all the .kde stuff and it boots up correctly (but crippled due to 
all my config missing), then the fifo underrun does _not_ occur. It occurs only 
once per login.

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I just took some updates to a number of graphic libraries on 16.04,
  and now I can't login to kubuntu. The symptom is that it takes my
  password on the greeter screen, but never updates the screen after
  that.

  The messages include these possibly related kernel messages:
  kernel: [ 701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
  kernel: [ 701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] 
*ERROR* CPU pipe B FIFO underrun

  I'm currently running kernel 4.4.0-36.

  Here are my most recent updates. The problem started after I rebooted.
  Of course that was the next time I logged in too...

  Start-Date: 2016-09-07 08:46:04
  Commandline: /usr/bin/unattended-upgrade
  Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
  End-Date: 2016-09-07 08:48:13

  Start-Date: 2016-09-07 16:42:27
  Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
  Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2
 743.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
  End-Date: 2016-09-07 16:44:34

  Start-Date: 2016-09-12 14:31:39
  Commandline: /usr/sbin/synaptic
  Requested-By: alanr (1000)
  Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64

[Desktop-packages] [Bug 1620994] Re: [regression] Starting in Mesa 12.0.2, EGL clients crash with SIGSEGV in dri2_destroy_context() (from eglDestroyContext or eglTerminate)

2016-09-15 Thread Chris Halse Rogers

Not an upstream bug; this is a semantic merge error when updating the
Mir EGL platform patch.

** Changed in: mesa (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

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

Title:
  [regression] Starting in Mesa 12.0.2, EGL clients crash with SIGSEGV
  in dri2_destroy_context() (from eglDestroyContext or eglTerminate)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed x86, nvidia 8600gt nouveau

  unity8-dash crashed with SIGSEGV in eglDestroyContext()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep  7 13:04:53 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-06-05 (93 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  SegvAnalysis:
   Segfault happened at: 0x7fcab45aea3e:mov0x30(%rbp),%rax
   PC (0x7fcab45aea3e) ok
   source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGSEGV in eglDestroyContext()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log: [2016-09-07:13:04:52.767] QEGLPlatformContext: 
eglMakeCurrent failed: 3001

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

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

[Desktop-packages] [Bug 1577942] Re: package ubuntu-drivers-common 1:0.4.17 failed to install/upgrade: pacote ubuntu-drivers-common não está pronto para configuração não posso configurar (estado atua

You may try to run

sudo apt-get -f install

which sometimes corrects this kind of thing.

May I ask you why you're using a 32-bit install? The 64-bit became the
recommended one some time ago.

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

Title:
  package ubuntu-drivers-common 1:0.4.17 failed to install/upgrade:
  pacote ubuntu-drivers-common não está pronto para configuração  não
  posso configurar (estado atual 'half-installed')

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

Bug description:
  I don't know if it is a real bug or a system misunderstanding. I'm
  running a brand new installation of Ubuntu Studio 16.04 32bit ins a
  Dell Inspiron 1525. It did not recognize my Broadcom Wireless card, so
  i ran "sudo apt-get install b43-fwcutter firmware-b43-installer" in a
  terminal and this error came to me.

  The system told me to run "sudo dpkg --configure -a" and reboot. I did
  it and tried again the installation of b43-fwcutter and this time,
  even with the same error, my wireless connection was recognized

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   b43-fwcutter: Install
   ubuntu-drivers-common: Configure
   b43-fwcutter: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Tue May  3 18:09:21 2016
  ErrorMessage: pacote ubuntu-drivers-common não está pronto para configuração  
não posso configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2016-05-03 (0 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ubuntu-drivers-common
  Title: package ubuntu-drivers-common 1:0.4.17 failed to install/upgrade: 
pacote ubuntu-drivers-common não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  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/1577942/+subscriptions

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

[Desktop-packages] [Bug 1623254] Re: Base: trying to set limits in queries gives an 'unexpected token' error

2016-09-15 Thread Christopher M. Penalver

Matteo Paolini:
1) Was this an issue in a prior LibreOffice version?
2) Would testing the latest version of LO provide a WORKAROUND via 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2 ?

** Changed in: libreoffice (Ubuntu)
   Importance: Low => Medium

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

Title:
  Base: trying to set limits in queries gives an 'unexpected token'
  error

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When I'm trying to set a limit in a query about how many records it
  should display I get an 'unexpected token' error, whether I input the
  value manually or choose it from the dropdown menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.4-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Tue Sep 13 17:40:45 2016
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-06-14 (91 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-09-15 Thread Christopher M. Penalver

Alan Robertson, thank you for reporting this and helping make Ubuntu
better.

To clarify, if you boot into the kernel prior to the update, does this
issue go away?

** Tags added: bios-outdated-2202 regression-update

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I just took some updates to a number of graphic libraries on 16.04,
  and now I can't login to kubuntu. The symptom is that it takes my
  password on the greeter screen, but never updates the screen after
  that.

  The messages include these possibly related kernel messages:
  kernel: [ 701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
  kernel: [ 701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] 
*ERROR* CPU pipe B FIFO underrun

  I'm currently running kernel 4.4.0-36.

  Here are my most recent updates. The problem started after I rebooted.
  Of course that was the next time I logged in too...

  Start-Date: 2016-09-07 08:46:04
  Commandline: /usr/bin/unattended-upgrade
  Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
  End-Date: 2016-09-07 08:48:13

  Start-Date: 2016-09-07 16:42:27
  Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
  Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2
 743.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
  End-Date: 2016-09-07 16:44:34

  Start-Date: 2016-09-12 14:31:39
  Commandline: /usr/sbin/synaptic
  Requested-By: alanr (1000)
  Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), 
accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
  End-Date: 2016-09-12 14:32:17

  
  It was after rebooting after updates that this occurred. My workaround is "rm 
-fr ~/.kde" - and that allows me to log in. I'm crippled, but at least I can 
log in...

  If I try to log in again without doing this, the problem recurs. This
  happens even if I just log in and log back out, and try to log in
  again.

  However, I may just found a better workaround - press ALT-CTRL-F1 then
  ALT-CTRL-F7, and then the next chunk of the login sequence occurs.

  This makes it consistent with an issue reported in AskUbuntu
  http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen-
  hangs

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

2016-09-15 Thread Luke Yelavich

Could anybody affected by this bug please try upgrading the HDA audio
driver, as outlined here.
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS.

If you have made changes to files in /etc/modprobe.d as suggested above,
please undo those changes prior to updating.

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-09-15 Thread Florian Fainelli

OK, just wondering because in my case that was it, I had nvidia in
/etc/modules and the blacklisted check seemed to fail because of that.

The whole gpu-manager code is pretty unreadable, and quite frankly I
don't even think this makes sense to write it in C considering that
there is already python code elsewhere, anyway...

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

[Desktop-packages] [Bug 1576977] Re: Lots of GEGL-gegl-operation.c-WARNING on starting gimp

2016-09-15 Thread Ted

I've fully updated all my packages and I am still getting this bug when
running gimp from the command line. Has anyone found a fix to this or do
I need to revert to an older version of gimp for it to work again?

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

Title:
  Lots of GEGL-gegl-operation.c-WARNING on starting gimp

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04
  gimp: 2.8.16-1ubuntu1

  rm ~/.gimp-2.8/
  LANG=en gimp

  
  (gimp:413): GLib-GObject-WARNING **: g_object_set_valist: object class 
'GeglConfig' has no property named 'cache-size'

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A3410 from "gimp:point-layer-mode" to "gimp
  :dissolve-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A39B0 from "gimp:point-layer-mode" to "gimp
  :behind-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4090 from "gimp:point-layer-mode" to "gimp
  :multiply-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A43A0 from "gimp:point-layer-mode" to "gimp
  :screen-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4790 from "gimp:point-layer-mode" to "gimp
  :overlay-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4BC0 from "gimp:point-layer-mode" to "gimp
  :difference-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5800 from "gimp:point-layer-mode" to "gimp
  :addition-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5BC0 from "gimp:point-layer-mode" to "gimp
  :subtract-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5F80 from "gimp:point-layer-mode" to "gimp
  :darken-only-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A63D0 from "gimp:point-layer-mode" to "gimp
  :lighten-only-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A68E0 from "gimp:point-layer-mode" to "gimp:hue-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A6B40 from "gimp:point-layer-mode" to "gimp
  :saturation-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A6F70 from "gimp:point-layer-mode" to "gimp:color-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A73E0 from "gimp:point-layer-mode" to "gimp:value-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7760 from "gimp:point-layer-mode" to "gimp
  :divide-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7BE0 from "gimp:point-layer-mode" to "gimp:dodge-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7F50 from "gimp:point-layer-mode" to "gimp:burn-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A83A0 from "gimp:point-layer-mode" to "gimp
  :hardlight-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A8740 from "gimp:point-layer-mode" to "gimp
  :softlight-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A8B40 from "gimp:point-layer-mode" to "gimp:grain-
  extract-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A90A0 from "gimp:point-layer-mode" to "gimp:grain-
  merge-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A93C0 from "gimp:point-layer-mode" to "gimp:color-
  erase-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A9730 from "gimp:point-layer-mode" to "gimp:erase-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20AA080 from "gimp:point-layer-mode" to "gimp
  :replace-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20AA450 from "gimp:point-layer-mode" to "gimp:anti-
  erase-mode"

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

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

[Desktop-packages] [Bug 1622832] Re: package nvidia-367 367.44-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

This does not happen in Ubuntu 16.04.1 with the standard 4.4 kernel.

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

Title:
  package nvidia-367 367.44-0ubuntu0.16.04.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 10

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

Bug description:
  отсутствуют модули для i915

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.44-0ubuntu0.16.04.2
  Uname: Linux 4.8.0-rc5-alelic-00176-gd0acc7d x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Sep 13 07:02:16 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2015-08-08 (401 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: nvidia-graphics-drivers-367
  Title: package nvidia-367 367.44-0ubuntu0.16.04.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 10
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (30 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741693/+files/Xorg.0.log

-- 
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 Committed

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 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

** Attachment added: "X.org log after updating to ubuntu-drivers-common from 
xenial-proposed"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741696/+files/Xorg.0.log

-- 
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 Committed

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 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

** Attachment added: "GPU Manager log after installing the 
ubuntu-drivers-common from xenial-proposed"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741695/+files/gpu-manager.log

** Attachment removed: "X.org log after installing the ubuntu-drivers-common 
from xenial-proposed"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741695/+files/gpu-manager.log

-- 
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 Committed

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 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

I installed this package from xenial-proposed and rebooted. The nVidia
card was shut down correctly.


** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741694/+files/gpu-manager.log

-- 
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 Committed

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 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

I can confirm that indee, installing newer drivers will cause the dGPU
to stay on.

** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741692/+files/gpu-manager.log

-- 
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 Committed

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 1606078] Re: No sound with Ubuntu 16.04

2016-09-15 Thread triode

Same issue. Upgraded from Xubuntu 14.04 to 16.04.

-- 
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:
  Confirmed

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 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all

2016-09-15 Thread Luke Yelavich

Could you please try updating the HDA audio driver, as outlined here:
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS.

Thanks.

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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 1598300] Re: cups hang after a while

I tried now the following:

till@till-x1carbon:~/printing/cups/bzr/y$ sudo systemctl stop cups
Warning: Stopping cups.service, but it can still be activated by:
  cups.socket
  cups.path
till@till-x1carbon:~/printing/cups/bzr/y$ ps auxwww | grep cupsd
till  4265  0.0  0.0  14224   896 pts/19   S+   23:33   0:00 grep 
--color=auto cupsd

Accessed http://localhost:631/ in web browser --> FAILED.


till@till-x1carbon:~/printing/cups/bzr/y$ lpstat -r
scheduler is running

Accessed http://localhost:631/ in web browser --> SUCCEEDED (the "lpstat -r" 
triggered cupsd by
 domain socket)

till@till-x1carbon:~/printing/cups/bzr/y$ ps auxwww | grep cupsd
root  4290  1.4  0.1 169908 10260 ?Ssl  23:33   0:00 
/usr/sbin/cupsd -l
till  4311  0.0  0.0  14224  1056 pts/19   S+   23:33   0:00 grep 
--color=auto cupsd
till@till-x1carbon:~/printing/cups/bzr/y$ 

So for the web interface we need some systemd unit file which triggers
CUPS via port 631. Any example files welcome.


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

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

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

@Florian

/etc/modules is empty (only a few genuine lines commented), so its not
the reason pushing that error.

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

-- 
Mailing list: https://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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-09-15 Thread Kyle

I cant tell anymore as i cant even get to a command prompt anymore, if i
recall something about dns is the error now

Sent from my HTC

- Reply message -
From: "Florian Fainelli" 
To: 
Subject: [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
Date: Thu, Sep 15, 2016 10:15 PM

The "/etc/modprobe.d is not a file" error is kind of confusing actually
and seems to be some stray debug in share/hybrid/gpu-manager.c.

Do you have nvidia in /etc/modules by chance?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1369216

Title:
gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
Get these lines logged into gpu-manager.log, on that fresh stock
installation

/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart 1.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep 14 08:42:45 2014
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
modified.conffile..etc.default.whoopsie: [modified]
modified.conffile..etc.gdm.Init.Default: [modified]
mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

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

First, xinetd is not needed. systemd handles running services on-demand
well.

Important to know is that there are two access methods for CUPS:

1. The domain socket file /var/run/cups/cups.sock

2. IP Port 631

CUPS can be configured to use one of these methods or both.

Both methods can be used and the applications printing via CUPS and
correctly implemented (usually using libcups) automatically choose a
suitable method.

As web browsers can only access network locations, the CUPS web
interface is only available via port 631, for example under the URI
http://localhost:631/. This means that a CUPS only configured for the
domain socket cannot use the web interface at all.

When I look at the systemd files which describe how to automatically
start CUPS, I see only a /lib/systemd/system/cups.socket which starts
CUPS by traffic on the domain socket and
/lib/systemd/system/cups.service which starts CUPS on boot. I do not see
some systemd instruction file making CUPS triggered via port 631. This
seems to be the problem.

By the way, Mike Sweet, author of CUPS, tells that the web interface
should work with on-demand CUPS daemon. See
https://github.com/apple/cups/issues/4874.

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

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-09-15 Thread Florian Fainelli

The "/etc/modprobe.d is not a file" error is kind of confusing actually
and seems to be some stray debug in share/hybrid/gpu-manager.c.

Do you have nvidia in /etc/modules by chance?

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

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

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Confirmed

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 1623487] Re: [OptiPlex 7040, Realtek ALC3234, Black Headphone Out, Front] No sound at all

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

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


** This bug has been marked a duplicate of bug 1616413
   [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all

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

Title:
  [OptiPlex 7040, Realtek ALC3234, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My desktop doesn't make any sound. I am using ubuntu 16.04.1 LTS. aplay -l 
output gives me this:
  card 0: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  But Iam not sure where to look for a driver or what else to do... For me it 
seems to be a bug.

  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:   jan4048 F...m pulseaudio
   /dev/snd/controlC0:  jan4048 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 14 15:01:43 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-09-07 (6 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jan4048 F...m pulseaudio
   /dev/snd/controlC0:  jan4048 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [OptiPlex 7040, Realtek ALC3234, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: Upgraded to xenial on 2016-09-14 (0 days ago)
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.5
  dmi.board.name: 096JG8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.5:bd06/27/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn096JG8:rvrA01: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/1623487/+subscriptions

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

[Desktop-packages] [Bug 1621210] Re: libgs9-common recommends fonts-droid-fallback, which isn't in main

2016-09-15 Thread Mathew Hodson

** No longer affects: fonts-android (Ubuntu)

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

Title:
  libgs9-common recommends fonts-droid-fallback, which isn't in main

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

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

[Desktop-packages] [Bug 1462647] Re: Native Client (NaCl) not working in Chromium Dev

2016-09-15 Thread vans163

This is quite unfortunate.

I am looking for NaCl support as well, javascript is just not fast
enough for some things nor does it give you access to the amazing pepper
api.

I will use Chrome for now but directing users to use Chrome vs chromium
is really unfortunate.

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

Title:
  Native Client (NaCl) not working in Chromium Dev

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Native Client isn't working in Chromium Browser dev ppa. Everything
  that requires Native Client will either silently fail, or display a
  gray box with a plug icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 45.0.2414.0-0ubuntu1~ppa1~vivid1 [origin: 
LP-PPA-saiarcot895-chromium-dev]
  Uname: Linux 4.1.0-040100rc6-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Jun  6 12:17:10 2015
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2015-05-02 (34 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron: Error: [Errno 13] Permission denied: '/proc/18807/environ'
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1621210] Re: libgs9-common recommends fonts-droid-fallback, which isn't in main

This bug was fixed in the package ghostscript - 9.19~dfsg+1-0ubuntu3

---
ghostscript (9.19~dfsg+1-0ubuntu3) yakkety; urgency=medium

  * debian/rules:
+ Make libgs9-common recommend fonts-noto-cjk instead of
  fonts-droid-fallback (LP: #1621210).

 -- Gunnar Hjalmarsson   Thu, 15 Sep 2016 08:22:00
+0200

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

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

Title:
  libgs9-common recommends fonts-droid-fallback, which isn't in main

Status in fonts-android package in Ubuntu:
  Invalid
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

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

[Desktop-packages] [Bug 1624162] [NEW] /usr/share/system-config-printer/system-config-printer.py:11:_gdk_window_has_impl:gdk_x11_window_get_xid:topmenu_monitor_set_cur_server:handle_cur_server_event:g

2016-09-15 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding system-config-printer.  This problem was most recently seen
with version 1.5.7+20160212-0ubuntu2, the problem page at
https://errors.ubuntu.com/problem/4beb2c1a7b67234391f51f1963a2e40a1fba747c
contains more details.

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

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

Title:
  /usr/share/system-config-printer/system-config-
  
printer.py:11:_gdk_window_has_impl:gdk_x11_window_get_xid:topmenu_monitor_set_cur_server:handle_cur_server_event:gdk_event_apply_filters

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding system-config-printer.  This problem was most recently seen
  with version 1.5.7+20160212-0ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/4beb2c1a7b67234391f51f1963a2e40a1fba747c
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1624162/+subscriptions

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

[Desktop-packages] [Bug 1561285] Re: snapd operations don't contain progress information

2016-09-15 Thread Robert Ancell

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

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

Title:
  snapd operations don't contain progress information

Status in Snappy:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  Polling for snapd operation status (/2.0/operations/[uuid]) doesn't
  seem to provide any information about progress (e.g. download count /
  rate). This makes it hard to estimate when an operation will complete.

  In comparison, 'snappy install' shows download information.

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

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

[Desktop-packages] [Bug 1621753] Re: Google Cast no longer finds Chromecast device

2016-09-15 Thread ChrisC

may not be an ubuntu bug...on Mint 17.1 using Chrome 64.after a
recent Chrome update my extension became inactive whenever chrome
started. Each time I have to go to extension menu, find google cast, and
turn it back on. I think this may be a Google issue.

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

Title:
  Google Cast no longer finds Chromecast device

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to latest chromium-browser version
  (52.0.2743.116-0ubuntu0.16.04.1.1250), the Google Cast extension no
  longer finds the Chromecast (v2) device. This used to work with the
  previous chromium version.

  Also, google-chrome-stable 53.0.2785.101-1 works fine on the same box,
  so the issue is with the chromium update.

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

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

[Desktop-packages] [Bug 1624150] [NEW] Resolution

2016-09-15 Thread Vitor Marchini Rolisola

Public bug reported:

the unique option for screen resolution is a proximally 680x480 and no
exist other option

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.1:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog: /dev/sda5: clean, 187756/5857280 files, 1290105/23402752 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Sep 15 18:41:44 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer 771/671 PCIE VGA Display Adapter [1558:0801]
InstallationDate: Installed on 2016-09-15 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 
802.11g 54Mbps Network Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Positivo Positivo Mobile
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=99fc0e3b-180c-4fc0-939a-928cc286081f ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/01/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.asset.tag: 1234567890
dmi.board.name: M7x0S
dmi.board.vendor: clevo
dmi.board.version: Bottom
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SiS
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/01/2009:svnPositivo:pnPositivoMobile:pvr1.00.13PO_POS:rvnclevo:rnM7x0S:rvrBottom:cvnSiS:ct1:cvrN/A:
dmi.product.name: Positivo Mobile
dmi.product.version: 1.00.13PO_POS
dmi.sys.vendor: Positivo
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Sep 15 14:21:42 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2

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


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

** Attachment added: "No option to choose"
   
https://bugs.launchpad.net/bugs/1624150/+attachment/4741606/+files/20160915_195508.jpg

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

Title:
  Resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  the unique option for screen resolution is a proximally 680x480 and no
  exist other option

  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.1:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda5: clean, 187756/5857280 files, 1290105/23402752 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep 15 18:41:44 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 771/671 PCIE VGA Display Adapter 
[1558:0801]
  InstallationDate: Installed on 2016-09-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor

[Desktop-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2016-09-15 Thread Bernie Bernstein

I'm seeing this same issue with Xenial and my logitech H800 headset.

The profile A2DP is automatically selected and I am unable to specify
HSP/HFP.  As a result, I am unable to get the microphone through
bluetooth.

I have bluez 5.37-0ubuntu5 currently installed.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

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

[Desktop-packages] [Bug 259698] Re: pptp vpn service stops unexpectedly

2016-09-15 Thread Mitchell Baker

I am using GalliumOS for my chromebook, which is an *buntu derivative.
I was checking permissions my user had in "Users and Groups" gui.
"Connect to wireless and ethernet networks" was not checked.

I checked it and saved.  Retried connecting to my PPTP vpn and it
worked.  I had also tried other solutions unsuccessfully so mileage may
vary.

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

Title:
  pptp vpn service stops unexpectedly

Status in pptp-linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pptp-linux

  Using ubuntu 8.10 x86.

  pptp-linux version 1.7.2-1

  When I select the vpn option, I can create the VPN configuration, but
  after trying to connect for around ~1 second, I get the popup error:

  "The VPN connection 'Warwick' failed because the VPN service stopped
  unexpectedly."

  Im not entirely sure how to execute the connection via command line,
  so I cant work out how to get any more info on what is going on.

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

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

[Desktop-packages] [Bug 1623151] Re: Screen flickers when using external monitor

2016-09-15 Thread Timo Aaltonen

could you bisect it using the mainline builds? It's probably either
4.5-rc1 or 4.6-rc1 that fixed it.. but would be good to know

** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Incomplete

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

Title:
  Screen flickers when using external monitor

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

Bug description:
  Continued from Bug 1572667

  Occasionally my external monitor will go black for a second and then
  return. Currently I am running the mainline kernel version
  4.6.7-040607 and the problem does not appear.

  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:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Sep 13 11:25:58 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2016-08-04 (39 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-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 13 11:24:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1049 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1623151/+subscriptions

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

[Desktop-packages] [Bug 1624108] Re: ¿?

2016-09-15 Thread Tyler Hicks

Hi Juan - Please see this page on how to upgrade Ubuntu:

  http://www.ubuntu.com/download/desktop/upgrade

If you need additional help, please see this page for a number of
support resources:

  https://community.ubuntu.com/help-information/

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

** Information type changed from Private Security to Public

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

Title:
  ¿?

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ¿?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-59.66-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.8
  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: Thu Sep 15 15:24:53 2016
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780MC [Mobility Radeon HD 3100] 
[1002:9613] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:ff50]
  InstallationDate: Installed on 2015-04-17 (517 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite M305D
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-59-generic 
root=UUID=02a275e7-f4c2-4972-8233-2d635622e645 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.50
  dmi.board.name: Satellite M305D
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.50:bd06/13/2008:svnTOSHIBA:pnSatelliteM305D:pvrPSMDYU-00E005:rvnTOSHIBA:rnSatelliteM305D:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:
  dmi.product.name: Satellite M305D
  dmi.product.version: PSMDYU-00E005
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Aug 23 22:22:52 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.3
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1616548] Re: Cups causes LibreOffice unittests to loop in a sbuild

Recently, CUPS in Ubuntu was configured to run on-demand, to save
resources, especially laptop or phone batteries. Perhaps one should
somehow make CUPS run permanently, perhaps as long as sbuild is doing a
build. Please try this.

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

Title:
  Cups causes LibreOffice unittests to loop in a sbuild

Status in cups package in Ubuntu:
  Confirmed
Status in sbuild package in Ubuntu:
  Incomplete
Status in winff package in Ubuntu:
  Fix Committed

Bug description:
  When building LibreOffice 1:5.2.0-0ubuntu1 on a xenial host with a
  yakkety sbuild, e.g. by:

  sbuild -A -d yakkety-amd64 (...).dsc

  this loops/busy hangs with unittests. This was working ok up to
  5.2.0~rc4 (=final), it is a regression by a LibreOffice dependency,
  most likely CUPS, which was updated.

  I tried to inject debug symbols by running with a: --chroot-setup-
  command and then run something along the lines of:

   apt install cups
   wget http://launchpadlibrarian.net/278966811/cups-dbgsym_2.2~rc1-4_amd64.ddeb
   wget 
http://launchpadlibrarian.net/278966816/libcups2-dbgsym_2.2~rc1-4_amd64.ddeb
   dpkg -i cups-dbgsym_2.2~rc1-4_amd64.ddeb
   dpkg -i libcups2-dbgsym_2.2~rc1-4_amd64.ddeb

  before starting the build proper, but I got only marginally better
  debug info. The hanging LibreOffice test processes usually have 2-4
  child processes. The parent and one of the childs are busy, while the
  rest idle.

  Here is a stacktrace of the busy child:

  Program received signal SIGPIPE, Broken pipe.
  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  43in fgetspent.c
  (gdb) bt
  #0  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  #1  0x001e in ?? ()
  #2  0x55c4976981e0 in ?? ()
  #3  0x2b0a8aff8d20 in ipp_options () from 
/usr/lib/x86_64-linux-gnu/libcups.so.2
  #4  0x4002 in ?? ()
  #5  0x2b0a8ada9feb in ppdCollect2 (ppd=0x2b0a8ada9bdf 
, section=29, min_order=0, choices=0x2b0a8adad6f3 
) at emit.c:145
  #6  0x in ?? ()

  Here is a stacktrace of the busy parent:

  Thread 3 "CUPSManager cup" received signal SIGPIPE, Broken pipe.
  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  43in fgetspent.c
  (gdb) bt
  #0  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  #1  0x001e in ?? ()
  #2  0x55c4976981e0 in ?? ()
  #3  0x2b0a8aff8d20 in ipp_options () from 
/usr/lib/x86_64-linux-gnu/libcups.so.2
  #4  0x4002 in ?? ()
  #5  0x2b0a8ada9feb in ppdCollect2 (ppd=0x2b0a8ada9bdf 
, section=29, min_order=0, choices=0x2b0a8adad6f3 
) at emit.c:145
  #6  0x in ?? ()

  
  When pressing "c" in gdb to continue, both processes stop very quickly again 
with the SIGPIPE.
  Venturing a guess: Is the signal handling of CUPS b0rked? As fgetspent reads 
the shadow file[1], maybe there are missing permissions or other sandbox issues 
that CUPS doesnt handle error cases for properly?

  [1] http://linux.die.net/man/3/fgetspent

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

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

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

I posted an upstream feature request now to improve the web interface
for CUPS running on-demand. See
https://github.com/apple/cups/issues/4874.


** Bug watch added: github.com/apple/cups/issues #4874
   https://github.com/apple/cups/issues/4874

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

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Desktop-packages] [Bug 1622206] Re: package account-plugin-google not installed failed to install/upgrade: trying to overwrite /usr/share/accounts/services/google-im.service , which is also in packag

2016-09-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package account-plugin-google  not installed  failed to
  install/upgrade: trying to overwrite  /usr/share/accounts/services
  /google-im.service , which is also in package kde-config-telepathy-
  accounts 4:15.12.3-0ubuntu1!

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 00:41:19 2016
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1622206] Re: package account-plugin-google not installed failed to install/upgrade: trying to overwrite /usr/share/accounts/services/google-im.service , which is also in packag

2016-09-15 Thread Tyler Hicks

** Information type changed from Private Security to Public

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

Title:
  package account-plugin-google  not installed  failed to
  install/upgrade: trying to overwrite  /usr/share/accounts/services
  /google-im.service , which is also in package kde-config-telepathy-
  accounts 4:15.12.3-0ubuntu1!

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 00:41:19 2016
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579319] Re: Text missing in GTK+ applications after suspend

2016-09-15 Thread Henry J. Douglas

I thought disabling Slight Hinting would solve it permanently, but then
I had to change the "SubPixel thing" to something else for it to stop
corrupting characters after screen lock/suspend. Then it happened again
anyway! I'm out of workarounds and I got tired of Ubuntu's bugs. Not
installed right now.

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

Title:
  Text missing in GTK+ applications after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Occasionally when resuming from suspend, text is randomly missing in
  GTK+ applications. Chrome and QT apps are unaffected. In my case it
  doesn't occur very frequently, perhaps once a week at most. I
  typically suspend my system every day and only reboot once or twice a
  month.

  It's not clear what is causing the problem. Based on the symptoms and
  similar bug reports, it seems most likely a problem with xorg and/or
  xserver-xorg-video-intel. It appears to be a new bug with 16.04 as I
  never experienced this in 15.10.

  I've noticed that the amount of missing text seems to vary depending
  on the font and font size. Some fonts/sizes seem to be okay, while
  with others there is no text on screen at all.

  Font rendering settings also appear have an effect. The problem is
  only visible with slight hinting and RGB sub pixel order. Disabling
  anti-aliasing or changing either the hinting or sub pixel order to
  anything else immediately renders all characters normally.

  Switching to a virtual terminal and back again fixes the problem
  (Ctrl+Alt+F1 then Ctrl+Alt+F7), as does restarting Xorg or logging
  out.

  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
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat May  7 12:39:24 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
  InstallationDate: Installed on 2016-04-23 (13 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Extensa 5230
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=ba619ff4-ea0b-4b58-aa61-e79a3e7e7c1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.28
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5230
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 02:12:16 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   15105 
   vendor LPL
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 856210] Re: giornata folle

2016-09-15 Thread Fabio Rossi

Caro,


Ho avuto una giornata folle ieri e ho voluto condividere la storia con voi,  si 
può trovare  qui 

Grazie per la tua considerazione,FBIO ROSSI

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

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

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

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

[Desktop-packages] [Bug 1599580] Re: package bamfdaemon 0.5.3~bzr0+16.04.20160523-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

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

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

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.04.20160523-0ubuntu1 failed to
  install/upgrade: triggers looping, abandoned

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  What does bamfdaemon do?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.3~bzr0+16.04.20160523-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul  3 11:06:00 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-04-21 (75 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.04.20160523-0ubuntu1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1624067] Re: network app open, error occured, (wired realtek not seen))

2016-09-15 Thread Apport retracing service

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

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

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

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

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

** This bug has been marked a duplicate of bug 1619922
   gnome-software crashed with SIGSEGV in look_at_pkg()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  network app open, error occured, (wired realtek not seen))

Status in gnome-software package in Ubuntu:
  New

Bug description:
  tom@ubuntu:~$ lspci
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 7 (rev b5)
  00:1c.7 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 
4 port SATA IDE Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  00:1f.5 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 
2 port SATA IDE Controller (rev 05)
  03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller
  04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  05:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge 
(rev 01)
  tom@ubuntu:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu2
  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-Classic:GNOME
  Date: Thu Sep 15 13:23:44 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-09-09 (6 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160825.1)
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1621210] Re: libgs9-common recommends fonts-droid-fallback which isn't in main

2016-09-15 Thread Jeremy Bicha

** Changed in: ghostscript (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  libgs9-common recommends fonts-droid-fallback, which isn't in main

Status in fonts-android package in Ubuntu:
  Invalid
Status in ghostscript package in Ubuntu:
  Fix Committed

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

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

[Desktop-packages] [Bug 1621210] Re: libgs9-common recommends fonts-droid-fallback, which isn't in main

2016-09-15 Thread Mathew Hodson

** Summary changed:

- libgs9-common recommends fonts-droid-fallback which isn't in main
+ libgs9-common recommends fonts-droid-fallback, which isn't in main

** Tags added: packaging

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

Title:
  libgs9-common recommends fonts-droid-fallback, which isn't in main

Status in fonts-android package in Ubuntu:
  Invalid
Status in ghostscript package in Ubuntu:
  Fix Committed

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

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

[Desktop-packages] [Bug 1623151] Re: Screen flickers when using external monitor

2016-09-15 Thread Bryan Abhser

Also this only happens when using my external dock not with the display
port on the laptop.

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

Title:
  Screen flickers when using external monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Continued from Bug 1572667

  Occasionally my external monitor will go black for a second and then
  return. Currently I am running the mainline kernel version
  4.6.7-040607 and the problem does not appear.

  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:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Sep 13 11:25:58 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2016-08-04 (39 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-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 13 11:24:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1049 
   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/1623151/+subscriptions

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

[Desktop-packages] [Bug 1621210] Re: [MIR] fonts-android

2016-09-15 Thread Mathew Hodson

** Bug watch removed: Debian Bug tracker #804684
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804684

** Summary changed:

- [MIR] fonts-android
+ libgs9-common recommends fonts-droid-fallback which isn't in main

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

Title:
  libgs9-common recommends fonts-droid-fallback, which isn't in main

Status in fonts-android package in Ubuntu:
  Invalid
Status in ghostscript package in Ubuntu:
  Fix Committed

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

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

[Desktop-packages] [Bug 1491043] Re: libxcb 1.10 has important bug fixed in 1.11

** Changed in: libxcb (Ubuntu Vivid)
   Status: Triaged => Invalid

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

Title:
  libxcb 1.10 has important bug fixed in 1.11

Status in libxcb package in Ubuntu:
  Fix Released
Status in libxcb source package in Trusty:
  Triaged
Status in libxcb source package in Vivid:
  Invalid

Bug description:
  libxcb 1.10 has serious bug which prevents multi-threaded OpenGL applications 
from working.
  It crashes app with message like:
  ../../src/xcb_conn.c:186: write_vec: Assertion `!c->out.queue_len' failed.
  It is described on:
  http://lists.freedesktop.org/archives/xcb/2013-December/009027.html
  Please release upgrade to 1.11 version which as far as I know fixed this 
issues for Ubuntu 15.04.

  Kubuntu 15.04

  libxcb1:
Zainstalowana: 1.10-2ubuntu1
Kandydująca:   1.10-2ubuntu1
Tabela wersji:
   *** 1.10-2ubuntu1 0
  500 http://pl.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1486456] Re: Please set back libvpx1 into Wily archive

** Changed in: libvpx (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Please set back libvpx1 into Wily archive

Status in libvpx package in Ubuntu:
  Invalid

Bug description:
  Wanting to install virtualbox 5.0 from  virtualbox.org, as the wily
  archive one (5.02-dfsg-2) has a vboxpci iommu issue.

  but i require libvpx1 to install (and no more available into Wily archive)
  https://launchpad.net/ubuntu/+source/libvpx

  virtualbox-5.0:
   Depends: libvpx1 (>=1.0.0) but it is not installable

  Error with the Wily package:
  dmesg | grep -i iommu
  [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-4-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on
  [0.00] DMAR: IOMMU enabled
  [   32.662814] vboxpci: IOMMU not found (not registered)

  (this is a test with intel_iommu=on kernel parameter, but without i
  get the same result. So i need the version from virtualbox.org)

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

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

[Desktop-packages] [Bug 1429535] Re: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

** Tags removed: vivid
** Tags added: yakkety

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

Title:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

Status in nautilus package in Ubuntu:
  New

Bug description:
  Get that error from journalctl

  org.gnome.Nautilus[1518]: ** (nautilus:3572): CRITICAL **:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

  https://developer.gnome.org/libnautilus-extension/stable/libnautilus-
  extension-nautilus-menu-provider.html

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Mar  8 09:35:05 2015
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  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/1429535/+subscriptions

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

[Desktop-packages] [Bug 1389582] Re: software-center misses a dependency on libgtk2-perl

** Tags removed: vivid wily

** Tags removed: xenial

** Tags added: xenial

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

Title:
  software-center misses a dependency on libgtk2-perl

Status in One Hundred Papercuts:
  Triaged
Status in software-center package in Ubuntu:
  Triaged

Bug description:
  Step to reproduce:
try to install package with debconf wizard (in my case, via double click on 
third-party Debian package)

  Current result:
   After long time installation fails.

  Expected:
   Dialog is appear and a instalation is succesful. 

  
  Workaround is to use just command line or install libgtk2-perl and then the 
installation via software-centrum doesn't fail.

  
  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  
  Logs:

  debconf: unable to initialize frontend: Gnome
  debconf: (Can't locate Gtk2.pm in @INC (you may need to install the Gtk2 
module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 
/usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 
/usr/share/perl/5.18 /usr/local/lib/site_perl .) at 
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 91.)
  debconf: falling back to frontend: Dialog
  Killed

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

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

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-09-15 Thread Pat McGowan

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

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

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

[Desktop-packages] [Bug 270744] Re: GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

That error should be gone now

** Changed in: rhythmbox (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT
  (object)' failed

Status in network-manager package in Ubuntu:
  Incomplete
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: network-manager

  When starting NM,  the following is spammed to the console.

  GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT
  (object)' failed

  amelo@amelo-laptop:~$ dpkg --list | grep network | grep manager
  ii  network-manager
0.7~~svn20080908t183521+eni0-0ubuntu2 network management framework daemon
  ii  network-manager-gnome  
0.7~~svn20080907t033843-0ubuntu2  network management framework (GNOME 
frontend
  ii  network-manager-openvpn
0.7~~svn20080908t183521a-0ubuntu2 network management framework (OpenVPN 
plugin

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

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

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

The attached debdiffs lp1609898-nm-[trusty|xenial|yakkety].debdiff patch
network-manager's debian/tests/wpa-dhclient test to use /128 instead of
/64 for its DHCPv6 address test.

Note it leaves the ipv6 Router Advertisement provided addresses with
/64, as that prefix length is provided to the client (unlike DHCPv6) in
the RA messages.

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  New
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  New
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

** Patch added: "lp1609898-nm-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741543/+files/lp1609898-nm-yakkety.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  New
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  New
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Desktop-packages] [Bug 1559895] Re: E: Internal Error, No file name for libgl1-mesa-glx:amd64

no more a problem

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

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

Title:
  E: Internal Error, No file name for libgl1-mesa-glx:amd64

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  With the latest mesa upgrade i get that error:

  E: Internal Error, No file name for libgl1-mesa-glx:amd64

  
  reproducible if libgl1-mesa-glx is reinstalled

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-glx 11.1.2-1ubuntu2
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.28  Wed Feb  3 15:48:04 
PST 2016
   GCC version:  gcc version 5.3.1 20160311 (Ubuntu 5.3.1-11ubuntu1)
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 21 08:36:28 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750] [1458:362e]
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC
  version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Mar 21 06:16:44 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Laser Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

** Patch added: "lp1609898-nm-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741542/+files/lp1609898-nm-xenial.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  New
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  New
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

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

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

** Patch added: "debdiff to fix network manager test in trusty"
   
https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741541/+files/lp1609898-nm-trusty.debdiff

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  New
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  New
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Desktop-packages] [Bug 1624055] [NEW] Dell i5779 - Sound only comes out of subwoofer. Speaker sound tests do not produce any sound for any speaker

2016-09-15 Thread Tom Ester

Public bug reported:

Kubuntu 16.04 amd64
Dell i7559

* Skylake PCIe controller
* Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
* aplay --list-devices
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 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

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
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   htmler 1526 F...m pulseaudio
 /dev/snd/controlC0:  htmler 1526 F pulseaudio
CurrentDesktop: X-Cinnamon
Date: Thu Sep 15 13:25:49 2016
InstallationDate: Installed on 2016-09-12 (3 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AudioUsers: pulse
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   htmler 1526 F...m pulseaudio
 /dev/snd/controlC0:  htmler 1526 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Sound works for some users but not for others
Title: [HDA-Intel - HDA Intel PCH, playback] sound not working for all users
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.8
dmi.board.name: 0H87XC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7559
dmi.product.version: 1.1.8
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-14T20:51:48.758875

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

Title:
  Dell i5779 - Sound only comes out of subwoofer. Speaker sound tests do
  not produce any sound for any speaker

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Kubuntu 16.04 amd64
  Dell i7559

  * Skylake PCIe controller
  * Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
  * aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 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

  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
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   htmler 1526 F...m pulseaudio
   /dev/snd/controlC0:  htmler 1526 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Sep 15 13:25:49 2016
  InstallationDate: Installed on 2016-09-12 (3 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AudioUsers: pulse
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   htmler 1526 F...m pulseaudio
   /dev/snd/controlC0:  htmler 1526 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Sound works for some users but not for others
  Title: [HDA-Intel - HDA Intel PCH, playback] sound not working for all users
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.

[Desktop-packages] [Bug 1576092] Re: libgl1-mesa-dri

is that issue still exist ?

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

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

Title:
  libgl1-mesa-dri

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Everytime I try to start Sweethome 3D, the interface appear and then
  directly crashes !

  When I launch it in Terminal, I get this :

  Java 3D: implicit antialiasing enabled
  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f70066de823, pid=1667, tid=140119133419264
  #
  # JRE version: OpenJDK Runtime Environment (8.0_03-b03) (build 
1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
  # Java VM: OpenJDK 64-Bit Server VM (25.03-b03 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [radeonsi_dri.so+0x256823]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # An error report file with more information is saved as:
  # /tmp/hs_err_pid1667.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.java.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #
  Aborted (core dumped)

  As mentionned, radeonsi-dri.so may have a problem. It's an important
  bug, as we can't install the proprietary fglrx drivers on ubuntu
  16.04.

  my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor / 8Go 
RAM / RADEON HD 7750 (no propretary drivers installed, as they are not 
available anymore in 16.04)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE 16.04
  InstallationDate: Installed on 2016-04-25 (3 days ago)
  InstallationMedia: neon 16.04 "Xenial" - Build amd64 LIVE Binary 
20160419-23:13
  Package: sweethome3d 4.5+dfsg-3 [origin: Ubuntu]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-21-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1624033] Re: unity issue

2016-09-15 Thread Paul White

How and why did you reset Unity?

Have you tired to reinstall Unity from a tty with "sudo apt install
unity --reinstall"  ?

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

Title:
  unity issue

Status in unity package in Ubuntu:
  New

Bug description:
  I tried to reset unity and remove all xauthority things. But after
  login there is no menubar, no launcher, nothing. only file , go etc
  menu at left bar and no minimize, maximize button at application
  window.

  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:
   [[0;32m  OK  [0m] Started Network Manager Wait Online.
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 15 22:00:41 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80dd]
  InstallationDate: Installed on 2016-02-21 (206 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 005: ID 22b8:2e24 Motorola PCS 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.37
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd07/25/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  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: Thu Sep 15 21:56:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14573 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

This bug was fixed in the package telephony-service -
0.1+16.10.20160909.1-0ubuntu1

---
telephony-service (0.1+16.10.20160909.1-0ubuntu1) yakkety; urgency=medium

  [ Tiago Salem Herrmann ]
  * Fix test failure with new libphonenumber release.
  * Move telepathy-ofono from "Depends" to "Suggests".

 -- Gustavo Pichorim Boiko   Fri, 09 Sep
2016 14:54:02 +

** Changed in: telephony-service (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

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

-- 
Mailing list: https://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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-15 Thread magic8east

I'll try and run a log-file capture when I have some time. The problem
occurs for me with both headphones in either front ports on the case,
directly to the rear motherboard ports, and with the sound NOT via
headphones to my monitor. It does seem to pop up more frequently with
headphones connected though.

On 15 September 2016 at 16:32, bpowell  wrote:

> I should note: During that log-file capture, all I did was start the
> capture, and then briefly check the internet...I did NOT plug or unplug
> anything during that capture. So any "Front Jack plugged in" messages are
> not accurate.
>
>
> On Thu, Sep 15, 2016 at 2:13 AM, Sebastien Bacher 
> wrote:
>
> > One of the log are regular events like this
> >
> > "Jack 'Front Headphone Jack' is now plugged in"
> >
> > Luke, do you see from the log what's going on exactly?
> >
> > ** Changed in: pulseaudio (Ubuntu)
> >Status: Incomplete => Confirmed
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1585084
> >
> > Title:
> >   Volume notification keeps popping up constantly(the notifyosd bubble
> >   on top-right corner)
> >
> > Status in pulseaudio package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
> >   preserving the home directory which is mounted in a separate
> >   partition. Even during the installation I had constant volume
> >   notification bubble appearing on the top-right corner of my screen, it
> >   would come and go about twice every minute. I just thought it was due
> >   to installing hardware drivers or something but the problem persisted
> >   even when I booted into the freshly installed system. I did some
> >   searching and two users reported the exact problem. And one more
> >   suggested this happens because constant disconnect and reconnect of
> >   the sound card which makes sense as the sound settings flashes briefly
> >   during every popup. Someone on IRC suggested to kill pulseaudio and
> >   thus restart it, that does not fix the issue. I also tried the Live
> >   environment thinking it might be due to some old config files in home
> >   partition (which was preserved during upgrade), but this problem
> >   happens in the live environment as well, which makes sense because it
> >   was present during installation as well.
> >
> >   Users with the same issue:
> >   http://ubuntuforums.org/showthread.php?t=2323815
> >   http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
> >   http://askubuntu.com/questions/767466/sound-card-being-disconnected-
> > reconnected-constantly
> >
> >   Thanks.
> >
> >   ProblemType: Bug
> >   DistroRelease: Ubuntu 16.04
> >   Package: pulseaudio 1:8.0-0ubuntu3
> >   ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
> >   Uname: Linux 4.4.0-22-generic x86_64
> >   ApportVersion: 2.20.1-0ubuntu2
> >   Architecture: amd64
> >   AudioDevicesInUse:
> >USERPID ACCESS COMMAND
> >/dev/snd/controlC2:  sidd   1651 F pulseaudio
> >/dev/snd/controlC0:  sidd   1651 F pulseaudio
> >/dev/snd/controlC1:  sidd   1651 F pulseaudio
> >   CurrentDesktop: Unity
> >   Date: Tue May 24 12:31:12 2016
> >   InstallationDate: Installed on 2016-05-23 (0 days ago)
> >   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> > (20160420.1)
> >   SourcePackage: pulseaudio
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >   dmi.bios.date: 08/23/2011
> >   dmi.bios.vendor: American Megatrends Inc.
> >   dmi.bios.version: 0705
> >   dmi.board.asset.tag: To be filled by O.E.M.
> >   dmi.board.name: M5A97 EVO
> >   dmi.board.vendor: ASUSTeK Computer INC.
> >   dmi.board.version: Rev 1.xx
> >   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.:bvr0705:bd08/23/2011:
> > svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:
> > rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:
> > cvrToBeFilledByO.E.M.:
> >   dmi.product.name: To be filled by O.E.M.
> >   dmi.product.version: To be filled by O.E.M.
> >   dmi.sys.vendor: To be filled by O.E.M.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+
> > bug/1585084/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1585084
>
> Title:
>   Volume notification keeps popping up constantly(the notifyosd bubble
>   on top-right corner)
>
> Status in pulseaudio package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
>   preserving the home directory which is mounted in

[Desktop-packages] [Bug 1579531] Re: xbrlapi debugging message spamming .xsession-errors; please silence it.

xbrlapi 5.4 on yakkety seems clean now; nothing logged into xsession-
errors.

** Tags removed: yakkety

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

Title:
  xbrlapi debugging message spamming .xsession-errors; please silence
  it.

Status in brltty package in Ubuntu:
  Confirmed

Bug description:
  16.04 amd64.

  $HOME/.xsession-errors contains cryptic messages that do not indicate
  where they come from. They turn out to be harmless but it would be
  good if they at least were prefixed with the source.

  openConnection: connect: No such file or directory
  cannot connect to brltty at :0

  They indicate the absence of a braille tty so how about:

  xbrlapi: Cannot find a Braille Teletype device
  xbrlapi: cannot connect to brltty at :0

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

-- 
Mailing list: https://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 1623254] Re: Base: trying to set limits in queries gives an 'unexpected token' error

2016-09-15 Thread Matteo Paolini

To reproduce the bug:

1) Create a new query in design mode and add a table

2) add either all or some fields to the query by double clicking on the 
list of fields that has appeared

3) set a limit to how many records should be displayed, either by 
entering a value manually in the box at the top that says "All" or by 
selecting a suggested value from the dropdown menu beside said box

4) run the query by pressing f5

normally it should display the records from the selected table equal to 
the value that I set previously, but instead I get an "unexpected token" 
error.


On 15/09/16 06:13, Christopher M. Penalver wrote:
> Matteo Paolini, thank you for reporting this and helping make Ubuntu
> better.
>
> 1) Could you please provide an example Base file?
> 2) Could you please provide a keyboard click-for-click of how to reproduce?
> 3) Could you please provide a screenshot of the error?
>
> ** Changed in: libreoffice (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: libreoffice (Ubuntu)
> Status: New => Incomplete
>


** Attachment added: "odb29-Count and Group.odb"
   
https://bugs.launchpad.net/bugs/1623254/+attachment/4741512/+files/odb29-Count%20and%20Group.odb

** Attachment added: "Screenshot from 2016-09-15 11-29-38.png"
   
https://bugs.launchpad.net/bugs/1623254/+attachment/4741513/+files/Screenshot%20from%202016-09-15%2011-29-38.png

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

Title:
  Base: trying to set limits in queries gives an 'unexpected token'
  error

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When I'm trying to set a limit in a query about how many records it
  should display I get an 'unexpected token' error, whether I input the
  value manually or choose it from the dropdown menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.4-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Tue Sep 13 17:40:45 2016
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-06-14 (91 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1624033] Re: unity issue

2016-09-15 Thread Anupam Datta

I tried with resetting everything but nothing worked, and I got this
suddnely and first time

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

Title:
  unity issue

Status in xorg package in Ubuntu:
  New

Bug description:
  I tried to reset unity and remove all xauthority things. But after
  login there is no menubar, no launcher, nothing. only file , go etc
  menu at left bar and no minimize, maximize button at application
  window.

  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:
   [[0;32m  OK  [0m] Started Network Manager Wait Online.
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 15 22:00:41 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80dd]
  InstallationDate: Installed on 2016-02-21 (206 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 005: ID 22b8:2e24 Motorola PCS 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.37
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd07/25/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  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: Thu Sep 15 21:56:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14573 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Desktop-packages] [Bug 1624033] [NEW] unity issue

2016-09-15 Thread Anupam Datta

Public bug reported:

I tried to reset unity and remove all xauthority things. But after login
there is no menubar, no launcher, nothing. only file , go etc menu at
left bar and no minimize, maximize button at application window.

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:
 [[0;32m  OK  [0m] Started Network Manager Wait Online.
 [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Sep 15 22:00:41 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80dd]
InstallationDate: Installed on 2016-02-21 (206 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 8087:07dc Intel Corp. 
 Bus 001 Device 005: ID 22b8:2e24 Motorola PCS 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.37
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd07/25/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard
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: Thu Sep 15 21:56:55 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14573 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  unity issue

Status in xorg package in Ubuntu:
  New

Bug description:
  I tried to reset unity and remove all xauthority things. But after
  login there is no menubar, no launcher, nothing. only file , go etc
  menu at left bar and no minimize, maximize button at application
  window.

  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:
   [[0;32m  OK  [0m] Started Network Manager Wait Online.
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 15 22:00:41 2016

[Desktop-packages] [Bug 1593611] Re: flashplugin-installer: Can't drop priviledges for downloading as file Warning

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

This is not a "flashplugin" issue as it happens randomly with some other
packages when a script validate an upgrade. that one has not been
updated to support the new apt design "'_apt'"

The real problem is : there is _apt user on the system

grep -B2 _apt /var/lib/dpkg/info/apt.postinst

# add unprivileged user for the apt methods
adduser --force-badname --system --home /nonexistent  \
--no-create-home --quiet _apt || true

# Fixup any mistake in the home directory of the _apt user
if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then
usermod --home /nonexistent _apt


** Changed in: flashplugin-nonfree (Ubuntu)
   Status: Confirmed => Invalid

** This bug has been marked a duplicate of bug 1522675
   Can't drop privileges for downloading : _apt user not created

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

Title:
  flashplugin-installer: Can't drop priviledges for downloading as file
  Warning

Status in One Hundred Papercuts:
  Confirmed
Status in flashplugin-nonfree package in Ubuntu:
  Invalid

Bug description:
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160616.1.orig.tar.gz
  Get:1 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160616.1.orig.tar.gz
 [27,1 MB]
  Fetched 27,1 MB in 8s (3.125 kB/s)


  W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160616.1.orig.tar.gz'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
  Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160616.1.orig.tar.gz
  Flash Plugin installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: flashplugin-installer 11.2.202.626ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 17 09:50:33 2016
  InstallationDate: Installed on 2016-04-26 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: flashplugin-nonfree
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1621210] Re: [MIR] fonts-android

2016-09-15 Thread Michael Terry

So we don't need this?  Will mark invalid.

** Changed in: fonts-android (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Invalid
Status in ghostscript package in Ubuntu:
  In Progress

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

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

[Desktop-packages] [Bug 1624018] [NEW] emacs segfaults when run under X (but not in console)

2016-09-15 Thread Ivan Zakharyaschev

Public bug reported:

$ emacs
Fatal error 11: Segmentation fault
Backtrace:
emacs[0x4f74cb]
emacs[0x4dcf3e]
emacs[0x4f611e]
emacs[0x4f6283]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7ffbb9c38330]
emacs[0x46f9e2]
emacs[0x5b5abe]
emacs[0x54fe5e]
emacs[0x58494b]
emacs[0x54fa0f]
emacs[0x54ee2d]
emacs[0x54f1f2]
emacs[0x552511]
emacs[0x5854f8]
emacs[0x54fa0f]
emacs[0x54fd1b]
emacs[0x58494b]
emacs[0x54fa0f]
emacs[0x54fd1b]
emacs[0x58494b]
emacs[0x54fd1b]
emacs[0x54f5a3]
emacs[0x552511]
emacs[0x5854f8]
emacs[0x54fd1b]
emacs[0x58494b]
emacs[0x54ee2d]
emacs[0x54f1f2]
emacs[0x5525fd]
emacs[0x54e3e3]
emacs[0x4dd446]
emacs[0x54e2be]
emacs[0x4e1bff]
emacs[0x4e1f14]
emacs[0x4171d5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7ffbb9884f45]
emacs[0x417cee]
Ошибка сегментирования (сделан дамп памяти)
$ dpkg -l emacs\*
Желаемый=неизвестно[u]/установить[i]/удалить[r]/вычистить[p]/зафиксировать[h]
| Состояние=не[n]/установлен[i]/настроен[c]/распакован[U]/частично настроен[F]/
частично установлен[H]/trig-aWait/Trig-pend
|/ Ошибка?=(нет)/требуется переустановка[R] (верхний регистр
в полях состояния и ошибки указывает на ненормальную ситуацию)
||/ Имя   Версия  Архитектура 
Описание
+++-=-===-===-
ii  emacs 45.0ubuntu1 all GNU 
Emacs editor (metapackage)
un  emacs22-common<нет>   <нет>   
(описание недоступно)
ii  emacs24   24.3+1-2ubuntu1 amd64   GNU 
Emacs editor (with GTK+ user interface)
ii  emacs24-bin-common24.3+1-2ubuntu1 amd64   GNU 
Emacs editor's shared, architecture dependent files
ii  emacs24-common24.3+1-2ubuntu1 all GNU 
Emacs editor's shared, architecture independent infrastructu
ii  emacs24-common-non-dfsg   24.3+1-1all GNU 
Emacs common non-DFSG items, including the core documentatio
ii  emacs24-dbg   24.3+1-2ubuntu1 amd64   
Debugging symbols for emacs24
un  emacs24-el<нет>   <нет>   
(описание недоступно)
un  emacs24-lucid <нет>   <нет>   
(описание недоступно)
un  emacs24-nox   <нет>   <нет>   
(описание недоступно)
un  emacsen   <нет>   <нет>   
(описание недоступно)
ii  emacsen-common2.0.7   all 
Common facilities for all emacsen
$ emacs --version
GNU Emacs 24.3.1
Copyright (C) 2013 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
$

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: emacs 45.0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 15 18:49:24 2016
InstallationDate: Installed on 2015-09-05 (375 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: emacs-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Package changed: emacs-defaults (Ubuntu) => emacs24 (Ubuntu)

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

Title:
  emacs segfaults when run under X (but not in console)

Status in emacs24 package in Ubuntu:
  New

Bug description:
  $ emacs
  Fatal error 11: Segmentation fault
  Backtrace:
  emacs[0x4f74cb]
  emacs[0x4dcf3e]
  emacs[0x4f611e]
  emacs[0x4f6283]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7ffbb9c38330]
  emacs[0x46f9e2]
  emacs[0x5b5abe]
  emacs[0x54fe5e]
  emacs[0x58494b]
  emacs[0x54fa0f]
  emacs[0x54ee2d]
  emacs[0x54f1f2]
  emacs[0x552511]
  emacs[0x5854f8]
  emacs[0x54fa0f]
  emacs[0x54fd1b]
  emacs[0x58494b]
  emacs[0x54fa0f]
  emacs[0x54fd1b]
  emacs[0x58494b]
  emacs[0x54fd1b]
  emacs[0x54f5a3]
  emacs[0x552511]
  emacs[0x5854f8]
  emacs[0x54fd1b]
  emacs[0x58494b]
  emacs[0x54ee2d]
  emacs[0x54f1f2]
  emacs[0x5525fd]
  emacs[0x54e3e3]
  emacs[0x4dd446]
  emacs[0x54e2be]
  emacs[0x4e1bff]
  emacs[0x4e1f14]
  emacs[0x4171d5]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7ffbb9884f45]
  emacs[0x417cee]
  Ошибка сегментирования (сделан дамп памяти)
  $ dpkg -l emacs\*

[Desktop-packages] [Bug 1538111] Re: untraceable serious bug in metacity 3.18

2016-09-15 Thread Alberts Muktupāvels

At this point only valid bug here might be / is problem when all windows
are hidden under desktop (?) window... I doubt that this is problem with
configuration.

** Changed in: metacity (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  untraceable serious bug in metacity 3.18

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS uses 3.18 version of gnome metacity.

  When doing lots of mess work in Desktop (such as open desktop window,
  sudo window, dragging window, and so on), "!! WHEN CLICKING CLOSE
  BUTTON OF A CERTAIN WINDOW !!", there is "small possibility" for
  metacity to get out of work --> Many windows are disappeared, with
  only nautilus desktop background and gnome-panel on screen. "Live
  Window List" still exists in gnome-panel, but no matter doing what
  (such as open new application from gnome-menu or use Alt+Tab to switch
  window), none of live windows can be displayed.

  So the only way is to switch to tty1 using Ctrl+Alt+F1, and executing
  "DISPLAY=:0 metacity -c --replace", then all windows came back.

  Till now, I meet this bug every day, but still not sure how to
  reproduce it bug. I think you should trace what the metacity do when
  clicking "close button" that makes all windows to be disappeared.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Jan 26 19:49:48 2016
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-15 Thread Yura Nosenko

Joakim, I listed everything I have installed 2 messages back. All your 7
debs seems to be included. Plus 32bit libpulse. I can try to reinstall
them today.

-- 
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 1624018] [NEW] emacs segfaults when run under X (but not in console)

You have been subscribed to a public bug:

$ emacs
Fatal error 11: Segmentation fault
Backtrace:
emacs[0x4f74cb]
emacs[0x4dcf3e]
emacs[0x4f611e]
emacs[0x4f6283]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7ffbb9c38330]
emacs[0x46f9e2]
emacs[0x5b5abe]
emacs[0x54fe5e]
emacs[0x58494b]
emacs[0x54fa0f]
emacs[0x54ee2d]
emacs[0x54f1f2]
emacs[0x552511]
emacs[0x5854f8]
emacs[0x54fa0f]
emacs[0x54fd1b]
emacs[0x58494b]
emacs[0x54fa0f]
emacs[0x54fd1b]
emacs[0x58494b]
emacs[0x54fd1b]
emacs[0x54f5a3]
emacs[0x552511]
emacs[0x5854f8]
emacs[0x54fd1b]
emacs[0x58494b]
emacs[0x54ee2d]
emacs[0x54f1f2]
emacs[0x5525fd]
emacs[0x54e3e3]
emacs[0x4dd446]
emacs[0x54e2be]
emacs[0x4e1bff]
emacs[0x4e1f14]
emacs[0x4171d5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7ffbb9884f45]
emacs[0x417cee]
Ошибка сегментирования (сделан дамп памяти)
$ dpkg -l emacs\*
Желаемый=неизвестно[u]/установить[i]/удалить[r]/вычистить[p]/зафиксировать[h]
| Состояние=не[n]/установлен[i]/настроен[c]/распакован[U]/частично настроен[F]/
частично установлен[H]/trig-aWait/Trig-pend
|/ Ошибка?=(нет)/требуется переустановка[R] (верхний регистр
в полях состояния и ошибки указывает на ненормальную ситуацию)
||/ Имя   Версия  Архитектура 
Описание
+++-=-===-===-
ii  emacs 45.0ubuntu1 all GNU 
Emacs editor (metapackage)
un  emacs22-common<нет>   <нет>   
(описание недоступно)
ii  emacs24   24.3+1-2ubuntu1 amd64   GNU 
Emacs editor (with GTK+ user interface)
ii  emacs24-bin-common24.3+1-2ubuntu1 amd64   GNU 
Emacs editor's shared, architecture dependent files
ii  emacs24-common24.3+1-2ubuntu1 all GNU 
Emacs editor's shared, architecture independent infrastructu
ii  emacs24-common-non-dfsg   24.3+1-1all GNU 
Emacs common non-DFSG items, including the core documentatio
ii  emacs24-dbg   24.3+1-2ubuntu1 amd64   
Debugging symbols for emacs24
un  emacs24-el<нет>   <нет>   
(описание недоступно)
un  emacs24-lucid <нет>   <нет>   
(описание недоступно)
un  emacs24-nox   <нет>   <нет>   
(описание недоступно)
un  emacsen   <нет>   <нет>   
(описание недоступно)
ii  emacsen-common2.0.7   all 
Common facilities for all emacsen
$ emacs --version
GNU Emacs 24.3.1
Copyright (C) 2013 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
$

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: emacs 45.0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 15 18:49:24 2016
InstallationDate: Installed on 2015-09-05 (375 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: emacs-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty
-- 
emacs segfaults when run under X (but not in console)
https://bugs.launchpad.net/bugs/1624018
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to emacs24 in Ubuntu.

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

[Desktop-packages] [Bug 1621210] Re: [MIR] fonts-android

Uploaded. Thanks.

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Incomplete
Status in ghostscript package in Ubuntu:
  In Progress

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

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

-- 
Mailing list: https://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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-15 Thread bpowell

I should note: During that log-file capture, all I did was start the
capture, and then briefly check the internet...I did NOT plug or unplug
anything during that capture. So any "Front Jack plugged in" messages are
not accurate.


On Thu, Sep 15, 2016 at 2:13 AM, Sebastien Bacher  wrote:

> One of the log are regular events like this
>
> "Jack 'Front Headphone Jack' is now plugged in"
>
> Luke, do you see from the log what's going on exactly?
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: Incomplete => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1585084
>
> Title:
>   Volume notification keeps popping up constantly(the notifyosd bubble
>   on top-right corner)
>
> Status in pulseaudio package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
>   preserving the home directory which is mounted in a separate
>   partition. Even during the installation I had constant volume
>   notification bubble appearing on the top-right corner of my screen, it
>   would come and go about twice every minute. I just thought it was due
>   to installing hardware drivers or something but the problem persisted
>   even when I booted into the freshly installed system. I did some
>   searching and two users reported the exact problem. And one more
>   suggested this happens because constant disconnect and reconnect of
>   the sound card which makes sense as the sound settings flashes briefly
>   during every popup. Someone on IRC suggested to kill pulseaudio and
>   thus restart it, that does not fix the issue. I also tried the Live
>   environment thinking it might be due to some old config files in home
>   partition (which was preserved during upgrade), but this problem
>   happens in the live environment as well, which makes sense because it
>   was present during installation as well.
>
>   Users with the same issue:
>   http://ubuntuforums.org/showthread.php?t=2323815
>   http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
>   http://askubuntu.com/questions/767466/sound-card-being-disconnected-
> reconnected-constantly
>
>   Thanks.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: pulseaudio 1:8.0-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC2:  sidd   1651 F pulseaudio
>/dev/snd/controlC0:  sidd   1651 F pulseaudio
>/dev/snd/controlC1:  sidd   1651 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Tue May 24 12:31:12 2016
>   InstallationDate: Installed on 2016-05-23 (0 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   SourcePackage: pulseaudio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/23/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 0705
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: M5A97 EVO
>   dmi.board.vendor: ASUSTeK Computer INC.
>   dmi.board.version: Rev 1.xx
>   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.:bvr0705:bd08/23/2011:
> svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:
> rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:
> cvrToBeFilledByO.E.M.:
>   dmi.product.name: To be filled by O.E.M.
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: To be filled by O.E.M.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+
> bug/1585084/+subscriptions
>

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

Title:
  Volume notification keeps popping up constantly(the notifyosd bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings

[Desktop-packages] [Bug 1538111] Re: untraceable serious bug in metacity 3.18

@dronus

check with some genuine config, to know if that still exist:
- purge compiz
- purge metacity
- set default theme (adwaita for ubuntu, does not know for others) via the 
tweak tool

- reinstall compiz (only the default ubuntu choice; no ccsm nor other plugins 
which are mainly not maintained since ages)
- reinstall metacity

- then logout and reboot;

note: set to "incomplete" as its not your report, and the OP has not
answered to #83

** Changed in: metacity (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  untraceable serious bug in metacity 3.18

Status in metacity package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS uses 3.18 version of gnome metacity.

  When doing lots of mess work in Desktop (such as open desktop window,
  sudo window, dragging window, and so on), "!! WHEN CLICKING CLOSE
  BUTTON OF A CERTAIN WINDOW !!", there is "small possibility" for
  metacity to get out of work --> Many windows are disappeared, with
  only nautilus desktop background and gnome-panel on screen. "Live
  Window List" still exists in gnome-panel, but no matter doing what
  (such as open new application from gnome-menu or use Alt+Tab to switch
  window), none of live windows can be displayed.

  So the only way is to switch to tty1 using Ctrl+Alt+F1, and executing
  "DISPLAY=:0 metacity -c --replace", then all windows came back.

  Till now, I meet this bug every day, but still not sure how to
  reproduce it bug. I think you should trace what the metacity do when
  clicking "close button" that makes all windows to be disappeared.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Jan 26 19:49:48 2016
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

I have Radeon HD 5970. As root I can do startx and use everything. All
has been configured correctly and Mesa OpenCL is even available. I
upgraded from xenial-proposed the next three packages too see if it
would fix it:

  liblightdm-gobject-1-0:amd641.18.3-0ubuntu1
  lightdm 1.18.3-0ubuntu1
  ubuntu-drivers-common   1:0.4.22

It did not. In /var/log/syslog I found:

Sep 15 16:57:44 ### systemd[1]: lightdm.service: Service hold-off time over, 
scheduling restart.
Sep 15 16:57:44 ### systemd[1]: Stopped Light Display Manager.
Sep 15 16:57:44 ### systemd[1]: Starting Detect the available GPUs and deal 
with any system changes...
Sep 15 16:57:44 ### gpu-manager[1950]: /etc/modprobe.d is not a file
Sep 15 16:57:44 ### gpu-manager[1950]: message repeated 4 times: [ 
/etc/modprobe.d is not a file]
Sep 15 16:57:44 ### gpu-manager[1950]: Error: can't open 
/lib/modules/4.4.0-38-generic/updates/dkms
Sep 15 16:57:44 ### gpu-manager[1950]: Error: can't open 
/lib/modules/4.4.0-38-generic/updates/dkms
Sep 15 16:57:44 ### gpu-manager[1950]: update-alternatives: error: no 
alternatives for x86_64-linux-gnu_gfxcore_conf
Sep 15 16:57:44 ### systemd[1]: Started Detect the available GPUs and deal with 
any system changes.
Sep 15 16:57:44 ### systemd[1]: Starting Light Display Manager...
Sep 15 16:57:44 ### systemd[1]: Started Light Display Manager.
Sep 15 16:57:44 ## systemd[1]: Started Session c10 of user lightdm.
Sep 15 16:57:45 ### systemd[1]: lightdm.service: Main process exited, 
code=exited, status=1/FAILURE
Sep 15 16:57:45 ### systemd[1]: lightdm.service: Unit entered failed state.
Sep 15 16:57:45 ### systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 15 16:57:45 ### systemd[1]: lightdm.service: Service hold-off time over, 
scheduling restart.
Sep 15 16:57:45 ### systemd[1]: Stopped Light Display Manager.
Sep 15 16:57:45 ### systemd[1]: gpu-manager.service: Start request repeated too 
quickly.
Sep 15 16:57:45 ### systemd[1]: Failed to start Detect the available GPUs and 
deal with any system changes.
Sep 15 16:57:45 ### systemd[1]: lightdm.service: Start request repeated too 
quickly.
Sep 15 16:57:45 ### systemd[1]: Failed to start Light Display Manager.
Sep 15 16:57:45 ### systemd[1]: Stopped Light Display Manager.
Sep 15 16:57:47 ### systemd[1]: gpu-manager.service: Start request repeated too 
quickly.
Sep 15 16:57:47 ### systemd[1]: Failed to start Detect the available GPUs and 
deal with any system changes.
Sep 15 16:57:47 ### systemd[1]: lightdm.service: Start request repeated too 
quickly.
Sep 15 16:57:47 ### systemd[1]: Failed to start Light Display Manager.
Sep 15 16:59:44 ### systemd[1]: Stopping User Manager for UID 104...

And the output of gpu-manager is:

# gpu-manager 
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
/etc/modprobe.d is not a file
can't access /run/u-d-c-fglrx-was-loaded file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
Looking for fglrx modules in /lib/modules/4.4.0-38-generic/updates/dkms
Error: can't open /lib/modules/4.4.0-38-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.4.0-38-generic/updates/dkms
Error: can't open /lib/modules/4.4.0-38-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? no
Is radeon loaded? yes
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 1002:689c
BusID "PCI:3@0:0:0"
Is boot vga? yes
Vendor/Device Id: 1002:689c
BusID "PCI:4@0:0:0"
Is boot vga? no
Skipping "/dev/dri/card1", driven by "radeon"
Skipping "/dev/dri/card0", driven by "radeon"
Found "/dev/dri/card1", driven by "radeon"
Number of connected outputs for /dev/dri/card1: 0
Skipping "/dev/dri/card1", driven by "radeon"
Skipping "/dev/dri/card0", driven by "radeon"
Skipping "/dev/dri/card1", driven by "radeon"
Skipping "/dev/dri/card0", driven by "radeon"
Does it require offloading? no
last cards number = 2
Has amd? yes
Has intel? no
Has nvidia? no
How many cards? 2
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no

Re: [Desktop-packages] [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-09-15 Thread Kyle

I updated to v16 and my pc is now unusable, though i suspect its because
i did not disable secure boot.

Sent from my HTC

- Reply message -
From: "Pander" <1369...@bugs.launchpad.net>
To: 
Subject: [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
Date: Thu, Sep 15, 2016 10:42 AM

Is there a workaround for xenial?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1369216

Title:
gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
Get these lines logged into gpu-manager.log, on that fresh stock
installation

/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart 1.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep 14 08:42:45 2014
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
modified.conffile..etc.default.whoopsie: [modified]
modified.conffile..etc.gdm.Init.Default: [modified]
mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

[Desktop-packages] [Bug 1376966] Re: gpu-manager treats all files in /etc/modprobe.d as config files

Related to https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1369216 ?

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

Title:
gpu-manager treats all files in /etc/modprobe.d as config files

Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Trusty:
Fix Released

Bug description:
My media center computer have a single nvidia GPU connected to a TV,
and have for many years been happily using the nvidia driver.
Unfortunately the recent upgrade to version 1:0.2.91.7 broke X.
Starting lightdm would fail, delete my xorg.conf and redirect libgl
symlinks to mesa.

After some debugging I fond that this was done by gpu-manager, because
it incorrectly believes that my nvidia module is blacklisted. gpu-
manager.log contained "Is nvidia blacklisted? yes".

More debugging determined that this was happening because I have a several
years old file named:
/etc/modprobe.d/blacklist.dpkg-old
which among other things contain the line "blacklist nvidia".

However that is _not_ a modprobe config file. modprobe only uses files
with a .conf extension. (See the man page modprobe.d(5)).
Unfortunately gpu-manager does not have this restriction and looks in
all files in /etc/modprobe.d by running:

grep -G "blacklist.*nvidia[[:space:]]*$" /etc/modprobe.d/*

I could work-around the bug by removing the .dpkg-old file. However this will
likely break other machines as well. I found two bugs 1373968 and 1374871 about
X not working after installing the latest update. However they does not contain
enough information to determine if they are duplicates of this bug or not.

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

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

[Desktop-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

Duplicate of https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1369216 ?

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

Title:
  /etc/modprobe.d is not a file

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

Bug description:
  /var/log/upstart# cat lightdm.log
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  Above looks weird... modprobe.d is a directory & why update-
  alternatives are called?!

  This is lightdm 1.10.5-0ubuntu1

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

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

[Desktop-packages] [Bug 1569200] Re: Error was made in a background: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

2016-09-15 Thread Leu

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

Bug affecting my installation after upgrading from 14.04. I've noticed
that before the SIGSEGV, the process tops at 100% of one of my core's
usage.

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

Title:
  Error was made in a background: gvfsd-dnssd crashed with SIGSEGV in
  avahi_service_resolver_event()

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Apr 12 09:15:44 2016
  ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd
  InstallationDate: Installed on 2016-04-02 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.4 
/org/gtk/gvfs/exec_spaw/5
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=pl
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f0e6b0e929a <__strcmp_sse2_unaligned+26>:   movdqu 
(%rdi),%xmm1
   PC (0x7f0e6b0e929a) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   avahi_service_resolver_event () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

Is there a workaround for xenial?

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

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

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

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

[Desktop-packages] [Bug 1443364] Re: gpu-manager systemd unit is not enabled

2016-09-15 Thread vgeloven

# systemctl status -l gpu-manager.service
● gpu-manager.service - Detect the available GPUs and deal with any system 
changes
   Loaded: loaded (/lib/systemd/system/gpu-manager.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) since Thu 2016-09-15 16:34:57 CEST; 3min 4s ago
  Process: 1950 ExecStart=/usr/bin/gpu-manager --log /var/log/gpu-manager.log 
(code=exited, status=0/SUCCESS)
 Main PID: 1950 (code=exited, status=0/SUCCESS)

Sep 15 16:34:57 *** gpu-manager[1950]: /etc/modprobe.d is not a file
Sep 15 16:34:57 *** gpu-manager[1950]: /etc/modprobe.d is not a file
Sep 15 16:34:57 *** gpu-manager[1950]: Error: can't open 
/lib/modules/4.4.0-38-generic/updates/dkms
Sep 15 16:34:57 *** gpu-manager[1950]: Error: can't open 
/lib/modules/4.4.0-38-generic/updates/dkms
Sep 15 16:34:57 *** gpu-manager[1950]: update-alternatives: error: no 
alternatives for x86_64-linux-gnu_gfxcore_conf
Sep 15 16:34:57 *** systemd[1]: Started Detect the available GPUs and deal with 
any system changes.
Sep 15 16:34:57 *** systemd[1]: gpu-manager.service: Start request repeated too 
quickly.
Sep 15 16:34:57 *** systemd[1]: Failed to start Detect the available GPUs and 
deal with any system changes.
Sep 15 16:35:02 *** systemd[1]: gpu-manager.service: Start request repeated too 
quickly.
Sep 15 16:35:02 *** systemd[1]: Failed to start Detect the available GPUs and 
deal with any system changes.

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

Title:
  gpu-manager systemd unit is not enabled

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  This happened with today's 15.04 image. The gpu-manager unit started,
  the xorg.conf was written, and so was the log but, somehow, even
  though the log says that the system needs offloading, no /var/lib
  /ubuntu-drivers-common/requires_offloading was created. This caused
  the system to boot into a black screen.

  Starting the same unit after (the failure to) boot, resulted in the
  correct creation of  /var/lib/ubuntu-drivers-
  common/requires_offloading . There is probably something weird going
  on in the systemd unit, as gpu-manager has never behaved like this
  with Upstart.

  This breaks hybrid graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-drivers-common 1:0.4.4
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 13 12:38:53 2015
  InstallationDate: Installed on 2015-04-13 (0 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150413)
  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/1443364/+subscriptions

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

[Desktop-packages] [Bug 1538111] Re: untraceable serious bug in metacity 3.18

2016-09-15 Thread dronus

While this bug don't happen very often to me, it behaves exactly as
described.

Some clarifications:

-It is not linked to Nvidia graphics, but happens on Intel too.

-It is definetely about graphical window depth order. The "hidden"
applications can be focused and work as expected. They even change the
mouse cursor according to their actions. They are just obscured by the
nautlilus or nemo desktop.

-If nautilus or nemo is killed, all other applications reappear, until
nautlilus or nemo is run again, in which case they are obscured again.
This can be repeated reliable after the bug once triggered.

-If metacity is restarted, the bug is gone until it is triggered again
by unknown reason. Trigger is likely the apperance of a new window (I
had the bug triggered on the failing appearance of some delete
verification request dialog).

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

Title:
  untraceable serious bug in metacity 3.18

Status in metacity package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 16.04 LTS uses 3.18 version of gnome metacity.

  When doing lots of mess work in Desktop (such as open desktop window,
  sudo window, dragging window, and so on), "!! WHEN CLICKING CLOSE
  BUTTON OF A CERTAIN WINDOW !!", there is "small possibility" for
  metacity to get out of work --> Many windows are disappeared, with
  only nautilus desktop background and gnome-panel on screen. "Live
  Window List" still exists in gnome-panel, but no matter doing what
  (such as open new application from gnome-menu or use Alt+Tab to switch
  window), none of live windows can be displayed.

  So the only way is to switch to tty1 using Ctrl+Alt+F1, and executing
  "DISPLAY=:0 metacity -c --replace", then all windows came back.

  Till now, I meet this bug every day, but still not sure how to
  reproduce it bug. I think you should trace what the metacity do when
  clicking "close button" that makes all windows to be disappeared.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Jan 26 19:49:48 2016
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1593611] Re: flashplugin-installer: Can't drop priviledges for downloading as file Warning

2016-09-15 Thread tt8811

This is still appearing -- saw it again this morning.

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

Title:
  flashplugin-installer: Can't drop priviledges for downloading as file
  Warning

Status in One Hundred Papercuts:
  Confirmed
Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160616.1.orig.tar.gz
  Get:1 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160616.1.orig.tar.gz
 [27,1 MB]
  Fetched 27,1 MB in 8s (3.125 kB/s)


  W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160616.1.orig.tar.gz'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
  Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160616.1.orig.tar.gz
  Flash Plugin installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: flashplugin-installer 11.2.202.626ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 17 09:50:33 2016
  InstallationDate: Installed on 2016-04-26 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: flashplugin-nonfree
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1623969] [NEW] Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-09-15 Thread Alan Robertson

Public bug reported:

I just took some updates to a number of graphic libraries on 16.04, and
now I can't login to kubuntu. The symptom is that it takes my password
on the greeter screen, but never updates the screen after that.

The messages include these possibly related kernel messages:
kernel: [ 701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
kernel: [ 701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* 
CPU pipe B FIFO underrun

I'm currently running kernel 4.4.0-36.

Here are my most recent updates. The problem started after I rebooted.
Of course that was the next time I logged in too...

Start-Date: 2016-09-07 08:46:04
Commandline: /usr/bin/unattended-upgrade
Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
End-Date: 2016-09-07 08:48:13

Start-Date: 2016-09-07 16:42:27
Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.274
 3.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
End-Date: 2016-09-07 16:44:34

Start-Date: 2016-09-12 14:31:39
Commandline: /usr/sbin/synaptic
Requested-By: alanr (1000)
Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), 
accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
End-Date: 2016-09-12 14:32:17


It was after rebooting after updates that this occurred. My workaround is "rm 
-fr ~/.kde" - and that allows me to log in. I'm crippled, but at least I can 
log in...

If I try to log in again without doing this, the problem recurs. This
happens even if I just log in and log back out, and try to log in again.

However, I may just found a better workaround - press ALT-CTRL-F1 then
ALT-CTRL-F7, and then the next chunk of the login sequence occurs.

This makes it consistent with an issue reported in AskUbuntu
http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen-
hangs

And it's possibly related to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779 - because
of the CPU underrun being apparently related to graphics.

In fact, each time I do this, I get a little further in the login
sequence. It appears that the trigger for this bug is likely the prompts
to provide passwords for my various ssh private keys (I have four). This
also includes prompts from the KDE wallet manager for me to use the KDE
wallet - and I don't use that feature.

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
ApportVersion: 2.20.1-0ubuntu2.1

[Desktop-packages] [Bug 1620934] Re: [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-15 Thread Timo Aaltonen

so, will you fix mir soon or should I revert that mesa commit for now?

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

Title:
  [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any
  more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

-- 
Mailing list: https://launchpad.net/~desktop-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-15 Thread Joakim Koed

Btw. maybe Eyal Zekaria can help you? I think he solved it with my
patches and skype.

-- 
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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-15 Thread Joakim Koed

Yura, could you try to install all my packages again? Maybe you are
missing something?

Remember to run: sudo dpkg -i *.deb  in the folder you extracted them
in.

You could apt search for all these, to make sure you have installed them
all:

libpulse0_8.0-0ubuntu3-vooze_amd64.deb
libpulsedsp_8.0-0ubuntu3-vooze_amd64.deb
libpulse-mainloop-glib0_8.0-0ubuntu3-vooze_amd64.deb
pulseaudio_8.0-0ubuntu3-vooze_amd64.deb
pulseaudio-module-bluetooth_8.0-0ubuntu3-vooze_amd64.deb
pulseaudio-module-x11_8.0-0ubuntu3-vooze_amd64.deb
pulseaudio-utils_8.0-0ubuntu3-vooze_amd64.deb

I'm not sure 100% exactly which 32bits you will need, maybe someone with
skype or something can check that :)

-- 
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 1526529] Re: akonadi 4:15.08.2-0ubuntu1 fails to read updates from IMAP server, reporting "log_kimap: Socket timeout!"