from:"sokai"

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2019-12-19 Thread sokai

Hi!

@Vadym K (hmvs): What is your workaround good for?

In general:
I'm also effected by this bug on 18.04.3 (NetworkManager v1.10.14) and can't 
see any 'official' solution (for Bionic). – Can someone maybe help (me)?

Thanks and KR!

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

2019-05-03 Thread sokai

FYI: I feel it's (somehow) fixed (for me). I haven't seen this behavior
since some days.

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

Title:
  Unlocking the  screen takes 5 seconds in Xorg sessions (not so much in
  Wayland sessions)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1556435] Re: totem crashed with SIGSEGV

2016-08-05 Thread sokai

*** This bug is a duplicate of bug 1574253 ***
https://bugs.launchpad.net/bugs/1574253

** This bug is no longer a duplicate of bug 1550444
   Parole media player segfaults when seeking forward in a video file
** This bug has been marked a duplicate of bug 1574253
   totem segfaults on 16.04

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

Title:
  totem crashed with SIGSEGV

Status in totem package in Ubuntu:
  New

Bug description:
  Just opening Totem causes it to segfault:
  $ totem
  Segmentation fault (core dumped)

  The machine in question is an old desktop with Pentium 4 and Radeon
  9200 SE AGP graphics card, Radeon driver. The OS is Ubuntu 16.04 with
  gnome-flashback (metacity).

  ~$ lscpu
  Architecture:  i686
  CPU op-mode(s):32-bit
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  Vendor ID: GenuineIntel
  CPU family:15
  Model: 4
  Model name:Intel(R) Pentium(R) 4 CPU 3.00GHz
  Stepping:  1
  CPU MHz:   3060.436
  BogoMIPS:  6120.87
  L1d cache: 16K
  L2 cache:  1024K
  Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx 
constant_tsc pebs bts pni dtes64 monitor ds_cpl cid xtpr

  Full hardware specs are at http://paste.ubuntu.com/15360138/.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Mar 12 17:45:41 2016
  Disassembly: => 0x1:  Cannot access memory at address 0x1
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-02-14 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160212)
  ProcCmdline: totem
  SegvAnalysis:
   Segfault happened at: 0x1:   Cannot access memory at address 0x1
   PC (0x0001) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV
  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/totem/+bug/1556435/+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 1584884] Re: totem crush with Segmentation fault.

2016-08-05 Thread sokai

*** This bug is a duplicate of bug 1574253 ***
https://bugs.launchpad.net/bugs/1574253

** This bug has been marked a duplicate of bug 1574253
   totem segfaults on 16.04

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

Title:
  totem crush with Segmentation fault.

Status in totem package in Ubuntu:
  Expired

Bug description:
  Run:
  >totem
  Segmentation fault (core dumped)
  >totem
  Segmentation fault (core dumped)

  run with gdb:

  >gdb totem
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from totem...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/bin/totem 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffdb903700 (LWP 21787)]
  [New Thread 0x7fffdacbd700 (LWP 21788)]
  [New Thread 0x7fffda3b0700 (LWP 21790)]
  [New Thread 0x7fffd9baf700 (LWP 21791)]
  [New Thread 0x7fffcacfc700 (LWP 21808)]
  [New Thread 0x7fffca08a700 (LWP 21810)]
  [New Thread 0x7fffc295f700 (LWP 21826)]
  [New Thread 0x7fffc215e700 (LWP 21827)]
  [New Thread 0x7fffc0881700 (LWP 21828)]
  [New Thread 0x7fffb3b88700 (LWP 21829)]
  [New Thread 0x7fff9b6b7700 (LWP 21844)]
  [New Thread 0x7fff9aeb6700 (LWP 21845)]
  [New Thread 0x7fff997c0700 (LWP 21848)]
  [New Thread 0x7fff8bfff700 (LWP 21850)]

  Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
  0x7fffdc55c083 in LLVMBuildLoad () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
  (gdb) q

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 23 19:59:00 2016
  InstallationDate: Installed on 2009-11-30 (2366 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to xenial on 2015-11-05 (200 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1584884/+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 1020051] Re: Xorg freeze

2013-02-28 Thread sokai

This bug hits me, too. :-/

I use a Samsung NC10.

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

Title:
  Xorg freeze

Status in Compiz:
  New
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  My screen hangs randomly. The only thing that is responsive is the
  touchpad. I can mve the mouse pointer across the screen but cannot
  click anything. The system cannot be soft-restarted too. The only
  resort is to press the power button long enough to do shutdown the
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Mon Jul  2 16:53:48 2012
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1020051/+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 1106110] Re: gnome-keyring changes tmp-folder during Gnome-session

2013-02-21 Thread sokai

Hi there!

This morning I had this problem again and I will explain the problem
more …

During my Gnome-session gnome-keyring dies (in the background) without any 
error messages (/var/log/syslog, ~/.xsession-errors).
As you can see in the following command output, there are multiple 
keyring-folders in /tmp.

# ps aux|grep keyr
$user 2337  0.0  0.0  51596  7428 ?Sl   Feb20   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
$user18099  0.2  0.1  75620 14032 ?SLl  10:18   0:01 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
$user18926  0.0  0.0   5884   832 pts/1S+   10:29   0:00 grep keyr

# ll /tmp/
drwx-- 2 $user   $user   4,0K Feb 20 16:50 keyring-92x5pQ/
drwx-- 2 $user   $user   4,0K Feb 20 13:18 keyring-B1KV8T/
drwx-- 2 $user   $user   4,0K Feb 20 16:46 keyring-lIhMpd/
drwx-- 2 $user   $user   4,0K Feb 21 10:18 keyring-ZciiCm/

It seems there are some similarities with Bug #383926 [0]. I think there
could be a temporarily workaround if I would know the equivalent for
„$SSH_AUTH_SOCK“.

[0] https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/383926/comments/10

I can use the new keyring-folder in (i.e.) Chromium after a automatic re-auth. 
(In Chromium the keyring-auth pops up and I can enter my password to get access 
to the new keyring instance.)
In Thunderbird/Enigmail that doesn't work! There is no re-auth dialog after the 
keyring-restart (in the background) and I only get a pop-up with the message, 
that I used a wrong password for encryption (of my email). :-/

For me only a logout→login solves the problem (with Thunderbird/Enigmail). – Or 
 a reboot …
I don't think that the silent deaths of gnome-keyring in the background are 
‚normal‘, so I posted this bug-report.

Thanks a lot for taking attention and best regards!

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

Title:
  gnome-keyring changes tmp-folder during Gnome-session

Status in “gnome-keyring” package in Ubuntu:
  New

Bug description:
  Hi there!

  Since some weeks I have the following problem on my system (Ubuntu
  12.04).

  During a running Ubuntu session (i.e. the uptime is 16 hours) my
  system looses the connection to the right tmp-folder of the running
  gnome-keyring-daemon.

  Error message:
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-Ea7GEe/pkcs11: 
Verbindungsaufbau abgelehnt

  Running process:
  $user25131  0.1  0.0  51620  7428 ?Sl   15:55   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

  Content of tmp-folder:
  drwx-- 2 $user   $user   4,0K Jan 26 00:00 keyring-Ea7GEe/
  drwx-- 2 $user   $user   4,0K Jan 26 16:09 keyring-t5kJex/

  So you can see, the original tmp-folder (Ea7GEe) is still there, but a
  new one (t5kJex) was created. And so I have to reboot my box, to get
  the correct connection for all my running apps (like Thunderbird with
  Enigmail) or on aria2 in my terminal (it works, but I get the error
  message).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1106110/+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 1106110] Re: gnome-keyring changes tmp-folder during Gnome-session

2013-02-21 Thread sokai

** Summary changed:

- gnome-keyring changes tmp-folder during session
+ gnome-keyring changes tmp-folder during Gnome-session

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

Title:
  gnome-keyring changes tmp-folder during Gnome-session

Status in “gnome-keyring” package in Ubuntu:
  New

Bug description:
  Hi there!

  Since some weeks I have the following problem on my system (Ubuntu
  12.04).

  During a running Ubuntu session (i.e. the uptime is 16 hours) my
  system looses the connection to the right tmp-folder of the running
  gnome-keyring-daemon.

  Error message:
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-Ea7GEe/pkcs11: 
Verbindungsaufbau abgelehnt

  Running process:
  $user25131  0.1  0.0  51620  7428 ?Sl   15:55   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

  Content of tmp-folder:
  drwx-- 2 $user   $user   4,0K Jan 26 00:00 keyring-Ea7GEe/
  drwx-- 2 $user   $user   4,0K Jan 26 16:09 keyring-t5kJex/

  So you can see, the original tmp-folder (Ea7GEe) is still there, but a
  new one (t5kJex) was created. And so I have to reboot my box, to get
  the correct connection for all my running apps (like Thunderbird with
  Enigmail) or on aria2 in my terminal (it works, but I get the error
  message).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1106110/+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 1106110] [NEW] gnome-keyring changes tmp-folder during session

2013-01-26 Thread sokai

Public bug reported:

Hi there!

Since some weeks I have the following problem on my system (Ubuntu
12.04).

During a running Ubuntu session (i.e. the uptime is 16 hours) my system
looses the connection to the right tmp-folder of the running gnome-
keyring-daemon.

Error message:
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-Ea7GEe/pkcs11: 
Verbindungsaufbau abgelehnt

Running process:
$user25131  0.1  0.0  51620  7428 ?Sl   15:55   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

Content of tmp-folder:
drwx-- 2 $user   $user   4,0K Jan 26 00:00 keyring-Ea7GEe/
drwx-- 2 $user   $user   4,0K Jan 26 16:09 keyring-t5kJex/

So you can see, the original tmp-folder (Ea7GEe) is still there, but a
new one (t5kJex) was created. And so I have to reboot my box, to get the
correct connection for all my running apps (like Thunderbird with
Enigmail) or on aria2 in my terminal (it works, but I get the error
message).

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

** Description changed:

  Hi there!
  
- Since some weeks I have the following problem on my system.
+ Since some weeks I have the following problem on my system (Ubuntu
+ 12.04).
  
  During a running Ubuntu session (i.e. the uptime is 16 hours) my system
  looses the connection to the right tmp-folder of the running gnome-
  keyring-daemon.
  
- Error message: 
+ Error message:
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-Ea7GEe/pkcs11: 
Verbindungsaufbau abgelehnt
  
  Running process:
  $user25131  0.1  0.0  51620  7428 ?Sl   15:55   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
  
  Content of tmp-folder:
  drwx-- 2 $user   $user   4,0K Jan 26 00:00 keyring-Ea7GEe/
  drwx-- 2 $user   $user   4,0K Jan 26 16:09 keyring-t5kJex/
  
  So you can see, the original tmp-folder (Ea7GEe) is still there, but a
  new one (t5kJex) was created. And so I have to reboot my box, to get the
  correct connection for all my running apps (like Thunderbird with
  Enigmail) or on aria2 in my terminal (it works, but I get the error
  message).

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

Title:
  gnome-keyring changes tmp-folder during session

Status in “gnome-keyring” package in Ubuntu:
  New

Bug description:
  Hi there!

  Since some weeks I have the following problem on my system (Ubuntu
  12.04).

  During a running Ubuntu session (i.e. the uptime is 16 hours) my
  system looses the connection to the right tmp-folder of the running
  gnome-keyring-daemon.

  Error message:
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-Ea7GEe/pkcs11: 
Verbindungsaufbau abgelehnt

  Running process:
  $user25131  0.1  0.0  51620  7428 ?Sl   15:55   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

  Content of tmp-folder:
  drwx-- 2 $user   $user   4,0K Jan 26 00:00 keyring-Ea7GEe/
  drwx-- 2 $user   $user   4,0K Jan 26 16:09 keyring-t5kJex/

  So you can see, the original tmp-folder (Ea7GEe) is still there, but a
  new one (t5kJex) was created. And so I have to reboot my box, to get
  the correct connection for all my running apps (like Thunderbird with
  Enigmail) or on aria2 in my terminal (it works, but I get the error
  message).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1106110/+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 876350] Re: Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient works; manually setting ESSID (which wasn't set by NM) fixes it -- Ralink RT2860 rt2800pci

2012-07-22 Thread sokai

** Changed in: network-manager (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient
  works; manually setting ESSID (which wasn't set by NM) fixes it --
  Ralink RT2860 rt2800pci

Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  Since my upgrade to Oneiric I can't connect to the unencrypted Ad-hoc network 
of my Freifunk community anymore. :(
  If I use the (Unity) network-indicator the connection can't be established. I 
have an ASUS EeePC 1000 with the Ralink RT2860 chip. With Oneiric my system 
uses the rt2800pci kernel module. (I did no changes to the modules or the GRUB 
command line etc..)

  After digging around I found out the following.
  1. During the connection process to the ad-hoc network with the ESSID 
www.freifunk-potsdam.de I can see this three lines in my /var/log/syslog:
  wpa_supplicant[2650]: Authentication with 00:00:00:00:00:00 timed out.
  wpa_supplicant[2650]: Trying to associate with SSID 'www.freifunk-potsdam.de'
  wpa_supplicant[2650]: Association request to the driver failed

  2. I can establish a connection if I do it manually by:
  $ iwconfig wlan0 mode ad-hoc
  $ iwconfig wlan0 essid www.freifunk-potsdam.de
  $ dhclient wlan0

  3. During the connection process - initiated by clicking on my network in the 
network-indicator - I can see that my wlan0 device hasn't set an ESSID.  - So 
for me its clear why I can't connect. Without a assigned ESSID I cen't get an 
IP address. iwconfig wlan0 during the connection process is:
  wlan0 IEEE 802.11bgn  ESSID:off/any  
Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: Not-Associated   
Tx-Power=20 dBm   
Retry  long limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off

  4. If I set the ESSID manually during the connection process -
  initiated by clicking on my network in the network-indicator - by
  iwconfig wlan0 essid 'www.freifunk-potsdam.de' the connection
  becomes established and I get an IP address at the end.

  To sum it up:
  During the connection process for an ad-hoc network during the 
network-indicator the ESSID is not set and so no connection can be established.

  I would be happy if you can give me an hint for fixing this. :)

  Thanks and best regards!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/876350/+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 876350] Re: Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient works; manually setting ESSID (which wasn't set by NM) fixes it -- Ralink RT2860 rt2800pci

2012-07-22 Thread sokai

@Thomas:

Thanks for your reminder...! ;)

Yes it seems to be fixed. Thanks a lot! Some minutes ago I switched the 
connection two times and everything looks like everything works O.K..
(Furthermore I changed this bug status to Fix Released...)

Best regards!

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

Title:
  Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient
  works; manually setting ESSID (which wasn't set by NM) fixes it --
  Ralink RT2860 rt2800pci

Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  Since my upgrade to Oneiric I can't connect to the unencrypted Ad-hoc network 
of my Freifunk community anymore. :(
  If I use the (Unity) network-indicator the connection can't be established. I 
have an ASUS EeePC 1000 with the Ralink RT2860 chip. With Oneiric my system 
uses the rt2800pci kernel module. (I did no changes to the modules or the GRUB 
command line etc..)

  After digging around I found out the following.
  1. During the connection process to the ad-hoc network with the ESSID 
www.freifunk-potsdam.de I can see this three lines in my /var/log/syslog:
  wpa_supplicant[2650]: Authentication with 00:00:00:00:00:00 timed out.
  wpa_supplicant[2650]: Trying to associate with SSID 'www.freifunk-potsdam.de'
  wpa_supplicant[2650]: Association request to the driver failed

  2. I can establish a connection if I do it manually by:
  $ iwconfig wlan0 mode ad-hoc
  $ iwconfig wlan0 essid www.freifunk-potsdam.de
  $ dhclient wlan0

  3. During the connection process - initiated by clicking on my network in the 
network-indicator - I can see that my wlan0 device hasn't set an ESSID.  - So 
for me its clear why I can't connect. Without a assigned ESSID I cen't get an 
IP address. iwconfig wlan0 during the connection process is:
  wlan0 IEEE 802.11bgn  ESSID:off/any  
Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: Not-Associated   
Tx-Power=20 dBm   
Retry  long limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off

  4. If I set the ESSID manually during the connection process -
  initiated by clicking on my network in the network-indicator - by
  iwconfig wlan0 essid 'www.freifunk-potsdam.de' the connection
  becomes established and I get an IP address at the end.

  To sum it up:
  During the connection process for an ad-hoc network during the 
network-indicator the ESSID is not set and so no connection can be established.

  I would be happy if you can give me an hint for fixing this. :)

  Thanks and best regards!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/876350/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Desktop-packages] [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

[Desktop-packages] [Bug 1556435] Re: totem crashed with SIGSEGV

[Desktop-packages] [Bug 1584884] Re: totem crush with Segmentation fault.

[Desktop-packages] [Bug 1020051] Re: Xorg freeze

[Desktop-packages] [Bug 1106110] Re: gnome-keyring changes tmp-folder during Gnome-session

[Desktop-packages] [Bug 1106110] Re: gnome-keyring changes tmp-folder during Gnome-session

[Desktop-packages] [Bug 1106110] [NEW] gnome-keyring changes tmp-folder during session

[Desktop-packages] [Bug 876350] Re: Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient works; manually setting ESSID (which wasn't set by NM) fixes it -- Ralink RT2860 rt2800pci

[Desktop-packages] [Bug 876350] Re: Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient works; manually setting ESSID (which wasn't set by NM) fixes it -- Ralink RT2860 rt2800pci

10 matches

Site Navigation

Mail list logo

Footer information