I've had a similar problem, but with alt+`. Switch between two windows
quickly, and sometimes they don't switch, sometimes they will lose focus
in the switch.
Another weird issue I've noticed:
* Open 2 Terminal windows
* Hold alt+` until the window previews appear
* Keep holding the key combinati
Thanks for the bug report. With the changes to the linker in 11.10, you
must specify the -llibrary arguments after the objects that reference
them. So in the above case:
gcc crypt.c -lcrypt
Please see http://wiki.debian.org/ToolChain/DSOLinking for an overview
of the changes.
** Changed in: manp
After playing around a bit I can reproduce it with alt+tab as well, it
just doesn't happen as frequently. For testing I only had two windows
open, gnome-terminal and Chrome. It seems to occur most frequently with
a slower alt+tab, but fast enough to avoid the window switcher appearing
on screen. St
Thanks for the bug report. I found an upstream bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=668035 and I submitted a
simple patch to fix it.
You can workaround the issue by manually adding:
PACKAGENAME
VERSION
REVISION
to the generated xml. It seems that is exactly what glib does, to
c
Looks like the configs were multiarched in python3.3 but
distutils.sysconfig wasn't updated to reflect the changes. Needs at
least two changes, in get_python_inc() and get_makefile_filename().
I'll attach a patch that let's me install a simple test c module here,
using sysconfig.get_config_var("M
We have actually been looking into this issue recently in #ubuntu, so I
thought I'd add my finding here.
As mentioned in the linked debian bug, logging into the session with gdm
fixes the issue (unless you are logging into a session that uses
compiz). And at the bottom of the report, lightdm-kde-g
I should also note that setting the cursor explicitly to the LEFT_PTR in
any gtk app will cause that app to show cursor updates properly when
hovered over (which is why I think Firefox still works when you hover
over it as mentioned in bug #86184 ):
#include
#include
int
main()
{
gtk_init(NUL
This seems be fixed in the latest nvidia-current release:
nvidia-graphics-drivers (304.43-0ubuntu1) quantal; urgency=low
* debian/rules:
- Add support for X ABI 13.
* New upstream release (LP: #1037483):
- Added support for the following GPUs:
o GeForce GTX 660 Ti
o Quadro
Forwarded upstream to:
http://pysvn.tigris.org/issues/show_bug.cgi?id=181
** Bug watch added: pysvn.tigris.org/issues/ #181
http://pysvn.tigris.org/issues/show_bug.cgi?id=181
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Updated the debdiff, forgot to bump the gtk+3.0 build-depends to 3.5.13
for the new gtk_entry_set_attributes() function in the patch.
** Patch added: "gnome-control-center_fix-big-editable-labels-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041756/+attachmen
This really appears to be more of a question than a bug report, so I am
going to convert it into a question.
Looking at the output from configure, it appears that you need to
install the package: libtinfo-dev
If you scroll down a bit in http://wiki.videolan.org/UnixCompile under
the heading "The
Public bug reported:
When running update-grub in Precise to add entries for a freshly
installed Quantal system on another partition, linux-boot-prober outputs
five entries:
/dev/sda5:/dev/sda5::/vmlinuz:/initrd.img:root=/dev/sda5ยท
/dev/sda5:/dev/sda5::/vmlinuz:/initrd.img:root=/dev/sda5
/dev/sda5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017678
Title:
Duplicate entries in grub2 menu for second ubuntu installed on another
partition
To manage notifications about this bug go to:
https://
** Bug watch added: Debian Bug tracker #649217
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649217
** Also affects: os-prober (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649217
Importance: Unknown
Status: Unknown
--
You received this bug notification because
With the update to 3.5.0-2-generic in quantal, /boot/grub/grub.cfg was
generated. When running update-grub from the precise partition, the
grub2 menu is now correct without duplicates (plus additional recovery
mode entries).
So I guess this is only an issue after an initial install using:
ubiquity
** Attachment added:
"0001-setup.py-use-absolute-path-for-hybrid-detect-install.patch"
https://bugs.launchpad.net/bugs/1026787/+attachment/3228804/+files/0001-setup.py-use-absolute-path-for-hybrid-detect-install.patch
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
With the update to the new kernel, I was checking the log and found:
init: Failed to spawn hybrid-gfx main process: unable to execute: No
such file or directory
Turns out with the changes to workaround bug 1026016 the hybrid-detect
executable is being copied to /usr/usr/bin/
Looking at the stacktrace top when we crash on 'import gnutls.crypto':
#0 __pthread_mutex_lock (mutex=0x756f32c4) at pthread_mutex_lock.c:50
#1 0x74f6c7bd in mutex_init (lock=0x7520e228, just_check=1) at
ath.c:132
#2 0x74f6c91d in _gcry_ath_mutex_lock (lock=0x7520e2
Thanks for the bug report. However, I cannot reproduce this bug. I am
going to move this to gnome-control-center. Can you add the output of:
apt-cache policy gnome-control-center;
Maybe you have a PPA overriding the default package. A screenshot of the
Appearance dialog may also be helpful. Thank
One more idea, try running in a terminal:
XDG_CURRENT_DESKTOP=Unity gnome-control-center;
It will only show that option in a unity session, but maybe your
XDG_CURRENT_DESKTOP environment variable is overwritten somewhere. If
the above works, check:
echo $XDG_CURRENT_DESKTOP;
--
You received th
Thanks for the screenshots. It turns out I am able to reproduce this in
the unity-2d session. Bug #1005136 is about adding the option for that
session.
Please check:
echo $DESKTOP_SESSION;
to see if you are running the ubuntu-2d session. If so, either try the
Ubuntu session or there are workarou
*** This bug is a duplicate of bug 995521 ***
https://bugs.launchpad.net/bugs/995521
Thanks for the bug report. This bug has been reported at bug #995521 ,
so I am going to mark this as a duplicate of that bug. There is a patch
there which adds proper quoting to the check_signature function. (
I think it is probably worth fixing, since fixing it in libnotify should
fix most applications uses notifications. I have filed
https://bugzilla.gnome.org/show_bug.cgi?id=679888 upstream with the test
case and a possible fix. For any other libraries (such as python-
notify2) we can probably file se
Looking at src/pandoc.hs, we have:
| htmlFormat && ascii ->
writerFn outputFile =<< selfcontain (toEntities result)
So it tries to do the right thing in that situation. result contains the
standalone html string and toEntities substitutes entities for non-ascii
characters. The problem is selfcont
Reported upstream at https://github.com/jgm/pandoc/issues/568
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024754
Title:
pandoc --ascii and --self-contained conflict
To manage notifications about
** Changed in: eglibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022111
Title:
dynamic linker issue causes run time errors
To manage notifications about t
Thanks for the bug report. I can confirm that enabling greeter-show-
manual-login results in the behavior above. This appears to be some sort
of drawing bug in unity-greeter, so I am going to move the bug to that
package.
After adding a few more debugging lines, the only difference I noted
between
My debdiff shouldn't be necessary anymore. It is fixed in the debian
branch above (slightly differently), and it was fixed in python3.3 in
the recent quantal upload (with the same debian/patches/ncursesw-
configure.diff change).
Sorry, I should have removed the patch tag when I noticed the fix the
*** This bug is a duplicate of bug 966570 ***
https://bugs.launchpad.net/bugs/966570
Thank you for taking the time to file a bug report and helping to make
ubuntu better. This is a known issue in precise, bug #966570. I am going
to mark this bug as a duplicate of that bug.
As a workaround, yo
This works correctly in pbuilder in precise, it is just that the
--othermirror option overrides ~/.pbuilderrc, and it seems this option
was added by default since commit 1208 in lp:ubuntu-dev-tools (or
somewhere around there).
I'm going to move this to ubuntu-dev-tools since that package has
pbuil
Public bug reported:
When building 3.2.0-25.40 with make-kpkg I get the following error:
ERROR: "sysfs_create_link_nowarn" [drivers/power/power_supply.ko]
undefined!
which I believe is caused by the commits pulled in to fix
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568064
The symbol
Could attach a build log but it doesn't really contain additional
information, marking as confirmed.
** 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.lau
Related debian bug report: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=660345
Seems like 2.1.10-5 contains a fix, although the fix is to completely
rewrite the maintainer scripts, so not exactly something easy to add to
the precise package.
Though, looking at debian/policycoreutils.postrm,
Actually, even if the above fix is sufficient, we are still blocked on
https://bugs.launchpad.net/ubuntu/+source/policycoreutils/+bug/935368
(the package doesn't build on precise anymore)
I'm attaching a debdiff which fixes the FTBFS and includes the changes
above, but I'm not really sure how to d
This is fixed in precise. The docs fail to build out-of-tree because the
makefile uses relative paths to the source. Also, the devhelp version in
oneiric expects the .devhelp filename to match the directory name, which
is why the currently empty docs aren't showing up.
Attached a branch that updat
Public bug reported:
The dbus-daemon binary installed to /bin from the dbus package appears to be
the debug version
with all of the DBUS_BUILD_TESTS sections enabled. (Probably likewise for the
other binaries, but
I only noticed dbus-daemon because of
https://bugs.freedesktop.org/show_bug.cgi?i
** Description changed:
- The dbus-daemon binary installed to /bin from the dbus package appears to be
the debug version
- with all of the DBUS_BUILD_TESTS sections enabled. (Probably likewise for the
other binaries, but
- I only noticed dbus-daemon because of
https://bugs.freedesktop.org/show_
That really isn't a fix, replacing the code with "/tmp" 2.1, since now
you are copying all those files directly to /tmp, tarring up the whole
thing and then trying to delete /tmp at the end. This is not a good
idea.
Just use tempfile.mkdtemp.
--
You received this bug notification because you are
It isn't limited to gedit, but seems to affect any GtkTreeView. I
believe it is fixed upstream though:
http://git.gnome.org/browse/gtk+/commit/gtk/gtktreeview.c?id=022c576bd2764dc1fc48e46ad97aa95287c175cc
Rebuilt gtk with the patch and I can't reproduce the crash.
** Also affects: gtk+3.0 (Ubuntu
*** This bug is a duplicate of bug 917071 ***
https://bugs.launchpad.net/bugs/917071
I believe this issue is the same as bug #917071 so I am going to mark
this bug as a duplicate, since the other has a bit more information.
Thanks for the test case!
** This bug has been marked a duplicate of
hdspmixer isn't building in precise either. Adding a branch which just
adds a build-dep on dh-autoreconf and allows hdspmixer to build.
I'm not sure whether the crashes listed above are fixed, since I don't
seem to have a supported sound card (running hdspmixer just prints out
"No RME cards founds
This is fixed in 3.3.8-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917071
Title:
gedit crashed with SIGSEGV in
_gtk_tree_selection_internal_select_node()
To manage notifications about
Do you have any geoclue providers other then geoclue-ubuntu-geoip
installed? It would be interesting to see the output of:
dpkg -l '*geoclue*'
I only ask because of a recent report from a user who was seeing high-
cpu usage from indicator-datetime-service when geoclue-yahoo was
installed, thought
Can everyone experiencing this issue please check the greeter log in
/var/log/lightdm/ and look for a line similar to:
WARNING: File '/usr/lib/indicators3/7/libdatetime.so' does not exist
and if you find it, make sure indicator-datetime is installed. The
issue, based on a discussion in irc, seems
I am seeing similar activity when I attempt to reboot over ssh. The
system boots fine and I don't see any high cpu activity from init
otherwise. The system will not reboot until I exit the ssh session. This
only appears to happen over ssh, it reboots fine otherwise.
Strace on pid 1 yields an endle
** Branch linked: lp:~jconti/unity-greeter/check_null_indicator
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921998
Title:
unity-greeter crashed with SIGSEGV in indicator_object_get_entries()
To m
*** This bug is a duplicate of bug 900988 ***
https://bugs.launchpad.net/bugs/900988
I am going to mark this bug as a duplicate of bug #900988 because there
is a proposed package there that should fix this issue. If you could
enable proposed, test that package and verify that it fixes the issu
Public bug reported:
As documented here: http://developer.yahoo.com/blogs/ydn/posts/2011/06
/yahoo-maps-apis-service-closure-announcement-new-maps-offerings-coming-
soon/ the Yahoo Maps API service ended September 13, 2011, and this API
is used by the geoclue-yahoo provider.
If this provider is t
Yes, install geoclue-ubuntu-geoip and then remove geoclue-yahoo. This is
related to bug #919364
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907012
Title:
indicator-datetime uses 80% of RAM or 3.1g
Looking at distutils/command/check.py , it subclasses Reporter from
docutils/utils.py in python-doctutils to override the system_message
method (I guess to stop it from writing output and raising exceptions).
But the original system_message method returns a nodes.system_message
object, which is use
Yes, there is a log of the events from several triple taps here
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/873482/+attachment/2544802/+files/input-events-
oneiric.txt if you are curious, however, I do not believe the bug is in
the upstream code. Ubuntu has a set of
Tested the webkit 1.4.3-0ubuntu4 packages from oneiric-proposed. The
documentation is built and available in devhelp. I did not encounter any
issues with devhelp which uses webkitgtk 3.0 or liferea which uses
webkitgtk 1.0.
--
You received this bug notification because you are a member of Ubuntu
I can reproduce this in precise as well. Here is a slightly better
backtrace:
1) gdb nautilus
2) run Computer://
3) Double click a partition in the nautilus window
4) Following backtrace:
(gdb) run Computer://
Starting program: /usr/bin/nautilus Computer://
[Thread debugging using libthread_db en
Found the problem, it is actually caused by ubuntuone-client
(specifically libsyncdaemon). Due to a recent change from bug #859635 ,
the library is registering a dbus message marshaller for VOID__POINTER,
however the type registered is actually VOID__BOXED, which happens to be
the same type as Devi
Looks like this is the same bug as in
https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/908787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910195
Title:
nautilus crashed with SIGSEGV
I think I worked out at least part of the problem, so might not be a
gnome-control-center bug after all. gnome-control-center uses the
mimetype "video/x-ogm+ogg" to determine the default Video app in Default
Applications. SMplayer does not have this mimetype in its
smplayer.desktop file, but instea
I think I see the issue. In monitor.h, the request types have been
renumbered, and the consolekit.patch sets
MONITOR_REQ_CONSOLEKIT_REGISTER = 400. But, monitor_read() only reads a
single byte for the type. 400 = 0x190, so we get 0x90 = 144.
Renumbering MONITOR_REQ_CONSOLEKIT_REGISTER = 144 and
MO
CTRL+D sends EOF to the shell, indicating the end of input, so the shell
exits, which causes gnome-terminal to exit. You can verify this by
running another bash session in the terminal:
bash
then press CTRL+D. That instance of bash will exit but gnome-terminal
will remain open. Another example, a
** Bug watch added: Debian Bug tracker #658075
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658075
** Also affects: blender (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658075
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
This is doable now that we have openimageio in quantal. I did a test
rebuild of blender 2.63a-1 from debian unstable for precise with cycles
enabled, and it seems to be working fine (at ppa:jconti/testing )
The problem is that openimageio currently only builds for i386/amd64
while blender builds f
Turned out that chat support was pretty straightforward to add, so I
went ahead and finished the patch. Should have pretty much everything
now, besides buddy icons, but note that the chat support is not
extensively tested yet since I don't use that feature. I noticed that
the pidgin-libnotify task
Test case doesn't crash with the version from -proposed (but does with
12.10.4-0ubuntu1). Looks good to me.
** 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://
** Bug watch added: Debian Bug tracker #695066
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695066
** Also affects: geant321 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695066
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This is caused by a change in cernlib. Tested in both raring and debian
unstable as well, and rebuilding the package there results in empty
packages. Forwarded the bug to debian with a description of the fix.
** Changed in: geant321 (Ubuntu)
Status: New => Confirmed
--
You received this b
Excellent, just noticed this bug while testing out other fixes in the
linux-image-3.5.0-20-generic -proposed package. Before updating I had
about 350 seccomp audit messages for google-chrome in dmesg after about
an hour of use. After installing the fixed kernel, 0 seccomp audit
messages for google-
Unfortunately, it is kind of on purpose. The .desktop file has
OnlyShowIn=Unity; otherwise there will be multiple Time & Date options
in gnome-control-center. There is a workaround though:
XDG_CURRENT_DESKTOP=Unity gnome-control-center indicator-datetime;
I suppose indicator-datetime could force
** Package changed: ubuntu => net-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074957
Title:
improper value display in net-tools statistics.c
To manage notifications about this bug
*** This bug is a duplicate of bug 1013798 ***
https://bugs.launchpad.net/bugs/1013798
** This bug is no longer a duplicate of bug 1014309
mandos server segfault problem
** This bug has been marked a duplicate of bug 1013798
Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1
-
*** This bug is a duplicate of bug 1013798 ***
https://bugs.launchpad.net/bugs/1013798
I'm going to mark this as a duplicate of bug #1013798. It is the same
sort of issue, and the patch there should fix it by calling
global_init() before GCRYCTL_SUSPEND_SECMEM_WARN.
** This bug has been marke
Seems that the further testing was needed. When adding chat support I
had to change how attention was set and didn't notice that it was being
set when the conversation was focused as well. Fixed in this patch.
Didn't update the ppa with the changes.
** Patch added: "pidgin-libnotify_messaging_menu
Bah sorry everyone, I was reviewing the patch after the comment and I
forgot a g_strfreev() on an error (that shouldn't ever happen but
still).
** Patch added: "pidgin-libnotify_messaging_menu_support_v3.debdiff"
https://bugs.launchpad.net/ubuntu/quantal/+source/pidgin-libnotify/+bug/1040259/+
@KruyKaze: Did you run gm-notify once first? You can search for it in
the dash or run gm-notify from the command line. It needs to be run once
to register with the messaging menu. (Unlike in previous versions where
there was a file in /usr/share/indicators/messages/applications/ that
would tell the
Affects the package in quantal as well. Part of the patch to enable
linking to libncursesw5 seems to have been dropped between python2.7 and
python3.2, so looking at the build log we see:
checking ncurses.h usability... no
checking ncurses.h presence... no
checking for ncurses.h... no
But in the
Running:
gdb --args wget -m url;
Followed by 'run' until the sigsegv, and then 'bt' should get a decent
trace, though having at least libc6-dbg installed as well at the dbgsym
package for wget from http://ddebs.ubuntu.com/pool/main/w/wget/ will get
us a better trace.
--
You received this bug no
** Summary changed:
- segfault in wget 1.13.4
+ wget 1.13.4 crashed with SIGSEGV in malloc_consolidate()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022124
Title:
wget 1.13.4 crashed with SIGSEG
The troublesome code from the valgrind log in iri.c (and the only major
change to iri.c since lucid) is from commit
2f6aa1d7417df1dfc5859686fbd77179b9fd:
diff --git a/src/iri.c b/src/iri.c
index 08cfde4..9b16639 100644
--- a/src/iri.c
+++ b/src/iri.c
@@ -264,6 +264,21 @@ remote_to_utf8 (struct
I have prepared a test package at
https://launchpad.net/~jconti/+archive/testing/+files/wget_1.13.4-2ubuntu2_amd64.deb
with the above patch reverted ( debdiff:
https://launchpad.net/~jconti/+archive/testing/+files/wget_1.13.4-2ubuntu1_1.13.4-2ubuntu2.diff.gz
), so that we might determine if that is
Excellent, thanks for testing. I have forwarded the bug upstream at
http://savannah.gnu.org/bugs/index.php?36823 and hopefully we have
enough information to work out a fix.
** Bug watch added: GNU Savannah Bug Tracker #36823
http://savannah.gnu.org/bugs/?36823
** Also affects: wget via
http
** Package changed: notification-daemon (Ubuntu) => libnotify (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023286
Title:
"icon_data" hint is deprecated, please use "image_data" instead
T
Thanks for the bug report. This is not really a bug in notification-
daemon, it is just warning us that the "icon_data" hint is deprecated,
which it is. It is difficult to tell exactly which app is misbehaving
from the information given, however I have been able to reproduce the
bug with a simple l
*** This bug is a duplicate of bug 1023474 ***
https://bugs.launchpad.net/bugs/1023474
Looking at /usr/bin/update-manager it uses #! /usr/bin/python but the
UpdateManager python code is in /usr/lib/python3/dist-packages. It does
run changing the shebang to /usr/bin/python3, though quickly glan
*** This bug is a duplicate of bug 1023474 ***
https://bugs.launchpad.net/bugs/1023474
Actually, looks like this was just fixed in 1:0.167 (sudo apt-get
update; sudo apt-get upgrade; to work around the issue until you can use
update-manager again). Marking this as a dup of bug #1023474
** Thi
Please do not remove com.ubuntu.update-notifier.auto-launch, it is
terribly annoying to have a dialog pop up when you are working on other
tasks. The icon is nice in that it alerts that new updates are
available, and I should install them as soon as I get a chance.
--
You received this bug notifi
Still seeing this with ssh using 1.4-0ubuntu5~jh with --log. Maybe I
should file a separate bug?
I haven't been able to come up with a minimal test case, but it turns
out you don't need to shutdown/reboot to see it, just have an ssh user
logged in, run: sudo stop ssh; and then watch init spin with
Public bug reported:
Steps to reproduce:
1) Boot the machine with --log on the kernel command line
2) Log into the machine through ssh
3) Execute: sudo stop ssh;
4) The init process will spin with EAGAIN on one if its file descriptors
5) Exit the remote ssh session and the service will stop
The
I think the attached source file, along with a simple upstart conf with:
exec /path/to/test-daemon may be a minimal example of the behavior.
sshd is spawned by upstart with -D so the initial process doesn't
daemonize. The upstart logging mechanism will setup a pty for
stdout/stderr. When receiving
The unref in BackgroundLoader.ready_cb seems to be the issue here, from
commit http://bazaar.launchpad.net/~unity-greeter-team/unity-
greeter/trunk/revision/367
At least on my system, after the updates to glib 2.32 and gtk 3.4, the
first BackgroundLoader that is created always ends up in ready_cb
Have you tested this since the updates to glib 2.32 and gtk 3.4? I
marked this as confirmed last night since I could reproduce it
consistently, but since the updates today, I can no longer reproduce the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It is almost certainly 200_fix_four_tap.patch, it reintroduces the
finger counting which is not valid for our touchpads.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873482
Title:
elantech: Touchpa
And merged upstream now, so I guess it finally is an upstream bug.
http://patchwork.freedesktop.org/patch/9628/
http://cgit.freedesktop.org/xorg/driver/xf86-input-
synaptics/commit/?id=da461b91659d0c64aa6827e065aee2682116a57e (a week
after I get the upstream bug closed...)
--
You received this bu
I haven't experienced this issue since the updated mutter package last
week, and it is still working with the recently released 3.4, so I am
going to mark this bug as fixed. Please feel free to reopen the bug if
you are still experiencing it.
** Changed in: gnome-shell (Ubuntu)
Status: Conf
I believe this is fixed in 0.85.0-1ubuntu1:
wayland (0.85.0-1ubuntu1) precise; urgency=low
* Merge from Debian experimental. For the remaining changes see
the changelog entry from 0.1.0~2-1ubuntu1.
* Drop COPYING.GPL-2, the project uses MIT/X11 license for the most
part, the rest is e
Public bug reported:
It appears if enabling the upstart user session (
https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes#Upstart_User_Sessions_.28technology_preview.29
) there is a race between gnome-session and upstart for who starts
gnome-settings-daemon first.
Most of the time on my system,
Ah, in that case this may just be a bug with my setup.
$HOME/.config/autostart/ is likely read before any of those directories,
and I have a copy of gnome-settings-daemon.desktop in there. Thanks for
the information. I'll delete it and continue testing, but this bug is
probably invalid.
--
You re
There is an attempt in pidgin-libnotify to generate unique strings for
each buddy, where each string is the id of a menu item in the Messaging
Menu. If you are getting repeat entries, then for some reason it is
generating two different strings for the same buddy.
If someone experiencing this bug c
Thanks for the information, the random characters at the end of the
buddy name seem to be what's hurting us here. It seems that sender may
contain too much information, looks like where the message originated
from. Originally it was using purple_buddy_get_name() instead of sender,
but for all the p
Thanks for testing. That buddy id was exactly what I was hoping to see,
so at least that part seems to be fixed.
Problem 1, as Sebastien mentioned, was unfortunately always there. I'm
not sure how to fix it. On my system at least, sometimes I will get the
first notification, sometimes not. I think
Though now I'm concerned that the patch will break jabber users where it
previously worked because they didn't have random strings at the end,
but still don't have purple_buddy_get_name() matching
purple_conversation_get_name()...
--
You received this bug notification because you are a member of
After a few minutes thought, I realized if
purple_conversation_get_name() == sender, and I can get the buddy with
account and sender, then I should be able to do the same with the
conversation name. So I have pushed a new test package to
ppa:jconti/gnome3. Please test it out and let me know if it f
Richard it looks like bug 1175537. There is a fix for that in saucy, or
you could try the raring build in ppa:jconti/gnome3. If that does not
fix it, please file a new bug. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
101 - 200 of 269 matches
Mail list logo
