** Description changed:

  Binary package hint: kdesudo
  
  When running kdesudo or kdesudo dbus-launch dolphin or another app that
  uses file protocol, the following message is received: "The process for
  the file protocol died unexpectedly" and the relevant folder shows no
  contents.  Gksudo dbus-launch seems to work OK after any previous
  kdesudo attempts have "timed-out".
  
  I have also posted about this at the Kubuntu forums
  (http://kubuntuforums.net/forums/index.php?topic=3109260.0) where some
  have confirmed the issue and others not. It seems to be inconsistent.
  
  Regards,
  
  Steve
  
  ProblemType: Bug
  Architecture: i386
  Date: Tue Jan 12 10:57:33 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: kdesudo 3.4.2.2-0ubuntu1
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
  SourcePackage: kdesudo
  Uname: Linux 2.6.31-18-generic i686
  XsessionErrors:
-  (polkit-gnome-authentication-agent-1:2207): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
-  (<unknown>:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion 
`GDK_IS_WINDOW (window)' failed
-  (<unknown>:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion 
`GDK_IS_WINDOW (window)' failed
+  (polkit-gnome-authentication-agent-1:2207): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
+  (<unknown>:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion 
`GDK_IS_WINDOW (window)' failed
+  (<unknown>:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion 
`GDK_IS_WINDOW (window)' failed

-- 
kdesudo - process for the file protocol died unexpectedly
https://bugs.launchpad.net/bugs/506361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to