Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-03 Thread auspex 
Seems to me that if NM stalls due to a race condition, then restarting NM
*is* a workaround, so yes, adding additional scripts to systemd is a
solution, but not the "answer".

derek

On Fri, Feb 3, 2017 at 1:11 AM, Tony Espy <1585...@bugs.launchpad.net>
wrote:

> @Kevin
>
> NetworkManager already has code to monitor system signals related to
> suspend/resume, so no adding additional scripts to /usr/lib/systemd
> /system-sleep isn't the answer.
>
> @Dan
>
> Different bug...  this bug is caused by NetworkManager's WiFi scanning
> logic stalling due to a race condition.  You can tell this by running
> 'sudo wpa_cli' and watching for scan events.  If you don't see any, then
> you've hit the bug.
>
> I've also unfortunately confirmed that dropping the original patch from
> 1.2.6 doesn't fix the problem either.  I tried a cycle of 100 with my
> version of 1.2.6 with the original ScanDone patch dropped and I still
> tripped the bug.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1448555).
> https://bugs.launchpad.net/bugs/1585863
>
> Title:
>   WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
>   required to fix it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions
>

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-12-22 Thread auspex 
You're kidding?  "no longer affects:network-manager"

It certainly did as recently as yesterday!

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-11-18 Thread auspex 
@JaSauders I think the downside is that restarting NetworkManager, on a
system that doesn't have any problem with network connections after a
suspend event (and that surely must be most systems, or this would be
fixed already) will result in a much slower reconnection to the network.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-11-17 Thread auspex 
btw, merely restarting Network Manager never worked for me. I have to
remove iwlwifi and reload it.

derek

On Thu, Nov 17, 2016 at 2:18 PM, Derek Broughton 
wrote:

> We used to have this. I'm sure, a decade ago, I could actually tell
> whatever was managing the hibernate/suspend, in the gui, to remove certain
> kernel modules on suspend and load them on resume. Now we're right back to
> needing it.
>
> derek
>
> On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon  wrote:
>
>> This serious issue is dragging to long.  People want computers that
>> "just work".  If pinpointing the source of the problem is difficult and
>> few resources are available, why not package a workaround that restarts
>> NetworkManager upon resume?
>>
>> Attached is my workaround.  Works nicely.  Finally, I have a computer
>> that "just works" and it's not a Mac (well, I have other issues but this
>> one is solved).
>>
>> Simple move the script under /lib/systemd/system-sleep and ensure it is
>> executable.
>>
>> ** Attachment added: "Workaround that restarts the NetworkManager upon
>> resume."
>>https://bugs.launchpad.net/ubuntu/+source/network-manager/+
>> bug/1585863/+attachment/4778652/+files/NetworkManagerR
>> estartWorkaroundForBug1380480.sh
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1448555).
>> https://bugs.launchpad.net/bugs/1585863
>>
>> Title:
>>   WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
>>   required to fix it.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions
>>
>
>

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-11-17 Thread auspex 
We used to have this. I'm sure, a decade ago, I could actually tell
whatever was managing the hibernate/suspend, in the gui, to remove certain
kernel modules on suspend and load them on resume. Now we're right back to
needing it.

derek

On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon  wrote:

> This serious issue is dragging to long.  People want computers that
> "just work".  If pinpointing the source of the problem is difficult and
> few resources are available, why not package a workaround that restarts
> NetworkManager upon resume?
>
> Attached is my workaround.  Works nicely.  Finally, I have a computer
> that "just works" and it's not a Mac (well, I have other issues but this
> one is solved).
>
> Simple move the script under /lib/systemd/system-sleep and ensure it is
> executable.
>
> ** Attachment added: "Workaround that restarts the NetworkManager upon
> resume."
>https://bugs.launchpad.net/ubuntu/+source/network-
> manager/+bug/1585863/+attachment/4778652/+files/
> NetworkManagerRestartWorkaroundForBug1380480.sh
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1448555).
> https://bugs.launchpad.net/bugs/1585863
>
> Title:
>   WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
>   required to fix it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions
>

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-08-04 Thread auspex 
You can try having the script do "modprobe -r" and "modprobe" on your wifi
module. That should always work, but seemed like overkill in my case. In
any case, these are workarounds, not fixes.

On 4 Aug 2016 6:01 a.m., "Aleve Sicofante" <asicofa...@gmail.com> wrote:

> @auspex: Your script doesn't work here. I just created it and gave it
> execution permissions, rebooted and tried a sleep/resume cycle. No dice.
>
> I'm just amazed no one from Canonical is chiming in. This has been
> happening from the very moment I installed 16.04 on its release day and
> it happens in the two laptops I use (Lenovo T400 and Dell Studio 1537,
> both with Intel wireless cards). It's so obvious I didn't even try to
> file a bug understanding it would be naturally solved by 16.04.1 at the
> latest... I'm truly amazed in the worst sense.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1448555).
> https://bugs.launchpad.net/bugs/1585863
>
> Title:
>   WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
>   required to fix it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions
>

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-07-23 Thread auspex 
I finally worked around my problem by adding a script in /lib/systemd
/system-sleep/:

$ cat /lib/systemd/system-sleep/12_wifi
#!/bin/bash

case $1 in
  "post")
# disable/enable wifi
rfkill block wifi; rfkill unblock wifi
logger "reenabled wifi"
  ;;
esac

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2016-07-14 Thread auspex 
because restarting network-manager from sleep.d isn't even a workaround,
let alone a fix.  With that, my network successfully reconnects just
about as often as if there is nothing in sleep.d.

Which, apparently, would be because /etc/pm/sleep.d is  never invoked.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update

2016-05-02 Thread auspex 
Please don't suggest installing non-standard packages as a "fix" for
broken packages in the default setup. Yeah, Network-manager is a pain
and always has been, but until the distros choose to focus on Wicd
rather than network-manager, NM is the tool that HAS to work to keep
interest in Linux up.

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

Title:
  [Kubuntu] Fail to connect to wifi after a recent update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I installed the recent updates in the Update Manager and after rebooting I 
wasn't able to connect to my wifi network anymore.
  It attempts to connect to the network and fails with the following error 
message:

  Failed to update connection [network name]
  connection.gateway-ping-timeout: can not set property:
  value "46730064" of type 'guint' is invalid or out of range for property 
'gateway-ping-timeout' of type 'guint'

  I am able to use wired connection.

  1. release:
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  2. network-manager version:
  network-manager:
Installed: 1.1.93-0ubuntu3
Candidate: 1.1.93-0ubuntu3
Version table:
   *** 1.1.93-0ubuntu3 500
  500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expected the machine to connect to wifi as always

  4. it failed to connect with the above error message

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 13 06:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-01 (11 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  IpRoute:
   default via 10.100.102.1 dev enp0s31f6  proto static  metric 100 
   10.100.102.0/24 dev enp0s31f6  proto kernel  scope link  src 10.100.102.5  
metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-12T22:28:14.870844
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s31f6  ethernet  connected/org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  d956dc0d-4de6-4f45-8869-a3703d8d0d28  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0 wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569674/+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 1296133] Re: Suspend and hibernate missing from KMenu and Power Management in System settings

2014-10-14 Thread auspex 
What would have fixed it? Given that there are all kinds of things that
have worked for some, and not for others, unless we know a specific
change that should fix the behaviour, I'd say there's still a bug.

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

Title:
  Suspend and hibernate missing from KMenu and Power Management in
  System settings

Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  I have used install scripts to install Kubuntu 14.04 on three
  completely different systems. Although the packages installed are
  basically the same, one of the system has no Suspend/hibernate options
  in the KMenu nor in the Power management in the KDE System settings.
  Since this is a laptop, this also means that the battery life is
  greatly reduced, because it cannot go to standby when lid is closed or
  when it's idle. Interestingly, If I logout,  there is a Standby button
  on the lighdm login screen. If I click it, the laptop goes to standby
  and wakes up without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 22 21:18:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-14 (8 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Alpha amd64 
(20140130)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1296133/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-05-06 Thread auspex 
I did have to upgrade oxygen as specified by David, too, as even with
the Raleigh theme I was getting failures (much less frequent or
reproducible than before upgrading libgtk, though).  After upgrading
oxygen, I didn't experience any further failures.

Of course, now I'm in the process of upgrading to ubuntu 14.04, so the
whole process is likely to begin again...

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

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

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

Re: [Desktop-packages] [Bug 1241101]

2014-04-16 Thread auspex 
Fingers crossed, David!  Simply installing libgtk-3-0 worked for the
trivial case I described above, where I could always make it fail (I
haven't upgraded oxygen, yet, and probably won't if this works without
it—I'm still using the override
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc).


On Wed, Apr 16, 2014 at 8:49 AM, David Matějček
1241...@bugs.launchpad.netwrote:

 It seems it is fixed in newer GTK, but after my recent experiences I am
 not so optimistic. But after upgrade to 1.3.5 and also GTK 3.10 and
 restarting the system Eclipse still did not crash (10 hours yesterday, 5
 hours today, switching git branches on massive project, debugging,
 refactoring).

 Can you try it someone too? (package is big, you need fast connection)
 sudo add-apt-repository ppa:gnome3-team/gnome3
 sudo apt-get install libgtk-3-0
 Download 1.3.5: https://launchpad.net/ubuntu/+source/oxygen-gtk3
 Unpack and see instructions in the file INSTALL.

 I hope Eclipse will be stable on Kubuntu 14.04 without these experiments
 ...

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1241101

 Title:
   Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

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



-- 
derek

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

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

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

Re: [Desktop-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-11 Thread auspex 
Nice idea, David but no luck for me.

I start Eclipse with:
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .

and do Ctrl-F, and click on Find, Find, Close. Eclipse aborts at
g_object_get_qdata+0x18

I restart Eclipse, find the PID, and do:
$  taskset -p 0x0001 32060
pid 32060's current affinity mask: f
pid 32060's new affinity mask: 1
so, it appears to have worked. I execute the same sequence and Eclipse
aborts  at g_object_get_qdata+0x18. Also note:
# An error report file with more information is saved as:
# /home/derek/.../hs_err_pid32060.log
so I had the right PID.



On Thu, Apr 10, 2014 at 10:28 PM, David Matějček 1241...@bugs.launchpad.net
 wrote:

 I use Eclipse Kepler 4.3.2 and this bug occurs more often then ever before!
 Eclipse also is not the only application crashing with this bug - today I
 have seen bugreport also for Gimp.

 Workaround:
 1) Start the Eclipse
 2) find pid of the process
 3) taskset -p 0x0001 pid

 The problem is something like with volatile and synchronized; with this I
 used two Eclipse instances for 12 hours without a crash!
 After restart I forgot to set it again and Eclipse crashed after 5 minutes
 ...

 Now again with taskset after 2 hours no problem.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1241101

 Title:
   Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

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



-- 
derek

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-11 Thread auspex 
I'll add that my test was not using Kepler, but David's suggesting
Kepler doesn't change things.

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 577919] Re: chromium-browser fails to start (guest account, OpenVZ): Failed to move to new PID namespace: Operation not permitted

2014-02-08 Thread auspex 
AND on 13.10.  Four years, and nobody gives a damn about making it
REALLY work.

So, what you're saying is we introduced a guest login, but we don't
really want it to be able to do anything (who on earth suggested
Firefox was a reasonable workaround?).

So, I have a workaround. Forget about every using the Guest account.
Create an a real user account, and remove the password. It's surely less
secure, but it can actually do real work.

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

Title:
  chromium-browser fails to start (guest account, OpenVZ): Failed to
  move to new PID namespace: Operation not permitted

Status in Chromium Browser:
  Unknown
Status in Light Display Manager:
  Fix Released
Status in OpenVZ kernel (patchset):
  Confirmed
Status in “gdm-guest-session” package in Ubuntu:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm-remote-session-freerdp” package in Ubuntu:
  Fix Released
Status in “lightdm-remote-session-uccsconfigure” package in Ubuntu:
  Fix Released
Status in “gdm-guest-session” source package in Precise:
  Won't Fix
Status in “lightdm” source package in Precise:
  Fix Released
Status in “lightdm-remote-session-freerdp” source package in Precise:
  Invalid
Status in “lightdm-remote-session-uccsconfigure” source package in Precise:
  Invalid

Bug description:
  Binary package hint: chromium-browser

  [Impact]
  Chromium-browser does not launch from guest session.

  Fix by Jamie Strandboge:
  It would be nice if AppArmor could merge profiles, but we can't yet, so we 
need to do like you initially did: have two mostly identical profiles. Because 
the lightdm remote sessions are shipping policy copies, the maintenance cost is 
getting high. I will be abstracting out the guest rules into 
abstracations/lightdm and then have a small snippet using a child profile in 
abstractions/lightdm_chromium-browser. The guest and remote lightdm profiles 
can just include these and all the policy is in the abstractions. Using a 
lightdm.d directory is a good idea, but upstream AppArmor is currently 
discussing how to best handle .d directories like this, and I'd rather not add 
another one until that discussions is finished.

  [Test Case]
  1. install chromium-browser
  2. login to the guest account
  3. login to vt1 or login via ssh as a regular user and verify that the 
lightdm profile
     is loaded and guest session applications are confined:
  $ sudo aa-status
  apparmor module is loaded.
  ...
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper
  ...
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1378)
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1414)
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1417)
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1418)
  ...

  Note: number of profiles and pids will vary.

  4. try to start chromium-browser either via the Dash or a terminal

  Prior to upgrading, chromium-browser will fail to start with:
  Failed to move to new PID namespace: Operation not permitted

  After upgrading, the guest session should be functional and chromium-browser 
should start. In addition, aa-status should report a child profile for 
chromium-browser and chromium-browser should be under that confinement with 
other guest session applications under the lightdm-guest-session-wrapper 
confinement:
  $ sudo aa-status
  apparmor module is loaded.
  ...
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser
  ...
 /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2667) 
 /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2672) 
 /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2682)
  ...
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser 
(3090)
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser 
(3092)
     /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser 
(3093)
  ...

  [Regression Potential]
  As mentioned in the Impact, the apparmor profile for lightdm has necessarily 
been broken out into multiple parts. As such, there is potential that the guest 
session profile won't
  work correctly, however, this is easily seen in the test cases and these 
changes have been in place since 12.10.

  [Other Info]
  Attached is a debdiff for 12.04. It:
   - adds debian/patches/05_lp577919-fix-chromium-launch.patch which is the 
same as
     debian/patches/09_lp577919-fix-chromium-launch.patch from quantal, except 
it a)
     does not include the fix for bug #1059510, which is uneeded on precise and 
b)
     includes the fix for bug #1189948 to install the abstractions with the 
correct
     permissions
   - additionally, debian/lightdm.postinst is updated to reload the

[Desktop-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-01-31 Thread auspex 
@daff Why would you assume a different bug? I have tried it with both forms
UBUNTU_MENUPROXY='' GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc 
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .
and setting the theme in System Settings, and I _can_ use Eclipse for a while, 
but sooner or later I'm going to crash in exactly the same location `# C  
[libgobject-2.0.so.0+0x19528]  g_object_get_qdata+0x18`

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-01-28 Thread auspex 
The GTK2_RC_FILES  theme workaround doesn't help me, nor does
UBUNTU_MENUPROXY.

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

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