[Desktop-packages] [Bug 1172313] Re: Displays Connected (none)

2013-11-07 Thread Austin Canfield
Seems to only happen on networks using WPA-Enterprise (e.g. my
university's wi-fi), but it may be an issue unrelated to that. This is
still happening in Ubuntu 13.10.

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

Title:
  Displays Connected (none)

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

Bug description:
  Since upgrading to 13.04 when I connect to my wireless network I see a
  notification that says "Connected (none)" where "(none)" is  there
  instead of the wireless SSID of the network I'm connected to or the
  name of the wireless connection (from edit connections) in the menu.
  It still really is connected and the wireless is working.  If I go to
  the connection information it knows what the names are there, though I
  didn't see the SSID in that information.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Wed Apr 24 07:56:53 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-11-08 (166 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  IpRoute:
   default via 192.168.2.1 dev eth8  proto static 
   169.254.0.0/16 dev eth8  scope link  metric 1000 
   192.168.2.0/24 dev eth8  proto kernel  scope link  src 192.168.2.195  metric 
1 
   192.168.2.0/24 dev wlan1  proto kernel  scope link  src 192.168.2.165  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to raring on 2013-04-19 (5 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyUSB0cdma  disconnected  
/org/freedesktop/NetworkManager/Devices/23 
   wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth8   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172313/+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 937114] Re: gnome-settings-daemon crashed with signal 5 in g_settings_schema_get_value()

2012-05-04 Thread Austin Canfield
The reason it was doing that was because it was loading a schema from
another directory which must have been forgotten about during the upgrade
process. I deleted it and I haven't had a problem since.
On May 4, 2012 12:30 AM, "Robert Ancell" 
wrote:

> Does this still occur?  The stacktrace shows gnome-settings-daemon
> trying to access a "screenshot" key which is not in your schema for some
> reason (/usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins
> .media-keys.gschema.xml).
>
> ** Visibility changed to: Public
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
>   Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/937114
>
> Title:
>  gnome-settings-daemon crashed with signal 5 in
>  g_settings_schema_get_value()
>
> Status in “gnome-settings-daemon” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Gnome-settings-daemon crashes on logon every time and causes certain
>  services to not run.
>
>  ProblemType: Crash
>  DistroRelease: Ubuntu 12.04
>  Package: gnome-settings-daemon 3.3.5-0ubuntu3
>  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
>  Uname: Linux 3.2.0-17-generic x86_64
>  NonfreeKernelModules: nvidia
>  ApportVersion: 1.91-0ubuntu1
>  Architecture: amd64
>  Date: Mon Feb 20 08:50:02 2012
>  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
>  ExecutableTimestamp: 1329408875
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64
> (20110427.1)
>  ProcCmdline: gnome-settings-daemon
>  ProcCwd: /home/austin
>  Signal: 5
>  SourcePackage: gnome-settings-daemon
>  StacktraceTop:
>   g_settings_schema_get_value (schema=0x1e22a40, key=0x7f67743a27f7
> "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:640
>   g_settings_schema_key_init (key=0x7fff8add19d0, schema=0x1e22a40,
> name=0x7f67743a27f7 "screenshot") at
> /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:751
>   g_settings_get_value (settings=0x1f7a4a0, key=0x7f67743a27f7
> "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1059
>   g_settings_get_string (settings=, key=) at
> /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1539
>   ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
>  Title: gnome-settings-daemon crashed with signal 5 in
> g_settings_schema_get_value()
>  UpgradeStatus: Upgraded to precise on 2012-02-09 (11 days ago)
>  UserGroups:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/937114/+subscriptions
>

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

Title:
  gnome-settings-daemon crashed with signal 5 in
  g_settings_schema_get_value()

Status in “gnome-settings-daemon” package in Ubuntu:
  Incomplete

Bug description:
  Gnome-settings-daemon crashes on logon every time and causes certain
  services to not run.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-settings-daemon 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Mon Feb 20 08:50:02 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ExecutableTimestamp: 1329408875
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline: gnome-settings-daemon
  ProcCwd: /home/austin
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_settings_schema_get_value (schema=0x1e22a40, key=0x7f67743a27f7 
"screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:640
   g_settings_schema_key_init (key=0x7fff8add19d0, schema=0x1e22a40, 
name=0x7f67743a27f7 "screenshot") at 
/build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:751
   g_settings_get_value (settings=0x1f7a4a0, key=0x7f67743a27f7 "screenshot") 
at /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1059
   g_settings_get_string (settings=, key=) at 
/build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1539
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
  Title: gnome-settings-daemon crashed with signal 5 in 
g_settings_schema_get_value()
  UpgradeStatus: Upgraded to precise on 2012-02-09 (11 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/937114/+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 873808] Re: brightness applet needs to support nvidia_backlight

2012-03-16 Thread Austin Canfield
I've installed the latest version of gnome-settings-daemon in precise,
and the new gsd-backlight-helper still prefers the malfunctioning sony
backlight driver to the working nvidia_backlight driver. How does it
determine which driver is the best?

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

Title:
  brightness applet needs to support nvidia_backlight

Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released

Bug description:
  There is a popular third-party backlight driver for Nvidia GPUs that
  are not supported by the manufacturers backlight driver, known as
  nvidiabl (or nvidia_backlight). See
  https://github.com/guillaumezin/nvidiabl for more information. This is
  not the same driver as nv_backlight.

  In order for this driver to be recognized by the brightness applet,
  nvidia_backlight needs to be added to the top of the vendor array in
  gsd-backlight-helper so that it looks like this:

/* available kernel interfaces in priority order */
static const gchar *backlight_interfaces[] = {
"nvidia_backlight",
"nv_backlight",
"asus_laptop",
"toshiba",
"eeepc",
"thinkpad_screen",
"acpi_video1",
"mbp_backlight",
"acpi_video0",
"fujitsu-laptop",
"sony",
"samsung",
NULL,
};

  nvidia_backlight needs to be placed at the top of the list because the
  non-functioning vendor module (sony, in my case) is still present in
  /sys/class/backlight, so nvidia_backlight needs to be recognized
  before sony.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/873808/+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 873808] [NEW] brightness applet needs to support nvidia_backlight

2011-10-13 Thread Austin Canfield
Public bug reported:

There is a popular third-party backlight driver for Nvidia GPUs that are
not supported by the manufacturers backlight driver, known as nvidiabl
(or nvidia_backlight). See https://github.com/guillaumezin/nvidiabl for
more information. This is not the same driver as nv_backlight.

In order for this driver to be recognized by the brightness applet,
nvidia_backlight needs to be added to the top of the vendor array in
gsd-backlight-helper so that it looks like this:

/* available kernel interfaces in priority order */
static const gchar *backlight_interfaces[] = {
"nvidia_backlight",
"nv_backlight",
"asus_laptop",
"toshiba",
"eeepc",
"thinkpad_screen",
"acpi_video1",
"mbp_backlight",
"acpi_video0",
"fujitsu-laptop",
"sony",
"samsung",
NULL,
};

nvidia_backlight needs to be placed at the top of the list because the
non-functioning vendor module (sony, in my case) is still present in
/sys/class/backlight, so nvidia_backlight needs to be recognized before
sony.

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

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

Title:
  brightness applet needs to support nvidia_backlight

Status in “gnome-settings-daemon” package in Ubuntu:
  New

Bug description:
  There is a popular third-party backlight driver for Nvidia GPUs that
  are not supported by the manufacturers backlight driver, known as
  nvidiabl (or nvidia_backlight). See
  https://github.com/guillaumezin/nvidiabl for more information. This is
  not the same driver as nv_backlight.

  In order for this driver to be recognized by the brightness applet,
  nvidia_backlight needs to be added to the top of the vendor array in
  gsd-backlight-helper so that it looks like this:

/* available kernel interfaces in priority order */
static const gchar *backlight_interfaces[] = {
"nvidia_backlight",
"nv_backlight",
"asus_laptop",
"toshiba",
"eeepc",
"thinkpad_screen",
"acpi_video1",
"mbp_backlight",
"acpi_video0",
"fujitsu-laptop",
"sony",
"samsung",
NULL,
};

  nvidia_backlight needs to be placed at the top of the list because the
  non-functioning vendor module (sony, in my case) is still present in
  /sys/class/backlight, so nvidia_backlight needs to be recognized
  before sony.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/873808/+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