[Bug 1243806] Re: The names column has its width dictated by other columns
Oof. Well, glad someone may be addressing it - kudos and all love to Carlos Soriano, it appears? https://bugzilla.gnome.org/show_bug.cgi?id=732004#c3 Apparently it's a simple one-liner: https://bug732004.bugzilla- attachments.gnome.org/attachment.cgi?id=284244 ...that won't be in upstream until GNOME 3.16, and Ubuntu is sticking with GNOME 3.12 stuff for Ubuntu 14.10. Any chance that is cherry-pick- able? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: The names column has its width dictated by other columns To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1243806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243806] Re: The names column has its width dictated by other columns
@Sebastien Bacher: Awesome, thanks! From the timing I guess that landed between visiting Launchpad and finishing typing. (Obviously got all that from your link to the GNOME bug just prior but I wasn't sure how much activity that indicated.) Now to actually try it out after work... :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: The names column has its width dictated by other columns To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1243806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243806] Re: The names column has its width dictated by other columns
re: my #38 above: Those screenshots accidentally expose another funny behavior - yes, when the yellow 'tip' appears at the bottom of the window it does at least tell you about the individual file that's been highlighted. Apparently in the contrived case of a window that small (felt like fitting both in one png and not sharing the labels of my external drives) it doesn't fully appear, different bug. But at normal window heights that part does work if you feel like individually examining each one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: The names column has its width dictated by other columns To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1243806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243806] Re: The names column has its width dictated by other columns
Does this mean it's fixed or someone just pushed the ignore pesky users button again? I see no new Nautilus updates since last week. Does this mean 14.10's version will be improved? The 14.04 examples in the attachment are a bit forced with non-sensitive data from my home machine, but when you're at work dealing with files and paths like /Clients/Lastname, Firstname/adv. Plaintiff/for filing/Motion (Second) for Extension of Time to File Opposition.pdf and any column gets truncated, you're in for a bad time when all search results return as e.g. Mot The Dash search also seems to have issues being useful with these common cases of 'important metadata is in the path as well as the filename' if you're trying to find Bob's motion and not Alice's. I know I'm without gruntle, but I'm told all of these features break equally when working with multiple git repos, so what audience is being adequately served by any of this again? ** Attachment added: Nautilus maximum column width still suboptimal - bring back horizontal scrollbar.png https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+attachment/4239812/+files/Nautilus%20maximum%20column%20width%20still%20suboptimal%20-%20bring%20back%20horizontal%20scrollbar.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: The names column has its width dictated by other columns To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1243806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932834] Re: Enable equalizer
It's not clear what themuso was referring to back in 2012, but as nevion alluded to above, qpaeq is 'just' a Python program. It's the GUI required (absent equivalent software) for the end-user to do something useful with the capability exposed by the modules (which do come stock, but aren't loaded by default). See: http://cgit.freedesktop.org/pulseaudio/pulseaudio/plain/src/utils/qpaeq Perhaps the problematic dependency back then was PyQt4 or sip? Or not, this is what's known as unfounded speculation on my part. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932834 Title: Enable equalizer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/932834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205055] Re: Impossible to change column width of Nautilus in list view
Trash issue in #11 and #12 reproduces with 13.10 (64-bit also) here as well. [Anybody else have my 'Modified' column header doesn't always accept mouseclicks to sort issue? Starting from Trash, which activates the Location column in new tabs within that window is actually a pretty good workaround...] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205055 Title: Impossible to change column width of Nautilus in list view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
As a parting comment, this was awful enough and lasted long enough that I was forced to drop 6450s in the affected hardware, so I don't know if any of that was resolved. I will note the following for those in the same boat: a) Dropping in Radeon 6450s did solve it and they were only $30 or so with careful shopping at that time, probably less now that they only have half the performance of an A8's integrated GPU. b) Dropping in 6450s did generate enough heat and power stress in combination to take out the aged capacitors in one of the two machines, forcing an upgrade, which forced the issue of upgrading the other machine to match. If you're upgrading an old machine with a fanless card and there's no case fan in the usual near the card cage position, I would suggest adding one for the extra $4 or so for insurance or rubber-chicken facto. At least, in my minimal sample of these 2 machines and 2 similar Socket AM2 boxes with case fans (~80-90mm low-RPM 'silent' types) it was only one of the fanless boxes that hit death. (I will also note that the dead box had a standard 'old fashioned' power supply with a small exhaust fan and mostly slots on the back, while the boxes with no trouble have all had the 'modern' style with a large 120mm fan pulling air up across the board from the bottom. In a marginal situation this might be enough to keep things alive until the hardware is obsolete for other reasons.) c) Fingers crossed, thus far I have not been bitten with too much bitrot in the 6450 support and I believe they are recent enough to still be a target for the ongoing improvements in the open-source driver.. this year, at least. fglrx still supports them right now. d) If I had realized Socket FM2 was a dead-end at the time I ended up having to buy new machines as a result of this saga, I would've been even more annoyed. If something's gone wrong now and you're still standing by AMD, do make sure you end up with something FM2+ (not plain FM2) so upgrades to anything interesting will be possible. The Unity/Libre/Firefox stack has been gradually bloating such that the maximum 2GB in the old machines was not going to support standard browsing/multiple-documents-and-reference-PDFs-open-at-once office tasks for much longer anyway. It is never fun to be forced to upgrade hardware solely for reasons of bitrot. While I think AMD ex-ATI has better intentions of providing good and stable FOSS/*NIX support for chips of roughly the vintage of the 6450 and later, and I sure appreciate what a nightmare maintaining X.org support must be (I was also 'bitten' by the rot of support for the 'well-supported' Matrox G200 at the end of the AGP era)... I will post grumpily grumpy about this to the extent that it might shame anyone into not letting the decay repeat quite so badly in the future. (There seemed to be initial good intentions with the RS480 and 780G, but breakage in support for both forced me to invest in a lot of 6450s... even when they had previously been quite adequate and the only 3D app in use was Unity itself. It does leave the customer feeling like a sucker and I can no longer say I've had no problems maintaining a business on AMD... even if I did get to sit out a dozen different incompatible Intel CPU socket 'generations' in the time this hardware lasted, and enjoy switching from the original Semprons to some of the last Athlon 64x2 parts when the former could no longer cut it.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205055] Re: Impossible to change column width of Nautilus in list view
Hmm. I just experimented with your problem here and notice that if the window is not wide enough in list view, you cannot stretch the contents of the Name field past the Questions: Do you get the double arrow - cursor when you hover over the | divider between the Name and Size fields? If you get the double arrow, Can you then hold the left button and drag to the left to make the Name field *smaller*? ...and then does dragging it back to the right work until the contents of the Modified column hits the right side of the window? I just checked and see that e.g. Nautilus 2.32 from GNOME 2.x would allow stretching the Name column to the right and beyond, creating a horizontal scrollbar. It appears that horizontal scrollbars are gone from Nautilus/Files 3.8.2. Maybe that is what you're missing? If so that appears to have been another GNOME simplification (see also the enforced spatial Nautilus controversy of a decade ago or the We've Decided You Must Have a Clock And It Must Be Centered In Your Top Panel of GNOME 3). Possible workarounds: * You can 'emulate' the horizontal scrollbar behavior clumsily by dragging the window around and stretching it wider than the screen (drag it so left edge hangs off left edge of screen, then widen to right, then drag the whole window back and forth. * For long paths, you can turn off the Location column under Visible Columns in the v dropdown menu, and have something close to every other operating system's behavior where the current path is just shown in the navigation bar for the window. I agree that more of a 'split line' view for search results would be great, so the full path could show below the items returned, or developers could bring back the 'caret'/'indented' sort of expanding tree view naturally indicating the parent directories - which I miss greatly when not searching, too. (I'm guessing the old code for that 'broke' at some point during the Nautilus rewrite or it would not have gone away.) And I agree that it was kind of ridiculous to get rid of horizontal scrolling entirely, especially now that mouse wheels with left/right tilt are common, but I'm guessing they conflicted visually with the sticky note that has replaced the status bar to see the size and item count for the selected item. Which is sort of redundant in list view where Size is a column by default. [Sadly my report of the Modified column still regularly becoming dead to clicks is still a problem for me.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205055 Title: Impossible to change column width of Nautilus in list view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205055] Re: Impossible to change column width of Nautilus in list view
You may also want to try installing XFCE's Thunar which appears to have similar scrollbar behavior to old Nautilus. This will probably pull in a large bunch of XFCE dependencies but if you have the disk space that should be okay; then just add it to your dock as an alternative file browser. (If there's a legacy Nautilus package that can co-exist with 3.x, I wouldn't mind one myself - sometimes I want the instant search, other times I miss that tree-browsing approach in list view.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205055 Title: Impossible to change column width of Nautilus in list view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174611] Re: tessaract ocr no longer available in gscan2pdf
Sorry I missed responding to the request for more info. The aside about page definitions seems to have been long-since cured in the 1.1.3 in the Ubuntu 13.10 repos at least. Using libsane-perl, no less. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174611 Title: tessaract ocr no longer available in gscan2pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1174611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205055] Re: Impossible to change column width of Nautilus in list view
At risk of making this another miscellaneous complaints bug, but it appears there is yet another intermittent issue where cut and paste moving of files ceases to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205055 Title: Impossible to change column width of Nautilus in list view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244806] Re: Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10
apport information ** Tags added: apport-collected saucy ** Description changed: Upgrading from Ubuntu 64-bit 13.04 to 13.10 resulted in the attached mess for the Outline presets for Bullets and Numbering in LibreOffice (Version: 4.1.2.3 Build ID: 410m0(Build:3)). - Noticed when forced to hand-renumber an imported .DOCX (saved to .ODT) - because the font for the numbering in an imported numbered list remained - stubbornly immutable, but that will be a different bug. + Noticed when forced to hand-renumber an imported .DOCX (saved to .ODT) because the font for the numbering in an imported numbered list remained stubbornly immutable, but that will be a different bug. + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + MarkForUpload: True + NonfreeKernelModules: fglrx + Package: libreoffice 1:4.1.2~rc3-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 + Tags: saucy + Uname: Linux 3.11.0-13-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-24 (33 days ago) + UserGroups: lp lpadmin nopasswdlogin scanner ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1244806/+attachment/3917742/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244806 Title: Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1244806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244806] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1244806/+attachment/3917743/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244806 Title: Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1244806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244806] Re: Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10
Extensions: Only the Presentation Minimizer that seems to have been included by default. I'm a little loathe to do a full deinstall/reinstall of the packages just yet (employer would prefer I get some writing done in between filing bugs) but while the homedirs and their cruft have been copied since 8.04, the current system began with a fresh install of Ubuntu 13.04 (which didn't show up this bug) and was then upgraded to 13.10. It'd be nice to hop over to the guest account and see what a clean ~ results in, but fglrx apparently doesn't want to let me do that right now - will report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244806 Title: Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1244806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253448] [NEW] Papercut: Visual diff - Replace your changes shows someone else's Changes
Public bug reported: The brittleness of /etc/gnome/defaults.list should be another bug*, but happens to show up a more basic problem with ambiguity in the helpful visual diff dialog. The software asks the user whether it should be allowed to: Replace your changes in '[file]' with a later version of the configuration file? If you don't know why the file is there already, it is usually safe to replace it. Changes: Options: [Keep], [Replace] The ambiguity is that the text refers to your changes, but the Changes shown are what would be wrought if one chooses to Replace their own changes. So instead of showing you something you can Keep or Replace, the diff is really showing changes to Refuse or Accept. There are a dozen ways to fix this. At minimum, the text strings could be disambiguated: Changes proposed: (or Proposed changes:; or Changes in new version:) [Diff] These changes will be applied if you choose Replace. ... * Does someone have a patent on the BSD-style approach of tossing untouched distribution defaults in /etc/defaults/ with local overrides a level above? Having an /etc/gnome/defaults/defaults.list with local changes in /etc/gnome/defaults.list would solve the underlying bug of signing up to be nagged forever once you've installed acroread or another global application that should be recognized by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: debconf 1.5.50ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 20 17:08:34 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: debconf UpgradeStatus: Upgraded to saucy on 2013-10-24 (27 days ago) ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: Top of diff: No hint re: origin of files for users with a clue https://bugs.launchpad.net/bugs/1253448/+attachment/3913588/+files/Screenshot%20from%202013-11-20%2015%3A34%3A32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253448 Title: Papercut: Visual diff - Replace your changes shows someone else's Changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1253448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253448] Re: Papercut: Visual diff - Replace your changes shows someone else's Changes
[Attachment: In this case, the changes necessary to make acroread work by default cause the system to forever more ask the user which foot they'd like to be shot in.] ** Attachment added: Would you like a system that recognizes PDFs or not? https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1253448/+attachment/3913591/+files/Screenshot%20from%202013-11-20%2015%3A36%3A09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253448 Title: Papercut: Visual diff - Replace your changes shows someone else's Changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1253448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205055] Re: Impossible to change column width of Nautilus in list view
Resizing columns doesn't seem to be a problem for me with Nautilus 3.8.2 on 13.10 x86-64 as just released (for the Name and Size fields - Type and Modified are apparently 'wide enough' and not adjustable), but I'm experiencing something potentially related: Intermittently, the Type and Modified columns do not respond to a click to sort by that column. Resizing the width of the window seems to be the most reliable workaround to get them responsive. When the columns can't be resized, do the fields still respond to 'sort- by' clicks? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205055 Title: Impossible to change column width of Nautilus in list view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244806] [NEW] Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10
Public bug reported: Upgrading from Ubuntu 64-bit 13.04 to 13.10 resulted in the attached mess for the Outline presets for Bullets and Numbering in LibreOffice (Version: 4.1.2.3 Build ID: 410m0(Build:3)). Noticed when forced to hand-renumber an imported .DOCX (saved to .ODT) because the font for the numbering in an imported numbered list remained stubbornly immutable, but that will be a different bug. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: lists numbering outline ** Attachment added: Screenshot from 2013-10-25 17:40:49.png https://bugs.launchpad.net/bugs/1244806/+attachment/3891481/+files/Screenshot%20from%202013-10-25%2017%3A40%3A49.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244806 Title: Libre outline numbering presets corrupt after upgrade to Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1244806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209326] Re: calculator fails to do proper calculatoins after CTRL+Z and Enter
Glad I'm not crazy. Recorded what I thought were steps to reproduce with gnome-calculator 1:3.8.1-0ubuntu1: Enter: 5994.34 * .50 see 5994.34 x .50 displayed hit enter result: 2997.17 ^Z undo see 5994.34 x .50 displayed hit enter result: 1498.585 ^Z undo see 5994.34 x .50 displayed hit enter result: 749.2925 ... however it seems like state has to go crazy as indicated by the 5994.34 in 5994.34 x .50 becoming boldface like an unedited result - making the actual outcome equivalent to hitting return without editing the formula to repeat the last operation (*.50), and meaning the above steps failed to reproduce it after some fiddling where it was not in the mood to mistreat the formula as an untouched result as apparently indicated by showing boldface. Nasty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209326 Title: calculator fails to do proper calculatoins after CTRL+Z and Enter To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1209326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174611] Re: tessaract ocr no longer available in gscan2pdf
As a headsup for others, 1.1.3 from PPA solves this but seems to have some work-in-progress quirks re: using scanning backends other than libsane-perl. In plain English this means you regain OCR but may lose access to some convenient page size definitions etc. if, say, scanimage worked more seamlessly with your scanner. [If this is a surprise, do let me know and I'll file a real bug.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174611 Title: tessaract ocr no longer available in gscan2pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1174611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187969] Re: uninstalling fglrx results in unknown bad state
Well, that's a simpler description and the detail's in the comment anyway, but I had no way of knowing if the GUI approach might be touching anything in the 'alternatives' system or thereabouts different from direct apt manipulation. Let me know if there's anything I can do to assist in solving, maybe I can see if this is reproducible from liveUSB where it wouldn't be hard to write a stick and get back to the Xorg radeon driver actually works fine until you try something else state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187969 Title: uninstalling fglrx results in unknown bad state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1187969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187969] [NEW] 13.04: Reverting from fglrx in Additional Drivers results in unknown bad state
Public bug reported: Dropped in a Diamond-branded Radeon 6450 card today to work around LP #1181355 - the default open-source Xorg radeon driver was working flawlessly until I switched to fglrx-updates and then attempted to switch back, all through the settings UI. Possibly I made the mistake of running aticonfig while testing - but same is a prerequisite to use the ATI/AMD utilities to peek at the card's temperature and clocks. (Trivia: The open-source driver does appear to run the card's RAM at 800MHz by default, or at least reports that it does, but this was causing no problems.) In any case, reselecting the Xorg driver after fglrx has been used appears to proceed without complaint, but rebooting then results in either only a purple screen or a 'wrapped screen' bug similar to that described in https://bugzilla.redhat.com/show_bug.cgi?id=827895#c23 - including 'shifted' vtys - that does not change after mode-flipping with Xrandr from a remote session - although modes other than the default 1920x1080 for the monitor are likely to be white, flashing, or full of colored cruft. (However, Unity doesn't appear to take input and whichever component is responsible for nagging for a keyring password doesn't appear to launch until after the mode is flipped to something else and back, so that's still a way to jiggle things enough to be able to interact with the Xorg session at all.) When the card comes up too confused to display more than a purple screen or blank vtys, the xrandr trick doesn't work enough to get that far. Still trying to figure out exactly what has happened here, but filing against software-properties-gtk as that is the component making the 'guarantee' to the user that things should return to a known state when the option is selected. In retrospect I think I may have been bitten by this on other systems and simply left them running fglrx, so it may have been around for a while. Expected behavior: Reselecting Xorg driver should work as well as it did prior to trying out fglrx when installed via the same UI. What happened instead: Stuck with troubleshooting what could possibly have changed to cause the 'permanent' breakage obeserved and/or with fglrx. I'd love to extract some useful telemetry from the affected machine but it's a bit annoying to interact with in the broken state [and at this exact moment someone is using it for work so it is inaccessible to re-break] - figured I would file fast and add detail later just in case this is a known issue with a known but hard-to-Google-for workaround. ** Affects: software-properties (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/1187969 Title: 13.04: Reverting from fglrx in Additional Drivers results in unknown bad state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1187969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
Reviewing state and this bug after wondering why the system wasn't flickering after a reboot, I am reminded that entering and leaving monitor sleep seems to be prerequisite to reproducing the issue. So every boot is fine until the monitor goes to sleep, and disabling it would be a workaround. ** Description changed: + [Edit: Issue narrowed down to Something Bad Happening when the display + goes to sleep. See wordy observations on how to reproduce and/or work- + around in comments ~#4-#7 in Launchpad.] + Any suggestions where to start welcome: Compaq SR1611NX desktop, Radeon Xpress 200 RS480 (R300) graphics. HP LV2311 LCD connected via VGA because that's the only output on this hardware. The VGA output used to be a little less than perfectly stable with older X.org (versions shipped from Ubuntu 9.x to 10.x). Unknown improvements since then have made the overall display much more stable - no more shifty horizontal flicker. In tradeoff, now the top half of the display occasionally flashes distractingly for fractions of a second (single frames?) with memory cruft as you might expect to see during boot or graphics init - generally offset large checkerboard-esque blocks of black and color with no obvious relation to what's on the display. This would seem to suggest it's an actual GPU/driver issue rather than a glitch on the VGA/monitor end of things. No idea how to trigger or reproduce other than that it will generally occur at least once within each 15 minutes or so of use. Expanding and retracting the dash (very slowly due to the current regression - takes about 5+ seconds to fade in and dismiss) will sometimes set it off, however. - - Recommendation for screen-recording software to see if it turns up in software short of pointing an actual camera at the screen? + Recommendation for screen-recording software to see if it turns up in + software short of pointing an actual camera at the screen? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 .tmp.unity.support.test.0: - + .tmp.unity.support.test.1: - + ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri May 17 13:56:33 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series] [1002:5954] (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Device [103c:2a26] + Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series] [1002:5954] (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Device [103c:2a26] MachineType: ASUSTeK Computer INC. RS482-SB400 MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-21-generic root=/dev/mapper/Gins_HD-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.15 dmi.board.name: Amberine M dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.15:bd01/25/2007:svnASUSTeKComputerINC.:pnRS482-SB400:pvr:rvnASUSTekComputerINC.:rnAmberineM:rvr1.03:cvn:ct3:cvr: dmi.product.name: RS482-SB400 dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri May 17 13:36:36 2013 xserver.configfile: default
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
Per multiple re-edits just now, whups, starting LibreOffice with a few documents open from autorecovery and maximizing a window has started it up without the monitor having gone to sleep since booting. Will try to pay attention and report if this puzzler is connected to Libre somehow - I'm never not running it and all workarounds described have probably been discovered/tested with it running and never killed or restarted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
Testing suggesting it's not very application-dependent: 1. With Libre started and 'flickering' occurring, kill -9 it and make sure it's dead; flickering persists while using Firefox. 2. From that state, conduct 'change mode and revert' workaround: flickering stops and does not recur after restarting Libre (prior to letting display sleep happen at least). [Also noting I am likely to give up on this and drop a Radeon 6450 card in as throwing different hardware at the problem is going to be cheaper than the time-cost. Still interested in seeing it resolved to the extent that it's regressive and also always farcical when the hardware requirements for word processing outside of vi arbitrarily go up.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
Workaround seems reproducible after a reboot, although switch to 1280x720 actually produced a working mode this time. (Rebooted to install updates available as of about 0400 UTC 2013-05-24 which contained some things tangentially related to udev, nothing that seemed likely to have graphics impact?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
It appears I was confused and most recent testing _did_ happen in the same session post-reboot, see timestamps in log snippet below; The bug recurs after the display goes to DPMS standby/sleep. It also appears the display corruption on switching modes occurs after the display has its first (or multiple) chances to sleep as I hit it now flipping to 1280x720 the second time in the session - no more clear 1280x720, again a wait for a garbled screen to revert. While Xorg log shows the machine rereading DDC/EDID data when things are woken out of DPMS (and the seizure-inducing flicker recommences), xrandr shows _no_ difference in modelines before/after... not really a surprise but was worth confirming. [I should probably be hunting this bug upstream where it's probably already fixed; maybe another night.] [ 718.155] (II) RADEON(0): Allocate new frame buffer 1280x720 stride 1280 [ 718.155] (II) RADEON(0): VRAM usage limit set to 48193K [ 748.647] (II) RADEON(0): Allocate new frame buffer 1920x1088 stride 1920 [ 748.692] (II) RADEON(0): VRAM usage limit set to 44089K [ 1528.849] (II) RADEON(0): EDID vendor HWP, prod id 12294 [ 1528.849] (II) RADEON(0): Using hsync ranges from config file [ 1528.849] (II) RADEON(0): Using vrefresh ranges from config file [ 1528.849] (II) RADEON(0): Printing DDC gathered Modelines: ... [ 27408.170] (II) RADEON(0): Allocate new frame buffer 1280x720 stride 1280 [ 27408.171] (II) RADEON(0): VRAM usage limit set to 48193K [ 27415.531] (II) RADEON(0): Allocate new frame buffer 1920x1088 stride 1920 [ 27415.576] (II) RADEON(0): VRAM usage limit set to 44089K [ 30534.725] (II) RADEON(0): EDID vendor HWP, prod id 12294 [ 30534.734] (II) RADEON(0): Using hsync ranges from config file [ 30534.734] (II) RADEON(0): Using vrefresh ranges from config file [ 30534.734] (II) RADEON(0): Printing DDC gathered Modelines: [ 30534.734] (II) RADEON(0): Modeline 1920x1080x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 30534.734] (II) RADEON(0): Modeline 800x600x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 30534.734] (II) RADEON(0): Modeline 640x480x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 30534.734] (II) RADEON(0): Modeline 720x400x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [ 30534.734] (II) RADEON(0): Modeline 1024x768x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 30534.734] (II) RADEON(0): Modeline 1280x720x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e) [ 30534.734] (II) RADEON(0): Modeline 1280x1024x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 30534.734] (II) RADEON(0): Modeline 1440x900x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e) [ 30534.735] (II) RADEON(0): Modeline 1680x1050x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) [ 30534.735] (II) RADEON(0): Modeline 1920x1080x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) === While flickering: --- xrandr -q --verbose Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 4096 x 4096 VGA-0 connected 1920x1080+0+0 (0x53) normal (normal left inverted right x axis y axis) 510mm x 287mm Identifier: 0x51 Timestamp: 27407961 Subpixel: no subpixels Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 000022f0063001010101 1216010368331d782e77c5a3544f9f27 115054a1080081c081809500b300d1c0 010101010101023a801871382d40582c 4500fe1f111e00fd00324c18 5e14000a20202020202000fc0048 50204c56323331310a20202000ff 0036434d323138305a43510a2020004c load detection: 1 (0x0001) range: (0,1) 1920x1080 (0x53) 148.5MHz +HSync +VSync *current +preferred h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.5KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz 1680x1050 (0x54) 146.2MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.3KHz v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz 1280x1024 (0x55) 108.0MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 64.0KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz 1440x900 (0x56) 106.5MHz -HSync +VSync h: width 1440 start 1520 end 1672 total 1904 skew0 clock 55.9KHz v: height 900 start 903 end 909 total 934
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
A possible temporary workaround after discovering the issue persists through a warm boot not starting VMWare Player, which I temporarily suspected - only been testing for about 5 minutes here: Used Displays to set 1280x720 instead of 1920x1080. Display becomes a horrible corrupt mess of offset chunks vaguely suggestive of what might be on the desktop except for a perfectly working hardware cursor. Waited for display to revert; post-reversion to 1920x1080 the seizure- inducing blipverts as shown in the images above seem gone and the desktop text is less flickery with timing cruft as well (longstanding problem using the analog output with this hardware similar to the bad old days of the Rage XL). Not sure if this implicates KMS / poor setup from KMS, as alluded to in other similar Radeon bugs. dmesg shows nothing, Xorg log shows nothing interesting from the resolution-flip operations: [ 718.155] (II) RADEON(0): Allocate new frame buffer 1280x720 stride 1280 [ 718.155] (II) RADEON(0): VRAM usage limit set to 48193K [ 748.647] (II) RADEON(0): Allocate new frame buffer 1920x1088 stride 1920 [ 748.692] (II) RADEON(0): VRAM usage limit set to 44089K Inability to successfully downgrade resolution probably counts as another bug but is not of personal interest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182655] Re: Samba printers are missing after reboot until smbd is restarted
** Tags added: raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1182655 Title: Samba printers are missing after reboot until smbd is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1182655/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1182655] Re: Samba printers are missing after reboot until smbd is restarted
Noticed today as well on 13.04 (64-bit). The reload-smbd upstart script already exists to handle this per the prior bugs, but apparently something's still racing. -rw-r--r-- 1 root root 213 Nov 23 08:55 /etc/init/reload-smbd.conf smbd.log appears to suggest that the reload isn't happening (boot at 13:00; manual restart of smbd when printing issue noticed at 14:23): [2013/05/21 13:00:07, 0] smbd/server.c:1026(main) smbd version 3.6.9 started. Copyright Andrew Tridgell and the Samba Team 1992-2011 [2013/05/21 13:00:07.819348, 0] smbd/server.c:1082(main) standard input is not a socket, assuming -D option [2013/05/21 13:00:07.828557, 0] printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2013/05/21 13:00:07.829032, 0] printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2013/05/21 13:00:09.208510, 0] printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2013/05/21 13:00:09.209564, 0] printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2013/05/21 14:23:11, 0] smbd/server.c:1026(main) smbd version 3.6.9 started. Copyright Andrew Tridgell and the Samba Team 1992-2011 [2013/05/21 14:23:12.160294, 0] smbd/server.c:1082(main) standard input is not a socket, assuming -D option -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1182655 Title: Samba printers are missing after reboot until smbd is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1182655/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1182655] Re: Samba printers are missing after reboot until smbd is restarted
** Tags added: raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182655 Title: Samba printers are missing after reboot until smbd is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1182655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182655] Re: Samba printers are missing after reboot until smbd is restarted
Noticed today as well on 13.04 (64-bit). The reload-smbd upstart script already exists to handle this per the prior bugs, but apparently something's still racing. -rw-r--r-- 1 root root 213 Nov 23 08:55 /etc/init/reload-smbd.conf smbd.log appears to suggest that the reload isn't happening (boot at 13:00; manual restart of smbd when printing issue noticed at 14:23): [2013/05/21 13:00:07, 0] smbd/server.c:1026(main) smbd version 3.6.9 started. Copyright Andrew Tridgell and the Samba Team 1992-2011 [2013/05/21 13:00:07.819348, 0] smbd/server.c:1082(main) standard input is not a socket, assuming -D option [2013/05/21 13:00:07.828557, 0] printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2013/05/21 13:00:07.829032, 0] printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2013/05/21 13:00:09.208510, 0] printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2013/05/21 13:00:09.209564, 0] printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2013/05/21 14:23:11, 0] smbd/server.c:1026(main) smbd version 3.6.9 started. Copyright Andrew Tridgell and the Samba Team 1992-2011 [2013/05/21 14:23:12.160294, 0] smbd/server.c:1082(main) standard input is not a socket, assuming -D option -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182655 Title: Samba printers are missing after reboot until smbd is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1182655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] [NEW] R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
Public bug reported: Any suggestions where to start welcome: Compaq SR1611NX desktop, Radeon Xpress 200 RS480 (R300) graphics. HP LV2311 LCD connected via VGA because that's the only output on this hardware. The VGA output used to be a little less than perfectly stable with older X.org (versions shipped from Ubuntu 9.x to 10.x). Unknown improvements since then have made the overall display much more stable - no more shifty horizontal flicker. In tradeoff, now the top half of the display occasionally flashes distractingly for fractions of a second (single frames?) with memory cruft as you might expect to see during boot or graphics init - generally offset large checkerboard-esque blocks of black and color with no obvious relation to what's on the display. This would seem to suggest it's an actual GPU/driver issue rather than a glitch on the VGA/monitor end of things. No idea how to trigger or reproduce other than that it will generally occur at least once within each 15 minutes or so of use. Expanding and retracting the dash (very slowly due to the current regression - takes about 5+ seconds to fade in and dismiss) will sometimes set it off, however. Recommendation for screen-recording software to see if it turns up in software short of pointing an actual camera at the screen? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri May 17 13:56:33 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series] [1002:5954] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a26] MachineType: ASUSTeK Computer INC. RS482-SB400 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-21-generic root=/dev/mapper/Gins_HD-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.15 dmi.board.name: Amberine M dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.15:bd01/25/2007:svnASUSTeKComputerINC.:pnRS482-SB400:pvr:rvnASUSTekComputerINC.:rnAmberineM:rvr1.03:cvn:ct3:cvr: dmi.product.name: RS482-SB400 dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri May 17 13:36:36 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPIXART USB OPTICAL MOUSE MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
After catching it in the act with my phone camera, the glitch seems prone to reusing more recognizable content today - this is my desktop background (although there's a pile of icon-litter on top of it in normal circumstances) offset and possibly tinted a bit. Also seeing more non-vertically-aligned bursts of horizontal dark lines and cruft while typing this. In fact, typing is a surprisingly good way to trigger it compared to leaving the screen idle... ** Attachment added: Caught in the act with phone cam - Offset desktop background https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+attachment/3679734/+files/Screenshot%20from%20VID_20130517_144325.mp4.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181355] Re: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p)
** Attachment added: Earlier frame from video while typing into LibreOffice https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+attachment/3679735/+files/Screenshot%20from%202013-05-17%2014%3A54%3A21.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181355 Title: R300 (RS480): Intermittent flickering corruption top half of display (VGA, 1080p) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176475] Re: 13.04 amd64: Packages missing on upgrade: activity-log-manager-control-center, gnome-control-center-signon, gnome-control-center-unity
As came up while trying to figure out where the U1 Music Store went (apparent answers after much screen-scraping: gone from Rhythmbox, not in The Store, moved into Dash which really just opens a link in Firefox, correct me in private if I'm wrong?), the Cloud Indicator is also missing. Some web-searching suggests this is indicator-sync - which is installed, and no change after a deinstall+reinstall of the package without a logout that I'm loathe to try just now... But that package is also described as indicating only sync status so I'm not sure it's even what the one that comes with a properly working 13.04. ...anyone got a clue here? Did this just not make it as a 64-bit package or do I have a big inexplicable indicators SNAFU? [Naturally I actually use U1 for some things - music purchases at least - while my user with a working cloud indicator doesn't, yet.] The U1 web UI (as linked by trying to buy music in the Dash) appears to be a workaround, but I'd like to solve how/why I quietly would up missing all these UI packages (including the perhaps-legally-important-in-some-jurisdictions 'privacy' panel) for the benefit of everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176475 Title: 13.04 amd64: Packages missing on upgrade: activity-log-manager- control-center, gnome-control-center-signon, gnome-control-center- unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176475] Re: 13.04 amd64: Packages missing on upgrade: activity-log-manager-control-center, gnome-control-center-signon, gnome-control-center-unity
** Attachment added: main.log https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+attachment/3665442/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176475 Title: 13.04 amd64: Packages missing on upgrade: activity-log-manager- control-center, gnome-control-center-signon, gnome-control-center- unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176475] [NEW] 13.04 amd64: Packages missing on upgrade: activity-log-manager-control-center, gnome-control-center-signon, gnome-control-center-unity
Public bug reported: Sat through an uneventful update-manager upgrade from 12.10 to 13.04 on amd64 recently - only to find that at least the following packages were absent after the upgrade: gnome-control-center-unity [provides Appearance settings panel] activity-log-manager-control-center [provides Privacy settings panel] gnome-control-center-signon [provides Online Accounts settings panel] It's a bit worrying that I was not aware the Privacy settings panel was missing 'via bug' rather than 'by new default' until I booted a liveUSB image to evaluate performance on some old hardware* and noticed the difference. I also seem to have acquired an Adwaita theme (missing icons and all) dating from the day of the upgrade not present in the liveCD image. [And I _also_ seem to have just discovered that double-clicking to open a sources.list in an archive in file-roller will automatically import unknown settings from the file when privileges are available rather than open it in gedit for examining as naively expected. I'm good at this game! Ugh.] *Unity now performs very well on the Radeon Xpress 200 under 13.04 and will spare me from adding graphics cards just to handle the desktop environment - kudos to all of the Xorg, Unity, Ubuntu and other developers behind that improvement. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: update-manager 1:0.186 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat May 4 23:14:18 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to raring on 2013-05-02 (3 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade raring ** Attachment added: apt-term.log https://bugs.launchpad.net/bugs/1176475/+attachment/3665434/+files/apt-term.log ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176475 Title: 13.04 amd64: Packages missing on upgrade: activity-log-manager- control-center, gnome-control-center-signon, gnome-control-center- unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176475] Re: 13.04 amd64: Packages missing on upgrade: activity-log-manager-control-center, gnome-control-center-signon, gnome-control-center-unity
** Attachment added: history.log https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+attachment/3665443/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176475 Title: 13.04 amd64: Packages missing on upgrade: activity-log-manager- control-center, gnome-control-center-signon, gnome-control-center- unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176475] Re: 13.04 amd64: Packages missing on upgrade: activity-log-manager-control-center, gnome-control-center-signon, gnome-control-center-unity
** Attachment added: apt.log https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+attachment/3665444/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176475 Title: 13.04 amd64: Packages missing on upgrade: activity-log-manager- control-center, gnome-control-center-signon, gnome-control-center- unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176475] Re: 13.04 amd64: Packages missing on upgrade: activity-log-manager-control-center, gnome-control-center-signon, gnome-control-center-unity
apt-term.log hidden as single manual attachment permitted in first wad of telemetry attached by running ubuntu-bug against update-manager (probably entirely uselessly but I'm still getting used to being redirected to ubuntu-bug to report issues). term.log empty and lspci.txt unlikely to be interesting so not attached. If anyone needs to see apt-clone_system_state.tar.gz let me know - pretty sure there's nothing thrillingly private in there compared to everything else already attached but it's not world-readable by default so just spent a few moments wondering why it wouldn't upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176475 Title: 13.04 amd64: Packages missing on upgrade: activity-log-manager- control-center, gnome-control-center-signon, gnome-control-center- unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1176475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098561] Re: Unsupported hardware watermark appears when FGLRX is installed on 13.04
Also seen in the release with: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6450] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 2311 (ID 1787:2311. Believe it's a Powercolor-branded card.) Switching to fglrx-updates under Software Updates - Additional Drivers is the quick fix. [Who knew it was hiding there? At least it's a one-click fix.] Beyond the obvious, this will be taking a few seconds off a lot of lifetimes because there's a black-screen delay on first boot after an upgrade where the watermark is the only thing visible. Probably under 30 seconds while misc. components of Unity and the rest of the desktop prep themselves, but enough time to wonder if that's *all* the driver's going to let you see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098561 Title: Unsupported hardware watermark appears when FGLRX is installed on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1098561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171979] [NEW] Ambiance vs. acroread (Adobe Reader): Unreadable tabs
Public bug reported: Screenshot attached is worth a thousand words. Radiance is, of course, a fix, but this has been present for a while and is a wart on the default theme. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubuntu-artwork 58 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Tue Apr 23 15:04:52 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-artwork UpgradeStatus: Upgraded to quantal on 2012-12-10 (134 days ago) ** Affects: ubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: Gray text on gray background in inactive Adobe Reader tabs with Ambiance theme https://bugs.launchpad.net/bugs/1171979/+attachment/3651794/+files/Theme_Conflict.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171979 Title: Ambiance vs. acroread (Adobe Reader): Unreadable tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-artwork/+bug/1171979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897786] Re: Kernel is dropping non-PAE flavour
@Chris Bainbridge re comment #31: but I haven't seen any reports of PAE kernel failing to boot on Pentium M. Does this go for Banias as well as Dothan Pentium Ms? My understanding is that Dothan actually supports PAE but was potentially crippled-by- chipset (but if so does that really touch cpuflags?) in common designs, while the original Banias supposedly completely lacks it [at least doesn't advertise it]... and the NX support that this is supposed to really be about came in with Dothan (which I assume will report under cpuflags in all circumstances?). I have a couple Dell D600s which are Banias so would be interested to know what the real deal is. (Not thrilled to play guinea pig more after treating the hardware as bricked for a year when it *was* supported because I expected the rtl8180 driver to work, but if no one else steps up...) Interesting that, per wikiality, Microsoft apparently made this same exact decision for Windows 8 and Fedora has apparently been enforcing it where supported by the hardware since c. 2009 but searching re: the Ubuntu issue never turned up screaming and rending of clothes from that camp. (Does Fedora do something more sane here?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897786 Title: Kernel is dropping non-PAE flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/897786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101374] Re: Can't add new location
*** This bug is a duplicate of bug 1090890 *** https://bugs.launchpad.net/bugs/1090890 ** This bug is no longer a duplicate of bug 1094676 fails to parse Yahoo response ** This bug has been marked a duplicate of bug 1090890 weather applet crashes when you add a locality -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101374 Title: Can't add new location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/1101374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101374] Re: Can't add new location
*** This bug is a duplicate of bug 1090890 *** https://bugs.launchpad.net/bugs/1090890 ** This bug has been marked a duplicate of bug 1094676 fails to parse Yahoo response -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101374 Title: Can't add new location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/1101374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101374] Re: Can't add new location
*** This bug is a duplicate of bug 821233 *** https://bugs.launchpad.net/bugs/821233 ** This bug is no longer a duplicate of bug 1090890 weather applet crashes when you add a locality ** This bug has been marked a duplicate of bug 821233 indicator-weather crashed with AttributeError in export_location_details(): Location instance has no attribute 'location_code' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101374 Title: Can't add new location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/1101374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087555] Re: Pidgin segfaults Metacity using unity-2d in 12.04 due to liboverlay-scrollbar
After somehow forgetting about this, I now note the place to stick the 'patch' override is /usr/share/applications/pidgin.desktop, making the Exec line: Exec=LIBOVERLAY_SCROLLBAR=0 pidgin Sadly the whole Unity/Dash morass made it a bit difficult to track that down (and this even for someone well aware of .desktop files, just not sure where the applicable one was sitting). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087555 Title: Pidgin segfaults Metacity using unity-2d in 12.04 due to liboverlay- scrollbar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1087555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087555] [NEW] Pidgin segfaults Metacity using unity-2d in 12.04 due to liboverlay-scrollbar
Public bug reported: Using pidgin 1:2.10.3-0ubuntu1 , overlay-scrollbar 0.2.16+r357-0ubuntu1 , Ubuntu 12.04 x86 32-bit... I was reliably blowing up Metacity, if not Xorg itself, trying to launch Pidgin; see mess of a pidgin -d log below that hinted the problem might have something to do with scrollbars - and lo: setting LIBOVERLAY_SCROLLBAR=0 results in a working Pidgin. Presumably this should be easy to reproduce. I would've been happy to just have had a startup script thrown in as a patch so as to not run into it. Under certain circumstances I may've managed to get it to take out more than just Metacity, like the entire X.org session, but I lost track of what exactly might reproduce that other than trying repeatedly, because how the heck did a boring app like Pidgin manage to break? It appears that was probably just an OOM kill for a crowded session with long uptime being stressed by whatever ridiculous thing X.org is being asked to do until it realizes it can't. floid@miscreant:~$ pidgin -d (22:44:06) prefs: Reading /home/floid/.purple/prefs.xml (22:44:06) prefs: Finished reading /home/floid/.purple/prefs.xml (22:44:06) prefs: purple_prefs_get_path: Unknown pref /pidgin/browsers/command (22:44:06) dbus: okkk (22:44:06) plugins: probing /usr/lib/pidgin/vvconfig.so (22:44:06) plugins: probing /usr/lib/pidgin/markerline.so (22:44:06) plugins: probing /usr/lib/pidgin/timestamp_format.so (22:44:06) plugins: probing /usr/lib/pidgin/themeedit.so (22:44:06) plugins: probing /usr/lib/pidgin/history.so (22:44:06) plugins: probing /usr/lib/pidgin/convcolors.so (22:44:06) plugins: probing /usr/lib/pidgin/extplacement.so (22:44:06) plugins: probing /usr/lib/pidgin/gestures.so (22:44:06) plugins: probing /usr/lib/pidgin/musicmessaging.so (22:44:06) plugins: probing /usr/lib/pidgin/xmppdisco.so (22:44:06) plugins: probing /usr/lib/pidgin/cap.so (22:44:06) plugins: probing /usr/lib/pidgin/spellchk.so (22:44:06) plugins: probing /usr/lib/pidgin/xmppconsole.so (22:44:06) plugins: probing /usr/lib/pidgin/ticker.so (22:44:06) plugins: probing /usr/lib/pidgin/notify.so (22:44:06) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (22:44:06) plugins: probing /usr/lib/pidgin/timestamp.so (22:44:06) plugins: probing /usr/lib/pidgin/pidginrc.so (22:44:06) plugins: probing /usr/lib/pidgin/sendbutton.so (22:44:06) plugins: probing /usr/lib/pidgin/iconaway.so (22:44:06) plugins: probing /usr/lib/purple-2/libjabber.so (22:44:06) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (22:44:06) plugins: probing /usr/lib/purple-2/libnovell.so (22:44:06) plugins: probing /usr/lib/purple-2/autoaccept.so (22:44:06) plugins: probing /usr/lib/purple-2/libyahoojp.so (22:44:06) plugins: probing /usr/lib/purple-2/libbonjour.so (22:44:06) plugins: probing /usr/lib/purple-2/ssl-nss.so (22:44:06) plugins: probing /usr/lib/purple-2/libzephyr.so (22:44:06) plugins: probing /usr/lib/purple-2/libxmpp.so (22:44:06) plugins: probing /usr/lib/purple-2/joinpart.so (22:44:06) plugins: probing /usr/lib/purple-2/libirc.so (22:44:06) plugins: probing /usr/lib/purple-2/libmxit.so (22:44:06) prpl-loubserp-mxit: Loading MXit libPurple plugin... (22:44:06) plugins: probing /usr/lib/purple-2/idle.so (22:44:06) plugins: probing /usr/lib/purple-2/libgg.so (22:44:06) plugins: probing /usr/lib/purple-2/perl.so (22:44:06) plugins: probing /usr/lib/purple-2/buddynote.so (22:44:06) plugins: probing /usr/lib/purple-2/libicq.so (22:44:06) plugins: probing /usr/lib/purple-2/libsimple.so (22:44:06) plugins: probing /usr/lib/purple-2/ssl.so (22:44:06) plugins: probing /usr/lib/purple-2/pidgin-libnotify.so (22:44:06) plugins: probing /usr/lib/purple-2/libymsg.so (22:44:06) plugins: /usr/lib/purple-2/libymsg.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (22:44:06) plugins: probing /usr/lib/purple-2/tcl.so (22:44:06) plugins: /usr/lib/purple-2/tcl.so is not loadable: libtk8.5.so.0: cannot open shared object file: No such file or directory (22:44:06) plugins: probing /usr/lib/purple-2/log_reader.so (22:44:06) plugins: probing /usr/lib/purple-2/libmyspace.so (22:44:06) plugins: probing /usr/lib/purple-2/psychic.so (22:44:06) plugins: probing /usr/lib/purple-2/liboscar.so (22:44:06) plugins: /usr/lib/purple-2/liboscar.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (22:44:06) plugins: probing /usr/lib/purple-2/newline.so (22:44:06) plugins: probing /usr/lib/purple-2/dbus-example.so (22:44:06) plugins: probing /usr/lib/purple-2/libyahoo.so (22:44:06) plugins: probing /usr/lib/purple-2/statenotify.so (22:44:06) plugins: probing /usr/lib/purple-2/libsametime.so (22:44:06) plugins: /usr/lib/purple-2/libsametime.so has a prefs_info, but is a prpl. This is no longer supported. (22:44:06
[Bug 1066294] Re: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
@alpha1: I'm just another vaguely-confused end user like you; as far as I can tell there should be no reason for the kernel to *demand* PAE aside from Ubuntu apparently wanting to make sure all their users have W^X protections (given Ubuntu's popularity among distributions, that's a fair point, but only the subset of users with PAE-less hardware would be vulnerable if they simply gave up on the apparently annoying-to-maintain emulation patch) ... and guarantee that people with 4GB running 32-bit can see all their RAM (the main reason PAE exists). As far as I can tell the 'official' solution is to hang back with 12.04 LTS and see what happens when the 'LTS' runs out. I don't think many other distributions have made the same decision yet (some people have pointed back to 'plain old Debian', for instance) and there's always the fun options of customizing your own kernel or trusting someone's unofficial build - so if you want to stick with 12.10, check around the forums for links to PPAs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066294 Title: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069063] Re: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066294 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069063 Title: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066294] Re: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
I hope this isn't just a me-too, but I want to add that I'm amazed that I somehow lived through both 12.04 (and the 12.10 upgrade process) completely oblivious to the fact that PAE had become 'temporarily requisite' for 12.04 at launch and now definitely requisite for 12.10 absent 'unsupported' hacks and workarounds.* The upgrade process on a Dell Latitude D600 laptop (first-generation Pentium M, no PAE) did warn that my graphics were at risk for being unsupported (as prior versions have), but there's no equivalent check and warning for the 'CPU surprise.' Since Ubuntu does leave old kernels lying around in /boot, the upgraded system was still bootable with 3.2.0, but between the kernel issue and the fact that Unity still isn't satisfied with what GL features the radeon driver can offer with an ATI Radeon Mobility 9000 (M9) Lf (AGP) (ChipID = 0x4c66) - yet no longer falls back to unity-2d, despite it still being installed** - I decided to back out rather than fight. For users bit by this scenario who want to 'downgrade' back to a known state, the following abuse of apt (as posted on the Ubuntu Wiki) works: Replace /etc/apt/sources.list with the helpfully-saved sources.list.distUpgrade in the same directory; Create the file /etc/apt/preferences containing the following: Package: * Pin: release a=precise Pin-Priority: 1001 Then: apt-get update; apt-get dist-upgrade; wait, wait some more, and you'll be back to 12.04. (That this managed to result in circular dependencies for CUPS on my system, so printing may be dead until you resolve that by hand, but elsewise things are back to normal.) *The 'official' workarounds aren't terribly bad if you're starting from a fresh install: Rely on xubuntu (XFCE) or lubuntu (LXDE), then install the ubuntu-desktop package if you want Unity alongside the lighter-weight desktops - but that sort of 'crossgrade' is a little more annoying on an installed system you'd just intended to update rather than modify. If you're determined, some minor adjustments to the above recipe should work. However, it's unclear how long the 'lightweight' distributions will continue to offer non-PAE kernels if the main Ubuntu kernel team is tired of maintaining some of the security patches; if there's a 'position statement' from those distros re: how long support can be expected, please link! **(The absence of unity-2d fallback is surely surmountable with editing of the GDM config; I just wasn't in the mood. I'm still somehow surprised that Unity demands more GL features than compiz.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066294 Title: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066294] Re: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Sorry, per #3 [thanks vilbara, wish I'd actually read your comment first!], it looks like xubuntu and lubuntu were workarounds for the initial PAE-free release of 12.04, but have already inherited the PAE requirement from mainline Ubuntu for 12.10, so... the 'grace period' offered by those distributions has already expired. [I'd be happy to live insecurely but cautiously without NX emulation - AFAIK it wasn't even introduced to Ubuntu until relatively recently, see bug #369978 - maintenance of the patch being claimed as one reason for going PAE-only - even if this required manual installation of a specific 'nopae-insecure' kernel with screaming warnings after the fact, but given the other limitations it seems unlikely that many of the 'hot new features' post-12.04LTS would be available on my hardware anyway.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066294 Title: package linux-image-3.5.0-17-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055766] Re: grep -R doesn't automatically search amazon
re: #35 - could this overlay functionality be used to present automatically-updating context-sensitive QR codes? Then a user poking through a source tree would simply have to point a smartphone at the screen to purchase a license to Visual Studio 2012. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055766 Title: grep -R doesn't automatically search amazon To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1055766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827193] [NEW] Asus M3A78-EM / Realtek ALC1200 - output selection SNAFU
Public bug reported: I made the mistake of trying to use headphones about 36 hours ago. ;) gnome-volume-control is aware of two 'connectors' for the analog device, Analog Output and Analog Headphones. It turns out the front headphone output [presumably at Node 0x1b, Headphone Playback Switch per /proc/asound/card0/codec#0] *does* pass output along with the rear line out (Node 0x14, [Jack] Line Out at Ext Rear) when Analog Output is selected, but both jacks go dead when Analog Headphones are selected. (The working headphone output under the Analog Output profile can be hard to notice when speakers are in the rear jack and cranked up!) Further investigating shows that alsamixer's conception of the Front channel has to be unmuted along with the headphone switch (choices of mute or '00' for 'Headphon' in alsamixer) to receive headphone output (or any output, since at least the rear green line-out depends on this as well). Somewhat worse, the switch sometimes must be toggled twice after muting to actually get sound out the jack - or as I've just noticed, the Front channel may also need to be 'jiggled' a second time before it unmutes or raises its volume level from 00. passing model=6stack to the snd-hda-intel module changed nothing - though I do note model parameters are device-specific and I'm still digging around to figure out how much alsa knows about the ALC1200 in this and future versions. Now that I've realized the front headphone output *is* working by default, I see that the rear output at Node 0x14 can be muted with the alsa hda-analyzer and the front headphone output keeps on playing. I suppose this means this bug is mainly with gnome-volume-control's idea of what the Analog Headphones mixer profile is, with the added confusion of the mixer settings not always 'taking' on the first try in alsamixer (although that only turned up when I started poking at those channels in alsamixer, never in normal use of the regular panel volume control). The behavior with Analog Output selected is fine with me (although one might assume that one is changing levels for the selected 'connector' only, and that this would be the rear connector only under the Analog Stereo Duplex profile), but clearly Analog Headphones should not be _disabling_ output from the front jack! ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: floid 2104 F pulseaudio /dev/snd/pcmC0D0p: floid 2104 F...m pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfbbf4000 irq 16' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,104382fe,00100101' Controls : 40 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbde8000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Aug 16 04:17:22 2011 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Internal Audio - HDA ATI SB Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [System Product Name, Realtek ALC1200, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to natty on 2011-04-13 (125 days ago) dmi.bios.date: 10/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2701:bd10/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827193 Title: Asus M3A78-EM / Realtek ALC1200 - output selection SNAFU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu
[Bug 827193] Re: Asus M3A78-EM / Realtek ALC1200 - output selection SNAFU
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827193 Title: Asus M3A78-EM / Realtek ALC1200 - output selection SNAFU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/827193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368679] Re: wifi module rtl8180 freezes the system
Does pcie_aspm=off as described in #21 do anything in systems that predate PCI-E? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/368679 Title: wifi module rtl8180 freezes the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768357] [NEW] Natty: Suspend bug(s) on Dell D600 as of 2011-04-21
Public bug reported: Yet another recent suspend bug, this time showing up on the Dell D600 with first-Centrino-generation-era hardware. Providing automated collection in case it's any help. Notes: 1. Problem inspiring filing is that I [fsck'd my system after problem 3 below], ran update-manager around 2011-04-21 USEDT, later Suspend- ed, and upon attempting resume got a black screen, unresponsive keyboard LEDs (CapsLock etc), and the disk access light wedged on. The boot apport collected from is from using the recovery menu to force fsck if there's any cruft from that. 2. Suspend [and possibly hibernate, see below] appeared to be working as recently as at least 2011-04-18 while running update-manager daily. 3. On the evening of local 2011-04-19 I attempted to *Hibernate* the machine and received a console message to the effect of 'not enough free memory to hibernate' (512MB RAM/512MB swap, this machine tends to fill both rapidly). Rebooting from that I discovered ext4 corruption such that grub would not recognize the partition. [Additional variables are that the HD is a CF card - which does claim write cache is disabled - and I am using laptop-mode with a ~30 second timeout to hopefully coalesce some writes and maybe spare it some wear. Of course I'm also swapping to it right now, but SMART indications are still good.] That's presumably a different (and presumably destructive!) bug that I lack any further detail for. 4. re: anything else that might look mildly unusual in dmesg, etc: I have my misbegotten internal rtl8185 wireless card still installed, the faulty rtl8180 driver has to be blacklisted to not freeze at boot. There's an old Atheros card in the cardbus slot allowing me to submit this. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: floid 1315 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5' Mixer name : 'SigmaTel STAC9750,51' Components : 'AC97a:83847650' Controls : 38 Simple ctrls : 24 Date: Thu Apr 21 10:16:06 2011 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6c28ff16-1b04-41f4-b000-06978aac3766 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302) Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0781:5562 SanDisk Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Computer Corporation Latitude D600 PccardctlIdent: Socket 0: no product info available Socket 1: product info: O2Micro, SmartCardBus Reader, V1.0, manfid: 0x, 0x0001 PccardctlStatus: Socket 0: 3.3V 32-bit PC Card Socket 1: 5.0V 16-bit PC Card Subdevice 0 (function 0) [unbound] ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=96e149e5-1f55-44d3-90e5-4fe144fc4662 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.51 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to natty on 2011-04-19 (2 days ago) dmi.bios.date: 06/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A12 dmi.board.name: 0G5152 dmi.board.vendor: Dell Computer Corporation dmi.chassis.type: 8 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA12:bd06/01/2004:svnDellComputerCorporation:pnLatitudeD600:pvr:rvnDellComputerCorporation:rn0G5152:rvr:cvnDellComputerCorporation:ct8:cvr: dmi.product.name: Latitude D600 dmi.sys.vendor: Dell Computer Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768357 Title: Natty: Suspend bug(s) on Dell D600 as of 2011-04-21 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768357] Re: Natty: Suspend bug(s) on Dell D600 as of 2011-04-21
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768357 Title: Natty: Suspend bug(s) on Dell D600 as of 2011-04-21 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 616097] Re: Dell D600 + RTL8185L = livecd boot hang through 11.04a3
*** This bug is a duplicate of bug 368679 *** https://bugs.launchpad.net/bugs/368679 With some sleep, blacklisting rtl8180 is obviously the short-term workaround, and this is a dupe of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679 ** This bug has been marked a duplicate of bug 368679 wifi module rtl8180 freezes the system * You can subscribe to bug 368679 by following this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/616097 Title: Dell D600 + RTL8185L = livecd boot hang through 11.04a3 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 616097] Re: Dell D600 - 10.04, 10.10 boot hang (livecd)
I'm chagrined to report that this continued to be a problem with 11.04 Alpha 3, but removing the third-party-surplus-sourced Arima-branded RTL8185L wireless card allows the installer to boot flawlessly. Obviously this is suboptimal for those who manage to have that hardware present and don't want to rip it out to install. Unfortunately without more verbose output even a text boot is not particularly helpful for debugging just *what* is going haywire and freezing the machine [apparently around the time it goes to configure that interface]. I have two of the apparently-troublesome cards in two D600s, and the freeze with the hardware installed reproduces in both of them across a couple BIOS versions. That's all I've got so far. Other OSes [DragonFly BSD, FreeDOS ...] are not as intrinsically bothered by the RTL8185L card being present. ** Summary changed: - Dell D600 - 10.04, 10.10 boot hang (livecd) + Dell D600 + RTL8185L = livecd boot hang through 11.04 ** Summary changed: - Dell D600 + RTL8185L = livecd boot hang through 11.04 + Dell D600 + RTL8185L = livecd boot hang through 11.04a3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/616097 Title: Dell D600 + RTL8185L = livecd boot hang through 11.04a3 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 616097] Re: Dell D600 + RTL8185L = livecd boot hang through 11.04a3
Popping the card back into a happily installed system results in a freeze somewhere just after the Radeon drm initializes and: * Starting AppArmor profiles; Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox [ OK ]. Thoughts on how to proceed will be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/616097 Title: Dell D600 + RTL8185L = livecd boot hang through 11.04a3 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 624043] Re: Avahi needs to be restarted after boot to broadcast netatalk services
This may or may not relate to this bug, and may or may not be the workaround, but recently [and only recently] became a recurring issue after accepting some updates on 9.10 machines. Musing on the source for that mysterious SIGTERM revealed duplicate up/down scripts for dhclient: in /etc/dhcp3/dhclient-enter-hooks.d/: -rwxr-xr-x 1 root root 1037 2008-07-27 14:35 avahi-autoipd -rwxr-xr-x 1 root root 1037 2011-03-04 15:51 avahi-autoipd.dpkg-new in /etc/dhcp3/dhclient-exit-hooks.d/: -rwxr-xr-x 1 root root 1039 2008-07-27 14:35 zzz_avahi-autoipd -rwxr-xr-x 1 root root 1039 2011-03-04 15:51 zzz_avahi-autoipd.dpkg-new and equivalent mess in /etc/network/if-up.d/ and if-down.d/. All files diffed identically, so assuming dpkg is at risk to keep making a mess, I removed the earlier copies and kept *.dpkg-new. Things now appear to be working and surviving a networking restart and various rude pokings of the dhclient. Hope this helps someone! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/624043 Title: Avahi needs to be restarted after boot to broadcast netatalk services -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 624043] Re: Avahi needs to be restarted after boot to broadcast netatalk services
[To clarify *my* issue and discovery: random loss of avahi / mDNS *after boot* was determined to be due to the duplicate scripts competing in absurd ways. This may not have anything to do with a separate race with netatalk, but I found this bug based on the SIGTERM logged in https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/624043/comments/9 which could be due to the same SNAFU.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/624043 Title: Avahi needs to be restarted after boot to broadcast netatalk services -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475704] Re: Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424
@Ton van Vliet:
I'm not in charge and barely know who is. Since it hasn't been
backported yet [as far as I know - I think my 10.04 machines are
demanding another reboot after auto-updates], ignoring the messages is
certainly one option.
Not to grouse about it [since I've gotten used to it] but the attitude
to LTS releases seems to be if something was broken, don't have any
expectation that 'support' means it should be fixed, 'support' equals
patches for security and major functional issues if a Y2K-type bug pops
up across all systems during the 'support' period. (Actually, keeping
the zoneinfo package current for the world's ever-changing DST rules is
probably a good example of what 'support' really means.) So since it
was doing this from day one, this bug is just an ongoing characteristic
('feature'?) of 10.04.
Of course, if we flag someone down by making noise here, the *real*
patch is simple enough now that it's identified that I don't think
anyone could complain about getting it in the tree.
In my brief evaluation of 10.10 I forgot to check whether the kernel with the
actual patch [and any other changes] would solve the issues with suspend/resume
on this hardware. That could be worth checking if suspend/resume is of
interest to you, I'll have to go back and try it myself.
--
Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT,
Returned by Handler for [SystemIO] 20090521 evregion-424
https://bugs.launchpad.net/bugs/475704
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 475704] Re: Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424
@Ton van Vliet: See #20 for a by hand patch for the actual problem - thanks to Frank Larimer for identifying it there. This or an equivalent made it into 10.10's kernel as described in my #22, so 10.10 is the lazy option if you want to upgrade. [Do I read it right: The MS compiler generates code with malformed addresses that are supposed to be 32-bit by the spec, while MS Windows cheerfully ignores upper 16 bits? Or is this something the author of the DSDT has to directly screw up, and Windows' behavior just lets them get away with it?] re: 10.10 on these systems, the unrelated noise from the other bug mentioned in my #22 is actually more intermittent/not nearly so much of an issue or annoyance as I first thought, if it's not already fixed anyway [haven't checked since 10.10 went final, it may have been fixed by now]. Importing or enabling the N,000 messages: Ignoring feature as found in certain BSDs might not be a bad idea, still... -- Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424 https://bugs.launchpad.net/bugs/475704 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 616097] Re: Dell D600 - 10.04 boot hang (livecd/post-install)
** Description changed: - This is being somewhat annoying to track down, so I'm posting with the - minimal information I have in case there's a quick, known fix -- or, - vexingly, if it helps confirm I'm the only person in the world who can - reproduce this problem, since there seem to be other users describing no - issue. + [Edited - problems still observed with 10.10 RC] - Symptoms: Attempting to boot from the LiveCD, or from a fresh install - with the alternate CD, results in a hang around the time the boot splash - animation reaches the final 'dot.' The boot splash animation also comes - up with a corrupt/'psychedelic' palette. The graphic stays frozen on - the screen, the fan runs, and the keyboard becomes unresponsive, making - troubleshooting annoying. + Symptoms: Attempting to boot 10.04 from the LiveCD or from a fresh + install with the alternate CD, and 10.10 RC LiveCD, results in a hang + around the time the boot splash animation reaches the final 'dot.' The + boot splash animation also comes up with a corrupt/'psychedelic' + palette. The graphic stays frozen on the screen, the fan runs, and the + keyboard becomes unresponsive, making troubleshooting annoying. - Booting the alternate CD to the console works. Somewhat quirkily, an - install from the alternate CD also worked when rebooted after the - apparent hang, but something (a post-install script?) got addled, - because I can both reach the console or startx with no problem, but dbus - was not starting properly and gdm et al. refused to work. I looked - around for the obvious culprit on *that* but couldn't find it, and right - now I'm trying to remove variables and achieve a normal installation, - not add more. Since the base system does boot fine in that - circumstance, I guess I'm looking at something more X or firstboot- - related, but I don't know what. + Booting the 10.04 alternate CD to the console worked. Somewhat + quirkily, an install from the 10.04 alternate CD also worked when + rebooted after the apparent hang, but something (a post-install script?) + got addled, because I can both reach the console or startx with no + problem, but dbus was not starting properly and gdm et al. refused to + work. I looked around for the obvious culprit on *that* but couldn't + find it at the time, and now that I have returned to the problem I'm + focusing on getting 10.10 up. Booting/installing 9.04 or thereabouts actually works, so it does not - seem to be an innate hardware problem - but sitting through upgrades - from there to 'present' is a workaround too awkward to test just yet. - + seem to be an innate hardware problem. Hardware configuration: Dell Latitude D600 laptop; 512MB RAM; 1024x768 LCD with what identifies as a RV250; only hardware quirks are use of a UDMA CompactFlash card in place of a disk and use of a generic Realtek-based miniPCI wireless card. + --- - If someone can summarize the parameters necessary to turn graphical boot off and watch dmesg/console up to the point that it hangs, I'd appreciate it. + I had asked if someone could summarize the parameters necessary to turn + graphical boot off and watch dmesg/console up to the point that it + hangs; thanks to Gordon Hopper for obliging. + + Using 10.10 RC on a USB stick [my CD burns have complained about a sense + error on one particular sector on multiple devices]: + + - With default options, but the 'splash' and 'quiet' removed, I make it to: + * Setting sensors limits + + - With 'text', and the 'nomodeset' and 'acpi=off' boxes checked for good measure, I make it to: + * Pulseaudio configured for per-user sessions + + Somewhere between these extremes, it can freeze at the message between them, this being: + * Starting Kernel Oops catching service kerneloops + + I have gone so far as to unplug the HD (a CF card in CF-to-IDE + carrier) and to attempt to set BIOS options as conservatively as + possible [but perhaps I have missed something]. + + This does not seem to be the best way to debug the problem. Insight / + further suggestions are appreciated - surely there's a way to make + booting more verbose than this? -- Dell D600 - 10.04 boot hang (livecd/post-install) https://bugs.launchpad.net/bugs/616097 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 616097] Re: Dell D600 - 10.04 boot hang (livecd/post-install)
Fails in a similar way at a similar point with the daily: maverick-desktop-i386.iso05-Oct-2010 09:15 693M Desktop CD for PC (Intel x86) computers (standard download) Particularly, still makes it exactly to * Pulseaudio configured for per-user sessions with all 'dangerous' options turned off in the menu + 'text', and to the speech-dispatcher with simply 'text'. ** Summary changed: - Dell D600 - 10.04 boot hang (livecd/post-install) + Dell D600 - 10.04, 10.10 boot hang (livecd) -- Dell D600 - 10.04, 10.10 boot hang (livecd) https://bugs.launchpad.net/bugs/616097 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 653388] Re: 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400)
Confirmed behavior: On the machine that was warm-booted into i386 10.10 RC and back to 9.10, 9.10 with i386 2.6.31-22-generic #65-Ubuntu SMP does generate the noise from timestamps ~ 20 to 67 at boot. I haven't bothered checking to make sure it goes away from a cold boot - it's hardly a big deal - but does imply the 10.10 RC 'nudged' the hardware into a state to trigger it. On an identical machine running 9.10 with the same i386 2.6.31-22-generic #65-Ubuntu SMP, I do have history back to boot-time and there's no such complaint. Obviously warnings that *never stop* are annoying, but that was only observed the once. -- 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400) https://bugs.launchpad.net/bugs/653388 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 653388] Re: 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400)
Trouble with bug-reporting towards local midnight: I lied in a couple important ways: 1. I noticed this because it was *continually* flooding dmesg in my first boot into 10.10 RC; the halt of the messages at [ 335.695389] was seen on a later boot, and suggests this is an intermittent issue; 2. After announcing that it only occurs with 10.10 RC, I caught a flash of it while booting back into 9.10, so it may not be a regression and just have been drowned out by https://bugs.launchpad.net/bugs/475704 . However, I've never noticed it mixed in with that bug's noise before, so the *continuous* complaining first observed must be a rare or new case. What I did *not* do was properly check the logs under 9.10 to confirm 'that really happened' and I was not just seeing something left in the framebuffer from the warm reboot. I'll have to take a look next time I'm near those machines. ** Description changed: Previous attempt to file resulted in a Launchpad timeout and lost screed, so here's the talk-like-the-Micro-Machines-guy version: 10.10 RC i386 Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux dmesg clogs with: [ 326.566996] serial8250: too much work for irq17 [ 326.580318] serial8250: too much work for irq17 [ 326.593635] serial8250: too much work for irq17 [ 326.606966] serial8250: too much work for irq17 [ 326.620285] serial8250: too much work for irq17 [ 326.633606] serial8250: too much work for irq17 oddly only until: [ 335.695389] serial8250: too much work for irq17 + on the boot I was reporting from; see comment #2 re: noticing this at all because it was ongoing under a different session and drowning out dmesg. Hardware: Compaq SR1611NX desktop - Not a problem under 9.10 using 2.6.31-22-generic #65-Ubuntu SMP Thu Sep - 16 15:48:58 UTC 2010 i686 GNU/Linux + Never observed as a continuous problem under 9.10 using + 2.6.31-22-generic #65-Ubuntu SMP Thu Sep 16 15:48:58 UTC 2010 i686 + GNU/Linux ; noise from https://bugs.launchpad.net/bugs/475704 may have + blocked ever noticing a short burst as above. All SR1611NXs put the modem, radeon, and AC97 controller on IRQ17; Forum folklore suggests pulling the modem could be the mindless fix but that would be annoying across multiple machines. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-22-generic 2.6.35-22.33 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - Cannot stat file /proc/4366/fd/40: Stale NFS file handle - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 2885 F pulseaudio + Cannot stat file /proc/4366/fd/40: Stale NFS file handle + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2885 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: - Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17' -Mixer name : 'Realtek ALC658D' -Components : 'AC97a:414c4781' -Controls : 38 -Simple ctrls : 24 + Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17' + Mixer name : 'Realtek ALC658D' + Components : 'AC97a:414c4781' + Controls : 38 + Simple ctrls : 24 Date: Sat Oct 2 01:46:01 2010 IwConfig: - lono wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth0 no wireless extensions. LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Release Candidate i386 (20100928) MachineType: Compaq Presario 061 ED866AA-ABA SR1611NX NA541 ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.38 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux dmi.bios.date: 01/25/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.15 dmi.board.name: Amberine M dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.version: dmi.modalias:
[Bug 475704] Re: Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424
To my delight, this does appear fixed with: Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux using the current 10.10 RC desktop CD (i386). I assume the patch referenced in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/475704/comments/18 landed? Unfortunately the machine still freezes with no display when resuming from suspend, probably unrelated. Unfortunately the ACPI chatter is replaced by as much serial8250: too much work for irq17 noise, but that's an unrelated bug.* *Footnote: Apparently due to presence of this modem, which happens to be sharing IRQ17 with the Radeon and AC97 controller, go figure. Will hunt down the right bug for this one... 02:09.0 Modem: Motorola SM56 Data Fax Modem (rev 04) (prog-if 00 [Generic]) Subsystem: Motorola Device 3020 Flags: bus master, stepping, medium devsel, latency 64, IRQ 17 Memory at fdcfd000 (32-bit, non-prefetchable) [size=4K] I/O ports at da00 [size=256] Capabilities: access denied Kernel driver in use: serial -- Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424 https://bugs.launchpad.net/bugs/475704 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 653388] [NEW] 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400)
Public bug reported: Previous attempt to file resulted in a Launchpad timeout and lost screed, so here's the talk-like-the-Micro-Machines-guy version: 10.10 RC i386 Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux dmesg clogs with: [ 326.566996] serial8250: too much work for irq17 [ 326.580318] serial8250: too much work for irq17 [ 326.593635] serial8250: too much work for irq17 [ 326.606966] serial8250: too much work for irq17 [ 326.620285] serial8250: too much work for irq17 [ 326.633606] serial8250: too much work for irq17 oddly only until: [ 335.695389] serial8250: too much work for irq17 Hardware: Compaq SR1611NX desktop Not a problem under 9.10 using 2.6.31-22-generic #65-Ubuntu SMP Thu Sep 16 15:48:58 UTC 2010 i686 GNU/Linux All SR1611NXs put the modem, radeon, and AC97 controller on IRQ17; Forum folklore suggests pulling the modem could be the mindless fix but that would be annoying across multiple machines. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-22-generic 2.6.35-22.33 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: Cannot stat file /proc/4366/fd/40: Stale NFS file handle USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2885 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17' Mixer name : 'Realtek ALC658D' Components : 'AC97a:414c4781' Controls : 38 Simple ctrls : 24 Date: Sat Oct 2 01:46:01 2010 IwConfig: lono wireless extensions. eth0 no wireless extensions. LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Release Candidate i386 (20100928) MachineType: Compaq Presario 061 ED866AA-ABA SR1611NX NA541 ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.38 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux dmi.bios.date: 01/25/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.15 dmi.board.name: Amberine M dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.15:bd01/25/2007:svnCompaqPresario061:pnED866AA-ABASR1611NXNA541:pvr0nx1411RE101AMBEM00:rvnASUSTekComputerINC.:rnAmberineM:rvr1.03:cvn:ct3:cvr: dmi.product.name: ED866AA-ABA SR1611NX NA541 dmi.product.version: 0nx1411RE101AMBEM00 dmi.sys.vendor: Compaq Presario 061 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kernel-config maverick needs-upstream-testing regression-potential -- 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400) https://bugs.launchpad.net/bugs/653388 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 653388] Re: 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400)
** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665334/+files/AcpiTables.txt ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665335/+files/AlsaDevices.txt ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665336/+files/AplayDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665337/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665338/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665339/+files/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665340/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665341/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665342/+files/Dependencies.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665343/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665344/+files/Lsusb.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665345/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665346/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665347/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665348/+files/ProcModules.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665349/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665350/+files/UdevLog.txt ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/653388/+attachment/1665351/+files/WifiSyslog.txt -- 10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400) https://bugs.launchpad.net/bugs/653388 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 630410] [NEW] Printer properties: Improve Test Page Self Test Page documentation
Public bug reported: Binary package hint: system-config-printer Using system-config-printer 1.2.0 on Ubuntu 10.04LTS, I recently discovered the true difference behind the Print Test Page and Print Self-Test Page buttons in a printer's properties dialog. Print Test Page appears to push the standard Ubuntu test page .ps through CUPS, and functions as expected. At the present time, Print Self-Test Page invokes print_self_test_page() in CUPS' filter/commandtops.c, recognizable by the short bit of Postscript and % You are using the wrong driver string spit out as plain text by the printer. Of course, through the local CUPS httpd, Maintenance-Print a Test Page prints the official *CUPS* test page (with palette circle and CUPS logo), while Maintenance-Print a Self Test Page sends the same Postscript directly to the non-Postscript printer. --- Problems: There is no Help available for the printer Properties dialog in system-config-printer. Currently the buttons and 'tooltips' available for test pages are: Print Test Page: CUPS test page Print Self-Test Page: Typically shows whether all jets on a print head are functioning and that the print feed mechanisms are working properly. Clearly these descriptions are somewhere between confusing and wrong. I would suggest at least amending the buttons and tooltips as follows: Print Test Page: Print a test page through CUPS as currently configured. Print Self-Test Page: Send a Postscript script to generate a test page directly to the printer. (For Postscript printers.) --- Now that I encounter these issues (and documentation issues) for the umpteenth time, I am reminded that we need to do something about terminology to stop pretending that we have monolithic drivers (specifically, there's a tendency to try to pretend that the PPD 'is' the driver, rather than that the PPD 'selects' the driver), and that it's ever always going to work [because if it's not the vendor driver, it's libusb, if it's not libusb, it's gs, if it's not gs, it's your application, and if it's not your application, maybe everything's working right but something's gone haywire with CUPS' state]. Note that Apple has essentially the *exact* same architecture with the exact same problems; they just have the benefit of peripheral vendors caring, and a somewhat slower release cycle (so once something works, it doesn't get broken by a new patch until next year). So if we have: CUPS, providing a standard spooler framework; The selected PPD, which: - Defines the properties of the printer as it appears to 'Postscript' applications; - Defines the print filter (with RIP, if necessary) Foomatic, playing the role of 'all-purpose swiss-army print filter whether-you-need-a-RIP-or-not' The RIP itself, in the form of the potentially fiddly vendor or open-source 'driver', generally relying on Ghostscript The communications mechanism (also part and parcel of the 'driver') ... Is there a way we can communicate this to the user without making them *wish* it was just a binary black box instead? If Help were actually available (beyond *only* troubleshooting), the article could at least make the point that 9 out of 10 of these functions are incorporated haphazardly within each driver package for certain commercial OSes, and the 'UNIX model' allows standardizing more of the commonly useful features (fit-to-page, N-up), and 'minimizing' what can go wrong. [Never mind that, by the time we get it all figured out, the price of ink and relatively simpler software issues will have made tablets the only way to go. ;)] ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: documentation interface opinion-piece papercut printing ui wishlist -- Printer properties: Improve Test Page Self Test Page documentation https://bugs.launchpad.net/bugs/630410 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 630410] Re: Printer properties: Improve Test Page Self Test Page documentation
Before I got lost in the wilderness, I wanted to communicate that the 'tip' or expanded documentation for the Print Self-Test Page button should ideally communicate: This sends a Postscript script to generate a test page directly to the printer. It is meant for Postscript printers, but may confirm communication by printing Postscript garbage if your printer supports 'plain text.' It makes no sense to write a novel in the tooltip, but a note about the 'also tests communication' could help, too. Or something could be refactored to store what bytes should be passed for the self-test page in the PPD, which would make a lot more sense [unless that already exists and just isn't being taken advantage of for my HP]. -- Printer properties: Improve Test Page Self Test Page documentation https://bugs.launchpad.net/bugs/630410 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 433438] Re: device descriptor read/64, error -110
I just noticed this 'regression?' on a 32-bit system running the prior 2.6.32.23 [meaning, I observed 'whups, it's broken again' on a machine that had been running that kernel for days or weeks] and an update to 2.6.32.24.25 did not immediately resolve it. The majority of USB devices, including the one I was trying to use [HP OfficeJet v40, scanner component via scanimage backend in gscan2pdf] are connected to the ports on the system's SB600 southbridge. Using the 'unbind' trick detailed above for the EHCI controller did not help. This configuration must have been working at some point, or we would have noticed earlier. I was at a loss after a few reboots until I tried a fully cold boot [as opposed to use of both soft-reboots and the reset switch], at which point the hardware is now 'happy' under 2.6.32.24.25 (and presumably would be under the prior kernel as well). Accordingly, please remember to give that a shot... and do mention if it's the only thing that works, as I suppose there could be an issue with the state 'warm' hardware comes up in. After the working boot, there is still with the following noise in dmesg, but the HP on 9-2 has 'always' been petulant like this: [ 60.184052] usb 9-2: new full speed USB device using ohci_hcd and address 10 [ 60.364041] usb 9-2: device descriptor read/64, error -62 [ 60.648033] usb 9-2: device descriptor read/64, error -62 [ 60.928045] usb 9-2: new full speed USB device using ohci_hcd and address 11 [ 61.108080] usb 9-2: device descriptor read/64, error -62 [ 61.392054] usb 9-2: device descriptor read/64, error -62 [ 61.672044] usb 9-2: new full speed USB device using ohci_hcd and address 12 [ 62.080046] usb 9-2: device not accepting address 12, error -62 [ 62.256040] usb 9-2: new full speed USB device using ohci_hcd and address 13 [ 62.664064] usb 9-2: device not accepting address 13, error -62 [ 62.664101] hub 9-0:1.0: unable to enumerate USB device on port 2 [ 74.084164] usb 9-2: new full speed USB device using ohci_hcd and address 14 [ 74.268064] usb 9-2: device descriptor read/64, error -62 [ 74.552063] usb 9-2: device descriptor read/64, error -62 [ 74.832051] usb 9-2: new full speed USB device using ohci_hcd and address 15 [ 75.012052] usb 9-2: device descriptor read/64, error -62 [ 75.300061] usb 9-2: device descriptor read/64, error -62 [ 75.568061] usb 9-2: new full speed USB device using ohci_hcd and address 16 [ 75.976043] usb 9-2: device not accepting address 16, error -62 [ 76.152061] usb 9-2: new full speed USB device using ohci_hcd and address 17 [ 76.560033] usb 9-2: device not accepting address 17, error -62 [ 76.560069] hub 9-0:1.0: unable to enumerate USB device on port 2 [ 117.306043] usb 9-2: new full speed USB device using ohci_hcd and address 18 [ 117.488058] usb 9-2: device descriptor read/64, error -62 [ 117.772052] usb 9-2: device descriptor read/64, error -62 [ 118.052056] usb 9-2: new full speed USB device using ohci_hcd and address 19 [ 118.232054] usb 9-2: device descriptor read/64, error -62 [ 118.520081] usb 9-2: device descriptor read/64, error -62 [ 118.800057] usb 9-2: new full speed USB device using ohci_hcd and address 20 [ 119.209054] usb 9-2: device not accepting address 20, error -62 [ 119.385055] usb 9-2: new full speed USB device using ohci_hcd and address 21 [ 119.796072] usb 9-2: device not accepting address 21, error -62 [ 119.796111] hub 9-0:1.0: unable to enumerate USB device on port 2 [ 311.280039] usb 7-1: new full speed USB device using ohci_hcd and address 2 [ 311.451784] usb 7-1: configuration #1 chosen from 1 choice ... [ 315.106835] hub 7-0:1.0: port 1 disabled by hub (EMI?), re-enabling... [ 315.106849] usb 7-1: USB disconnect, address 2 ... [ 321.920040] usb 9-2: new full speed USB device using ohci_hcd and address 22 [ 322.132562] usb 9-2: configuration #1 chosen from 1 choice Note that nothing?, except possibly a USB KVM, is connected to bus 7. Bus 009 Device 022: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 03f0:0f11 Hewlett-Packard OfficeJet V40 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 003 Device 002: ID 10d5:0116 Uni Class Technology Co., Ltd Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 008: ID 062a: Creative Labs Optical mouse Bus 001 Device 007: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 001 Device 006: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card
[Bug 616097] [NEW] Dell D600 - 10.04 boot hang (livecd/post-install)
Public bug reported: This is being somewhat annoying to track down, so I'm posting with the minimal information I have in case there's a quick, known fix -- or, vexingly, if it helps confirm I'm the only person in the world who can reproduce this problem, since there seem to be other users describing no issue. Symptoms: Attempting to boot from the LiveCD, or from a fresh install with the alternate CD, results in a hang around the time the boot splash animation reaches the final 'dot.' The boot splash animation also comes up with a corrupt/'psychedelic' palette. The graphic stays frozen on the screen, the fan runs, and the keyboard becomes unresponsive, making troubleshooting annoying. Booting the alternate CD to the console works. Somewhat quirkily, an install from the alternate CD also worked when rebooted after the apparent hang, but something (a post-install script?) got addled, because I can both reach the console or startx with no problem, but dbus was not starting properly and gdm et al. refused to work. I looked around for the obvious culprit on *that* but couldn't find it, and right now I'm trying to remove variables and achieve a normal installation, not add more. Since the base system does boot fine in that circumstance, I guess I'm looking at something more X or firstboot- related, but I don't know what. Booting/installing 9.04 or thereabouts actually works, so it does not seem to be an innate hardware problem - but sitting through upgrades from there to 'present' is a workaround too awkward to test just yet. Hardware configuration: Dell Latitude D600 laptop; 512MB RAM; 1024x768 LCD with what identifies as a RV250; only hardware quirks are use of a UDMA CompactFlash card in place of a disk and use of a generic Realtek-based miniPCI wireless card. If someone can summarize the parameters necessary to turn graphical boot off and watch dmesg/console up to the point that it hangs, I'd appreciate it. ** Affects: ubuntu Importance: Undecided Status: New -- Dell D600 - 10.04 boot hang (livecd/post-install) https://bugs.launchpad.net/bugs/616097 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 595650] Re: After the last updates HP printer stopped working
@Cesare Mastroianni: Regarding the double-sided printing trouble, have you confirmed you are using the same version of hplip as before the update that gave you the troublesome libusb (check /var/log/apt/history.log for what else was installed in the update that gave you libusb-0.1-4 0.1.12-14ubuntu0.1)? If it's a regression compared to an older hplip, you want to file a bug against it at https://bugs.launchpad.net/ubuntu/+source/hplip/ . 0.1.12-14 was the libusb-0.1-4 released with lucid [the only version available until now], and you observed it broken after downgrading back to that, so it smells like hplip to me. @world: I didn't see the .1 in the original versioning, so my advice to use: aptitude forbid-version libusb-0.1-4=2:0.1.12-14ubuntu0 will exclude the patched patch too, oops! It should have read: aptitude forbid-version libusb-0.1-4=2:0.1.12-14ubuntu0.1 If you don't have the lucid-proposed repo enabled, it looks like you can undo this overbroad 'forbid-version' by running: aptitude install libusb-0.1-4=2:0.1.12-14ubuntu0.2 and saying 'No' to its intention to install libusb-0.1-4=2:0.1.12-14ubuntu0.1 when ...ubuntu0.2 is not available. Then you can run the correct: aptitude forbid-version libusb-0.1-4=2:0.1.12-14ubuntu0.1 to only exclude the bad version, and accept ...ubuntu0.2 when it's approved. -- After the last updates HP printer stopped working https://bugs.launchpad.net/bugs/595650 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 595650] Re: After the last updates HP printer stopped working
It's fairly common to have the legacy or stable branch of a library installed concurrently with its current or development branch. This generally indicates that the interface [is assumed to have] changed between libusb-0.1 and libusb-1.0 such that consumers of the former can't just relink against the latter. Juggling the version numbers without introducing human error in referencing them is another matter! -- After the last updates HP printer stopped working https://bugs.launchpad.net/bugs/595650 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 595650] Re: After the last updates HP printer stopped working
@Cesare Mastroianni: Try specifying libusb-0.1-4 rather than libusb. Upstream http://www.libusb.org/ gives some background for that naming convention [it should be possible to install the legacy libusb-0.1-4 and stable libusb-1.0-0 concurrently if you ever need to], though why the -4 became codified is beyond me at the moment. :) -- After the last updates HP printer stopped working https://bugs.launchpad.net/bugs/595650 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 595650] Re: After the last updates HP printer stopped working
@Till Kamppeter: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/602560 It takes this bug to trigger that behavior in gscan2pdf, and without realizing the cause it made scanning look broken after backing out the bad libusb. So worth documenting here while reporting there. :) -- After the last updates HP printer stopped working https://bugs.launchpad.net/bugs/595650 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 595650] Re: After the last updates HP printer stopped working
Tangentially related to this: If gscan2pdf suddenly refuses to show any device-dependent options (such as DPI or color vs. grayscale mode) for the scanner on your multifunction [perhaps due to this bug or side- effects of attempts to correct it], use the Clear device-dependent options cache feature in gscan2pdf's Edit-Preferences menu. This was not terribly obvious, since it takes some exploring to discover there's a 'cache' - it's on by default, since it cuts out some of the wait in normal usage. In my case it cached some sort of corrupt result while unable to communicate with the scanner, and misled me into thinking that the scanimage backend must have remained broken. [Moral of this story: When in doubt, remember to rename .gscan2pdf aside, or test under a fresh user account.] I guess I'll open a bug on gscan2pdf to suggest offering a Refresh cache? right in the Scan-Options dialog when the cached configuration is corrupt. -- After the last updates HP printer stopped working https://bugs.launchpad.net/bugs/595650 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 602560] [NEW] device-dependent options cache inobvious
Public bug reported: Binary package hint: gscan2pdf As described over at https://bugs.launchpad.net/hplip/+bug/595650/comments/43 and observed with gscan2pdf-0.9.29-1ubuntu1 Under certain conditions [#595650], the device-dependent options cache can become corrupt [for a particular combination of backend and device] and begin displaying a blank options dialog. Even advanced users may not be aware a cache exists and will spend time hunting elsewhere. Possible fixes: * Detect a 'blank' device-dependent options state and present a very noticable 'Refresh cache?' button; [Clever] * Detect a 'blank' device-dependent options state and automatically try to refresh the cache; [Good idea; loop-prone?] * Squish a small 'Refresh' icon into the 'Options' tab of the Scan dialog under all circumstances to hint that a cache exists and can be refreshed; [Easiest to implement, nonmodal] * Stop enabling the cache by default [Solves the problem, but pessimistic to responsiveness] I'm going to attach the .gscan2pdf which triggers this, cwd and serial numbers REDACTED; of course the device URI has to be edited to match a detected device to actually get the program to use the bad cache. ** Affects: gscan2pdf (Ubuntu) Importance: Undecided Status: New -- device-dependent options cache inobvious https://bugs.launchpad.net/bugs/602560 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 602560] Re: device-dependent options cache inobvious
** Attachment added: bad_cache-.gscan2pdf http://launchpadlibrarian.net/51497914/bad_cache-.gscan2pdf -- device-dependent options cache inobvious https://bugs.launchpad.net/bugs/602560 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 602560] Re: device-dependent options cache inobvious
** Attachment added: Screenshot with corrupt cache. Did scanimage break? Nope, it's the cache! http://launchpadlibrarian.net/51497930/Screenshot-Scan%20Document.png -- device-dependent options cache inobvious https://bugs.launchpad.net/bugs/602560 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 595650] Re: after the last updates printer stopped working
@Johan Stenlund, and anyone else stymied, the incantation you are looking for is: aptitude forbid-version libusb-0.1-4=2:0.1.12-14ubuntu0 (Or use apt-get's same 'downgrade' feature directly.) It would also help [me] to remember that /var/log/apt/history.log exists when trying to recover from a bad update. (Has anyone thought of having update-manager create and install local meta-package .debs instead of installing directly for ease of backing out after a SNAFU? Does apt even support that? Belongs on Brainstorm, not in this bug, but I'll type it here while it's fresh...) Nice detective work on this one! -- after the last updates printer stopped working https://bugs.launchpad.net/bugs/595650 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 495648] Re: Karmic / 9.10: Automagic printing of legal, letter, multiple size pages to PostScript printer fails (Regression from 8.04)
Automatic notification, manual comment: I'm holding off on upgrading those machines until I have a moment to breathe, so I can't comment at the moment but will report back when I've had the chance. -- Karmic / 9.10: Automagic printing of legal, letter, multiple size pages to PostScript printer fails (Regression from 8.04) https://bugs.launchpad.net/bugs/495648 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 544994] Re: the rhythmbox mtp code hijacks cameras
If it was fixed in 0.12.8-0ubuntu2 it's now regressed in 0.12.8-0ubuntu3 on my fresh Lucid upgrade. lsof snippet: gvfs-gpho 6062 floid 13u CHR189,146 0t02544556 /dev/bus/usb/002/019 ... rhythmbox 6244 floid 43u CHR189,146 0t02544556 /dev/bus/usb/002/019 Rhythmbox gets hung up sleeping (Sl state) as soon as the camera is connected / if it is run with the camera connected. This causes the ever-complained-of Error mounting location: Error initializing camera: -60: Could not lock the device from gphoto2 and its consumers. At some point I got a -1 error out of it as well. Of course it's an unexpected race depending whether gphoto2/F-Spot/similar is run before Rhythmbox or not. But with Rhythmbox closed, the device actually works as a PTP camera in F-Spot, much to my relief, and it even gvfs mounts (so turns out I'm not affected by another bug I thought I was). Observed with a Kodak Easyshare Z1485 IS: Bus 002 Device 019: ID 040a:05c8 Kodak Co. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x040a Kodak Co. idProduct 0x05c8 bcdDevice1.00 iManufacturer 1 Eastman Kodak Company iProduct2 KODAK EASYSHARE Z1485 IS Digital Camera iSerial 3 KCXKF92400305 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 16 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered -- the rhythmbox mtp code hijacks cameras https://bugs.launchpad.net/bugs/544994 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 570087] Re: Canon camera not auto mounted by gphoto2 backend, manually accessing gphoto2://[usb:id] works though
I thought I was bitten by this, but discovered I was affected by LP#544994 instead (Rhythmbox improperly trying to open USB PTP camera). This might be a different issue, but since it was very inobvious, make sure Rhythmbox is not running when testing. -- Canon camera not auto mounted by gphoto2 backend, manually accessing gphoto2://[usb:id] works though https://bugs.launchpad.net/bugs/570087 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 475704] Re: Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424
I did some scraping around after my last comment and determined that the closest thing to a proper venue 'upstream' would be http://acpica.org/bugzilla/ , but someone ought to do due-diligence and make sure the collateral issues in #7 here aren't magically resolved in their bleeding-edge code first. (Again, the patch regarding the ByteAcc vs. WordAcc should fix the bug found here, but the fatal compiler errors about the _PSW method smell like they could be due to changes between the version of the ACPI standard the original authors of the HPaq code targeted vs. what iasl supports compiling. Determining the correct workaround for *that* seems to require someone who can parse the actual workings of the code, rather than just respond to 'obvious' error messages as I did. :)) I have a bunch of other stuff on my plate at the moment [real life/the day job], so if anyone can run with that thought I'd appreciate it. -- Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424 https://bugs.launchpad.net/bugs/475704 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 475704] Re: Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424
As I found above, it's a simple and silly type error, but the more thorny fatal incompatibility between recent iasl and the original code is beyond my familiarities. Running the simple patch through the Microsoft compiler would probably do the trick, but it would take someone with a bit more familiarity (half a clue) to 'port' around that _PSW SNAFU. Anyone able to flag down such a person? -- Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424 https://bugs.launchpad.net/bugs/475704 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 444235] Re: [6.311772] ACPI: I/O resource piix4_smbus [0b00-0xb07] conflicts with region SOR1 [0xb00-0xb0f] on KUBUNTU Karmic boot
Aside from any more obvious lmsensors breakage, the inability to load piix4_smbus blocks the ability to use `decode-dimms` from i2ctools on these AMD systems, which is annoying. -- [6.311772] ACPI: I/O resource piix4_smbus [0b00-0xb07] conflicts with region SOR1 [0xb00-0xb0f] on KUBUNTU Karmic boot https://bugs.launchpad.net/bugs/444235 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 493961] Re: some apps in System Administration do not work with sudo
Thought I'd heard something about this and was glad to find the background here. I was reminded while catching both the punt-users-on-shutdown-warning and CPU Frequency Scaling Monitor applet being smart enough to ask for the password for the local superuser while e.g. Synaptic still doesn't. I'll mark myself affected since it would be convenient to run Synaptic from a running X session without having to ssh -X localhost as my privileged user*, but it's more a wishlist for 10.04 than a killer bug here. *On that particular machine, to avoid dozens of what's-the-password? calls, I put the 'usual' unprivileged user into a localusers group, gave it a hard random password, and rigged up some pam magic to make a local login through gdm sufficient without a password. This apes Windows' behavior for users without passwords - and if anyone is looking for a project, it'd be nice to codify that as a feature in Ubuntu so I don't have to remember what I did there on every upgrade. ;) -- some apps in System Administration do not work with sudo https://bugs.launchpad.net/bugs/493961 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108623] Re: totem isn't buffering correctly
Observed annoying with totem-gstreamer 2.28.2-0ubuntu3, whether in the browser plugin or natively in Totem. I haven't fiddled with any of the gconf settings, I did go in and tell Totem I have 1.5Mbps T1/Intranet/LAN (which is true, 1.5mbit/s ATT DSL - though that does mean it craps out just shy of a full 1.5mbits after PPP and line overhead). I could go in and poke at it, but I shouldn't really have to, right? More annoying is the failure to cache, combined with a failure to seek properly [either refuses to seek back at all or jumps back to 0:00], which I've been hunting for the (surely-existing) bug for. Seen with http://static.tvpaint.com/community/gallery/content/Filmakademie_Urs_Trailer.mp4 and other sample content on that site if anyone's looking for more test cases. @#29: mplayer has been the de-facto I-just-want-it-to-work-on-UNIX player for a while (and still has major performance advantages on sub- GHz systems), but gstreamer and Totem are supposed to offer GNOME the conveniences DirectShow and Quicktime do for the Other Major Platforms. So it'd be nice if they actually functioned properly. -- totem isn't buffering correctly https://bugs.launchpad.net/bugs/108623 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 475704] Re: Karmic desktop livecd constant kernel ACPI exception messages: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-424
Hmm. Happened to be at the machine when I saw the last comment, so I decided
to poke at it.
Attempting to recompile my SR1611NX DSDT with iasl (note that the -dc option
doesn't seem to be working as advertised, but simply running `iasl DSDT.dsl`
works at the expense of obliterating the contents of the directory, and `iasl
-c DSDT.dsl` will try the same but create an empty .aml and a populated .src -
I guess because the errors prevent it from actually generating the .aml).
...
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
DSDT.dsl 284: Method (\_WAK, 1, NotSerialized)
Warning 1080 - ^ Reserved method must return a value (_WAK)
DSDT.dsl 410: WBYT (TSAD, 0x4F, Local0)
Error4050 -^ Method local variable is not
initialized (Local0)
DSDT.dsl 632: CSMS ()
Warning 1099 -^ Statement is unreachable
DSDT.dsl 646: CSMS ()
Warning 1099 -^ Statement is unreachable
DSDT.dsl 1406: Name (_PSW, 0x01)
Error4078 - ^ Reserved name must be a control
method (with arguments)
DSDT.dsl 1428: Name (_PSW, 0x01)
Error4078 - ^ Reserved name must be a control
method (with arguments)
DSDT.dsl 1450: Name (_PSW, 0x01)
Error4078 - ^ Reserved name must be a control
method (with arguments)
DSDT.dsl 2985: Field (SECF, WordAcc, NoLock, Preserve)
Error4027 - ^ Access width is greater than region size
DSDT.dsl 2987: SCFN, 8
Error4028 -^ Access width of Field Unit extends beyond
region limit
DSDT.dsl 3534: Method (IPHP, 2, NotSerialized)
Warning 1087 -^ Not all control paths return a value
(IPHP)
DSDT.dsl 3888: If (LEqual (HGDT (Local1), 0x01))
Warning 1092 -^ Called method may not
always return a value
DSDT.dsl 3912: If (LEqual (IPHP (0x06,
Local1), Local3))
Warning 1092 -Called method may not always return a value ^
DSDT.dsl 3946: Method (HGDT, 1, NotSerialized)
Warning 1087 -^ Not all control paths return a value
(HGDT)
DSDT.dsl 3994: And (IPHP (0x07, Arg0), Arg1, Local2)
Warning 1092 - ^ Called method may not always
return a value
ASL Input: DSDT.dsl - 5409 lines, 165894 bytes, 1913 keywords
Compilation complete. 6 Errors, 8 Warnings, 0 Remarks, 626 Optimizations
...
I know slightly less than enough about ACPI to be dangerous; this is
what I've been able to figure out thus far:
Our troublesome GPE.L09 is a General Purpose Event register.. but I
wish I had a clue what that SMFN method that relates to it is
[supposed to be] doing.
As to what iasl dislikes (but MSFT Compiler Version 0x010E (16777230)
obviously was happy to generate):
In the STOS method:
DSDT.dsl 410: WBYT (TSAD, 0x4F, Local0)
Error4050 -^ Method local variable is not
initialized (Local0)
...the failure to initialize can be cured by a Store (Zero, Local0)
before that line. I'm not sure if that's really the right thing to do
or not since I have no clue what it's writing to and how the MSFT
compiler would treat the unassigned variable [looks like the arguments
there are address, command, data].
DSDT.dsl 1406: Name (_PSW, 0x01)
Error4078 - ^ Reserved name must be a control
method (with arguments)
DSDT.dsl 1428: Name (_PSW, 0x01)
Error4078 - ^ Reserved name must be a control
method (with arguments)
DSDT.dsl 1450: Name (_PSW, 0x01)
Error4078 - ^ Reserved name must be a control
method (with arguments)
These are tricky; thus far all I've found is that _PSW (power state
wake) was part of ACPI 1.0, and was deprecated by ACPI 3.0 - but
'deprecated' shouldn't mean 'keels over and fails,' right? Or is
something very malformed here?
DSDT.dsl 2985: Field (SECF, WordAcc, NoLock, Preserve)
Error4027 - ^ Access width is greater than region size
DSDT.dsl 2987: SCFN, 8
Error4028 -^ Access width of Field Unit extends beyond
region limit
Could be the big culprit -
Mutex (FLMX, 0x00)
OperationRegion (SECF, SystemMemory, 0x000F97E0, 0x01)
Field (SECF, WordAcc, NoLock, Preserve)
{
SCFN, 8
}
...it's trying to access a region declared to be byte-sized with the
WordAcc size. Using ByteAcc instead cures that.
[Bug 433817] Re: Gnome hang
This is an annoyance and can also occur with gnome-panel alone (I am not a Gnome Do user, but just got into a 'stuck' drag situation accidentally dragging from Nautilus to the Window List or vice-versa). At least, I assume gnome-panel is part of the problem, but killing both Nautilus and it failed to release the drag. Removing and replugging the USB mouse got some limited keyboard focus back, but also didn't release the drag this time, and window manager bindings were still hosed (no Alt-Tab or workspace switching). [Hmm... not a Compiz user there either, maybe I should've given metacity a kick.] This observed on Karmic, wherein the Xorg cursor remains stuck as the drag and copy cursor similar to: http://developer.gnome.org/projects/gup/hig/draft_hig_new/images/input-drag-cursor.png and no clicks are passed through / the icon is impossible to 'drop.' Expected behavior would be for the 'stickiness' to not happen in the first place and for Escape to release it if it does. Anyone know if there's a bug upstream for this? -- Gnome hang https://bugs.launchpad.net/bugs/433817 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 259513] Re: The Floid's Floppy Issues Tracking Bug (8.04)
#244304 re: USB floppies is long-since resolved. Let me retarget this one at the SB600 + legacy floppy combo, which I just had a chance to test again and discovered it remains broken as of 9.10, Linux hostname 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux: [910731.568023] [910731.568033] floppy driver state [910731.568037] --- [910731.568044] now=227607892 last interrupt=227607143 diff=749 last called handler=f80bd700 [910731.568050] timeout_message=floppy start [910731.568053] last output bytes: [910731.568057] 13 90 4294896060 [910731.568062] 0 90 4294896060 [910731.568066] 1a 90 4294896060 [910731.568070] 0 90 4294896060 [910731.568073] 3 90 4294896060 [910731.568077] c1 90 4294896060 [910731.568081] 10 90 4294896060 [910731.568085] 7 80 4294896060 [910731.568088] 0 90 4294896060 [910731.568092] 8 81 4294896060 [910731.568096] f 80 4294896061 [910731.568100] 0 90 4294896061 [910731.568103] 1 91 4294896061 [910731.568107] 8 81 4294896062 [910731.568111] 4 80 227607142 [910731.568115] 0 90 227607142 [910731.568118] f 80 227607142 [910731.568122] 0 90 227607142 [910731.568126] 0 91 227607142 [910731.568130] 8 81 227607143 [910731.568133] last result at 227607143 [910731.568137] last redo_fd_request at 227607142 [910731.568140] 20 0 [910731.568156] status=80 [910731.568160] fdc_busy=1 [910731.568163] fd_timer.function=f80bd430 [910731.568167] cont=f80c254c [910731.568170] current_req=c2fa1578 [910731.568174] command_status=-1 [910731.568177] [910731.568184] floppy0: floppy timeout called [910731.568192] end_request: I/O error, dev fd0, sector 0 [910746.756016] [910746.756023] floppy driver state [910746.756027] --- [910746.756034] now=227611689 last interrupt=227610939 diff=750 last called handler=f80bd500 [910746.756039] timeout_message=floppy start [910746.756042] last output bytes: [910746.756047] f 80 227607142 [910746.756051] 0 90 227607142 [910746.756055] 0 91 227607142 [910746.756059] 8 81 227607143 [910746.756063] 8 80 227610803 [910746.756067] 8 80 227610803 [910746.756071] 8 80 227610803 [910746.756075] 8 80 227610803 [910746.756079] 12 80 227610939 [910746.756082] 0 90 227610939 [910746.756086] 13 90 227610939 [910746.756090] 0 90 227610939 [910746.756093] 1a 90 227610939 [910746.756097] 0 90 227610939 [910746.756101] 3 90 227610939 [910746.756105] c1 90 227610939 [910746.756109] 10 90 227610939 [910746.756113] 7 80 227610939 [910746.756116] 0 90 227610939 [910746.756120] 8 81 227610939 [910746.756123] last result at 227610939 [910746.756127] last redo_fd_request at 227610939 [910746.756130] 20 0 [910746.756144] status=80 [910746.756148] fdc_busy=1 [910746.756151] fd_timer.function=f80bd430 [910746.756155] cont=f80c254c [910746.756158] current_req=c2fa1190 [910746.756162] command_status=-1 [910746.756165] [910746.756172] floppy0: floppy timeout called [910746.756179] end_request: I/O error, dev fd0, sector 0 [910772.276019] [910772.276026] floppy driver state [910772.276029] --- [910772.276036] now=227618069 last interrupt=227617457 diff=612 last called handler=f80bd700 [910772.276041] timeout_message=floppy start [910772.276044] last output bytes: [910772.276048] 13 90 227617319 [910772.276053] 0 90 227617319 [910772.276057] 1a 90 227617319 [910772.276061] 0 90 227617319 [910772.276064] 3 90 227617319 [910772.276068] c1 90 227617319 [910772.276072] 10 90 227617319 [910772.276075] 7 80 227617319 [910772.276079] 0 90 227617319 [910772.276082] 8 81 227617319 [910772.276086] f 80 227617319 [910772.276090] 0 90 227617319 [910772.276094] 1 91 227617319 [910772.276097] 8 81 227617320 [910772.276101] 4 80 227617456 [910772.276105] 0 90 227617456 [910772.276108] f 80 227617456 [910772.276112] 0 90 227617456 [910772.276116] 0 91 227617456 [910772.276119] 8 81 227617457 [910772.276122] last result at 227617457 [910772.276126] last redo_fd_request at 227617319 [910772.276130] 20 0 [910772.276144] status=80 [910772.276147] fdc_busy=1 [910772.276150] fd_timer.function=f80bd430 [910772.276154] cont=f80c254c [910772.276158] current_req=c2fa1320 [910772.276161] command_status=-1 [910772.276164] [910772.276170] floppy0: floppy timeout called [910772.276179] end_request: I/O error, dev fd0, sector 0 [910781.317015] [910781.317023] floppy driver state [910781.317026] --- [910781.317033] now=227620329 last interrupt=227619579 diff=750 last called handler=f80bd500 [910781.317039] timeout_message=floppy start [910781.317043] last output bytes: [910781.317047] f 80 227617456 [910781.317051] 0 90 227617456 [910781.317055] 0 91 227617456 [910781.317059] 8 81 227617457 [910781.317063] 8 80 227619443 [910781.317067] 8 80 227619443 [910781.317070] 8 80 227619443 [910781.317074] 8 80 227619443 [910781.317077] 12 80 227619579 [910781.317081] 0 90 227619579 [910781.317085] 13 90 227619579 [910781.317089] 0 90 227619579 [910781.317092] 1a 90 227619579
[Bug 357457] Re: fglrx causing APIC errors on AMD 780G
No longer an issue for me with fglrx 2:8.660-0ubuntu4, linux 2.6.31-17.54 (==2.6.31.17.30? I am not so familiar with interpreting dpkg-query output yet.). I'd mark it resolved, but how are things for the 8.04LTS crowd? -- fglrx causing APIC errors on AMD 780G https://bugs.launchpad.net/bugs/357457 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 259513] apport-collect data
Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: floid 21140 F pulseaudio /dev/snd/pcmC0D0p: floid 21140 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfbbf4000 irq 16' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,104382fe,00100101' Controls : 40 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbde8000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=d4cd04c8-c662-4a61-bfed-f58ca29423d7 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: fglrx Package: linux (not installed) ProcCmdLine: root=UUID=e7772abe-e959-48eb-94a8-e959bf693309 ro quiet splash ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-17.54-generic RelatedPackageVersions: linux-backports-modules-2.6.31-17-generic N/A linux-firmware 1.25 RfKill: Uname: Linux 2.6.31-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare WpaSupplicantLog: dmi.bios.date: 03/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd03/27/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- SB600 w/legacy floppy still a problem - start at LP comment #6 https://bugs.launchpad.net/bugs/259513 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 259513] AlsaDevices.txt
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/38027570/AlsaDevices.txt -- SB600 w/legacy floppy still a problem - start at LP comment #6 https://bugs.launchpad.net/bugs/259513 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
