[Bug 228794] Re: Evolution "forgets" POP3 passwords after sending GPG-signed mails
Even after the patch/fix, still evolution forgets the passwords of web calendars, I will open a new bug on this -- Evolution "forgets" POP3 passwords after sending GPG-signed mails https://bugs.launchpad.net/bugs/228794 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 237424] [NEW] Evolution forgets webcal passwords, and web calendars are not displayed on the gnome-clock-applet
Public bug reported: Binary package hint: evolution, evolution-data-server evolution and evolution-data-server version 2.22.1.1-0ubuntu3 Ubuntu 8.04 - Hardy updates Even after the fixing of bug #228794, evolution still forgets webcal passwords. How to reproduce: 1) Open evolution 2) Subscribe to a web calendar and insert password with the "remember password" flag 3) Close evolution and reopen it 4) Evolution asks for the password again and again... 5) The clock applet do not display web calendars at all This did not happen with evolution version 2.22.1-0ubuntu3 and evolution-data-server version 2.22.1-0ubuntu2 originally shipped with Hardy: evolution remembered webcal passwords and web calendars were displayed by the clock applet ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Also affects: evolution (Ubuntu) Importance: Undecided Status: New ** Description changed: - Binary package hint: evolution-data-server - Binary package hint: evolution, evolution-data-server evolution and evolution-data-server version 2.22.1.1-0ubuntu3 Ubuntu 8.04 - Hardy updates Even after the fixing of bug #228794, evolution still forgets webcal passwords. How to reproduce: 1) Open evolution 2) Subscribe to a web calendar and insert password with the "remember password" flag 3) Close evolution and reopen it 4) Evolution asks for the password again and again... 5) The clock applet do not display web calendars at all This did not happen with evolution version 2.22.1-0ubuntu3 and evolution-data-server version 2.22.1-0ubuntu2 originally shipped with Hardy: evolution remembered webcal passwords and web calendars were displayed by the clock applet -- Evolution forgets webcal passwords, and web calendars are not displayed on the gnome-clock-applet https://bugs.launchpad.net/bugs/237424 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 228794] Re: Evolution "forgets" POP3 passwords after sending GPG-signed mails
OK, I did it, see bug #237424 -- Evolution "forgets" POP3 passwords after sending GPG-signed mails https://bugs.launchpad.net/bugs/228794 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
I tried Intrepid Ibex Alpha5 live, but it is getting worse every new release: I get coloured stripes instead of the ubuntu desktop, and if I try to use the console (CTL+ALT+Fx) I cannot do anything because the cursor is stuck in the upper left corner of the screen; I can type commands but the output is completely messed up (strange characters), so I cannot understand where is the problem, and after typing some commands, I cannot see anything because the screen does not scroll down... I tried also to boot in safe graphics mode, but I get the same "results". I tried to install the new kernel packages on my old Feisty, but it asks me to upgrade some other packages, and I definitely do not want to risk to mess up everything, because at least now I have a working system. Leann Ogasawara wrote: > The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the > upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would > appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. > There are one of two ways you should be able to test: > > 1) If you are comfortable installing packages on your own, the linux- > image-2.6.27-* package is currently available for you to install and > test. > > --or-- > > 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer > 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. > Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. > You should then be able to test via a LiveCD. > > Please let us know immediately if this newer 2.6.27 kernel resolves the > bug reported here or if the issue remains. More importantly, please > open a new bug report for each new bug/regression introduced by the > 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please > specifically note if the issue does or does not appear in the 2.6.26 > kernel. Thanks again, we really appreicate your help and feedback. > > ** Tags added: cft-2.6.27 > > -- Avv. Alberto Pianon Via Napoli 4 - 36100 Vicenza (Italy) Tel. +39 0444 545666 Fax. +39 0444 322151 [EMAIL PROTECTED] -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
I tried Intrepid Ibex Alpha5 live, but it is getting worse every new release: I get coloured stripes instead of the ubuntu desktop, and if I try to use the console (CTL+ALT+Fx) I cannot do anything because the cursor is stuck in the upper left corner of the screen; I can type commands but the output is completely messed up (strange characters), so I cannot understand where is the problem, and after typing some commands, I cannot see anything because the screen does not scroll down... I tried also to boot in safe graphics mode, but I get the same "results". I tried to install the new kernel packages on my old Feisty, but it asks me to upgrade some other packages, and I definitely do not want to risk to mess up everything, because at least now I have a working system. -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
** Description changed: Binary package hint: linux-image-2.6.22-14-generic I have an ABIT NF-M2S MotherBoard (NVIDIA GeForce 6100+405 Chipset) With Feisty everything worked perfectly. When I upgraded to Gutsy, I found that the system clock was running way too fast than normal, as well as keyboard repetition, mouse pointer animations, and there were severe problems with many applications because of the abnormal speed of the clock. Furthermore, the NVDIA proprietary driver apparently worked but the computer friezed if you tried to restart the X server. I tried to disable acpi at boot time (acpi=off): the clock worked - properly, but I can't shutdown the system (and restarting the X server - always freezes the system). + properly, but I couldn't shutdown the system (and restarting the X + server always friezed the system). - I tried with a fresh Gutsy install, both 32 and 64 bit version, but the problem is always the same. + I tried with a fresh Gutsy install, both 32 and 64 bit version, but the problem was always the same. I tried many other things, including reconfiguring X through "dpkg-reconfigure -phigh xserver-xorg" and even manually (I have tried vesa, nvidia, nv), but with no results as for the clock abnormal speed (with vesa drivers the x server can be restarted, but there is no 3d support...). - Finally, I downgraded the kernel to Feisty's one (2.6.20-16), and + Finally, I downgraded the kernel to Feisty's one (2.6.20-16), and now everything works fine (for some reason, I had to downgrade also gnome- - mount to mount USB devices correctly in gnome), apart the NVIDIA + mount to mount USB devices correctly in gnome), apart from the NVIDIA proprietary driver (restarting X always freezes the system, unless you use the vesa driver or the old nvidia-legacy driver). - So I think that there is a problem with kernel 2.6.22-14 and ABIT NF-M2S - and/or NVIDIA GeForce 6100+405 Chipset. + I think that there is a problem with kernel 2.6.22-14 and ABIT NF-M2S + and/or NVIDIA GeForce 6100+405 Chipset (and maybe another problem with + xserver-xorg and nvidia) - ANOTHER USER REPORTED EXACTLY THE SAME PROBLEM HERE, and I replied explained as I "solved" the problem: + ANOTHER USER REPORTED EXACTLY THE SAME PROBLEM HERE http://ubuntuforums.org/showthread.php?t=636772 -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
** Description changed: Binary package hint: linux-image-2.6.22-14-generic I have an ABIT NF-M2S MotherBoard (NVIDIA GeForce 6100+405 Chipset) With Feisty everything worked perfectly. - When I upgraded to Gutsy, I found that the system clock was running way too fast than normal, as well as keyboard repetition, mouse pointer animations, and other problems with many applications because of the abnormal speed of the clock. Furthermore, the NVDIA proprietary driver apparently works but the computer freezes if you try to restart the X server. + When I upgraded to Gutsy, I found that the system clock was running way too fast than normal, as well as keyboard repetition, mouse pointer animations, and there were severe problems with many applications because of the abnormal speed of the clock. Furthermore, the NVDIA proprietary driver apparently worked but the computer friezed if you tried to restart the X server. - I tried to disable acpi at boot time (acpi=off): the clock works + I tried to disable acpi at boot time (acpi=off): the clock worked properly, but I can't shutdown the system (and restarting the X server always freezes the system). I tried with a fresh Gutsy install, both 32 and 64 bit version, but the problem is always the same. I tried many other things, including reconfiguring X through "dpkg-reconfigure -phigh xserver-xorg" and even manually (I have tried vesa, nvidia, nv), but with no results as for the clock abnormal speed (with vesa drivers the x server can be restarted, but there is no 3d support...). Finally, I downgraded the kernel to Feisty's one (2.6.20-16), and everything works fine (for some reason, I had to downgrade also gnome- mount to mount USB devices correctly in gnome), apart the NVIDIA proprietary driver (restarting X always freezes the system, unless you use the vesa driver or the old nvidia-legacy driver). So I think that there is a problem with kernel 2.6.22-14 and ABIT NF-M2S and/or NVIDIA GeForce 6100+405 Chipset. - ANOTHER USER REPORTED THE SAME PROBLEM HERE, AND I REPLIED: + ANOTHER USER REPORTED EXACTLY THE SAME PROBLEM HERE, and I replied explained as I "solved" the problem: http://ubuntuforums.org/showthread.php?t=636772 -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187092] [NEW] Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
Public bug reported: Binary package hint: linux-image-2.6.22-14-generic I have an ABIT NF-M2S MotherBoard (NVIDIA GeForce 6100+405 Chipset) With Feisty everything worked perfectly. When I upgraded to Gutsy, I found that the system clock was running way too fast than normal, as well as keyboard repetition, mouse pointer animations, and other problems with many applications because of the abnormal speed of the clock. Furthermore, the NVDIA proprietary driver apparently works but the computer freezes if you try to restart the X server. I tried to disable acpi at boot time (acpi=off): the clock works properly, but I can't shutdown the system (and restarting the X server always freezes the system). I tried with a fresh Gutsy install, both 32 and 64 bit version, but the problem is always the same. I tried many other things, including reconfiguring X through "dpkg-reconfigure -phigh xserver-xorg" and even manually (I have tried vesa, nvidia, nv), but with no results as for the clock abnormal speed (with vesa drivers the x server can be restarted, but there is no 3d support...). Finally, I downgraded the kernel to Feisty's one (2.6.20-16), and everything works fine (for some reason, I had to downgrade also gnome- mount to mount USB devices correctly in gnome), apart the NVIDIA proprietary driver (restarting X always freezes the system, unless you use the vesa driver or the old nvidia-legacy driver). So I think that there is a problem with kernel 2.6.22-14 and ABIT NF-M2S and/or NVIDIA GeForce 6100+405 Chipset. ANOTHER USER REPORTED THE SAME PROBLEM HERE, AND I REPLIED: http://ubuntuforums.org/showthread.php?t=636772 ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
I tried Hardy Beta (live) - (quite the) same result: 1) system clock (and mouse pointer animation, etc) way too fast than normal 2) no restricted drivers available (but maybe it's just the live version) 3) shutdown works (at least...) -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
as requested... ** Attachment added: "version.log" http://launchpadlibrarian.net/12961012/version.log -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/12961013/dmesg.log -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/12961017/lspci-vvnn.log -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 187092] Re: Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system
I tested Hardy alpha 6. Same problem (system clock way too fast than normal - seconds are running about 3-4 times than "real" seconds - and everything is affected by this - mouse pointer, cursor, apps, etc.) Furthermore, no nvidia proprietary drivers were signalled as available (but maybe it's just the live cd) Tell me if you need something more (logs, dmesg, other stuff?) -- Upgrade from Feisty to Gutsy: system clock way too fast than normal and shutdown does not work on ABIT NF-M2S + restarting X freezes the system https://bugs.launchpad.net/bugs/187092 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 502276] Re: LIRC configuration for TechniSat/TechnoTrend USB IR receiver
where is the bug? Is there is somethin that I am missing? I would like to buy one... -- LIRC configuration for TechniSat/TechnoTrend USB IR receiver https://bugs.launchpad.net/bugs/502276 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 997630] Re: evince and eog broken on remote sessions (X, NX, x2go and VNC)
Patch do not apply to the source for armel architecture. The code of geis.c is slightly different, but I am not a programmer so I do not know how to fix it I attach the file that I get with "apt-get source libutouch-geis1" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997630 Title: evince and eog broken on remote sessions (X, NX, x2go and VNC) To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/997630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997630] Re: evince and eog broken on remote sessions (X, NX, x2go and VNC)
** Attachment added: "geis.c for armel architecture" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/997630/+attachment/3251843/+files/geis.c_armel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997630 Title: evince and eog broken on remote sessions (X, NX, x2go and VNC) To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/997630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783107] Re: cx88 remote control does not work
I have the same problem with the HVR-4000 remote. The only "output" I can get is from /dev/lirc0 but it is irregular and uncomprehensible I tried to apply this patch to cx88 kernel modules: https://patchwork.kernel.org/patch/758262/ however it still does not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783107 Title: cx88 remote control does not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783107] Re: cx88 remote control does not work
SOLVED! There were two patches to apply for 32-bit kernel, not only one http://www.mail-archive.com/linux-media@vger.kernel.org/msg30942.html However, only one patch as been accepted in the stable 2.6.38 tree, the other one has been inserted in the devel tree, as far as I can understand from here (and from next messages in thread): http://www.mail-archive.com/linux-media@vger.kernel.org/msg30982.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783107 Title: cx88 remote control does not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783107] Re: cx88 remote control does not work
however there are two other issues: 1) in order to make it work, one has to remove the ir-lirc-codec module AFTER it has been loaded if one prevents it to load from the beginning (with something like "alias ir-lirc-codec /dev/null") the remote does not work One has to let it load and THEN remove it, then trying with evtest or ir-keytable the remote seems to work fine 2) I did not manage to make the remote work with lirc yet, but only with inputlirc (while it worked perfectly with lirc with my previous installation of Ubuntu 9.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783107 Title: cx88 remote control does not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783107] Re: cx88 remote control does not work
the command I am using is inputlircd -g -n cx88* -m 0 -d /var/run/lirc/lircd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783107 Title: cx88 remote control does not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758821] Re: freevo.real crashed with IOError in __main__: [Errno 2] No such file or directory: '/usr/lib/pymodules/python2.5/freevo/version.py'
Natty installs python 2.7 but freevo searches for 2.5 modules! This is a mistake in the building of the package, I guess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758821 Title: freevo.real crashed with IOError in __main__: [Errno 2] No such file or directory: '/usr/lib/pymodules/python2.5/freevo/version.py' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
