mono April 2013

mono@lists.fedoraproject.org

5 discussions

[Bug 927964] New: Issue with some running apps not having the option to PIN to dock
by Red Hat Bugzilla 05 Feb '14

05 Feb '14

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=927964 Bug ID: 927964 Summary: Issue with some running apps not having the option to PIN to dock Product: Fedora Version: 18 Component: docky Severity: medium Priority: unspecified Assignee: lzap(a)redhat.com Reporter: naipaul_ojar(a)hotmail.com QA Contact: extras-qa(a)fedoraproject.org CC: lzap(a)redhat.com, mono(a)lists.fedoraproject.org +++ This bug was initially created as a clone of Bug #927950 +++ Description of problem: I have two issues with docky - this one [unable to pin a specific app] and another [unable to launch caja]. It has taken some time to ber sufficiently annoyed to raise these issues. I have a company developed Java application that I am not able to "PIN" to dock. It appears as a running application in docky which can be manipulated but not pinned. The app has a .desktop launcher and it appears in my menu system and I have place it in my favourites, but I would dearly like to have in docky. Version-Release number of selected component (if applicable): docky-2.1.4-1.fc18.x86_64 How reproducible: The running app, has right click properties, but pin is not available. Steps to Reproduce: 1. Start app from menu or favourites or Gnome search 2. The running app appears in Docky as an active application 3. Right click the app in the dock and it has properties 4. PIN is not an available option Actual results: Docky is not able to automatically add application Expected results: To be able to PIN the application in docky Additional info: As a work-around, I have found that I can create a desktop launcher short-cut which I can then drag onto docky and dock it that way. I was not able to do it that way from the Gnome favourites. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=jQk6x4uSNx&a=cc_unsubscribe

1 3

[Bug 909443] New: Docky crashes regularly - Once per hour.
by Red Hat Bugzilla 13 Dec '13

13 Dec '13

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=909443 Bug ID: 909443 Summary: Docky crashes regularly - Once per hour. Product: Fedora Version: 18 Component: docky Severity: unspecified Priority: unspecified Reporter: naipaul_ojar(a)hotmail.com Description of problem: Docky is running then it dissapears. Normally I can re-execute and it will remain for another period of time. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start docky or from login, docky dock is seen 2. docky dissapears 3. restart docky - if successful wait 4. if docky does not start from menu, start from command line and list the errors listed Actual results: Docky crashes because mono-core has core dumped Expected results: When using Fedora 16, This problem did not occur ========== docky [Info 19:24:47.283] Docky version: 2.1.4 Release [Info 19:24:47.302] Kernel version: 3.7.5.201 [Info 19:24:47.302] CLR version: 4.0.30319.1 Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for Docky.Services.DockServices ---> GLib.GException: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. at GConf.Client.GetConnections (System.String dir) [0x00000] in <filename unknown>:0 at GConf.Client.AddNotify (System.String dir, GConf.NotifyEventHandler notify) [0x00000] in <filename unknown>:0 at Docky.Services.Prefs.Preferences..ctor (System.String owner) [0x00000] in <filename unknown>:0 at Docky.Services.PreferencesService.Get (System.String basePath) [0x00000] in <filename unknown>:0 at Docky.Services.SystemService..ctor () [0x00000] in <filename unknown>:0 at Docky.Services.DockServices..cctor () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Docky.UserArgs.Parse (System.String[] args) [0x00000] in <filename unknown>:0 at Docky.Docky.Main (System.String[] args) [0x00000] in <filename unknown>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for Docky.Services.DockServices ---> GLib.GException: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. at GConf.Client.GetConnections (System.String dir) [0x00000] in <filename unknown>:0 at GConf.Client.AddNotify (System.String dir, GConf.NotifyEventHandler notify) [0x00000] in <filename unknown>:0 at Docky.Services.Prefs.Preferences..ctor (System.String owner) [0x00000] in <filename unknown>:0 at Docky.Services.PreferencesService.Get (System.String basePath) [0x00000] in <filename unknown>:0 at Docky.Services.SystemService..ctor () [0x00000] in <filename unknown>:0 at Docky.Services.DockServices..cctor () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Docky.UserArgs.Parse (System.String[] args) [0x00000] in <filename unknown>:0 at Docky.Docky.Main (System.String[] args) [0x00000] in <filename unknown>:0 ========== Additional info: [root@naipaulpc log]# grep mono-core -A 2 -B 4 /var/log/messages Feb 5 22:00:44 naipaulpc yum[6495]: Installed: perl-XML-SAX-0.99-5.fc18.noarch Feb 5 22:00:46 naipaulpc yum[6495]: Installed: 1:perl-XML-LibXML-2.0004-1.fc18.x86_64 Feb 5 22:00:47 naipaulpc yum[6495]: Installed: libgnomeui-2.24.5-5.fc18.x86_64 Feb 5 22:00:47 naipaulpc yum[6495]: Installed: libgdiplus-2.10-6.fc18.x86_64 Feb 5 22:00:50 naipaulpc yum[6495]: Installed: mono-core-2.10.8-3.fc18.x86_64 Feb 5 22:00:51 naipaulpc yum[6495]: Installed: gtk-sharp2-2.12.11-6.fc18.x86_64 Feb 5 22:00:52 naipaulpc yum[6495]: Installed: 1:dbus-sharp-0.7.0-6.fc18.x86_64 -- Feb 6 01:59:30 naipaulpc dbus-daemon[943]: dbus[943]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 6 01:59:30 naipaulpc dbus[943]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 6 01:59:40 naipaulpc abrtd: Directory 'ccpp-2013-02-06-01:59:39-15904' creation detected Feb 6 01:59:40 naipaulpc abrt[23467]: Saved core dump of pid 15904 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-06-01:59:39-15904 (132415488 bytes) Feb 6 01:59:40 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 6 01:59:40 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-06-01:59:39-15904' exited with 1 Feb 6 01:59:40 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-06-01:59:39-15904', deleting -- Feb 6 02:32:44 naipaulpc dbus-daemon[943]: dbus[943]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 6 02:32:44 naipaulpc dbus[943]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 6 02:32:45 naipaulpc abrtd: Directory 'ccpp-2013-02-06-02:32:44-7378' creation detected Feb 6 02:32:45 naipaulpc abrt[4616]: Saved core dump of pid 7378 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-06-02:32:44-7378 (139608064 bytes) Feb 6 02:32:45 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 6 02:32:45 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-06-02:32:44-7378' exited with 1 Feb 6 02:32:45 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-06-02:32:44-7378', deleting -- Feb 6 17:14:42 naipaulpc yum[7969]: Installed: systemd-ui-1-3.fc18.x86_64 Feb 6 17:14:44 naipaulpc abrtd: Directory 'ccpp-2013-02-06-17:14:43-2964' creation detected Feb 6 17:14:44 naipaulpc abrt[8822]: Saved core dump of pid 2964 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-06-17:14:43-2964 (139022336 bytes) Feb 6 17:14:44 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 8822 Feb 6 17:14:44 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 6 17:14:44 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-06-17:14:43-2964' exited with 1 Feb 6 17:14:44 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-06-17:14:43-2964', deleting -- Feb 7 01:31:23 naipaulpc dbus[979]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 7 01:31:25 naipaulpc abrtd: Directory 'ccpp-2013-02-07-01:31:23-2994' creation detected Feb 7 01:31:25 naipaulpc abrt[14686]: Saved core dump of pid 2994 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-07-01:31:23-2994 (162004992 bytes) Feb 7 01:31:25 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 14686 Feb 7 01:31:25 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 7 01:31:25 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-07-01:31:23-2994' exited with 1 Feb 7 01:31:25 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-07-01:31:23-2994', deleting -- Feb 7 01:40:40 naipaulpc systemd-tmpfiles[2558]: stat(/run/user/1000/gvfs) failed: Permission denied Feb 7 01:40:40 naipaulpc systemd[1]: Started Cleanup of Temporary Directories. Feb 7 01:41:27 naipaulpc abrtd: Directory 'ccpp-2013-02-07-01:41:26-18760' creation detected Feb 7 01:41:27 naipaulpc abrt[5486]: Saved core dump of pid 18760 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-07-01:41:26-18760 (165949440 bytes) Feb 7 01:41:27 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 7 01:41:27 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-07-01:41:26-18760' exited with 1 Feb 7 01:41:27 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-07-01:41:26-18760', deleting -- Feb 7 01:46:23 naipaulpc udisksd[1776]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD20EADS_11R6B1_WD_WCAVY1643772: Error updating SMART data: sk_disk_check_sleep_mode: Operation not supported (udisks-error-quark, 0) Feb 7 01:48:00 naipaulpc abrtd: Directory 'ccpp-2013-02-07-01:47:59-9456' creation detected Feb 7 01:48:00 naipaulpc abrt[20652]: Saved core dump of pid 9456 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-07-01:47:59-9456 (165937152 bytes) Feb 7 01:48:00 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 20652 Feb 7 01:48:00 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 7 01:48:00 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-07-01:47:59-9456' exited with 1 Feb 7 01:48:00 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-07-01:47:59-9456', deleting -- Feb 7 20:55:27 naipaulpc abrtd: Directory 'ccpp-2013-02-07-20:55:26-3002' creation detected Feb 7 20:55:27 naipaulpc abrt[29294]: Saved core dump of pid 3002 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-07-20:55:26-3002 (145371136 bytes) Feb 7 20:55:27 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 29294 Feb 7 20:55:28 naipaulpc yum[28624]: Installed: 1:gnome-games-gnobots2-3.6.1-1.fc18.x86_64 Feb 7 20:55:28 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 7 20:55:28 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-07-20:55:26-3002' exited with 1 Feb 7 20:55:28 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-07-20:55:26-3002', deleting -- Feb 8 09:37:38 naipaulpc dbus[973]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 8 09:37:57 naipaulpc abrtd: Directory 'ccpp-2013-02-08-09:37:56-3052' creation detected Feb 8 09:37:57 naipaulpc abrt[7406]: Saved core dump of pid 3052 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-08-09:37:56-3052 (150851584 bytes) Feb 8 09:37:57 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 7406 Feb 8 09:37:57 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 8 09:37:57 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-08-09:37:56-3052' exited with 1 Feb 8 09:37:57 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-08-09:37:56-3052', deleting -- Feb 8 13:08:20 naipaulpc yum[29036]: Updated: 1:telepathy-mission-control-5.14.0-2.fc18.x86_64 Feb 8 13:08:21 naipaulpc abrtd: Directory 'ccpp-2013-02-08-13:08:20-3059' creation detected Feb 8 13:08:21 naipaulpc abrt[2452]: Saved core dump of pid 3059 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-08-13:08:20-3059 (149311488 bytes) Feb 8 13:08:21 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 2452 Feb 8 13:08:22 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 8 13:08:22 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-08-13:08:20-3059' exited with 1 Feb 8 13:08:22 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-08-13:08:20-3059', deleting -- Feb 8 14:13:09 naipaulpc yum[29036]: Installed: colord-libs-0.1.28-1.fc18.i686 Feb 8 14:13:09 naipaulpc yum[29036]: Updated: libuuid-2.22.2-3.fc18.i686 Feb 8 14:13:26 naipaulpc abrtd: Directory 'ccpp-2013-02-08-14:13:24-24690' creation detected Feb 8 14:13:26 naipaulpc abrt[23686]: Saved core dump of pid 24690 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-08-14:13:24-24690 (132550656 bytes) Feb 8 14:13:26 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 8 14:13:26 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-08-14:13:24-24690' exited with 1 Feb 8 14:13:26 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-08-14:13:24-24690', deleting -- Feb 8 18:06:49 naipaulpc abrtd: Directory 'ccpp-2013-02-08-18:06:47-18944' creation detected Feb 8 18:06:49 naipaulpc abrt[11366]: Saved core dump of pid 18944 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-08-18:06:47-18944 (172322816 bytes) Feb 8 18:06:49 naipaulpc abrtd: Lock file '/var/spool/abrt/ccpp-2013-02-06-00:13:05-1735/.lock' is locked by process 11366 Feb 8 18:06:49 naipaulpc yum[10495]: Installed: xfce4-panel-4.10.0-2.fc18.x86_64 Feb 8 18:06:49 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 8 18:06:49 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-08-18:06:47-18944' exited with 1 Feb 8 18:06:49 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-08-18:06:47-18944', deleting -- Feb 8 19:22:38 naipaulpc abrtd: Directory 'ccpp-2013-02-08-19:22:36-5969' creation detected Feb 8 19:22:38 naipaulpc abrt[19259]: Saved core dump of pid 5969 (/usr/bin/mono) to /var/spool/abrt/ccpp-2013-02-08-19:22:36-5969 (142741504 bytes) Feb 8 19:22:38 naipaulpc dbus-daemon[969]: dbus[969]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Feb 8 19:22:38 naipaulpc dbus[969]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Feb 8 19:22:38 naipaulpc abrtd: Blacklisted package 'mono-core' Feb 8 19:22:38 naipaulpc abrtd: 'post-create' on '/var/spool/abrt/ccpp-2013-02-08-19:22:36-5969' exited with 1 Feb 8 19:22:38 naipaulpc abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2013-02-08-19:22:36-5969', deleting -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=TbMP1tRdwT&a=cc_unsubscribe

1 7

[Bug 927950] New: Issue with starting some docked apps
by Red Hat Bugzilla 13 Dec '13

13 Dec '13

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=927950 Bug ID: 927950 Summary: Issue with starting some docked apps Product: Fedora Version: 18 Component: docky Severity: medium Priority: unspecified Assignee: lzap(a)redhat.com Reporter: naipaul_ojar(a)hotmail.com QA Contact: extras-qa(a)fedoraproject.org CC: lzap(a)redhat.com, mono(a)lists.fedoraproject.org Description of problem: I have two issues with docky - this one [unable to launch caja] and another [unable to pin a specific app]. It has taken some time to ber sufficiently annoyed to raise these issues. I have two file Managers pinned to docky, Nautilus and Caja. Only Nautilus launches from Docky properly. Caja seems to be launched, but fails to complete the launch. I am able to maximise and minimise once launched. New window also does not work. I am able to launch the caja.desktop via the menu and from Gnome Favourites and I am able to remove and re-pin to docky. Version-Release number of selected component (if applicable): docky-2.1.4-1.fc18.x86_64 How reproducible: Initial launch failure is very repeatable - I have many other apps launching correctly - its just caja that is giving grief ... I even created a desktop launcher app on the Gnome Desktop, which works when I double-click on it, yet it will not work from docky. Steps to Reproduce: 1. Start caja from menu or favourites or Gnome search and then pin to docky 2. Close caja application - indication that caja instance is active should be also gone 3. Invoke caja app, icon bounces from dock twice but no application is launched 4. Invoke caja app from Gnome Favourites and caja is launched 5. From docky, caja can be minimised, maximised and closed Actual results: Docky does not start application. Expected results: To be able to start the application defined in the launcher definition. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=vZ4ieECgAO&a=cc_unsubscribe

1 3

[Bug 814274] New: dependency not automatically installed when you yum install docky
by Red Hat Bugzilla 01 Aug '13

01 Aug '13

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: dependency not automatically installed when you yum install docky https://bugzilla.redhat.com/show_bug.cgi?id=814274 Summary: dependency not automatically installed when you yum install docky Product: Fedora Version: 16 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: docky AssignedTo: lzap(a)redhat.com ReportedBy: che666(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: lzap(a)redhat.com, mono(a)lists.fedoraproject.org Classification: Fedora Story Points: --- Type: Bug Regression: --- Mount Type: --- Documentation: --- Description of problem: after yum install docky and starting it some operations seem to miss a dependency: [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for Docky.ConfigurationWindow ---> System.DllNotFoundException: libgnome-desktop-2.so.17 Version-Release number of selected component (if applicable): docky-2.0.12-1 on x86_64 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 846177] New: [abrt] docky-2.0.12-3.fc17: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "PurpleConversationGetData" with signature "is" on interface "im.pidgin.purple.PurpleInterface" doesn't exist
by Red Hat Bugzilla 31 Jul '13

31 Jul '13

https://bugzilla.redhat.com/show_bug.cgi?id=846177 Bug ID: 846177 QA Contact: extras-qa(a)fedoraproject.org Severity: unspecified Whiteboard: abrt_hash:5f33d1a74914194afe3125407b4adfd8380e0d3f Version: 17 Priority: unspecified CC: lzap(a)redhat.com, mono(a)lists.fedoraproject.org Assignee: lzap(a)redhat.com Summary: [abrt] docky-2.0.12-3.fc17: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "PurpleConversationGetData" with signature "is" on interface "im.pidgin.purple.PurpleInterface" doesn't exist Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: xaero(a)xaerolimit.net Type: --- Documentation: --- Hardware: x86_64 Mount Type: --- Status: NEW Component: docky Product: Fedora libreport version: 2.0.10 abrt_version: 2.0.10 cmdline: python /usr/share/docky/helpers/pidgin_control.py event_log: 2012-08-06-23:37:21> Smolt profile successfully saved executable: /usr/share/docky/helpers/pidgin_control.py kernel: 3.5.0-2.fc17.x86_64 time: Mon 06 Aug 2012 11:30:03 PM EDT uid: 1000 username: chris backtrace: :connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "PurpleConversationGetData" with signature "is" on interface "im.pidgin.purple.PurpleInterface" doesn't exist : : :Traceback (most recent call last): : File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 586, in msg_reply_handler : reply_handler(*message.get_args_list(**get_args_opts)) : File "/usr/share/docky/helpers/pidgin_control.py", line 87, in list_names_handler : self.update_badge() : File "/usr/share/docky/helpers/pidgin_control.py", line 141, in update_badge : count = count + self.pidgin.iface.PurpleConversationGetData(conv, "unseen-count") : File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__ : **keywords) : File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking : message, timeout) :DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "PurpleConversationGetData" with signature "is" on interface "im.pidgin.purple.PurpleInterface" doesn't exist : : :Local variables in innermost frame: :byte_arrays: False :self: <dbus._dbus.SessionBus (session) at 0x7fb8ca57ae30> :args: (dbus.Int32(692900), 'unseen-count') :utf8_strings: False :bus_name: dbus.UTF8String(':1.100') :get_args_opts: {'byte_arrays': False, 'utf8_strings': False} :object_path: '/im/pidgin/purple/PurpleObject' :timeout: -1.0 :signature: None :dbus_interface: 'im.pidgin.purple.PurpleInterface' :message: <dbus.lowlevel.MethodCallMessage object at 0x7fb8d10cec00> :method: 'PurpleConversationGetData' smolt_data: : : :General :================================= :UUID: 7797ae6e-eec7-4816-bbcf-db717f9fa61b :OS: Fedora release 17 (Beefy Miracle) :Default run level: Unknown :Language: en_US.UTF-8 :Platform: x86_64 :BogoMIPS: 4389.84 :CPU Vendor: GenuineIntel :CPU Model: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz :CPU Stepping: 7 :CPU Family: 6 :CPU Model Num: 42 :Number of CPUs: 4 :CPU Speed: 2200 :System Memory: 7765 :System Swap: 9823 :Vendor: ASUSTeK Computer Inc. :System: K53E 1.0 :Form factor: Notebook :Kernel: 3.5.0-2.fc17.x86_64 :SELinux Enabled: 0 :SELinux Policy: targeted :SELinux Enforce: Unknown :MythTV Remote: Unknown :MythTV Role: Unknown :MythTV Theme: Unknown :MythTV Plugin: :MythTV Tuner: -1 : : :Devices :================================= :(32902:7241:4163:4423) pci, None, PCI/ISA, HM65 Express Chipset Family LPC Controller :(6505:4227:4163:6225) pci, atl1c, ETHERNET, AR8151 v2.0 Gigabit Ethernet :(32902:278:4163:5714) pci, i915, VIDEO, 2nd Generation Core Processor Family Integrated Graphics Controller :(32902:7190:4163:4423) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 4 :(32902:7184:4163:4423) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 1 :(32902:7186:4163:4423) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 2 :(32902:7200:4163:6979) pci, snd_hda_intel, MULTIMEDIA, 6 Series/C200 Series Chipset Family High Definition Audio Controller :(32902:7202:4163:4423) pci, None, SERIAL, 6 Series/C200 Series Chipset Family SMBus Controller :(6945:4162:4163:4185) pci, xhci_hcd, USB, ASM1042 SuperSpeed USB Host Controller :(5772:43:6715:4233) pci, ath9k, NETWORK, AR9285 Wireless Network Adapter (PCI-Express) :(32902:7171:4163:4423) pci, ahci, STORAGE, 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller :(32902:7213:4163:4423) pci, ehci_hcd, USB, 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 :(32902:7206:4163:4423) pci, ehci_hcd, USB, 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 :(32902:260:4163:4423) pci, agpgart-intel, HOST/PCI, 2nd Generation Core Processor Family DRAM Controller :(32902:7226:4163:4423) pci, mei, SIMPLE, 6 Series/C200 Series Chipset Family MEI Controller #1 :(32902:7194:4163:4423) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 6 : : :Filesystem Information :================================= :device mtpt type bsize frsize blocks bfree bavail file ffree favail :------------------------------------------------------------------- :/dev/mapper/vg_silverdragon-lv_root / xfs 4096 4096 13100800 8200310 8200310 52428800 51841640 51841640 :/dev/sda1 /boot ext4 1024 1024 508644 399000 373400 128016 127665 127665 :/dev/mapper/vg_silverdragon-lv_home /home xfs 4096 4096 140456952 109736046 109736046 562102272 561909767 561909767 : -- You are receiving this mail because: You are on the CC list for the bug.

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mono April 2013