[Bug 1971434] Re: Display powersave only blanks, but does not turn off
One extra observation: when I use "xset dpms force off" to send the display to sleep, it stays in sleep indefinitely until the next user input, so apparently g-s-d never touches the power state. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
I'm using Xorg 2:21.1.3-2ubuntu2, with kms on "Intel Iris Plus Graphics (G7)". Xorg.0.log attached as well. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+attachment/5586349/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1971434/+attachment/5586347/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
apport information ** Tags added: apport-collected ** Description changed: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-07-04 (667 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + Package: gnome-settings-daemon 42.1-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + Tags: jammy + Uname: Linux 5.15.0-27-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1971434/+attachment/5586346/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1971434/+attachment/5586348/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
OK, have also reported this against gstreamer-vaapi as https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1971463 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] [NEW] Display powersave only blanks, but does not turn off
Public bug reported: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
One more datapoint, vlc seems to be using VAAPI on the same machine & distro without issues: ``` $ vlc big_buck_bunny_720p_surround.mp4 VLC media player 3.0.16 Vetinari (revision 3.0.13-8-g41878ff4f2) [55cebcc6f580] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [7f9b1c003e50] gl gl: Initialized libplacebo v4.192.1 (API v192) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7f9b39141220] avcodec decoder: Using Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 () for hardware decoding ``` -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
I'm pretty sure this is not a Totem issue, but rather a GStreamer issue. E.g. for the linked video, if I try to play it through playbin on Jammy (`gst-launch-1.0 playbin uri=file:///home/floe/Downloads/big_buck_bunny_720p_surround.mp4`), I get a black window with the audio track playing in the background. Same happens for any movie that also has the same issue with Totem. Running with GST_DEBUG=3 gives a lot of ``` 0:00:00.381581482 183712 0x7f5f6c05b640 ERROR vaapivideomemory gstvaapivideomemory.c:254:map_vaapi_memory: failed to make image current 0:00:00.381663666 183712 0x7f5f6c05b640 ERRORdefault video-frame.c:168:gst_video_frame_map_id: failed to map video frame plane 0 0:00:00.381711318 183712 0x7f5f6c05b640 WARN xvimagesink xvimagesink.c:1038:gst_xv_image_sink_show_frame: could not map image ``` so this may be VAAPI-related? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Update: can confirm that this issue can be worked around by uninstalling gstreamer1.0-vaapi package. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782077] [NEW] network/wifi icon missing from top bar and user menu
Public bug reported: On 18.04, after a recent update, the top bar in gnome-shell does not show a wifi icon anymore. More importantly, the network menu entry is missing in the user menu. This appears to be already tracked in this upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 Here's the recent updates that may have cause this (apparently the switch from 3.28.1 to 3.28.2): gnome-shell-common:amd64 (3.28.1-0ubuntu2, 3.28.2-0ubuntu0.18.04.1) gnome-shell:amd64 (3.28.1-0ubuntu2, 3.28.2-0ubuntu0.18.04.1) gnome-desktop3-data:amd64 (3.28.1-1ubuntu1, 3.28.2-0ubuntu1) libgnome-desktop-3-17:amd64 (3.28.1-1ubuntu1, 3.28.2-0ubuntu1) c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 17 08:56:18 2018 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-12 (2103 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-06-14 (32 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "gnome-network.png" https://bugs.launchpad.net/bugs/1782077/+attachment/5164365/+files/gnome-network.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1782077 Title: network/wifi icon missing from top bar and user menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219870] [NEW] Saving PDF annotations in evince breaks PDF in acroread
Public bug reported: [ Ubuntu 12.04, Evince 3.4.0, Poppler 0.18.4 ] When I add annotations to a PDF in evince and save a copy of this PDF (with annotations), I can no longer open the saved PDF in acroread (gives an error message root object invalid or not found). As far as I can tell, this only happens if the XREF table in the PDF is a compressed stream - a workaround is to run pdftk in.pdf output out.pdf uncompress before annotating output.pdf in evince. The result can be opened in acroread. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1219870 Title: Saving PDF annotations in evince breaks PDF in acroread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1219870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100320] Re: Annotation Font-Color is unreadable in Evince
I'm pretty sure the patch should also apply cleanly for the quantal package. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1100320 Title: Annotation Font-Color is unreadable in Evince To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1100320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1129866] Re: Reload in context menu discards unsaved changes
The only possible edit you can do to a document in evince is adding/editing annotations, so there are no other cases where this can happen. If you try to close a document with unsaved annotations, a dialog asking you to save first pops up. In any case, this can certainly lead to unintentional loss of data (edits) by just one mis-click, so in my opinion, it is certainly a bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1129866 Title: Reload in context menu discards unsaved changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1129866/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 919965] Re: Adding annotation: No input possible until some focus change
Here's a patch for this issue, tested against 3.4.0-0ubuntu1.4 from Precise. Should also work for newer versions. ** Patch added: fix-annotation-focus.patch https://bugs.launchpad.net/ubuntu/+source/evince/+bug/919965/+attachment/3537660/+files/fix-annotation-focus.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/919965 Title: Adding annotation: No input possible until some focus change To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/919965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100320] Re: Annotation Font-Color is unreadable in Evince
Here's a patch for this issue, backported from 3.6.1 to 3.4.0-0ubuntu1.4, the current package in Precise. ** Patch added: fix-annotation-color.patch https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1100320/+attachment/3537662/+files/fix-annotation-color.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1100320 Title: Annotation Font-Color is unreadable in Evince To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1100320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100320] Re: Annotation Font-Color is unreadable in Evince
Will this be backported to precise? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1100320 Title: Annotation Font-Color is unreadable in Evince To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1100320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1129866] [NEW] Reload in context menu discards unsaved changes
Public bug reported: 1) Description:Ubuntu 12.04.2 LTS Release:12.04 2) evince: Installed: 3.4.0-0ubuntu1.4 Candidate: 3.4.0-0ubuntu1.4 3) When a document has unsaved annotations, triggering reload should ask if those changes should be saved. 4) When creating annotations in a PDF document, accidentially hitting reload in the context menu will reload the document and discard all unsaved annotations without asking. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1129866 Title: Reload in context menu discards unsaved changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1129866/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 988522] Re: Can't watch TV (DVB-T)
Followup: from what I've gathered, this is not really a totem bug, but rather one in gstreamer itself. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/988522 Title: Can't watch TV (DVB-T) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/988522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 988522] Re: Can't watch TV (DVB-T)
Same for me. When running totem --gst-debug-level=2, I get lots of output along the lines of 0:00:38.039119153 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:mpegtsdemux1 looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.74703 compared to last timestamp: 0:00:12.839413376 0:00:38.078117061 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:mpegtsdemux1 looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.78703 compared to last timestamp: 0:00:12.839413376 0:00:38.111948530 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:mpegtsdemux1 looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.82703 compared to last timestamp: 0:00:12.839413376 0:00:38.147027498 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:mpegtsdemux1 looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.86703 compared to last timestamp: 0:00:12.839413376 0:00:38.193047320 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:mpegtsdemux1 looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.90703 compared to last timestamp: 0:00:12.839413376 0:00:38.241357790 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:mpegtsdemux1 looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.94703 compared to last timestamp: 0:00:12.839413376 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/988522 Title: Can't watch TV (DVB-T) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/988522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 829332] [NEW] closing laptop lid incorrectly throttles screensaver, even with external display
Public bug reported: When I close the lid of my laptop, gnome-power-manager always throttles the screensaver (as indicated by the following output): $ gnome-screensaver --debug --no-daemon | grep -i throttle [listener_add_ref_entry] gs-listener-dbus.c:716 (10:53:12): adding throttler from Power screensaver for reason 'Laptop lid is closed' on connection :1.18 [listener_check_throttle] gs-listener-dbus.c:353 (10:53:12): Checking for throttle [list_ref_entry] gs-listener-dbus.c:279 (10:53:12): throttler: Power screensaver for reason: Laptop lid is closed [gs_listener_set_throttle] gs-listener-dbus.c:340 (10:53:12):Changing throttle status: 1 However, this should not happen when external displays are connected, as it is the case for me. 1) Description:Ubuntu 11.04 Release:11.04 2) gnome-power-manager: Installed: 2.32.0-2ubuntu2 Candidate: 2.32.0-2ubuntu2 Version table: *** 2.32.0-2ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status 3) Screensaver should activate on external display, even when laptop lid closed. 4) Screen is blanked only due to throttling. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/829332 Title: closing laptop lid incorrectly throttles screensaver, even with external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/829332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 782165] Re: Evolution 2.32.2 in Natty mindlessly uses socks proxy environment
I'd also like to add another aspect to this bug: even when a valid global SOCKS proxy is configured, evolution will _always_ try to use the proxy, regardless of the entries in the global ignore list. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/782165 Title: Evolution 2.32.2 in Natty mindlessly uses socks proxy environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/782165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 820899] [NEW] S/MIME signature broken due to wrong MIME multipart header
Public bug reported: When attempting to send a signed S/MIME message with evolution, the mail is sent as multipart/mixed instead of multipart/signed, thereby preventing signature validation. GPG signed messages are formatted and verified correctly. S/MIME signatures from other mailers are also verified correctly by Evolution itself. Expected header: Content-Type: multipart/signed; protocol=application/x-pkcs7-signature; micalg=SHA1; boundary==_NextPart_000_0097_01CC529D.8F3107C0 Actual header: Content-Type: multipart/mixed; boundary==-y1IUcclJdzFtE471smGQ Ubuntu Release: 11.04 evolution: Installed: 2.32.2-0ubuntu7 Candidate: 2.32.2-0ubuntu7 Version table: *** 2.32.2-0ubuntu7 0 500 http://de.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/820899 Title: S/MIME signature broken due to wrong MIME multipart header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/820899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 815349] Re: gvfsd-dav crashed with SIGABRT in raise()
This bug is actually caused by libproxy0, specifically by a string parsing error in url.c:308 - when the URL contains username and port, but no pass, the parsing fails. A workaround is to specifiy neither user nor password in the connect to dialog, but to enter both in the password dialog that follows. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/815349 Title: gvfsd-dav crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/815349/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 766081] Re: gvfsd-dav assert failure: gvfsd-dav: misc.c:39: px_malloc0: Assert-makro ”mem != ((void *)0)”
This bug is actually caused by libproxy0, specifically by a string parsing error in url.c:308 - when the URL contains username and port, but no pass, the parsing fails. A workaround is to specifiy neither user nor password in the connect to dialog, but to enter both in the password dialog that follows. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/766081 Title: gvfsd-dav assert failure: gvfsd-dav: misc.c:39: px_malloc0: Assert- makro ”mem != ((void *)0)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/766081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 367771] [NEW] gnome-power-manager crashes on AC unplug
Public bug reported: Hi everyone, I've just upgraded my Acer Aspire One L110 to Jaunty Jackalope, and now my gnome-power-manager applet reliably crashes when I unplug the AC power. Running it with --verbose doesn't give any useful information. I can restart it, and it works also when I reattach the power - until I remove it again. 1. Ubuntu version is 9.04 2. g-p-m version is 2.24.2-2ubuntu8. 3. expected g-p-m to keep running 4. g-p-m quit unexpectedly UPDATE: I've tried debugging with --no-daemon, and now I'm getting something useful: TI:09:23:31 TH:0x918c640FI:gpm-cell.c FN:hal_device_property_modified_cb,273 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.charge_level.current, added=0, removed=0, finally=0 TI:09:23:31 TH:0x918c640FI:gpm-cell.c FN:hal_device_property_modified_cb,273 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.reporting.current, added=0, removed=0, finally=0 TI:09:23:31 TH:0x918c640FI:gpm-cell.c FN:hal_device_property_modified_cb,273 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.voltage.current, added=0, removed=0, finally=1 E: socket-client.c: socket(): Address family not supported by protocol Segmentation fault I suppose that the address family not supported error is caused by the custom kernel I'm running; however, g-p-m should handle that gracefully, as I've used the same kernel in Intrepid without problems. Florian UPDATE 2: I've just checked this with the stock 2.6.28-11 kernel, and while the socket() error is gone, g-p-m still crashes at the same point. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- gnome-power-manager crashes on AC unplug https://bugs.launchpad.net/bugs/367771 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 367771] Re: gnome-power-manager crashes on AC unplug
** Description changed: Hi everyone, I've just upgraded my Acer Aspire One L110 to Jaunty Jackalope, and now my gnome-power-manager applet reliably crashes when I unplug the AC power. Running it with --verbose doesn't give any useful information. I can restart it, and it works also when I reattach the power - until I remove it again. 1. Ubuntu version is 9.04 2. g-p-m version is 2.24.2-2ubuntu8. 3. expected g-p-m to keep running 4. g-p-m quit unexpectedly UPDATE: I've tried debugging with --no-daemon, and now I'm getting something useful: TI:09:23:31 TH:0x918c640FI:gpm-cell.c FN:hal_device_property_modified_cb,273 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.charge_level.current, added=0, removed=0, finally=0 TI:09:23:31 TH:0x918c640FI:gpm-cell.c FN:hal_device_property_modified_cb,273 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.reporting.current, added=0, removed=0, finally=0 TI:09:23:31 TH:0x918c640FI:gpm-cell.c FN:hal_device_property_modified_cb,273 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.voltage.current, added=0, removed=0, finally=1 E: socket-client.c: socket(): Address family not supported by protocol Segmentation fault I suppose that the address family not supported error is caused by the custom kernel I'm running; however, g-p-m should handle that gracefully, as I've used the same kernel in Intrepid without problems. Florian + + UPDATE 2: I've just checked this with the stock 2.6.28-11 kernel, and + while the socket() error is gone, g-p-m still crashes at the same point. -- gnome-power-manager crashes on AC unplug https://bugs.launchpad.net/bugs/367771 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
