Re: [Bug 305565] Re: kleopatra complains that gpgme should be compiled with gpgconf support
OK, gotcha. I misunderstood. Thanks. -- Bryan Harris Research Engineer Structures and Materials Evaluation Group harri...@notes.udayton.edu http://www.udri.udayton.edu/ (937) 229-5561 On Wednesday 18 March 2009 16:20:44 you wrote: > No. All it means is that the bug isn't in kdepim. -- kleopatra complains that gpgme should be compiled with gpgconf support https://bugs.launchpad.net/bugs/305565 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
Re: [Bug 305565] Re: kleopatra complains that gpgme should be compiled with gpgconf support
So does this means you aren't going to fix this in Intrepid because the Jaunty package works? -- Bryan Harris Research Engineer Structures and Materials Evaluation Group harri...@notes.udayton.edu http://www.udri.udayton.edu/ (937) 229-5561 On Wednesday 18 March 2009 15:16:13 you wrote: > ** Changed in: kdepim >Status: New => Invalid -- kleopatra complains that gpgme should be compiled with gpgconf support https://bugs.launchpad.net/bugs/305565 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 93360] Workaround
- Partial WORKAROUND -
The error message in question gets generated here:
/etc/dhcp3/dhclient-exit-hooks.d/_dhcdbd
Where we have the following code:
if [ -n "${dhc_dbus}" ]; then
/usr/bin/dbus-send \
--system \
--dest=com.redhat.dhcp \
--type=method_call \
/com/redhat/dhcp/$interface \
com.redhat.dhcp.set \
'string:'"`env | /bin/egrep -v
'^(PATH|SHLVL|_|PWD|dhc_dbus)\='`";
fi;
Now this always gives an error message about a bad path because "
/com/redhat/dhcp/$interface" doesn't exist.
Also this part:
'string:'"`env | /bin/egrep -v '^(PATH|SHLVL|_|PWD|dhc_dbus)\='`"
just spits out all the environment variables. That doesn't sound right. I
think this is supposed to pass information about the interaface to a database
or something, but envirnment variables don't seem right. I would guess that
this is supposed to be passing permanent leases to the dhcdbd.
Anyway I have attached the workaround patch which fixed the Network
Manager interaction for me.
Basically it changes "/com/redhat/dhcp/$interface" to "/"
This stops the error and gets rid of the need to restart my network interface
every time I connect to a network. I still contend it should be doing
something other than passing environment variables, but I don't know enough
about dbus to fix it. Hopefully, this will show the right person where to look.
** Attachment added: "Partial workaround for dhcdbd/Network Manager interaction
problem."
http://launchpadlibrarian.net/15627657/workaround.patch
--
Dhcdbd doesn't recognize permanent (-1) DHCP leases
https://bugs.launchpad.net/bugs/93360
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
Re: [Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
The problem is that the proc filesystem (linux kernel) reports no battery present. What does "cat /proc/acpi/battery/BAT1" from a command line spit out? It should say "present:yes" and then a bunch of other info, assuming you have a battery. On Thu, 2007-12-06 at 03:36 +, Scott Kitterman wrote: > It appears to still be a problem. I reinstalled kde-guidance- > powermanager and booted into the kernel. I never saw a battery status > from it. Let me know when there are new kernels and I'll be glad to > continue to test. > > ** Changed in: linux (Ubuntu) >Status: Incomplete => Confirmed > -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 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 120445] Re: Firestarter firewall continuously crashes no matter which desktop or screen it's on.
G_SLICE=always-malloc gksu /usr/sbin/firestarter This workaround fixes the crashing for me. -- Firestarter firewall continuously crashes no matter which desktop or screen it's on. https://bugs.launchpad.net/bugs/120445 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 120445] Re: Firestarter firewall continuously crashes no matter which desktop or screen it's on.
G_SLICE=always-malloc gksu /usr/sbin/firestarter fixes the problem for me. 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 GNU/Linux Firestarter 1.0.3 -- Firestarter firewall continuously crashes no matter which desktop or screen it's on. https://bugs.launchpad.net/bugs/120445 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 155700] Re: tracker_get_hit_counts: assertion `query->words' failed
I take that back it is indexing. I restarted the tracker daemon with the "trackerd -R" command. I do get this error message, but it seems to be working. -- tracker_get_hit_counts: assertion `query->words' failed https://bugs.launchpad.net/bugs/155700 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 155700] Re: tracker_get_hit_counts: assertion `query->words' failed
I am getting this error and tracker is not getting any hits. I can look at tracker-stats and the program is indexing: (see below) but even if I search for something it should find like "grub" nothing comes up. ---fetching index stats- default : 0 Files : 2235 Folders : 355 Documents : 114 Images : 156 Music : 916 Videos : 40 Text : 270 Development : 146 Other : 238 Emails : 0 EvolutionEmails : 0 ThunderbirdEmails : 0 KMailEmails : 0 EmailAttachments : 0 EvolutionAttachments : 0 KMailAttachments : 0 Conversations : 0 GaimConversations : 0 Applications : 648 -- tracker_get_hit_counts: assertion `query->words' failed https://bugs.launchpad.net/bugs/155700 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 146132] Re: regression: acpi not working since upgrade from feisty to Gutsy
** Tags added: acpi dsdt gutsy regression -- regression: acpi not working since upgrade from feisty to Gutsy https://bugs.launchpad.net/bugs/146132 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 146132] Re: regression: acpi not working since upgrade from feisty to Gutsy
** Also affects: gnome-power Importance: Undecided Status: New ** Also affects: gnome-applets Importance: Undecided Status: New ** Also affects: acpi Importance: Undecided Status: New ** Also affects: acpi-support Importance: Undecided Status: New -- regression: acpi not working since upgrade from feisty to Gutsy https://bugs.launchpad.net/bugs/146132 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 146132] update: compiled vanilla kernel-> acpi works fine
I compiled a vanilla kernel version 2.6.22.9 and acpi works. I used the vanilla sources from kernel.org and the config file from /boot/config-2.6.22-12-generic. There was an error message involving a missing acpi file which I assume is related to a debian/ubuntu patch. this was the symbol the vanilla kernel didn't like from line 18: CONFIG_ACPI_CUSTOM_DSDT_INITRD=y I saw a few rumblings about this when I googled for acpi problems, but they all involved older kernels. What kernel version is the gutsy image based on? It looked in the changelog like they maintain their own patch-set against 2.6.22, but that doesn't seem right... Can someone clear this up for me? I guess I have a workaround of sorts, but I don't know if the vanilla kernel will break any Ubuntu features. I remember in Fedora Core it caused all sorts of problems... It seems fine here. I would love to be able to use the stock kernel. Bryan -- regression: acpi not working since upgrade from feisty to Gutsy https://bugs.launchpad.net/bugs/146132 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 146132] regression: acpi not working since upgrade from feisty to Gutsy
Public bug reported: Binary package hint: acpi I have a Dell Latitude L400. Ever since the install of tribe 5 I have not battery information. The power usage is unavailable and proc reports that my battery is not present. I get the following (incorrect) message from dmesg: ACPI: Battery Slot [BAT1] (battery absent) It also reports that the AC adapter is "online" though it is currently unplugged. ACPI: AC Adapter [ACAD] (on-line) Furthermore, the temperature always shows a constant 50C which is incorrect. This could become a very serious problem because it will allow the computer to overheat under load. All the fans stay off until the temperature reads 65C... All this worked under feisty. full dmesg: [0.00] BIOS-e820: 0fff - 0c00 (ACPI data) [0.00] BIOS-e820: 0c00 - 1000 (ACPI NVS) [0.00] ACPI: RSDP 000F6ED0, 0014 (r0 PTLTD ) [0.00] ACPI: RSDT 0FFFC65F, 002C (r1 DELL ATLAS II 20010314 LTP 0) [0.00] ACPI: FACP 0B65, 0074 (r1 DELL Atlas II 20010314 PTL F4240) [0.00] ACPI: DSDT 0FFFC68B, 34DA (r1PTLBX-TJ 20010314 MSFT 107) [0.00] ACPI: FACS 0FC0, 0040 [0.00] ACPI: BOOT 0BD9, 0027 (r1 PTLTD $SBFTBL$ 20010314 LTP 1) [0.00] ACPI: PM-Timer IO Port: 0x8008 [ 29.267682] ACPI: Core revision 20070126 [ 29.268019] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found. [ 29.273871] ACPI: setting ELCR to 0200 (from 0c00) [ 29.284592] ACPI: bus type pci registered [ 29.299793] ACPI: EC: Look up EC in DSDT [ 29.319205] ACPI: EC: GPE=0x00, ports=0x66, 0x62 [ 29.327426] ACPI: Interpreter enabled [ 29.327487] ACPI: (supports S0 S3 S4 S5) [ 29.327745] ACPI: Using PIC for interrupt routing [ 29.354587] ACPI: Device [FDDA] status [0008]: functional but not present; setting present [ 29.358035] ACPI: Device [CDRM] status [0008]: functional but not present; setting present [ 29.364285] ACPI: EC: GPE=0x00, ports=0x66, 0x62 [ 29.364515] ACPI: PCI Root Bridge [PCI0] (:00) [ 29.365105] PCI quirk: region 8000-803f claimed by PIIX4 ACPI [ 29.365861] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 29.366019] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] [ 29.369583] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 14 15) [ 29.370400] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 14 15) [ 29.371182] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled. [ 29.372053] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 14 15) [ 29.372975] ACPI: Power Resource [PFN0] (off) [ 29.373139] ACPI: Power Resource [PFN1] (off) [ 29.373304] pnp: PnP ACPI init [ 29.373386] ACPI: bus type pnp registered [ 29.406123] pnp: PnP ACPI: found 10 devices [ 29.406188] ACPI: ACPI bus type pnp unregistered [ 29.406250] PnPBIOS: Disabled by ACPI PNP [ 29.406487] PCI: Using ACPI for IRQ routing [ 29.442037] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 [ 29.442108] ACPI: PCI Interrupt :00:0a.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 [ 33.167166] ACPI: Transitioning device [FAN0] to D3 [ 33.167237] ACPI: Transitioning device [FAN0] to D3 [ 33.167298] ACPI: Fan [FAN0] (off) [ 33.167537] ACPI: Transitioning device [FAN1] to D3 [ 33.167595] ACPI: Transitioning device [FAN1] to D3 [ 33.167653] ACPI: Fan [FAN1] (off) [ 33.192165] ACPI: CPU0 (power states: C1[C1] C2[C2]) [ 33.192339] ACPI: Processor [CPU0] (supports 8 throttling states) [ 33.197731] ACPI: Thermal Zone [THRM] (50 C) [ 35.306449] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 [ 35.306522] ACPI: PCI Interrupt :00:07.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 35.444881] ACPI: PCI Interrupt :00:0d.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 [8.292000] Time: acpi_pm clocksource has been installed. [ 35.456000] ACPI: PCI Interrupt :02:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 [ 36.084000] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 [ 36.084000] ACPI: PCI Interrupt :00:08.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 [ 44.488000] ACPI: Battery Slot [BAT1] (battery absent) [ 44.564000] ACPI: Power Button (FF) [PWRF] [ 44.576000] ACPI: Lid Switch [LID] [ 44.584000] ACPI: Sleep Button (CM) [SBTN] [ 45.12] ACPI: AC Adapter [ACAD] (on-line) [ 49.98] apm: overridden by ACPI. full lspci -vvn: 00:00.0 0600: 8086:7190 (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:01.0 0604: 8086:7191 (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
