[Desktop-packages] [Bug 1650990] Re: Chromium 55 not playing H264 videos
Also on Xenial. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1650990 Title: Chromium 55 not playing H264 videos Status in chromium-browser package in Ubuntu: Confirmed Bug description: On Yakkety, the updated Chromium 55 package doesn't play back H264 videos anymore. For example, using this test page: http://www.quirksmode.org/html5/tests/video.html the H264/MP4 video shows the player disabled, while WebM and Ogg/Theora work fine. I have the following packages installed: ii chromium-browser 55.0.2883.87-0ubuntu0.16.10.1328 amd64Chromium web browser, open-source version of Chrome ii chromium-browser-l10n 55.0.2883.87-0ubuntu0.16.10.1328 all chromium-browser language packages ii chromium-codecs-ffmpeg-extra 55.0.2883.87-0ubuntu0.16.10.1328 amd64Extra ffmpeg codecs for the Chromium Browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1650990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478820] [NEW] Can't restore broadband connection after resume from suspend
Public bug reported: After resume nm-applet doesn't restore broadband connections automatically. Instead it asks for the SIM PIN[1], but after unlocking the SIM no connection is established. Connecting manually from popup results in a message box showing the following error message: (32) Connection 'Notebook Flat' is not available on the device cdc-wdm0 at this time. Backtrace for this dialog is: #0 0x770c08a0 in gtk_message_dialog_new () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x00433c00 in utils_show_error_dialog (title=0x77ed5f02 "Verbindung fehlgeschlagen", text1=, text2=0xacd980 "(32) Connection 'Notebook Flat' is not available on the device cdc-wdm0 at this time.", modal=0, parent=) at utils.c:188 #2 0x00417392 in activate_connection_cb (client=, active=, error=, user_data=0x791600) at applet.c:673 #3 0x7656de1a in ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 #4 0x7656f6a5 in ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 #5 0x70e66962 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #6 0x70e69e81 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #7 0x760cb5d5 in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 #8 0x75347c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x75347f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x75348242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x004132ec in main (argc=1, argv=0x7fffdf58) at main.c:106 Trying to debug this now. My assumption is that modem-manager publishes the modem at a new DBus path because of the unlocking and apparently nm- applet fails to pickup that new path. [1] Although the PIN should be stored in the keyring, but let's ignore that bug for now. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1478820 Title: Can't restore broadband connection after resume from suspend Status in network-manager-applet package in Ubuntu: New Bug description: After resume nm-applet doesn't restore broadband connections automatically. Instead it asks for the SIM PIN[1], but after unlocking the SIM no connection is established. Connecting manually from popup results in a message box showing the following error message: (32) Connection 'Notebook Flat' is not available on the device cdc- wdm0 at this time. Backtrace for this dialog is: #0 0x770c08a0 in gtk_message_dialog_new () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x00433c00 in utils_show_error_dialog (title=0x77ed5f02 "Verbindung fehlgeschlagen", text1=, text2=0xacd980 "(32) Connection 'Notebook Flat' is not available on the device cdc-wdm0 at this time.", modal=0, parent=) at utils.c:188 #2 0x00417392 in activate_connection_cb (client=, active=, error=, user_data=0x791600) at applet.c:673 #3 0x7656de1a in ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 #4 0x7656f6a5 in ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 #5 0x70e66962 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #6 0x70e69e81 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #7 0x760cb5d5 in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 #8 0x75347c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x75347f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x75348242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x004132ec in main (argc=1, argv=0x7fffdf58) at main.c:106 Trying to debug this now. My assumption is that modem-manager publishes the modem at a new DBus path because of the unlocking and apparently nm-applet fails to pickup that new path. [1] Although the PIN should be stored in the keyring, but let's ignore that bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1478820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478816] [NEW] Network-Manager applet crashes when ModemManager restarts
Public bug reported: "sudo service ModemManager restart" results in this crash: #0 0x74d4b267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x74d4ceca in __GI_abort () at abort.c:89 #2 0x7536db55 in g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7536dbea in g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x0043215f in get_icon (device=0x8f23a0, state=NM_DEVICE_STATE_PREPARE, connection=0x7fffd801d650, out_pixbuf=0x7fffdcc8, out_indicator_icon=0x7fffdcd8, tip=0x7fffdcd0, applet=0x794780) at applet-device-broadband.c:644 #5 0x0041be32 in applet_get_device_icon_for_state (out_tip=, out_indicator_icon=, out_pixbuf=, applet=) at applet.c:3258 #6 applet_update_icon (user_data=0x794780) at applet.c:3365 #7 0x75347b4d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x75347f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x75348242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x004132ec in main (argc=1, argv=0x7fffdf58) at main.c:106 This is exactly the same place the patch for LP1418260 tries to fix. Apparently that patch is incomplete (or incorrect). With the attached patch the crash disappears. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Patch added: "lp1418260_really_dont_crash_if_mm_isnt_avail.patch" https://bugs.launchpad.net/bugs/1478816/+attachment/4434946/+files/lp1418260_really_dont_crash_if_mm_isnt_avail.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1478816 Title: Network-Manager applet crashes when ModemManager restarts Status in network-manager-applet package in Ubuntu: New Bug description: "sudo service ModemManager restart" results in this crash: #0 0x74d4b267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x74d4ceca in __GI_abort () at abort.c:89 #2 0x7536db55 in g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7536dbea in g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x0043215f in get_icon (device=0x8f23a0, state=NM_DEVICE_STATE_PREPARE, connection=0x7fffd801d650, out_pixbuf=0x7fffdcc8, out_indicator_icon=0x7fffdcd8, tip=0x7fffdcd0, applet=0x794780) at applet-device-broadband.c:644 #5 0x0041be32 in applet_get_device_icon_for_state (out_tip=, out_indicator_icon=, out_pixbuf=, applet=) at applet.c:3258 #6 applet_update_icon (user_data=0x794780) at applet.c:3365 #7 0x75347b4d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x75347f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x75348242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x004132ec in main (argc=1, argv=0x7fffdf58) at main.c:106 This is exactly the same place the patch for LP1418260 tries to fix. Apparently that patch is incomplete (or incorrect). With the attached patch the crash disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1478816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130918] Re: Please upgrade the foo2qpdl package
Awesome! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/1130918 Title: Please upgrade the foo2qpdl package Status in “foo2zjs” package in Ubuntu: New Bug description: Please upgrade this package as support for quite a few new printers was added in the meantime. At least for the Samsung CLP-365W difference between using a somewhat compatible driver, and using this updated driver is dramatic: With Ubuntu's driver version color printouts look like examples off modern art, whereas printouts with the most recent code look pretty well. 2013-02-21Rick Richardson * hbpldecode: Handle \r\n in the PCL stream. * hbpldecode: Update for HBPL version 2 2013-01-22Rick Richardson * New Printer: Samsung CLX-3185, CLX-3185FW 2013-01-14Rick Richardson * hplj10xx_gui.tcl: Bug: add "replace" parm in "old" 2013-01-13Rick Richardson * hplj1000: add a sleep 3 2013-01-04Rick Richardson * New Printer: Okidata C301dn 2013-01-02Rick Richardson * New Printer: Samsung CLP-365W 2012-09-09Rick Richardson * Makefile: Add DESTDIR to CUPS_SERVERBIN 2012-06-01Rick Richardson * Makefile, hplj1000: remove /lib/udev/rules.d/86-hpmud_plugin.rules Same thing as 2010-12-10, different path! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/1130918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130918] Re: Please upgrade the foo2qpdl package
Thanks a lot! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/1130918 Title: Please upgrade the foo2qpdl package Status in “foo2zjs” package in Ubuntu: New Bug description: Please upgrade this package as support for quite a few new printers was added in the meantime. At least for the Samsung CLP-365W difference between using a somewhat compatible driver, and using this updated driver is dramatic: With Ubuntu's driver version color printouts look like examples off modern art, whereas printouts with the most recent code look pretty well. 2013-02-21Rick Richardson * hbpldecode: Handle \r\n in the PCL stream. * hbpldecode: Update for HBPL version 2 2013-01-22Rick Richardson * New Printer: Samsung CLX-3185, CLX-3185FW 2013-01-14Rick Richardson * hplj10xx_gui.tcl: Bug: add "replace" parm in "old" 2013-01-13Rick Richardson * hplj1000: add a sleep 3 2013-01-04Rick Richardson * New Printer: Okidata C301dn 2013-01-02Rick Richardson * New Printer: Samsung CLP-365W 2012-09-09Rick Richardson * Makefile: Add DESTDIR to CUPS_SERVERBIN 2012-06-01Rick Richardson * Makefile, hplj1000: remove /lib/udev/rules.d/86-hpmud_plugin.rules Same thing as 2010-12-10, different path! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/1130918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130918] [NEW] Please upgrade the foo2qpdl package
Public bug reported: Please upgrade this package as support for quite a few new printers was added in the meantime. At least for the Samsung CLP-365W difference between using a somewhat compatible driver, and using this updated driver is dramatic: With Ubuntu's driver version color printouts look like examples off modern art, whereas printouts with the most recent code look pretty well. 2013-02-21 Rick Richardson * hbpldecode: Handle \r\n in the PCL stream. * hbpldecode: Update for HBPL version 2 2013-01-22 Rick Richardson * New Printer: Samsung CLX-3185, CLX-3185FW 2013-01-14 Rick Richardson * hplj10xx_gui.tcl: Bug: add "replace" parm in "old" 2013-01-13 Rick Richardson * hplj1000: add a sleep 3 2013-01-04 Rick Richardson * New Printer: Okidata C301dn 2013-01-02 Rick Richardson * New Printer: Samsung CLP-365W 2012-09-09 Rick Richardson * Makefile: Add DESTDIR to CUPS_SERVERBIN 2012-06-01 Rick Richardson * Makefile, hplj1000: remove /lib/udev/rules.d/86-hpmud_plugin.rules Same thing as 2010-12-10, different path! ** Affects: foo2zjs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/1130918 Title: Please upgrade the foo2qpdl package Status in “foo2zjs” package in Ubuntu: New Bug description: Please upgrade this package as support for quite a few new printers was added in the meantime. At least for the Samsung CLP-365W difference between using a somewhat compatible driver, and using this updated driver is dramatic: With Ubuntu's driver version color printouts look like examples off modern art, whereas printouts with the most recent code look pretty well. 2013-02-21Rick Richardson * hbpldecode: Handle \r\n in the PCL stream. * hbpldecode: Update for HBPL version 2 2013-01-22Rick Richardson * New Printer: Samsung CLX-3185, CLX-3185FW 2013-01-14Rick Richardson * hplj10xx_gui.tcl: Bug: add "replace" parm in "old" 2013-01-13Rick Richardson * hplj1000: add a sleep 3 2013-01-04Rick Richardson * New Printer: Okidata C301dn 2013-01-02Rick Richardson * New Printer: Samsung CLP-365W 2012-09-09Rick Richardson * Makefile: Add DESTDIR to CUPS_SERVERBIN 2012-06-01Rick Richardson * Makefile, hplj1000: remove /lib/udev/rules.d/86-hpmud_plugin.rules Same thing as 2010-12-10, different path! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/1130918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954352] Re: Enable wayland backend
darxus, plus a small patch for gtk: the wayland backend exported some private symbol by accident. the fix is upstreamed already. rob, it seems we'll need cairo-gl. but there also seems to be some chances, that the cairo-gl vs. nvidia issue was a TLS bug in libc 2.13 (at least that's what the gentoo guys claim). precise has libc 2.15. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Add --enable-wayland-backend to build flags. I believe this is all that's necessary for wayland to work with the existing Precise gtk packages. Wayland has one released version, 0.85, which is in the precise archives: https://launchpad.net/ubuntu/+source/wayland/ I'm told gtk 3.4 is (and will remain) compatable with it. Since gtk 3.4 is apparently already packaged for Precise, all that remains to be able to use some gtk applications via wayland is this build flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954352] Re: Enable wayland backend
darxus - uch, that hurts! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Add --enable-wayland-backend to build flags. I believe this is all that's necessary for wayland to work with the existing Precise gtk packages. Wayland has one released version, 0.85, which is in the precise archives: https://launchpad.net/ubuntu/+source/wayland/ I'm told gtk 3.4 is (and will remain) compatable with it. Since gtk 3.4 is apparently already packaged for Precise, all that remains to be able to use some gtk applications via wayland is this build flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954352] Re: Enable wayland backend
https://launchpad.net/~hasselmm/+archive/ppa/+builds?build_state=building -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Add --enable-wayland-backend to build flags. I believe this is all that's necessary for wayland to work with the existing Precise gtk packages. Wayland has one released version, 0.85, which is in the precise archives: https://launchpad.net/ubuntu/+source/wayland/ I'm told gtk 3.4 is (and will remain) compatable with it. Since gtk 3.4 is apparently already packaged for Precise, all that remains to be able to use some gtk applications via wayland is this build flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954352] Re: Enable wayland backend
ok, next problem: for whatever reason GtkSocket and GtkPlug get lost if you build with --enable-wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Add --enable-wayland-backend to build flags. I believe this is all that's necessary for wayland to work with the existing Precise gtk packages. Wayland has one released version, 0.85, which is in the precise archives: https://launchpad.net/ubuntu/+source/wayland/ I'm told gtk 3.4 is (and will remain) compatable with it. Since gtk 3.4 is apparently already packaged for Precise, all that remains to be able to use some gtk applications via wayland is this build flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954352] Re: Enable wayland backend
ok, it's more work than just passing --enable-wayland-backend: configure: error: Package requirements ( cairo-gl) were not met: No package 'cairo-gl' found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Add --enable-wayland-backend to build flags. I believe this is all that's necessary for wayland to work with the existing Precise gtk packages. Wayland has one released version, 0.85, which is in the precise archives: https://launchpad.net/ubuntu/+source/wayland/ I'm told gtk 3.4 is (and will remain) compatable with it. Since gtk 3.4 is apparently already packaged for Precise, all that remains to be able to use some gtk applications via wayland is this build flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954352] Re: Enable wayland backend
how about setting up a PPA to verify this theory? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Add --enable-wayland-backend to build flags. I believe this is all that's necessary for wayland to work with the existing Precise gtk packages. Wayland has one released version, 0.85, which is in the precise archives: https://launchpad.net/ubuntu/+source/wayland/ I'm told gtk 3.4 is (and will remain) compatable with it. Since gtk 3.4 is apparently already packaged for Precise, all that remains to be able to use some gtk applications via wayland is this build flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 831594] Re: email causes preview to stop working until restart or crashes evolution
upstream bug? https://bugzilla.gnome.org/show_bug.cgi?id=661690 ** Bug watch added: GNOME Bug Tracker #661690 https://bugzilla.gnome.org/show_bug.cgi?id=661690 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/831594 Title: email causes preview to stop working until restart or crashes evolution Status in “evolution” package in Ubuntu: Confirmed Bug description: Attached is an email I get from a cron job I run for updating my debmirror. After upgrading to evolution 3.1 (currently still present on 3.1.5-0ubuntu2), whenever I access this email (and the other daily debmirror emails), either message preview stops working until I restart evolution or evolution crashes. Steps to reproduce: 1. install evolution and make sure message previews are enabled 2. import the attached into a local folder 3. in the message list for this local folder, go back and forth between this email and another in the local folder 4. go to this email and use the scrollbar in the message preview window and scroll up and down several times. This may cause evolution to crash. The problem seems exacerbated when accessing the email over imap for some reason. This does not happen every time, but is pretty easy to reproduce nonetheless (eg, do the above steps a few times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/831594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp