from:"Piotr Kołaczkowski"

Looks like a bug in the memory allocator.

Running fine under tcmalloc_minimal:
root@p5520:/home/pkolaczk# export 
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/libtcmalloc_minimal.so.4"
root@p5520:/home/pkolaczk# NetworkManager --debug
  [1538139465.9143] NetworkManager (version 1.12.2) is starting... (after 
a restart)
  [1538139465.9143] Read config: /etc/NetworkManager/NetworkManager.conf 
(lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, 
no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, 
default-wifi-powersave-on.conf)
...
  [1538139466.1844] manager: rfkill: WWAN enabled by radio killswitch; 
disabled by state file
iface-state: 'external')
  [1538139473.5529] device (tun0): state change: secondaries -> activated 
(reason 'none', sys-iface-state: 'external')
  [1538139473.5622] device (tun0): Activation: successful, device 
activated.
// no crash

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

Title:
  Network manager crashes and restarts 2 seconds after establishing a
  VPN connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  When trying to get on a company VPN, the connection is initially
  established and works (I can access intranet websites), but after ~1-2
  seconds from starting VPN connection the Network Manager seems to
  crash and restart, taking all connections down. This makes VPN totally
  unusable.

  syslog:

  
  // VPN activation:
  ...
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running 
ordered scripts...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5368] device 
(tun0): Activation: starting connection 'tun0' 
(6bd0ba91-b53b-4e9a-b94c-394a9a9f336b)
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5370] device 
(tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5377] device 
(tun0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5382] device 
(tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5384] device 
(tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5391] device 
(tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5396] device 
(tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service.
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5471] device 
(tun0): Activation: successful, device activated.

  // VPN active and usable - why can't it stay so?

  Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: 
(/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open 
/var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu
  Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered 
scripts...
  Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.

  // Something fishy here:

  Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted 
chunks 3
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
  Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was 
not added
  Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing 
a network device that was not added]
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service:

[Desktop-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection

Retried a few times and it works fine under valgrind.

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

Title:
  Network manager crashes and restarts 2 seconds after establishing a
  VPN connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  When trying to get on a company VPN, the connection is initially
  established and works (I can access intranet websites), but after ~1-2
  seconds from starting VPN connection the Network Manager seems to
  crash and restart, taking all connections down. This makes VPN totally
  unusable.

  syslog:

  
  // VPN activation:
  ...
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running 
ordered scripts...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5368] device 
(tun0): Activation: starting connection 'tun0' 
(6bd0ba91-b53b-4e9a-b94c-394a9a9f336b)
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5370] device 
(tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5377] device 
(tun0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5382] device 
(tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5384] device 
(tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5391] device 
(tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5396] device 
(tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service.
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5471] device 
(tun0): Activation: successful, device activated.

  // VPN active and usable - why can't it stay so?

  Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: 
(/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open 
/var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu
  Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered 
scripts...
  Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.

  // Something fishy here:

  Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted 
chunks 3
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
  Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was 
not added
  Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing 
a network device that was not added]
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 5.
  Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online.
  Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online...
  Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 1581 (dhclient) in control group while starting unit. Ignoring.
  Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination 
of a previous run, or service implementation deficiencies.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 7924 (dhclient) in control group while starting unit. Ignoring.
  Sep 28

[Desktop-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection

Ok, I did some debugging and this looks really weird.
First, trying to run NetworkManager --debug manually:

  [1538138381.5570] audit: op="connection-activate" 
uuid="1a43441b-6b26-4e0c-8343-976afcf790fd" name="DataStax" pid=3717 uid=1001 
result="success"
  [1538138381.5755] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",0]:
 Started the VPN service, PID 8148
  [1538138381.5973] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",0]:
 Saw the service appear; activating connection
  [1538138381.6059] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",0]:
 VPN plugin: state changed: starting (3)
  [1538138381.6060] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",0]:
 VPN connection: (ConnectInteractive) reply received
  [1538138381.6485] manager: (tun0): new Tun device 
(/org/freedesktop/NetworkManager/Devices/6)
  [1538138381.6586] devices added (path: /sys/devices/virtual/net/tun0, 
iface: tun0)
  [1538138381.6586] device added (path: /sys/devices/virtual/net/tun0, 
iface: tun0): no ifupdown configuration found.
  [1538138382.5173] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",0]:
 VPN connection: (IP4 Config Get) reply received from old-style plugin
  [1538138382.5177] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data: VPN Gateway: 12.111.84.106
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data: Tunnel Device: "tun0"
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data: IPv4 configuration:
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Internal Address: 10.150.1.247
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Internal Prefix: 32
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Internal Point-to-Point Address: 10.150.1.247
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Static Route: 0.0.0.0/0   Next Hop: 0.0.0.0
  [1538138382.5178] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Static Route: 10.150.1.247/32   Next Hop: 0.0.0.0
  [1538138382.5179] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Internal DNS: 10.200.1.10
  [1538138382.5179] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   Internal DNS: 10.200.1.11
  [1538138382.5179] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data:   DNS Domain: 'datastax.lan'
  [1538138382.5179] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 Data: No IPv6 configuration
  [1538138382.5179] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 VPN plugin: state changed: started (4)
  [1538138382.5447] 
vpn-connection[0x55c2f915e0b0,1a43441b-6b26-4e0c-8343-976afcf790fd,"DataStax",7:(tun0)]:
 VPN connection: (IP Config Get) complete
  [1538138382.5451] device (tun0): state change: unmanaged -> unavailable 
(reason 'connection-assumed', sys-iface-state: 'external')
  [1538138382.5796] keyfile: add connection in-memory 
(b59f240b-d74e-4c9f-a5c7-219cdff8374d,"tun0")
  [1538138382.5809] device (tun0): state change: unavailable -> 
disconnected (reason 'connection-assumed', sys-iface-state: 'external')
  [1538138382.5819] device (tun0): Activation: starting connection 'tun0' 
(b59f240b-d74e-4c9f-a5c7-219cdff8374d)
  [1538138382.5824] device (tun0): state change: disconnected -> prepare 
(reason 'none', sys-iface-state: 'external')
  [1538138382.5829] device (tun0): state change: prepare -> config 
(reason 'none', sys-iface-state: 'external')
  [1538138382.5833] device (tun0): state change: config -> ip-config 
(reason 'none', sys-iface-state: 'external')
  [1538138382.5840] device (tun0): state change: ip-config -> ip-check 
(reason 'none', sys-iface-state: 'external')
  [1538138382.5852] device (tun0): state change: ip-check -> secondaries 
(reason 'none', sys-iface-state: 'external')
  [1538138382.5854] device (tun0): state change: secondaries -> activated 
(reason 'none', sys-iface-state: 'external')
  [1538138382.5913] device (tun0): Activation: successful, device 
activated.
Naruszenie ochrony pamięci  ///  SIGSEGV (crash)


Then trying to do the same under valgrind:
  [1538138423.6684] audit: op="connection-activate" 
uuid="1a43441b-6b26-4e0c-8343-976afcf790fd" name="DataStax" pid=3717 uid=1001 
result="success"
==9083== 
==9083== HEAP SUMMARY:
==9083== in use at exit: 1,070,170 bytes

[Desktop-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection

Tried rebooting the laptop / replugging the dock / rebooting the dock. No 
change.
My TB16 firmware is up-to-date.

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

Title:
  Network manager crashes and restarts 2 seconds after establishing a
  VPN connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  When trying to get on a company VPN, the connection is initially
  established and works (I can access intranet websites), but after ~1-2
  seconds from starting VPN connection the Network Manager seems to
  crash and restart, taking all connections down. This makes VPN totally
  unusable.

  syslog:

  
  // VPN activation:
  ...
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running 
ordered scripts...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5368] device 
(tun0): Activation: starting connection 'tun0' 
(6bd0ba91-b53b-4e9a-b94c-394a9a9f336b)
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5370] device 
(tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5377] device 
(tun0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5382] device 
(tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5384] device 
(tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5391] device 
(tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5396] device 
(tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service.
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5471] device 
(tun0): Activation: successful, device activated.

  // VPN active and usable - why can't it stay so?

  Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: 
(/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open 
/var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu
  Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered 
scripts...
  Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.

  // Something fishy here:

  Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted 
chunks 3
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
  Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was 
not added
  Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing 
a network device that was not added]
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 5.
  Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online.
  Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online...
  Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 1581 (dhclient) in control group while starting unit. Ignoring.
  Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination 
of a previous run, or service implementation deficiencies.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 7924 (dhclient)

[Desktop-packages] [Bug 1794966] [NEW] Network manager crashes and restarts 2 seconds after establishing a VPN connection

Public bug reported:

When trying to get on a company VPN, the connection is initially
established and works (I can access intranet websites), but after ~1-2
seconds from starting VPN connection the Network Manager seems to crash
and restart, taking all connections down. This makes VPN totally
unusable.

syslog:


// VPN activation:
...
Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 
scripts)
Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running 
ordered scripts...
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5368] device 
(tun0): Activation: starting connection 'tun0' 
(6bd0ba91-b53b-4e9a-b94c-394a9a9f336b)
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5370] device 
(tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'external')
Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service...
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5377] device 
(tun0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5382] device 
(tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5384] device 
(tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 
'external')
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5391] device 
(tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 
'external')
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5396] device 
(tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 
'external')
Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service.
Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5471] device 
(tun0): Activation: successful, device activated.

// VPN active and usable - why can't it stay so?

Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 scripts)
Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: 
(/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open 
/var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu
Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered 
scripts...
Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.

// Something fishy here:

Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted chunks 
3
Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process exited, 
code=dumped, status=6/ABRT
Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was not 
added
Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing a 
network device that was not added]
Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 5.
Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online.
Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online...
Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager.
Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 1581 (dhclient) in control group while starting unit. Ignoring.
Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination of 
a previous run, or service implementation deficiencies.
Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 7924 (dhclient) in control group while starting unit. Ignoring.
Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination of 
a previous run, or service implementation deficiencies.
Sep 28 13:48:30 p5520 systemd[1]: Starting Network Manager...
Sep 28 13:48:30 p5520 NetworkManager[8337]:   [1538135310.5754] 
NetworkManager (version 1.12.2) is starting... (after a restart)
Sep 28 13:48:30 p5520 NetworkManager[8337]:   [1538135310.5754] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf,

[Desktop-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection

The problem seem to exist only if the laptop is connected to wired connection 
through TB16 dock. 
Otherwise, when on WiFi, VPN connects fine and stays stable.

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

Title:
  Network manager crashes and restarts 2 seconds after establishing a
  VPN connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  When trying to get on a company VPN, the connection is initially
  established and works (I can access intranet websites), but after ~1-2
  seconds from starting VPN connection the Network Manager seems to
  crash and restart, taking all connections down. This makes VPN totally
  unusable.

  syslog:

  
  // VPN activation:
  ...
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running 
ordered scripts...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5368] device 
(tun0): Activation: starting connection 'tun0' 
(6bd0ba91-b53b-4e9a-b94c-394a9a9f336b)
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5370] device 
(tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service...
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5377] device 
(tun0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5382] device 
(tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5384] device 
(tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5391] device 
(tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5396] device 
(tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 
'external')
  Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service.
  Sep 28 13:48:22 p5520 NetworkManager[6892]:   [1538135302.5471] device 
(tun0): Activation: successful, device activated.

  // VPN active and usable - why can't it stay so?

  Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 
scripts)
  Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: 
(/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open 
/var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu
  Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered 
scripts...
  Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
  Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server.
  Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server.

  // Something fishy here:

  Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted 
chunks 3
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
  Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was 
not added
  Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing 
a network device that was not added]
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 5.
  Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online.
  Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online...
  Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager.
  Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over 
process 1581 (dhclient) in control group while starting unit. Ignoring.
  Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination 
of a previous run, or service implementation deficiencies.
  Sep 28 13:48:30 p5520 systemd[1]:

[Desktop-packages] [Bug 1681249] Re: tracker-extract crashed with signal 31 in chdir()

2018-09-24 Thread Piotr Kołaczkowski

It is happening for me in Ubuntu 18.10.

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

Title:
  tracker-extract crashed with signal 31 in chdir()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  tracker crash while indexing my homedir

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-extract 1.12.0-0ubuntu1
  Uname: Linux 4.10.8-041008-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr  8 14:00:45 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-extract
  ExecutableTimestamp: 1490023113
  JournalErrors:
   No journal files were found.
   -- No entries --
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcCwd: /home/bonnaudl
  Signal: 31
  SourcePackage: tracker
  Title: tracker-extract crashed with signal 31 in chdir()
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

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

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

[Desktop-packages] [Bug 1735986] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1735986/+attachment/5017752/+files/ProcCpuinfoMinimal.txt

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the mouse button, the window
  shrinks to 2x smaller, so it adapts to lower DPI of that screen.
  Everything is sharp and crispy and the sizes are ok.

  
  Problems:

  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly
  on the external screen. Everything is twice too big. When started,
  they appear first on the built-in hiDPI screen with the correct size,
  but after dragging to the external screen, they remain scaled by 200%.

  * When I enabled dock to be displayed on all screens, the dock icons
  are twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.

  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is
  only twice too large when over the desktop background, but ok when
  over an application window. This is a very minor issue, but looks
  funny.

  -
  What I tried so far:

  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.

  Then I tried enabling experimental fractional scaling, with 200% /
  100% scales set (I do not really need fractional scaling, but I hoped
  it changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.

  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it
  is blurred even if I disconnect the external display. It looks as if
  it rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps
  like terminal.

  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case
  everything is a bit lower resolution, but still sharp enough.

  Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-04-12 (234 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.14.3-041403-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage

[Desktop-packages] [Bug 1735986] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1735986/+attachment/5017751/+files/JournalErrors.txt

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the mouse button, the window
  shrinks to 2x smaller, so it adapts to lower DPI of that screen.
  Everything is sharp and crispy and the sizes are ok.

  
  Problems:

  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly
  on the external screen. Everything is twice too big. When started,
  they appear first on the built-in hiDPI screen with the correct size,
  but after dragging to the external screen, they remain scaled by 200%.

  * When I enabled dock to be displayed on all screens, the dock icons
  are twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.

  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is
  only twice too large when over the desktop background, but ok when
  over an application window. This is a very minor issue, but looks
  funny.

  -
  What I tried so far:

  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.

  Then I tried enabling experimental fractional scaling, with 200% /
  100% scales set (I do not really need fractional scaling, but I hoped
  it changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.

  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it
  is blurred even if I disconnect the external display. It looks as if
  it rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps
  like terminal.

  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case
  everything is a bit lower resolution, but still sharp enough.

  Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-04-12 (234 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.14.3-041403-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage

[Desktop-packages] [Bug 1735986] Re: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display

apport information

** Tags added: apport-collected artful wayland-session

** Description changed:

  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.
  
  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).
  
  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.
  
  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:
  
  loginctl show-session 2 -p Type
  Type=wayland
  
  With external display connected, display settings show that the high DPI
  laptop screen got scaling set automatically to 200%, and the external
  low DPI display got scaling set to 100%. So far, looks good - automatic
  detection of hi dpi screens did the right thing.
  
  The built-in Ubuntu applications like terminal, file browser or setting
  window work fine. When I start e.g. the terminal, it appears first on
  the laptop screen - it is scaled properly, then I drag it to the
  external screen and once I release the mouse button, the window shrinks
  to 2x smaller, so it adapts to lower DPI of that screen. Everything is
  sharp and crispy and the sizes are ok.
  
  
  Problems:
  
  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on
  the external screen. Everything is twice too big. When started, they
  appear first on the built-in hiDPI screen with the correct size, but
  after dragging to the external screen, they remain scaled by 200%.
  
  * When I enabled dock to be displayed on all screens, the dock icons are
  twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.
  
  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is only
  twice too large when over the desktop background, but ok when over an
  application window. This is a very minor issue, but looks funny.
  
  -
  What I tried so far:
  
  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.
  
  Then I tried enabling experimental fractional scaling, with 200% / 100%
  scales set (I do not really need fractional scaling, but I hoped it
  changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.
  
  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it is
  blurred even if I disconnect the external display. It looks as if it
  rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps like
  terminal.
  
  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case everything
  is a bit lower resolution, but still sharp enough.
  
- Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi
- support for me at all, despite some rumours it should have. I still have
- to switch to lower resolution on the builtin display to get everything
- crisp and the right size.
+ Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-xenial-amd64-20160624-2
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2017-04-12 (234 days ago)
+ InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
+ Package: gnome-control-center 1:3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
+ Tags:  artful wayland-session
+ Uname: Linux 4.14.3-041403-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
+ UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1735986/+attachment/5017750/+files/Dependencies.txt

-- 
You received this bug

[Desktop-packages] [Bug 1735986] [NEW] Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display

Public bug reported:

I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So now 
running on 17.10.
I upgraded to 17.10 because I hoped for better HiDPI scaling support.

My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
Intel graphics (it has nvidia too, but disabled).

Additionally, I have an external Dell U3011 2560x1600 30" display
connected to it.


When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

loginctl show-session 2 -p Type
Type=wayland

With external display connected, display settings show that the high DPI
laptop screen got scaling set automatically to 200%, and the external
low DPI display got scaling set to 100%. So far, looks good - automatic
detection of hi dpi screens did the right thing.

The built-in Ubuntu applications like terminal, file browser or setting
window work fine. When I start e.g. the terminal, it appears first on
the laptop screen - it is scaled properly, then I drag it to the
external screen and once I release the mouse button, the window shrinks
to 2x smaller, so it adapts to lower DPI of that screen. Everything is
sharp and crispy and the sizes are ok.


Problems:

* Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on
the external screen. Everything is twice too big. When started, they
appear first on the built-in hiDPI screen with the correct size, but
after dragging to the external screen, they remain scaled by 200%.

* When I enabled dock to be displayed on all screens, the dock icons are
twice too big on the external screen. So, 200% scaling seems to be
applied to the dock on both screens.

* Sometimes the mouse pointer is twice as large. Sometimes it is twice
too small. I didn't figure out yet when it happens. Sometimes it is only
twice too large when over the desktop background, but ok when over an
application window. This is a very minor issue, but looks funny.

-
What I tried so far:


Resetting dconf to factory settings with:
dconf reset -f /org/gnome/
did not help.

Then I tried enabling experimental fractional scaling, with 200% / 100%
scales set (I do not really need fractional scaling, but I hoped it
changes how things are rendered and where scaling is applied). This
actually helped for both scaling issues - including the dock scaling
problem. Windows get even properly scaled in the *middle of dragging*
between displays. Everything is the right size with this setting on.
Really cool.

Unfortunately now the image on the builtin display for the non-native
applications like Firefox, Chrome or Idea is severely blurred. And it is
blurred even if I disconnect the external display. It looks as if it
rendered these apps at half the resolution (I noticed xrandr shows
1920x1080 for that screen, but ubuntu display settings window shows
3840x2160) and then upscaled twice the bitmap to reach higher 4k real
screen resolution. The blur does not happen for native Ubuntu apps like
terminal.

Unfortunately the blurring effect is much stronger than if I just
manually force the builtin screen to 1920x1080. In this case everything
is a bit lower resolution, but still sharp enough.

Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi
support for me at all, despite some rumours it should have. I still have
to switch to lower resolution on the builtin display to get everything
crisp and the right size.

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

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the

[Desktop-packages] [Bug 1689261] Re: Network manager says my USB-based ethernet devices are not supported, though I can connect manually

Ok, I found a workaround here:
https://askubuntu.com/questions/865945/after-upgrade-to-16-10-ethernet-stopped-working


sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf

Magic! Worked for me!
But there seems to be a bug anyway.

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

Title:
  Network manager says my USB-based ethernet devices are not supported,
  though I can connect manually

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a Dell Precision 5520 laptop with a Thunderbolt USB 3.1 type C
  port that I connect to a Dell TB15 docking station connected with an
  Ethernet cable.

  Network manager section for ethernet connections is all grayed out,
  and it says "device unsupported".

  USB subsystem seems to detect the device just fine:

  ```
  $ lsusb
  Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
  Bus 004 Device 002: ID 0424:5537 Standard Microsystems Corp.
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 046d:c31f Logitech, Inc.
  Bus 003 Device 003: ID 0bda:4014 Realtek Semiconductor Corp.
  Bus 003 Device 002: ID 0424:2137 Standard Microsystems Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ```

  ```
  $ sudo lsusb -v -d 0bda:8153
  Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   3.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 9
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x8153
    bcdDevice   30.01
    iManufacturer   1 Realtek
    iProduct2 USB 10/100/1000 LAN
    iSerial 6 0100
    bNumConfigurations  2
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   57
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   64mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   3
    bInterfaceClass   255 Vendor Specific Class
    bInterfaceSubClass255 Vendor Specific Subclass
    bInterfaceProtocol  0
    iInterface  0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst   3
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst   3
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes3
    Transfer TypeInterrupt
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0002  1x 2 bytes
  bInterval   8
  bMaxBurst   0
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   98
  bNumInterfaces  2
  bConfigurationValue 2
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   64mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 2 Communications
    bInterfaceSubClass  6 Ethernet Networking

[Desktop-packages] [Bug 1689261] Re: Network manager says my USB-based ethernet devices are not supported, though I can connect manually

** Attachment added: "Network manager applet screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1689261/+attachment/4873431/+files/Zrzut%20ekranu%20z%202017-05-08%2013-05-58.png

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

Title:
  Network manager says my USB-based ethernet devices are not supported,
  though I can connect manually

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a Dell Precision 5520 laptop with a Thunderbolt USB 3.1 type C
  port that I connect to a Dell TB15 docking station connected with an
  Ethernet cable.

  Network manager section for ethernet connections is all grayed out,
  and it says "device unsupported".

  USB subsystem seems to detect the device just fine:

  ```
  $ lsusb
  Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
  Bus 004 Device 002: ID 0424:5537 Standard Microsystems Corp.
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 046d:c31f Logitech, Inc.
  Bus 003 Device 003: ID 0bda:4014 Realtek Semiconductor Corp.
  Bus 003 Device 002: ID 0424:2137 Standard Microsystems Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ```

  ```
  $ sudo lsusb -v -d 0bda:8153
  Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   3.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 9
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x8153
    bcdDevice   30.01
    iManufacturer   1 Realtek
    iProduct2 USB 10/100/1000 LAN
    iSerial 6 0100
    bNumConfigurations  2
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   57
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   64mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   3
    bInterfaceClass   255 Vendor Specific Class
    bInterfaceSubClass255 Vendor Specific Subclass
    bInterfaceProtocol  0
    iInterface  0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst   3
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst   3
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes3
    Transfer TypeInterrupt
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0002  1x 2 bytes
  bInterval   8
  bMaxBurst   0
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   98
  bNumInterfaces  2
  bConfigurationValue 2
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   64mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 2 Communications
    bInterfaceSubClass  6 Ethernet Networking
    bInterfaceProtocol  0
    iInterface

[Desktop-packages] [Bug 1689261] Re: Network manager says my USB-based ethernet devices are not supported, though I can connect manually

To make my workaround permanent, I tried adding the following lines to
/etc/network/interfaces:


auto eth0
iface eth0 inet dhcp


Weirdly, this hosed my system to the point it could no longer boot to login 
screen. It got totaly stuck at configuring eth0 (no matter if the cable was 
connected or not).

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

Title:
  Network manager says my USB-based ethernet devices are not supported,
  though I can connect manually

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a Dell Precision 5520 laptop with a Thunderbolt USB 3.1 type C
  port that I connect to a Dell TB15 docking station connected with an
  Ethernet cable.

  Network manager section for ethernet connections is all grayed out,
  and it says "device unsupported".

  USB subsystem seems to detect the device just fine:

  ```
  $ lsusb
  Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
  Bus 004 Device 002: ID 0424:5537 Standard Microsystems Corp.
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 046d:c31f Logitech, Inc.
  Bus 003 Device 003: ID 0bda:4014 Realtek Semiconductor Corp.
  Bus 003 Device 002: ID 0424:2137 Standard Microsystems Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ```

  ```
  $ sudo lsusb -v -d 0bda:8153
  Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   3.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 9
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x8153
    bcdDevice   30.01
    iManufacturer   1 Realtek
    iProduct2 USB 10/100/1000 LAN
    iSerial 6 0100
    bNumConfigurations  2
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   57
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   64mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   3
    bInterfaceClass   255 Vendor Specific Class
    bInterfaceSubClass255 Vendor Specific Subclass
    bInterfaceProtocol  0
    iInterface  0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst   3
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst   3
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes3
    Transfer TypeInterrupt
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0002  1x 2 bytes
  bInterval   8
  bMaxBurst   0
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   98
  bNumInterfaces  2
  bConfigurationValue 2
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   64mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 2 Communications

[Desktop-packages] [Bug 1689261] [NEW] Network manager says my USB-based ethernet devices are not supported, though I can connect manually

Public bug reported:

I have a Dell Precision 5520 laptop with a Thunderbolt USB 3.1 type C
port that I connect to a Dell TB15 docking station connected with an
Ethernet cable.

Network manager section for ethernet connections is all grayed out, and
it says "device unsupported".

USB subsystem seems to detect the device just fine:

```
$ lsusb
Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
Bus 004 Device 002: ID 0424:5537 Standard Microsystems Corp.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 046d:c31f Logitech, Inc.
Bus 003 Device 003: ID 0bda:4014 Realtek Semiconductor Corp.
Bus 003 Device 002: ID 0424:2137 Standard Microsystems Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```

```
$ sudo lsusb -v -d 0bda:8153
Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 9
  idVendor   0x0bda Realtek Semiconductor Corp.
  idProduct  0x8153
  bcdDevice   30.01
  iManufacturer   1 Realtek
  iProduct2 USB 10/100/1000 LAN
  iSerial 6 0100
  bNumConfigurations  2
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   57
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower   64mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol  0
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   3
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   3
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval   8
bMaxBurst   0
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   98
bNumInterfaces  2
bConfigurationValue 2
iConfiguration  0
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower   64mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 2 Communications
  bInterfaceSubClass  6 Ethernet Networking
  bInterfaceProtocol  0
  iInterface  5 CDC Communications Control
  CDC Header:
bcdCDC   1.10
  CDC Union:
bMasterInterface0
bSlaveInterface 1
  CDC Ethernet:
iMacAddress  3 D481D773B38D
bmEthernetStatistics0x
wMaxSegmentSize   1514
wNumberMCFilters0x
bNumberPowerFilters  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2014-12-26 Thread Piotr Kołaczkowski

An unofficial (and unacceptable) fix that finally worked for me was to 
switch to Linux Mint 17.1. 
It is based on Ubuntu 14.04 LTS, so I wonder what they did better, particularly 
because they seem to be using exactly the same X org and  graphics driver 
versions. 
X.org 1.15.1
Nvidia: 331.113

Not sure of xorg, but nvidia is definitely from the Ubuntu repos.

Things that work correctly now:
- booting the system with the second monitor plugged in
- no strange temporary artifacts/glitches when changing graphics mode during 
startup of the x session (however, it also takes *longer* for mint to display 
the desktop, than for Ubuntu)
- booting the system with the laptop lid closed (!) by pressing the docking 
station power button and using only the big secondary screen (last time I 
checked this with Ubuntu, I got a permanent system freeze and both screens 
black)
- plugging/unplugging the laptop multiple times from the docking station with 
external monitor turned on 
- suspending/hibernating, undocking, resuming (it picks up the new screen 
config after resume just fine)
- suspending/hibernating, docking, resuming

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is created whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2014-12-08 Thread Piotr Kołaczkowski

Any updates? This issue is driving me crazy.

A few days ago I had a talk at Cassandra Summit and this bug almost
ruined my presentation - it was not possible to use my laptop with an
external wide-screen projector through HDMI, somehow the screen
distortion problem happened always and I was not able to switch Ubuntu
to screen mirroring mode, becacuse before you connect the second
monitor / projector that option is disabled. And although D-sub analog
connection worked, the resolution was awfully low (not sure if that was
Ubuntu or the D-Sub to DVI adapter problem). Good they had a replacement
laptop (a Mac) and we managed to transfer the presantation there.

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is created whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2014-12-08 Thread Piotr Kołaczkowski

http://askubuntu.com/questions/557149/14-10-dual-monitors-are-displayed-
as-distorted-single-screen-mode

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is created whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu Display configuration dialog detects both

[Desktop-packages] [Bug 1396032] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-11-25 Thread Piotr Kołaczkowski

Public bug reported:

It looks similar to other issues but the message isn't exactly the same. 
It just appeared after regular Ubuntu update.  The system seems to be working 
fine despite this problem.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.16.0-25-generic
Date: Tue Nov 25 09:16:29 2014
InstallationDate: Installed on 2012-03-21 (978 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
UpgradeStatus: Upgraded to utopic on 2014-10-17 (39 days ago)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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


** Tags: amd64 apport-package third-party-packages utopic

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  It looks similar to other issues but the message isn't exactly the same. 
  It just appeared after regular Ubuntu update.  The system seems to be working 
fine despite this problem.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Tue Nov 25 09:16:29 2014
  InstallationDate: Installed on 2012-03-21 (978 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (39 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2014-10-19 Thread Piotr Kołaczkowski

Installing Nvidia 340.46 driver does not fix the problem (and adds one
more - incorrect rendering of menu highlight - but this driver is not
officially supported by ubuntu yet, so never mind).

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is created whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2014-10-18 Thread Piotr Kołaczkowski

Yesterday evening I updated the kernel to 3.16.0-23-generic (tpogether
with all the other updates) and the problem still exists.

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is created whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu Display configuration dialog

[Desktop-packages] [Bug 1382409] [NEW] nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

Public bug reported:

Upgrading from Ubuntu 14.04 LTS to 14.10. Previous nvidia driver:
331.38.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.89-0ubuntu5
Uname: Linux 3.16.5-031605-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu7
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Fri Oct 17 10:07:53 2014
InstallationDate: Installed on 2012-03-21 (939 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
UpgradeStatus: Upgraded to utopic on 2014-10-17 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages utopic

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upgrading from Ubuntu 14.04 LTS to 14.10. Previous nvidia driver:
  331.38.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  Uname: Linux 3.16.5-031605-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Fri Oct 17 10:07:53 2014
  InstallationDate: Installed on 2012-03-21 (939 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (0 days ago)

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

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

[Desktop-packages] [Bug 1382462] [NEW] Desktop/windows painted incorrectly in dual monitor configuration

Public bug reported:

My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
to DisplayPort.

I was using Nvidia 331.38 prioprietary driver for quite a long time with
Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to
Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following
problem:

1. When I boot up the computer with the monitor connected, the login
screen looks fine. Both displays get detected properly and resolutions
are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011)
and screen contents scaled properly.

2. Then I log into my account, for 3 seconds U3011 displays some rubbish
(but it was always like that) and when it finally logs in, it displays
everything stretched horizontally through both my screens. It looks as
if it tried to paint the contents of a single display on two of them, by
stretching the content horizontally, so everything (icons, windows,
wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to
render correctly. Physical resolution of both screens is ok. I'll attach
a photo, because it is hard to describe how it looks.

3. I cannot use system in this state - mouse click position seems to not
be synchronized with what's on the display - e.g. I can start
applications, but then they don't react to mouseclicks.

However: booting up without the second display connected, logging in and
*then* connecting the second display works fine.

I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains. 
I also tried to go into the Displays configuration when everything is ok, apply 
the settings there (without any changes) in hope it will persist them somehow, 
but after restart it is broken again. 

I also tried reinstalling nvidia 331.89 drivers, because it complained
about not being able to install nvidia-uvm during the upgrade process
(reported separately), and now all nvidia packages installed cleanly.
Before that I also got rid of all the ppa mainline kernels I had, just
in case they mess something up.

I remember the same problem happened on Ubuntu 14.04 when I tried to
upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
workaround was to downgrade back to official 331.38. Now I have no
choice :(

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
 GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Fri Oct 17 11:02:50 2014
DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:04a3]
 NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell Device [1028:14a3]
InstallationDate: Installed on 2012-03-21 (939 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=37dce0bb-1e68-402b-8cba-78a6e04193de ro quiet splash reboot=pci 
acpi_backlight=vendor resume=UUID=4b9dc764-1ab9-4d9f-b661-1561bfe83648
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to utopic on 2014-10-17 (0 days ago)
dmi.bios.date: 10/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.56+git20140920.77dce9a0-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.4.0~git20140925.23247e80-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri-experimental:

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Attachment added: After starting a session and opening a few windows
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238845/+files/DSC_0029.JPG

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly. Physical resolution of both screens is ok.
  I'll attach a photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, loggin in and then connecting.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  
  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Oct 17 11:02:50 2014
  DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04a3]
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell Device [1028:14a3]
  InstallationDate: Installed on 2012-03-21 (939 days

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Attachment added: The same windows immediately after undocking the laptop, 
see how aspect ratio on the builtin screen changed
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238849/+files/DSC_0031.JPG

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly. Physical resolution of both screens is ok.
  I'll attach a photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, loggin in and then connecting.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  
  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Oct 17 11:02:50 2014
  DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04a3]
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell Device [1028:14a3]

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Attachment added: Windows, which normally were placed in one of the
screens, now are placed partially on both

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238846/+files/DSC_0030.JPG

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

Title:
Desktop/windows painted incorrectly in dual monitor configuration

Status in “xorg” package in Ubuntu:
New

Bug description:
My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
to DisplayPort.

I was using Nvidia 331.38 prioprietary driver for quite a long time
with Ubuntu 14.04 LTS and everything worked perfectly. Today I
upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
the following problem:

1. When I boot up the computer with the monitor connected, the login
screen looks fine. Both displays get detected properly and resolutions
are ok (1920x1080 on the builtin laptop display and 2560x1600 on
U3011) and screen contents scaled properly.

2. Then I log into my account, for 3 seconds U3011 displays some
rubbish (but it was always like that) and when it finally logs in, it
displays everything stretched horizontally through both my screens. It
looks as if it tried to paint the contents of a single display on two
of them, by stretching the content horizontally, so everything (icons,
windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
seem to render correctly. Physical resolution of both screens is ok.
I'll attach a photo, because it is hard to describe how it looks.

3. I cannot use system in this state - mouse click position seems to
not be synchronized with what's on the display - e.g. I can start
applications, but then they don't react to mouseclicks.

However: booting up without the second display connected, logging in
and *then* connecting the second display works fine.

If I boot up with connected monitor and log in (desktop distorted),
disconnecting and connecting monitor does *not* help. After disconnecting the
U3011, the builtin display is painted ok, but after connecting, it returns back
to the incorrect state and both are rendered incorrectly.
The only thing that helps recovering from this state seems to be
disconnecting the second monitor, reboot, loggin in and then connecting.

BTW: I'm using a docking station - not sure if it is related - if you
think it might be, I can try with connecting the monitor directly.

I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem
remains.
I also tried to go into the Displays configuration when everything is ok,
apply the settings there (without any changes) in hope it will persist them
somehow, but after restart it is broken again.

I also tried reinstalling nvidia 331.89 drivers, because it complained
about not being able to install nvidia-uvm during the upgrade process
(reported separately), and now all nvidia packages installed cleanly.
Before that I also got rid of all the ppa mainline kernels I had, just
in case they mess something up.

I remember the same problem happened on Ubuntu 14.04 when I tried to
upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
workaround was to downgrade back to official 331.38. Now I have no
choice :(

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary:
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18
PDT 2014
GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
.tmp.unity.support.test.0:

ApportVersion: 2.14.7-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission
denied
Date: Fri Oct 17 11:02:50 2014
DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:04a3]
NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:14a3]

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Description changed:

  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.
  
  I was using Nvidia 331.38 prioprietary driver for quite a long time with
  Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to
  Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following
  problem:
  
  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011)
  and screen contents scaled properly.
  
  2. Then I log into my account, for 3 seconds U3011 displays some rubbish
  (but it was always like that) and when it finally logs in, it displays
  everything stretched horizontally through both my screens. It looks as
  if it tried to paint the contents of a single display on two of them, by
  stretching the content horizontally, so everything (icons, windows,
  wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to
  render correctly. Physical resolution of both screens is ok. I'll attach
  a photo, because it is hard to describe how it looks.
  
  3. I cannot use system in this state - mouse click position seems to not
  be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.
  
  However: booting up without the second display connected, logging in and
  *then* connecting the second display works fine.
  
- I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains. 
- I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again. 
+ If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
+ The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, loggin in and then connecting.
+ 
+ BTW: I'm using a docking station - not sure if it is related - if you
+ think it might be, I can try with connecting the monitor directly.
+ 
+ 
+ I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
+ I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.
  
  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.
  
  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
-  GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
+  GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Oct 17 11:02:50 2014
  DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:04a3]
-  NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Dell Device [1028:14a3]
+  Intel Corporation 2nd Generation Core

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Description changed:

  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.
  
  I was using Nvidia 331.38 prioprietary driver for quite a long time with
  Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to
  Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following
  problem:
  
  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011)
  and screen contents scaled properly.
  
  2. Then I log into my account, for 3 seconds U3011 displays some rubbish
  (but it was always like that) and when it finally logs in, it displays
  everything stretched horizontally through both my screens. It looks as
  if it tried to paint the contents of a single display on two of them, by
  stretching the content horizontally, so everything (icons, windows,
  wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to
  render correctly. Physical resolution of both screens is ok. I'll attach
  a photo, because it is hard to describe how it looks.
  
  3. I cannot use system in this state - mouse click position seems to not
  be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.
  
  However: booting up without the second display connected, logging in and
  *then* connecting the second display works fine.
  
  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
- The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, loggin in and then connecting.
+ The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.
+ 
+ Suspending to memory and waking up does not change the layout of the
+ screen (neither fixes the broken one nor destroys the good one).
  
  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.
- 
  
  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.
  
  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.
  
  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Oct 17 11:02:50 2014
  DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04a3]
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell Device [1028:14a3]
  InstallationDate: Installed on 2012-03-21 (939 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: Dell Inc. Precision M4600
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Description changed:

  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.
  
  I was using Nvidia 331.38 prioprietary driver for quite a long time with
  Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to
  Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following
  problem:
  
  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011)
  and screen contents scaled properly.
  
  2. Then I log into my account, for 3 seconds U3011 displays some rubbish
  (but it was always like that) and when it finally logs in, it displays
  everything stretched horizontally through both my screens. It looks as
  if it tried to paint the contents of a single display on two of them, by
  stretching the content horizontally, so everything (icons, windows,
  wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to
- render correctly. Physical resolution of both screens is ok. I'll attach
- a photo, because it is hard to describe how it looks.
+ render correctly and the resolution/size of the top menu is correct.
+ Physical resolution of both screens is ok. I'll attach a photo, because
+ it is hard to describe how it looks.
  
  3. I cannot use system in this state - mouse click position seems to not
  be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.
  
  However: booting up without the second display connected, logging in and
  *then* connecting the second display works fine.
  
  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.
  
  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).
+ 
+ Using a Guest session instead of my account does not fix my problem (I
+ was hoping this was something screwed up in my .config).
+ 
+ Switching to a Guest user account while I'm using both monitors in the
+ good layout creates a session with a broken layout. Then logging out
+ from Guest and switching back to my original session restores the good
+ layout. The good layout seems to not be forgotten until I finish the
+ session and logout. The bad layout is created whenever I start a new
+ session with both monitors plugged in.
  
  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.
  
  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.
  
  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.
  
  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(
+ 
+ Some other observations that may or may not be related to the problem,
+ but I disclose them anyway, maybe they are helpful:
+ 
+ * Notifications (e.g. network connection) displayed on the login screen
+ in dual screen mode seem to be misplaced and instead of being painted in
+ the upper right corner of one of the displays they get painted in some
+ hard to logically explain position - neither at the center, nor in any
+ corner.
+ 
+ * The splash screen of IntelliJ IDEA (this is using Java / AWT probably)
+ is also rendered in a strange position - below the center of the laptop
+ screen, moved to the right (but not touching the edge), instead of exact
+ center as it should be.
+ 
+ * GMail notification just displayed at the moment when I'm writing it
+ exactly at the left-lower corner of the bigger screen (U3011).
+ 
+ * Nvidia settings lists only U3011 in the list of the devices (attached
+ screenshot).
+ 
+ * Ubuntu Display configuration dialog detects both displays correctly
+ and their positions and resolutions are ok (attached screenshot).
+ However I could not check that when the problem was active.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

** Attachment added: Display config as seen by Nvidia-settings (when working
correctly)

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238972/+files/Screenshot%20from%202014-10-17%2015%3A34%3A18.png

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

Title:
Desktop/windows painted incorrectly in dual monitor configuration

Status in “xorg” package in Ubuntu:
New

Bug description:
My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
to DisplayPort.

2. Then I log into my account, for 3 seconds U3011 displays some
rubbish (but it was always like that) and when it finally logs in, it
displays everything stretched horizontally through both my screens. It
looks as if it tried to paint the contents of a single display on two
of them, by stretching the content horizontally, so everything (icons,
windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
seem to render correctly and the resolution/size of the top menu is
correct. Physical resolution of both screens is ok. I'll attach a
photo, because it is hard to describe how it looks.

3. I cannot use system in this state - mouse click position seems to
not be synchronized with what's on the display - e.g. I can start
applications, but then they don't react to mouseclicks.

However: booting up without the second display connected, logging in
and *then* connecting the second display works fine.

Suspending to memory and waking up does not change the layout of the
screen (neither fixes the broken one nor destroys the good one).

Using a Guest session instead of my account does not fix my problem (I
was hoping this was something screwed up in my .config).

Switching to a Guest user account while I'm using both monitors in the
good layout creates a session with a broken layout. Then logging out
from Guest and switching back to my original session restores the good
layout. The good layout seems to not be forgotten until I finish the
session and logout. The bad layout is created whenever I start a new
session with both monitors plugged in.

BTW: I'm using a docking station - not sure if it is related - if you
think it might be, I can try with connecting the monitor directly.

Some other observations that may or may not be related to the problem,
but I disclose them anyway, maybe they are helpful:

* Notifications (e.g. network connection) displayed on the login
screen in dual screen mode seem to be misplaced and instead of being
painted in the upper right corner of one of the displays they get
painted in some hard to logically explain position - neither at the
center, nor in any corner.

* The splash screen of IntelliJ IDEA (this is using Java / AWT
probably) is also rendered in a strange position - below the center of
the laptop screen, moved to the right (but not touching the edge),
instead of exact center as it should be.

* GMail notification just displayed at the moment when I'm writing it
exactly at the left-lower corner of the bigger screen (U3011).

* Nvidia settings lists

[Desktop-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration