[Desktop-packages] [Bug 1633855] Re: akonadi fails to start after upgrade to yakkety
Also affects Ubuntu 14.04.5 LTS.
The whole of Kontact/Kmail is broken.
The reason seems to be the mysql security updates of 2016-10-26:
Start-Date: 2016-10-26 00:40:44
Upgrade: mysql-common:amd64 (5.5.52-0ubuntu0.14.04.1, 5.5.53-0ubuntu0.14.04.1)
End-Date: 2016-10-26 00:40:51
Start-Date: 2016-10-26 00:41:16
Upgrade: mysql-server-core-5.5:amd64 (5.5.52-0ubuntu0.14.04.1,
5.5.53-0ubuntu0.14.04.1)
End-Date: 2016-10-26 00:41:25
Start-Date: 2016-10-26 00:41:45
Upgrade: mysql-client-core-5.5:amd64 (5.5.52-0ubuntu0.14.04.1,
5.5.53-0ubuntu0.14.04.1), mysql-common:amd64 (5.5.52-0ubuntu0.14.04.1,
5.5.53-0ubuntu0.14.04.1), libmysqlclient18:amd64 (5.5.52-0ubuntu0.14.04.1,
5.5.53-0ubuntu0.14.04.1)
End-Date: 2016-10-26 00:41:53
The log file "~/.local/share/akonadi/akonadiserver.error" says:
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/username/.local/share/akonadi/mysql.conf",
"--datadir=/home/username/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-username.EZqgDd/mysql.socket")
stdout: ""
stderr: "/usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' (Error
2)
161027 5:22:54 [ERROR] Failed to access directory for --secure-file-priv.
Please make sure that directory exists and is accessible by MySQL Server.
Supplied value : /var/lib/mysql-files
161027 5:22:54 [ERROR] Aborting
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1633855
Title:
akonadi fails to start after upgrade to yakkety
Status in akonadi package in Ubuntu:
Confirmed
Status in mysql-5.5 package in Ubuntu:
New
Bug description:
After yesterday 15 sept. upgrade to Kubuntu 16.10 Yakkety Yak, kmail
fails to start, because akonadi backend fails.
Starting akonadi from command line,
$ akonadictl start
the output contains:
stderr: "mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 -
No such file or directory)\n2016-10-16T11:54:23.365277Z 0 [Warning] The syntax
'--log_warnings/-W' is deprecated and will be removed in a future release.
Please use '--log_error_verbosity' instead.\n2016-10-16T11:54:23.365377Z 0
[Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use
--explicit_defaults_for_timestamp server option (see documentation for more
details).\n2016-10-16T11:54:23.365479Z 0 [ERROR] Failed to access directory for
--secure-file-priv. Please make sure that directory exists and is accessible by
MySQL Server. Supplied value :
/var/lib/mysql-files\n2016-10-16T11:54:23.365488Z 0 [ERROR]
Aborting\n\n2016-10-16T11:54:23.365508Z 0 [Note] Binlog end\n"
The cause is a regression in the file
/etc/xdg/akonadi/mysql-global.conf
provided by the package
akonadi-backend-mysql
Diff of the content of mysql-global.conf from Yakkety vs Xenial:
diff -u "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf"
"akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf"
--- "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf"
2016-06-24 15:51:12.0 +0200
+++ "akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf"
2016-04-20 10:42:09.0 +0200
@@ -100,5 +100,14 @@
# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K
+# KUBUNTU:
+# Unset the export dir check as only the full mysql-server package creates it
+secure_file_priv=
+
+# KUBUNTU:
+# workaround for 5.7 being more strict with column types
+# (reverts to 5.6 behavior)
+sql_mode=NO_ENGINE_SUBSTITUTION
+
[client]
default-character-set=utf8
Applying this patch fixes the bug.
The "secure_file_priv" setting went missing is referenced in the package
changelog:
akonadi (4:15.12.3-0ubuntu5) xenial; urgency=medium
* kubuntu_disable_secure_file_priv_check.diff:
- Set secure_file_priv to empty as that directory is not set in a default
kubuntu install
-- Philip Muškovac Mon, 18 Apr 2016 15:24:43
+0200
Marco Gamberoni
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1633855/+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 1280053] Re: eclipse is a crashy mess on trusty
Can you check whether you are suffering this: https://bugs.launchpad.net/eclipse/+bug/1241101 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1280053 Title: eclipse is a crashy mess on trusty Status in “eclipse” package in Ubuntu: Confirmed Bug description: It seems apport has stopped catching eclipse crashes, so I'm reporting this issue by hand. To reproduce, all I have to do is open a medium sized Java project in eclipse and try to navigate around (using F3 and F4 etc.). After 3 or 4 operations, eclipse always crashes. This started right after upgrading to trusty. What can I do to help folks debug this further? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eclipse-platform 3.8.1-5.1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 13 21:11:10 2014 InstallationDate: Installed on 2011-09-18 (879 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: eclipse UpgradeStatus: Upgraded to trusty on 2014-02-02 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1280053/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Tried the following workarounds on Kubuntu 14.04 amd64 with Eclipse from
package management, all did not help
- Opening the search menu (CTRL+F) and closing it with ESC only takes 2-3
attempts to crash Eclipse:
- Setting affinity (taskset -c 1 eclipse)
- Setting theme to Raleigh in systemsettings
- GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc eclipse
- UBUNTU_MENUPROXY= eclipse
- Using all of the above at once ("export
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc ; export
UBUNTU_MENUPROXY= ; taskset -c 1 eclipse" - and setting Raleigh in
systemsettings)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in “gtk+2.0” package in Ubuntu:
Triaged
Status in “unity” package in Ubuntu:
Invalid
Status in “gtk+2.0” package in Suse:
New
Bug description:
Running smartgit 4.6.4 on 13.10 64 bits. After registering the
product, smartgit crash when trying to open a new repository. Java
error log :
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0
I tried different version of Java (Oracle v7 and v6 jre) with same
result. Also, Eclipse display blank menus so there's a general java
problem with displays.
To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Can confirm the issue with Kubuntu 14.04 amd64, Eclipse crashes when closing the search window: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f487db99718, pid=13246, tid=139949693536000 # # JRE version: OpenJDK Runtime Environment (7.0_55-b14) (build 1.7.0_55-b14) # Java VM: OpenJDK 64-Bit Server VM (24.51-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19718] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1294325] [NEW] Chromium password autocomplete broken for certain fields
Public bug reported:
Used Ubuntu: Kubuntu 13.10 amd64
Today I installed the following upgrades (taken from /var/log/apt/history.log):
Start-Date: 2014-03-18 20:22:56
Upgrade: chromium-codecs-ffmpeg-extra:amd64
(32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1,
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1), chromium-browser-l10n:amd64
(32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1,
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1), chromium-browser:amd64
(32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1,
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1)
End-Date: 2014-03-18 20:23:19
They broke autocomplete for HTML password fields which have the
"autocomplete=off" attribute set.
While this might not sound like a bug to you, it IS a regression: With previous
versions, the "autocomplete=off" attribute could be temporarily disabled with a
JavaScript bookmarklet [1]. Then Chromium would ask the user to store the
password. Once the password was stored in the database, future visits of the
site would autocomplete the field. So basically in previous versions, the
"autocomplete=off" flag was only a guardian against storing the password in the
database, NOT against restoring it from the database if it is already in the
database.
In the current version, autocomplete does NOT restore the stored password
anymore, even when manually choosing the username from the username field's
drop down menu. Using the bookmarklet to set "autocomplete=on" also doesn't
help. I've tried this with two different websites.
You might argue that this is intended by the website's developer. But I
think it is an unacceptable restriction of my personal choice as a user
of what I want to do with my computer. It wastes my time to continuously
have to enter shitloads of passwords of websites which I have to visit
every day. And the disabling of autocomplete form is slowly creeping
into a lot of websites because it allows them to generate a false sense
of security for non-expert users while obstructing anyone who trusts his
machine.
[1] Store this as a bookmark, without the quotes: "javascript:(function(){var
fm=document.getElementsByTagName('form');for(i=0;ihttps://bugs.launchpad.net/bugs/1294325
Title:
Chromium password autocomplete broken for certain fields
Status in “chromium-browser” package in Ubuntu:
New
Bug description:
Used Ubuntu: Kubuntu 13.10 amd64
Today I installed the following upgrades (taken from
/var/log/apt/history.log):
Start-Date: 2014-03-18 20:22:56
Upgrade: chromium-codecs-ffmpeg-extra:amd64
(32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1,
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1), chromium-browser-l10n:amd64
(32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1,
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1), chromium-browser:amd64
(32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1,
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1)
End-Date: 2014-03-18 20:23:19
They broke autocomplete for HTML password fields which have the
"autocomplete=off" attribute set.
While this might not sound like a bug to you, it IS a regression: With
previous versions, the "autocomplete=off" attribute could be temporarily
disabled with a JavaScript bookmarklet [1]. Then Chromium would ask the user to
store the password. Once the password was stored in the database, future visits
of the site would autocomplete the field. So basically in previous versions,
the "autocomplete=off" flag was only a guardian against storing the password in
the database, NOT against restoring it from the database if it is already in
the database.
In the current version, autocomplete does NOT restore the stored password
anymore, even when manually choosing the username from the username field's
drop down menu. Using the bookmarklet to set "autocomplete=on" also doesn't
help. I've tried this with two different websites.
You might argue that this is intended by the website's developer. But
I think it is an unacceptable restriction of my personal choice as a
user of what I want to do with my computer. It wastes my time to
continuously have to enter shitloads of passwords of websites which I
have to visit every day. And the disabling of autocomplete form is
slowly creeping into a lot of websites because it allows them to
generate a false sense of security for non-expert users while
obstructing anyone who trusts his machine.
[1] Store this as a bookmark, without the quotes: "javascript:(function(){var
fm=document.getElementsByTagName('form');for(i=0;ihttps://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1294325/+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 1242975] [NEW] "gksu -u other_user .." is broken
Public bug reported: I did this test run with Lubuntu 13.10 amd64 and Xubuntu 13.10 amd64 in separate VMs. Steps to reproduce: - Install fresh Lubuntu/Xubuntu - Open the XFCE terminal. - Type "sudo -i", enter password, and do the following: # create a secondary useraccount adduser testuser # use nano or your favorite editor: nano /etc/sudoers.d/testuser # allow your main useraccount to execute ANY commands as the "testuser" user using sudo. password will NOT be required your_main_username ALL=(testuser)NOPASSWD: ALL # save the file. # set permissions of sudoers.d correctly chmod 440 /etc/sudoers.d/* - now open a shell as your main user, NOT as root. do: gksudo -u testuser xfce4-terminal This should open a terminal logged in as "testuser". But it does nothing. Add the debug option and pipe to less to view what happens: "gksudo -du testuser xfce4-terminal 2>&1 | less" Output: No ask_pass set, using default! xauth: /tmp/libgksu-wPttP0/.Xauthority STARTUP_ID: gksudo/xfce4-terminal/2799-0-xubuntu1_TIME2139054 cmd[0]: /usr/bin/sudo cmd[1]: -H cmd[2]: -S cmd[3]: -p cmd[4]: GNOME_SUDO_PASS cmd[5]: -u cmd[6]: testuser cmd[7]: -- cmd[8]: xfce4-terminal buffer: -No protocol specified- buffer: -- buffer: -(xfce4-terminal:2802): Gtk-WARNING **: cannot open display: :0.0- buffer: -- buffer: -- buffer: -- buffer: -- buffer: -- buffer: -- (a lot more of the previous messages) brute force GNOME_SUDO_PASS ended... No password prompt found; we'll assume we don't need a password. xauth: /tmp/libgksu-wPttP0/.Xauthority xauth_env: /home/xor/.Xauthority dir: /tmp/libgksu-wPttP0 The fact that there is output of xfce4-terminal BEFORE gksudo talks about password, .Xauthority, etc. might indicate that it tries to run the child application too early? I haven't read the source code though, please validate this claim by reading it. ** Affects: gksu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1242975 Title: "gksu -u other_user .." is broken Status in “gksu” package in Ubuntu: New Bug description: I did this test run with Lubuntu 13.10 amd64 and Xubuntu 13.10 amd64 in separate VMs. Steps to reproduce: - Install fresh Lubuntu/Xubuntu - Open the XFCE terminal. - Type "sudo -i", enter password, and do the following: # create a secondary useraccount adduser testuser # use nano or your favorite editor: nano /etc/sudoers.d/testuser # allow your main useraccount to execute ANY commands as the "testuser" user using sudo. password will NOT be required your_main_username ALL=(testuser)NOPASSWD: ALL # save the file. # set permissions of sudoers.d correctly chmod 440 /etc/sudoers.d/* - now open a shell as your main user, NOT as root. do: gksudo -u testuser xfce4-terminal This should open a terminal logged in as "testuser". But it does nothing. Add the debug option and pipe to less to view what happens: "gksudo -du testuser xfce4-terminal 2>&1 | less" Output: No ask_pass set, using default! xauth: /tmp/libgksu-wPttP0/.Xauthority STARTUP_ID: gksudo/xfce4-terminal/2799-0-xubuntu1_TIME2139054 cmd[0]: /usr/bin/sudo cmd[1]: -H cmd[2]: -S cmd[3]: -p cmd[4]: GNOME_SUDO_PASS cmd[5]: -u cmd[6]: testuser cmd[7]: -- cmd[8]: xfce4-terminal buffer: -No protocol specified- buffer: -- buffer: -(xfce4-terminal:2802): Gtk-WARNING **: cannot open display: :0.0- buffer: -- buffer: -- buffer: -- buffer: -- buffer: -- buffer: -- (a lot more of the previous messages) brute force GNOME_SUDO_PASS ended... No password prompt found; we'll assume we don't need a password. xauth: /tmp/libgksu-wPttP0/.Xauthority xauth_env: /home/xor/.Xauthority dir: /tmp/libgksu-wPttP0 The fact that there is output of xfce4-terminal BEFORE gksudo talks about password, .Xauthority, etc. might indicate that it tries to run the child application too early? I haven't read the source code though, please validate this claim by reading it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1242975/+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 653705] Re: Doesn't ask for a password - IMAP
- So can you please fix the Evolution package to be dependent on "gnome- keyring"? -- 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/653705 Title: Doesn't ask for a password - IMAP Status in “evolution” package in Ubuntu: Incomplete Bug description: Binary package hint: evolution It doesn't ask for a password for automatically created Google IMAP account.So it just hangs. I see same bug dated by 2006 year. It is sad. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sat Oct 2 22:11:28 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928) ProcEnviron: SHELL=/bin/bash LANG=ru_RU.utf8 SourcePackage: evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/653705/+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 653705] Re: Doesn't ask for a password - IMAP
I found a workaround: As I am using Kubuntu (=Ubuntu with KDE), not all Gnome packages are installed. So I manually installed "gnome-keyring" (+ dependancies "gcr", "libpam-gnome-keyring"), which seems to be the password backend for Evolution. Now Evolution asks for a password :) -- 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/653705 Title: Doesn't ask for a password - IMAP Status in “evolution” package in Ubuntu: Incomplete Bug description: Binary package hint: evolution It doesn't ask for a password for automatically created Google IMAP account.So it just hangs. I see same bug dated by 2006 year. It is sad. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sat Oct 2 22:11:28 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928) ProcEnviron: SHELL=/bin/bash LANG=ru_RU.utf8 SourcePackage: evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/653705/+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 653705] Re: Doesn't ask for a password - IMAP
Getting this on Kubuntu 12.10 with Evolution 3.6.2 -- 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/653705 Title: Doesn't ask for a password - IMAP Status in “evolution” package in Ubuntu: Incomplete Bug description: Binary package hint: evolution It doesn't ask for a password for automatically created Google IMAP account.So it just hangs. I see same bug dated by 2006 year. It is sad. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sat Oct 2 22:11:28 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928) ProcEnviron: SHELL=/bin/bash LANG=ru_RU.utf8 SourcePackage: evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/653705/+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
