[Bug 1835912] [NEW] Notmuch package recommends various MUAs, but if NeoMutt is installed, none of the recommended list should be
Public bug reported: The notmuch package recommends: Recommends: elpa-notmuch | notmuch-vim | notmuch-mutt | alot, gnupg- agent, gpgsm By default it will try to an MUA, and that will be elpa-notmuch if you don't have any other. However, if you already installed NeoMutt, that also works with notmuch. It's not the same as notmuch-mutt. (In fact, the notmuch-mutt package is unhelpful and a source of confusion if using NeoMutt, because NeoMutt has the functionality built in, and it's possible to mistakenly think you need to follow notmuch-mutt docs and update your .muttrc, but you shouldn't.) When NeoMutt is installed, it doesn't install notmuch, because it only needs the library, libnotmuch. That means, if NeoMutt is installed, you may later install notmuch (as I did to get `notmuch insert` and `notmuch tag` functions), and then it tries to install another MUA. Same if you install them in one command. I think it would be proper to add neomutt to the list so this doesn't happen: Recommends: elpa-notmuch | notmuch-vim | notmuch-mutt | alot | neomutt, gnupg-agent, gpgsm I suggest it would be helpful, to a user wishing to try out notmuch, to put neomutt ahead of notmuch-mutt (at least), simply because notmuch- mutt is a bit clunky to use unlike the integrated notmuch in all the other MUAs in that list, but that's a policy decision so I'll stay out of that :-) ** Affects: notmuch (Ubuntu) Importance: Undecided Status: New ** Affects: notmuch (Debian) Importance: Undecided Status: New ** Also affects: notmuch (Debian) 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/1835912 Title: Notmuch package recommends various MUAs, but if NeoMutt is installed, none of the recommended list should be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notmuch/+bug/1835912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
For what it's worth, I'm still seeing set-name having no affect on a server's only interface. Server is using Ubuntu 19.04, with netplan.io-0.96-0ubuntu4.1, AMD64 arch. It's a bare-metal server with a single "e1000e" ethernet device. No cloud-init installed. Config file /etc/netplan/01-netcfg.yaml starts like this: network: version: 2 renderer: networkd ethernets: enp4s0: match: name: enp4s0 set-name: eth0 addresses: - $IPV4 - $IPV6 (etc.) The interface is configured adequately in boot, but the interface name is not changed according to "set-name eth0". It just doesn't change, with "netplan apply" or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645555] Re: Dropbear initramfs hook creates authorized_keys file in an invalid folder
The temp directory is fine, because the script also generates /etc/passwd setting root's home directory to be the temp directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/164 Title: Dropbear initramfs hook creates authorized_keys file in an invalid folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579552] Re: libcoro-perl not available in Ubuntu 16.04 LTS
Looks like nobody is going to pick this up any time soon, even though Debian have released a fix. Is there anything I can do to help? Thanks, -- Jamie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579552 Title: libcoro-perl not available in Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcoro-perl/+bug/1579552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1579552] Re: libcoro-perl not available in Ubuntu 16.04 LTS
Now that Debian has released a fix, any chance of Ubuntu packaging the same fix? Thanks, -- Jamie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579552 Title: libcoro-perl not available in Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcoro-perl/+bug/1579552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579552] Re: libcoro-perl not available in Ubuntu 16.04 LTS
** Changed in: libcoro-perl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579552 Title: libcoro-perl not available in Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcoro-perl/+bug/1579552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579544] Re: vmhgfs-fuse inconsistencies cause Git index corruption and Bus Error crashes; older vmhgfs was fine
I am using this patch to fix the specific problem with rename()
which looks like a clear bug no matter what the cache behaviour.
In trivial tests, Git has started behaving after this. I haven't
stress tested it to see if other cache consistency issues still
cause problems.
This patch doesn't fix cache consistency in general, and it doesn't
address other changes from vmhgfs such as less control over file
permissions than before.
If it's going to use a fixed cache timeouts without checking,
it should probably do what NFS does: close-to-open consistency
and unlock-to-lock consistency, which applications have
historically been ok with.
--- open-vm-tools-10.0.7-3227872/vmhgfs-fuse/main.c~ 2016-02-16
20:06:49.0 +
+++ open-vm-tools-10.0.7-3227872/vmhgfs-fuse/main.c 2016-05-09
05:56:59.423936135 +0100
@@ -622,6 +622,7 @@ hgfs_rename(const char *from, //IN: fro
res = HgfsRename(absfrom, absto);
HgfsInvalidateAttrCache(absfrom);
+ HgfsInvalidateAttrCache(absto);
exit:
LOG(4, ("Exit(%d)\n", res));
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579544
Title:
vmhgfs-fuse inconsistencies cause Git index corruption and Bus Error
crashes; older vmhgfs was fine
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1579544/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572211] Re: vmhgfs module not built
The project maintainers are welcome to declare vmhgfs unsupported, but until they do I think the current situation is a regression in functionality. vmhgfs-fuse just isn't a functional replacement yet. (Background: I am using VMWare Fusion 8.0 on a Mac. I had a working system which has broke on upgrading to Ubuntu 16.04 due to vmhgfs going away, and unfortunately after trying a number of methods I still haven't found a solution to replace it. NFS and CIFS to the host have not worked out, and Samba client is currently broken. I am rather desparately now trying a patched vmhgfs-fuse, but having vmhgfs kernel module available would be more welcome.) ** Changed in: open-vm-tools (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572211 Title: vmhgfs module not built To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1572211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572211] Re: vmhgfs module not built
The vmhgfs-fuse client is too buggy to use for some things, such as running Git, as reported (by me) at https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1579544 Even if that's fixed, the vmhgfs-fuse client has different behaviour with file permissions and creating files on the host, compared with the vmhgfs kernel module. So until vmhgfs-fuse supports most of the functionality and fairly reliably, it would still be useful to be able to use the vmhgfs kernel module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572211 Title: vmhgfs module not built To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1572211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579552] [NEW] libcoro-perl not available in Ubuntu 16.04 LTS
Public bug reported: I am surprised nobody reported this as a bug, so I have created it as a placeholder. Anyone who searches for the present status of Coro with Perl 5.22 will quickly find there are maintenance problems due to differences of opinion. Builds fail, and it is understandable that it would be dropped or deprioritised. On the other hand, it does have a number of innocent users who have done nothing wrong except use it, and dependent packages that fail to build, and it's not easy to replace its functionality. It's an unpleasant surprise to upgrade a server to Ubuntu 16.04 and find a load of Perl code stopped working which is difficult to fix (without rearchitecting applications), simply due to the minor version change to Perl 5.22 which isn't supposed to break that much. There are a few proposed patches around. However this patch by Nicholas Clark is the only one I've seen that makes the claim to avoid affecting the Perl installation or binary compatibility: http://www.nntp.perl.org/group/perl.perl5.porters/2016/05/msg236195.html I don't know if that patch is adequate but if it is, given the LTS status of Ubuntu 16.04 meaning it is unlikely to change Perl minor version, if that patch makes libcoro-perl work and the dependent packages build again, it would seem a good thing to do. ** Affects: libcoro-perl (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/1579552 Title: libcoro-perl not available in Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcoro-perl/+bug/1579552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579544] [NEW] vmhgfs-fuse inconsistencies cause Git index corruption and Bus Error crashes; older vmhgfs was fine
Public bug reported: Summary: The switch from vmhgfs to newer vmhgfs-fuse (in open-vm-tools) results in data corruption and bus errors, due to particularly bad cache coherency issues. I noticed this when using Git. Detail: I'm running Ubuntu 16.04 in a VM on my Macbook using VMware Fusion 8.0. I use VMware Fusion's folder sharing to access the Mac's home directory from Linux. >From the Linux point of view, this is vmhgfs. Previously I was running an older version of Ubuntu, and I upgraded it recently. Following the upgrade, I found the vmhgfs kernel module was no longer available, vmhgfs-fuse was packaged as part of open-vm-tools, and the syntax needed in /etc/fstab changed significantly. This was inconvenient at the time, but not a serious problem. What has emerged as a serious problem, though, is when I run almost any Git command on one of these shared folders, I get one or both of these errors: - Reports of Git index corruption - Git crashes with a Bus Error Investigations found this test case: $ echo foo > TEST; ls -l TEST; echo longer > TEST.new; mv TEST.new TEST; ls -l TEST; sleep 6; ls -l TEST -rw-rw-r-- 1 jamie jamie 4 May 7 03:26 TEST -rw-rw-r-- 1 jamie jamie 4 May 7 03:26 TEST <-- This should have size 7, not 4. -rw-rw-r-- 1 jamie jamie 7 May 7 03:26 TEST <-- After the 6 second delay it shows the correct size. That's awful behaviour for a filesystem, and it makes vmhgs-fuse quite useless for serious interactions in which we write to the filesystem. The Bus Errors which Git had were due to it calling mmap() with the reported size, and then finding that some of the mapped range was not readable because it wasn't the real size. I tried disabling caching with the documented FUSE options: - entry_timeout=0 - attr_timeout=0 Unfortunately vmhgfs-fuse ignores these. It has its own /hard-coded/ 5 second cache for attributes, separate from FUSE's cache, and it doesn't even notice when it itself is responsible for changing a file on the client size. The fact you can't disable the first and the second doesn't work are individually both quite bad. The source for vmhgfs-fuse defines the hard-coded timeout as CACHE_TIMEOUT in cache.c. Since the old vmhgfs worked, is there a way to install it on Ubuntu 16.04? (This has forced me to stop using vmhgfs-fuse and look for alternatives to access my Mac's home directory from the VM. Unfortunately NFS has user id mapping problems (changing either user id isn't a solution for me), Mac SMB can't convey executability to Linux CIFS (this also breaks Git), and Samba smbclient currently has a bug whereby it can't connect to Mac SMB shares with a password! So I am still looking for a solution! :) ** Affects: open-vm-tools (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/1579544 Title: vmhgfs-fuse inconsistencies cause Git index corruption and Bus Error crashes; older vmhgfs was fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1579544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579540] [NEW] smbclient 4.3.9 can't connect WITH password to OSX share due to NTLMSSP "short signature" & workarounds don't fix
Public bug reported: This bug may be related to the security fixes in Samba 4.3.8 which have broken Samba in a number of scenarios, and #1572301 (OSX clients can't connect) and #1572876 (smbclient can't connect to Windows shares without password). However I didn't see a bug files for Samba as client to a share WITH password. I'm using Ubuntu 16.04 LTS as my client (in a VM on the Mac), connecting to Mac OSX 10.9 which is serving my home directory to the Ubuntu client. I haven't changed the samba configuration files from defaults in any way. The client is running version 2:4.3.9+dfsg-0ubuntu0.16.04.1 of smbclient, libsmbclient, libwbclient, samba-common and samba-libs. The symptoms if I enter the correct password: $ smbclient //Jamies-Macbook-Pro.local/jamie -U jamie WARNING: The "syslog" option is deprecated Enter jamie's password: NTLMSSP packet check failed due to short signature (0 bytes)! NTLMSSP NTLM2 packet check failed due to invalid signature! session setup failed: NT_STATUS_ACCESS_DENIED The options suggested in #1572876 do change the authentication result, but don't make access to the share possible: $ smbclient //Jamies-Macbook-Pro.local/jamie -U jamie \ --option='client use spnego = no' \ --option='client ntlmv2 auth = no' \ --option='client ipc max protocol = NT1' WARNING: The "syslog" option is deprecated Enter jamie's password: protocol negotiation failed: NT_STATUS_NOT_SUPPORTED The SMB server is working fine when the client is Linux kernel CIFS. Unfortunately for me, OSX SMB server doesn't support the POSIX extensions so file permissions are all the same, which is what motivated me to try smbclient and see if the server does better with SMB2/SMB3. ** Affects: samba (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/1579540 Title: smbclient 4.3.9 can't connect WITH password to OSX share due to NTLMSSP "short signature" & workarounds don't fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1579540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 944040] Re: Cannot connect to RDP if host fingerprint changes
I had the same experience *without* any upgrade to Ubuntu. The Remmina client simply stopped working one day. Today I spent several hours on a Windows 7 box trying to work out why "Unable to connect to RDP server". Was it the Windows firewall? Was it McAfee being expired? What does the Windows event log tell us? (It tells us there's a connection, a session is started, and then it's disconnected. Nothing useful.) Was there an authentication problem? How about connecting with no user/password? Was it some obscure need- to-login-at-the-console-first session problem (as happens with SSH sometimes). No, in the end the forums gave the answer: It's Remmina, not Windows. Delete ~/.freerdp/known_hosts and it'll work. I just removed one line from that file, and all my problems were solved. Meanwhile the changes to Windows to try and find the problem were a waste of time and maybe not such a good idea :-) I don't know what went wrong with the signature in ~/.freerdp/known_hosts - as I didn't upgrade the Ubuntu client, and I didn't do anything on the Windows box either (it's been running for years). The only thing I'm aware of is Windows 7 rebooted itself after an automatic update somewhere between Remmina working and not working. But even reboots don't normally cause this problem. I think this might have happened for me once before. Like #27, the workaround is hard to remember because the error message doesn't say anything useful. This is on Ubuntu 13.04, remmina-1.0.0-4ubuntu2, libfreerdp-1.0.1-2ubuntu1. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/944040 Title: Cannot connect to RDP if host fingerprint changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/944040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810327] Re: Synaptics touchpad ceases functioning after suspend and resume
And thank you to Philipp Wendler for mentioning that atkbd.reset fixes it, so that I was able to solve it on mine! Otherwise I would have been rather dismayed and wondered if the new motherboard was faulty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810327 Title: Synaptics touchpad ceases functioning after suspend and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810327] Re: Synaptics touchpad ceases functioning after suspend and resume
I have the same issue on a Fujitsu-Siemens Amilo Si-1520, which is the same motherboard as V3205. Running Ubuntu Natty, touchpad doesn't respond after resume. I can confirm that adding atkbd.reset=1 to the boot kernel command line fixes it for me too. I'm using a kernel.org vanilla kernel, 2.6.39-rc7-00211-gc1d10d1. (I was quite surprised that I couldn't find anywhere else to set the flag other than the boot command line, so I had to reboot to find out. Is this not one of the purposes of sysfs?) It is reported elsewhere that downgrading the BIOS version to 1.10 also fixes the problem of touchpad unavailable after resume, however that isn't an option if using certain newer CPUs on these laptops, the manufacturer claims that Vista requires a later BIOS, and (worst of all) searching for the BIOS upgrade on the manufacturer's support site reveals a program that only runs on Windows Vista. I did not have this problem for several years, but a couple of days ago I replaced the motherboard due to a broken power connector, and then I noticed touchpad not working after resume. It seems very likely this is because the replacement had a newer BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810327 Title: Synaptics touchpad ceases functioning after suspend and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673236] Re: maverick toolchain producing unbootable (hanging) kernels
Hi Leann,
The patch you said is included upstream was reverted the next day in
v2.6.38-rc2, so the reason given for Fix Released status is not
applicable.
I don't have permission to revert the status change, so please do that
if you agree.
$ git describe --contains 6b35eb9ddcddde7b510726de03fae071178f1ec4
v2.6.38-rc2~32^2~1
commit 6b35eb9ddcddde7b510726de03fae071178f1ec4
Author: Ingo Molnar
Date: Wed Jan 19 10:09:42 2011 +0100
Revert "x86: Make relocatable kernel work with new binutils"
This reverts commit 86b1e8dd83cb ("x86: Make relocatable kernel work with
new binutils").
Markus Trippelsdorf reported a boot failure caused by this patch.
It might be that the issue does not occur with the binutils in Oneiric
anyway, as the reverted kernel patch (86b1e8dd83cb) mentions a binutils
version range with an upper limit. I have not tried building a kernel
with CONFIG_RELOCATABLE=y on Oneiric to find out. If binutils behaviour
was changed a second time, fixing this issue, it might be more helpful
to backport the binutils change to Maverick instead of a kernel change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673236
Title:
maverick toolchain producing unbootable (hanging) kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/673236/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804585] [NEW] BBC Radio 4 Extra not supported in pre-Oneiric versions
Public bug reported: This patch released on 2 April adds supported for BBC Radio 4 Extra: http://lists.infradead.org/pipermail/get_iplayer/2011-April/001230.html and is incorporated in the get-iplayer packaged for Ubuntu Oneiric: https://launchpad.net/ubuntu/+source/get-iplayer/2.79-2 with this changelog: get-iplayer (2.79-2) unstable; urgency=low * Patch for Radio 4 Extra support -- Ubuntu Archive Auto-SyncSat, 30 Apr 2011 12:47:15 + Although this is far from a priority item, as long as Ubuntu Oneiric is not ready for general use, I think users of Natty and maybe earlier Ubuntu versions would appreciate get-iplayer seeing all the channels. Until googling to find this patch, I thought a BBC programme I was looking for was simply unavailable via get-iplayer, thinking maybe they'd started using DRM or a new incompatible scheme. But no, it's just that get-iplayer hard-codes the channel list. I have applied the patch to Natty's get_iplayer 2.79-1 and it checked that it works perfectly. (Except that it doesn't automatically fetch the new channel until you do --refresh, but I am sure that is a quirk/bug in all versions.) Therefore I think this patch should be backported at least to Natty and perhaps older Ubuntu versions (it's such a trivial patch it probably applies easily.) I don't need this change personally, as I simply run the patched get_iplayer on Natty. But I think other users would appreciate it. Ideally the list of channels would be downloaded periodically from somewhere, just like the content listings, but for now it is hard-coded into specific versions of get-iplayer, which unfortunately means users of properly released Ubuntu versions depend on this kind of backport to keep up with channel changes. ** Affects: get-iplayer (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/804585 Title: BBC Radio 4 Extra not supported in pre-Oneiric versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/get-iplayer/+bug/804585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409119] Re: Configuration of flashplugin-installer succeeds even when download fails
I've hit this bug when upgrading Maverick to Natty, and I've also had it happen a year or two ago during a previous upgrade. The older one: - For some reason after downloading everything in a full GUI-led upgrade, some other package caused the wireless network to turn off and flashplugin then quietly failed to install properly but marked itself as done. It was a proper Ubuntu upgrade, so it's only by chance that I happened to look at the "details" window as it failed and knew what to do. - Maverick to Natty failure. Again a full upgrade (this time I used do-release-upgrade from the command line though.) flashplugin again failed, this time with the same errors as comment #10 - it's trying to resolve "false". Because it shows the full URL, and finished with a permission error rather than an DNS failure (unfortunately my ISP has a wildcard DNS for all failed matches), I wrongly thought it was a Canonical server being temporarily broken, and would be well known and fixed in due course. But no, and looking now, I see it's an old proxy setting in /etc/apt.conf. Here's the thing: That setting is exactly what the original CD-ROM installer had put there. I've never changed it. It says: APT::Authentication::TrustCDROM "true"; Acquire::http::Proxy "false"; That's been there since my first Ubuntu (probably Dapper) from CD-ROM, and not many packages use that setting. It's been there for so long, why did previous flashplugin installers work fine? Has the meaning of Acquire::http::Proxy changed, and flashplugin (perhaps foolishly) decided to depend on the new meaning ,without apt's own upgrade script deleting redundant old settings? Anyway, the main point of *this* bug is it silently leaves "flashplugin-installer" installed and configured but Flash not working. And sometimes, even reinstalling/reconfiguring the package doesn't fix an Ubuntu that's been through quite a few upgrades before getting to Natty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/409119 Title: Configuration of flashplugin-installer succeeds even when download fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 710762] Re: Middle mouse button no longer works
I agree with comment #13 - middle clicking on a mouse's scroll wheel is quite difficult and clicking left+right buttons together is easier. Some mice are worse than others for this (some have too little wheel resistance), but all of them require more care to click on the wheel (without scrolling it) than clicking buttons. So among other things, this is an accessibility issue. Also as I mainly use a laptop, I'm used to clicking the two touchpad buttons for pasting text, so it feels more natural to do that with a separate mouse, on the rare occasions when I use one. But that is of course quite personal. I understand the rationale for upstream's change, but I've never noticed noticed the single button lag or any problems arising from it. But maybe I'm just used to it. Finally, the obvious thing that seems to be missing is a tick box under System -> Preferences -> Mouse to decide this behaviour. Editing xorg.conf for something like this makes no sense when other basic mouse preferences are configured via the GUI. The idea that only power users use middle-click to paste and power users can edit xorg.conf (comment #4) is nonsense (as well as being an example of a logical fallacy). Lots of GUI text-pasting users never edit system files or do any system administration at all, and even some casual users learn that way of pasting. Even if that's minority usage, they aren't the same subset as those who are comfortable using sudo and editing config files - or even using the command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710762 Title: Middle mouse button no longer works -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760131] Re: Power consumption raised significantly in natty
Comment #24, reini wrote on 2011-04-28: > Julian: From this bug's description, it's a regression from maverick, which > comes with 2.6.35. > In the comment to bug #524281 you reference, the big discrepancy is between > 34 and 35, > i.e. it should have been apparent in maverick and not just have appeared in > natty. > IMHO this all points to different bugs with similar symptom Not necessarily. In another area (touchscreen drivers) I recently found to my great surprise that Ubuntu's 2.6.35-28 kernel does not contain all changes in the 2.6.35 vanilla upstream kernel! That was a shock, I expected 2.6.35-28 to be based on 2.6.35 with Ubuntu changes or stability backports. I don't know if that applies to this bug, but don't assume every upstream change between 34 and 35 is necessarily in Maverick's 2.6.35 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760131 Title: Power consumption raised significantly in natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673236] Re: maverick toolchain producing unbootable (hanging) kernels
Working kernels can be built in Maverick with any one of these:
1. Disabled CONFIG_RELOCATABLE. That makes the problem go away,
and it makes a bunch of build warnings go away too (they indicate the
problem, and they really should cause the build to fail, but they just
warn).
2. Use an older Binutils linker. The problem is caused by a change in the
behaviour
of linker build scripts in a particular corner case, which is hit by the
x86 Linux linker script,
but only affects CONFIG_RELOCATABLE=y.
3. Judging by the patch comments below, use a newer Binutils linker. I
haven't tried this.
4. Take a look at mainline kernel commits. For me a patch similar to the older
one below
fixed booting with Maverick built kernels on *32-bit* x86. The "reported
boot failures"
were x86_64 only as far as I can tell, so this might not help with x86_64.
6b35eb9ddcddde7b510726de03fae071178f1ec4
Date: Wed Jan 19 10:09:42 2011 +0100
Revert "x86: Make relocatable kernel work with new binutils"
This reverts commit 86b1e8dd83cb ("x86: Make relocatable kernel work
with
new binutils").
Markus Trippelsdorf reported a boot failure caused by this patch.
The real solution to the original patch will likely involve an
arch-generic solution to define an overlaid jiffies_64 and jiffies
variables.
Until that's done and tested on all architectures revert this commit to
solve the regression.
which reverts the Maverick build fix you are looking for
86b1e8dd83cbb0fcbf3d61d2b461df8be1f528cf
Date: Tue Jan 18 08:57:49 2011 +0800
x86: Make relocatable kernel work with new binutils
The CONFIG_RELOCATABLE=y option is broken with new binutils, which will
make
boot panic.
According to Lu Hongjiu, the affected binutils are from 2.20.51.0.12 to
2.21.51.0.3, which are release since Oct 22 this year. At least ubuntu
10.10 is
using such binutils. See:
http://sourceware.org/bugzilla/show_bug.cgi?id=12327
The reason of the boot panic is that we have 'jiffies = jiffies_64;' in
vmlinux.lds.S. The jiffies isn't in any section. In kernel build, there
is
warning saying jiffies is an absolute address and can't be relocatable.
At
runtime, jiffies will have virtual address 0.
5. Enjoy the thread at http://www.gossamer-
threads.com/lists/linux/kernel/1328685
** Bug watch added: Sourceware.org Bugzilla #12327
http://sourceware.org/bugzilla/show_bug.cgi?id=12327
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673236
Title:
maverick toolchain producing unbootable (hanging) kernels
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673236] Re: maverick toolchain producing unbootable (hanging) kernels
Ok, I've found the problem. Binutils changed the meaning of symbol assignments in linker scripts. It is actually documented, but rather obscurely in /usr/share/doc/binutils/ld/NEWS.gz. This breaks the relocation of "jiffies". It also makes got.plt go away in each vdso (a small improvement). This means there *isn't* a binutils bug. Upstream kernels need a small patch, which I have got ready with some proper explanation and will send after I've had some sleep. -- maverick toolchain producing unbootable (hanging) kernels https://bugs.launchpad.net/bugs/673236 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 673236] Re: maverick toolchain producing unbootable (hanging) kernels
** Also affects: linux Importance: Undecided Status: New -- maverick toolchain producing unbootable (hanging) kernels https://bugs.launchpad.net/bugs/673236 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 633983] Re: Can't boot Maverick beta amd64 live cd on macbook (EFI)
See #673236 for the binutils issue. -- Can't boot Maverick beta amd64 live cd on macbook (EFI) https://bugs.launchpad.net/bugs/633983 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 673236] Re: maverick toolchain producing unbootable (hanging) kernels
I can confirm this problem, although my symptoms are slightly different. I've been using vanilla kernels (tracking kernel.org) since Lucid on my x86 32-bit laptop. After upgrading to Maverick, subsequent built kernels all failed to boot, panicing early with a message about timer IRQ routing and the APIC. After spending a few days (:-/) bisecting, because I thought a new revision must be the cause, I eventually found the exact same git revision and kernel config failed to boot, compared with a previously built kernel that is fine (using it at the moment). I downgraded all the GCC packages to Lucid's version, and the resulting build still failed to boot, in the same way. Then I downgraded Binutils to Lucid's version, rebuilt, and the resulting kernel (a) booted fine (using it at the moment), and (b) had the same symbol map as the kernel built previously before I upgraded Lucid to Maverick. This means Binutils is definitely affecting the kernel build, in a way which causes various boot failures. Comments earlier in this bug, my different symptom, and a mention elsewhere (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/633983/comments/36), imply that the symptoms aren't consistent, except that booting fails. The variation in symptoms is entirely consistent with CONFIG_RELOCATABLE having something to do with it. That is, it looks like random code corruption ;-) When I compare the kernel's Symbol.map built with Lucid vs. Maverick's binutils, and Lucid's gcc (for both), with my particular kernel + config, I see this: - The version built with Maverick's binutils has slightly larger kallsyms tables (just a few bytes). Everything else in Symbol.map looks to be the same size. - In arch/x86/boot/compressed/vmlinux, the ELF section sizes (objdump -h) are the same size in both versions, except .rodata..compressed is about 1.6k smaller in the version built with Maverick. - In arch/x86/boot/compressed/vmlinux.bin, the ELF section sizes are the same size, except in the Maverick-binutils-built version, .rodata is 16 bytes smaller, .param is 32 bytes smaller, and .init.data is 32 byte larger. I'm still looking at the reason for the differences. -- maverick toolchain producing unbootable (hanging) kernels https://bugs.launchpad.net/bugs/673236 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 633983] Re: Can't boot Maverick beta amd64 live cd on macbook (EFI)
I can confirm there is a *Binutils* issue with building kernels on Maverick, which results in boot failures on (at least my) *32-bit* x86 laptop (not a Mac). The symptoms are different to those described here, but consistent. It suggests a miscompilation/mislinking. When building on Maverick, I get a kernel which doesn't boot. When building on the same system, with the same kernel source and config, with just GCC downgraded to Lucid's version, boot fails in the same way. When Binutils is also downgraded, the kernel boots - and the symbol map is at last identical to the kernel I built before upgrading Lucid to Maverick. I mention this here because an earlier comment refers to Binutils. Perhaps this entire bug is due to the Binutils issue? -- Can't boot Maverick beta amd64 live cd on macbook (EFI) https://bugs.launchpad.net/bugs/633983 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
Re: [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
daneel wrote: > I was trying this patch in Arch Linux and reading some clarifications > in the forum (https://bbs.archlinux.org/viewtopic.php?id=108516). > Apparently, this patch is not about IO performance, but only the > scheduling of process in different tty. So, if you launch all in the > same tty is not going to help at all. True. But as it produces such a difference for tasks which are in different ttys (i.e. inside terminal windows, and initial daemons), perhaps it would be good to create scheduling groups for other things too, such as daemons (do they go in their own group when they detach from a tty with the patch, or keep the group they had when they were created?), different classes of background process (especially I/O kernel tasks), and maybe different X applications? I presume it's possible to create new scheduling groups manually, to test the effect on desktop responsiveness? If it's shown to make a good difference, then it'd be possible to look into whether the kernel should do so automatically. Also, there are I/O CFQ cgroups (CONFIG_CFQ_GROUP_IOSCHED) in current kernels. That may be worth looking into in a similar way. -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 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 552221] Re: Volume control icon not present after upgrade to Lucid final
Responding to comment #18, Milan Bouchet-Valat wrote on 2010-05-02: > So we'd need to be sure that the actual wanted behavior is adding the applet. Else, another solution would be to autostart gnome-volume- control-applet when we detect that the applet is not present. - How about *not remove* the gnome-volume-control-applet on upgrade? Most users who care (maybe all) had it there before the upgrade. I'm not sure if the applet changed name; if so, then rename? Also, I suspect the following would also help most affected users. - List the gnome-volume-control-applet under "Add to Panel". It was there in Karmic and earlier as "Volume control applet" or something like that. Because it is no longer shown in "Add to Panel", I assumed for months that it had been removed from the distribution, as I assumed all installed and properly packaged applets would appear in that list. There is really no clue at all that adding "Indicator applet" provides a volume control. Even including "volume" somewhere in the menu's descriptive text would have been helpful. Finally: Sorry, I was wrong in the previous comment about it being much harder to control the indicator-applet with the mouse. I was echoing a complaint elsewhere that it's now a horizontal scrollbar and not controllable with mouse "scroll wheel" or touchpad scroll area. But actually those do still work. (However, I suggest the old applet's visuals are better when scrolling: The gnome-volume-control-applet's changing tooltip gives much better visual feedback about the volume, especially useful when there's nothing currently making a sound. And the old applet shows as muted when slid to the minimum volume; the indicator-applet doesn't.) Thanks -- Volume control icon not present after upgrade to Lucid final https://bugs.launchpad.net/bugs/552221 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 552221] Re: Volume control icon not present after upgrade to Lucid final
I've just upgraded a laptop, in the last 2 days, Jaunty -> Karmic -> Lucid (one upgrade each night). (This was a very vanilla Jaunty installation, previously upgraded from Intrepid and kept the same for ages, very little extra installed, virtually no settings changes, and used by its owner almost exclusively for Firefox.) Afterwards there was no volume control in the task bar. It was previously in a convenient location close to the top right. The comments here say indicator-applet should be installed automatically, but that clearly hasn't happened. (There is an envelope in the task bar, but it is still the Evolution launcher (which was there before), and looks like an open envelope rather than a closed one.) I wasn't surprised the volume control disappeared as the same happened with my laptop, but in my case it's taken me 5 months to discover that's because (a) the upgrade process removes the old applet, but doesn't install the new applet, and (b) for some unclear reason the old volume control cannot be added from the "Add to Panel" menu. For my friend's laptop, I will follow the instructions to manually edit startup applications to run the old applet. The indicator applet would confuse her due to the superfluous envelope, and also the new applet's volume control is much harder to use with a mouse (she has physical difficulties.) -- Volume control icon not present after upgrade to Lucid final https://bugs.launchpad.net/bugs/552221 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 468923] Re: [i945] X server crash on Intel 945GM
I'm sorry to report that I experience complete X crashes with 945GM about every
2 weeks.
I've had the laptop about 4 years and run Ubuntu continuously on it, upgrading
to each release.
The crashes have been noticably worse since Lucid. There have been some
Ubuntu releases that didn't crash, so I'm fairly confident it is not the
hardware.
I always run without compositing - that is, "Visual Effects" = "None".
At first I thought it might be due to the introduction of KMS, so I have
checked whether booting with/without KMS ("nomodeset" to the kernel) makes a
difference. It certainly affects the bootup screen (it's obviously not been
tested much with nomodeset ;-) ), but it doesn't stop the crashes (or screen
corruption -- see
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/378794/comments/22).
When it happens, it tries to restart X and that always fails - so
eventually it stops trying, and offers to run in "low graphics mode".
However, once, it didn't even do that, instead it had the appearance of
repeatedly trying to restart X forever.
That suggests the hardware, or the kernel, can get into a state where
the X driver cannot reinitialise it.
Whatever that state is, it's probably a clue to what the cause of
crashing is.
--
[i945] X server crash on Intel 945GM
https://bugs.launchpad.net/bugs/468923
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 378794] Re: [i945] Intel 945GME screen corruption
I also get occasional complete crashes of the X server, about once every
2 weeks (average). I guess that's a different bug, but they might be
related. It is very annoying as all applications are killed instantly.
When that happens, it tries to restart X and that always fails - so
eventually it stops trying, and offers to run in "low graphics mode".
However, once, it didn't even do that, instead it had the appearance of
repeatedly trying to restart X forever.
That suggests the hardware, or the kernel, can get into a state where
the X driver cannot reinitialise it.
I have checked whether booting with/without KMS ("nomodeset" to the
kernel) makes a difference. It certainly affects the bootup screen
(it's obviously not been tested much with nomodeset ;-) ), but:
The X display issues - this block pixel corruption, and occasional
crashes - are the same with and without KMS. So it can probably be
ruled out as the cause.
--
[i945] Intel 945GME screen corruption
https://bugs.launchpad.net/bugs/378794
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 378794] Re: [i945] Intel 945GME screen corruption
Fwiw, I get a lot of screen corruption with Karmic and now Lucid, but it looks different to all the screenshots in prior comments. I notice it mostly when using Gnome Terminal - usually a block of characters is drawn blank (as if spaces), but occasionally (~25% of the time) will contain a corrupt spattering of pixels. But that's probably because I use the terminal more than anything else. It does sometimes happen when rendering in Firefox. I'll try to get a screen shot next time. My system is a laptop with Intel 945GM, and I have not enabled compositing (Visual Effects == None). I've had problems with the X Intel video drivers from all versions of Ubuntu since about Hoary Hedgehog (maybe earlier), including a different type of corruption in Jaunty (which I haven't seen since), but the "block of pixels misdrawn" corruption seems to be only the last two releases. -- [i945] Intel 945GME screen corruption https://bugs.launchpad.net/bugs/378794 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
Re: [Qemu-devel] [Bug 595117] Re: qemu-nbd slow and missing "writeback" cache option
Serge Hallyn wrote: > The default of qemu-img (of using O_SYNC) is not very sensible > because anyway, the client (the kernel) uses caches (write-back), > (and "qemu-nbd -d" doesn't flush those by the way). So if for > instance qemu-nbd is killed, regardless of whether qemu-nbd uses > O_SYNC, O_DIRECT or not, the data in the image will not be > consistent anyway, unless "syncs" are done by the client (like fsync > on the nbd device or sync mount option), and with qemu-nbd's O_SYNC > mode, those "sync"s will be extremely slow. Do the "client syncs" cause the nbd server to fsync or fdatasync the file? > It appears it is because by default the disk image it serves is open > with O_SYNC. The --nocache option, unintuitively, makes matters a > bit better because it causes the image to be open with O_DIRECT > instead of O_SYNC. [...] > --cache=off is the same as --nocache (that is use O_DIRECT), > writethrough is using O_SYNC and is still the default so this patch > doesn't change the functionality. writeback is none of those flags, > so is the addition of this patch. The patch also does an fsync upon > "qemu-nbd -d" to make sure data is flushed to the image before > removing the nbd. I really wish qemu's options didn't give the false impression "nocache" does less caching than "writethrough". O_DIRECT does caching in the disk controller/hardware, while O_SYNC hopefully does not, nowadays. -- Jamie -- qemu-nbd slow and missing "writeback" cache option https://bugs.launchpad.net/bugs/595117 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 533982] Re: WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440 serial_unthrottle 0x7b/0x80 [usbserial]()
I have just had 3 of these kernel warnings with backtraces while using my USB serial adapter. I'm using the current kernel released with Lucid, on 32-bit x86. My serial adapter is an Arkmicro Technologies Inc. ARK3116 Serial. It's not just innocuous warnings. A script talking to the device at the other and of the serial cable is getting garbage back from the serial port. I've seen the garbage repeatedly during an hour long session (in fact, can't use the script - the data coming back is too unreliable). Specifically, it contains repeated portions of text sent earlier, over and over. strace confirms the kernel serial driver is returning these repeated bits of text, not a bug in the script. It's using Perl and libexpect-perl. Strangely, when I use minicom to talk to the device manually I don't get these repeated selections of old text back. I had suspected the device at the other end, until I started getting apport crash reports towards the end of my hour long session. Now I suspect a bug in the usb-serial driver or the tty layer - both were changed near this kernel version. I will keep a copy of my script, to see if this can be reproduced another time. Rather than a one-off, this looks quite likely to duplicated as at least some of these other reports: #533982 WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440 serial_unthrottle 0x7b/0x80 [usbserial]() #433604 WARNING: at /build/buildd/linux-2.6.31/drivers/usb/serial/usb-serial.c:448 serial_unthrottle+0x76/0x80 [usbserial]() #471157 WARNING: at /build/buildd/linux-2.6.31/drivers/usb/serial/usb-serial.c:446 serial_unthrottle+0x76/0x80 [usbserial]() #470007 WARNING: at /build/buildd/linux-2.6.31/drivers/usb/serial/usb-serial.c:446 serial_unthrottle+0x76/0x80 [usbserial]() #407939 System freeze after WARNING: at /build/buildd/linux-2.6.31/drivers/usb/serial/usb-serial.c:374 serial_write+0xb9/0xc0 [usbserial]() #286703 WARNING: at /build/buildd/linux-2.6.27/drivers/usb/serial/usb-serial.c:311 serial_write+0xa4/0xb0 [usbserial]() #438311 WARNING: at /build/buildd/linux-2.6.31/drivers/usb/serial/usb-serial.c:401 serial_write+0xbb/0xc0 [usbserial]() Notice a common theme? They are all USB serial. These are my variations on the warnings: Mar 19 10:16:17 localhost kernel: [33130.516205] usb 3-2: new full speed USB device using uhci_hcd and address 2 Mar 19 10:16:17 localhost kernel: [33130.672508] usb 3-2: configuration #1 chosen from 1 choice Mar 19 10:16:18 localhost kernel: [33130.698253] usbcore: registered new interface driver usbserial Mar 19 10:16:18 localhost kernel: [33130.698283] USB Serial support registered for generic Mar 19 10:16:18 localhost kernel: [33130.698343] usbcore: registered new interface driver usbserial_generic Mar 19 10:16:18 localhost kernel: [33130.698348] usbserial: USB Serial Driver core Mar 19 10:16:18 localhost kernel: [33130.700253] USB Serial support registered for ark3116 Mar 19 10:16:18 localhost kernel: [33130.700275] ark3116 3-2:1.0: ark3116 converter detected Mar 19 10:16:18 localhost kernel: [33130.727487] usb 3-2: ark3116 converter now attached to ttyUSB0 Mar 19 10:16:18 localhost kernel: [33130.727527] usbcore: registered new interface driver ark3116 Mar 19 12:34:53 localhost kernel: [41446.080220] [ cut here ] Mar 19 12:34:53 localhost kernel: [41446.080240] WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:406 serial_write_room+0x75/0x80 [usbserial]() Mar 19 12:34:53 localhost kernel: [41446.080247] Hardware name: Amilo Si 1520 Mar 19 12:34:53 localhost kernel: [41446.080251] Modules linked in: ark3116 usbserial binfmt_misc ppdev kqemu kvm_intel kvm sha256_generic aes_i586 aes_generic dm_crypt joydev snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy arc4 snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device sbp2 iwl3945 snd iwlcore soundcore mac80211 ricoh_mmc sdhci_pci sdhci led_class psmouse serio_raw snd_page_alloc cfg80211 lp parport fbcon tileblit font bitblit softcursor vga16fb vgastate ohci1394 i915 drm_kms_helper drm i2c_algo_bit e100 mii ieee1394 video intel_agp output agpgart Mar 19 12:34:53 localhost kernel: [41446.080367] Pid: 9, comm: events/0 Not tainted 2.6.32-16-generic #25-Ubuntu Mar 19 12:34:53 localhost kernel: [41446.080372] Call Trace: Mar 19 12:34:53 localhost kernel: [41446.080386] [] warn_slowpath_common+0x72/0xa0 Mar 19 12:34:53 localhost kernel: [41446.080396] [] ? serial_write_room+0x75/0x80 [usbserial] Mar 19 12:34:53 localhost kernel: [41446.080406] [] ? serial_write_room+0x75/0x80 [usbserial] Mar 19 12:34:53 localhost kernel: [41446.080413] [] warn_slowpath_null+0x1a/0x20 Mar 19 12:34:53 localhost kernel: [41446.080422] [] serial_write_room+0x75/0x80 [usbserial] Mar 19 12:34:53 localhost kernel: [41446.080432] [] ? tty_put_char
[Bug 473615] Re: cryptsetup init scripts are redundant and can break the boot
Just another data point. I've been seeing the "asks for your passphrase 3 times" problem ever since I upgraded to 9.10 back in 2009-10, along with the "press ESC to get a root shell" type message, sometimes twice. I only have /home encrypted. Although it feels a bit like the passphrase input is being eaten by another program, I've tried various combinations of pressing Enter at the passphrase prompts, thinking that maybe at some step through the process, the line I enter will be seen be a passphrase reader and not another process, but with all the combinations I've tried, it always asks again at least once, and I've never seen any other program do anything interesting in response to my typing. In all cases, the characters typed appear as '*'s, not visible. I do use usplash, and have to; the boot gets completely stuck for some reason unknown to me quite early if I boot with the text console. (It was fine in 9.04). I do get occasional random boot lockups, but I've attributed that to KMS, X or some unknown kernel mystery. After all, X locks up every 1-2 weeks anyway (has done since 9.04; Intel 945GM graphics). Luckily for me, apart from occasional boot hangs, I've not had a problem mounting my /home, after typing the passphrase twice or three times. I haven't noticed any changed in behaviour between 2009-10 and now. -- cryptsetup init scripts are redundant and can break the boot https://bugs.launchpad.net/bugs/473615 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 264683] Re: (intrepid) When coming out of hibernate/suspend (resume) in a different physical location, wireless networks are not updated.
Btw, Fixed rather than Invalid, because it's still an issue when using Ubuntu 9.04 and earlier. -- (intrepid) When coming out of hibernate/suspend (resume) in a different physical location, wireless networks are not updated. https://bugs.launchpad.net/bugs/264683 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 264683] Re: (intrepid) When coming out of hibernate/suspend (resume) in a different physical location, wireless networks are not updated.
I am under the impression this was a genuine bug, and it was fixed last year. It was fixed in the kernel, in generic wireless code. Upgrading the kernel is enough to fix it. See "Making NetworkManager work with suspend/resume", http://lwn.net/Articles/321102/ This is consistent with my experience: The bug was fixed for me when I upgraded Ubuntu 9.04 to 9.10. I didn't comment because there was nothing more to add. Therefore this bug should be marked as Fixed, rather than Invalid. -- (intrepid) When coming out of hibernate/suspend (resume) in a different physical location, wireless networks are not updated. https://bugs.launchpad.net/bugs/264683 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 122045] Re: "no response from target" with 0.4.0 up to 0.5.3 but not with 0.3.3
Btw, it was only after about 45 minutes of trying different things, killing NetworkManager, starting vpnc manually and so on that I eventually found this bug report here, and discovered the "Local Port 1" advice which worked. Unfortunately the error "no response" isn't very informative, although it is surely secure. You never know if you've got all the right options for NAT traversal type and other things, so you have to try everything. A suggested recipe going through the known common problems and trying each workaround in turn would be very helpful - if there is a short list of known common problems, that is. -- "no response from target" with 0.4.0 up to 0.5.3 but not with 0.3.3 https://bugs.launchpad.net/bugs/122045 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 122045] Re: "no response from target" with 0.4.0 up to 0.5.3 but not with 0.3.3
Confirmed with vpnc in Karmic. Adding "Local Port 1" makes it work here. The oddest thing is "Local Port 499" works too, and so does "Local Port 501". It looks like port 500 is specifically getting blocked. This is running from home, through a Linksys Etherfast Cable/DSL Router, BEFSR41 V3, to a cable connection. The connection is through Virgin Media in the UK. I have checked the web configuration interface and there seems to be no mention of port 500 anywhere. The router does not have any IPsec or VPN options that might be snooping that port, either. The laptop where I am running vpnc does not have any iptables rules, and all policies are set to ACCEPT. The most annoying thing about this behaviour is there's no obvious way to add the option through NetworkManager, and NetworkManager doesn't use the normal configuration files, so you can't use NetworkManager's VPN controls at all. Because these things always happen from time to time, imho NetworkManager's GUI should offer a way to add arbitrary options or point to a config file to pass to vpnc, for those occasions when you need extra options that it doesn't know about. Its "Mobile Broadband" and "DSL" GUIs have the same problem: when you need to give extra options to pppd for an unusual reason, there is no way to do it, or if there is a way it's obscure. -- "no response from target" with 0.4.0 up to 0.5.3 but not with 0.3.3 https://bugs.launchpad.net/bugs/122045 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 336210] Re: Package description is incomplete and misleading
What is the purpose of this package? For editing PHP files in Emacs, there is also the php-elisp package. >From their descriptions, one could be led to believe they do exactly the same thing. Do they provide different functionality? -- Package description is incomplete and misleading https://bugs.launchpad.net/bugs/336210 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
Re: [Bug 269329] Re: [MASTER] NM 0.7 lacks bluetooth 3g support
Oded Arbel wrote: > I did not manage to get the PAN checkbox at the end of the bluetooth > pairing dialog for either of my Nokia E90 (which may not support it) or > my Ericsson P1i (which does support PAN). I used PAN with a Sony-Ericsson K850i without having to set anything on the phone. Just pair the phone and the computer, then after that, PAN worked using "pand" from the computer. (There was some extra scripting needed because of possible Bluez bugs, to enable HCI encryption first, before PAN worked). I used DUN with a Nokia 6210 Classic without having to set anything on the phone. Just pair the phone and the computer, then after that, with the right settings on the computer, DUN (using RFCOMM) worked using "rfcomm" and "pppd". -- Jamie -- [MASTER] NM 0.7 lacks bluetooth 3g support https://bugs.launchpad.net/bugs/269329 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
Re: [Bug 269329] Re: [MASTER] NM 0.7 lacks bluetooth 3g support
Stefan Nuxoll wrote: > PAN support doesn't cover many bluetooth devices (like my N75) that use > the Bluetooth DUN profile instead. And even those which do support PAN, don't always create an internet connection if the bluetooth paired network is already being used for another purpose like local file sharing. DUN might be a bit more reliable in that case, I'm not sure. -- Jamie -- [MASTER] NM 0.7 lacks bluetooth 3g support https://bugs.launchpad.net/bugs/269329 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 433397] Re: FFe for emacs23
Ouch, that was a surprise. I've been using Karmic with the "emacs" package and therefore emacs23 for a few weeks, without significant problems (just Emacs quirks which I hope will be tidied up in time). Today, update-manager tried to install emacs22, which I didn't want. I appreciate that emacs23 isn't in main, and emacs of course must be. (Since I include universe I hadn't noticed any problems, and just assumed emacs23 was the version to be used in Karmic.) Nonetheless, the surprise installation of emacs22 was undesired. Is it possible to have the "emacs" package depend on emacs22 OR emacs23, and prefer emacs22 if neither is installed already, to avoid this? -- FFe for emacs23 https://bugs.launchpad.net/bugs/433397 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
Re: [Bug 131094] FsOpBench shows only data=writeback with cfq works
Tobias Oetiker wrote: > I have just completed extensive benchmarking on 2.6.31.2 and 2.6.24 > with a new benchmark program I have written, to measure real-world > io performance in high load situations where readers and writers > are compeeting. > > I am looking at HW RAID setups as well a normal single harddrive > situations. The bottom line is that on a single harddrive only > > data=writeback with cfq scheduler > > has decent performance when readers and writers are in competition > and even then, there will be huge outliers of many seconds happeing > every now and then. See > > http://insights.oetiker.ch/linux/fsopbench/ > > for details. Is that with ext4 or ext3? -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 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 418366] Re: hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes
We're discussing this on a bug filed against the Ubuntu Gnumeric package, on the Ubuntu bug tracker, not the Gnumeric upstream bug tracker, so my apologies if people accidentally found themselves here without knowing much about Ubuntu ;-) Karmic is the name of the current Ubuntu development release; it's where I'd expect the upstream package to appear eventually. Unfortunately that may be bit slow if there's no Ubuntu packager tracking this bug report. I thought that was you because of your fast response; sorry for my mistake. There's a separate bug tracker for Gnome and Gnumeric upstream, and I understand you relayed this bug to there (thank you). I understand that hlookup() and vlookup() were incorrectly sharing the same cache. Just to check, can you confirm that lookups in different sheets in the same workbook use separate caches too? Since you're there, please pass on that the match() function should be cached in the same way as hlookup() and vlookup(). In fact you can write hlookup() and vlookup() in terms of match(), which is what I did to workaround this bug. (I also found it's the only way to make a sheet that also works in OpenOffice.org, which doesn't support the as_index option. That's what match() is for (in conjunction with offset()); as_index was never really needed). Thanks for your help getting the bug fixed. I look forward to testing it when it percolates downstream. -- hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes https://bugs.launchpad.net/bugs/418366 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 418366] Re: hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes
I'll try the fix as soon as there's a package for it. Let me know if you have a test package which works on Karmic, if it's not in Karmic. I tried compiling from upstream source, but there were too many library dependencies; I didn't have time to chase them all down. -- hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes https://bugs.launchpad.net/bugs/418366 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
Re: [Bug 418366] Re: hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes
Andreas Guelzow wrote: > When you open the file you see the results stored in the file. Gnumeric > will not recalculate automatically since you want to see what was > stored. Understood. > When you press F9 you are recalculating and you see the answer > your current version of Gnumeric produces. Not really. The results stored in the file were produced by the _same_ version of Gnumeric after editing those formulae. The purpose of this file is to show that F9 changes the results from what the same version of Gnumeric already calculated - which it should never do, when there are no circular dependencies. > Are you seeing any changes on further F9s? Yes I have, as the report explains: I have seen a series of changes on up to three F9 presses in a row, but I have not been able to produce a file showing it. > After the recalculation in a current version of Gnumeric I see 2005-2006 > in C6, 2007-2008 in D6 and #N/A in C7:D8. This all seems correct to me. You are right. I accedentally omitted to set as_index to TRUE in the inner vlookup calls in this file, as I was editing it so much and nothing I did produced working formulae. No, I wasn't trying to be Excel compatible, I was trying to demonstrate a problem and made a mistake in those formulae because the correct formulae produced the same error. Append TRUE to the arguments of the inner vlookup formulae, and you'll see it still shows #N/A. That's the basic problem. > On first glance, the #N/A in F6 to F8 seems to be incorrect. Yes. I have managed to workaround the problem by writing hlookup+vlookup using the match function instead. I suspect match is not cached like hlookup and vlookup (it probably should be, once the cache is fixed). -- hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes https://bugs.launchpad.net/bugs/418366 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 418366] [NEW] hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes
Public bug reported: Binary package hint: gnumeric When using the hlookup() and vlookup() functions in a formula, I was quite surprised to see the result often showing as #N/A or #VALUE! when I was sure I was using them correctly. After some fiddling, I confirmed that they are indeed failing to match the right value sometimes. I know they aren't working, because simply editing a formula and not changing it can cause a successfully looked up value to change to an error, or vice versa. Pressing F9 to force recalculation also causes some lookups to start succeeding, and others to start failing. I've seen a F9 cycle through three changes in succession until reaching a stable set of values, but still wrong. At this point you're thinking: does the lookup overlap the cells containing the formulae? No, in fact they are separate sheets. I've attached a file which shows this problem. If it is opened in gnumeric-1.9.9-1ubuntu1 (for Karmic), you should see this: - It should open on the "Buggy lookup" sheet, on cell D6, showing "#N/A". - The correct result for cell D6 is "2007-2008". - Cell C6 shows "2005-2006". It is the same formula as D6, but already showed the correct value. - Cells F6 to F8 show text "Personal allowance (age < 65)", "Basic rate threshold" and "Higher rate threshold". - Those are the correct results for the formulae in those cells. - Cells C7, C8, D7, D8 show "#N/A". Those are the formula I was trying to get right which caused me to notice the hlookup/vlookup problems. They use hlookup and vlookup in the same formula. I've never had a useful result from these (no matter how many times I copy & paste or edit them among sheets), so it's possible they are not correct, but I think they are. They should show numbers, taken from the other sheet called "Tax parameters". Now press F9 (for Recalculate), and you should see a few changes: - Cell D6 changes to show "2007-2008". This shows an incorrect #N/A changing to a correct value. - Cells F6 to F8 change from text results to "#N/A". This shows a correct value changing to #N/A. - Cells C7:D8 change from "#N/A" to "#VALUE!". As I say, I don't know if these formulae are correct as every attempt to use hlookup and vlookup together has failed for me, but I am quite sure they are not meant to change as a result of pressing F9. I have confirmed this bug in gnumeric-1.8.4 in Jaunty (which is the Ubuntu version I am using). I upgraded to gnumeric-1.9.1-1ubuntu1 from Karmic, because I hoped the bug would have been fixed, but it has not. The attached file has only been tested for the exact behaviour described above on gnumeric-1.9.1-1ubuntu1. Therefore this bug affects both Jaunty and Karmic. It seems likely this bug was introduced with the hlookup/vlookup caching changes in Gnumeric 1.8.3 or so. Unfortunately there is no way to disable the cache. It looks like the caching code has not been well tested, especially for this bug to survive so long. Bug #313670 also describes vlookup returning incorrect results, but it appears to be a different bug (though probably in the same code). That bug returns numerically wrong values, whereas this one, as far as I've seen, only returns #VALUE! or #N/A (or -1 if as_index is TRUE); I haven't seen the wrong cell values being found by lookup. Generally I'm happy with Gnumeric - it has been much more reliable than OpenOffice calc at handling sheets from Excel and OpenOffice had lots of rendering errors last time I used it too. Gnumeric's motto is "free, fast, accurate, pick any three". So I'm a bit disturbed to find it giving wrong answers in such a basic function, and to see the answers change on recalculations. Thanks. ** Affects: gnumeric (Ubuntu) Importance: Undecided Status: New -- hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes https://bugs.launchpad.net/bugs/418366 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 418366] Re: hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes
** Attachment added: "Excel file (saved from Gnumeric 1.9.1-1ubuntu1) which shows the bug clearly" http://launchpadlibrarian.net/30784702/gnumeric_bug.xls -- hlookup and vlookup return invalid results, and F9 (force recalculate) can break or fix the result, so can "editing" formula with no changes https://bugs.launchpad.net/bugs/418366 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
I did the debugging work because I thought you (or upstream) might find it useful. Plenty of lockups have been reported but not many where it's possible to observe a faulty kernel or hardware state in detail. Specifically, because of the clues in how the kernel or hardware state was broken and X server restart didn't recover it, I though you or upstream developers would find it useful. But it appears that was a mistake since you weren't interested in analysis, just whether running Karmic for a month locks up less often. (Running it for a day would not be enough). In other words, if I'd just reported it locking up, your response would have been exactly the same: try Karmic, see if it's more reliable. I'm not sure what response you were waiting for, other than 'I ran Karmic and don't get (as many) lockups'. Instead I turned off DRI entirely (on Jaunty), and I get far fewer lockups but have still had one, unfortunately. Presumably the one I had subsequently was a different kind, as the one in this report depends on DRI. ==> So, I have a question: If I do experience lockups when I eventually move to Karmic and re-enable DRI, and it's not a complete system freeze so possible to debug like in this report, should I spend the hours doing that or is it not useful here? Thanks! Btw, why is the new status Invalid and not Closed? This report may be useful to someone else who comes searching in future, especially if the problem reappears, and Invalid bugs tend to be skipped over when searching. -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 361938] Re: qcow2 corruption
See also bug #404394, which suggests there are still qcow2 bugs in the Ubuntu package. -- qcow2 corruption https://bugs.launchpad.net/bugs/361938 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 361938] Re: qcow2 corruption
I was the original submitter of the "qcow2 corruption observed, fixed by reverting old change" thread on the qemu-de...@nongnu.org list, after finding corruption when testing kvm-83. I've just submitted an update to the qemu and kvm lists, saying that the symptom I observed (a blue screen while booting some image) seems to be fixed in kvm-85, but not kvm-84. I'm not sure if the kvm-84 to kvm-85 qcow2 fix is in the latest Ubuntu kvm package, kvm-1:84+dfsg-0ubuntu11 indicated by the previous comment. If it is, that's great. But if the latest package only includes code equivalent to upstream's kvm-84, there's an important qcow2 corruption fix which should still be included. Also, I see from release notes for the later upstream kvm versions that there are further qcow2 corruption fixes in later versions. You may wish to incorporate those too, I don't know. -- qcow2 corruption https://bugs.launchpad.net/bugs/361938 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
Here are some lined grepped from my kernel log at the time of this freeze. I don't think they are related, but you never know. I did a "grep i915 /var/log/kern.log". The initial freeze happens after the entry at time 00:47:30, before the entry at 04:45:10. The entries from 04:45:10 are due to me starting more X servers. ** Attachment added: "Kernel log around the time of testing, 'grep i915 /var/log/kern.log'" http://launchpadlibrarian.net/28982624/i915_kernel_log.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "Fourth X server log, DRI completely disabled, freezes in userspace loop waiting on PP_STATUS reg" http://launchpadlibrarian.net/28982552/X4_no_DRI_stuck_in_loop_gdb.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "Third X server log, with 'Option "DRI" "no"', shows some broken hardware state details" http://launchpadlibrarian.net/28982514/X3_no_DRI_broken_hwstate.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "Second X server log, got stuck in the same during initialisation" http://launchpadlibrarian.net/28982504/X2_DRI_frozen_startup.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "X server log of the first stuck server, same one as straced etc." http://launchpadlibrarian.net/28982487/X_DRI_freeze_log.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "File descriptors when frozen, to relate to strace" http://launchpadlibrarian.net/28982441/X_DRI_freeze_fds.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "strace of X server not responding except mouse moves" http://launchpadlibrarian.net/28982429/X_DRI_freeze_strace.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 398968] [NEW] [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
Public bug reported: Binary package hint: xserver-xorg-video-intel This Intel freeze is one where the mouse kept working, and I was able to login over SSH and do some diagnostics which point to DRI. I have a 945GM chipset, on a laptop. I was able to get some diagnostic output which might help identify the cause. Kernel DRI is implicated: it's stuck in the kernel, but interruptible with a signal (in this type of freeze). But after turning off DRI, the Intel hardware is still in a stuck state, implying it's not necessarily a bug in kernel DRI, just getting stuck due to an unexpected hardware state, which X server initialisation does not clear. I ran GDB on an X server with DRI disabled in this state, and found which memory location it is polling. All my X locking up problems started with upgrade from Intrepid to Jaunty, very soon after Jaunty was released. I recall one lockup with mouse movement soon after the upgrade, but most have been complete freezes without even network access. This was a rare one with mouse working, so I took a closer look. I am not using Compiz, just a standard Ubuntu 9.04 GNOME desktop, and mostly just Firefox, Emacs and Gnome-Terminal. Ubuntu's System > Settings > Appearance > Visual Effects is set to None, and I'd not run any 3d applications. Freeze in ioctl(/dev/dri/card0, DRM_I915_GEM_THROTTLE), mouse still works = This Intel freeze is one where the mouse kept working, and I was able to login over SSH and do some diagnostics which point to DRI. Since updating to Jaunty, I've seen freezes every few days or weeks on my laptop while using X. Usually there is nothing I can do except power cycle - no network, no keyboard response, Alt-SysRq not working. Occasionally though, the mouse keeps working. Kernel version is: 2.6.28-13-generic CPU is 32-bit x86, a Core Duo 2.0GHz with 2.5GB RAM. Graphics is Intel 945GM according to Xorg.0.log. Kernel package: linux-image-2.6.28-13-generic 2.6.28-13.45 X packages: xserver-xorg-video-intel 2:2.6.3-0ubuntu9.3 xserver-common 2:1.6.0-0ubuntu14 xserver-xorg 1:7.4~5ubuntu18 xserver-xorg-core2:1.6.0-0ubuntu14 xserver-xorg-dev 2:1.6.0-0ubuntu14 xorg 1:7.4~5ubuntu18 GPU according to Xorg.log: Intel 945GM. Like many people I've been having apparently random freezes with Jaunty on Intel graphics h/w, and more than one kind of freeze. This time, mouse movement worked: specifically, the pointer moved around in response. However, there was no visible reaction from clicking or key presses or focus changes, and no other screen updates. Just pointer movement. I straced the X server, and saw it blocked on ioctl(0x6458) on /dev/dri/card0; I think that's DRM_I915_GEM_THROTTLE for this chip. Mouse movements interrupted the ioctl() with a SIGIO signal. It handled SIGIO, reading some events, then it went back to calling the DRI ioctl(). This must be why mouse movement worked. See [X_DRI_freeze_strace.txt] for the strace, and [X_DRI_freeze_fds.txt] for the file descriptors. During SIGIO, it called select() on the /dev/input/eventN only. It didn't select on any of the socket descriptors. Because it didn't check any sockets, all attempts to communicate with the X server, including starting a new app from the text console, had no effect on the strace; it remained blocked in the DRI ioctl(). So it's not surprising there was no screen update from apps. Clearly the problem was being stuck in the ioctl(11, 0x6458, 0), and clearly that is not _intended_ to block for long. That was /dev/dri/card0, and I think the ioctl is DRM_I915_GEM_THROTTLE for this chip. Inside the ioctl(), the Xorg process was waiting in kernel function i915_wait_request(), according to "ps -opid,comm,wchan 3971". The numeric WCHAN is 0x6080e if that's helpful. See [X_DRI_freeze_wchan.txt]. It looks like the kernel is broken or the chip is stuck in some "impossible" way. Judging by the way the X server does not try to handle sockets while this call is blocked, I guess it is not supposed to block for long. As last resort, I killed the server: "kill 3971" didn't kill it. "kill -HUP 3971" didn't kill it. "kill -QUIT 3971" did. The Xorg.0.log from this X server is [X_DRI_freeze_log.txt]. You can see from the end that there's nothing interesting at the time it gets stuck. Once DRI is stuck, it stays stuck: = After killing it, gdm automatically started another X server. The new X server started well, judging by it's log. But it only produced a black screen (not even the X stipple background). strace showed it stuck waiting for the same ioctl() as before, on /dev/dri/card0... gdm eventually gave up waiting for it. The Xorg.log from the second X server is [X2_DRI_frozen_startup.txt]. Disabling DRI with [Option "DRI" "no"] broke the X server ===
[Bug 398968] Re: [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen
** Attachment added: "ps WCHAN, confirming it's blocked in the kernel at i915_wait_request" http://launchpadlibrarian.net/28982461/X_DRI_freeze_wchan.txt -- [i945GM] X server gets stuck in loop waiting on DRI, reads mouse events but ignores all socket I/O hence appears frozen https://bugs.launchpad.net/bugs/398968 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 323733] Re: [Compaq Presario CQ60] suspend/resume problem
I have a dmesg output from boot through suspend and it's subsequent resume failure. To answer some questions in earlier comments (although they were directed at someone else): - This lock up + disk I/O errors happens on every suspend/resume I've tried which is about 4 times total in a few hours. All but the one for this dmesg output are simply boot to the desktop, then suspend. - The trace attached with this comment involves a hibernate and resume before the suspend & resume. The hibernate and resume seemed to go ok. I'd provide a cleaner trace, but getting any trace was tricky with all disk I/O reporting errors. The attached dmesg trace comes from: - Boot into Linux. Start Firefox. - Hibernate to disk. - Resume from disk. Seemed to go ok. Not very pretty though, but it did resume back to the working Firefox, after presenting a locked-screen password dialog box. - Switch away from the X login screen to a text console, to reduce the chance that suspend problems are due to video drivers. The NVidia driver is loaded, but similar looking suspend/resume problems have been seen after the NVidia driver was uninstalled and the system restarted. So it does not look like a likely cause. - Login on the text console, and type "pm-suspend". - It suspended ok, though a bit slowly. Windows suspended quite slowly too. - On resume, text console returned showing I/O error messages, eventually ext4 remounted itself read-only, and generally doing anything was tough, but the keyboard and console output did work. - Used a USB flash key plugged in after resume and raw writing with dd to capture the dmesg output. - All the problems may be due to SATA I/O errors. ** Attachment added: "suspend_trace.txt" http://launchpadlibrarian.net/28791911/suspend_trace.txt -- [Compaq Presario CQ60] suspend/resume problem https://bugs.launchpad.net/bugs/323733 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 323733] Re: [Compaq Presario CQ60] suspend/resume problem
I've just tried suspend in Windows Vista on the same laptop (as the previous comment). - Suspend is a bit slow, but works. - Resume is quite fast, about 2 seconds from button press to a Windows desktop. So those slow Linux resumes must be failing at an early stage. -- [Compaq Presario CQ60] suspend/resume problem https://bugs.launchpad.net/bugs/323733 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 323733] Re: [Compaq Presario CQ60] suspend/resume problem
I can confirm the same problems on a Compaq Presario CQ60-219EA with 4GB RAM running 64-bit Jaunty, installed and updated a couple of hours ago. The console shows disk I/O errors, and ext4 eventually decides to remount the disk read-only. When this first happened, I have the NVidia proprietary driver installed and: - Suspend took a long time. I think about 10-20 seconds. - Resume also took a long time in a blank screen phase, and eventually the X mouse pointer appeared, but the remaining desktop didn't, it was all black. - I was able to Control-Alt-F1 to a text console, and that showed disk I/O errors and ext4 remounting read-only. - I was not able to login on the console. Each time I tried, a couple of disk I/O error messages appeared, and then after a few seconds the login: prompt reappeared. On that occasion, after the post-resume broken state, I held down the power button for 5 seconds to power down. Then pressed the power button to start up again, and booted back into Linux. Despite the theoretical power cycle, Linux was unable to complete the boot process, at some point showing messages about CPU#0 and CPU#1 both being stuck and detected by soft-locked. I held down the power button again, to power cycle again, and this time Linux did boot successfully back to the desktop. Then I removed the NVidia proprietary driver, and logged out then into X again. Perhaps unsurprisingly, the screen was a mess, showing neither a good picture as with NVidia, nor the low-resolution extremely slow picture without the drive. Fair enough, who tests driver removal. So I power cycled again. This time it booted and showed the low-resolution extremely slow desktop, confirming the NVidia's driver had gone. So I tried suspend/resume, and got similar results: - Long time to suspend - Nothing useful on resume For one last test, I power cycled again, and this time instead of logging in to X, I switched to a text console after the X login window appeared. (This is still without the NVidia proprietary driver loaded at all during this session). >From the text console, I did "pm-suspend", which took a while but did suspend. Then when I pressed the power button to resume, the power light came on, and eventually the wireless light (very slowly - about 30 seconds to the wireless light), but a blank screen with no backlight. Caps Lock did not respond either, so it wasn't simply a case of no screen. I can only do quite occasional testing of this laptop from here, because all this was in preparing it for someone else. For whom my advice is obviously going to be "don't use suspend, at least for now". -- [Compaq Presario CQ60] suspend/resume problem https://bugs.launchpad.net/bugs/323733 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 336012] Re: bluetooth network PAN fails to connect to mobile phone
I sent a debugging patch to bug #268502, which installs the bluetooth network protocol code from (Hardy's) 2.6.24 into a current Ubuntu kernel, which makes this problem go away. (The problem is not present in 2.6.24 - that kernel doesn't need any of the "hcitool" commands; "pand" is enough). I also tried with various combinations of kernels, both USB bluetooth drivers, and different bluez package versions, and narrowed it down. Altogether it strongly suggests the problem is caused by a change in the bluetooth network protocol code somehere between Hardy's 2.6.24 and Intrepid's 2.6.27, as opposed to any of the userspace packages or bluetooth hardware drivers. It's possible that it's been fixed already in upstream kernels and hasn't yet made it's way into an Ubuntu package kernel. If so, that fix would be good to cherrypick. If not, some bisecting may find the cause. -- bluetooth network PAN fails to connect to mobile phone https://bugs.launchpad.net/bugs/336012 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 336012] Re: bluetooth network PAN fails to connect to mobile phone
As if to demonstrate, I'm writing these comments over the 3g bluetooth connection to a Sony-Ericsson K850i, made with the script attached to the previous comment :-) For anyone wanting to reproduce this, I'm running: - Ubuntu 9.04 + updates - That means kernel 2.6.28-13-generic (x86, 32-bit) right now. - Bluetooth packages updated to version 4.40-2 from Debian, as described in these comments: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502/comments/232 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502/comments/239 I think the Bluetooth package updates are not important. That info is just in case someone needs to reproduce what I've done. The only interesting difference between my script and Håkon's earlier script is mine adds a "hcitool auth $addr" line, because without it "hcitool enc $addr" just prints an error message. -- bluetooth network PAN fails to connect to mobile phone https://bugs.launchpad.net/bugs/336012 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 336012] Re: bluetooth network PAN fails to connect to mobile phone
Fwiw, I agree that the Bluez documentation is poor in this area. But Bluetooth is quite complicated; it would be difficult to write good documentation. The D-Bus documentation of Bluez is poor for controlling PAN connections, which you are supposed to do now that "pand" is in "bluez- compat", meaning deprecated. The documentation is minimal, and doesn't really explain that the D-Bus calls have changed between Bluez versions, without backward compatibility. When I last looked, the sample script calling D-Bus didn't work with the current Bluez version. And D-Bus is too difficult to use from a shell script, when compound values are involved. So hooray for still having "pand", which is simple and works :-) -- bluetooth network PAN fails to connect to mobile phone https://bugs.launchpad.net/bugs/336012 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 336012] Re: bluetooth network PAN fails to connect to mobile phone
Thanks Håkon! The script does not work for me, but adding one more command makes it work on my Sony-Ericsson K850i. "hcitool cc $addr; hcitool enc $addr" outputs this for me: HCI set encryption request failed: Input/output error The trick, at least with my phone, is to add "hcitool auth $addr" between them: hcitool cc $addr hcitool auth $addr hcitool enc $addr pand -c "$addr" I'm attaching the script which I use to connect to the internet over my phone now. To use the script, edit the phone_mac= line near the start, then run the script as 3g_connect or 3g_disconnect (I have one symlinked to the other). ** Attachment added: "Script used for connecting/disconnecting to the net via a 3g phone" http://launchpadlibrarian.net/28683684/3g_connect -- bluetooth network PAN fails to connect to mobile phone https://bugs.launchpad.net/bugs/336012 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 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Thanks Håkon! The script does not work, but adding one more command makes it work on my Sony-Ericsson K850i. I'll be adding details to bug #336012, which is the proper place for it. I had it confused with the "hci_cmd_task: hci0 command tx timeout" because I have seen that too, occasionally, when trying to make these connections. There's now good evidence that the difficulty connecting to Sony- Ericsson phones is a completely separate bug, although it's possible to have both if you're unlucky. Further comments from me, including a script which I now use to connect to the net over 3g on my Sony-Ericsson phone, on #336012. -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Unfortunately updating Bluez doesn't work for me. I've tried updating Bluez from 4.32 to 4.40 as per the suggestion. Specifically, these packages from Debian: bluetooth_4.40-2_all.deb bluez_4.40-2_i386.deb bluez-alsa_4.40-2_i386.deb bluez-compat_4.40-2_i386.deb bluez-cups_4.40-2_i386.deb bluez-gstreamer_4.40-2_i386.deb bluez-utils_4.40-2_all.deb libbluetooth3_4.40-2_i386.deb Using the above packages and Jaunty's latest kernel, 2.6.28-13-generic, I'm still not able to make connections to my Sony-Ericsson K850i phone. The symptoms are the same old: the phone seems an attempted connection, and asks for confirmation (if not already allowed), and then the phone sees a second attempted connection. With my ancient kernel patch (long ago now on this bug), there's only one connection and it works. -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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 249620] Re: dash does not support multi-digit file descriptors
Confirmed. This doesn't work either: exec 200>file Neither does the sample code given in the "flock" man page: ( flock -s 200 # ... commands executed under lock ... ) 200>/var/lock/mylockfile -- dash does not support multi-digit file descriptors https://bugs.launchpad.net/bugs/249620 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
Re: [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
Milan Bouchet-Valat wrote: > Providing a testing kernel package would really be great! Then it would > make sense to ask people to confirm the bug is still here. Though we > have learned that I/O and responsiveness are very difficult to measure - > not sure we'll be able to clearly confirm anything on a so large > thread... ;-) There are several reports that copying a large file always make the desktop very slow, so that should be simple to test - on those systems. -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
kylea wrote: > I then checked the output from sdptool browse and noticed that the > SyncMLClient channel had changed from 6 to 5 !!! That's fine. It's not much different to computers changing IP address. Apps should read the metadata (from sdptool!) and work out the right channel to use. > So I changed my settings to 5 in the Multisync tool, all good calender > transfer worked Sounds like the bug is Multisync requiring you to enter the channel number. It should work it out automatically. Maybe you could file a bug report for Multisync? -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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 341952] Re: ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
Since installing Jaunty, I'm getting lockups every few days on my laptop and I *don't* use ath5k. X freezes, no mouse movement, no keyboard, no Alt-F1 to switch to console. So the lockup might have nothing to do with ath5k. One time when it happened, the mouse kept moving though nothing happened under it and the keyboard didn't work, and I was able to login over the network. I looked at the last kernel messages with "dmesg" and saw something about DRI. So it may be DRI is to blame. I don't have Compiz turned on, though. I have an Intel 945GM graphics chipset here, and my wi-fi is iwl3945 (which works very well). I was using a Jaunty kernel before it was released, but with an Intrepid distribution otherwise (except for essential packages needing to match the kernel). With an Intrepid distribution running on top of a Jaunty kernel, I didn't experience any of these lockups. So it's quite likely that it's either not a kernel bug, or a kernel bug which depends on the newer userspace to trigger it. Due to the DRI message I saw once, I vaguely suspect the X server and/or DRI code. -- ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout" https://bugs.launchpad.net/bugs/341952 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Dominique Meeùs wrote: > Mine still does not work. This is a regression form 8.04 over two > releases 8.10 and 9.04. I wonder why the Bluez bug (filed more than six > month ago) is still considered New (through two releases), importance > undecided (decidedly important to me) and unassigned (I am not able to > fix it myself!) Ah well, mine doesn't work either - unless I apply my _kernel_ patch which reverts _net/bluetooth_ back to the 2.6.24 Hardy kernel's protocol stack. (Patch posted earlier to this long bug report). The latest kernel fixes to make the USB Bluetooth driver better don't make any difference on my system. Neither does running older Bluez code. I see a protocol bug in the kernel. Fortunately for me, I have a workaround, but unfortunately it's not suitable for general use as it reverts the entire kernel bluetooth stack quite a long way. -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
Hendrik van den Boogaard wrote: > @Jamie: > On my 7200.11 1 TB drives (also one of the first 1 TBs on the > market) I also disabled NCQ because I found some thread that it > might kill the contents of the file system. If you want I can lookup > where I found that. I'm guessing it's barriers not being implemented or enabled properly in the kernel? (See ext3 "barrier=1" off by default, controversial threads about it..) Even if the filesystem does barriers, Linux software RAID does not. If it's not that, I'm interested in why NCQ should be disabled. In principle, if used right, it should always be an improvement or about the same, and it would be quite bad firmware to fail at that. > This machine however has a SATA disk and I never experienced any > sluggishness on this machine, so far running Hardy and Intrepid. So the > sluggishness may even be drive specific? It might. There are tools, such as blktrace, which can help diagnose if it's the drive if you know how to read the output. It is quite outside what I have time for though :-) -- Jamie -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 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
Re: [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
Hendrik van den Boogaard wrote: > Copy the large files in one window (PATA -> SATA) and do a 'find /' > (SATA drive) in the other window. I found out that the 'find' command is > a *lot* more responsive pushing file names to the screen when I put the > NCQ buffer on 1 item (effectively disabling NCQ). The mouse and cursor > still lock up often for less than a second and performance is still > sluggish but the machine is not completely unusable. While I am typing > this I put the NCQ setting back to 31 as it was on before but now I > cannot even type this complete sentence without seeing it appear on the > screen. That's quite surprising: NCQ should in theory always make it faster, unless you have a terrible drive implementation. > As far as I can remember somewhere in the 2.6.1x kernels NCQ was > added together with all the new libata stuff (that's for me when a lot > of trouble started; a bad sector on a disk created kernel-oopses on > another NVidia based computer with a 4TB software Raid5 Array). This > might also explain why I have not seen this problem before as my old > 160G drive is PATA and has no NCQ. Both of these things (the oopses and the NCQ reduction in performance) ought to be reported to Linux's libata maintainer... -- Jamie -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 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
Re: [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
Milan wrote: > Thanks for these detailed informations. So you suggest that the IO > scheduler is not giving enough priority to tasks other than the file > copy; that's an interesting way of finding the cause of the problem, > indeed! I suggest you try the new kernel, and if it's not fixed, go to > the upstream report and explain them your case. You can find many > different scripts to test the system's responsiveness there, and you'll > notice that's really tricky (long thread...). I suggest it's not just about giving I/O priority to tasks other than the copy, but also giving them enough "anticipatory" time so there isn't a pair of head seeks for every I/O operation by the non-copying tasks. It has to look like this to be efficient: I/O for copy I/O for copy I/O for copy I/O for copy I/O for copy I/O for other thing I/O for other thing I/O for other thing I/O for other thing I/O for other thing I/O for copy I/O for copy I/O for copy I/O for copy I/O for copy I/O for other thing I/O for other thing I/O for other thing etc. And not I/O for copy I/O for other thing I/O for copy I/O for other thing I/O for copy I/O for other thing etc. -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 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
Re: [Bug 326609] Re: [MASTER] No flash in firefox after upgrade from intrepid to jaunty
Tareeq Ali wrote: > Ok I have had this issue, I tried both sudo apt-get remove --purge > flashplugin-nonfree and without the --purge option, and then re- > installed didn't work, tried purging again deleted the .deb file from > /var/cache/apt/archive folder, and then tried sudo apt-get install > flashplugin-nonfree. That did not work at all. > > I was finally able to solve the problem by downloading the adobe flash > plugin (tar.gz) and copying the (.so) plugin to the > /usr/lib/firefox-3.0.8/plugin folder. > > the flashplugin-nonfree deb installer does not give any errors, apt does > not give any errors. You might have needed to "apt-get remove --purge flashplugin-installer" as well, before trying to install flashplugin-nonfree. That worked for me, and it's flashplugin-installer which shows the "cannot connect to network error" during upgrade. -- Jamie -- [MASTER] No flash in firefox after upgrade from intrepid to jaunty https://bugs.launchpad.net/bugs/326609 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 326609] Re: [MASTER] No flash in firefox after upgrade from intrepid to jaunty
I just did an upgrade from Intrepid to Jaunty and have the same problem. I spotted this in the output from update-manager: Setting up flashplugin-installer (10.0.22.87ubuntu2) ... Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Downloading... --2009-04-18 21:05:57-- http://archive.canonical.com/pool/partner/a/adobe-flash plugin/adobe-flashplugin_10.0.22.87.orig.tar.gz Resolving archive.canonical.com... failed: Name or service not known. wget: unable to resolve host address `archive.canonical.com' download failed The Flash plugin is NOT installed. As others have reported, NetworkManager stopped working for a large part of the install and dropped my _wired_ ethernet connection. NM started working again towards the end, after "Setting up flashplugin-installer". The NetworkManager problem isn't a flashplugin bug. But flashplugin not being able to fix itself when the network comes back would be best fixed in flashplugin. After all, there might be other reasons why the network is down at that exact moment. Some ideas: - Can it tell dpkg that setup failed and needs to be run again after everything else? - Can it use a trigger on the upgrade of NM, or a generic trigger on network change? - If fetching fails during upgrade, can it attempt to fetch the file the next time Firefox is started? This would be quite robust. Also, earlier comments say that uninstalling without --purge then reinstallng does not fix it. --purge shouldn't be necessary, just to trigger fetching the file it needs which it hasn't installed yet. -- [MASTER] No flash in firefox after upgrade from intrepid to jaunty https://bugs.launchpad.net/bugs/326609 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Richard Hamnett wrote: > I am not having the success you had with bluetooth, because I am using > some more advanced featuresbut this should not really be happening > if the only problem was the kernel bluetooth upgrade. I'm pretty sure there's at least 3 different bugs affecting you: 1. One which is fixed by changing kernel USB bluetooth driver only. 2. One which is fixed by changing kernel bluetooth network protocols only. 3. One to do with OBEX and Gnome for file transfers. -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Richard Hamnett wrote: > Can you confirm that you can / cannot send a file from your mobile > device to the laptop? I never send files over Bluetooth between phone and laptop, and don't know how to it. I just tried it now, with the patched kernel, and these things happened: - When I asked the phone to "send by bluetooth" a picture file, it searched for devices and couldn't see my laptop, even though I set the laptop to be visible in the GNOME Bluetooth Preferences. - When in GNOME Bluetooth Preferences I told it to search for a new device to connect to, it couldn't see the phone even though I set the phone to be visible. - The laptop does have the phone in its list of known devices, so when I clicked button in GNOME Bluetooth Preferences to connect explicitly, the button grayed out, but the status icon still didn't show it connected after several seconds. - Despite the above "not connecting properly as shown by GNOME", when I ran pand on the laptop, it *was* able to make a 3G data connection to the internet through the phone! - Even though the phone was connected and had 3G networking going on, and the phone's screen showed a connected icon, the phone _still_ didn't show the laptop in the list of devices to send files to. I'm guessing the laptop isn't advertising its ability to receive files. Since I never use this part of Bluetooth, and there's no option for it in GNOME Bluetooth Preferences (they removed it!), I don't know if this has anything to do with the kernel changes. All I know which works is 3g data networking - running "pand" on the laptop, that pairing with the phone, and the resulting BNEP network able to be used as an internet connection. (Btw, it's annoying that "pand" isn't in the new bluez packages at all... and the scripts on bluez.org using D-BUS to connect don't work with the new version of bluez... a different bug). It's possible that sending and receiving files is not connected with the kernel change at all, since I noticed some people are reporting bugs with that and responses say it's something to do with the OBEX server, not pairing. As I don't use this part of Bluetooth at all, I'm not interested in fiddling about with OBEX except just trying it for you now :-) -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Here's an alternative patch which might be easier for some people to try. Just apply this one to a linux-source-2.6.28-7 tree. It's exactly the same as the previous small patch, but you don't have fetch a 2.6.24 tree yourself and copy bits over. There's no point trying both patches, they're the same code. ** Attachment added: "Apply this to linux-source-2.6.28-7, see if it fixes Bluetooth for you..." http://launchpadlibrarian.net/23019382/put_old_working_bluetooth_into_2.6.28_7.diff -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Thanks for trying, NagPer. Yes, there's a small hunk missing from my "diff" - in include/net/bluetooth/rfcomm.h. Here's a new one, called make_2.6.24_bluetooth_work_in_2.6.28.diff. You still apply it after copying over the bluetooth tree from 2.6.24 over 2.6.28, as per the instructions. ** Attachment added: "Apply this after copying 2.6.24 net/bluetooth and include/net/bluetooth into a 2.6.28 tree." http://launchpadlibrarian.net/23019106/make_2.6.24_bluetooth_work_in_2.6.28.diff -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
isecore wrote: > For whatever it's worth, when I bought a new BT 2.0 dongle it > immediately worked flawlessly. It's the same generic chinese/taiwan > brand (Billionton)as my first (which does not work) but it identifies > completely different: > > [code]Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd > Bluetooth Dongle (HCI mode)[/code] > > In the forums, it seems people have had success with 2.0-compliant > devices, while 1.1 and older suffer from whatever this is. Mine has the same id as your new one and doesn't work: Bus 004 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) But then I've said my bug may be a different one. -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
I wrote: > Brian Rogers wrote: > > Switching to the older driver is more of a workaround than a solution. > > But anyone who wants working Bluetooth today can build a custom > > kernel with hci_usb instead of btusb. > > Thanks for finding that, but it didn't help. > I've tried hci_usb with Jaunty's 2.6.28-7, and it didn't solve my > problem. > > My next attempt will be to try and build the entire Bluetooth stack > from 2.6.24 grafted into the newer kernel, and see if that works... Ok, success for me! I forward-ported the Bluetooth protocol stack from 2.6.24 to 2.6.28, and now I'm able to connect to my Sony-Ericsson phone over Bluetooth, and using the BNEP protocol connect to the internet over 3G. I'm using the connection to post this command, and have used it to fetch about 50 web pages. Note I did *not* have to change the drivers, only the network protocol stack... I'm using the "btusb" driver module, which is the one Ubuntu enables. It's hard to be sure, but for anyone wanting to reproduce this and see if it fixes their problem, I think the steps for the forward port are as follows: 1. Fetch a linux-2.6.24 source tree from kernel.org, and unpack it. (http://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.tar.bz2). 2. Install package kernel-source-2.6.28 (from Jaunty's repo). (Start from https://launchpad.net/ubuntu/+source/linux, I think you can download a package file and install it with dpkg). 3. Unpack /usr/src/linux-source-2.6.28.tar.bz2 to somewhere handy. 4. Enter the unpacked linux-source-2.6.28 directory. 5. cp /boot/config-$(uname -r) .config 6. mv net/bluetooth net/bluetooth.orig 7. mv include/net/bluetooth include/net/bluetooth.orig 8. Copy files from 2.6.24: cp -r ../linux-2.6.24/net/bluetooth net/ cp -r ../linux-2.6.24/include/net/bluetooth include/net/ 9. Apply a tiny patch to make it compile (attached to this comment). 10. make bzImage 11. make modules 12. make install modules_install 13. update-initramfs -a 14. grub-update 15. Reboot with the new kernel... It's a fairly trivial forward port. ** Attachment added: "diff" http://launchpadlibrarian.net/22814665/diff -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Brian Rogers wrote: > The configuration menu only lets you select one of the two drivers, but > I don't see a reason the two should conflict as long as you only allow > one of them to load. > > Switching to the older driver is more of a workaround than a solution. > The new driver needs to be fixed one way or another, and once we have > the fix, we can backport it. > > But anyone who wants working Bluetooth today can build a custom kernel > with hci_usb instead of btusb. Thanks for finding that, but it didn't help. I've tried hci_usb with Jaunty's 2.6.28-7, and it didn't solve my problem. My next attempt will be to try and build the entire Bluetooth stack from 2.6.24 grafted into the newer kernel, and see if that works... (I suspect my problem is a different bug.) -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
Brian Rogers wrote: > The problem still exists on the very latest upstream kernel. I'm going > to bisect between 2.6.26 and 2.6.27, and report the bad commit to the > Bluetooth guys. Then it shouldn't be too long before we have a fix. If you narrow it down to the bad commit, I'll be happy to test it with my S-E phone, which has similar but not quite the same problems. (Btw, is it even possible to bisect Ubuntu kernels? A recent article from lwn.net notes that distro kernels have distro-specific initramfs setups making it impossible to use vanilla kernels on some laptop configurations now...) -- Jamie -- Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth association no longer works
hyperair wrote: > You kidding? Bluetooth works perfectly for me on Intrepid, so please > don't talk as though the entire Ubuntu community is affected. Either > way, can someone who is affected open up a Jaunty installation (or > LiveCD) and see if the issue is fixed over there? It does not work for me with Jaunty kernels and Jaunty bluez on an otherwise Intrepid system. I boot a Hardy kernel when I want to use Bluetooth, then it works fine. The bluez version doesn't seem to make any difference, only the kernel version. -- Bluetooth association no longer works https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 268502] Re: Bluetooth association no longer works
yngd wrote: > New kernel @ Jaunty, 2.6.28 series fixes my problem. > Now I got my bluetooth headset working on Skypefinally. > > Intrepid remains "unpreant" release for me, it was still fine with > Hardy. Jaunty's 2.6.28-4 doesn't do it for me. Still can't connect to PAN on my Sony-Ericsson K850i phone. Intrepid's 2.6.27 kernels can't connect, but Hardy's 2.6.24 kernels can. (So I have to reboot to a 2.6.24 kernel to use bluetooth 3g broadband through my phone, but it that kernel breaks a bunch of other things). Someone else reports similar, they can't connect to ther S-E phone starting from Interpid. -- Jamie -- Bluetooth association no longer works https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 269329] Re: [MASTER] NM 0.7 lacks bluetooth 3g support
Valmantas Palikša wrote: > Blueman 1.0svn handles bluetooth dialup connections very nicely. It > exposes rfcomm interfaces to hal and network manager grabs them > automatically. > > Here's a demonstration video: > http://walmis.balticum.lt/blueman1.0_networking.ogv.tar Valmantas, does it work with bluetooth PANU way of connecting to the internet too? Thanks, -- Jamie -- [MASTER] NM 0.7 lacks bluetooth 3g support https://bugs.launchpad.net/bugs/269329 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 288613] Re: Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta
I've used all combinations of Hardy/Intrepid kernels, and Hardy/Intrepid bluez packages. The probles I've had are entirely dependent on kernel version, and the bluez version makes no difference at all (that I've found). Therefore I think this bug should be marked as a duplicate of #268502, which is the same bug but assigned to the kernel and Ubuntu Kernel Team. The kernel is the place to look for this one. The problems I've observed are dependent on kernel version, and not dependent at all on bluez version (I've used all combinations.Because the problem is highly dependent on kernel ver -- Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta https://bugs.launchpad.net/bugs/288613 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 268502] Re: Bluetooth association no longer works
kylea, I usually boot with the Bluetooth radio off. It's USB internally and disconnected when I boot, then I switch it on after logging in. I still have this pairing problem every time with 2.6.27 kernels. So changing the load sequence wouldn't fix it. The information we need may be to bisect between the last kernel which works reliably and the one after, trying it on someone's machine until the change which breaks it is identified. Alas I don't have the time for it, so I just run old kernels with Intrepid. -- Bluetooth association no longer works https://bugs.launchpad.net/bugs/268502 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
Re: [Bug 288613] Re: Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta
okkie wrote: > >From what I've read till now I think the whole Intrepid bluetooth problem > >has been reported in full as it appears that pairing the devices is the > >main issue. > What is of major importance to me and many others i'm sure, is the time it > will take to fix the problem as my income depend on transferring files to and > from my phone.I lack the knowledge to offer any personal help and would like > to thank the programmers in advance for their efforts to rectify the problem > as soon as possible. I boot a 2.6.24 kernel from Hardy, and then Bluetooth works fine for me. I have these packages from Ubuntu Hardy (8.04) installed on my Intrepid system: linux-image-2.6.24-21-generic (version 2.6.24-21.43) linux-restricted-modules-2.6.24-21-generic (version 2.6.24.14-21.51) linux-ubuntu-modules-2.6.24-21-generic (version 2.6.24-21.33) linux-backports-modules-2.6.24-21-generic (version 2.6.24-21.27) With those packages, Linux 2.6.24-21 is available in the boot menu. To be able to install those packages, I have these two lines added to the end of /etc/apt/sources.list: deb http://archive.ubuntu.com/ubuntu/ hardy main restricted deb http://archive.ubuntu.com/ubuntu/ hardy-updates main restricted Then those packages can be selected for install in Synaptic. Note that they won't upgrade to newer Hardy kernel packages automatically. Indeed, while writing this I just noticed there are 2.6.24-22 versions out, which I'm about to select and install. :-) -- Jamie -- Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta https://bugs.launchpad.net/bugs/288613 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 256267] Re: please update to 0.9.1
Nick Ellory wrote: "there only appears to be more minor bug fixes". I think supporting KVM is a pretty major new feature. Especially as KVM is Ubuntu's official VM solution, and virt-manager (the other GUI which manages KVM) is not always the best tool, depending on what you do with your VMs. -- please update to 0.9.1 https://bugs.launchpad.net/bugs/256267 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 288613] Re: Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta
I'm unable to connect to PAN on my mobile phone (Sony-Ericsson K850i) with the 2.6.27 kernels, but I was able to do so with Hardy's 2.6.24 kernel. I don't do file transfers, only PAN. To be precise about the kernels: I ran Hardy the distro for a while with Intrepid beta kernels (to test the kernels), and connections made with "pand" were ultimately rejected with "Connection Refused" when running those Intrepid kernels (on a Hardy distro), but when booting a Hardy kernel "pand" worked fine. It's a bit odd, in that the connection seems to work at first, with the phone's screen asking if it's ok to accept this connection. But on saying ok, then the phone asks a _second_ time the same question, and when it _asks_ the second time, "pand" reports "Connection Refused" immediately. Note that the laptop and phone are already known to each other, this is just the phone asking "Laptop wants to use the phone as a modem? yes or no". If I tell the phone to allow it without asking, there are no dialogs or delays, "pand" just gets to "Connection Refused" very quickly.) Whereas with Hardy's own kernel, the phone asks just once, and the connection always succeeds in "pand"'s log. Note the bluetooth userspace utilities were _exactly_ the same in these tests. So in my case, the ability to pair with the phone was affected by booting a different kernel *alone*, with 2.6.27 kernels failing and 2.6.24 kernels succeeding. I'm now running Intrepid the whole distro (upgraded from Hardy), and generally up to date. The ability to pair (with "pand") is still broken, same as running Hardy with Intrepid's kernel. I haven't yet had a chance to try the other way around and boot the Hardy kernel on my Intrepid distro, to see if that fixes "pand". So for people with pairing problems, it might be worth booting Hardy's latest kernel, to see if that fixes the problem. If it does, that will at least narrow it down to the kernel bluetooth stack. I suspect there's more than one different pairing problem, but this is one of them. -- Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta https://bugs.launchpad.net/bugs/288613 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 291902] Re: Previously working DHCP on wired ethernet is assigned static IP from unrelated interface after upgrade to Intrepid
"putting eth0 in NM" should read "putting eth0 in /etc/network/interfaces" -- Previously working DHCP on wired ethernet is assigned static IP from unrelated interface after upgrade to Intrepid https://bugs.launchpad.net/bugs/291902 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 291902] Re: Previously working DHCP on wired ethernet is assigned static IP from unrelated interface after upgrade to Intrepid
For NM everything in /etc/network/interfaces are just connection configuration - which are not bound to a particular device ... unless the names match devices NMis supposed to manage. So NM will consider them for devices that don't have any other explicit configuration. This seems a very odd behaviour, as it's contrary to what /etc/network/interfaces means. Does NM do anything else surprising with /etc/network/interfaces, like parse the comments, look for special keywords, or invent random numbers? I'm just wondering, because taking a static IP configuration for one interface and automatically applying it to a different interface seems like would never be the right thing to do. Is there a rationale for this behaviour - i.e. a situation where it makes sense? (By the way, why does it use the unrelated interface configurations as possible configs for eth0, but not for wlan0?) If it makes no sense, I suggest removing it! But if there are scenarios where it makes sense - it really could do with being a controllable option. I do still want to use NM, as it works quite well for wireless interfaces when roaming. (When it handles Bluetooth 3g broadband, that will be really nice.) In Hardy it worked for wired ethernet too - if that was plugged in, it used it, and if not, it looked for a wireless signal. (On Hardy, I still had to kill and restart NM whenever I used 3g broadband or PPP, but NM's wired/wireless behaviour is very useful). If I follow your suggestion of putting eth0 in NM, that would prevent NM from managing eth0 wouldn't it? But managing eth0 - like wireless - is useful behaviour that worked in Hardy. The useful behaviour was detecting when a cable is plugged in, and running DHCP. In my situation, does NM also touch the tap0 / tap1 / tap2 / tun0 / bnep0 / pan0 interfaces which are found on my laptop, or does it just manage eth0 and wlan0? >From reading /usr/share/doc/network-manager/README.Debian, I guess it won't manage tap0 / tap1 / tap2 because those are mentioned in /etc/network/interfaces - but it _will_ try to manage tun0 (which is created by OpenVPN) and bnep0 (which is created by Bluez pand), and pan0 (which is created by something I don't know about, but connected with Bluetooth somehow). Is that correct? Your suggestion to try managed=true is... puzzling. README.Debian explains that this causes NM to manage all the interfaces - but what I (think I) need is for NM to manage eth0 and wlan0, but not any other interfaces (whether mentioned in /etc/network/interfaces or not), and not to read the configurations of unrelated interfaces from /etc/network/interfaces as potential eth0 configurations. Neither managed=false nor managed=true will achieve that according to my reading of the docs. But I'll try managed=true, since I'm curious what "managed all the interfaces in /etc/network/interfaces and honours all the DHCP / static settings" really means :-) Ok, tried it. Restarted /etc/init.d/NetworkManager restart. The GUI shows exactly the same as before: "ifupdown (tap0)" (+ tap1 and tap2) under Wired Networks, and when a wire is plugged in I expect it to use a faulty static config from tap1 as before. There is no visible change. What is managed=true supposed to change? Broadening this to a couple of constructive suggestions for the future: 1. What would be useful, I think, are options like: manage_interfaces_wired=eth0 manage_interfaces_wireless=wlan0 2. Many of us with multiple interfaces would basically like NM to manage the usual ones, and to not do anything with the rest - except detecting they exist and are up for the ONLINE/OFFLINE purposes. But not all up interfaces mean ONLINE - for example tun0 for VPN and tap0 for local VMs may not, depending on user's preferences (e.g. whether Firefox should say it's offline, or should attempt to visit a VM's server). So in addition to the above: report_online_if_up=eth0,wlan0 3. The above options should be entries in /etc/network/interfaces for those interfaces listed in that file: the presence of keywords "network_manager yes (no)" in each interface section, and "report_online_if_up yes (no)". 4. Right now, NM will let you select a wireless AP on wlan0 to connect to, or the wired interface on eth0 if there's a signal. When Bluetooth 3g is added, that's like more wireless APs to choose from, but on another interface. In general, exclusively selecting just one interface according to an available connection, and disabling the others (except for scanning on wireless and cable detection on wired) is a really nice policy for roaming machines. But alongside that, it would be a nice feature if the GUI were able to manage _other_ interfaces in the sense of bringing them up and down _independently_. For interfaces with just one configuration, these would be tickboxes rather than radio buttons, when user-controllable, and greyed out tickboxes for non-user-controllable interfaces (if you wan
[Bug 289796] Re: NetworkManager should forget list of currently cached APs after resume (WAS: wlan roaming problems after wakeup from hibernate)
Alexander, my bug is now reported as bug #292890, with the title you suggested. -- NetworkManager should forget list of currently cached APs after resume (WAS: wlan roaming problems after wakeup from hibernate) https://bugs.launchpad.net/bugs/289796 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 292890] [NEW] NM doesnt forget currently cached APs when there are zero APs in proximity
Public bug reported: Binary package hint: network-manager This was originally a comment in bug #289796, but it is a different bug. The following issue did not occur on Hardy. My system is now upgraded to Intrepid. After resuming from suspend, the list of APs was not cleared for a long time (at least 50 minutes), when the laptop had no APs in range. Explicit scans from the command line did not result in NM's list refreshing. Details: I have just suspended the laptop at home, where there's an AP called "christopher" which I use, and another one in range. I resumed about 50 minutes ago, in another place with no APs in range. nm-applet is still showing the two APs which were in range when I suspended - after 50 minutes! It should have had plenty of time to do another scan. I've just forced a scan using "sudo iwlist wlan0 scanning", and it says "wlan0 No scan results". 5 minutes after doing that (then doing it again), nm-applet is _still_ showing those 2 APs from before the laptop was suspended. I can even select "christopher", the AP I used when suspended, and it will try to connect to it. After the attempt fails, it pops up the dialog asking for the AP key. It appears NetworkManager is simply not refreshing its list, even though the Wi-Fi driver has done multiple scans itself in this time. I did see this behaviour in Hardy occasionally, where nm-applet took annoyingly long to notice changes despite explicit manual scans with iwlist, but nm-applet would always catch up after a couple of minutes. Arguably, a second bug is: Popping up a dialog asking for the AP key for an AP which is not in range (does not show up in a scan) _and_ is not / has never been in the list managed by "Connect to Hidden Wireless Network". If an AP was in range when it was selected in the UI, but is no longer showing in scans by the time NM tries to connect, and the AP is not believed to be hidden, then asking for the AP key seems like the wrong thing to do, and instead it could alert that it has gone out of range (if requested explicitly from the UI) or simply try another AP (if the one out of range was chosen automatically). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NM doesnt forget currently cached APs when there are zero APs in proximity https://bugs.launchpad.net/bugs/292890 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
