[Desktop-packages] [Bug 779754] Re: NM status icon sometimes not clickable

2013-01-28 Thread Domen Kožar
Same here running 12.04 with latests updates. What can I do to help with
debugging?

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

Title:
  NM status icon sometimes not clickable

Status in “network-manager-applet” package in Ubuntu:
  In Progress

Bug description:
  Sometimes lately after upgrade to Natty the network manager status
  icon is not possible to click on, nothing happens. When it happened
  now, it seems to be solved by restarting network-manager service
  (sudo service network-manager restart).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic i686
  Architecture: i386
  CRDA: Error: [Errno 2] Ingen slik fil eller filkatalog
  Date: Mon May  9 09:09:42 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IpRoute:
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.130  
metric 2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   default via 192.168.1.1 dev wlan0  proto static
  Keyfiles: Error: [Errno 2] Ingen slik fil eller filkatalog
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=nb_NO:en
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to natty on 2011-04-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/779754/+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 903422] Re: Ubuntu does not work with Samsung Galaxy phones ( Unable to open raw device 0)

2013-01-17 Thread Domen Kožar
Agreed, this needs to be backported, otherwise we are losing users :)

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

Title:
  Ubuntu does not work with Samsung Galaxy phones ( Unable to open raw
  device 0)

Status in GVFS:
  Fix Released
Status in “gmtp” package in Ubuntu:
  Invalid
Status in “gvfs” package in Ubuntu:
  In Progress
Status in “udev” package in Ubuntu:
  Invalid
Status in “gmtp” source package in Precise:
  Invalid
Status in “gvfs” source package in Precise:
  Confirmed
Status in “udev” source package in Precise:
  Invalid
Status in “gmtp” source package in Quantal:
  Invalid
Status in “gvfs” source package in Quantal:
  Confirmed
Status in “udev” source package in Quantal:
  Invalid

Bug description:
  If your device is not supported please open a new bug specifying:
  * device in question (make / model / release)
  * output of `mtp-detect` when the device is attached
  * output of `lsusb` when the device is attached

  This bug will be a catch all for recent Samsung Nexus  Nexus 7, or
  please comment what other recent Andorid 4.x devices are affected.

  Yes there is a lag in providing support for the most recent devices.
  As soon as the fixes are available, SRUs will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/903422/+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 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically

2012-12-05 Thread Domen Kožar
What is the actual bug link_

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

Title:
  NetworkManager does not auto-connect to VPNs marked Connect
  Automatically

Status in NetworkManager:
  Unknown
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “network-manager” package in Debian:
  New

Bug description:
  VPN connections marked Connect Automatically are not activated when
  a wired or wireless network becomes available.

  Fixed upstream in commit:

  commit ece5e209cdc409a21e249dacbdbc953a1db4c6b7
  Author: Jiří Klimeš jkli...@redhat.com
  Date:   Tue Aug 21 17:49:41 2012 +0200

  core: VPN autoconnect feature (bgo #560471) (rh #483120)

  We go through the SECONDARIES state where we check if there are some
  secondary
  (VPN or other) UUIDs that are to be activated before progressing to
  ACTIVATED.
  In case of an error with a secondary UUID or its activation, the base
  connection
  can't activate successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/280571/+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 821745] Re: There is no option to do nothing when power is critically low (11.10).

2012-07-31 Thread Domen Kožar
In GConf: /apps/gnome-power-manager/actions/critical_battery -
nothing

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

Title:
  There is no option to do nothing when power is critically low
  (11.10).

Status in “gnome-power-manager” package in Ubuntu:
  Confirmed

Bug description:
  The only options provided are hibernate and shutdown. Do nothing
  should be allowed, especially for situations where hibernation would
  not work, and also for calibrating the battery (which requires being
  able to have the system do nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/821745/+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 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically

2012-01-01 Thread Domen Kožar
Following script works with NM 0.9, goals:

* if VPN connection is not disconnected by user himself, reconnect 
(configurable max_attempts)
* on new active network connection, activate VPN

https://gist.github.com/1547663

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

Title:
  NetworkManager does not auto-connect to VPNs marked Connect
  Automatically

Status in NetworkManager:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Triaged
Status in Debian GNU/Linux:
  New

Bug description:
  VPN connections marked Connect Automatically are not activated when
  a wired or wireless network becomes available.

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