[Bug 1667125] Re: Please build with fieldtrial_testing_like_official_build=true
Thanks! Apologies for the confusing flag name. I'm going to try to get some of this fixed up to be saner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667125 Title: Please build with fieldtrial_testing_like_official_build=true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667125] [NEW] Please build with fieldtrial_testing_like_official_build=true
Public bug reported: IMPORTANT: Fix this *before* shipping M56. Chromium builds built with the default developer settings will enable all experimental features, even ones that aren't ready to be shipped yet. End-user builds of Chromium-derived code need to build with fieldtrial_testing_like_official_build=true to disable these. See this thread where this was announced in 2015 for details: https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/UmdUH3AkQRE/TifdFA-OAgAJ Notably, these settings in M56 aren't compatible with each other (one of the field trials is not shipping for M56). See https://bugs.chromium.org/p/chromium/issues/detail?id=693943 ** Affects: chromium-browser (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/1667125 Title: Please build with fieldtrial_testing_like_official_build=true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550643] [NEW] Please backport OpenSSL SNI signature algorithms fix.
Public bug reported: If an OpenSSL consumer uses SSL_set_SSL_CTX (very commonly done with SNI), OpenSSL 1.0.1i and earlier lose internal state relating to TLS 1.2 which causes it to forget the peer's digest preferences. The end result is such servers will *only* sign SHA-1 ServerKeyExchanges in TLS 1.2, even if the peer advertises other hashes or even doesn't advertise SHA-1 at all. See: https://rt.openssl.org/Ticket/Display.html?id=3560 https://bugzilla.redhat.com/show_bug.cgi?id=1150033 https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=4e05aedbcab7f7f83a887e952ebdcc5d4f2291e4 http://www.ietf.org/mail-archive/web/tls/current/msg19195.html Glancing at packages.ubuntu.com, this seems to affect Ubuntu vivid and below. It would be greatly appreciated if you would backport this fix to all applicable releases so Ubuntu servers do not become the limiting factor in someday removing SHA-1 here. The links above should have reproduction steps you can use to confirm the bug and test the fix. (Note that it requires a build of OpenSSL 1.0.2 to confirm the bug. OpenSSL 1.0.1's s_client doesn't print the necessary information.) ** Affects: openssl (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/1550643 Title: Please backport OpenSSL SNI signature algorithms fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1550643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399044] Re: Alt-tab in unity only raises one window of a multi-window application
You can, but that's not the point. In most systems, alt-tab naturally forms an LRU ordering, which means you can switch between two applications very quickly. This behavior means that LRU is broken on multimonitor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399044 Title: Alt-tab in unity only raises one window of a multi-window application To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1399044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935525] Re: libglib-perl version 2:1.241-1 FTBFS on i386 in precise
The child process is literally doing nothing but calling POSIX::_exit. I
find it hard to believe that the problem is that a slow machine takes
more than 30 seconds to process that. I think it's more likely there's
another problem here.
my $pid = fork();
if (! defined $pid) {
die oops, cannot fork: $!;
}
if ($pid == 0) {
# child
require POSIX;
POSIX::_exit(42); # no END etc cleanups
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935525
Title:
libglib-perl version 2:1.241-1 FTBFS on i386 in precise
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglib-perl/+bug/935525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935525] Re: libglib-perl version 2:1.241-1 FTBFS on i386 in precise
That timing is not exact, and an ideal fix would be event-based rather than wallclock seconds, but doubling the time allowed is generous. It's also worth noting that the test is testing something event-based in the first place. It's testing that child watches fire events when the child dies. The timeout is only there if it fails and hangs. So this doesn't mean the test is flakey and uses ad-hoc timeouts. It means the test is failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935525 Title: libglib-perl version 2:1.241-1 FTBFS on i386 in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglib-perl/+bug/935525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754622] Re: GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed
Still happens on 11.10. If you use G_DEBUG=fatal-criticals and catch the error with gdb, this bug comes from dbusmenu. ** Also affects: libdbusmenu (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/754622 Title: GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/754622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 953404] Re: ia32-libs in precise is missing libgconf-2-4:i386
It's also missing in oneiric (but not natty). If it would be possible to backport this fix to oneiric users, that would be convenient. http://packages.ubuntu.com/natty/amd64/ia32-libs/filelist http://packages.ubuntu.com/oneiric/amd64/ia32-libs/filelist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953404 Title: ia32-libs in precise is missing libgconf-2-4:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/953404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 856993] Re: NP_GetMIMEDescription returns NULL in x86_64 instrumented Citrix ICA client npwrapper.npica.so
(I'm the current nspluginwrapper upstream maintainer. Came across this report via Google Alerts.) If you're running nspluginwrapper 1.2.2, I strongly recommend using a more stable release. Versions before the 1.4.x series have many many known bugs and race conditions. That said, I don't think I fixed anything relating to NP_GetMIMEDescription, so 1.2.x should be the same here. (Not sure where you're getting that 1.2.2 is trunk. The project home page is http://nspluginwrapper.org/ ) I don't seem to be able to reproduce your results, either with 1.4.4 or 1.2.2. I modified your test program to use argv[1] instead of a hard- coded string and got: $ gcc test.c -o test64 -ldl $ gcc test.c -o test32 -m32 -ldl $ ./test32 ./npica.so No plugin version Got NP_GetMIMEDescription: 0xf77a2590 Got MIME description: application/x-ica:ica:Handles ICA connections Got NP_GetValue: 0xf77a2420 $ ./test64 ./npwrapper.npica.so No plugin version Got NP_GetMIMEDescription: 0x7f411cee0a80 Got MIME description: application/x-ica:ica:Handles ICA connections Got NP_GetValue: 0x7f411cee0370 $ ./test64 ./npwrapper.npica-1.2.2.so No plugin version Got NP_GetMIMEDescription: 0x7fc2fc16c040 Got MIME description: application/x-ica:ica:Handles ICA connections Got NP_GetValue: 0x7fc2fc16be60 I notice that your program in the first script uses /usr/OOO/ICAClient/npica.so. Did you possibly rename npwrapper.npica.so between the two runs? The generated wrapper plugin doesn't actually contain the original plugin and just uses the path you installed it with. It's possible you're getting all the NULLs because it can't find the original 32-bit plugin anymore. (Huh, I was not aware of NP_GetPluginVersion. I'll modify nspluginwrapper to wrap it sometime. Although it doesn't seem to be used by any plugin I can find.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856993 Title: NP_GetMIMEDescription returns NULL in x86_64 instrumented Citrix ICA client npwrapper.npica.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/856993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329410] Re: does not set configured resolutions at GNOME startup any more
Someone want to verify if this patch is at all still needed? The linked upstream bug has been closed obsolete, so it should probably be dropped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329410 Title: does not set configured resolutions at GNOME startup any more To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/329410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
No, this is probably unrelated. I do not have a radeon chip in my laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
@Andy: Are you sure about that? Comment 72 seems to directly contradict you here. I do not run natty, but on my maverick installation, I was bit by both the tpm issues and the blinking moon ones. The failure mode of the tpm issue is not a blinking moon. It starts to suspend and, after a second gives up, and wakes back up again. This has since been fixed as far as I can tell and otherwise requires a workaround to unload/reload the module. The failure mode of the other issue is that the machine begins to sleep but the moon never stops blinking and drawing power until you power cycle the machine and lose all your state; a far far worse bug. This has not been fixed and I have been forced to run with the chvt hack since I installed maverick. It appears that, until comment 65, this bug was not in any way related to the tpm issues. I believe the other bug is a timing thing related DRI and graphics drivers. See comment 76. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724587] Re: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash
https://bugzilla.redhat.com/show_bug.cgi?id=680279 The patched has made it into Fedora. ** Bug watch added: Red Hat Bugzilla #680279 https://bugzilla.redhat.com/show_bug.cgi?id=680279 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724587 Title: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
I think this report at some point switched to being about two bugs instead of one and is causing confusing. The tpm_tis seems to be fixed. But the timing bug that's hacked around with the chvt in comment #43 does not appear to be. (The latter is the one that gets stuck at the flashing moon. tpm_tis's failure more for me was that it gets to the flashing moon, gives up, and returns to the desktop.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659712] Re: New device name enumerated after suspend/resume cycle
I'm not sure what change did the trick, but the bug seems fixed for me on the latest kernel in maverick (2.6.35-27.48). Do things work for others? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659712 Title: New device name enumerated after suspend/resume cycle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724587] [NEW] [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash
Public bug reported: Binary package hint: nspluginwrapper nspluginwrapper has a race condition during NPP_Destroy (called when a tab is closed) that can crash the plugin. The race happens particularly often when another tab has a video playing; I suspect this is because it causes enough traffic over the IPC to delay the processes and trigger the race. If NPP_Destroy is called by the wrapper process at the same time the viewer (plugin) process makes some call, then, from the plugin's perspective, its call to NPN_InvalidateRect resulted in the plugin instance being destroyed from under its feet. This is, of course, nonsense, so Flash shortly crashes to let us know how silly we are being. :-) I've written patches for this issue here https://github.com/davidben/nspluginwrapper/commits/master Only the second of the two patches is strictly relevant; the other is a separate race I came across in a previous iteration of this patch. It detects when NPP_Destroy is being called at an unsafe point and delays it to another message loop iteration. With the caveat that requests can't be reordered. So, when it must, the patch lies to the wrapper about NPP_Destroy's return values. Any delayed NPSavedData gets discarded. That said, I've never seen Flash use this feature, and the docs do allow the browser to discard them arbitrarily. The relevant bug in Chromium is here: http://code.google.com/p/chromium/issues/detail?id=53940 (To be thorough, this is on nspluginwrapper 1.2.2-0ubuntu7 on google- chrome-beta 10.0.648.82-r75062 on Ubuntu maverick. I've also reproduced this crash in Firefox, and a cursory look at Debian stable's nspluginwrapper 1.3.0-1 suggests the bug is there too...) As far as I can tell, nspluginwrapper no longer has an upstream. If that's not the case, this patch should probably be forward. ** Affects: nspluginwrapper (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/724587 Title: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724587] Re: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash
This is the first of two patches in the linked git repo. (The formatting might look off because nspluginwrapper assumes tabs are 4 spaces. It's kind of obnoxious.) ** Patch added: [PATCH 1/2] Make delayed_calls_process re-entrant https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/724587/+attachment/1869593/+files/0001-Make-delayed_calls_process-re-entrant.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724587 Title: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724587] Re: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash
And this is the second. ** Patch added: [PATCH 2/2] Delay calls to NPP_Destroy when the plugin instance is on the stack https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/724587/+attachment/1869594/+files/0002-Delay-calls-to-NPP_Destroy-when-the-plugin-instance-.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724587 Title: [Patch included] nspluginwrapper has a race condition on NPP_Destroy and may crash Flash -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659712] Re: New device name enumerated after suspend/resume cycle
I believe this is a regression caused by the fix to bug #86820. Specifically, commit 1ca56e513a9fd356d5a9e0de45dbe0e189e00386; I had ran into the referenced bug in karmic on my T400 and tried a kernel with that fix in. It fixed the keyboard problem, but failed to fix it for my touchpad and trackpoint. When the touchpad and trackpoint come back, X decides it's a new device, so I imagine this reset is causing it. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1ca56e513a9fd356d5a9e0de45dbe0e189e00386 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86820 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659712 Title: New device name enumerated after suspend/resume cycle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/X60/T6x suspend fails
This started occurring far more frequently for me when I switched from metacity's built-in compositor to compiz. It appear's metacity's compositor (not mutter) is actually XRender-based, not GL like compiz. I also recall one of the few times it happening to me under metacity was when I had Braid open. So perhaps this is related to GL or DRI. (I'm using a Thinkpad T400 with integrated intel.) I think the chvt workaround may be a timing thing. Looks like the kernel itself may do a VT switch on suspend anyway? suspend_prepare calls pm_prepare_console which calls vt_move_to_console. Perhaps making it happen earlier gives compiz and whoever else is using DRI more time to release whatever's causing a problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86820] Re: touchpad doesn't work after suspend
I'm not Sayantan, but I also have my touchpad disabled on resume until a few seconds pass. This is an up-to-date maverick system on a T400 Thinkpad. % uname -r 2.6.35-24-generic % cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.10 DISTRIB_CODENAME=maverick DISTRIB_DESCRIPTION=Ubuntu 10.10 I've attached a syslog of a reboot, suspend, and resume with i8042.debug=1. It appears that a lot of the initial kernel bootup spew got lost (perhaps i8042.debug is so noisy that some buffer got exceeded before the logger could capture it). I have also noticed that, when I resume, the touchpad gets completely reset and I lose all my settings on it, which is a regression from before maverick. Although, it appears from Xorg.0.log that X treats it as a new input device getting plugged in? I don't know if it's intentional, but it seems a little poor. Though, I could believe this should be GNOME's fault for not reprogramming the device (or my fault for using settings GNOME doesn't support; I manually enable two-finger scroll emulation with xinput). ** Attachment added: /var/log/syslog excerpt https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86820/+attachment/1774865/+files/i8042.syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/86820 Title: touchpad doesn't work after suspend -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379874] Re: auctex uses xpdf by default but does not depend on the package
Can an attempt to made to upstream this change, to minimize deviation from upstream? -- auctex uses xpdf by default but does not depend on the package https://bugs.launchpad.net/bugs/379874 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 415153] Re: Switch to classic menu style is not functioning properly
The patch in question is likely kubuntu_68_remove_applet_confirmation.diff. It appears to be disabled because it's broken at the moment and doesn't apply properly with the new upstream release. Please do not restore it again and instead go upstream to get the feature in. A new build for karmic without the bug would also be appropriate. -- Switch to classic menu style is not functioning properly https://bugs.launchpad.net/bugs/415153 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 487184] Re: [gm45] Okular with intel graphics driver does not draw view in page thumbnail
I believe you misunderstand me. The problem *did* occur in the stock Ubuntu Karmic kernel. For unrelated reasons, I compiled a vanilla 2.6.32.8 kernel to test other things and noticed that it was *fixed* in 2.6.32.8. As such, assuming Lucid ships a sufficiently new kernel from the 2.6.32 and assuming Ubuntu does not reintroduce the bug with a patch, the bug should be fixed in Lucid. I will verify this later when I have time. -- [gm45] Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 487184] Re: [gm45] Okular with intel graphics driver does not draw view in page thumbnail
I have not tested against Lucid, but the issue appears fixed when running with a custom compiled 2.6.32.8 kernel (was seeing if newer kernel fixed broken wireless problems). -- [gm45] Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 415153] Re: Switch to classic menu style is not functioning properly
Bug was reported upstream, but allegedly this is a result of a bad Kubuntu patch. https://bugs.kde.org/show_bug.cgi?id=211549 ** Bug watch added: KDE Bug Tracking System #211549 http://bugs.kde.org/show_bug.cgi?id=211549 -- Switch to classic menu style is not functioning properly https://bugs.launchpad.net/bugs/415153 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 491483] Re: Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is used. (low graphics mode error)
I am aware of this; I know the details of this problem, having discovered it independently in the days I spent figuring out why Ubuntu failed to boot on my laptop into either X or single-user mode. If kdm was used, then this bug also occurred in single-user mode because the configuration check occurs before the single-user check and returned a non-zero exit status. The failsafe-x init script lacks a sanity check to not run when booting into single-user mode, like kdm and gdm do have. While it is true that this bug cannot currently be triggered, this package is *failsafe* X. If care cannot be taken to make sure it doesn't kill the system due to driver problems, extreme care should at least be taken to ensure it does not break existing, more fail-proof, failsafe methods. If the gdm script ever accidentally returns a non-zero exit status from a future change for whatever reason, this bug will happen again and we will attempt to launch failsafe-x on single-user mode. This is especially unfortunate; presumably if I'm booting into recovery mode, it means that failsafe X already failed and launching it again only risks further disabling the user's machine. It would be good engineering to, for instance, add a check in failsafe-x's script. If not by listening for the starting-dm event, at least do the same /proc/cmdline check that gdm does. Perhaps change the start on rule to start on (stopped gdm EXIT_STATUS=[!0] and starting-dm) But I don't know upstart particularly well, and I cannot test this on my machine; any attempt to bring up failsafe X results in killing it. -- Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is used. (low graphics mode error) https://bugs.launchpad.net/bugs/491483 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 491483] Re: Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is used. (low graphics mode error)
This bug also affected single-user mode. While it no longer occurs after the fix, the script for failsafe-x should be disabled when booting with kernel option single. It is otherwise extremely ironic that this so- called failsafe-x has the potential to (and in fact did) cause the real failsafe boot option to fail. gdm and kdm currently check for this. A similar check should be added. Likewise, kdm's init config should get the similar patch, to avoid this problem from occurring in a possible future kdm-based failsafe X to complement the one that current depends on gdm. -- Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is used. (low graphics mode error) https://bugs.launchpad.net/bugs/491483 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 491483] Re: Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is used. (low graphics mode error)
Actually, can failsafe-x be set up to never run unless starting-dm has been emitted? I see a initctl emit starting-dm DM=kdm and a similar line in gdm.conf. I don't know how upstart works, but presumably one can configure it to only consider running if starting-dm has occurred. That seems like a more reasonable fix to failsafe X's propensity to start unwanted and hang machines. -- Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is used. (low graphics mode error) https://bugs.launchpad.net/bugs/491483 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 487184] [NEW] Okular with intel graphics driver does not draw view in page thumbnail
Public bug reported: Binary package hint: xserver-xorg-video-intel Okular using default (hardware-backed) graphics engine does not draw the grey box in the thumbnail panel that shows where the current view is. Running okular -graphicssystem raster causes it to display properly, so this isn't a problem with Okular telling Qt to draw the box. Downloading the Qt 4.6 RC and using LD_LIBRARY_PATH to force that shared library likewise does not cause a problem, so it is unlikely this is a bug in Qt or Ubuntu's package of it. That leaves a regression in the intel driver. The version of xserver-xorg-video-intel on my machine is 2.9.0-1ubuntu2, arch amd64. My graphics card is 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Lenovo Device [17aa:20e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 30 Region 0: Memory at f440 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1800 [size=8] Capabilities: access denied Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) Subsystem: Lenovo Device [17aa:20e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at f420 (64-bit, non-prefetchable) [size=1M] Capabilities: access denied This is a Lenovo Thinkpad T400. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 487184] Re: Okular with intel graphics driver does not draw view in page thumbnail
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/35977870/Xorg.0.log -- Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 487184] Re: Okular with intel graphics driver does not draw view in page thumbnail
Taken with okular -graphicssystem raster ** Attachment added: Expected results http://launchpadlibrarian.net/35977934/okular-raster.png -- Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 487184] Re: Okular with intel graphics driver does not draw view in page thumbnail
Taken with default arguments ** Attachment added: Actual results http://launchpadlibrarian.net/35977950/okular-native.png -- Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 487184] Re: Okular with intel graphics driver does not draw view in page thumbnail
This also occurs with ksnapshot's region capture mode feature. As both these involve transparent overlays of things, I imagine this is in fact the same bug. Steps to reproduce for ksnapshot: 1. Run ksnapshot 2. Set Capture Mode to Region 3. Press New Snapshot 4. Drag some region of the screen Expected: Screen gets slightly darker with the region in question left undarkened and a little resize widget on the border. This, also, works properly (with some flicker) without hardware acceleration (ksnapshot -graphicssystem raster) -- Okular with intel graphics driver does not draw view in page thumbnail https://bugs.launchpad.net/bugs/487184 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 467251] [NEW] oxygen-cursor-theme-extra does not install all color schemes
Public bug reported: Oxygen upstream (and the current version's source package) provides many color scheme for the cursors, but the debian .install files only install a few of them. Notably, the zion and wonton color schemes are good for people who prefer dark cursors but don't like the dark border on the black one. ** Affects: oxygencursors (Ubuntu) Importance: Undecided Status: New -- oxygen-cursor-theme-extra does not install all color schemes https://bugs.launchpad.net/bugs/467251 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 467251] Re: oxygen-cursor-theme-extra does not install all color schemes
Also, none of the big variants of the cursors are installed. -- oxygen-cursor-theme-extra does not install all color schemes https://bugs.launchpad.net/bugs/467251 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 459933] Re: wifi disconnects when nm scans (iwlagn - intel 5100 AGN)
I am also getting similar data from iwevent and it seems to be related to the wireless problems I have been having. -- wifi disconnects when nm scans (iwlagn - intel 5100 AGN) https://bugs.launchpad.net/bugs/459933 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 322204] Re: [iwl3945] Wireless connection dies in mac80211/rate.h:152 (2.6.27-11)
I can confirm this bug. WPA networks appear to be extremely unstable in Ubuntu Intrepid. Apr 23 21:47:58 frogstar kernel: [98886.677063] [ cut here ] Apr 23 21:47:58 frogstar kernel: [98886.677071] WARNING: at /build/buildd/linux-2.6.27/include/../net/mac80211/rate.h:152 rs_get_rate+0xaf/0x4b 0 [iwl3945]() Apr 23 21:47:58 frogstar kernel: [98886.677079] Modules linked in: aes_i586 aes_generic af_packet i915 drm binfmt_misc openafs(P) rfcomm bridge stp bnep sco l2cap bluetooth ipv6 ppdev acpi_cpufreq cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table cpufreq_ userspace wmi sbs sbshc pci_slot iptable_filter ip_tables x_tables ext2 sbp2 parport_pc lp parport joydev pcmcia serio_raw evdev snd_hda_intel psmouse snd_pcm_oss snd_mixer_oss arc4 ecb crypto_blkcipher snd_pcm pcspkr iwl3945 sdhci_pci rfkill snd_seq_dummy container sdhci mac80211 mmc_ core video output yenta_socket rsrc_nonstatic tifm_7xx1 led_class snd_seq_oss pcmcia_core tifm_core snd_seq_midi snd_rawmidi cfg80211 snd_seq_m idi_event snd_seq iTCO_wdt iTCO_vendor_support ac battery button snd_timer snd_seq_device snd intel_agp agpgart shpchp pci_hotplug soundcore sn d_page_alloc ext3 jbd mbcache sd_mod sr_mod crc_t10dif cdrom sg ata_generic pata_acpi ata_piix e100 libata mii ohci1394 scsi_mod dock ieee1394 ehci_hcd uhci_hcd usbcore t Apr 23 21:47:58 frogstar kernel: ermal processor fan fbcon tileblit font bitblit softcursor fuse Apr 23 21:47:58 frogstar kernel: [98886.677326] Pid: 2830, comm: iwl3945 Tainted: PW 2.6.27-11-generic #1 Apr 23 21:47:58 frogstar kernel: [98886.677334] [c037d4fb] ? printk+0x1d/0x22 Apr 23 21:47:58 frogstar kernel: [98886.677349] [c0131ee9] warn_on_slowpath+0x59/0x90 Apr 23 21:47:58 frogstar kernel: [98886.677374] [c012a037] ? load_balance_newidle+0x97/0x270 Apr 23 21:47:58 frogstar kernel: [98886.677387] [c0102df6] ? __switch_to+0xa6/0x160 Apr 23 21:47:58 frogstar kernel: [98886.677398] [c012852b] ? finish_task_switch+0x2b/0xe0 Apr 23 21:47:58 frogstar kernel: [98886.677409] [c037da89] ? schedule+0x429/0x790 Apr 23 21:47:58 frogstar kernel: [98886.677422] [c037f09e] ? account_scheduler_latency+0xe/0x220 Apr 23 21:47:58 frogstar kernel: [98886.677433] [c02534e1] ? number+0x291/0x2a0 Apr 23 21:47:58 frogstar kernel: [98886.677448] [c01234b4] ? __enqueue_entity+0xd4/0x100 Apr 23 21:47:58 frogstar kernel: [98886.677464] [f8bed29b] ? sta_info_get+0xb/0x60 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677502] [f8c2cd7f] rs_get_rate+0xaf/0x4b0 [iwl3945] Apr 23 21:47:58 frogstar kernel: [98886.677522] [c0124b1a] ? enqueue_entity+0xda/0x2f0 Apr 23 21:47:58 frogstar kernel: [98886.677533] [c014e78b] ? getnstimeofday+0x4b/0x100 Apr 23 21:47:58 frogstar kernel: [98886.677545] [c01135f5] ? apic_wait_icr_idle+0x15/0x40 Apr 23 21:47:58 frogstar kernel: [98886.677561] [f8bed29b] ? sta_info_get+0xb/0x60 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677607] [f8bf7aa1] rate_control_get_rate+0x71/0x130 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677643] [f8bfe897] invoke_tx_handlers+0x467/0x630 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677680] [f8bfee6d] ieee80211_tx+0x7d/0x1b0 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677710] [c02ec3d9] ? pskb_expand_head+0xe9/0x150 Apr 23 21:47:58 frogstar kernel: [98886.677732] [f8bff0e4] ieee80211_master_start_xmit+0x144/0x210 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677764] [c02f44db] dev_hard_start_xmit+0x16b/0x1c0 Apr 23 21:47:58 frogstar kernel: [98886.66] [c03068f5] __qdisc_run+0x1b5/0x200 Apr 23 21:47:58 frogstar kernel: [98886.677787] [c02f6417] dev_queue_xmit+0x2e7/0x3f0 Apr 23 21:47:58 frogstar kernel: [98886.677796] [c02ec832] ? __alloc_skb+0x52/0x110 Apr 23 21:47:58 frogstar kernel: [98886.677817] [f8bf0b34] ieee80211_sta_tx+0x74/0x90 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677852] [f8bf134f] ieee80211_send_auth+0x11f/0x150 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677885] [f8bf67e0] ieee80211_sta_work+0x2e0/0x380 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677919] [f8bf6500] ? ieee80211_sta_work+0x0/0x380 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677951] [c0143765] run_workqueue+0x95/0x160 Apr 23 21:47:58 frogstar kernel: [98886.677965] [c0147696] ? finish_wait+0x16/0x70 Apr 23 21:47:58 frogstar kernel: [98886.677975] [c0143a08] worker_thread+0x88/0xf0 Apr 23 21:47:58 frogstar kernel: [98886.677984] [c01475d0] ? autoremove_wake_function+0x0/0x50 Apr 23 21:47:58 frogstar kernel: [98886.677997] [c0143980] ? worker_thread+0x0/0xf0 Apr 23 21:47:58 frogstar kernel: [98886.678008] [c0147261] kthread+0x41/0x80 Apr 23 21:47:58 frogstar kernel: [98886.678018] [c0147220] ? kthread+0x0/0x80 Apr 23 21:47:58 frogstar kernel: [98886.678029] [c0105297] kernel_thread_helper+0x7/0x10 Apr 23 21:47:58 frogstar kernel: [98886.678039] === Apr 23 21:47:58 frogstar
[Bug 300292] Re: warning issued in iwl3945 about rs_get_rate
Confirmed on a Toshiba Satellite A105. Wireless connections to our new Cisco access points with WPA are extremely unstable. Apr 23 21:47:58 frogstar kernel: [98886.677063] [ cut here ] Apr 23 21:47:58 frogstar kernel: [98886.677071] WARNING: at /build/buildd/linux-2.6.27/include/../net/mac80211/rate.h:152 rs_get_rate+0xaf/0x4b 0 [iwl3945]() Apr 23 21:47:58 frogstar kernel: [98886.677079] Modules linked in: aes_i586 aes_generic af_packet i915 drm binfmt_misc openafs(P) rfcomm bridge stp bnep sco l2cap bluetooth ipv6 ppdev acpi_cpufreq cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table cpufreq_ userspace wmi sbs sbshc pci_slot iptable_filter ip_tables x_tables ext2 sbp2 parport_pc lp parport joydev pcmcia serio_raw evdev snd_hda_intel psmouse snd_pcm_oss snd_mixer_oss arc4 ecb crypto_blkcipher snd_pcm pcspkr iwl3945 sdhci_pci rfkill snd_seq_dummy container sdhci mac80211 mmc_ core video output yenta_socket rsrc_nonstatic tifm_7xx1 led_class snd_seq_oss pcmcia_core tifm_core snd_seq_midi snd_rawmidi cfg80211 snd_seq_m idi_event snd_seq iTCO_wdt iTCO_vendor_support ac battery button snd_timer snd_seq_device snd intel_agp agpgart shpchp pci_hotplug soundcore sn d_page_alloc ext3 jbd mbcache sd_mod sr_mod crc_t10dif cdrom sg ata_generic pata_acpi ata_piix e100 libata mii ohci1394 scsi_mod dock ieee1394 ehci_hcd uhci_hcd usbcore t Apr 23 21:47:58 frogstar kernel: ermal processor fan fbcon tileblit font bitblit softcursor fuse Apr 23 21:47:58 frogstar kernel: [98886.677326] Pid: 2830, comm: iwl3945 Tainted: PW 2.6.27-11-generic #1 Apr 23 21:47:58 frogstar kernel: [98886.677334] [c037d4fb] ? printk+0x1d/0x22 Apr 23 21:47:58 frogstar kernel: [98886.677349] [c0131ee9] warn_on_slowpath+0x59/0x90 Apr 23 21:47:58 frogstar kernel: [98886.677374] [c012a037] ? load_balance_newidle+0x97/0x270 Apr 23 21:47:58 frogstar kernel: [98886.677387] [c0102df6] ? __switch_to+0xa6/0x160 Apr 23 21:47:58 frogstar kernel: [98886.677398] [c012852b] ? finish_task_switch+0x2b/0xe0 Apr 23 21:47:58 frogstar kernel: [98886.677409] [c037da89] ? schedule+0x429/0x790 Apr 23 21:47:58 frogstar kernel: [98886.677422] [c037f09e] ? account_scheduler_latency+0xe/0x220 Apr 23 21:47:58 frogstar kernel: [98886.677433] [c02534e1] ? number+0x291/0x2a0 Apr 23 21:47:58 frogstar kernel: [98886.677448] [c01234b4] ? __enqueue_entity+0xd4/0x100 Apr 23 21:47:58 frogstar kernel: [98886.677464] [f8bed29b] ? sta_info_get+0xb/0x60 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677502] [f8c2cd7f] rs_get_rate+0xaf/0x4b0 [iwl3945] Apr 23 21:47:58 frogstar kernel: [98886.677522] [c0124b1a] ? enqueue_entity+0xda/0x2f0 Apr 23 21:47:58 frogstar kernel: [98886.677533] [c014e78b] ? getnstimeofday+0x4b/0x100 Apr 23 21:47:58 frogstar kernel: [98886.677545] [c01135f5] ? apic_wait_icr_idle+0x15/0x40 Apr 23 21:47:58 frogstar kernel: [98886.677561] [f8bed29b] ? sta_info_get+0xb/0x60 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677607] [f8bf7aa1] rate_control_get_rate+0x71/0x130 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677643] [f8bfe897] invoke_tx_handlers+0x467/0x630 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677680] [f8bfee6d] ieee80211_tx+0x7d/0x1b0 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677710] [c02ec3d9] ? pskb_expand_head+0xe9/0x150 Apr 23 21:47:58 frogstar kernel: [98886.677732] [f8bff0e4] ieee80211_master_start_xmit+0x144/0x210 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677764] [c02f44db] dev_hard_start_xmit+0x16b/0x1c0 Apr 23 21:47:58 frogstar kernel: [98886.66] [c03068f5] __qdisc_run+0x1b5/0x200 Apr 23 21:47:58 frogstar kernel: [98886.677787] [c02f6417] dev_queue_xmit+0x2e7/0x3f0 Apr 23 21:47:58 frogstar kernel: [98886.677796] [c02ec832] ? __alloc_skb+0x52/0x110 Apr 23 21:47:58 frogstar kernel: [98886.677817] [f8bf0b34] ieee80211_sta_tx+0x74/0x90 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677852] [f8bf134f] ieee80211_send_auth+0x11f/0x150 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677885] [f8bf67e0] ieee80211_sta_work+0x2e0/0x380 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677919] [f8bf6500] ? ieee80211_sta_work+0x0/0x380 [mac80211] Apr 23 21:47:58 frogstar kernel: [98886.677951] [c0143765] run_workqueue+0x95/0x160 Apr 23 21:47:58 frogstar kernel: [98886.677965] [c0147696] ? finish_wait+0x16/0x70 Apr 23 21:47:58 frogstar kernel: [98886.677975] [c0143a08] worker_thread+0x88/0xf0 Apr 23 21:47:58 frogstar kernel: [98886.677984] [c01475d0] ? autoremove_wake_function+0x0/0x50 Apr 23 21:47:58 frogstar kernel: [98886.677997] [c0143980] ? worker_thread+0x0/0xf0 Apr 23 21:47:58 frogstar kernel: [98886.678008] [c0147261] kthread+0x41/0x80 Apr 23 21:47:58 frogstar kernel: [98886.678018] [c0147220] ? kthread+0x0/0x80 Apr 23 21:47:58 frogstar kernel: [98886.678029] [c0105297] kernel_thread_helper+0x7/0x10 Apr 23 21:47:58 frogstar kernel: [98886.678039]
[Bug 345039] [NEW] NetworkManager spins CPU and leaks memory
Public bug reported: Binary package hint: network-manager In Ubuntu Intrepid, network-manager will fairly often begin to spin my CPU and eat up RAM quickly (gaining about 3MB a second). I am connected to wireless when this occurs, and often I have recently resumed from suspend. (That said, I suspend/resume very frequently, so it may be unrelated to it.) This machine is a clean install. It appears to occur more frequently when I am consuming a lot of network traffic, for instance, copying a large file over scp from a computer on the local network. Restarting NetworkManager (via /etc/init.d/NetworkManager restart) stops the CPU spin. My wireless card is an Intel Wireless 3945ABG. Here is its lspci -vv output: 05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) Subsystem: Intel Corporation Device 1040 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 220 Region 0: Memory at f080 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: iwl3945 Kernel modules: iwl3945 When the error occurs, my dmesg contains several error messages from the iwl3945 driver. I have attached the portion of the dmesg output starting from the resume. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager spins CPU and leaks memory https://bugs.launchpad.net/bugs/345039 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 345039] Re: NetworkManager spins CPU and leaks memory
** Attachment added: dmesg output http://launchpadlibrarian.net/24060489/dmesg -- NetworkManager spins CPU and leaks memory https://bugs.launchpad.net/bugs/345039 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 123185] Re: qemu completely broken with current version of bochbios
So, are there any plans to backport this to Gutsy? It seems strange that a fix has been in Hardy and for quite some time now, and yet Gutsy still doesn't have it. I can hardly imagine that stable users want the old package, seeing as it doesn't work. -- qemu completely broken with current version of bochbios https://bugs.launchpad.net/bugs/123185 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 32963] Re: totem overrides XV_CONSTRAST to wrong default value (Xv movies on i810/i945 have horrible colour/gamma)
I can confirm this regression in Gutsy. (Feisty-Gutsy upgrades anyway.) The problem occurs consistently and is always reproducible. -- totem overrides XV_CONSTRAST to wrong default value (Xv movies on i810/i945 have horrible colour/gamma) https://bugs.launchpad.net/bugs/32963 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162950] Totem crashes on close in gutsy with X error
Public bug reported: Binary package hint: totem In Gutsy, totem crashes on close. Steps to Reproduce: 1. Open totem from a terminal 2. Do anything... or nothing 3. Close totem Results: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 277 error_code 8 request_code 141 minor_code 13) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Running through a debugger doesn't give anything useful, and I see no additional package to download the stripped debug symbols. (Might be useful to consider providing such packages if possible. They're useful for a lot of things.) My guess is that this is related to the video overlay as Gutsy also seems to have considerable problems with that. (The contrast setting gets set to zero, and I have to manually eyeball it to find the correct setting. Will file a report when I narrow down the exact triggers of the problem.) My graphics device is an integrated Intel chip: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) I am running an up-to-date Gutsy install that was upgraded from Feisty with no totem or graphics-related modifications. This error did not occur in Ubuntu Feisty. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- Totem crashes on close in gutsy with X error https://bugs.launchpad.net/bugs/162950 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 155216] Re: network-manager fails to stop properly when connected to wireless
More information. This also occurs (and seems to occur more often) after a suspend (for significantly long, like one hour) and seems to be caused by NetworkManager hanging and so it will not respond to a stop command. Also, when this happens, nm-applet is stuck on displaying old information, i.e. I'm still connected to the network I was on before I suspended. When the latter case happens, running top shows that it is at 100% CPU. I tried to attach a debugger to get a stack trace, but gdb crashed and I did not have pstack installed. The next time this happens, I will try pstack. However, there aren't any symbols in the binary, so I don't know how much use it'll be. My guess is that there are some critical points of NetworkManager's execution that cause it to behave very badly to a stop command and this gets triggered when it's told to shut down at the wrong time. -- network-manager fails to stop properly when connected to wireless https://bugs.launchpad.net/bugs/155216 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 156765] Re: GIMP 2.4's new print dialog is disabled
Could it then be at least in backports for those of us who'd like a more
functional GIMP and don't want to wait for Hardy?
I could compile it myself, sure, but it'd be nice for it to integrate
nicely into the package manager. And Linux is hardly attractive to the
Windows crowd if they have to compile from source or {update,wait for
the next version of} their distro just to get a feature that's supposed
to be _in the current release_ much less a new version.
I don't understand why most users should have to wait that long. It
shouldn't take much to test the code. There's very little of it, and a
lot is the same as every other app that uses the GtkPrint API. I'd be
several security upgrades that do get pushed have a larger quantity of
untested code. Like Firefox revisions.
And this doesn't even replace any code that may have worked before.
Gutenprint seems to be happy to co-exist with the new plugin, so people
can always just use the old plugin.
What does it take to test the print plugin and have it be deemed worthy
of getting into Gutsy? I'd be happy to help test it if no one else will.
( Perhaps it's worth slightly rethinking the upgrade policy? Several people
I've suggested Linux to complain that Ubuntu makes it difficult to get new
versions of some program they like to use. In comparison, in Windows one can
just go and install the new version. Whereas I couldn't play with the GIMP 2.4
rc's because the package in Feisty was a bugfix and maintenance version behind.
Would it be sensible/feasible to have something sort of in between the current
stable and grabbing the alphas and betas of the next release? A
repository/release-schedule for those who aren't on systems that must be up
150% of the time and can handle code that's only been tested for a few weeks as
opposed to 6 months if it means we can get reasonably up-to-date packages and
have our packages supported with the upstream bugfixes. )
--
GIMP 2.4's new print dialog is disabled
https://bugs.launchpad.net/bugs/156765
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 156729] Repeat Key dies after resume in Gutsy
Public bug reported: After resuming from a hibernate in Gutsy, particularly a long one, my keyboard often loses the ability to repeat the key. That is, I can no longer hold down the left arrow key to move left. It works for one character and then I have to press and release over and over again. This is extremely annoying. Going to System-Prefs-Keyboard and disabling and enabling the option makes it work again, but I'd rather not have to go through that constantly. I am running a Toshiba Satellite A105 and an up-to-date gutsy system that was upgraded from feisty. I have yet to find the exact trigger for the problem as it does not occur on every resume. However, it has occurred several times already. This problem never occurred throughout constant hibernations in Feisty. ** Affects: ubuntu Importance: Undecided Status: New -- Repeat Key dies after resume in Gutsy https://bugs.launchpad.net/bugs/156729 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 156765] GIMP 2.4's new print dialog is disabled
Public bug reported: Binary package hint: gimp GIMP 2.4 now uses GTK+'s print dialog. (See http://gimp.org/release- notes/gimp-2.4.html ) This is very nice as the gimp-print plugin's dialog is very confusing and sometimes acts weird with respect to CUPS. The build in Ubuntu appears to not be compiled with support for the new print dialog and only prints with gutenprint. I can confirm that the nicer dialog exists in -rc3 from a build of it I made on my other machine a while back. I'm pretty sure that build was compiled with default configure options, but I don't have it recorded anywhere to confirm. (I couldn't do it in Feisty because the repositories did not wish to update from GTK+ 2.10.11 to 2.10.13 and GIMP 2.4 depends on the latter due to bugs in the one shipped in Feisty.) Anyway, could the package be compiled to include support for the new dialog? It's a much more convenient and easy to use dialog than the original messy gutenprint/gimp-print one. (Incidentally, now that the final stable version of GIMP 2.4 is released, will Ubuntu Gutsy get an updated package? The changes are just bugfixes and the Release Candidate on the splash screen looks really unpolished and unprofessional.) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- GIMP 2.4's new print dialog is disabled https://bugs.launchpad.net/bugs/156765 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 128320] Re: [gutsy] special keys on laptop don't work on Toshiba Satellite A105
Confirmed on Satellite A105-S4254. In Feisty, the function keys mostly did stuff, (although most of it was broken) but now they generate the exact same keycodes as without the Fn key. -- [gutsy] special keys on laptop don't work on Toshiba Satellite A105 https://bugs.launchpad.net/bugs/128320 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 155030] Brightness applet flickers on Toshiba Satellite A105 (A105-S4254)
Public bug reported:
Binary package hint: hal
The brightness applet now causes the screen to flicker on a Toshiba
Satellite A105-S4254. When using the applet, the screen flashes on and
off between two brightnesses. Going through it a step at a time shows
that the brightness appears to wrap around a bunch and flicker back and
forth. (With a switch every 3-4 clicks)
I know the screen is capable of more than two settings because the Fn-keys
worked on the Windows side and I can cat from and echo into
/proc/acpi/video/GFX0/LCD/brightness to change things. (Although the latter
isn't very uniform. I don't remember if the settings are the same as the
Windows ones; haven't booted there for a while. Will check sometime later.)
-- For the record, the Fn-keys report Fn-less keycodes in Gutsy, and in Feisty
they blanked the screen and made it come back in about half a second with no
change in brightness.
When unplugging the AC cord, the screen flickers a ton and then settles
on the lower setting. This hurts my eyes a lot. I can work around this
by making it only dim the screen by 7%. Except that the dim screen when
idle option still makes it flicker, and I'd like it to work.
The brightness applet does not appear to affect
/proc/acpi/video/GFX0/LCD/brightness at all.
In Feisty, it didn't work at all.[1]
The contents of /proc/acpi/video/GFX0/LCD/brightness:
levels: 75 35 10 25 35 50 60 75 90 100
current: 100
[1] Actually, the bug may have existed in a form in Feisty as well:
Background: So, when I first installed Feisty, the brightness applet did
absolutely nothing. In fact it had a little crossed out sign. I added
little scripts in /etc/acpi/{ac,battery}.d to brighten and dim the
screen with /proc/acpi/video/GFX0/LCD/brightness and all was well.
Reasonably.
Some time later I noticed that it would flicker a bit when I pulled the
cord, but I paid little attention to it. It wasn't as bad as the Gutsy
default. Also, the little brightness notify thing didn't appear on the
screen then. (The popup was what prompted me to play with the brightness
applet in Gutsy.)
My guesses are that what changed between the two events is hal, because
I at some point enabled feisty-backports and there is a new hal in
there. Although, the brightness popup didn't appear in Feisty. I don't
know if that's because the brightness applet still didn't work or if the
old gnome-power-manager didn't display those. (And doing a downgrade and
then an upgrade and so on is kind of annoying.)
(Because of that, and the fact that the brightness applet's source code shows
that it's just a dbus frontend to hal, I set the package to hal instead of
gnome-power-manager.)
** Affects: hal (Ubuntu)
Importance: Undecided
Status: New
--
Brightness applet flickers on Toshiba Satellite A105 (A105-S4254)
https://bugs.launchpad.net/bugs/155030
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 155216] network-manager fails to stop properly when connected to wireless
Public bug reported: Binary package hint: network-manager NetworkManager hangs the shutdown process for me if connected to a network. I rebooted several times, doing nothing but set up the network and then restarting and each time this was reproducible. Steps to Reproduce: 1. Set the kernel to boot without the quiet option, so it's possible to see what's happening (or whichever option it was) 2. Connect computer to wireless 3. Logout - Restart The restart hangs at killing NetworkManager. Pressing the power button at this point makes the process start over, this time shutting down instead of restarting, and it succeeds in killing NM. There is a warning between system-tools-backends and NetworkManager (before NM) about not being able to kill a certain PID because it doesn't exist anymore. This PID is not that of NM. (Probably some service was already killed and it was trying to kill it again.) After this, the computer needs to be manually turned on since it is shutting down instead of restarting. (Note: on the one time I tried this when I had hibernated in between, pressing the button didn't work and I had to hold it down and power down without shutting down cleanly.) I am running an up-to-date Gutsy install that was updated from Feisty. Wireless card: ipw3945 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- network-manager fails to stop properly when connected to wireless https://bugs.launchpad.net/bugs/155216 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 138338] man page out-of-date
Public bug reported: Binary package hint: file-roller The man page of file-roller is out of date. Compare man file-roller to file-roller --help (The source tarball does not (I think) provide a man page, so I presume this is an issue with the package.) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- man page out-of-date https://bugs.launchpad.net/bugs/138338 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 117808] Re: totem-mozilla does not replay videos when stopped in the middle
I use totem-gstreamer. (I presume this is the default? I do not remember ever messing with the settings.) The link to the video is the thumbnail. Sorry for not mentioning it before. The problem occurs on every site which links to a video that I can find (which, admittedly, isn't all that many), including: http://www.fsf.org/resources/formats/playogg (The video is the You can then test to see that... bit of the VLC-related section) http://macslow.thepimp.net/?p=110 The problem occurs on both the ogg file and the avi. -- totem-mozilla does not replay videos when stopped in the middle https://bugs.launchpad.net/bugs/117808 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 117808] totem-mozilla does not replay videos when stopped in the middle
Public bug reported: Binary package hint: totem-mozilla The totem-mozilla plugin seems to have difficulties playing a video if you stop its downloading in a middle and then reopen the video. Steps to Reproduce: - Open Firefox - Go to http://community.linux.com/community/07/05/17/1640207.shtml?tid=41tid=12 - Middle-click the link to the video - A few seconds in, close the tab - Middle-click the link again - Restart Firefox - Click the link again - Let the video go to completion (sorry the test case is kinda long) - Close the tab and re-open the video Expected Results: The video plays in all four attempts. Actual Results: The video does not play in the second attempt, when one opens a video again after closing the tab once. Reproducible: I have managed to reproduce this in all tests so far I am using Ubuntu Feisty Fawn, and have the latest versions of all the packages available in the repository. To the best of my knowledge, I have no third-party packages that relate to totem-mozilla installed. ** Affects: totem (Ubuntu) Importance: Undecided Status: Unconfirmed -- totem-mozilla does not replay videos when stopped in the middle https://bugs.launchpad.net/bugs/117808 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 69331] Re: Open folder icon cannot be stretched without blurring.
I don't think it's a problem with index.theme or whatever... the new svg simply isn't included. Place that attached SVG in /usr/share/icons/Human/scalable/status and run cd /usr/share/icons/Human/scalable/status sudo ln -s folder-drag-accept.svg gnome-fs-directory-accept.svg sudo gtk-update-icon-cache /usr/share/icons/Human -f It works if you do that. A similar SVG but greyscaled is needed at folder-visiting.svg and gnome- fs-directory-visiting.svg to fix the other missing icon. (Which was actually the original subject of the bug report it seems.) -- Open folder icon cannot be stretched without blurring. https://bugs.launchpad.net/bugs/69331 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
