[Desktop-packages] [Bug 246364] Re: seahorse asks twice for gpg key password

2017-03-31 Thread Andrew Skalski 
I did some troubleshooting on this issue, because it affects me as well.
The previous comment mentions an upstream bug report, but I haven't been
able to find it, so I'll post this here.

The first time I send a signed message after restarting Thunderbird, I
get prompted twice for my gpg key password.  Each subsequent time I send
a signed message within the same Thunderbird session, I am only prompted
once.

I should make it clear that I have my gpg-agent configured with "ignore-
cache-for-signing" enabled.  Although upstream states this case is
working as intended, I can suggest a minor code change which would
eliminate the need for the extra password prompt.

As mentioned previously, there are two signing requests to gpg2 during
this first transaction.  The first of these ("--clearsign") is signing
the message "Dummy Test" for the sole purpose of detecting which digest
algorithm gpg2 intends to use: it looks for a line such as "Hash:
SHA256" in the output.

One thing I noticed when testing gpg2 on the command line is gpg2
outputs the "Hash: SHA256" line *before* it prompts for the password.
So, the password prompt can be bypassed by adding the argument
"--pinentry-mode cancel" to the gpg2 command line:


$ /usr/bin/gpg2  --charset utf-8 --display-charset utf-8 --use-agent --batch 
--no-tty --status-fd 2 -t --clearsign --pinentry-mode cancel -u 
0xE19CF36DDF865D8405B1E4100B39535099304B41 <<< 'Dummy Test'
[GNUPG:] BEGIN_SIGNING H8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dummy Test
gpg: signing failed: Operation cancelled
[GNUPG:] FAILURE sign 67108963
gpg: [stdin]: clearsign failed: Operation cancelled


Enigmail can then parse the digest algorithm from the output without needing to 
bother the user with an extra password prompt.

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

Title:
  seahorse asks twice for gpg key password

Status in seahorse:
  Invalid
Status in enigmail package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: seahorse

  Recently I've installed Hardy. When I'm sending an email with
  Thunderbird, Enigmail asks twice for my gpg password, even though I've
  typed it correctly. This happens on Enigmail from Ubuntu package, and
  on the one downloaded from addons.mozilla.org. Same version of
  enigmail worked properly on Gutsy so it might be a Thunderbird bug.

  Edit: it's a seahorse issue. I've checked an option to remember the
  GPG password and ask before using it and now I get 2 questions about
  using my GPG password.

  Edit2: OK, now I get it. It happens when I choose the option to not
  remember my GPG passwords.

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/246364/+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 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

2016-06-29 Thread Andrew Skalski 
I tested metacity version 1:3.18.5-0ubuntu0.1 from xenial-proposed, and
confirmed the fix works correctly and with no regressions.  Firefox and
Thunderbird windows can now be dragged above the top of the screen.


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  Windows can not be moved above the top of screen because the coordinates 
system used is wrong.

  [Test Case]
  * Launch a non-CSD application, such as Firefox or Thunderbird;
  * Try Alt-dragging it above the top of the screen.

  [Regression Potential]
  The fix is changing the coordinates system to the right one and should not 
cause any regressions.

  -

  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect

  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+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 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

2016-06-21 Thread Andrew Skalski 
I tested by applying the patch against the current Ubuntu Xenial release
version of the metacity package (metacity_3.18.4-0ubuntu0.3).  I can
confirm the patch fixes the regression (it allows me to drag my Firefox
and Thunderbird windows above the top of the screen.)  So far, I have
encountered no new regressions.

I also tried building metacity git master, but ran into several unmet
dependencies (newer versions of gtk+/glib than what I have installed),
so I was unable to complete that test.

Thanks for looking into this!

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

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  New

Bug description:
  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect
 
  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+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 1509031] [NEW] can no longer alt-drag firefox/thunderbird windows above top of screen

2015-10-22 Thread Andrew Skalski 
Public bug reported:

After upgrading to 15.10, I can no longer Alt-drag Firefox and
Thunderbird windows above the top of the screen.  When I attempt to do
so, the window snaps downward along the y-axis so that the titlebar
aligns with top of screen.  Other applications such as gnome-terminal do
not seem to be affected.

I ran git-bisect on metacity, and narrowed the regression down to this
commit:

https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
Author: Alberts Muktupāvels 
Date:   Fri Apr 3 23:30:20 2015 +0300

window: add a meta_window_get_titlebar_rect
   
Based on mutter commits:

https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b

https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: metacity 1:3.17.2-4ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu Oct 22 13:35:02 2015
InstallationDate: Installed on 2014-09-22 (394 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: metacity
UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  New

Bug description:
  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect
 
  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+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 1293252] Re: gnome-panel crashed with signal 5 in _XReply()

2014-11-18 Thread Andrew Skalski 
Is there anything I can do to help troubleshoot this?  I purchased
Kerbal Space Program early access on Steam this morning, and gnome-
panel crashes with this error whenever I try to run the game.  This does
not happen with the KSP demo, only the full version.  A web search
suggests this may affect any game that uses the Unity engine, not just
KSP.

While KSP is running, any attempt to start up gnome-panel results in an
immediate crash with this error output:

(gnome-panel:7495): Gdk-ERROR **: The program 'gnome-panel' received an X 
Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 2047 error_code 8 request_code 62 (core protocol) minor_code 
0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap

I use gnome-session-flashback as my desktop environment on Ubuntu
14.10.  The default desktop environment does not seem to be affected by
this (I tried in a Guest session), but even in the Guest session you can
still reproduce the error by attempting to execute gnome-panel in a
terminal window while KSP is running.

If I install libcairo2-dbg and run gnome-panel with the GDK_SYNCHRONIZE
environment variable, the crash occurs on line 905 of
cairo-1.13.0~20140204/src/cairo-xlib-surface-shm.c when
_cairo_xlib_surface_update_shm calls XCopyArea().  According to the
XCopyArea docs at www.x.org, The drawables must have the same root and
depth, or a BadMatch error results.  Unfortunately I am not versed in X
programming, so I don't know what to try next.

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

Title:
  gnome-panel crashed with signal 5 in _XReply()

Status in “gnome-panel” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-panel 1:3.8.0-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 16 23:53:20 2014
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-02-28 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  ProcCmdline: gnome-panel
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-panel
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-panel crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1293252/+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 1293252] Re: gnome-panel crashed with signal 5 in _XReply()

2014-11-18 Thread Andrew Skalski 
I still get the crash even after removing the window-list applet.  I
actually just finished building libwnck3-3.4.7 with this line commented
out in libwnck/xutils.c in the try_pixmap_and_mask() function, and it
successfully prevents the crash.  I haven't noticed any side-effects
other than some errors logged to my terminal:

  if (mask_surface)
{
  //XXX cairo_mask_surface (cr, mask_surface, 0, 0);
  cairo_surface_destroy (mask_surface);
}
  else
cairo_paint (cr);

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

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

Title:
  gnome-panel crashed with signal 5 in _XReply()

Status in “gnome-panel” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-panel 1:3.8.0-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 16 23:53:20 2014
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-02-28 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  ProcCmdline: gnome-panel
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-panel
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-panel crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1293252/+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 1293252] Re: gnome-panel crashed with signal 5 in _XReply()

2014-11-18 Thread Andrew Skalski 
The libwnck git master works perfectly.

I can also confirm that specific commit
(5f88636284154e76611012c8a7c7495b9d917bd7) constitues the fix: applying
the diff to libwnck3_3.4.7-3.debian fixes the crash; conversely,
reverting the diff on git master reintroduces the crash.

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

Title:
  gnome-panel crashed with signal 5 in _XReply()

Status in “libwnck3” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-panel 1:3.8.0-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 16 23:53:20 2014
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-02-28 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  ProcCmdline: gnome-panel
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-panel
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-panel crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1293252/+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 924082] Re: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi

2013-09-15 Thread Andrew Skalski 
This issue no longer affects me.  The problem went away when two changes
were made to the wireless network over the span of about a week.  I
don't know which change actually fixed it, but I suspect it was the
second of the two:

One change was updating the firmware on the access points.

In the other, a misconfiguration was corrected where DHCP was issuing
gateway addresses outside of the subnet.

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

Title:
  NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino
  Ultimate-N 6300 iwlwifi

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  The iwlwifi drivers give exceptional performance on all APs I have
  connected to, be they WEP, WPA or open. The only time this system lets
  me down is when connecting to my campus wireless network.
  NetworkManager will only sometimes connect, and even manually
  configuring with iwconfig does not always work.

  The error usually given is either:

  Jan 30 01:07:51 Beast kernel: [ 8777.748471] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 (try 1/3)
  Jan 30 01:07:51 Beast kernel: [ 8777.945384] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 (try 2/3)
  Jan 30 01:07:51 Beast kernel: [ 8778.144952] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 (try 3/3)
  Jan 30 01:07:52 Beast kernel: [ 8778.344474] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 timed out

  or:

  Nov 30 19:01:27 Beast kernel: [ 1924.850725] wlan0: authenticate with 
00:24:6c:60:d0:00 (try 1)
  Nov 30 19:01:27 Beast kernel: [ 1924.852183] wlan0: 00:24:6c:60:d0:00 denied 
authentication (status 17)

  Other people report that this error may be linked to MAC filtering by
  the AP, but this should not be the case: my old computer with a
  Broadcom BCM4312 had no trouble.

  This bug is also different from several bug reports that complain of
  limited speed or packet loss: when I can connect, the connection is
  flawless. But very often I cannot connecct. The connection is
  generally worse in crowded areas, or areas with many access points.

  lspci:
  Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 
[8086:4238] (rev 3e)

  ifconfig wlan0:
  wlan0 Link encap:Ethernet  HWaddr 24:77:03:26:e8:50
    inet addr:130.64.153.137  Bcast:130.64.153.255  Mask:255.255.255.0
    inet6 addr: fe80::2677:3ff:fe26:e850/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:1288307 errors:0 dropped:0 overruns:0 frame:0
    TX packets:296448 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1016044127 (1.0 GB)  TX bytes:27674773 (27.6 MB)

   iwconfig wlan0:
  wlan0 IEEE 802.11abgn  ESSID:tuftswireless
    Mode:Managed  Frequency:5.785 GHz  Access Point: 00:24:6C:60:D0:10
    Bit Rate=300 Mb/s   Tx-Power=15 dBm
    Retry  long limit:7   RTS thr:off   Fragment thr:off
    Power Management:off
    Link Quality=61/70  Signal level=-49 dBm
    Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
    Tx excessive retries:2749  Invalid misc:7   Missed beacon:0

  lsmod | grep iw:
  iwlwifi   320164  0
  mac80211  506154  1 iwlwifi
  cfg80211  209294  2 iwlwifi,mac80211

  dmesg | grep wlan:

  [   12.059405] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
  [   12.258109] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3)
  [   12.457695] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3)
  [   12.657205] wlan0: direct probe to 00:24:6c:60:d0:00 timed out
  [   20.624778] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
  [   20.822683] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3)
  [   21.022217] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3)
  [   21.221788] wlan0: direct probe to 00:24:6c:60:d0:00 timed out
  [   29.105117] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
  [   29.303463] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3)
  [   29.503007] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3)
  [   29.702581] wlan0: direct probe to 00:24:6c:60:d0:00 timed out
  [   37.888734] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
  [   38.087513] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3)
  [   38.287083] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3)
  [   38.486602] wlan0: direct probe to 00:24:6c:60:d0:00 timed out
  [   46.376942] wlan0: authenticate with 00:24:6c:60:d0:00 (try 1)
  [   46.411091] wlan0: 00:24:6c:60:d0:00 denied authentication (status 17)

  syslog:

  Nov 30 19:01:27 Beast kernel: [ 1924.850725] wlan0: authenticate with 
00:24:6c:60:d0:00 (try 1)
  Nov 30 19:01:27 Beast kernel: [ 1924.852183] wlan0: 00:24:6c:60:d0:00 denied 
authentication (status 17)
  Nov 30 19:02:24 Beast NetworkManager[1332]: warn Activation

[Desktop-packages] [Bug 924082] Re: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi

2012-09-14 Thread Andrew Skalski 
I have a Dell Precision M4600 with Ultimate-N 6300 (rev 35), and have
had this sort of problem for quite some time.  It generally happens with
networks where there are many access points, and many people connecting
to the network (at work, at hotels, etc.)

A workaround which has been reliable in getting me connected to the
wireless network at work is to run this script in a terminal window
while NM is trying to associate with the network.  For whatever reason,
running iwconfig wlan0 essid WhateverSSID at the right moment during
association makes it succeed for me.  (On the other hand, it sometimes
causes a kernel NULL pointer derefernce in  __cfg80211_mlme_deauth,
which means I have to hard-shutdown the machine.)  I would be interested
in knowing if this script helps anybody else.

#! /bin/bash

connection_id=The SSID of your network
interface=wlan0
polls=90
interval=1

change_status() {
tput dl1
tput cr
echo $1
}

check_connection() {
if nmcli con status id $1 | grep -q '^GENERAL.STATE:.*activated'
then
change_status Activated
exit 0
fi
}

check_connection $connection_id
for (( i = 1; i = $polls; i++ ))
do
echo -n .
sudo iwconfig $interface essid $connection_id
sleep $interval
check_connection $connection_id
done

change_status '???'
exit 1

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

Title:
  NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino
  Ultimate-N 6300 iwlwifi

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  The iwlwifi drivers give exceptional performance on all APs I have
  connected to, be they WEP, WPA or open. The only time this system lets
  me down is when connecting to my campus wireless network.
  NetworkManager will only sometimes connect, and even manually
  configuring with iwconfig does not always work.

  The error usually given is either:

  Jan 30 01:07:51 Beast kernel: [ 8777.748471] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 (try 1/3)
  Jan 30 01:07:51 Beast kernel: [ 8777.945384] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 (try 2/3)
  Jan 30 01:07:51 Beast kernel: [ 8778.144952] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 (try 3/3)
  Jan 30 01:07:52 Beast kernel: [ 8778.344474] wlan0: direct probe to 
00:1a:1e:a0:3b:c0 timed out

  or:

  Nov 30 19:01:27 Beast kernel: [ 1924.850725] wlan0: authenticate with 
00:24:6c:60:d0:00 (try 1)
  Nov 30 19:01:27 Beast kernel: [ 1924.852183] wlan0: 00:24:6c:60:d0:00 denied 
authentication (status 17)

  Other people report that this error may be linked to MAC filtering by
  the AP, but this should not be the case: my old computer with a
  Broadcom BCM4312 had no trouble.

  This bug is also different from several bug reports that complain of
  limited speed or packet loss: when I can connect, the connection is
  flawless. But very often I cannot connecct. The connection is
  generally worse in crowded areas, or areas with many access points.

  lspci:
  Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 
[8086:4238] (rev 3e)

  ifconfig wlan0:
  wlan0 Link encap:Ethernet  HWaddr 24:77:03:26:e8:50
    inet addr:130.64.153.137  Bcast:130.64.153.255  Mask:255.255.255.0
    inet6 addr: fe80::2677:3ff:fe26:e850/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:1288307 errors:0 dropped:0 overruns:0 frame:0
    TX packets:296448 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1016044127 (1.0 GB)  TX bytes:27674773 (27.6 MB)

   iwconfig wlan0:
  wlan0 IEEE 802.11abgn  ESSID:tuftswireless
    Mode:Managed  Frequency:5.785 GHz  Access Point: 00:24:6C:60:D0:10
    Bit Rate=300 Mb/s   Tx-Power=15 dBm
    Retry  long limit:7   RTS thr:off   Fragment thr:off
    Power Management:off
    Link Quality=61/70  Signal level=-49 dBm
    Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
    Tx excessive retries:2749  Invalid misc:7   Missed beacon:0

  lsmod | grep iw:
  iwlwifi   320164  0
  mac80211  506154  1 iwlwifi
  cfg80211  209294  2 iwlwifi,mac80211

  dmesg | grep wlan:

  [   12.059405] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
  [   12.258109] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3)
  [   12.457695] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3)
  [   12.657205] wlan0: direct probe to 00:24:6c:60:d0:00 timed out
  [   20.624778] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
  [   20.822683] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3)
  [   21.022217] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3)
  [   21.221788] wlan0: direct probe to 00:24:6c:60:d0:00 timed out
  [

[Desktop-packages] [Bug 877803] Re: network-manager forgets wireless password after I cancel connection

2011-10-26 Thread Andrew Skalski 
This also affects me, ever since upgrading to Oneiric.  What I would
like the behavior to be: Only update the keyring after successfully
authenticating to the wireless network.  This would protect good keys
from temporary failures.

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

Title:
  network-manager forgets wireless password after I cancel connection

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  When I am using my netbook in a different room from where the router
  is and have a weak connection, sometimes network-manager has a hard
  time connecting and prompts me for a password, with the password field
  filled with the correct password (although hidden). Normally I hit
  cancel because it's unlikely to succeed, and a few minutes later I
  try to connect again by clicking on my wireless network through the
  panel applet. After upgrading to Oneiric, if I hit cancel, network-
  manager automatically deletes the password, which is no longer to be
  found in the Edit Connections dialog, so I have to go find out the
  password and enter it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.1.90-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Oct 19 01:07:25 2011
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.3  metric 1
  Keyfiles: Error: [Errno 2] No such file or directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/877803/+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