Re: [Bug 186049] Re: System.DllNotFoundException: libgalago
Only caveat: metainformation for searchresults, which hung beagle-search previously, isn't filled in automatically and metainfo for a searchresult only appears after a click on the searchresult. I think thats a known bug/feature of beagle-search - that the information is only shown after clicking on the search result. -- System.DllNotFoundException: libgalago https://bugs.launchpad.net/bugs/186049 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
[Bug 207157] Re: dbus does not start automatically in Hardy
Here is the startup script in the recent debian dbus-x11 package: /etc/X11/Xsession.d/75dbus_dbus-launch ... (from http://packages.debian.org/sid/i386/dbus-x11/filelist) -- dbus does not start automatically in Hardy https://bugs.launchpad.net/bugs/207157 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
[Bug 207157] Re: dbus does not start automatically in Hardy
I checked with the dbus-x11 package in other distributions. They contain an xinit startup script which starts dbus with X. I couldnt check the contents of the dbus-x11 in hardy, but others are installing dbus-x11 to fix this problem. Of course the relevant apps need to also depend on dbus-x11. -- dbus does not start automatically in Hardy https://bugs.launchpad.net/bugs/207157 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
[Bug 213128] Re: [Hardy] Guidance-power-manager doesn't know when laptop is mains unplugged
Same on inspiron 1100 w/ Hardy. Identical lshal/lshal -m outputs so not attaching anything. I can do some tests if needed. Thanks. -- [Hardy] Guidance-power-manager doesn't know when laptop is mains unplugged https://bugs.launchpad.net/bugs/213128 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
[Bug 239579] Re: Beagle extension designated as incompatible with latest version of firefox 3
We should fix the package. Then use the files for the beagle-firefox package for Intrepid. That is based on beagle-0.3.7 and contains a compatible extension. -- Beagle extension designated as incompatible with latest version of firefox 3 https://bugs.launchpad.net/bugs/239579 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
[Bug 239579] Re: Beagle extension designated as incompatible with latest version of firefox 3
Alexander, Pasting from the email about the nomination of the extension on addons.mozilla.org ... --- Your nominated add-on, Beagle Indexer, has been reviewed by a Mozilla Add-ons editor who decided to retain your add-on in the sandbox. Review Information: Reviewer: Sid Kalra Comments: One of the requirements to go public on addons.mozilla.org is that your add-on must have some reviews either on AMO or elsewhere. See http://shawnwilsher.com/archives/108 for some ideas on how to do that. Once you have those reviews in place, please renominate to go public on AMO.br / br / Thanks. -- -- Beagle extension designated as incompatible with latest version of firefox 3 https://bugs.launchpad.net/bugs/239579 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
[Bug 239579] Re: Beagle extension designated as incompatible with latest version of firefox 3
I am one of the upstream developers. This bug can be closed at it is not related to Ubuntu. * The beagle extension packaged in Ubuntu Hardy is not meant to be used in Firefox-3. * The beagle extension the reporter used was from addons.mozilla.org. * The beagle extension in the Intrepid version works with Firefox-3. Alberto, the extension at addons.mozilla.org will be corrected once Firefox-3 is released. In any case, Mozilla rejected the addons (the reason was there is no public review of the extension). So, it is not best to track that site. Instead you should use the link from http ://beagle-project.org/Browser_Extension -- Beagle extension designated as incompatible with latest version of firefox 3 https://bugs.launchpad.net/bugs/239579 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
[Bug 186049] Re: System.DllNotFoundException: libgalago
I didnt try but based on the above information, this problem will happen if you try to open a chat search result. Thats when libgalago is called. Also take a look at the duplicate bugs for more information. -- System.DllNotFoundException: libgalago https://bugs.launchpad.net/bugs/186049 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
[Bug 239579] Re: Beagle extension designated as incompatible with latest version of firefox 3
Upstream rejected it. The extension included with beagle-0.3.5 and earlier was not fully compatible with firefox-3. beagle-0.3.6 later came out with a compatible extension. If ubuntu didnt change anything in the extensions then the extension would work fine as intended (i.e. pre- beagle-0.3.6 incompatible with firefox-3 and 0.3.6 and later is compatible). ** Bug watch added: GNOME Bug Tracker #538071 http://bugzilla.gnome.org/show_bug.cgi?id=538071 ** Also affects: beagle via http://bugzilla.gnome.org/show_bug.cgi?id=538071 Importance: Unknown Status: Unknown -- Beagle extension designated as incompatible with latest version of firefox 3 https://bugs.launchpad.net/bugs/239579 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
[Bug 238709] Re: Crash beagle-search then search to a Pidgin history
*** This bug is a duplicate of bug 186049 *** https://bugs.launchpad.net/bugs/186049 ** This bug has been marked a duplicate of bug 186049 System.DllNotFoundException: libgalago -- Crash beagle-search then search to a Pidgin history https://bugs.launchpad.net/bugs/238709 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
[Bug 220310] Re: Brightness function keys reversed
Same issue here. Hardy + all available updates. Why is the status of this bug incomplete ? -- Brightness function keys reversed https://bugs.launchpad.net/bugs/220310 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
[Bug 228787] Re: beagle search does not open thundbird any more..
Ah... this will cause a problem. You need to add /home/eric/Mail/Mail to the exclude-directory list in beagle-settings (i.e. tell beagle's filesystem crawler to leave thunderbird's email to thunderbird crawler only). Remove ~/.beagle/Indexes/FileSystemIndex and then start beagled. The re-indexing is necessary because thunderbird email information is stored twice in the index causing the problem. -- beagle search does not open thundbird any more.. https://bugs.launchpad.net/bugs/228787 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
[Bug 228903] Re: beagle crash while trying to open messenger application
*** This bug is a duplicate of bug 186049 *** https://bugs.launchpad.net/bugs/186049 ** This bug has been marked a duplicate of bug 186049 System.DllNotFoundException: libgalago -- beagle crash while trying to open messenger application https://bugs.launchpad.net/bugs/228903 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
[Bug 228787] Re: beagle search does not open thundbird any more..
file:///home/eric/Mail/Mail/eric.sagnard/ct.sbd/Ricci.msf this does not look like thunderbird email !!! Isnt it supposed to be in ~/.thunderbird or something like that ? -- beagle search does not open thundbird any more.. https://bugs.launchpad.net/bugs/228787 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
[Bug 228787] Re: beagle search does not open thundbird any more..
Can you start beagle-search from a terminal, search for some email, try to open the email and then paste here the terminal contents ? -- beagle search does not open thundbird any more.. https://bugs.launchpad.net/bugs/228787 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
[Bug 207157] Re: dbus does not start automatically in Hardy
dbus not starting by default in KDE - isnt this some kind of major bug ? importance is still undecided and no one seems to care about this problem. What is the ubuntu way to at least mark a bug as confirmed ? Can users mark it as confirmed ? -- dbus does not start automatically in Hardy https://bugs.launchpad.net/bugs/207157 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
[Bug 224318] Re: Please merge beagle 0.3.4-1 from debian sid
Debian unstable has 0.3.7-1 (7 more days to enter testing). Maybe grabbing from unstable would be better. -- Please merge beagle 0.3.4-1 from debian sid https://bugs.launchpad.net/bugs/224318 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
[Bug 221073] Re: Beagle does not index Thunderbird mails
Disabling the EvolutionDataServer backend might help. There are similar crash bugs filed against evolution-sharp which beagle uses. -- Beagle does not index Thunderbird mails https://bugs.launchpad.net/bugs/221073 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
[Bug 186049] Re: System.DllNotFoundException: libgalago
Moving the bug to galago-sharp since thats where the bug actually is. ** Changed in: galago-sharp (Ubuntu) Sourcepackagename: beagle = galago-sharp -- System.DllNotFoundException: libgalago https://bugs.launchpad.net/bugs/186049 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
[Bug 207157] Re: dbus does not start automatically in Hardy
As mentioned in the comments of LP #62163, you might have to install dbus-x11 and restart kdm. -- dbus does not start automatically in Hardy https://bugs.launchpad.net/bugs/207157 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
[Bug 207157] Re: dbus does not start automatically in Hardy
Possibly some missing package or incorrect dependency; as a result of which whatever is starting dbus for you is not exporting the required environment variable DBUS_SESSION_BUS_ADDRESS (this variable is not required by only beagle; it is must available feature of dbus) -- dbus does not start automatically in Hardy https://bugs.launchpad.net/bugs/207157 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
[Bug 207157] Re: dbus does not start automatically in Hardy
Ok - I changed the subject of the bug to reflect the true reason; this should get the required attention. I still believe its some bug in your system; this is too major a bug to go unnoticed. ** Summary changed: - beagle dbus integration broken for battery detection + dbus does not start automatically in Hardy ** Description changed: + (read below: the original problem is caused by dbus not running) + Binary package hint: beagle It appears that something is inconsistent with dbus and beagle. Beagle is using dbus to detect the battery status but it cannot. I get the following log messages when starting beagle. I am using Hardy Beta with packages updated to the latest as of 26 March 2008, morning, CST6CDT. Description:Ubuntu hardy (development branch) Release:8.04 20080326 09:26:54.0089 13200 Beagle INFO: Starting Beagle Daemon (version 0.3.3) 20080326 09:26:54.6157 13200 Beagle INFO: Running on Mono 1.2.6 20080326 09:26:54.6162 13200 Beagle INFO: Command Line: /usr/lib/beagle/BeagleDaemon.exe --replace --bg 20080326 09:26:54.6610 13200 Beagle WARN: Extended attributes are not supported on this filesystem. Performance will suffer as a result. 20080326 09:27:17.1678 13200 Beagle ERROR EX: Failed to access dbus session bus. Battery monitoring will be disabled. 20080326 09:27:17.1678 13200 Beagle ERROR EX: System.Exception: Unable to open the session message bus. --- System.ArgumentNullException: Argument cannot be null. 20080326 09:27:17.1678 13200 Beagle ERROR EX: Parameter name: address 20080326 09:27:17.1678 13200 Beagle ERROR EX: at NDesk.DBus.Bus.Open (System.String address) [0x0] 20080326 09:27:17.1678 13200 Beagle ERROR EX: at NDesk.DBus.Bus.get_Session () [0x0] --- End of inner exception stack trace --- 20080326 09:27:17.1678 13200 Beagle ERROR EX: 20080326 09:27:17.1678 13200 Beagle ERROR EX: at NDesk.DBus.Bus.get_Session () [0x0] 20080326 09:27:17.1678 13200 Beagle ERROR EX: at NDesk.DBus.BusG.Init () [0x0] 20080326 09:27:17.1678 13200 Beagle ERROR EX: at Beagle.Daemon.BatteryMonitor.Init () [0x0] -- dbus does not start automatically in Hardy https://bugs.launchpad.net/bugs/207157 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
[Bug 213477] Re: crash when previewing an IM conversation in search results (missing DLL libgalago)
*** This bug is a duplicate of bug 186049 *** https://bugs.launchpad.net/bugs/186049 ** This bug has been marked a duplicate of bug 186049 System.DllNotFoundException: libgalago -- crash when previewing an IM conversation in search results (missing DLL libgalago) https://bugs.launchpad.net/bugs/213477 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
[Bug 207157] Re: beagle dbus integration broken for battery detection
Shouldnt this be filed with X for this to get fixed ? -- beagle dbus integration broken for battery detection https://bugs.launchpad.net/bugs/207157 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
[Bug 207157] Re: beagle dbus integration broken for battery detection
Do you have DBUS_SESSION_BUS_ADDRESS set ? and dbus running ? -- beagle dbus integration broken for battery detection https://bugs.launchpad.net/bugs/207157 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
[Bug 207157] Re: beagle dbus integration broken for battery detection
Well ... dbus session bus address has to be set for any application to contact dbus. Could be a hardy error. BTW, if you log in via ssh, then dbus session is not set and you have to set it manually. -- beagle dbus integration broken for battery detection https://bugs.launchpad.net/bugs/207157 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
[Bug 207157] Re: beagle dbus integration broken for battery detection
Then its a kdm bug. dbus-launch (or dbus-daemon --session, IIRC) is supposed to export that environment variable. KDE does not use a lot of dbus otherwise you would have noticed it somewhere else too. -- beagle dbus integration broken for battery detection https://bugs.launchpad.net/bugs/207157 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
[Bug 202871] Re: BeagleDaemon.exe crashed with SIGSEGV in mono_class_from_typeref()
See if this helps: https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608 -- BeagleDaemon.exe crashed with SIGSEGV in mono_class_from_typeref() https://bugs.launchpad.net/bugs/202871 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
[Bug 194608] Re: beagled dependency not met
Depends on #193715 -- beagled dependency not met https://bugs.launchpad.net/bugs/194608 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
[Bug 193715] Re: Merge beagle 0.3.3-2 from Debian(Unstable)
This is due to the new gnome in which gconf-sharp dropped its dependency on glib. Fix is given here and is in upstream too http://bugzilla.gnome.org/show_bug.cgi?id=514252 -- Merge beagle 0.3.3-2 from Debian(Unstable) https://bugs.launchpad.net/bugs/193715 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
[Bug 200132] Re: beagle search daemon doesn't work
*** This bug is a duplicate of bug 194608 *** https://bugs.launchpad.net/bugs/194608 ** This bug has been marked a duplicate of bug 194608 beagled dependency not met -- beagle search daemon doesn't work https://bugs.launchpad.net/bugs/200132 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
[Bug 193715] Re: Merge beagle 0.3.3-2 from Debian(Unstable)
Any progress on this one ? -- Merge beagle 0.3.3-2 from Debian(Unstable) https://bugs.launchpad.net/bugs/193715 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
[Bug 84699] Re: crash for other application (beagled-helper....)
Simone, you are facing https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608 A lot of people are complaining about this, ubuntu should fix their build asap. -- crash for other application (beagled-helper) https://bugs.launchpad.net/bugs/84699 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
[Bug 186049] Re: System.DllNotFoundException: libgalago
About the taglib-sharp, it was reported in https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608 Debian-0.3.3-2 might have fixed it, not sure. -- System.DllNotFoundException: libgalago https://bugs.launchpad.net/bugs/186049 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
[Bug 179023] Re: beagle dosn't index 7zip file
** Bug watch added: GNOME Bug Tracker #386028 http://bugzilla.gnome.org/show_bug.cgi?id=386028 ** Also affects: beagle via http://bugzilla.gnome.org/show_bug.cgi?id=386028 Importance: Unknown Status: Unknown -- beagle dosn't index 7zip file https://bugs.launchpad.net/bugs/179023 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153051] Re: sqlite version mismatch causes problems in Evolution backend
The problem is fixed in the hardy version. -- sqlite version mismatch causes problems in Evolution backend https://bugs.launchpad.net/bugs/153051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 69752] Re: beagled-helper and beagle run away with CPU and memory
Osmo, the mozilla-thunderbird errors were due to a faulty Thunderbird backend which was actually disable upstream but strangely enabled in ubuntu. That and the other errors were fixed in 0.3.0 which was released a month ago. The ICSharpCode.SharpZipLib.Zip.ZipException is not fatal, it just indicated a failure in indexing of a certain file, probably due to a corrupt archive. -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user -- beagled-helper and beagle run away with CPU and memory https://bugs.launchpad.net/bugs/69752 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177473] Re: New upstream release (0.3.1)
0.3.1 has entered debian! Aren't there automatic ways to make ubuntu packages from debian packages ? -- New upstream release (0.3.1) https://bugs.launchpad.net/bugs/177473 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139558] Re: [gutsy] Email subject not displayed in beagle-search and kerry
This really depends on https://bugs.launchpad.net/ubuntu/+source/gmime2.2/+bug/157127 How do you add dependson bug number in launchpad ? -- [gutsy] Email subject not displayed in beagle-search and kerry https://bugs.launchpad.net/bugs/139558 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157127] Re: libgmime2-cil should depend on libgmime2
** Summary changed: - Missing package dependency prevents indexing beagle to index kmail + libgmime2-cil should depend on libgmime2 ** Description changed: In this thread https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/139558 we found at that when installing beagle on a kubuntu system, kmail is not indexed properely. Only libgmime2-cil is installed as dependency when installing - kerry but not libgmime2. + kerry but not libgmime2. Since libgmime2-cil is the C# bindings for + libgmime2, the binding absolutely requires libgmime2 to function. -- libgmime2-cil should depend on libgmime2 https://bugs.launchpad.net/bugs/157127 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69752] Re: beagled-helper and beagle run away with CPU and memory
Panagiotis, just in case if beagled is still running or if you happen to find this again, could you send the output of $ beagle-index-info $ beagle-status $ ls -l ~/.beagle/Log/ In two terminals, do $ tail -f ~/.beagle/Log/current-Beagle $ tail -f ~/.beagle/Log/current-IndexHelper (it will keep printing the debug messages, press ctrl-c to stop) Then from another terminal, $ kill -USR2 `pidof beagled` (if pidof program is not installed, find the pid of beagled and use it) This command will print something in the current-Beagle and current-IndexHelper log files. Paste the outputs of both. Thanks. Chris, this bug _is_ getting attention. Read the previous responses from Joe - there has been several different causes for the same problem; many are fixed and for the rest, we need some diagnostic feedback to trace where the problem is. You should realize that these problems are not easy to reproduce. -- beagled-helper and beagle run away with CPU and memory https://bugs.launchpad.net/bugs/69752 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117892] Re: i810/intel xorg drivers hang Inspiron 1100
Well, it is well eshtablished now that the current intel driver in xorg does not work with 1100 and other 845 based video cards. There are discussions about this in xorg mailing list and other distro bugzilla (e.g. Mandriva). Apparently the LVDS driver isnt implemented. As expected the Gutsy live cd does not work. -- i810/intel xorg drivers hang Inspiron 1100 https://bugs.launchpad.net/bugs/117892 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69752] Re: beagled-helper and beagle run away with CPU and memory
Jared, Thunderbird Indexing is disabled in the beagle-0.2.18 release due to memory and CPU usage problems. Looks like it is enabled on your computer; maybe the ubuntu packager enables it. I suggest turning it off by doing this as user from the command line $ beagle-config daemon DenyBackend Thunderbird -- beagled-helper and beagle run away with CPU and memory https://bugs.launchpad.net/bugs/69752 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139558] Re: [gutsy] Email subject not displayed in beagle-search and kerry
Shouldn't libgmime2.2-cil depend on libgmime2 ? Can you take this up with libgmime2-cil people ... if there is a dependency problem that should be resolved urgently. There are other programs that depend on libgmime2-cil. -- [gutsy] Email subject not displayed in beagle-search and kerry https://bugs.launchpad.net/bugs/139558 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156753] Re: beagle-search crashes with GLib.GException: Couldn't recognize the image file format
*** This bug is a duplicate of bug 93064 *** https://bugs.launchpad.net/bugs/93064 ** This bug has been marked a duplicate of bug 93064 beagle-search crashes when selecting a gaim conversation -- beagle-search crashes with GLib.GException: Couldn't recognize the image file format https://bugs.launchpad.net/bugs/156753 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139558] Re: [gutsy] Email subject not displayed in beagle-search and kerry
Aha ... you have a non-english language. There was a known issue with languages using , as a decimal separator - there is a ubuntu update waiting to be approved to fix this, Then there is a separate issue (beagle-search isnt affected by the locale problem but kerry is). Somehow your email dont seem to have some crucial information ... possibly our email filter is having some problems. Can you attach any kmail email file ? e.g. file:///home/schmidt/.kde/share/apps/kmail/dimap/.1725759156.directory/.Finanzen.directory/Bestellungen/cur/1191823656.13884.z1XX2:2,S file:///home/schmidt/.kde/share/apps/kmail/dimap/.1725759156.directory/Spamverdacht/cur/1190008426.8665.Vm9xj:2,S (or any file appearing as Uri:file:///home/schmidt/.kde/share/apps/kmail/dimap/.1725759156.directory/... in the above attached log file - any one file will do). -- [gutsy] Email subject not displayed in beagle-search and kerry https://bugs.launchpad.net/bugs/139558 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 139558] Re: [gutsy] Email subject not displayed in beagle-search and kerry
** Attachment added: 1190008426.8665.Vm9xj:2,S http://launchpadlibrarian.net/10155871/1190008426.8665.Vm9xj%3A2%2CS I works correctly on my machine :( EMails are extracted using gmime-sharp (gmime-cil depending on how it is packaged) which depends on gmime. So, there could be some problem there. One more check, can you send me the output of $ beagle-extract-content --mimetype=message/rfc822 /path/to/1190008426.8665.Vm9xj:2,S -- [gutsy] Email subject not displayed in beagle-search and kerry https://bugs.launchpad.net/bugs/139558 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139558] Re: [gutsy] Email subject not displayed in beagle-search and kerry
Can you attach the output of $ beagle-query --verbose amazon The output will be quite large, so redirect it to a file and attach the file. Just cross check that the same query is giving no subject/no sender in beagle-search. -- [gutsy] Email subject not displayed in beagle-search and kerry https://bugs.launchpad.net/bugs/139558 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 149979] Re: libbeagle should be compiled with python support
it wasn't, after a sudo apt-get install python-beagle it workes fine. Is there a simple way to tell the user about that or could it be added to the prerequisites of deskbar-applet, as a normal user expects this to work. IMO, python-beagle _should_ be added as a prerequisite to deskbar. -- libbeagle should be compiled with python support https://bugs.launchpad.net/bugs/149979 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149979] Re: libbeagle should be compiled with python support
Is the python-beagle package installed ? It is needed. -- libbeagle should be compiled with python support https://bugs.launchpad.net/bugs/149979 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117892] Re: i810/intel xorg drivers hang Inspiron 1100
I am also an (unfortunate) 1100 user. I was trying out the gutsy rc1 live cd and noticed how it failed to detect my video card and monitor and started using vesa. Furthermore, once I logged out, it refused to return me to the login screen. :( Anyway, brianglass/raveenys, the IgnoreEDID trick works with vesa or also with i810 (or intel) ? Ubuntu live cd is not easy to tweak but I still want to try. -- i810/intel xorg drivers hang Inspiron 1100 https://bugs.launchpad.net/bugs/117892 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128804] Re: beagled crashes
I checked and found 0.2.18 (the upstream package) was uploaded for Gutsy. -- beagled crashes https://bugs.launchpad.net/bugs/128804 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126142] Re: beagled-helper uses 100% CPU
if you are using 0.2.14+, then you can send $kill -SIGUSR2 `pidof beagled-helper` which will print the name of the file beagled-helper is stuck at in the log file ~/.beagle/Log/current-IndexHelper (from http://beagle-project.org/Troubleshooting_CPU) -- beagled-helper uses 100% CPU https://bugs.launchpad.net/bugs/126142 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104871] Re: beagled-helper needs 100% CPU after some idle time
if you are using 0.2.14+, then you can send $kill -SIGUSR2 `pidof beagled-helper` which will print the name of the file beagled-helper is stuck at in the log file ~/.beagle/Log/current-IndexHelper (from http://beagle-project.org/Troubleshooting_CPU) -- beagled-helper needs 100% CPU after some idle time https://bugs.launchpad.net/bugs/104871 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139547] Re: Index all Maildir folders
The bug with xdgmime might be hard to fix. It is really hard to detect correct rfc822 files with all the different headers MUAs put it. Still its a good idea to let them know. If there are hidden directories, then even with the bug fixed, it will not improve current situation. Someone has to write a generic maildir backend, which will go into those directories and index those files. Possibly a stripped out version of the kmail backend. -- Index all Maildir folders https://bugs.launchpad.net/bugs/139547 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139547] Re: Index all Maildir folders
This has been implemented upstream. Check here for details: http://mail.gnome.org/archives/dashboard-hackers/2007-September/msg00012.html -- Index all Maildir folders https://bugs.launchpad.net/bugs/139547 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139314] Re: Archive indexing is needed.
beagle can index zip files since a long time. Possibly you are using a rather old version. -- Archive indexing is needed. https://bugs.launchpad.net/bugs/139314 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133377] Re: SIGSEGV in beagle-search
So its more a gtk-sharp/mono/PPC bug. I think they should be notified. Can someone change the product so that the mono guys can see this and work on this ? -- SIGSEGV in beagle-search https://bugs.launchpad.net/bugs/133377 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133377] Re: SIGSEGV in beagle-search
This has something to do with the recent mono. These are similar problems in monodevelop and banshee. http://lists.ximian.com/pipermail/monodevelop-list/2007-August/006512.html http://www.mail-archive.com/debian-bugs-rc%40lists.debian.org/msg109852.html -- SIGSEGV in beagle-search https://bugs.launchpad.net/bugs/133377 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115260] Re: beagled exceptions reported in log file
I am told that without gmcs, the performance will be slow(er). I have no actual experience though. -- beagled exceptions reported in log file https://bugs.launchpad.net/bugs/115260 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115682] Re: beagle seems to interfer with other applications
This was fixed upstream either in 0.2.16.3 or if not, 0.2.17 -- beagle seems to interfer with other applications https://bugs.launchpad.net/bugs/115682 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115370] Re: beagle don't allow to add additional paths for indexing
** Bug watch added: GNOME Bug Tracker #393456 http://bugzilla.gnome.org/show_bug.cgi?id=393456 ** Also affects: beagle (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=393456 Importance: Unknown Status: Unknown -- beagle don't allow to add additional paths for indexing https://bugs.launchpad.net/bugs/115370 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115003] Re: [apport] BeagleDaemon.exe crashed with SIGSEGV in _Unwind_Backtrace()
I checked that page. Konqueror crashes as it is on that page. The stacktrace shows somefault in libpcre0. This is a konqueror bug, nothing to do with beagle. Beagle does not crash for me with this page. I suspect if beagle crashed in the original report, it must have been a coincidence. There are separate bugs opened about random beagle crashes and this could be one of them. But definitely nothing to do with konqueror. -- [apport] BeagleDaemon.exe crashed with SIGSEGV in _Unwind_Backtrace() https://bugs.launchpad.net/bugs/115003 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115289] Re: smarter beagle configuration for excluding items
This is upstream commit http://svn.gnome.org/viewcvs/beagle?rev=3736view=rev Beagle ignores a lot of patterns, but *.db was not among them, I added it it. http://svn.gnome.org/viewcvs/beagle?rev=3747view=rev -- smarter beagle configuration for excluding items https://bugs.launchpad.net/bugs/115289 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115260] Re: beagled exceptions reported in log file
Beagle (and other xml-serializer + asp.net based apps) requires gmcs to run. I asked Joe (maintainer of Beagle) about this, and he says that beagle package should depend on whatever package gmcs is. -- beagled exceptions reported in log file https://bugs.launchpad.net/bugs/115260 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89487] Re: beagle-build-index uses 100% of cpu when started from cron.daily
the strange thing is that it seems that the index builder removes files and readds them into the index Beagle is supposed to check if a file is already indexed, if not it prints the -file:/// and +file:/// and proceeds to add the file to the index. The actual file is indexed between these two lines, the -file:/// last printed will tell you which file is being currently indexed. So, (1) by observing the output during 100% cpu can you find out which document is taking up all the CPU. Possibly is a bug in some beagle file parser. (2) Do you think beagle is re-adding some files that it indexed before and the file was not changed in between ? Some bug could have been introduced here lately. Can you output two consequtive runs of beagle-build-index to some log file and attach it here/send it to me ? -- beagle-build-index uses 100% of cpu when started from cron.daily https://bugs.launchpad.net/bugs/89487 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89487] Re: beagle-build-index uses 100% of cpu when started from cron.daily
Actually, I would rather see the documentation one. The application is working ok. The reason you see files being repeated is, build-index does not have any filter (parser) for screensaver desktop files, so when the indexer gets such a file it says Error: Could not filter file: No desktop entry and moves on to the next file. On the next run, beagle retries to index this file (since you might have installed a new filter for screensaver desktop files in the meantime) and again fails. This goes on in every run. The index doesn't change - the crawler anyway has to crawl all files, so nobody loses. And its also fast. The documentation one might reveal if some document is taking long time to index or being actually re-parsed over and over again. -- beagle-build-index uses 100% of cpu when started from cron.daily https://bugs.launchpad.net/bugs/89487 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89487] Re: beagle-build-index uses 100% of cpu when started from cron.daily
Yeah, the ionice is supposed to lower the io priority. Actually, if you check the first two lines of the log, you will see Debug: Set best effort IO priority to lowest level (7) Debug: Reniced process to 19 - which means beagle is already trying to play fare. Could you attach one of the recrawled xml files ? I could possibly get any of them from the web, but just wanted to make sure I have the exact same one that you have. I will try to reproduce this here. -- beagle-build-index uses 100% of cpu when started from cron.daily https://bugs.launchpad.net/bugs/89487 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89487] Re: beagle-build-index uses 100% of cpu when started from cron.daily
I figured out the problem. The docbook parser is failing to parse those files, thus those files are getting filtered again on re-indexing. It really cannot be avoided, since users can always install updated filters before re-running build-index. The bad thing is that the docbook filter decides success or failure only at the end of the parsing the whole file. Someone needs to look at the docbook filter, but other than that everything else is working ok. -- beagle-build-index uses 100% of cpu when started from cron.daily https://bugs.launchpad.net/bugs/89487 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115289] Re: smarter beagle configuration for excluding items
exe, dll, .o etc binary files are already ignored. Are you seeing them appearing in the log file ? The last suggestion in already in place upstream. -- smarter beagle configuration for excluding items https://bugs.launchpad.net/bugs/115289 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91974] Re: Beagle continues to index data while laptop is on battery power
Rodrigo, if you are still seeing the problem can you attach the log files (from ~/.beagle/Log/). -- Beagle continues to index data while laptop is on battery power https://bugs.launchpad.net/bugs/91974 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103295] Re: beagle doesn't look for liferea feed in ~/.liferea_1.2 folder
Ok. Can someone re-open the upstream bug please ? Thanks. -- beagle doesn't look for liferea feed in ~/.liferea_1.2 folder https://bugs.launchpad.net/bugs/103295 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103295] Re: beagle doesn't look for liferea feed in ~/.liferea_1.2 folder
Someone above said Have you tried removing the .liferea directory? After running Liferea 1.2 it says you should do that. ... Though, after running liferea again, it gave me a .liferea symlink to .liferea_1.2. - can anyone else confirm if this is the case ? If liferea indeed creates the symlink, then liferea is properly taking care of its data location. Beagle would work w/out any change. -- beagle doesn't look for liferea feed in ~/.liferea_1.2 folder https://bugs.launchpad.net/bugs/103295 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111124] Re: beagle throws exceptions, fills hard drive with logs
Beagle filling the hard disk is an unfortunate side effect of the main bug which is basically a duplicate of 108957. Fix for 108957 has been released upstream in 0.2.17 -- beagle throws exceptions, fills hard drive with logs https://bugs.launchpad.net/bugs/24 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108957] Re: Beagle doesn't handle coma in mail folder name
Upstream release 0.2.17 fixes the problem. -- Beagle doesn't handle coma in mail folder name https://bugs.launchpad.net/bugs/108957 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 106513] Re: Beagle search keeps telling me Your data is being indexed
Mabye I'm just impatient. After a wait (what I consider a long wait) it does go away, so maby things are working as intented and it just takes a long time to index my files? But I just booted and now have the message. This is the output of the command you requested: ~$ beagle-info --status Scheduler: Count: 256 Status: Waiting for next task at 04/20/2007 10:24:55 Pending Tasks: 1 Delayed 0 (04/20/2007 10:24:52) File Crawler 2 Delayed 0 (04/20/2007 10:24:53) Tree Crawler Pending directories: 315 When you boot up, beagle has to crawl your directories to find out if old files need to re-indexed and new files need to be indexed. To keep the effect at minimum, this operation happens very slowly. As shown above, right after you boot up, there are at least these two tasks pending (among others) - one is the file crawler (which finds file in some directory) and other the directory crawler (which current has 315 directories to crawl - as they are indexed, their subdirectories will be added to the directorycrawler). The message will go away after both the crawls are over. The optimizeindex tasks are one-time, short jobs. You can ignore them. There could possibly a bug if the message stays there but beagle-info --status shows no tree crawl or file crawl tasks. Can you wait for sometime and then check the scenario and report back ? Thanks. -- Beagle search keeps telling me Your data is being indexed https://bugs.launchpad.net/bugs/106513 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104647] Re: beagle stuck in indexing loop
Is the error always for those files/directory or it changes ? Also, can you attach the log files of beagled and index-helper ? -- beagle stuck in indexing loop https://bugs.launchpad.net/bugs/104647 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104647] Re: beagle stuck in indexing loop
Which version of beagle are you using ? -- beagle stuck in indexing loop https://bugs.launchpad.net/bugs/104647 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106513] Re: Beagle search keeps telling me Your data is being indexed
If the problem is still there, could you attach the output of (while beagle is running and the notification is being shown) $ beagle-info --status -- Beagle search keeps telling me Your data is being indexed https://bugs.launchpad.net/bugs/106513 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71383] Re: Beagle crash on startup
Philip, could you do the following ? (it will be very helpful). 1) Put this in your .gdbinit in your home directory ---8- define mono_backtrace select-frame 0 set $i = 0 while ($i $arg0) set $foo = mono_pmip ($pc) if ($foo == 0x00) frame else printf #%d %p in %s\n, $i, $pc, $foo end up-silently set $i = $i + 1 end end --8-- 2) start beagled from the terminal as beagled --fg --indexing-delay 300 then from another terminal, 3) find out the pid of beagle, $ ps ux | grep beagled 4) start gdb $ gdb --pid=pid of beagled 5) once gdb starts, enter at the gdb prompt handle SIGXCPU SIG33 SIG35 SIGPWR nostop noprint 6) Enter at the gdb prompt c or continue 7) when beagled crashes, enter this at gdb prompt mono_backtrace 10 8) Copy the output of mono_backtrace to a file and attach it. 9) At gdb prompt, type q or quit 10) If it asks to detach, say yes. 11) Kill beagled if it is still running Its a long process but not tedious :-). You can almost reliably reproduce the crash, so I am seeking your help. Thanks. -- Beagle crash on startup https://bugs.launchpad.net/bugs/71383 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89487] Re: beagle-build-index hangs and must be killed
I have had the same problem here, but I cannot reproduce it. I stopped beagle-build-index using 'killall beagle-build-index', and the logs confirm that it stopped normally. But anyway, it was eating all CPU, apparently building a new index because I have recently upgraded to Feisty. I attach the two logs hoping this can help, but if you find a way to Unfortunately beagle-build-index is different that beagled (you attached the logs for beagled). beagled works in your home directory and other directories containing your personal files and data. beagle-build-index works on system/common files only. To reproduce this, find who is starting beagle-build-index (its one of the crop scripts probably). Look at the full command line (ps auxw) to see the full command line parameters. Then kill b-b-i and give the same command from a terminal (you might need to sudo with the correct user). Observe the terminal, you will know which file was causing the CPU drain. -- beagle-build-index hangs and must be killed https://launchpad.net/bugs/89487 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89487] Re: beagle-build-index hangs and must be killed
I dont think I can remove the attachment, I dont have the permission. Kerry (the KDE client) has the notification system. No mechanism to pause it though. Adding a ready made index is a good idea. Any feisty dev listening ??? -- beagle-build-index hangs and must be killed https://launchpad.net/bugs/89487 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92662] Re: [apport] BeagleDaemon.exe crashed with SIGSEGV
Its a .exe because thats the naming convention used for .Net binaries. It should not be confused with a win32 executable :-). What's in a name ?! -- [apport] BeagleDaemon.exe crashed with SIGSEGV https://launchpad.net/bugs/92662 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90921] Re: [apport] IndexHelper.exe crashed with SIGSEGV
Yes you are right. These information is pretty much useless for mono apps. If you will, see if you can reproduce the crash by starting beagled from a terminal (give --fg --mono-debug as an argument, it will generate verbose output stacktrace). If beagled crashes, it will leave a stacktrace which will be useful. Copy the stacktrace and the last 10-15 lines from the verbose output and attach it to the bug. Thanks. -- [apport] IndexHelper.exe crashed with SIGSEGV https://launchpad.net/bugs/90921 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90152] Re: Beagle loses file index on restart
No it isnt normal. However, it could be that beagled in just wrapping up before exiting. You can try the following. $ tail -f ~/.beagle/Log/current-Beagle This will keep printing whatever the log messages. Do a beagle-shutdown, see what messages show up in the log. If beagle is in the middle of a costly operation, sometimes it has to wait for it to finish before quitting. But those operations are very rare and dont last for too long. -- Beagle loses file index on restart https://launchpad.net/bugs/90152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90152] Re: Beagle loses file index on restart
Upstream is faster in exiting when SIGTERM is sent. If it persists, I would be curious to know how long it is taking to exit after the signal is sent ? In general, if beagle is in the middle of indexing a huge file, it will finish that file and then exit. -- Beagle loses file index on restart https://launchpad.net/bugs/90152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90426] Re: [apport] BuildIndex.exe crashed with SIGSEGV
Can you run open a terminal and give this command: beagle-build-index --debug /usr/lib/beagle/BuildIndex.exe --target /tmp/beagledocindex --disable-directories --recursive --allow-pattern *.xml,*.html,*.docbook /usr/share/doc /usr/local/share/doc /opt/kde3/share/doc /opt/gnome/share/gnome/help /usr/share/gnome/help /opt/gnome/share/gtk-doc/html /usr/share/gtk-doc/html /usr/share/gnome/html If it crashes then there will be some stacktrace on the terminal. Please copy it to a file and attach it to a bug. -- [apport] BuildIndex.exe crashed with SIGSEGV https://launchpad.net/bugs/90426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89506] Re: Beagle crashes when creating folder on GNOME desktop
Enigma, you seem to be having the problem on a regular basis. With a little effort, you may be able to provide valuable input in identifying the problem. After you login, in a terminal give, $ beagled --replace --fg This will start beagle in the terminal and print all kind of lines saying what it is doing. You can ignore them. Then create a new folder or file which you think might trigger the crash. We expect the terminal at that point to have some informative output like a stacktrace of some lines saying Exception. If you see them, please copy those lines (maybe 20 more lines before that to preserve the context) and attach it to the bug. Another user had some success by stopping the evolution-mail backend. You can give this command from a terminal, $ beagle-config daemon DenyBackend EvolutionMail restart beagle (using beagled --restart or logout/login) and see if it crashes. Thanks. -- Beagle crashes when creating folder on GNOME desktop https://launchpad.net/bugs/89506 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90152] Re: Beagle loses file index on restart
kill -9 (kill -SIGKILL) should never be sent to any program which is not hanged. Ever tried sending SIGKILL to any filesystem or kernel process ? You should use SIGTERM or SIGINT. kill -9 can not be handled by the process and so beagle exits with an inconsistent state. Even if the issue in the gnome bug is fixed, there is a high chance that after kill-9, your existing index will have to purged and everything re- indexed. On a different note, why do you have to restart beagle ? Note that, besides SIGINT and SIGTERM beagle ships with the command beagle-shutdown to stop beagle. -- Beagle loses file index on restart https://launchpad.net/bugs/90152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89768] Re: mono-jit crashed
apport crashdump is not very useful for mono apps like beagle. Mono stacktrace is the one that is needed. Please follow the instructions at http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login to help us get a mono stacktrace. -- mono-jit crashed https://launchpad.net/bugs/89768 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88715] Re: beagled crash on startup
MKersloot, when you say catching the errors does not reveal any useful information. It only shows there are recurrences in my calendar - I presume you are doing the 2~/.beagle/crash thing as mentioned in the wiki. I am still interested in the contents of that file because it should not contain the recurrence information but crash information. I check log files of some users - from the nature of the crash the crash does not seem to be related to any internal working of beagle. But please send them too, at least the most recent set of current-Beagle and current-IndexHelper. Anyway, if you have some tracing information from beagled --fg, that is awesome. Please email them to me personally at [EMAIL PROTECTED] Thanks a ton. -- beagled crash on startup https://launchpad.net/bugs/88715 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89688] Re: [apport] mono crashed with SIGSEGV
apport crashdump is not very useful for mono apps like beagle. Mono stacktrace is the one that is needed. Please follow the instructions at http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login to help us get a mono stacktrace. -- [apport] mono crashed with SIGSEGV https://launchpad.net/bugs/89688 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88370] Re: [apport] mono crashed with SIGSEGV
The crash might be a random one. If you want, there are some instructions at http://beagle- project.org/Troubleshooting#Beagle_crashes_on_login on how to get the mono stacktrace when beagle crashes. We'll appreciate if you follow the steps and help us obtain a mono stacktrace. -- [apport] mono crashed with SIGSEGV https://launchpad.net/bugs/88370 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89911] Re: [apport] beagled crashed with SIGSEGV
Do you have the package mono-mcs installed ? This package is necessary for beagle. If not, can you install this and let us know if it crashes even then. -- [apport] beagled crashed with SIGSEGV https://launchpad.net/bugs/89911 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71383] Re: Beagle crash on startup
To figure out what is crashing beagle we need the mono stracktrace. Please see this http://beagle- project.org/Troubleshooting#Beagle_crashes_on_login -- Beagle crash on startup https://launchpad.net/bugs/71383 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69136] Re: beagle crashed right after reboot
This does not seem to be due to anything in beagle. For more information, you need to attach the mono stacktrace. Please see this http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login -- beagle crashed right after reboot https://launchpad.net/bugs/69136 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88925] Re: Mono crashed on start-up
The crash could be a random one. From other's reports, it does not seem to be any problem inside beagle. To figure out what is crashing beagle we need the mono stracktrace when it crashed. Please see this http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login -- Mono crashed on start-up https://launchpad.net/bugs/88925 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88591] Re: [apport] beagled crashed with SIGSEGV
To figure out what is crashing beagle we need the mono stracktrace. Please see this http://beagle- project.org/Troubleshooting#Beagle_crashes_on_login -- [apport] beagled crashed with SIGSEGV https://launchpad.net/bugs/88591 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88715] Re: beagled crash on startup
Or, you can follow the instructions given in http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login to collect the mono stacktrace. The mono stacktrace is necessary in finding out what is causing the crash. -- beagled crash on startup https://launchpad.net/bugs/88715 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87825] Re: [apport] BuildIndex.exe crashed with SIGSEGV
Unfortunately the apport crash dump is not very useful. Please run the command from a terminal. When buildindex crashes, it will leave the mono stacktrace on the terminal which is useful. $ beagle-build-index --debug /usr/lib/beagle/BuildIndex.exe --target /tmp/beagle-index-documentation --disable-directories --recursive --allow-pattern *.xml,*.html,*.docbook /usr/share/doc /usr/local/share/doc /opt/kde3/share/doc /opt/gnome/share/gnome/help /usr/share/gnome/help /opt/gnome/share/gtk-doc/html /usr/share/gtk- doc/html /usr/share/gnome/html -- [apport] BuildIndex.exe crashed with SIGSEGV https://launchpad.net/bugs/87825 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
