Over a year later and no triage, no nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694149
Title:
ssl error using urllib2
To manage notifications about this bug go to:
Hrm. What is the point of LTS even if bugs like this can go completely
ignored?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694149
Title:
ssl error using urllib2
To manage notifications about
I wonder why this ticket has not even been triaged.
It was filed against an LTS release of Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694149
Title:
ssl error using urllib2
To manage
Public bug reported:
On Ubuntu 14.04.5 LTS with python 2.7.5-5ubuntu3 and libpython2.7-stdlib
2.7.6-8ubuntu0.3, using this little example program:
#!/usr/bin/python
import urllib2
USER_AGENT = 'Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/41.0.2272.101
And yet another Ubuntu bug that has zero activity for 3 years only be
closed EOL. No wonder I don't use Ubuntu any more. Seems there is zero
interested in fixing any bug that doesn't affect a phone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Currently the dbus upstart script has this:
start on local-filesystems
But this makes the dbus startup fail if /usr is an NFS filesystem.
After changing the above line to:
start on remote-filesystems
dbus started working correctly.
This actually highlights the problem
So "Confirmed" but nothing done about it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182225
Title:
KVM ubuntu 12.04.2 guest installation with kickstart config fails
To manage notifications
> 3.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
This one works.
I've got to say that it's really annoying that every time I reboot my
system comes back with a degraded array:
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
> 4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
This kernel works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
Title:
make_request bug: can't convert block across chunks
Nope.
# uname -r
3.2.80-030280-generic
[18455.876945] md/raid0:md1: make_request bug: can't convert block across
chunks or bigger than 512k 1102518240 124
[18455.876959] md/raid1:md0: md1: rescheduling sector 1102518240
[18455.935138] md/raid1:md0: redirecting sector 1102518240 to other mirror:
So now that I have determined that this problem is fixed in the
newer/upstream kernel, what next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
Title:
make_request bug: can't convert block
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
Title:
make_request bug: can't convert block across chunks or bigger than
512k 2554601336 124
To manage
I got past it with --ignore-depends=kmod. Array is rebuilding right
now. We'll know in a couple of hours when the backups start whether the
kernel complains again or not. I will update then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
# dpkg -i
linux-image-4.6.0-040600rc4-generic_4.6.0-040600rc4.201604172330_amd64.deb
(Reading database ... 84773 files and directories currently installed.)
Unpacking linux-image-4.6.0-040600rc4-generic (from
.../linux-image-4.6.0-040600rc4-generic_4.6.0-040600rc4.201604172330_amd64.deb)
...
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632630/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
Title:
FWIW, I did use "ubuntu-bug linux" to create this ticket and the report
that was generated did contain all of the same things as the requested
"apport-collect 1568830" but they didn't all get attached to this
ticket. Seems like ubuntu-bug is a bit broken.
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632627/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632631/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632626/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632629/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632628/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632621/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632625/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568830
Title:
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632622/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632624/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1568830/+attachment/4632623/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I have a couple of RAID arrays with the following configuration:
/dev/md1:
Version : 1.2
Creation Time : Sat Dec 26 19:49:41 2015
Raid Level : raid0
Array Size : 1953524736 (1863.03 GiB
Public bug reported:
I have a couple of RAID arrays with the following configuration:
/dev/md1:
Version : 1.2
Creation Time : Sat Dec 26 19:49:41 2015
Raid Level : raid0
Array Size : 1953524736 (1863.03 GiB 2000.41 GB)
Raid Devices : 2
Total Devices : 2
Persistence :
There was support when this ticket was opened, 6 years ago and then not
a single thing happened with it (the ticket). It didn't even get
triaged.
No wonder I don't install Ubuntu any more and am converting what few
Ubuntu systems I have left to RedHat/CentOS.
--
You received this bug
Indeed! This bug was reported over 5 years ago and never got any more
attention than "is it working now?".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/640289
Title:
bluetooth-applet crashed with
@Christopher: I wasn't suggesting it should stay open. I was just
making a comment on how letting tickets stagnate until everyone gives up
and stops commenting is one sure way to close tickets.
I don't actually use Ubuntu any more because my experience when I last
did (and the reason I switched)
> That version is now outdated and no more supported
Waiting for the Ubuntu versions that bugs are filed against to just
become unsupported is one way to close tickets I suppose. Even tickets
that affect 243 people.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When I log out of my desktop I get some files in ~/.config/gnome-session
/saved-session/, pressumably the saving of my session so that it can be
restored on next login.
But on next login I get an error from gnome-session:
env: unrecognized option '--sm-client-id'
Try 'env
As you will notice, upstream closed this bug OBSOLETE with the
explanation:
Version 3.9 is an ancient unstable development version and not supported
anymore by GNOME developers. GNOME developers are no longer working on that
older version, so there will not be any bug fixes by GNOME developers
I no longer have that particular scanner nor do I use Ubuntu any
more[1]. I'm afraid the general bug stagnation has chased me away from
Ubuntu. This bug is a good example in fact. 6.5 years old now.
I guess you might as well just close this.
[1] desktops here are all Fedora now and servers
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297800
Title:
During upgrades, new certificates will be added. Please choose
Interesting. I don't recall ever [re-]setting that option. In any
case:
# debconf-show ca-certificates
ca-certificates/title:
* ca-certificates/enable_crts: ...
* ca-certificates/trust_new_crts: ask
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Sun, 2014-02-23 at 14:00 +, Pavel Malyshev wrote:
Four years passed...
What is the point to use LTS releases if such pure-Ubuntu bugs are not fixed
fore years?
I asked myself that same question a while ago. This was my
conclusion/solution:
$ cat /etc/issue
Fedora release 20
Public bug reported:
On current LTS (Precise) CUPS does not see printers advertised from CUPS
1.6 systems. Yes, I understand that the whole CUPS browse feature went
away in CUPS 1.6, but that means that current LTS has a functionality
hole/regression where CUPS 1.6 servers are concerned.
Fedora
Public bug reported:
It seems that while the libvdpau_nvidia library is available for nvidia-
current:
/usr/lib/nvidia-current/vdpau/libvdpau_nvidia.so.295.40
So such driver is available for nvidia-173-updates.
** Affects: nvidia-graphics-drivers-173-updates (Ubuntu)
Importance: Undecided
Wow. 2.5 year old bug report reporting that the currently packaged
version is no longer supported and still, no update to a newer version.
The version currently being packaged is over 7 years old!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So, will this be backported to LTS (precise) given that it fixes a known
security issue: CVE 2011-1755.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044039
Title:
badly needs an update
To manage
This bug was opened 2011-12-17 and it's now 1/3 way into 2013 and it
still exists on LTS/precise. Is this bug actually going to get fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905686
Title:
On 13-04-14 02:36 PM, Jeremy Bicha wrote:
This was apparently fixed in rhythmbox 2.98 which is available in Ubuntu
13.04.
Which doesn't really do LTS users much good. Can we have a fix
backported? Or even just the patch I supplied to this bug applied and
released?
TBH, getting a fix released
On 13-04-15 09:37 AM, Jeremy Bicha wrote:
Brian, if you want this fix for 12.04 LTS, you should look at the SRU
procedures:
https://wiki.ubuntu.com/StableReleaseUpdates
Like I said, *I* don't need a release of this in LTS. I have my local
patched copy and it's working just fine.
But other
On 13-04-15 11:04 AM, Jeremy Bicha wrote:
If you think this patch needs to be in Ubuntu 12.04, then please add
more specific information to the description than a pretty reproducible
segfault. I have no idea how common the crash is or how to reproduce it
myself. Thanks.
A segfault is a bug,
On 13-04-15 11:37 AM, Jeremy Bicha wrote:
What specific steps should we take to recreate this bug?
TBH, after all of this time, I don't recall.
I'm not at all saying that this bug shouldn't be fixed but honestly
there isn't enough information here for me to know what the bug is, so
it's
On 13-04-06 06:05 AM, Harald Glatt wrote:
Also the fact that this bug is two years old means the time span for
patience has long been left standing in the dust...
Patience for this bug to be fixed or patience with Ubuntu in general?
I know which one it is for me.
--
You received this bug
On 13-03-08 08:08 AM, Dmitry Shachnev wrote:
The patch is applied in gnome-keyring = 3.6.1,
Will that release go into the current LTS, 12.04? LTS is Long Term
Support so I would expect it to see bug fixes without requiring
individuals to file specific requests to have a bug fixed in it.
--
But I do have a 12.04 machine and I already submitted a patch (which
just came from upstream, not my patch) which fixes the problem on the
gnome-keyring shipped in 12.04 LTS. So really, I don't know why you are
proposing all of this rigmarole with backporting patches from g-k-r
3.6.1 and
Public bug reported:
I have a machine here that network boots (i.e. no resident hard disk,
pxeboot and nfsroot) and during it's boot it gets an ipv6 address on our
network but after it's booted, even though it still has an ipv6 network
configured (address and routing) any ipv6 packets sent to it
On 13-02-21 03:10 AM, ill wrote:
It's been a bug for two years now. It has a known, easy to implement
fix. If the ubuntu devs wanted to fix it they would have done it a long
time ago.
Indeed. It's this apathy for the real problems real users have that is
driving me away from Ubuntu. All new
(In reply to Dominik from comment #30)
Workaround:
Save attached message to folder (outside Thunderbird) and import it with the
addon ImportExportTools.
Well, yes. I think we all understand what the workaround is. But I
think we all agree that it's cumbersome at best. That's why we are
This problem exists in LTS 12.04. It causes machines coming back from
resume to use illegal IP addresses since it uses the address that it had
when it suspended and does not renew it on resume. This means if the
lease expired while suspended, it is against network and security
policies (of
Can we get a comment from the maintainer whether this patch is or will
(not) be applied and explanation as to why not if not?
This bug is percolating to many downstream consumers of this package.
It's not really reasonable to ignore it here and expect them all to fix
it themselves.
--
You
This is not wishlist. This is a bug.
It is absolutely invalid and wrong to just get onto a network and use an
address that was not either given to you manually by the network
administrator or obtained through some autoconfiguration tool such as
DHCP. Therefore, using an IP address after it's
So when will this bug be fixed in 12.04, the LTS release that is
supposed to be being supported currently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005504
Title:
[Upstream] Writer: Avery 5167
On 13-01-25 11:33 AM, Björn Michaelsen wrote:
fix is in 3.6 released with quantal
This doesn't, answer my question about 12.04 which is the current LTS
release and should be currently (and for quite a while still) supported.
When will this fix go into the current LTS?
--
You received this bug
On 13-01-25 12:20 PM, Björn Michaelsen wrote:
doesnt qualify: https://wiki.ubuntu.com/StableReleaseUpdates
Oh, so LTS == Long Term Support, except where it's not?
What's the point of LTS if users have to put up with a whole slew of
issues which doesnt qualify to be fixed for (at minimum) the 2
OK. So debate about LTS aside, back to the issue at hand: how am I as a
user of an LTS system supposed to be able to print labels given this
bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005504
It seems that http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.2.34-precise/, which 3.2.0-35-generic is apparently
based on has a number of issues with suspend/resume also.
Suspend/resume worked great in 2.6.38-13 (natty). Why has it gone all
to hell since then?
--
You received this bug
Public bug reported:
Simply doing an rmmod mceusb; modprobe mceusb triggers the crash in
the crash.txt attachment.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-generic 3.2.0.35.40
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
Uname: Linux 3.2.0-35-generic i686
Worth adding, all tests, on both kernels were done without any
binary/proprietary nvidia module loaded in the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098981
Title:
fails to resume
Public bug reported:
Latest precise kernel (and most previous ones) seem to fail to resume
from suspend on the hardware in this bug report. The mainline kernel at
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.31-precise/ doesn't
have this problem.
To suspend I am simply doing:
# echo mem
On 13-01-07 01:06 PM, Sebastien Bacher wrote:
Thanks Brian, do you have details on how to trigger the leak?
Nothing more specific than just sit back and wait. :-) Seriously, I
don't to anything special here. I keep SSH and PGP keys in my keyring
and ssh a lot and sign every outgoing e-mail.
This patch from upstream bug #684351 seems to fix the problem here for
me.
** Patch added: patch to fix memory leak
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1094496/+attachment/3474829/+files/10_bz_684351_memory_leak.patch
** Bug watch added: GNOME Bug Tracker #684351
Public bug reported:
I have what appears to be a pretty reproducible segfault here in 2.96.
If you need any more info, please don't hesitate to ask.
FWIW, I do have a full apport crash report but since apport sends whole
core files, which these days typically contain account credentials, I
This patch appears to fix the segfault in my local testing.
** Patch added: patch to fix segfault
https://bugs.launchpad.net/rhythmbox/+bug/1095270/+attachment/3472612/+files/git_bz690993.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On 13-01-02 11:18 AM, Mario Limonciello wrote:
I think the easiest solution for you would be to just comment out the
line in the cron job in /etc.
Yeah. I've done that in the meanwhile.
If we ever add something else to that
cron job it will do a conffile prompt on upgrade.
Right. Yet
Public bug reported:
In /etc/cron.weekly/mythtv-database there is:
/usr/share/mythtv/mythconverg_backup.pl
Which ends up producing an error:
ERROR: DBBackupDirectory not specified, stopped at
/usr/share/mythtv/mythconverg_backup.pl line 856.
run-parts: /etc/cron.weekly/mythtv-database exited
Public bug reported:
gnome-keyring-daemon gets killed here every few days due to it's memory
size exceeding the site imposed limit of 2GB per process. The ulimit of
course is not the problem as even with an unlimited setting, it would
just grow until it was killed by the OOM killer.
The real
No worries. I'm using linphone now. Have been for a long time now and
it's meeting all of my needs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005928
Title:
segfault in
I should add though, I've never had any large address books. I doubt
I've ever had more than a dozen entries in one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005928
Title:
segfault in
On 12-12-18 06:20 AM, Eugen Dedu wrote:
Please use ekiga 4.0.0, it fixes such issues.
That's not available (yet) and I guess won't be for a few years for LTS
users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 12-12-18 08:04 AM, Eugen Dedu wrote:
It is not about address book, but about the call history.
Ahhh. My mistake. I do suppose I could have had a long call history
given that this was a client on my home PBX.
Thanks much for the clarification.
--
You received this bug notification because
On 12-11-08 09:03 AM, zapman wrote:
That said, compiling gtkg from source is extremely easy. Just download the
source tarball from http://gtk-gnutella.sourceforge.net/, extract it say in
your home directory. Then open a terminal and type (or copypaste) the
following commands:
sudo
On 12-11-05 07:07 PM, Mario Limonciello wrote:
Well and actually that conflicts with what this commit says:
http://code.mythtv.org/trac/changeset/4a515ba3904bde90f7d9b64c5a7dc10e49a77dd8/mythtv
In theory 0.25 should be able to dump.
I'm using 0.25-fixes and not getting core dumps. I've
Public bug reported:
The mythtv-backend process needs to be run in a directory that it can
write into, ~mythtv for example. This is required so that a core file
can be collected if/when it segfaults -- like it has been doing here.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package:
I should add, look at the
modified.conffile..etc.init.mythtv.backend.conf.txt attachment for an
example of how to do this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073580
Title:
On 12-10-31 10:40 AM, Thomas Mashos wrote:
Shouldn't the crash file already be written to /var/crash/ ?
Interesting point. It doesn't seem to be the case however. Given this
segfault:
Oct 30 22:00:03 pvr kernel: [1937721.428406] mythbackend[13502]:
segfault at 28 ip 0620ef91 sp b2ffe140
Public bug reported:
Per the RedHat bug https://bugzilla.redhat.com/show_bug.cgi?id=754940
the same patch needs to be applied to the Ubuntu package. As you will
see from that RH bug report, the patch has been accepted upstream,
presumably for 2.4.13:
Public bug reported:
In the rsnapshot.conf that is included with rsnapshot-1.3.1-3, there are
paths as such:
#linux_lvm_cmd_lvcreate /path/to/lvcreate
#linux_lvm_cmd_lvremove /path/to/lvremove
Yes, I see they are commented out by default so somebody uncommenting
them ought to fix the /path/to/
** Package changed: ubuntu = rsnapshot (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064636
Title:
shouldn't use /path/to/...
To manage notifications about this bug go to:
Public bug reported:
While installing sasl2-bin I got the following message:
Setting up sasl2-bin (2.1.25.dfsg1-3ubuntu0.1) ...
update-rc.d: warning: saslauthd stop runlevel arguments (0 1 6) do not match
LSB Default-Stop values (1)
* Starting SASL Authentication Daemon saslauthd
...done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1059567
Title:
update-rc.d: warning: saslauthd stop runlevel arguments (0 1 6) do not
match LSB Default-Stop values (1)
To
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059567
Title:
update-rc.d: warning: saslauthd stop runlevel arguments (0 1 6) do not
match LSB Default-Stop values (1)
To manage notifications about
Public bug reported:
While installing sasl2-bin I got the following message:
Setting up sasl2-bin (2.1.25.dfsg1-3ubuntu0.1) ...
update-rc.d: warning: saslauthd stop runlevel arguments (0 1 6) do not match
LSB Default-Stop values (1)
* Starting SASL Authentication Daemon saslauthd
...done.
OK. So when will this be fixed? This bug has been open for a year and
3 months already. It was reported in the previous LTS and is still
present in the current LTS. That makes this bug over 2 years old.
Is having a crashing proxy server in two LTS releases acceptable? Is it
acceptable
OK. So when will this be fixed? This bug has been open for a year and
3 months already. It was reported in the previous LTS and is still
present in the current LTS. That makes this bug over 2 years old.
Is having a crashing proxy server in two LTS releases acceptable? Is it
acceptable
On 12-09-26 11:35 AM, Colin Watson wrote:
Could affected people retest with GRUB 2.00 in an up-to-date build of
Ubuntu 12.10, please?
Just a suggestion...
In general, I'd guess that most people are unable to do such things. I
don't know about anyone else, but I stick to stable releases for my
Public bug reported:
Squid 3.1.19 is failing with:
assertion failed: AclProxyAuth.cc:229:
authenticateUserAuthenticated(Filled(checklist)-auth_user_request)
This is reported and fixed upstream however the fix only went into 3.2
because it's too invasive for 3.1.
Thus, squid3 on Qunatal AND
Public bug reported:
There is a nasty performance issue with TB 15 which is fixed in 15.0.1
according to reports in
https://bugzilla.mozilla.org/show_bug.cgi?id=787348.
I have confirmed this by installing 15.0.1 from
https://launchpad.net/~mozillateam/+archive/thunderbird-stable.
This needs to
On 12-09-25 08:45 AM, Chris Coulson wrote:
Huh, I thought we'd already updated this???!! (at least, I uploaded it
to the security PPA 2 weeks ago).
Security PPA?
And I'm not sure why it's in the
thunderbird-stable PPA.
I would imagine because it's the latest stable release?
Using those
Just a guess, but failed build on ia64 and sparc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049428
Title:
Thunderbird 15.0.1 stable update tracking bug
To manage notifications about this bug
Public bug reported:
Squid 3.1.19 is failing with:
assertion failed: AclProxyAuth.cc:229:
authenticateUserAuthenticated(Filled(checklist)-auth_user_request)
This is reported and fixed upstream however the fix only went into 3.2
because it's too invasive for 3.1.
Thus, squid3 on Qunatal AND
And still, a month and a half later, not even a triage of this bug.
I guess it might be time to move on to a new distro. Ubuntu seem like
they have better things to do than fix bugs that seem to continue on
from one release to another.
In any case, if I remove all of my LVM snapshots this
And here's a patch that restores the behaviour.
** Patch added: fix sm.d/ dir usage
https://bugs.launchpad.net/ubuntu/+source/jabberd2/+bug/1043637/+attachment/3283702/+files/30sm.patch
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Jabberd2 has fixed a number of bugs in 2.2.15:
https://bugs.launchpad.net/jabberd2/+bug/899284
https://bugs.launchpad.net/jabberd2/+bug/374687
It would be very nice to see an update in Ubuntu Linux that reflects
this progress. If I am reading
Public bug reported:
The jabberd2 package includes an sm.d subdirectory of /etc/jabberd2/
where one is suppose to be able to configure additional realms/domains
to be serviced by the jabberd2 instance. This directory is completely
ignored by the current startup scripts. Pity.
** Affects:
Public bug reported:
I have installed:
flashplugin-installer:
Installed: 11.2.202.238ubuntu0.12.04.1
Candidate: 11.2.202.238ubuntu0.12.04.1
But when I run:
$ sudo dpkg-reconfigure flashplugin-installer
And hit return at the Location to the local file: prompt, leaving the
input empty so
1 - 100 of 1481 matches
Mail list logo
