** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270208
Title:
8086:422b [Dell Latitude E6520] linux-image-3.11.0-15-generic appears
The fix for this is to add the following to /etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=8
The problem was caused by the following commit, which disabled TX
aggregation by default on the "old" hardware managed by the iwldvm
driver (including our Intel 6300AGN):
https://git.kernel.
Duane, just click this link on this bug report page :)
http://i.imgur.com/wEuiOoZ.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131864
Title:
After Upgrade to Boost 1.53 Build Fails
To manage
** Changed in: unity-for-arch
Status: In Progress => 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/1131864
Title:
After Upgrade to Boost 1.53 Build Fails
To manage notifications
Progress
** Changed in: unity-for-arch
Assignee: (unassigned) => Xiao-Long Chen (cxl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131864
Title:
After Upgrade to Boost 1.53 Build Fails
To manage no
I've completed the bisect. The broken commit is
da27a24383b2b10bf6ebd0db29b325548aafecb4. The commit
47f531e8ba3bc3901a0c493f4252826c41dea1a1 mentioned before is *not*
broken (at least for my system). You can see this in my bisect log
linked below.
Broken commit: http://paste.kde.org/690824/raw/
B
I'm also doing a git bisect and reverting the two commits that Seth
mentioned does seem to solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1146988
Title:
linux 3.8.0.10-generic does
If I extract initrd.img-3.8.0-9-generic and initrd.img-3.8.0-10-generic
and "diff -Nru" them, there's is no difference (other than the newer
kernel modules, obviously).
I'm not sure what could be the problem. In the changelog, I see many USB
bug fixes and also some bug fixes for PRIME. I'm not boo
With this release, my laptop (Lenovo W520) no longer boots. The system
gets stuck in the initramfs stage, but does not hang (ie. caps lock
light works, Ctrl + Alt + Delete restarts, etc).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The Quantal and Raring versions of indicator-appmenu currently contain
libtool archives (/usr/lib/indicators3/7/libappmenu.la). I don't see any
mention of this in the changelog. I assume that it's not supposed to be
there.
Could we get this removed for the next release? Thank
Everything is fine now in Quantal, and Raring. Precise was never
affected.
** 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/1079938
Awesome, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Hi Timo, I've been searching the automake docs all day and I think I've
found something relevant.
According to https://www.gnu.org/software/automake/manual/html_node
/Standard-Directory-Variables.html if "--datadir=..." is not passed
(like in Ubuntu), then "@datadir@" is replaced with "${prefix}/s
Actually, I think it's sssd that's at fault for not being able to parse
debhelper's ./configure arguments, since pretty much every other project
using ./configure can. I'll see if I can come up with a patch for the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bu
Okay, I've found the real cause of the issue. It's due to some
differences between debhelper and rpmbuild:
**On Ubuntu:
Take a look at /usr/share/perl5/Debian/Debhelper/Buildsystem/autoconf.pm
(Screenshot: http://i.imgur.com/WozcJoe.png )
Notice how debhelper passes '\${prefix}' directly to ./co
Hello Adam,
The sssd in 12.04 was never affected since it's on the 1.8.x series.
Both 1.9.1-0ubuntu1.2 in Quantal and 1.9.3-0ubuntu2 in Raring still have
'${prefix}' in /usr/lib/python2.7/dist-packages/SSSDConfig/__init__.py
** Tags removed: verification-needed
** Tags added: verification-failed
Sorry, you're right. It came from the Canonical Qt5 PPA:
http://ppa.launchpad.net/canonical-
qt5-edgers/qt5-beta1/ubuntu/pool/main/w/wayland/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110982
Titl
Public bug reported:
Please rebuild GTK3 for the new wayland 1.0.5+git~20130130-1ubuntu1. The
new wayland *is not* binary compatible and will cause LightDM/GDM/any
GTK application to fail with:
symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined
symbol: wl_registry_interface
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103721
Title:
Enable virtualbox backend in raring
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Awesome, thanks!
I don't know if it'll be helpful, but I created a PPA with the vbox
backend enabled: https://launchpad.net/~cxl/+archive/libvirt/ The
package builds successfully in pbuilder :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Would it be possible to enable the virtualbox backend in libvirt in
raring? All that needs to be changed is adding "--with-vbox" to
debian/rules.
With the version of libvirt in raring, there is *no need* for virtualbox
to be installed while building anymore.
Thanks in advanc
Thanks a lot! I'll file a new bug about the virtualbox backend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103683
Title:
Merge libvirt 1.0.1 from Debian experimental
To manage notifications abo
Public bug reported:
Would it be possible to merge libvirt 1.0.1 from Debian experimental?
The 1.0.1 release fixes a few issues, such as setting up a NAT network
on a remote libvirt system. A few of the apparmor patches are accepted
upstream as well as a few other patches.
Also, the Debian packag
Public bug reported:
The Control + Alt + [Left + Up] key combination to switch to the top
left workspace is currently broken. Of the four combinations for
diagonal switching:
1. [_*_|___] -> Control + Alt -> [___|___]
[___|___] -> + [Down + Right] -> [___|_*_]
2. [___|_*_] -> Control + A
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098392
Title:
Sync 3.4.3 from Debian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yum/+bug/10
Public bug reported:
Version 3.4.3 is available in Debian Experimental:
http://packages.debian.org/experimental/yum Would it be possible to
merge this into Ubuntu? The current release is not very useful. It's too
old to create a chroot for any supported Fedora release.
** Affects: yum (Ubuntu)
Public bug reported:
This is not really a bug. The polkit developers have changed the way
rules are defined in version 0.107, so when Ubuntu updates to that
version, the attached rules file will need to be used (goes in
/usr/share/polkit-1/rules.d/). It's a direct translation of the unity-
greeter
Here is the exact error message: http://paste.ubuntu.com/1411155/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notification
The problem is that "${prefix}" taken litterally by the python file.
"ipa-client-install" with crash when configuring sssd because the path
cannot be found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I didn't know you had it done already...oops :)
As for the third change, I assumed that the .../krb5/ was the correct
path, since that's what the krb5 packaging creates:
https://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/raring/krb5/raring/view/head:/debian/libkrb5-3.dirs.in
--
You received t
I've created a patch that fixes this issue. It:
1. Removes leftover cdbs bits
2. Bumps compat version to 9, so "--libdir=/usr/lib/$(DEB_HOST_MULTIARCH)" is
not needed anymore
3. Fixes kerberos plugins path. Ubuntu uses /usr/lib/.../krb5/plugins/krb5/
instead of /usr/lib/.../krb5/plugins/libkrb5/
I've found the cause of the issue. The offending line is in
debian/rules: http://paste.ubuntu.com/1363982/
which causes this: http://paste.ubuntu.com/1363979/
I don't see ${prefix} or ${libdir} defined anywhere, which is probably
why this issue happens.
--
You received this bug notification bec
Ubuntu 13.04's package is also affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notifications about this bug go to:
h
Public bug reported:
Currently, "${prefix}" is showing up in /usr/lib/python2.7/dist-
packages/SSSDConfig/__init__.py, causing packages like freeipa to fail.
I'm not sure if any other files are affected.
Please fix Ubuntu 12.10 package. Thanks in advance!
** Affects: sssd (Ubuntu)
Importanc
Thanks for fixing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044836
Title:
Does not need to be built with gcc 4.6 anymore
To manage notifications about this bug go to:
https://bugs.launchpad.n
Indicator messages 12.10.4-0ubuntu1 seems to fix this :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796661
Title:
telepathy-indicator crashed with SIGSEGV in
g_simple_async_result_complete()
I'm not sure if it's related, but Thunderbird is crashing with the same
error for me: http://pastie.org/4900282
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796661
Title:
telepathy-indicator crashe
Thanks for merging the patch! This was my first code contribution to any
open-source software :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048348
Title:
Icon fallback code needed
To manage not
Hi Sam,
Thanks for the reply! You were right about the shared library. I'm
actually packaging for Fedora, which builds with
"-DBUILD_SHARED_LIBS:BOOL=ON" by default. When I build compiz manually,
all is fine.
My fault, sorry :)
--
You received this bug notification because you are a member of U
Sorry, I didn't know how to link the bug to the downstream packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044836
Title:
Does not need to be built with gcc 4.6 anymore
To manage notificat
By the way, gtk-window-decorator links with
libgtk_window_decorator_settings_notified_interface.so, which doesn't
get installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1042323
Title:
[FFE] Po
>From the CMakeLists.txt files, support for metacity themes seems to be
optional, but gtk-window-decorator fails to build when USE_METACITY is
undefined (ie. when metacity headers are not installed or if support is
explicitly disabled).
Here's the build log (built with CMAKE_VERBOSE_MAKEFILE so th
New patch for 1.99-21ubuntu2
** Patch added: "Patch for Grub 2 1.99-21ubuntu2"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/924622/+attachment/3023701/+files/ubuntu_no_smooth_boot_on_efi.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
@David: Thank you very much for the reply! Hopefully the Unity
developers agree. It would be very helpful for us packagers of Unity in
other distros :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884
I am also having this problem. The problem is reproducible in the latest
version of any distro. I've tried compiling the latest kernel and xorg
from git and problem still exists :(
I think you should rename the title of the bug to something like
"Touchpad and trackpoint glitches on Synaptics multi
*** This bug is a duplicate of bug 879858 ***
https://bugs.launchpad.net/bugs/879858
This bug was marked as a duplicate of 879858, but I don't think that
they're the same bugs. The other bug is about a kernel error when using
efibootmgr while installing GRUB EFI. This bug suggests a better com
The included patch disables the generation of the lines in grub.cfg for
Ubuntu's smooth boot feature. That's what currently preventing the boot
on UEFI systems.
I've created a PPA with grub2 version 1.99-17ubuntu1 with the patch
included: https://launchpad.net/~cxl/+archive/grub2-efi
Please test
** Patch added: "fix-ubuntumenuproxy-build.patch"
https://bugs.launchpad.net/bugs/945135/+attachment/2802839/+files/fix-ubuntumenuproxy-build.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945
Public bug reported:
The '043_ubuntu_menu_proxy.patch' patch causes the GTK2 build to fail
with:
In file included from gtkaccelgroup.c:39:0:
gtkalias.h:6241:18: error: 'ubuntu_gtk_menu_shell_activate_mnemonic' undeclared
here (not in a function)
This is reproducible in Ubuntu (11.10 and 12.04)
The patch was taken from György Balló's Arch Linux Unity repository:
http://sources.ayatana.info/gtk2-ubuntu-2.24.10-1.src.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945135
Title:
043_ubun
Great! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926440
Title:
Fails to build with new libdbusmenu (patch included)
To manage notifications about this bug go to:
https://bugs.launchpad.
Public bug reported:
Nautilus 3.3.5 in Ubuntu 12.04 contains the patch
16_run_in_gnome_unity.patch. It's pretty pointless, since the original
file already contains what the patch adds (which can also be seen in the
patch).
Redundant "OnlyShowIn=GNOME;Unity": http://paste.ubuntu.com/843362/
** Af
** Patch added: "Build fix"
https://bugs.launchpad.net/bugs/926973/+attachment/2715470/+files/build_fix_with_libdbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926973
Title:
No long
Public bug reported:
With the new libdbusmenu, the /usr/include/*/libdbusmenu-gtk3
directories were renamed to libdbusmenu-gtk. This is true for Ubuntu
12.04 and Arch Linux. The attached patch fixes the '#include' lines to
reflect this change.
** Affects: indicator-application (Ubuntu)
Impor
** Patch added: "Build fix"
https://bugs.launchpad.net/bugs/926971/+attachment/2715469/+files/build_fix_with_libdbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926971
Title:
No long
Public bug reported:
With the new libdbusmenu, the /usr/include/*/libdbusmenu-gtk3
directories were renamed to libdbusmenu-gtk. This applies with the
libdbusmenu-gtk3 versions found in Ubuntu 12.04 and Arch Linux. The
attached patch fixes the '#include' lines in the source code.
** Affects: appme
** Patch added: "Build fix"
https://bugs.launchpad.net/bugs/926469/+attachment/2712448/+files/build_fix_with_libdbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926469
Title:
Fails t
Public bug reported:
With recent versions of libdbusmenu, the /usr/include/*/libdbusmenu-gtk3
directories were renamed to libdbusmenu-gtk (for both GTK 2 and 3). This
applies to both Ubuntu 12.04 and Arch Linux. A patch that fixes the
'#include' lines is attached.
** Affects: indicator-appmenu (U
** Patch added: "Build fix"
https://bugs.launchpad.net/bugs/926462/+attachment/2712435/+files/build_fix_with_libdbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926462
Title:
Fails t
Public bug reported:
The libdbusmenu include directories have been renamed from /usr/include
/*/libdbusmenu-gtk3 to libdbusmenu-gtk. This applies to Ubuntu 12.04 and
Arch Linux. The attached patch fixes the '#include' lines in the source
code.
** Affects: indicator-messages (Ubuntu)
Importan
** Patch added: "Build fix"
https://bugs.launchpad.net/bugs/926458/+attachment/2712422/+files/fix_build_with_libdbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926458
Title:
Build f
Public bug reported:
The new libdbusmenu renamed /usr/include/*/libdbusmenu-gtk3 to
libdbusmenu-gtk, causing the '#include' lines to fail. This is
reproducible in Ubuntu 12.04 and Arch Linux. The attached patch fixes
this issue.
** Affects: indicator-session (Ubuntu)
Importance: Undecided
** Patch added: "Fix build"
https://bugs.launchpad.net/bugs/926440/+attachment/2712390/+files/fix_build_with_libdbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926440
Title:
Fails t
Public bug reported:
The /usr/include/*/libdbusmenu-gtk3 directories were renamed to
libdbusmenu-gtk for GTK 2 and GTK 3 versions of libdbusmenu. This is
reproducible in both Ubuntu 12.04 and Arch Linux. The attached patch
fixes the issue.
** Affects: indicator-sound (Ubuntu)
Importance: Und
** Patch added: "Build fix"
https://bugs.launchpad.net/bugs/926429/+attachment/2712341/+files/fix_build_with_dbusmenu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926429
Title:
No longer
Public bug reported:
The build fails due to the /usr/include/*/libdbusmenu-gtk3 directories
being renamed to libdbusmenu-gtk (even in GTK 3 packages). This is
reproducible in Ubuntu 12.04 and in Arch Linux. A patch is attached to
fix the '#include' lines in the source code.
** Affects: indicator-
** Description changed:
Ubuntu 11.10 and Ubuntu 12.04 have an issue where neither the boot
messages nor Plymouth are shown. This is due to GRUB2 not having a font
to load (unicode.pf2) and therefore update-grub doesn't generate needed
sections in the grub.cfg file.
Here's a diff of De
** Description changed:
Ubuntu 11.10 and Ubuntu 12.04 have an issue where neither the boot
messages nor Plymouth are shown. This is due to GRUB2 not having a font
to load (unicode.pf2) and therefore update-grub doesn't generate needed
sections in the grub.cfg file.
Here's a diff of De
Public bug reported:
Ubuntu 11.10 and Ubuntu 12.04 have an issue where neither the boot
messages nor Plymouth are shown. This is due to GRUB2 not having a font
to load (unicode.pf2) and therefore update-grub doesn't generate needed
sections in the grub.cfg file.
Here's a diff of Debian's and Ubun
Public bug reported:
With more UEFI based systems now, it's pretty important that GRUB 2 is
installed correctly on those systems.
The way Ubuntu installs GRUB 2 on UEFI systems puts the GRUB 2
configuration files in EFI_PARTITION/efi/ubuntu/grub.cfg. I'm not sure
how it actually is installed, but
This bug still exists in Ubuntu 11.10 and will continue to exist in
future Ubuntu versions because, as far as I know, this is a bug in the
nVidia blob that only nVidia can fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
It looks like those are the default settings for the synaptics Xorg
driver (xf86-input-synaptics upstream or xserver-xorg-input-synaptics in
Ubuntu). In the latest version of xf86-input-synaptics (1.50),
src/synaptics.c contains the following lines:
pars->tap_time = xf86SetIntOption(opts, "MaxTapT
72 matches
Mail list logo
