The source package cyrus-sasl2-heimdal needs the same patch as cyrus-
sasl2 (0050_sasl_encode64_term), for the same reason.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2009-0688
** Changed in: cyrus-sasl2-heimdal (Ubuntu)
Status: New => Confirmed
--
Dependencies out
Public bug reported:
Observed using the binary sextractor package on Ubuntu hardy i386:
some columns in the object catalog end up containing only zeros, an
incorrect result for the input data supplied.
To reproduce, take a FITS file and run it through sextractor. The problem can
be reproduced u
Public bug reported:
Binary package hint: python-central
Sometime between versions 0.5.12 (Debian etch) and 0.6.7ubuntu0.1 (hardy),
python-central was changed
to store a package manifest in /usr/share/pyshared-data/ and to use the
information in that file to create
the necessary symlinks at pkg
Public bug reported:
This bug was fixed in Debian's a2ps 1:4.13b.dfsg.1-0.2, patch
14_lp_lpr_workaround.dpatch.
The issue is that a2ps-lpr-wrapper expects -d, not -P, to indicate the
printer name, and that the expansion of @LPR_QUEUE_OPTION@ depends on
the configuration of the system on which the
Public bug reported:
Binary package hint: linux-source-2.6.12
The patch
kernel-exit_CVE-2005-3805.dpatch
reads in part:
if (group_dead)
+ exit_itimers(tsk->signal);
acct_process(code);
exit_mm(tsk);
Either the acct_process(code); line is in
** Bug watch added: Debian Bug tracker #420132
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420132
** Also affects: ekiga (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420132
Importance: Unknown
Status: Unknown
--
ekiga hangs after x server restart
https://bug
I believe I can reproduce this in Debian 4.0 (and in Ubuntu 6.06). I
didn't have to actually zap my X server; just closing the ekiga window
with Alt+F4 is enough to leave the instance running in the background.
It will start spinning at 100% CPU after logout.
--
ekiga hangs after x server restart
Public bug reported:
Binary package hint: lftp
Judging from the stack trace, this bug is distinct from #75304 and
#82394.
Running Ubuntu 6.06 LTS, lftp 3.4.0-1, i386.
To reproduce:
$ lftp http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/1.0.8
lftp releases.mozilla.org:/pub/mozilla.org/
Reproducible with lftp 3.4.0-1 on Ubuntu 6.06 LTS i386. I used
file:///tmp/ as the URL, got:
Program received signal SIGSEGV, Segmentation fault.
0x0809e5a9 in StringSet::Empty ()
(gdb) bt
#0 0x0809e5a9 in StringSet::Empty ()
#1 0x08091fc9 in DirList::~DirList ()
#2 0x080cbc4e in LocalDirList::
I also find it the current lack of flexibility highly inconvenient.
However, none of the alternatives proposed in the comments above really
cut it as far as I'm concerned. Here is how I'd like to be able to set
up our desktops (users' home directories are on network shares and have
quota imposed on
*** This bug is a duplicate of bug 1315020 ***
https://bugs.launchpad.net/bugs/1315020
** This bug has been marked a duplicate of bug 1315020
PDF.js prints blank pages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
This issue affects OpenAFS 1.6 series releases prior to 1.6.1pre3. It was
reported upstream as, e.g.,
https://rt.central.org/rt/Ticket/Display.html?id=130361
and addressed in a series of patches, the most recent of which appears to be
http://git.openafs.org/?p=openafs.git;a=c
** Tags added: oneiric precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975838
Title:
OpenAFS 1.6 client can flood file servers with duplicate NAT ping
traffic
To manage notifications about
Public bug reported:
The fileserver component of OpenAFS 1.6.0 (and prereleases) is known to corrupt
users' files under certain conditions, some of which are described in the
upstream bug report
https://rt.central.org/rt/Ticket/Display.html?id=130295
[Impact]
Has been observed to cause loss of
Public bug reported:
Seen in lucid after the latest kernel ABI upgrade to 2.6.32-41:
$ aptitude search --disable-columns ~i~Dlinux-image-2.6.32-40-generic
i linux-image-generic - Generic Linux kernel image
$ aptitude show linux-image-generic
Package: linux-image-generic
State: installed
Automat
* Robert Ancell [2014-07-08 04:27:34 -]:
> It's not clear if the problem is the way we are using PAM in LightDM
> (i.e. insufficient/wrong information for pam-krb5 to do the right thing)
> or an assumption by pam-krb5 that is not occurring.
pam_krb5 needs to be told the name of the credentials
The description of this bug is incomplete, so I can't be sure that the
root cause is the same in my case as for the original reporter. Anyway,
here goes:
I'm seeing this on an AMD family 15 CPU. If I try to run mcelog
--foreground by hand, I get the following output:
mcelog: AMD Processor family
My earlier patch solves the problem for AMD family 15, but clearly not for
family 16 and newer. For a complete fix one will need to modify the init
script. If the CPU is unsupported, both daemon and trigger mode should be
disabled.
It may be useful to add an --is-cpu-supported command-line option
* Sergio Gelato [2014-08-22 07:29:32 -]:
> I'm now testing my one-line patch from comment #5 on top of 3.2.0-67.101
> (amd64, generic kernel flavour). So far it doesn't seem to make things
> worse, but since I don't have a sure-fire way of triggering the bug it
&
Public bug reported:
/usr/share/gnome-session/sessions/cairo-dock.session lists gnome-
settings-daemon (on trusty; may be unity-settings-daemon for some
releases of Ubuntu) as a required component. This is a real requirement:
when gnome-session-bin is installed but gnome-settings-daemon isn't,
att
I'm seeing the same problem (on multiple systems), and have been looking
at the lightdm and unity-greeter log files in an attempt to understand
what is going on. Some additional observations:
* I see three processes survive the termination of the greeter session:
init (aka Upstart), indicator-soun
* Matthieu Baerts [2015-08-06 11:55:05 +]:
> Yes, you are right! The problem is that we cannot simply add
> gnome/unity-settings-daemon as required component because it will force
> installing almost all GNOME/Unity packages on other sessions (e.g. it can be
> annoying for KUbuntu users).
>
* Matthieu Baerts [2015-08-06 14:46:00 +]:
> Yes, it's true but on the other hand, a KDE user doesn't need and doesn't
> want all GNOME specific packages just to have the dock.
That KDE-only user doesn't need /usr/share/gnome-session/. Splitting off
cairo-doc.session to a package she doesn't
The system where this was observed had stray /etc/rc*.d/*autofs symlinks
in place. Not sure why these weren't removed by autofs.postinst on
upgrade to trusty, but I've now removed them. I assume this is a
sufficient solution to the problem.
** Changed in: autofs (Ubuntu)
Status: New => Inva
We've seen this too (on Ubuntu T). It started happening immediately
after the upgrade to Firefox 36. Other web browsers are unaffected;
e.g., if I set my preferred web browser to Lynx and click on a URL in
Thunderbird the link is being followed.
--
You received this bug notification because you
Public bug reported:
On Ubuntu 12.04, when running /usr/bin/evince-thumbnailer on a .dvi file
that references a font for which there is no PK file on the system yet,
AppArmor blocks the execution of /usr/share/texmf/web2c/mktexnam etc.
Here are sample audit log messages:
[ 5720.378549] type=1400
Public bug reported:
Architecture: amd64
Version: 7.2+dfsg-4
Description:Ubuntu 14.04.3 LTS
Release:14.04
To reproduce:
1) /usr/bin/ds9 -unix_only &
(Note: the -unix_only is not required in order to reproduce the bug,
it's just more secure to run ds9 that way; I get the same symptom
* Ole Streicher [2015-11-20 14:17:12 +]:
> I have no IRAF to test; could you check whether this still appears on
> the 7.4 beta releases? And/or with the version downloaded from upstream:
> http://ds9.si.edu/archive/source/ds9.7.2.tar.gz
It doesn't happen with the upstream 7.2 binary
(http://d
Update: dropping the two hunks of debian/patches/iis.patch that modify
iis/xim.C has cured the symptoms for me (on amd64). So I was *almost*
right in my conjecture that this bug and Debian #805641 might have the
same root cause. The bugs are not the same (the problem here in
7.2+dfsg-4 is that the
Public bug reported:
Starting with Ubuntu kernel 3.13.0-44.73, the system spuriously reboots
instead of powering off. Kernels up to 3.13.0-43.72 are not affected.
The problem is 100% reproducible. It has also been mentioned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346269/comments/1
This problem does not manifest itself in log files. The relevant
hardware information (lspci output) is already attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504003
Title:
Regression: spu
** Attachment removed: "lspci -vvvnn output on EliteBook 850 G1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504003/+attachment/4488282/+files/lspci-vvvnn.log
** Attachment added: "lspci -vvvnn output on HP EliteBook 850 G1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/15
* Christopher M. Penalver [2015-10-09 09:45:00 +]:
> Sergio Gelato, please perform the apport-collect as previously
> requested.
I tried. apport-collect refused to run, asking me to install python-apport.
I did that. apport-collect still refused to run, with the same request.
I will
Frank: I think it's better to file a new bug about this. Do include the
actual log message. I'm looking at the source code for 3.13.0-66.108 and
the fix is still in place, so it can't be *exactly* the same problem as
before.
--
You received this bug notification because you are a member of Ubuntu
unity-greeter has code to kill upstart, but for some reason this isn't
being executed. My best guess is that unity-greeter often (if not
always) dies before it exits the GTK main loop. Does it receive a second
SIGTERM, or a SIGPIPE? (When lightdm says "Stopping display server, no
sessions require i
Public bug reported:
Symptom: on a fresh wily install in a PV virtual machine under Xen,
systemd's boot.mount action fails. /boot is on /dev/xvda1, other
filesystems (including /) are on LVM and get mounted OK [after a manual
"vgchange -ay" at the (initramfs) prompt, but that's a different bug].
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374008
Title:
update-grub causes error messages when accessing extended partition
To manage notifications about this bug go to:
ht
Public bug reported:
The symptoms for this bug are very similar to those of #1396213: booting
(a freshly installed wily VM) drops me to the (initramfs) prompt because
the root filesystem (root=/dev/mapper/VG-root) cannot be found. Typing
"vgchange -a y; exit" at the (initramfs) prompt allows the b
This problem went away when I added udev_log="debug" to
/etc/udev/udev.conf and ran update-initramfs -u. (Aside: someone more
knowledgeable please update the advice on
https://wiki.ubuntu.com/DebuggingLvm.)
Here is an almost-minimal sequence:
1) do a fresh install.
2) reboot into the new system.
Upstream git commit bb5c512de22eeb7464f120a01fd1d59e7a4bbb7b addresses
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467151
Title:
60-persistent-storage.rules fails to create by-uuid li
Public bug reported:
I've installed precise in virtual machines running on top of the Xen 4.0
hypervisor (with a Debian squeeze dom0).
In both i386 machines (running 3.2.0-23-generic-pae #36-Ubuntu) and amd64
machines (with 3.2.0-23-generic #36-Ubuntu), "facter is_virtual" prints out
"false" an
Public bug reported:
I've installed precise in virtual machines running on top of the Xen 4.0
hypervisor (with a Debian squeeze dom0).
In both i386 machines (running 3.2.0-23-generic-pae #36-Ubuntu) and amd64
machines (with 3.2.0-23-generic #36-Ubuntu), "facter is_virtual" prints out
"false" an
** Attachment added: "xen-detection-fix"
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/980291/+attachment/3055752/+files/xen-detection-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9802
*** This bug is a duplicate of bug 980291 ***
https://bugs.launchpad.net/bugs/980291
** This bug has been marked a duplicate of bug 980291
In Xen domU, "facter virtual" prints "physical"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
* Julian Wiedmann [2012-05-10 22:29:19 -]:
> You're probably missing the rpcsec_gss_krb5 module. Try installing the
> linux-image-extra-virtual package.
Indeed that does the trick.
Now a couple of questions:
1) On what basis was rpcsec_gss_krb5 relegated to linux-image-extra-virtual
while au
* Jonathan Sahagun [2016-01-29 12:51:08 +]:
> In this file:
> /etc/xdg/xdg-xubuntu/lightdm/
You probably mean /etc/xdg/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf
.
> In line 27, in a default installation, it reads:
> show-indicators=power;~session;~language;~a11y;~power;
>
> Remove the fir
Silly me, I had overlooked the fact that we aren't using the same
greeter. I've got [SeatDefaults]greeter-session=unity-greeter in
/etc/lightdm/lightdm.conf. So of course your solution didn't work for
me. (I need to give users a choice of desktop sessions, and found unity-
greeter to be better at r
> This is a glaring red sign that neither lightdm nor upstart are the
> appropriate packages for this issue, but lightdm-gtk-greeter is.
That still doesn't explain how I'm getting the problem with unity-
greeter. There may be more than one bug at play here. Maybe my issue is
better tracked by bug
* ScHRiLL [2014-10-02 14:01:59 +]:
> Same error with new kernel. It was fine and working without a hick up
> and today the same issue reverted. 16:01:16 up 6 days
Please check changelog.Debian.gz before jumping to conclusions. The fix is
not in #103 because it was committed too late in the cyc
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348670
Title:
BUG: unable to handle kernel NULL pointer dereferen
I've upgraded the OS on the affected computer to trusty and found that
the problem is still present in trusty's version of nux. Same symptoms,
and my patch still applies.
** Tags added: precise trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
tag -patch
done
* Sergio Gelato [2014-10-07 06:27:49 +]:
> I've upgraded the OS on the affected computer to trusty and found that
> the problem is still present in trusty's version of nux. Same symptoms,
> and my patch still applies.
I'll take that back: the patch
I can't seem to persuade apport to upload my crash file for this bug, so here
is what I see as the gist of it.
The crash is due to the method nux::IOpenGLShaderProgram::Begin() being
invoked on a null object. It occurs while trying to read field _OpenGLID,
and the failing instruction (i386) is
Public bug reported:
An NFSv4 client running kernel 3.13.0-44-generic #73-Ubuntu (amd64) suddenly
started spewing
nfs4_schedule_state_manager: kthread_run: -12
log messages at an average rate of 2.65 kHz. It did not stop until I rebooted
it.
At the very least that message needs to be rate-li
Logs too big for inclusion (the problem was log flooding). Also, they
would be missed by apport-collect because /var had been filled by an
earlier, not necessarily related, problem; the only full copy of the
logs is on a remote syslog server which does not run Ubuntu.
** Changed in: linux (Ubuntu)
So far, this particular symptom has been seen exactly once. The host it
was observed on was reinstalled from scratch with trusty a few weeks ago
following a hard disk failure, so no dist-upgrade involved. I did some
NFS-client-related tuning on this and many other machines this week so
it's conceiv
Public bug reported:
Based on the version of apparmor in trusty-updates:
Various profiles grant permissions for files in @{HOME}/.cache/. This is
only sufficient as long as one hasn't set the environment variable
XDG_CACHE_HOME to point somewhere else. (Use case: store caches locally
when home di
This is most likely a duplicate of #1423151 but it's hard to be certain
since the dkms build log is missing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1419907
Title:
package openafs-client 1.6.7
This is due to the backport of a kernel change:
move d_rcu from overlapping d_child to overlapping d_alias
to 3.2.0-76.111 and 3.13.0-46.*.
The OpenAFS package in Debian sid (1.6.10-4) has the necessary fixes. If
you want to cherry-pick them, try the patches I'll attach shortly.
--
You receive
** Patch added: "Part 1 (upstream) patch for this problem"
https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1423151/+attachment/4325259/+files/11642.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Patch added: "Part 2 (additional backporting fixes)"
https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1423151/+attachment/4325260/+files/11642%2B1.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Changed in: openafs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423151
Title:
openafs-modules-dkms 1.6.7-1: openafs kernel module failed to build
To m
Public bug reported:
autofs 5.0.7-3ubuntu3.1 installs *both* /etc/init/autofs.conf and
/etc/init.d/autofs. (One wonders what this duplication is needed for.)
It is apparently possible for /etc/init.d/autofs start to be run before
Upstart decides to act on /etc/init/autofs.conf. When this happens
Public bug reported:
I have an HP Color LaserJet Enterprise CP4525 with firmware 07.164.1,
which supports PDF files natively (@PJL LANGUAGE=PDF), and a print
server running Debian 7 (cups-filters 1.0.18 and its pdftopdf, and a
PDF-enabled PPD).
I have been given a PDF file (from pdflatex) that us
Public bug reported:
First seen after upgrading from precise to trusty, reproducible with
both trusty (3.13.0-40) and backported utopic (3.16.0-25) kernels on the
following hardware/BIOS: LENOVO 963673G/LENOVO, BIOS 2QKT29AUS
07/29/2008 . The information that follows is mostly from booting 3.13.0
I'm unable to run apport-collect but the bug description already
contains detailed information from the logs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
* Christopher M. Penalver [2014-11-27 20:21:56 +]:
> Sergio Gelato, could you please specify why exactly you cannot run the
> apport-collect?
The authorization page doesn't work in my default browser (lynx);
I get an error page after authentication.
I've tried opening it in Fi
I'm not aware of any activity on this since Robert Ancell's comment #4
indicating that a proper fix might require extensive refactoring (too
extensive for Ubuntu T?). As a workaround I've added an Upstart
configuration file to run krenew in every user's session; it's as simple
as
start on xsession
* Brian Murray [2014-06-25 18:54:46 -]:
> Sergio - could you provide a test case which is part of the Stable
> Release Update process so that we can get this fixed in 14.04?
Let me try. The problem manifested itself spontaneously in my production
environment so I'm not sure exactly which ingre
Public bug reported:
As already noted by Brian Knoll in
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/24
lightdm 1.10.1-0ubuntu1 uses an inappropriate credentials cache, /tmp/krb5cc_0,
when refreshing Kerberos credentials on screen unlock.
I couldn't find the new bug R
Public bug reported:
Seen in trusty on initial installation of a new-style *-el package:
ERROR: is broken - called emacs-package-install as a new-style
add-on, but has no compat file.
Unpacking () ...
The package does have a compat file. I believe that the error message is
issued because the
* Tim Gardner [2014-05-13 19:04:45 -]:
> Marking verification-done-trusty.
>
> dpkg-deb --contents linux-image-3.13.0-26-generic_3.13.0-26.48_amd64.deb
> |grep rpcsec_gss_krb5
> -rw-r--r-- root/root 50260 2014-05-07 18:38
> ./lib/modules/3.13.0-26-generic/kernel/net/sunrpc/auth_gss/rpcse
Public bug reported:
Very occasionally powernapd runs away on me and starts using almost 100%
of available CPU cycles. I'm running version 2.17-0ubuntu2 on i386,
Ubuntu 12.04.4. The hardware is a Fujitsu Siemens LifeBook S7020 with
BIOS version 1.05.
The last two entries in /var/log/powernap.log
Public bug reported:
pbuilder version 0.215ubuntu7, currently in both trusty and utopic, still has
DISTRIBUTION=saucy
in its /usr/share/pbuilder/pbuilderrc . While easy to work around, this is
inelegant.
Maybe the default should be something like $(lsb_release -s -c) ? I'm
not sure it's safe to
… OK for Ubuntu; Debian would likely end up with DISTRIBUTION=sid no
matter what, which is also inappropriate for testing/stable/oldstable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316423
Title:
The problem here is that rpcsec_gss_krb5 is in linux-image-extra, not in
linux-image. As a result, if one installs the -virtual kernel flavour
that module is missing.
The problem still exists in trusty (linux-
image-{,extra-}3.13.0-24-generic). It's annoying since Kerberized NFS is
a perfectly nor
Public bug reported:
I've seen this happen twice in the last 8 days on an NFS server running
Ubuntu precise and kernels 3.2.0-65.98-generic (on the first occasion)
and 3.2.0-67.101-generic (the second time), amd64. This never happened
before in several months of operation; until 2014-07-01 this se
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348670/+attachment/4162784/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348670
T
*** This bug is a duplicate of bug 769527 ***
https://bugs.launchpad.net/bugs/769527
** This bug has been marked a duplicate of bug 769527
Missing rpcsec_gss_krb5 module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Can't run apport-collect on this server.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348670
Title:
BUG: unable to handle kern
* Sergio Gelato [2014-07-25 14:23:03 -]:
> Could this be related to the following entry in the changelog
> for 3.2.0-65.98?
>
> * NFSD: Call ->set_acl with a NULL ACL structure if no entries
> - LP: #1328154
Yes, I think that's it. That change allows posix_state_
** Bug watch added: Debian Bug tracker #754420
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754420
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754420
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
I'm now testing my one-line patch from comment #5 on top of 3.2.0-67.101
(amd64, generic kernel flavour). So far it doesn't seem to make things
worse, but since I don't have a sure-fire way of triggering the bug it
may take a while to get experimental confirmation that it cures the issue.
(I'm reas
* Michiel [2014-08-07 10:58:29 -]:
> Any hints at a workaround in the meantime? It's especially nasty since a
> dead NFS server locks up the clients completely.
I'd say either test my suggested patch (I'm on holiday and haven't gotten
around to testing, but since it only modifies the code path
* Sebastien Bacher [2014-01-08 16:57:52 -]:
> Thanks for your bug report. Could you add an example for such dvi file?
I cen try and construct one that reproduces the issue on my system, but
there is no guarantee that the same choice of font will reproduce the
problem somewhere else: that depen
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365869
Title:
After upgrade to 3.13.0-35.62, rpc.gssd complains abo
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348670
Title:
BUG: unable to handle kernel NULL pointer dereference
** Bug watch added: Debian Bug tracker #738927
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738927
** Also affects: mcelog (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738927
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
I've now implemented and tested (on AMD families 15 and 16) the solution
I suggested in comment #4. The patch is in two parts: one for the
upstream source code, to be dropped into debian/patches/, and a new
version of debian/mcelog.init to take advantage of the new feature.
** Patch added: "Implem
** Attachment added: "New version of the init file using --is-cpu-supported"
https://bugs.launchpad.net/debian/+source/mcelog/+bug/1279293/+attachment/4207327/+files/mcelog.init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
* Joseph Salisbury [2014-09-03 19:46:04 +]:
> Also, has the patch in comment #12 been sent upstream for inclusion in
> the mainline/stable kernel?
The affected code was refactored out of existence in kernel 3.14. As such,
my patch is inapplicable to 3.14 and later. The replacement set_acl meth
I'm a bit confused by Tim's changes in #16. The bug affects kernels up
to and including 3.13 (trusty). I'll take his word that it also affects
lucid, but what does a status of Invalid mean?
** Tags removed: regression-update
** Tags added: regression-updatekernel-fixed-upstream
** Tags removed: r
Public bug reported:
The following changes in 3.13.0-35.62:
* sunrpc: create a new dummy pipe for gssd to hold open
- LP: #1327563
* sunrpc: replace sunrpc_net->gssd_running flag with a more reliable check
- LP: #1327563
* nfs: check if gssd is running before attempting to use krb5i auth
** Tags removed: fixed-in-upstream-kernel
** Tags added: kernel-fixed-upstream
** Description changed:
The following changes in 3.13.0-35.62:
- * sunrpc: create a new dummy pipe for gssd to hold open
-- LP: #1327563
- * sunrpc: replace sunrpc_net->gssd_running flag with a more reliable ch
Won't run apport-collect. (Not really needed for this particular bug.)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365869
Title
I've built, installed and tested the kernel described in comment #4. It does
what I expected it to do:
* file /run/rpc_pipefs/gssd/clntXX/info now exists;
* rpc.gssd no longer complains.
No adverse side effects so far.
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
I've just upgraded a client from precise to trusty. As part of that
upgrade, postgresql-client-9.1 was uninstalled and replaced with
postgresql-client-9.3. This broke the psql client's access to databases
that are listed in ~/.postgresqlrc as running version 9.1. If I run
psq
Public bug reported:
After upgrading from precise to trusty, I started seeing the following
error messages in the logs whenever there was Kerberized NFS activity:
Jun 17 08:02:43 hostname rpc.gssd[1021]: ERROR: GSS-API: error in
gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been
Version: 1:1.2.8-6ubuntu1.1 verified on trusty amd64.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331201
Title:
rpc.gssd: ER
I had to apply this change already in precise. (The issue affected me
because I set [LightDM]user-authority-in-system-dir=true in
lightdm.conf.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339727
T
1 - 100 of 117 matches
Mail list logo
