[Desktop-packages] [Bug 1640741] Re: ubuntu 17.04 gnome-software install button not working

[rahmadani]

** Changed in: ubuntu-gnome
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => rahmadani (rahmadani)

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

Title:
  ubuntu 17.04 gnome-software install button not working

Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  on ubuntu 17.04 gnome-software install button does nothing.
  try with different applications: UFRaw, Shutter, Entangle ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.2+git20161108.0.a58dfc7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:08:48 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-11-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1681031] [NEW] Copy/paste contents column wise between tables or within a table in LibreOffice-Writer turns gibberish.

[Anirbaan Biddyaniketan]

Public bug reported:

Copy/paste contents column wise between tables or within a table in
LibreOffice-Writer turns gibberish.

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

** Summary changed:

- Copy/paste contents columnwise between tables or within tables of 
LibreOffice-Writer turns gibberish.
+ Copy/paste contents column wise between tables or within tables of 
LibreOffice-Writer turns gibberish.

** Summary changed:

- Copy/paste contents column wise between tables or within tables of 
LibreOffice-Writer turns gibberish.
+ Copy/paste contents column wise between tables or within a table of 
LibreOffice-Writer turns gibberish.

** Summary changed:

- Copy/paste contents column wise between tables or within a table of 
LibreOffice-Writer turns gibberish.
+ Copy/paste contents column wise between tables or within a table in 
LibreOffice-Writer turns gibberish.

** Description changed:

- Copy/paste contents column wise between tables or within a table of
+ Copy/paste contents column wise between tables or within a table in
  LibreOffice-Writer turns gibberish.

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

Title:
  Copy/paste contents column wise between tables or within a table in
  LibreOffice-Writer turns gibberish.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Copy/paste contents column wise between tables or within a table in
  LibreOffice-Writer turns gibberish.

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

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

[Desktop-packages] [Bug 1681030] [NEW] LibreOffice-impress crashes while changing font or font color in a textbox

[Anirbaan Biddyaniketan]

Public bug reported:

LibreOffice-impress crashes while changing font or font color in a
textbox.

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

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

Title:
  LibreOffice-impress crashes while changing font or font color in a
  textbox

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice-impress crashes while changing font or font color in a
  textbox.

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

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

[Desktop-packages] [Bug 1681025] Re: dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd-timesyncd.service

[J.D.]

Please find the attached patch service that was used to delay the
network initialization so that it is not affected by the time-change by
systemd-timesyncd.service. This may not exactly be an acceptable
solution but demonstrates how equivalent changes can be performed to
arrive at the solution.

** Attachment added: "delayNetwork.service"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681025/+attachment/4857992/+files/delayNetwork.service

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

Title:
  dhclient fails to assign IP address during system boot inspite of
  valid DHCP Offer when time change is performed by systemd-
  timesyncd.service

Status in network-manager package in Ubuntu:
  New

Bug description:
  System Information:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Package Information:
  network-manager:
Installed: (none)
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  Expected Behavior:
  The system has one ethernet interface ens160 that is expected to be assigned 
an IPv4 address using DHCP as part of the bootup process so that services that 
depends on presence of IPv4 address do not fail to initialize during the boot 
process.

  Problem Behavior:
  The ethernet interface ens160 was UP but no IPv4 address was assigned inspite 
of correct response from the DHCP server, thereby causing the services that 
depends on presence of IPv4 address to fail during the boot process.

  Problem Details:
  The default 16.04.2 LTS server installed in a VMWare virtual machine running 
on SuperMicro server using ESXi 6 fails to obtain an IP address from a DHCP 
server during system startup when there is a simultaneous time change as 
evidenced by "systemd[1]: Time has been changed" entry in syslog. The system 
successfully obtains the IP address after significant delay (ranging from 2 - 5 
minutes) after system startup. 

  Note that the system has open-vmware-tools package and the VMWare
  tools settings are set to NOT synchronize the guest time, thereby
  eliminating any scope of interference from virtualization host (The
  host itself is set to use NTP synchronization and has correct timing).

  Wireshark was used to sniff the BOOTP messages. When system is
  rebooted, system sends a DHCP Release to the DHCP server. When system
  starts, it broadcasts a valid DHCP Discover to network and received a
  valid DHCP Offer from the network within 4 secs. Note that a "Time has
  been changed" log appears just before dhclient logs "No DHCPOFFERS
  received" in syslog. (The time appears to be moved ahead by around 6
  mins.)

  After about 4 minutes, system broadcasts a valid DHCP Discover to
  which DHCP server responds with DHCP Offer, system responds with DHCP
  Request and DHCP server responds with DHCP Ack and the system is
  assigned its IP address. The dhclient logs in syslog concurs with the
  wireshark trace:

  Apr  6 18:39:05 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 
255.255.255.255 port 67 interval 3 (xid=0x92322e17)
  Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 
255.255.255.255 port 67 interval 8 (xid=0x92322e17)
  Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPREQUEST of 192.168.1.161 on 
ens160 to 255.255.255.255 port 67 (xid=0x172e3292)
  Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPOFFER of 192.168.1.161 from 
192.168.1.1
  Apr  6 18:39:09 etCorgServer dhclient[1071]: DHCPACK of 192.168.1.161 from 
192.168.1.1
  Apr  6 18:39:09 etCorgServer dhclient[1071]: bound to 192.168.1.161 -- 
renewal in 33171 seconds.

  An attempt to release and reacquire the IP address after the system is
  up and running always succeeds immediately with the aforesaid "happy"
  usecase.

  Workaround Attempted:
  Turning off systemd-timesyncd.service always allows dhclient to immediately 
assign the IP address during the boot process. Turning it on leads to the above 
problem usecase with very high probability. Based on this observation, an 
assumption can be made that  the time synchronization happens to overlap the 
DHCP processing performed by dhclient. There is a time-change which causes the 
DHCP Offer sent by the DHCP server to be ignored and dhclient to snooze for a 
long time before attempting another DHCP Discover message to the server. Under 
such circumstances, the services that depend on presence of an IP address fail. 

  Attempted Workaround:
  Above assumption was further used to create a delayNetwork.service patch 
one-shot systemd service that ca

[Desktop-packages] [Bug 1681025] Re: dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd-timesyncd.service

[J.D.]

Please find the attached wireshark trace of the BOOTP messages for
problem usecase, whereby the system was rebooted.

** Attachment added: "Wireshark trace of the problem reboot sequence."
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681025/+attachment/4857990/+files/bootp.pcapng

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

Title:
  dhclient fails to assign IP address during system boot inspite of
  valid DHCP Offer when time change is performed by systemd-
  timesyncd.service

Status in network-manager package in Ubuntu:
  New

Bug description:
  System Information:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Package Information:
  network-manager:
Installed: (none)
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  Expected Behavior:
  The system has one ethernet interface ens160 that is expected to be assigned 
an IPv4 address using DHCP as part of the bootup process so that services that 
depends on presence of IPv4 address do not fail to initialize during the boot 
process.

  Problem Behavior:
  The ethernet interface ens160 was UP but no IPv4 address was assigned inspite 
of correct response from the DHCP server, thereby causing the services that 
depends on presence of IPv4 address to fail during the boot process.

  Problem Details:
  The default 16.04.2 LTS server installed in a VMWare virtual machine running 
on SuperMicro server using ESXi 6 fails to obtain an IP address from a DHCP 
server during system startup when there is a simultaneous time change as 
evidenced by "systemd[1]: Time has been changed" entry in syslog. The system 
successfully obtains the IP address after significant delay (ranging from 2 - 5 
minutes) after system startup. 

  Note that the system has open-vmware-tools package and the VMWare
  tools settings are set to NOT synchronize the guest time, thereby
  eliminating any scope of interference from virtualization host (The
  host itself is set to use NTP synchronization and has correct timing).

  Wireshark was used to sniff the BOOTP messages. When system is
  rebooted, system sends a DHCP Release to the DHCP server. When system
  starts, it broadcasts a valid DHCP Discover to network and received a
  valid DHCP Offer from the network within 4 secs. Note that a "Time has
  been changed" log appears just before dhclient logs "No DHCPOFFERS
  received" in syslog. (The time appears to be moved ahead by around 6
  mins.)

  After about 4 minutes, system broadcasts a valid DHCP Discover to
  which DHCP server responds with DHCP Offer, system responds with DHCP
  Request and DHCP server responds with DHCP Ack and the system is
  assigned its IP address. The dhclient logs in syslog concurs with the
  wireshark trace:

  Apr  6 18:39:05 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 
255.255.255.255 port 67 interval 3 (xid=0x92322e17)
  Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 
255.255.255.255 port 67 interval 8 (xid=0x92322e17)
  Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPREQUEST of 192.168.1.161 on 
ens160 to 255.255.255.255 port 67 (xid=0x172e3292)
  Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPOFFER of 192.168.1.161 from 
192.168.1.1
  Apr  6 18:39:09 etCorgServer dhclient[1071]: DHCPACK of 192.168.1.161 from 
192.168.1.1
  Apr  6 18:39:09 etCorgServer dhclient[1071]: bound to 192.168.1.161 -- 
renewal in 33171 seconds.

  An attempt to release and reacquire the IP address after the system is
  up and running always succeeds immediately with the aforesaid "happy"
  usecase.

  Workaround Attempted:
  Turning off systemd-timesyncd.service always allows dhclient to immediately 
assign the IP address during the boot process. Turning it on leads to the above 
problem usecase with very high probability. Based on this observation, an 
assumption can be made that  the time synchronization happens to overlap the 
DHCP processing performed by dhclient. There is a time-change which causes the 
DHCP Offer sent by the DHCP server to be ignored and dhclient to snooze for a 
long time before attempting another DHCP Discover message to the server. Under 
such circumstances, the services that depend on presence of an IP address fail. 

  Attempted Workaround:
  Above assumption was further used to create a delayNetwork.service patch 
one-shot systemd service that causes the networking service to delay 
networking.service until time-sync.target is reached by the 
systemd-timesyncd.service. Such patch seems to cause dhclient

[Desktop-packages] [Bug 1681025] [NEW] dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd-timesyncd.service

[J.D.]

Public bug reported:

System Information:
Description:Ubuntu 16.04.2 LTS
Release:16.04

Package Information:
network-manager:
  Installed: (none)
  Candidate: 1.2.6-0ubuntu0.16.04.1
  Version table:
 1.2.6-0ubuntu0.16.04.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 1.2.2-0ubuntu0.16.04.4 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 1.1.93-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


Expected Behavior:
The system has one ethernet interface ens160 that is expected to be assigned an 
IPv4 address using DHCP as part of the bootup process so that services that 
depends on presence of IPv4 address do not fail to initialize during the boot 
process.

Problem Behavior:
The ethernet interface ens160 was UP but no IPv4 address was assigned inspite 
of correct response from the DHCP server, thereby causing the services that 
depends on presence of IPv4 address to fail during the boot process.

Problem Details:
The default 16.04.2 LTS server installed in a VMWare virtual machine running on 
SuperMicro server using ESXi 6 fails to obtain an IP address from a DHCP server 
during system startup when there is a simultaneous time change as evidenced by 
"systemd[1]: Time has been changed" entry in syslog. The system successfully 
obtains the IP address after significant delay (ranging from 2 - 5 minutes) 
after system startup. 

Note that the system has open-vmware-tools package and the VMWare tools
settings are set to NOT synchronize the guest time, thereby eliminating
any scope of interference from virtualization host (The host itself is
set to use NTP synchronization and has correct timing).

Wireshark was used to sniff the BOOTP messages. When system is rebooted,
system sends a DHCP Release to the DHCP server. When system starts, it
broadcasts a valid DHCP Discover to network and received a valid DHCP
Offer from the network within 4 secs. Note that a "Time has been
changed" log appears just before dhclient logs "No DHCPOFFERS received"
in syslog. (The time appears to be moved ahead by around 6 mins.)

After about 4 minutes, system broadcasts a valid DHCP Discover to which
DHCP server responds with DHCP Offer, system responds with DHCP Request
and DHCP server responds with DHCP Ack and the system is assigned its IP
address. The dhclient logs in syslog concurs with the wireshark trace:

Apr  6 18:39:05 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 
255.255.255.255 port 67 interval 3 (xid=0x92322e17)
Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 
255.255.255.255 port 67 interval 8 (xid=0x92322e17)
Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPREQUEST of 192.168.1.161 on 
ens160 to 255.255.255.255 port 67 (xid=0x172e3292)
Apr  6 18:39:08 etCorgServer dhclient[1071]: DHCPOFFER of 192.168.1.161 from 
192.168.1.1
Apr  6 18:39:09 etCorgServer dhclient[1071]: DHCPACK of 192.168.1.161 from 
192.168.1.1
Apr  6 18:39:09 etCorgServer dhclient[1071]: bound to 192.168.1.161 -- renewal 
in 33171 seconds.

An attempt to release and reacquire the IP address after the system is
up and running always succeeds immediately with the aforesaid "happy"
usecase.

Workaround Attempted:
Turning off systemd-timesyncd.service always allows dhclient to immediately 
assign the IP address during the boot process. Turning it on leads to the above 
problem usecase with very high probability. Based on this observation, an 
assumption can be made that  the time synchronization happens to overlap the 
DHCP processing performed by dhclient. There is a time-change which causes the 
DHCP Offer sent by the DHCP server to be ignored and dhclient to snooze for a 
long time before attempting another DHCP Discover message to the server. Under 
such circumstances, the services that depend on presence of an IP address fail. 

Attempted Workaround:
Above assumption was further used to create a delayNetwork.service patch 
one-shot systemd service that causes the networking service to delay 
networking.service until time-sync.target is reached by the 
systemd-timesyncd.service. Such patch seems to cause dhclient to always assign 
IP address during boot process. However, it would be desirable to ensure that 
dhclient and/or the networking.service take correct steps to protect itself 
against race conditions that may arise due to time changes affected by the 
systemd-timesyncd.service. At the very least, possibility of time change during 
such critical and vulnerable system component initialization must be minimized 
by isolating the time change to occur during a bootup phase when such 
components are not being initialized.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager (not installed)
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Apr  7 22:50:11 2

[Desktop-packages] [Bug 1681021] Re: can't enable SLI under linux with am4 motherboard

[Chen Chen]

** Attachment added: "nvidia-bug-report-opensource-378.13.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1681021/+attachment/4857985/+files/nvidia-bug-report-opensource-378.13.log.gz

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

Title:
  can't enable SLI under linux with am4 motherboard

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

Bug description:
  In your logs I see see vesafb warnings and it needs to be disabled.

  NVRM: Your system is not currently configured to drive a VGA console
  4月 01 07:55:58 ATC kernel: NVRM: on the primary VGA device. The NVIDIA 
Linux graphics driver
  4月 01 07:55:58 ATC kernel: NVRM: requires the use of a text-mode VGA 
console. Use of other console
  4月 01 07:55:58 ATC kernel: NVRM: drivers including, but not limited to, 
vesafb, may result in
  4月 01 07:55:58 ATC kernel: NVRM: corruption and stability problems, and is 
not supported.

  To disable it,
  Code:
  Add 'video=vesafb:off vga=normal'
  on the kernel command line in the bootloader configuration file.

  Then reboot.


  Let me know if this helps or not and if not describe the problem and
  generate and attach new logs.

  System Ubuntu Budgie 17.04 with ryzen 1800X and Titian X Pascal tring
  to solve the problem that enable 2way SLI causes black screen and can
  doing nothing

  Motherboard https://www.ebay.com/itm/232274935746

  Q1:Why the NVIDIA official said the motherboard is not in the official list?
  http://www.geforce.com/hardware/technology/sli/motherboards
  Only am3+ show up 
  Q2:does it means the official support not followed titly but will support 
inthe future 
  Q3:does it mean it will not support am4 motherboard under Linux With SLI only 
Windows can use the sli function?
  Q4:how to add the command
  Code:
  'video=vesafb:off vga=normal
  as the official said (How to do and where to put it )
  nvidia-bug-report-opensource-378.13.log.gz

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

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

[Desktop-packages] [Bug 1681021] [NEW] can't enable SLI under linux with am4 motherboard

[Chen Chen]

Public bug reported:

In your logs I see see vesafb warnings and it needs to be disabled.

NVRM: Your system is not currently configured to drive a VGA console
4月 01 07:55:58 ATC kernel: NVRM: on the primary VGA device. The NVIDIA Linux 
graphics driver
4月 01 07:55:58 ATC kernel: NVRM: requires the use of a text-mode VGA console. 
Use of other console
4月 01 07:55:58 ATC kernel: NVRM: drivers including, but not limited to, 
vesafb, may result in
4月 01 07:55:58 ATC kernel: NVRM: corruption and stability problems, and is 
not supported.

To disable it,
Code:
Add 'video=vesafb:off vga=normal'
on the kernel command line in the bootloader configuration file.

Then reboot.


Let me know if this helps or not and if not describe the problem and
generate and attach new logs.

System Ubuntu Budgie 17.04 with ryzen 1800X and Titian X Pascal tring to
solve the problem that enable 2way SLI causes black screen and can doing
nothing

Motherboard https://www.ebay.com/itm/232274935746

Q1:Why the NVIDIA official said the motherboard is not in the official list?
http://www.geforce.com/hardware/technology/sli/motherboards
Only am3+ show up 
Q2:does it means the official support not followed titly but will support inthe 
future 
Q3:does it mean it will not support am4 motherboard under Linux With SLI only 
Windows can use the sli function?
Q4:how to add the command
Code:
'video=vesafb:off vga=normal
as the official said (How to do and where to put it )
nvidia-bug-report-opensource-378.13.log.gz

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  can't enable SLI under linux with am4 motherboard

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

Bug description:
  In your logs I see see vesafb warnings and it needs to be disabled.

  NVRM: Your system is not currently configured to drive a VGA console
  4月 01 07:55:58 ATC kernel: NVRM: on the primary VGA device. The NVIDIA 
Linux graphics driver
  4月 01 07:55:58 ATC kernel: NVRM: requires the use of a text-mode VGA 
console. Use of other console
  4月 01 07:55:58 ATC kernel: NVRM: drivers including, but not limited to, 
vesafb, may result in
  4月 01 07:55:58 ATC kernel: NVRM: corruption and stability problems, and is 
not supported.

  To disable it,
  Code:
  Add 'video=vesafb:off vga=normal'
  on the kernel command line in the bootloader configuration file.

  Then reboot.


  Let me know if this helps or not and if not describe the problem and
  generate and attach new logs.

  System Ubuntu Budgie 17.04 with ryzen 1800X and Titian X Pascal tring
  to solve the problem that enable 2way SLI causes black screen and can
  doing nothing

  Motherboard https://www.ebay.com/itm/232274935746

  Q1:Why the NVIDIA official said the motherboard is not in the official list?
  http://www.geforce.com/hardware/technology/sli/motherboards
  Only am3+ show up 
  Q2:does it means the official support not followed titly but will support 
inthe future 
  Q3:does it mean it will not support am4 motherboard under Linux With SLI only 
Windows can use the sli function?
  Q4:how to add the command
  Code:
  'video=vesafb:off vga=normal
  as the official said (How to do and where to put it )
  nvidia-bug-report-opensource-378.13.log.gz

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

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

[Desktop-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x

[Rogério Vinhal Nunes]

So, I just upgraded to 17.04 with Xorg 1.19.3 and nvidia 375.xx drivers.
By default, Ubuntu installed a modprobe.d file to set drm modeset = 0
for the nvidia kernel module and that seem to prevent Prime
Synchronization from working.

I tried to change the modeset to 1 so I could finally try the
synchronization configuration, but that froze the system hard as long as
lightdm booted. I installed gnome with gdm3 and I could get to gdm3 and
try to login to gnome with no avail. But after a few tries (without
changing anything) it just logged in, but prime synchronization was off
for both the laptop screen as my TV. I did the "modprobe -v nvidia-drm"
to check the modeset and it was 1, but whenever I tried to set the Prime
Synchronization via xrandr, the screen went black for a sec and came
back, but xrandr --verbose still displayed Prime Synchronization off.

Why is that cat /etc/modprobe.d/nvidia-graphics-drivers.conf with the
"options nvidia_375_drm modeset=0"? Why does changing it to 1 freeze the
whole system thereafter?

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

Title:
  PRIME synchronization not working with xserver-1.19.x

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

  Shows this in kern.log so support is enabled

  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

  But in Xorg.0.log -
  randr: falling back to unsynchronized pixmap sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+subscriptions

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

[Desktop-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x

[Doug McMahon]

** Description changed:

  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799
  
  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.
  
  Shows this in kern.log so support is enabled
  
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp
+ 
+ But in Xorg.0.log -
+ randr: falling back to unsynchronized pixmap sharing
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  PRIME synchronization not working with xserver-1.19.x

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

  Shows this in kern.log so support is enabled

  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

  But in Xorg.0.log -
  randr: falling back to unsynchronized pixmap sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+subscriptions

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

[Desktop-packages] [Bug 1654918] Re: No Internet access with default of Automatic (DHCP) & current kernel

[Doug McMahon]

also seen in Ubuntu-Gnome install

** Also affects: network-manager
   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/1654918

Title:
  No Internet access with default of  Automatic (DHCP) & current kernel

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1680433] Re: Flash: This plugin is not supported.

[SunBear]

$ apt policy adobe-flashplugin
adobe-flashplugin:
  Installed: 1:20170314.1-0ubuntu0.16.04.1
  Candidate: 1:20170314.1-0ubuntu0.16.04.1
  Version table:
 *** 1:20170314.1-0ubuntu0.16.04.1 500
500 http://archive.canonical.com/ubuntu xenial/partner amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Flash: This plugin is not supported.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 57.0.2987.98-0ubuntu0.16.04.1276
Candidate: 57.0.2987.98-0ubuntu0.16.04.1276
Version table:
   *** 57.0.2987.98-0ubuntu0.16.04.1276 500
  500 http://sg.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://sg.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  My system was just updated with chromium-browser 
57.0.2987.98-0ubuntu0.16.04.1276 amd64 today. However, this resulted in 
breaking the flash plugin. When I open a webpage requiring flash, the webpage 
returned
  "This plugin is not supported".

  When i inspected the code, the failure appears to be related to:

  http://www.mconline.sg/nres1/{F639486D-19A1-43EE-919E-
  AD353407EDE1}/skin/scorm_topbar.swf" quality="high" bgcolor="#ff"
  width="100%" height="100%" name="topNav" id="topNav" scale="exactfit"
  align="middle" allowscriptaccess="sameDomain" type="application/x
  -shockwave-flash"
  pluginspage="http://www.macromedia.com/go/getflashplayer";
  title="undefined">

  How can this issue be fixed?

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

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

[Desktop-packages] [Bug 1680433] Re: Flash: This plugin is not supported.

[SunBear]

@Chad I checked my /var/log/apt/history.log. It showed that the
following chromium role-commit-package upgrades were performed:

chromium-browser:amd64 (56.0.2924.76-0ubuntu0.16.04.1268,
57.0.2987.98-0ubuntu0.16.04.1276), chromium-codecs-ffmpeg-extra:amd64
(56.0.2924.76-0ubuntu0.16.04.1268, 57.0.2987.98-0ubuntu0.16.04.1276),
chromium-browser-l10n:amd64 (56.0.2924.76-0ubuntu0.16.04.1268,
57.0.2987.98-0ubuntu0.16.04.1276)


Also, a day before this upgrade, my kernel was upgraded:
linux-headers-generic-hwe-16.04:amd64 (4.8.0.45.17, 4.8.0.46.18)

I don't know which adobe-flashplugin I had initially. To fix it, I had to issue 
the following command:
apt-get install browser-plugin-freshplayer-pepperflash

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

Title:
  Flash: This plugin is not supported.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 57.0.2987.98-0ubuntu0.16.04.1276
Candidate: 57.0.2987.98-0ubuntu0.16.04.1276
Version table:
   *** 57.0.2987.98-0ubuntu0.16.04.1276 500
  500 http://sg.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://sg.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  My system was just updated with chromium-browser 
57.0.2987.98-0ubuntu0.16.04.1276 amd64 today. However, this resulted in 
breaking the flash plugin. When I open a webpage requiring flash, the webpage 
returned
  "This plugin is not supported".

  When i inspected the code, the failure appears to be related to:

  http://www.mconline.sg/nres1/{F639486D-19A1-43EE-919E-
  AD353407EDE1}/skin/scorm_topbar.swf" quality="high" bgcolor="#ff"
  width="100%" height="100%" name="topNav" id="topNav" scale="exactfit"
  align="middle" allowscriptaccess="sameDomain" type="application/x
  -shockwave-flash"
  pluginspage="http://www.macromedia.com/go/getflashplayer";
  title="undefined">

  How can this issue be fixed?

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

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

[Desktop-packages] [Bug 1676958] Re: Please merge 0.2.8.4-10.6 from Debian: for for allocating huge block of memory (CVE-2016-9011)

[Launchpad Bug Tracker]

This bug was fixed in the package libwmf - 0.2.8.4-10.6ubuntu1

---
libwmf (0.2.8.4-10.6ubuntu1) zesty; urgency=low

  * Merge from Debian unstable. (LP: #1676958) Remaining changes:
- Split out GTK plugin into separate package.

 -- Balint Reczey   Tue, 28 Mar 2017 15:37:26 +

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

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

Title:
  Please merge 0.2.8.4-10.6 from Debian: for for allocating huge block
  of memory (CVE-2016-9011)

Status in libwmf package in Ubuntu:
  Fix Released
Status in libwmf package in Debian:
  Fix Released

Bug description:
  Debian's changes:

  Changes:
   libwmf (0.2.8.4-10.6) unstable; urgency=medium
   .
 * Non-maintainer upload.
 * Fix allocating huge block of memory (CVE-2016-9011) (Closes: #842090)

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

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

[Desktop-packages] [Bug 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Launchpad Bug Tracker]

This bug was fixed in the package pygobject-2 - 2.28.6-12ubuntu2

---
pygobject-2 (2.28.6-12ubuntu2) zesty; urgency=medium

  * Sync build-arch fix from debian, thanks to Emilio Monfort (LP: #1679835).
  * Use --disable-silent-rules also as per debian.

 -- Robert Bruce Park   Thu, 06 Apr 2017
17:11:50 -0700

** Changed in: pygobject-2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  Fix Released

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

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

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

[Desktop-packages] [Bug 1669655] Re: Adapt to new Nautilus icon name

[rahmadani]

** Changed in: humanity-icon-theme (Ubuntu)
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: nautilus (Ubuntu)
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => rahmadani (rahmadani)

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

Title:
  Adapt to new Nautilus icon name

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Nautilus 3.24's app icon name is org.gnome.Nautilus instead of system-
  file-manager for better flatpak compatibility.

  I have updated ubuntu-themes and humanity-icon-theme for this change
  (adding a new symlink pointing to system-file-manager).

  ubuntu-themes is handled via bileto so I'll ask the appropriate people
  to sponsor that separately. DONE

  I pushed my change to the humanity bzr branch but I don't have upload rights 
for it so I'll need sponsorship for this:
  https://code.launchpad.net/~ubuntu-art-pkg/humanity/release/

  I let other Ubuntu flavors know about this change at bug 1669663.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1669655/+subscriptions

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

[Desktop-packages] [Bug 1681001] [NEW] des plantages

[laurence]

Public bug reported:

Bonjour,
Mon ordi se fige régulièrement et très souvent
par moment la connection internet s'arrête (filaire et wifi) et je perds des 
messqges assez long que j'étais entrain d'écrire.
Merci de me dépanner, en espérant que ce n'est pas difficile.
A bientôt.

PS : S'il vous plait, ce serait bien l'aide en français. Merci encore

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Apr  8 03:08:26 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 ndiswrapper, 1.60, 4.4.0-66-generic, x86_64: installed
 ndiswrapper, 1.60, 4.4.0-70-generic, x86_64: installed
 ndiswrapper, 1.60, 4.4.0-71-generic, x86_64: installed
 ndiswrapper, 1.60, 4.4.0-72-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:14c7]
   Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:14c7]
InstallationDate: Installed on 2016-11-10 (148 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. X75VC
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=84851d8d-6614-4115-b387-fc45015f127a ro drm.debug=0xe 
intel_idle.max_cstate=1 plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X75VC.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X75VC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX75VC.202:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnX75VC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX75VC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X75VC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Apr  8 02:29:10 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5928 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug 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/1681001

Title:
  des plantages

Status in xorg package in Ubuntu:
  New

Bug description:
  Bonjour,
  Mon ordi se fige régulièrement et très souvent
  par moment la connection internet s'arrête (filaire et wifi) et je perds des 
messqges assez long que j'étais entrain d'écrire.
  Merci de me dépanner, en espérant que ce n'est pas difficile.
  A bientôt.

  PS : S'il vous plait, ce serait bien l'aide en français. Merci encore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr  8 03:08:26 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.60, 4.4.0-66-generic, x86_64: installed
   ndiswrapper, 1.60, 4.4.0-70-ge

[Desktop-packages] [Bug 1680433] Re: Flash: This plugin is not supported.

[Oliver Sperke]

I have exactly the same problem. Seems like Chrome 57 breaks with the
old plugin API. The plugin is installed but not working. It worked fine
in previous versions.

$ apt-cache policy flashplugin-installer 
flashplugin-installer:
  Installiert:   25.0.0.127ubuntu0.16.04.1
  Installationskandidat: 25.0.0.127ubuntu0.16.04.1
  Versionstabelle:
 *** 25.0.0.127ubuntu0.16.04.1 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages
100 /var/lib/dpkg/status
 11.2.202.616ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages

$ apt-cache policy chromium-browser
chromium-browser:
  Installiert:   57.0.2987.98-0ubuntu0.16.04.1276
  Installationskandidat: 57.0.2987.98-0ubuntu0.16.04.1276
  Versionstabelle:
 *** 57.0.2987.98-0ubuntu0.16.04.1276 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 49.0.2623.108-0ubuntu1.1233 500
500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

Title:
  Flash: This plugin is not supported.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 57.0.2987.98-0ubuntu0.16.04.1276
Candidate: 57.0.2987.98-0ubuntu0.16.04.1276
Version table:
   *** 57.0.2987.98-0ubuntu0.16.04.1276 500
  500 http://sg.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://sg.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  My system was just updated with chromium-browser 
57.0.2987.98-0ubuntu0.16.04.1276 amd64 today. However, this resulted in 
breaking the flash plugin. When I open a webpage requiring flash, the webpage 
returned
  "This plugin is not supported".

  When i inspected the code, the failure appears to be related to:

  http://www.mconline.sg/nres1/{F639486D-19A1-43EE-919E-
  AD353407EDE1}/skin/scorm_topbar.swf" quality="high" bgcolor="#ff"
  width="100%" height="100%" name="topNav" id="topNav" scale="exactfit"
  align="middle" allowscriptaccess="sameDomain" type="application/x
  -shockwave-flash"
  pluginspage="http://www.macromedia.com/go/getflashplayer";
  title="undefined">

  How can this issue be fixed?

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

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

[Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

[spike speigel]

I'm experiencing this behavior with a Dell XPS 13 9360 Developer Edition

I'm not running xfce.  I'm using stock Unity, but lightdm is running.

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  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/1581302/+subscriptions

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

[Desktop-packages] [Bug 1678594] Re: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/s

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified:
  usr/share/doc/libavutil52/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different
  from other instances of package libavutil52:i386

Status in libav package in Ubuntu:
  New

Bug description:
  'Error: Brokencount > 0'

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libavutil52/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Sun Apr  2 16:15:39 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.11
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
  DpkgTerminalLog:
   Preparing to unpack .../libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb ...
   Unpacking libavutil52:i386 (6:9.20-0ubuntu0.14.04.1) over (6:9.11-2ubuntu2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other 
instances of package libavutil52:i386
  DuplicateSignature: package:libavutil52:6:9.20-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libavutil52/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other 
instances of package libavutil52:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other 
instances of package libavutil52:i386
  InstallationDate: Installed on 2017-03-22 (10 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libav
  Title: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', 
which is different from other instances of package libavutil52:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1678594] Re: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/s

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified:
  usr/share/doc/libavutil52/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different
  from other instances of package libavutil52:i386

Status in libav package in Ubuntu:
  New

Bug description:
  'Error: Brokencount > 0'

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libavutil52/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Sun Apr  2 16:15:39 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.11
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
  DpkgTerminalLog:
   Preparing to unpack .../libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb ...
   Unpacking libavutil52:i386 (6:9.20-0ubuntu0.14.04.1) over (6:9.11-2ubuntu2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other 
instances of package libavutil52:i386
  DuplicateSignature: package:libavutil52:6:9.20-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libavutil52/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other 
instances of package libavutil52:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other 
instances of package libavutil52:i386
  InstallationDate: Installed on 2017-03-22 (10 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libav
  Title: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', 
which is different from other instances of package libavutil52:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1678504] Re: Wifi does not connect to network

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Wifi does not connect to network

Status in network-manager package in Ubuntu:
  New

Bug description:
  I do not speak the jargon language you guys used to, so bear with me. 
Although I can only try my best as to describe the trouble that I'm going 
through with my network manager, I really don't know whats going wrong?
  Moments ago I filled-out this field and when I was done and hit the "Submit 
Bug Report" button, I was brought to a blank page stating network issues.
  Whether I go and start Firefox, Thunderbird, or conduct an update through 
"update manager" or command line, I get a network error. My way of working 
around this issue is to initialize Chromium. When I start Chromium I'll go to 
ebay.com or any site I normally peruse, I get a blank page, it automatically 
refreshes and I'd finally get a web page open up like normal. I close chromium, 
conduct an update, open FireFox or start Chromium and it'll work like normal. 
But if I spend long enough time, I am no longer able to browse. Redirect me if 
I filled out the wrong bug report
  Please help

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr  1 12:12:08 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-25 (341 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.9 metric 600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
C8A090  e897215f-3697-44f8-9676-c912b3554dad  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1679921] Re: package python-gnome2 2.28.1+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package python-gnome2 2.28.1+dfsg-1ubuntu2 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 1

Status in gnome-python package in Ubuntu:
  New

Bug description:
  please help me,,, when im starting my ubuntu, this message always
  shown up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gnome2 2.28.1+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Wed Apr  5 12:41:46 2017
  DuplicateSignature: package:python-gnome2:2.28.1+dfsg-1ubuntu2:subprocess 
installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-03-10 (25 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: gnome-python
  Title: package python-gnome2 2.28.1+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2017-03-16 (20 days ago)

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

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

[Desktop-packages] [Bug 1679921] Re: package python-gnome2 2.28.1+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-gnome2 2.28.1+dfsg-1ubuntu2 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 1

Status in gnome-python package in Ubuntu:
  New

Bug description:
  please help me,,, when im starting my ubuntu, this message always
  shown up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gnome2 2.28.1+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Wed Apr  5 12:41:46 2017
  DuplicateSignature: package:python-gnome2:2.28.1+dfsg-1ubuntu2:subprocess 
installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-03-10 (25 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: gnome-python
  Title: package python-gnome2 2.28.1+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2017-03-16 (20 days ago)

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

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

[Desktop-packages] [Bug 1680974] [NEW] libegl1-mesa depends on libmirclient9

[Fred]

Public bug reported:

Mir is dead.
libegl1-mesa should no longer depend on it.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libegl1-mesa 17.0.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Classic:GNOME
Date: Fri Apr  7 23:55:04 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2013-12-26 (1197 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-PRO
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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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 Apr  7 20:23:48 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  libegl1-mesa depends on libmirclient9

Status in mesa package in Ubuntu:
  New

Bug description:
  Mir is dead.
  libegl1-mesa should no longer depend on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libegl1-mesa 17.0.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Fri Apr  7 23:55:04 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2013-12-26 (1197 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.t

[Desktop-packages] [Bug 1680964] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680964/+attachment/4857701/+files/Disassembly.txt

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

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

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680964/+attachment/4857707/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680964/+attachment/4857709/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680964/+attachment/4857710/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1663954

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  signon-ui crashed with SIGSEGV in QWindow::setModality()

Status in signon-ui package in Ubuntu:
  New

Bug description:
  connecting Kontact with Owncloud CalDav/CardDav

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  7 22:38:31 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2017-04-07 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  ProcCmdline: /usr/bin/signon-ui
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1680964/+subscriptions

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

[Desktop-packages] [Bug 1680957] [NEW] [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

[Shaon Sikder]

Public bug reported:

missing audio output

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  shaon  3414 F pulseaudio
CurrentDesktop: Unity
Date: Sat Apr  8 02:26:22 2017
InstallationDate: Installed on 2017-04-07 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  shaon  3414 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.8
dmi.board.name: 0664DJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1680957

Title:
  [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  missing audio output

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaon  3414 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr  8 02:26:22 2017
  InstallationDate: Installed on 2017-04-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaon  3414 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.8
  dmi.board.name: 0664DJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1680928] Re: [Snap] Spellcheck not working

[Ads20000]

** Description changed:

  I need the relevant `hunspell` package (in my case, `hunspell-en-gb`)
  for spellcheck to work but it's not installed inside the Snap. The Snap
  should depend on or install the relevant `hunspell` package that the
  user wants and should install the relevant ones the user needs if they
  want to spellcheck in another language, but I have no idea how this
  could be done inside the Snap.
+ 
+ Alternatively, Sergio says it should be done using LibreOffice's 'built
+ in implementation to bring in language packs'.
+ https://forum.snapcraft.io/t/how-to-make-deb-or-rpm-packages-work-
+ inside-snaps/149/11?u=ads2

** Description changed:

  I need the relevant `hunspell` package (in my case, `hunspell-en-gb`)
  for spellcheck to work but it's not installed inside the Snap. The Snap
  should depend on or install the relevant `hunspell` package that the
  user wants and should install the relevant ones the user needs if they
  want to spellcheck in another language, but I have no idea how this
  could be done inside the Snap.
  
  Alternatively, Sergio says it should be done using LibreOffice's 'built
  in implementation to bring in language packs'.
  https://forum.snapcraft.io/t/how-to-make-deb-or-rpm-packages-work-
  inside-snaps/149/11?u=ads2
+ 
+ Ubuntu 16.10
+ Ubuntu Core 16-2 Rev 1577
+ LibreOffice 5.3.2.2 Rev 19

** Tags added: snap yakkety

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

Title:
  [Snap] Spellcheck not working

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I need the relevant `hunspell` package (in my case, `hunspell-en-gb`)
  for spellcheck to work but it's not installed inside the Snap. The
  Snap should depend on or install the relevant `hunspell` package that
  the user wants and should install the relevant ones the user needs if
  they want to spellcheck in another language, but I have no idea how
  this could be done inside the Snap.

  Alternatively, Sergio says it should be done using LibreOffice's
  'built in implementation to bring in language packs'.
  https://forum.snapcraft.io/t/how-to-make-deb-or-rpm-packages-work-
  inside-snaps/149/11?u=ads2

  Ubuntu 16.10
  Ubuntu Core 16-2 Rev 1577
  LibreOffice 5.3.2.2 Rev 19

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

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

[Desktop-packages] [Bug 1680952] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680952/+attachment/4857637/+files/Disassembly.txt

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

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

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680952/+attachment/4857643/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680952/+attachment/4857645/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680952/+attachment/4857646/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1663954

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  signon-ui crashed with SIGSEGV in QWindow::setModality()

Status in signon-ui package in Ubuntu:
  New

Bug description:
  I tried to add GTalk IM account but the Google button did nothing and
  then the crash report popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  7 23:08:34 2017
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2014-03-07 (1126 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  ProcCmdline: /usr/bin/signon-ui
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: Upgraded to zesty on 2017-03-29 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (thunderbird:2467): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (thunderbird:2467): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (rhythmbox:2464): Rhythmbox-WARNING **: Unable to grab media player keys: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SettingsDaemon was not provided by any .service files
   (thunderbird:2456): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (thunderbird:2456): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1680952/+subscriptions

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

[Desktop-packages] [Bug 1676463] Re: Unable to keep homepage across firefox restarts

[Cliff Carson]

This is not a problem in Zesty Unity.  Have two Zesty Gnome system that
will not retain their home page.

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

Title:
  Unable to keep homepage across firefox restarts

Status in firefox package in Ubuntu:
  New

Bug description:
  Running firefox 50.1 on gnome 17.04 and every restart of firefox I
  have to reset my homepage.  Tried the normal way by dragging the
  current tab to the homepage icon and manually editing prefs.js to the
  wanted homepage.  Once set the homepage setting is held until firefox
  reload.  Since the /home page is common to both the 17.04 system and
  16.10 gnome system I've tried to reproduce this failure on 16.10 but
  cannot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 50.1.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  2231 F pulseaudio
  BuildID: 20161213225349
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Mar 27 10:29:15 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-02-13 (41 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.194 metric 
600
  MostRecentCrashID: bp-46c62897-65eb-4932-916e-3061f2170315
  Plugins:
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   GNOME Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=50.1.0/20161213225349 (In use)
  RelatedPackageVersions: gnome-shell 3.24.0-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.name: W35_37ET
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

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

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

[Desktop-packages] [Bug 1680937] [NEW] package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances o

[Leszek]

Public bug reported:

Problem during standard "sudo apt upgrade" procedure

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk-3-0 3.18.9-1ubuntu3.2
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Apr  7 20:55:38 2017
DuplicateSignature:
 package:libgtk-3-0:3.18.9-1ubuntu3.2
 Unpacking libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.18.9-1ubuntu3.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgtk-3-0_3.18.9-1ubuntu3.3_amd64.deb (--unpack):
  trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different 
from other instances of package libgtk-3-0:amd64
ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is 
different from other instances of package libgtk-3-0:amd64
InstallationDate: Installed on 2016-02-28 (404 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.20
SourcePackage: gtk+3.0
Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying 
to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other 
instances of package libgtk-3-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict third-party-packages xenial

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

Title:
  package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying
  to overwrite shared '/etc/gtk-3.0/settings.ini', which is different
  from other instances of package libgtk-3-0:amd64

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Problem during standard "sudo apt upgrade" procedure

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3.2
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  7 20:55:38 2017
  DuplicateSignature:
   package:libgtk-3-0:3.18.9-1ubuntu3.2
   Unpacking libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.18.9-1ubuntu3.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgtk-3-0_3.18.9-1ubuntu3.3_amd64.deb (--unpack):
trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different 
from other instances of package libgtk-3-0:amd64
  ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which 
is different from other instances of package libgtk-3-0:amd64
  InstallationDate: Installed on 2016-02-28 (404 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.20
  SourcePackage: gtk+3.0
  Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying 
to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other 
instances of package libgtk-3-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1670379] Re: Support GNOME Shell 3.24's 'Launch Using Dedicated Graphics Card'

[Jeremy Bicha]

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

turns out we needed switcheroo-control so closing this bug

** This bug has been marked a duplicate of bug 1671828
   [FFe] [needs-packaging] switcheroo-control

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

Title:
  Support GNOME Shell 3.24's 'Launch Using Dedicated Graphics Card'

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  I don't have NVIDIA hardware but I package gnome-shell.

  Ubuntu GNOME 17.04 has GNOME 3.24. It would be great if the new
  support for hybrid graphics worked.

  https://blogs.gnome.org/uraeus/2016/11/01/discrete-graphics-and-
  fedora-workstation-25/

  (The GNOME part is step 6 in that blog post.)

  Could you look into seeing if this works? And if it doesn't work,
  could you report what doesn't work so it can be mentioned in the
  Release Notes for those wondering about the feature?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1670379/+subscriptions

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

[Desktop-packages] [Bug 1680928] [NEW] [Snap] Spellcheck not working

[Ads20000]

Public bug reported:

I need the relevant `hunspell` package (in my case, `hunspell-en-gb`)
for spellcheck to work but it's not installed inside the Snap. The Snap
should depend on or install the relevant `hunspell` package that the
user wants and should install the relevant ones the user needs if they
want to spellcheck in another language, but I have no idea how this
could be done inside the Snap.

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

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

Title:
  [Snap] Spellcheck not working

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I need the relevant `hunspell` package (in my case, `hunspell-en-gb`)
  for spellcheck to work but it's not installed inside the Snap. The
  Snap should depend on or install the relevant `hunspell` package that
  the user wants and should install the relevant ones the user needs if
  they want to spellcheck in another language, but I have no idea how
  this could be done inside the Snap.

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

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

[Desktop-packages] [Bug 1328670] Re: spacebar shortcut for "load next image in the folder" is a very bad idea

[Starlet Tom]

I was googling how to re-enable this feature, as this feature is removed
on the 17.04 Ubuntu beta Gnome.

Unfortunately, I disagree that this feature is counter intuitive.

This feature is mostly useful for left handed people like me to select
the next picture.

IMO, this feature can be disabled by default but must have option in the
settings to enable it.

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

Title:
  spacebar shortcut for "load next image in the folder" is a very bad
  idea

Status in eog package in Ubuntu:
  New

Bug description:
  In MOST graphics editing and viewing software, the spacebar usually allows 
you to move the document around with the mouse relative to the window. This is 
a very widespread convention and has been so for decades.
  In Image Viewer, you can do that by just clicking and dragging, so it's OK 
that the space bar is not needed for that, but it is a TERRIBLE idea to use it 
as a shortcut for something else.

  And even a worse idea is to use it as the shortcut for "load the next
  file in the folder". Nobody in his right mind would expect the space
  bar to do that. It's one of the most counterintuitive keyboard
  shortcuts I've ever seen. And when the set of shortcuts is not
  supposed to be intuitive (when there are a lot of functions for which
  to design a shortcut, it's ok to give up intuitiveness and have the
  user learn the shortcuts by looking at the menus), then it is common
  and good practice to avoid obvious and common keys (such as the space
  bar), that can be hit by mistake, for non-obvious tasks (such as load
  another file in the folder).

  Also, the key or key combination used for "load next file" should have
  an obvious counterpart for "load previous file". So, for example, the
  "pagedown" key would be a reasonable choice for "next", because you
  could then have "pageup" for "previous". Or perhaps the right arrow
  combined with ctrl, shift or something (not alone, because you expect
  that to move the image), because its obvious counterpart for previous
  would be the left arrow. The spacebar doesn't have any obvious
  "opposite" key so it's intrinsically a bad candidate as a shortcut for
  "next file".

  So there are at least 3 reasons why the space bar is a terrible
  keyboard shortcut for the action of loading the next file in the
  folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: eog 3.10.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 10 21:42:59 2014
  InstallationDate: Installed on 2013-10-11 (242 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: eog
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago)

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

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

[Desktop-packages] [Bug 1631246] Re: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também e

[Hans Joachim Desserud]

** Also affects: account-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: account-plugins (Ubuntu)
   Status: New => Confirmed

** Tags added: package-conflict

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  a tentar sobre-escrever '/etc/signon-ui/webkit-
  options.d/api.twitter.com.conf', que também está no pacote account-
  plugin-twitter 0.12+16.04.20160126-0ubuntu1

Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  Error during installation of KDE Plasma on Ubuntu 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct  7 01:55:46 2016
  ErrorMessage: a tentar sobre-escrever 
'/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também está no 
pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2016-09-11 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', 
que também está no pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1680921] Re: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libasyncns0:i386 0.8-5build1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libasyncns package in Ubuntu:
  New

Bug description:
  did not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libasyncns0:i386 0.8-5build1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  7 13:48:11 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libasyncns0:i386:0.8-5build1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libasyncns0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-05 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libasyncns
  Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1680921] [NEW] package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[Jeremy]

Public bug reported:

did not install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libasyncns0:i386 0.8-5build1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Apr  7 13:48:11 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu7
DuplicateSignature:
 package:libasyncns0:i386:0.8-5build1
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libasyncns0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-04-05 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: libasyncns
Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libasyncns0:i386 0.8-5build1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libasyncns package in Ubuntu:
  New

Bug description:
  did not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libasyncns0:i386 0.8-5build1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  7 13:48:11 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libasyncns0:i386:0.8-5build1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libasyncns0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-05 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libasyncns
  Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Iain Lane]

This is in -proposed, awaiting unblock

** Changed in: pygobject-2 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  Fix Committed

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

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

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

[Desktop-packages] [Bug 1674930] Re: Amazon EC2 instances broken

[Bryan Larsen]

That workaround doesn't work for me because of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584, which
loads the nvidia kernel module repeatedly.

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

Title:
  Amazon EC2 instances broken

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  I have installed nvidia-367 package because it is required by the
  Amazon Ec2 instance type g2.2xlarge. They are using an older Nvidia
  card (GRID K520) which is supported by nvidia-367 driver. This driver
  does now install nvidia-375. That driver does not support the
  g2.2xlarge instance card. I cannot use the gfx now on the g2
  instances.

  00:03.0 VGA compatible controller: NVIDIA Corporation GK104GL [GRID
  K520] (rev a1)

  ii  nvidia-367   375.39-0ubuntu0.16.04.1
amd64Transitional package for nvidia-375
  ii  nvidia-375   375.39-0ubuntu0.16.04.1
amd64NVIDIA binary driver - version 375.39

  [  1120.056] (WW) NVIDIA(0): The NVIDIA GRID K520 GPU installed in this 
system is supported
  [  1120.056] (WW) NVIDIA(0): through the NVIDIA 367.xx Legacy drivers. 
Please visit
  [  1120.056] (WW) NVIDIA(0): http://www.nvidia.com/object/unix.html for 
more
  [  1120.056] (WW) NVIDIA(0): information.  The 375.39 NVIDIA driver will 
ignore this
  [  1120.056] (WW) NVIDIA(0): GPU.  Continuing probe...

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

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

[Desktop-packages] [Bug 1652463] Re: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland

[Bug Watch Updater]

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  gnome-terminal-server crashed with SIGSEGV in XSync() when launched
  from desktop under Wayland

Status in GTK+:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME
  3.22 I have found that when I use the right-click menu to open
  Terminal from the desktop that a window looking like this shows up on
  the screen for about a second or less:

  Terminal_Opened_From_Desktop.png

  And then when it closes all the other Terminal sessions go with it
  instantly killing anything I've got running from any of the gnome-
  terminal windows which is really quite annoying and luckily I didn't
  have anything vital running from one at the time. But this could
  seriously cause something quite bad for another unsuspecting person.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 24 19:59:50 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-15 (223 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   ?? ()
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   gdk_window_process_all_updates () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libvte-2.91.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-terminal-server crashed with SIGSEGV in XSync()
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (66 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1633769] Re: Bug with kernel 4.8

[Sebastian Ramacher]

intel-vaapi-driver only provides a driver for encoding and decoding
videos and has nothing to do with the mentioned problems.

** Changed in: intel-vaapi-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

[Iain Lane]

Can you ask someone upstream whether the approach is valid?

I think it might be easiest to just always show the settings - what do
you think?

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  On up to date Raring alpha, on System Settings > Mouse & Touchpad the
  Mouse settings are completely missing.  The General and Touchpad
  sections are there but none for mouse.  See attached screenshot.

  xinput --list shows
  ~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MOSART Semi. 2.4G Keyboard Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [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)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ MOSART Semi. 2.4G Keyboard Mouseid=10   [slave  
keyboard (3)]
  ↳ Dell Dell USB Keyboard  id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  and from lsusb:
  Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser 
Mouse SMWLL11]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Sat Feb 23 09:40:41 2013
  InstallationDate: Installed on 2012-08-01 (205 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1680336] Re: libreoffice java based extension cannot find java_uno due to wrong java.library.path

[Schlomo Schapiro]

Can you please explain why you believe that the root cause is a hard
coded path in this extension? I unpacked the OXT and the embedded JAR
file and could not find any "libreoffice" string in any of the files
there. I could find all kind of other UI strings from the extension so
that I tend to believe my test showing that the path is *not* hard
coded.

What else makes you so sure that only the extension can be blamed for
this problem?


---
Regarding your general point and closing this issue:

I totally understand - and agree with - your line of arguments and also
your view on what is proper with regard to file locations.

Nevertheless I kindly ask you to reconsider adding my workaround (or something 
more appropriate to the same effect) to the LO packages on Ubuntu for the 
following reasons:
* Users don't know or care why something fails. They just get frustrated. If we 
as Ubuntu have the chance to help them then we should do so.
* If we can add a fix to Ubuntu that does not harm anybody but helps some 
people then IMHO we should do so - not as a step down from our high principles 
but as a step up towards just helping our users.
* I estimate that we can "fix" 90% of Linux users of this extension
* I have the impression that fixing it here will be much easier then getting 
DeutschePost to fix it, they don't really care about us.

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

Title:
  libreoffice java based extension cannot find java_uno due to wrong
  java.library.path

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I try to use the "E-Porto Add In" (extension to insert a stamp for the
  German postal system) from https://www.deutschepost.de/de/i
  /internetmarke-porto-drucken/e-porto-add-in.html on Ubuntu 16.04
  amd64.

  The extension contains several XCU and one JAR:

  
schlomo@brho:~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu265944hpbsb.tmp_/loeportoinstaller_v3_0_0.oxt$
 ll
  total 744
  drwxrwx--- 8 schlomo schlomo   4096 Apr  5 06:45 ./
  drwxrwx--- 3 schlomo schlomo   4096 Apr  5 06:45 ../
  drwxrwx--- 4 schlomo schlomo   4096 Apr  5 06:45 assets/
  -rw-rw 1 schlomo schlomo   1339 Apr  5 06:45 description.xml
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 images/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 07:01 lib/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 licenses/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 META-INF/
  -rw-rw 1 schlomo schlomo 721541 Apr  5 06:45 OOEporto.jar
  drwxrwx--- 3 schlomo schlomo   4096 Apr  5 06:45 registry/
  
schlomo@brho:~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu265944hpbsb.tmp_/loeportoinstaller_v3_0_0.oxt$
 cat META-INF/manifest.xml 
  
  http://openoffice.org/2001/manifest";>





  

  Using the extension throws the following Java exception:

  Exception in thread "Thread-1312" com.sun.star.lang.IllegalArgumentException
at 
com.sun.star.comp.bridgefactory.BridgeFactory.createBridge(BridgeFactory.java:126)
at 
com.sun.star.comp.urlresolver.UrlResolver$_UrlResolver.resolve(UrlResolver.java:107)
at com.sun.star.comp.helper.Bootstrap.bootstrap(Bootstrap.java:349)
at com.sun.star.comp.helper.Bootstrap.bootstrap(Bootstrap.java:280)
at de.deutschepost.ooeporto.comm.a.e(Unknown Source)
at de.deutschepost.ooeporto.comm.a.c(Unknown Source)
at de.deutschepost.ooeporto.comm.a.a(Unknown Source)
at de.deutschepost.ooeporto.comm.a.a(Unknown Source)
at de.deutschepost.ooeporto.core.e.c(Unknown Source)
at de.deutschepost.ooeporto.core.e.a(Unknown Source)
at de.deutschepost.ooeporto.gui.bM.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
  Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.sun.star.uno.UnoRuntime.getBridge(UnoRuntime.java:474)
at com.sun.star.uno.UnoRuntime.getBridgeByName(UnoRuntime.java:512)
at 
com.sun.star.comp.bridgefactory.BridgeFactory.createBridge(BridgeFactory.java:121)
... 11 more
  Caused by: java.lang.UnsatisfiedLinkError: no java_uno in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at 
com.sun.star.lib.uno.environments.remote.NativeThreadPool.(NativeThreadPool.java:77)
at 
com.sun.star.lib.uno.environments.remote.ThreadP

[Desktop-packages] [Bug 1680750] Re: pm-hibernate does nothing at all

[Jim Garlick]

** Package changed: powerman (Ubuntu) => pm-utils (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/1680750

Title:
  pm-hibernate does nothing at all

Status in pm-utils package in Ubuntu:
  New

Bug description:
  I have run from a command line:
  # sudo pm-hibernate

  and NOTHING f***ing happens.

  Usually it works (except for lots of issues on resume), but now I have
  tried it twice and it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: powerman (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  7 10:47:47 2017
  InstallationDate: Installed on 2013-10-11 (1273 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: powerman
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago)

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

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

[Desktop-packages] [Bug 1680750] [NEW] pm-hibernate does nothing at all

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have run from a command line:
# sudo pm-hibernate

and NOTHING f***ing happens.

Usually it works (except for lots of issues on resume), but now I have
tried it twice and it does nothing.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: powerman (not installed)
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr  7 10:47:47 2017
InstallationDate: Installed on 2013-10-11 (1273 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: powerman
UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial
-- 
pm-hibernate does nothing at all
https://bugs.launchpad.net/bugs/1680750
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pm-utils 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 1680874] Re: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680874/+attachment/4857378/+files/Disassembly.txt

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

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

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680874/+attachment/4857393/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680874/+attachment/4857394/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680874/+attachment/4857395/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1679731

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  No further info

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xmir 2:1.19.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu3
  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:Unity8
  Date: Fri Apr  7 17:30:12 2017
  DistUpgraded: 2017-04-07 14:25:48,882 DEBUG /openCache(), new cache size 87191
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-71-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-46-generic, x86_64: installed
   nvidia-375, 375.39, 4.8.0-46-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xmir
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:80a5]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80a5]
  MachineType: HP HP Pavilion Notebook
  ProcCmdline: Xmir -rootless -displayfd 3 -mir telegramdesktop
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=ed66a69d-bac5-428b-806f-5c2250f82299 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: Upgraded to zesty on 2017-04-07 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.77
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A5
  dmi.board.vendor: HP
  dmi.board.version: 91.1C
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A5:rvr91.1C:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubun

[Desktop-packages] [Bug 1680526] Re: nVidia-340 (340.102) Kernel 4.10.0-14-generic

[MauRice]

** Summary changed:

- nVidia-340 (340.02) Kernel 4.10.0-14-generic
+ nVidia-340 (340.102) Kernel 4.10.0-14-generic

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

Title:
  nVidia-340 (340.102) Kernel 4.10.0-14-generic

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

Bug description:
  Problem Type: Bug
  Release: 16.04.2 LTS (Xenial Xerus)
  Kernel: 4.10.0-14-generic
  Arch: x86_64
  nVidia driver: 340.102-0ubuntu0.16.04.1
  Graphics Processor: Quadro FX 4600

  Error building kernel modules nvidia-340.ko & nvidia_340_uvm.ko (DKMS)
  Attachemnt: DKMS make.log file

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

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

[Desktop-packages] [Bug 1053443] Re: Unable to print to Konica Minolta C552DS printer - job history

[rahmadani]

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

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

Title:
  Unable to print to Konica Minolta C552DS printer - job history

Status in GS-GPL:
  Unknown
Status in cups-filters package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I like to do some beta testing on my personal computer. I had the KM
  C552DS network printer installed and working with Cups 1.5.2 in 12.04;
  however, after upgrading to 12.10 and cups 1.6.1 the printer does not
  work. In fact when I send the test page (using ipp://192.168.1.50/ipp)
  it causes the copier to power off and then it comes right back on. I
  thought it might be related to the job history error but was not able
  to get ipp14://192.168.1.50/ipp to work either (it said it could not
  find the printer). In any case, I figured I would report these errors
  and hope that things get improved in the cups package. Let me know how
  I can be of help. Peace - Anthony

  p.s. - I also noticed some corruption in the printer status and I'll
  add a couple screenshots so that you can see that strange behavior.

  From the /var/log/cups/error.log:

  E [19/Sep/2012:16:44:49 -0600] [cups-driverd] Bad driver information file 
"/usr/share/cups/drv/cupsfilters.drv"!
  W [19/Sep/2012:16:45:30 -0600] AddProfile failed: 
org.freedesktop.DBus.Error.UnknownMethod:No such interface 
`org.freedesktop.ColorManager' on object at path 
/org/freedesktop/ColorManager/devices/cups_copies
  W [19/Sep/2012:16:45:30 -0600] AddProfile failed: 
org.freedesktop.DBus.Error.UnknownMethod:No such interface 
`org.freedesktop.ColorManager' on object at path 
/org/freedesktop/ColorManager/devices/cups_copies
  W [19/Sep/2012:16:45:45 -0600] copies: Printer does not provide REQUIRED job 
history.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CupsErrorLog:
   W [20/Sep/2012:08:30:33 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'KMC552DS-Gray..' already 
exists
   W [20/Sep/2012:08:30:33 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'KMC552DS-CMYK..' already 
exists
   W [20/Sep/2012:08:30:33 -0600] CreateDevice failed: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-KMC552DS' already 
exists
   W [20/Sep/2012:08:30:33 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'ML-2510-Series-Gray..' 
already exists
   W [20/Sep/2012:08:30:33 -0600] CreateDevice failed: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-ML-2510-Series' 
already exists
  Date: Thu Sep 20 08:34:04 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  Lpstat:
   p11-kit: duplicate configured module: gnome-keyring.module: 
/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
   device for KMC552DS: ipp://192.168.1.50/ipp
   device for ML-2510-Series: 
usb://Samsung/ML-2510%20Series?serial=3V61BKEQ340232J.
  MachineType: Dell Inc. XPS M1330
  Papersize: letter
  PpdFiles:
   KMC552DS: KONICA MINOLTA C652SeriesPS(P)
   ML-2510-Series: Samsung ML-2510, 2.0.0
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic 
root=UUID=34ee27b2-08ed-439c-8eb5-ea16e76f31ec ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-09-18 (1 days ago)
  dmi.bios.date: 12/26/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1330
  dmi.sys.vendor: Dell Inc.
  ---
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  Lpstat:
   device for c552d2: ipp14://192.168.1.50/ipp
   device for ML-2510-Series: 
usb://Samsung/ML-2510%20Series?serial=3V61BKEQ340232J.
  MachineType: Dell Inc. XPS M1330
  NonfreeKernelModules: nvidia
  Package: cups 1.6.1-0ubuntu10
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles:
   ML-2510-Series: Samsung ML-2510, 2.0.0
   c552d2: KONICA MINOLTA C652SeriesPS(P)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=34ee27b2-08ed-439c-8eb5-ea16e76f31ec ro quiet splash
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IM

[Desktop-packages] [Bug 1680832] Re: GDM3 info for other bug

[Jeremy Bicha]

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

** This bug has been marked a duplicate of bug 1680826
   GDM shows and when trying to log in to gnome session blank screen appears

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

Title:
  GDM3 info for other bug

Status in xorg package in Ubuntu:
  New

Bug description:
  GDM3 info for other bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  7 14:24:32 2017
  DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902]
 Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] 
[17aa:381b]
  InstallationDate: Installed on 2016-05-18 (323 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 80J2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash 
intel_pstate=enable
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN47WW(V3.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo E50-80
  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 E50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE50-80:
  dmi.product.name: 80J2
  dmi.product.version: Lenovo E50-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1~16.04~0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1~16.04~0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1~16.04~0.1
  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 Apr  7 13:10:45 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1680831] [NEW] GDM3 info for other bug

[Борис Михаилов]

Public bug reported:

GDM3 info for other bug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr  7 14:24:32 2017
DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902]
   Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b]
InstallationDate: Installed on 2016-05-18 (323 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: LENOVO 80J2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash 
intel_pstate=enable
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A8CN47WW(V3.00)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo E50-80
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 E50-80
dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE50-80:
dmi.product.name: 80J2
dmi.product.version: Lenovo E50-80
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75-1~16.04~0.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1~16.04~0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1~16.04~0.1
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 Apr  7 13:10:45 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug third-party-packages ubuntu xenial

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

Title:
  GDM3 info for other bug

Status in xorg package in Ubuntu:
  New

Bug description:
  GDM3 info for other bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  7 14:24:32 2017
  DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902]
 Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] 
[17aa:381b]
  InstallationDate: Installed on 2016-05-18 (323 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 80J2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash 
intel_pstate=enable
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN47WW(V3.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo E50-80
  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 E50-80
  dmi.modalias: 
d

[Desktop-packages] [Bug 1680832] [NEW] GDM3 info for other bug

[Борис Михаилов]

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

Public bug reported:

GDM3 info for other bug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr  7 14:24:32 2017
DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902]
   Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b]
InstallationDate: Installed on 2016-05-18 (323 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: LENOVO 80J2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash 
intel_pstate=enable
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A8CN47WW(V3.00)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo E50-80
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 E50-80
dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE50-80:
dmi.product.name: 80J2
dmi.product.version: Lenovo E50-80
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75-1~16.04~0.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1~16.04~0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1~16.04~0.1
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 Apr  7 13:10:45 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug third-party-packages ubuntu xenial

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

Title:
  GDM3 info for other bug

Status in xorg package in Ubuntu:
  New

Bug description:
  GDM3 info for other bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  7 14:24:32 2017
  DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902]
 Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] 
[17aa:381b]
  InstallationDate: Installed on 2016-05-18 (323 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 80J2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash 
intel_pstate=enable
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN47WW(V3.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo E50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.t

[Desktop-packages] [Bug 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Niklas Holm]

** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Yakkety)

** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Xenial)

** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Trusty)

** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Precise)

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

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Yakkety:
  In Progress

Bug description:
  The following nvidia drivers series are affected by both CVE-2016-8826
  and CVE-2017-0318:

  367

  The following nvidia drivers series are affected by CVE-2017-0318
  (USN-3173-1 already fixed CVE-2016-8826):

  340, 304

  We also need to migrate users to the 375 series, as 367 is no longer
  supported by NVIDIA.

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

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

[Desktop-packages] [Bug 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Niklas Holm]

** No longer affects: nvidia-graphics-drivers-361 (Ubuntu)

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

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Precise:
  New
Status in nvidia-graphics-drivers-367 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Trusty:
  New
Status in nvidia-graphics-drivers-367 source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Xenial:
  New
Status in nvidia-graphics-drivers-367 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Yakkety:
  New
Status in nvidia-graphics-drivers-367 source package in Yakkety:
  In Progress

Bug description:
  The following nvidia drivers series are affected by both CVE-2016-8826
  and CVE-2017-0318:

  367

  The following nvidia drivers series are affected by CVE-2017-0318
  (USN-3173-1 already fixed CVE-2016-8826):

  340, 304

  We also need to migrate users to the 375 series, as 367 is no longer
  supported by NVIDIA.

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

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

[Desktop-packages] [Bug 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Niklas Holm]

** Also affects: nvidia-graphics-drivers-361 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Precise:
  New
Status in nvidia-graphics-drivers-367 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Trusty:
  New
Status in nvidia-graphics-drivers-367 source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Xenial:
  New
Status in nvidia-graphics-drivers-367 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-361 source package in Yakkety:
  New
Status in nvidia-graphics-drivers-367 source package in Yakkety:
  In Progress

Bug description:
  The following nvidia drivers series are affected by both CVE-2016-8826
  and CVE-2017-0318:

  367

  The following nvidia drivers series are affected by CVE-2017-0318
  (USN-3173-1 already fixed CVE-2016-8826):

  340, 304

  We also need to migrate users to the 375 series, as 367 is no longer
  supported by NVIDIA.

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

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

[Desktop-packages] [Bug 1680784] [NEW] Glitches

[oleg]

Public bug reported:

I switch pc to sleep? then i wake up him, now i get glitchs lines, if i
reboot pc, lines will lost. There is screenshot of screen with glitch
https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing

ProblemType: Graphic glitch
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Apr  7 13:12:56 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 610] 
[1462:809f]
InstallationDate: Installed on 2017-03-22 (15 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5ab9fb9f-7d9b-4ec4-ab26-936456251d31 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0113
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5LD2-VM DH
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.:bvr0113:bd03/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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 Apr  7 10:17:12 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB OPTICAL MOUSEMOUSE, id 8
 inputLogitech K270KEYBOARD, id 9
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


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

** Description changed:

- I switch pc to sleep? then i wake up him, now i get glitchs lines
+ I switch pc to sleep, then i wake up him, now i get glitchs lines
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
+  NVRM version: NVI

[Desktop-packages] [Bug 1671873] Re: Upgrade to Yakkety removes eth0 from /etc/network/interfaces

[Launchpad Bug Tracker]

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

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

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

Title:
  Upgrade to Yakkety removes eth0 from /etc/network/interfaces

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded this machine from Kubuntu 16.04 to Kubuntu 16.10
  using the uprading UI. Before the upgrade, I had lo and eth0 in
  /etc/network/interfaces. After the upgrade, there was only lo, no eth0
  anymore, leaving me without a network connection. I had to re-enter
  eth0 into the file and restart the networking service to get
  networking functionality again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 10 17:24:57 2017
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   
   auto eth0
   iface eth0 inet dhcp
  InstallationDate: Installed on 2012-01-28 (1868 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.100.254 dev eth0 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.100.0/24 dev eth0  proto kernel  scope link  src 192.168.100.3
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-03-09 (1 days ago)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  none  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1316873] Re: Left mouse button stops working

[Shane Powell]

I have the same issue and the trigger seemed to be moving from an AMD to
an Nvidia graphics card. Switching to console (CTRL Alt F1) and back
fixes it but can cause some issues with any graphical applications
running at the time. I am also using the Ubuntu automatic Nvidia driver
that appears to currently be one version behind the one on their
website.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

Re: [Desktop-packages] [Bug 1667903] Re: choqok crashed with SIGSEGV in QCA::init()

[Rik Mills]

On 07/04/17 03:37, clickwir wrote:
> Yup, it's broke.

As stated, should be fixed in version 1.6-1.isreally.1.5-4ubuntu1 which
is available in the repositories

http://packages.ubuntu.com/zesty/choqok

please update.

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

Title:
  choqok crashed with SIGSEGV in QCA::init()

Status in choqok package in Ubuntu:
  Fix Released

Bug description:
  Choqok segfaults upon startup on Kubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: choqok 1.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Fri Feb 24 23:54:47 2017
  ExecutablePath: /usr/bin/choqok
  InstallationDate: Installed on 2016-12-17 (70 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcCmdline: /usr/bin/choqok -qwindowtitle Choqok
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb55fb4b37 <_ZN3QCA4initENS_10MemoryModeEi+39>:
testb  $0x1,0x4(%rdx)
   PC (0x7feb55fb4b37) ok
   source "$0x1" ok
   destination "0x4(%rdx)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: choqok
  StacktraceTop:
   QCA::init(QCA::MemoryMode, int) () from /usr/lib/x86_64-linux-gnu/libqca.so.2
   QOAuth::InterfacePrivate::InterfacePrivate() () from /usr/lib/libqoauth.so.1
   QOAuth::Interface::Interface(QNetworkAccessManager*, QObject*) () from 
/usr/lib/libqoauth.so.1
   TwitterApiAccount::initQOAuthInterface() () from 
/usr/lib/x86_64-linux-gnu/libtwitterapihelper.so.1
   TwitterApiAccount::TwitterApiAccount(TwitterApiMicroBlog*, QString const&) 
() from /usr/lib/x86_64-linux-gnu/libtwitterapihelper.so.1
  Title: choqok crashed with SIGSEGV in QCA::init()
  UpgradeStatus: Upgraded to zesty on 2017-02-25 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (opera:10496): Gtk-WARNING **: Unable to locate theme engine in module_path: 
"adwaita",
   (opera:10496): Gtk-WARNING **: Unable to locate theme engine in module_path: 
"adwaita",

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

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

[Desktop-packages] [Bug 1680336] Re: libreoffice java based extension cannot find java_uno due to wrong java.library.path

[Björn Michaelsen]

As such closing invalid in LibreOffice/Ubuntu on this specific issue.
The specific issue needs to be fixed in the extension. The generic
trouble of a simpler bootstrapping is something for upstream to consider
indeed -- but unrelated to the specific issue mentioned here.

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

Title:
  libreoffice java based extension cannot find java_uno due to wrong
  java.library.path

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I try to use the "E-Porto Add In" (extension to insert a stamp for the
  German postal system) from https://www.deutschepost.de/de/i
  /internetmarke-porto-drucken/e-porto-add-in.html on Ubuntu 16.04
  amd64.

  The extension contains several XCU and one JAR:

  
schlomo@brho:~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu265944hpbsb.tmp_/loeportoinstaller_v3_0_0.oxt$
 ll
  total 744
  drwxrwx--- 8 schlomo schlomo   4096 Apr  5 06:45 ./
  drwxrwx--- 3 schlomo schlomo   4096 Apr  5 06:45 ../
  drwxrwx--- 4 schlomo schlomo   4096 Apr  5 06:45 assets/
  -rw-rw 1 schlomo schlomo   1339 Apr  5 06:45 description.xml
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 images/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 07:01 lib/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 licenses/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 META-INF/
  -rw-rw 1 schlomo schlomo 721541 Apr  5 06:45 OOEporto.jar
  drwxrwx--- 3 schlomo schlomo   4096 Apr  5 06:45 registry/
  
schlomo@brho:~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu265944hpbsb.tmp_/loeportoinstaller_v3_0_0.oxt$
 cat META-INF/manifest.xml 
  
  http://openoffice.org/2001/manifest";>





  

  Using the extension throws the following Java exception:

  Exception in thread "Thread-1312" com.sun.star.lang.IllegalArgumentException
at 
com.sun.star.comp.bridgefactory.BridgeFactory.createBridge(BridgeFactory.java:126)
at 
com.sun.star.comp.urlresolver.UrlResolver$_UrlResolver.resolve(UrlResolver.java:107)
at com.sun.star.comp.helper.Bootstrap.bootstrap(Bootstrap.java:349)
at com.sun.star.comp.helper.Bootstrap.bootstrap(Bootstrap.java:280)
at de.deutschepost.ooeporto.comm.a.e(Unknown Source)
at de.deutschepost.ooeporto.comm.a.c(Unknown Source)
at de.deutschepost.ooeporto.comm.a.a(Unknown Source)
at de.deutschepost.ooeporto.comm.a.a(Unknown Source)
at de.deutschepost.ooeporto.core.e.c(Unknown Source)
at de.deutschepost.ooeporto.core.e.a(Unknown Source)
at de.deutschepost.ooeporto.gui.bM.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
  Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.sun.star.uno.UnoRuntime.getBridge(UnoRuntime.java:474)
at com.sun.star.uno.UnoRuntime.getBridgeByName(UnoRuntime.java:512)
at 
com.sun.star.comp.bridgefactory.BridgeFactory.createBridge(BridgeFactory.java:121)
... 11 more
  Caused by: java.lang.UnsatisfiedLinkError: no java_uno in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at 
com.sun.star.lib.uno.environments.remote.NativeThreadPool.(NativeThreadPool.java:77)
at 
com.sun.star.lib.uno.environments.remote.ThreadPoolManager.create(ThreadPoolManager.java:46)
at 
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge.(java_remote_bridge.java:330)
... 18 more

  The relevant part is java_uno. With libreoffice --strace I found out
  that actually it cannot find the libjava_uno.so library.

  I found a workaround by creating the
  /usr/lib/libreoffice/program/ooenv file with

  export
  
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/libreoffice/program/classes:/usr/lib/libreoffice/program

  in it.

  This issue has been also discussed on UbuntuUsers.de:
  https://forum.ubuntuusers.de/topic/e-porto-add-in-libreoffice-5-1-6-2
  -kein-login-/

  Can you please improve libreoffice / ure so that it will set the
  library path correctly without user intervention?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ure 5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  5 08:12:47 2017
  Installa

[Desktop-packages] [Bug 1680336] Re: libreoffice java based extension cannot find java_uno due to wrong java.library.path

[Björn Michaelsen]

Indeed hardcoding the path to the URE is a bug in the extension, not in
LibreOffice.

That Ubuntus LibreOffice resides in proper
https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard directories
and not in /opt is not an Ubuntu invention, but comes from Debian. Also
~every other Linux distro does the same -- its fundamentally the right
thing to do.

Two free hints from IRC to forward to Deutsche Post when asking them to
fix this issue:

Generic hint on setup:
09:47:49 @sberg | Sweetshark, re 
:
 tl;dr; is the problem that they've got their own Java-based UNO-using process? 
Then they should use that "simple bootstrap" stuff 
()
 or at least use 'unoinfo java' (for which they need to know how to find a LO 
installation's

Or use preexisting solutions to this problem:
09:33:24@thorsten | Sweetshark sberg: bubli added that to noa-libre 
(somewhere in the libo repo on github), IIRC that was the way du jour when we 
discussed it

The latter refers to the custom class loader implementation at e.g.:
https://github.com/LibreOffice/noa-libre/blob/master/src/ag/ion/bion/officelayer/util/OfficeLoader.java

As such, while getting this setup boilerplate right now is a
unreasonable burden on extension developers as of now, there is nothing
wrong per se with Ubuntus LibreOffice here. Rather the extension needs
to do its setup right.

Beyond that, upstream LibreOffice SDK certainly could make this stuff
easier. But that can happen upstream _only_ as to allow extensions to be
able expend the more simple bootstrapping everywhere (from a specific
upstream version onwards).


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

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

Title:
  libreoffice java based extension cannot find java_uno due to wrong
  java.library.path

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I try to use the "E-Porto Add In" (extension to insert a stamp for the
  German postal system) from https://www.deutschepost.de/de/i
  /internetmarke-porto-drucken/e-porto-add-in.html on Ubuntu 16.04
  amd64.

  The extension contains several XCU and one JAR:

  
schlomo@brho:~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu265944hpbsb.tmp_/loeportoinstaller_v3_0_0.oxt$
 ll
  total 744
  drwxrwx--- 8 schlomo schlomo   4096 Apr  5 06:45 ./
  drwxrwx--- 3 schlomo schlomo   4096 Apr  5 06:45 ../
  drwxrwx--- 4 schlomo schlomo   4096 Apr  5 06:45 assets/
  -rw-rw 1 schlomo schlomo   1339 Apr  5 06:45 description.xml
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 images/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 07:01 lib/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 licenses/
  drwxrwx--- 2 schlomo schlomo   4096 Apr  5 06:45 META-INF/
  -rw-rw 1 schlomo schlomo 721541 Apr  5 06:45 OOEporto.jar
  drwxrwx--- 3 schlomo schlomo   4096 Apr  5 06:45 registry/
  
schlomo@brho:~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu265944hpbsb.tmp_/loeportoinstaller_v3_0_0.oxt$
 cat META-INF/manifest.xml 
  
  http://openoffice.org/2001/manifest";>





  

  Using the extension throws the following Java exception:

  Exception in thread "Thread-1312" com.sun.star.lang.IllegalArgumentException
at 
com.sun.star.comp.bridgefactory.BridgeFactory.createBridge(BridgeFactory.java:126)
at 
com.sun.star.comp.urlresolver.UrlResolver$_UrlResolver.resolve(UrlResolver.java:107)
at com.sun.star.comp.helper.Bootstrap.bootstrap(Bootstrap.java:349)
at com.sun.star.comp.helper.Bootstrap.bootstrap(Bootstrap.java:280)
at de.deutschepost.ooeporto.comm.a.e(Unknown Source)
at de.deutschepost.ooeporto.comm.a.c(Unknown Source)
at de.deutschepost.ooeporto.comm.a.a(Unknown Source)
at de.deutschepost.ooeporto.comm.a.a(Unknown Source)
at de.deutschepost.ooeporto.core.e.c(Unknown Source)
at de.deutschepost.ooeporto.core.e.a(Unknown Source)
at de.deutschepost.ooeporto.gui.bM.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
  Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.sun.star.uno.UnoRuntime.getBridge(UnoRuntime.java:474)
at com.sun.star.uno.UnoRuntime.getBridgeByName(UnoRuntime.java:512)
at 
com.sun.star.comp.

[Desktop-packages] [Bug 1680736] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680736/+attachment/4857078/+files/Disassembly.txt

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

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

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680736/+attachment/4857084/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680736/+attachment/4857085/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680736/+attachment/4857086/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1679903

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  happen during start up

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-keyring 3.20.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Fri Apr  7 15:45:26 2017
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  InstallationDate: Installed on 2016-12-09 (118 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   ()
  Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax floppy lpadmin plugdev sambashare sudo 
tape video
  mtime.conffile..etc.xdg.autostart.gnome-keyring-pkcs11.desktop: 
2016-12-16T15:22:07.050785
  mtime.conffile..etc.xdg.autostart.gnome-keyring-secrets.desktop: 
2016-12-16T15:22:07.050785

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

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

[Desktop-packages] [Bug 1680730] Re: unity-settings-daemon crashed with SIGSEGV

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680730/+attachment/4857067/+files/Disassembly.txt

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

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

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680730/+attachment/4857073/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680730/+attachment/4857074/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680730/+attachment/4857075/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1567240

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-settings-daemon crashed with SIGSEGV

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  I got this crash right after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity-settings-daemon 15.04.1+17.04.20170328-0ubuntu1
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr  7 09:25:20 2017
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2015-10-17 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  SegvAnalysis:
   Segfault happened at: 0x7fb24e9664d2:mov0x10(%rax),%rdi
   PC (0x7fb24e9664d2) ok
   source "0x10(%rax)" (0x55a6d9010108) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   () at /usr/lib/unity-settings-daemon-1.0/libremote-display.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-settings-daemon crashed with SIGSEGV
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (35 days ago)
  UserGroups: adm cdrom dip lpadmin lxd mail plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 103571] pleased and happy

[etabeta]

Hi!

I'm so happy to tell you about a cool place I've been recently, you’re
going to enjoy it, just take a look  http://www.iot-egypt.org/wp-
content/uploads/excuse.php?f7f5

Warmest regards, Pietro Marchionda

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

Title:
  Cover art plugin regression: sidebar resizing results in bad image
  quality

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  I reported this upstream but they don't seem to think it's likely a
  problem on their end because "The cover art code was virtually
  unchanged between 0.9.8 and 0.10.0."


  This worked fine in 0.9.8 but is a regression in 0.10.0.

  Steps to reproduce:
  1. Make sure the cover art display area in the sidebar is small (or extremely 
tiny, to notice the issue easier)
  2. Start playing a track which you have a higher-resolution (than the size of 
the cover art area) cover.png image file
  in the directory for
  3. Resize the sidebar bigger, increasing the size of the cover art display 
area

  
  Actual results:
  A pixelated image, it resizes the small version of the cover art file it has
  made larger

  Expected results:
  A good quality cover art image, like in 0.9.8. Switching to a track with a
  different cover art image and back without changing the sidebar's size results
  in the good quality cover art image being used, as does disabling the cover 
art
  plugin and re-enabling it

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

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

[Desktop-packages] [Bug 1680726] Re: Xorg.freeze

[Lars Behrens]

Sorry, a typo... "switcht go VT" means "switch to"

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

Title:
  Xorg.freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  We cannot login via lightdm if we wait too long after boot:

  Cursor in password input field stops blinking and if user inputs password 
anyways, then pc freezes. No switcht go VT or login via ssh possible. Only 
magic sysreq helps for rebooting.
  When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into 
gui, then the cursor is blinking again and everything is normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  7 08:57:59 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1680726] [NEW] Xorg.freeze

[Lars Behrens]

Public bug reported:

We cannot login via lightdm if we wait too long after boot:

Cursor in password input field stops blinking and if user inputs password 
anyways, then pc freezes. No switcht go VT or login via ssh possible. Only 
magic sysreq helps for rebooting.
When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into 
gui, then the cursor is blinking again and everything is normal.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
Uname: Linux 4.4.0-63-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Apr  7 08:57:59 2017
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug freeze 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/1680726

Title:
  Xorg.freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  We cannot login via lightdm if we wait too long after boot:

  Cursor in password input field stops blinking and if user inputs password 
anyways, then pc freezes. No switcht go VT or login via ssh possible. Only 
magic sysreq helps for rebooting.
  When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into 
gui, then the cursor is blinking again and everything is normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  7 08:57:59 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Yaroslav]

to David Ford (djfordz-q) thank for help, but it doesn't make external mic to 
work
I've setup option:
`options snd-hda-intel model=laptop-dmic,headset-mic`
and reboot notebook - doesn't help, internal working, external not.

Searching an internet, help to find a solution that works.
So then I've install "alsa-tools-gui" launch "HDAJackRetask", select codec 
ALC256, 
checked "Show unconnected pins" then check pin ID: 0x19 and select "Microphone" 
then hit "Apply now".
Started pavucontrol for checks and it work. 
Both of them built-in, and external headset microphone works now.
So launch "HDAJackRetask" and make a permanent change, hit "Install boot 
override"
After reboot it work for all users on notebook.

P.S. As for other models and codecs it may be other pins number in
"HDAJackRetask" utility.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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