[Desktop-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

[Klaus Kudielka]

As a temporary work-around on my ubuntu machine, I added the following
line to /lib/systemd/system/NetworkManager.service in the [Service]
section:

ExecStartPre=-/bin/sh -c 'rm -f
/var/lib/NetworkManager/dhclient6-*.lease'

Now I get DHCPv6 leases again, even if my machine was powered off for some time.
This probably doesn't work for suspend/resume, but is better than nothing.

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

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

[Desktop-packages] [Bug 1642146] [NEW] not recognize Cyrillic characters

[Александр]

Public bug reported:

not recognize Cyrillic characters

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 16 11:24:22 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2015-08-27 (446 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (28 days ago)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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


** Tags: amd64 apport-bug yakkety

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

Title:
  not recognize Cyrillic characters

Status in nautilus package in Ubuntu:
  New

Bug description:
  not recognize Cyrillic characters

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 16 11:24:22 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2015-08-27 (446 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (28 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1642134] [NEW] Kodi crashes upon start, downgrading nvidia-*304 fixes it

[nuaimat]

Public bug reported:

I am on Ubuntu 16.04.1 LTS

after upgrading packages to version 304.132-0ubuntu2  
- nvidia-304
- nvidia-current
- nvidia-libopencl1-304
- nvidia-opencl-icd-304

Kodi on ubuntu crashes and fails to start, after downgrading to version
304.131-0ubuntu3 and reboot, kodi started successfully.

Kodi crash log:


# Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Sun Nov 13 02:00:15 CST 2016
 Kodi Options:
 Arch: x86_64
 Kernel: Linux 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016
 Release: Ubuntu 16.04.1 LTS (Xenial Xerus)
## END SYSTEM INFO ##

### STACK TRACE #
=>  Core file: /home/nuaimat/core (2016-11-13 02:00:15.144874481 -0600)
=
[New LWP 1383]
[New LWP 1385]
[New LWP 1386]
[New LWP 1387]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin --standalone'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0070 in ?? ()
[Current thread is 1 (Thread 0x7fa52c806980 (LWP 1383))]

Thread 4 (Thread 0x7fa508e83700 (LWP 1387)):
#0  0x7fa524cb4357 in ioctl () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa527977a52 in ?? () from /usr/lib/x86_64-linux-gnu/libasound.so.2
#2  0x00abf241 in CAESinkALSA::AddPackets(unsigned char**, unsigned 
int, unsigned int) ()
#3  0x00a8cf26 in 
ActiveAE::CActiveAESink::OutputSamples(ActiveAE::CSampleBuffer*) ()
#4  0x00a8e062 in ActiveAE::CActiveAESink::StateMachine(int, 
Actor::Protocol*, Actor::Message*) ()
#5  0x00a8ea97 in ActiveAE::CActiveAESink::Process() ()
#6  0x01d2ac6f in CThread::Action() ()
#7  0x01d2af2f in CThread::staticThread(void*) ()
#8  0x7fa52aff170a in start_thread (arg=0x7fa508e83700) at 
pthread_create.c:333
#9  0x7fa524cbe82d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa509684700 (LWP 1386)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x00a8af77 in ActiveAE::CActiveAE::Process() ()
#2  0x01d2ac6f in CThread::Action() ()
#3  0x01d2af2f in CThread::staticThread(void*) ()
#4  0x7fa52aff170a in start_thread (arg=0x7fa509684700) at 
pthread_create.c:333
#5  0x7fa524cbe82d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa50a4ac700 (LWP 1385)):
#0  0x7fa524cb2b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x01027a2b in CFDEventMonitor::Process() ()
#2  0x01d2ac6f in CThread::Action() ()
#3  0x01d2af2f in CThread::staticThread(void*) ()
#4  0x7fa52aff170a in start_thread (arg=0x7fa50a4ac700) at 
pthread_create.c:333
#5  0x7fa524cbe82d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fa52c806980 (LWP 1383)):
#0  0x0070 in ?? ()
#1  0x00847fe5 in CMediaSourceSettings::Clear() ()
#2  0x00e24841 in CSettingsManager::OnSettingsUnloaded() ()
#3  0x00e254b3 in CSettingsManager::Unload() ()
#4  0x00e28a1e in CSettingsManager::Clear() ()
#5  0x00835d4c in CSettings::Uninitialize() ()
#6  0x008365af in CSettings::~CSettings() ()
#7  0x7fa524bf1ff8 in __run_exit_handlers (status=-1, listp=0x7fa524f7b5f8 
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#8  0x7fa524bf2045 in __GI_exit (status=) at exit.c:104
#9  0x7fa524bd8837 in __libc_start_main (main=0x7c23c0 , argc=2, 
argv=0x7fff43d54d98, init=, fini=, 
rtld_fini=, stack_end=0x7fff43d54d88) at ../csu/libc-start.c:325
#10 0x0081bb89 in _start ()
# END STACK TRACE ###
# LOG FILE ##

02:00:14 T:140347392944512  NOTICE: special://profile/ is mapped to: 
special://masterprofile/
02:00:14 T:140347392944512  NOTICE: 
---
02:00:14 T:140347392944512  NOTICE: Starting Kodi (16.1 Git:c327c53). Platform: 
Linux x86 64-bit
02:00:14 T:140347392944512  NOTICE: Using Release Kodi x64 build
02:00:14 T:140347392944512  NOTICE: Kodi compiled Apr 25 2016 by GCC 5.3.1 for 
Linux x86 64-bit version 4.4.6 (263174)
02:00:14 T:140347392944512  NOTICE: Running on Ubuntu 16.04.1 LTS, kernel: 
Linux x86 64-bit version 4.4.0-47-generic
02:00:14 T:140347392944512  NOTICE: FFmpeg statically linked, version: 
2.8.6-kodi-2.8.6-Jarvis-16.0
02:00:14 T:140347392944512  NOTICE: Host CPU: Intel(R) Atom(TM) CPU 230 @ 
1.60GHz, 2 cores available
02:00:14 T:140347392944512  NOTICE: special://xbmc/ is mapped to: 
/usr/share/kodi
02:00:14 T:140347392944512  NOTICE: special://xbmcbin/ is mapped to: 
/usr/lib/kodi
02:00:14 T:140347392944512  NOTICE: special://masterprofile/ is mapped to: 

[Desktop-packages] [Bug 1641264] Re: libreoffice crashes on startup when using OpenGL rendering and proprietary nvidia driver.

[Christopher M. Penalver]

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

To see if this is already resolved upstream could you please advise if
this is reproducible with the latest LibreOffice version available from
https://launchpad.net/~libreoffice ?

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

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

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

Title:
  libreoffice crashes on startup when using OpenGL rendering and
  proprietary nvidia driver.

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  I noticed that Libreoffice was rendering very slow (I can see each
  menu option drawn) so I tried using OpenGL rendering, which causes
  libreoffice to crash immediately on start-up.

  I confirm that OpenGL is working fine:

  $ glxinfo | head
  name of display: :0.0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4

  I'm able to use glxgears and other apps like djv_view with fast
  rendering.

  I've attached the gdb trace resulting from the crash with debug
  symbols, following is an except:

  Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  #0  0x in ?? ()
  #1  0x768e96f7 in OpenGLContext::AcquireFramebuffer (this=0x128f600, 
rTe
  xture=...) at 
/build/libreoffice-OypX7x/libreoffice-5.1.4/vcl/source/opengl/Open
  GLContext.cxx:1773

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 11 18:45:52 2016
  InstallationDate: Installed on 2010-11-05 (2198 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-11-02 (9 days ago)

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

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

[Desktop-packages] [Bug 1636011] Re: pretty print for thunderbird -h

[Mathew Hodson]

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

** Tags added: string-fix

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

Title:
  pretty print for thunderbird -h

Status in thunderbird package in Ubuntu:
  New

Bug description:
  In file debian/thunderbird.sh.in the debug command help strings should
  be aligned with the other commands in thunderbird -h. See patch file
  attached.

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

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

[Desktop-packages] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13

[Christopher M. Penalver]

vak, after what package update precisely did this issue start happening
again with?

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

Title:
  Random stuck keys on Lenovo Yoga 13

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  pressing arrow keys leads randomly to the effect of stuck number key
  and produces output in consoles or text editors like: "22" or
  "88". Pressing some other key stops the infinite flooding.

  This may (or not) be related to the following flooding in
  /var/log/system

  May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.
  May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key 
released (translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.

  
  these messages are generated approximately each 200 msec. If the former is 
not related to stuck key problem, please, ignore.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 24 09:45:39 2016
  DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2013-11-17 (918 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 2191
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN55WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 24 08:57:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 864 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1610666] Re: Mouse cursor moves choppy/doesn't update its position as it should

[Christopher M. Penalver]

** Description changed:

  Q. What I expected to happen?
  A. The mouse would run smoothly as it does run in windows.
  
  Q. What happened instead?
  A. The mouse lags moves choppy/doesn't update its position as it should
  
  Additional Information:
  Output of "xinput --list --short"
  
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ E-Signal USB Gaming Mouse   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ E-Signal USB Gaming Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft® LifeCam HD-3000  id=9[slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  
  Output of "xinput --list-props 11"
  
  Device 'E-Signal USB Gaming Mouse':
   Device Enabled (133):1
   Coordinate Transformation Matrix (135):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (259):  0
   Device Accel Constant Deceleration (260):1.00
   Device Accel Adaptive Deceleration (261):1.00
   Device Accel Velocity Scaling (262): 10.00
   Device Product ID (251): 1241, 41132
   Device Node (252):   "/dev/input/event4"
   Evdev Axis Inversion (263):  0, 0
   Evdev Axes Swap (265):   0
   Axis Labels (266):   "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (257), 
"Rel Vert Wheel" (258)
   Button Labels (267): "Button Left" (136), "Button Middle" (137), "Button 
Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz 
Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button Side" (255), 
"Button Extra" (256), "Button Unknown" (254), "Button Unknown" (254), "Button 
Unknown" (254), "Button Unknown" (254)
   Evdev Scrolling Distance (268):  1, 1, 1
   Evdev Middle Button Emulation (269): 0
   Evdev Middle Button Timeout (270):   50
   Evdev Third Button Emulation (271):  0
   Evdev Third Button Emulation Timeout (272):  1000
   Evdev Third Button Emulation Button (273):   3
   Evdev Third Button Emulation Threshold (274):20
   Evdev Wheel Emulation (275): 0
   Evdev Wheel Emulation Axes (276):0, 0, 4, 5
   Evdev Wheel Emulation Inertia (277): 10
   Evdev Wheel Emulation Timeout (278): 200
   Evdev Wheel Emulation Button (279):  4
   Evdev Drag Lock Buttons (280):   0
  
  Output of "lsusb"
  
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 002: ID 0bc2:3321 Seagate RSS LLC
  Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 005: ID 04d9:a0ac Holtek Semiconductor, Inc.
  Bus 001 Device 003: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  
  Note : Holtek Semiconductor, Inc. is my mouse
  
  Also found this in dmesg :
  
  [  292.597380] usb 1-1.4: new full-speed USB device number 5 using ehci-pci
  [  293.941408] usb 1-1.4: New USB device found, idVendor=04d9, idProduct=a0ac
  [  293.941413] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  293.941416] usb 1-1.4: Product: USB Gaming Mouse
  [  293.941418] usb 1-1.4: Manufacturer: E-Signal
  [  294.241702] input: E-Signal USB Gaming Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04D9:A0AC.0004/input/input16
  [  294.242160] hid-generic 0003:04D9:A0AC.0004: input,hidraw0: USB HID v1.10 
Mouse [E-Signal USB Gaming Mouse] on usb-:00:1a.0-1.4/input0
  [  294.841559] input: E-Signal USB Gaming Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04D9:A0AC.0005/input/input17
  [  294.897825] hid-generic 0003:04D9:A0AC.0005: input,hiddev0,hidraw1: USB 
HID v1.10 Keyboard [E-Signal USB Gaming Mouse] on usb-:00:1a.0-1.4/input1
  [  295.241685] hid-generic 0003:04D9:A0AC.0006: hiddev0,hidraw2: USB HID 
v1.10 Device [E-Signal USB Gaming Mouse] on usb-:00:1a.0-1.4/input2
  
  Things that i have already tried:
  
  Set "Device Accel Constant Deceleration (260):1.00" prop to greater
  values, makes the mouse go faster doesn't make it update its position
  

[Desktop-packages] [Bug 1640769] Re: Fatal exception: Signal 11

[Christopher M. Penalver]

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

Could you please provide the file(s) that reproduce this?

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

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

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

Title:
  Fatal exception: Signal 11

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Often happens when I have a specific xls file open and I load another .doc.
  Happens also when generating PDF from document.

  
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: Fatal exception: Signal 11
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: Stack:
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x39530)[0x7f8c4f48d530]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x398c3)[0x7f8c4f48d8c3]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x399f8)[0x7f8c4f48d9f8]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0)[0x7f8c4f0c04b0]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/../program/libswlo.so(_ZNK9SwFEShell24GetObjCntTypeOfSelectionEPP9
  SdrObject+0x12)[0x7f8bfad06f62]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/../program/libswlo.so(_ZN14SwTransferable17GetSotDestinationERK10S
  wWrtShellPK5Point+0x1b7)[0x7f8bfb1f8c47]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/../program/libswlo.so(+0xb159d3)[0x7f8bfb2f59d3]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/libvclplug_genlo.so(+0x41462)[0x7f8c3b015462]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/libvclplug_genlo.so(+0x5395a)[0x7f8c3b02795a]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c677)[0x7f8c4f490677]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x770a)[0x7f8c4e77d70a]
  Nov 10 12:23:28 acer-03 org.gnome.Nautilus[1966]: 
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f8c4f19182d]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 10 12:33:42 2016
  InstallationDate: Installed on 2014-10-07 (764 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-10-12 (28 days ago)

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

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

[Desktop-packages] [Bug 1599952] Re: Blurred images with kernels after 4.2.x

[Launchpad Bug Tracker]

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

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

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

Title:
  Blurred images with kernels after 4.2.x

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Have used Ubuntu or its flavors for 3 years with no issues on this
  machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
  16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with
  blurred images.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-07-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6850
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=30188e44-b1e6-4cdc-bd16-62f107d213a7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6850
  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.:bvr1301:bd12/21/2011:svnASUSTeKComputerINC.:pnCM6850:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM6850:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6850
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Launchpad Bug Tracker]

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

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

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

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

Status in xorg package in Ubuntu:
  Expired

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

  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 

[Desktop-packages] [Bug 1482938] Re: im-config gcin qt5

[Bug Watch Updater]

** Changed in: im-config (Debian)
   Status: Unknown => Fix Released

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

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: im-config 0.29-1ubuntu2 [modified: 
usr/share/im-config/data/26_gcin.rc]
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug  9 09:01:10 2015
  InstallationDate: Installed on 2015-04-26 (104 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1482938] Re: im-config gcin qt5

[Launchpad Bug Tracker]

This bug was fixed in the package im-config - 0.29-1.4ubuntu1

---
im-config (0.29-1.4ubuntu1) zesty; urgency=medium

  * Merge with Debian unstable (LP: #1482938, LP: #1642001), remaining
changes:
- d/im-config.user-session.upstart, d/im-config.links, d/rules:
  - Install upstart user session job.
- d/user/im-config.override, d/user/im-config.service, d/rules:
  - Install systemd user session job.
- debian/menu
- debian/patches/01-ubuntu-default-mode.patch
- debian/patches/03-not-always-require-zenity.patch
- debian/patches/use-distinguishable-abstract-address.patch

  * debian/patches/use-whiptail-as-better-dialog.patch:
- Dropped; applied upstream.

 -- Gunnar Hjalmarsson   Wed, 16 Nov 2016 03:44:00
+0100

** Changed in: im-config (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: im-config 0.29-1ubuntu2 [modified: 
usr/share/im-config/data/26_gcin.rc]
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug  9 09:01:10 2015
  InstallationDate: Installed on 2015-04-26 (104 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1642001] Re: uim-qt5 check is broken

[Bug Watch Updater]

** Changed in: im-config (Debian)
   Status: Unknown => Fix Released

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

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  XIM support check for Qt5 in UIM is broken — it uses the same paths as for 
Qt4, but they've been changed.
  It's already fixed in Debian (0.29-1.2), so the package should probably be 
just reimported.

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

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

[Desktop-packages] [Bug 1642001] Re: uim-qt5 check is broken

[Launchpad Bug Tracker]

This bug was fixed in the package im-config - 0.29-1.4ubuntu1

---
im-config (0.29-1.4ubuntu1) zesty; urgency=medium

  * Merge with Debian unstable (LP: #1482938, LP: #1642001), remaining
changes:
- d/im-config.user-session.upstart, d/im-config.links, d/rules:
  - Install upstart user session job.
- d/user/im-config.override, d/user/im-config.service, d/rules:
  - Install systemd user session job.
- debian/menu
- debian/patches/01-ubuntu-default-mode.patch
- debian/patches/03-not-always-require-zenity.patch
- debian/patches/use-distinguishable-abstract-address.patch

  * debian/patches/use-whiptail-as-better-dialog.patch:
- Dropped; applied upstream.

 -- Gunnar Hjalmarsson   Wed, 16 Nov 2016 03:44:00
+0100

** Changed in: im-config (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  XIM support check for Qt5 in UIM is broken — it uses the same paths as for 
Qt4, but they've been changed.
  It's already fixed in Debian (0.29-1.2), so the package should probably be 
just reimported.

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

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

[Desktop-packages] [Bug 1482938] Re: im-config gcin qt5

[Gunnar Hjalmarsson]

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

** Also affects: im-config (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787618
   Importance: Unknown
   Status: Unknown

** Changed in: im-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu)
   Status: New => In Progress

** Changed in: im-config (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  In Progress
Status in im-config package in Debian:
  Unknown

Bug description:
  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: im-config 0.29-1ubuntu2 [modified: 
usr/share/im-config/data/26_gcin.rc]
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug  9 09:01:10 2015
  InstallationDate: Installed on 2015-04-26 (104 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1642001] Re: uim-qt5 check is broken

[Gunnar Hjalmarsson]

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

** Also affects: im-config (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792588
   Importance: Unknown
   Status: Unknown

** Changed in: im-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu)
   Status: New => In Progress

** Changed in: im-config (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  In Progress
Status in im-config package in Debian:
  Unknown

Bug description:
  XIM support check for Qt5 in UIM is broken — it uses the same paths as for 
Qt4, but they've been changed.
  It's already fixed in Debian (0.29-1.2), so the package should probably be 
just reimported.

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Charles]

The chromium package in canonical-chromium-builds/stage PPA works for
me. A unstable browser is better than one that cannot access most of my
websites.

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.

[Leon]

I was experiencing this bug with KDE NEON 5.8 on my MacBookPro5,5.
Luckily I stumbled over https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/+bug/1389215/comments/50 (Thank you Hans
Deragon (deragon)).

As my laptop uses NVIDIA GeForce 9400M, I had to slightly tweak his
script and like magic after  making it executable, running it and a
quick reboot for safe measures.. IT WORKS!!

See attached

** Attachment added: "nvidia-proprietary-brigthness-keys-fix_NVID_9400M.sh"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1389215/+attachment/4777901/+files/nvidia-proprietary-brigthness-keys-fix_NVID_9400M.sh

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

Title:
  Brightness controls are not working in Unity / Xorg because of Nvidia
  proprietary driver.

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

Bug description:
  Affects: Ubuntu 16.04 and 14.04.
  Occurs only with Nvidia proprietary driver.  Nouveau works well.

  Brightness controls are not working in Unity / Xorg.  When pressing
  the keys  and  on my Lenovo W510, I see the
  indicator on the screen showing the level of brightness changing, so
  key mapping is not the problem.  However, the brightness is not
  changing.

  On the kernel level, I have the single following device:

  # cd /sys/class/backlight
  # ls -l
  total 0
  lrwxrwxrwx 1 root root 0 Nov  3 17:16 acpi_video0 -> 
../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0

  When playing with the  and , the value of
  /sys/class/backlight/brightness changes accordingly.  The screen
  brightness does not change.

  Performing:

  # echo 10 >brightness

  ...does not have any effect (regardless of the value provided, 10
  being just an example).

  WORKAROUND

  There is an odd workaround.  Simply go to the console using
   and using the  and  keys,
  brightness then changes.  Return to Unity / Xorg with 
  and the selected brightness persists.

  NON WORKING WORKAROUND

  On the web, I read that adding:

  Option "RegistryDwords" "EnableBrightnessControl=1"'

  in xorg.conf might fix the problem.  I do not have an xorg and when I
  let the proprietary Nvidia driver generate one and add this option, X
  does not start anymore.

  Ubuntu 14.04.1 LTS with latest updates as of this writing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  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_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  4 07:38:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2145]
  InstallationDate: Installed on 2014-11-01 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4318CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO

[Desktop-packages] [Bug 1642089] [NEW] Banshee crashes after indeterminate amount of play time

[calexil]

Public bug reported:

crashes with the error:

Banshee: Fatal IO error 11 (Resource temporarily unavailable) on X
server :0.

after playing songs for a while, time varies.. no indicators as to
something triggering it.

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

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

Title:
  Banshee crashes after indeterminate amount of play time

Status in banshee package in Ubuntu:
  New

Bug description:
  crashes with the error:

  Banshee: Fatal IO error 11 (Resource temporarily unavailable) on X
  server :0.

  after playing songs for a while, time varies.. no indicators as to
  something triggering it.

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

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

[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

[Dik]

Downgrade the firmware to iwlwifi-3945-1.ucode seems to fix the problem.

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1642081] [NEW] software updater breaks packages

[Scott Dunbar]

Public bug reported:

System is an up to date Ubuntu 16.04.  Run "software" program.  Believe
it when it says you have updates.  Try to log back in and packages are
broken.  Cinnamon is semi removed (won't restart) and when you try to
reinstall it you get messages like:

scott@bluerock:~$ sudo apt install cinnamon
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cinnamon : Depends: libmuffin0 (>= 3.2.0) but it is not going to be installed
Depends: gir1.2-meta-muffin-0.0 (>= 3.2.0) but it is not going to 
be installed
Recommends: cinnamon-bluetooth but it is not installable
E: Unable to correct problems, you have held broken packages.

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

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

Title:
  software updater breaks packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  System is an up to date Ubuntu 16.04.  Run "software" program.
  Believe it when it says you have updates.  Try to log back in and
  packages are broken.  Cinnamon is semi removed (won't restart) and
  when you try to reinstall it you get messages like:

  scott@bluerock:~$ sudo apt install cinnamon
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cinnamon : Depends: libmuffin0 (>= 3.2.0) but it is not going to be installed
  Depends: gir1.2-meta-muffin-0.0 (>= 3.2.0) but it is not going to 
be installed
  Recommends: cinnamon-bluetooth but it is not installable
  E: Unable to correct problems, you have held broken packages.

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

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

[Desktop-packages] [Bug 1642078] [NEW] Black screen at startup

[victor gaspar]

Public bug reported:

Problem description:
The laptop starts up fine but the screen is black; even though the screen is 
black I can hear the drum sound prompting me to log in. After rebooting laptop 
all is well with the screen and I have a fully functional system. Sometimes, 
though, I have to restart twice.

After some search I found people reporting the same issue:
https://ubuntuforums.org/showthread.php?t=2337274

or similar issues:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074?comments=all

Additional information:

1) Ubuntu release:
Description:Ubuntu 16.04.1 LTS
Release:16.04

2) Package version:
xorg:
  Instalados: 1:7.7+13ubuntu3
  Candidato:  1:7.7+13ubuntu3
  Tabla de versión:
 *** 1:7.7+13ubuntu3 500
500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) Computer information:
Processor: AMD A10-8700 Radeon R6
Graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0)

Kind regards,
Victor

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Nov 15 17:56:57 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Carrizo [103c:8246]
InstallationDate: Installed on 2016-11-10 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-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: 05/03/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.03
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8246
dmi.board.vendor: HP
dmi.board.version: 98.11
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.03:bd05/03/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn8246:rvr98.11:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Nov 15 17:21:18 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: amdgpu

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

Title:
  Black screen at startup

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem description:
  The laptop starts up fine but the screen is black; even though the screen is 
black I can hear the drum sound prompting me to log in. After rebooting laptop 
all is well with the screen and I have a fully functional system. Sometimes, 
though, I have to restart twice.

  After some search I found people reporting the same issue:
  https://ubuntuforums.org/showthread.php?t=2337274

  or similar issues:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074?comments=all

  Additional information:

  1) Ubuntu release:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) Package version:
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Computer information:
  Processor: AMD A10-8700 Radeon R6
  Graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0)

  Kind 

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

[Andrea Simonetti]

Thanks.. I'll see if i can understand what happens..

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

Title:
  [Touch] Incoming call gets silent randomly

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

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

  Device: E5, OTA-12, stable channel

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

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

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

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

[Desktop-packages] [Bug 977228] Re: gnome-screenshot forgets "last-save-directory"

[Le Gluon Du Net]

Bug still present in Ubuntu 16.10

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

Title:
  gnome-screenshot forgets "last-save-directory"

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04, Beta 2
  1) press [PrintScreen] to do a screenshot
  2) gnome-screenshot proposes to save it in "$HOME/pictures"
  3) change location to "$HOME/videos" or similiar and close gnome-screenshot
  4) press [PrintScreen] again and take another screenshot
  6) tool wants to save picture in "$HOME/pictures" again
  5) expected behaviour: proposes to save pic in "$HOME/videos"

  BTW: Setting a fixed path in dconf-editor entry "last-save-directory"
  doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.4.0-0ubuntu1
  Uname: Linux 3.3.1-030301-generic i686
  ApportVersion: 2.0-0ubuntu4
  Architecture: i386
  Date: Mon Apr  9 15:37:26 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to precise on 2011-11-24 (136 days ago)

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

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

[Desktop-packages] [Bug 1000534] Re: Gnome-Screenshot is not using the last saved folder to preselect

[Le Gluon Du Net]

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

Bug still present in Ubuntu 16.10

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

Title:
  Gnome-Screenshot is not using the last saved folder to preselect

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  after you save one screenshot in another folder, then close the
  application and take a screenshot it is not preselecting that folder,
  and you end up having to navigating it to again

  eventhough the last saved folder is recorded in dconf settings it is
  not being used

  this wasn't the case in Ubuntu 10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Thu May 17 13:15:32 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to precise on 2012-03-31 (46 days ago)

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

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

[Desktop-packages] [Bug 1642063] [NEW] Split DNS with openvpn erroneously removes nameservers from dnsmasq

[manic]

Public bug reported:

I was setting up a fresh ubuntu xenial a few days ago (Ubuntu 16.04.1 LTS)
with network-manager 1.2.2-0ubuntu0.16.04.3.

I connect to an openvpn server that pushes a DNS Server to me:

push "dhcp-option DNS 172.24.32.1"

This DNS-Server is properly received and (as I have marked "use for this 
network only"
configured correctely over DBus to dnsmasq (sorry, german logs):

Nov 15 22:23:47 chili dnsmasq[1422]: vorgelagerte Server von DBus gesetzt
Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 172.24.32.1#53 für 
Domain example.com
Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 172.24.32.1#53 für 
Domain 24.172.in-addr.arpa

So now dnsmasq has Nameservers for my vpn internal domain and the reverse 
domains
of the routes pushed by the vpn. That's exactly what I want - for the VPN 
ressources.

BUT (and this took me some time to understand) the previously valid nameservers 
(originated from the DHCP server of the Wireless connection) are REMOVED. This 
means
that dnsmasq is left with name servers for specific domains only, there are no
generic name servers available any more. If queried for a name resolution for 
e.g.
"www.google.com", dnsmasq just returns an error message.

So while I had full IP connectivity in the network behind the VPN AND to the 
internet, I had no name resolution any more for domains outside of the VPN.

I would have expected that the domain servers (that are specific to the VPN 
Domains) are ADDED to the list of dnsmasq's servers, but they are replaced.
As (according to the  dnsmasq man page) "More specific domains take precendence
over less specific domains", no leakage of DNS requests would happen in either 
direction.

I even monitored the D-Bus communication and it can be seen that it uses
the "SetServersEx" command (which replaces the list).

I built a workaround using a script in /etc/NetworkManager/dispatcher.d combined
with a configuration file in /etc/NetworkManager/dnsmasq.d that points to a 
"servers-file". When the vpn comes up, the script populates the servers-file
from the $IP4_NAMESERVERS variable and HUPs dnsmasq, which finally gives me
in /var/log/syslog:

Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 8.8.8.8#53
Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 172.24.32.1#53 für 
Domain example.com
Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 172.24.32.1#53 für 
Domain 24.172.in-addr.arpa

Of course the script undos the changes when the vpn comes down again. If anyone
is interested, I can share my script - but it is quite specific to my use
case so I wonder if others are interested in...

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

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

Title:
  Split DNS with openvpn erroneously removes  nameservers from dnsmasq

Status in network-manager package in Ubuntu:
  New

Bug description:
  I was setting up a fresh ubuntu xenial a few days ago (Ubuntu 16.04.1 LTS)
  with network-manager 1.2.2-0ubuntu0.16.04.3.

  I connect to an openvpn server that pushes a DNS Server to me:

  push "dhcp-option DNS 172.24.32.1"

  This DNS-Server is properly received and (as I have marked "use for this 
network only"
  configured correctely over DBus to dnsmasq (sorry, german logs):

  Nov 15 22:23:47 chili dnsmasq[1422]: vorgelagerte Server von DBus gesetzt
  Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 172.24.32.1#53 für 
Domain example.com
  Nov 15 22:23:47 chili dnsmasq[1422]: Benutze Namensserver 172.24.32.1#53 für 
Domain 24.172.in-addr.arpa

  So now dnsmasq has Nameservers for my vpn internal domain and the reverse 
domains
  of the routes pushed by the vpn. That's exactly what I want - for the VPN 
ressources.

  BUT (and this took me some time to understand) the previously valid 
nameservers 
  (originated from the DHCP server of the Wireless connection) are REMOVED. 
This means
  that dnsmasq is left with name servers for specific domains only, there are no
  generic name servers available any more. If queried for a name resolution for 
e.g.
  "www.google.com", dnsmasq just returns an error message.

  So while I had full IP connectivity in the network behind the VPN AND to the 
  internet, I had no name resolution any more for domains outside of the VPN.

  I would have expected that the domain servers (that are specific to the VPN 
  Domains) are ADDED to the list of dnsmasq's servers, but they are replaced.
  As (according to the  dnsmasq man page) "More specific domains take 
precendence
  over less specific domains", no leakage of DNS requests would happen in 
either direction.

  I even monitored the D-Bus communication and it can be seen that it uses
  the "SetServersEx" command (which replaces the list).

  I built a workaround using a script in 

Re: [Desktop-packages] [Bug 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off

[Luke Yelavich]

Thanks very much for doing the leg work for this. Once pulseaudio in
xenial-proposed gets pushed to updates, which should be very soon, I
will do the necessary work to sponsor this and get it into Xenial.

Thanks again.

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

[Desktop-packages] [Bug 1639663] Re: vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

Title:
  vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2

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

Bug description:
  Running version 16.04.2
  vdpau only works as root in version 304.132-0ubuntu0.16.04.2.

  I can run vdpauinfo as normal user and get an error, unable to create
  device. Run as root (sudo vdpauinfo) and it works.  Similarly, running
  mythfrontend with vdpau requires sudo mythfrontend to be able to work.

  The previous version 304.131 worked fine.  I have temporarily fixed
  the problem by rolling back to that version.

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Nick Ceriello]

Any ETA on the release?

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Chad Miller]

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641629] Re: Autocomplete popups are misplaced

[gpothier]

Hi, I just noticed the bug happens on both monitors. I am attaching a
new screenshot, this one is on the primary (external) monitor; the
previous one was on the secondary (laptop) monitor.

** Attachment added: "20161115_181027.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1641629/+attachment/4777814/+files/20161115_181027.jpg

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

Title:
  Autocomplete popups are misplaced

Status in firefox package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.10, Firefox misplaces autocomplete popups. In the
  attached screenshot, the autocomplete popup is displayed below the
  "Nombre transferencia" field, although the focused field is "Mensaje
  para destinatario", below. Also, moving the mouse pointer below the
  correct field actually highlights completion options as if the menu
  was there (see the mouse pointer position on the screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 49.0.2+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gpothier   3169 F pulseaudio
   /dev/snd/controlC0:  gpothier   3169 F pulseaudio
  BuildID: 20161025164528
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Nov 14 11:57:19 2016
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (660 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-604f3b87-472e-4026-8588-3d2122160725
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=49.0.2/20161025164528 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   rhythmbox-mozilla 3.4.1-1ubuntu1
   gnome-shell   3.20.4-0ubuntu2
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to yakkety on 2016-10-30 (15 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1642045] [NEW] Please check about these issues

[giorgio]

Public bug reported:

Please check about these issues

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  340.98  Mon Sep 19 16:44:35 PDT 
2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov 15 21:35:03 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-46-generic, i686: installed
 bbswitch, 0.8, 4.4.0-47-generic, i686: installed
 nvidia-340, 340.98, 4.4.0-46-generic, i686: installed
 nvidia-340, 340.98, 4.4.0-47-generic, i686: installed
GraphicsCard:
 NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
InstallationDate: Installed on 2016-08-24 (83 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug 
plymouth:debug=1=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.04
dmi.board.name: Newark
dmi.board.vendor: FOXCONN
dmi.board.version: HP P/N
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: NQ918AA-ABZ CQ5023IT
dmi.sys.vendor: Compaq-Presario
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Nov 15 20:17:16 2016
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: apport-bug compiz-0.9 i386 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/1642045

Title:
  Please check about these issues

Status in xorg package in Ubuntu:
  New

Bug description:
  Please check about these issues

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  340.98  Mon Sep 19 16:44:35 PDT 
2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov 15 21:35:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-46-generic, i686: installed
   bbswitch, 0.8, 4.4.0-47-generic, i686: installed
   nvidia-340, 340.98, 4.4.0-46-generic, i686: installed
   nvidia-340, 340.98, 4.4.0-47-generic, i686: installed
  GraphicsCard:
   NVIDIA 

[Desktop-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Launchpad Bug Tracker]

This bug was fixed in the package unity-scopes-shell -
0.5.8+17.04.20161115.3-0ubuntu1

---
unity-scopes-shell (0.5.8+17.04.20161115.3-0ubuntu1) zesty; urgency=medium

  [ Michael Terry ]
  * Handle running inside a snap by paying attention to the $SNAP
prefix. (LP: #1629009)

 -- Marcus Tomlinson   Tue, 15 Nov 2016
10:54:03 +

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

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+subscriptions

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

[Desktop-packages] [Bug 1560162] Re: Xenial: scaling is horribly out on xps13 install session

[Mathieu Trudel-Lapierre]

Since it's been verified by Nara; marking verification-done.

** Tags added: verification-done

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

Title:
  Xenial: scaling is horribly out on xps13 install session

Status in OEM Priority Project:
  New
Status in metacity package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Committed

Bug description:
  STEPS:
  Requirements laptop desktop with a hidpi screen (Here xps 13)
  1. Grab the latest daily image and trigger an install
  2. On the first page notice the of centre and over scaled window

  EXPECTED:
  I expect to see something resembling a normal scaled desktop install

  ACTUAL:
  Things are not quite correct see attached screenshots

  ubiquity/xenial 2.21.49 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1560162/+subscriptions

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

[Desktop-packages] [Bug 1547762] Re: "SSL Protocol Error" in Chromium for several Google web sites after installing Ubuntu Security Updates for libnss3

[Bryan]

I to have started to have SSL certificate errors with Chromium. Chrome
and Firefox are OK.

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

Title:
  "SSL Protocol Error" in Chromium for several Google web sites after
  installing Ubuntu Security Updates for libnss3

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Scenario: Laptop computer running Ubuntu 12.04.5 LTS (64-bit)
  ("Precise Pangolin")

  Issue: In the Chromium web browser - "Version 37.0.2062.120 Ubuntu
  12.04 (281580) (64-bit)" - after having installed the Ubuntu security
  Updates that were available on Feb 18, 2016, I get the following error
  while trying to access some Google Web sites (e.g.
  https://www.google.com ; https://plus.google.com/ ;
  https://hangouts.google.com/ ):

    
  SSL connection error

  Unable to make a secure connection to the server. This may be a problem with 
the server, or it may be requiring a client authentication certificate that you 
don't have.  
  Error code: ERR_SSL_PROTOCOL_ERROR
  

  Those web sites still appear correctly in the same computer, using
  other web browsers, namely Google Chrome - "Version 48.0.2564.109
  (64-bit)" - or Mozilla Firefox - version "44.0.2"

  The updates installed on Feb 18, 2016 were the following:

  libnss3:amd64 (3.19.2.1-0ubuntu0.12.04.2, 3.21-0ubuntu0.12.04.1)  
  libnss3:i386 (3.19.2.1-0ubuntu0.12.04.2, 3.21-0ubuntu0.12.04.1)  
  libnss3-1d:amd64 (3.19.2.1-0ubuntu0.12.04.2, 3.21-0ubuntu0.12.04.1)

  "libnss3" is listed at
  http://packages.ubuntu.com/search?keywords=libnss3 as being the
  "Network Security Service libraries", so I believe it's possible that
  update may be related to this issue that I'm facing.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  ProcVersionSignature: Ubuntu 3.13.0-77.121~precise1-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  Date: Sat Feb 20 03:37:51 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   
  SourcePackage: chromium-browser
  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/chromium-browser/+bug/1547762/+subscriptions

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

[Desktop-packages] [Bug 1607240] Re: Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it should be 1.0)

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-system-settings -
0.4+17.04.20161109.1-0ubuntu1

---
ubuntu-system-settings (0.4+17.04.20161109.1-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * Allow scroll speed multipliers up to 3.0; since the default speed in
(LP: #1607240, #1627567)

  [ Ken VanDine ]
  * Updated example plugin to work with current SDK
  * Fixed pep8 failure

  [ Timo Jyrinki ]
  * Stop depending on transitional packages. (LP: #1583079) (LP:
#1583079)

  [ jonas-drange ]
  * Drop “at” from “Updated at ” string

 -- Ken VanDine   Wed, 09 Nov 2016 15:27:26
+

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it
  should be 1.0)

Status in Canonical System Image:
  Fix Released
Status in QtMir:
  Fix Released
Status in qtubuntu:
  Fix Released
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

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

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

[Desktop-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu

[Ivan Koldaev]

J McDonald, thank you for pointing to the PPA!
I was patiently waiting more than month for official update, but free space on 
my iPhone running out, so I have to finally copy these photos :)

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

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

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

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

[Ryan Lee Sipes]

This affects me as well. Seemingly with each type of bluetooth device
I've connected. Sony SRS-X11 bluetooth speaker, my JBL Bluetooth speaker
(not sure on the model), and my SkullCandy Hesh 2 Wireless Headphones.

Restarting the devices multiple times appears to randomly fix it. Then I
just make sure to keep the device connected on my desk all day to ensure
it does not get disconnected.

Will try the workaround.

This affects me on both 16.04 and 16.10 (tested on multiple machines
here at System76).

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

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

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

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

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

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

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

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

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Lake]

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => 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/1553685

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1642013] [NEW] brasero does not preserve files date/time

[Davide Capodaglio]

Public bug reported:

ISO images (and so burned CD/DVDs) generated by brasero do not preserve files 
date/time, they are all set to 'now'.
Creating an ISO with standard options with genisoimage or xfburn does work 
flawlessly.

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

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

Title:
  brasero does not preserve files date/time

Status in brasero package in Ubuntu:
  New

Bug description:
  ISO images (and so burned CD/DVDs) generated by brasero do not preserve files 
date/time, they are all set to 'now'.
  Creating an ISO with standard options with genisoimage or xfburn does work 
flawlessly.

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

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

[Desktop-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-keyboard -
0.100+17.04.20161108-0ubuntu1

---
ubuntu-keyboard (0.100+17.04.20161108-0ubuntu1) zesty; urgency=medium

  * Add support for building as a snap (LP: #1572653, #1629009)

 -- Michael Sheldon   Tue, 08 Nov 2016
11:24:43 +

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+subscriptions

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

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Bengt Nilsson]

I tried xfce4-settings 4.12.1-11 as mentioned in #133 and indeed it "works", X 
does not crash.
However, the set screen resolution is lost. When I turn on the screen again, 
the desktop defaults to the highest possible screen resolution. 
In my case, it means that my desktop menu bar and docky are placed outside the 
screen bounds, tricky to reset.
Better than it was before, but not quite there yet.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

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

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Oleksandr Pikozh]

** Description changed:

  I'm unable to start plasma after nvidia nvidia-304 package upgrade (and
  reboot).
  
  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).
  
- Current version of packages make my system at all:
+ Current version of packages make my system unusable at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).
  
  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
-   Installed: 4:5.5.5.2-0ubuntu1
-   Candidate: 4:5.5.5.2-0ubuntu1
-   Version table:
-  *** 4:5.5.5.2-0ubuntu1 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 4:5.5.5.2-0ubuntu1
+   Candidate: 4:5.5.5.2-0ubuntu1
+   Version table:
+  *** 4:5.5.5.2-0ubuntu1 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  nvidia-304:
-   Installed: 304.132-0ubuntu0.16.04.2
-   Candidate: 304.132-0ubuntu0.16.04.2
-   Version table:
-  *** 304.132-0ubuntu0.16.04.2 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
- 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
-  304.131-0ubuntu3 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
+   Installed: 304.132-0ubuntu0.16.04.2
+   Candidate: 304.132-0ubuntu0.16.04.2
+   Version table:
+  *** 304.132-0ubuntu0.16.04.2 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
+ 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
+  304.131-0ubuntu3 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
-   Installed: 304.132-0ubuntu0.16.04.2
-   Candidate: 304.132-0ubuntu0.16.04.2
-   Version table:
-  *** 304.132-0ubuntu0.16.04.2 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
- 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
-  304.131-0ubuntu3 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
+   Installed: 304.132-0ubuntu0.16.04.2
+   Candidate: 304.132-0ubuntu0.16.04.2
+   Version table:
+  *** 304.132-0ubuntu0.16.04.2 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
+ 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
+  304.131-0ubuntu3 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
-   Installed: 361.42-0ubuntu1
-   Candidate: 361.42-0ubuntu1
-   Version table:
-  *** 361.42-0ubuntu1 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+   Installed: 361.42-0ubuntu1
+   Candidate: 361.42-0ubuntu1
+   Version table:
+  *** 361.42-0ubuntu1 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  
  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).
  
  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
-  qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
-  QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
-  

[Desktop-packages] [Bug 1641264] Re: libreoffice crashes on startup when using OpenGL rendering and proprietary nvidia driver.

[b]

I reproduced this bug on two different xenial machines running nvidia
304.131-0ubuntu3 (legacy) and 340.98-0ubuntu0.16.0

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

Title:
  libreoffice crashes on startup when using OpenGL rendering and
  proprietary nvidia driver.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I noticed that Libreoffice was rendering very slow (I can see each
  menu option drawn) so I tried using OpenGL rendering, which causes
  libreoffice to crash immediately on start-up.

  I confirm that OpenGL is working fine:

  $ glxinfo | head
  name of display: :0.0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4

  I'm able to use glxgears and other apps like djv_view with fast
  rendering.

  I've attached the gdb trace resulting from the crash with debug
  symbols, following is an except:

  Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  #0  0x in ?? ()
  #1  0x768e96f7 in OpenGLContext::AcquireFramebuffer (this=0x128f600, 
rTe
  xture=...) at 
/build/libreoffice-OypX7x/libreoffice-5.1.4/vcl/source/opengl/Open
  GLContext.cxx:1773

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 11 18:45:52 2016
  InstallationDate: Installed on 2010-11-05 (2198 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-11-02 (9 days ago)

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

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

[Desktop-packages] [Bug 1642001] [NEW] uim-qt5 check is broken

[Vsevolod Velichko]

Public bug reported:

XIM support check for Qt5 in UIM is broken — it uses the same paths as for Qt4, 
but they've been changed.
It's already fixed in Debian (0.29-1.2), so the package should probably be just 
reimported.

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

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

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  New

Bug description:
  XIM support check for Qt5 in UIM is broken — it uses the same paths as for 
Qt4, but they've been changed.
  It's already fixed in Debian (0.29-1.2), so the package should probably be 
just reimported.

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

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

[Desktop-packages] [Bug 1639298] Re: package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

[Alberto Salvia Novella]

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

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

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

Title:
  package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  errorenell'aggiornamento automatico

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcuda1-331-updates 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] È una 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.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  4 17:34:34 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu4
   libcuda1-340 340.96-0ubuntu3.16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: 2016-05-21 12:31:16,114 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-43-generic, i686: installed
   bbswitch, 0.8, 4.4.0-46-generic, i686: installed
   nvidia-304, 304.132, 4.4.0-46-generic, i686: installed
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2011-06-15 (1969 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=df47aabd-4975-43d0-847e-c681ee20576f ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-340
  Title: package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to xenial on 2016-05-21 (167 days ago)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Nov  4 17:14:38 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Alberto Salvia Novella]

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: plasma-workspace (Ubuntu)
   Importance: Medium => Critical

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
Installed: 4:5.5.5.2-0ubuntu1
Candidate: 4:5.5.5.2-0ubuntu1
Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
Installed: 361.42-0ubuntu1
Candidate: 361.42-0ubuntu1
Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1641740] Re: gnome-calendar needs an Ubuntu-style title bar

[Sebastien Bacher]

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  gnome-calendar needs an Ubuntu-style title bar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  On both 16.10 (Yakkety) and 17.04 (Zesty), gnome-calendar has no
  Ubuntu-style title bar displaying the name of the program.  So it
  looks inconsistent with other applications on the Ubuntu desktop.
  What's more, if I set the option "Show the menus for a window" to "In
  the window's title bar" in the Appearance control panel, then the top-
  level menu in gnome-calendar is no longer available at all.

  Since gnome-calendar is in main, it should be patched to have an
  Ubuntu title bar, just like other GNOME applications.

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

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

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

[Alberto Salvia Novella]

If you are experiencing this bug after upgrading the package, please set
status back to "confirmed".

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

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

Title:
  Nautilus does not start

Status in nautilus package in Ubuntu:
  Fix Released

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

  
  lotuspsychje@R00TBOOK:~$ nautilus

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

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

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

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

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

  
  gksu nautilus opens nautilus, but also with an error:

  
  lotuspsychje@R00TBOOK:~$ gksu nautilus

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

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

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

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

[Desktop-packages] [Bug 1591157] Re: webbrowser-app does not honour scale setting on HiDPI display

[Alberto Salvia Novella]

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided => High

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

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

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

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

Title:
  webbrowser-app does not honour scale setting on HiDPI display

Status in One Hundred Papercuts:
  Confirmed
Status in Oxide:
  Invalid
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The attached screenshot should say it all, showing it in comparison
  with Firefox and, indeed, the rest of the Unity desktop.

  Basically, on a 4K display, with a native resolution of 3840x2160, but
  with the scaling factor set to 2, and Scale all window contents set
  on, *most* of the unity desktop these days respects this; it nearly
  all works.

  webbrowser-app seems to have no awareness of it at all, and thus its
  windows show up tiny.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 10 12:55:30 2016
  InstallationDate: Installed on 2016-03-30 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

[Brian Murray]

** No longer affects: ubuntu-release-upgrader (Ubuntu)

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in pm-utils package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1641985] [NEW] Lexmark E232 printer when printing pdf or html, first time prints ok, then on second print request, prints gobbledygook

[Stubuntu]

Public bug reported:

1. Kubuntu 16.10; KDE Frameworks Version 5.26.0; Qt Version 5.6.1; Kernel 
4.8.0-27-generic; 64-bit
2. Cups printer driver for Lexmark E238
3. Expected to be able to print several PDF or Html web pages with no problems
4. Prints the first document fine.  When I print the second document I get 
multiple pages of gobbldy-gook. Gobbledy-gook continues until I un-plug the 
printer and plug it in again.
I used the lpadmin commands as listed in the Ubuntu Wiki/debugging printer 
problems section 12,2 and 12, 3. Neither fixed the problem.  Note: I have Mint, 
Ubuntu, and Debian installed on this computer and the command [lpadmin -p 
 -o usb-no-reattache-default=true] fixes the problem in each of those 
OS's. 
This is only a problem with my Lexmark E232 printer.  The Brother printer works 
fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cups 2.2.0-2
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Nov 15 10:30:58 2016
InstallationDate: Installed on 2016-10-08 (38 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
Lpstat:
 device for Lexmark__Lexmark_E232: usb://Lexmark/E232?serial=722K51B
 device for Lexmark_Lexmark_E232: ///dev/null
 device for MFC-495CW: usb://Brother/MFC-495CW?serial=BROH9F322671
 device for PDF: cups-pdf:/
MachineType: ASUSTeK COMPUTER INC. CM1745
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Lexmark__Lexmark_E232.ppd', '/etc/cups/ppd/MFC-495CW.ppd', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Lexmark__Lexmark_E232.ppd: Permission denied
 grep: /etc/cups/ppd/MFC-495CW.ppd: Permission denied
 grep: /etc/cups/ppd/PDF.ppd: Permission denied
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9751167b-fcd3-4623-881c-2a97e840eadf ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5007
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM1745
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5007:bd08/27/2012:svnASUSTeKCOMPUTERINC.:pnCM1745:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM1745:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: CM1745
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apparmor apport-bug yakkety

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

Title:
  Lexmark E232 printer when printing pdf or html, first time prints ok,
  then on second print request, prints gobbledygook

Status in cups package in Ubuntu:
  New

Bug description:
  1. Kubuntu 16.10; KDE Frameworks Version 5.26.0; Qt Version 5.6.1; Kernel 
4.8.0-27-generic; 64-bit
  2. Cups printer driver for Lexmark E238
  3. Expected to be able to print several PDF or Html web pages with no problems
  4. Prints the first document fine.  When I print the second document I get 
multiple pages of gobbldy-gook. Gobbledy-gook continues until I un-plug the 
printer and plug it in again.
  I used the lpadmin commands as listed in the Ubuntu Wiki/debugging printer 
problems section 12,2 and 12, 3. Neither fixed the problem.  Note: I have Mint, 
Ubuntu, and Debian installed on this computer and the command [lpadmin -p 
 -o usb-no-reattache-default=true] fixes the problem in each of those 
OS's. 
  This is only a problem with my Lexmark E232 printer.  The Brother printer 
works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 15 10:30:58 2016
  InstallationDate: Installed on 2016-10-08 (38 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Lpstat:
   device for Lexmark__Lexmark_E232: usb://Lexmark/E232?serial=722K51B
   device for Lexmark_Lexmark_E232: ///dev/null
   device for MFC-495CW: usb://Brother/MFC-495CW?serial=BROH9F322671
   device for PDF: cups-pdf:/
  MachineType: ASUSTeK COMPUTER INC. CM1745
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Lexmark__Lexmark_E232.ppd', '/etc/cups/ppd/MFC-495CW.ppd', 
'/etc/cups/ppd/PDF.ppd'] failed 

[Desktop-packages] [Bug 1641936] Re: button label doesn't change after installation

[Sebastien Bacher]

** Summary changed:

- Softwarecenter view not installed
+ button label doesn't change after installation

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

Title:
  button label doesn't change after installation

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Hello

  I have new installed 16.10 32 bit. Ubuntu is up to date.

  I have installed synaptik-pakage-manager. Istallation has finish.

  I can not see in the window, this is finish?

  See the picture: Install is finish?

  Best Regards

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Martin]

Sorry, I changed the status by accident, it's still not released.

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted

[henrythung]

The problem still exists.
Using drag and drop, I can select the private key file, but get ""Unencrypted 
private keys are insecure" message, and unable to click "connect" button 
(inactive).

Any workaround yet?

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

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG

[Launchpad Bug Tracker]

This bug was fixed in the package gnutls28 - 3.5.6-4ubuntu1

---
gnutls28 (3.5.6-4ubuntu1) zesty; urgency=medium

  * Merge with Debian.  Remaining changes:
- debian/patches/disable_global_init_override_test.patch: disable failing
  test.
- debian/patches/add-openssl-test-link.patch: add link for libssl
  * New upstream version avoids getrandom() at initialization which caused
NetworkManager to hang at boot. (LP: #1622893)

gnutls28 (3.5.6-4) unstable; urgency=medium

  * Pull 40_01_sockets-only-use-gnutls_bye-on-a-valid-socket-sessio.patch
   40_02_gnutls-cli-debug-terminate-sessions-which-cannot-be-.patch from
   upstream git master. The latter fixes a gnutls-cli-debug segfault.
   Closes: #844061

gnutls28 (3.5.6-2) unstable; urgency=low

  * Upload to unstable.
  * Bump libtasn1-6-dev b-d to >= 4.9 to support OIDs with elements that are
longer than 32-bits. (Upstream GIT commit
fcdb461e935dbdc0892241a35be7499116f22a67).

gnutls28 (3.5.6-1) experimental; urgency=low

  * New upstream version.
+ Drop superfluous patches (40_gnutls_certificate_set_key_apifixup.diff
  41_Reverted-the-behavior-of-sending-a-status-request-ex.patch).
+ Update symbol file.

gnutls28 (3.5.5-6) unstable; urgency=medium

  * Upload to unstable.

gnutls28 (3.5.5-5) experimental; urgency=medium

  * 41_Reverted-the-behavior-of-sending-a-status-request-ex.patch from
https://gitlab.com/gnutls/gnutls/merge_requests/128 - Fix compatibility
issue with GnuTLS 3.3 clients. Closes: #841723
  * Bump symbol dependency info for multiple
gnutls_certificate_(set|get)_*_key* functions. If
%GNUTLS_CERTIFICATE_API_V2 is set these functions will return a
non-negative return code on success instead of 0 for success and negative
numbers for failure.
  * Add b-d on openssl (for testsuite).

gnutls28 (3.5.5-4) unstable; urgency=medium

  * Upload to unstable.
  * Refresh 40_gnutls_certificate_set_key_apifixup.diff from master branch.

gnutls28 (3.5.5-3) experimental; urgency=medium

  * 40_gnutls_certificate_set_key_apifixup.diff: Fix ABI breakage introduced
in 3.5.5.

gnutls28 (3.5.5-2) unstable; urgency=medium

  * Upload to unstable.

gnutls28 (3.5.5-1) experimental; urgency=medium

  * New upstream version.
+ Update symbol file.

gnutls28 (3.5.4-2) unstable; urgency=medium

  * Upload to unstable.

gnutls28 (3.5.4-1) experimental; urgency=medium

  * New upstream version.
+ Drop superfluous patches:
  35_gnutls-cli-print-Handshake-was-completed.patch
  36_gnutls-cli-fixed-the-behavior-when-starttls-or-start.patch
  37_openssl-format-fix-from-openconnect.patch
  39_ocsptool-corrected-bug-in-session-establishment.patch
  40_ocsp-corrected-the-comparison-of-the-serial-size-in-.patch
  45_01-tests-enhance-the-DTLS-window-unit-test-to-account-f.patch
  45_02-dtls-ensure-that-the-DTLS-window-doesn-t-get-stalled.patch
  45_03-tests-mini-dtls-record-modified-expected-order-to-ac.patch
  45_04-Import-DTLS-sliding-window-validation-from-OpenConne.patch
+ Update symbol file.
  * Add b-d on softhsm2 for pkcs11 tests.

 -- Martin Pitt   Mon, 14 Nov 2016 12:47:23
+0100

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

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

Title:
  NetworkManager takes very long to start, or times out, blocked on RNG

Status in Auto Package Testing:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager package in Debian:
  Fix Released

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1641929] Re: Many HTTPS sites not working in chroium NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

[Launchpad Bug Tracker]

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

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  Many HTTPS sites not working in chroium
  NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Geting the error like this :

  Your connection is not private

  Attackers might be trying to steal your information from mail.ru (for 
example, passwords, messages, or credit cards). 
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
Automatically report details of possible security incidents to Google. 
Privacy policy
  ReloadHIDE ADVANCED
  mail.ru normally uses encryption to protect your information. When Chromium 
tried to connect to mail.ru this time, the website sent back unusual and 
incorrect credentials. This may happen when an attacker is trying to pretend to 
be mail.ru, or a Wi-Fi sign-in screen has interrupted the connection. Your 
information is still secure because Chromium stopped the connection before any 
data was exchanged.

  You cannot visit mail.ru right now because the website uses HSTS.
  Network errors and attacks are usually temporary, so this page will
  probably work later.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov 15 14:53:46 2016
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-07-23 (845 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  InstalledPlugins:
   
  Load-Avg-1min: 0.81
  Load-Processes-Running-Percent:   0.2%
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770T-ES3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=cef88176-7e1d-4b3f-a03c-10907c2e7cd1 ro quiet splash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (170 days ago)
  dmi.bios.date: 08/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4a
  dmi.board.name: GA-MA770T-ES3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4a:bd08/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-ES3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-ES3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770T-ES3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-05-28T21:42:26.756092

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

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

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

[Richard Andreu]

Fixed for me after sudo apt-get update && sudo apt-get upgrade and a
reboot

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

Title:
  Nautilus does not start

Status in nautilus package in Ubuntu:
  Confirmed

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

  
  lotuspsychje@R00TBOOK:~$ nautilus

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

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

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

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

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

  
  gksu nautilus opens nautilus, but also with an error:

  
  lotuspsychje@R00TBOOK:~$ gksu nautilus

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

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

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

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

[Desktop-packages] [Bug 256876] Re: MathType formulas messed up and not converted

[Abe]

open office doesn't display math equations in my word document, it
leaves it as blank and sometimes has weird characters like a box with
little numbers inside..not good to use..

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

Title:
  MathType formulas messed up and not converted

Status in LibreOffice:
  Fix Released
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  OpenOffice Writer does not show and convert MathType equations
  correctly. When the .doc file containing  MathType 5 formulas is
  opened in OO, all symbols of integrals, derivatives, sums etc. are
  missed or substituted by funny characters. As a result the formulas
  are messed up completely. The formulas are not converted to OO Math,
  but shown as figures (not editable) even if "convert math from/to
  MathType" option is selected.

  This bug seems to be ubuntu-specific. Original bug sent to OO team was not 
reproduced (http://www.mail-archive.com/allbugs@openoffice.org/msg396313.html). 
However, it was confirmed in Ubuntu 8.04 and 8.10alpha, but not in Mandriva 
Spring (http://ubuntuforums.org/showthread.php?t=872833).
  The bug exists even when the deb package provided on the OO.o website is used 
instead of the ubuntu repos version.

  This bug is really critical for people, who exchange documents with
  formulas with collaborators using MSWord+MathType.

  The test file can be found in original bug report (http://www.mail-
  archive.com/allb...@openoffice.org/msg396313.html).

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

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

[Desktop-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Karl-Philipp Richter]

Just now have `unity-panel-service` consuming 9.7 GB of RAM on Ubuntu
16.10. Do you want another report or an `apport-collect`?

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in firefox source package in Xenial:
  Incomplete
Status in hud source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

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

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[lothar4ever]

Steps i did to solve this:

1. sudo apt-get install nvidia-304=304.131-0ubuntu3
(it will downgrade to 131)
2. sudo apt-mark hold nvidia-304
(it will prevent future automatic updates)

I don't know if in the future it will be a problem not having it
updated, but for now i can work like this.

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
Installed: 4:5.5.5.2-0ubuntu1
Candidate: 4:5.5.5.2-0ubuntu1
Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
Installed: 361.42-0ubuntu1
Candidate: 361.42-0ubuntu1
Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Sebastien Bacher]

k, closing the bug then, feel free to post a comment once you figure out
what the problem is/was though

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
Installed: 4:5.5.5.2-0ubuntu1
Candidate: 4:5.5.5.2-0ubuntu1
Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
Installed: 361.42-0ubuntu1
Candidate: 361.42-0ubuntu1
Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Veress Krisztián]

1. Fekete nvidia-304.
sudo apt remove --purge nvidia-304

2. Download nvidia-304.131.0ubuntu3.deb
3. Install nvidia driver
sudo dpkg -i nvidia-304.131.0ubuntu3
deb
4. Reboot

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
Installed: 4:5.5.5.2-0ubuntu1
Candidate: 4:5.5.5.2-0ubuntu1
Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
Installed: 361.42-0ubuntu1
Candidate: 361.42-0ubuntu1
Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Launchpad Bug Tracker]

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

** Changed in: plasma-workspace (Ubuntu)
   Status: New => Confirmed

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
Installed: 4:5.5.5.2-0ubuntu1
Candidate: 4:5.5.5.2-0ubuntu1
Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
Installed: 304.132-0ubuntu0.16.04.2
Candidate: 304.132-0ubuntu0.16.04.2
Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
Installed: 361.42-0ubuntu1
Candidate: 361.42-0ubuntu1
Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off

[Cristian Klein]

Backport from PulseAudio 9.0:
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

** Patch added: 
"0102-switch-on-port-available-prefer-ports-that-have-been.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+attachment/422/+files/0102-switch-on-port-available-prefer-ports-that-have-been.patch

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

[Desktop-packages] [Bug 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off

[Cristian Klein]

I added the quilt patches that need to be added on top of the current
xenial-proposed. (Sorry if this is not the best way to present them, my
"how to contribute to Ubuntu" is a bit rusty.)

I already tested them as follows:

(1) Play some music through speakers connected through an HDMI display.

(2) type `xset dpms force off`

(3) Move mouse to bring screen back up.

Before patch: music plays in internal speaker, even after display wakes
up

After patch: music plays in HDMI speaker after display wakes up

Let me know if I can somehow help to push this into xenial-proposed.

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

[Desktop-packages] [Bug 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off

[Cristian Klein]

This patch needs to be refreshed, due to the previous two patches.

** Patch added: "0203-card-Add-hook-before-profile-changes.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+attachment/423/+files/0203-card-Add-hook-before-profile-changes.patch

** Tags added: patch patch-rejected-upstream

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

[Desktop-packages] [Bug 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off

[Cristian Klein]

Backport from PulseAudio 9.0:
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09

** Patch added: "0101-card-add-preferred-input-output-port.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+attachment/421/+files/0101-card-add-preferred-input-output-port.patch

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

[Desktop-packages] [Bug 1641954] [NEW] Output switches from HDMI speakers to internal speakers on DPMS off

[Cristian Klein]

Public bug reported:

PulseAudio 8.0 includes a well-known user-experience regression: Its new
auto-routing algorithm tries to switch to another output, as soon as the
active output gets disconnected. This leads to the following bad user
experience:

(1) Alice listens to music on her speakers, which are connected to the
screen, which is connected through HDMI to the computer.

(2) Alice leaves the computer, the screen gets suspended (DPMS off).

(3) PulseAudio sees that the HDMI output got disconnected (although only
for a short interval) and switches to internal speaker.

(4) Alice returns to the computer but finds that the music is now
playing through the internal speakers.

(5) Alice can switch the output to the HDMI speakers manually, but the
above user experience bug will reoccur when she leaves the computer
again.

This is a well-known upstream bug that was fixed in PulseAudio 9.0. Due
to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is desirable
to backport this fix to PulseAudio 8.0, so that all LTS users have
better experience. Upstream said they would not do this and that I
should report this to Ubuntu directly.

Other information:
* Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
* Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
* Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

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

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

[Desktop-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+2.0 - 2.24.31-1ubuntu1

---
gtk+2.0 (2.24.31-1ubuntu1) zesty; urgency=low

  * Merge with Debian unstable.  Remaining changes:
- d/libgtk2.0-0.symbols: update symbols file.
- d/libgtk2.0-dev.manpages: add gtk-builder-convert.1 manpage.
- d/rules: enable manpage.
- d/update-icon-caches: run with "--include-image-data" flag.
- add Ubuntu patches:
  + debian/patches/012_ubuntu-set-grab-add.patch
- Added ubuntu_gtk_widget_set_has_grab so we can grab sliders and
  things in menus, needed by ido
  + debian/patches/062_dnd_menubar.patch:
- Allow click on menubars for dnd
  + debian/patches/063_treeview_almost_fixed.patch:
- Add an ubuntu-almost-fixed-height-mode property, (required for
  software-center)
  + debian/patches/071_no_offscreen_widgets_grabbing.patch:
- Don't let offscreen widgets do grabbing
  + debian/patches/090_logging_file_saves.patch:
- improve the logging of saved files
  + debian/patches/092_default_to_xdg_document_dir.patch:
- Use $XDG_DOCUMENTS_DIR as default directory rather than the home
  directory for the 'Print to File' function.
  + debian/patches/093_gtk3_gtkimage_fallbacks_use.patch:
- Backported gtk3 patch to add a "use-fallback" property to GtkImage,
  using it "icon-name and GIcon type of GtkImages can use automatic
  fallback names.", it will be useful for the indicator stack
  + debian/patches/095_git_menus_scrolling.patch:
- backported gtk3 commit to fix menu scrolling issues
  + debian/patches/096_git_gtkprintsettings.patch:
- upstream git commit backported from the gtk3 serie, don't ignore the
  gtkprintsettings resolution settings
  + debian/patches/097_statusicon_image_fallback.patch: Make GtkStatusIcon
images use fallbacks by default if the property is available.
  + debian/patches/098_multiarch_module_path.patch:
- Fallback to the pre-multiarch directory for compatibility
  + debian/patches/099_printer_filename_fix.patch
- Fix to the print dialog for print to file, make sure a non-hidden 
filename
  is the default
  + debian/patches/100_overlay_scrollbar_loading.patch
- support for dynamically loading overlay scrollbars
  + debian/patches/gtk-shell-shows-menubar.patch:
- list gtk-shell-shows-menubar setting, that's required to have the 
local
  menubars hidding under unity in favor of the unity ones,
  + debian/patches/print-dialog-show-options-of-remote-dnssd-printers.patch:
- Make printing on remote DNS-SD/Bonjour-shared printers work
  + debian/patches/backport_search_printer_location.patch
-  The list of printers should be searchable/sortable
  + debian/patches/menubar_toolbar_dragging.patch:
- Allow windows to be dragged using blank spaces in the toolbar as
  well as the menubar
  + debian/patches/use-secrets-service-for-cups-auth_info.patch
  * Fixes issue with GtkEntry causing applications to crash (LP: #1576424)

gtk+2.0 (2.24.31-1) unstable; urgency=medium

  * New upstream release.
  * Drop obsolete maintainer scripts which cleaned up the /usr/share/doc
symlinks.
  * Refresh patches. Drop the ones which have been merged upstream.
  * When linking against libgail18, automatically generate a dependency on
libgail-common. This was originally achieved via a .shlibs file but since
we use a .symbols file nowadays, move this over there.
  * Remove an old shlibs.local hack which doesn't seem necessary anymore.
  * Use idiomatic variables from default.mk dpkg include.
Bump Build-Depends on dpkg-dev to (>= 1.16.1).

 -- Iain Lane   Thu, 10 Nov 2016 18:10:52 +

** Changed in: gtk+2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  In Progress
Status in gtk+2.0 source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without 

[Desktop-packages] [Bug 1615602] Re: IRC message truncation

[Marc Deslauriers]

Thanks for the debdiff.

For this to be acceptable as an SRU for trusty, you need to prepare a
debdiff for the development release (zesty) first.

Also, please add the bug number to the changelog, and properly tag the
patch using these guidelines:

http://dep.debian.net/deps/dep3/

Thanks!

** Also affects: pidgin (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: pidgin (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: pidgin (Ubuntu Zesty)
   Importance: Low
   Status: New

** Also affects: pidgin (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

Title:
  IRC message truncation

Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin source package in Trusty:
  Confirmed
Status in pidgin source package in Xenial:
  Confirmed
Status in pidgin source package in Yakkety:
  Confirmed
Status in pidgin source package in Zesty:
  Confirmed

Bug description:
  This was upstream bug (https://developer.pidgin.im/ticket/4753) that
  recently has been fixed.

  I propose to add the patch to the offician ubuntu package so that
  users can get this fix before the new release, since the bug is quite
  irritating.

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

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

[Desktop-packages] [Bug 1627769] Re: limits.conf not applied

[Ewan Leith]

Still seems to be an issue for me, logging into the terminal I have the
modified ulimit values, but not in a lightdm session

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

Title:
  limits.conf not applied

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1641949] [NEW] Paper jam when the printer is shared in xenial

[smurf]

Public bug reported:

I made a fresh install from scratch of Xenial Xerus 16.04 Mate, my printer is a 
Brother HL-2140.
The printer was working well until Y decided to share it, because I have other 
two pcs that use the printer.
So I opened the printer manager from the menu, I checked the "Share" box in the 
printer window, then I opened the "Server Configuration" and I checked the 
"Publish shared printers" box and the "Allow printing from Internet" box.
Starting from that moment my printer is no more able to print because each time 
that prints one sheet automatically collect a second sheet (as if it was the 
same sheet, probably an error in paper size) and obviously an error occurs and 
everything get blocked.
Unfortunately even if I unpublished and unshared the printer, the error persist 
so now I can't print, I suspect that the Server is the guilty and I wish to try 
to "Desconnect" the server to prove it, but I don't know how to do it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Nov 15 08:25:23 2016
InstallationDate: Installed on 2016-11-04 (10 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lpstat:
 device for Deskjet_3520: hp:/net/Deskjet_3520_series?ip=10.21.39.105
 device for HL-2140-series: usb://Brother/HL-2140%20series?serial=G8J723823
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_3520.ppd', 
'/etc/cups/ppd/HL-2140-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Deskjet_3520.ppd: Permission denied
 grep: /etc/cups/ppd/HL-2140-series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=d99fe658-6f6c-472d-a1d0-05507c89d3c5 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A55M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd03/29/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA55M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1641949

Title:
  Paper jam when the printer is shared in xenial

Status in cups package in Ubuntu:
  New

Bug description:
  I made a fresh install from scratch of Xenial Xerus 16.04 Mate, my printer is 
a Brother HL-2140.
  The printer was working well until Y decided to share it, because I have 
other two pcs that use the printer.
  So I opened the printer manager from the menu, I checked the "Share" box in 
the printer window, then I opened the "Server Configuration" and I checked the 
"Publish shared printers" box and the "Allow printing from Internet" box.
  Starting from that moment my printer is no more able to print because each 
time that prints one sheet automatically collect a second sheet (as if it was 
the same sheet, probably an error in paper size) and obviously an error occurs 
and everything get blocked.
  Unfortunately even if I unpublished and unshared the printer, the error 
persist so now I can't print, I suspect that the Server is the guilty and I 
wish to try to "Desconnect" the server to prove it, but I don't know how to do 
it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Nov 15 08:25:23 2016
  InstallationDate: Installed on 2016-11-04 (10 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat:
   device for Deskjet_3520: hp:/net/Deskjet_3520_series?ip=10.21.39.105
   device for HL-2140-series: usb://Brother/HL-2140%20series?serial=G8J723823
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_3520.ppd', '/etc/cups/ppd/HL-2140-series.ppd'] failed 
with exit code 2: grep: /etc/cups/ppd/Deskjet_3520.ppd: Permission denied
   grep: 

Re: [Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Chad Miller]

That PPA has a very stern warning on it. Ignore it at your peril.


On Tue, Nov 15, 2016 at 5:32 AM, Marc Pignat <1641...@bugs.launchpad.net>
wrote:

> This PPA does the job, thank you!
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1641380
>
> Title:
>   chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
>   certs
>
> Status in chromium-browser package in Ubuntu:
>   Fix Committed
>
> Bug description:
>   Chromium browser in xenial no longer trusts Symantec issued
>   certificates. See [1].
>
>   1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177
>
>   Ubuntu release: 16.04
>   chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+
> subscriptions
>

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641929] Re: Many HTTPS sites not working in chroium NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

[Chad Miller]

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

** This bug has been marked a duplicate of bug 1641380
   chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

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

Title:
  Many HTTPS sites not working in chroium
  NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Geting the error like this :

  Your connection is not private

  Attackers might be trying to steal your information from mail.ru (for 
example, passwords, messages, or credit cards). 
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
Automatically report details of possible security incidents to Google. 
Privacy policy
  ReloadHIDE ADVANCED
  mail.ru normally uses encryption to protect your information. When Chromium 
tried to connect to mail.ru this time, the website sent back unusual and 
incorrect credentials. This may happen when an attacker is trying to pretend to 
be mail.ru, or a Wi-Fi sign-in screen has interrupted the connection. Your 
information is still secure because Chromium stopped the connection before any 
data was exchanged.

  You cannot visit mail.ru right now because the website uses HSTS.
  Network errors and attacks are usually temporary, so this page will
  probably work later.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov 15 14:53:46 2016
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-07-23 (845 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  InstalledPlugins:
   
  Load-Avg-1min: 0.81
  Load-Processes-Running-Percent:   0.2%
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770T-ES3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=cef88176-7e1d-4b3f-a03c-10907c2e7cd1 ro quiet splash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (170 days ago)
  dmi.bios.date: 08/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4a
  dmi.board.name: GA-MA770T-ES3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4a:bd08/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-ES3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-ES3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770T-ES3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-05-28T21:42:26.756092

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

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

[Desktop-packages] [Bug 1640958] Re: Can not update Ubuntu

[Matthew Paul Thomas]

** Package changed: software-center (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)

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

Title:
  Can not update Ubuntu

Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I've tried to update Ubuntu multiple time and it just won't work. I go
  into the Ubuntu Software Center and see theres an update. So what I
  did was click install, then left it alone for about half and hour.
  When I looked back at it it's at the same place as before -- so I'm
  like "hey, maybe it just takes a long time". 2 hours later and now I
  definitely know theres a problem, cuz I got a very fast laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.17
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Nov 10 18:17:34 2016
  InstallationDate: Installed on 2016-10-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-11-10T15:24:41.536481

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

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

[Desktop-packages] [Bug 1641892] Re: symantec certifcate problem does not allow to access some sites

[Launchpad Bug Tracker]

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

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  symantec certifcate problem does not allow to access some sites

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  problem is described here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  and here:
  
https://security.googleblog.com/2015/10/sustaining-digital-certificate-security.html

  chrome 54 solves it.

  This prohibites to visit sites that use such kind of certificates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   edid-base64: 
AP///wBMLWgIQk1UWiMVAQMOMBt4Kq1Bo1dSoScNUFS/74BxT4EAgUCBgJUAlQ+pQLMAAjqAGHE4LUBYLEUA3QwRAAAe/QA4Sx5REQAKICAgICAg/ABTTVMyMkExMDAKICAg/wBIOUxCODEwNTE3CiAgAD4=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 
1280x960 1280x800 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wBMg0ZBAAAXAQOAIhN4CnEFk1VXjykgUFQBAQEBAQEBAQEBAQEBAQEBQRxWoFAAFjAwICUAWMIQAAAZDwAAACBSAxUA/gBTQU1TVU5HCiAgICAg/gAxNTZBVDM1LVQwMQogAHo=
   dpms: On
   modes: 1366x768
   enabled: enabled
   status: connected
  Date: Tue Nov 15 10:43:15 2016
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-07-17 (486 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Load-Avg-1min: 2.29
  Load-Processes-Running-Percent:   0.1%
  MachineType: TOSHIBA SATELLITE L50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad9f2e07-12d4-4ca4-89fd-2c12d497cade ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (185 days ago)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-00H00UIT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE L50-B
  dmi.product.version: PSKTNE-00H00UIT
  dmi.sys.vendor: TOSHIBA
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1641936] Re: Softwarecenter view not installed

[Julian Andres Klode]

That's not apt related, but gnome-software.

** Package changed: apt (Ubuntu) => gnome-software (Ubuntu)

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

Title:
  Softwarecenter view not installed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Hello

  I have new installed 16.10 32 bit. Ubuntu is up to date.

  I have installed synaptik-pakage-manager. Istallation has finish.

  I can not see in the window, this is finish?

  See the picture: Install is finish?

  Best Regards

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

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

[Desktop-packages] [Bug 1641936] [NEW] Softwarecenter view not installed

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello

I have new installed 16.10 32 bit. Ubuntu is up to date.

I have installed synaptik-pakage-manager. Istallation has finish.

I can not see in the window, this is finish?

See the picture: Install is finish?

Best Regards

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

-- 
Softwarecenter view not installed
https://bugs.launchpad.net/bugs/1641936
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software 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 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

[Ubuntu Foundations Team Bug Bot]

** Tags added: xenial2yakkety

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in pm-utils package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1641841] Re: At startup shows the icon of the card reader

[Ubuntu Foundations Team Bug Bot]

The attachment "the panel unity" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  At startup shows the icon of the card reader

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  At startup shows the icon of the card reader, after you select "open
  in folder" opens in another instance of "folder shortcut on the panel
  unity". At the same time with this panel, unity displays the label
  stick. When you click on the shortcut of pendrive folder opens in a
  new instance "icon on the unity panel". Read more on the photo.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity-settings-daemon 15.04.1+16.10.20161003-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 15 11:33:30 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-fallback-mount-helper
  InstallationDate: Installed on 2015-08-27 (445 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-settings-daemon
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (27 days ago)

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

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

[Desktop-packages] [Bug 1641929] [NEW] Many HTTPS sites not working in chroium NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

[Nikolay Morozov]

Public bug reported:

Geting the error like this :

Your connection is not private

Attackers might be trying to steal your information from mail.ru (for example, 
passwords, messages, or credit cards). 
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
  Automatically report details of possible security incidents to Google. 
Privacy policy
ReloadHIDE ADVANCED
mail.ru normally uses encryption to protect your information. When Chromium 
tried to connect to mail.ru this time, the website sent back unusual and 
incorrect credentials. This may happen when an attacker is trying to pretend to 
be mail.ru, or a Wi-Fi sign-in screen has interrupted the connection. Your 
information is still secure because Chromium stopped the connection before any 
data was exchanged.

You cannot visit mail.ru right now because the website uses HSTS.
Network errors and attacks are usually temporary, so this page will
probably work later.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Nov 15 14:53:46 2016
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
 
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstallationDate: Installed on 2014-07-23 (845 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
InstalledPlugins:
 
Load-Avg-1min: 0.81
Load-Processes-Running-Percent:   0.2%
MachineType: Gigabyte Technology Co., Ltd. GA-MA770T-ES3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=cef88176-7e1d-4b3f-a03c-10907c2e7cd1 ro quiet splash
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to xenial on 2016-05-28 (170 days ago)
dmi.bios.date: 08/02/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4a
dmi.board.name: GA-MA770T-ES3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4a:bd08/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-ES3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-ES3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA770T-ES3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
etcconfigcpepperflashpluginnonfree:
 flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
 flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed 
-e "s/,/./g"`
 CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium-browser: [deleted]
mtime.conffile..etc.chromium-browser.default: 2016-05-28T21:42:26.756092

** Affects: chromium-browser (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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641929

Title:
  Many HTTPS sites not working in chroium
  NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Geting the error like this :

  Your connection is not private

  Attackers might be trying to steal your information from mail.ru (for 
example, passwords, messages, or credit cards). 
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
Automatically report details of possible security incidents to Google. 
Privacy policy
  ReloadHIDE ADVANCED
  mail.ru normally uses encryption to protect your information. When Chromium 
tried to connect to mail.ru this time, the website sent back unusual and 
incorrect credentials. This may happen when an attacker is trying to pretend to 
be mail.ru, or a Wi-Fi sign-in screen has interrupted the connection. Your 
information is still secure because Chromium stopped the connection before any 
data was exchanged.

  You cannot visit mail.ru right now because the website uses HSTS.
  Network errors and attacks are usually temporary, so this page will
  probably work later.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  

[Desktop-packages] [Bug 1641928] [NEW] "Unknown audio device" dialog pops up every time I plug in headphones

[Zoltan Kiss]

Public bug reported:

I used to use Ubuntu 15.10 for a long time and everything was fine. As
soon as I installed (clean install) Ubuntu 16.04 the dialog started
appearing every time I plugged in my earphones. Problem still present on
16.10.

-Saw this bug report 
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790
-In there someone posted a link to 
http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-on-newer-laptops/
-which encourages users to submit their own bug reports using ubuntu-bug audio 
in order to collect hw info, so I did.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  zoltan  F pulseaudio
 /dev/snd/controlC1:  zoltan  F pulseaudio
CurrentDesktop: Unity
Date: Tue Nov 15 11:48:15 2016
InstallationDate: Installed on 2016-10-15 (30 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [XPS 13 9343, Realtek ALC3263, Black Headphone Out, Left] Playback 
problem
UpgradeStatus: Upgraded to yakkety on 2016-10-23 (22 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  "Unknown audio device" dialog pops up every time I plug in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I used to use Ubuntu 15.10 for a long time and everything was fine. As
  soon as I installed (clean install) Ubuntu 16.04 the dialog started
  appearing every time I plugged in my earphones. Problem still present
  on 16.10.

  -Saw this bug report 
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790
  -In there someone posted a link to 
http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-on-newer-laptops/
  -which encourages users to submit their own bug reports using ubuntu-bug 
audio in order to collect hw info, so I did.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zoltan  F pulseaudio
   /dev/snd/controlC1:  zoltan  F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 15 11:48:15 2016
  InstallationDate: Installed on 2016-10-15 (30 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (22 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1297790] Re: "Unknown audio device" dialog pops up every time I plug in headphones

[Zoltan Kiss]

Updated to 16.10 when it came out and the issue is still present

** Tags added: yakkety

** Tags added: xenial

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

Title:
  "Unknown audio device" dialog pops up every time I plug in headphones

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I've got a combined headphone/headset socket on my Laptop. Every time
  I plug in my headphones, an "unknown audio device" dialog pops up
  asking whether I've plugged in headphones or a headset.  This is isn't
  a great user experience as my phone can auto-detect the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1949 F pulseaudio
   /dev/snd/controlC0:  mark   1949 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 26 11:03:29 2014
  InstallationDate: Installed on 2014-03-24 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Latitude E7440, Realtek ALC292, Green Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: DE004505
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: DE004505
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

[Ara Pulido]

What version of Ubuntu? What version of network manager? Has this been
tested in Zesty)

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

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

Title:
  The network indicator shows the wrong status

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , remove wireless connection
  Note : the issue can't be reproduced with wifi connection
  2.Enable/disable wifi function by hotkey the check wifi manager status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1641919] [NEW] hibernation has stopped working in 16.10 Yakkety Yak

[crysman]

Public bug reported:

After upgrading to 16.10 (from 16.04) hibernation has stopped working.
I've been using hibernation for years already without problems (with
some initial tuning).

I am talking about using "pm-hibernate"

There is a workaround to make it work I've described here:
http://askubuntu.com/a/849679/208566

Also, there are some warnings while updating initramfs, which had not been 
present before:

sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915


ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.8
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Tue Nov 15 12:19:19 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-06 (374 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
VarLogDistupgradeTermlog:

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

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade yakkety

** Also affects: pm-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in pm-utils package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

[Kent Lin]

** Also affects: network-manager-applet
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Importance: Critical => High

** Also affects: oem-priority/xenial
   Importance: Undecided
   Status: New

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

Title:
  The network indicator shows the wrong status

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , remove wireless connection
  Note : the issue can't be reproduced with wifi connection
  2.Enable/disable wifi function by hotkey the check wifi manager status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1641914] [NEW] Please backport two recent-manager patches

[Curaga]

Public bug reported:

https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b

Please apply/backport these two patches from the 3.22 branch. They fix a memory 
DOS, originally reported against mate-panel here:
https://github.com/mate-desktop/mate-panel/issues/479

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

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

Title:
  Please backport two recent-manager patches

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b

  Please apply/backport these two patches from the 3.22 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

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

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

[Desktop-packages] [Bug 1641912] [NEW] Please backport two recent-manager patches

[Curaga]

Public bug reported:

https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca

Please apply/backport these two patches from the 2.24 branch. They fix a memory 
DOS, originally reported against mate-panel here:
https://github.com/mate-desktop/mate-panel/issues/479

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

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

Title:
  Please backport two recent-manager patches

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca

  Please apply/backport these two patches from the 2.24 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

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

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

[Desktop-packages] [Bug 1581560] Re: system crash when attaching external display

[kay]

Why did you close the issue? I still have to power off my laptop instead
of suspending.

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

Title:
  system crash when attaching external display

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
  and reboots when I attach an external display.

  Process: 
  -  put laptop to sleep.
  - come into work the next day
  - open up laptop
  - plug in external display
  - observe bug

  Expected behavior: I can attach the external display
  Observed behavior: system shows black screen on both laptop and display and 
after a minute or two reboots.  Laptop drives external display fine after 
reboot.

  I ssh to the laptop from another machine and monitored
  /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors.  All I
  see in those files before the lockup is this, from Xorg.0.log:

  [ 34289.447] (II) intel(0): Enabled output DP1-8
  [ 34289.448] (II) intel(0): Enabled output DP1-1
  [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440
  [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 
0,
  (0, 0), rotation normal, reflection none

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 09:24:07 2016
  DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  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 2015-09-10 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BS0031US
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BS0031US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BS0031US
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  drirc:
   
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 13 09:04:56 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4669 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Marc Pignat]

This PPA does the job, thank you!

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer

[Natratchakorn Thaveekhanarat]

** Changed in: account-plugins
 Assignee: Alberto Mardegan (mardy) => (unassigned)

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  Fix Released
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in account-plugins package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released
Status in account-plugins source package in Quantal:
  Fix Released
Status in signon-plugin-oauth2 source package in Quantal:
  Fix Released
Status in account-plugins source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Fix Released
Status in signon-plugin-oauth2 source package in Trusty:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

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

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

[Desktop-packages] [Bug 1641892] Re: symantec certifcate problem does not allow to access some sites

[Olivier Dony (Odoo)]

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

** This bug has been marked a duplicate of bug 1641380
   chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

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

Title:
  symantec certifcate problem does not allow to access some sites

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  problem is described here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  and here:
  
https://security.googleblog.com/2015/10/sustaining-digital-certificate-security.html

  chrome 54 solves it.

  This prohibites to visit sites that use such kind of certificates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   edid-base64: 
AP///wBMLWgIQk1UWiMVAQMOMBt4Kq1Bo1dSoScNUFS/74BxT4EAgUCBgJUAlQ+pQLMAAjqAGHE4LUBYLEUA3QwRAAAe/QA4Sx5REQAKICAgICAg/ABTTVMyMkExMDAKICAg/wBIOUxCODEwNTE3CiAgAD4=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 
1280x960 1280x800 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wBMg0ZBAAAXAQOAIhN4CnEFk1VXjykgUFQBAQEBAQEBAQEBAQEBAQEBQRxWoFAAFjAwICUAWMIQAAAZDwAAACBSAxUA/gBTQU1TVU5HCiAgICAg/gAxNTZBVDM1LVQwMQogAHo=
   dpms: On
   modes: 1366x768
   enabled: enabled
   status: connected
  Date: Tue Nov 15 10:43:15 2016
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-07-17 (486 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Load-Avg-1min: 2.29
  Load-Processes-Running-Percent:   0.1%
  MachineType: TOSHIBA SATELLITE L50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad9f2e07-12d4-4ca4-89fd-2c12d497cade ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (185 days ago)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-00H00UIT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE L50-B
  dmi.product.version: PSKTNE-00H00UIT
  dmi.sys.vendor: TOSHIBA
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Peter Buri]

Until the package is not fixed you can use builds from
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641892] [NEW] symantec certifcate problem does not allow to access some sites

[Daniele Cruciani]

Public bug reported:

problem is described here:
https://bugs.chromium.org/p/chromium/issues/detail?id=664177

and here:
https://security.googleblog.com/2015/10/sustaining-digital-certificate-security.html

chrome 54 solves it.

This prohibites to visit sites that use such kind of certificates

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
DRM.card0-DP-1:
 edid-base64: 
AP///wBMLWgIQk1UWiMVAQMOMBt4Kq1Bo1dSoScNUFS/74BxT4EAgUCBgJUAlQ+pQLMAAjqAGHE4LUBYLEUA3QwRAAAe/QA4Sx5REQAKICAgICAg/ABTTVMyMkExMDAKICAg/wBIOUxCODEwNTE3CiAgAD4=
 dpms: On
 modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 
1280x960 1280x800 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 640x480 640x480 640x480 640x480 720x400
 enabled: enabled
 status: connected
DRM.card0-HDMI-A-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-eDP-1:
 edid-base64: 
AP///wBMg0ZBAAAXAQOAIhN4CnEFk1VXjykgUFQBAQEBAQEBAQEBAQEBAQEBQRxWoFAAFjAwICUAWMIQAAAZDwAAACBSAxUA/gBTQU1TVU5HCiAgICAg/gAxNTZBVDM1LVQwMQogAHo=
 dpms: On
 modes: 1366x768
 enabled: enabled
 status: connected
Date: Tue Nov 15 10:43:15 2016
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
 
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstallationDate: Installed on 2015-07-17 (486 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
Load-Avg-1min: 2.29
Load-Processes-Running-Percent:   0.1%
MachineType: TOSHIBA SATELLITE L50-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad9f2e07-12d4-4ca4-89fd-2c12d497cade ro noprompt persistent quiet 
splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to xenial on 2016-05-13 (185 days ago)
dmi.bios.date: 12/02/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 2.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-00H00UIT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE L50-B
dmi.product.version: PSKTNE-00H00UIT
dmi.sys.vendor: TOSHIBA
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "error in a well known site"
   
https://bugs.launchpad.net/bugs/1641892/+attachment/4777606/+files/Errore%20di%20privacy.png

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

Title:
  symantec certifcate problem does not allow to access some sites

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  problem is described here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  and here:
  
https://security.googleblog.com/2015/10/sustaining-digital-certificate-security.html

  chrome 54 solves it.

  This prohibites to visit sites that use such kind of certificates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   edid-base64: 
AP///wBMLWgIQk1UWiMVAQMOMBt4Kq1Bo1dSoScNUFS/74BxT4EAgUCBgJUAlQ+pQLMAAjqAGHE4LUBYLEUA3QwRAAAe/QA4Sx5REQAKICAgICAg/ABTTVMyMkExMDAKICAg/wBIOUxCODEwNTE3CiAgAD4=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 
1280x960 1280x800 1152x864 1024x768 1024x768 1024x768 832x624 

[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

[Cyrus Lien]

The issue already fixed, please help to pull the patch into ubuntu 
network-manager-applet package.
Thanks!

Upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=770218.


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

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

Title:
  The network indicator shows the wrong status

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

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , remove wireless connection
  Note : the issue can't be reproduced with wifi connection
  2.Enable/disable wifi function by hotkey the check wifi manager status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1641889] [NEW] The network indicator shows the wrong status

[Cyrus Lien]

Public bug reported:

[Summary] The network indicator shows the wrong status

[Reproduce Steps]
1.Boot into Ubuntu OS , remove wireless connection
Note : the issue can't be reproduced with wifi connection
2.Enable/disable wifi function by hotkey the check wifi manager status

[Results]
Expected: "Enable Wi-Fi" option should be OFF
Actual:"Enable Wi-Fi" option is ON

[Additional Information]
Product Name:Inspiron-7460
BIOS Version:1.0.0

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

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

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

Title:
  The network indicator shows the wrong status

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

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , remove wireless connection
  Note : the issue can't be reproduced with wifi connection
  2.Enable/disable wifi function by hotkey the check wifi manager status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Quentin Decaunes]

Good News =) Thanks
Any idea on ETA ?
Shouldn't be too long I think.

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641867] [NEW] GtkMenu: Submenu navigation triangle doesn't work

[Sam Douglas]

Public bug reported:

The navigation triangle code for keeping a submenu open when the mouse
is moving diagonally toward it is broken due to incorrect rounding.

This was reported upstream at:
https://bugzilla.gnome.org/show_bug.cgi?id=710388

The attached patch (also submitted upstream) rounds the cursor location
when calculating the navigation triangle bounds.

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

** Patch added: "Fix for navigation triangle bug"
   
https://bugs.launchpad.net/bugs/1641867/+attachment/4777560/+files/submenu_navigation_region_fix.patch

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

Title:
  GtkMenu: Submenu navigation triangle doesn't work

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The navigation triangle code for keeping a submenu open when the mouse
  is moving diagonally toward it is broken due to incorrect rounding.

  This was reported upstream at:
  https://bugzilla.gnome.org/show_bug.cgi?id=710388

  The attached patch (also submitted upstream) rounds the cursor
  location when calculating the navigation triangle bounds.

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

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