[Bug 302132] Re: Pidgin memory leak on Intrepid
Testing very lightly yet, I also believe I have Jean-Rémy's described behaviour. Pidgin 2.5.5 in jauty. -- Pidgin memory leak on Intrepid https://bugs.launchpad.net/bugs/302132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62361] Re: Edgy doesn't detect instantly like Dapper
Hi, Unfortunately, I am not using the same laptop anymore, so I can't answer for sure. I believe it has been fixed, but don't really remember, as this problem didn't really bug me much. Since there are only two old reports about it, I suggest closing the bug, if it resurfaces someone will post it again. -- Edgy doesn't detect instantly like Dapper https://bugs.launchpad.net/bugs/62361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48612] Re: demux_flac.c does not set XINE_STREAM_INFO_HAS_AUDIO
Ok, I have ubuntu 6.10 here with not many "different" packages (quite a few from universe, multiverse, etc, and w32codecs, flash etc, but virtually nothing hand-compiled or taken from a completely alien source). Took the ubuntu source packages for amarok-1.4.1, compiled it, no FLAC. Took the ubuntu source packages for xine-lib 1.1.2 and xine-extracodecs, compiled them, everything with amarok is ok. I am not shure if I have or haven't recompiled amarok after the xine upgrade, but I don't think so. Totem with xine seems to be working fine, too (didn't test reading a DVD, though), and I did not recompile it. I guess this bug may be closed if this version of xine-libs and xine- extracodecs is backported to 6.10. Thanks for all the hard work! -- demux_flac.c does not set XINE_STREAM_INFO_HAS_AUDIO https://launchpad.net/bugs/48612 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69152] Re: Problems with Alps touchpad after upgrade to Edgy
Fixed here too, but I don't remember *when* it became fixed (I don't reboot often and upgraded to Feisty during beta, so I don't know if the fix appeared before or after the upgrade). -- Problems with Alps touchpad after upgrade to Edgy https://bugs.launchpad.net/bugs/69152 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 23946] Re: Xorg fails to configure the trackpad on Sony VAIO
Hi, I have a toshiba satellite M50 that suffers from the same problem on edgy (this was upgraded from dapper, which worked flawlessly). X "thinks" the trackpad is at "event2" when it is, in fact, at "event3". Restarting X, or going to text mode and back, solves this. This is version 0.14.6-0ubuntu3 of the driver. I believe bugs 69152 and 63714 are duplicates of this one, and maybe 46934 too. Also, I have the same behavior as that described in bug 62361 (will post an update there too), which I didn't have before, so these two things may be related. -- Xorg fails to configure the trackpad on Sony VAIO https://launchpad.net/bugs/23946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62361] Re: Edgy doesn't detect instantly like Dapper
Hi, Same here, on a toshiba satellite M50, this didn't happen in dapper. I also have the problem described in bug 23946 that didn't exist in dapper too, maybe the two are related. -- Edgy doesn't detect instantly like Dapper https://launchpad.net/bugs/62361 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552227] Re: gwibber-accounts crashed with KeyError in get_account_data()
Using an up-to-date Lucid with gwibber 2.30.0.1-0ubuntu1, I have the same problem: I authenticate on facebook but cannot add. Tried the patch from Toby Roworth (post #64) and got exactly the same error message as Jorge Rubio on post #67. Since some people had success with OpenDNS (not my case), this error might have something to do with language settings; my system is configured for pt-BR, a language supported by facebook. The facebook login page within gwibber is presented in pt-BR. I was unable to make the facebook page come up in English. If someone knows how to do it, I may try to see if the behaviour changes. What I already tried: I tried unsetting LANG, LANGUAGE and LC_ALL before running gwibber (the UI was presented in English, but not the Facebook page), tried to activate a proxy on gnome preferences and on firefox to go through a us-based proxy (not sure it worked, though), changed DNS servers to OpenDNS, and tried to change the preferred languages order in firefox (is firefox the embedded browser?). -- gwibber-accounts crashed with KeyError in get_account_data() https://bugs.launchpad.net/bugs/552227 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454404] [NEW] gnome-keyring does not grant permissions automatically on resume
Public bug reported: Binary package hint: gnome-keyring When I log in, nm-applet connects automatically to my access point, since the default keyring is unlocked on login and the WPA key is stored there. But if I suspend the machine (to RAM) and then bring it back, I get a prompt asking for my password to unlock the keyring (as nm-applet needs it to reconnect to the access point). However, I already entered my password on the screensaver prompt (the screen on my machine is locked on resume, I believe this is the default). This double-prompting is unexpected and, indeed, did not happen on Jaunty (nor Hardy); it started after upgrading to karmic beta. ProblemType: Bug Architecture: i386 Date: Sun Oct 18 01:32:09 2009 DistroRelease: Ubuntu 9.10 Package: gnome-keyring 2.28.0-0ubuntu2 ProcEnviron: LANGUAGE=pt_BR.UTF-8 PATH=(custom, user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-keyring Uname: Linux 2.6.31-14-generic i686 ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- gnome-keyring does not grant permissions automatically on resume https://bugs.launchpad.net/bugs/454404 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454404] Re: gnome-keyring does not grant permissions automatically on resume
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33860515/Dependencies.txt -- gnome-keyring does not grant permissions automatically on resume https://bugs.launchpad.net/bugs/454404 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454404] Re: gnome-keyring does not grant permissions automatically on resume
This key is set to true; the key use_screensaver_settings is also set to true. FWIW, /apps/gnome-screensaver/lock_enabled is also enabled. Thanks for the attention! -- gnome-keyring does not grant permissions automatically on resume https://bugs.launchpad.net/bugs/454404 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454404] Re: gnome-keyring does not grant permissions automatically on resume
Uh? Please note: 1. I did not change this; it is the default value; 2. This did not happen in Hardy, Intrepid or Jaunty (and probably not before either); the behaviour changed by itself on the upgrade to karmic; 3. It is IMHO a good idea to lock the keyring on suspend, since it makes a lot of sense for those that do not let the screensaver lock the screen on suspend. However, if the screensaver did lock the screen, typing the password on the screensaver prompt should unlock the keyring again automatically. In fact, I believe there is a PAM module (pam_gnome_keyring.so) supposed to do exactly this (and it is enabled in /etc/pam.d/gnome-screensaver, which is the default, as again I did not change it); 4. If you disagree, then at the very least the default should be changed. This behaviour is unexpected and a regression. Maybe this is a gnome-screensaver bug, or a bug in the mentioned PAM module? -- gnome-keyring does not grant permissions automatically on resume https://bugs.launchpad.net/bugs/454404 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454404] Re: gnome-keyring does not grant permissions automatically on resume
Yes, it is in my user's config; therefore, indeed it is not the default. The file is dated 2008-03-28, however, so the behaviour did change by itself on the switch to karmic. And in fact, the problem is not that the keyring is locked (I would even argue that this should be the default, but this is a different subject). The problem is that it should be unlocked by the screensaver. -- gnome-keyring does not grant permissions automatically on resume https://bugs.launchpad.net/bugs/454404 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735439] [NEW] latin.xdy is built incorrectly (causing crash)
Public bug reported: When building the xindy-rules package, the file "make- rules/inputenc/Makefile.in" uses grep to remove comment lines from latin?.xdy files and concatenate them into latin.xdy. This fails because gnu grep recognizes some of the files as binary and, instead of outputting the expected lines, simply writes out "Binary file (standard input) matches", which is obviously invalid. Therefore, trying to use xindy with a simple LaTeX document results in --- texindy testfile.idx Opening logfile "/dev/null" (done) Reading indexstyle... Loading module "/tmp/F5cxozedk0"... Loading module "lang/general/latin9-lang.xdy"... Loading module "lang/general/latin9.xdy"... Finished loading module "lang/general/latin9.xdy". Finished loading module "lang/general/latin9-lang.xdy". Loading module "tex/inputenc/latin.xdy"... Error in line 4: ;; Generated from latin?.xdy Binary ERROR: EVAL: variable BINARY has no value --- A good solution was added to gentoo (https://bugs.gentoo.org/573794 ). I suggest ubuntu (and debian) incorporate this patch. ** Affects: xindy (Ubuntu) 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/1735439 Title: latin.xdy is built incorrectly (causing crash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xindy/+bug/1735439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735439] Re: latin.xdy is built incorrectly (causing crash)
For those struggling with this issue, a workaround is to call "texindy -C utf8" or, if using imakeidx, using "\makeindex[options=-C utf8]" (obviously, as long as your document is indeed utf8). Using XeLaTex/LuaLaTeX also works, because both also force utf8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735439 Title: latin.xdy is built incorrectly (causing crash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xindy/+bug/1735439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 942991] Re: Really long login time under Ubuntu session
This happens to me when using startx, not when using lightdm. It also happens if I try to start gnome-session over ssh. Right now I am on a Oneiric machine, but I am pretty sure the same happens on Precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/942991 Title: Really long login time under Ubuntu session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/942991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336619] [NEW] mplayer built without support for libdvdnav in trusty
Public bug reported: It seems that the mplayer build for trusty tahr has been compiled without support for dvdnav. Since dvdnav support was included in previous versions and since the changelog does not mention this change, I assume this is a bug. This is mplayer version 2:1.1+dfsg1-0ubuntu3 . ** Affects: mplayer (Ubuntu) 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/1336619 Title: mplayer built without support for libdvdnav in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1336619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 942991] Re: Really long login time under Ubuntu session
It does not happen for me anymore with an up-to-date 12.04 ubuntu, but I was unable to identify what solved 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/942991 Title: Really long login time under Ubuntu session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/942991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237362] Re: Broken keymap using Tightvnc w/ Gnome
Server (running Xtightvnc) is karmic, client (running vinagre) is maverick. I have the same problem, and XKL_XMODMAP_DISABLE=1 solves it. There are lots of messages and bug reports on this since feisty, including weird suggestions to disable gnome-session or set up an invalid keymap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/237362 Title: Broken keymap using Tightvnc w/ Gnome -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454404] Re: gnome-keyring does not grant permissions automatically on resume
I cannot reproduce this in maverick anymore and, in fact, it resolved by itself quite some time ago. I suppose it was on the upgrade to Lucid, but I do not remember at all, sorry. I guess the bug may be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/454404 Title: gnome-keyring does not grant permissions automatically on resume -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
