[Desktop-packages] [Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)

[jean-christophe manciot]

Same issue on Ubuntu 24.04 noble LTS:

- gnome-shell: 46.0-0ubuntu5
- linux 6.8.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 14 14:56:46 UTC 
2024 x86_64
- DisplayManager: lightdm 1.30.0-0ubuntu14

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

Title:
  Can't update stage views actor  (regarding MetaWindowGroup,
  MetaWindowActorX11, MetaSurfaceActorX11)

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  These messages repeat:

  [  105.711276] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bba91da500] is on because it needs an 
allocation.
  [  105.711772] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbac95c330] is on because it needs an 
allocation.
  [  105.711903] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbae726860] is on because it needs an 
allocation.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  Uname: Linux 6.1.11-060111-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 21:54:39 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-22 (179 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2007742/+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 1811724] Re: libbd_mdraid.so.2: cannot open shared object file

[jean-christophe manciot]

Ubuntu focal
linux 5.4.0-17-generic x86_64
udisks2 2.8.4-1ubuntu1
libblockdev-crypto2 2.23-2ubuntu3

Same issue:
udisksd[1920]: Failed to load the 'mdraid' libblockdev plugin

Installing libblockdev-mdraid2 pulls in mdadm which is not a solution on
systems which don't implement RAID.

On such systems, udisksd should not try to load the 'mdraid' libblockdev
plugin.

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

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+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 1851144] Re: Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting

[jean-christophe manciot]

No such issue with eaon.

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

Title:
  Switching from unity-greeter to lightdm-gtk-greeter prevents
  lightdm.service from starting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  lightdm 1.30.0-0ubuntu2
  lightdm-gtk-greeter 2.0.6-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  Date: Sun Nov  3 16:15:54 2019
  InstallationDate: Installed on 2015-04-28 (1650 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1851144/+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 1851144] [NEW] Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting

[jean-christophe manciot]

Public bug reported:

Ubuntu 20.04
lightdm 1.30.0-0ubuntu2
lightdm-gtk-greeter 2.0.6-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
Uname: Linux 5.3.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
Date: Sun Nov  3 16:15:54 2019
InstallationDate: Installed on 2015-04-28 (1650 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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


** Tags: amd64 apport-bug focal

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

Title:
  Switching from unity-greeter to lightdm-gtk-greeter prevents
  lightdm.service from starting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  lightdm 1.30.0-0ubuntu2
  lightdm-gtk-greeter 2.0.6-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  Date: Sun Nov  3 16:15:54 2019
  InstallationDate: Installed on 2015-04-28 (1650 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1851144/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

[jean-christophe manciot]

I have just found the following message in syslog:
Feb 12 13:25:56 samsung5-ubuntu colord-sane: message repeated 2 times: [ [bjnp] 
create_broadcast_socket: ERROR - bind socket to local address failed - Cannot 
assign requested address]
that matches:
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: 
enabled)
   Active: active (running) since Tue 2019-02-12 02:30:41 CET; 11h ago
 Main PID: 2098 (colord)
Tasks: 3 (limit: 4915)
   Memory: 14.9M
   CGroup: /system.slice/colord.service
   └─2098 /usr/lib/colord/colord

Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Starting Manage, Install and 
Generate Color Profiles...
Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Started Manage, Install and 
Generate Color Profiles.
Feb 12 02:30:42 samsung5-ubuntu colord[2098]: failed to get session [pid 2118]: 
No data available
Feb 12 02:30:42 samsung5-ubuntu colord-sane[2240]: [bjnp] 
create_broadcast_socket: ERROR - bind socket to local address failed - Cannot 
assign requested address

This lead me to investigate the SANE scanner and more specifically 
/etc/sane.d/dll.conf which seems to list image scanner hardware drivers, 
including canon ones. 
However, commenting out 'net' or all canon-related lines does not change 
anything:
# systemctl restart colord
# systemctl status colord
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: 
enabled)
   Active: active (running) since Tue 2019-02-12 14:21:12 CET; 4s ago
 Main PID: 31838 (colord)
Tasks: 4 (limit: 4915)
   Memory: 8.0M
   CGroup: /system.slice/colord.service
   └─31838 /usr/lib/colord/colord

Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Starting Manage, Install and 
Generate Color Profiles...
Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Started Manage, Install and 
Generate Color Profiles.
Feb 12 14:21:13 samsung5-ubuntu colord-sane[31859]: [bjnp] 
create_broadcast_socket: ERROR - bind socket to local address failed - Cannot 
assign requested address

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

[jean-christophe manciot]

I ha

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

[jean-christophe manciot]

If anyone knows a way to pinpoint some process which sends some specific
packets, I'd be glad to investigate further.

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

[jean-christophe manciot]

I experience the same symptoms on Ubuntu 19.04 disco, but there is no
cups* packages installed:

# apt-cache policy cups*| grep Installed | grep -v none
# 

The issue is definitely unrelated to CUPS.

Some other process sends many strange IPv6/UDP packets to all IPv6 local nodes 
with 2 different types; the wireshark trace shows 2 types of "Discover scanner 
commands":
1. source port 8612 (canon-bjnp2) --> dest port 8610 (canon-mfnp)
2. source port 8612 (canon-bjnp2) --> dest port 8612 (canon-bjnp2)

I have no canon device on the network nor on the server and no USB device 
connected on the server.
There is no canon related package/kernel module installed.

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1731428] Re: gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

[jean-christophe manciot]

There is no TryExec in gnome-settings-daemon.desktop:

[Desktop Entry]
Type=Application
Name=GNOME Settings Daemon
Exec=/usr/lib/gnome-settings-daemon/gnome-settings-daemon-localeexec
OnlyShowIn=GNOME;
NoDisplay=false
X-GNOME-Autostart-Phase=Initialization
X-GNOME-Autostart-Notify=true
X-GNOME-AutoRestart=true
X-Ubuntu-Gettext-Domain=gnome-settings-daemon

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

Title:
  gnome-session-binary: Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-session package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 artful
  gnome-session 3.26.1-0ubuntu6
  gnome-settings-daemon 3.26.1-0ubuntu5

  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: 
Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before 
timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  There is no other mention of org.gnome.SettingsDaemon.Color.desktop
  before in syslog and kern.log, which is odd.

  However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
  Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Could not parse desktop file 
gnome-settings-daemon.desktop or it references a not found TryExec binary
  Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

  I'll try to reinstall gnome-settings-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.0-16-generic x86_64
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:18:44 2017

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731428/+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 1731428] [NEW] gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

[jean-christophe manciot]

Public bug reported:

On Ubuntu 17.10 artful
gnome-session 3.26.1-0ubuntu6
gnome-settings-daemon 3.26.1-0ubuntu5

Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We failed, 
but the fail whale is dead. Sorry

There is no other mention of org.gnome.SettingsDaemon.Color.desktop
before in syslog and kern.log, which is odd.

However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: 
WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it 
references a not found TryExec binary
Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

I'll try to reinstall gnome-settings-daemon.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.26.1-0ubuntu5
Uname: Linux 4.13.0-16-generic x86_64
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov 10 09:18:44 2017

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

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

Title:
  gnome-session-binary: Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-session package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 artful
  gnome-session 3.26.1-0ubuntu6
  gnome-settings-daemon 3.26.1-0ubuntu5

  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: 
Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before 
timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  There is no other mention of org.gnome.SettingsDaemon.Color.desktop
  before in syslog and kern.log, which is odd.

  However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
  Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Could not parse desktop file 
gnome-settings-daemon.desktop or it references a not found TryExec binary
  Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

  I'll try to reinstall gnome-settings-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.0-16-generic x86_64
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:18:44 2017

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731428/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status rpcbind.service"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665098/+files/rpcbind.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status iscsid.service"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665104/+files/iscsid.service.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status sysinit.target"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665101/+files/sysinit.target.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status open-iscsi.service"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665103/+files/open-iscsi.service.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status zfs-fuse.service"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665102/+files/zfs-fuse.service.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status remote-fs-pre.target"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665100/+files/remote-fs-pre.target.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] Re: NetworkManager service does not start during bootup

[jean-christophe manciot]

** Attachment added: "systemctl -l status network.target"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665099/+files/network.target.log

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1582986] [NEW] NetworkManager service does not start during bootup

[jean-christophe manciot]

Public bug reported:

Ubuntu 16.04 4.4.0-22
systemd 229-4
network-manager 1.1.93
network-manager-gnome 1.2.0

Multiple services and targets are deleted by systemd to "break ordering
cycle" (cf. boot.log), but NetworkManager is the only one of them
(network.target,rpcbind,sysinit.target,open-iscsi.service,remote-fs-
pre.target,iscsid.service,zfs-fuse.service - cf. their respective logs)
which is not started after bootup:

sudo systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)

May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
NetworkManager.service/verify-active deleted to break ordering cycle
starting with network.target/start

Attachments:
---
- journalctl -l -b0 --system _COMM=systemd > boot.log
- systemctl -l status rpcbind  > rpcbind.log
- systemctl -l status network.target  > network.target.txt
- systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
- systemctl -l status sysinit.target  > sysinit.target.log
- systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
- systemctl -l status open-iscsi.service  > open-iscsi.service.log
- systemctl -l status iscsid.service  > iscsid.service.log

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


** Tags: service startup systemd

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1568528] [NEW] ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789")

[jean-christophe manciot]

Public bug reported:

Ubuntu 15.10 4.2.0-35
network-manager Ubuntu sources: network-manager_1.0.4.orig.tar.xz built with:

dpkg-buildpackage -b -m"Jean-Christophe Manciot
<manciot.jeanchristo...@gmail.com>"

...
=
   NetworkManager 1.0.4: src/platform/tests/test-suite.log
=

# TOTAL: 29
# PASS:  27
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 2

.. contents:: :depth: 2

ERROR: test-link-linux
==

# random seed: R02S51e6130ccfacff746e76534eba2e4658
1..7
# Start of link tests
ok 1 /link/bogus
PASS: test-link-linux 1 /link/bogus
ok 2 /link/loopback
PASS: test-link-linux 2 /link/loopback
ok 3 /link/internal
PASS: test-link-linux 3 /link/internal
ok 4 /link/external
PASS: test-link-linux 4 /link/external
**
NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value == 
"789"): ("788" == "789")
# Start of software tests
Aborted (core dumped)
# NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value 
== "789"): ("788" == "789")
ERROR: test-link-linux - too few tests run (expected 7, got 4)
ERROR: test-link-linux - exited with status 134 (terminated by signal 6?)

Full log attached.

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

** Attachment added: "Full log"
   
https://bugs.launchpad.net/bugs/1568528/+attachment/4631500/+files/Error%20building%201.0.4.log

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

Title:
  ERROR:test-link.c:303:test_software: assertion failed (value ==
  "789"): ("788" == "789")

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 15.10 4.2.0-35
  network-manager Ubuntu sources: network-manager_1.0.4.orig.tar.xz built with:

  dpkg-buildpackage -b -m"Jean-Christophe Manciot
  <manciot.jeanchristo...@gmail.com>"

  ...
  =
 NetworkManager 1.0.4: src/platform/tests/test-suite.log
  =

  # TOTAL: 29
  # PASS:  27
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 2

  .. contents:: :depth: 2

  ERROR: test-link-linux
  ==

  # random seed: R02S51e6130ccfacff746e76534eba2e4658
  1..7
  # Start of link tests
  ok 1 /link/bogus
  PASS: test-link-linux 1 /link/bogus
  ok 2 /link/loopback
  PASS: test-link-linux 2 /link/loopback
  ok 3 /link/internal
  PASS: test-link-linux 3 /link/internal
  ok 4 /link/external
  PASS: test-link-linux 4 /link/external
  **
  NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value 
== "789"): ("788" == "789")
  # Start of software tests
  Aborted (core dumped)
  # NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value 
== "789"): ("788" == "789")
  ERROR: test-link-linux - too few tests run (expected 7, got 4)
  ERROR: test-link-linux - exited with status 134 (terminated by signal 6?)

  Full log attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1568528/+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 1510648] Re: [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

I've made some progress: 
If I remove the following lines from /etc/network/interfaces:
iface wlan0 inet dhcp
iface wlan0 inet6 auto

NetworkManager errors "nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy 
!= NULL' failed" are gone:
systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2015-11-02 09:42:09 CET; 3s ago
 Main PID: 5524 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
   └─5524 /usr/sbin/NetworkManager --no-daemon

Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (tap1): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (tap1): 
Activation: successful, device activated.
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr4): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr4): 
Activation: successful, device activated.
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr11): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr11): 
Activation: successful, device activated.
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr7): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr7): 
Activation: successful, device activated.
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr3): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 02 09:42:10 msi-ge60-ubuntu NetworkManager[5524]:   (virbr3): 
Activation: successful, device activated.

However, it seems that the module rtl8723ae is not loaded:
lsmod | grep -i rtl8723ae

modinfo rtl8723ae
libkmod: ERROR ../libkmod/libkmod-module.c:192 kmod_module_parse_depline: 
ctx=0x55ae7dba3010 
path=/lib/modules/4.2.0-16-generic/updates/drivers/net/wireless/rtlwifi/rtl8723com/rtl8723-common.ko
 error=No such file or directory
libkmod: ERROR ../libkmod/libkmod.c:506 lookup_builtin_file: could not open 
builtin file '/lib/modules/4.2.0-16-generic/modules.builtin.bin'
filename:   
/lib/modules/4.2.0-16-generic/updates/drivers/net/wireless/rtlwifi/rtl8723ae/rtl8723ae.ko
modinfo: ERROR: could not get modinfo from 'rtl8723ae': No such file or 
directory

lshw -C network
  *-network UNCLAIMED
   description: Network controller
   product: RTL8723AE PCIe Wireless Network Adapter
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:05:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress cap_list
   configuration: latency=0
   resources: ioport:c000(size=256) memory:f780-f7803fff

This is strange because I can see some WiFi networks in the top right hand side 
menu.
Furthermore, if I try to connect to a WiFi hotspot (Nexus 5 here), 
NetworkManager tries to connect to the Nexus 5 bluetooth interface 
(BC:F5:AC:4B:72:11):

Nov  2 09:43:17 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): Activation: starting connection 'Nexus 5 Network' 
(3a1ff886-d78c-49c3-8984-a635c16ec9c9)
Nov  2 09:43:17 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): device state change: disconnected -> prepare (reason 
'none') [30 40 0]
Nov  2 09:43:17 msi-ge60-ubuntu NetworkManager[5524]:   NetworkManager 
state is now CONNECTING
Nov  2 09:43:17 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): device state change: prepare -> config (reason 'none') [40 
50 0]
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): Error connecting with bluez: 
GDBus.Error:org.bluez.Error.Failed: Input/output error
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): device state change: config -> failed (reason 
'bluetooth-failed') [50 120 44]
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   NetworkManager 
state is now CONNECTED_LOCAL
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   Connection 'Nexus 
5 Network' failed to autoconnect; 4 tries left
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): Activation: failed for connection 'Nexus 5 Network'
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   
(BC:F5:AC:4B:72:11): device state change: failed -> disconnected (reason 
'none') [120 30 0]
Nov  2 09:43:23 msi-ge60-ubuntu NetworkManager[5524]:   Device 
'BC:F5:AC:4B:72:11' has no connection; scheduling activate_check in 0 seconds.

Now, if I try to turn off bluetooth, Ubuntu goes into airplane mode
which disables WiFi as well - I'm unable to turn off bluetooth alone.

Connecting Ubuntu Server to Nexus 5 Bluetooth: OK

Reconnecting it to Nexus 5 Hotspot: KO
Nov  2 10:00:35 

[Desktop-packages] [Bug 1510648] Re: [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

Hoorah! 
I have been able to find a workaround by compliing the realtek drivers 
available here: http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/ 
with:

make defconfig-rtlwifi
make
sudo make install

shutdown -r now

The rtl8723ae module is now loaded:
lsmod | grep -i rtl8723ae
rtl8723ae 155648  0
rtl8723_common 24576  1 rtl8723ae
btcoexist  57344  1 rtl8723ae
rtl_pci40960  1 rtl8723ae
rtlwifi   106496  2 rtl_pci,rtl8723ae
compat 16384  5 cfg80211,mac80211,btcoexist,rtlwifi,rtl8723ae

modinfo rtl8723ae
filename:   
/lib/modules/4.2.0-16-generic/updates/drivers/net/wireless/rtlwifi/rtl8723ae/rtl8723ae.ko
version:backported from Linux (v4.2-rc1-0-gd770e55) using backports 
v4.2-rc1-1-0-g83a2518
firmware:   rtlwifi/rtl8723efw.bin
description:Realtek 8723E 802.11n PCI wireless
license:GPL
author: Realtek WlanFAE 
author: lizhaoming  
srcversion: 964ADBC6D9D3E9FEC736FA8
alias:  pci:v10ECd8723sv*sd*bc*sc*i*
depends:rtlwifi,rtl8723-common,rtl_pci,compat,btcoexist
vermagic:   4.2.0-16-generic SMP mod_unload modversions 
parm:   swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:   ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:   swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:   fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:   debug:Set debug level (0-5) (default 0) (int)
parm:   disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)

The UNCLAIMED network is gone:
lshw -C network
  *-network
   description: Wireless interface
   product: RTL8723AE PCIe Wireless Network Adapter
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:05:00.0
   logical name: wlan0
   version: 00
   serial: 24:0a:64:dd:b1:3c
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=rtl8723ae 
driverversion=4.2.0-16-generic firmware=N/A ip=192.168.43.11 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11bgn
   resources: irq:17 ioport:c000(size=256) memory:f780-f7803fff


Now connecting to Nexus 5 hotspot, from syslog:
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   keyfile: new 
connection /etc/NetworkManager/system-connections/Nexus 5 Hotspot 
(bf5dcf2b-a41f-4dee-b86b-47b8b3d8849a,"Nexus 5 Hotspot")
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   SCPlugin-Ofono: 
(36699040) ... get_connections.
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   SCPlugin-Ofono: 
(36699040) connections count: 0
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   get unmanaged 
devices count: 0
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   monitoring kernel 
firmware directory '/lib/firmware'.
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   monitoring 
ifupdown state file '/run/network/ifstate'.
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   rfkill1: found 
WiFi radio killswitch (at 
/sys/devices/pci:00/:00:1c.5/:05:00.0/ieee80211/phy0/rfkill1) 
(driver rtl8723ae)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMVxlanFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMVlanFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMVethFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMTunFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMMacvlanFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMInfinibandFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMGreFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMEthernetFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMBridgeFactory (internal)
Nov  2 12:00:33 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMBondFactory (internal)
Nov  2 12:00:34 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Nov  2 12:00:34 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
Nov  2 12:00:34 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 
plugin: NMAtmManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
Nov  2 12:00:34 msi-ge60-ubuntu NetworkManager[1185]:   Loaded device 

[Desktop-packages] [Bug 1510648] Re: [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

Now the question remains: why do I need to manually install the Realtek
drivers in Ubuntu Server 15.10 when it is not needed in Ubuntu Desktop
15.10?

** Summary changed:

- [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to WPA2/AES
+ [Workaround] [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to 
WPA2/AES

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

Title:
  [Workaround] [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot
  connect to WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+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 1510648] Re: [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

Some additional information:
- no similar issue on the same laptop with Ubuntu ***desktop*** 15.04/15.10
- same issue with Ubuntu ***server*** 15.04/15.10

I've modified the title to reflect these informations.

** Summary changed:

- [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES 
+ [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to WPA2/AES

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

Title:
  [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to
  WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+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 1510648] [NEW] [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

Public bug reported:

Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
---
sudo systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
 Main PID: 1204 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
   └─1204 /usr/sbin/NetworkManager --no-daemon

Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

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

** Attachment added: "lshw"
   https://bugs.launchpad.net/bugs/1510648/+attachment/4506837/+files/lshw.txt

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

Title:
  [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+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 1510648] Re: [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

Bug report first sent to Gnome: 
https://bugzilla.gnome.org/show_bug.cgi?id=757178
It seems to be an issue related to "nm_urfkill_get_wlan_state()" coming from an 
Ubuntu patch.

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

Title:
  [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+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 1510648] Re: [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+attachment/4506839/+files/syslog.txt

** Bug watch added: GNOME Bug Tracker #757178
   https://bugzilla.gnome.org/show_bug.cgi?id=757178

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

Title:
  [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+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 1510648] Re: [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

** Attachment added: "lspci -vn"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+attachment/4506838/+files/lspci.txt

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

Title:
  [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1510648/+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 1460388] [NEW] Multiple Issues with Ping6

[jean-christophe manciot]

Public bug reported:

- ping6 always use the same source address, whatever the destination is; it 
should use one of the IPv6 addresses of the connected interface it is sending 
the traffic on, by default
- ping6 cannot use a specified source interface/address using the -I option, 
which could have been used as a workaround to the previous issue

All the details are available here:
http://ubuntuforums.org/showthread.php?t=226p=13295631#post13295631

root@msi-ge60:/# lsb_release -rd
Description:Ubuntu 15.04
Release:15.04

root@msi-ge60:/# apt-cache policy iputils-ping
iputils-ping:
  Installed: 3:20121221-5ubuntu2
  Candidate: 3:20121221-5ubuntu2

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

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

Title:
  Multiple Issues with Ping6

Status in iputils package in Ubuntu:
  New

Bug description:
  - ping6 always use the same source address, whatever the destination is; it 
should use one of the IPv6 addresses of the connected interface it is sending 
the traffic on, by default
  - ping6 cannot use a specified source interface/address using the -I option, 
which could have been used as a workaround to the previous issue

  All the details are available here:
  http://ubuntuforums.org/showthread.php?t=226p=13295631#post13295631

  root@msi-ge60:/# lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  root@msi-ge60:/# apt-cache policy iputils-ping
  iputils-ping:
Installed: 3:20121221-5ubuntu2
Candidate: 3:20121221-5ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1460388/+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 1414912] [NEW] Hardware configuration not supported

[jean-christophe manciot]

Public bug reported:

Environment: Ubuntu 14.10 - nvidia-prime 0.6.7 - GeForce GTX 765M -
Intel 4700MQ

When trying to install latest nvidia driver 346.35, I got the following error 
in nvidia-prime-upstart.log:
Sorry but your hardware configuration is not supported

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

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

Title:
  Hardware configuration not supported

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Environment: Ubuntu 14.10 - nvidia-prime 0.6.7 - GeForce GTX 765M -
  Intel 4700MQ

  When trying to install latest nvidia driver 346.35, I got the following error 
in nvidia-prime-upstart.log:
  Sorry but your hardware configuration is not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1414912/+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 1388530] Re: 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M

[jean-christophe manciot]

Hey,

I have just found a workaround by chance: purging xserver-xorg-video-
nouveau (without replacing it by a Nvidia driver) from the system
removes the freezing issue during shutdown!

That's very strange because the driver is loaded with initrd during the
boot, meaning rebooting after the removal does not prevent X Server from
using the nouveau driver... without the shutdown issue that was directly
caused by the same driver.

Maybe someone can shed light on this mystery.

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

Title:
  14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed

Bug description:
  I know someone who solved this issue by installing a Nvidia driver.
  Do you test your Nouveau driver on MSI computers and computers with Nvidia 
graphics card before rolling out new releases?
  This is not the first time I'm experiencing a significant flaw with this 
driver.

  More information about the issue can be found here:
  http://ubuntuforums.org/showthread.php?t=2250017

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1388530/+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 1388530] Re: 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M

[jean-christophe manciot]

A trace has recently shown up during a failed shutdown; the following is
the OCR translation obtained from a picture (available as attachment),
meaning some decoding errors may be still there, especially in the
Modules linked in section that I have not checked:

wait-for-state stop/waiting
* Stopping rsync daemon rsync
* speech-dispatcher disabled; edit /etc/default/speech-dispatcher
* Stopping uuidd generator uuidd
* Asking all remaining processes to terminate...
* Killing all remaining processes...

ModemManager(1044]: warn Could not acquire the 
'org.freedesktop.ModemManageris service name
modemManager(1044]: info ModemManager is shut down
Deactivating swap...
[ 3944.666185] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 3944.666206] IP: [ (null)] (null)
[ 3944.666219] PGD 0
[ 3944.666225] Oops: 0010 [#1] SMP

[ 3944.666234] Modules linked in: ctr ccm rfComm bnep nls_iso88591 
snd_hda_codec_realtek snd-hda-codec-geheric snd-hda-codec-hdmi IP6t-REJECT 
xt_hl iP6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT arc4 xt_t_OG xt_limit 
xt_tcpudp x
We nf-conntracK-IPv4 nf_defrag_ipv4 xt_conntrack intel_rapi rt18723ae 
ip6table_filter ip6_tables rt18723_common x86_0(g_temp_thermal rti_pci 
intei_powerclamp uvcvideo nf_conntrack_netbios_ns rt lwif i coretemp 
nf_conntrack_broadcast
nf_nat_ftp mace snd_hda_intel kvm_intel snd_hda_controller nf_nat 
videobuf2_vmalloc snd_hda_codec Kvm snd_hwdep nf_conntrack_ftp videobuf2_memops 
videobuf2_core nf_conntrack snd_pcm v412_common 1915 videodev iptable_filter 
media
es snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi crctlOdif_pcIml snd_seq 
x_tables crc32_pclmul btusb ghash_clmuli_intel ttm aesni_intel snd_seq_device 
drm_kms_helper bluetooth aes_x86_64 snd_timer irw drm snd gf128mui rtsx
lue_helper soundcore memstick 6lowpan_lphc ablk_helper jdydev i2c_algd_bit 
cryptd mei_me IPc_ich mei shpchp serio_raw parport_pc ppdev msi_wmi 
sparse_keymap mxm_wmi 1p wmi soc_button_array parport mac hid video hid_generic 
usbhid b_storage rtsx_pci_sdmac ahci psmouse alx libahci rtsx_pci mdio
[ 3944.666555] CPU: 5 PID: 1584 Comm: Xorg Tainted: S I 3.16.0-24-generic 
#32-Ubuntu
[ 3944.666574] Hardware name: Micro-Star International Co., Ltd. GE 30 6.0-24 
BIOS El6GCIMS.511 08/27/2013
[ 3944.666596] task! 880437739e90 ti: 880427824000 task.ti: 
880427824000
[ 3944.12] RIP: 0010:[] [ (null)] (null)
1 3944.28] RSP: 0018:880427827b60 EFLAGS: 00010246
( 3944.40] RAX: c0acd040 RBX: 880438c47800 RCX: 
e0:11)
( 3944.55] RDX: c0abfaa7 RSI:  RDI: 880438c47800
[ 3944.70] RBP: 880427827b80 R08: 000O R09: c0abf9a8
[ 3944.86] R10: c0a2cb58 R11: 880438c47a00 R12: 0001
[ 3944.666701] R13:  R14: 880435282d30 R15: 8804360d3088
[ 3944.666716] FS: 7f4c73ad99c0() GSOfff88044fb4() 
knIGS:
[ 3944.666733] CS: 0010 DS:  ES:  CR0: 80050033
[ 394406667451 CR2:  CR3: 02c13000 CR4: 001407e0
[ 3944.6667601 Stack:
[ 3944.666765] 209e7065 880435282d20 880435282d48 

[ 3944.666783] 880427827bd0 c09ed98a 880427827bc0 
c0abf9a8
[ 3944.666802]   880438c47800 
c0abf810
[ 3944.666820] Call Trace:
[ 3944.666838] kc09ef065] ? nouveau_object_dec+0x125/0x2a0 [nouveau]
[ 3944.666858] [afffc09ed98a] nouveau_handle_fini+Oxlfa/Ox2a0 [nouveau]
[ 3944.666878] [Offfc09ecld3] nouveau_client_fini+Ox53/0x80 [nouveau]
[ 3944.666907] [afffc0a6e16f] nouveau_cli_destroy+Ox2f/Ox50 [nouveau]
[ 3944.666934] [c0a6e25b] nouveau_drm_postclose+Ox1b/Ox50 [nouveau]
[ 3944.666956] [dfffc03fdce4] drm_release+Ox334/0x640 [dm]
[ 3944.666970] Wfff821e26b4] __fput+Oxe4/0x240
[ 3944.666981] [afff821e285e] f_put+Oxe/Ox10
[ 3944.666994] l820919c0] task_work_run+Oxd4/Oxf0
[ 3944.6670071 (afff820725c7] do_exit+Ox377/0xab0
[ 3944.667023] kc09eef27] ? nouveau_object_del+0x97/OxbO [nouveau]
[ 3944.667039] [82072d83] do_group_exit+Ox43/0xc0
[ 3944.667052] Wfff8208312.b] get_signal_to_deliver+Ox29f/Ox8d0
( 3944.667067] U82012588] do_signal+0x48/OxbOO
( 3944.6670911 kc0a6e0da] ? nouveau_drm_ioct1+0x8a/Oxa0 [nouveau]
[ 3944.667106] (Offf8204bc8] ? do_vfs_ioctl+0x2c8/0x4a0
[ 3944.667120] k820130c9] do_notiy_resume+Ox69/OxbO
( 3944.667133] [afff82787faw] int_signal+0x12/0x17
( 3944.667144] Code: Bad RIP value.
( 3944.667154] RIP ( (null)] (null)
( 3944.667166] RSP 880427827b60
( 3944.667174] CR2: 

Nouveau is clearly involved in the bug.

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

Title:
  14.10 freezes during 

[Desktop-packages] [Bug 1388530] [NEW] 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M

[jean-christophe manciot]

Public bug reported:

I know someone who solved this issue by installing a Nvidia driver.
Do you test your Nouveau driver on MSI computers and computers with Nvidia 
graphics card before rolling out new releases?
This is not the first time I'm experiencing a significant flaw with this driver.

More information about the issue can be found here:
http://ubuntuforums.org/showthread.php?t=2250017

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  I know someone who solved this issue by installing a Nvidia driver.
  Do you test your Nouveau driver on MSI computers and computers with Nvidia 
graphics card before rolling out new releases?
  This is not the first time I'm experiencing a significant flaw with this 
driver.

  More information about the issue can be found here:
  http://ubuntuforums.org/showthread.php?t=2250017

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1388530/+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 1369049] [NEW] Error Compiling Evince 3.13.91

[jean-christophe manciot]

Public bug reported:

Environment: Ubuntu 14.04
---
root@MSI-GE60-Ubuntu-14:/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91#make
 -j6
...
  CC   libevview3_la-ev-job-scheduler.lo
In file included from ev-form-field-accessible.c:25:0:
ev-view-private.h:234:2: error: unknown type name 'GtkGesture'
  GtkGesture *pan_gesture;
  ^
ev-view-private.h:235:2: error: unknown type name 'GtkGesture'
  GtkGesture *zoom_gesture;
  ^
In file included from ev-image-accessible.c:25:0:
ev-view-private.h:234:2: error: unknown type name 'GtkGesture'
  GtkGesture *pan_gesture;
  ^
ev-view-private.h:235:2: error: unknown type name 'GtkGesture'
  GtkGesture *zoom_gesture;
  ^
make[3]: *** [libevview3_la-ev-form-field-accessible.lo] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: *** [libevview3_la-ev-image-accessible.lo] Error 1
make[3]: Leaving directory 
`/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91/libview'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91/libview'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91'
make: *** [all] Error 2

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

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

Title:
  Error Compiling Evince 3.13.91

Status in “evince” package in Ubuntu:
  New

Bug description:
  Environment: Ubuntu 14.04
  ---
  
root@MSI-GE60-Ubuntu-14:/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91#make
 -j6
  ...
CC   libevview3_la-ev-job-scheduler.lo
  In file included from ev-form-field-accessible.c:25:0:
  ev-view-private.h:234:2: error: unknown type name 'GtkGesture'
GtkGesture *pan_gesture;
^
  ev-view-private.h:235:2: error: unknown type name 'GtkGesture'
GtkGesture *zoom_gesture;
^
  In file included from ev-image-accessible.c:25:0:
  ev-view-private.h:234:2: error: unknown type name 'GtkGesture'
GtkGesture *pan_gesture;
^
  ev-view-private.h:235:2: error: unknown type name 'GtkGesture'
GtkGesture *zoom_gesture;
^
  make[3]: *** [libevview3_la-ev-form-field-accessible.lo] Error 1
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** [libevview3_la-ev-image-accessible.lo] Error 1
  make[3]: Leaving directory 
`/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91/libview'
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
`/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91/libview'
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory 
`/home/actionmystique/Program-Files/Ubuntu/Evince/evince-3.13.91'
  make: *** [all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1369049/+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 991481] Re: Constant dns traffic for daisy.ubuntu.com

[jean-christophe manciot]

Uninstalled - One DNS request for daisy.ubuntu.com should be enough.

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “network-manager” package in Ubuntu:
  In Progress
Status in “whoopsie” package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/991481/+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