[Ubuntu-x-swat] [Bug 1698609] [NEW] Ubuntu running slow

2017-06-17 Thread Jalo Moster 
Public bug reported:

1.) When I use the shortcut CTRL+ALT+T to open a terminal, it takes a while to 
load.
2.) When I try to open Google Chrome or Chromium, I get a very big delay 
followed by a black screen before the browser loads.
3.) When I hold my laptop close to my ear, I can hear some small buzzing sounds 
that I am a little concerned about.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Jun 18 00:31:09 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:075b]
InstallationDate: Installed on 2017-06-07 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=30d3e102-c256-4697-b0f1-f0ae1abdb6a2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 05HM5Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell 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 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

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


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

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

Title:
  Ubuntu running slow

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1691486] Re: Mouse cursor jumps to top left corner on click+drag

2017-06-17 Thread David R. Hedges 
I admit I don't fully understand how the "Coordinate Transformation
Matrix" works (well, especially in the context of a mouse instead of a
trackpad or something), but it appears that's the trigger for this
issue.

After I eliminated that modified Coordinate Transformation Matrix, the
dragging/jump issue disappeared.

(For anyone else who happens to have the same problem, I was able to solve the 
mouse hyper-sensitivity issue like this instead:
  xinput set-prop "Razer Razer DeathAdder" "libinput Accel Speed" "-0.3"
  xinput set-prop "Razer Razer DeathAdder" "libinput Accel Profile Enabled" 0, 1

Thanks to https://patrickmn.com/aside/lowering-gaming-mouse-sensitivity-
in-ubuntu-9-10/ (updated) and http://mouseaccuracy.com/ for helping me
decide on a comfortable value.)

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

Title:
  Mouse cursor jumps to top left corner on click+drag

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698594] [NEW] Kubuntu Installer for 17.04 crashes reproducable with a too small /boot partition due to "No space left on device"

2017-06-17 Thread andy 
Public bug reported:

Hello,

i have experienced reproducable crashes of the installer. The problem
seems to be that my boot partition is to small. I have a /boot partition
of about 100 MB

The problem seems to be that the initrd file in the boot partition is
very big and cannot be properly updated.

Is there a restriction to the size of a /boot partition? 100 MB seems to
be way to little, even though the initial installation is possible. But
at the end of the installation process the installer crashes.

= start  -> see full log at the end of the report
update-initramfs: Generating /boot/initrd.img-4.10.0-22-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
= end 


I used my existing paritions and i would at least expect a warning (hint) that 
the /boot partition needs to be of a certain size (or just prevents 
installation with a too small boot partition).

I am also having problems updating the kernel, which seems to be the
same cause of the crash of the installer:


here is some information:

wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x241c6624

Device Boot Start   End   Sectors   Size Id Type
/dev/sda1  * 2048 390625279 390623232 186,3G  7 HPFS/NTFS/exFAT
/dev/sda2   390625280 39081983919456095M 83 Linux
/dev/sda3   390819840 586131455 195311616  93,1G 83 Linux
/dev/sda4   586133502 976771071 390637570 186,3G  5 Extended
/dev/sda5   586133504 586717183583680   285M 82 Linux swap / Solaris
/dev/sda6   586719232 976771071 390051840   186G 83 Linux


wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=4042808k,nr_inodes=1010702,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=813128k,mode=755)
/dev/sda3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=3715)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda2 on /boot type ext2 (rw,relatime,block_validity,barrier,user_xattr,acl)
/dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/119 type tmpfs 
(rw,nosuid,nodev,relatime,size=813124k,mode=700,uid=119,gid=127)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=813124k,mode=700,uid=1000,gid=1000)
/dev/sda1 on /mnt/ntfs type fuseblk 
(rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)


wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo apt-get upgrade -u
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up initramfs-tools (0.125ubuntu9) ...

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

2017-06-17 Thread Robert M. Muncrief 
Yes Micheal, that's all anyone confronted with this bug needs to do
initially so they can boot.

After booting they should also open a terminal and issue one of the
following commands:

For amd64 systems:
sudo apt-mark hold libepoxy-dev libepoxy0 libepoxy0:i386

For i386 systems:
sudo apt-mark hold libepoxy-dev libepoxy0

This will prevent libepoxy0 from being updated until this bug is fixed.
Note that if you use programs like Synaptic libepoxy0 needs to be locked
there as well.

And by the way, the only reason I wasn't able to use recovery mode
initially was because I didn't know libepoxy0 was the culprit. About 15
updates appeared together, with several of them being for Mir which is
what I initially suspected caused the problem. Since I wasn't sure what
was wrong it took awhile for me to whittle it down to libepoxy0.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

2017-06-17 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

2017-06-17 Thread Michael 
I can confirm this.

Linux Mint 18.1 Serena
Linux Kernel 4.4.0-79-generic
AMDGPU-PRO 16.40-348864

After libepoxy update from 1.3.1-1 to 1.3.1-1ubuntu0.16.04.1 I got a black 
screen on system boot. However, in contrast to the original submission, I was 
able to boot into recovery mode and downgrade libepoxy with 
sudo apt-get install libepoxy0=libepoxy1.3.1-1

This solved the problem for me.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-06-17 Thread FFab 
https://bugs.freedesktop.org/show_bug.cgi?id=101483

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

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-06-17 Thread FFab 
to comment #18
filed upstream 

** Bug watch added: freedesktop.org Bugzilla #101483
   https://bugs.freedesktop.org/show_bug.cgi?id=101483

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-17 Thread Zhanglei Mao 
Translate from Huawei's reply mail: The sever board have only this VGA PCI 
devices: 
   19e5  Huawei Technologies Co., Ltd.
   1711  Hi1710 [iBMC Intelligent Management system chip w/VGA support]

Please check if this math to our D05 testing environment.

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-x-swat] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-17 Thread Zhanglei Mao 
hi Danneil,

Those are translate from Huawei's reply mail:

The sever board have only this VGA PCI devices:
   19e5 Huawei Technologies Co., Ltd.
   1711 Hi1710 [iBMC Intelligent Management system chip w/VGA support]

Please check if this math to our D05 testing environment.

thanks,
Mao

On Fri, Jun 16, 2017 at 4:21 PM, Zhanglei Mao 
wrote:

> hi Daniel,
>
> It is very nice for your to provide a patch for it. For other PCI IDs, I
> will check with Huawei team and back to you at next week.
>
> By the way, what is status of first bug ( The busid reported by libdrm on
> the arm64 system is "0007:a1:00.0"), has it been accept by upstram? Do you
> have bug id for it? Actually, I think we can take both those 2 bugs back to
> Huawei or Pearl team in case it is bugs from Kernel.
>
> thanks,
> Mao
>
> On Fri, Jun 16, 2017 at 11:46 AM, Daniel Axtens <
> daniel.axt...@canonical.com> wrote:
>
>> Hi Mao,
>>
>> I have done more work on the HiSilicon board. I have talked with the SEG
>> team and our conclusion is that the hardware is not compliant with the
>> specification, but that it is appropriate to include a workaround in
>> software.
>>
>> I have developed a patch that adds a workaround or 'quirk' to the kernel
>> specifically for the hisilicon graphics card and the hisilicon PCI
>> bridge. It tests for the card and the bridge on the development board. I
>> think it might be acceptable for upstream. With this, X
>> autoconfiguration works.
>>
>> Please could you ask the HiSilicon people if there are other boards or
>> parts with different PCI IDs that should be included in this fixup?
>>
>> Regards,
>> Daniel
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1691991
>>
>> Title:
>>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>>
>> Status in xorg package in Ubuntu:
>>   New
>>
>> Bug description:
>>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>>   [sudo] password for ubuntu:
>>
>>   X.Org X Server 1.18.4
>>   Release Date: 2016-07-19
>>   X Protocol Version 11, Revision 0
>>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
>> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
>> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
>> earlycon=pl011,mmio,0x602B console=tty0
>>   Build Date: 02 November 2016  10:05:28PM
>>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
>> http://www.ubuntu.com/support)
>>   Current version of pixman: 0.33.6
>> Before reporting problems, check http://wiki.x.org
>> to make sure that you have the latest version.
>>   Markers: (--) probed, (**) from config file, (==) default setting,
>> (++) from command line, (!!) notice, (II) informational,
>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>   pci id for fd 10: 19e5:1711, driver (null)
>>   EGL_MESA_drm_image required.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>>   (EE)
>>   (EE) Segmentation fault at address 0xa0
>>   (EE)
>>   Fatal server error:
>>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>>   (EE)
>>   (EE)
>>   Please consult the The X.Org Foundation support
>>  at http://wiki.x.org
>>for help.
>>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
>> additional information.
>>   (EE)
>>   (EE) Server terminated with error (1). Closing log file.
>>   Aborted (core dumped)
>>   ubuntu@ubuntu:~$
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/
>> +subscriptions
>>
>
>
>
> --
> Zhanglei Mao
> Solutions Architect, Sales and Business Development
> Canonical Group Ltd.
> zhanglei@canonical.com
> +86-13625010929 <+86%20136%202501%200929> (m)
> +852-6700 6026 <+852%206700%206026> (m)
> www.ubuntu.com
> www.canonical.com
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@canonical.com
+86-13625010929 (m)
+852-6700 6026 (m)
www.ubuntu.com
www.canonical.com

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   :

[Ubuntu-x-swat] [Bug 1698516] [NEW] package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package lib

2017-06-17 Thread Henry 
Public bug reported:

Was doing a regular sudo apt-get upgrade and got an error all of a
sudden.  Was expected a clean upgrade with no intervention like now the
upgrade normally works.

Description:Ubuntu 16.04.2 LTS
Release:16.04

apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 11.2.0-1ubuntu2.2
  Candidate: 12.0.6-0ubuntu0.16.04.1
  Version table:
 12.0.6-0ubuntu0.16.04.1 500
500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-updates/main amd64 
Packages
500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 11.2.0-1ubuntu2.2 100
100 /var/lib/dpkg/status
 11.2.0-1ubuntu2 500
500 mirror://mirrors.ubuntu.com/mirrors.txt xenial/main amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgl1-mesa-dri 11.2.0-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.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.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jun 16 23:12:47 2017
DistUpgraded: 2016-08-14 23:56:55,953 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-34-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-36-generic, x86_64: installed
DuplicateSignature:
 package:libgl1-mesa-dri:11.2.0-1ubuntu2.2
 Unpacking libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1) over 
(11.2.0-1ubuntu2.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_12.0.6-0ubuntu0.16.04.1_amd64.deb 
(--unpack):
  trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from 
other instances of package libgl1-mesa-dri:amd64
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2768]
InstallationDate: Installed on 2015-02-08 (860 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5f6d3d07-0215-46db-9fea-737305a33e02 ro rootflags=subvol=@ nomodeset 
nomdmonddf nomdmonisw
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: mesa
Title: package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
UpgradeStatus: Upgraded to xenial on 2016-08-15 (305 days ago)
dmi.bios.date: 01/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0904
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0904:bd01/06/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.68+git1604280630.fc09c5~gd~t
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev:

[Ubuntu-x-swat] [Bug 1698516] Re: package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl

2017-06-17 Thread Apport retracing service 
** Tags removed: need-duplicate-check

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

Title:
  package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade:
  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:amd64

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp