On 27/06/12 07:57 PM, Ilguiz Latypov wrote:
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
After reporting my work-around I followed advice of the davmail author
and disabled the use of system proxy settings
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
I believe it is possible that davmail could compile with Open JDK 1.7
and that its build system prevents higher version numbers by mistake.
I believe changing the
Package: linux-2.6
Version: 2.6.32-30
Severity: critical
Justification: breaks the whole system
Both normal and safe boot modes panicked when running the ram disk
image. Worse, the upgrade DELETED the earlier kernel image and ram disk
image. I managed to boot by editing the safe mode command
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
Package: update-manager-gnome
Version: 0.200.3-1
Severity: grave
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
Tags: sid
Justification: renders package unusable
Update Manager crashed on its start.
*** /tmp/update-manager-bugm_Su6p
The information below has been automatically
Package: python2.5-minimal
Version: 2.5.5-5
Severity: normal
I wonder if this can be fixed with the following change,
--- /usr/lib/python2.5/py_compile.py.orig 2010-04-21 06:00:38.0 -0400
+++ /usr/lib/python2.5/py_compile.py2010-04-21 05:46:52.0 -0400
@@ -153,6 +153,7 @@
Package: python-central
Version: 0.5.13
Followup-For: Bug #418108
I am guessing that the fix to the problem can be as simple as adding a
line global config under global _defaults in the failed script:
--- /usr/share/pycentral-data/pyversions.py.orig2007-04-06
23:23:10.0 -0400
7 matches
Mail list logo