Public bug reported:
Summary:
Intel has stopped supporting TLS 1.0 on its VPN endpoints, which is
apparently a new default configuration for some Cisco VPN servers. This
configuration is incompatible with the Ubuntu 14.04.5 openconnect and my
openconnect now fails to connect.
Details:
I'm
A fix for this issue has been mergd in to the tip tree. It will likely
be in the 3.18 kernel.
http://git.kernel.org/tip/cebf15eb09a2fd2fa73ee4faa9c4d2f813cf0f09
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: ignore-mc-sanity-check.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338919/+attachment/4208094/+files/ignore-mc-sanity-check.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is definitely a kernel bug. Essentially, we're reporting out NUMA
information in cpuinfo when we should be reporting out information about
the CPU itself. I'm working on an upstream kernel patch. I have a
patch available for testing that I can attach to this bug, although I'm
unsure this
Public bug reported:
I thought my system was hanging at boot. It turns out that a lot of
stuff was left in /tmp from a benchmark that was running and then
crashed. I instrumented /etc/init/mounted-tmp.conf and found out that
the 'find's to clear out /tmp were taking about 20 minutes to
Agreed that large amounts of its brain were missing. But the symptoms
here were severe: completely unbootable system where the recovery option
didn't work either. It was also something that persisted beyond a dist-
upgrade. We can certainly do a lot better than let a package install
while
Do you have custom or non-standard jobs in /etc/init that reference
the 'mounted' event?
Not that I know of.
Is this problem reproducible in 12.04 LTS?
Yeah, it managed to persist after the dist-upgrade.
After a bit more digging in /etc/init, I realized that some of
mountall's
Public bug reported:
Symptoms: system hangs forever at boot
Versions: originally discovered with 2.25ubuntu1, but reproduced with 2.31 as
well
Description:Ubuntu 11.04
Release:11.04
# apt-cache policy mountall
mountall:
Installed: 2.25ubuntu1
Candidate: 2.25ubuntu1
Version
One little note from
Debian:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635575#42
Debian kernels do not include the intel_idle driver.
Whatever is going on, it's fairly widespread, and other people seem to see it:
http://marc.info/?l=linux-kernelm=131459136817352w=2
Although, I do question
I haven't. It's still stumping me. I will try the cstate thing for a
bit and see how it turns out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/674075
Title:
Maverick won't resume (lucid will)
I wonder if anyone understands why we need to hit the power button after
opening the lid in order to make suspend proceed. Finding and fixing
that may be the key here.
Hah! I thought the power button trick was my little secret.
I've not had as much success with the power button when I
I filed this:
http://avahi.org/ticket/324
** Bug watch added: Avahi Bugs #324
http://www.avahi.org/ticket/324
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/31037
Title:
Vino-server takes 90% of
I think this is connected to avahi, somehow. Everybody's backtraces
seem to have avahi_entry_group_free() in them. People also can't kill
the process without kill -9, which is consistent with it being inside a
signal handler.
I can reproduce this by starting and stopping the vino daemon by
I _think_ this may be more complicated than we first thought. I've now
seen cases where the Ubuntu 2.6.35-23-generic kernel suspends and
resumes fine. I've also seen cases where recent mainline (2.6.37-rc7)
doesn't resume properly. They seem to do this in bunches. I couldn't
get it to suspend
I booted 2.6.35-23-generic with i915.modeset=0 on the kernel command-
line, just to take kernel modesetting out of the equation. The kernel
booted to a text console. I then did
echo mem /sys/power/state
The system appears to have suspended normally. But, it freezes upon
waking
If you're chroot'ing anyway, then you should have privileged access.
You could probably do this entirely in userspace, without even specially
intercepting the syscalls. When you set up the chroot, just get a copy
of how you want cpuinfo to look, and bind mount it on top of the
existing cpuinfo
If you're chroot'ing anyway, then you should have privileged access.
You could probably do this entirely in userspace, without even specially
intercepting the syscalls. When you set up the chroot, just get a copy
of how you want cpuinfo to look, and bind mount it on top of the
existing cpuinfo
Public bug reported:
The kernel uses profile=2 in the bootloader command-line arguments to
indicate that the kernel should turn on instruction pointer profiling at
boot time. This has existed for many years.
The readahead package uses 'profile' on the command-line to indicate
that it should do
So, the Ubuntu bug fixing policy seems to go as follows:
1. tell the user to install debuginfo
2. tell the user to go turn off the features causing their bug
3. let the user go find the bug themselves
4. when the user finds the bug, go tell them to file it with the original
project's bug tracker
Then rather then jerking people around, let's just tell them off the bat
that bugs on which triage team has no real competence to work can not
be filed here. People should just be told from the beginning to file
bugs with the originating project.
--
Evolution momentarily hangs during message
Yes, it appears to still occur with Hardy.
--
Evolution momentarily hangs during message composition
https://bugs.launchpad.net/bugs/196836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It *definitely* still occurs with Hardy.
--
Evolution momentarily hangs during message composition
https://bugs.launchpad.net/bugs/196836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
1. Create a honking large address book in Evolution
2. Turn on the plugin that we've been talking about, and enable
Preferences/Mail Preferences/Automatic Contacts periodic contact
synchronization.
The freeze occurs while iterating over the *ENTIRE* address book in the
plugin.
--
Evolution
Yes, disabling that plugin solved my freezes.
Is there a long-term solution to this issue? It seems awfully bad
behavior to have, even in a plugin, to freeze the entire UI. Should it
be disabled? Or, should we open up a bug against the plugin to get the
issue fixed properly?
--
Evolution
I ran the whole of evolution under gdb today. I see these messages
coming out on the console during a freeze:
bbdb: Buddy list has changed since last sync.
bbdb: Synchronizing buddy list to contacts...
freeze here
bbdb: Done syncing buddy list to contacts.
I believe this is from one of the
There are no debug symbol packages that I can find for libedataserver,
but I've got them for evolution and libglib. Is that going to be a
problem?
--
Evolution momentarily hangs during message composition
https://bugs.launchpad.net/bugs/196836
You received this bug notification because you are
New backtrace:
(gdb) bt
#0 0xb7865e6f in g_unichar_tolower () from /usr/lib/libglib-2.0.so.0
#1 0xb78661c8 in g_utf8_casefold () from /usr/lib/libglib-2.0.so.0
#2 0xb7cc38a7 in e_util_utf8_strcasecmp (s1=0xb65eeda0 Wendy, s2=0x8165bf8
Michael J. Wolf)
at e-data-server-util.c:274
#3
Public bug reported:
Binary package hint: evolution-data-server
During message composition, evolution hangs on me. This happens perhaps
every two minutes. After pegging the CPU for about 5 seconds, it
returns to normal. This can be a wee bit annoying when trying to
compose an email. :)
I do
I'm seeing the same behavior. I have 9 workspaces, and they all appear
in one row in the switcher, despite me having Show all workspaces in: 3
rows set as a workspace switcher option.
I've confirmed that manually killing brightside, followed by
modification of the workspace switcher option
29 matches
Mail list logo
