The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package has been published and the bug is being set to Fix Released
** Description changed:
This bug is for tracking the version to be filled upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated
Released to -security and -updates, including -meta.
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed = Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed = Fix Released
--
You received this bug notification because you
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package has been published and the bug is being set to Fix Released
** Description changed:
This bug is for tracking the version to be filled upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated
** Also affects: bamf
Importance: Undecided
Status: New
** Also affects: unity
Importance: Undecided
Status: New
** Visibility changed to: Public
** Changed in: bamf
Importance: Undecided = Critical
** Changed in: unity
Importance: Undecided = Critical
** Changed in:
This bug was fixed in the package ssldump - 0.9b3-4ubuntu1
---
ssldump (0.9b3-4ubuntu1) oneiric; urgency=low
* Configure --with-pcap-lib=/usr/lib/$(DEB_HOST_MULTIARCH).
Closes: #634526. LP: #832857.
-- Matthias Klose d...@ubuntu.com Tue, 13 Sep 2011 12:27:59 +0200
**
This bug was fixed in the package splat - 1.3.0-1ubuntu1
---
splat (1.3.0-1ubuntu1) oneiric; urgency=low
* Fix FTBFS with ld --as-needed. LP: #832844.
-- Matthias Klose d...@ubuntu.com Tue, 13 Sep 2011 12:36:50 +0200
** Changed in: splat (Ubuntu Oneiric)
Status:
*** This bug is a duplicate of bug 837803 ***
https://bugs.launchpad.net/bugs/837803
This bug was fixed in the package linux-mvl-dove - 2.6.32-218.36
---
linux-mvl-dove (2.6.32-218.36) lucid-proposed; urgency=low
* Release tracking bug
- LP: #837803
[ Paolo Pisati ]
This bug was fixed in the package linux-mvl-dove - 2.6.32-218.36
---
linux-mvl-dove (2.6.32-218.36) lucid-proposed; urgency=low
* Release tracking bug
- LP: #837803
[ Paolo Pisati ]
* Rebased to 2.6.32-34.76
[ Ubuntu: 2.6.32-34.76 ]
* Release Tracking Bug
- LP:
I've now got a setup similar to Adams, but even with the 3.0.0-11.17
kernel, I'm still seeing the problem. Took 14 good boots to get a bad
one though :) I'm testing with oneiric server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming bug on Oneiric. Workaround is to use the arista-transcode
CLI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814911
Title:
arista-gtk crashed with GError in setup_source(): Icon
This bug was fixed in the package linux-mvl-dove - 2.6.32-218.36
---
linux-mvl-dove (2.6.32-218.36) lucid-proposed; urgency=low
* Release tracking bug
- LP: #837803
[ Paolo Pisati ]
* Rebased to 2.6.32-34.76
[ Ubuntu: 2.6.32-34.76 ]
* Release Tracking Bug
- LP:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/842198
Title:
oneconf-service crashed with IOError in update(): [Errno 2] No such
file or directory:
*** This bug is a duplicate of bug 848783 ***
https://bugs.launchpad.net/bugs/848783
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #848783, so is being marked as such. Please
WhyteHorse, can you run the following commands in a terminal window:
sudo /usr/lib/cups/backend/dnssd
sudo /usr/lib/cups/backend/snmp
hp-makeuri 192.168.2.89
hp-probe -bnet -mmdns
hp-probe -bnet -mslp
If a command does not exit by itself, stop it with Ctrl + C, post the
output of all commands
Actually a problem in libfolks, reassigning
** Bug watch added: GNOME Bug Tracker #658631
https://bugzilla.gnome.org/show_bug.cgi?id=658631
** Also affects: empathy via
https://bugzilla.gnome.org/show_bug.cgi?id=658631
Importance: Unknown
Status: Unknown
** Project changed:
** Changed in: xsensors (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832850
Title:
xsensors version 0.70-1.1ubuntu2 failed to build in oneiric
To manage
Thanks for the advice on where to insert cupsenable and cupsaccept
steps.
As for encryption, I still don't see why we need to force its usage,
especially given how we'll be manipulating localhost at all steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: unity
Status: Confirmed = Invalid
** Changed in: unity (Ubuntu)
Status: Confirmed = Invalid
** Changed in: bamf
Status: Confirmed = Won't Fix
** Changed in: bamf
Status: Won't Fix = Fix Released
** Changed in: bamf (Ubuntu)
Status: Confirmed =
This bug was fixed in the package linux-mvl-dove - 2.6.32-218.36
---
linux-mvl-dove (2.6.32-218.36) lucid-proposed; urgency=low
* Release tracking bug
- LP: #837803
[ Paolo Pisati ]
* Rebased to 2.6.32-34.76
[ Ubuntu: 2.6.32-34.76 ]
* Release Tracking Bug
- LP:
I am unable to verify this, because kernel 3.0 is extremely unstable on
my ubuntu+1 host and it seems to be going from bad to worse with each
new kernel package uploaded to Oneiric. Since the kernel only manages to
remain on for a very short amount of time, I am unable to launch
ubuntu-bug linux
** Changed in: empathy (Ubuntu)
Status: Fix Released = Triaged
** Description changed:
Binary package hint: empathy
+
+ Issue still present in Oneiric.
In Karmic, Lucid Maverick, the text ~does not~ wrap when typing text
in a chat window. Instead, the window grows.
This
Ok, so now (after that my branch has been merged) this should have been
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/846441
Title:
Repeated indicators in unity-2d panel when second screen
In Oneiric (and maybe previous releases) this doesn't happen anymore,
closing.
** Changed in: cairo (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/414806
*** This bug is a duplicate of bug 845896 ***
https://bugs.launchpad.net/bugs/845896
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #845896, so is being marked as such. Please
Can somebody please verify whether or not this affects oneiric as well
so that we can move on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379382
Title:
gnome-screenshot (Alt-Printscreen)
Public bug reported:
Please sync lptools 0.0.1~bzr29-1 (universe) from Debian unstable (main)
Changelog entries since current oneiric version 0.0.1~bzr28-1:
lptools (0.0.1~bzr29-1) unstable; urgency=medium
* New upstream snapshot.
+ Fixes typo which broke lp-project-upload. LP: #845170
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848773
Title:
please cherry-pick savagefb regression fix for 3.0
To manage notifications about this bug go to:
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package splashy - 0.3.13-5.1ubuntu1
---
splashy (0.3.13-5.1ubuntu1) oneiric; urgency=low
* Remove the Debian hack for #297741. LP: #831285.
* Don't build with -Werror. Closes: #625406.
-- Matthias Klose d...@ubuntu.com Tue, 13 Sep 2011 12:41:01 +0200
I can replicate the bug with creating a root owned /rootfile and ln -s
/rootfile ~/.Xauthority. lightdm changes /rootfile then.
Writing ~/.dmrc uses g_file_set_contents() which is safe against symlink
attacks. However, it's still more robust to drop privileges instead of
chown()ing.
--
You
*** This bug is a duplicate of bug 838037 ***
https://bugs.launchpad.net/bugs/838037
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel
Upstream was a dupe, reassigning to actual issue
** Bug watch added: GNOME Bug Tracker #653599
https://bugzilla.gnome.org/show_bug.cgi?id=653599
** Changed in: empathy
Importance: Medium = Unknown
** Changed in: empathy
Status: Invalid = Unknown
** Changed in: empathy
Remote
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
** Description changed:
gnome-volume-control crashed while testing speakers.
I have the gdm welcome sound and login sound but after that, unable to
play any sound (gstreamer, aplay, ...)
the volume control crashes while testing speakers
- user@ubuntu:~$ aplay -l
+ user@ubuntu:~$
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
*** This bug is a duplicate of bug 833092 ***
https://bugs.launchpad.net/bugs/833092
Public bug reported:
Update request from 0.9.6 to 0.9.7. The newer release has a ~ 20% speed
increase for typical encoder settings, especially the real-time setting
used for videoconferencing.
ProblemType:
** Also affects: bamf
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848828
Title:
bamfdaemon crashed with SIGSEGV in
** Changed in: language-selector (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/713346
Title:
gnome-language-selector crashed with NotAuthorizedError in
** Changed in: libvpx (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/833092
Title:
[FFe] please sync libvpx (0.9.7.p1-1) from debian sid
To manage
Did this ever get fixed? The upstream patch with the helper was posted
to the mailing list in November 2009 and in the same thread it is
mentioned that the Ubuntu packaging would enable this by the time
Lucid/qemu-0.12-rc1 was released.
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
Okay, so... if I understand what you mean, that's what you did:
Index: metacity-2.34.1/src/core/window.c
===
--- metacity-2.34.1.orig/src/core/window.c 2011-09-13 12:37:46.240667605
+0200
+++ metacity-2.34.1/src/core/window.c
** Changed in: kernel-sru-workflow/verification-testing
Status: New = In Progress
** Description changed:
This bug is for tracking the 2.6.38-11.50 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package packeth - 1.6.5-1ubuntu1
---
packeth (1.6.5-1ubuntu1) oneiric; urgency=low
* Fix link order to list libraries after the objects that require them
(LP: #771125).
-- Colin Watson cjwat...@ubuntu.com Tue, 13 Sep 2011 11:46:02 +0100
** Changed
This bug was fixed in the package linux-mvl-dove - 2.6.32-218.36
---
linux-mvl-dove (2.6.32-218.36) lucid-proposed; urgency=low
* Release tracking bug
- LP: #837803
[ Paolo Pisati ]
* Rebased to 2.6.32-34.76
[ Ubuntu: 2.6.32-34.76 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux-mvl-dove - 2.6.32-218.36
---
linux-mvl-dove (2.6.32-218.36) lucid-proposed; urgency=low
* Release tracking bug
- LP: #837803
[ Paolo Pisati ]
* Rebased to 2.6.32-34.76
[ Ubuntu: 2.6.32-34.76 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
** Changed in: lptools
Status: New = Fix Released
** Changed in: lptools (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: lptools
Assignee: (unassigned) = Jelmer Vernooij (jelmer)
** Changed in: lptools (Ubuntu)
Assignee: (unassigned) = Jelmer Vernooij (jelmer)
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.24
---
linux-ti-omap4 (2.6.35-903.24) maverick-proposed; urgency=low
* Release tracking bug
- LP: #838037
[ Upstream Kernel Changes ]
* ipv6: make fragment identifications less predictable, CVE-2011-2699
-
Public bug reported:
hromium-browser crashed
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 15.0.871.0~svn20110904r99583-0ubuntu1~ucd1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
ApportVersion: 1.22.1-0ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848872
Title:
chromium-browser crashed with SIGSEGV in _XSend()
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848869
Title:
Gtk-Warning on shell
To manage notifications about this bug go to:
Public bug reported:
Running pavucontrol from the terminal exposes a number of warnings when
the locale is de_DE.UTF-8:
$ echo $LANG
de_DE.UTF-8
$ pavucontrol
(pavucontrol:20040): Gtk-WARNING **: Failed to set text from markup due
to error parsing markup: Fehler in Zeile 1, Zeichen 25: »« ist
*** This bug is a duplicate of bug 848873 ***
https://bugs.launchpad.net/bugs/848873
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #848873, so is being marked as such. Please
601 - 700 of 2935 matches
Mail list logo