[Bug 1926393] [NEW] xdg-mime silently ignores invalid .desktop file
Public bug reported: I created an invalid ~/.local/share/applications/mailto.desktop file (note the quotes in Exec): #!/usr/bin/env xdg-open [Desktop Entry] Version=1.0 Type=Application Terminal=false Name[en_AU]=mailto Exec="mailto %f" Name=mailto I then set the default, and queried it: $ xdg-mime default mailto.desktop 'x-scheme-handler/mailto' $ echo $? 0 $ xdg-mime query default 'x-scheme-handler/mailto' thunderbird.desktop $ echo $? 0 As you can see, no error codes are returned, but the system default application is returned. If I fix the mailto.desktop file by removing the quotes, the query performs as expected: $ xdg-mime query default 'x-scheme-handler/mailto' mailto.desktop Running in verbose mode doesn't give any further information, i.e., that the .desktop file was passed over in search because it was invalid: $ # bad $ XDG_UTILS_DEBUG_LEVEL= xdg-mime query default 'x-scheme-handler/mailto' --verbose Checking /home/duncan/.config/mimeapps.list Checking /home/duncan/.local/share/applications/mimeapps.list Checking /home/duncan/.local/share/applications/defaults.list and /home/duncan/.local/share/applications/mimeinfo.cache Checking /home/duncan/.local/share/applications/defaults.list and /home/duncan/.local/share/applications/mimeinfo.cache Checking /usr/share/stumpwm/applications/defaults.list and /usr/share/stumpwm/applications/mimeinfo.cache Checking /usr/share/stumpwm/applications/defaults.list and /usr/share/stumpwm/applications/mimeinfo.cache Checking /usr/local/share//applications/defaults.list and /usr/local/share//applications/mimeinfo.cache Checking /usr/local/share//applications/defaults.list and /usr/local/share//applications/mimeinfo.cache Checking /usr/share//applications/defaults.list and /usr/share//applications/mimeinfo.cache thunderbird.desktop $ # good $ XDG_UTILS_DEBUG_LEVEL= xdg-mime query default 'x-scheme-handler/mailto' --verbose Checking /home/duncan/.config/mimeapps.list mailto.desktop ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xdg-utils 1.1.3-2ubuntu1.20.10.2 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 28 12:39:08 2021 InstallationDate: Installed on 2020-11-03 (175 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926393 Title: xdg-mime silently ignores invalid .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1926393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925713] [NEW] Can't connect to an SSH server using a GPG auth key on a Yubikey
Public bug reported: I have a Raspberry Pi server, which I connect to using a GPG auth key that lives on my Yubikey. For example, from console: ➜ ~ ssh pi@nas.local Linux nas.local 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. Last login: Fri Apr 23 01:38:54 2021 from 192.168.1.128 pi@nas:~ $ Before the login proceeds, I'm prompted to unlock the Yubikey, and then I touch the Yubikey to permit gpg-agent to use the key. This is all as expected. However, when I try to connect to the same server from Nemo, I am not prompted either to unlock or touch the Yubikey. Instead I immediately receive the error "Permission denied". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nemo 4.6.5-1 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 23 12:03:41 2021 ExecutablePath: /usr/bin/nemo InstallationDate: Installed on 2020-11-03 (170 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-50-generic linux-base SourcePackage: nemo UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nemo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Screenshot of the dialog and error message." https://bugs.launchpad.net/bugs/1925713/+attachment/5491179/+files/nemo.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925713 Title: Can't connect to an SSH server using a GPG auth key on a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1925713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 450093] Re: whiptail failing in a MultiTerm buffer in Emacs
This bug can be closed. I've verified that whiptail now runs with a $TERM type of eterm-colour. Not sure when in the past 12 years it was fixed though :) :) :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/450093 Title: whiptail failing in a MultiTerm buffer in Emacs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/450093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"
The same problem effects me; Ubuntu 17.04 on Lenovo ThinkPad X220. Previous versions of Ubuntu, other distros, and FreeBSD have worked fine w/ this printer. I've attached the --debug log from system-config-printer as requested. ** Attachment added: "output from system-config-printer --debug" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+attachment/4923356/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707193 Title: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"
Sorry, forgot to mention that my printer is a Fuji Xerox CM115W. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707193 Title: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431179] Re: usb_modeswitch@.service fails
I wonder if this is related? https://bugs.launchpad.net/linuxmint/+bug/1444717 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431179 Title: usb_modeswitch@.service fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notifyOSD ignores the expire timeout parameter
I was developing a script based on inotify that would use very short- lived onscreen notifications. Turns out I can't, at least not with notify-send; I spent some time trying to debug my script before thinking it might be a bug elsewhere. This needs fixing either by: - making osd-notify honour the setting, or - removing it from notify-send, or - clearly documenting the issue in notify-send --help grump :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/390508 Title: notifyOSD ignores the expire timeout parameter To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notifyOSD ignores the expire timeout parameter
I love this thread. It is the bug that keeps on giving, year after year, each time someone spends a few hours in frustration and then stumbles across this bug. Frustrations turns to disbelief and then finally to resignation. +1 ... that describes my recent experience. This sort of heavy-handed decision - not trusting developers to use the API appropriately - belongs on Apple systems, not Free systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/390508 Title: notifyOSD ignores the expire timeout parameter To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 628651] [NEW] [Realtek ALC269] ALSA test tone not correctly played back on headphones; internal speakers okay
Public bug reported: I have upgraded ALSA using the script here: http://ubuntuforums.org/showthread.php?p=6589810 ... but I still hear no sound from headphones when plugged in. The internal speakers work fine however. I am running Ubuntu 10.04 Netbook Remix on an Asus Eee PC R101. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on Jul 6 2010 for kernel 2.6.32-24-generic (SMP). AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: duncan 1539 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 29' Mixer name : 'Realtek ALC269' Components : 'HDA:10ec0269,10438442,0014' Controls : 7 Simple ctrls : 4 Date: Thu Sep 2 16:43:50 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_AU.utf8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [Realtek ALC269] ALSA test tone not correctly played back dmi.bios.date: 04/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd04/30/2010:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid ubuntu-une -- [Realtek ALC269] ALSA test tone not correctly played back on headphones; internal speakers okay https://bugs.launchpad.net/bugs/628651 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 628651] Re: [Realtek ALC269] ALSA test tone not correctly played back on headphones; internal speakers okay
** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536811/+files/AlsaDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536812/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536813/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536814/+files/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536815/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536816/+files/Dependencies.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536817/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/628651/+attachment/1536818/+files/ProcCpuinfo.txt -- [Realtek ALC269] ALSA test tone not correctly played back on headphones; internal speakers okay https://bugs.launchpad.net/bugs/628651 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 430349] Re: gnome-volume-manager exits
I can confirm that this is still a problem on an updated Ubuntu 9.04 box, but that it appears fixed in 9.10. -- gnome-volume-manager exits https://bugs.launchpad.net/bugs/430349 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 450093] [NEW] Root password prompt failing
Public bug reported: I am running on Ubuntu karmic (development branch) release 9.10. If I run sudo apt-get install mysql-server-5.1 from within a MultiTerm buffer in Emacs, I am not prompted for the root password. Instead I see the following error: Unknown terminal: eterm-color Check the TERM environment variable. Also make sure that the terminal is defined in the terminfo database. Alternatively, set the TERMCAP environment variable to the desired termcap entry. debconf: whiptail output the above errors, giving up! dpkg: error processing /var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 255 Errors were encountered while processing: /var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) When I run the same command from a GNOME Terminal session, I am prompted for the root password and MySQL installs correctly. I don't know that it's reasonable for apt-get to support being run from within MultiTerm, but the error message is only helpful to users with an understanding of what the termcap library is why it might be failing. Perhaps apt-get could raise a warning if it's being run on an unsupported terminal type? ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New -- Root password prompt failing https://bugs.launchpad.net/bugs/450093 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 429765] Re: Evolution segfaults when saving recurring appointment from week view
Ooh, symbols :-) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb61f9770 (LWP 5480)] 0xb5be8506 in comp_util_sanitize_recurrence_master (comp=0xa7efda0, client=0xa5aa7c0) at comp-util.c:823 823 comp-util.c: No such file or directory. in comp-util.c (gdb) backtrace #0 0xb5be8506 in comp_util_sanitize_recurrence_master (comp=0xa7efda0, client=0xa5aa7c0) at comp-util.c:823 #1 0xb5c7de6a in save_comp (editor=0xa6ea000) at comp-editor.c:804 #2 0xb5c7e10e in save_comp_with_send (editor=0xa6ea000) at comp-editor.c:913 #3 0xb5c80cba in action_save_cb (action=0xa6b40b0, editor=0xa6ea000) at comp-editor.c:1186 #4 0xb6bf83a4 in IA__g_cclosure_marshal_VOID__VOID (closure=0xa3e9510, return_value=0x0, n_param_values=1, param_values=0xa7b6900, invocation_hint=0xbfdcd9ec, marshal_data=0xb5c80b80) at /build/buildd/glib2.0-2.20.1/gobject/gmarshal.c:77 #5 0xb6beac7b in IA__g_closure_invoke (closure=0xa3e9510, return_value=0x0, n_param_values=1, param_values=0xa7b6900, invocation_hint=0xbfdcd9ec) at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #6 0xb6c00e57 in signal_emit_unlocked_R (node=0xa35ff48, detail=0, instance=0xa6b40b0, emission_return=0x0, instance_and_params=0xa7b6900) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:3247 #7 0xb6c024b9 in IA__g_signal_emit_valist (instance=0xa6b40b0, signal_id=609, detail=0, var_args=0xbfdcdb8c ôof·�...@k\n\b]5\n¸ÃܿeÃ\021·°@k\n\200=Ã\t¸3Ã\têÃ\021·ôoF·) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #8 0xb6c02936 in IA__g_signal_emit (instance=0xa6b40b0, signal_id=609, detail=0) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #9 0xb711b305 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #10 0xb711d365 in gtk_action_activate () from /usr/lib/libgtk-x11-2.0.so.0 #11 0xb72c4ece in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #12 0xb6bf83a4 in IA__g_cclosure_marshal_VOID__VOID (closure=0xa355000, return_value=0x0, n_param_values=1, param_values=0xa7b6a38, invocation_hint=0xbfdcdd5c, marshal_data=0xa4d1000) at /build/buildd/glib2.0-2.20.1/gobject/gmarshal.c:77 #13 0xb6beac7b in IA__g_closure_invoke (closure=0xa355000, return_value=0x0, n_param_values=1, param_values=0xa7b6a38, invocation_hint=0xbfdcdd5c) at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #14 0xb6c00e57 in signal_emit_unlocked_R (node=0x9ed3760, detail=0, instance=0xa355d08, emission_return=0x0, instance_and_params=0xa7b6a38) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:3247 #15 0xb6c024b9 in IA__g_signal_emit_valist (instance=0xa355d08, signal_id=104, detail=0, var_args=0xbfdcdefc üÃöôÃö\b]5\n\030Ãܿøq\023·\b]5\n°q\023·8Ãܿ¤\203¿¶\b]5\n¸3Ã\t=¤¿¶ôÃö\220i{\nh;Ã\thÃܿÃ\223¾¶h;Ã\t) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #16 0xb6c02936 in IA__g_signal_emit (instance=0xa355d08, signal_id=104, detail=0) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #17 0xb7135bda in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #18 0xb71371f8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #19 0xb6bf83a4 in IA__g_cclosure_marshal_VOID__VOID (closure=0x9ed3b68, return_value=0x0, n_param_values=1, param_values=0xa7b6990, invocation_hint=0xbfdce0cc, marshal_data=0xa355d08) at /build/buildd/glib2.0-2.20.1/gobject/gmarshal.c:77 #20 0xb6be93d9 in g_type_class_meta_marshal (closure=0x9ed3b68, return_value=0x0, n_param_values=1, param_values=0xa7b6990, invocation_hint=0xbfdce0cc, marshal_data=0x1a4) at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c:878 #21 0xb6beac7b in IA__g_closure_invoke (closure=0x9ed3b68, return_value=0x0, n_param_values=1, param_values=0xa7b6990, invocation_hint=0xbfdce0cc) at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #22 0xb6c006c0 in signal_emit_unlocked_R (node=0x9ed3ba8, detail=0, instance=0xa355d08, emission_return=0x0, instance_and_params=0xa7b6990) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:3177 #23 0xb6c024b9 in IA__g_signal_emit_valist (instance=0xa355d08, signal_id=103, detail=0, var_args=0xbfdce26c üÃöôoF·\220\\\023·\210âܿ³\\\023·\b]5\n\220\\\023ᬉܿ\005\037·\b]5\nà \005ճ\220\003Ã\tôÃö) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #24 0xb6c02936 in IA__g_signal_emit (instance=0xa355d08, signal_id=103, detail=0) at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #25 0xb7135c7a in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0 #26 0xb7135cb3 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #27 0xb71f0526 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #28 0xb6be93d9 in g_type_class_meta_marshal (closure=0xa355d08, return_value=0xbfdce450, n_param_values=2, param_values=0xa355d08, invocation_hint=0xbfdce43c, marshal_data=0xb4) at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c:878 #29 0xb6beac7b in IA__g_closure_invoke (closure=0x9ece1d8, return_value=0xbfdce450, n_param_values=2, param_values=0xa786c00,
[Bug 429765] [NEW] Evolution segfaults when saving recurring appointment from week view
Public bug reported: System: Dell Vostro 200 running Ubuntu 9.04 Intrepid Ibex, Evolution 2.26.1. Repro steps: 1. Add Google calendar to Evolution 2. Create non-recurring appointment in Google Calendar, and save it. 3. Switch to week view in Evolution. 4. Edit the appointment, and make it recurring. 5. Click Save. Result: At this point, Evolution closes immediately without any warning. The following is all that was written to console during execution: ** (evolution:6075): DEBUG: mailto URL command: evolution %s ** (evolution:6075): DEBUG: mailto URL program: evolution ** (evolution:6075): DEBUG: EI: SHELL STARTUP camel-imap-provider-Message: Unable to load summary: no such table: INBOX/Drafts camel-imap-provider-Message: Unable to load summary: no such table: INBOX/Tasks Segmentation fault Backtrace: I obtained a backtrace for the crash from gdb; how much use it will be I don't know because there aren't any symbols: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6071770 (LWP 6134)] 0xb5a60506 in comp_util_sanitize_recurrence_master () from /usr/lib/evolution/2.26/components/libevolution-calendar.so (gdb) backtrace #0 0xb5a60506 in comp_util_sanitize_recurrence_master () from /usr/lib/evolution/2.26/components/libevolution-calendar.so #1 0xb5af5e6a in ?? () from /usr/lib/evolution/2.26/components/libevolution-calendar.so #2 0xb5af610e in ?? () from /usr/lib/evolution/2.26/components/libevolution-calendar.so #3 0xb5af8cba in ?? () from /usr/lib/evolution/2.26/components/libevolution-calendar.so #4 0xb6a703a4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #5 0xb6a62c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #6 0xb6a78e57 in ?? () from /usr/lib/libgobject-2.0.so.0 #7 0xb6a7a4b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #8 0xb6a7a936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #9 0xb6f93305 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #10 0xb6f95365 in gtk_action_activate () from /usr/lib/libgtk-x11-2.0.so.0 #11 0xb713cece in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #12 0xb6a703a4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #13 0xb6a62c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #14 0xb6a78e57 in ?? () from /usr/lib/libgobject-2.0.so.0 #15 0xb6a7a4b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #16 0xb6a7a936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #17 0xb6fadbda in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #18 0xb6faf1f8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #19 0xb6a703a4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #20 0xb6a613d9 in ?? () from /usr/lib/libgobject-2.0.so.0 #21 0xb6a62c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #22 0xb6a786c0 in ?? () from /usr/lib/libgobject-2.0.so.0 #23 0xb6a7a4b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #24 0xb6a7a936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #25 0xb6fadc7a in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0 #26 0xb6fadcb3 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #27 0xb7068526 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #28 0xb6a613d9 in ?? () from /usr/lib/libgobject-2.0.so.0 #29 0xb6a62c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #30 0xb6a78aff in ?? () from /usr/lib/libgobject-2.0.so.0 #31 0xb6a7a34f in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #32 0xb6a7a936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #33 0xb71832ae in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #34 0xb7060f7c in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #35 0xb7062327 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #36 0xb6db334a in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #37 0xb69d9b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #38 0xb69dd0eb in ?? () from /usr/lib/libglib-2.0.so.0 #39 0xb69dd5ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #40 0xb73c4cc3 in bonobo_main () from /usr/lib/libbonobo-2.so.0 #41 0x0805d563 in ?? () #42 0xb6853775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #43 0x08050221 in ?? () ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- Evolution segfaults when saving recurring appointment from week view https://bugs.launchpad.net/bugs/429765 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 192112] Re: Error while uploading keys to keyservers
I can confirm this bug in Ubuntu Jaunty as well; it still uses GPA 0.7.6 777. Open for over a year :-( Presumably the fix to this is to ship a GPG binary that's compiled with gpgkeys_ldap and gpgkeys_hkp? How do we go about co-ordinating that? Presumably the GPG package maintainers would need to be notified? -- Error while uploading keys to keyservers https://bugs.launchpad.net/bugs/192112 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 192112] Re: Error while uploading keys to keyservers
That said, I'm not sure that the fix is as simple as compiling with gpgkeys_ldap and gpgkeys_hkp. I have installed the libldap2-dev package, and I can see the following in the output from ./configure on the latest (1.4.9) GPG source: checking whether LDAP via -lldap is present and sane... yes checking for ldap_get_option... yes checking for ldap_set_option... yes checking for ldap_start_tls_s... yes checking for ldap_start_tls_sA... no checking whether HKP keyserver support is requested... yes Having built and installed GPG from source with (AFAICT) LDAP and HKP enabled, I can use gpg from the CLI to send my key to an HKP server: $ gpg --send-keys DXXX gpg: sending key DXXX to hkp server keys.gnupg.net ... but GPA still crashes with Invalid argument. -- Error while uploading keys to keyservers https://bugs.launchpad.net/bugs/192112 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 373059] [NEW] Installed third party .DEBs not appearing as installed
Public bug reported: Binary package hint: synaptic I am using synaptic 0.62.5ubuntu3 on Ubuntu 9.04 Jaunty Jackalope 32-bit Desktop Edition on a Compaq C700 notebook. I have installed several .DEB packages using gdebi (both Brother MFC 7220 drivers, and my own company-internal packages). These packages install correctly without any warnings, and can be removed with command- line tools (e.g. apt-get remove mypackage). My own packages validate correctly with lintian. However, none of them - either my own, or Brother's - appear in Synaptic. I open Synaptic from the menu (System - Administration - Synaptic Package Manager), click Origin, click All, then type the package names into Quick search. I expect to see my installed packages there; instead, nothing is displayed in the list of packages. ** Affects: synaptic (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: synaptic I am using synaptic 0.62.5ubuntu3 on Ubuntu 9.04 Jaunty Jackalope 32-bit Desktop Edition on a Compaq C700 notebook. I have installed several .DEB packages using gdebi (both Brother MFC 7220 drivers, and my own company-internal packages). These packages install correctly without any warnings, and can be removed with command- - line tools (e.g. apt-get remove mydeb.deb). My own packages validate + line tools (e.g. apt-get remove mypackage). My own packages validate correctly with lintian. However, none of them - either my own, or Brother's - appear in Synaptic. I open Synaptic from the menu (System - Administration - Synaptic Package Manager), click Origin, click All, then type the package names into Quick search. I expect to see my installed packages there; instead, nothing is displayed in the list of packages. -- Installed third party .DEBs not appearing as installed https://bugs.launchpad.net/bugs/373059 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